> For the complete documentation index, see [llms.txt](https://docs.snowbl.capital/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snowbl.capital/how-it-works/overcollateralization.md).

# Collateralization

How Snowbl vaults maintain a surplus of assets to smooth out yield volatility and protect the share price.

Snowbl vaults hold more assets in value than what is reported to depositors. This surplus acts as a buffer that absorbs yield volatility and short-term valuation fluctuations.

<div align="center"><figure><img src="https://4071387789-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsZ2bEvRrM0aVDEWfEdbr%2Fuploads%2FH6PMGQ1L1YJIV5rzb563%2FScreenshot%202026-02-06%20at%2012.54.03.png?alt=media&amp;token=ccc43ec2-3857-467f-ba8b-232269313869" alt="" width="188"><figcaption></figcaption></figure></div>

<p align="center"><em>Collateralization is continuously updated on the detailed vault view.</em></p>

As a result, the share price of each vault remains stable and is not directly impacted by temporary swings in underlying yield or asset valuations. Only realized, confirmed gains are reflected in the share price over time.

This overcollateralization model ensures that depositors benefit from consistent, smoothed returns rather than being exposed to the noise of day-to-day market movements.


---

# 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://docs.snowbl.capital/how-it-works/overcollateralization.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.
