Definition and scope
Signer Lists, Weights, and Quorums Explained addresses a distinct part of accounts and wallet controls. Design approval policies using signer weights and the minimum quorum required for authorization.
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
SignerListSet defines signer accounts, integer weights, and a SignerQuorum. A multi-signed transaction is authorized only when unique valid signer weights meet or exceed that quorum.
- SignerListSet: verify this field, object, or component against the cited protocol documentation.
- SignerEntries: verify this field, object, or component against the cited protocol documentation.
- SignerWeight: verify this field, object, or component against the cited protocol documentation.
- SignerQuorum: verify this field, object, or component against the cited protocol documentation.
Practical example and checks
A policy might give an operations key weight 1 and two recovery keys weight 2 each, with a quorum chosen so routine and recovery paths match documented governance.
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
A mathematically valid quorum can still be operationally fragile. Avoid designs where one unavailable signer blocks every path or one compromised signer can act alone unintentionally.
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.