Hub Overview

What It Is

Hub is the shared entity layer for corporations and nonprofits. It provides a consistent on-chain identity, authority roles, governance actions, wallet types, and evidence anchors so every organization follows the same structure. Templates build on this kernel, letting apps and explorers read any entity with the same rules.

Kernel Foundations

Shared foundations stay on for every template: the kernel defines the minimum data an entity must publish so identity, authority, and wallets can be verified everywhere. Interfaces are downstream views of the chain, so the same entity looks consistent across apps, explorers, and indexers.

Optional Adapters

Add jurisdiction or sector context on top of the kernel without changing core authority. Adapters can express local attestations or disclosure rules while leaving the base structure intact. If an adapter is not present, the kernel still supplies the complete operating foundation for the entity.

Corporation Templates

Pick a template that scales from solo owners to multi-class governance. Each corporation template sets default ownership units, approval layers, and wallet structure so operations and capital flows stay clear. Start with the closest fit now and move as ownership or approvals change.

This comparison highlights the main structural differences across corporation templates, from single-owner control to committee governance. It shows where approvals, investor consents, and capital workflows appear while keeping the kernel consistent across all templates.

Nonprofit Templates

Choose a template built for public trust, donation flows, and program allocation. Each nonprofit template defines board roles, committee scopes, and fund separation so giving stays transparent and policy driven. As programs grow, you can shift to deeper governance or fund controls without losing continuity.

This comparison focuses on governance depth and fund controls across nonprofit templates. It shows where boards, committees, designated funds, and selective disclosure appear while the donation baseline stays shared. Use it to understand how oversight and program complexity expand as you move up.

Tagging and Evidence

Tags are short labels applied to payments so every flow stays understandable. Core tags apply across all entities, while context tags add program, fund, or treasury detail. Evidence anchors attach a secure reference to approvals or receipts without exposing private files.

Operating Flow

The Hub flow starts with registration and ends with verifiable activity. You bind authority roles, connect wallet types, and run payments with required tags. Evidence anchors support material actions, while live views show balances and allocation splits. The same flow applies across templates, with extra steps for complex structures.

Live On-Chain Views

Explorers and indexers compute live summaries from tagged flows without waiting for manual exports. You can see balances, program splits, and coverage as activity happens. Anyone viewing the same entity sees the same totals, which keeps public understanding in sync.

Lifecycle and Status

Signals show whether an entity is active, paused, or closed, so partners know when payments should go through. Interfaces show the status automatically as a safety cue. This reduces confusion and prevents money from going to inactive entities.

Where to Operate and Verify

The official app handles day-to-day actions like registration, payment requests, tagging, and approvals. Public tools let anyone verify identity, status, and wallet bindings. The official indexer powers shared views, while third-party dApps and SDKs support custom integrations.