Overview
This node enables the transfer of NFTs (Non-Fungible Tokens) on the WAX blockchain. It is designed to facilitate sending one or multiple NFTs from the user's account to another specified account. This is particularly useful for users who want to automate NFT transfers, such as marketplaces, gaming platforms, or collectors managing their digital assets programmatically.
Practical examples include:
- Sending purchased NFTs to a buyer's wallet automatically.
- Transferring NFTs as rewards or gifts within an application.
- Batch transferring multiple NFTs to different accounts in a workflow.
Properties
| Name | Meaning |
|---|---|
| To Account | The recipient's WAX blockchain account name where the NFT(s) will be sent. |
| Asset IDs (Comma-Separated) | A comma-separated list of NFT asset IDs to transfer. Each ID corresponds to a unique NFT. |
| Memo | An optional memo or note attached to the transfer transaction. |
| API Endpoint | The URL of the WAX blockchain API endpoint to connect to (default: https://wax.greymass.com). |
| Contract | The smart contract account handling the NFT transfer (default: atomicassets). |
Output
The node outputs a JSON object containing the result of the blockchain transaction. Specifically, it includes the full response from the WAX blockchain API after attempting the transfer, which typically contains transaction details such as transaction ID, block number, and status.
Example output structure:
{
"result": {
// Transaction response details from the WAX blockchain
}
}
No binary data is produced by this node.
Dependencies
- Requires an API key credential that provides access to a WAX blockchain private key and associated account.
- Connects to the WAX blockchain via a configurable API endpoint (defaulting to
https://wax.greymass.com). - Uses the
eosjslibrary for blockchain interaction and signing transactions. - Requires proper network connectivity to the specified WAX API endpoint.
Troubleshooting
- Invalid Account or Asset IDs: If the "To Account" or any asset ID is incorrect or does not exist, the transaction will fail. Verify account names and asset IDs before running.
- Insufficient Permissions: The private key used must have active permission on the sender's account. Errors related to authorization indicate permission issues.
- Network Issues: Connection failures to the API endpoint may occur if the endpoint is down or unreachable. Check network connectivity and endpoint URL.
- Transaction Expiry: Transactions expire if not included in a block within the configured time (30 seconds). Retrying may be necessary.
- Empty Asset IDs: Providing an empty string or improperly formatted asset IDs will cause errors. Ensure asset IDs are comma-separated without extra spaces.