Registry | dCorps Hub

Registry Scope

Reference interfaces (testnet) are the public tools that read or submit Hub actions, and the Registry is the read-only view for entity profiles and status. Interfaces are reference access points; the protocol is the authority. Protocol scope is defined in the protocol overview. Registry state is on-chain, time-ordered, and tamper-evident. Role visibility is wallet-bound; the Registry does not infer human identity.

Read-only View

Registry pages display entity profiles and governance context without allowing edits or transactions.

Protocol-defined Status

Lifecycle status and role bindings are set by protocol rules, not by interface input.

Verification Links

Shareable links expose entity status, role bindings, and wallet types in a single view.

Registry Views

See the fields external tools use to verify identity, governance, and wallets. Entities retain control of funds; the Hub anchors authority and events. Operations are stablecoin-native; no fiat rails or custody. Views align across Registry and Explorer so different interfaces show the same structure.

Entity Profile

Entity ID, template type, and disclosure mode displayed with current lifecycle status.

Role Bindings

Role bindings show which authority wallets can approve actions and which bindings are active.

Governance History

Governance actions and approvals appear with timestamps and links to evidence anchors.

Wallet Bindings

Canonical wallet types map to addresses for merchant, donation, treasury, or program flows.

Evidence Anchors

Anchored document hashes reference policies, minutes, receipts, or approvals tied to governance and payments.

Status Signals

Status signals show active, suspended, or dissolved states based on on-chain lifecycle updates.

Verification Flow

Use the registry flow to verify an entity before acting. Start with entity ID, review status and role bindings, confirm wallet types, then open explorer and indexer views to compare tags and history. This sequence keeps verification consistent across tools.

Find Entity

Search by entity ID or name to open the canonical profile view.

Check Status

Check lifecycle status and disclosure mode to understand whether actions are active.

Review Bindings

Review role bindings and wallet types to confirm which addresses are authorized.

Confirm Views

Open explorer or indexer summaries to cross-check tagged flows and governance history.

Authority Boundaries

The Registry is a visibility layer only. It does not confer legal standing, compliance approval, or institutional endorsement. Authority remains defined by on-chain rules and role approvals, and external processes determine any legal or regulatory outcomes.

Legal Standing

Registry visibility does not create legal personhood or incorporation; it only shows on-chain status.

Compliance Scope

No regulatory approval is implied; compliance remains off-chain and outside registry responsibilities.

Interface Authority

The Registry is non-authoritative; protocol rules and signed governance actions define validity.

Testnet Boundaries

Registry data is testnet-scoped and can change as protocol and indexer coverage evolve. Status is testnet; no claims beyond current capability. Reset events, schema changes, or label updates can shift what appears, so treat outputs as integration signals and confirm against current releases.

Testnet Resets

Testnet resets can clear history or change entity addresses, so avoid relying on persistence.

Coverage Shifts

Coverage can be partial while indexer schemas evolve; missing fields or tags should be expected.

Schema Updates

Schema updates can revise fields or labels; confirm current meanings in the protocol overview.

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.