Skip to content
EnabledTier ATokens

NFTokenMintOffer XLS-52

A sell offer can be created immediately when an NFT is minted. NFTokenMintOffer is enabled on the XRP Ledger. xrpscan reports Feb 15, 2025 (UTC) as its activation date and rippled 2.3.0 as its first version.

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

Status
Enabled
XLS
XLS-52
Enabled
Feb 15, 2025 (UTC)

What does this amendment change?

Why does this amendment exist?

A minter had to create an NFT and its first sell offer in two separate transactions, leaving an unnecessary intermediate state without the intended offer.

How does the mechanism work?

NFTokenMint gains optional price, destination account, and expiration fields. If Amount is set, the transaction atomically creates the NFT and a sell NFTokenOffer whose ledger Flags include lsfSellNFToken.

What changes compared with the predecessor?

BeforeAfter
The issuer had to submit NFTokenMint first and then NFTokenCreateOffer as a separate transaction.One minting transaction can create the new NFT and its first sell offer together.

Who is this change relevant to?

XRP holders and users

Buyers do not receive the NFT simply because it is minted. They must still accept the created offer and check its price and destination restrictions.

Wallets and app developers

Marketplaces can save one step but must inspect both the new NFT and the new offer in the result.

Exchanges and issuers

Minters can offer an NFT for sale without an intermediate state and optionally restrict the offer to a destination account or expiration time.

Node operators

Nodes create up to two reserve-requiring objects in one transaction and must accept or reject the entire operation atomically.

What limitations and risks remain?

  • This extension creates only a sell offer. A buy offer cannot be created during minting.
  • The minting account owns the created sell offer; NFTokenMint takes no separate Owner field.
  • The offer does not automatically transfer the NFT.
  • Amount, Destination, and Expiration extend only NFTokenMint and do not change the remaining XLS-20 trading rules.

What fee and performance figures does the specification provide?

  • A successful transaction can require two additional reserves: one for a new NFTokenPage and one for the NFTokenOffer.
Technical details: transactions, fields, codes and invariants

Transactions

  • NFTokenMint

Ledger objects

  • NFTokenPage
  • NFTokenOffer

Fields and flags

  • Amount
  • Destination
  • Expiration
  • lsfSellNFToken 0x00000001 (NFTokenOffer)

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?

NFTokenMintOffer is enabled on the XRP Ledger. xrpscan reports Feb 15, 2025 (UTC) as its activation date and rippled 2.3.0 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