The phrase 'unstoppable money' has stopped four times this year. By my count.
The phrase 'unstoppable money' has stopped four times this year. By my count.
EURC 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.
You deposit EURC (a euro stablecoin) on Ethereum and earn 2.23% APY, supplied by borrowers who pay 3.94% to take loans in EURC. Your deposit is redeemable whenever $17.53M in liquidity is available; currently 63% of the reserve is lent out. EURC cannot be used as collateral—it's borrow-only—so your role is purely as a lender. The supply rate is set by borrow demand: borrowers' 3.94% rate × 63% utilization × (1 − 10% reserve factor) flows to you.
Active reserve under standard Aave governance; no pause, freeze, isolation, or siloed flags present.
Supply APY tracks borrow demand against EURC. At 63% utilization and 10% reserve factor, rates are stable—neither crowded (≥85%) nor starved (≤20%). Modest but steady inflows from borrowers seeking euro exposure.
No elevated risks flagged. Stablecoin depeg signal is healthy. EURC issuer not listed in registry, so direct redemption or custody terms are not documented on-chain; standard operational risk for stablecoins without explicit treasury backing disclosure.
Good fit for conservative allocators seeking low-volatility euro yield and comfortable holding EURC off-exchange. Avoid if you need frequent redemptions—$17.53M available liquidity covers only 37% of supply.
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.
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.