DecentralChain (DCC)
Actions36
- Account Actions
- Matcher Actions
- Token/Asset Actions
- Transaction Actions
- Utility Actions
Overview
The node facilitates creating, signing, and optionally broadcasting DecentralChain blockchain transactions specifically for the "Reissue Tokens" operation under the "Transaction" resource. This operation allows users to mint additional tokens of an existing asset on the DecentralChain network, effectively increasing its total supply.
Typical use cases include:
- Token issuers who want to increase the circulating supply of their token.
- Projects managing token economics by controlling token reissuance.
- Automated workflows that adjust token supplies based on external triggers or conditions.
For example, a user can configure this node to reissue 1,000,000 units of a specific token on the mainnet, signed with their seed phrase, and automatically broadcast the transaction to the blockchain.
Properties
| Name | Meaning |
|---|---|
| Base URL | The base API endpoint URL to connect to the DecentralChain node if no credential is supplied. |
| Authentication Method | How the transaction will be signed: Seed Phrase, Private Key, or create an 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 to specify Mainnet ("?") or Testnet ("!"). |
| Auto Broadcast | Whether to automatically broadcast the signed transaction after creation (only applicable for signed tx). |
Output
The node outputs a JSON object containing:
transaction: The created transaction object including details such as transaction type, version, proofs, signature presence, and transaction ID.broadcastResult(optional): If auto-broadcast is enabled and successful, contains the response from the blockchain node confirming broadcast.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 status.
No binary data output is produced by this operation.
Dependencies
- Requires access to a DecentralChain node API endpoint (configurable via Base URL or credentials).
- Uses an external library for transaction creation and signing (
@decentralchain/waves-transactionsor fallback mocks). - Requires either a seed phrase or private key credential for signing unless creating unsigned transactions.
- Optional automatic broadcasting depends on network connectivity to the specified node URL.
Troubleshooting
- Library Loading Failure: If the transaction library fails to load at runtime, the node falls back to mock functions which do not perform real blockchain operations. Ensure the required library is installed and accessible in the n8n environment.
- Invalid Attachment Errors: Attachments must be valid base58 strings or UTF-8 text within size limits (max 140 bytes). Invalid attachments cause errors.
- Broadcast Failures: Network issues or incorrect node URLs can cause broadcast failures. Check the Base URL and network connectivity.
- Missing Credentials: Signing requires either a seed phrase or private key depending on the selected authentication method. Missing these will cause errors.
- Unsigned Transactions: When creating unsigned transactions, the sender public key must be provided explicitly.
- Error Messages: Common error messages include invalid JSON inputs, attachment validation failures, and HTTP request errors. Review debug output for detailed context.
Links and References
- DecentralChain official documentation: https://docs.decentralchain.io/
- Waves Transactions Library (used internally): https://github.com/wavesplatform/waves-transactions
- Base58 encoding reference: https://en.wikipedia.org/wiki/Base58
This summary focuses exclusively on the "Reissue Tokens" operation under the "Transaction" resource, describing how the node constructs, signs, and optionally broadcasts a token reissuance transaction on the DecentralChain blockchain.