What happened
CoinDesk reported Monday that Batch V1. 1, a protocol amendment on the XRP Ledger, is one validator vote away from activation. The current tally sits at 27 of 35 trusted validators on the default Unique Node List, one short of the two-thirds supermajority XRPL amendments require before a fourteen-day activation timer starts.
The amendment introduces atomic transaction batching. Users would be able to submit up to eight linked transactions that either all succeed or all fail as a single operation. That is a meaningful change to how the ledger handles multi-step payment flows, which today have to be stitched together off-chain and reconciled after the fact.
Ripple's C++ engineering team wrote the reference implementation, and independent operators, exchanges, and Ripple-run validators are the ones voting.
Why it matters
XRPL's core pitch has always been payments settlement, and Batch V1. 1 is the piece that lets developers build genuinely composable payment logic on top of it. Bundle a currency swap, a fee payment, and a settlement instruction into one atomic call and either the whole thing clears or none of it does.
That removes an entire class of half-executed transactions that ops teams currently have to unwind manually. It also opens the door to more sophisticated DEX routing on the ledger's native order book, cleaner escrow flows, and the kind of multi-leg trades that Ethereum's account abstraction crowd has been iterating on for two years. The headline number, 27 of 35, is not a done deal.