DecentralChain (DCC)

Create, sign and broadcast DecentralChain transactions, plus query blockchain data

Actions25

Overview

The node facilitates creating, signing, and optionally broadcasting DecentralChain blockchain transactions specifically for the Token Sponsorship operation under the Transaction resource. Token Sponsorship allows enabling or disabling fee sponsorship for a token, which means that transaction fees can be paid by the token issuer instead of the user.

This node is useful in scenarios where users want to manage token sponsorship settings programmatically within an n8n workflow, such as automating token management tasks or integrating with other systems that require dynamic control over token sponsorship status.

Example use cases:

Automatically enable sponsorship for newly issued tokens.
Disable sponsorship for tokens based on business logic or external triggers.
Integrate token sponsorship changes into broader blockchain asset management workflows.

Properties

Name	Meaning
Base URL	The base API endpoint URL to connect to the DecentralChain node if no credential is supplied. Defaults to `https://nodes.decentralchain.io`.
Authentication Method	How the transaction will be signed. Options: Seed Phrase, Private Key, or Create Unsigned Transaction.
Seed Phrase	Secret seed phrase used to sign the transaction (required if using Seed Phrase authentication).
Private Key	Private key used to sign the transaction (required if using Private Key authentication).
Sender Public Key	Public key of the sender, required when creating unsigned transactions.
Chain ID	Network identifier to create the transaction for. Options: Mainnet (`?`) or Testnet (`!`).
Auto Broadcast	Whether to automatically broadcast the transaction after signing. Only applicable if signing with Seed Phrase or Private Key.

Output

The node outputs a JSON object containing:

transaction: The created transaction object including its details such as type, version, proofs, signature presence, and transaction ID.
broadcastResult (optional): If auto-broadcasting is enabled and successful, this contains the response from the blockchain node confirming broadcast.
status: Indicates whether the transaction was just created (created), successfully broadcasted (broadcasted), or if broadcasting failed (broadcast_failed).
broadcastError (optional): Error message if broadcasting failed.
debug: Detailed debug information including operation name, chain ID, authentication method, base URL, transaction ID, timestamp, and broadcast success flag.

If the transaction is created unsigned, the output notes that auto-broadcast is disabled and no signature is present.

Dependencies

Requires the @decentralchain/waves-transactions library for transaction creation and signing. The node attempts to load this library at runtime and falls back to mock functions if unavailable.
Requires access to a DecentralChain node API endpoint, either via credentials or the specified Base URL.
For signing transactions, requires either a valid seed phrase or private key depending on the chosen authentication method.
Network selection (Mainnet or Testnet) must be specified via Chain ID.

Troubleshooting

Library Loading Failure: If the @decentralchain/waves-transactions library fails to load, the node uses mock functions which do not perform real transactions. Ensure the library is installed correctly in the n8n environment.
Broadcast Failures: Errors during broadcasting usually indicate network issues, invalid transaction data, or incorrect credentials. Check the error message in broadcastError for details.
Missing Signing Credentials: If the authentication method is set to Seed Phrase or Private Key but the corresponding input is empty or invalid, transaction creation will fail.
Unsigned Transactions: When creating unsigned transactions, ensure the Sender Public Key is provided; otherwise, transaction creation will fail.
Incorrect Chain ID: Using the wrong Chain ID may cause transactions to be rejected by the network.