Skip to content
EnabledTier AUsability

DeletableAccounts XLS-7

Accounts can be deleted along with certain ledger objects they own. DeletableAccounts is enabled on the XRP Ledger. xrpscan reports May 8, 2020 (UTC) as its activation date and rippled 1.4.0 as its first version.

Sources reviewed Oct 5, 2026 · English page updated Oct 5, 2026 · Phil · CryptoTuts founder

Status
Enabled
XLS
XLS-7
Enabled
May 8, 2020 (UTC)

What does this amendment change?

Why does this amendment exist?

Unused AccountRoot objects permanently occupied ledger storage and tied up remaining balances. Recreating the same address later also needed to reliably reject old signed transactions.

How does the mechanism work?

AccountDelete transfers the remaining XRP balance to an existing destination and then removes the AccountRoot. Deletable owned objects such as offers, tickets, DepositPreauth, and SignerList are removed too. Newly created accounts start with the current LedgerSequence so old signed transactions do not become valid again after later recreation.

What changes compared with the predecessor?

BeforeAfter
Once created, an AccountRoot remained permanently in the ledger, and new accounts began with Sequence 1.An account meeting the sequence-age condition and cleared of blocking objects can be closed. Its remaining XRP goes to another existing account after the increased fee is deducted.

Who is this change relevant to?

XRP holders and users

A user can close an unused account and transfer its remaining XRP. Blocking obligations must be removed first.

Wallets and app developers

Apps must show all deletion blockers, check the existing destination account, and use ledger-based Sequence values after account recreation.

Exchanges and issuers

Exchanges can retire accounts in an orderly way but must retain required destination tags. Trust lines, checks, escrows, and payment channels prevent deletion.

Node operators

Nodes remove permitted directory entries within limits, check replay protection, and treat AccountDelete as a transaction-queue blocker.

What limitations and risks remain?

  • With current rules, the account's Sequence plus 255 must be no greater than the current ledger index. This checks Sequence, not simply the account's creation age.
  • The destination must already exist, differ from the source, and provide any required deposit authorization.
  • Checks, escrows, payment channels, and RippleState trust lines block deletion.
  • More than 1,000 directory entries cause rejection, protecting the ledger against oversized deletion operations.
  • A later payment can recreate a deleted identity. The new Sequence prevents replay of old transactions but does not prevent address reuse.

What fee and performance figures does the specification provide?

  • AccountDelete's minimum fee equals one owner reserve and also applies to multisigning.
  • At most 1,000 directory entries are processed per deletion.
Technical details: transactions, fields, codes and invariants

Transactions

  • AccountDelete
  • EscrowFinish
  • PaymentChannelClaim
  • PaymentChannelFund

Ledger objects

  • AccountRoot
  • DepositPreauth
  • DirectoryNode
  • Offer
  • SignerList
  • Ticket

Fields and flags

  • Account
  • Destination
  • DestinationTag
  • Sequence

API methods

  • account_objects: type blocks_deletion

Result codes

  • tefPAST_SEQ
  • tefTOO_BIG

Invariants

  • For ordinary user accounts, a successful AccountDelete removes exactly one AccountRoot. Later protocol features define separate lifecycle rules for their pseudo-accounts.
  • The amendment's original account-creation invariant allowed at most one new AccountRoot through Payment. Later features such as AMMs extend creation rules for protocol pseudo-accounts; this historical rule should not be treated as the complete current invariant.

How does this amendment relate to others?

Every direct relationship has a type, an explanation and a primary source.

What happens next for this amendment?

DeletableAccounts is enabled on the XRP Ledger. xrpscan reports May 8, 2020 (UTC) as its activation date and rippled 1.4.0 as its first version.

These rules are already part of Mainnet. Server operators need a compatible xrpld (formerly rippled) version; ordinary wallet users do not need to enable anything manually.

Where does it sit within its amendment family?

AMM and Clawback: protocol progression

  1. DeletableAccountsEnabled · from rippled 1.4.0
  2. TicketBatchEnabled · from rippled 1.7.0
  3. DisallowIncomingEnabled · from rippled 1.10.0
  4. AMMEnabled · from rippled 1.12.0
  5. ClawbackEnabled · from rippled 1.12.0
  6. fixDisallowIncomingV1Enabled · from rippled 2.0.0
  7. fixInnerObjTemplateEnabled · from rippled 2.1.0
  8. fixAMMOverflowOfferEnabled · from rippled 2.1.1
  9. fixAMMv1_1Enabled · from rippled 2.2.0
  10. fixPreviousTxnIDEnabled · from rippled 2.2.0
  11. AMMClawbackEnabled · from rippled 2.3.0
  12. fixAMMv1_2Enabled · from rippled 2.3.0
  13. fixInnerObjTemplate2Enabled · from rippled 2.3.0
  14. fixFrozenLPTokenTransferEnabled · from rippled 2.4.0
  15. DeepFreezeEnabled · from rippled 2.4.0
  16. PermissionedDEXEnabled · from rippled 2.5.0
  17. fixAMMv1_3Enabled · from rippled 2.5.0
  18. PermissionDelegationDeprecated · from rippled 2.5.0
  19. fixAMMClawbackRoundingEnabled · from rippled 3.0.0
  20. SponsorOpen for voting · from xrpld 3.3.0
  21. PermissionDelegationV1_1Enabled · from xrpld 3.3.0
  22. fixCleanup3_3_0Enabled · from xrpld 3.3.0
  23. fixCleanup3_4_0Enabled · from xrpld 3.4.0
  24. MPTokensV2In development

Which primary sources support this information?

← All XRPL amendments and XLS specifications