Mainnet Readiness

Mainnet is not one deployment switch. Every gate below must have accountable evidence.

Market data and oracle

• Execute a Chainlink Data Streams commercial agreement.
• Receive production API credentials and endpoints.
• Approve exact stream IDs, schemas, decimals, and coverage per market.
• Verify the official Robinhood verifier proxy, reference feeds, and sequencer feed.
• Measure report-to-inclusion latency at p50, p95, and p99 under load.
• Test stale, future, wide-confidence, deviating, closed-market, sequencer, and provider-outage behavior.
• Fund the router with LINK only if the live fee manager requires it.

Contracts and economics

• Freeze interfaces and deployment bytecode.
• Split or redesign the near-EIP-170-limit core before feature growth.
• Complete independent smart-contract and oracle/economic audits.
• Close findings and publish verification evidence.
• Review leverage, margin, fees, liquidation bonus, funding, OI, skew, staleness, confidence, and deviation per market.
• Model insolvency, correlated gaps, market closures, and withdrawal stress.
• Establish insurance and bad-debt policy.

Collateral and liquidity

• Select a reviewed production collateral token.
• Define custody, minting, redemption, depeg, blacklist, and upgrade risks.
• Capitalize the vault and insurance backstop.
• Establish deposit, withdrawal, caps, and emergency policy.
• Rehearse solvent and insolvent settlement scenarios.

Governance and keys

• Transfer ownership to a reviewed multisig.
• Put sensitive parameter changes behind a timelock.
• Separate deployer, governance, guardian, keeper, and oracle responsibilities.
• Use managed keys or HSM-backed signing.
• Document rotation, compromise, pause, and recovery procedures.

Reliability

• Run redundant keeper and RPC infrastructure without duplicate execution.
• Deploy regional failover for price streaming and BFF services.
• Configure metrics, paging, logs, traces, backups, restore drills, and status communication.
• Test reorg, sequencer outage, provider outage, database restore, and keeper failover.

Compliance and launch

• Complete legal review for perpetuals, jurisdictions, and RWA references.
• Implement required geo and eligibility controls.
• Publish terms, risk disclosures, privacy policy, and incident contacts.
• Start with capped deposits and one canary market.
• Raise limits only after defined observation periods and launch-policy approval.