WAX icon

WAX

Interact with the WAX blockchain

Overview

This node interacts with the WAX blockchain, specifically to retrieve the token balance of a given WAX account. It is useful in scenarios where you need to programmatically check how many tokens (such as WAX tokens) an account holds on the blockchain. For example, it can be used in automated workflows that monitor user balances before executing transactions or for reporting purposes.

Properties

Name Meaning
API Endpoint The URL of the WAX blockchain API endpoint to connect to (default: https://wax.greymass.com).
Account Name The WAX blockchain account name whose token balance you want to retrieve.
Token Contract The smart contract managing the token, e.g., eosio.token for standard WAX tokens.
Symbol The symbol of the token to check the balance for, e.g., WAX.

Output

The node outputs JSON data containing the token balance information for the specified account and token symbol. The exact structure depends on the response from the WAX blockchain API but typically includes fields such as the amount of tokens held by the account.

If the node encounters an error during execution, it outputs a JSON object with an error field describing the issue.

No binary data output is produced by this node.

Dependencies

  • Requires access to a WAX blockchain API endpoint (default is https://wax.greymass.com).
  • Optionally requires an API key credential if the endpoint demands authentication (not explicitly required here).
  • No additional external dependencies are indicated.

Troubleshooting

  • Common issues:

    • Incorrect or misspelled account names will result in errors or empty balances.
    • Using an invalid or unreachable API endpoint will cause connection failures.
    • Specifying a token contract or symbol that does not exist on the blockchain will return no balance or errors.
  • Error messages:

    • Errors returned from the blockchain API (e.g., "account not found") should be checked against the input parameters.
    • Network or timeout errors indicate connectivity problems with the specified API endpoint.
  • Resolution tips:

    • Verify the correctness of the account name, token contract, and symbol.
    • Ensure the API endpoint URL is reachable and correct.
    • If using a private or restricted API endpoint, confirm that necessary credentials or tokens are configured.

Links and References

Discussion