Patent 11756371

Derivative works

Defensive disclosure: derivative variations of each claim designed to render future incremental improvements obvious or non-novel.

Active provider: Google · gemini-2.5-flash

Derivative works

Defensive disclosure: derivative variations of each claim designed to render future incremental improvements obvious or non-novel.

✓ Generated

Defensive Disclosure: Derivatives of US Patent 11756371

This document outlines several derivative works and technical disclosures for US Patent 11756371, titled "Systems, methods, and media for implementing internet-based wagering." The purpose of this disclosure is to establish prior art, potentially rendering future incremental improvements by competitors as obvious or non-novel, thereby limiting the scope of claims related to internet-based roulette wagering with pre-selected enhanced payouts.

The core inventive concept of US11756371 involves a system where, prior to a roulette ball landing, a hardware processor randomly or pseudo-randomly selects one or more positions on a roulette wheel to receive an increased payout. If a bet is placed on such a selected position and the ball lands there, the player receives this enhanced payout, which is greater than the standard payout for that position. This disclosure expands upon this core concept across various technical axes.


Combination Prior Art Scenarios

The mechanisms described in US11756371, particularly those related to real-time interaction, video streaming, and managing player bets and payouts, can be combined with existing open-source standards to demonstrate obviousness or enhance the prior art landscape.

  1. US11756371 + WebSockets Standard (RFC 6455):
    The real-time communication requirements for streaming live video (via encoder 116 to player devices 130, 132, 134), receiving bet information (at core application computer 108 from player devices), and displaying dynamic payout updates and visual effects (on game display 136 and player devices) are ideally suited for the WebSocket protocol. Integrating WebSockets (defined by RFC 6455) for all client-server communication between player devices and the core application computer (108) would allow for persistent, full-duplex communication channels. This enables significantly lower latency for bet placement, instant notification of selected increased payout positions, seamless delivery of visual effect triggers (e.g., lightning effects on game display 136 via audiovisual control system 122 and LED driver 124), and efficient real-time updates for game state, eliminating the overhead of traditional HTTP polling and enhancing the "live" interactive experience described in the patent.

  2. US11756371 + Open Gaming Architecture (OGA) Standard:
    The system described in US11756371 includes various networked components like dealer computer 106, core application computer 108, and player devices 130, 132, 134. Implementing the game logic, bet management, and payout determination (all handled by core application computer 108) within a framework compliant with an Open Gaming Architecture (OGA) standard, such as those promoted by organizations like the Gaming Standards Association (GSA), would allow for interoperability with diverse casino management systems or third-party game modules. For example, the random selection of increased payout positions and subsequent payout determination could be a distinct OGA-compliant service module communicating with a broader OGA-compliant roulette game engine. This modular approach, leveraging standardized communication protocols and data formats (e.g., XML or JSON over TCP/IP), ensures that the enhanced payout feature can be readily integrated into existing or future multi-vendor gaming environments, both online and in physical casinos.

  3. US11756371 + HTML5 Canvas API:
    The presentation of graphical user interfaces (e.g., interface 300) on player devices (130, 132, 134), including a simulated roulette board (area 310) and visual effects (e.g., lightning effects 402, 502), can be robustly implemented using the HTML5 Canvas API. Instead of relying solely on pre-rendered images or basic HTML elements, the Canvas API allows for dynamic, programmatic rendering of complex graphics, animations, and interactive elements directly within a web browser. The core application computer 108 would transmit data representing the roulette board state, selected positions, and visual effect triggers (e.g., coordinates for lightning strikes, "500x" indicators). The player devices would use JavaScript and the Canvas API to render these elements with high fidelity and fluid animations, providing a rich and engaging user experience that can scale across different device resolutions and form factors, eliminating the need for plugins and leveraging standard web technologies for the graphical presentation described in FIGS. 3, 4, and 5 of the patent.


Derivative Variations

The following derivatives expand on the core claims of US11756371, proposing alternative implementations and applications.

1. Material & Component Substitution

Derivative 1.1: Fully Virtualized, Physics-Engine-Driven Roulette Simulation

Enabling Description:
Instead of a physical roulette wheel (102) and ball, the system (100) utilizes a fully virtualized, high-fidelity 3D physics engine running on core application computer 108. The wheel sensor (104) is replaced by the physics engine's deterministic outcome calculation. The processor (602) within core application computer (108) is specifically tuned for real-time physics simulation, potentially augmented by a dedicated Graphics Processing Unit (GPU) for rendering and physics acceleration. The "spinning" action (206) and "ball drop" detection (214) are entirely simulated within the software, guaranteeing a controlled environment for random or pseudo-random selection of increased payout positions (210) while maintaining the visual realism for players on devices (130, 132, 134). The virtual environment allows for dynamic real-time alteration of wheel properties (e.g., friction, ball velocity) to fine-tune game characteristics, without affecting the provable fairness derived from the pseudo-random number generator for payout selection.

graph TD
    A[Player Device] -- Bet Info --> B(Core Application Computer)
    B -- Virtual Spin/Drop Calc --> C{Physics Engine}
    C -- Outcome --> D{Random Payout Selector}
    D -- Selected Payout Positions --> B
    B -- Game State + Payouts --> E[Virtual Roulette Wheel 3D Model]
    E -- Rendered Video Stream --> F[Video/Audio Encoder]
    F -- Encoded Stream --> A
    D -- Applicable Payout --> G(Payout Processor)
    G -- Payout Confirmation --> A
Derivative 1.2: Multi-Spectral Imaging for Wheel/Ball Detection with AI Analysis

Enabling Description:
Wheel sensor 104 is replaced by a multi-spectral imaging array, comprising an infrared (IR) camera, an ultraviolet (UV) camera, and a high-frame-rate visible light camera (all part of cameras 112, 114, or dedicated sensors). This array continuously captures images of the roulette wheel (102) and ball. The data is fed into a dedicated image processing unit, potentially a Field-Programmable Gate Array (FPGA) or a specialized AI accelerator (e.g., Google's Tensor Processing Unit, TPU), connected to dealer computer 106 or directly to core application computer 108. An AI model (e.g., a Convolutional Neural Network trained for object detection and tracking) analyzes the multi-spectral data to precisely detect the wheel's rotation, ball's trajectory, and final landing position (214), even under varying lighting conditions or obfuscation attempts. The multi-spectral data provides redundancy and enhanced accuracy, improving the robustness of the physical game environment's input for the digital processing of increased payouts. The core application computer (108) then uses this high-precision data for determining applicable payouts (212) based on the randomly selected positions (210).

graph TD
    A[Roulette Wheel + Ball] -- Multi-Spectral Light --> B[IR Camera]
    A -- Visible Light --> C[Visible Camera]
    A -- UV Light --> D[UV Camera]
    B -- Raw Data --> E(Image Processing Unit/AI Accelerator)
    C -- Raw Data --> E
    D -- Raw Data --> E
    E -- Processed Position Data --> F(Core Application Computer)
    F -- Random Payout Selection --> G(Increased Payout Logic)
    G -- Payout Determination --> F
    F -- Streamed Data/Video --> H[Player Device]
Derivative 1.3: Electro-Optical Matrix Display for Dynamic Position Highlighting

Enabling Description:
LED matrix 126, which is stated to be a "collection of one or more LEDs, lights, and/or any other visual effects" around the wheel, is specifically implemented as a micro-LED or Organic Light-Emitting Diode (OLED) display matrix integrated directly into the surface of the roulette wheel stator (the non-rotating part) and/or the number pockets. This electro-optical matrix is controlled by LED driver 124, which in turn receives commands from audiovisual control system 122 and core application computer 108. When positions are randomly selected for increased payouts (210), this matrix dynamically illuminates or changes the color/texture of the specific chosen number pockets and/or betting areas in real-time. This provides a visually immersive and direct indication of the bonus positions, visible both in the live video stream (captured by cameras 112, 114) and on the physical wheel itself, thereby enhancing player engagement (as described in FIG. 4 and 5).

graph TD
    A(Core Application Computer) -- Payout Selection Data --> B(Audiovisual Control System)
    B -- Lighting Commands --> C(LED Driver)
    C -- Electrical Signals --> D[Electro-Optical Matrix Display (on Wheel)]
    D -- Visual Effect --> E[Cameras 112, 114]
    E -- Video Stream --> F(Video/Audio Encoder)
    F -- Encoded Stream --> G[Player Device]

2. Operational Parameter Expansion

Derivative 2.1: Hyper-Volatility Mode with Extreme Payout Scaling

Enabling Description:
The system (100), specifically core application computer 108, implements a "Hyper-Volatility Mode" where the number of randomly selected positions (210) for increased payouts is significantly reduced (e.g., only one position out of 37/38) but the corresponding payout multipliers (212) are dramatically escalated, ranging from 999:1 up to 9999:1. Conversely, the non-selected payout (212) for all other positions is reduced to a very low ratio, e.g., 1:1, to offset the extreme bonus payouts and maintain a predetermined house edge. This mode is explicitly advertised to players via the graphical user interface (300) on player devices, allowing them to opt into games with higher risk and potentially astronomical rewards. The pseudo-random number generator (210) is biased to select fewer positions, and a dynamic payout calculation module (part of core application computer 108) adjusts all other payouts to compensate, ensuring actuarial balance.

graph TD
    A[Player Device] -- Mode Selection + Bet --> B(Core Application Computer)
    B -- Activate Hyper-Volatility --> C{Random Payout Selector}
    C -- Select 1 Position (e.g., 1 in 37) --> D(Payout Determination Logic)
    D -- Max Payout (9999:1) for Selected --> D
    D -- Min Payout (1:1) for Non-Selected --> D
    D -- Display Payouts + Game Start --> E[Game Display / Player Device]
    E -- Spin & Ball Drop --> F{Wheel Sensor}
    F -- Outcome --> D
    D -- Final Payout Calc --> G(Player Account Management)
Derivative 2.2: Adaptive Payout Selection Based on Player Behavior Analytics

Enabling Description:
Core application computer 108 includes an "Adaptive Payout Selection Module" integrated with a player behavior analytics engine. This engine, leveraging machine learning algorithms (e.g., reinforcement learning or collaborative filtering), continuously analyzes aggregated and individual player betting patterns, session durations, and engagement metrics (e.g., from player devices 130, 132, 134). Based on this analysis, the system dynamically adjusts the parameters for randomly selecting increased payout positions (210) and determining payouts (212) for subsequent spins. For example, if player engagement is low, the system might increase the frequency or magnitude of increased payouts to a wider range of positions to stimulate interest. If certain numbers are historically under-bet, the system could temporarily increase their probability of being selected for a bonus payout to encourage diverse betting. This optimization aims to maximize player retention and lifetime value while maintaining a long-term house advantage.

graph TD
    A[Player Devices] -- Player Behavior Data --> B(Player Analytics Engine)
    B -- Engagement Metrics --> C(Adaptive Payout Selection Module)
    C -- Adjust Selection/Payout Params --> D{Random Payout Selector}
    D -- Selected Positions + Payouts --> E(Core Application Computer)
    E -- Game Execution --> F[Roulette Wheel]
    F -- Outcome --> E
    E -- Payout to Player --> G[Player Account]
Derivative 2.3: Multi-Stage Payout Escalation with Bet Thresholds

Enabling Description:
The system (100) introduces a multi-stage payout escalation mechanism. When positions are randomly selected (210) for increased payouts, these payouts are initially set at a base increased rate (e.g., 49:1). However, if the collective wager amount on a specific selected position (or a group of selected positions) by all players exceeds a predefined threshold (monitored by core application computer 108 from bet information received at 204), the payout for that position automatically "escalates" to a higher tier (e.g., 99:1, then 199:1, up to 499:1). This escalation occurs prior to the ball landing and is visually communicated to players through enhanced effects on game display 136 and player device interfaces. This encourages higher stakes and creates a dynamic, competitive betting environment, where players collectively influence potential bonus rewards.

graph TD
    A[Player Device] -- Bet Info (204) --> B(Core Application Computer)
    B -- Receive Bet Info --> C{Random Payout Selector (210)}
    C -- Select Positions & Base Payouts --> D(Bet Threshold Monitor)
    D -- Current Bets on Selected Positions --> E{Evaluate Threshold}
    E{Threshold Met?} -- Yes --> F(Payout Escalation Logic)
    F -- New Higher Payouts --> G(Payout Display Module)
    E{Threshold Met?} -- No --> G
    G -- Display Dynamic Payouts (212) --> H[Game Display / Player Device]
    H -- Spin & Ball Drop (206, 214) --> I(Payout Determination)
    I -- Final Payout --> J[Player Account]

3. Cross-Domain Application

Derivative 3.1: Lottery System with Pre-Selected Bonus Numbers

Enabling Description:
The mechanism is applied to an internet-based lottery system. A hardware processor (analogous to core application computer 108) receives digital lottery ticket purchases from player devices (analogous to 130, 132, 134). Prior to the drawing of the winning numbers, the processor randomly or pseudo-randomly selects a subset of potential lottery numbers (e.g., 5 numbers out of a pool of 49) to be "bonus numbers." If a player's ticket matches one of these pre-selected bonus numbers in addition to the regular winning numbers, the payout for that match is substantially increased (analogous to the first increased payout in roulette). This selection of bonus numbers and the increased payout structure is clearly communicated to players before the draw. The "ball landing" is analogous to the draw outcome.

graph TD
    A[Player Device] -- Buy Lottery Ticket --> B(Lottery Server)
    B -- Receive Tickets --> C{Random Bonus Number Selector}
    C -- Select Bonus Numbers (Pre-Draw) --> D(Payout Multiplier Logic)
    D -- Define Bonus Payouts --> B
    B -- Notify Players of Bonus Numbers --> A
    B -- Initiate Number Draw --> E{Lottery Draw System}
    E -- Winning Numbers --> B
    B -- Match & Payout Calculation --> D
    D -- Apply Bonus if Matched --> B
    B -- Distribute Winnings --> A
Derivative 3.2: Financial Market Prediction Game with Dynamic Asset Boosts

Enabling Description:
The system (100) is adapted for a financial market prediction game. Players use player devices (130, 132, 134) to place bets on the predicted movement (e.g., up/down, specific price target) of various financial assets (e.g., stocks, cryptocurrencies, commodities) within a specified timeframe. A hardware processor (core application computer 108) prior to the market closing or the prediction window ending, randomly or pseudo-randomly selects certain assets or specific prediction outcomes (e.g., "AAPL stock goes up by >2%") to receive an "enhanced odds multiplier" for that round. If a player placed a bet on such a pre-selected, boosted outcome and it materializes, their payout is significantly higher than standard. The "ball landing" is analogous to the final market outcome for the prediction.

graph TD
    A[Player Device] -- Place Prediction Bet --> B(Prediction Game Server)
    B -- Receive Bets --> C{Random Asset/Outcome Booster}
    C -- Select Boosted Outcomes (Pre-Event) --> D(Odds Multiplier Engine)
    D -- Apply Enhanced Multipliers --> B
    B -- Display Boosted Outcomes --> A
    B -- Monitor Market Outcome --> E{Market Data Feed}
    E -- Final Outcome --> B
    B -- Determine Winning Bets & Payouts --> D
    D -- Apply Boosted Payouts --> B
    B -- Settle Bets --> A
Derivative 3.3: Esports Betting with Live Event Odds Boosts

Enabling Description:
This mechanism is applied to an internet-based esports betting platform. Players place wagers on specific in-game events or outcomes (e.g., "Team A wins first blood," "Player X achieves a triple kill," "Total kills over 20") in a live esports match, using player devices (130, 132, 134). A hardware processor (core application computer 108), prior to the commencement of the match or a specific critical in-game phase, randomly or pseudo-randomly selects certain in-game events or specific outcomes to have "boosted odds." These boosted odds provide a significantly increased payout if the selected event occurs and a player has wagered on it. The "ball landing" is analogous to the specific in-game event or match outcome occurring. Visual effects and announcements (similar to game display 136) can highlight these boosted events to viewers/bettors.

graph TD
    A[Player Device] -- Place Esports Bet --> B(Esports Betting Platform)
    B -- Receive Bets --> C{Random Event/Outcome Booster}
    C -- Select Boosted Events (Pre-Match/Phase) --> D(Odds Calculation Engine)
    D -- Apply Enhanced Odds --> B
    B -- Announce Boosted Events --> A
    B -- Monitor Live Esports Match --> E{Live Game Data Feed}
    E -- In-Game Events --> B
    B -- Determine Winning Bets & Payouts --> D
    D -- Apply Boosted Payouts --> B
    B -- Settle Bets --> A

4. Integration with Emerging Tech

Derivative 4.1: AI-Driven Dynamic Payout Optimization

Enabling Description:
Core application computer 108 integrates an AI-driven "Dynamic Payout Optimization Engine." This engine, using advanced machine learning models (e.g., deep reinforcement learning), analyzes vast datasets including historical game outcomes, player demographics, betting patterns, and real-time game liquidity. Its objective is to dynamically determine the optimal number of positions to select for increased payouts (210), the magnitude of these payouts (212), and the inverse adjustment to non-selected payouts. The AI's decisions are designed to balance factors such as player engagement, perceived fairness, long-term house edge, and short-term volatility management. The AI continuously learns and adapts its strategy, optimizing the game's economic parameters in real-time, delivering payout instructions to the random payout selector within core application computer 108 prior to each spin.

graph TD
    A[Historical Game Data] -- Training Data --> B(AI Payout Optimization Engine)
    C[Real-time Player Data] -- Input --> B
    D[Game Liquidity Data] -- Input --> B
    B -- Optimal Payout Parameters --> E(Core Application Computer)
    E -- Apply to Random Payout Selection (210) --> F{Payout Determination Logic}
    F -- Dynamic Payouts (212) --> G[Game Display / Player Device]
    G -- Player Action --> C
Derivative 4.2: IoT-Enhanced Environmental Triggered Bonuses

Enabling Description:
The physical casino studio (where roulette wheel 102 and dealer are located) is equipped with an array of IoT sensors (e.g., ambient light sensors, temperature sensors, acoustic sensors for crowd noise, air quality sensors), networked via computer network 128 to audiovisual control system 122 and core application computer 108. These sensors provide real-time environmental data. The core application computer (108) includes a module that prior to the spin, can use thresholds or patterns detected in this IoT data to trigger or modify the increased payout selection (210). For example, if crowd excitement (detected by acoustic sensors) reaches a peak, the system might trigger a "hot streak" where more positions or higher payouts are selected for the next spin. This adds an external, contextual layer of randomness and excitement to the game, connecting the physical environment directly to the digital bonus mechanism.

graph TD
    subgraph Casino Studio
        A[Roulette Wheel]
        B[Ambient Light Sensor]
        C[Temperature Sensor]
        D[Acoustic Sensor]
    end

    A --- E(Wheel Sensor)
    B --- F(IoT Gateway)
    C --- F
    D --- F

    F -- Real-time Environmental Data --> G(Computer Network 128)
    G -- Data Stream --> H(Core Application Computer 108)
    H -- Environmental Triggers --> I{Random Payout Selector (210)}
    I -- Enhanced Payout Selection --> J(Payout Determination Logic)
    J -- Payouts & Visual Effects --> K[Game Display / Player Device]
Derivative 4.3: Blockchain-Verified Provably Fair Payout Selection

Enabling Description:
The random or pseudo-random selection of increased payout positions (210) and the determination of their values (212) is performed using a provably fair system underpinned by blockchain technology. Core application computer 108 interacts with a decentralized oracle network (e.g., Chainlink) or directly with a smart contract on a public blockchain (e.g., Ethereum, Avalanche). Prior to the ball landing, a cryptographic hash of the random seed used for payout selection, combined with a block hash from the blockchain, is committed to the blockchain. After the spin and ball drop, the full random seed is revealed, allowing players on devices (130, 132, 134) to independently verify the fairness of the bonus selection process against the on-chain commitment. This provides immutable transparency for the increased payout mechanism, building player trust beyond a centralized pseudo-random number generator.

sequenceDiagram
    participant P as Player Device
    participant CAS as Core Application Server (108)
    participant DRN as Decentralized Randomness Network / Oracle
    participant BC as Blockchain

    P->>CAS: Place Bet
    CAS->>DRN: Request Provably Fair Seed (Pre-Spin)
    DRN->>CAS: Provide Random Seed Hash
    CAS->>BC: Commit Random Seed Hash
    CAS->>CAS: Randomly Select Payout Positions (using seed)
    CAS->>P: Display Selected Payout Positions (210)
    CAS->>CAS: Initiate Roulette Spin (206)
    CAS->>CAS: Determine Ball Drop (214)
    CAS->>DRN: Request Random Seed Reveal
    DRN->>CAS: Reveal Random Seed
    CAS->>BC: Publish Random Seed
    CAS->>P: Payout Notification & Verification Link
    P->>BC: Verify Payout Selection (Optional)

5. The "Inverse" or Failure Mode

Derivative 5.1: Graceful Degradation to Standard Play (Low-Power/Limited-Functionality)

Enabling Description:
The core application computer 108 continuously monitors system health, network latency (of computer network 128), and processing load (of hardware processor 602). In the event of detected degraded performance (e.g., high network congestion, excessive CPU utilization, or partial failure of audiovisual control system 122), the system automatically enters a "Graceful Degradation Mode." In this mode, the random selection of increased payout positions (210) is temporarily suspended or significantly reduced (e.g., only one position with a minimal boost). Visual effects (LED matrix 126, game display 136) associated with bonus payouts are disabled or simplified. The game defaults to standard roulette payouts for all positions. Player devices (130, 132, 134) are immediately notified of the degraded state via the user interface (300). This ensures continuous play with standard rules, prioritizing availability over the enhanced bonus feature, and prevents potential inconsistencies or errors arising from system strain.

stateDiagram-v2
    state NormalOperation {
        [*] --> Initialize
        Initialize --> MonitorSystem
        MonitorSystem --> SelectBonusPayouts
        SelectBonusPayouts --> ConductGameRound
        ConductGameRound --> MonitorSystem
        MonitorSystem --> DegradedMode : [System Health < Threshold]
    }

    state DegradedMode {
        [*] --> NotifyPlayersDegraded
        NotifyPlayersDegraded --> DefaultToStandardPayouts
        DefaultToStandardPayouts --> SimplfiedVisuals
        SimplfiedVisuals --> ConductGameRoundDegraded
        ConductGameRoundDegraded --> MonitorSystemDegraded
        MonitorSystemDegraded --> NormalOperation : [System Health > Threshold]
    }
Derivative 5.2: Fail-Safe Payout Reversion with Automated Audit

Enabling Description:
The system (100) incorporates a "Fail-Safe Payout Reversion" mechanism for the increased payout feature. Core application computer 108, in conjunction with dealer computer 106, employs redundant internal checks and external verification (e.g., checksums, independent random number generation processes). If any discrepancy or error is detected in the random selection (210), payout determination (212), or ball landing detection (214) that could compromise the integrity of the increased payout for a given spin, the system automatically defaults all payouts for that specific spin to the first non-selected payout (i.e., the standard payout rate). An automated audit log (stored in storage 606) is immediately generated, detailing the detected failure and the reversion event. Players are notified on their devices (130, 132, 134) that due to an integrity check, the bonus payouts for the round were nullified and standard payouts applied, with an option to view the audit log details for transparency.

graph TD
    A(Core Application Computer) -- Trigger Spin --> B{Random Payout Selector (210)}
    B -- Proposed Increased Payouts --> C(Integrity Verification Module)
    C -- Check Randomness, Payout Rules --> D{Error Detected?}
    D -- Yes --> E(Fail-Safe Payout Reversion)
    E -- Default to Standard Payouts --> F(Payout Processor)
    E -- Generate Audit Log --> G(Storage 606)
    D -- No --> H(Payout Determination Logic)
    H -- Apply Increased Payouts --> F
    F -- Notify Players --> I[Player Device]
Derivative 5.3: Limited Preview/Demonstration Mode

Enabling Description:
The system (100) provides a "Limited Preview/Demonstration Mode" accessible by new players or as a public promotional tool. In this mode, players on devices (130, 132, 134) can observe game rounds and the increased payout selection process without placing real money bets. The core application computer (108) still performs the random selection of increased payout positions (210) and determines payouts (212), and these are visually presented on the game display (136) and player interfaces. However, the system bypasses the bet reception (204) and payout distribution (214) steps for these demonstration rounds. This allows prospective players to experience the unique bonus feature and understand its mechanics before committing real funds, without affecting the underlying random selection algorithms or live game operations. The system uses a dedicated flag in the session state to differentiate between real and demonstration plays.

stateDiagram-v2
    state PlayerSession {
        [*] --> GuestUser
        GuestUser --> RealMoneyPlayer : [Login & Deposit]
        GuestUser --> DemoMode : [Select "Play Demo"]

        state DemoMode {
            [*] --> ObserveGameFlow
            ObserveGameFlow --> RandomBonusSelectionVisible
            RandomBonusSelectionVisible --> SimulateSpinOutcome
            SimulateSpinOutcome --> ShowHypotheticalPayouts
            ShowHypotheticalPayouts --> ObserveGameFlow : [Next Round]
            DemoMode --> GuestUser : [Exit Demo]
        }

        state RealMoneyPlayer {
            [*] --> Authenticate
            Authenticate --> PlaceBets
            PlaceBets --> RandomBonusSelectionActive
            RandomBonusSelectionActive --> LiveSpinOutcome
            LiveSpinOutcome --> ProcessRealPayouts
            ProcessRealPayouts --> PlaceBets : [Next Round]
        }
    }

Generated 5/16/2026, 12:49:23 AM