# Levels & difficulty

***

QRbase uses a 10-level progression system designed to reward skill while keeping the game economy balanced and competitive.

As players progress through the levels:

* puzzles become more challenging
* timers become shorter
* entry costs increase
* prize rewards grow significantly
* daily free attempts become more limited at higher levels

Skilled players can earn substantially more rewards per solve as they climb the ladder.

***

### How leveling works

All players begin at **Level 1** with:

* a **60-second timer**
* **3 free daily attempts**

To advance to the next level, players must meet **all three promotion requirements simultaneously**:

1. complete enough solves at the current level
2. maintain the required solve rate
3. achieve the required consecutive win streak

This system ensures progression is based on consistency and genuine skill rather than grinding attempts.

Player level is displayed directly in the game UI and on the leaderboard.

### Promotion requirements

| To reach | Solves at current level | Required solve rate | Consecutive streak |
| -------- | ----------------------- | ------------------- | ------------------ |
| Level 2  | 15                      | 60%                 | 3                  |
| Level 3  | 25                      | 55%                 | 4                  |
| Level 4  | 35                      | 50%                 | 5                  |
| Level 5  | 50                      | 50%                 | 5                  |
| Level 6  | 60                      | 45%                 | 6                  |
| Level 7  | 75                      | 40%                 | 6                  |
| Level 8  | 90                      | 35%                 | 7                  |
| Level 9  | 110                     | 30%                 | 8                  |
| Level 10 | 130                     | 30%                 | 10                 |

***

### Economy table

| Level | Timer | Cost  | Prize  | Free/day | Daily limit |
| ----- | ----- | ----- | ------ | -------- | ----------- |
| 1     | 60s   | 50    | 100    | 3        | 15          |
| 2     | 55s   | 100   | 170    | 3        | 15          |
| 3     | 50s   | 150   | 240    | 3        | 18          |
| 4     | 45s   | 250   | 400    | 2        | 20          |
| 5     | 40s   | 350   | 550    | 2        | 20          |
| 6     | 35s   | 500   | 800    | 2        | 18          |
| 7     | 30s   | 800   | 1,500  | 1        | 15          |
| 8     | 25s   | 1,500 | 3,000  | 1        | 12          |
| 9     | 20s   | 2,500 | 6,000  | 1        | 10          |
| 10    | 15s   | 5,000 | 15,000 | 0        | 8           |

***

### Leaderboard tabs

| Tab      | Ranks by                                              |
| -------- | ----------------------------------------------------- |
| Skilled  | Level + win rate %                                    |
| Wins     | Total wins all-time                                   |
| Spenders | Total attempts bought ($SCAN spent)                   |
| Referral | Total $SCAN earned from referrals or friends referred |

***

### Why QRbase uses levels

The progression system is designed to:

* reward player skill instead of spam attempts
* make higher rewards feel earned
* maintain a sustainable token economy
* reduce abuse from low-quality or automated accounts
* create meaningful long-term progression for competitive players

***

### Fair-play policy

QRbase may use anti-cheat systems, bot detection, and reward restrictions for suspicious activity.

The philosophy is simple:

```
easier to get in, harder to cheat
```


---

# 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.qrbase.xyz/for-players/levels-and-difficulty.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.