Skip to content
EnabledTier ATokens

NonFungibleTokensV1_1 XLS-20

The corrected XLS-20 version provides native NFTs on the XRPL. NonFungibleTokensV1_1 is enabled on the XRP Ledger. xrpscan reports Oct 31, 2022 (UTC) as its activation date and rippled 1.9.2 as its first version.

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

Status
Enabled
XLS
XLS-20
Enabled
Oct 31, 2022 (UTC)

What does this amendment change?

Why does this amendment exist?

The first native NFT version was disabled after problems were found, requiring a new amendment ID incorporating the fixes.

How does the mechanism work?

XLS-20 stores native NFTs compactly in NFTokenPage objects with up to 32 entries. Mint, Burn, and three offer transactions cover issuance, selling, buying, brokerage, and deletion. Immutable token flags and an optional TransferFee are set at minting.

What changes compared with the predecessor?

BeforeAfter
The XRPL had no dedicated nonfungible token type or native marketplace workflow for individual tokens.NFTs have unique NFTokenIDs, compact page objects, and reserve-requiring buy or sell offers in the ledger.

Who is this change relevant to?

XRP holders and users

Holders can own NFTs directly in the ledger and trade them through buy or sell offers. The ledger guarantees neither value nor the availability of external metadata.

Wallets and app developers

Wallets and marketplaces must correctly handle page objects, direct and brokered offer acceptance, destination accounts, expiration times, and transfer fees.

Exchanges and issuers

Minters define transferability, taxon, URI, and any TransferFee at issuance. An authorized NFTokenMinter can mint on the issuer's behalf.

Node operators

Nodes manage compact NFTokenPage structures, unique IDs, and offer directories under reserve and deletion rules.

What limitations and risks remain?

  • URI is not validated, is limited to 256 bytes, and often references content outside the ledger.
  • Minting flags are immutable. DynamicNFT permits URI updates only for NFTs explicitly minted as mutable.
  • TransferFee is permitted only for transferable NFTs.
  • NFTokenPage requires an owner reserve and holds at most 32 NFTs.
  • NFTokenBurn removes at most 500 associated offers in one pass. Further offers may remain in the ledger.
  • The original NonFungibleTokensV1 amendment is deprecated. The corrected V1_1 version is the relevant foundation.

What fee and performance figures does the specification provide?

  • One NFTokenPage costs one owner reserve. With 32 NFTs on a full page, that reserve is shared across 32 entries.
  • Each NFTokenOffer requires its own owner reserve.
Technical details: transactions, fields, codes and invariants

Transactions

  • NFTokenMint
  • NFTokenBurn
  • NFTokenCreateOffer
  • NFTokenCancelOffer
  • NFTokenAcceptOffer (XLS-20 draft name: NFTokenOfferAccept, type 29)

Ledger objects

  • NFTokenPage containing NFToken entries
  • NFTokenOffer

Fields and flags

  • NFTokenID
  • NFTokenTaxon
  • Issuer / Owner
  • URI (at most 256 bytes)
  • TransferFee
  • NFTokenMinter
  • MintedNFTokens / BurnedNFTokens / FirstNFTokenSequence
  • Amount / Destination / Expiration
  • tfTransferable
  • lsfOnlyXRP 0x0002

API methods

  • account_nfts
  • nft_info (Clio)
  • nft_buy_offers
  • nft_sell_offers

Invariants

  • An NFToken may be stored only in a page whose lower 96 bits do not exceed the lower 96 bits of its NFTokenID.
  • An account with a difference between its minted and burned NFT counts cannot be deleted.

How does this amendment relate to others?

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

What happens next for this amendment?

NonFungibleTokensV1_1 is enabled on the XRP Ledger. xrpscan reports Oct 31, 2022 (UTC) as its activation date and rippled 1.9.2 as its first version.

These rules are already part of Mainnet. Server operators need a compatible xrpld (formerly rippled) version; ordinary wallet users do not need to enable anything manually.

Where does it sit within its amendment family?

Native NFTs: protocol progression

  1. NonFungibleTokensV1Deprecated · from rippled 1.9.0
  2. fixNFTokenDirV1Deprecated · from rippled 1.9.1
  3. NonFungibleTokensV1_1Enabled · from rippled 1.9.2
  4. fixNFTokenNegOfferDeprecated · from rippled 1.9.2
  5. fixRemoveNFTokenAutoTrustLineEnabled · from rippled 1.9.4
  6. fixNonFungibleTokensV1_2Enabled · from rippled 1.10.0
  7. fixNFTokenRemintEnabled · from rippled 1.11.0
  8. fixNFTokenReserveEnabled · from rippled 2.1.0
  9. fixEnforceNFTokenTrustlineEnabled · from rippled 2.3.0
  10. fixNFTokenPageLinksEnabled · from rippled 2.3.0
  11. NFTokenMintOfferEnabled · from rippled 2.3.0
  12. DynamicNFTEnabled · from rippled 2.4.0
  13. fixEnforceNFTokenTrustlineV2Enabled · from rippled 2.5.0

Which primary sources support this information?

← All XRPL amendments and XLS specifications