Skip to main content

Token Policy

Document type: Token policy
Doc ID: TOKEN-POLICY
Status: Final v0.1
Release date: December 21, 2025
Author: Nicolas Turcotte, Founder
Source repo: dcorps-docs-public (docs/token/TOKEN-POLICY.md)
Last updated: 2026-01-25

Scope: Purpose, allowed uses, and constraints for the DCHUB token, consistent with the public disclaimers. This document is not an offer or solicitation of any kind.

1. Purpose and nature of DCHUB

DCHUB is the native token of the dCorps Hub. It is intended to serve as:

  • the gas token for transactions on the Hub;
  • a governance token for on-chain decision-making;
  • a token for protocol-level fees (entity registration, module registry actions, anchoring).

DCHUB is not:

  • equity or shares in any corporation or nonprofit;
  • a right to dividends, profits, or residual assets;
  • a guarantee of price appreciation or investment performance.

Any sale, distribution, or other transfer of DCHUB that might have legal implications is handled under separate, dedicated documentation and terms.

2. Utility and use cases

DCHUB’s intended uses include:

  • paying transaction fees on the Hub;
  • participating in protocol governance; and
  • paying protocol-level fees where applicable.

Governance may introduce additional protocol-level uses consistent with this policy, but should avoid overloading DCHUB with functions that create confusion about its nature.

Applications and services may accept DCHUB for their own purposes, but such uses are outside the scope of this policy and are the responsibility of those applications.

3. Supply and monetary policy

This policy provides high-level guidance; detailed figures and schedules are defined in:

v1 supply stance (as described in docs/whitepaper/WHITEPAPER_LONG.md, section 10):

  • DCHUB has a fixed hard-cap total supply minted at genesis.
  • There is no discretionary inflation path intended to create additional DCHUB beyond what was created at genesis.
  • “Emissions” refers to tokens entering circulation from predefined allocations (for example the protocol operations pool), not supply creation beyond the fixed cap.

Any changes to supply-related mechanics (for example release caps or rewards distribution parameters) should be debated transparently, enacted via on-chain governance, and documented in the whitepaper and related policy artifacts.

4. Governance over token parameters

On-chain governance may control:

  • protocol operations distribution schedules and related parameters, within predefined bounds;
  • community program release caps and related guardrails;
  • fee routing and treasury share parameters;
  • distribution mechanisms for community or ecosystem allocations.

High-impact changes (e.g. major shifts in emissions schedules, release caps, or supply availability) should:

  • have stronger approval thresholds and longer voting periods;
  • be accompanied by analysis, scenarios, and stress tests;
  • be recorded in governance proposal metadata with clear rationale.

Governance may not retroactively change the terms of any legal agreements or contracts under which DCHUB has already been sold or granted; those remain governed by their own documentation.

This policy:

  • does not constitute legal, tax, or investment advice;
  • does not create any entitlement to tokens or rights for any person;
  • is subject to change as legal guidance and regulatory landscapes evolve.

Participants are responsible for:

  • understanding and complying with laws in relevant jurisdictions;
  • obtaining professional advice where appropriate;
  • making their own risk assessments when acquiring, holding, or using DCHUB.