Overview
This node verifies whether a given WAX blockchain account exists. It sends a request to the specified WAX API endpoint to check the presence of the account on the blockchain. This is useful in workflows where you need to validate user accounts or ensure that an account name is valid before proceeding with further blockchain operations.
Practical examples:
- Validating user input for WAX account names in onboarding processes.
- Filtering or routing workflow execution based on the existence of WAX accounts.
- Automating checks before performing transactions or querying account-specific data.
Properties
| Name | Meaning |
|---|---|
| Account Name | The WAX blockchain account name to verify. |
| API Endpoint | The URL of the WAX blockchain API endpoint to query (default: https://wax.greymass.com). |
Output
The node produces two outputs:
Valid output: Contains items for accounts that exist on the WAX blockchain. Each item has a JSON object with:
account: The verified account name.created: The timestamp when the account was created (from the blockchain response).message: Confirmation message stating the account exists.
Invalid output: Contains items for accounts that do not exist or could not be verified. Each item has a JSON object with:
account: The account name that failed verification.message: Explanation of why verification failed (e.g., "Account does not exist on the WAX blockchain", "Account not found (404)", or detailed error messages from the API).
No binary data is produced by this node.
Dependencies
- Requires access to a WAX blockchain API endpoint, typically provided as a REST API URL.
- Uses HTTP POST requests to the
/v1/chain/get_accountendpoint of the WAX API. - No special credentials are required beyond network access to the API endpoint.
Troubleshooting
Common issues:
- Incorrect or misspelled account names will result in "Account does not exist" errors.
- Network connectivity problems or incorrect API endpoint URLs can cause request failures.
- If the API returns unexpected errors, these are surfaced in the invalid output with descriptive messages.
Error messages and resolutions:
"Account not found (404)": The account name does not exist on the blockchain. Verify the spelling and try again."Account verification failed: ...": Indicates an error returned by the API. Check the API endpoint URL and ensure it is reachable.- General network errors: Confirm internet connectivity and that the API endpoint is correct and operational.