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 changes compared with the predecessor?
Who is this change relevant to?
What limitations and risks remain?
What fee and performance figures does the specification provide?
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?
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?
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.