Skip to content
In developmentTier ADeFi & DEX

MPTokensV2 XLS-82

Multi-Purpose Tokens are intended to become directly tradable on the native DEX. MPTokensV2 is listed by xrpl.org as in development and is not yet listed for Mainnet voting. A stable xrpld (formerly rippled) release and validator voting are still required.

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

Status
In development
XLS
XLS-82
Version
Not released
Enabled
Not enabled

What is the development status?

Why is this feature being developed?

MPTokensV1 provides the token type but does not yet fully support its use in native trading and liquidity paths.

How is the mechanism intended to work?

MPTokensV2 lets existing DEX, payment, check, and AMM transactions reference an MPT through mpt_issuance_id without adding separate top-level transaction fields or ledger object types. Each operation applies the relevant issuance capabilities, authorization, and issuance or holder lock checks, with transaction-specific issuer exceptions.

What is still required before Mainnet?

After implementation and testing, the change must appear in a stable xrpld (formerly rippled) release before Mainnet voting can begin.

What changes compared with the predecessor?

BeforeAfter
MPTokensV1 supports direct MPT payments but keeps MPTs separate from order books, cross-currency paths, checks, and AMMs.The proposed extension allows MPTs to be combined with XRP, trust line tokens, or other MPTs in existing liquidity paths.

Who is this change relevant to?

XRP holders and users

After activation, holders could trade MPTs directly through order books and pools. The issuance's issuer rights would continue to apply in the DEX.

Wallets and app developers

DEX and payment software must process mpt_issuance_id in all asset and amount variants, paths, and API responses.

Exchanges and issuers

Issuers could create native MPT markets but would need CanTrade enabled, plus CanTransfer for transfers between holders.

Node operators

Nodes extend the existing DEX engine with MPT checks and the MPT variant of STIssue, without introducing a second trading engine.

What limitations and risks remain?

  • This amendment is a draft in development, not a Mainnet feature.
  • MPTs do not support payment rippling through reciprocal balances like trust lines.
  • Trades fail or are removed from the order book if CanTrade, CanTransfer, authorization, or lock status does not permit them.
  • The MPT amount limit from XLS-33 remains in place.
  • The draft uses the spelling tecOBJECT_NO_FOUND alongside tecOBJECT_NOT_FOUND. This page retains both specification labels rather than silently treating them as identical.
  • The specification and implementation may change before a stable xrpld (formerly rippled) release.
Technical details: transactions, fields, codes and invariants

Transactions

  • AMMCreate
  • AMMDeposit
  • AMMWithdraw
  • AMMDelete
  • AMMClawback
  • CheckCreate
  • CheckCash
  • OfferCreate
  • Payment

Ledger objects

  • MPTokenIssuance
  • MPToken
  • Offer
  • AMM
  • Check

Fields and flags

  • mpt_issuance_id in Amount and Asset
  • Amount / Amount2
  • Asset / Asset2
  • TakerGets / TakerPays
  • SendMax / DeliverMin / Paths
  • lsfMPTAMM 0x00000004
  • lsfMPTCanTrade
  • lsfMPTCanTransfer
  • lsfMPTRequireAuth

API methods

  • path_find
  • ripple_path_find
  • amm_info
  • book_offers

Result codes

  • temDISABLED
  • tecOBJECT_NOT_FOUND / tecOBJECT_NO_FOUND
  • tecNO_AUTH
  • tecNO_PERMISSION
  • tecFROZEN
  • tecPATH_DRY
  • tecPATH_PARTIAL
  • tecUNFUNDED_OFFER
  • terNO_AMM

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?

MPTokensV2 is listed by xrpl.org as in development and is not yet listed for Mainnet voting. A stable xrpld (formerly rippled) release and validator voting are still required.

After implementation and testing, the change must appear in a stable xrpld release before Mainnet voting can begin.

Where does it sit within its amendment family?

AMM and Clawback: protocol progression

  1. DeletableAccountsEnabled · from rippled 1.4.0
  2. TicketBatchEnabled · from rippled 1.7.0
  3. DisallowIncomingEnabled · from rippled 1.10.0
  4. AMMEnabled · from rippled 1.12.0
  5. ClawbackEnabled · from rippled 1.12.0
  6. fixDisallowIncomingV1Enabled · from rippled 2.0.0
  7. fixInnerObjTemplateEnabled · from rippled 2.1.0
  8. fixAMMOverflowOfferEnabled · from rippled 2.1.1
  9. fixAMMv1_1Enabled · from rippled 2.2.0
  10. fixPreviousTxnIDEnabled · from rippled 2.2.0
  11. AMMClawbackEnabled · from rippled 2.3.0
  12. fixAMMv1_2Enabled · from rippled 2.3.0
  13. fixInnerObjTemplate2Enabled · from rippled 2.3.0
  14. fixFrozenLPTokenTransferEnabled · from rippled 2.4.0
  15. DeepFreezeEnabled · from rippled 2.4.0
  16. PermissionedDEXEnabled · from rippled 2.5.0
  17. fixAMMv1_3Enabled · from rippled 2.5.0
  18. PermissionDelegationDeprecated · from rippled 2.5.0
  19. fixAMMClawbackRoundingEnabled · from rippled 3.0.0
  20. SponsorOpen for voting · from xrpld 3.3.0
  21. PermissionDelegationV1_1Enabled · from xrpld 3.3.0
  22. fixCleanup3_3_0Enabled · from xrpld 3.3.0
  23. fixCleanup3_4_0Enabled · from xrpld 3.4.0
  24. MPTokensV2In development

Which primary sources support this information?

← All XRPL amendments and XLS specifications