Official Indexer | dCorps Hub

Reference Indexer

The official indexer is the reference data service that powers explorer summaries and derived views on testnet. Interfaces are reference access points; the protocol is the authority. Protocol scope is defined in the protocol overview. It ingests on-chain, time-ordered, tamper-evident events, normalizes them into readable tables, and exposes query APIs for tools. It is non-authoritative, and independent indexers can reproduce the same outputs.

Derived Views

Transforms events into balances, allocations, and coverage summaries for explorers and dashboards.

Query Access

APIs deliver entity, wallet, and commerce data for tools that read the Hub.

Reference Output

Acts as the baseline implementation for parity checks and conformance reporting work.

Open Reproducibility

Independent indexers can match outputs by following the shared schemas and event rules.

Core Coverage

The indexer organizes chain data into searchable surfaces so tools can answer common questions fast. Coverage includes entity registry state, governance actions, wallet flows with tags, evidence anchors, and commerce objects like invoices or recurring plans. Entities retain control of funds; the Hub anchors authority and events. Operations are stablecoin-native; no fiat rails or custody. These surfaces mirror the Hub schema and remain aligned across tools.

Entity Registry

Entity IDs, template types, status, and canonical wallet bindings derived from chain state.

Governance Trail

Proposals, approvals, and authority changes with timestamps and references for verification use.

Wallet Flows

Tagged inflows and outflows with categories, evidence links, and coverage ratios shown.

Commerce Objects

Catalog items, invoices, and recurring plans exposed for apps and dashboards tools.

Pipeline Flow

Keep outputs reproducible across tools by following a consistent indexing loop. Events emit from transactions, indexers normalize them, and views update with coverage signals. Use this flow to debug differences and confirm parity against the reference output.

Ingest Events

Stream blocks, transactions, and events from the Hub through JSON-RPC and indexed logs.

Normalize Data

Map raw events into tables that follow shared schemas and tag definitions.

Publish Views

Update derived views for entities, wallets, governance, and commerce objects continuously today.

Compare Outputs

Compare outputs against the official explorer and reference exports to confirm parity.

Signals and Reliability

Indexers expose signals that show freshness, coverage, and parity across tools. These include ingestion lag, missing tags, and mismatched totals so teams can resolve issues early. Signals support transparency but do not change protocol authority.

Freshness

Lag metrics show the last indexed block so viewers know how current the data is.

Coverage

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

Parity Checks

Parity checks compare outputs across indexers and detect mismatched totals or classifications.

Testnet Boundaries

The official indexer is testnet-scoped and evolves with protocol changes. Resets, endpoint shifts, and schema updates can affect outputs between cycles. Treat results as integration signals and verify against the current bundle when publishing.

Reset Cycles

State resets can clear indexed data, so maintain export or snapshot procedures.

Endpoint Shifts

JSON-RPC endpoints may shift between cycles; refresh connections regularly today.

Non-Authoritative

Indexer outputs are derived views; protocol state remains the authority always first.

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.