Skip to content
Not a network amendmentTier BUpcoming standardsSpec: Draft

PseudoAccount XLS-64

A shared security and reserve standard for protocol-controlled AccountRoot objects without usable signing keys. This is an XLS specification, not a network amendment of its own. One part of it belongs to an amendment: fixCleanup3_3_0 carries XLS-64.1 (the freeze and lock checks for assets moved into or out of pseudo-accounts) and is enabled on Mainnet. The rest of the document has no amendment of its own.

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

Network status
Not a network amendment
XLS
XLS-64
Spec status
Draft
Spec revision
Sep 8, 2026

What does this XLS propose?

What problem is the proposal intended to solve?

On the account-based XRPL, ordinary ledger objects cannot themselves hold XRP or tokens. Some protocols therefore need an AccountRoot governed exclusively by their rules and created under consistent security requirements.

How is the mechanism designed in the current draft?

The creating protocol deterministically derives an unpredictable AccountID from an object identifier and nonce. The AccountRoot receives exactly one <Object>ID link field, lsfDisableMaster, and lsfDepositAuth. Sequence remains zero and no RegularKey may be set. The pseudo-account and parent object are created together and deleted together.

How settled is the proposal?

This is an XLS specification, not a network amendment of its own. One part of it belongs to an amendment: fixCleanup3_3_0 carries XLS-64.1 (the freeze and lock checks for assets moved into or out of pseudo-accounts) and is enabled on Mainnet. The rest of the document has no amendment of its own.

What changes compared with the predecessor?

BeforeAfter
Each protocol had to define its own rules for an auxiliary account that holds assets but cannot sign transactions.AMMs, vaults, or future protocols could share the same immutable security, linking, and reserve rules.

Who is this change relevant to?

XRP holders and users

Users interact with protocol rules rather than an ordinary key holder. DepositAuth blocks direct payments to the pseudo-account.

Wallets and app developers

Explorers and wallets must recognize pseudo-accounts, resolve their parent object, and avoid presenting them as freely controlled user accounts.

Exchanges and issuers

Tokens can be held in protocol accounts whose movements are permitted exclusively by their parent protocol. This does not automatically change freeze, clawback, or authorization rights.

Node operators

Nodes check AccountID collisions, fixed flags, Sequence, linking, and the shared lifetime of AccountRoot and parent object.

What limitations and risks remain?

  • XLS-64 is a draft. Each protocol using it still needs its own concrete amendment logic.
  • A pseudo-account has no usable signing key and cannot sign an ordinary transaction.
  • It may be linked to exactly one parent object.
  • DepositAuth rejects ordinary payments; asset movements require explicitly permitted protocol paths.
  • The account must be deleted together with its parent object.
  • AMM pseudo-accounts created before the standard may carry their historical LedgerSequence instead of zero. That value must also never change.
  • An implementation bug in the parent protocol cannot be corrected by an account holder because there is no such key holder.

What fee and performance figures does the specification provide?

  • An owned pseudo-account increases its owner's reserve requirement by one additional object reserve.
  • An unowned pseudo-account, such as an AMM account, instead requires a burned special fee of at least one incremental owner reserve. The draft's historical 2 XRP value is adjustable through fee voting.
Technical details: transactions, fields, codes and invariants

Transactions

  • no general transactions; creation and deletion through the relevant parent protocol

Ledger objects

  • AccountRoot of the pseudo-account
  • linked parent object

Fields and flags

  • <Object>ID as exactly one link field
  • Flags / Sequence = 0 / RegularKey unset
  • lsfDisableMaster 0x00040000
  • lsfDepositAuth 0x01000000

Invariants

  • The parent object identified by <Object>ID must exist.
  • Exactly one <Object>ID field may be present.
  • lsfDisableMaster and lsfDepositAuth must remain set permanently.
  • New pseudo-accounts retain a zero Sequence and may not have a RegularKey. Older AMM pseudo-accounts may retain their different initial value but must never change it.

How does this proposal relate to others?

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

What happens next for this proposal?

This is an XLS specification, not a network amendment of its own. One part of it belongs to an amendment: fixCleanup3_3_0 carries XLS-64.1 (the freeze and lock checks for assets moved into or out of pseudo-accounts) and is enabled on Mainnet. The rest of the document has no amendment of its own.

The draft needs further technical development and may still change fundamentally or be abandoned. Network voting applies to fixCleanup3_3_0, the amendment that carries XLS-64.1; any further protocol change would need its own xrpld (formerly rippled) amendment and network vote.

Where does it sit within its amendment family?

PseudoAccount has no amendment family with other members on this site, so there is no progression to show here.

Which primary sources support this information?

← All XRPL amendments and XLS specifications