Definition and scope
Understanding the XRPL AccountRoot Object addresses a distinct part of accounts and wallet controls. Read the ledger object that stores an account's balance, sequence, flags, owner count, and settings.
An XRPL account is a ledger object controlled by cryptographic authorization—not an app login. These topics explain how accounts begin, how transactions are ordered, and how master keys, regular keys, signer lists, and domain settings change operational control. Authorization changes should be rehearsed with independent recovery paths. No guide requires sharing a seed, family secret, or private key.
How it works
AccountRoot is the root ledger entry for an account. Fields include Account, Balance, Sequence, OwnerCount, Flags, and optional settings such as Domain, RegularKey, TicketCount, and signer-list information represented elsewhere.
- AccountRoot: verify this field, object, or component against the cited protocol documentation.
- Balance: verify this field, object, or component against the cited protocol documentation.
- Sequence: verify this field, object, or component against the cited protocol documentation.
- OwnerCount: verify this field, object, or component against the cited protocol documentation.
- Flags: verify this field, object, or component against the cited protocol documentation.
Practical example and checks
A wallet can read Balance and OwnerCount to estimate spendable XRP, inspect Flags before changing authorization, and use Sequence when preparing the next ordinary transaction.
For production use, preserve the exact signed or queried data, record the network and validated ledger reference, and compare the result with the current primary documentation before changing off-ledger state.
Open the related live demo or evidence lab →Limits, risks, and common confusion
AccountRoot does not contain secret keys or a complete history. Field presence and flags require protocol-aware decoding, and balances must be considered alongside reserves and owned objects.
Authorization changes should be rehearsed with independent recovery paths. No guide requires sharing a seed, family secret, or private key.
Current network status
Enabled on XRPL Mainnet. The underlying protocol capability is available on XRPL Mainnet. Individual services can still impose additional rules, limits, or trust assumptions.
Status reviewed 2026-08-23. Amendment-dependent behavior must be rechecked against the network's live feature state before operational use.