> For the complete documentation index, see [llms.txt](https://documents.velo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documents.velo.org/base-concepts/drs-mechanism.md).

# DRS Mechanism

![](/files/-MHz9017LQODwlwfGLBe)

The Digital Reserve System will algorithmically rebalance the VELO token Collateral Pools backing the issued digital credit to maintain a 1:1 value link between the digital credit and the VELO token and the original fiat deposit. When a Trusted Partner received a fiat deposit from a end user, they then engage the Velo Protocol to generate a digital credit by posting and locking an equivalent value of VELO tokens via the Velo Protocol. The DRS then tracks these pooled tokens by assigning them to a collateral pool that is linked with the digital credit issued and adjusting the amount of tokens in the pool at any given time to maintain the value at initial issuance. At the time of creation, the value of the digital credit equals the value of VELO tokens deposited as well as the fiat original deposited with the Trusted Partner. After this period, however, the price of VELO tokens will naturally fluctuate on the open market as a function of supply and de- mand. In response, the DRS will automatically rebalance the amount of VELO tokens in the Col- lateral Pool to maintain the 1:1 value link with the value of digital credits created. If the price of VELO tokens goes up, then VELO tokens will be removed from the Collateral Pool and returned to the Reserve Pool. This action reduces the number of tokens in the Collateral Pool to maintain 1:1 link between collateral value and digital credit value. If the price of Velo Token goes down relative to the digital credit, then the DRS will add VELO tokens to the Collateral Pool from the Reserve Pool, to maintain the value link of collateral value and digital credit value.

{% content-ref url="/pages/-MHzC8Oh-UM9u4sDRfKp" %}
[Setup stable credit](/base-concepts/setup-stable-credit.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MHzGy2lmkajgJtMK-wo" %}
[Mint stable credit](/base-concepts/mint-stable-credit.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MHzHn0KE2KYaOYjiuID" %}
[Redeem stable credit](/base-concepts/redeem-stable-credit.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MHzIor6rHfL7uDAYSqm" %}
[Rebalancing the Reserve and Collateral Pool](/base-concepts/rebalancing-the-reserve-and-collateral-pool.md)
{% endcontent-ref %}


---

# 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://documents.velo.org/base-concepts/drs-mechanism.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.