# StakeDAO BoostHub

CurveYield StakeDAO BoostHub is a Convex-style boost aggregation layer for StakeDAO liquid-locker assets.

It is designed to help CurveYield vaults route deposits into StakeDAO gauges, apply delegated `vlSDT` boost where available, harvest rewards through approved strategy and keeper flows, compound rewards, and report yield through standard vault accounting.

The BoostHub vaults share the same core risk profile. Each vault depends on the relevant StakeDAO liquid-locker token, StakeDAO gauge behavior, delegated boost availability, reward-token prices, keeper execution, swap liquidity, and vault harvest settings. The main differences are the underlying asset, network, liquidity depth, and reward conversion route.

CurveYield is independently built and is not an official StakeDAO product unless approved or integrated through StakeDAO's own governance, contributors, or platform process.

## Why BoostHub exists

StakeDAO liquid-locker assets can generate rewards, but maximizing those rewards usually requires staking, boost delegation, gauge accounting, reward claiming, swaps, compounding, and monitoring.

CurveYield packages that complexity into boosted sd-token vaults. Users deposit into a vault, receive CurveYield vault shares, and the strategy routes the underlying asset through BoostHub.

The goal is not to claim that boost aggregation is new. The goal is to integrate a Convex-style boost layer into the broader CurveYield system: boosted vaults, productive pool assets, yield-bearing collateral markets, protocol-owned liquidity, cross-chain rate publishing, and DAO-governed revenue routing.

## Supported boosted sd-token vaults

| Vault         | Intended underlying exposure | Status          |
| ------------- | ---------------------------- | --------------- |
| `cysdCRV`     | `sdCRV`                      | Live / Deployed |
| `cysdFXN`     | `sdFXN`                      | Live / Deployed |
| `cysdSPECTRA` | `sdSPECTRA`                  | Live / Deployed |

## Deposit flow

The intended flow is:

1. User deposits the underlying StakeDAO liquid-locker asset into a CurveYield vault.
2. The vault allocates assets to a CurveYield strategy.
3. The strategy routes deposits through BoostHub.
4. BoostHub stakes into the relevant StakeDAO gauge.
5. Delegated `vlSDT` boost is applied where available.
6. Rewards are claimed through strategy or keeper flows.
7. Rewards are compounded or routed according to the vault strategy.
8. Yield is recorded through vault accounting and reflected in vault shares over time.

## Boost mechanics

BoostHub supports multiple lockers and pool configurations. The system is designed around delegated boost, gauge checkpointing, reward claiming, and owner-configured pool settings.

Boost can improve reward capture, but it does not create a fixed APR. The realized return depends on gauge rewards, boost availability, reward-token prices, liquidity, swap execution, keeper performance, and the vault's strategy settings.

## Rewards and compounding

Rewards are claimed by approved strategy or keeper flows. After rewards are claimed, the strategy can convert them into the vault's underlying asset, compound into the boosted position, route value through fee logic, or report profit through the user-facing vault.

This design keeps reward claiming predictable and prevents random users from controlling vault harvest timing.

## Why BoostHub matters to CurveYield DEX

BoostHub vault shares can become productive assets for CurveYield pools where rate providers, liquidity, and risk controls support them.

That means a CurveYield pool can hold assets that already produce yield before swap fees are counted. The same capital may earn underlying strategy yield while also supporting liquidity, trading volume, and fee generation.

## How StakeDAO can benefit

If CurveYield and StakeDAO align on licensing, integration, or platform support, the relationship can create additional utility for StakeDAO systems:

* additional demand for StakeDAO liquid-locker assets;
* additional vault routes that highlight StakeDAO boost mechanics;
* future pools that may direct liquidity, incentives, or treasury activity toward StakeDAO-linked assets;
* potential votemarket participation if StakeDAO accepts CurveYield onto its platform;
* clearer public attribution for StakeDAO's role in the underlying boost architecture.

Any official integration, listing, or licensing relationship depends on StakeDAO approval and should be documented separately.

## Credit-market potential

Boosted sd-token vault shares can become candidates for yield-bearing collateral markets where pricing and liquidation paths are robust.

A future credit market for a BoostHub vault share would need asset-specific collateral rules, borrow caps, oracle routes, liquidation assumptions, withdrawal assumptions, and governance approval.

## Governance and controls

BoostHub configuration is controlled by CurveYield governance or DAO-authorized operators.

Important controls include:

* supported lockers;
* supported StakeDAO gauges;
* depositor allowlists where used;
* boost delegation;
* reward claiming permissions;
* keeper permissions;
* fee settings;
* emergency or pause controls where implemented.

The production control standard is DAO-governed ownership rather than founder or deployer-wallet override.

## Current status

The boosted sd-token vault family is marked **Live / Deployed**. Current public addresses and deployment status are maintained in [Contracts](/reference/contracts.md) and [Product Status](/reference/product-status.md).


---

# 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/products/stakedao-boosthub.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.