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

# Sights Token & Revenue Share

**SIGHTS Token:** The SIGHTS Token is the native currency of the SwapSights trading ecosystem. It allows its holders to benefit from SwapSights’s 50% revenue share program, while also granting access to more advanced plans, trading analytics & trading tools. In order to access the Elite SwapSights plan, a minimum token holding amount is required.

**Sights Tokenomics:** 

**Total Supply:** 1 000 000

**Buy Fee:** 5% *(4% Marketing, 1% Liquidity)*

**Sell Fee:** 5% (4% Marketing, 1% Liquidity)

**Revenue Share:** 50% of all revenues collected by the platform from both subscriptions and trading fees are shared with token holders. 

These royalties are proportionally distributed between all holders on a bi-weekly basis via the medium of a mass airdrop.


---

# 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, and the optional `goal` query parameter:

```
GET https://swapsights.gitbook.io/swapsights-whitepaper/sights-token-and-revenue-share.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.