Aave

Simple Summary

Activation of Aave rescue mission Phase 1, Level 2 (Long) Executor part

Motivation

Since the birth of the Aave ecosystem, multiple people have sent tokens by mistake to incorrect addresses.

In some cases, when the transfer is to another unknown wallet, the tokens are usually locked and lost forever, as it is factually impossible to prove that the transfer was a mistake.

But there are special cases, where the transfer happens to a well-known smart contract address of the ecosystem, for which is simple to understand that the action was really a mistake, as there is no rational reason to send tokens there.

In the case of Aave, the existence of upgradeable smart contracts across the ecosystem makes technically possible the recovery of such tokens sent by mistake. Consequently, given the requests from members of the community affected, we have come up with a plan to “rescue” those funds, providing the affected people a way to recover them.

This initial phase will affect the following:

• Users who sentAAVE, LEND, USDT and UNI to the AAVE token smart contract
• Users who sent LEND to the LEND smart contract
• User who sent LEND to the LendToAaveMigrator smart contract
• Users who sent AAVE and stkAAVE to the stkAAVE contract

The LEND sent to the specified contracts will be claimed already as AAVE tokens with the transformation LEND to AAVE already taken into account (1 AAVE = 100 LEND)

Specification

To rescue the tokens specified on Phase 1 that are on AAVE and stkAAVE token contracts, the payload will connect and initialize the new implementations for the AAVE token and the stkAAVE token with appropriate amounts and send them to the AaveMerkleDistributor specified on the Rescue Short Executor Proposal. To be as less invasive as possible, these new implementations only include that extra logic on their initialize() function, with everything else remaining the same.

• AaveTokenV2: from this new implementations the following tokens will be rescued:
  • LEND: 19845132947543342156792 LEND in WEI (~19845,13 LEND).
  • AAVE: 28420317154904044370842 AAVE in WEI (~28420,32 AAVE).
  • UNI: 110947986090000000000 UNI in WEI (~110,95 UNI).
  • USDT: 15631946764 USDT in WEI (~15631,95 USDT).
• StakedTokenV2Rev4: from this new implementation the following tokens will be rescued:
  • AAVE: 768271398516378775101 AAVE in WEI (~768,27 AAVE).
  • stkAAVE: 107412975567454603565 stkAAVE in WEI (~107,41 stkAAVE).

References

A list of relevant links like for this proposal:

• forum discussion
• tests
• Contracts:
  • ProposalPayloadLong
  • AaveTokenV2 Implementation
  • StkAaveTokenV2Rev4 Implementation

Security Considerations

The contracts have been audited by Certora, and the report can be found here

Implementation diffs have been generated to see that the new implementations only differ on the rescue logic:

• AaveTokenV2 Diff
• StkAaveV2Rev4 Diff

Storage layouts diffs have also been generated for the contracts where the implementation is updated:

• Aave Token storage layout Diff
• StkAave Token storage layout Diff

Deployed Contracts

• ProposalPayloadLong
• AaveTokenV2 Implementation
• StkAaveTokenV2Rev4 Implementation

Copyright

Copyright and related rights waived via CC0.