WAX

Interact with the WAX blockchain

Actions9

Account Actions
Token Actions
- Get Account Token Balance
- Transfer Tokens
Asset Actions
- Get Assets
- Transfer Assets

Overview

This node interacts with the WAX blockchain to retrieve asset information associated with a specified WAX account. It is particularly useful for users who want to query and analyze digital assets (such as NFTs) owned by an account on the WAX blockchain. For example, a user might use this node to fetch all assets belonging to their account or filter assets by specific templates, collections, or schemas.

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 assets you want to retrieve.
Template ID (Optional)	Comma-separated list of template IDs to filter the assets returned.
Collection (Optional)	Comma-separated list of collections to filter the assets returned.
Schema (Optional)	Comma-separated list of schemas to filter the assets returned.
Code	The smart contract code to query against (default: `atomicassets`).

Output

The node outputs JSON data representing the assets retrieved from the WAX blockchain for the specified account and filters. Each item in the output array corresponds to an asset with its detailed properties as returned by the blockchain API. The structure typically includes asset identifiers, ownership details, template information, and metadata.

If the node supports binary data output (not evident from the provided code), it would represent any associated media or files linked to the assets, but this is not explicitly shown here.

Dependencies

Requires access to a WAX blockchain API endpoint (default is https://wax.greymass.com).
May require an API key or authentication token if the endpoint enforces access control (not explicitly stated in the code).
No additional external libraries are indicated beyond the bundled resource module.
No internal credential names are exposed; however, the node optionally accepts an API key credential for private key usage.

Troubleshooting

Common Issues:
- Incorrect or unreachable API endpoint URL may cause connection failures.
- Invalid or misspelled account names will result in no assets found or errors.
- Improperly formatted comma-separated lists for template IDs, collections, or schemas may lead to unexpected filtering results.
Error Messages:
- Errors thrown during execution are caught and can be output as error messages in the JSON response if "continue on fail" is enabled.
- Network or API errors should be checked by verifying endpoint accessibility and credentials.

WAX