Loading
Sharpe FinanceDID YOU KNOWnext in 7s
The most-traded asset in DeFi history isn't ETH, BTC, or USDC. It's a wrapper around one of them.
Morpho Blue · Aave V3 · 11 chains · scoring refreshed every 5 min
The most-traded asset in DeFi history isn't ETH, BTC, or USDC. It's a wrapper around one of them.
FXS supply on Aave V3 (Ethereum). Read-only on Sharpe — deposits, withdrawals, and borrows execute on app.aave.com. We surface parameters, rates, and risk so you can compare this reserve against Morpho vaults on the same asset cohort.
Plain-English summary of this vault — what it does, who runs it, where the yield comes from, and what could break it. Generated from the same deterministic inputs shown elsewhere on this page; the numbers are the source, this is just the explanation.
Depositing FXS on Ethereum means lending it to borrowers in exchange for the variable supply rate, currently 0.00%. Your deposit is redeemable at the reserve's available liquidity ($134.45), though the reserve is frozen by governance—new deposits and withdrawals are blocked. FXS is borrow-only; it cannot be used as collateral to secure loans. The supply rate is set by borrow demand (0.24% borrow APY) multiplied by utilization (1.2%) and reduced by Aave's 20% reserve factor.
Aave governance has frozen this reserve, signaling a direct halt on new capital entry and exit—a governance-initiated pause distinct from normal operational risk management.
Supply APY is effectively zero because utilization is extremely low at 1.2%, leaving minimal borrower demand to generate returns. The frozen status prevents new deposits from earning even nominal yield.
The reserve is frozen by governance—the primary risk is that you cannot withdraw or deposit capital while this flag remains active. This is not a market risk but a governance lock.
Avoid—the reserve is frozen and produces no yield; capital is trapped until governance unfreezes it.
On Aave V3, a supplier can withdraw up to the reserve's available liquidity instantly. Above that, the withdrawal must wait for borrowers to repay or new suppliers to deposit. Markets at 95%+ utilization can keep large redemptions waiting for hours to days at current rates.
Reserve parameters are set by Aave governance (BGD Labs + Aave Chan Initiative + Risk Council). Listings, caps, IRM curves, and LLTVs change through on-chain votes.
This reserve isn't usable as collateral, so LTV / Liquidation LLTV / liquidation bonus don't apply. Borrowers can take it against other collateral; suppliers earn the variable rate driven by borrow demand.
On Aave V3, supply APY = borrow APY × utilization × (1 − reserve factor). There is no curator skim; the only intermediation cost is the reserve factor, which funds the Aave treasury. No emissions slice in v1 of this integration — the headline is fully sustainable.
Aave V3 reserves carry parameter risk (LTV/LLTV adequacy vs collateral volatility), liquidity risk (high utilization slows exit), and depeg risk on the underlying. Governance can pause / freeze / adjust caps in response to incidents. Sharpe's full risk decomposition for Aave reserves rolls in v1.1.
How the composite risk score breaks down. Every number traces to an explicit input — /methodology documents each factor's formula.
Per-collateral decomposition: Sharpe-style realized σ from 30 daily log returns, blended 50/50 with the asset-taxonomy tier fallback. Phase 2 will replace the tier slot with liquidity depth, mechanism classification, and holder concentration. Methodology in /methodology.
The honest version. Every structural failure mode this vault is exposed to, ranked by severity. If you want to know whether to invest, start here.
New supply and borrow are disabled; withdrawal and repay remain open. Typically applied during a deprecation glide path or when governance is unwinding exposure.
Aave V3 prices and liquidations route through Chainlink's aggregator feed for this asset. A stale, manipulated, or wrong-side update is the protocol's largest single-point-of-failure for this reserve. Chainlink has a strong track record but the failure mode is binary.