Definition and scope
Issued Currencies vs. Multi-Purpose Tokens addresses a distinct part of issued tokens and trust lines. Choose between trust-line-based assets and MPTs by comparing structure and capabilities.
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
Classic issued currencies use RippleState trust lines and integrate deeply with rippling and the historic payment engine; MPTs use dedicated issuance and holder objects with a different control and accounting model.
- RippleState: verify this field, object, or component against the cited protocol documentation.
- MPTokenIssuance: verify this field, object, or component against the cited protocol documentation.
- authorization: verify this field, object, or component against the cited protocol documentation.
- ecosystem support: verify this field, object, or component against the cited protocol documentation.
Comparison at a glance
Use these dimensions to choose between the concepts without treating their names as interchangeable.
| Dimension | Issued currency | Multi-Purpose Token |
|---|---|---|
| Core ledger objects | RippleState trust lines | MPTokenIssuance and MPToken |
| Historic payment integration | Deep integration with rippling and paths | Depends on supported MPT flows |
| Holder relationship | Bilateral trust line | Dedicated holder object |
| Selection test | Payment-engine and trust-line needs | MPT controls and ecosystem support |
Practical example and checks
A designer compares required authorization, transferability, DEX or payment integration, holder object costs, clawback needs, wallet support, and migration constraints before choosing a model.
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
Newer does not automatically mean better. The right model depends on required protocol integrations and ecosystem support, while both remain issuer obligations rather than 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.