# Anti-Cheat & Fair Play

![HISTORY app — every game session is logged + scoring is validated server-side](/files/V7nvHGzsbdsrV7Y2XYRv)

Snake OS uses both **synchronous preflight** and **async session analysis** to detect cheating.

## Synchronous Preflight (At Score Submission)

When your game ends and the score posts to `/api/scores/solo` or `/api/pvp/score`:

* Server checks game length vs minimum possible time for that score
* Validates tick rate (≥150ms floor — accounts for SPEED BOOST)
* Flags impossible "eat rates" (apples per second beyond physical reaction time)
* Rejects scores that violate any check before they hit the database

This closes the TOC/TOU window where a cheater could potentially insert a forged score and have it briefly visible.

## Async Session Analysis

After insertion, every game session is queued for deeper analysis:

* Input timing patterns (bot vs human signatures)
* Mouse/touch movement entropy
* Reaction-time distribution
* Cross-session anomalies (suspiciously identical session shapes)

Flagged sessions are marked `is_flagged=true` and excluded from PvP scoring + reward eligibility.

## Bans

Per the Terms:

* **Botting / scripted input** → immediate permanent ban, no refund of in-flight stakes
* **Wash-trading PvP** (matches with yourself via a second wallet) → ban + winnings clawed back
* **Client modifications** to bypass checks → ban + audit
* **Exploit reports** → bug-bounty rewards (responsible disclosure)

If you think your account was banned in error, report it in our support topic on [Telegram](https://t.me/snakeOS_sol) with your wallet address — every ban triggers an admin audit log we can review.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.snake-os.com/snake-game/anti-cheat.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.