In the last post, we went through how the Aventus blockchain supports NFTs. The post covered the pallet design, detailing the current possibilities and the avenues for further expansion.
This post is intended for version 0.4 and above of the AVN Gateway API.
If you get an error on the links, please, verify that you are viewing 0.4 and above before logging an issue.
In this post, we'll cover the various variable names involved in minting and managing NFTs. Whether you're minting an NFT, transferring an NFT, listing an NFT for sale, or even canceling an NFT, all variables are covered below. These variables should be used as is.
| Variable | Description |
|---|---|
avnRelayerAddress | The address of a AVN-approved relayer. |
nftOwnerAddress | The AVN address of the entity who will own the NFT. |
externalRef | This is a link to where the digital item that the NFT is linked to is stored. |
royalties | Configuration for which specific addresses get royalties from each resale of the NFTs. |
t1AdminName | The name of the entity (individual/contract) on tier1 that oversees the minted NFT e.g. marketplace. |
nftId | The ID of the NFT being referenced. |
recipientAvnAddress | When changing ownership of an NFT, this will be the AVN address of the recipient of the NFT. |
market | An ENUM value indicating the market where the NFT will be sold. |
Royalties
Royalties can be configured when minting an NFT or creating a batch of NFTs. Currently, royalties can only be configured during the minting/creation process and not after.
| Variable | Description |
|---|---|
recipient_t1_address | The address of an entity who will receive royalties from the sale of the NFT. For example, if the tier 1 is Ethereum, then this will be the recipient's Ethereum address. |
parts_per_million | The percentage of the sale fee that the specified recipient will receive. blockchain's don't generally handle decimals well, so this value is an integer. For example 10000 is 1% |