> For the complete documentation index, see [llms.txt](https://docs.sweep.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sweep.finance/ecosystem-components/platform/booster.md).

# Booster

#### **What is Booster**

Booster is a sequential elimination game where users receive one final reward from a predefined set of outcomes.

Each round is built around a group of possible rewards that are generated based on the amount selected by the user. These rewards are displayed visually before the game starts.

When the game starts, the system begins removing rewards one by one. The remaining reward is assigned to the user.

***

#### **How it works**

Users begin by selecting the amount they want to play with.

Based on this amount:

* A set of possible rewards is generated
* These rewards are displayed on the screen at the start

When the user starts the game:

* The system begins removing rewards one by one
* Each step eliminates one possible outcome
* The process continues in sequence

At the end of the sequence:

* Only one reward remains
* The remaining reward is given to the user

The entire process is completed instantly and follows predefined system logic.

***

#### **Key mechanics**

Booster operates on a sequential elimination model.

* All possible rewards are known at the beginning
* Outcomes are removed step by step
* The final remaining reward determines the result
* Users experience the full range of possibilities before the final outcome

The value range of rewards is directly related to the selected amount.

At the same time, each interaction contributes to the platform:

* Every action generates transaction volume
* A fixed **5% protocol fee** is applied
* **2.5% is burned** and **2.5% is distributed in USDT**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.sweep.finance/ecosystem-components/platform/booster.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
