Ripple’s developer arm, RippleX, is pushing to make the XRP Ledger’s newest asset class—Multi‑Purpose Tokens (MPTs)—easier to recognize, sort and integrate across the ecosystem. In a thread posted on X late Tuesday, the team announced a draft standard, XLS‑0089d, that would give every MPT a common set of on‑ledger metadata fields, from a ticker symbol and human‑readable name to a canonical icon URL and “asset_class” taxonomy.
“Multipurpose Tokens (MPTs) unlock new flexibility on the XRP Ledger, but they need structure to be useful across the ecosystem,” RippleX wrote. “We’re proposing a recommended metadata standard to make MPTs easier to discover, rank, and integrate.
Ripple Pushes Upgrade For Make Multi-Purpose Tokens
PTs were introduced last year via XLS‑82d, which let issuers replace the familiar currency and issuer pair with a cryptographic mpt_issuance_id, opening the door to tokens whose meaning is defined entirely by an embedded JSON blob. That design choice gave builders unprecedented latitude—for example, to mint wrapped assets, gaming points or real‑world‑asset receipts—yet it also broke many UX assumptions. Without a fixed currency code, wallets and block explorers struggle to display tokens consistently, and search engines cannot tell one issuance from another.
RippleX’s own description is blunt: MPTs “lack structured fields like a currency code. Instead, they rely on a free‑form metadata field, which makes them harder to identify or display in UIs.”
The proposal, authored by Ripple engineers Shawn Xie, Greg Tsipenyuk, Shashwat Mittal, Julian Berridi and Dennis Dawson, lays out a “minimally standardized” JSON schema: “This document proposes a minimally standardized metadata format for MPTs… The goal is not to restrict expressiveness, but to define a baseline set of fields that support reliable parsing and integration across services like block explorers, indexers, wallets, and cross‑chain applications.”
Under the draft, every token would carry required keys—currency, name, asset_class—and optional ones such as desc, icon, acct_name and an array of weblinks. A 1024‑byte limit keeps the payload on‑ledger, while an external URI can point to richer off‑chain data. The spec also classifies assets by purpose (rwa, defi, gaming, memes, wrapped, other) and, when applicable, by subclass (stablecoin, commodity, equity, etc.), giving explorers a taxonomy for side‑by‑side ranking with traditional IOUs.
Adherence will be voluntary, but RippleX plans to use soft pressure: “SDKs (xrpl.js, xrpl‑py, xrpl4j) will display a warning if metadata is missing, so developers know their tokens may be harder to discover or integrate. Nothing will be blocked.”
In another tweet, the team underscored the payoff for early adopters: with the schema in place, “MPTs [become] searchable by ticker… rankable alongside IOUs… usable in explorers, DEX UIs, [and] wallets… [and] easier to parse.
”For token issuers, the proposal promises a clear path to visibility without forfeiting flexibility: the on‑ledger stub ensures a base level of trust and immutability, while richer data can live off‑chain and be updated if branding or compliance needs change. Wallet vendors, in turn, gain a predictable way to surface icons, tickers and risk labels; DEX interfaces can filter or sort order books by asset class; and indexers can rank MPTs against IOUs in liquidity tables or price feeds.
For now, XLS‑0089d is currently a draft in the XRPL‑Standards repository, open for public comment. Once feedback is incorporated, the amendment needs to pass the 80% threshold to be activated. Given the Ledger’s built‑in amendment process, no hard fork is required.
At press time, XRP traded at $3.1497.
Related Posts
