Can You Delete an XRP Account? XRPL AccountDelete Fees, Reserve Recovery, and Risks (2026)

By XORA · Published 2026-09-07

Yes, an eligible XRP Ledger account can be deleted, but deletion is neither free nor private. A successful AccountDelete removes the account's current ledger entry and sends its remaining XRP to an existing destination. At the Mainnet settings verified on 7 September 2026, the minimum deletion fee is 0.2 XRP. A clean account holding only the 1 XRP base reserve can therefore recover 0.8 XRP under minimum-load assumptions. Its validated transaction history is not erased, and the address can later be funded into existence again.

The simplest reserve-recovery example

Start with an account that has exactly 1 XRP, owns no ledger objects, has no obligations, and meets the sequence-age rule. It submits AccountDelete with a Fee of 200,000 drops, equal to 0.2 XRP, and names an already funded account as Destination. When the transaction succeeds, the fee is destroyed, the other 0.8 XRP moves to the destination, and the source AccountRoot disappears from the current ledger state.

This is not a refund transaction with a special “reserve” output. Reserve is a balance requirement, not a separate locked coin. The implementation first charges the signed transaction fee, then transfers the source account's entire remaining XRP balance. If the account held 4 XRP instead, the same minimum-fee example would deliver 3.8 XRP. If the signer specified a fee above the required amount, the ledger would destroy the exact higher amount that was signed.

Why AccountDelete costs 0.2 XRP, not 10 drops

The official transaction-cost documentation lists 10 drops, or 0.00001 XRP, as the minimum for an ordinary reference transaction. AccountDelete is deliberately different. Its pre-load-scaling base fee equals one incremental owner reserve. The rippled implementation calculates that special base fee from the live owner-reserve setting.

On 7 September 2026, an official Mainnet server_info response at validated ledger 106,820,692 reported a 1 XRP base reserve, 0.2 XRP owner reserve, and 0.00001 XRP base fee. The minimum deletion fee was therefore 200,000 drops, 20,000 times the ordinary 10-drop reference fee. These settings can change through validator fee voting, so wallet software should query them immediately before building a transaction.

The sequence rule creates a cooling-off window

An account is too recent or too transactionally active to delete when its current Sequence is too close to the ledger index. The current rule is account Sequence + 255 ≤ current validated ledger index. Put differently, the ledger must have advanced far enough beyond the account's sequence to create a 256-ledger safety margin. On Mainnet, 256 ledgers are typically about 15 minutes, but a frequently used account may need to stop transacting and wait.

This rule prevents an old signed transaction from being replayed if the same address is funded and recreated later. Accounts that issued NFTs have an additional age test based on FirstNFTSequence + MintedNFTokens + 255, and all NFTs issued by that account must have been burned. The safe test uses the latest validated ledger and the current AccountRoot, not the age of a wallet app installation.

Deletion blockers versus objects removed automatically

The headline “delete an account and its objects” needs qualification. Objects that represent assets, obligations, or an unfinished movement of funds generally block deletion. The current XRPL deletion-blocker table includes Checks, escrows, payment channels, trust lines, NFT pages, permissioned domains, bridges, MPT holdings or issuances, vaults, sponsorships, and two cross-chain claim object types. Enabled amendments determine which newer types exist on a given network.

Other owned state can be cleaned up as part of successful deletion. As of the source reviewed for this article, rippled has deletion handlers for offers, signer lists, tickets, deposit preauthorizations, NFT offers, DIDs, oracles, credentials, and delegate entries. That automatic cleanup does not mean every relationship is safe to ignore. An account with more than 1,000 linked owner-directory objects is rejected even if all those objects would otherwise be deletable.

Sponsored accounts add further constraints where the Sponsor amendment applies. A sponsored account must send its remainder to its sponsor. Accounts sponsoring other accounts or objects must first transfer or dissolve those commitments. The broad operational rule is simple: query and paginate the account's objects, inspect its AccountRoot, and resolve every blocker before exposing a 0.2 XRP minimum fee to a possible validated failure.

What deletion does not delete

AccountDelete removes live state; it does not rewrite blockchain history. Full-history servers can retain the account's earlier transactions and the deletion transaction itself. Account deletion is therefore not a privacy tool, a right-to-erasure mechanism, or a way to make transfers untraceable. It also does not close an exchange or custodial customer profile. A hosted service controls its own database, terms, withdrawal process, and account closure separately from the XRPL address it uses.

The address can be recreated by sending it enough XRP to meet the then-current base reserve. Whoever funds it does not gain control: control still follows the cryptographic keys for that address. The recreated account starts as a new ledger account, so earlier flags, regular-key settings, signer lists, sequence state, and other deleted settings do not return. Keeping an old secret after deletion can therefore matter if anyone later reactivates the address.

A safer AccountDelete workflow

1. Confirm custody. Make sure you control a signing key authorized for the source account and a separate, already funded destination. For an exchange destination, verify the destination tag through the exchange itself.
2. Read validated state. Use account_info for Sequence, OwnerCount, NFT counters, flags, and sponsorship fields. Use paginated account_objects results to inventory every linked entry.
3. Remove blockers deliberately. Zero and default trust lines, cancel Checks and offers, finish or cancel escrows, close payment channels, transfer or burn NFTs, and resolve amendment-specific obligations. Re-query after each cleanup transaction validates.
4. Refresh economics. Query a validated server for current base reserve, owner reserve, ledger index, and load. Calculate the expected delivered amount as source balance minus the exact signed Fee.
5. Bound and verify submission. Use a reasonable LastLedgerSequence, submit with fail_hard, and treat only validated tesSUCCESS as deletion. Verify metadata, delivered amount, destination balance, and absence of the source AccountRoot.

Never infer success from a preliminary engine response or a wallet notification. The destination may require a tag or deposit authorization, network state can change between inspection and application, and a validated tec can claim the fee. If the remaining balance is small, the 0.2 XRP minimum cost may make deletion economically pointless even when it is technically possible.

Recovering reserve is not the same as making XRP productive

Account deletion can recover most of a clean account's base reserve, but it ends the account instead of earning a return. XORA's separate proposition is up to 22% APY value (15% native subsidised + XORA reward value). That value is variable, is not guaranteed, and carries custody, liquidity, operational, counterparty, market, and reward-value risks. Review the security model and use an amount appropriate for your risk tolerance.

xora.finance is where to put your XRP to work and earn up to 22% instead of leaving it idle on an exchange.