XRP Ledger made accounts deletable for the first time

The XRP Ledger activated its DeletableAccounts amendment on May 8, 2020, allowing qualifying accounts to be removed from the ledger’s current state for the first time.

The protocol change introduced an `AccountDelete` transaction and ended the assumption that every funded XRP Ledger account would remain permanently present. It also let an account owner recover most XRP held to satisfy the network’s account reserve, subject to a substantial deletion cost and restrictions intended to protect other users and discourage abuse.

This was not merely a new wallet-interface feature. It altered transaction processing, account lifecycle assumptions and the behavior software needed when looking up or sending funds to an address.

What changed on May 8

The XRP Ledger’s contemporaneous announcement recorded that DeletableAccounts became enabled on May 8. A contemporaneous report, citing former XRP Center manager Arturo Portilla, placed activation at 04:29:30 UTC in ledger 55,313,921 after the amendment maintained the required validator support.

Before activation, an account remained part of the ledger’s current state after it had been funded. The network then required a base reserve of 20 XRP for an account, partly because each account occupied shared ledger space.

Under the new rules, the owner of an eligible account could submit an `AccountDelete` transaction naming a destination. The destination received the account’s remaining XRP after a minimum deletion cost of 5 XRP was destroyed. For a simple account holding the 20-XRP reserve, that meant as much as 15 XRP could be recovered.

Those figures describe the protocol parameters in force on May 8, not permanent XRP Ledger settings. Reserve requirements and fees could be changed through later governance and protocol processes.

Deletion came with safeguards

An account could not simply disappear while leaving unresolved obligations. The amendment specification prevented deletion when the account retained certain ledger objects, including trust lines, checks, escrows or payment channels. It also limited deletion when an account had more than 1,000 directory entries.

The specification required an account’s sequence number to be at least 256 below the current ledger index before deletion. That delay raised the cost and complexity of repeatedly creating and deleting accounts.

DeletableAccounts also changed the initial sequence number assigned to newly funded accounts. Instead of starting at one, a new account began with a sequence number matching the ledger index at creation. This protected a deleted and subsequently re-created account from accepting an old signed transaction whose sequence number might otherwise become valid again.

Deletion did not erase history. Full-history servers could still retain the account’s earlier transactions even though the account no longer existed in the current ledger state. An address could also be re-created by funding it with the required reserve, but its former settings and ledger objects would not return. Control still depended on possession of the corresponding cryptographic keys.

Why integrations had to adapt

The amendment changed assumptions embedded in exchanges, wallets, custody systems and payment software. An application could no longer treat a successful past account lookup as proof that the account would still exist when a later payment was submitted.

Software that assumed every new account started with sequence number one also needed adjustment. The event-day implementation guidance recommended querying the account’s actual sequence number or allowing signing software to populate it automatically.

The institutional significance was therefore operational rather than market-based. DeletableAccounts offered users a way to consolidate unused accounts and reduced permanent ledger state, but it also created new failure cases for payment and account-management systems.

No defensible same-day XRP price effect is asserted. Cryptocurrency prices varied continuously across venues, and the available protocol records do not establish that activation caused any particular market move. The verified May 8 development was narrower: a validator-approved amendment changed what an XRP Ledger account could be and required connected software to recognize that account existence was no longer permanent.