> For the complete documentation index, see [llms.txt](https://veloriz-network-ltd.gitbook.io/veloriz-network-ltd-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://veloriz-network-ltd.gitbook.io/veloriz-network-ltd-docs/usdvlr-cex-exchange-trading-fees-a-tool-for-buyback.md).

# $VLR Cex Exchange Trading Fees; A Tool For Buyback

Connecting Exchange Activity to $VLR Utility

The Veloriz Exchange is intended to create an economic relationship between the activity taking place within the trading environment and the long-term utility of $VLR.

Tokens listed on the Veloriz Exchange will generate trading fees from eligible buy and sell transactions. Under the proposed ecosystem model, 5% of eligible trading-fee revenue generated by listed tokens will be allocated toward the purchase and buy back of $VLR.

The purpose of this mechanism is to ensure that the growth of trading activity across the Veloriz Exchange can contribute directly to demand for the native ecosystem token.

Rather than directing all exchange-generated revenue toward operational purposes, a defined portion will be used to create recurring market demand for $VLR.

**Why 5%?**

The 5% allocation establishes a predictable connection between exchange activity and $VLR demand while allowing the remaining trading-fee revenue to support the operation, development, security, liquidity and sustainability of the exchange and broader Veloriz infrastructure.

As more eligible tokens are listed and trading activity increases, the aggregate fees generated by the exchange may increase. Consequently, the amount allocated toward $VLR purchases may also increase.

The intended economic relationship is:

More Listed Tokens → More Trading Activity → More Eligible Fees → 5% Allocation → $VLR Buyback

**Buyback Execution**

The buyback mechanism will be implemented according to the technical and operational framework adopted by Veloriz at the time of deployment.

Where applicable, buybacks may be executed periodically rather than on every individual transaction, allowing the system to aggregate eligible fees and execute purchases efficiently. The relevant allocation and execution activity will be subject to appropriate transparency measures, allowing the community to understand how the mechanism operates.

The purchased $VLR may subsequently be held by the ecosystem, allocated according to approved ecosystem policies, or subjected to another predefined treatment. The final treatment should be established and disclosed before the mechanism becomes operational.

**A Utility-Driven Model**

The objective of the buyback mechanism is not to create an artificial price floor or guarantee appreciation of $VLR. Market value remains determined by supply, demand, liquidity and broader market conditions. Instead, the mechanism is designed to establish a fundamental principle within the Veloriz economy:

> When the ecosystem generates economic activity, a portion of that activity contributes to the utility and demand of the ecosystem's native token.

This creates a connection between the success of the Veloriz Exchange and the broader $VLR economy, allowing exchange growth to become one of the potential sources of recurring demand for $VLR.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://veloriz-network-ltd.gitbook.io/veloriz-network-ltd-docs/usdvlr-cex-exchange-trading-fees-a-tool-for-buyback.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.