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

# Why Custos

Custos reconnects protocols with their communities, injecting vitality back into tokens while redefining the standard and financial utility of commitment.

With Custos, you can:

* Deploy Trustlocker to manage token lockup and vesting, serving as a verifiable and long-term on-chain proof of commitment. 
* Generate yields and earning via rollocking. 
* Leverage any rollocked asset for prediction, breaking the constraints of stablecoin-only.

In Custos, locking no longer implies stagnant liquidity. Instead, it unlocks asset productivity, creating a self-sustaining engine of external value capture. We empowers tokens to find their voice:

* **Liquidity Enhancement**: Reconstructing how token value is discovered and assessed.
* **On-chain Commitment**: Building consensus in a transparent, trustless, and strategic way.
* **Capital Efficiency**: Tokens evolve into assets with multi-layered utility.
* **Community Emotion**: Tokens channel collective sentiment and information.

Custos is the <mark style="color:blue;">**first**</mark> to introduce the structured prediction market that delivers real-time pricing for liquidity, risk exposure, and community consensus.


---

# 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://custos-org.gitbook.io/custos/why-custos.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.