Skip to content
EnabledTier ATokens

DynamicNFT XLS-46

The URI of an NFT with the appropriate flag can be changed after minting. DynamicNFT is enabled on the XRP Ledger. xrpscan reports Jun 11, 2025 (UTC) as its activation date and rippled 2.4.0 as its first version.

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

Status
Enabled
XLS
XLS-46
Enabled
Jun 11, 2025 (UTC)

What does this amendment change?

Why does this amendment exist?

Some NFTs represent changing states. Their metadata URI therefore needs targeted updates without making every native NFT mutable.

How does the mechanism work?

At minting, tfMutable explicitly makes an NFT's URI mutable. The issuer or a minter authorized by it can then replace or remove the URI through NFTokenModify. NFTs without this minting flag retain XLS-20's immutable rule.

What changes compared with the predecessor?

BeforeAfter
A native XRPL NFT's URI set at minting remained immutable.Only an NFT created with tfMutable can later change its URI through NFTokenModify.

Who is this change relevant to?

XRP holders and users

Before acquisition, buyers need to see whether linked metadata can later be changed or removed.

Wallets and app developers

Marketplaces should show tfMutable and every URI change and refresh cached metadata after NFTokenModify.

Exchanges and issuers

Minters can represent changing game states, tickets, or updateable media but must disclose this control at minting.

Node operators

Nodes allow NFTokenModify only for authorized accounts and only for an NFT whose immutable minting flag permits updates.

What limitations and risks remain?

  • tfMutable must be set at minting and cannot be added later.
  • Only the URI changes. The ledger neither changes nor validates content at the URI's destination.
  • The issuer or an authorized minter retains technical control over the URI.
  • An NFT created without tfMutable remains immutable.
Technical details: transactions, fields, codes and invariants

Transactions

  • NFTokenMint
  • NFTokenModify

Ledger objects

  • NFTokenPage containing an NFToken

Fields and flags

  • Owner
  • NFTokenID
  • URI
  • tfMutable 0x00000010

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?

DynamicNFT is enabled on the XRP Ledger. xrpscan reports Jun 11, 2025 (UTC) as its activation date and rippled 2.4.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