XRPL Multi-Purpose Tokens: What's Live, What's Next for RWA Issuers

XRPL Multi-Purpose Tokens (MPT, XLS-33) are live on mainnet. Here is what they are, how they differ from trust lines, and what the roadmap means for RWA issuers today.

XRPL Multi-Purpose Tokens RWA Tokenization XRP Ledger Token Standards Compliance
XRPL Multi-Purpose Tokens: What's Live, What's Next for RWA Issuers

XRPL Multi-Purpose Tokens (MPT) crossed from specification into live infrastructure just over a year ago, and the protocol layer around them has been evolving at speed ever since. For issuers thinking about where to deploy regulated real-world assets, the current state of XRPL Multi-Purpose Tokens — what is on-chain, what is in-flight, and what is still pending — matters more than any market-size headline. This post lays it out clearly.

From Trust Lines to MPTs: What Changed and Why

The XRP Ledger has had fungible tokens since 2012, built on a trust line model. In that model, holding a token requires a bilateral relationship between the issuer account and each holder account. The holder establishes a trust line to signal willingness to hold a specific currency from a specific issuer, and the balance is recorded as a bidirectional debt.

This works for simple stablecoins, but it creates friction for institutional issuers of regulated assets: compliance rules must be layered on top of the base token, there is no native place to store structured metadata, and the on-ledger footprint grows with every holder.

XRPL Multi-Purpose Tokens replace this with an object-based model. Instead of relying on bilateral trustlines between issuer and holder, MPTs introduce a more streamlined, object-based model that simplifies token usage and reduces complexity for both developers and users. Each issuance is a single on-chain object — an MPTokenIssuance entry — and each holder has a compact MPToken entry. According to the XRPL Foundation’s MPT FAQ, MPTokens are designed to be significantly smaller on-ledger, up to 5× smaller for some tokens.

Critically, compliance controls are baked in at the protocol level rather than through custom application code. Per the XLS-33 specification, MPTs carry on-chain metadata and compliance controls — allow-listing, transfer limits, locking, clawback — at the protocol level, so issuers set rules in the token itself rather than in a separate custom contract.

The MPTokensV1 Amendment: What Went Live in October 2025

According to CryptoRank’s coverage of the activation, the XRP Ledger formally launched the Multi-Purpose Token standard with the MPTokensV1 amendment activating on October 1, 2025 at around 01:12 PM UTC, after receiving 28 approvals out of 38 validators. The upgrade embeds the new token standard directly into the XRP Ledger, which means developers no longer have to hard-code custom smart contracts for tokenization projects.

What MPTokensV1 delivered:

  • On-chain metadata. Each issuance gets a unique on-chain MPT Issuance ID (a 192-bit identifier) and can carry up to 1024 bytes of arbitrary metadata following the XLS-89 schema, covering fields like ticker, name, asset class, issuer name, and icon.
  • Issuer-controlled compliance flags. Issuers set capabilities — clawback, transfer restrictions, locking — at the time of issuance. Per the XLS-33 specification, an issuer can freeze or unfreeze a holder’s MPT balance using the MPTokenIssuanceSet transaction.
  • Holder opt-in. Holders cannot be forced to accept tokens; they must first send an MPTokenAuthorize transaction that explicitly signals willingness to hold the token. This replaces the implicit trust-line setup and gives issuers clear confirmation of a holder’s on-chain consent.
  • Cap-table visibility. A new mpt_holders API method returns a list of accounts that hold a specific MPT issuance, giving issuers a native on-chain investor registry.

What MPTokensV1 did not include: DEX or AMM trading. Per the XLS-33 specification, the standard covers the new data structures and MPT-to-MPT payments; later amendments will integrate MPTs with other XRPL features such as the DEX.

See Libertum’s token standards overview and XRPL standards page for how MPTs fit alongside ERC-3643, CIP-113, and the rest of the multi-chain stack.

Credentials, Permissioned Domains, and Issuer-Authorised Holders

MPTs are most powerful when combined with the credential and permissions infrastructure that has gone live in parallel on XRPL.

The Credentials amendment (XLS-70) provides an on-chain identity layer where authorised issuers can attest facts about accounts — identity verification, sanctions screening, investor classification — that any other participant can rely on. Building on this, Permissioned Domains (XLS-80) went live on February 4, 2026, after more than 91% of validators backed the amendment. As described in the XRPL Commons devnet report, Permissioned Domains let operators create controlled environments on XRPL: a domain operator defines which credentials are accepted, and accounts holding valid credentials automatically become members.

For RWA issuers, the practical implication is that the entire holder-authorisation workflow — KYC credential issued off-chain, credential verified on-chain, holder admitted to the MPT allow-list — can be encoded at the protocol level. Permissioned Domains use credential-based access to support KYC and AML compliance without exposing sensitive personal data on-chain. That is a meaningful difference from EVM token standards, where the same logic requires a separate smart contract and an external oracle.

Libertum’s T-Suite handles KYC/KYB, whitelist management, and investor on-boarding as part of the core issuance workflow — the platform’s multi-chain support means issuers using XRPL get the same structured on-boarding experience as those on EVM or Cardano. For more detail on how T-Suite manages these flows, see the T-Suite product documentation.

The DynamicMPT Amendment: Post-Issuance Flexibility

One practical constraint of the original MPTokensV1 design is that most token properties — metadata URI, transfer fee, capability flags — are fixed at the time of issuance. This made sense from a security standpoint, but it creates real problems for tokenised instruments that have legitimate reasons to evolve: a bond whose prospectus URI is updated, a fund whose transfer fee changes, or a real estate token whose metadata needs to reflect a new valuation or property management company.

The DynamicMPT amendment, currently in development per the XRPL known-amendments registry, addresses this directly. As documented on xrpldashboard.com’s live amendment tracker — which reflects the state of the network as of late October 2026 — DynamicMPT makes specific MPT properties mutable by default: the on-chain metadata, the transfer fee, and the ability to enable MPT issuance flags such as trading or issuer clawback. The same source notes the core issue: today, the base MPT specification fixes metadata, transfer fees, asset scale, and capability flags at issuance — only the lock flag is mutable post-mint via MPTokenIssuanceSet — which limits product flexibility for tokenised RWAs that need to update reference data, transfer fees, or URI metadata over time.

The DynamicMPT design also introduces an ImmutableFlags field, so issuers can selectively lock only the fields that should be immutable — giving them precise control rather than an all-or-nothing choice.

What Is Still Pending: DEX Trading of XRPL Multi-Purpose Tokens

The most significant capability still missing from the live MPT stack is secondary-market trading on the XRPL’s native DEX and AMM. The XRPL.org MPT documentation states plainly that trading MPTs in the DEX is not currently implemented.

The roadmap item is MPTokensV2 (XLS-82), listed on the XRPL known-amendments page as In Development: TBD. When it arrives, MPTokensV2 will extend the XRPL’s Decentralized Exchange to natively support Multi-Purpose Tokens as a tradeable asset class; MPTs will be pairable with XRP, trust line tokens, or other MPTs across existing DEX transactions such as OfferCreate, Payment, AMM, and Checks. A September 2026 pull request to the xrpl-py library adding MPTokensV2 support confirms that the amendment is still marked Supported::No in rippled and is listed under an in-development heading in the node configuration.

For issuers evaluating XRPL today, the practical implication is clear: MPTs support primary issuance, holder management, and compliant transfers right now. The XRPL.org migration guide advises that if your integration depends on pathfinding, DEX, AMM, cross-currency payments, or Checks, you should wait for MPTokensV2 before migrating that flow.

This is not a blocker for private placements or regulated securities with restricted transfer — which is precisely the profile of most RWA issuances today. It is, however, a constraint for issuers who need open secondary-market liquidity on XRPL itself. Those use cases will unlock once MPTokensV2 passes the validator threshold.

Confidential MPTs: Privacy on the Horizon

A further extension is in research and specification: Confidential MPTs (XLS-96). According to the XLS-96 specification published on xls.xrpl.org, which was created in January 2026 and updated in September 2026, the proposal introduces a cryptographic extension of XLS-33 that enables confidential balances and hidden transfer amounts while preserving public supply verifiability. The protocol uses EC-ElGamal encryption and zero-knowledge proofs to enforce transfer correctness and balance sufficiency without requiring validators to decrypt individual balances.

Critically, as a paper published on the IACR ePrint archive explains, confidentiality is scoped to transaction amounts and account balances; sender and receiver identities remain public, preserving XRPL’s account-based execution model. The design maintains full compatibility with existing MPT semantics and continues to support issuer-controlled operations such as freeze and clawback.

For institutional issuers, this matters: position sizes between competing institutions on the same public ledger are commercially sensitive. The XLS-96 design allows regulators and auditors to retain visibility through designated audit keys while keeping balances private from the general public — a model that aligns with how privacy-with-accountability is being framed across regulated digital-asset markets.

What This Means for Issuers Choosing a Chain

XRPL’s MPT stack is now a credible primary-issuance environment for regulated RWAs. The core features that institutional issuers need — protocol-level compliance controls, on-chain metadata, credential-gated holder authorisation — are live. The protocol offers 3-to-5 second finality and very low transaction costs, with no need for custom smart contracts.

The gap is secondary-market infrastructure: DEX trading and AMM liquidity for MPTs are still pending. That is a known, documented limitation with a named amendment in development.

For issuers who want to reach investors across multiple chains, Libertum’s T-Suite and XRPL standards support let you issue on XRPL alongside EVM (ERC-3643, ERC-20, ERC-721) and Cardano (CIP-113) from a single platform — without rebuilding compliance infrastructure for each chain. The Distribution Hub and Libby AI then help match issued tokens with the right investor base. If you are evaluating XRPL as an issuance venue, explore Libertum’s issuer solutions or review the full token standards documentation to see how MPT fits into a multi-standard issuance strategy.

FAQ

What is the difference between an XRPL MPT and an XRPL trust line token?

Trust line tokens are built on a bilateral relationship between issuer and holder — both parties must agree, and compliance rules must be added externally. MPTs use an object-based model with on-chain metadata and built-in compliance controls (allow-listing, clawback, transfer limits) set by the issuer at the token level, without custom smart contracts. Each issuance has a unique 192-bit Issuance ID and can carry up to 1024 bytes of structured metadata.

Can MPTs be traded on the XRPL DEX right now?

No. DEX and AMM trading for MPTs requires the MPTokensV2 amendment (XLS-82), which is currently listed as In Development: TBD on the XRPL known-amendments registry. Primary issuance, holder authorisation, and compliant peer-to-peer transfers are all supported today under the live MPTokensV1 amendment.

How does Libertum support XRPL Multi-Purpose Tokens?

Libertum’s T-Suite supports XRPL issued currencies and XRPL Multi-Purpose Tokens (MPT, XLS-33) as part of its multi-chain token standards, alongside EVM token standards (ERC-3643, ERC-20, ERC-721) and Cardano’s CIP-113. KYC/KYB on-boarding, whitelist management, dividends, and governance are all handled within the same platform regardless of which chain an issuer deploys on.