Production gates

Blocked. Eight conditions must all hold before mainnet. All eight are open. Gate 1 is blocking and everything else is downstream of it.

#Gate 1 — The premise is proven

Open, blocking.

It has not been established that Fomo accounts hold Robinhood Chain positions. The entire product assumes they do.

Closing this gate requires all three, together: a live FomoScan key, a real Fomo handle, and observable Robinhood Chain activity at the EVM address that handle resolves to. Not one of them, and not an inference from the other two.

Until then, no surface in this system claims it — the disclosure appears on the status page and in the site footer, and the market labels its identity data as fixtures.

#Gate 2 — Roles are a multisig and timelock

Open. A single EOA holding PAUSER_ROLE across the protocol is a single point of failure. Production requires a multisig for admin and a timelock for parameter changes.

#Gate 3 — The execution adapter is proven against the real venue

Evidence complete; the adapter is still disabled. It has now been exercised against the real venue — the live SwapRouter02, QuoterV2 and anchor pool on a mainnet fork — covering a buy, a partial sell, a full exit, a swap that fails on its floor, slippage rejection after the pool is moved against the trade, measured price impact, and a TWAP that refuses to follow a single large swap. Twelve tests, all passing.

It ships disabled anyway. That is a decision about what V1 turns on, not a gap in what has been shown. The fork is read-only and reached the live chain only to read it.

#Gate 4 — External security review

Open. The protocol is unaudited. No review has been commissioned or completed.

#Gate 5 — Every listed asset is individually reviewed

Open. Each asset needs its own recorded review: behaviour, decimals cross-checked on chain, canonical pool, liquidity against the floor, TWAP history, and a full-size exit quote.

Warning. A token is never approved because of its name. This chain hosts six verified contracts called Quoter, two of them wired to fork factories.

#Gate 6 — Operational readiness

Open. Monitoring, alerting and an incident runbook do not exist yet. See Monitoring and recovery, which is labelled planned for exactly this reason.

#Gate 7 — Capacity is set from executable conditions

Open. A vault's NAV cap must be derived from what can actually be executed and exited at size in real liquidity, not chosen as a round number.

#Gate 8 — Disclosure is accurate

Open. Every claim the interface makes must match what the deployed system does, verified at deployment rather than assumed from the development build.

#Already met

Some things are done, and they are worth separating from the gates above: verified chain configuration that fails closed, the structural identity/positions split, the invariant suite, virtual-share protection, exact-and-revoked approvals, and an exit path with no pause check and no oracle dependency.

#The one-line summary

Nothing is deployed to any public network, and nothing should be until gate 1 is closed — because if the premise is false, every gate below it is solving the wrong problem.