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

# Taco Token ($TACO)

**Token Details:**

* Ticker: TACO
* Token address: 0x9066e87Bac891409D690cfEfA41379b34af06391
* Chain: Binance Smart Chain (BEP-20)
* Supply: Unlimited

**Emission Rate:**

* 1 TACO/block;
* 28,800 TACO/day; and
* 9.09% will be sent to the developer’s address for marketing, developer's payout, and to fund future partnership & development (we inherited this model from Goose Finance).

**Deflationary Mechanics:**

* 5% burn fee will be charged when you staked in the pool.

**Burn Mechanism:**

* 80% of the deposit fees will be used to buyback TACOs and all the TACOs purchased will be burned immediately.
* 10% of the deposit fees will be sent to the developer’s address as payouts;
* 10% will be held in escrow for Taco Finance, for future projects; and emergency funds.
* The current burning operation is done manually to stabilize the TACO price. The frequency of the burn is not fixed, as it depends on when there are massive dumps happen. 


---

# 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://taco-finance.gitbook.io/taco-finance/tokenomics/taco-token.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.