Definition and scope
What Are Multi-Purpose Tokens? addresses a distinct part of issued tokens and trust lines. Introduce XRPL's newer fungible-token model and its on-ledger issuance object.
Unlike native XRP, most fungible assets on XRPL represent obligations issued by an account. This category explains the trust relationships, flags, controls, and accounting conventions that make issued currencies and newer Multi-Purpose Tokens work. Issued assets depend on their issuer and must not be described as native XRP. Issuer controls apply only to eligible issued balances.
How it works
MPTokens use an MPTokenIssuance ledger entry and per-holder MPToken entries instead of classic RippleState trust lines. Issuance flags define transferability, locking, authorization, clawback, and other lifecycle behavior.
- MPTokenIssuance: verify this field, object, or component against the cited protocol documentation.
- MPToken: verify this field, object, or component against the cited protocol documentation.
- MPTokensV1: verify this field, object, or component against the cited protocol documentation.
- issuance ID: verify this field, object, or component against the cited protocol documentation.
Practical example and checks
An issuer creates an MPTokenIssuance, records the issuance ID, authorizes holders when required, and uses MPT-specific transactions and amount formats for transfers.
For production use, preserve the exact signed or queried data, record the network and validated ledger reference, and compare the result with the current primary documentation before changing off-ledger state.
Open the related live demo or evidence lab →Limits, risks, and common confusion
MPTokensV1 is enabled on Mainnet, but client, custody, and exchange support can lag. MPTs remain issuer-dependent assets and are not native XRP.
Issued assets depend on their issuer and must not be described as native XRP. Issuer controls apply only to eligible issued balances.
Current network status
Enabled on XRPL Mainnet. MPTokensV1 was enabled on XRPL Mainnet in feature responses from both official public servers at review time. Client and service support can still vary.
Status reviewed 2026-08-23. Amendment-dependent behavior must be rechecked against the network's live feature state before operational use.