WAX icon

WAX

Interact with the WAX blockchain

Actions12

Asset → Mint Asset

AI-generated

Overview

This node interacts with the WAX blockchain to mint a new asset (NFT) from a specified template within an AtomicAssets collection. It is useful for users who want to programmatically create new NFTs on the WAX blockchain, specifying details such as the collection, template ID, new owner, and optional data overrides. For example, a game developer could use this node to mint unique in-game items as NFTs and assign them to players' accounts.

Use Case Examples

  1. Mint a new NFT from a predefined template in an AtomicAssets collection and assign ownership to a specific WAX account.
  2. Override immutable and mutable data fields during minting to customize the asset's metadata.
  3. Back the minted NFT with specific EOSIO assets to add value or utility.

Properties

Name Meaning
API Endpoint WAX blockchain API endpoint URL used to connect to the blockchain network.
Collection Name The AtomicAssets collection that owns the template from which the asset will be minted.
Template ID ID of the template to mint from; the asset's schema is derived from this template.
New Asset Owner The WAX account name that will receive ownership of the newly minted asset.
Contract The AtomicAssets contract account name, typically 'atomicassets', used for signing the minting transaction.
Immutable Data Override (JSON) JSON object to override per-asset immutable data fields matching the schema format; usually empty when minting from a template.
Mutable Data (JSON) JSON object specifying per-asset mutable data fields matching the schema format.
Back with Assets Optional comma-separated list of EOSIO asset strings to back the minted NFT with, adding value or utility.

Output

JSON

  • json - The JSON output contains the result of the minting operation, including details of the minted asset or error information if the operation failed.

Dependencies

  • Requires connection to a WAX blockchain API endpoint, typically needing an API key or private key credential for signing transactions.

Troubleshooting

  • Common issues include invalid template ID, incorrect collection name, or insufficient permissions for the signing account, which may cause transaction failures.
  • Error messages may indicate connection issues to the WAX API endpoint or malformed JSON in data overrides; ensure endpoint URL is correct and JSON data is properly formatted.

Links

Discussion