Definition and scope
When and How the XRPL Master Key Can Be Disabled addresses a distinct part of accounts and wallet controls. Understand the prerequisites, benefits, and lockout risks of disabling master-key signing.
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
The asfDisableMaster AccountSet flag prevents the account's intrinsic master key pair from authorizing transactions. XRPL requires another signing method, such as a regular key or signer list, before the master key can be disabled.
- asfDisableMaster: verify this field, object, or component against the cited protocol documentation.
- AccountSet: verify this field, object, or component against the cited protocol documentation.
- RegularKey: verify this field, object, or component against the cited protocol documentation.
- SignerList: verify this field, object, or component against the cited protocol documentation.
Practical example and checks
An operator first installs and tests replacement authority, confirms it from a second system, then submits AccountSet with the master key and validates that the alternate signer can still transact.
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
Disabling the master key without a recoverable alternate can permanently lock the account. A signer list or regular key can itself be lost or misconfigured, so recovery must be tested before the change.
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.