multi-asset contracts (equals ERC-1155 on Ethereum)
FA2 implementations
The FA2 standard has multiple implementations. We support the following:
Single
With this implementation, you can only have one collection. It is like the ERC-721 style. Only owner minter can mint new NFTs.
Multiple
With this implementation, you can have multiple collections. In each collection, you can define the number of copies of each NFT. It is somehow like the ERC-1155 style.
Smart contract deployment
We offer a set of default FA2 based smart contract templates, providing the main functionality needed for NFT projects.
chain: [string]chain to work with. Either TEZOS or GHOSTNET.
contract: [string]smart contract address.
Body parameters:
{"minterAddress":"string"}
minterAddress: [string] an account address that will be able to mint new NFTs.
Example:
curl -X POST "http://0.0.0.0:7000/v2/nftkit/nft/TEZOS/chain/GHOSTNET/contract/KT1QDuCUqmgotFqRtCK757J7xu47Bc7Ajp6q/minter"
-H"Content-Type: application/json"-d"{"minterAddress":"tz1YiZtFfeu6qmr2G6PnyisJNjxDyaEWXs9J"}"
val chain= TezosChain.GHOSTNETval smartContractAddress="KT1Ennr99qgqzKEUCEqypXEexH4wWzVL5a9m"val minterAddress="tz1YiZtFfeu6qmr2G6PnyisJNjxDyaEWXs9J"val result = TezosNftService.addMinter(chain, smartContractAddress , minterAddress)println("Operation ID: ${result.operationHash}")println("Operation external url: ${result.operationExternalUrl}")tl
NFT Minting
With this API, you can mint a new NFT. It have multiple options to manages NFT minting. You can generate NFT URI metadata by yourself or let the NFT KIT generate it.
metadataUri: [string] metadata URI of the new token.If you want to generate metadata URI using NFT KIT, set the "metadataUri "value as an empty string.
tokenId: [string] the account address who will receive the NFT
amount: [string] the account address who will receive the NFT
recipientAddress: [string] the account address who will receive the NFT
metadata: NFT KIT will use values inside metadata to generate metadata URI of the new token. It confirms the structure defined by ERC721 and ERC1155 standards. For more details about NFT metadata standard.
description: [string] a description of the token
name: [string] the name of this specific token
image: [string] this is the URL to the image of the item. Can be just about any type of image and can be IPFS URLs or paths.
image_data: [string] Raw SVG image data, if you want to generate images on the fly (not recommended). Only use this if you're not including the image parameter.
external_url: [string] This is the URL that will appear below the asset's image on OpenSea and will allow users to leave OpenSea and view the item on your site.
attributes: [string] To give your items a little more pizazz, we also allow you to add custom "attributes" to your metadata that will show up underneath each of your assets.