DecentralChain (DCC) icon

DecentralChain (DCC)

Create, sign and broadcast DecentralChain transactions, plus query blockchain data

Actions25

Overview

The node enables 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, 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 issuance dynamically.
  • Developers automating token reissuance as part of smart contract workflows or administrative tools.

For example, a user can specify the asset ID of a token they previously issued and request to mint more units, choosing whether to sign the transaction with a seed phrase, private key, or create an unsigned transaction for external signing.

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 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 create the transaction for: Mainnet (?) or Testnet (!).
Auto Broadcast Whether to automatically broadcast the signed transaction to the network after creation.

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 (if auto broadcast is enabled and successful): The response from the network after broadcasting the transaction.
  • status: Indicates the state of the transaction, e.g., "created", "broadcasted", or "broadcast_failed".
  • broadcastError (if broadcasting fails): Error message describing why broadcasting failed.
  • debug: Detailed debug information including operation name, chain ID, authentication method, base URL, transaction ID, timestamp, and transaction metadata.

If the transaction is unsigned, the output indicates that the transaction was created but not signed or broadcasted.

Dependencies

  • Requires the @decentralchain/waves-transactions library (or compatible) for transaction creation and signing.
  • Optionally requires access to a DecentralChain node API endpoint (specified by Base URL or credentials).
  • If auto broadcasting is enabled, the node must have network access to send HTTP requests to the blockchain node.
  • Requires either a seed phrase or private key credential for signing unless creating unsigned transactions.

Troubleshooting

  • Library Loading Failure: If the underlying transaction library fails to load, the node falls back to mock functions which do not perform real operations. Ensure the @decentralchain/waves-transactions package is installed and accessible in the n8n environment.
  • Missing Credentials: Errors occur if required signing credentials (seed phrase or private key) are missing when needed. Provide valid credentials or choose unsigned mode.
  • Broadcast Failures: Network issues or invalid transaction data may cause broadcasting errors. Check the error messages returned in broadcastError and verify network connectivity and transaction parameters.
  • Invalid Chain ID: Using an incorrect chain ID may result in rejected transactions. Confirm the correct network identifier (? for mainnet, ! for testnet).
  • Unsigned Transactions: When creating unsigned transactions, ensure the sender public key is provided; otherwise, transaction creation will fail.

Links and References

Discussion