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

# Tokenomics

#### Airdrop & Tokenomics

Bulla Exchange is a fully self-funded project with no insider allocations, venture capital,  just a fair and transparent airdrop of $BULLA directly to the community.

At Token Generation Event (TGE), 30% of the total supply will be distributed to BULLA Points holders, ensuring a fair launch. The team’s allocation will be fully locked from day one, reinforcing a long-term commitment to the ecosystem.

**How to Earn $BULLA:**

* Provide liquidity to select trading pairs on Bulla Exchange
* Delegate to validators who send rewards to Bulla’s vaults

**Revenue Sharing & Fee Switch:**

$BULLA tokenomics prioritize revenue sharing to benefit stakers. Upon launch, a 25% fee switch will activate, directing all collected fees exclusively to $BULLA stakers. More details on this mechanism will be released closer to launch.

**Track Key Metrics:**

For insights into **trading volume, liquidity, user activity, and overall platform performance**, check out the [**Bulla Exchange Dune Dashboard**](https://dune.com/bulla/bulla-exchange-metrics). This data can help you choose the best pairs to participate in.

More tokenomics details will be revealed at launch! 🚀


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bulla.exchange/bulla-exchange/tokenomics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
