Definition and scope
How to Activate an XRP Ledger Account addresses a distinct part of accounts and wallet controls. Learn why a classic address becomes an account only after receiving enough XRP for the base reserve.
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
A mathematically valid address becomes an AccountRoot ledger object only after receiving enough XRP to meet the current base reserve. Activation creates ledger state; generating a key pair alone does not create an on-ledger account.
- AccountRoot: verify this field, object, or component against the cited protocol documentation.
- base reserve: verify this field, object, or component against the cited protocol documentation.
- account_info: verify this field, object, or component against the cited protocol documentation.
- funding payment: verify this field, object, or component against the cited protocol documentation.
Practical example and checks
Fund a newly generated address with at least the live base reserve, wait for a validated payment, then query account_info and confirm the AccountRoot before submitting account transactions.
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
Reserve values can change through fee voting, and sending exactly an old quoted amount may leave the address unfunded. Never send a secret key to a faucet or activation service.
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.