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

# $SKEYE Token

Ticker: SKEYE

Total Supply: 11,000,000

Supply Distribution:&#x20;

* 16.8586% allocated for Marketing & potential CEX listings. Originates from the Burn Wallet.
* 10% allocated for the Team.

**Transaction Taxes:**&#x20;

* BUY - 0% tax.
* SELL 4% total. 1% to \*Liquidity, 3% to the \*Community Engagement Token Pool.

\*Liquidity Tax.

Implemented to reduce price volatility, incrementally increase the floor price and allow for large investors to enter.

\*Engagement Pool.

Implemented to incentivise and reward the ongoing discourse and exploration of finding stemming from Skeye Camera footage.&#x20;

2. Launch Type.

The relaunch will take place on Ethereum, with past $LIFE token holders who have been captured in the token snapshot (Snapshot taken at the time the $LIFE contract's trading is frozen) being airdropped 1:1 with the equivalent dollar value, numerical quantity, and proportion of total supply of tokens from the former contract. Liquidity will be matched 1:1 from the deprecated $LIFE token out of pocket by the Skeye team and backers. &#x20;

<br>

<br>


---

# 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://skeye.gitbook.io/litepaper/token/usdskeye-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.
