> For the complete documentation index, see [llms.txt](https://vaultbook.gauntlet.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vaultbook.gauntlet.xyz/vaults/morpho-vaults/prime-vaults-conservative-yield-strategies.md).

# Prime Vaults

Prime vaults prioritize capital preservation, high withdrawability, strong oracle integrity, and maximum security. These vaults are designed for users seeking conservative exposure and dependable access to liquidity while earning yield consistent with a low-risk profile.

* **Asset Selection:** Blue-chip collateral assets with deep secondary markets, strong market structure, and low realized volatility.
  * Target assets are those capable of supporting large notional liquidations with limited market impact.
  * As a reference point, this category is generally limited to assets such as BTC, ETH, and wstETH.
* **High Withdrawable Liquidity:** Prime vaults maintain elevated targeted withdrawable liquidity thresholds based on the chain and the surrounding market ecosystem. Liquidity management is optimized to preserve a high level of withdrawable capital at all times, reducing withdrawal friction and improving resiliency under stressed conditions.
* **Timelock Policy (v2):** Prime vaults enforce the most restrictive per-selector timelock schedule. Key actions carry a 7-day timelock including all adapter and allocation cap management and structural gateway actions. `setForceDeallocatePenalty` carries a 1-day timelock — stricter than Balanced/Frontier — maximizing the reaction window for market participants in the event of adverse changes or compromise.

| Selectors                                                                                | Prime (days) |
| ---------------------------------------------------------------------------------------- | ------------ |
| setReceiveSharesGate, setSendSharesGate, setReceiveAssetsGate                            | Abdicate     |
| setSendAssetsGate, setAdapterRegistry, increaseTimelock, abdicateTimelock, removeAdapter | 7            |
| addAdapter, increaseRelativeCap, increaseAbsoluteCap                                     | 7            |
| setForceDeallocatePenalty                                                                | 1            |
| setPerformanceFee, setManagementFee                                                      | 1            |
| setIsAllocator, setPerformanceFeeRecipient, setManagementFeeRecipient                    | 0            |

* **Oracle Risk Considerations:** Prime vaults should not rely solely on hardcoded, manually maintained, or structurally misaligned oracle designs. Oracle configurations are expected to track collateral and debt relationships dynamically and support robust pricing integrity under stressed market conditions.


---

# 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://vaultbook.gauntlet.xyz/vaults/morpho-vaults/prime-vaults-conservative-yield-strategies.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.