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 in marketplaces, giveaways, or asset management workflows.
Practical examples include:
- Sending collectible NFTs to a buyer after purchase.
- Distributing promotional NFTs to multiple recipients.
- Automating NFT gifting or rewards within an application.
Properties
| Name | Meaning |
|---|---|
| To Account | The recipient's WAX blockchain account name to which the NFTs will be transferred. |
| Asset IDs (Comma-Separated) | A comma-separated list of NFT asset IDs that you want to transfer. |
| Memo | An optional memo or note to include with 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 managing the NFTs (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 NFT transfer. This typically contains transaction details such as transaction ID, block number, and status.
Example output structure:
{
"result": {
"transaction_id": "string",
"processed": { /* detailed transaction processing info */ }
}
}
No binary data output is produced by this node.
Dependencies
- Requires an API key credential that provides access to a WAX blockchain private key for signing transactions.
- Connects to a configurable WAX blockchain API endpoint (default is
https://wax.greymass.com). - Uses the
eosjslibrary for interacting with the WAX blockchain. - Requires proper network connectivity to the specified API endpoint.
Troubleshooting
- Invalid or missing private key: Ensure the API key credential includes a valid private key authorized to perform transfers on the WAX blockchain.
- Incorrect recipient account: Verify the "To Account" value is a valid WAX account name.
- Asset IDs format: Asset IDs must be provided as a comma-separated string without extra spaces; invalid IDs will cause transaction failure.
- API endpoint issues: If the default endpoint is unreachable or slow, specify a different reliable WAX API endpoint.
- Transaction expiration or blocksBehind errors: These indicate timing issues with the blockchain state; retrying the operation usually resolves them.
- Permission errors: The private key must have active permission on the sender account to authorize transfers.