The XRP Ledger (XRPL) has rolled out a critical software update which delivers its first major improvement. The system now operates with version 3.1.1 which replaces version 3.1.0 and disables both Batch amendment and its previous correction method fixBatchInnerSigs. The move follows a serious bug report submitted through the Bug Bounty program.
The update is narrow but firm. The system eliminates all potential dangers. The system shows that stability must come before speed.
The reference server implementation, rippled, now treats Batch as “unsupported.” The amendment needs more work. The developers decided to remove the system because they found existing problems instead of using temporary solutions.
Also Read: XRPL Revival: $1B Strategy to Turn XRP Into the World’s Financial Highway
XRP Ledger Update Prioritizes Stability
The XRP Ledger Foundation issued an announcement. The message was direct. Validators must update. But first, they must acknowledge new GPG keys.
Ripple is currently changing its GPG key which serves as the digital signature for its rippled package. This matters. If operators fail to trust the new key, automatic upgrades may fail. Systems could stall.
The foundation urged node validators to download and trust the new signing key before making the jump to version 3.1.1. The process requires two functions which combine into one essential task. In distributed systems, small oversights grow fast.
XRP Ledger Devnet Reset Scheduled
The XRPL will reset its devnet on March 3, 2026. The reset exists as a technical procedure which requires implementation. The procedure impacts developers while excluding active users from its effects.
Validators who upgrade their systems will face amendment-blocking issues because the devnet remains unchanged. A complete reset provides protection against potential problems.
The reset will erase all devnet ledger data. The system will delete all accounts, transactions, balances, offers, AMMs, and escrows. Everything goes to zero. The system resets its block number to one.
Main networks remain untouched. XRPL mainnet, XRPL Testnet, Xahau, and the Hooks testnet will operate as usual. Users can expect all services including APIs and faucets and explorers and wallet integrations to operate normally after the reset.
Developers, however, must recreate accounts. They will need fresh test XRP from the faucet. The previous balances will not be restored.
The message is clear. The xrp ledger is choosing caution over haste. The system operates to fix bugs which exist in public view. The system restarts networks when it requires operation. The blockchain system achieves resilience through incremental system updates.