# Fees & Distribution Mechanism

## Detailed working mechanism

Our BLLO token operates on a sophisticated Fees & Distribution Mechanism that is designed to optimize rewards for users of our ecosystem. Specifically, BLLO tokens come with a 2% buy and a 2% sell fee, both of which are distributed into the reward pool.

To **maximize the potential rewards**, we encourage users to buy BLLO tokens and stake them in order to earn $bBLLO, our ecosystem booster token. Once you have bBLLO tokens, you can access the reward pool and begin earning upto 200% rewards.

For those **looking to further maximize their rewards**, we offer [a bonding mechanism](/wpp/ecosystem/protocol/bonding-mechanism.md) that allows users to lock their stablecoins and receive bBLLO tokens in return. By doing so, users can instantly receive double rewards while also contributing to the growth and stability of the ecosystem.

With the initial development project in mind, we wanted to build a project based on “real yield” rewards, using the fees generated by the protocol in the most optimal way.

<mark style="color:blue;">**Our revenue will come from the following:**</mark>

* **2% buy and 2% sell fee**
* **Swap fee**
* **LP minting and burning fee**
* **Emergency unlock**
* **APY Boosting system**

<mark style="color:blue;">**Revenue is distributed as follows:**</mark>&#x20;

* **Add LP: 40%**
* **bBLLO holder: 30%**
* **Ecosystem fund: 20%**
* **Trading incentive: 10%**


---

# 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://balloondao.gitbook.io/wpp/ecosystem/protocol/fees-and-distribution-mechanism.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.