Skip to content
EnabledTier ATokens

MPTokensV1 XLS-33

Multi-Purpose Tokens are a compact native standard for fungible assets. MPTokensV1 is enabled on the XRP Ledger. xrpscan reports Oct 1, 2025 (UTC) as its activation date and rippled 2.3.0 as its first version.

Sources reviewed Oct 5, 2026 · English page updated Oct 5, 2026 · Phil · CryptoTuts founder

Status
Enabled
XLS
XLS-33
Enabled
Oct 1, 2025 (UTC)

What does this amendment change?

Why does this amendment exist?

Fungible assets with many holders need a more compact alternative to pairwise trust lines.

How does the mechanism work?

An MPTokenIssuance stores an issuance's properties, while each MPToken object represents one holder's balance. This one-way model replaces the bidirectional RippleState relationship for this token type. Dedicated transactions create, modify, and delete issuances or authorize holder positions, while Payment and Clawback process MPT amounts.

What changes compared with the predecessor?

BeforeAfter
Fungible XRPL tokens primarily used pairwise trust lines with two sides, limits, and rippling properties.An issuer can create a compact, unidirectional issuance and maintain holder positions in dedicated MPToken objects.

Who is this change relevant to?

XRP holders and users

MPTs are issued assets, not a form of XRP. Before acquisition, check authorization, transfer, locking, escrow, trading, clawback, and TransferFee for the particular issuance.

Wallets and app developers

Integrations need the 192-bit MPTokenIssuanceID, integer MPT amounts, and dedicated ledger objects alongside traditional trust line tokens.

Exchanges and issuers

Issuers gain a more compact model for many holders and can configure issuer controls at issuance. Capability flags are fixed in V1 alone, while the lock state can already change when CanLock is enabled. DynamicMPT later permits supported capability updates.

Node operators

MPTs reduce long-term storage requirements compared with bidirectional trust lines but add serialization, ledger types, and API queries.

What limitations and risks remain?

  • MPTs do not represent bidirectional debt relationships and do not support balance netting like trust lines.
  • MPTokensV1 integrates only direct MPT payments. The DEX, cross-currency payments, checks, and AMMs require MPTokensV2.
  • MPT amounts are integers from 0 through 2^63 minus 1. AssetScale maps those integer units to a standard unit for application display and computation.
  • Issuance capability flags are fixed in V1 alone; the lock state remains mutable when CanLock is enabled. DynamicMPT changes the rules for supported properties when that extension is enabled.
  • TransferFee can be as high as 50 percent and requires the issuance to support transfers.
  • With RequireAuth, a holder must create its MPToken object before the issuer can authorize it.
  • MPTs are an alternative, not a general replacement for trust lines.

What fee and performance figures does the specification provide?

  • The MPT holder model is designed to use less on-ledger storage than complete bidirectional trust line structures; actual storage depends on the objects and metadata involved.
Technical details: transactions, fields, codes and invariants

Transactions

  • MPTokenIssuanceCreate
  • MPTokenIssuanceSet
  • MPTokenIssuanceDestroy
  • MPTokenAuthorize
  • Payment
  • Clawback
  • AccountDelete

Ledger objects

  • MPTokenIssuance
  • MPToken

Fields and flags

  • MPTokenIssuanceID
  • Issuer / Sequence
  • AssetScale
  • MaximumAmount / OutstandingAmount
  • TransferFee
  • MPTokenMetadata
  • MPTAmount
  • lsfMPTLocked 0x0001
  • lsfMPTCanLock 0x0002
  • lsfMPTRequireAuth 0x0004
  • lsfMPTCanEscrow 0x0008
  • lsfMPTCanTrade 0x0010
  • lsfMPTCanTransfer 0x0020
  • lsfMPTCanClawback 0x0040

API methods

  • ledger_entry
  • mpt_holders (Clio)

Result codes

  • temMALFORMED
  • tesSUCCESS

How does this amendment relate to others?

Every direct relationship has a type, an explanation and a primary source.

What happens next for this amendment?

MPTokensV1 is enabled on the XRP Ledger. xrpscan reports Oct 1, 2025 (UTC) as its activation date and rippled 2.3.0 as its first version.

These rules are already part of Mainnet. Server operators need a compatible xrpld (formerly rippled) version; ordinary wallet users do not need to enable anything manually.

Where does it sit within its amendment family?

Multi-Purpose Tokens: protocol progression

  1. DeletableAccountsEnabled · from rippled 1.4.0
  2. TicketBatchEnabled · from rippled 1.7.0
  3. DisallowIncomingEnabled · from rippled 1.10.0
  4. fixDisallowIncomingV1Enabled · from rippled 2.0.0
  5. MPTokensV1Enabled · from rippled 2.3.0
  6. PermissionedDEXEnabled · from rippled 2.5.0
  7. TokenEscrowEnabled · from rippled 2.5.0
  8. PermissionDelegationDeprecated · from rippled 2.5.0
  9. fixTokenEscrowV1Enabled · from rippled 3.0.0
  10. fixMPTDeliveredAmountEnabled · from rippled 3.0.0
  11. fixCleanup3_2_0Enabled · from xrpld 3.2.0
  12. DynamicMPTOpen for voting · from xrpld 3.3.0
  13. SponsorOpen for voting · from xrpld 3.3.0
  14. ConfidentialTransferOpen for voting · from xrpld 3.3.0
  15. PermissionDelegationV1_1Enabled · from xrpld 3.3.0
  16. fixCleanup3_4_0Enabled · from xrpld 3.4.0
  17. MPTokensV2In development

Which primary sources support this information?

← All XRPL amendments and XLS specifications