DecentralChain (DCC)

Overview

The node enables creating, signing, and optionally broadcasting DecentralChain (DCC) blockchain transactions, specifically supporting a "Mass Transfer" operation among others. This operation allows sending tokens to multiple recipients in a single transaction, which is efficient for batch payments or distributions.

Typical use cases include:

• Distributing tokens or rewards to many users simultaneously.
• Performing bulk transfers to multiple addresses without creating separate transactions.
• Automating token distribution workflows in decentralized applications or token management systems.

For the "Mass Transfer" operation, the node constructs a mass transfer transaction with specified recipients and amounts, signs it using one of several authentication methods (seed phrase, private key, or unsigned), and can broadcast it to the DCC network automatically if configured.

Properties

Note: For the Mass Transfer operation specifically, additional parameters would be expected (not listed in the provided properties snippet but typically including recipient list and amounts).

Output

The node outputs JSON objects containing:

• transaction: The created transaction object, including details such as transaction type, version, proofs, signature presence, and transaction ID.
• broadcastResult: If auto-broadcasting is enabled and successful, this contains the response from the blockchain network confirming broadcast.
• status: Indicates whether the transaction was just created (created), successfully broadcasted (broadcasted), or if broadcasting failed (broadcast_failed).
• broadcastError: Present only if broadcasting failed, contains error message details.
• debug: Contains metadata useful for troubleshooting, such as operation name, chain ID, authentication method, base URL, timestamps, and transaction details.

If broadcasting is disabled or the transaction is unsigned, the output will reflect that status accordingly.

No binary data output is produced by this node.

Dependencies

• Requires the external library @decentralchain/waves-transactions (or compatible alternative) for transaction creation and signing.
• Needs access to a DecentralChain node API endpoint, configurable via Base URL or credentials.
• Requires an API key credential or similar authentication setup in n8n to access the DecentralChain node API if not using default public nodes.
• Environment must support dynamic loading of the waves-transactions library or fallback to mock implementations (for testing).

Troubleshooting

• Library Loading Failure: If the waves-transactions library fails to load at runtime, the node falls back to mock functions, which means no real transactions can be created or broadcasted. Ensure the library is installed correctly in the environment.
• Broadcast Failures: Errors during broadcasting usually indicate network issues, invalid transaction data, or incorrect authentication. Check the error messages in broadcastError and verify credentials and network connectivity.
• Missing Required Parameters: Transactions require specific fields like seed phrase, private key, or sender public key depending on the authentication method. Omitting these will cause errors.
• Unsigned Transactions: When creating unsigned transactions, the sender's public key must be provided; otherwise, transaction creation will fail.
• Incorrect Chain ID: Using the wrong chain ID for the target network may cause transaction rejection by the blockchain node.
• Auto Broadcast Disabled: If auto broadcast is off, remember to manually broadcast the transaction later; otherwise, it won't be submitted to the network.

Links and References

• DecentralChain Documentation
• Waves Transactions Library GitHub
• n8n Documentation - Creating Custom Nodes