KVORUM
aaveSource: Aave governance v3 · #522

Safety Module August 2026 - Allowance Update

executedSep 24, 2026, 11:53 AM UTCby2C0x2cc1…4df1

01Summary

AISummary by Kvorum

An AI summary is not generated yet. Read the description →

02Description

438 words

Simple Summary

This AIP tops up the AAVE allowance funding stkAAVE rewards so that it fully covers the accrual since the snapshot plus 90 days of future emissions at the unchanged rate of 150 AAVE per day, together with one quarter of the 50,500 AAVE backlog gap accumulated before the snapshot, and resizes the allowances of the three sunset Safety Module tokens (stkABPT v1, stkGHO, stkAAVEwstETHBPTv2) so that each one matches its residual claimable rewards. These modules have been updated to have no emissions, so the values are absolute. No emission rate, cooldown or slashing parameter is modified.

Motivation

Every Safety Module stake token pays its AAVE rewards out of the Ecosystem Reserve through an ERC20 allowance. Rewards accrue to stakers continuously, but the allowance is only consumed when a staker claims. Once the allowance is exhausted, every claim reverts until governance tops it up.

At the snapshot (block 25843055, 2026-08-27), the stkAAVE allowance covered only 8.4% of what stakers had already earned. Given the size of the accumulated backlog, this proposal funds the ongoing accrual and the full 90-day forward buffer, plus one quarter of the backlog gap now, keeping the standing approval limited while claims resume; the remaining backlog can be funded through future allowance updates. The three sunset modules emit nothing, so their allowances are set to absolute values slightly above their residual claimable rewards; in particular, stkAAVEwstETHBPTv2 holds 7.4 times what it can ever owe, and reducing it releases roughly 14,400 AAVE of standing approval without affecting any claimant.

Specification

The payload calls AaveEcosystemReserveController.approve(ECOSYSTEM_RESERVE, AAVE, module, amount) for each of the four modules, resetting the allowance to 0 before setting the new value (same pattern as AIP 439).

ModuleAddressNew allowance (AAVE)
stkAAVE0x4da27a545c0c5B758a6BA100e3a049001de870f5currentAllowance + 50,500 / 4 + emissionPerSecond x (block.timestamp - snapshot + 90 days)
stkABPT v10xa1116930326D21fB917d5A27F1E9943A9595fb471,250 (absolute)
stkGHO0x1a88Df1cFe15Af22B3c4c783D4e6F7F9e0C1885d1,200 (absolute)
stkAAVEwstETHBPTv20x9eDA81C21C273a82BE9Bbc19B6A61822120681012,500 (absolute)

The new stkAAVE allowance is computed at execution time as the sum of the allowance read at execution, one quarter of the 50,500 AAVE backlog gap measured at the snapshot (claims between snapshot and execution reduce the allowance read at execution by the same amount, so no already-claimed rewards are double counted), the accrual since the snapshot timestamp (1787791523) and 90 days of forward emissions, both read on-chain from the stkAAVE emission configuration.

References

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorum

A calldata-vs-description analysis is not generated yet. Review the decoded actions →

04Actions

1 total
#0execute()chain 0x1
Target
0x2801…b843
Value
0 wei
Function
execute()
Arguments
{}
Calldata

05Tally

Summed from votes

Voters0
VP participating0
Outcome (current)—
Current support—

06Voters

0 total

No votes recorded yet.

07Forum

No forum thread is confidently linked to this proposal.