Introduction
This process tool plugin allows you to mint native tokens and NFTs on the Cardano blockchain, with option to also embed additional form data into the transaction metadata according to the CIP-20 standard & NFT metadata according to the CIP-25 standard.
Note
- Do ensure that the minter account has sufficient balance for the required transaction fee to mint assets.
Plugin Properties
Configure Cardano Mint Token Tool
| Name | Description |
|---|---|
| Network Type | Select the network to mint assets on:
"Mainnet" uses assets with actual monetary value. Please use "Testnet" for testing purposes. |
| Backend Service | Select the backend service you wish to use to execute your blockchain queries/transactions with:
|
| Blockfrost Project Key | This property will only appear when Backend Service is Blockfrost. Paste in your generated mainnet/testnet project API key. See blockfrost.io. |
Token Properties
| Name | Description |
|---|---|
| Form | Select a form to retrieve minting data from. All fields from the selected form will be made available for field mapping in the sections below. |
| Minting Account | |
| Account Address | The account's address to mint and possess the freshly minted asset. |
| Account Mnemonic Phrase | This is the minter's account secret key required in order to perform actions with the minter's account. Only accepts Hash Variable that points to the minter's encrypted stored mnemonic phrase. Caution Account Mnemonic Phrase MUST be strictly secured at all times, and only viewable to the intended user. Do NOT key in the plain-text mnemonic phrase here. Anyone who possesses this phrase has full unrestricted control and can do irreparable damage! |
| Minting Configuration | |
| Minting Policy Handling | Select the method for the minting policy upon minting assets:
Do note that at the time of writing, the Generate New method only creates a non-locking single issuer minting policy. |
| Policy ID | This property will only appear when Minting Policy Handling is Reuse. The policy ID to be reused for minting. Typically a Hash Variable is used here. Do note that only non-locked policies can be freely reused. |
| Policy Script | This property will only appear when Minting Policy Handling is Reuse. The policy script that is associated with the policy ID. Typically a Hash Variable is used here. |
| Policy Secret Key | This property will only appear when Minting Policy Handling is Reuse. The policy secret key that is associated with the policy ID. Only accepts a Hash Variable that points to the encrypted stored policy secret key. |
| Mint Type | Select the type of asset to mint:
|
| Token Name | This property will only appear when Mint Type is Native Token. The token name (e.g.: MyFirstToken) |
| Token Symbol | This property will only appear when Mint Type is Native Token. Typical 3 to 5 characters long, and all letters in UPPERCASE. |
| Amount To Mint | This property will only appear when Mint Type is Native Token. Amount of native tokens to mint. |
| NFT Name | This property will only appear when Mint Type is NFT. The NFT name (e.g.: My-NFT-Test). |
| NFT Description | This property will only appear when Mint Type is NFT. To describe what this NFT is about. |
| NFT File Name | This property will only appear when Mint Type is NFT. The actual file name represented by this NFT. |
| NFT File Type | This property will only appear when Mint Type is NFT. Select the file type that this NFT represents:
|
| IPFS Content ID | This property will only appear when Mint Type is NFT. The IPFS content ID of the file that you have obtained after uploading your file to an IPFS gateway. |
| Additional Metadata | |
| Metadata | This property will only appear when Mint Type is Native Token. Fields available here depends on the Form selected. Select the field(s) you wish to embed into the transaction metadata. Written transaction metadata follows the CIP-20 standard. To learn more about transaction metadata, see https://developers.cardano.org/docs/transaction-metadata/. Transactions performed on the blockchain are publicly viewable, including its metadata, as it is intended primarily as an always-accessible proof of existence. Do NOT directly embed sensitive information to the transaction metadata. |
| NFT Properties | This property will only appear when Mint Type is NFT. Fields available here depends on the Form selected. Select the field(s) you wish to embed into the NFT metadata. Written NFT metadata follows to the CIP-25 standard. Transactions performed on the blockchain are publicly viewable, including its metadata, as it is intended primarily as an always-accessible proof of existence. Do NOT directly embed sensitive information to the NFT metadata. |
Store Minting Policy To Form
This configuration tab will only appear when Minting Policy Handling property is Generate New.
| Name | Description |
|---|---|
| Form | Select a form to store information about the newly generated minting policy. All fields from the selected form will be made available for field mapping in the section below. |
| Field Mapping | |
| Minting Policy ID | The policy ID. This value will be stored as the record ID of the chosen form. |
| Minting Policy Script | The policy script that is associated with the policy ID. |
| Minting Policy Secret Key (encrypted) | The secret key that signed the minting policy. This value is stored as an encrypted value in the database. |
| Minting Account | The account address that is associated with the policy ID. |
| Is Testnet Flag | To indicate if this policy belongs to the mainnet or testnet. |
Store Asset Data To Form
| Name | Description |
|---|---|
| Form | Select a form to store information about the newly minted asset. All fields from the selected form will be made available for field mapping in the section below. |
| Field Mapping | |
| Asset ID | The asset ID. This value is basically a combination of the policy ID and hex encoded token/NFT name. This value will be stored as the record ID of the chosen form. |
| Token Name | The native token/NFT asset name. |
| Associated Policy ID | The policy ID that minted this asset. |
| Asset Account Owner | The account address that minted and is first to possess the minted asset. |
| Is Testnet Flag | To indicate if this minted asset belongs to the mainnet or testnet. |
Store Response To Workflow Variable
| Name | Description |
|---|---|
| Is Transaction Successful | To indicate if this transaction has executed successfully. Returns true if successful, otherwise it returns false. You can use this value in your process to route your business logic and fully customize the user experience flow. |
| Is Transaction Validated | To indicate if this transaction has been successfully validated. This value will typically start with a false value. Only after the transaction has been confirmed/validated on the blockchain, only then this value will automatically be changed to true. |
| Transaction ID | To store the transaction ID of the transaction performed. |
| Transaction Explorer URL | To store an auto-generated URL to see transaction details on the official Cardano blockchain explorer. Do note that explorers typically has a short delay to sync to the latest blockchain state in order to reflect your transactions. |