> 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/core-thesis.md).

# Core Thesis

Solana Unchained is built on a simple but powerful principle:

#### *Tokens should not rely on demand. They should create it.*

In traditional token models, demand is external. It depends on market conditions, narratives, and investor sentiment. In Solana Unchained, demand is internal. It is generated by the system itself through enforced usage.

Every meaningful interaction within the platform – from running an AI inference to staking for enhanced features, from buying a gift card to setting up a wallet recovery – requires the SOLANA UNCHAINED token. This transforms the token from a passive asset into an active component of the system’s functionality.

The result is a self‑reinforcing loop in which usage drives demand, demand supports value, and value encourages further participation.


---

# 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/core-thesis.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.