From 6f261205d8ce170af47221e31512479b3d0dc84a Mon Sep 17 00:00:00 2001 From: ddawson Date: Fri, 17 Feb 2023 10:39:01 -0800 Subject: [PATCH] Add collections topic --- content/concepts/tokens/nft-collections.md | 18 ++++++++++++++++++ .../protocol-reference/data-types/nftoken.md | 9 +++++---- dactyl-config.yml | 5 +++++ 3 files changed, 28 insertions(+), 4 deletions(-) create mode 100644 content/concepts/tokens/nft-collections.md diff --git a/content/concepts/tokens/nft-collections.md b/content/concepts/tokens/nft-collections.md new file mode 100644 index 0000000000..a3d756bf0d --- /dev/null +++ b/content/concepts/tokens/nft-collections.md @@ -0,0 +1,18 @@ +--- +html: nft-collections.html +parent: non-fungible-tokens.html +blurb: You can mint NFTs as collections using the NFT Taxon field. +labels: + - Non-fungible Tokens, NFTs +--- + +# Minting NFTs into Collections + +You can use the `NFTokenTaxon` field to group NFTs into collections. As the minter, you can choose any numeric value from `0x0` to `0xFFFFFFFF`and assign it to NFTs as you create them. The significance of the taxon is entirely up to you. + +For example, for your first collection, you might set the `NFTokenTaxon` to `1`. You might have a collection of NFTs with taxon values of `316`, `420`, or `911`. You might use taxons that start with a digit to indicate the type of NFT (for example, all Real Estate NFTs have a taxon that starts with `2`). + +While the `NFTokenTaxon` field is required, you can set the value to `0` if you don't intend to create a collection. + +See [NFTokenTaxon](nftoken.html#nftokentaxon). + diff --git a/content/references/protocol-reference/data-types/nftoken.md b/content/references/protocol-reference/data-types/nftoken.md index 238a9f07e6..073865ac3d 100644 --- a/content/references/protocol-reference/data-types/nftoken.md +++ b/content/references/protocol-reference/data-types/nftoken.md @@ -98,14 +98,15 @@ The fourth section is a `NFTokenTaxon` created by the issuer. An issuer might issue several `NFToken` objects with the same `NFTokenTaxon`; to ensure that `NFToken` objects are spread across multiple pages, the `NFTokenTaxon` is scrambled using the fifth section, a sequential number, as the seed for a random number generator. The scrambled value is stored with the `NFToken`, but the unscrambled value is the actual `NFTokenTaxon`. -![Dumb Sequential](img/nftokene.png "Dumb Sequential") - -Notice that the scrambled version of the `NFTokenTaxon` is `0xBC8B858E`: the scrambled version of the `NFTokenTaxon` specified by the issuer. But the _actual_ value of the `NFTokenTaxon` is the unscrambled value. +Notice that the scrambled version of the `NFTokenTaxon` is `0xBC8B858E`, the scrambled version of the `NFTokenTaxon` specified by the issuer. But the _actual_ value of the `NFTokenTaxon` is the unscrambled value. ### Token Sequence -The fifth section is a sequence number that increases with each `NFToken` the issuer creates. The [NFTokenMint transaction][] sets this part of the `NFTokenID` automatically based on the `MintedTokens` field of the `Issuer` account. If the issuer's [AccountRoot object][] does not have a `MintedTokens` field, the field is assumed to have the value 0; the value of the field is then incremented by exactly 1. +The fifth section is a sequence number that increases with each `NFToken` the issuer creates. +![Sequence Number](img/nftokene.png "Sequence Number") + +The [NFTokenMint transaction][] sets this part of the `NFTokenID` automatically based on the `MintedTokens` field of the `Issuer` account. If the issuer's [AccountRoot object][] does not have a `MintedTokens` field, the field is assumed to have the value 0; the value of the field is then incremented by exactly 1. ## URI diff --git a/dactyl-config.yml b/dactyl-config.yml index db803c8a08..f491a18045 100644 --- a/dactyl-config.yml +++ b/dactyl-config.yml @@ -795,6 +795,11 @@ pages: - en - ja + - md: concepts/tokens/nft-collections.md + targets: + - en + - ja + - md: concepts/tokens/freezes.md targets: - en