> For the complete documentation index, see [llms.txt](https://verta-1.gitbook.io/verta-cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://verta-1.gitbook.io/verta-cloud/verta-cloud-eng/publish-your-docs-3.md).

# Dynamic Burning Model

#### **Burning Mechanism**

VERTA tokens are burned during transactions, dynamically reducing the total supply. This creates scarcity and increases token value.

#### **How It Works:**

1. **Token Transfer Example:**
   * Transferring 100 tokens triggers a burn mechanism.
2. **Commission Calculation:**

   Formula:

   **Commission = Transaction Amount × (Total Supply ÷ 1,000,000)**

   * **Example:** If 10,000,000 tokens are in circulation:

     **100 × (10,000,000 ÷ 1,000,000) = 1 token burned.**
   * If the supply reduces to 5,000,000 tokens:

     **100 × (5,000,000 ÷ 1,000,000) = 0.5 token burned.**
   * Lower supply results in reduced commission, maintaining deflationary effects.
3. **Burning Process:**
   * The commission amount is automatically burned, reducing the total supply.

***

#### **Benefits of the Burning Model**

* **Active Token Usage:** Higher activity accelerates token scarcity.
* **Value Growth:** Reduced supply increases token worth.


---

# 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://verta-1.gitbook.io/verta-cloud/verta-cloud-eng/publish-your-docs-3.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.