# Accepting the Terms

After connecting your wallet, you'll see the Terms of Service modal. **Reading + accepting this is required before playing.**

## What You're Agreeing To

The full Terms are at [Terms of Service](/legal/tos.md), but the key points:

1. **You're 18+** and not in a sanctioned jurisdiction.
2. **You understand PvP wagers are real SOL** — your stake goes to our treasury wallet on match start, the winner gets 95% of the combined pot, 5% is the protocol fee.
3. **token is not live yet** — any "rewards" UI is a placeholder. No tokens accumulate during beta.
4. **Rewards require participation.** Once the token launches, token rewards are claimable only by users who (i) made a market purchase, (ii) placed a PvP wager, OR (iii) hold the token in their wallet. Solo-only accounts get cosmetic badges, not tokens.
5. **You're responsible for your own wallet security** — we never hold your private keys.
6. **Botting/scripted input/wash-trading** = immediate ban with no refund of in-flight stakes.

## The Beta Slot Mechanic

The first **20 wallets** to accept the Terms get the closed-beta slot AND a permanent **BETA badge** that displays next to your username forever.

* Slots are claimed atomically on TOS-accept, not on first connect — so disconnecting before accepting doesn't burn a slot.
* If you connect after slot 20 is filled, you'll see "Beta is full" and can't continue until we open the cap.
* The 20 BETA badges are **non-transferable and permanent**. Even after launch, your wallet keeps the badge as OG identification.

## If We Update the Terms

We use versioned Terms (`tos_version`). If we materially change the policy — like the recent v2 update that added the reward-eligibility clause — you'll be prompted to re-accept on your next sign-in. Re-accepts don't claim a new slot or re-grant items; they just record your acceptance of the new version.


---

# 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/getting-started/accepting-tos.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.