Ripple said asset managers are preparing for the XRP Ledger’s next payments upgrade, an amendment called Batch V1.1 that makes linked asset and payment transfers succeed together or fail together, with activation projected for Sept. 29.
What Batch V1.1 changes
Multi-step trades on the XRP Ledger currently settle as separate transactions. If the second leg of a trade fails, the first leg has already gone through, and one side is left holding the risk. Batch V1.1 groups linked transfers into a single all-or-nothing unit: either every leg settles, or none does.
Consider the trade a fund manager actually makes. A tokenized money market fund position needs to become USDC. Without batching, that is two transactions, and each side has to trust the other or wrap the trade in escrow. With Batch, the ledger enforces both sides at once. If the stablecoin leg bounces, the share transfer reverses with it.
That protection is standard in traditional finance, where delivery-versus-payment is so baked into settlement that traders rarely think about it. Tokenized markets have had to rebuild it piece by piece, and most chains do it through smart contracts, which push the work and the risk onto developers. The XRP Ledger’s version keeps execution in the protocol itself, closer to how an exchange matching engine behaves. Ripple said commercial projects are already being built around the capability.
The amendment also covers payments between people, not just fund trades. Payroll runs, subscription billing and market maker rebalancing all share the same structure: a set of transfers that only makes sense if all of them land. A batch that fails as a whole returns every asset to its starting point, which turns a reconciliation problem into a simple retry.
Activation math
The amendment’s countdown began Sept. 15 at 14:06:41 UTC. Under the ledger’s rules, Batch V1.1 activates shortly after the same time on Sept. 29 if validator support holds at or above 80% for the entire 14-day window. Validators can change their votes, which makes the date conditional rather than fixed. If support dips below the threshold, the countdown resets and the amendment waits for consensus again, as earlier XRPL amendments have.
Eighty percent sounds like a high bar, but the XRP Ledger’s Unique Node Lists make it reachable: validators signal support by voting for the amendment, and Ripple runs only part of the network. Independent exchanges, wallet operators and other operators hold the rest of the votes. The design keeps any single company, Ripple included, from forcing an upgrade through alone.
The security work behind it was broad. Ripple’s review included internal adversarial testing, AI-assisted analysis, a Sherlock attack contest and assessments by the firms Halborn and Common Prefix. Earlier versions of the proposal carried flaws that had to be fixed before the countdown could start, which is one reason the amendment took its time.
Batch has been in the works for months. The proposal went through several revisions after the security review flagged issues in earlier drafts, and the Sept. 15 countdown only started once the fixes were in. That pace is deliberate. The ledger’s amendment system does not ship anything until an overwhelming majority of operators agree it is safe, and a settlement primitive aimed at institutional money draws more scrutiny than most.
Where this sits for XRP
The upgrade lands in a busy stretch for the ledger. The core software, xrpld 3.4.0, shipped this week with new lending protocol amendments, extending the chain’s push into on-chain credit. Ripple’s institutional pitch has shifted over the past year from cross-border payments toward tokenized funds and stablecoin settlement, and batch execution is the piece that makes multi-asset trades safe enough for fund managers to touch.
Ripple has spent the year courting asset managers with RLUSD, its own stablecoin, at the center of the offer. Batch settlement is aimed at the point where tokenized funds and stablecoins meet, which is where the company sees the payments business moving. The upgrade also matters for the ledger’s decentralized exchange, where batched orders remove the partial-fill problem that has kept larger traders cautious about size.
For the decentralized exchange in particular, the change is worth spelling out. Today, a large order that cannot fill completely either sits on the book or fills in part, leaving the trader exposed to the remainder. Batched offers let a trader state the whole trade as one condition, fill everything or walk away. Market makers in traditional venues have had this for decades through all-or-none order types. Bringing the same control on-chain lowers the barrier for desks that trade size.
The market backdrop is quieter. XRP trades near $1.40, and cumulative inflows into US spot XRP ETFs have stalled at $1.71 billion, with weekly totals shrinking for three straight weeks. Product development and price are moving in opposite directions, a split that has defined the asset since the funds launched.
For ledger watchers, the comparison that matters is with other settlement rails. Ethereum settles atomic trades through smart contracts, which give developers full control at the cost of complexity and gas risk. Solana compresses settlement into fast block times. The XRP Ledger is betting that protocol-level batching, with a validator set institutions can inspect, is the version fund managers will pick. Sept. 29 is the next checkpoint for that bet.
If the vote holds, Batch V1.1 goes live without any action from users. Wallets and exchanges that want to offer batched transactions will need to update their software to build the new transaction type, so real-world usage will ramp over weeks rather than on activation day itself.