Actions113
- blocks Actions
- Get Block Details By Block Hash UTXOs
- List Transactions by Block Hash EVM
- List Transactions by Block Hash UTXOs
- List Transactions By Block Hash XRP
- List Transactions By Block Height XRP
- List Transactions by Block Height EVM
- List Transactions by Block Height UTXOs
- Get Block Details By Block Height UTXOs
- Get Block Details By Block Height EVM
- Get Block Details By Block Height XRP
- Get Block Details By Block Hash EVM
- Get Block Details By Block Hash XRP
- Get Last Mined Block EVM
- Get Last Mined Block UTXOs
- Get Latest Mined Block XRP
- List Latest Mined Blocks UTXOs
- List Latest Mined Blocks EVM
- List Latest Mined Blocks XRP
- HD Wallets Actions
- Sync HD Wallet (xPub, yPub, zPub)
- Derive And Sync New Receiving Addresses UTXO
- Derive And Sync New Change Addresses UTXO
- Derive And Sync New Receiving Addresses EVM
- Derive And Sync New Receiving Addresses XRP
- List Synced Addresses UTXO
- List Synced Addresses EVM
- List Synced Addresses XRP
- List HD Wallet (xPub, yPub, zPub) Transactions UTXO
- List HD Wallet (xPub, yPub, zPub) Transactions EVM
- List HD Wallet (xPub, yPub, zPub) Transactions XRP
- List HD Wallet (xPub, yPub, zPub) UTXOs
- Prepare A UTXO-Based Transaction From HD Wallet (xPub, yPub, zPub)
- Prepare A Transaction From an Address in HD Wallet (xPub, yPub, zPub) EVM
- Get HD Wallet (xPub, yPub, zPub) Assets UTXO
- Get HD Wallet (xPub, yPub, zPub) Assets EVM
- Get HD Wallet (xPub, yPub, zPub) Assets XRP
- Get HD Wallet (xPub, yPub, zPub) Details UTXO
- Get HD Wallet (xPub, yPub, zPub) Details EVM
- Get HD Wallet (xPub, yPub, zPub) Details XRP
- List Synced HD Wallets (xPub, yPub, zPub)
- Activate HD Wallet (xPub, yPub, zPub)
- Delete Synced HD Wallet (xPub, yPub, zPub)
- address-latest Actions
- Utilities Actions
- simulate-transactions Actions
- addresses-latest Actions
- Get Address Balance Solana
- List Transactions By Address Solana
- Get Address Balance EVM
- Get Address Balance XRP
- Get Address Balance Kaspa
- List Confirmed Transactions By Address EVM
- List Transactions by Address XRP
- List Confirmed Transactions By Address UTXOs
- List Confirmed Transactions By Address Kaspa
- List Unconfirmed Transactions by Address UTXOs
- List Internal Transactions By Address EVM
- Get Next Available Nonce EVM
- List Confirmed Tokens Transfers By Address EVM
- addresses-historical Actions
- Get Address Balance UTXOs
- List Confirmed Transactions By Address EVM history
- List Confirmed Transactions By Address UTXO Historical
- List Unspent Transaction Outputs By Address UTXOs
- Sync Address
- List Synced Addresses
- Get Synced Address Tokens Transfer EVM
- Activate Synced Address
- Delete Synced Address
- List Synced Address Internal Transactions EVM
- List Tokens By Address Synced EVM
- blockchain-events Actions
- New Confirmed Coins Transactions
- New Unconfirmed Coins Transactions
- New Confirmed Tokens Transactions
- New Confirmed Coins Transactions And Each Confirmation
- New Confirmed Tokens Transactions And Each Confirmation
- Mined Transaction
- New Block
- List Blockchain Events Subscriptions
- Get Blockchain Event Subscription Details By Reference ID
- Delete Blockchain Event Subscription
- Activate Blockchain Event Subscription
- New Confirmed Internal Transactions
- New Confirmed Internal Transactions And Each Confirmation
- Crypto Transactions Actions
- Get Transaction Details By Transaction Hash Solana
- Get Transaction Details By Transaction Id Kaspa
- Get Transaction Details By Transaction Hash EVM
- Get Transaction Details By Transaction Hash UTXOs
- Get Transaction Details By Transaction Hash XRP
- List Internal Transaction Details by Transaction Hash EVM
- List Tokens Transfers By Transaction Hash EVM
- List Logs By Transaction Hash EVM
- Get Raw Transaction Data UTXOs
- contracts Actions
- blockchain-fees Actions
- broadcast-transactions Actions
- prepare-transactions Actions
- Market Data & Prices Actions
Overview
This node interacts with a Crypto APIs REST API to list synced Ethereum Virtual Machine (EVM) addresses derived from an HD Wallet's extended public key. It fetches addresses that have been previously synchronized on the blockchain, supporting pagination and filtering options.
Common scenarios include:
- Retrieving all known EVM addresses generated from a hierarchical deterministic wallet for auditing or monitoring.
- Integrating wallet address data into workflows for balance checks, transaction history retrieval, or further blockchain analysis.
- Managing large wallets by paginating through addresses using limit and offset parameters.
Example: A user wants to list the first 10 synced addresses on the Ethereum mainnet for a given extended public key to verify which addresses have activity.
Properties
| Name | Meaning |
|---|---|
| blockchain | The blockchain network to query (e.g., Ethereum, Binance Smart Chain). |
| extendedPublicKey | The extended public key (xpub) of the HD Wallet to list synced addresses from. |
| network | The specific network within the blockchain (e.g., mainnet, testnet). |
| context | Optional context string to correlate requests or responses. |
| addressFormat | Format of the returned addresses; options are "standard" or "base58". |
| isChangeAddress | Boolean flag to filter addresses that are change addresses in the wallet derivation path. |
| limit | Number to limit how many addresses to return (pagination). |
| offset | Number to offset the starting point of the returned addresses (pagination). |
Output
The output is a JSON array where each item represents a synced EVM address with its associated details as returned by the Crypto APIs service. The exact structure depends on the API response but typically includes fields such as the address string, derivation path, and possibly metadata about synchronization status.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Crypto APIs REST API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- Uses a local OpenAPI specification file (
2024-12-12-final.json) bundled with the node for operation definitions.
Troubleshooting
- Operation not found error: If the specified operation cannot be found, ensure the operation name matches exactly and the bundled OpenAPI spec file is present and uncorrupted.
- Invalid or missing parameters: Required parameters like
blockchain,extendedPublicKey, andnetworkmust be provided; otherwise, the API call will fail. - API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Pagination issues: Using incorrect
limitoroffsetvalues may result in empty results or repeated data; adjust these carefully. - Network connectivity: Ensure the node can reach the Crypto APIs endpoint without firewall or proxy issues.