Actions12
- Account Actions
- Token Actions
- Asset Actions
- Template Actions
- Schema Actions
Template → Create Template
AI-generatedOverview
This node interacts with the WAX blockchain to create a new asset template within a specified collection and schema. It is useful for users who want to define new templates for minting digital assets on the WAX blockchain, specifying properties such as transferability, burnability, maximum supply, and immutable data associated with the template.
Use Case Examples
- Creating a new asset template in a WAX collection to define unique digital collectibles.
- Setting up a template with specific rules like non-transferable or burnable assets for a blockchain game.
Properties
| Name | Meaning |
|---|---|
| API Endpoint | The WAX blockchain API endpoint to connect to for performing operations. |
| Collection Name | The name of the collection in which the new template will be created. |
| Schema Name | The schema name that the template will adhere to. |
| Transferable | Boolean flag indicating whether assets minted from this template can be transferred. |
| Burnable | Boolean flag indicating whether assets minted from this template can be burned. |
| Max Supply | Maximum number of assets that may be minted from this template. A value of 0 means unlimited supply. |
| Contract | The AtomicAssets contract account name, typically 'atomicassets', used for signing under the active permission. |
| Immutable Data (JSON) | A JSON object containing per-template immutable data whose keys and types match the schema format. |
Output
JSON
returnData- The data returned from the WAX blockchain after creating the template, typically including transaction details and template information.
Dependencies
- WAX blockchain API endpoint
- An API key credential for signing transactions
Troubleshooting
- Ensure the API endpoint URL is correct and accessible to avoid connection errors.
- Verify that the collection name and schema name exist and are correctly spelled to prevent operation failures.
- Check that the JSON provided in Immutable Data matches the expected schema format to avoid validation errors.
- If the node throws permission or signing errors, confirm that the API key or private key credentials are correctly configured and have the necessary permissions.