Settlement & verification
How a live fixture becomes an official result.
The lifecycle
The backend watches fixture windows, obtains validated price snapshots, and submits kickoff and end prices to the oracle. The contracts compute and record the outcome after the required data arrives. A result is final when the onchain settlement completes.
- Fixture scheduled
- Kickoff snapshot submitted
- Live score shown in the app
- End snapshot validated and submitted
- Onchain result settled
- Winning claims enabled
Pre-submit verification
Before submitting end prices, the backend independently recomputes the expected outcome with contract-equivalent integer math and simulates the oracle call. It aborts submission if the simulated contract result and independent calculation disagree.
Trust model
Onchain contracts make submissions and payouts inspectable. The backend still selects, validates and submits source prices, so its oracle role is material. The source-priority policy and deviation guard help make that role explicit; they do not make the price feed fully trustless.