Create
NMKR Studio provides a streamlined approach to launching your token project, whether it's Non-Fungible Tokens (NFTs) or Fungible Tokens (FTs).
NMKR Studio provides a streamlined approach to launching your token project, whether it's Non-Fungible Tokens (NFTs) or Fungible Tokens (FTs).
To create a new project, go to the NFT Projects Tab and select "Create new Project". This will open a new Tab where you will configure the fundamental settings for your project. It's a simple four-step process, and if you need to change something, you can always return to the previous page by clicking "previous."
Many of these settings can be changed, but some cannot be changed after the project is created. You can't change whether the project is for fungible or non-fungible tokens, and you can't change the policy locking settings after you created the project. Please read the policy documentation to learn more about these very important settings.
It is preselected to create a Non-Fungible Token, if you want to create a Fungible Token, please select "Fungible Token (FT) project" and specify the maximum Token supply. The maximum Token supply limits the amount of Fungible Tokens (identical copies) that can be minted for each token that is uploaded to the project. You can create multiple different Fungible Tokens within the same project, but they will all have the same maximum supply. If this is not what you want, kindly start a new project for each FT you want to create. If you want to learn more about that, please read Non-Fungible Tokens and Fungible Tokens.
Give the project a unique name. This name won't be shared and will only be used to make it easier for you to locate your project in the NFT projects tab.
The image you can upload by clicking "Upload project image" will be only used for NMKR Pay PNG files with a 300x100px maximum size are acceptable.
The project URL and Description won't be shared and are also optional. They should help you to better identify your projects.
The Token Name Prefix can contain maximum 15 characters and no special characters. This Prefix will be added to the Asset Name of each token in the project. If you specify a prefix here, please don't add another one in the Tokens metadata or token naming itself, or you will have them double.
Specify how long the token is reserved for the customer via NMKR Pay. The token will shift from "reserved" to "free" and become available to mint for other customers if a client doesn't pay within that period. by standard it is set to 20 minutes, which is a good value for normal blockchain load.
Add your twitter handle for example @nmkr_io to this field to allow customers that use the "share on twitter" feature after a successful purchase in NMKR Pay, to tag you in the tweet.
The sendback or MinUtxo is a minimum amount of ADA that has to be send together with each transaction that contains an NFT. This is a Cardano requirement and is mandatory except you activate the MultiSig payment. The standard is 2ADA for each NFT, but you can decide if you want to choose 2ADA for every 5 NFTs, or the option "MinUtxo" which calculates for every transaction depending on the token amount and metadata size.
This field allows you to select the storage provider. The standard storage provider is IPFS, but with the integration of Iagon, NMKR Studio can now use another decentralized storage provider for your project. You don't need to worry about the metadata template placeholders switching from IPFS to Iagon because they do so automatically.
If you're using custom metadata without a template, make sure to use "image": "<iagon_link>" instead of "image": "<ipfs_link>".
As Iagon is still in it's very early days, the storage on Iagon is always going to be additional to the upload and pin to IPFS. Please expect a slower uploading process than IPFS.
Please select the wallet that you want to use to receive the funds from the sales. If you don't find any wallets to select in the dropdown, please set up a wallet for your account first. The payout wallet you specify here, will be the main receiver wallet if you specify any additional payout wallets.
In the second step of creating your project, you either set up a new policy or you choose to import an existing policy.
If you decide to create a new policy ID, please decide if you want to have the policy locked and also specify the locking date.
The Policy locking and specified locking dates can't be changed afterwards! Please read the policy documentation if you need more details to understand what this means.
To learn how to import a policy ID, please read the documentation about how to use one policy ID for multiple projects.
The metadata template tab shows you the standard metadata template of your project. It is recommended to use the standard template for creating the project. You can edit the metadata template whenever you want in your project's settings.
Fields with values that should apply for every token in the project can be added as hard written values. Like a field with a link to your website. use the prepared boxes or add them manually to the template.
Add custom fields and placeholders to your metadata template. The actual values of the fields that replace the <placeholders> will be given later on with each token individually.
If you want to learn more about the metadata template and the fields and placeholders in it, please click here.
In this tab, you can also decide if your project should use the CIP-25 or CIP-68 metadata standard. CIP-25 is the regular metadata standard, where CIP-68 is the one to choose if you want to repeatedly update your NFTs with a smart contract. For more info about CIp-68, please click here.
The summary allows you to determine whether all of your settings are specified correctly. Please double-check before clicking "save project" to create the project. If you need to make changes, please use "previous" to navigate to the previous tabs.