Build: SDKs | dCorps Hub

Integration Scope

SDKs and APIs are the client surfaces used to integrate with the Hub testnet. Official packages target JSON-RPC and indexer APIs, with signing flows and query patterns that keep outputs consistent with the kernel. Use these surfaces to connect, submit actions, and read state.

SDK Packages

Official packages provide typed helpers for entity actions, wallet flows, and tag payloads.

JSON-RPC Interface

Low-level node interface for transaction submission and raw chain query calls.

Indexer API

HTTP endpoints for standardized queries, reporting views, and wallet/event metadata.

Event Streams

Indexed event feeds for monitoring, reconciliation, and data pipelines at scale.

Surface Capabilities

SDKs expose the actions that power entity setup, wallet activity, and tagging. Use them to submit transactions, read chain state, and stream events into apps and dashboards. Each surface supports different abstraction levels, from direct node calls to higher-level helpers for app builders.

Signing and Broadcast

SDK signing helpers build transactions, attach tags, and broadcast with the correct fee settings.

Entity Actions

Create and update entities, roles, units, and wallets through consistent action calls.

Query and Views

Read chain state, wallet balances, and tag activity for dashboards and compliance checks.

Event Streams

Subscribe to event feeds for reactive apps and automated monitoring pipelines and systems.

Versioning and Status

Testnet surfaces evolve quickly, so versions and coverage can shift between cycles. Compatibility targets are best-effort and published alongside each bundle. Treat SDKs as integration references rather than long-term contracts, and expect updates as modules mature and tooling expands.

Status Bands

Surfaces are labeled available, limited, or planned to signal current coverage levels.

Compatibility Window

Testnet versions can change between cycles, so pin dependencies to the current bundle.

Deprecations

Interfaces may be retired or replaced as modules mature, with update notes shared per cycle.

Integration Flow

Use this flow to align your app with the current testnet surface. It keeps setup consistent across teams and makes it easy to verify that actions, tags, and views match Hub expectations. Repeat the flow after testnet resets or SDK updates to confirm your environment.

Review Surfaces

Scan the SDK list and interface layers that match your integration target.

Connect Testnet

Configure JSON-RPC endpoints from the current bundle and confirm chain ID.

Build Transactions

Use SDK helpers to assemble actions, attach tags, and set fee parameters.

Submit and Observe

Broadcast signed actions and monitor confirmations plus event feeds for success or failure.

Validate Outputs

Compare explorer and indexer views to confirm tag coverage and data consistency.

Testnet Constraints

These SDKs are built for testnet work, so behavior can shift as the protocol evolves. Resets, parameter changes, and endpoint updates are normal. Plan for fast iteration, and confirm your integration against the latest bundle before sharing results externally.

Reset Cycles

State resets can occur, so export configs and keep integration data portable.

Endpoint Shifts

Endpoints and peers may change between cycles; always refresh from the latest bundle.

Coverage Gaps

Some modules and query views may lag during testnet iterations or brief update 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.