WAX Transfer Token

Transfer tokens on the WAX blockchain

Overview

This node enables transferring tokens on the WAX blockchain. It is useful for automating token transfers between accounts, such as paying users, distributing rewards, or moving funds programmatically within workflows. For example, a user could set up an automated payment system that sends a specified amount of WAX tokens to a recipient account whenever triggered.

Properties

Name	Meaning
To Account	The recipient's WAX blockchain account name to which tokens will be transferred.
Amount	The number of tokens to transfer (e.g., 1).
Symbol	The token symbol to transfer (e.g., "WAX").
Precision	Number of decimal places for the token amount (default is 8).
Memo	Optional memo string attached to the transfer transaction.
API Endpoint	The URL of the WAX blockchain API endpoint to connect to (e.g., "https://wax.greymass.com").
Contract	The token contract account on the blockchain (e.g., "eosio.token" for WAX tokens).

Output

The node outputs JSON data containing the result of the blockchain transaction for each input item. The json field includes a result object with details about the executed transfer transaction, such as transaction ID and status.

No binary data output is produced by this node.

Dependencies

Requires an API key credential providing a private key authorized to sign transactions on the WAX blockchain.
Connects to a WAX blockchain API endpoint (configurable).
Uses the eosjs library and its signature provider for transaction signing.
Requires network access to the specified blockchain endpoint.

Troubleshooting

Invalid credentials or private key errors: Ensure the provided private key is correct and has permission to authorize transfers from the source account.
Insufficient funds: Transfers will fail if the source account does not have enough tokens.
Incorrect account names or contract: Verify that the "To Account" and "Contract" fields are accurate and exist on the blockchain.
API endpoint connectivity issues: Confirm the endpoint URL is reachable and operational.
Precision mismatch: Make sure the precision matches the token's actual decimal places to avoid invalid quantity formatting.
Transaction expiration or block lag: If transactions fail due to timing, consider adjusting blocksBehind or expireSeconds parameters in the code (currently fixed).