Explorer | dCorps Hub

Explorer Scope

Reference interfaces (testnet) are the public tools that read or submit Hub actions, and the Explorer is the read-only view for them. Interfaces are reference access points; the protocol is the authority. Protocol scope is defined in the protocol overview, and integration guidance sits in the build overview. Registry state and governance history are on-chain, time-ordered, tamper-evident, and the Explorer displays that state alongside indexer summaries. Role visibility is wallet-bound; the Explorer does not infer human identity.

Read-only View

Read-only surface for entity status, governance actions, and wallet views without submitting transactions or approvals.

Indexer Summaries

Uses the official indexer to summarize tagged flows, coverage ratios, and derived views across tools.

Verification Links

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

Coverage Surfaces

Explorer coverage spans entity identity, role authority, governance actions, wallet flows, commerce objects, and evidence anchors. Role views are wallet-bound only; personal identity is not inferred. Entities retain control of funds; the Hub anchors authority and events. Operations are stablecoin-native; no fiat rails or custody. These views follow shared schemas so explorers, apps, and auditors see consistent surfaces.

Entity Profiles

Entity IDs, template type, and lifecycle status aligned to the Registry view for public reference.

Roles and Authority

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

Governance Actions

Resolutions, approvals, and policy changes appear with timestamps and attached evidence references.

Wallet Flows

Tagged inflows and outflows show operational, treasury, and program activity by wallet type.

Commerce Objects

Invoices, recurring plans, and catalog items surface payment intent and counterparty context.

Evidence Anchors

Anchored document hashes link policies, minutes, or receipts to the related actions.

Provenance Flow

The Explorer follows a consistent pipeline from chain events to readable views. On-chain state is time-ordered and tamper-evident, while indexer transforms events into summaries that tools can display. Use this flow to compare what the chain emitted with what the Explorer renders.

Emit On-Chain

Transactions emit state updates, tags, and approvals that define the authoritative chain output.

Normalize Events

Official indexer maps events into views, categories, and coverage signals using shared schemas.

Render Views

Explorer renders entity pages, governance trails, wallet flows, and evidence references for read-only use.

Confirm Alignment

Users compare Explorer views with protocol queries or registry links to confirm alignment.

Signals and Limits

Explorer views include signals that help interpret coverage during testnet. Freshness indicators show how recent the indexed block is, coverage ratios show missing tags, and reset markers flag historical gaps. These signals inform verification but do not change protocol authority.

Freshness

Shows the last indexed block and time lag so readers know how current the view is.

Coverage

Coverage ratios highlight missing tags or incomplete flows inside a time window.

Reset Markers

Reset markers note when testnet history restarts or data sets are pruned.

Interpretation Limits

Explorer outputs are descriptive summaries and never replace signed approvals or governance actions.

Testnet Boundaries

Explorer access is testnet-scoped and evolves as protocol and indexer coverage expands. Status is testnet; no claims beyond current capability. Treat outputs as integration signals and confirm them against the current release bundle when important actions depend on the view.

Read-only Boundary

Read-only outputs do not grant authority or replace approvals; they are views of chain state.

Partial Coverage

Coverage can be partial during active development; missing tags or lagging views should be expected.

Testnet Resets

Testnet resets can change addresses, balances, and history, so avoid relying on persistence.

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.