DecentralChain (DCC)
Actions36
- Account Actions
- Matcher Actions
- Token/Asset Actions
- Transaction Actions
- Utility Actions
Overview
This node provides various operations to interact with the DecentralChain (DCC) blockchain ecosystem. Specifically, for the Utility resource and the Validate Address operation, it validates whether a given blockchain address is correctly formatted according to DCC standards.
This validation is useful in workflows where you need to ensure that user input or external data contains valid DCC addresses before proceeding with transactions or queries. For example, before sending tokens or querying account balances, you can validate the address to avoid errors downstream.
Practical example:
- A workflow receives an address from a form submission and uses this node to verify its validity.
- If the address is invalid, the workflow can halt or notify the user, preventing failed blockchain calls.
Properties
| Name | Meaning |
|---|---|
| Base URL | The base URL of the DCC node API to use if no credential is supplied. Defaults to https://nodes.decentralchain.io. |
| Address to Validate | The blockchain address string that you want to validate for correct format. |
Output
The output JSON contains the response from the DCC node API endpoint /addresses/validate/{address}. This typically includes a boolean or structured result indicating whether the address is valid.
Example output structure (simplified):
{
"valid": true,
"address": "someDccAddress",
"message": "Address is valid"
}
The exact fields depend on the API response but generally confirm the validity status.
No binary data output is produced by 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.
- The node makes HTTP GET requests to the DCC node API.
- No additional external libraries are required specifically for this operation.
Troubleshooting
Common issues:
- Invalid or malformed address strings will cause the API to return invalid status.
- Network connectivity issues to the specified Base URL will cause request failures.
- Missing or incorrect Base URL configuration may lead to connection errors.
Error messages:
- HTTP request errors such as timeouts or DNS failures indicate connectivity problems.
- API error responses may include messages about invalid address format.
Resolutions:
- Verify the address string is correctly formatted before passing it.
- Ensure the Base URL is reachable and correct.
- Configure credentials properly if authentication is required by the node API.
Links and References
- DecentralChain official documentation (for address formats and API):
https://docs.decentralchain.io/ - Base58 encoding reference (used elsewhere in the node):
https://en.wikipedia.org/wiki/Base58 - n8n HTTP Request node documentation (for understanding underlying requests):
https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/