DecentralChain (DCC)
Create, sign and broadcast DecentralChain transactions, plus query blockchain data
Actions36
- Account Actions
- Matcher Actions
- Token/Asset Actions
- Transaction Actions
- Utility Actions
Overview
This node facilitates creating, signing, and optionally broadcasting a Mass Transfer transaction on the DecentralChain (DCC) blockchain. A Mass Transfer allows sending tokens to multiple recipients in a single transaction, which is more efficient than sending individual transfers.
Typical use cases include:
- Distributing tokens or rewards to many users at once.
- Batch payments or payouts in tokenized form.
- Efficiently managing bulk token transfers for projects or organizations.
For example, a project could use this node to send monthly dividends to all token holders or distribute airdrops to a list of addresses.
Properties
| Name | Meaning |
|---|---|
| Base URL | The base URL of the DCC node API to connect to if no credential is supplied. Default: https://nodes.decentralchain.io. |
| Authentication Method | How the transaction will be signed. Options: • Seed Phrase — sign using a secret seed phrase. • Private Key — sign using a private key. • Create Unsigned Transaction — create an unsigned transaction requiring external signing. |
| Seed Phrase | Secret seed phrase used to sign the transaction. Required if "Seed Phrase" authentication method is selected. |
| Private Key | Private key used to sign the transaction. Required if "Private Key" authentication method is selected. |
| Sender Public Key | Public key of the sender. Required if creating an unsigned transaction. |
| Chain ID | Network identifier to create the transaction for. Options: • Mainnet (?) • Testnet (!) |
| Auto Broadcast | Whether to automatically broadcast the signed transaction to the network after creation. Only applicable when using "Seed Phrase" or "Private Key" authentication methods. Defaults to false. |
| Attachment Mode | How to provide an optional attachment with the transaction. Options: • None • Plain Text (UTF-8 text encoded as base58) • Base58 (raw base58-encoded bytes) |
| Attachment Text | Plain text to encode as base58 attachment (max 140 bytes UTF-8). Shown only if Attachment Mode is "Plain Text". |
| Attachment (Base58) | Base58-encoded attachment bytes (max 140 bytes decoded). Shown only if Attachment Mode is "Base58". |
Output
The node outputs JSON objects representing the created transaction and optionally the broadcast result:
transaction: The transaction object created by the underlying library, including fields like transaction ID, type, version, proofs, and signature presence.broadcastResult(if auto broadcast enabled): The response from the blockchain node after broadcasting the transaction, typically containing the transaction ID and status.status: Indicates whether the transaction was just created (created), successfully broadcast (broadcasted), or if broadcasting failed (broadcast_failed).debug: Contains metadata such as operation name, chain ID, authentication method, base URL, timestamps, and details about the transaction structure and broadcast success.
If the transaction is unsigned, the output contains the unsigned transaction data ready for external signing.
No binary data output is produced by this operation.
Dependencies
- Requires access to a DecentralChain node API endpoint (specified by Base URL or credentials).
- Uses an external library for transaction creation and signing (
@decentralchain/waves-transactionsor fallback mocks). - If broadcasting is enabled, requires network connectivity to the specified node.
- For signing, requires either a seed phrase or private key credential, or a sender public key for unsigned transactions.
Troubleshooting
- Library Loading Failure: If the transaction library fails to load at runtime, the node falls back to mock functions that do not perform real signing or broadcasting. This results in mock transaction IDs and no real blockchain interaction. Ensure the required library is installed and accessible in the n8n environment.
- Attachment Errors: Attachments must be valid base58 strings or UTF-8 text under 140 bytes. Invalid attachments cause errors with messages like "Attachment is not valid base58" or "Attachment exceeds 140 bytes".
- Broadcast Failures: If broadcasting fails, the error message from the node is included in the output. Common causes include network issues, invalid credentials, or node API errors. Verify API endpoint accessibility and credentials.
- Missing Required Parameters: The node requires certain parameters depending on the authentication method and operation. For example, unsigned transactions require the sender's public key. Missing these will cause errors.
- Invalid JSON Input: Not applicable for mass transfer but relevant for other operations where raw JSON input is accepted.
Links and References
This summary covers the Mass Transfer operation of the DecentralChain node, focusing on its execute logic, inputs, outputs, dependencies, and common troubleshooting points.