Build: Validation | dCorps Hub

Purpose and Coverage

Validation here means integration checks, not approvals. It defines how teams confirm that actions, tags, and derived views stay consistent across SDKs, indexers, and explorers on testnet. The coverage focuses on repeatable outputs, parity across tools, early detection of mismatches, and conformance reports with evidence hashes.

Schema Alignment

Action payloads follow the current bundle types so validation stays consistent across tools.

Tag Coverage

Flows carry required tags so views can classify activity without manual interpretation.

View Consistency

Derived views match indexer outputs so explorers show the same totals and classifications.

Tool Parity

Official and third-party tools align on the same inputs, outputs, and tag logic.

Conformance Surfaces

Validation checks apply to the kernel surfaces that drive Hub behavior: transactions, events, view derivation, and explorer output. Each surface has expected schemas and tag patterns so outputs line up across tooling. Coverage expands each testnet cycle, so updates are incremental.

Transaction Output

Signed actions emit expected events and state updates within current chain parameters.

Event Streams

Event feeds publish consistent payloads so downstream tools can parse and index them.

View Derivation

Indexer logic matches reference calculations for balances, allocations, and coverage ratios across tools.

Explorer Display

Explorer views surface the same results indexers compute, with matching tags and metadata.

Validation Signals

Lightweight checks show whether outputs match the current bundle. They include fixture comparisons, tag completeness checks, and indexer parity checks so teams can spot drift early. They are informative and guide integration work, not approvals or certifications.

Golden Fixtures

Reference fixtures compare expected outputs against live testnet responses for drift detection.

Diff Checks

Automated diff checks compare indexer outputs across environments to flag mismatches early.

Tag Completeness

Coverage checks flag missing tags so flows can be corrected before sharing results.

Error Signals

Errors are logged with action IDs so teams can trace failures quickly.

Conformance Reports

Publish conformance reports with version targets, results summary, and evidence hashes for review.

Validation Flow

Use this flow to align your integration with the current testnet surface. It keeps setup consistent across teams and highlights mismatches early. Repeat the flow after resets or bundle updates to keep your baseline aligned with current testnet behavior.

Review the Bundle

Pull the latest bundle and confirm schema versions, endpoints, and chain ID.

Run Sample Actions

Submit a small set of test actions that exercise wallets, roles, and tags.

Verify Tag Coverage

Check tag coverage for each action and fix missing or mis-typed values.

Compare Views

Compare explorer and indexer outputs to confirm totals and classifications match consistently.

Log and Re-run

Track mismatches, adjust integration logic, and re-run checks after updates as required.

Publish Report

Publish a conformance report with version targets and evidence hashes for review.

Testnet Boundaries

Validation work runs on testnet and inherits its constraints. Resets, parameter shifts, and partial coverage are normal during active development. Treat results as integration signals and verify again when the bundle changes. Bundle updates indicate when validation steps should be re-run.

Reset Cycles

State resets can occur, so keep fixtures and configs portable across cycles.

Parameter Shifts

Module parameters may change; align validation against the latest bundle each cycle.

Partial Coverage

Some modules may lag or be incomplete during testnet iterations for brief periods.

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.