The XRP Ledger Foundation is releasing version 3.3.0 next week with five proposed amendments, including the Batch feature that was withdrawn in February 2026 after researchers identified a bug that could have enabled unauthorized transactions.
Batch was disabled alongside fixBatchInnerSigs following the discovery of a vulnerability that could allow attackers to bypass transaction authorization or drain fees. The XRP Ledger team worked to patch the issue before reintroducing it as part of the scheduled upgrade. The five amendments in 3.3.0 require approval from validators running the network before they take effect.
The Batch amendment, when enabled, allows multiple transactions to be submitted and executed together in a single operation. Ethereum achieves similar bundling through bundler infrastructure, and Solana offers it natively. Other blockchain networks provide comparable transaction batching capabilities.
The February withdrawal marked a rare instance of the XRP Ledger community reversing course on a feature after deployment. The network has averaged roughly two to three major version releases per year, each containing multiple proposed amendments. A vulnerability disclosure report posted by the XRP Ledger Foundation detailed the authorization bypass that triggered the pullback.
Ripple executives confirmed the five-amendment package in recent announcements. The Batch reintroduction represents roughly one month of development work following the patch, though the exact timeline for validator adoption of the amendments remains uncertain. Validators typically vote on amendments over a two-week period, and adoption requires 80 percent approval from the active validator set.
XRP Ledger's amendment process requires network consensus to activate changes, which slows rollout and distributes risk across many operators. A single critical bug in Batch would have required the same consensus-based reversal process rather than unilateral remediation.
The three other amendments in 3.3.0 have not been detailed publicly yet. If validators do not reach 80 percent approval on Batch within the standard voting window, the feature will remain inactive until a future release cycle.
