Files
xrpl-dev-portal/content/concepts/tokens/nfts/index.md
ddawson ab146f40a8 Reorg tokens & stablecoin use case
wip

fix links

fix 2 links

trim and add topics

Add checklist, rename sc subtopics

Fix internal links

Add DEX/AMM

Add graphics

reorg files

reorg/rename

Fix blurb

Remove old JA files

edits per review

review changes

rename output file name of index files to match the folder name

Update output file and parent filenames

add reusable links snippet

fix broken links

Update Ja file

Move path.md to same location in i18n folder

Revert naming for nft-collections page

Rename to match files in En and Ja

update links to reflect updated file name

Rename nft-auctions under Ja folder and update links throughout

Rename nftoken-authorized-minting and update links throughout

Fix links

Rename the nft-fixed-supply Ja file to match the reorg in English  and update links

Move nft-reserve-requirements file in Ja and update links

Fix some more broken links

Fix more broken links by renaming html files back

Stablecoin reorg: fix various issues

Remove nfts_by_issuer method (unreleased) page

Remove redundant parent: attrs from config file

Fix syntax highlighting of Authorizing Another Minter js

Fix config/frontmatter errors
2023-12-06 17:21:23 -08:00

2.9 KiB

html, parent, blurb, labels
html parent blurb labels
non-fungible-tokens.html tokens.html Introduction to XRPL NFTs.
Non-fungible Tokens, NFTs

Non-Fungible Tokens

The XRP Ledger natively supports non-fungible tokens (NFTs, or “nifties” in the vernacular). Non-fungible tokens serve to encode ownership of unique physical, non-physical, or purely digital goods, such as works of art or in-game items.

(Added by the [NonFungibleTokensV1_1 amendment][].)

To represent digital assets similar to these, use the XRP Ledger's Non-Fungible Tokens feature (sometimes referred to by its standards draft number, XLS-20).

NFTs on the XRP Ledger

On the XRP Ledger, an NFT is represented as a [NFToken][] object. An NFT is a unique, indivisible unit that is not used for payments. Users can mint (create), hold, buy, sell, and burn (destroy) NFTs.

The ledger stores up to 32 NFTa owned by the same account in a single [NFTokenPage object][] to save space. As a result, the owner's reserve requirement for NFTs only increases when the ledger needs to make a new page to store additional tokens.

Accounts can also name a Broker or an Authorized Minter who can sell or mint NFTs on their behalf.

NFTs have several immutable settings that are defined when the token is minted. These include:

  • Identifying data that uniquely defines the token.
  • Whether the issuer can burn the token, regardless of who currently holds it.
  • Whether the holder of the token can transfer it to others. (An NFT can always be sent to or from the issuer directly.)
  • If transfers are allowed, the issuer can charge a transfer fee as a percentage of the sale price.
  • Whether the holder can sell the NFT for fungible token amounts, or only for XRP.

NFT Lifecycle

Anyone can create a new NFT using the [NFTokenMint transaction][]. The NFT lives on the [NFTokenPage object][] of the issuing account. Either the owner or an interested party can send a [NFTokenCreateOffer transaction][] to propose buying or selling the NFT; the ledger tracks the proposed transfer as a [NFTokenOffer object][], and deletes the NFTokenOffer when either side accepts or cancels the offer. If the NFT is transferable, it can be traded multiple times between accounts.

You can destroy an NFT you own using the [NFTokenBurn transaction][]. If the issuer minted the token with the tfBurnable flag enabled, the issuer can also burn the token, regardless of the current owner. (This could be useful, for example, for a token that represents a ticket to an event that is used up at some point.)

The NFT Lifecycle

For more info about transferring NFTs, see Trading NFTs on the XRP Ledger.

{% include '_snippets/rippled-api-links.md' %} {% include '_snippets/tx-type-links.md' %} {% include '_snippets/rippled_versions.md' %}