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 operation derives multiple cryptocurrency wallet addresses from an extended public key (xPub, yPub, zPub) for a specified blockchain. It supports generating both change and receiving addresses based on hierarchical deterministic (HD) wallet standards. This is useful when you want to generate new wallet addresses programmatically without exposing private keys, for example, to monitor incoming payments or manage change outputs in wallets.
Practical examples include:
- Generating a batch of receiving addresses for a Bitcoin wallet using an xPub key.
- Deriving change addresses for Ethereum or other supported blockchains to track change outputs.
- Supporting different address formats like legacy, SegWit, or cash address formats depending on the blockchain.
Properties
| Name | Meaning |
|---|---|
| blockchain | The target blockchain network (e.g., Bitcoin, Ethereum) where addresses will be derived. |
| extendedPublicKey | The extended public key (xPub, yPub, zPub) used as the root for deriving child addresses. |
| network | The network type such as mainnet or testnet for the blockchain. |
| context | Optional additional context string for derivation (usage depends on implementation). |
| addressFormat | The format of the derived addresses. Options include: p2pkh, p2sh, p2wpkh, standard, p2sh-cash, p2pkh-cash, classic, base58. |
| addressesCount | Number of addresses to derive starting from the start index. |
| isChange | Boolean flag indicating whether to derive change addresses (true) or receiving addresses (false). |
| startIndex | The starting index for address derivation (default is usually 0). |
Output
The output is a JSON array containing the derived addresses. Each item typically includes the derived address string and possibly associated metadata such as the index or path used for derivation.
If binary data output is supported, it would represent raw address data or related cryptographic material, but this operation primarily outputs JSON with address strings.
Dependencies
- Requires an API key credential for the Crypto APIs REST API service.
- The node relies on the Crypto APIs backend to perform the actual derivation and address generation.
- No local cryptographic libraries are used directly; all operations are performed via API calls.
- Proper configuration of the API key credential in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or malformed extended public key input can cause errors.
- Unsupported blockchain or network values may result in failed requests.
- Requesting too many addresses at once might hit API limits or timeouts.
- Incorrect address format options for the selected blockchain could lead to invalid addresses.
Error messages:
"Operation ... not found": Indicates the requested operation is not recognized by the node, likely due to misconfiguration.- API errors returned from the Crypto APIs service will be passed through; check the error message for details such as invalid parameters or authentication failures.
Resolutions:
- Verify the extended public key is correct and corresponds to the chosen blockchain.
- Confirm that the blockchain and network parameters match supported values.
- Reduce the number of addresses requested if hitting rate limits.
- Ensure the API key credential is valid and has sufficient permissions.