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

# Tokenomics

Blockchain Bets ($BCB) has a total of 1 billion tokens, which can be broken down as follows:

·        882m in circulation

·        118m burned

·        41m in exchange reserves (From circulation)

## Token Sale

All tokens were released for purchase to the community at launch, with 41m being purchased and held within the Exchange Reserves for platform operations.

The token burn volume was determined based on engagement with the platform over the first month. Due to engagement being significantly higher than our initial targets, a higher token burn was completed. This resulted in close to 12% of the total token volume being removed from the circulating supply forever.

## Token Taxes and Fees

Blockchain Bets ($BCB) implements a Sell Tax on their token. There is no Buy Tax, but to sell your token you will need to pay a 5% Sell Tax. This 5% is recycled back into our marketing and development to enhance the offers we provide to our customers.


---

# 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:

```
GET https://blockchainbets.gitbook.io/docs/tokenomics.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.