Ripple will reset the XRP Ledger's Testnet and Devnet on November 25, erasing every test account, balance, order, and ledger record stored on the two developer networks. The maintenance window runs from 5 p.m. to 6 p.m. Pacific Time, as set out in a notice from XRP Ledger Operations and a reset announcement posted for ledger developers.

What the reset covers

When the reset takes effect, all data held on both environments will be permanently removed — including standing orders in test order books and complete historical ledger records. Anything not saved or migrated before the one-hour window closes cannot be recovered afterward. Because the XRP issued on these networks carries no monetary value, the deletion affects development workflows rather than real funds.

Background: XRPL's developer networks

The XRP Ledger is an open-source blockchain that went live in 2012 and is best known for low-cost payment capabilities. Alongside its live Mainnet, the project operates public Testnet and Devnet environments where developers can build applications, test integrations, and trial new features without handling real funds. The two environments are not identical in role: Testnet mirrors the Mainnet configuration for realistic integration testing, while Devnet runs the newest features, including some not yet enabled on Mainnet, giving builders an early trial ground. Test accounts on these networks are provisioned through faucet services, and the test XRP issued there carries no monetary value.

Resets of these environments are a routine part of operations, returning the networks to a clean baseline state free of accumulated test data, stale accounts, and deprecated configurations. After a reset, developers generate fresh test credentials from the faucets and redeploy any accounts or configurations they wish to continue using.

What developers should do

Developers who rely on either network should treat November 25 as a hard cutoff: export or document any settings and test data they need beforehand, and expect to recreate accounts and re-run tests on the fresh environments afterward. Teams running automated test suites against either network should plan to rebuild credentials and re-run their pipelines once the one-hour window closes.

This content was first published on COINOTAG.