Read current network, node, and service health.
Make blockchain launch work understandable for every team.
The guide explains launch plans, chain profile, wallet custody, token supply, allowlisted operations, and the API surface without forcing readers to understand every infrastructure detail.
Three surfaces, one model
Home — explains the service
Portal — handles daily work
Guide — supports admins & developers
1Plans
Compare the three launch packages and choose the right starting point.Read →2Chain
Runtime capabilities, consensus profiles, and chain API endpoints.Read →3Genesis
Chain ID, token supply, treasury address, and genesis hash model.Read →4Wallets
Treasury, operator, validator wallets, and production custody rules.Read →5Operations
Health checks, maintenance requests, snapshots, recovery — in safe order.Read →6API
Endpoints, payloads, and tokens for network and job orchestration.Read →7Security
Access rules, tenant separation, secrets handling, and audit expectations.Read →Three plans, one architecture model.
Plan defines validators, quorum, API capacity, and archive roles. Pick a plan, name the network, and the rest is provisioned through audited jobs.
Foundation-55 validators4 quorum0 API · 0 archive1f BFT
Resilient-77 validators5 quorum1 API · 1 archive2f BFT
Scale-99 validators7 quorum2 API · 2 archive2f BFT
The portal mirrors the service surface.
- Launch: create a network record from plan, environment, chain ID, supply, treasury, and size.
- Networks: see service status and capacity for every tenant network.
- Wallets: generate treasury and operator wallets through audited worker jobs.
- Access: users, scoped API tokens, and audit review.
- Maintenance: read-only and guarded actions backed by audited worker jobs.
Allowlisted maintenance tasks.
Recommend recovery actions without mutating the network.
Fetch recent node logs with optional marker filtering.
Restart one node through the guarded maintenance flow.
Create a node data snapshot before repair.
Recover a stale node from a healthy donor.
Restore one node from a verified snapshot.
Generate a wallet through the approved service flow.
Every action is recorded as an audit event with actor, target, and result — keep this guarantee when you wire production execution.