Ripple Prepares XRP Ledger For Major Batch Upgrade
Ripple says asset managers and commercial projects are readying themselves for the XRP Ledger's next major payments upgrade, as a rebuilt version of the Batch amendment approaches a mainnet a
A
AnonymousCryptoCompass newsroom
September 21, 2026
3 min read
NEWS
CryptoCompass editorial visual for altcoins coverage.
Ripple says asset managers and commercial projects are readying themselves for the XRP Ledger's next major payments upgrade, as a rebuilt version of the Batch amendment approaches a mainnet activation date of September 29.
What Batch V1.1 Does
The feature, called Batch V1.1, can combine as many as eight transactions into a single operation. Its all-or-nothing mode ensures that every transaction succeeds or the entire group is canceled, avoiding cases in which one side of a deal settles while the other fails.
The change would allow several transactions from different accounts to run together in one ledger close, so applications could package related instructions to be evaluated as a coordinated unit rather than submitting each step separately and hoping every leg settles. Two parties exchanging tokens could require both transfers to complete together, a custody move could be paired with the matching payment, and a wallet or marketplace could collect a platform fee in the same operation as a customer payment. Ripple has specifically flagged delivery-versus-payment as a core use case, though the company has not publicly named the asset managers or disclosed firm launch dates.
A Rebuilt Amendment After a Critical Security Flaw
Batch V1.1 is not arriving without history. In February 2026, security researchers and Cantina AI found a critical flaw in the original Batch design while it was still awaiting activation. A signature-validation routine returned success too early when it encountered a signer whose account did not yet exist on the ledger, skipping checks on remaining signers. That logic error could have allowed unauthorized inner transactions, but because the amendment had not gone live, no funds were at risk.Trusted validators were advised to vote against it, and an emergency software release marked the original Batch code unsupported.
Developers subsequently released V1.1 with redesigned authorization and reviews by Halborn and Common Prefix.Batch V1.1 is the replacement shipped in xrpld version 3.3.0.
Validator support for the upgraded amendment is now strong. The amendment has support from 30 of the XRP Ledger's 35 tracked validators, above the 28 votes required to enter its activation countdown, which began September 15 at 14:06:41 UTC.The XRP Ledger's amendment system demands that a proposal remains above 80% support for two consecutive weeks before being permanently integrated into the protocol.Batch V1.1 is projected to activate shortly after the same time on September 29, provided support remains at or above 80% for the full 14-day window, though validators can change their votes, making the date conditional.
Binance Red Packet Code 22 September 2026: Today’s Answer Want to receive free cryptocurrency on Binance without purchasing, trading, or staking assets? The daily Binance Red Packet Code offe
Altcoins are taking the lead as Bitcoin holds above $83,000, but the latest market move comes with a warning for traders watching for a full altseason. NEAR, Avalanche and Sui are posting dou
The European Central Bank (ECB) is bringing traditional finance on-chain with the launch of Pontes, a new platform connecting its TARGET settlement system directly to blockchain-based financi