crypto.news and Coin Edition report different validator vote totals for the same day, a discrepancy that determines whether Batch V1.1 crossed the 80% activation threshold.
crypto.news and Coin Edition report different validator vote totals for the same day, a discrepancy that determines whether Batch V1.1 crossed the 80% activation threshold.
What all sources agree on
- Batch V1.1 is a corrected replacement for an earlier Batch amendment that had a security flaw.
- The original flaw was found before mainnet activation, so no user funds were at risk.
- Batch V1.1 ships in xrpld 3.3.0.
- The amendment must maintain at least 80% validator support for 14 consecutive days before it can activate.
- Batch would allow multiple transactions to be grouped and executed together, succeeding or failing as a unit.
- Developers/RippleX conducted additional security reviews including audits from Halborn and Common Prefix and a Sherlock contest.
Where the reports disagree
1Number of validator votes in favor on Tuesday
Support stood at 27 of the 35 trusted validators on Tuesday, equal to roughly 77%, leaving the proposal just below the 80% level required to enter the network's activation period.
crypto.news2026-09-15 06:21
The XRP Ledger's Batch V1.1 upgrade reached 29 validator votes in favor Tuesday, moving closer to its planned Sept. 29 activation.
Coin Edition2026-09-15 20:19
What would settle it: The XRP Ledger's public amendment voting tracker (validator UNL vote data) for the relevant date.
What to make of it
Treat the broader narrative—that Batch V1.1 fixes prior security issues and is nearing the 80% activation threshold—as established, but do not rely on either specific vote count (27 vs 29) until checked against the XRP Ledger's own amendment voting tracker.
Treat the broader narrative—that Batch V1.1 fixes prior security issues and is nearing the 80% activation threshold—as established, but do not rely on either specific vote count (27 vs 29) until checked against the XRP Ledger's own amendment voting tracker.