Crypto APIs

Overview

This node operation "List Unspent Transaction Outputs By Address UTXOs" under the resource "addresses-historical" interacts with a cryptocurrency API to retrieve unspent transaction outputs (UTXOs) for a specified blockchain address. UTXOs represent the amount of digital currency available to be spent from that address, which is crucial for wallet balance calculations and transaction creation.

Common scenarios where this node is beneficial include:

• Wallet applications needing to display spendable balances.
• Blockchain explorers showing detailed address activity.
• Automated systems preparing transactions by selecting UTXOs.
• Auditing tools verifying funds availability on specific addresses.

For example, a user can input a Bitcoin address on the mainnet and get a list of all unspent outputs, including amounts and transaction references, enabling them to build new transactions or analyze funds flow.

Properties

Output

The output is a JSON array where each element represents an unspent transaction output associated with the specified address. Each UTXO typically includes details such as:

• Transaction ID referencing the original transaction.
• Output index within the transaction.
• Amount/value available to spend.
• Possibly other metadata like script type or confirmations.

If the node supports binary data output, it would relate to raw transaction or blockchain data, but in this operation, the focus is on JSON-formatted UTXO data.

Dependencies

• Requires an active connection to a Crypto APIs REST service.
• Needs an API key credential configured in n8n for authentication.
• Relies on the external Crypto APIs endpoint corresponding to the selected blockchain and network.
• Uses internal helper functions to perform HTTP requests to the API.

Troubleshooting

• Common issues:

  • Invalid or missing blockchain/network/address parameters will cause errors.
  • Network connectivity problems or invalid API credentials will prevent successful API calls.
  • Exceeding rate limits imposed by the external API may result in throttling errors.

• Error messages:

  • "Operation ... not found" indicates a misconfiguration or unsupported operation name.
  • API response errors usually contain descriptive messages; ensure parameters are correct.
  • If the node returns { error: "..." } in output, check the message for guidance.

• Resolutions:

  • Verify all required parameters are correctly set.
  • Confirm API credentials are valid and have necessary permissions.
  • Check network access and retry after some time if rate limited.

Links and References

• Crypto APIs Documentation
• Understanding UTXOs
• n8n Documentation