DecentralChain (DCC)

Overview

This node interacts with the DecentralChain (DCC) blockchain to perform various operations including creating, signing, and broadcasting transactions, as well as querying blockchain data. Specifically, for the Utility resource with the Get Aliases operation, it retrieves all aliases associated with a given DCC address.

Use cases include:

• Retrieving all human-readable aliases linked to a blockchain address for easier identification.
• Verifying which aliases belong to an address in wallet management or blockchain explorers.
• Integrating alias information into workflows that require user-friendly address representations.

Example: Given a DCC address, this node fetches all aliases registered to that address, enabling downstream processes to display or use these aliases instead of raw addresses.

Properties

Output

The output JSON contains the list of aliases associated with the specified blockchain address. The structure corresponds directly to the response from the DecentralChain API endpoint /alias/by-address/{address}.

Typical output example (simplified):

{
  "aliases": [
    {
      "alias": "myalias1",
      "address": "3Pxxx...",
      "timestamp": 1234567890
    },
    {
      "alias": "myalias2",
      "address": "3Pxxx...",
      "timestamp": 1234567891
    }
  ]
}

• Each alias object includes the alias name and related metadata.
• The output is provided in the json field of the node's output.
• No binary data is produced by this operation.

Dependencies

• Requires access to a DecentralChain node API endpoint, either via:
  • An API key credential configured in n8n (optional).
  • Or the Base URL parameter specifying the node URL.
• Uses HTTP GET requests to query the blockchain node.
• No additional external libraries are required beyond those bundled with the node.

Troubleshooting

• Common issues:

  • Incorrect or unreachable Base URL or API endpoint will cause HTTP request failures.
  • Providing an invalid or malformed blockchain address will result in errors or empty alias lists.
  • Network connectivity problems can prevent successful API calls.

• Error messages:

  • "Request failed" or similar HTTP errors indicate connectivity or endpoint issues.
  • "Invalid address" or empty results suggest the address has no aliases or is incorrect.

• Resolutions:

  • Verify the Base URL is correct and accessible.
  • Confirm the address format matches DecentralChain address specifications.
  • Check network connectivity and firewall settings.
  • Enable "Continue on Fail" in the node settings to handle errors gracefully in workflows.

Links and References

• DecentralChain official node API documentation (for alias endpoints):
  https://docs.decentralchain.io/api/#alias-by-address
• DecentralChain blockchain overview:
  https://decentralchain.io/
• n8n documentation on HTTP Request usage and credentials:
  https://docs.n8n.io/

This summary focuses exclusively on the Utility > Get Aliases operation as requested, based on static analysis of the provided source code and property definitions.