Tokenomics | dCorps Hub

Allocation Table

Initial allocations and unlock rules so anyone can see who receives tokens and when they enter circulation. This table is the official summary used for governance and reporting.

Total supply 1,000,000,000 DCHUB

Supply notes

Fixed hard-cap supply minted at genesis.
Assigned to vesting contracts and governance vaults at genesis.
Emissions are releases from allocations, not new supply.

Community + ecosystem

33%

330,000,000

Caps Annual + quarterly

Releases Governance-controlled

Account Community program vault

Network incentives reserve

18%

180,000,000

Schedule Governance budgets

Recipients Operators + infrastructure providers

Account Network incentives reserve vault

Protocol Treasury

40,000,000

Releases Governance-controlled

Voting Non-voting by default

Account Treasury vault

dCorps foundation

40,000,000

Releases Governance-controlled

Voting Non-voting by default

Policy Release policy required

Account Foundation vault

Liquidity bootstrap

30,000,000

Use Operational liquidity

Policy Disclosure required

Voting Non-voting by default

Account Treasury/liquidity

Investors

15%

150,000,000

Lockups Round-specific lockups*

Vesting Round-specific schedules*

Distribution On-chain vesting account

*shared with authorized investors

Core team + contributors

80,000,000

Cliff 18m

Vesting 48m linear

Distribution On-chain vesting account

Founder

15%

150,000,000

Cliff 24m

Vesting 72m linear after cliff

Distribution On-chain vesting account

Voting Power Balance

Baseline (illustrative) voting-eligible supply over the 96-month issuance window, based on the published vesting schedules and release caps in the token docs. Each band starts from zero so you can compare where each allocation lands by month 96.

0m 6m 12m 18m 24m 30m 36m 42m 48m 54m 60m 66m 72m 78m 84m 90m 96m

Community programs

Security, tooling, jurisdiction pilots, NGO support, ecosystem growth, gas credits (cap envelope).
Network incentives reserve

Governance-budgeted incentives for operators, reliability programs, and infrastructure grants.
Investors

Aggregate of round-based lockups and vesting schedules (includes public sale/ICO if any).
Core team + contributors

18m cliff with linear vesting after cliff.
Founder

24m cliff with linear vesting through month 96.

Calculated from baseline vesting schedules and published release limits. Community is shown as a cap envelope; non-voting governance vaults (Treasury, foundation, liquidity) are excluded.

Supply Stance + Definitions

Explains what the token is used for and what a fixed supply means, so circulation is not confused with new minting. It also defines emissions and makes clear the token is not equity.

Hard-cap total supply 1,000,000,000 DCHUB minted at genesis Assigned to vesting contracts and governance vaults at genesis.

Circulating supply Transferable DCHUB without vesting or governance release constraints Increases via vesting unlocks and governed releases.

Locked vs unlocked Locked = vesting, rewards pool, and governance custody; Unlocked = transferable Locked supply requires time or governance to release.

Emissions definition Tokens entering circulation from predefined allocations Does not create supply beyond the fixed cap.

Community and Ecosystem Programs

This pool funds public goods and ecosystem growth. Governance releases and caps pace spending and keep it transparent with regular reporting.

Allocation details

Allocation

33% (330,000,000)

Cliff

Not applicable; governed releases

Vesting

Not applicable; releases follow annual and quarterly caps

Distribution

Community program vault (governance-controlled)

Sub-buckets / programs

See Program portfolio below for the detailed breakdown.

Voting eligible

Program portfolio

Security and audits

Allocation: 7% (70,000,000)

Audits, monitoring, bug bounties, and incident response tooling.

Core tooling and developer grants

Allocation: 9% (90,000,000)

SDKs, indexers, explorers, accounting tooling, and module development grants.

Jurisdiction pilots and module development

Allocation: 6% (60,000,000)

Adapter pilots, standards work, and jurisdiction module implementation.

NGO onboarding and support

Allocation: 6% (60,000,000)

Onboarding programs, fee waivers, training, and reporting tooling.

Ecosystem growth and incentives

Allocation: 4.95% (49,500,000)

Adoption programs tied to verified usage and ecosystem reliability.

Gas-free onboarding credits

Allocation: 0.05% (500,000) set aside within ecosystem growth

Time-boxed fee grants cover entity onboarding gas at large scale, with per-entity caps, governance approval, and public reporting.

Release and adoption policy

Release caps

Max 50,000,000 per year and 20,000,000 per quarter (rolling window).

Gas-free adoption credits

Set aside 0.05% (500,000) within ecosystem growth allocation; issued as time-boxed fee grants with per-entity caps, governance approval, and public reporting.

Recruiting incentives

Discretionary incentives can be issued by the foundation or designated onboarding operators for high-value entities, under published policy, governance oversight, and reporting.

Targeted airdrops

One-time token distributions to reward verified adoption, with anti-sybil checks and public reporting.

Network incentives reserve

Incentives fund operators, reliability programs, and infrastructure support. The reserve is capped and released only through governance-approved budgets; there is no consensus-emissions program in the Orbit rollup.

Allocation details

Allocation

18% (180,000,000)

Cliff

Not applicable

Vesting

Not applicable; releases follow approved budgets

Distribution

Network incentives reserve vault

Sub-buckets / programs

Operator ops; Infrastructure grants

Governance-controlled

40,000,000

Year 1

35,000,000

Year 2

30,000,000

Year 3

25,000,000

Year 4

20,000,000

Year 5

15,000,000

Year 6

10,000,000

Year 7

5,000,000

Year 8

Network incentives reserve total: 180,000,000 DCHUB (operator + infrastructure incentives).

Tokens enter circulation only as governance-approved budgets to operators and infrastructure programs.

Schedule is illustrative; governance may adjust releases within the reserve cap.

As reserve releases decline, operator funding shifts toward protocol fees and transparent budget cycles.

Protocol Treasury

Long-term development, grants, and operations are funded through treasury balances under governance control. They are non-voting by default and held in governance vaults so releases follow approved policy and reporting.

Allocation details

Allocation

4% (40,000,000)

Cliff

Not applicable

Vesting

Not applicable; governance-controlled releases

Distribution

Treasury vault (governance approval)

Sub-buckets / programs

Development; Grants; Operations; Reserves

Non-voting by default

dCorps Foundation

Stewardship and public goods are supported by foundation balances. They are non-voting by default and move only with governance approval and reporting to keep accountability.

Allocation details

Allocation

4% (40,000,000)

Cliff

Not applicable

Vesting

Not applicable; release policy required

Distribution

Foundation vault (governance approval)

Sub-buckets / programs

Policy-defined foundation initiatives

Non-voting by default

Liquidity Bootstrap

This pool provides operational liquidity for markets and infrastructure. Balances are non-voting by default, and releases require disclosure and governance approval so liquidity is managed openly.

Allocation details

Allocation

3% (30,000,000)

Cliff

Not applicable

Vesting

Not applicable; policy-driven releases

Distribution

Treasury or liquidity account (governance approval)

Sub-buckets / programs

Operational liquidity operations

Non-voting by default

Investors

On-chain lockups and vesting avoid sudden supply shocks and align investor capital with network growth. Schedule details are shared with verified investors.

Allocation details

Allocation

15% (150,000,000)

Cliff

Round-specific lockup periods (shared with authorized investors)

Vesting

Round-specific vesting schedules (shared with authorized investors)

Distribution

On-chain vesting account

Sub-buckets / programs

Round set adjusted as needed (shared with authorized investors)

Voting eligible

Core Team and Future Contributors

Tokens unlock over time to retain talent and keep incentives aligned with the network's long-term health. Only vested tokens count for voting, and the schedule is fixed in launch documents.

Allocation details

Allocation

8% (80,000,000)

Cliff

18 months

Vesting

48-month linear vesting (longer schedules possible for some roles)

Distribution

On-chain vesting account (time-locked)

Sub-buckets / programs

Core team; future contributors

Voting eligible

Months Core team and future contributors 18-month cliff - 48-month linear vesting

0 12 24 36 48 60 72 84 96

18m cliff 48m vesting Policy tail

Longer schedules possible for some roles.

Founder

Long-term vesting rewards building while reducing short-term selling pressure. Only vested tokens count for voting, and the schedule is fixed in launch documents.

Allocation details

Allocation

15% (150,000,000)

Cliff

24 months

Vesting

72-month linear vesting after cliff

Distribution

On-chain vesting account (time-locked)

Sub-buckets / programs

Not subdivided

Voting eligible

Months Founder 24-month cliff - 72-month linear vesting

0 12 24 36 48 60 72 84 96

24m cliff 72m vesting

Monthly unlocks after cliff.

Treasury/Fee Flow Map

Shows where fees go so users can understand who gets paid and why. Gas fees are paid in DCHUB and routed per governance-defined fee policy, while service fees fund the Treasury and are reported by category.

Gas fees (DCHUB) Operator fee recipient

Routed via governance-defined fee policy and public reporting.

Service fees (USDC or approved stablecoins) Protocol Treasury vault Category outflows (development, grants, operations, reserves)

Governance may define explicit splits (foundation, jurisdictions, community pool).

Starting balance Inflows Outflows by category Period delta Ending balance

Development Grants Operations Reserves

Reporting should be derived from tagged on-chain events where possible.

Release Authority Matrix

Shows who can release each allocation so it is clear what is automatic versus governance-controlled. This makes the checks and controls visible.

Founder Vesting schedule Time-locked vesting account On-chain vesting account

Core team and future contributors Vesting schedule Time-locked vesting account On-chain vesting account

Investors Lockup + vesting schedule Time-locked vesting account On-chain vesting account

Community and ecosystem programs Governed release caps Governance approval Community program vault

Network incentives reserve Governed budget schedule Governance approval Network incentives reserve vault

Protocol Treasury Governed release policies Governance approval Treasury vault

dCorps foundation Governed release policies Governance approval Foundation vault

Liquidity bootstrap Operational liquidity policy Governance approval Treasury or liquidity account

Governance/Change Control

Explains how token policy can change and why approvals matter. Documentation and existing legal agreements protect participants from surprise changes.

High-impact changes use stronger thresholds and longer voting windows.

Material changes must be documented in token policy artifacts.

Legal agreements already in force cannot be retroactively altered.

Hard-cap supply Not changeable after genesis Fixed at genesis; no discretionary inflation.

Allocation percentages Governance + legal agreements Material changes must be documented; existing agreements stand.

Vesting schedules On-chain vesting accounts Schedules are encoded at genesis or in policy updates.

Release caps Governance approval Used for community and ecosystem programs.

Rewards schedule Governance + parameter updates Reflected in governance fee policy parameters.

Treasury splits Governance approval Splits must be disclosed and reported.

Transparency Expectations

Sets expectations for on-chain visibility so anyone can verify supply, vesting, and releases. This is about trust and auditability.

Publish minted supply and circulating supply as separate values.

Make vesting and lockup contracts inspectable on-chain.

Trace distributions and governed releases from protocol vaults.

Report Treasury inflows and outflows by category.

Manifesto

"My goal is simple: make it possible for anyone, anywhere, to form an entity that can operate with credibility, continuity, and real financial rails, built for stablecoin-native operations."

Read the Manifesto

Nicolas Turcotte

Founder and Lead Engineer

Contribute now

Testnet is for builders, operators, and stewards who want to validate the Hub in public.

Protocol engineers

Working on kernel definitions, message scope, and invariants.

Indexer and data engineers

Defining event schemas and reproducible view inputs.

Early operators

Testing sequencer, batch posting, and operational scope under testnet rules.

Infrastructure-aligned investors

Tracking scope, risks, and progress (no return claims implied).

Legal counsel

Reviewing boundary posture, non-custodial scope, and document stack order.

Governance stewards

Shaping kernel/adapters separation and upgrade posture.

Testnet

Testnet access

If you're building or validating the Hub, request testnet access to evaluate it.

Request testnet access

Newsletter

Stay in the loop

Concise updates on testnet readiness, releases, and governance milestones.

Testnet

Testnet access

If you're building or validating the Hub, request testnet access to evaluate it.

Request testnet access

Newsletter

Stay in the loop

Concise updates on testnet readiness, releases, and governance milestones.