Oracle And Hybrid Games
Not every game that fits Midgard will be fully onchain or fully native to Starknet.
Midgard still wants an oracle or hybrid path for games that are:
- off-chain
- semi-onchain
- on another chain
- not yet ready to implement the full Starknet-native flow
Why this matters
Section titled “Why this matters”Midgard works best with games that produce clear scores and short sessions.
That includes a much wider set of games than the current Starknet-native ecosystem alone. If Midgard only supported fully onchain Starknet games, a large part of the design space would stay closed.
Current state
Section titled “Current state”The current live contract path is still the Starknet-native one:
- factories create sessions through a game contract
- challenges create sessions through a game contract
- activation and settlement read score and
game_overdirectly from that contract
The frontend contains experimental local game surfaces, but those are not yet a published contract-supported builder path for hybrid or off-chain games.
What the oracle path is for
Section titled “What the oracle path is for”The custom oracle is meant to let Midgard work with games that cannot rely on Starknet contracts alone for score truth.
That includes:
- browser games that run off-chain
- games with a mix of off-chain gameplay and onchain settlement
- games hosted on other chains
- games that want Midgard’s market layer without rewriting their core runtime for Starknet
How to think about the architecture
Section titled “How to think about the architecture”Starknet-native games
Section titled “Starknet-native games”Use the standard embeddable route described in Game Integration and in the official Provable Games EGS docs.
Hybrid and external games
Section titled “Hybrid and external games”Use the oracle path.
The oracle layer is intended to:
- attest to the session being valid
- provide the score Midgard should settle against
- let Midgard preserve the same factory and challenge economics even when gameplay happens elsewhere
What this unlocks
Section titled “What this unlocks”This is the path that makes Midgard bigger than a Starknet-only game adapter.
It opens the door to:
- Midgard-native arcade games that are mostly off-chain
- semi-onchain games with stronger UX than pure contract execution
- game studios outside Starknet that still want score-backed challenge markets
Practical guidance
Section titled “Practical guidance”If you are building a fully onchain Starknet game, start with Game Integration.
If you are building something hybrid, off-chain, or cross-chain, treat the oracle route as a roadmap conversation with the Midgard team rather than a ready-made integration surface today.