The XRP Ledger amendment called BatchV1_1 has entered its activation countdown. On-chain amendment status data says the proposal won majority validator backing starting Sept. 15, and if that support stays above the required line, it could switch on as soon as Sept. 29.
Up to eight transactions in one operation
BatchV1_1 is built to bundle up to eight XRP Ledger transactions into one operation. Simple rule: either all of them go through, or none of them do.
RippleX engineering lead Ayo Akinyele said the batch feature links several transactions together so that "either they all execute, or not a single one executes." The setup is intended to keep linked transactions consistent.
Ripple pointed to use cases such as delivery-versus-payment settlement, charging service fees at the exact time a customer payment happens, and moving assets and funds in sync. In every one of those situations, a breakdown halfway through can leave things only partly finished, and that can be messy to reverse.
Threshold is 28 of 35 validators for 14 consecutive days
For an XRPL amendment to go live, it needs at least 80% validator support and has to hold that mark for 14 straight days. With 35 tracked validators, that works out to 28 seats.
On-chain data shows majority support for BatchV1_1 started at 14:06 UTC on Sept. 15. Right now, 30 of the 35 tracked validators back the amendment, which is above the 28-seat threshold.
If support stays at or above that level for the entire period, the earliest activation time is Sept. 29 at 14:06 UTC, or 10:06 p.m. Taipei time on Sept. 29. For now, though, the amendment is still inactive.
Earlier version was withdrawn before launch
This is not the first batch feature to make it through the amendment process. The first Batch proposal was pulled before activation after a major flaw in signature verification was discovered in February 2026.
On-chain records still list the original Batch proposal at 12 of 35 seats. A separate fix, called fixBatchInnerSigs, is at 10 seats. Neither one passed.
Ripple said the rebuilt V1.1 version went through several rounds of review: internal testing, AI-assisted analysis, Sherlock’s security competition, and reviews by security firms Halborn and Common Prefix.
Ripple mentioned asset managers but named none
Akinyele also said more information would be shared after the feature goes live, "including partnerships with major asset management institutions." That is all the public claim says right now about institutional demand.
No asset manager was named, and no scale or timeline was given. So the only things that can be independently checked right now are the technical and governance details on-chain: the amendment ID, validator vote count, when the countdown began, and the earliest possible activation time.
As for which asset management firms might be getting ready to use the feature, that still rests only on Ripple’s own statement.