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 "Derive And Sync New Receiving Addresses XRP" under the "HD Wallets" resource interacts with a Crypto APIs REST API to derive and synchronize new receiving addresses specifically for the XRP blockchain. It is useful in scenarios where users manage hierarchical deterministic (HD) wallets and need to programmatically generate fresh receiving addresses for XRP, ensuring wallet address management is automated and synchronized with the blockchain state.
Practical examples include:
- Automatically generating new XRP receiving addresses for user wallets in a crypto exchange or wallet service.
- Synchronizing wallet addresses after importing an extended public key to keep track of all derived addresses.
- Managing multiple XRP accounts by deriving addresses on demand without exposing private keys.
Properties
| Name | Meaning |
|---|---|
| blockchain | The blockchain network to use; here it should be set to the XRP blockchain identifier. |
| extendedPublicKey | The extended public key (xpub) from which new receiving addresses will be derived. |
| network | The specific XRP network environment (e.g., mainnet, testnet) to operate on. |
| context | Optional string to provide additional context or metadata for the request. |
| JSON Body | A collection of additional parameters to customize the request body sent to the API. |
Output
The node outputs a JSON array where each item corresponds to the result of the API call to derive and sync new XRP receiving addresses. The JSON structure typically includes details about the newly derived addresses, such as their public keys, derivation paths, and synchronization status.
If binary data were involved (not indicated here), it would represent raw data related to addresses or transactions, but this operation focuses on JSON data output.
Dependencies
- Requires an active connection to the Crypto APIs REST API service.
- Needs an API authentication token or API key credential configured in n8n to authorize requests.
- The node reads a local OpenAPI specification file (
2024-12-12-final.json) bundled with the node to map operations and parameters. - Uses internal helper functions to perform HTTP requests to the Crypto APIs endpoints.
Troubleshooting
Common issues:
- Incorrect or missing extended public key can cause failure in deriving addresses.
- Using an unsupported or incorrect blockchain/network value may lead to errors.
- Network connectivity or API authentication failures will prevent successful API calls.
Error messages:
Operation <operationName> not found: Indicates the requested operation is not defined in the API spec or the node configuration; verify the operation name.- API response errors (e.g., unauthorized, bad request) will be returned as error messages in the output JSON if "Continue On Fail" is enabled.
Resolutions:
- Ensure all required properties are correctly set.
- Verify API credentials and network availability.
- Check that the extended public key is valid and corresponds to the specified blockchain and network.