Definition and scope
NFTokenPages and NFT Reserve Requirements addresses a distinct part of non-fungible tokens. Learn how NFTs are grouped into pages and when additional owner reserve is required.
XRPL NFTs are protocol-native ledger objects rather than smart-contract records. This collection follows an NFToken from its identifier and mint settings through custody, offers, transfers, brokered sales, royalties, storage pages, and destruction. An on-ledger token records protocol ownership and identifiers; off-ledger media, licensing, authenticity, and marketplace claims require separate evidence.
How it works
An account's NFTs are packed into linked NFTokenPage ledger entries. Reserve treatment depends on page objects and current protocol rules rather than a simple one-owner-object-per-token assumption.
- NFTokenPage: verify this field, object, or component against the cited protocol documentation.
- OwnerCount: verify this field, object, or component against the cited protocol documentation.
- account_nfts: verify this field, object, or component against the cited protocol documentation.
- reserve: verify this field, object, or component against the cited protocol documentation.
Practical example and checks
An application queries account_nfts and account_objects, observes page creation or compaction across mint and transfer operations, and reads current reserve documentation before estimating spendable XRP.
For production use, preserve the exact signed or queried data, record the network and validated ledger reference, and compare the result with the current primary documentation before changing off-ledger state.
Open the related live demo or evidence lab →Limits, risks, and common confusion
Page layout is an implementation detail that can change as tokens move. Wallets should not promise a fixed per-NFT reserve without checking current amendment behavior and account state.
An on-ledger token records protocol ownership and identifiers; off-ledger media, licensing, authenticity, and marketplace claims require separate evidence.
Current network status
Enabled on XRPL Mainnet. NonFungibleTokensV1_1 was enabled on XRPL Mainnet in feature responses from both official public servers at review time. Client and service support can still vary.
Status reviewed 2026-08-23. Amendment-dependent behavior must be rechecked against the network's live feature state before operational use.