Actions9
- Account Actions
- Token Actions
- Asset Actions
Overview
The node enables interaction with the WAX blockchain, specifically allowing users to transfer digital assets from one account to another. This is useful in scenarios where you need to programmatically move NFTs or other tokenized assets on the WAX blockchain, such as automating asset distribution, managing game items, or handling marketplace transactions.
For example, a user can specify a list of asset IDs and transfer them to a different WAX account with an optional memo note describing the transfer purpose.
Properties
| Name | Meaning |
|---|---|
| API Endpoint | The URL of the WAX blockchain API endpoint to connect to (default: https://wax.greymass.com). |
| To Account | The WAX account name to which the assets will be transferred. |
| Asset IDs (Comma-Separated) | A comma-separated list of asset IDs that are to be transferred. |
| Contract | The smart contract managing the assets (default: atomicassets). |
| Memo | An optional text memo attached to the transfer transaction. |
Output
The node outputs JSON data representing the result of the transfer operation. This typically includes confirmation details such as transaction status, transaction ID, or any returned metadata from the blockchain after executing the transfer.
No binary data output is indicated by the source code.
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 for signing transactions (not explicitly shown but implied by the presence of credentials in the bundled code).
- The node depends on internal resource definitions and execution logic imported from a local
resourcesmodule.
Troubleshooting
Common issues:
- Invalid or missing asset IDs may cause the transfer to fail.
- Incorrect "To Account" names or accounts that do not exist on the WAX blockchain will result in errors.
- Network connectivity problems with the specified API endpoint can prevent successful communication.
- Missing or invalid credentials for signing transactions may cause authorization failures.
Error messages:
- Errors thrown during execution will be caught and can be output as error messages if "Continue On Fail" is enabled.
- Typical error messages might include "Invalid asset ID", "Account does not exist", or "Transaction failed".
Resolution tips:
- Verify all asset IDs are correct and belong to the sender.
- Confirm the destination account exists on the WAX blockchain.
- Ensure the API endpoint URL is reachable and correct.
- Provide valid credentials if required for transaction signing.