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

# Tokenomics

### Token Details

    **Ethereum**

* Contract: 0x8790f2fc7Ca2e7Db841307FB3f4e72a03Baf7b47
* Token name: $SpillWays
* Total Supply: 100 million $SpillWays (2.73% burned)

*\*The supply is immuable and will never go above 100 Million that is on Ethereum, any token minted on the sidechains is backed by the bridge who holds the supply, then mints it to the chain.* 

### Token Purpose

The $SpillWays token serves multiple purposes within the SpillWays project. It can be used to:

* Invest in the project growth & success
* Pay for services and fees on the platform with reduced or zero fees
* Gives access to WayGuard VPN Premium for holders of 10k+ $SpillWays
* Earn rewards through activities such as airdrops, staking, and more investor-oriented benefits

### Token Taxes

#### Buy

* 2% of the transaction
* 1% allocated to Dev Wallet
* 1% allocated to Liquidity

#### Sell

* 4% of the transaction
* 2% allocated to Dev Wallet
* 2% allocated to Liquidity

### Token Repartition

\
100% Fair Launch, 100% of the supply added to the liquidity and is currently circulating without any token pre-owned by the team. 


---

# 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://spillways.gitbook.io/documentation/project/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.