Protocol Overview | dCorps Hub

Protocol Scope

Define the canonical entity record the Hub stores on-chain, and what stays off-chain. Kernel scope and boundary rules keep every entity readable under the same minimum standard. Interfaces remain downstream views of the chain.

Kernel record

Minimum shared record for identity, authority, decisions, wallets, treasury history, and anchors.

Recorded actions

Governance decisions, tagged wallet events, and document anchors recorded in sequence.

DCHUB mechanics

Gas, protocol fees, and governance define execution and upgrades.

Downstream interfaces

Interfaces are non-authoritative; apps submit actions and render views.

Kernel Record

A minimal kernel is required for every entity, with or without adapters. It stays small so entities can evolve through governance without changing the standard.

Entity registry

Unique ID, type, and lifecycle status so an entity can be referenced and verified.

Roles and authority

Role bindings and permissions that define who can act, approve, or spend.

Governance actions

Recorded proposals, approvals, and resolutions that define decisions over time.

Canonical wallets

Official wallets linked to authority so treasury activity is attributable.

Tagged events

Standardized inflow/outflow events with tags so reporting is consistent.

Document anchors

Hash fingerprints that prove documents existed and match later.

Boundary Rules

Keep the protocol neutral and non-custodial through boundary rules. It is not a bank, broker, exchange, or custodian. It makes no production-readiness claims.

Kernel required

No entity exists without the kernel record and its required fields.

Adapters optional

Adapters add context or recognition but cannot override kernel state.

Non-custodial

Funds remain in entity wallets; the protocol never holds assets.

No compliance guarantee

Legal recognition and compliance remain external; kernel correctness stays independent.

Kernel vs Adapters

Treat the kernel as required; adapters are optional layers that add context without redefining core authority. They can be attached or removed without changing the base record.

Kernel

Identity, roles, decisions, wallets, events, anchors that are always present.

Optional adapters

Jurisdiction, sector, attestation, reporting overlays that sit above the kernel.

Privacy, Disclosure, and Lifecycle

The protocol records a disclosure mode so explorers can show what is public versus aggregated. It also records lifecycle status so anyone can see whether an entity is draft, active, suspended, or dissolved. This reduces confusion and helps prevent payments to inactive entities.

Mode A

Everything public

Maximum transparency and verification.

Mode B

Structure public, selective disclosure

Public structure and totals, with privacy-aware details.

Mode C

Private execution with public proof

Private execution using private zones or sub-chains, with public anchors for evidence.

Registration status

draft

active

suspended

dissolved

Recorded Actions

Stablecoin-native actions are recorded on-chain in time order and are tamper-evident. This creates an auditable history without custody or fiat rails.

Registration

Create the entity and update lifecycle status as it changes.

Governance

Record approvals, votes, and resolutions as protocol state.

Treasury events

Tag income, expenses, and transfers from canonical wallets.

Document anchors

Attach evidence hashes so documents can be verified later.

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.