[ RESEARCH REPORT // 04 ]TXLINE ORACLES & SOLANACONSUMER & FAN EXPERIENCES

Octopus Crowd: Real-Time World Cup Prediction Engine via Oracle Merkle Proofs

Transforming passive second-screen sports consumption into provably fair micro-challenges settled on live telemetry streams, bypassing regulatory gambling traps through a zero-stake reputation model.

BY VINICIUS PONTUAL — SYSTEMS & FULL-STACK ARCHITECT
DEPLOYED: JUL 18, 2026 // TXLINE × SOLANA HACKATHON
Octopus Crowd Match Room Architecture and Real-Time Event Pipeline
FIG 1.0: LIVE TXLINE SSE STREAM → INGESTION WORKER → NEON POSTGRES → MERKLE SETTLEMENT[ ORACLE & IDENTITY SPECIFICATION ]
Latency PipelineSub-Second SSE
Settlement LayerMerkle Oracle
Capital At Risk$0 (Identity Only)
Infra OverheadServerless Node

01. The Problem: Passive Second Screens & Gambling Grey Zones

During major sporting events like the World Cup, over 80% of spectators consume the match with a mobile device in hand. However, current fan interaction remains completely passive: refreshing static scores on live-ticker apps, doomscrolling social timelines, and waiting for highlights.

Existing Web3 solutions uniformly converge into the same pattern: sportsbooks. They demand that users deposit collateral, calculate odds spreads, and risk capital on binary outcomes. This creates two immediate systemic barriers:

  • Regulatory Exclusion: Sportsbooks face aggressive geo-blocking, compliance red tape, and strict state licensing frameworks, excluding the majority of global retail fans.
  • High-Friction Onboarding: Forcing a user to purchase, bridge, and risk tokens just to engage with a live soccer match destroys consumer retention and viral loop mechanics.
  • Oracle Opacity: Centralized betting apps compute resolutions internally in private databases. Bettors must take match resolutions on pure faith without cryptographic proofs.

02. Strategic Positioning: Skill & Cryptographic Proof vs. Betting

Octopus Crowd deliberately dissociates sports prediction from financial wagering. It operates strictly as a real-time, skill-based intuition game:

// Non-Custodial Identity LayerThe connected Solana wallet acts solely as an Ed25519 identity anchor. It signs session tokens and links global leaderboard streaks. It never deposits, holds, or risks user funds.

// Mathematical Verification (TxLINE Merkle Proofs)Resolutions are not asserted by an opaque server. Each resolved challenge fetches an immutable Merkle inclusion proof directly from TxLINE’s on-chain oracle endpoints, allowing any participant or auditor to verify that the underlying event occurred.

// The CrowdBrain Reputation EngineInstead of compiling a single numerical score, the engine computes specialized categorical reputation indices (Next Goal Accuracy, Cards, Corner Readings), establishing a verifiable record of fan intuition.

“Octopus Crowd is not a sportsbook in disguise. It is a real-time engagement layer for sports media brands built on live, cryptographically verifiable telemetry.”— Vinicius Pontual, Project Demonstration

03. Demonstration: Match Room & Real-Time Execution

Live run illustrating real match telemetry consumption, automatic challenge initiation, instantaneous zero-intervention resolution, and Merkle verification:

TXLINE × SOLANA WORLD CUP HACKATHON // TECHNICAL SUBMISSIONDirect YouTube Link [›]

04. Pipeline Architecture: Ephemeral Ingestion & Edge Sync

To maintain high throughput without incurring continuous infrastructure server costs, the pipeline decouples data consumption from frontend presentation:

  • TxLINE Live SSE Consumers: A dedicated Node 22 worker binds to TxLINE's Server-Sent Events stream (/api/scores/stream). It consumes event deltas including kickoffs, periodic ticks, yellow/red bookings, and confirmed goals.
  • Ephemeral GitHub Actions Workers: Rather than paying for an always-on VPS, worker instances are orchestrated via GitHub Actions workflows triggered during active match schedules.
  • Neon Serverless Postgres: Raw events are written immediately to Neon Postgres connection pools. When a goal event triggers, the worker resolves open challenges in an atomic SQL transaction and dispatches the next micro-challenge simultaneously.
  • Next.js 16 Edge API Routes: Frontend clients consume normalized challenge state through lightweight API routes authenticated via Solana wallet signatures.

05. Front-Running Defense & API Integrity

Micro-prediction games face exploitation from latency arbitrage and client-side clock tampering. Octopus Crowd enforces defensive guarantees:

01 / Oracle Server Timestamp Locking: Prediction windows are validated strictly against the TxLINE server-emitted timestamp. Client system clocks are completely disregarded, eliminating local clock manipulation attacks.
02 / Secret Token Isolation: Long-lived TxLINE authentication bearer tokens reside exclusively within backend environment variables; client web bundles never touch or expose upstream credentials.
03 / Atomic Wallet Idempotency: Submissions enforce a unique constraint index on `(wallet_address, challenge_id)`. Race conditions designed to place divergent predictions across multiple tabs are dropped by Postgres unique constraints.

06. Specifications & Live Deployment Endpoints

Technical artifacts and core dependencies utilized in the live build:

ComponentSpecification / Endpoint
Telemetry ProviderTxLINE Live Oracle (Scores & Odds SSE)
Proof EndpointGET /api/scores/stat-validation (Merkle Proof)
Runtime StackNext.js 16 App Router, Turbopack, Tailwind CSS 4
Database ArchitectureNeon Serverless Postgres (@neondatabase/serverless)
Test CoverageVitest unit suite validated on real goal payloads
ENGINE TEST RUN: pnpm --filter core exec vitest run
DEPLOYMENT PROFILE: Vercel (Web / Edge API) + GitHub Actions Scheduled Ingestion Worker
// ENGINEERING DOSSIERS

Explore More Projects

All 13 Projects →