Devnet → Mainnet

SportsPerp has been live on Solana devnet since early 2026. Mainnet is targeted before June 12, 2026 — the kickoff of the 2026 FIFA World Cup. This page documents what’s done, what remains, and the order of operations.

Current state (as of 2026-05)

Detail on every item: PRD.md §14 Roadmap.

What “mainnet-ready” means

Nine gates must close before mainnet:

1. External security audit (engagement pending)

Two Solana-specialist audit firms will be engaged before mainnet — names published here once engagement letters are signed. Scope: full on-chain program, oracle pipeline, SDK math parity, liquidation cascade. The mainnet date is gated on a clean final report, with remediation + re-review windows ahead of deploy.

2. Multi-source oracle deployed

oracle-pusher/multi-oracle.mjs (588 lines, built) replaces the single-source admin oracle with 2-of-N weighted-median consensus. Remaining work: second Hetzner node, second Helius key, configuration testing, deploy cutover. ~1 day of engineering, €4.50/month infrastructure.

3. Admin keys → multi-sig + timelock

Today the admin keypair is a single key. For mainnet, admin operations (update_market_params, pause_market, configure_insurance, etc.) move behind a 3-of-5 multi-sig with a 48-hour timelock on parameter-changing instructions. The upgrade authority moves to the same multi-sig.

4. Switchboard PullFeed integration

For additional oracle resilience on mainnet, the 2-of-N consensus will include Switchboard TEE-backed feeds as a third leg. This adds hardware-level attestation to the existing off-chain sources.

5. Insurance fund mainnet seeding

The 20K USDC devnet fund will scale to a mainnet-appropriate size, seeded from protocol treasury. Target: $250K–$500K at launch, sufficient to absorb normal Layer 2 flow without ADL risk during the initial low-liquidity window.

6. Mainnet USDC + roster migration

All 68 markets will be re-initialized on mainnet with the mainnet USDC mint (EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v). Insurance fund, oracle feeds, all PDAs — fresh. Devnet state does not carry over by design: mainnet is a clean slate for real capital.

7. Points program go-live

Points Program wires up at the same moment as mainnet. First trading activity earns points.

8. Frontend mainnet cutover

The frontend auto-switches when it detects the mainnet program ID. Users connect their Phantom / Solflare / Backpack wallets, approve mainnet USDC, trade.

9. Operational runbooks

Every admin operation (emergency pause, market initialization, sunset, insurance top-up) has a runbook. The on-call rotation is established. Telegram alerts point to the oncall channel.

Target sequencing

Now (2026-04) ─────────────────────────────────────────┐
  │                                                     │
  ├─ External audit engagement (in flight)              │
  ├─ Multi-source oracle 2nd deploy                     │ 4-6
  ├─ Admin CLI + operational tooling                    │ weeks
  ├─ Multi-sig + timelock setup                         │
  ├─ Switchboard PullFeed integration                   │
  │                                                     │
  └─► 2026-05 (late May): Audit report received ◄──────┤
      │                                                 │
      ├─ Remediation window (high-sev findings)         │ 1-2
      ├─ Re-review of fixes                             │ weeks
      │                                                 │
      └─► 2026-06 (early June): Mainnet deploy ◄───────┤
          │                                             │
          ├─ Insurance fund seeded ($250K–$500K)        │ 1
          ├─ All 68 markets reinitialized                │ week
          ├─ Points program activates                    │
          ├─ Frontend mainnet cutover                    │
          │                                              │
          └─► 2026-06-12: World Cup kickoff ◄───────────┘

The window is tight but feasible. The biggest schedule risks are external-audit findings requiring structural changes (have mitigations drafted for likely scenarios) and multi-source oracle coordination (one-day implementation, but requires operational setup on a second VPS).

What ships later

These are post-mainnet additions, not mainnet blockers:

• Limit order book (currently trigger orders only)
• Cross-market portfolio margin
• Sub-accounts (multiple positions per trader per market)
• Mobile app (PWA today; native iOS/Android later)
• Keeper economic incentives tuning — live reward data will inform rebalancing
• Admin CLI consolidation
• Live match processor systemd hardening — deployed but needs extended stress testing under matchday load

What deliberately doesn’t ship

A few features we’ve ruled out for v1, each for a specific reason:

• More leagues / sports. La Liga, Bundesliga, or NFL markets could launch, but doubling the market count before mainnet tests of EPL at scale would dilute focus. See Expansion.
• Token launch at mainnet. $SPERP launches post-mainnet. See $SPERP → Overview for the rationale.
• Non-USDC collateral. SOL, other stablecoins, LP tokens are plausible; none are v1.
• Leveraged staking or yield wrappers on $SPERP. Post-TGE conversation at earliest.

Discipline on the “no” list is what makes the timeline credible.

Devnet continues

Devnet stays live throughout mainnet. It’s the canonical testing environment for SDK consumers, keeper development, and any protocol changes. Mainnet does not replace devnet — they coexist.

Further reading

• World Cup 2026 — why the launch date matters.
• Expansion — what ships after mainnet.
• Security → Audits — the audit process and status.
• PRD §14 Roadmap — canonical phase tracker.