What problem does it solve?
It makes it harder for a project to claim it is ready when the evidence is missing, changed, or hidden.
Plain-English Doorway
Quantum Pi Forge is a public proof engine for digital launches.
It shows what was built, what was verified, what is locked, and what still requires approval before anything goes live.
Think of it like a black box flight recorder for a launch.
Digital projects can change files quietly, make unproven claims, or launch with hidden steps. Quantum Pi Forge creates a visible proof trail first, so people can inspect the state before activation.
Builder
Creates the system and commits the work.
→
Proof Receipts
Records what was checked and what the result was.
→
Public Review
Lets outside people inspect the evidence.
→
Operator Approval
Requires explicit human approval for the next move.
→
Activation
Only happens after proofs and approval are clear.
What can someone check?
They can check the repo state, verification commands, receipts, locked status, and whether execution has happened.
Why does it matter?
Because trust should not depend only on promises. It should be backed by public, repeatable proof.
One-minute explanation
Quantum Pi Forge is for people who want to prove a digital system was built, checked, and held in a locked state before launch. Instead of saying “trust me,” it creates a public trail showing what happened, what passed, what is still blocked, and who must approve the next step.
Genesis Activation Evidence (Gated)
Status: Implemented but gated — not a claim that the full network or economy is live. Project records document a genesis activation path on 0G Aristotle (chain ID 16661) with sealed local execution receipts. Canonical public addresses remain Pending in contracts/DEPLOYED_ADDRESSES.md until independently re-verified. Liquidity, staking, public mint opening, and bridge activation remain gated.
- Execution receipt (project artifact):
receipts/execution/v2-mainnet-cutover-execution-v1.json - Main commit (historical):
4c9c392— Activate v2 mainnet cutover: BirthGenesisHeartbeat (#341) - Chain ID (declared):
16661 - Recorded candidate addresses (pending canonical matrix): OINIO Token
0x75995EC0fdf881189850aeD864cB3f43c0DFCb58; Model Registry0x67aD7169184581f23D1E10B39d4eb4e98293E87a; Heartbeat Monitor0x5E50b92E57e854659f7D98c733088aABd551C49F - Recorded birth block (pending independent check):
36214213 - Status table:
docs/review/VERIFICATION_STATUS_TABLE_V1.md
Note: EIP-712 / permit support is not part of the recorded OINIO Token or Model Registry contracts. It remains a future extension for signature-based flows. Do not treat this section as proof of live yield, mint, stake, or Pi bridge.