The XRP Ledger team has announced that it will reset its Testnet and Devnet networks on November 25, 2026, between 5 PM and 6 PM Pacific time. The reset will delete all existing accounts, balances, tokens, and other on-chain data on both networks. The XRPL mainnet, as well as the Xahau and Hooks testnet, will continue to operate normally.
Scope of the Reset
According to an announcement from the XRP Ledger Operations account on November 10, the reset will erase all existing on-chain state, including transactions, account settings, offers, automated market makers (AMMs), escrows, and other ledger data. The operation is limited to Testnet and Devnet.
The reset is intended to improve full history server stability. A blog post explained that Testnet’s infrastructure relied on a single full history server that crashed and could not be recovered without resetting the environment. Ripple plans to upgrade the network’s storage capacity to reduce the frequency of future resets, though some data retention limits will remain.
Impact on Developers
Developers will need to obtain new test XRP through the faucet and recreate their accounts and other on-chain setups. Those relying on particular account addresses can request funding for the same addresses again, but recreated AMMs will generally receive different account addresses.
The network’s important URLs, network IDs, and validator settings will remain unchanged. Testnet’s amendment status will also be restored to match Mainnet’s after the reset.
Developers running their own servers connected to Testnet and Devnet are advised to delete their existing database files and restart the server after the reset.
Role in XRPL’s Release Pipeline
The XRPL community uses both Testnet and Devnet to test features and integrations without risking real money. The reset comes as the network looks to expand its developer capabilities. Last month, Ayo Akinyele, Ripple’s senior director of engineering, revealed that the company has been working on a roadmap for XRPL that includes confidential transfers, transaction batching, and infrastructure for AI agents, which could introduce more complex testing requirements as developers build new applications.
Permission delegation has also undergone security revisions, and its V.1.1 implementation recently completed testing after researchers found vulnerabilities in the earlier version.
