Session lifecycle
Mutual-claim result finalization
A match finalizes only when both participants independently claim the same outcome. Each result submission consumes a single-use session token bound to that user and match.Security boundaries
The SDK never
- verifies token signatures (the backend is the identity owner),
- holds or signs wallet private keys (custody uses multi-party computation),
- invents endpoints (all paths live in SDK core and mirror the backend controllers),
- decides a match outcome (it only submits the player’s claim).
Event plane
Events are buffered and flushed in batches over the event plane. The SDK subscribes to session, wallet, and status events and exposes them through a polling API. See Events & realtime.Environment integrity
Before a purchase, the SDK runs on-device checks (root/jailbreak, debugger, suspicious accessibility, screen capture, …). Any detected risk blocks the purchase client-side and reports anENV_COMPROMISED security event. The
computed level is one of SAFE, WARN, COMPROMISED. See
Environment integrity & anti-tamper.
