The XRP Ledger development community has taken swift action to address a critical bug discovered in the proposed batch transaction amendment just before its activation. According to a tweet from XRP Ledger validator Vet, the bug was caught through the XRP Ledger Foundation's Bug Bounty program on February 20, 2026, preventing a potentially flawed feature from going live.
The batch amendment was only one validator vote away from reaching the majority required for activation when the bug was detected. In response, the XRP Ledger Foundation immediately urged all network validators to veto the amendment while engineers conducted a review. The Foundation confirmed that the core XRP Ledger network remains unaffected and safe, emphasizing that the issue was isolated to the proposed amendment itself.
A fix for the bug is already underway and is undergoing additional validation. The Foundation is preparing a new software release, expected next week, which will formally deprecate the current, bug-ridden batch amendment. Vet outlined the logical next steps: a detailed bug report blog post will be published, followed by another XRP software update containing a corrected and fixed batch amendment. No specific timeline for the corrected amendment's release has been provided.
The batch transaction feature is a highly anticipated upgrade for the XRP Ledger. It would enable the atomic execution of multiple transactions, a capability that developers believe will make it significantly easier to build applications that can generate revenue directly on-chain, automate complex transaction flows, and offer paid features within apps.
In a related development, a separate bug was also identified in the 'fixbatchinnersigs' amendment, which is designed to correct an issue with how signatures are validated for inner transactions within a batch. Both amendments are now under review.
Separately, Ripple has rotated the GPG (GNU Privacy Guard) key used to sign rippled software packages. A notice on the XRPL blog advises users to download and trust the new key to prevent issues with future upgrades, as automatic updates may fail until the new key is verified.
