What It Covers
Build is the integration area for teams building on the Hub. It covers SDKs and APIs, testnet networks, validation checks, indexer integration, optional extensions, and dApp patterns. Use it to choose an entry point and keep outputs aligned with the kernel as testnet changes.
SDKs and APIs
Client libraries and API patterns to sign actions, submit transactions, and read Hub state with consistent types.
View pageNetwork Environments
Testnet RPC endpoints, faucet access, and chain parameters for integration testing, reset cycles, and repeatable iteration.
View pageValidation and Conformance
Conformance checks and fixtures to confirm outputs match expected schema, tag coverage, and view parity across tools.
View pageIndexer Integration
Read-only integration paths for explorers and dashboards that consume Hub data directly and keep views consistent.
View pageExtensions and Adapters
Optional overlays for sector or jurisdiction logic that leave kernel authority unchanged while adding specialized workflows.
View pagedApp Patterns
Reference flows and UI patterns for dashboards, registries, and verification surfaces used by builders at scale.
View pageBuild Flow
Integration work follows a consistent loop: connect to testnet, use SDKs to send actions, validate outputs, and refine. The flow stays light so teams can iterate quickly, while reference tooling confirms that transactions, tags, and views align with the kernel.
Map the Surface
Map the surface you are building: SDK, network, validation, extension, or dApp pattern.
Connect to Testnet
Connect to testnet endpoints and fund signer wallets for network transaction fees.
Implement Actions
Implement core actions with the SDK or API and submit signed transactions.
Validate Outputs
Validate outputs with the official indexer and explorer to confirm schemas and tags.
Refine and Share
Refine flows and document integration assumptions so teams can repeat results reliably.
Reference Interfaces (testnet)
Use downstream views of the chain to inspect results during testnet work. They show identity, wallets, transactions, and summaries so you can confirm outputs match the kernel. Use them for verification and demos while you build against SDKs and network endpoints.
Official App
Use the official app to run core actions and verify signing flows end to end.
View pageThe Registry
Use the registry to verify entity identity, status, and canonical wallet bindings.
View pageThe Explorer
Use the explorer to inspect transactions, balances, and tag coverage as they update.
View pageOfficial Indexer
Reference indexer powers derived views and reporting summaries so outputs stay consistent across tools.
View pageManifesto
"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 ManifestoNicolas 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.
Newsletter
Stay in the loop
Concise updates on testnet readiness, releases, and governance milestones.
Testnet
Testnet access
If you're building or validating the Hub, request testnet access to evaluate it.
Request testnet accessNewsletter
Stay in the loop
Concise updates on testnet readiness, releases, and governance milestones.