WAX icon

WAX

Interact with the WAX blockchain

Overview

This node enables interaction with the WAX blockchain, specifically allowing users to transfer tokens from one account to another. It is useful in scenarios where automated token transfers are needed, such as paying for services, distributing rewards, or managing token balances programmatically on the WAX blockchain.

For example, a user can configure this node to send a specified amount of WAX tokens to another user's account with an optional memo describing the transaction purpose.

Properties

Name Meaning
API Endpoint The URL of the WAX blockchain API endpoint to connect to (default: https://wax.greymass.com).
Token Contract The smart contract managing the token, e.g., "eosio.token" for standard WAX tokens.
Symbol The symbol of the token to transfer, e.g., "WAX".
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).
Precision Number of decimal places for the token amount (default is 8).
Memo Optional text memo attached to the transfer transaction.

Output

The node outputs JSON data representing the result of the token transfer operation. This typically includes transaction details such as transaction ID, status, and any relevant blockchain response data confirming the transfer.

No binary data output is produced by this node.

Dependencies

  • Requires access to a WAX blockchain API endpoint (configurable via the "API Endpoint" property).
  • May require an API authentication token or private key credential configured in n8n to authorize transactions on behalf of the user.
  • Relies on internal resource and operation implementations bundled in the node's dependencies.

Troubleshooting

  • Common issues:

    • Incorrect or unreachable API endpoint URL may cause connection failures.
    • Invalid recipient account name or insufficient token balance will cause transaction errors.
    • Missing or invalid authorization credentials can prevent successful token transfers.
  • Error messages:

    • Errors related to network connectivity or endpoint unavailability suggest checking the API endpoint URL and network settings.
    • Authorization errors indicate missing or incorrect API keys/private keys; ensure proper credentials are configured.
    • Transaction rejection errors often mean invalid parameters (e.g., wrong token symbol, precision mismatch) or insufficient funds; verify input values carefully.

Links and References

Discussion