Actions9
- Account Actions
- Token Actions
- Asset Actions
Overview
The node interacts with the WAX blockchain, specifically allowing users to stake WAX tokens on an account's NET bandwidth resource. Staking NET bandwidth is a common operation in WAX and EOSIO-based blockchains to allocate network resources for transactions. This node is useful when automating resource management for WAX accounts, such as preparing accounts for higher transaction throughput or delegating staking to other accounts.
A practical example: A user wants to programmatically stake 10 WAX tokens to their account's NET bandwidth to ensure smooth transaction processing during high activity periods.
Properties
| Name | Meaning |
|---|---|
| API Endpoint | The URL of the WAX blockchain API endpoint to connect to (e.g., https://wax.greymass.com) |
| Account Name | The WAX account name on which to perform the staking operation |
| Amount (WAX) | The amount of WAX tokens to stake on the NET bandwidth |
| Transfer Stake to New Account | Whether the staked tokens' ownership should be transferred to a new account (true/false) |
Output
The node outputs JSON data representing the result of the staking operation on the WAX blockchain. This typically includes transaction details such as transaction ID, status, and any returned blockchain response data confirming the stake action.
No binary data output is indicated.
Dependencies
- Requires access to a WAX blockchain API endpoint.
- May require an API authentication token or private key credential configured in n8n to authorize staking transactions.
- Network connectivity to the specified API endpoint must be available.
Troubleshooting
- Common issues:
- Incorrect or unreachable API endpoint URL can cause connection failures.
- Insufficient WAX balance in the account will cause staking transactions to fail.
- Invalid account names or permissions may lead to authorization errors.
- Error messages:
- Errors related to "insufficient funds" indicate the account does not have enough WAX tokens.
- "Unauthorized" or "permission denied" errors suggest missing or invalid credentials.
- Network timeouts or connection refused errors point to endpoint accessibility problems.
- Resolutions:
- Verify the API endpoint URL and network connectivity.
- Ensure the account has sufficient WAX balance.
- Confirm that the required API authentication credentials are correctly set up in n8n.