Marketplace App
Deploying an NFT Marketplace App
If unfamiliar with the steps of deploying an app, go back to the first example where we explain in detail all the different parts of deploying an App.
If any of the messages in this example do not work, you might want to cross reference the messages with the ADO specific section which always contains the latest ADO versions to make sure they are correct. Other than that the logic will remain the same.
Make sure to read the Introduction to Apps before going through building an app.
Defining our App
For this App, we will be selling NFTs using the Marketplace ADO. The steps that will be performed:
Mint NFTs
Setup the marketplace
Send the NFTs to the markeplace to be sold
Buying the NFT
Defining the Messages
The components/ADOs we would need:
CW721 (NFT contract)
Although not necessary, if you are unfamiliar with these ADOs, it is suggested to read through each of the them before deploying an app.
Let us first start by representing the instantiation message for each of our ADOs:
Keep in mind that the app takes these messages as base64 encoded.
CW721
Make sure to set the minter as your own address.
As base64:
Marketplace
We only need to define the kernel address for the Marketplace component.
As base64:
App
The Kernel address used here might be outdated in the future. Check our deployed contracts to get the latest Kernel or run "chain config" in CLI which will also display the address.
There are several components found here. A simple name for the app, the components of the app itself and a reference to the “Kernel”. Each component of the app provides two values: a name used for referencing for other components within the app, and the base64 encoded instantiation message.
Instantiating the App
If you do not have the CLI downloaded, go to the Introduction to Apps section to get the latest version.
First, let us open the CLI by running andr
in our terminal. We then need to choose the chain we want to deploy on. Run "chain use"
in the CLI and select the testnet that you want to deploy on. For this example I will be using the Andromeda test-net Galileo-3.
If this is the first time using the CLI make sure to run "wallet add <wallet-name>"
in order to create a wallet. Then go to that chain's faucet (usually located in their discord) and request tokens.
We have already uploaded the App ADO to the Andromeda testnet. A simple way to check the latest code id for the App ADO is to query it from the ADODB using the chain you want to use.
In the CLI, while connected to the chain of choice, run:
The code Id to use will be returned.
Now we can instantiate our App. We will be using our wasm command to instantiate our app:
Do not copy and paste the command below as it will not work. Make sure to make the appropriate changes before running the command.
Replace the <code_id> with the returned code-id for the app ADO.
You will be using the contract addresses that were instantiated for you instead of the ones in this tutorial.
Interacting with the App
Mint NFTs
Now we need to mint an NFT to send to the marketplace.
Send NFT to Marketplace to be Sold
In order to start a sale on the NFT, we need to send it to the marketplace ADO.
The attached message is a start_sale
message to start the auction when the NFT is sent.
Buy the NFT
Now let us buy the NFT. On the CLI:
Make sure to use a wallet other than the owner of the NFT as the owner cannot buy the NFT.
Make sure to attach funds to the message equal to the listed price of the NFT which is 1000uandr in our case.
Conclusion
We have seen in this example how we can easily sell NFTs using our marketplace ADO. All this and more can be done using our web-app making the process even easier for the user.
Last updated