dcc

n8n community nodes for interacting with DecentralChain (DCC) node REST API (accounts, tokens, transactions, utilities).

Package Information

Released: 9/17/2025
Downloads: 67 weekly / 224 monthly
Latest Version: 0.2.8
Author: elwizard

Available Nodes

Example Node
Basic Example Node
HttpBin icon
HttpBin
Interact with HttpBin API
DecentralChain (DCC) icon
DecentralChain (DCC)
Create, sign and broadcast DecentralChain transactions, plus query blockchain data

Documentation

Banner image

DCC Node Api Connector for N8N

npm version CI npm downloads license: MIT

Production readiness: early 0.x; expect breaking changes until 1.0. Follow semver guidance below.

The DCC Node REST API offers the ability to read blockchain data such as account data, token data, active leases, blocks, transactions, and other data including feature activation status and block reward voting status. It also provides transaction management functions like broadcasting signed transactions, pre-validating and checking transaction status. Additionally, it offers utilities for generating addresses from public keys, validating addresses, generating random seeds, calculating hashes, and more.

With this N8N you will be able to connect the DCC node api to your workflows, automate blockchain tasks or trigger wallet creations and more.

Installation

Install the community package in your n8n instance (requires enabling Community Nodes):

npm install n8n-nodes-dcc

Restart n8n after installation so it loads the new node bundle.

Enabling Community Nodes (if not already)

  1. In n8n UI go to Settings > Community Nodes.
  2. Enable the feature (confirm the security notice).
  3. Add this package name n8n-nodes-dcc if using the in-app installer or install via CLI as above.

Updating

npm update n8n-nodes-dcc

Check changelog and commit history for potential breaking changes (0.x minor bumps may be breaking until 1.0.0).

Semantic Versioning

This project follows Semantic Versioning principles; however while in 0.x the API surface (parameters, field names) may change in minor releases. Once 1.0.0 is reached:

  • MAJOR: Breaking changes to node description/fields/behavior.
  • MINOR: Backwards-compatible features (new resources / operations / optional fields).
  • PATCH: Backwards-compatible bug fixes and internal maintenance.

Pin exact versions in mission‑critical environments to avoid unexpected changes.

Releasing Manually

  1. Update CHANGELOG.md with changes.
  2. Bump version in package.json following SemVer guidance.
  3. Commit: chore(release): vX.Y.Z.
  4. Tag: git tag -a vX.Y.Z -m "vX.Y.Z" then git push --tags.
  5. Release workflow (after added) publishes on matching tag.

See detailed steps in CONTRIBUTING.md.

Features / Operations

Resources supported:

  • Account
    • Get Account: Retrieve balance & basic account info
  • Token
    • Get Token: Retrieve token / asset metadata
  • Transaction
    • List Transactions: Paginated list for an address (limit & offset)
    • Broadcast Transaction: Broadcast a signed transaction JSON
  • Utility
    • Generate Address: Derive address from a supplied public key
    • Validate Address: Check if an address is valid in the network

Credentials

The node can operate with or without credentials. Create a credential of type DccApi if you want to centrally manage the Base URL and/or include a bearer token for authenticated endpoints (future expansion).

Credential fields:

Field Description
Base URL Optional override of default public node endpoint
Token Bearer token (if your node requires auth)

If no credential is supplied, the node uses the Base URL parameter on the node itself.

Usage Examples

1. Get Account

  1. Add the DCC node.
  2. Select Resource = Account, Operation = Get Account.
  3. Enter the account Address.
  4. Execute to receive balances and other basic data.

2. List Transactions

  1. Resource = Transaction, Operation = List Transactions.
  2. Provide Owner Address, adjust Limit & Offset as needed.
  3. Execute to return an array of transactions.

3. Broadcast Transaction

  1. Resource = Transaction, Operation = Broadcast Transaction.
  2. Paste the signed transaction JSON into the Signed Transaction JSON field.
  3. Execute; response includes success status or validation errors.

4. Generate Address

  1. Resource = Utility, Operation = Generate Address.
  2. Provide a Public Key.
  3. Execute to get derived address.

5. Validate Address

  1. Resource = Utility, Operation = Validate Address.
  2. Provide the address string.
  3. Execute to get validation result.

Development / Build

Install dependencies and build:

npm install
npm run build
npm run check:dist

Lint & format:

npm run lint
npm run lintfix
npm run format

Project Health

Prerequisites

You need the following installed on your development machine:

  • Node API Key, you can get this by running your own node or renting an API from someone else in the network.

More information

Refer to our documentation to get more background on how the DCC node works: DecentralChain Documentation

Contributing

Issues & PRs welcome. Please open security-related issues with the SECURITY prefix (see Security Policy).

License

MIT

Discussion