Governance | dCorps Hub

Decision Framework

Governance defines how the dCorps Hub changes, who can approve upgrades, and how authority is shown on-chain as time-ordered, tamper-evident state. The framework prioritizes safety, neutrality, and transparency over speed. Status is testnet; no claims beyond current capability.

Change Control

Protocol changes follow defined proposal, review, and adoption steps.

Safety First

High-impact changes use stronger thresholds, review windows, and clear rationale.

Neutrality

The Hub defines shared structures without favoring jurisdictions or institutions.

Phase-Gated Authority

Decision authority expands only after phase gates confirm readiness.

Governance Bodies

Defined bodies and advisory groups manage decisions, with on-chain governance as the intended authority at mainnet. Pre-mainnet coordination is founder-led and documented in public policies. Planned bodies are design intentions until incorporated or activated.

On-Chain Governance

Primary authority at mainnet for upgrades, parameters, and module lifecycle.

Protocol Council

Advisory body that reviews high-impact proposals and publishes guidance.

Foundation (planned)

Design intention for stewardship, public-goods funding, and coordination.

DevCo and ResCo

Planned service providers for engineering and research under governance scope.

Working Groups

Time-bounded advisory groups for specialist review and coordination.

Decision Domains

Scope covers parameters, modules, sub-chains, upgrades, treasury, and policy. The kernel is the minimum shared rule set; adapters and modules are optional overlays and cannot redefine it. Each domain expects published rationale, thresholds, and review notes.

Parameter Changes

Adjust protocol parameters within defined governance thresholds.

Module Lifecycle

Sub-Chain Recognition

Grant or withdraw sub-chain status based on explicit governance decisions.

Software Upgrades

Approve releases, migration plans, and rollback plans for kernel updates.

Treasury and Budgets

Allocate funds under published treasury policy with disclosed rationale.

Policy and Docs

Adopt or amend governance documents with versioned updates.

Transition Path

Authority shifts as phase gates are met, moving from founder-led coordination to on-chain governance. The foundation forms before mainnet, with IP stewardship transferring to it as a launch gate. Advisory bodies remain non-binding throughout.

Founder Coordination

Pre-mainnet coordination follows published policies and public disclosures.

Foundation Formation

Foundation forms before mainnet, receives IP stewardship as a launch gate, and prepares to execute governance-approved off-chain actions.

On-Chain Authority

Mainnet governance becomes the primary approval path for protocol changes.

Advisory Continuity

Council and working-group guidance remains advisory across all phases.

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.