Extension Framework
Modules are optional add-ons that extend the Hub without rewriting kernel history. The registry and attachment events keep modules interoperable, while boundary rules keep the system neutral.
Optional add-ons
Modules extend entity workflows while leaving the kernel record intact.
Registry listing
Registry entries include scope, version, compatibility, and attachment details.
On-chain attachment
Attachments are recorded on-chain in time order and tamper-evident.
Compatibility signal
Listing signals interoperability only, not approval, compliance, or legal status.
Kernel Modules (Required)
Every entity has required modules that define the canonical record. They stay minimal so governance can evolve without changing the standard.
Entity registry
Identity, type, and lifecycle status used across the network.
Authority and governance
Role bindings and decision records define who can act and approve.
Wallets and events
Canonical wallets and tagged treasury events capture inflows and outflows.
Document anchors
Hash anchors connect evidence and documents to the chain record.
Optional Modules and Adapters
Add specialized workflows or context by attaching optional modules and adapters that interpret kernel state. They can be attached or removed without rewriting the core record.
Jurisdiction workflows
Optional workflows that align entities with local recognition requirements.
Sector frameworks
Industry or impact overlays that sit above the kernel record.
Attestations
Third-party verification layers that reference canonical state.
Reporting overlays
Derived reporting views built from standardized event records.
Attachment Mechanics
Opt in to attachments that are recorded on-chain, so history remains time-ordered and verifiable. Entities can detach without changing kernel history.
-
Propose a module
Submit scope, version, and attachment rules for registry review.
-
Verify compatibility
Registry checks declared scope, parameters, and integration details.
-
Attach by governance
Entity decision-makers choose to attach, configure, or skip.
-
Record on-chain
Attachment events and parameters are recorded in sequence.
Governance Gates
Registry inclusion follows governance-defined gates so the module catalog stays neutral and consistent. Listing signals compatibility, not legal approval or compliance.
Listing eligibility
Governance defines who can submit and maintain registry entries.
Compatibility criteria
Scope, versioning, and attachment mechanics must be declared.
No implied approval
Listings do not confer legal recognition, compliance, or endorsements.
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 ManifestoNicolas 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.
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 accessNewsletter
Stay in the loop
Concise updates on testnet readiness, releases, and governance milestones.