DecentralChain (DCC)Install

Overview

This node enables creating, signing, and optionally broadcasting various types of DecentralChain (DCC) blockchain transactions. It supports multiple transaction operations such as transferring tokens, issuing new tokens, burning tokens, leasing, alias creation, storing key-value data on the blockchain, and more.

The "Store Data" operation under the "Transaction" resource specifically allows users to store arbitrary key-value data on the DecentralChain blockchain by creating a data transaction. This is useful for embedding metadata or small pieces of information immutably on-chain.

Common scenarios where this node is beneficial include:

• Recording audit trails or logs on the blockchain.
• Storing configuration or state data that must be tamper-proof.
• Embedding application-specific metadata linked to blockchain addresses or assets.

Practical example:

• A supply chain app stores shipment status updates as key-value pairs on-chain using the "Store Data" transaction.
• An identity system records user attributes or verifications immutably via data transactions.

Properties

Output

The node outputs JSON objects representing the created transaction and optionally the broadcast result.

• If the transaction is successfully created (and optionally broadcasted), the output includes:

  • transaction: The full transaction object with details like type, version, proofs, signature, and transaction ID.
  • broadcastResult (if auto broadcast enabled): The response from the network after broadcasting.
  • status: Indicates whether the transaction was just created or broadcasted.
  • debug: Contains metadata about the operation, chain ID, authentication method, timestamps, and transaction details for troubleshooting.

• If broadcasting fails, the output contains:

  • broadcastError: Error message describing the failure.
  • status: Set to "broadcast_failed".
  • debug: Includes error details and stack trace snippet.

• If transaction creation fails, the output contains an error field with a descriptive message.

No binary data output is produced by this node.

Dependencies

• Requires access to a DecentralChain node API endpoint (configurable via Base URL or credentials).
• Uses an external library for transaction creation and signing (@decentralchain/waves-transactions or compatible).
• Requires either a seed phrase or private key credential for signing transactions unless creating unsigned transactions.
• Optional automatic broadcasting requires network connectivity to the specified node API.

Troubleshooting

• Library Loading Failure: If the transaction library fails to load at runtime, the node falls back to mock functions which do not perform real transactions. Ensure the library is installed correctly in the n8n environment.
• Invalid Attachment: Attachments must be valid base58 strings or UTF-8 text under 140 bytes. Errors will indicate invalid base58 or size exceeded.
• Missing Credentials: Signing requires either a seed phrase or private key depending on the selected authentication method. Missing these will cause errors.
• Broadcast Failures: Network issues or node API errors during broadcasting will produce detailed error messages. Check node URL, network connectivity, and API permissions.
• Unsigned Transactions: When creating unsigned transactions, the sender public key must be provided explicitly.
• JSON Parsing Errors: For some operations requiring raw JSON input, invalid JSON will cause errors.

Links and References

• DecentralChain Documentation
• Waves Transactions Library (compatible)
• Base58 Encoding Reference

This summary focuses on the "Transaction" resource and the "Store Data" operation context, describing how the node creates and manages data transactions on the DecentralChain blockchain.