Affects: Aave v3 (protocol)
What happened
Aave DAO voters approved the fxSAVE temperature check, advancing the proposed Ethereum Core collateral listing to ARFC analysis.
What changed
fxSAVE entered formal risk review as a potential collateral asset carrying f(x) Protocol strategy, smart-contract, liquidity, leverage, and underlying stETH dependencies.
What did not change
No collateral parameters, oracle, ARFC approval, AIP, execution, or live reserve was established by the temperature check.
Confirmed
- The Snapshot closed on July 18, 2025 with approximately 811,728 voting YAE and negligible opposition.
- The target market is Aave v3 Ethereum Core.
- The proposal identifies fxSAVE as a yield-bearing f(x) Protocol token.
- The proposal defers risk parameters to later service-provider analysis.
- The stated next governance stage is an ARFC.
Still open
- Asset contract and complete dependency mapping.
- Collateral, liquidation, cap, E-mode, and oracle parameters.
- Upgrade, pause, redemption, liquidity, and strategy-loss controls.
- ARFC, AIP, and execution outcomes.
What it means for an advisor
- Require a full fxSAVE and f(x) dependency review before any Aave memo expansion.
- Monitor later parameters and execution without treating temperature-check approval as a live or suitable collateral listing.
Sources
- [TEMP CHECK] Onboard fxSAVE to Aave V3 Core Instance · Aave DAO Snapshot · · effective
Version 1, published . We check this event again on . Educational research, not investment advice.