Win/Loss Verification

Win–Loss Recording Model

Win–loss verification describes how each resolved game outcome is translated into a deterministic balance movement within the GMG Engine ledger. The system does not evaluate randomness quality or game math; it verifies that the numerical result reported by a provider is applied consistently, arithmetically, and traceably to the player balance.

Outcome Normalization

All game outcomes are normalized into a common settlement representation before ledger application. Stakes, payouts, and net results are converted into the engine’s internal accounting units, ensuring that different game types, currencies, or networks do not alter the verification logic.

Ledger Application Rules

For each completed round, the engine records the balance before the outcome, applies the net result, and records the balance after settlement. The win or loss state is therefore derived from ledger arithmetic rather than from visual game indicators or screenshots.

Verification Properties

A win–loss record is considered verifiable when the reported outcome can be replayed against the ledger to reproduce the same balance transition. Any mismatch between expected and actual balance movement is treated as an exception rather than silently corrected.

Failure and Exception Handling

If provider data is incomplete, delayed, or inconsistent, the engine does not infer a result. Such cases are flagged for review, preserving ledger integrity and preventing unverified balance changes from being finalized.

Scope and Dependencies

This page is a derivative specification within GMG Engine. It does not define or redefine core primitives such as settlement, determinism, finality, proof, or exception handling. All authoritative definitions are inherited from the locked GMG Engine core primitives.

Related Core Primitives

This page depends on the authoritative definitions established in: Deterministic Outcomes, Settlement Ledger Format, Settlement Finality, Transaction Proof.