DecentralChain (DCC)

Overview

This node interacts with the DecentralChain (DCC) blockchain to retrieve information about multiple tokens/assets. Specifically, the "Get Multiple Tokens" operation fetches details for a list of token IDs from the blockchain via an HTTP API.

This operation is useful when you need to obtain metadata or status information about several tokens at once, such as their names, descriptions, total supply, decimals, and other on-chain attributes. For example, a user might want to display detailed info about a portfolio of tokens held by an account or verify token properties before performing transactions.

Practical examples:

• Fetching details of multiple tokens to show in a dashboard.
• Validating token information before issuing or transferring tokens.
• Aggregating token data for reporting or analytics.

Properties

Output

The output JSON contains the response from the DecentralChain API for multiple token details. It typically includes an array or object with detailed information about each requested token ID, such as:

• Token identifiers
• Names and descriptions
• Supply and decimal precision
• Other blockchain-specific metadata

The exact structure depends on the DecentralChain API response but generally provides comprehensive token asset data.

No binary data output is produced by this operation.

Dependencies

• Requires access to a DecentralChain node API endpoint, either specified by the "Base URL" property or provided via credentials.
• Uses standard HTTP requests to query the /assets/details endpoint with multiple token IDs.
• No additional external libraries beyond those bundled with the node are required for this operation.

Troubleshooting

• Common issues:

  • Invalid or unreachable Base URL: Ensure the API endpoint is correct and accessible.
  • Malformed token ID list: The token IDs must be comma-separated strings without extra spaces.
  • API rate limits or downtime: The DecentralChain node may throttle or reject requests if overloaded.

• Error messages:

  • Network errors or timeouts indicate connectivity problems; verify network and endpoint availability.
  • API error responses will be returned in the JSON output under an error field.
  • If the node fails to load the underlying blockchain transaction library, it falls back to mock functions but this does not affect read-only operations like fetching token details.

• Resolution tips:

  • Double-check the Base URL and token ID formatting.
  • Use valid token IDs known to exist on the blockchain.
  • Enable "Continue On Fail" in the node settings to handle intermittent failures gracefully.

Links and References

• DecentralChain official node API documentation (for /assets/details endpoint):
  https://docs.decentralchain.io/api/#get-assets-details
• General DecentralChain blockchain info:
  https://decentralchain.io/
• n8n documentation on creating custom nodes and using HTTP request helpers:
  https://docs.n8n.io/

This summary focuses exclusively on the "Token/Asset" resource and the "Get Multiple Tokens" operation as requested.