DecentralChain (DCC)Install

Overview

This node interacts with the DecentralChain (DCC) blockchain network to retrieve all token balances for a specified account address. Specifically, the Account - Get All Asset Balances operation fetches the complete list of asset balances held by an account on the DCC blockchain.

This is useful in scenarios where you want to monitor or audit all tokens owned by a particular address, such as portfolio tracking, wallet balance display, or integration with other financial services that require up-to-date asset holdings.

Example use cases:

• A crypto portfolio dashboard fetching all token balances for a user’s wallet.
• Automated reporting tools that summarize all assets held by an account.
• Wallet applications displaying detailed token holdings.

Properties

Output

The output JSON contains the full list of asset balances for the specified account address. The structure corresponds directly to the response from the DecentralChain node's /assets/balance/{address} endpoint.

Typical fields include:

• Asset identifiers
• Balance amounts per asset
• Possibly metadata about each asset balance

The exact structure depends on the blockchain node's API response but generally provides a mapping of asset IDs to their respective balances for the queried address.

No binary data output is involved in 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 property specifying the node URL to query.
• Uses standard HTTP GET requests to the blockchain node.
• No additional external libraries are required specifically for this operation.

Troubleshooting

• Common issues:

  • Incorrect or unreachable Base URL: Ensure the Base URL points to a valid and accessible DecentralChain node.
  • Invalid or malformed account address: The address parameter must be a valid DCC address; otherwise, the API will return an error.
  • Network connectivity problems: Check internet connection and firewall settings.

• Error messages:

  • HTTP errors from the node API (e.g., 404 Not Found, 400 Bad Request) usually indicate invalid parameters or unavailable resources.
  • Timeout or connection refused errors suggest network or node availability issues.

• Resolution tips:

  • Verify the correctness of the account address input.
  • Confirm the Base URL is correct and the node is operational.
  • If using credentials, ensure they are valid and have necessary permissions.

Links and References

• DecentralChain Node API Documentation (for API endpoints and responses)
• DecentralChain Official Website
• Base58 Encoding Reference (used internally for attachments in other operations)

Note: This summary focuses exclusively on the Account - Get All Asset Balances operation as requested.