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

# Tokens

There are 3 ‘’Tokens’’ in the Bug Finance ecosystem. <mark style="color:purple;">$BUG</mark>, <mark style="color:purple;">veBUG</mark>, and <mark style="color:purple;">‘’The Swarm’’ Bug NFTs</mark>:

<mark style="color:purple;">**$BUG**</mark>**&#x20;- Utility token of Bug Finance**

<mark style="color:purple;">$BUG</mark> will be emitted to LP providers and governed by <mark style="color:purple;">veBUG</mark> holders. There are 3 objectives of <mark style="color:purple;">$BUG</mark>:

1. Reach and maintain adequate liquidity to facilitate optimal trading conditions. $BUG is emitted as farming rewards to incentivize deep liquidity.
2. $BUG needs to be used to acquire veBUG by staking $BUG in partner LP pairs, such as `BUG/MATIC`, `BUG/USDT`, and `BUG/fBOMB`. This will create deep-locked liquidity for $BUG and partner pools. You also have the option to acquire veBUG by single-sided staking $BUG. This however will give you less voting power.
3. The goal is to become truly decentralized. $BUG will be used to take part in the governance for the continued development of the platform. <br>

<mark style="color:purple;">**veBUG**</mark>**&#x20;- ERC-721 Governance token in the form of an NFT**

<mark style="color:purple;">veBUG</mark> is the vote-escrowed version of <mark style="color:purple;">$BUG</mark>. Users can stake any whitelisted LP paired with $BUG or stake $BUG alone to receive 30% of the voting power BUG LP receives. The voting power will be determined based on the amount of $BUG token in your LP at the time of voting. It's possible to exit any veBUG position via the exit mechanism. More about can be found in the [<mark style="color:purple;">veBUG</mark>](/bugfinance/tokenomics/vebug.md) section.

Unlike other ve(3,3) implementations, all <mark style="color:purple;">veBUG</mark> has the same voting power and doesn't decrease over time. In our system, your voting power is dynamic and gets calculated every time you vote. How it works is that your voting power is based on the amount of $BUG in your LP, it is then multiplied by 2 since BUG only represents 50% of the LP. <mark style="color:purple;">veBUG</mark> positions can be increased, split up, and resold on a secondary market besides being exitable via the exit mechanism.

<mark style="color:purple;">**“The Swarm’’ Bug NFT**</mark>**&#x20;- ERC-721 founders NFT**&#x20;

Bug NFTs can be staked to receive a percentage of the weekly trading fees, starting at 20% and slowly decreasing to 15% after 4 months. Bug NFTs will also receive a lot of other utilities which can be found in the next section.

{% content-ref url="/pages/S9ZUcTGq9jdLh37C5WaK" %}
[The Swarm - Introduction](/bugfinance/the-swarm-bug-nfts/the-swarm-introduction.md)
{% endcontent-ref %}

### Contract Addresses

| Token                                                     | Contract Address |
| --------------------------------------------------------- | ---------------- |
| <mark style="color:purple;">$BUG</mark>                   |                  |
| <mark style="color:purple;">veBUG</mark>                  |                  |
| <mark style="color:purple;">''The Swarm'' Bug NFTs</mark> |                  |


---

# 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://bugfinance.gitbook.io/bugfinance/tokenomics/tokens.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.