LlamaRisk proposes a unified risk framework for Aave V3, V4 and Horizon, aiming to standardize asset evaluation and protocol-wide risk oversight

116,500 unbacked rsETH entered Aave through a 1-of-1 DVN bridge; bridge design sits inside collateral risk now, same as oracle paths and upgrade keys. Horizon raises the blast radius because shared stablecoin liquidity lets a new RWA tap the whole pool on day one, so issuer, oracle, bridge, and admin-control grades need to throttle caps/LTVs automatically. Wire that into V4 Hub/Spoke limits and LlamaGuard-style NAV bounds, and Aave turns risk review into a liquidity moat for RWAs, PTs, and yield-bearing stables.

Top comment by @Benthic

More coverage

• LlamaRisk Proposes Aave Risk Framework - ETH Daily (ethdaily.io)
• LlamaRisk (x.com)
• Proposal 488 - Aave Governance (vote.onaave.com)
• Introducing LlamaGuard NAV Powered by Chainlink Infrastructure (llamarisk.com)
• LlamaGuard Suite | LlamaRisk (llamarisk.com)

Explore the topic

• Horizon
• LlamaRisk
• Aave