XRP News Today: RippleX Introduces XLS-0089d Metadata Standard for XRP Ledger

RippleX, the development arm focused on advancing the XRP Ledger, has introduced a new metadata standard proposal named XLS-0089d. This proposal aims to enhance the organization and visibility of tokens on the XRP Ledger, particularly for multipurpose tokens (MPTs). The standard defines a 1024-byte metadata field per token and introduces a standardized schema to support token discoverability and machine-readable parsing by external services such as wallets, block explorers, and cross-chain applications.

The schema includes a set of required metadata fields that provide core identification elements. These include a ticker, a short uppercase alphanumeric code limited to six characters, a name and description, which are UTF-8 strings used for display and description, and an icon, an HTTPS URL pointing to a visual icon. Additionally, an issuer_name field is included to make the source of the token easier to identify by both users and systems. Such structured fields provide consistency and allow greater sorting and comparison between tools.

Besides the required fields, XLS-0089d also includes optional fields that provide more detailed information, particularly helpful in the context of real-world assets (RWAs) like tokenized equities, stablecoins, or treasury instruments. Fields such as asset_class and asset_subclass can be used to determine whether a token belongs to other categories such as gaming, decentralized finance (DeFi), or RWAs. Optional data structures allow token issuers to add shaped data pertinent to their kind, such as interest rates, maturity dates, or issuer type for RWAs. These fields offer more context for institutional users, explorers, and indexers seeking detailed insight into a token’s function and origin. The schema can also be used to connect additional data through uniform resource identifiers (URIs), allowing more data to be kept off-ledger so that the 1024-byte metadata field does not limit what the identity of the token can include.

The XLS-0089d standard is backward-compatible and entirely optional. Parties issuing tokens on the XRP Ledger are not obliged to use the schema. Any token that decides not to adhere will still operate on the XRPL as usual, keeping the network stable and compatible. With this opt-in scheme, wallets, indexers, and explorers can opt to handle tokens with different metadata values as they want. These systems are not supposed to crash or produce errors but just ignore nonstandard entries or revert to basic default displays.

As this news broke, developers discussed the topic on GitHub and other technical groups. RippleX made it clear that the goal of the standard was to make the ecosystem more usable, not to impose a strict set of restrictions. The increased attention on Ripple’s ecosystem following recent technical developments could be contributing to market interest. Despite the proposed XLS-0089d still being reviewed, the community's response has been positive, with many developers appreciating the potential benefits of the new metadata standard for token organization and visibility on the XRP Ledger.