bOS v3.0 — Multi-Mode Gaming Platform
The Complete Game Modes Design Document
Version: 3.0 | Last Updated: January 2026 | Status: Design Phase Vision: One Platform, Multiple Ways to Play — Fantasy, Props, Trading, and Pools
Table of Contents
Overview
Game Modes
Technical Design
Implementation
1. Introduction
1.1 The Evolution of Fantasy Gaming
bOS v3.0 introduces a revolutionary multi-mode gaming platform that goes beyond traditional fantasy sports. Instead of offering just one way to engage with sports, we provide four distinct game modes that cater to different player preferences, skill levels, and engagement styles.
1.2 Why Multiple Game Modes?
| Benefit | Description |
|---|---|
| User Choice | Different users prefer different engagement styles |
| Higher LTV | More ways to play = more time on platform = higher lifetime value |
| Cross-Selling | Fantasy users discover props, casual users try trading |
| Risk Diversification | Not dependent on single game mode succeeding |
| Unique Positioning | No competitor offers all four modes in one platform |
| Continuous Engagement | Pre-match: Fantasy + Props. During match: Trading. Post-match: All settle |
1.3 The Four Game Modes at a Glance
| Mode | Description | Complexity | Engagement Window | Payout Model |
|---|---|---|---|---|
| Classic Fantasy | Pick team, earn points, compete in pools | Medium | Pre-match only | Rank-based prize pool |
| Player Props | Over/under predictions on player stats | Low | Pre-match only | Fixed multiplier (3x-25x) |
| Live Trading | Buy/sell outcome shares in real-time | High | Before + during match | Market-based (buy low, sell high) |
| Prediction Pools | Pick outcomes, crowd-set odds | Low | Pre-match only | Parimutuel (pool-based) |
2. The Multi-Mode Philosophy
2.1 One Match, Many Ways to Play
For any given match (e.g., MI vs CSK), users see a unified interface with all available game modes:
┌─────────────────────────────────────────────────────────────────┐
│ MI vs CSK — Starts in 2 hours │
│ Your Balance: 150 USDT │
├─────────────────────────────────────────────────────────────────┤
│ │
│ ┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐ │
│ │ CLASSIC FANTASY │ │ PLAYER PROPS │ │ LIVE TRADING │ │
│ │ ━━━━━━━━ │ │ ━━━━━━━━ │ │ ━━━━━━━━ │ │
│ │ │ │ │ │ │ │
│ │ Pick 11 │ │ Over/Under │ │ Buy/Sell │ │
│ │ Earn Points │ │ Quick Picks │ │ Real-Time │ │
│ │ Win Pool │ │ Up to 25x │ │ Dynamic Odds │ │
│ │ │ │ │ │ │ │
│ │ 15 contests │ │ 24 props │ │ Opens at toss │ │
│ │ [Enter] │ │ [Pick] │ │ [Preview] │ │
│ └─────────────────┘ └─────────────────┘ └─────────────────┘ │
│ │
│ ┌─────────────────┐ ┌─────────────────┐ │
│ │ PREDICTION POOL │ │ HEAD-TO-HEAD │ │
│ │ ━━━━━━━━ │ │ ━━━━━━━━ │ │
│ │ │ │ │ │
## 2.3 Cross-Mode Engagement Strategy
Users are encouraged to try multiple modes through:
1. **Progressive Disclosure** — New users start with Fantasy or Props, unlock Trading after engagement milestones
2. **Cross-Mode Bonuses** — "Play 3 modes this match, get 5% bonus on winnings"
3. **Unified Leaderboards** — "Top earner across all modes this week"
4. **Mode-Specific Tutorials** — Interactive guides for each game mode
---
# 3. Unified Platform Architecture
## 3.1 Shared Infrastructure
All game modes share core platform components:
```mermaid
flowchart TB
subgraph UserInterface[User Interface Layer]
TMA[Telegram Mini App]
Web[Web Dashboard]
API[Public API]
end
subgraph GameModes[Game Mode Engines]
FE[Fantasy Engine]
PE[Props Engine]
TE[Trading Engine]
PoolE[Pool Engine]
end
subgraph SharedCore[Shared Core Services]
Athletes[Athlete Database]
Events[Live Event Feed]
Scoring[Scoring Engine]
Wallet[Wallet Service]
Agent[Agent Commission]
end
subgraph Settlement[Settlement Layer]
USDT[USDT Payments]
Escrow[Escrow Service]
Payout[Payout Engine]
end
TMA --> FE & PE & TE & PoolE
Web --> FE & PE & TE & PoolE
API --> FE & PE & TE & PoolE
FE --> Athletes & Events & Scoring & Wallet
PE --> Athletes & Events & Wallet
TE --> Athletes & Events & Wallet
PoolE --> Athletes & Events & Wallet
Wallet --> USDT & Escrow
Scoring --> Payout
FE & PE & TE & PoolE --> Agent
3.2 Shared Data Model
All modes reference the same core entities:
| Entity | Description | Used By |
|---|---|---|
| Match | A sporting event with teams/players | All modes |
| Athlete | Individual player with stats | All modes |
| User | Platform user with wallet | All modes |
| Agent | Referral partner earning commission | All modes |
| Event | Real-time match event (run, wicket, goal) | Fantasy, Trading, Props |
3.3 Mode-Specific Data
Each mode has additional entities:
| Mode | Specific Entities |
|---|---|
| Fantasy | Contest, Entry, Team, Roster, Leaderboard |
| Props | PropLine, Pick, Slip, Outcome |
| Trading | Market, Share, Position, Trade, OrderBook |
| Pools | Pool, Prediction, Stake, PayoutTable |
4. Classic Fantasy
4.1 Overview
Classic Fantasy is the traditional DFS (Daily Fantasy Sports) experience familiar to Dream11 and DraftKings users. Players select a team of athletes within a salary cap and earn points based on real-world performance.
Key Characteristics:
- Pre-match team selection only (no changes after lock)
- Points accumulate based on athlete performance
- Compete in pools with other players
- Rank-based prize distribution
4.2 User Flow
4.3 Contest Types
| Type | Description | Entry Range | Pool Size |
|---|---|---|---|
| Mega Pool | Platform-wide, networked across agents | 5-50 USDT | 5,000-50,000 players |
| Agent Pool | Single agent's players only | 1-100 USDT | 50-500 players |
| Head-to-Head | 1v1 against another player | 5-1000 USDT | 2 players |
| Private League | Invite-only friends group | 5-100 USDT | 3-20 players |
| Guaranteed | Fixed prize regardless of entries | 10-100 USDT | Guaranteed by platform |
4.4 Scoring System
Scoring is sport-agnostic and config-driven. Example for Cricket T20:
| Action | Points |
|---|---|
| Run scored | +1 |
| Boundary (4) | +1 bonus |
| Six | +2 bonus |
| Half-century (50) | +8 bonus |
| Century (100) | +16 bonus |
| Wicket taken | +25 |
| Maiden over | +12 |
| Catch taken | +8 |
| Run out (direct) | +12 |
| Captain bonus | 2x points |
| Vice-Captain bonus | 1.5x points |
4.5 Prize Distribution
Standard prize structure for a 1000-player contest:
| Rank | Prize (% of pool) |
|---|---|
| 1st | 15% |
| 2nd | 8% |
| 3rd | 5% |
| 4th-10th | 2% each (14% total) |
| 11th-50th | 0.5% each (20% total) |
| 51st-200th | 0.15% each (22.5% total) |
| Total Distributed | 84.5% |
| Platform Rake | 15.5% |
5. Player Props
5.1 Overview
Player Props offer a simplified prediction experience where users pick over/under on specific player statistics. This mode is inspired by PrizePicks and Underdog Fantasy — both valued at $1B+ in the US market.
Key Characteristics:
- Binary decisions (OVER or UNDER)
- Fixed multiplier payouts (not pool-based)
- Combine multiple picks for higher multipliers
- Quick, low-friction experience
5.2 User Flow
PLAYER PROPS — MI vs CSK
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Build your slip (pick 2-6 props):
┌─────────────────────────────────────────────────┐
│ Rohit Sharma — Runs │
│ Line: 32.5 │
│ │
│ [OVER] [UNDER] │
│ │
│ Last 5 matches: 45, 28, 67, 31, 52 │
│ vs CSK average: 38.2 │
└─────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────┐
│ Jasprit Bumrah — Wickets │
│ Line: 1.5 │
│ │
│ [OVER] [UNDER] │
│ │
│ Last 5 matches: 2, 1, 3, 0, 2 │
│ vs CSK average: 1.8 │
└─────────────────────────────────────────────────┘
YOUR SLIP:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✓ Rohit Sharma Runs OVER 32.5
✓ Bumrah Wickets OVER 1.5
○ Pick 1 more for 3-pick payout...
Entry Amount: [10] USDT
PAYOUT TABLE:
┌────────────────────────────────────┐
│ 2 correct = 3x (30 USDT) │
│ 3 correct = 6x (60 USDT) │
│ 4 correct = 10x (100 USDT) │
│ 5 correct = 20x (200 USDT) │
│ 6 correct = 25x (250 USDT) │
└────────────────────────────────────┘
[Lock Picks]
5.3 Prop Types
| Category | Example Props |
|---|---|
| Batting | Runs, Boundaries, Strike Rate, Balls Faced |
| Bowling | Wickets, Economy Rate, Dot Balls, Maidens |
| Fielding | Catches, Run Outs |
| Team | Total Runs, Total Sixes, Highest Individual Score |
| Match | Winner, Margin, First Innings Score |
5.4 Line Setting
Lines are set by the platform using:
- Historical data — Player's recent performance
- Matchup data — Performance against specific opponent
- Venue data — Ground-specific statistics
- Conditions — Pitch report, weather
- Balancing — Adjust based on early pick distribution
5.5 Payout Structure
| Picks | All Correct Payout | Risk Level |
|---|---|---|
| 2 | 3x | Low |
| 3 | 6x | Low-Medium |
| 4 | 10x | Medium |
| 5 | 20x | High |
| 6 | 25x | Very High |
Insurance Option: For 20% higher entry, get 1 "miss" forgiven (e.g., 4/5 correct still pays).
6. Live Trading
6.1 Overview
Live Trading brings prediction market mechanics to sports, allowing users to buy and sell outcome shares in real-time as matches unfold. Inspired by Polymarket and Kalshi, this mode offers the highest engagement but also the highest complexity.
Key Characteristics:
- Continuous trading before and during matches
- Prices reflect real-time probability
- Buy low, sell high (or hold to settlement)
- Most engaging during live action
6.2 Market Structure
Each market represents a binary outcome question:
MARKET: Will Rohit Sharma score 50+ runs?
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Current State:
┌────────────────────────────────────────────────┐
│ │
│ YES $0.42 ████████░░░░░░░ NO $0.58 │
│ │
│ Buy YES = Bet Rohit scores 50+ │
│ Buy NO = Bet Rohit doesn't score 50+ │
│ │
│ If YES wins: Each YES share pays $1.00 │
│ If NO wins: Each NO share pays $1.00 │
│ │
└────────────────────────────────────────────────┘
Your Position: None
24h Volume: $12,450
Liquidity: $8,200
[Buy YES] [Buy NO]
6.3 Price Mechanics
Prices are determined by an Automated Market Maker (AMM) using a constant product formula:
Price_YES = Reserve_NO / (Reserve_YES + Reserve_NO)
Price_NO = Reserve_YES / (Reserve_YES + Reserve_NO)
Always: Price_YES + Price_NO = $1.00
Example:
- Pool has 1000 YES shares and 1500 NO shares
- Price_YES = 1500 / 2500 = $0.60
- Price_NO = 1000 / 2500 = $0.40
When user buys YES:
- They add to NO reserve
- They remove from YES reserve
- Price_YES increases
6.4 Live Trading Flow
6.5 Market Types
| Category | Example Markets |
|---|---|
| Match Outcome | Team A to win, Match to go to Super Over |
| Player Milestones | Player X scores 50+, Player Y takes 3+ wickets |
| Innings | First innings 180+, Powerplay 60+ |
| Specific Events | First ball six, Hat-trick in match |
| Live Props | Next over 10+ runs, Wicket this over |
6.6 Risk Controls
| Control | Description |
|---|---|
| Position Limits | Max $500 per market per user |
| Market Limits | Max $50,000 total liquidity per market |
| Trading Halts | Pause during controversial events (DRS, rain) |
| Slippage Protection | Max 5% slippage per trade |
| Cooldowns | 5-second minimum between trades |
7. Prediction Pools
7.1 Overview
Prediction Pools offer a parimutuel betting experience where users pick outcomes and odds are determined by the distribution of picks. The more people pick an outcome, the lower the payout.
Key Characteristics:
- Crowd-determined odds
- No "house edge" on odds
- Simple pick-and-play
- Social proof visible (see what others picked)
7.2 Pool Structure
PREDICTION POOL: Player of the Match
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Pool closes at toss | Current pool: 5,240 USDT
┌────────────────────────────────────────────────┐
│ Rohit Sharma ████████████ $1,820 (35%) │
│ If you pick: 2.9x payout │
├────────────────────────────────────────────────┤
│ Virat Kohli ████████ $1,150 (22%) │
│ If you pick: 4.5x payout │
├────────────────────────────────────────────────┤
│ Jasprit Bumrah ██████ $890 (17%) │
│ If you pick: 5.9x payout │
├────────────────────────────────────────────────┤
│ Ravindra Jadeja ████ $680 (13%) │
│ If you pick: 7.7x payout │
├────────────────────────────────────────────────┤
│ Other MI Players ██ $350 (7%) │
│ If you pick: 14.3x payout │
├────────────────────────────────────────────────┤
│ CSK Players ██ $350 (7%) │
│ If you pick: 14.3x payout │
└────────────────────────────────────────────────┘
Your pick: [Rohit Sharma ▼]
Amount: [25] USDT
If Rohit wins POTM, you receive: ~72.5 USDT
[Join Pool]
7.3 Parimutuel Math
Pool mechanics:
- All stakes go into a shared pool
- Platform takes 15% rake
- Remaining 85% distributed to winners proportionally
Payout calculation:
Your Payout = (Your Stake / Total Stake on Winner) × (Total Pool × 0.85)
Example:
- Total pool: 10,000 USDT
- You bet 100 USDT on Rohit
- Total on Rohit: 3,500 USDT
- Rohit wins POTM
- Your payout: (100 / 3500) × (10000 × 0.85) = 242.86 USDT
7.4 Pool Types
| Pool Type | Question Format | Example |
|---|---|---|
| Player of Match | Who will be POTM? | Pick from 22 players |
| Top Scorer | Who scores most runs? | Pick from batting lineup |
| Top Bowler | Who takes most wickets? | Pick from bowling lineup |
| Winning Margin | By how many runs/wickets? | Ranges (1-10, 11-20, etc.) |
| First Event | What happens first? | Boundary, wicket, dot ball |
8. Game Mode Engine Architecture
8.1 Engine Design
Each game mode has its own engine that plugs into the shared core:
8.2 Event Flow
All engines consume events from the shared Kafka stream:
| Event | Fantasy | Props | Trading | Pools |
|---|---|---|---|---|
match.started | Lock entries | Lock slips | Open markets | Lock pools |
ball.completed | Update scores | Check outcomes | Update prices | — |
player.milestone | Bonus points | Resolve props | Settle markets | — |
match.completed | Final settle | Final resolve | Close all | Settle pools |
8.3 Technology Stack
| Component | Technology | Justification |
|---|---|---|
| Fantasy Engine | TypeScript/Node.js | Existing expertise, good for I/O |
| Props Engine | TypeScript/Node.js | Simple logic, fast development |
| Trading Engine | Rust | Performance-critical, needs <10ms latency |
| Pool Engine | TypeScript/Node.js | Simple math, low complexity |
| Event Stream | Apache Kafka | Proven at scale, ordered delivery |
| Cache | Redis | Sub-ms reads for leaderboards/prices |
| Database | PostgreSQL | ACID compliance, complex queries |
9. Market Making & Liquidity
9.1 The Liquidity Challenge
Live Trading requires liquidity — someone must be on the other side of every trade. Options:
| Approach | Pros | Cons |
|---|---|---|
| Order Book (User-to-User) | No platform risk, true market | Needs critical mass, cold start problem |
| AMM (Platform-Backed) | Always liquid, simple UX | Platform takes price risk |
| Hybrid | Balance of both | Complex to implement |
Recommendation: Start with AMM for guaranteed liquidity, add order book features later.
9.2 AMM Design
We use a Constant Product Market Maker (CPMM) similar to Uniswap:
Invariant: x × y = k
Where:
- x = YES shares in pool
- y = NO shares in pool
- k = constant (until liquidity added/removed)
Initial Seeding:
- Platform seeds each market with $1,000 liquidity
- 500 YES + 500 NO shares (50/50 starting odds)
- Prices adjust as users trade
9.3 Platform Risk Management
| Risk | Mitigation |
|---|---|
| Directional exposure | Limit total platform liability per market |
| Black swan events | Reserve fund for extreme payouts |
| Manipulation | Position limits, trade velocity limits |
| Oracle failures | Multiple data sources, manual override |
10. Settlement & Payouts
10.1 Settlement Triggers
| Mode | Settlement Trigger | Settlement Time |
|---|---|---|
| Fantasy | Match completion | Within 5 minutes |
| Props | Individual stat finalized | Real-time as events occur |
| Trading | Market close (end of match/event) | Immediate |
| Pools | Outcome confirmed | Within 5 minutes |
10.2 Payout Flow
10.3 Dispute Handling
| Scenario | Resolution |
|---|---|
| Data feed error | Pause settlement, verify with backup sources |
| Match abandoned | Refund all entries/positions at original price |
| Player injury mid-match | Fantasy: points as-is. Props: refund if unresolved. |
| Controversial decision | Manual review, platform decision final |
11. Phased Rollout Plan
11.1 Phase Overview
11.2 Phase 1: Fantasy + Props (Weeks 1-10)
Deliverables:
- Classic Fantasy with networked pools
- Player Props with 2-6 pick slips
- Unified wallet and agent commission
Success Metrics:
- 1,000 daily active users
- 50 active agents
- $50,000 daily volume
11.3 Phase 2: Prediction Pools (Weeks 11-16)
Deliverables:
- Parimutuel pool engine
- 5+ pool types per match
- Real-time odds display
Success Metrics:
- 20% of users try pools
- $20,000 daily pool volume
11.4 Phase 3: Live Trading (Weeks 17-34)
Deliverables:
- AMM-based trading engine
- 10+ markets per match
- Real-time price feeds
- Position management UI
Success Metrics:
- $100,000 daily trading volume
- 500 active traders
12. Risk Management
12.1 Platform Risk Matrix
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| AMM losses | Medium | High | Position limits, reserve fund |
| Data feed failure | Low | High | Multiple providers, fallback |
| Regulatory action | Medium | Critical | Legal counsel, jurisdiction selection |
| Low liquidity | Medium | Medium | Platform seeding, incentives |
| Fraud/Collusion | Low | Medium | Velocity limits, ML detection |
12.2 Financial Controls
| Control | Description |
|---|---|
| Reserve Fund | 10% of volume set aside for extreme events |
| Daily Limits | Max $100,000 platform exposure per day |
| User Limits | Max $10,000 per user per mode per day |
| Automatic Hedging | IBO integration for large exposures |
13. Regulatory Considerations
13.1 Mode Classification
| Mode | Likely Classification | Rationale |
|---|---|---|
| Classic Fantasy | Skill game | Established precedent (Dream11 ruling) |
| Player Props | Skill game / Gray area | Similar to fantasy, outcome-based |
| Live Trading | Prediction market / Securities | May need specific licensing |
| Prediction Pools | Parimutuel betting | Regulated in many jurisdictions |
13.2 Jurisdiction Strategy
| Jurisdiction | Fantasy | Props | Trading | Pools |
|---|---|---|---|---|
| India | ✅ Legal | ⚠️ Gray | ❌ Likely not | ⚠️ Gray |
| USA (most states) | ✅ Legal | ✅ Legal | ⚠️ Varies | ❌ Illegal |
| UK | ✅ Legal | ⚠️ Licensed | ✅ Licensed | ⚠️ Licensed |
| Philippines | ✅ Legal | ⚠️ Gray | ⚠️ Gray | ⚠️ Gray |
| Crypto-native | ✅ | ✅ | ✅ | ✅ |
13.3 Compliance Approach
- Geo-fencing — Restrict modes by user location
- KYC tiers — Higher limits require more verification
- USDT-only — Avoid fiat banking regulations
- Skill classification — Emphasize skill elements in marketing
- Legal counsel — Jurisdiction-specific legal review
Appendix A: Glossary
| Term | Definition |
|---|---|
| AMM | Automated Market Maker — algorithm that provides liquidity |
| DFS | Daily Fantasy Sports |
| Parimutuel | Betting system where winners share the pool |
| Prop | Proposition bet on a specific outcome |
| Slip | Collection of picks that must all win |
| CPMM | Constant Product Market Maker (x × y = k) |
| Slippage | Difference between expected and executed price |
| Settlement | Process of determining winners and paying out |
Appendix B: API Endpoints (Summary)
Fantasy
POST /fantasy/contests— Create contestGET /fantasy/contests— List contestsPOST /fantasy/entries— Submit entryGET /fantasy/leaderboard/{contestId}— Get rankings
Props
GET /props/lines— Get available prop linesPOST /props/slips— Submit pick slipGET /props/slips/{id}— Check slip status
Trading
GET /trading/markets— List active marketsGET /trading/markets/{id}— Get market detailsPOST /trading/trades— Execute tradeGET /trading/positions— Get user positions
Pools
GET /pools— List active poolsGET /pools/{id}— Get pool details with oddsPOST /pools/predictions— Submit prediction
Document maintained by bOS Product Team. Last updated January 2026.
| User Type | Primary Mode | Secondary Mode | Characteristics |
|---|---|---|---|
| Hardcore Fantasy | Classic Fantasy | Props | Deep sport knowledge, time to research |
| Casual Fan | Props | Prediction Pools | Quick decisions, low time investment |
| Trader/Crypto Native | Live Trading | Props | Active during matches, likes volatility |
| Social Player | Prediction Pools | Head-to-Head | Plays with friends, community-driven |
| High Roller | Classic Fantasy | Live Trading | Large stakes, seeks big prize pools |