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 changes compared with the predecessor?
Who is this change relevant to?
What limitations and risks remain?
What fee and performance figures does the specification provide?
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?
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.