Build: dApp Integration

Interface Scope

dApps are non-custodial interfaces that read Hub state and submit actions through wallet signatures. These patterns cover how front ends and services read chain state, submit actions, and present tagged flows to users. The intent is clear, consistent user experiences that align with kernel authority and remain verifiable on testnet.

Non-Custodial UX

Apps request signatures from user wallets and avoid holding funds or keys.

Read Surfaces

UIs pull entity, wallet, and tag data from explorers and indexers for consistency.

Write Actions

Apps submit actions for roles, wallets, invoices, and tagged payments on chain.

Authority Checks

Interfaces confirm roles and approval limits before presenting privileged actions to users.

Query Patterns

Use these patterns to read the Hub without creating local silos. They focus on registry state, governance history, wallet activity, tagged flow summaries, and commerce objects like invoices and recurring plans. When queries follow these patterns, apps and explorers surface consistent data for everyone.

Entity Registry

Read entity IDs, template types, and lifecycle status for navigation and access gating.

Governance History

Surface approvals, resolutions, and authority changes directly from chain state sources for accuracy.

Wallet Activity

Read wallet balances, flows, and tags so financial views stay aligned across tools.

Commerce Objects

Read catalog items, invoices, and recurring plans so commerce activity stays visible.

Tag Summaries

Pull tagged flow summaries to power allocations, grants, and revenue views reliably.

Write Patterns

Submit actions without taking custody by following these patterns. They cover governance actions, role updates, wallet flows, and evidence anchors. Following these patterns keeps UI actions aligned with the kernel and makes audit trails consistent across tools.

Governance Actions

Submit governance actions for approvals, policy updates, and authority changes on chain.

Role Updates

Update role bindings, delegate operators, and revoke access through signed actions safely.

Invoices and Payments

Generate invoice flows with tagged payments so settlement stays transparent and verifiable.

Evidence Anchors

Anchor document hashes when evidence is required for approvals or disclosures in apps.

Indexing Patterns

Keep data views consistent across explorers and dashboards by using a simple indexing loop. Events emit from transactions, indexers normalize them, and derived views present totals and coverage summaries. When apps follow this loop, they stay aligned with public visibility.

Emit Events

Transactions emit tagged events that describe activity and authority changes clearly for tracking.

Normalize Data

Indexers normalize events into structured outputs for dashboards and explorers across tools.

Publish Views

Derived views publish balances, tag summaries, and coverage indicators for verification clarity.

Integration Flow

Use this flow to align dApp behavior with the current testnet surface. It keeps setup consistent, highlights missing permissions, and ensures your UI matches the kernel outputs. Repeat after resets or SDK updates so your dApp stays aligned with evolving testnet behavior.

Map the UX

List the actions your UI exposes and map them to kernel actions and tags.

Connect Surfaces

Wire SDKs, RPCs, and indexer endpoints to the current testnet bundle quickly.

Test Permissions

Validate wallet roles and approval limits before enabling privileged actions in UI.

Run Transactions

Submit sample flows, review confirmations, and verify tags on-chain for accuracy.

Verify Views

Check explorer and indexer views so your UI matches public outputs exactly.

Testnet Boundaries

dApp patterns are testnet-scoped and will evolve with kernel and tooling updates. Resets, parameter shifts, and incomplete module coverage are normal in active development. Keep your UI flexible and confirm behavior against the current bundle before wider use.

Reset Cycles

State resets can occur, so avoid hardcoding network assumptions in apps today.

Parameter Shifts

Module parameters can change; align UI logic with the latest bundle each cycle.

Coverage Gaps

Some views or flows may lag during testnet iterations and tooling updates.

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.