Not a network amendmentTier BUpcoming standardsSpec: Draft
MultipleSignerLists XLS-49
A draft for multiple SignerLists per account, each authorized only for selected transaction types. This is a proposal, not an active network feature. Whether any part of it will launch, and when, remains open.
Sources reviewed Oct 5, 2026 · English page updated Oct 5, 2026 · Phil · CryptoTuts founder
- Network status
- Not a network amendment
- XLS
- XLS-49
- Spec status
- Draft
- Spec revision
- Feb 20, 2026
What does this XLS propose?
What changes compared with the predecessor?
Who is this change relevant to?
What limitations and risks remain?
What fee and performance figures does the specification provide?
Technical details: transactions, fields, codes and invariants
Transactions
- SignerListSet
- all transaction types submitted through MultiSign
Ledger objects
- multiple SignerList objects per AccountRoot
Fields and flags
- SignerListID = 0 for the global list
- SignerListID = 1 + TxType for a type-specific list
- TransactionTypeBitmask
- SignerQuorum / SignerEntries
Invariants
- An update must not change an existing SignerList object's SignerListID.
How does this proposal relate to others?
Every direct relationship has a type, an explanation and a primary source.
What happens next for this proposal?
Where does it sit within its amendment family?
MultipleSignerLists has no amendment family with other members on this site, so there is no progression to show here.