Build: Network | dCorps Hub

Network Scope

Testnet environments are the networks integrations rely on. They include a local sandbox for fast iteration, a shared dev testnet for team alignment, plus the public testnet and rehearsal network used for upgrade practice. The configuration bundle lists chain IDs, peers, and parameters so teams stay in sync as the protocol evolves.

Local Sandbox

Single-node chain for local testing with deterministic behavior and fast resets.

Dev Testnet

Shared network for integration, operator coordination, and cross-team reproducibility checks during testnet cycles.

Public Testnet

Open testnet for external builders and operators with published chain IDs and onboarding steps.

Rehearsal Testnet

Mainnet rehearsal environment that practices upgrades and release candidates while remaining resettable.

Config Bundle

Current chain ID, genesis, peers, and base settings packaged for quick onboarding.

Resettable State

Testnet state can reset and parameters can shift as features are validated.

Access and Roles

Network access is split between builders, operators, and data services. Builders connect through JSON-RPC to submit actions, while operators run sequencer, batch posting, and node services under testnet rules. Indexers follow the chain to publish consistent views, and faucets supply test DCHUB for gas.

Builder Access

JSON-RPC endpoints expose transaction submission and chain queries for integration work.

Operator Track

Operator participation follows the current testnet ruleset with rotations, upgrades, and performance checks.

Indexer Sync

Indexer pipelines follow the chain and publish derived views for explorer and reporting surfaces.

Testnet Gas

Faucets distribute test DCHUB so signer wallets can pay transaction fees during development.

Network Parameters

Core parameters are published with each testnet configuration bundle and should be treated as active for the current cycle. These include chain identifiers, fee token settings, and genesis defaults used by Hub modules. Use the bundle as the single reference when running nodes or connecting client tooling.

Chain ID

Chain ID labels the network version and matches the current configuration bundle.

Gas Denom

Gas is paid in DCHUB on testnet; signer wallets hold balances for fees.

Genesis Defaults

Genesis defaults define module parameters for the current cycle and may shift on reset.

Peer Set

Peer lists and seeds keep nodes connected to the shared testnet for data sync.

Connection Flow

Use this flow to connect, submit actions, and validate outputs against the network. The steps apply to local or dev testnet and keep integration loops consistent across teams. Repeat the flow after resets to confirm your configuration is current.

Get the Bundle

Fetch the latest chain ID, genesis, and peer list for the current cycle.

Start or Connect

Run a local node or connect to shared testnet endpoints for RPC access.

Fund Signers

Use the faucet to fund signer wallets with DCHUB for network transaction fees.

Submit Actions

Send signed transactions through SDKs or APIs and monitor confirmations on chain.

Validate Outputs

Check explorer and indexer views to verify tag coverage and data consistency.

Testnet Boundaries

Cycles are intentionally flexible so the protocol can evolve quickly. State resets, parameter shifts, and version bumps are normal during early development. Use these environments to validate integrations and avoid assumptions about long-lived continuity.

Reset Cycles

State can reset between cycles, so keep configurations and data exports portable.

Parameter Drift

Parameters may shift as modules evolve, so verify against the latest bundle.

Testnet Focus

These environments support development and validation, not long-lived production workloads or stability.

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.