DecentralChain (DCC) icon

DecentralChain (DCC)

Create, sign and broadcast DecentralChain transactions, plus query blockchain data

Overview

This node interacts with the DecentralChain (DCC) blockchain network, providing various blockchain-related operations. Specifically, for the Utility resource and Generate Address operation, it generates a blockchain address derived from a given public key.

This is useful in scenarios where you have a public key and need to obtain the corresponding DCC address without performing manual derivation or using external tools. For example, when integrating wallet functionality or verifying addresses programmatically, this node can generate the address directly from the public key.

Properties

Name Meaning
Base URL The base URL of the DecentralChain node API to use if no credential is supplied. Defaults to https://nodes.decentralchain.io.
Public Key The public key string from which the blockchain address will be derived.

Output

The output JSON contains the generated address information returned by the DecentralChain API endpoint /addresses/publicKey/{publicKey}. This typically includes the derived address corresponding to the provided public key.

Example output structure (simplified):

{
  "address": "DCC1q2w3e4r5t6y7u8i9o0p...",
  "publicKey": "base58encodedPublicKeyString",
  // possibly other metadata fields depending on API response
}

No binary data output is produced by this operation.

Dependencies

  • Requires access to a DecentralChain node API endpoint, either via:
    • A configured API credential providing a base URL, or
    • The manually specified Base URL property.
  • The node uses HTTP requests to communicate with the DecentralChain API.
  • No additional external services or environment variables are required beyond network access to the specified base URL.

Troubleshooting

  • Common issues:

    • Incorrect or malformed public key input may cause the API to return errors or invalid responses.
    • Network connectivity problems or incorrect Base URL settings can lead to request failures.
    • If credentials are used but misconfigured, the node might fallback to the Base URL property or fail to authenticate.
  • Error messages:

    • Errors from the API such as "Invalid public key" or "Address generation failed" indicate input issues.
    • HTTP request errors like timeouts or connection refused suggest network or endpoint configuration problems.
    • The node returns error details in the output JSON under an error field if execution fails and "Continue On Fail" is enabled.
  • Resolution tips:

    • Verify the public key format and correctness before running the node.
    • Ensure the Base URL points to a valid and accessible DecentralChain node API.
    • Check network connectivity and firewall settings.
    • Use the "Continue On Fail" option to handle errors gracefully during workflow execution.

Links and References


This summary is based solely on static analysis of the provided source code and property definitions.

Discussion