Skip to content
Independent XRP reference
Our standards
← All XRP news

XRP Ledger

How the November 25 XRPL Testnet and Devnet Reset Affects Wallet and Pool Addresses

XRPL will reset Testnet and Devnet on Nov. 25. A team can fund its old test address again, but a pool it builds for the same pair will usually get a new address. The reset has no effect on XRP held on Mainnet.

By
A brass hand-cranked shaver holds a cobalt wax cylinder, grooved on the left and smooth on the right, with a curl of wax beside the cutter.

Which XRP Ledger networks will reset on November 25?

Ripple plans to clear the XRP Ledger’s Testnet and Devnet on November 25, 2026. Mainnet balances are outside the reset. Developers can fund a familiar test wallet address again, but a liquidity pool rebuilt for the same assets will generally have a different address. Applications that saved the old pool address will need to check it.

XRPL Operations put the work between 5 and 6 p.m. Pacific on Wednesday, November 25. For teams working in UTC, that is 01:00 to 02:00 on Thursday, November 26. Those are the scheduled hours. A team with a test run queued for 02:00 UTC should look for confirmation that its network is back before treating a failed run as a defect in its application.

The scope matters to anyone who sees a wallet balance disappear. A developer using test XRP from a faucet should expect to rebuild the test account. Someone holding XRP on Mainnet has no account recovery step to perform for this event. Xahau and the Hooks Testnet are also outside the maintenance notice. A wallet’s selected network is the first thing to check when deciding which instructions apply.

Section sources[1][2][3][4]

Why Testnet’s history server prompted a reset

XRPL’s November 9 engineering notice traces the problem to the one server that kept Testnet’s full history. It crashed, and the team says recovering it requires a reset. The announced remedy includes more storage. The team still expects limits on how much history it can retain. It gives no retention period on which an application developer could base a promise to customers.

Testnet and Devnet serve different purposes. Testnet gives an integration team somewhere to try software against rules close to the ones on Mainnet. After the reset, its amendment settings are due to match Mainnet’s. Devnet lets a developer try features from the development branch. The diagnosis in the notice identifies Testnet’s history server specifically. Including Devnet in the work does not establish that a second history server crashed there.

Consider a wallet team investigating a bug that shows up only under a proposed transaction rule. A successful Devnet run can be useful evidence for that bug. Repeating it on a freshly reset Testnet asks a different question if the rule has yet to reach Mainnet. Record which network and feature the test depends on before the maintenance window. Otherwise a change in the test conditions can look like a regression in the wallet.

Section sources[2][3][4]

What an XRP faucet can restore at an old address

The XRPL faucet lets a developer select a test network and request funds for an existing test address. That option is useful if a sample app has the address in its configuration or a tutorial asks readers to send a payment to it. Once funded again, the address can receive a new test payment. Looking up an old payment at that address is a different operation. The reset clears the network’s transaction history.

Take a payment demo in which a merchant accepts an issued token and a customer pays an invoice. The developer can keep the two public test addresses in the demo. A refill supplies test XRP. The setup still needs to establish the token relationship and give the customer the test tokens the payment requires. The old invoice payment cannot serve as the receipt for the rebuilt demo. Run a new payment and save its resulting transaction reference alongside the new test run.

A useful inventory has two columns. Put inputs the team controls in the first, such as the test network, public addresses and intended account settings. Put results the old ledger supplied in the second, such as a transaction identifier or a balance after payment. Feed the first column into the setup procedure. Replace the second with observations from the new run. Keep signing secrets out of that inventory and use separate credentials for Mainnet, as the XRPL faucet documentation advises.

For a bug report that already points to a test transaction, save the response and the steps that produced it before the reset. A saved response lets someone inspect what the application saw at the time. A short set of reproduction steps gives a maintainer a way to exercise the same behavior against the new ledger, even when the old transaction lookup is gone.

Section sources[2][3][4][5]

How to find a rebuilt XRPL liquidity pool

An automated market maker (AMM) holds two assets that users can trade against the pool. A wallet application might display the pool by the names of its assets while its backend fetches details using a saved pool account address. XRPL’s notice says that recreating an AMM will generally give it a different account address. A person looking at the same asset names could reasonably think the application is showing the same pool.

The XRPL API offers a way to check. Its amm_info method accepts either the AMM account address or the two asset definitions. For a test pool holding XRP and an issued token, specify XRP on one side and the test token’s currency and issuer on the other. After the pool has been recreated, query by that pair against a validated ledger on the intended network. Read the pool address from result.amm.account and compare it with the one the application has saved.

This gives a developer a way to narrow down a blank pool screen. If the rebuilt pair resolves and the application is still querying an older address, correct the saved reference and run the lookup again. If the pair lookup finds no pool, first verify the issuer and whether anyone actually recreated the pool. Refilling the wallet used to create it and establishing the new pool are separate steps. Testing those steps individually helps locate the failure without changing the trading code.

Section sources[2][3][4][6][7]

What to check before declaring a test integration recovered

XRPL says important network URLs, network IDs and validator settings will carry over. A connection check can therefore succeed at the same endpoint even though the escrow, order or pool that the next test expects has disappeared. For an escrow integration, a useful recovery test is to create a fresh test escrow, record its reference and exercise the operation the application was built to perform. Checking only that the endpoint answers would miss a failure in that sequence.

Teams that operate their own xrpld servers on either affected network have an additional job. XRPL advises clearing the affected node’s database data after the reset and restarting the server. Its instructions identify the database locations through the node configuration. On a machine that also serves another environment, verify which service and data directories belong to the test network before following the operator procedure. A team using a hosted endpoint can ask the provider about readiness and proceed with rebuilding its own test data.

Uncertainty remains about the first usable moment for any particular integration. The published window cannot tell a wallet team when its provider will have a working endpoint, its issuer will have issued the test tokens or its pool will be available to query. For a scheduled demo, use one representative transaction as the acceptance test. Keep its network, new transaction reference and expected result together so the next person can reproduce what actually worked.

Section sources[2][3][4]

What to watch next

  • • Ahead of November 25, check XRPL Operations for changes to the announced Pacific maintenance window.
  • • After operations resume, verify Testnet’s amendment settings for the particular feature your test exercises.
  • • Refill a test address, recreate one required ledger object and confirm that the app can read the new result.
  • • For a rebuilt liquidity pool, compare the account returned for the asset pair with the address saved by your integration.

Sources and verification

We prioritize primary records and label supporting coverage. Dates reflect each source’s publication record.

  1. [1]XRPL Operations · November 25 maintenance windowprimary
  2. [2]XRP Ledger · Upcoming Testnet and Devnet Resetsprimary
  3. [3]CryptoPotato · Wayne Jones on the XRPL test network resetsupporting
  4. [4]U.Today · XRP Ledger Testnet and Devnet Face Major November Resetsupporting
  5. [5]XRP Ledger · Test XRP faucet and wallet refillprimaryUndated reference
  6. [6]XRP Ledger · amm_info request and response fieldsprimaryUndated reference
  7. [7]Nodit · Node provider reference for the XRPL amm_info methodsupporting