From 5a7ab26472bec5d3c41aa76f669938f18aa5b548 Mon Sep 17 00:00:00 2001 From: Dzmitry Hil Date: Fri, 17 May 2024 15:20:28 +0300 Subject: [PATCH] Update NFT spec with dynamic data. (#831) --- x/asset/nft/spec/README.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/x/asset/nft/spec/README.md b/x/asset/nft/spec/README.md index 3b9e7f8ef..c2536b999 100644 --- a/x/asset/nft/spec/README.md +++ b/x/asset/nft/spec/README.md @@ -34,6 +34,13 @@ Here is the list of features: We will discuss each feature separately. +### Minting +The minting is enabled for all issued NFT classes. The minting allows to mint a token for an NFT class by the issuer of the class. +There are two data types that can be used for NFT minting `DataBytes` and `DataDynamic`. The `DataBytes` contains immutable data bytes +array. The `DataDynamic` contains the list of the `DataDynamicItem` which can be updated depending on item's `editors`. +Currently supported `DataEditors` are `admin` and `owner`. If only one editor is set for the item, only that editor can update the +item's `data` using the`MsgUpdateData`. If both, both can update the `data`. If the `editors` list is empty no one can update the `data`. + ### Burning If this feature is enabled, it allows the holders of the token to burn the tokens they hold. It should be noted here that the issuer can burn their token regardless of this feature. @@ -105,6 +112,21 @@ This feature is related to the DEX, and if it is enabled, every time that an NFT + + Update + ⓘ + ⓘ + + + + + + + + + + + Burn ➕