dCorps Hub
DevCo Testnet Foundation Audit Mainnet Adoption

Digital-native base layer for corporations and nonprofits

Stablecoin-native entity operations, with optional adapters for external context.

Entity Registry Authority Governance Treasury Ledger Anchors
READ WHITEPAPER EXPLORE HUB

Entity Hub

The dCorps Hub is a blockchain built for organizations.

Think of it like a public, tamper-proof company book that anyone can verify: it gives each entity a unique registry ID, clearly shows who has authority to act, records governance decisions, and tracks treasury activity with standardized, tagged accounting events. Under the hood it runs like any modern blockchain (consensus, transactions, a state machine), but its purpose is simple: it is the canonical source of truth for how an entity operates on-chain.

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

Status

A public snapshot of what each phase builds, who it serves, and what "done" means.

DevCo

Build

Builds the Hub chain and reference tooling for engineers and early reviewers.

Milestone: the kernel runs end-to-end on testnet with reproducible builds from source.

Testnet

Current
Reality

Runs the system in public so builders, operators, and data teams can test it under real conditions.

Next: testnet evidence supports a confident mainnet launch decision.

Foundation

Transition

Transitions stewardship from DevCo to a neutral governance process for operators, builders, and long-term contributors.

Ready when governance and upgrade processes run without DevCo control.

Audit

Assurance

Runs independent security and operational reviews before mainnet exposure.

Ready when audits, incident drills, and release checklists are validated.

Mainnet

Protocol

Operates as a permissionless rollup execution environment for real entity operations, with an open operator set and Ethereum settlement.

Proven by reliability, incident response, and upgrade safety under real usage.

Adoption

Ecosystem

Expands the ecosystem of applications and integrations that rely on the canonical entity record.

Outcome: multiple independent tools and interfaces—no single app required.

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.

Why it exists

Compare the fragmented entity stack of 2.0 with a stablecoin-native 3.0 model built around a shared, verifiable record.

Actual world (2.0)
  • Entity identity lives in local registries, while operations live across banks, custodians, and stablecoin wallets.
  • Authority changes and approvals are recorded in private tools and verified by humans, not by a shared record.
  • Governance decisions and accounting events sit in separate systems, so audits become manual reconciliation across many sources.
  • Standards and reporting formats diverge across jurisdictions, so cross-border comparisons remain inconsistent.
Kernel model (3.0)
  • A canonical on-chain record for identity and authority defines the source of truth.
  • Governance actions are recorded as protocol events, so the same history can be verified by anyone.
  • Tagged accounting events standardize treasury inflows and outflows and produce reproducible views.
  • A shared kernel stays stable while optional adapters add context without rewriting history.

Who it serves

The Hub is designed for organizations that need verifiable authority, governance, and stablecoin-native operations.

Founders and operators

Keeping cap tables clean, decisions clear, and stablecoin treasury activity auditable.

Nonprofits and NGOs

Running board governance with transparent donation and program flows.

Protocols and DAOs

Adding a formal entity layer beyond multisigs and informal tooling.

Builders and auditors

Using standard event schemas and reproducible reporting views.

Jurisdictions and regulators

Reading machine-readable entity and governance records without manual reconciliation.

Donors and counterparties

Verifying who can sign and how funds were allocated.

Kernel and adapters

Kernel is required; adapters are optional overlays that never redefine kernel history.

Kernel (required) Required
  • Entity registry and lifecycle status.
  • Roles, authority bindings, and governance actions.
  • Canonical wallets and tagged accounting events.
  • Document anchoring and audit trail.
  • Chain execution and consensus rules.

Always present.

Optional adapters Optional
  • Jurisdiction recognition workflows.
  • Sector and impact frameworks.
  • Attestation and assurance modules.
  • External reporting overlays and eligibility rules.
  • Registry labels and discovery signals.

Attached by choice.

How it works

Entities become verifiable by recording identity, authority, and actions in a fixed sequence.

  1. 1

    Register a Hub corporation or Hub nonprofit and receive a canonical entity ID.

  2. 2

    Bind roles and canonical wallets, and define governance rules.

  3. 3

    Record governance actions and resolutions as state.

  4. 4

    Record tagged accounting events for inflows and outflows.

  5. 5

    Anchor material documents by hash when evidence is required.

  6. 6

    Attach optional adapters that publish derived interpretations.

Operating assets

USDC is the reference stablecoin for treasury inflows and outflows. DCHUB is the protocol token used for gas, governance, and protocol-level fees.

USDC

Reference stablecoin for treasury inflows, outflows, and tagged accounting events on the Hub.

DCHUB

Protocol token for gas, governance, and protocol-level fees; entities may hold it per treasury policy.

Testnet

Testnet access

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

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.

References

The core references define the Hub kernel, scope, and current phase constraints.

Learn overview

Definitions and document stack order for the current scope.
Protocol overview

Kernel boundary, invariants, and module separation.
Hub overview

Entity kernel and Hub container summary.
Build overview

Integration posture for engineers at the current stage.
Roadmap (dev phases)

Phase structure and status without timelines.
Governance

Decision actors, scope, and limits.