Actions25
- Account Actions
- Token/Asset Actions
- Transaction Actions
- Utility Actions
Overview
The 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, invoking smart contracts, and more.
This node is beneficial for users who want to automate interactions with the DecentralChain blockchain within their workflows, such as sending payments, managing tokens, or updating blockchain data programmatically.
Practical example:
- Automatically transfer DCC tokens to a recipient address after a trigger event.
- Issue a new token asset with specified supply and properties.
- Store custom key-value data on the blockchain for audit or record-keeping purposes.
- Create unsigned transactions for offline signing scenarios.
Properties
| Name | Meaning |
|---|---|
| Base URL | The base URL of the DecentralChain node API to use if no credential is supplied. Default: https://nodes.decentralchain.io. |
| Authentication Method | How to sign the transaction. Options: Seed Phrase, Private Key, or Create Unsigned Transaction (no signature). |
| Seed Phrase | Secret seed phrase used to sign transactions when "Seed Phrase" authentication is selected. |
| Private Key | Private key used to sign transactions when "Private Key" authentication is selected. |
| Sender Public Key | Public key of the sender, required when creating unsigned transactions. |
| Chain ID | Network identifier for the transaction. Options: Mainnet (?) or 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. |
Additional input properties specific to the Store Data operation (Resource: Transaction, Operation: Store Data) are not explicitly listed in the provided properties JSON snippet, but based on the node's design pattern, this operation would typically require parameters like key-value pairs to store on-chain.
Output
The node outputs an array of JSON objects, each representing the result of processing one input item.
For the Store Data transaction operation, the output JSON includes:
transaction: The created transaction object containing details such as transaction type, version, proofs, and signature presence.status: Indicates whether the transaction was just created (created) or successfully broadcasted (broadcasted).broadcastResult(if auto-broadcast is enabled): The response from the blockchain node after broadcasting the transaction.broadcastError(if broadcasting fails): Error message describing why broadcasting failed.debug: Contains metadata useful for troubleshooting, including operation name, chain ID, authentication method, base URL, transaction ID, timestamp, and transaction details summary.
If the transaction creation fails, the output contains an error field with a descriptive message and debug information.
No binary data output is produced by this node.
Dependencies
- Requires access to a DecentralChain node API endpoint, either via a user-supplied Base URL or credentials that provide this information.
- Uses the external library
@decentralchain/waves-transactions(or compatible) for transaction creation and signing. If this library is unavailable at runtime, the node falls back to mock implementations but will log errors. - Optional: Credentials providing API keys or authentication tokens may be configured in n8n to simplify connection setup.
Troubleshooting
- Library loading failure: If the external transaction library cannot be loaded, the node logs detailed error messages and uses mock functions, which means actual transaction creation will fail. Ensure the library is installed correctly in the n8n environment.
- Transaction creation failure: If required parameters are missing or invalid, the node returns an error indicating failure to create the transaction.
- Broadcasting errors: When auto-broadcast is enabled, network issues or invalid transaction signatures can cause broadcasting to fail. The node outputs detailed error messages and stack traces to help diagnose these problems.
- Unsigned transactions: When creating unsigned transactions, ensure the sender public key is provided; otherwise, transaction creation will fail.
- Incorrect Chain ID: Using the wrong network identifier (
?for mainnet or!for testnet) can cause transactions to be rejected by the network.
Links and References
- DecentralChain Official Node API Documentation (example base URL)
- Waves Transactions Library GitHub (similar library used for transaction creation/signing)
- n8n Documentation - Creating Custom Nodes
Note: This summary focuses on the Transaction > Store Data operation context, but the node supports many other transaction types with similar patterns.