The XRP Ledger (XRPL) has released a critical software update, version 3.1.1, which disables the Batch amendment due to a serious defect discovered through its Bug Bounty program. The update marks a significant step for network stability, requiring validators to acknowledge new security keys before upgrading. Separately, a full reset of the XRPL development network is scheduled for March 3, 2026, which will erase all test data while leaving mainnet operations unaffected.
The XRP Ledger (XRPL) has deployed a critical software update to version 3.1.1. This release disables the Batch amendment and its previous correction method, fixBatchInnerSigs, following the discovery of a serious bug reported through the platform’s Bug Bounty program.
The update treats Batch as “unsupported,” prioritizing stability over speed. Developers chose to remove the feature entirely rather than apply a temporary fix for the existing problems.
The XRP Ledger Foundation issued a direct announcement urging validators to update. The message stated that validators must first acknowledge new GPG keys before proceeding, as Ripple is currently changing its digital signature key for its rippled package.
The foundation warned that automatic upgrades could fail if operators do not trust the new key. This two-step process is essential to prevent systems from stalling in the distributed network.
A complete reset of the XRPL development network is scheduled for March 3, 2026. The procedure will erase all devnet ledger data, including accounts, transactions, balances, and other test information.
Main networks, including the XRPL mainnet, XRPL Testnet, Xahau, and the Hooks testnet, will operate normally. Developers, however, must recreate their test accounts and obtain fresh test XRP after the reset.
The ledger’s approach demonstrates a focus on caution and resilience. The system is addressing publicly known bugs and restarting test networks through deliberate, incremental updates.
