Skip to content
Not a network amendmentTier BUpcoming standardsSpec: Draft

URIToken XLS-35

An older draft for lightweight URI tokens, each requiring its own reserve, as an alternative to the XLS-20 NFT structure. This is a proposal, not an active network feature. Whether any part of it will launch, and when, remains open.

Sources reviewed Oct 5, 2026 · English page updated Oct 5, 2026 · Phil · CryptoTuts founder

Network status
Not a network amendment
XLS
XLS-35
Spec status
Draft
Spec revision
Feb 9, 2023

What does this XLS propose?

What problem is the proposal intended to solve?

XLS-20 groups NFTs into pages and uses separate offer objects with numerous special cases. The proposal seeks a smaller model consisting of a first-class object, a URI, and at most one current sell offer.

How is the mechanism designed in the current draft?

URITokenMint creates exactly one ltURI_TOKEN per issuer and URI combination and can optionally set an immutable content digest and tfBurnable. URITokenCreateSellOffer writes the price and optional destination directly into this object. URITokenBuy fulfills its single existing offer without pathfinding. Burn and Cancel remove the object or its sale fields, respectively.

How settled is the proposal?

This is a proposal, not an active network feature. Whether any part of it will launch, and when, remains open.

What changes compared with the predecessor?

BeforeAfter
Native XLS-20 NFTs are entries in NFTokenPage and trade through separate buy or sell offer objects.Each URIToken would be its own owner object carrying at most one directly embedded sell offer.

Who is this change relevant to?

XRP holders and users

Buyers can verify the optional digest against the URI's content. If tfBurnable is set, the issuer may burn the token later.

Wallets and app developers

Indexers receive one object per token and need to represent only one sell offer. Purchases allow no pathfinding and no currency other than the offer's currency.

Exchanges and issuers

Minters cannot mint for third parties and can create only one token per URI. The digest and burn right are defined at issuance.

Node operators

Each token occupies its own owner object, and its reserve requirement moves to the new owner when ownership changes.

What limitations and risks remain?

  • XLS-35 has been listed as a draft since 2023 and is not an active Mainnet feature.
  • There are no buy offers and at most one sell offer per token.
  • URITokenBuy supports no pathfinding. The purchase amount and offer must use the same currency.
  • Each token requires a full owner reserve instead of sharing an NFTokenPage reserve with other NFTs.
  • Setting tfBurnable at issuance lets the issuer burn the token later, even after a sale.
  • Without a digest, content at the URI may change. With a digest, a deliberate dynamic update no longer verifies against the original digest.
  • The proposal has no XLS-20 TransferFee or parallel marketplace offers.

What fee and performance figures does the specification provide?

  • Each URIToken requires its own owner reserve from its current owner. Burning it releases that reserve.
Technical details: transactions, fields, codes and invariants

Transactions

  • URITokenMint
  • URITokenBurn
  • URITokenBuy
  • URITokenCreateSellOffer
  • URITokenCancelSellOffer

Ledger objects

  • URIToken (ltURI_TOKEN)

Fields and flags

  • URITokenID derived from Issuer and URI
  • URI / Issuer / Owner
  • Digest (SHA512-Half)
  • Amount / Destination
  • tfBurnable 0x00000001

Invariants

  • An issuer can issue at most one URIToken for a given URI.
  • The token carries at most one active sell offer.

What does a concrete workflow look like?

In the proposed workflow, an issuer mints a URIToken with a digest. The owner sets one XRP offer. A buyer specifies the same URITokenID and at least the required amount, transferring the object and its reserve requirement to the buyer.

How does this proposal relate to others?

Every direct relationship has a type, an explanation and a primary source.

What happens next for this proposal?

This is a proposal, not an active network feature. Whether any part of it will launch, and when, remains open.

The draft needs further technical development and may still change fundamentally or be abandoned. Only a corresponding xrpld (formerly rippled) amendment would trigger a separate network vote.

Where does it sit within its amendment family?

URIToken has no amendment family with other members on this site, so there is no progression to show here.

Which primary sources support this information?

← All XRPL amendments and XLS specifications