XRP Ledger Schedules Testnet and Devnet Reset for November 25; Mainnet Unaffected

BTCLiveETHLiveSOLLiveXRPLiveBNBLiveDOGELiveADALiveAVAXLive
CHARTING PARTNERTradingViewAdvanced charts, indicators and market tools.OPEN CHARTS →
Start with today’s trader mapBefore you leave: see the cross-asset levels, confirmations, invalidations and catalysts NetNapz is tracking for the next session.DAILY TRADER BRIEF →STRATEGY DESK →

XRP LEDGER · DEVELOPER INFRASTRUCTURE

XRP Ledger Schedules Testnet and Devnet Reset for November 25; Mainnet Unaffected

Published 14 November 2026 · Scheduled reset: 25 November 2026 · NetNapz Currency Desk

Black XRP symbol identifying the XRP Ledger developer-network advisory
XRP symbol by Benwhale1 via Wikimedia Commons, CC BY-SA 4.0. Wikimedia PNG rendition; no design changes. Trademark rights retained; no endorsement. Editorial identification, not an image of the reset.

The XRP Ledger’s Testnet and Devnet are scheduled to reset on Wednesday, 25 November 2026. An official XRP Ledger developer advisory published on 9 November says both development networks will lose their existing ledger data, while Mainnet and other networks will continue operating normally.

The distinction matters: this is a planned developer-infrastructure event, not a Mainnet outage, XRP balance deletion or protocol-wide rollback. Test XRP has no monetary value, and the advisory does not tell Mainnet users to move funds.

What the reset deletes

The advisory says the reset will remove all Testnet and Devnet ledger data, including accounts, transactions, balances, settings, offers, automated market makers and escrows. Developers relying on existing test objects will need to recreate them and obtain new test XRP from the faucet.

The published network URLs, network IDs and validator settings are expected to stay the same. XRP Ledger also says Testnet amendment statuses will be restored to match Mainnet after the reset. Those continuity points reduce configuration changes, but they do not preserve the old test ledger history.

Why XRP Ledger says the reset is necessary

According to the project, Testnet depended on one full-history server that crashed and could not be recovered without a reset. Ripple plans to increase storage capacity, although the advisory says retention limits will still apply. The stated goal is to improve full-history stability and reduce how often resets are required.

Devnet serves a different purpose from Testnet: it previews proposed and upcoming functionality from the development branch, while Testnet is intended to more closely mirror Mainnet’s amendment status. Resetting both environments gives builders a clean state, but it also means test fixtures and historical assumptions must be rebuilt.

Actions for developers and node operators

Teams should inventory any tests that depend on fixed accounts, transaction histories, AMMs, escrows or offers before 25 November. The advisory says the faucet can fund the same address again when code depends on a particular address, but recreated AMMs will generally receive different account addresses.

Operators of xrpld servers connected to Testnet or Devnet are instructed to stop the service, remove the relevant local database data and restart after the reset. Because database locations depend on configuration, operators should use the paths documented for their own deployment and follow the official advisory rather than copying an unverified deletion command.

The project also repeats a security practice with wider relevance: developers should not reuse Mainnet addresses or key pairs on test networks. A test environment is not an appropriate place for production secrets.

NetNapz assessment

The reset is operationally significant for developers because it invalidates stored test state and can break automated tests that assume persistent ledger objects. It does not establish a defect in Mainnet consensus, change XRP ownership rights or imply that production balances are at risk.

The strongest post-reset evidence will be successful Testnet and Devnet restarts, restored amendment status, functioning faucets and stable full-history service. Until those checks are observable, the 25 November outcome remains scheduled rather than completed.

Verification scope

NetNapz checked the XRP Ledger advisory and its 9 November publication date on 14 November 2026 at 00:38 GMT. The article’s attachment 3982, source URL, PNG media type, dimensions, alt text and CC BY-SA 4.0 attribution were verified before publication. NetNapz did not operate an xrpld server, preserve test data, execute database commands or independently test the developer networks.

Primary source

XRP Ledger: “Upcoming Testnet and Devnet Resets,” published 9 November 2026. Reset scope, affected data, continuity details and operator guidance are attributed to this advisory.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top