Actions25
- Account Actions
- Token/Asset Actions
- Transaction Actions
- Utility Actions
Overview
This node enables users to create, sign, and optionally broadcast DecentralChain (DCC) blockchain transactions specifically related to leasing DCC tokens. Leasing DCC tokens is a mechanism used to delegate tokens to another address for network rewards without transferring ownership.
Typical use cases include:
- Leasing DCC tokens to a node or validator to earn staking rewards.
- Automating lease transactions as part of a larger workflow managing DCC assets.
- Creating unsigned lease transactions for offline signing or external processing.
For the "Lease DCC" operation, the node constructs a lease transaction specifying the recipient address and amount of DCC to lease, signs it using the chosen authentication method (seed phrase, private key, or unsigned), and can automatically broadcast it to the network.
Properties
| Name | Meaning |
|---|---|
| Base URL | The base API URL to connect to the DecentralChain node if no credential base URL is provided. |
| Authentication Method | How the transaction will be signed: Seed Phrase, Private Key, or Create Unsigned Transaction. |
| Seed Phrase | Secret seed phrase used to sign the transaction (required if auth method is Seed Phrase). |
| Private Key | Private key used to sign the transaction (required if auth method is Private Key). |
| Sender Public Key | Public key of the sender, required when creating an unsigned transaction. |
| Chain ID | Network identifier: Mainnet (?) or Testnet (!). |
| Auto Broadcast | Whether to automatically broadcast the signed transaction after creation (true/false). |
| Recipient Address | Address to which the DCC tokens will be leased (required). |
| Amount to Lease | Amount of DCC to lease in smallest units (required). |
Output
The node outputs a JSON object containing details about the created lease transaction and its status:
transaction: The full lease transaction object including fields like type, version, proofs, signature, and transaction ID.status: Indicates whether the transaction was just created (created) or successfully broadcasted (broadcasted).broadcastResult: Present only if auto broadcasting is enabled and successful; contains the response from the blockchain node.broadcastError: Present if broadcasting failed; contains error message details.debug: Contains metadata such as operation name, chain ID, authentication method, base URL, transaction ID, timestamp, and transaction details (e.g., number of proofs, presence of signature).
If the transaction is unsigned, the output indicates that the transaction is created but not signed or broadcasted.
No binary data output is produced by this operation.
Dependencies
- Requires the
@decentralchain/waves-transactionslibrary 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 (configurable via Base URL or credentials).
- If auto broadcasting is enabled, the node makes HTTP requests to the configured node API to submit transactions.
- Requires either a seed phrase or private key credential for signing unless creating unsigned transactions.
Troubleshooting
- Library Loading Failure: If the
@decentralchain/waves-transactionslibrary fails to load, the node uses mock functions which do not perform real signing or broadcasting. Ensure the library is installed correctly in the n8n environment. - Broadcast Failures: Errors during broadcasting (e.g., network issues, invalid transaction) are captured and returned in the output under
broadcastError. Check the error message and ensure the Base URL is correct and reachable. - Missing Required Parameters: The node requires recipient address and amount for leasing. Missing these will cause transaction creation failure.
- Authentication Issues: Using incorrect or missing seed phrase/private key will prevent signing. For unsigned transactions, the sender public key must be provided.
- Network Mismatch: Ensure the Chain ID matches the intended network (Mainnet or Testnet) to avoid transaction rejection.
- Auto Broadcast Disabled: If auto broadcast is false, the transaction is created but not sent to the network. You must handle broadcasting separately.
Links and References
- DecentralChain Official Node API - API endpoint for broadcasting and querying transactions.
- Waves Transactions Library - Underlying library used for transaction creation and signing (similar usage).
- DecentralChain Documentation - General blockchain documentation and transaction types.
This summary focuses on the "Transaction" resource with the "Lease DCC" operation as requested.