> For the complete documentation index, see [llms.txt](https://solana-unchained.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://solana-unchained.gitbook.io/whitepaper/why-this-exists/overview.md). # Overview The crypto industry has matured significantly in its ability to create, distribute, and trade digital assets. However, one core issue remains unresolved: the majority of tokens do not sustain long term demand. They are purchased with the expectation of appreciation, held in anticipation of momentum, and eventually sold when liquidity allows. This cycle, while effective in early stage capital formation, fails to produce durable ecosystems. ### *Solana Unchained is built to break that pattern.* Rather than positioning the token as a speculative instrument, Solana Unchained introduces a system where the token becomes necessary for participation. The design shifts focus away from passive ownership and toward active engagement, creating an environment where value is continuously generated through usage rather than external market forces. By combining AI‑powered tools, token‑gated access, staking incentives, and a family of real‑world infrastructure protocols, Solana Unchained establishes a closed‑loop economy in which tokens circulate, lock, and re‑enter the system in a controlled and intentional manner. --- # 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://solana-unchained.gitbook.io/whitepaper/why-this-exists/overview.md?ask=&goal= ``` `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.