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 WAX tokens to multiple recipients based on certain triggers.

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 smart contract managing the token (e.g., "eosio.token" for WAX tokens).

Output

The node outputs a JSON object containing the result of the blockchain transaction. This includes details about the transaction receipt returned by the WAX blockchain after submitting the transfer action. The output structure is:

{
  "result": {
    // Transaction response object from the WAX blockchain API
  }
}

No binary data is produced by this node.

Dependencies

Requires an API key credential with a private key authorized to sign transactions on the WAX blockchain.
Connects to a specified WAX blockchain API endpoint.
Uses the eosjs library and its signature provider for signing and sending transactions.

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: The source account must have enough tokens to cover the transfer amount plus any network fees.
Incorrect account names or contract: Verify that the "To Account" and "Contract" fields are accurate and exist on the WAX blockchain.
API endpoint connectivity issues: Confirm the API endpoint URL is reachable and operational.
Precision mismatch: Make sure the precision matches the token's actual decimal places to avoid invalid quantity formatting.