DecentralChain (DCC) icon

DecentralChain (DCC)

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

Overview

This node enables users to create, sign, and optionally broadcast a "Create Alias" transaction on the DecentralChain (DCC) blockchain network. The "Create Alias" operation allows an account to register a human-readable alias (a short alphanumeric name) that can be used as an alternative to the long blockchain address. This simplifies sending and receiving tokens by using easy-to-remember names.

Typical use cases include:

  • Registering a new alias for your DCC address to simplify payments.
  • Automating alias creation in workflows where new accounts are provisioned.
  • Integrating alias creation into broader blockchain automation pipelines.

For example, a user might create an alias "myalias123" linked to their wallet address so others can send tokens to alias:?myalias123 instead of the full address.

Properties

Name Meaning
Base URL The base URL of the DCC node API to connect to 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 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 if creating an unsigned transaction.
Chain ID Network identifier: Mainnet (?) or Testnet (!).
Auto Broadcast Whether to automatically broadcast the signed transaction to the network after signing.
Alias Name The alias string to create (4-30 characters, alphanumeric).

Output

The node outputs a JSON object containing details about the created alias transaction. The output includes:

  • transaction: The transaction object representing the alias creation, including its ID and type.
  • status: Indicates whether the transaction was just created or successfully broadcasted.
  • broadcastResult (if auto-broadcast enabled): The response from the network after broadcasting.
  • debug: Metadata such as operation name, chain ID, authentication method, base URL, transaction ID, timestamp, and transaction signature/proofs info.

If broadcasting fails, the output contains an error message and debug information about the failure.

No binary data is produced by this node.

Dependencies

  • Requires access to a DecentralChain node API endpoint (Base URL).
  • Needs either a seed phrase or private key credential for signing transactions unless creating unsigned transactions.
  • Optionally requires network connectivity to broadcast transactions.
  • Uses the @decentralchain/waves-transactions library (or a compatible fallback) for transaction creation and signing.

Troubleshooting

  • Library Loading Failure: If the underlying transaction library fails to load, the node falls back to mock functions which do not perform real transactions. Ensure the environment has the required dependencies installed.
  • Invalid Alias Name: Alias must be 4-30 alphanumeric characters. Invalid input may cause transaction creation errors.
  • Attachment Size Limits: Although not relevant for alias creation, other operations have attachment size limits (max 140 bytes).
  • Broadcast Failures: Network issues or invalid credentials can cause broadcast errors. Check the error message in output and verify API endpoint and credentials.
  • Unsigned Transactions: When creating unsigned transactions, the sender public key must be provided explicitly.
  • Authentication Method Mismatch: Using the wrong authentication method without providing required keys will cause errors.

Links and References


This summary focuses exclusively on the "Transaction" resource with the "Create Alias" operation as requested.

Discussion