Overview
- Developers pulled the original Batch V1.0 after researchers found a critical signature‑validation bug in February that could have let unauthorized transactions bypass checks, and the flawed code never activated on the live ledger.
- RippleX rebuilt Batch as V1.1 and shipped the replacement in xrpld version 3.3.0 on August 6, then ran expanded security reviews including internal adversarial tests, AI analysis, a Sherlock contest, and audits by Halborn and Common Prefix.
- Validators reached the threshold to start the amendment’s 14‑day activation countdown on Sept. 15, and the amendment now shows 30 of 35 tracked validator votes; it will only activate shortly after Sept. 29 if at least 80% support holds for the full window.
- Votes can change during the countdown, and if support falls below 80% the clock pauses and a new 14‑day window must run after the amendment regains the required majority.
- RippleX says asset managers and commercial projects are preparing to build for Batch, but real‑world use still depends on activation plus wallets, exchanges and marketplaces completing integration, testing and compliance work.