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 enables users to create, sign, and optionally broadcast a "Lease DCC" transaction on the DecentralChain (DCC) blockchain network. Leasing DCC tokens allows users to lease their tokens to another address, typically to support network operations such as staking or earning rewards.
Common scenarios for this node include:
- Leasing DCC tokens to a validator or node operator to participate in network consensus.
- Temporarily delegating token control without transferring ownership.
- Automating leasing transactions within workflows for DeFi or staking applications.
Example use case:
- A user wants to lease 100 DCC tokens (expressed in smallest units) to a specific recipient address to earn network rewards. They provide their seed phrase or private key to sign the transaction and optionally broadcast it immediately.
Properties
| Name | Meaning |
|---|---|
| Base URL | The base URL of the DCC node API to send requests to if no credential is supplied. |
| Authentication Method | How to sign the transaction: 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 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. |
| Amount to Lease | Amount of DCC tokens to lease, specified in the smallest units (e.g., satoshis). |
Output
The node outputs a JSON object containing details about the created lease transaction and, if auto-broadcast is enabled, the result of broadcasting it to the network.
Output fields include:
transaction: The full transaction object with properties such as transaction ID, type, version, proofs, and signature presence.broadcastResult(optional): The response from the network after broadcasting the transaction.status: Indicates whether the transaction was just created (created), successfully broadcast (broadcasted), or if broadcasting failed (broadcast_failed).debug: Contains metadata useful for troubleshooting, including operation name, chain ID, authentication method, base URL, transaction ID, timestamp, and broadcast success flag.
If the transaction is unsigned, the output notes that the transaction is created but not signed or broadcast.
No binary data output is produced by this operation.
Dependencies
- Requires access to a DecentralChain node API endpoint (Base URL).
- Uses an external library for transaction creation and signing (
@decentralchain/waves-transactionsor compatible). - Requires either a seed phrase or private key credential for signing unless creating an unsigned transaction.
- Optional: network connectivity to broadcast the transaction if auto broadcast is enabled.
Troubleshooting
- Library Loading Failure: If the external transaction library fails to load, the node falls back to mock functions and logs errors. This will prevent actual transaction creation and broadcasting.
- Invalid Attachment: Although not relevant for lease operation, other transaction types validate attachment size and base58 encoding; similar validation errors may occur if inputs are malformed.
- Broadcast Failures: Errors during broadcasting (e.g., network issues, invalid transaction) are caught and included in the output under
broadcastError. Users should verify network connectivity and transaction validity. - Missing Required Parameters: The node requires recipient address and amount for lease operation; missing these will cause errors.
- Authentication Issues: Using incorrect or missing seed phrase/private key will cause signing failures.
- Unsigned Transactions: When creating unsigned transactions, the sender public key must be provided; otherwise, transaction creation will fail.
Links and References
- DecentralChain Official Documentation
- Waves Transactions Library (used for DCC)
- Base58 Encoding Reference
This summary focuses exclusively on the "Transaction" resource with the "Lease DCC" operation as requested.