DecentralChain (DCC)Install

Overview

This node interacts with the DecentralChain (DCC) blockchain to retrieve details for multiple tokens/assets in a single request. It is useful when you need to fetch information about several tokens at once, such as their metadata or status, without making individual calls for each token.

Typical use cases include:

• Displaying detailed information about a list of tokens owned by a user.
• Aggregating token data for portfolio tracking or analytics.
• Batch querying token details before performing further operations like transfers or trades.

For example, if you have a comma-separated list of token IDs, this node can query the blockchain API and return detailed information about all those tokens in one response.

Properties

Output

The output is a JSON array containing the detailed information of the requested tokens. Each item corresponds to a token and includes its properties as returned by the DecentralChain API under the /assets/details endpoint.

The structure typically includes fields such as token ID, name, description, decimals, total supply, reissuable flag, and other metadata related to each token.

No binary data output is produced by this operation.

Example output snippet (simplified):

[
  {
    "id": "tokenId1",
    "name": "Token One",
    "description": "Description of Token One",
    "decimals": 8,
    "totalSupply": "1000000000",
    "reissuable": true,
    ...
  },
  {
    "id": "tokenId2",
    "name": "Token Two",
    "description": "Description of Token Two",
    "decimals": 2,
    "totalSupply": "50000000",
    "reissuable": false,
    ...
  }
]

Dependencies

• Requires access to a DecentralChain node API endpoint, either via a credential or the provided Base URL.
• No special environment variables are needed beyond standard HTTP connectivity.
• Uses internal HTTP request helper from n8n to communicate with the blockchain API.

Troubleshooting

• Invalid or unreachable Base URL: Ensure the Base URL is correct and accessible from your n8n instance. Network issues or incorrect URLs will cause HTTP request failures.
• Malformed token IDs input: The token IDs must be provided as a comma-separated string without extra spaces or invalid characters. Improper formatting may lead to empty or error responses.
• API rate limits or downtime: If the DecentralChain node API is rate-limited or down, requests may fail or timeout. Retry later or switch to a different node endpoint.
• Error messages: Common errors include HTTP 4xx/5xx responses indicating bad requests or server errors. Check the error message details returned in the node output for guidance.

Links and References

• DecentralChain API Documentation — Official API docs for endpoints including /assets/details.
• n8n HTTP Request Node — For understanding how HTTP requests are made within n8n nodes.
• Base58 Encoding Reference — Related to attachment encoding used elsewhere in the node but not directly in this operation.