> For the complete documentation index, see [llms.txt](https://docs.hedge.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hedge.so/protocol-overview/vault-types.md).

# Vault Types

Before onboarding new vault types, the Hedge community will carefully assess the risks of each collateral (e.g. liquidity & volatility) and set the parameters for the vault.

For each vault there exists various parameters including:

* **Collateral Token**: this is the collateral that the Hedge protocol will accept in the vault to mint USH.
* **Minimum Collateral Ratio (MCR)**: This is the minimum collateral ratio a vault must maintain before be liquidated.
* **Recovery Mode Collateral Ratio (RMCR)**: This is the minimum amount that the Vault Type must be collateralised by before entering Recovery Mode and enabling the liquidation of vaults under this collateral ratio.
* **Minimum Debt**: This is the minimum debt that must be extended against an individual vault type to be opened.
* **Maximum Debt against Vault Type**: This is the total debt against a Vault Type that can be extended. This is used to avoid having too much debt set against a certain type of collateral.
* **Interest Rate**: If set to a value other than 0, the vault will accumulate interest over time.
* **Initialization Fee**: This is the fee taken during loan initiation.
* **Redeemability**: Whether the vault can have collateral redeemed to keep USH peg. Only the lowest collateral ratio vault for each Vault Type may be redeemed against. See more details at [Redeeming against a vault](/protocol-overview/redeeming-against-a-vault.md).
* **Oracle**: The oracle price feeds used for this Vault Type.

The Hedge Protocol currently supports:

<table><thead><tr><th> </th><th>SOL-110</th><th width="118">mSOL-110</th><th width="95">cUSDC-105</th><th width="114">wBTC-110</th><th width="126">soETH-110</th><th width="124">cUSDT-106</th></tr></thead><tbody><tr><td>Vault Collateral</td><td>SOL</td><td>mSOL</td><td>Solend cUSDC</td><td>wBTC</td><td>soETH</td><td>Solend cUSDT</td></tr><tr><td>Interest Rate</td><td>0%</td><td>0%</td><td>2%</td><td>0%</td><td>0%</td><td>1.50%</td></tr><tr><td>Initialization Fee</td><td>0.5%</td><td>0.5%</td><td>0.25%</td><td>0.5%</td><td>0.5%</td><td>0.1%</td></tr><tr><td>MCR</td><td>110%</td><td>110%</td><td>105%</td><td>110%</td><td>110%</td><td>106%</td></tr><tr><td>Recovery Mode Trigger</td><td>150%</td><td>150%</td><td>N/A</td><td>150%</td><td>150%</td><td>N/A</td></tr><tr><td>Redeemable</td><td>Yes</td><td>Yes</td><td>No</td><td>Yes</td><td>Yes</td><td>No</td></tr><tr><td>Min Debt</td><td>200 USH</td><td>200 USH</td><td>50 USH</td><td>200 USH</td><td>200 USH</td><td>50 USH</td></tr><tr><td>Max Total Debt</td><td>1B USH</td><td>100M USH</td><td>10M USH</td><td>1M USH</td><td>1M USH</td><td>2.5M USH</td></tr><tr><td>Oracle</td><td>Pyth, Chainlink, Switchboard</td><td>Pyth</td><td>Solend via Switchboard</td><td>Pyth, Chainlink, Switchboard</td><td>Pyth</td><td>Solend via Switchboard</td></tr></tbody></table>


---

# 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://docs.hedge.so/protocol-overview/vault-types.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.