Definition and scope
How XRPL Multi-Signing Works addresses a distinct part of accounts and wallet controls. Require multiple independent signatures before a transaction can be authorized.
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
XRPL multi-signing authorizes a transaction when signatures from listed accounts reach the configured quorum. Signers sign a shared transaction payload without a normal SigningPubKey, and the assembled Signers array is submitted once.
- SignerListSet: verify this field, object, or component against the cited protocol documentation.
- SignerEntry: 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 treasury can require any two of three independent devices by assigning weight 1 to each signer and setting a quorum of 2, then rejecting any assembled transaction whose fields differ from the approved payload.
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
Multi-signing improves separation of authority but does not verify business intent or prevent colluding signers. Signer-list reserves, signer availability, and secure coordination remain operational dependencies.
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.