NFT Gen 2 Tech Doc
  • Introduction
  • Overview
    • NFT Data Chain
    • Cosmos SDK
    • Modules
      • Core Module
      • Oracle
  • Integration
    • Creating Schema
    • System Mode
      • Minting
      • Sending Action
    • User Mode
      • Minting
      • Sending Action
  • Data-chain Base URI
  • Getting Started
    • Installation (Golang)
    • Getting Started
      • Download Binary
      • Developer Resources
      • Binary Overview
      • Create Account
      • Faucet
      • Deploy NFT Gen2
      • Perform Action of NFT Gen2
      • Update NFT Schema
      • Script
    • SDK Package for NodeJs
      • Example Resources
      • Deploy NFT Gen2
      • Perform Action of NFT Gen2
      • Update NFT Schema
    • SDK for GO
      • Requirements
      • Installation
      • Usage
      • Preparing Key for Authentication
      • Supported Messages and Queries
      • Examples
    • Six Protocol Developer Community
Powered by GitBook
On this page
  1. Integration
  2. System Mode

Minting

PreviousSystem ModeNextSending Action

Last updated 2 years ago

Below will explain the flow to create metadata on NFT Data Chain.

Explanation

When you decide to reveal the NFT metadata, you, as a creator, need to send the transaction to NFT Data Chain to initialize data for each token. In this mode, NFT Data Chain will fully trust your request.

During the creation of the metadata, it is required to pass an origin address of the holder along with the message. Optionally you can send along the native address (Cosmos-based address) with the message. NFT Data Chain will map those two addresses together and assume they belong to the same owner (EVM Support will involve this part). However, if you don't plan to manage this native address (key storing), NFT Chain will generate one account and throw away the private key upon creation. In another sense, this native account is the bridge account between EVM (or origin) account and the native account.

To explain how the creator control how to create data for each token.