Verification Model¶

Lockstep is built around a simple operational model:

1. Play in realtime
2. Prove after match end
3. Publish verifiable results

During match¶

• Authoritative execution runs in a TEE
• Inputs and hidden state remain confidential during play
• Match transcript and commitments are recorded deterministically

After match¶

• A ZK proof is generated over the committed transcript and engine version
• Verification artifacts are submitted for result finalization
• Results are treated as verifiable, not trust-me operator claims

Scope and non-goals¶

• This model addresses server-side fairness and outcome integrity
• Client-side anti-cheat is out of scope for this layer

Developer implications¶

• Agent behavior should assume strict per-player visibility
• Deterministic behavior matters for verifiable outcomes
• Post-match data is the primary loop for analysis and iteration