NFT marketplace smart contract tutorial#
In this tutorial you will create an NFT Marketplace. The contract provides some functionalities, such as minting semi-fungible, and non-fungible tokens, buying and selling NFTs with fixed prices, setting commissions for your marketplace, and setting royalties for your NFTs to get some fees from secondary sales in this marketplace. Before you start, it is important to note that this is not a beginner-level tutorial; it does not cover the basics like downloads, node configurations, wallet setup and export, and so on.
This tutorial will be the first part of the Marketplace. There will be no UI interaction. You will invoke the functions with
concordium-client. In the end, while implementing a dApp, what you have to do is implement a client that connects your backend with the blockchain.
concordium-client is that client and does that. In the second part which will be released soon, you will implement this marketplace from scratch with an empty React template.
You can download the contract from this link. Go over the functions of both the contract file
lib.rs and its helpers.
Errors.rs contains the custom error files (check this link to see how you can implement them), the
state.rs includes the state structs of the marketplace and tokens, the
params.rs includes the parameter structs and
cli_client.rs is the marketplace’s client in order to talk with a CIS-2 token contract. In order to call another contract’s function (because the marketplace will need to invoke the transfer() function of the NFT contract to be able to transfer tokens), your marketplace smart contract needs a client.
This client is a sort of intermediary layer between those two contracts. It allows the parent contract to abstract away the logic of calling the child contract for the methods. Check the client code and see the
invoke_contract_read_only() to understand how contract invocation works from another contract. It needs to implement the functions that you will invoke and requires some parameters such as the address of the contract, entrypoint, and so on. Basically, the parent has to implement the child’s function and provide all necessary inputs. That function connects with the child contract, gets the response, and conveys it to the master contract after deserializing it.
Before starting the next steps, make sure that you have setup the developer environment with the tools needed.
To continue with the tutorial, click here.