Crypto APIs

Overview

This node operation, Derive And Sync New Change Addresses UTXO under the HD Wallets resource, interacts with a cryptocurrency API to derive new change addresses from an HD wallet and synchronize their Unspent Transaction Outputs (UTXOs). It is useful for blockchain developers or wallet service providers who need to programmatically manage hierarchical deterministic wallets by generating new change addresses and keeping track of their spendable outputs.

Typical use cases include:

• Automatically deriving new change addresses as transactions occur.
• Synchronizing UTXO data to maintain an up-to-date wallet state.
• Integrating wallet management into broader blockchain applications or services.

For example, a developer building a multi-currency wallet could use this node to derive change addresses on-demand and fetch their UTXOs to display available balances or prepare transactions.

Properties

Output

The node outputs a JSON array where each element corresponds to the response from the API call that derives and syncs new change addresses' UTXOs. The exact structure depends on the API response but generally includes:

• Details about newly derived change addresses.
• Their associated UTXOs (unspent transaction outputs), including transaction IDs, output indices, amounts, and confirmations.
• Metadata related to synchronization status.

No binary data output is indicated for this operation.

Dependencies

• Requires an active connection to the Crypto APIs REST API service.
• Needs an API authentication token configured in n8n credentials to authorize requests.
• The node reads a local OpenAPI specification file (2024-12-12-final.json) bundled with the node for operation definitions.
• No other external dependencies are required.

Troubleshooting

• Operation Not Found Error: If the specified operation cannot be found, ensure the operation name matches exactly and the bundled API spec file is present and correctly loaded.
• Missing Required Parameters: The blockchain, extendedPublicKey, and network properties are mandatory. Omitting them will cause errors.
• API Request Failures: Network issues, invalid API keys, or incorrect parameter values can cause request failures. Verify API credentials and parameter correctness.
• Continue On Fail Behavior: If enabled, errors during execution will be returned as JSON error objects instead of stopping the workflow.

Links and References

• Crypto APIs Documentation
• Hierarchical Deterministic Wallets (BIP32)
• UTXO Model Explanation