Loading
Sharpe FinanceDID YOU KNOWnext in 7s
Stablecoin issuers are now among the top 20 holders of US Treasury bills.
Morpho Blue · Aave V3 · 11 chains · scoring refreshed every 5 min
Stablecoin issuers are now among the top 20 holders of US Treasury bills.
rETH 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 rETH means you lend Rocket Pool's liquid-staked Ethereum to borrowers on Aave, redeemable at the $103.23M available liquidity. Your deposit earns 0.00% APY (the 0.02% borrow rate × 0.1% utilization × 85% kept by lenders). rETH is enabled as collateral, so borrowers can use it to secure loans at a 75% loan-to-value ratio, or up to 93% in ETH eMode. You hold the staking yield from Rocket Pool itself separately.
Aave governance (Risk Council / BGD Labs) has not flagged this reserve; it remains in standard active mode with no pauses, freezes, or isolation restrictions.
The 0.00% supply rate reflects near-zero utilization (0.1%)—almost nobody is borrowing rETH right now. The reserve factor captures 15% of any borrower interest for Aave's treasury. Until borrow demand rises materially, lenders earn only the underlying rETH staking yield, not lending yield.
Deterministic risk score of 14/100 is low. No elevated risks are flagged. The main dependency is Rocket Pool's operational continuity and rETH's peg to ETH; neither shows current stress.
Good fit for ETH stakers who want passive rETH staking yield and don't need lending income—avoid if you depend on borrow-side yield to justify capital deployment.
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.
Borrowers in this eMode category operate against a raised LTV / LLTV against correlated assets. The on-chain liquidation surface for this reserve is the eMode LLTV, not the base — supply-side risk is calibrated to the higher figure when the borrower opts in.
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.
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.
Aave V3 has been live since March 2022 with significant TVL and continuous third-party audits. Historical incidents have been contained but the protocol surface is large (Pool / aTokens / debtTokens / IRM / Oracle / UiHelpers). Treat as bounded but non-zero tail risk.