-
Notifications
You must be signed in to change notification settings - Fork 0
Description
1. Why propose the MRC-721 protocol under MetaID?
-
Under the MetaID protocol, any PIN can be an NFT. The introduction of MRC-721 aims to uniformly specify any NFT recorded in a designated collection by the NFT creator.
-
Based on the MetaID protocol, any PIN can be considered as an NFT. Creators can manage NFTs through the NFT protocol and provide a unified standard for NFT asset application extensions.
2. How does the MRC-721 protocol associate with MetaID?
-
Propose to add a base node named 'NFT' under the rootId of the MetaID protocol.
-
The MRC-721 proposes to include a node named 'Collection' under the 'NFT' node, where creators can declare any NFT collection under the Collection node.
3. What is NFT Collection?
A standard NFT Collection contains the following information
-
-
TotalSupply
-
-
-
Name
-
-
-
Intro
-
-
-
Cover
-
-
-
Website
-
The MRC-721 protocol stipulates that the Collection includes the following fields
-
Collection
Json
{
“totalSupply”:"{Collection Minting Limit}",
“collectionName”:"{Collection Name}",
“intro”:"{Collection intro}",
“cover”:"{Collection Cover Image}",
“website”:"{Collection Official Website}",
“metaData”:"{Used for appending additional extra information,non-mandatory field}"
}
About Collection Item
Users do not need to declare the NFT serial number and validity. This part is handled by the indexer for sorting and validation.
-
items
Items represent the payload of each NFT in the Collection.
Json
{
"nftName":"Demo NFT item name",
"content":"metafile://[PINID]",
"intro":"Demo NFT item intro",
"collectionId":"Demo Collection Genesis PINID",
“metaData”:"{Used for appending additional extra information,non-mandatory field}"
}
Epilogue
MRC-721 is currently in the drafting phase, and the final adoption result will be determined by the open-source community. Other developers are welcome to provide suggestions.