# Vault Layer

The Vault Layer turns complex DeFi strategies into simpler deposit tokens.

Users deposit an asset into a CurveYield vault and receive vault shares. The vault and strategy system handles staking, reward claiming, compounding, route management, fee accounting, and automation.

CurveYield uses two vault framework families.

## Vault family status

| Vault family                 | Purpose                                                                                                    | Public status   |
| ---------------------------- | ---------------------------------------------------------------------------------------------------------- | --------------- |
| StakeDAO BoostHub vaults     | Boosted liquid-locker vault strategies for `sdCRV`, `sdFXN`, and `sdSPECTRA`                               | Live / Deployed |
| QuickSwap Merkl strat vaults | Reward-harvesting vaults for QuickSwap strat products such as `cystratUSD`, `cystratETH`, and `cystratBTC` | Live / Deployed |
| Convex `cvxCRV` vault        | Auto-compounding `cycvxCRV` vault                                                                          | Live / Deployed |
| IPOR Fusion route vaults     | Controlled route execution for specialized collateral and strategy paths                                   | Route-specific  |

## Yearn V3-style ERC4626 vaults

Yearn V3-style vaults provide a standard user-facing vault layer:

* ERC4626-compatible share accounting;
* strategy allocation;
* profit reporting;
* profit unlock smoothing;
* strategy migration without replacing the vault token;
* automated reward harvesting and compounding.

This framework is used for vaults where simple ERC4626 accounting and strategy migration are the right fit.

## IPOR Fusion-style vaults

IPOR Fusion-style vaults are used for controlled route systems where every external position needs explicit execution, accounting, pricing, and permission paths.

An IPOR-style vault route includes:

* a user-facing PlasmaVault-style vault;
* execution fuses for protocol actions;
* balance fuses for accounting;
* price oracle middleware;
* market substrates / allowlists;
* withdrawal routes;
* reward claim managers;
* keeper automation.

This model keeps user deposits inside structured vault accounting while strategy-specific behavior is isolated behind approved route modules.

## StakeDAO BoostHub vault family

The first major boosted vault family is built around CurveYield StakeDAO BoostHub.

Supported designs include:

* `cysdCRV`;
* `cysdFXN`;
* `cysdSPECTRA`.

These vaults deposit StakeDAO liquid-locker assets into CurveYield strategies, route through BoostHub, stake into the relevant StakeDAO gauges, apply delegated `vlSDT` boost where available, harvest rewards through keeper-controlled flows, compound rewards, and report yield through standard vault accounting.

## Other vault families

CurveYield vault work also includes or explores:

* Base reward-harvesting vault designs such as `cystratUSD`, `cystratETH`, and `cystratBTC`;
* Convex `cvxCRV` auto-compounding with reward-mode optimization;
* IPOR Fusion route vaults for specialized collateral and leverage strategies;
* yield-bearing BTC, ETH, stablecoin, RWA, and partner-asset strategies where risk review supports them.

## Vault economics

CurveYield vault fees can include deposit fees, withdrawal fees, management fees, performance fees, or strategy-specific route fees. Exact fee design is documented per vault rather than generalized across all vaults.

Fees may be used to offset entry/exit costs, fund keepers, route value to the treasury, support vault PPS, or compensate the DAO for strategy management.

## Vault risk reference

A vault share is not a fixed-yield product. It is a claim on an automated strategy whose value depends on the assets and routes used by that strategy.

System-wide and vault-specific risk categories are maintained in [Risks](/reference/risks.md). Product pages only list risks that are unique to a vault family.


---

# Agent Instructions: 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:

```
GET https://docs.curveyield.com/architecture/vault-layer.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.