Skip to content
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 problem is the proposal intended to solve?

Today's SignerList can authorize any account transaction. This all-or-nothing authority makes separation of duties harder and increases the potential damage from compromised signers.

How is the mechanism designed in the current draft?

SignerListID zero remains the global list. For a transaction type with UInt16 code TxType, the specialized list uses 1 plus TxType. SignerListSet accepts a TransactionTypeBitmask and can create, modify, or delete several lists derived in this way together. During multisigning, the ledger checks the global list and the list matching the particular transaction type.

How settled is the proposal?

This is a proposal, not an active network feature. Whether any part of it will launch, and when, remains open.

What changes compared with the predecessor?

BeforeAfter
An account could have only one global SignerList, whose quorum applied to all transaction types.Additional SignerLists could authorize only payments, TrustSet, or other selected transaction types.

Who is this change relevant to?

XRP holders and users

Ordinary personal accounts rarely need multiple lists. For jointly managed accounts, users could see which key set may perform each action.

Wallets and app developers

Wallets and custody systems must resolve the appropriate list and quorum configuration for each transaction type and administer multiple lists.

Exchanges and issuers

Exchanges and issuers could separate withdrawals, token administration, and account configuration organizationally and limit key risks.

Node operators

Nodes store one owner object for each additional list and check both global and type-specific permissions during MultiSign.

What limitations and risks remain?

  • XLS-49 is a draft, and its metadata also lists XLS-74 as a requirement.
  • Each additional SignerList requires its own owner reserve.
  • Even a narrowly scoped list can burn an account's XRP through deliberately high fees.
  • A list authorized for SignerListSet could indirectly grant itself further permissions.
  • The global list retains full access and cannot be restricted to selected transaction types.
  • The specification leaves specific tem and tec codes for invalid bitmasks or insufficient reserve dependent on implementation.

What fee and performance figures does the specification provide?

  • Each additional SignerList costs another owner reserve. The specification's historical 2 XRP value is not a permanently fixed amount.
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?

This is a proposal, not an active network feature. Whether any part of it will launch, and when, remains open.

The draft needs further technical development and may still change fundamentally or be abandoned. Only a corresponding xrpld (formerly rippled) amendment would trigger a separate network vote.

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.

Which primary sources support this information?

← All XRPL amendments and XLS specifications