DecentralChain (DCC) icon

DecentralChain (DCC)

Create, sign and broadcast DecentralChain transactions, plus query blockchain data
Join our community

Actions36

Overview

This node interacts with the DecentralChain (DCC) blockchain network to retrieve detailed information about a specific token or asset. The "Get Token Details" operation fetches comprehensive metadata and status for a given token/asset identifier from a specified DCC node API endpoint.

Typical use cases include:

  • Displaying token details such as name, description, total supply, decimals, and reissuability in blockchain dashboards.
  • Verifying token information before performing transactions or analytics.
  • Integrating token metadata into DeFi applications or wallets that support DCC tokens.

Example: Given an Asset ID, the node queries the DCC blockchain node's REST API to return all relevant details about that token, enabling users to programmatically access token info within their workflows.

Properties

Name Meaning
Base URL The base URL of the DCC node API to query if no credential is supplied. Defaults to https://nodes.decentralchain.io.
Asset ID The unique identifier of the token or asset whose details are to be retrieved.

Output

The output JSON contains the full response from the DCC node API endpoint /assets/details/{assetId}. This typically includes fields such as:

  • Token/Asset ID
  • Name
  • Description
  • Decimals (number of decimal places)
  • Total supply
  • Reissuable flag (whether more tokens can be minted)
  • Other blockchain-specific metadata related to the token

The output may also include debug information such as the operation name, endpoint URL, base URL used, parameters, and timestamp of the request.

No binary data is produced by this operation.

Dependencies

  • Requires access to a DecentralChain node API endpoint (default or custom via Base URL).
  • Optionally uses credentials that provide a base URL override.
  • Uses HTTP GET requests to fetch token details.
  • No external libraries beyond standard n8n helpers and optional blockchain transaction libraries are required for this operation.

Troubleshooting

  • Common issues:

    • Invalid or missing Asset ID will cause the API call to fail or return an error.
    • Incorrect Base URL or network connectivity issues will prevent successful API calls.
    • If the node cannot reach the specified DCC node API, it will throw an HTTP request error.

  • Error messages:

    • Errors from the DCC node API (e.g., 404 Not Found if the asset does not exist).
    • Network errors indicating inability to connect to the Base URL.
    • JSON parsing errors if the response is malformed (unlikely but possible).

  • Resolutions:

    • Verify the Asset ID is correct and exists on the queried blockchain network.
    • Confirm the Base URL is reachable and points to a valid DCC node.
    • Check network/firewall settings to allow outbound HTTP requests.
    • Use the debug output included in the node response to diagnose endpoint URLs and parameters.

Links and References

Note: This summary focuses exclusively on the "Get Token Details" operation under the "Token/Asset" resource as requested.

Discussion