Launch workspace · Pons on Robinhood Chain

Launch the token.
Bind the treasury.

Six steps produce one deterministic manifest and digest covering creator tax, immutable 5/95 fee settlement, project-owned treasury routes, token support, authority, caps and failure behavior. Public execution remains canary-gated.

MAINNET INFRASTRUCTURE LIVE18 CONTRACTS VERIFIEDTOKEN LAUNCH · CANARY GATED
Loading the launch workspacePlan first. Wallet authorization only after server verification.
After the manifest

What turns a plan into a launch.

The wallet signs one session authorization, then explicitly approves each simulated transaction. Every receipt is verified before PROG reveals the next step. The protocol's 5% share is fixed infrastructure policy; creators control the remaining 95% project route.

01

Generate + keep

Download the manifest JSON. The digest is reproducible from the file alone; re-import it here at any time to confirm.

02

Bind authority

Your project Safe signers review the digest. The Safe becomes treasury owner; the operator is bounded to claim/allocate plans.

03

Re-simulate

Pons readiness v2 re-verifies the exact treasury runtime, escrow binding and every dependency lock at a fresh canonical block.

04

Gated canary

Only after the orchestrator, bounded authority, monitoring and an explicit owner approval are ready does a tiny public canary execute. Until then the API stays 503.

Identity · PENDINGFlywheel · PENDINGManifest · READYMonitoring · PENDINGCanary approval · PENDINGRelease gates ↗