đDeploy and Interact
In this section, we will deploy the contract, initialize it, and invoke all of the entrypoints created on testnet.
Last updated
In this section, we will deploy the contract, initialize it, and invoke all of the entrypoints created on testnet.
Last updated
Build
We will build the smart contract with the command below. In your production releases, we suggest using this flag and publishing the code. This way people can later check that the contract source matches the deployed module. More information about verifiable builds can be found here.
Please note that this build embeds the schema so you don't have to keep the schema as a separate compilation output anymore. The use of embedded schema is strongly recommended by Concordium.
Please note that the classical build command also works, however, you will get the following warning:
This is not a verifiable build. Consider using the --verifiable option before deploying the module. A verifiable build packages sources and makes it possible to verify that the sources match the deployed module.
You should run Docker in your system and let it pull the required image.
Do not include the Cargo.lock file in .gitignore.
Deploy
Initialize
Mint
There will be 3 different metadata for each state of our pet from puppy to strong dog. Each metadata and image below is uploaded to IPFS, therefore publicly available for you, and can be used for demo purposes.
Little Puppy CIS2 Compatible Metadata File
Cool Boy CIS2 Compatible Metadata File
Strong Dog CIS2 Compatible Metadata File
Excellent. Now we should create all necessary JSON files to mint our token. First, let's create a JSON file for MintParams. Remember the struct we created in the smart contract; it requires an owner and corresponding tokens that holds a list of MetadataUrl for a token ID and the amount of it. Please note that we will create it with only the first two metadata to be able to test the addMetadata and upgrade functions.
Don't forget to upload the metadata files to IPFS as well. This means when you mint a token, you should give a hyperlink to the metadata file and the SHA(256) of the content optionally.
Now let's mint our token with the following command.
Nice! We have successfully minted our token. Let's go and check it from our wallet.
Upgrade
Now, it is the big moment. Let's test whether this NFT is dynamic or not! We should be able to upgrade the metadata and evolve this little puppy into a cool boy! The upgrade function requires the token ID as a string in the JSON file.
Run the following command and see the magic!
The transaction is complete. So excited! Let's go and check!
Please keep in mind that this step can be triggered by an oracle or any other interaction.
Add Metadata
Now we are about to finalize our tutorial. One last step is the addition of new metadata. Our cool boy will become a strong and majestic star!
Let's go and check the AddParams struct to create the right form of JSON file. It expects tokensthat holds both token ID and MetadataUrl which is essentially url and hash.
Wait for the transaction's finalization.
Let's upgrade it once again with the same command in the previous step!
Are you ready to see our cool boy? Well, he may have changed a little...
Token Metadata History
Now, let's see what he has been through in all this time. We will invoke tokenMetadataList function to be able to see it. It accepts a vector of token IDs (see the following JSON) to be able to return all of the tokens in the contract and their history in the form of a TokenMetadataList struct which we defined as Vec<Vec<MetadataUrl>>.
And we will be able to see all the previous forms of the token we have from the contract state.
Isn't he gorgeous? Our little puppy is now a cool boy!
Wow, it has been a great journey so far. Since the very first moment we embarked on this journey we knew that our little puppy would become a tremendous loyal hero.
