World Cup 2026
The 2026 FIFA World Cup kicks off on June 12, 2026, hosted across 16 cities in the United States, Canada, and Mexico. It is the largest single sports event of the decade and the launch window SportsPerp is aimed at.
Why the World Cup is the right launch moment
Three reasons:
1. Peak global engagement in football
The 2022 World Cup drew an estimated 5 billion viewers across its month-long run — more than half the planet. The 2026 edition expands to 48 teams (up from 32), 104 matches (up from 64), and hosts for the first time in North America, which brings a new audience into the engagement surface.
No other sports event comes close. A SportsPerp product that is live, functional, and has meaningful liquidity during that window captures a distribution opportunity that does not repeat for another four years.
2. A natural narrative for a performance index
World Cup squads are curated from 48 national teams. Every match is globally televised. Every player on the pitch has a persistent reputation, a club context traders already follow, and a post-match OBV that publishes within 24 hours via our data partner’s feed.
The index values SportsPerp trades — z-scored OBV per 90, form, results — are exactly the metrics that the informed football audience debates between matches. A trader forming a view on “Is Mbappé or Haaland more valuable right now?” has a tradable answer on SportsPerp, not a betting slip.
3. Crypto has been there before
Every major crypto cycle has a “World Cup narrative” trade that traders coordinate around — fan tokens, NFT projects, prediction markets. SportsPerp is the first to package that narrative as continuously tradable perpetuals on performance, rather than outcome-fixed bets. The product-market fit argument is strongest when the addressable audience’s attention is highest.
What SportsPerp will support for the World Cup
Expanded market coverage
EPL is SportsPerp’s launch surface (68 markets). For the World Cup window, we plan to add:
- 24–32 national team markets — the major-contender national teams at the tournament. Market IDs in a dedicated non-clashing range (likely 100–131).
- 60–80 player markets covering top players across those teams. Same selection algorithm as EPL (position-group z-scored composite, position quotas, max per team).
- Total tournament addition: ~100 new markets for the duration of the tournament, sunsetting at the end per standard market lifecycle.
National team markets inherit the same mechanics as EPL clubs: OBV-driven composite, 100–900 index range, three-layer liquidation, same fees.
Tournament-specific features
Several features are on the roadmap specifically for the tournament:
- Fixture-aware funding — funding intervals anchored to match schedules so accrual behaves predictably around games.
- Match-day leaderboards — publicly surfaced top traders per match. Narrative fuel for social engagement.
- Live-match overlay parity — the real-time OBV pipeline gets the same latency and reliability budget as EPL live coverage.
- Pre-tournament fixture calendar integrated into the frontend so traders can plan around kickoff times.
Non-goals for the tournament window
We will not ship:
- Prop markets (“Mbappé scores first”). These are discrete outcomes — a sportsbook product, not a continuous index product.
- Fan-token-style speculative assets. SportsPerp is OBV-index perpetuals; that’s the scope.
- Tournament-specific token emissions or airdrops outside of the ongoing Points Program.
Focus discipline during the most intense user-acquisition window matters more than feature expansion.
Operational preparation
Scaling for load
A matchday with 4 concurrent matches produces ~8,000 live events, driving:
- ~8,000 WebSocket broadcasts to connected clients.
- ~100–200 oracle pushes (live match cadence is ~30s, not 5min).
- Proportional keeper activity for any matchday triggers.
Load testing in Q2 2026 will validate that the current Hetzner CPX22 can handle this. If not, either upgrade to CPX32 (8 vCPU, 16 GB RAM) or split the oracle pipeline across two nodes — both are trivial changes.
Oncall rotation
The World Cup window is 2026-06-11 through 2026-07-19 (final). Our team will operate a 24/7 oncall rotation for the tournament window, with defined runbooks for:
- Oracle staleness on a live match.
- Live-match overlay degradation.
- Insurance fund utilization > 75%.
- Unusual liquidation activity.
The monitoring service emits structured alerts to disk on Hetzner today and is ready to forward to a Telegram bot once the production webhook is wired (NANOCLAW_ALERT_URL). Wiring the webhook is on the pre-launch checklist for the rotation.
Communication
- Status page publishing oracle health, service uptime, and fund stats in real-time.
- Transparent incident writeups within 72 hours of any material service issue.
- Pre-tournament load test day published in advance — community invited to stress-test the system with devnet positions before the real window.
Post-tournament
The World Cup is a launch window, not a product. After the tournament:
- National team markets sunset on the standard 72-hour oracle-staleness schedule. Existing traders have 72+ hours to close; stragglers get
settle_position’d at the last known mark. - EPL markets resume as the core offering.
- Retrospective — what worked, what failed, what to ship for the 2027 EPL season opener (August 2026) and the 2028 European Championship in the UK and Ireland.
The World Cup is the first sports perp moment. It won’t be the last.
Further reading
- Devnet → Mainnet — the pre-launch roadmap pointing at this date.
- Expansion — what comes after the tournament.
- Market Lifecycle — how temporary tournament markets sunset cleanly.