# Utility

<figure><img src="/files/v1duyPyGUZQsGMrUYdDK" alt=""><figcaption></figcaption></figure>

### Revenue Share

Token holders can claim rewards on our dApp, generated from bot revenue (40% after referrals) collected in our community pot. These rewards are distributed back to each holder, creating a source of passive income for our community. [More about Revenue Share.](/archive/utility/revenue-share.md)

### Community Course Access

Every $FOOT holder will have free access to our Advanced MEMECOIN Trading Education. We will keep updating all educational content. We will teach you how a beginner meme trader can become an elite sniper.

### Bitfoot Community Raffle

Token holders can participate in our monthly community raffle by staking their tokens and collecting raffle tickets. Each month, we allocate the total revenue generated from one day’s fees and select a lucky winner. The estimated arable pots are expect to range between $10,000 and $150,000, based on the daily volumes of our competitors. [More about Raffles.](/archive/utility/raffles.md)

### Sniper Bot Access

Every $FOOT holder will have free access to our Sniper Bot. All Bitfoot token holders will always receive the newest features and content first.

### Buy Back

10% will be used to buy back tokens from the market & burn, ensuring healthy growth. This strategy not only reinforces our commitment to being a community-driven project but also supports the price action and gives back to our community.


---

# 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.bitfoot.com/archive/utility.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.