Default
Door Remote - 19 Sep 2026
Batch could also let exchanges, wallets and marketplaces attach their service charges directly to a customer transaction. A payment and the platform’s fee could be processed as one operation rather than through separate transfers.
“Some projects are already being built with Batch in mind, so activation would allow that work to move closer to production,” Akinyele shared. “We’ll share more on specific partners and launch timing as those plans are finalized.”
The amendment has support from 30 of the XRP Ledger’s 35 tracked validators, above the 28 votes required to enter its activation countdown.
Feature arrives after earlier flaws fixedThat countdown began Sept. 15 at 14:06:41 UTC. Batch V1.1 is projected to activate shortly after the same time on Sept. 29, provided support remains at or above 80% for the full 14-day window. Validators can change their votes, making the date conditional.
The approaching activation follows a security failure that caused developers to withdraw the original version.
Researchers found a critical flaw in Batch V1.0’s signature-validation process in February. Under certain conditions, the code could stop checking signatures early and allow an attacker to include transactions from another account without its owner’s authorization.
Read More: XRP Ledger upgrade brings back features once pulled over critical bugs
“Some projects are already being built with Batch in mind, so activation would allow that work to move closer to production,” Akinyele shared. “We’ll share more on specific partners and launch timing as those plans are finalized.”
The amendment has support from 30 of the XRP Ledger’s 35 tracked validators, above the 28 votes required to enter its activation countdown.
Feature arrives after earlier flaws fixedThat countdown began Sept. 15 at 14:06:41 UTC. Batch V1.1 is projected to activate shortly after the same time on Sept. 29, provided support remains at or above 80% for the full 14-day window. Validators can change their votes, making the date conditional.
The approaching activation follows a security failure that caused developers to withdraw the original version.
Researchers found a critical flaw in Batch V1.0’s signature-validation process in February. Under certain conditions, the code could stop checking signatures early and allow an attacker to include transactions from another account without its owner’s authorization.
Read More: XRP Ledger upgrade brings back features once pulled over critical bugs