Aave founder Stani Kulechov has floated a new risk framework for the protocol after the KelpDAO exploit, according to The Block.
The practical point is simple. Aave doesn’t just list assets. It manages the risk of loans getting liquidated too late or collateral being overvalued. If the framework is approved, Kulechov said it would be applied across all markets and assets.
What Kulechov wants to change
Kulechov’s statement, as reported by The Block, ties the proposal directly to the KelpDAO incident. The message for users is that this is not a one-off patch for a single market. The intent is systemic.
Applying the framework across all markets and assets matters because Aave’s core vulnerability pattern is rarely “one asset breaks on its own.” More often, risk models fail to reflect the real-world failure mode of assets under stress.
Why “across all markets” is the key phrase
If the framework rolls out globally, it could reshape how Aave evaluates collateral and debt across its ecosystem. The risk framework would affect which assets are supported, how they’re parameterized, and how quickly the protocol can react when conditions deteriorate.
That matters because DeFi risk is not static. Liquidity can thin out. Price oracles can lag. Attacks can exploit execution paths or assumptions inside incentive loops. A global framework is the difference between “fixing one hole” and “changing the house rules.”
The missing detail readers will watch next
The Block’s excerpt in this prompt includes Kulechov’s rollout plan but not the technical mechanics of the framework itself. That is the part the market will want to see.
For a risk framework, readers should look for specifics like how it treats oracle behavior during volatility, how it models liquidation dynamics when liquidity is stressed, and how it handles cross-market dependencies.
Even good models can get it wrong. Risk frameworks do not erase risk. They only change how that risk shows up and how fast Aave tries to contain it.
Security context: the KelpDAO angle
The catalyst here is the KelpDAO exploit. In practice, these incidents usually expose gaps in assumptions about how capital and incentives behave when something breaks. The point of Kulechov’s proposal, as framed by The Block, is to translate lessons from an exploit into risk controls that apply broadly.
That broad application is also why the proposal could take time. Protocol-wide parameter and policy changes often come with testing and governance overhead. Until it passes, assets and markets keep operating under the existing framework.
What happens if it passes
Kulechov told The Block that once the proposal passes, the framework will be applied across all markets and assets.
For users, the implication is operational. Expect risk settings and monitoring to evolve. For asset issuers and integrators, expect supported collateral behavior to be re-evaluated under the new rules.
For everyone holding Aave assets as risk exposure, the takeaway is that security work here is governance work. Approval decides whether the protocol changes its risk math at scale.
| Item | What The Block reports |
|---|---|
| Who proposed it | Aave founder Stani Kulechov |
| Trigger | KelpDAO exploit |
| Scope if approved | Applied across all markets and assets |
| Where it goes next | Governance approval process, per the reported “if passes” framing |