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

# Summary

Three Token will benefit the One Token ecosystem by pumping all three tokens in the ecosystem with buybacks of each token and a treasury allocation to help pay for marketing and expenses.

Three Token will work to lower the tokens in each pool which will positively impact the price of each token.

One Token is like the Bitcoin of our ecosystem, you hold it as a store of value. 5% of Three Token's taxes will go directly to buying One Token.

Two Token is like Ethereum, you either accumulate more or arbitrage trade it to accumulate more One Tokens. 2% of Three Token's taxes will go to buying Two Token (which involves buying One Token and swapping it for Two Token, putting the extra 2% of buy pressure on One Token).

Three Token is like BNB, you buy, sell, trade or accumulate more of it. 2% of Three Token's taxes will go to buying Three Token.

Or think of it this way: One is gold, Two is silver, Three is bronze.


---

# 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://olivers-organization-1.gitbook.io/three-token-whitepaper/summary.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.