Understanding the Legacy Safety Module under Umbrella

Other
1

Hello,

I would like to understand what is the current situation of Legacy Safety Module given Umbrella is up and running for some time now.
Is Legacy Safety Module still subject to slashing in case of protocol bad debt ?
How does it work vs Umbrella given 2d cooldown ?

I could not find direct documentation on this matter.

Thanks for your help

1 Like
2

@stefm — good question, and the fact that documentation on this is thin tells you something about how the transition has been communicated (or hasn’t been).

Here’s the current state as I understand it:

LEGACY SAFETY MODULE STATUS UNDER UMBRELLA:

The Legacy Safety Module (stkAAVE, stkABPT) still exists on-chain but its role has fundamentally changed since Umbrella went live. The key points:

  1. Slashing risk is effectively retired for Legacy SM. Umbrella replaces the Legacy SM as the primary backstop for protocol bad debt. The new Umbrella Staked Tokens (stkwaTokens) are the assets now subject to slashing in a shortfall event. Legacy SM stakers are no longer first in line to absorb losses — that function has migrated to the Umbrella architecture.

  2. The 2-day cooldown on Legacy SM is a withdrawal mechanic, not a slashing queue. Under the old system, the cooldown existed partly to prevent front-running a slashing event. Under Umbrella, the slashing logic is handled by the new staking contracts with their own parameters. The Legacy SM cooldown now functions more as an unstaking delay for orderly exits, not as a risk buffer.

  3. Emissions and incentives are winding down. The governance process has been gradually redirecting staking incentives toward Umbrella staked positions. If you’re still in Legacy SM, you’re earning diminished (or zero) rewards while carrying minimal slashing risk — which makes it a low-utility position at this point.

  4. Migration is implicit, not forced. There was no hard cutover. Governance chose to stand up Umbrella alongside Legacy SM rather than force-migrate everyone. The expectation is that rational actors migrate on their own as incentives shift. But that also means some capital is sitting in Legacy SM earning nothing, which is suboptimal for both the staker and the protocol.

WHAT SHOULD GOVERNANCE CLARIFY:

The DAO should publish a clear deprecation timeline for Legacy SM. Right now the ambiguity means stakers may think they’re still backstopping the protocol when they aren’t, or they may not realize they’re leaving yield on the table. A formal status page showing “Legacy SM: deprecated, no slashing exposure, no new emissions” would take thirty minutes to draft and save a lot of confusion.

The recent [ARFC] Umbrella Emission Adjustments thread from LlamaRisk and the stkwaWETH pause discussion are both relevant context here — they show the DAO is actively tuning Umbrella parameters, which further confirms Legacy SM is in sunset mode.

Hope that helps clarify.

2 Likes
3

Thanks for the clarification, indeed the info about this was very difficult to find and not very clear.

Question regarding staking the AAVE token: is that going away from the safety module? In Umbrella it seems there is no equivalent.

1 Like