XRPL to Reset Testnet and Devnet on November 25: All Data Will Be Deleted

The XRP Ledger (XRPL) team announced a planned reset of the Testnet and Devnet test networks on November 25, 2026. The operation is scheduled to take place from 5:00 PM to 6:00 PM Pacific Time, which corresponds to 1:00–2:00 AM UTC on November 26. During the operation, all ledger data from both networks, including accounts, balances, transaction history, and user-created objects, will be deleted.

The changes will affect only the test infrastructure used by developers to test applications and new XRPL features. The main XRP Ledger (Mainnet), as well as Xahau and Hooks Testnet, will continue to operate normally. Real XRP in the main network will not be affected.

Why XRPL is Resetting Test Networks

According to the official notification, the reason for the operation is infrastructure issues with the Testnet. The network relied on a single server that stored the complete ledger history. After the equipment failure, it was not possible to restore the server without resetting the test environment.

Ripple plans to increase storage capacity to enhance infrastructure resilience and reduce the need for such operations. However, limitations on historical data storage will remain, so developers do not rule out future resets.

Testnet is designed for testing applications in conditions close to the main XRPL network. Devnet is used for testing new features and protocol changes before their potential implementation. Both environments allow developers to experiment with test XRP without risking real funds.

What Data Will Be Deleted

After the reset, existing accounts, balances, transaction history, and account settings in Testnet and Devnet will disappear. The deletion will also affect issued tokens, decentralized exchange orders, automated market makers (AMM), and escrow operations.

Developers will need to recreate necessary objects and obtain test XRP through a special token distribution service (faucet). If an application depends on a specific address, it can be replenished again through this service. However, the addresses of restored AMM pools will generally differ from the previous ones, so related integrations will need to be updated.

Meanwhile, the main connection URLs, network identifiers (Network ID) and validator settings will remain unchanged. After the restart, the status of protocol amendments in Testnet will also be aligned with the main XRPL network.

What Developers Need to Do

The XRPL team recommends that developers anticipate the upcoming loss of test data. Applications using existing accounts, tokens, trade orders, or liquidity pools may require reconfiguration after the operation is completed. This is especially true for projects dependent on specific addresses or transaction history.

Operators of their own xrpld servers connected to Testnet or Devnet need to delete old local database files and restart the server after the reset. The relevant directories are determined by the database_path and node_db parameters in the configuration. Developers have published sample commands for servers with standard settings.

The reset is aimed at restoring the functionality of the test infrastructure and improving the stability of ledger history storage. It is not related to the removal of assets from the main XRP Ledger network and does not require action from regular XRP holders.