One validator pushes XRPL Batch V1.1 to activation countdown threshold
XRPL’s Batch V1.1 amendment has 27 of 35 trusted validators in favor, about 77%. The network requires 80% support to start a 14-day activation countdown, so it is one validator short. The feature only activates if support remains above 80% for the entire window. Validators can change votes, which resets the countdown if support drops.
Amendments XRPSCAN
What Batch V1.1 Does
Batch V1.1 lets users bundle up to eight linked transactions into one atomic operation: either all execute or none do. Use cases include two-sided token swaps that complete simultaneously and wallet or marketplace flows that pair a customer payment with a platform fee in one submission. The feature shipped in xrpld 3.3.0 and is now up for validator vote. Activation has not occurred on Mainnet.
The Batch V1.1 amendment shipped in xrpld 3.3.0 and is now up for voting.
After the v1.0 signature bug was caught in February (pre-Mainnet, no funds at risk), we rebuilt it: root-cause fix, 4 senior reviewers, a Sherlock attackathon, and audits from Halborn and Common Prefix. We…
— Mayukha Vadari (@msvadari) September 14, 2026
Security Rewrite and Review
Batch V1.1 replaces a prior proposal that was withdrawn before Mainnet after researchers identified a flaw that could have allowed inclusion of another account’s transactions without approval under specific conditions. No funds were at risk because it did not activate. The replacement shipped in XRP Ledger 3.3.0 on August 6.
Incident Response XRPL.org
RippleX documented a follow-up security process: reviews by four senior engineers, audits by Halborn and Common Prefix, a Sherlock security contest, and automated testing. Reviewers identified 11 additional issues related to signatures, authorization checks, and server stability. Common Prefix rated one issue as critical because it could have enabled reuse of a signed permission to execute more transactions than intended.
Network and Industry Implications
If activated after a sustained 80% majority for 14 days, Batch V1.1 would provide a native mechanism for multi-step payment coordination without smart contracts. This affects settlement flows like agentic transaction rails and stablecoin operations linked to RLUSD settlement volume. RippleX stated that commercial projects using Batch are under contract or development, but it has not disclosed counterparties. The current state: 27 approvals, one vote short of the threshold, and the countdown has not started.
Key activation mechanics: 28 validator votes out of 35 initiate the 14-day majority period. Support must remain above 80% for the feature to go live. Any drop below the threshold resets the countdown.









