> For the complete documentation index, see [llms.txt](https://gxb-2.gitbook.io/gxb-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gxb-2.gitbook.io/gxb-docs/10.-token-velocity-control.md).

# 10. TOKEN VELOCITY CONTROL

GXB operates a macro-level Token Velocity Control mechanism to prevent value dilution caused by excessive market circulation and to ensure the long-term stability of asset value:

* **Treasury Reserve:** Excess market supply is absorbed into the protocol treasury and converted into a permanent or long-term locked supply state.
* **Institutional Lock:** Long-term holding obligations are imposed on key ecosystem partners and financial institutions, fundamentally eliminating sell-side pressure.
* **Staking:** Individual and institutional investors voluntarily lock up tokens in exchange for staking rewards, thereby directly reducing the circulating supply in the market.
* **Burn Mechanism:** A portion of fees and protocol revenues is permanently burned, exponentially increasing the scarcity of the asset over time.
* **Liquidity Reserve:** In the event of abnormal market volatility, a protocol-level buffer mechanism is activated to ensure liquidity stability and resilience.


---

# 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://gxb-2.gitbook.io/gxb-docs/10.-token-velocity-control.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.
