# FUEGO Tokenomics

## Initial Supply - 100,000,000 Tokens

<table><thead><tr><th width="345"></th><th></th></tr></thead><tbody><tr><td>80,000,000</td><td>Fair Launch (Locked Liquidity)</td></tr><tr><td>6,000,000 (Over 10 Intervals @ 5%)</td><td>Airdrop (70% gauge incentives -  30% WINT Treasury owners)</td></tr><tr><td>4,000,000 + 10 ETH from Integer (INT)</td><td>Pairing Wallet (Multi-Sig Treasury)</td></tr><tr><td>6,000,000 (Over 10 Intervals @ 5%)</td><td>Team Wallet (Multi-Sig)</td></tr><tr><td>4,000,000</td><td>Marketing &#x26; Incentive Wallet (Multi-Sig)</td></tr></tbody></table>

## **FUEGO Fair Launch & Protocol-Owned Liquidity (POL)**

\
FUEGO launched fairly on Uniswap V3, paired with ETH. No external parties were notified of the launch name, ticker, or time. Anti-sniping methods were used to ensure decentralization. The Telegram and social channels opened at launch. A total of 80 million FUEGO tokens were deployed via LP.

## **Airdrop – AirdropFuego.base.eth**

\
Airdrops are used to reward gauge based voters on participating solidly protocols where FUEGO has a gaauge and also reward the Integer community (who contributed 10 ETH to seed the Treasury), 6 million FUEGO tokens will be airdropped for the use in incentivizing gauges and for the Integer Protocol WINT DAO holders. 70% (4.2M) will go to solidly gauge holders and 30% (1.8M) to eligible Wrapped Integer ($WINT) holders.

Tokens are released in 600,000 increments at every 5% FUEGO burn milestone. &#x20;

## **DAO Treasury – DAOFuego.base.eth**

\
Seeded with 10 ETH and 4M FUEGO (from Integer), the DAO Treasury launched 10 LPs with major Base tokens ($cbBTC, $AERO, $DEGEN, $BRETT, $VIRTUAL, $LUNA) and deflationary tokens ($fBOMB, $PEAS, $CIRCLE, $NULL).

Trading fees from these pools are used to compound or start new pools. When FUEGO supply allows, the Treasury may also vote on gauges on platforms like Aerodrome and Equalizer. Once 50% of supply is burned, Treasury revenue will be paid as yield to holders. Treasury control will then shift to the DAO and be secured by a 3-of-5 mult-isig wallet.

## **Marketing & Incentive Wallet – IncentiveFuego.base.com**

\
The Marketing & Incentive Wallet supports partnerships, gauge incentives, contests, content creation, and social engagement. Contributions above 500,000 FUEGO (or 10,000 after 50% burn) require DAO approval. Unused tokens may be moved to the Treasury to boost yields. The wallet is secured by a 3-of-5 multisig.

## **Team Wallet – TeamFuego.base.com**

\
The team will receive 600,000 FUEGO at each 5% burn milestone, totaling 6 million. With multi-chain experience (Ethereum, Fantom, Base), their mission is to build a sustainable, deflationary protocol that preserves value amid inflationary market trends.

<table><thead><tr><th>FUEGO Burn %</th><th width="296">Team FUEGO Payment</th><th>Team FUEGO Balance</th></tr></thead><tbody><tr><td>5%</td><td>600,000</td><td>5,400,000</td></tr><tr><td>10%</td><td>600,000</td><td>4,800,000</td></tr><tr><td>15%</td><td>600,000</td><td>4,200,000</td></tr><tr><td>20%</td><td>600,000</td><td>3,600,000</td></tr><tr><td>25%</td><td>600,000</td><td>3,000,000</td></tr><tr><td>30% </td><td>600,000</td><td>2,400,000</td></tr><tr><td>35%</td><td>600,000</td><td>1,800,000</td></tr><tr><td>40%</td><td>600,000</td><td>1,200,000</td></tr><tr><td>45%</td><td>600,000</td><td>600,000</td></tr><tr><td>50%</td><td>600,000</td><td>0</td></tr></tbody></table>

Once the 50% burn threshold has been achieved by the project, the DAO will begin paying 90% of the trading fee revenue to the FUEGO DAO holders.  The other 10% will continue to be paid to the original dev team for ongoing protocol maintenance and ongoing work done for the DAO.


---

# 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://ibased.gitbook.io/fuego/basics/markdown.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.
