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. Staking NET tokens is a common operation in blockchain environments like WAX to allocate bandwidth or network resources to an account, which can improve transaction throughput and reduce fees.
This node’s "Stake NET" operation enables users to specify an amount of WAX tokens to stake as NET bandwidth for a given WAX account. It also supports optionally transferring the staked tokens' ownership to another account.
Practical examples include:
- A user staking NET tokens to their own account to increase network resource limits.
- An account owner staking NET tokens but transferring the stake to a newly created account, useful during account creation or delegation scenarios.
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 account name on which to perform the staking operation. |
| Amount (WAX) | The quantity of WAX tokens to stake as NET bandwidth. |
| Transfer Stake to New Account | Boolean flag indicating whether the staked tokens 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 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 to authorize staking transactions on behalf of the specified account.
- The node depends on bundled internal resources and operations logic (not fully visible here), which handle the actual blockchain interaction.
Troubleshooting
Common issues:
- Incorrect or unreachable API endpoint URL may cause connection failures.
- Insufficient WAX balance in the account to cover the staking amount plus any transaction fees.
- Invalid or missing account name will prevent the operation from executing.
- Lack of proper authorization or missing credentials can cause transaction rejection.
Error messages:
- Errors related to network connectivity or API endpoint unavailability.
- Blockchain errors indicating insufficient funds or invalid account.
- Permission denied errors if the provided credentials do not authorize staking.
Resolutions:
- Verify the API endpoint URL and network connectivity.
- Ensure the account has enough WAX tokens to stake.
- Confirm that the correct account name is used.
- Provide valid API authentication credentials with necessary permissions.