Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node operation "Derive And Sync New Receiving Addresses UTXO" under the "HD Wallets" resource interacts with a blockchain API to derive new receiving addresses from an extended public key (xpub) and synchronize their unspent transaction outputs (UTXOs). It is useful for wallet applications or services that need to generate fresh receiving addresses deterministically from an HD wallet and keep track of their spendable balances on a specified blockchain network.

Typical use cases include:

  • Generating new deposit addresses for users without exposing private keys.
  • Keeping wallet address states updated with current UTXO information for accurate balance and transaction management.
  • Integrating with blockchain explorers or APIs to automate wallet address management in crypto payment systems.

Properties

Name Meaning
blockchain The blockchain network to operate on (e.g., Bitcoin, Litecoin).
extendedPublicKey The extended public key (xpub) from which new receiving addresses will be derived.
network The specific network type (e.g., mainnet, testnet) for the blockchain.
context Optional context string to provide additional metadata or scoping for the request.
JSON Body Additional parameters as a JSON collection to customize the request body if needed.

Output

The output is a JSON array where each item represents data returned by the API about newly derived receiving addresses and their synchronized UTXOs. This typically includes:

  • Address details derived from the extended public key.
  • UTXO information such as transaction IDs, output indices, amounts, and confirmations.
  • Metadata related to the blockchain and network context.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to a blockchain API service that supports HD wallet operations and UTXO synchronization.
  • Needs an API authentication token or API key credential configured in n8n to authorize requests.
  • Relies on the bundled OpenAPI specification file (2024-12-12-final.json) for endpoint definitions and parameter mappings.

Troubleshooting

  • Common issues:

    • Invalid or malformed extended public key may cause errors or empty results.
    • Incorrect blockchain or network values can lead to failed API calls or no data returned.
    • Missing or invalid API credentials will result in authentication errors.
    • Network connectivity problems can cause timeouts or request failures.

  • Error messages:

    • "Operation <operationName> not found": Indicates the requested operation is not defined in the API spec; verify the operation name.
    • API response errors usually contain descriptive messages; check the error field in the output JSON.

  • Resolutions:

    • Validate all input parameters carefully before execution.
    • Ensure API credentials are correctly set up and have necessary permissions.
    • Confirm the blockchain and network names match those supported by the API provider.
    • Use the optional "context" property to scope or debug requests if supported.

Links and References

Discussion