Build: Extensions | dCorps Hub

Optional Layers

Extensions are optional layers that sit on top of the kernel. Modules and adapters add specialized logic for sectors, jurisdictions, or assurance workflows without changing core authority rules. Extensions add capability while the kernel stays stable, shared, and consistent across all entities.

Optional Modules

Extensions add specific logic on top of the kernel without changing base authority.

Non-Authoritative

Extensions do not override kernel rules; they attach as overlays with limited scope.

Interface Declarations

Adapters publish their interfaces and versions so tools know how to integrate.

Testnet Status

Extension listings are testnet scoped and may shift as criteria evolve during each cycle.

Kernel vs Extension

Start from the shared base: entity registry, roles, wallets, and tagged flows. Extensions add specialized logic for domains like sector requirements, jurisdiction overlays, or assurance layers. This keeps the core stable while allowing optional layers for teams that use them.

Kernel Core

Entity registry, roles, governance actions, and canonical wallets define baseline behavior for all entities.

Extension Layers

Optional adapters add domain logic, attestations, or reporting patterns without kernel changes.

Registry Listing

Extensions are listed in the module registry with metadata that describes compatibility, version ranges, and status labels. Listings make it easier for builders to discover available adapters and confirm integration details. Listing is informational and does not imply approval or legal recognition.

Listing Metadata

Module metadata includes identifiers, version ranges, and ownership of each extension entry.

Compatibility Range

Compatibility signals show which kernel versions and interfaces the adapter supports today.

Governance Gate

Registry policies require governance actions to list, update, or retire modules officially.

Status Labels

Modules are marked draft, active, or retired to show current operational status.

Attachment Flow

Extensions attach through governance actions so the decision is transparent and consistent across tools. The attachment links the entity to a module and exposes the adapter metadata in explorers and registries. Detachments and updates follow the same flow and keep the chain state aligned.

Propose Attachment

Submit a governance action that names the module and the entity it will attach to.

Capture Approval

Approval results are stored on chain so tools can verify the decision.

Attach the Module

Link the module to the entity and expose its metadata in the registry.

Update or Detach

Use the same governance flow to update versions or remove modules safely.

Testnet Boundaries

Extensions are testnet-scoped and may change as modules and policies evolve. Listings, compatibility ranges, and governance flows can shift between cycles. Treat extensions as integration references and verify their status before relying on them for external commitments.

Reset Cycles

State resets can affect module listings, so keep configurations portable across cycles.

Policy Shifts

Registry policies can change between cycles; review updates always before attaching modules.

Coverage Gaps

Some adapters may be experimental or incomplete as testnet evolves quickly today.

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.