DeFi Intel

Request: include 25K USDC sent directly to V3 Pool in next Rescue Mission phase

Hi all, On [date] I mistakenly sent 25,000 USDC directly to the Aave V3 Pool contract on [network] instead of supplying via the interface. Tx hash: 0x6a4cd27125fe4916909efdb9e6cc79f298ce514e56bd4851e92641f71c666b5c Pool proxy address: 0x98c23e9d8f34fefb1b7bd6a91b7ff122f4e16f5c Sending wallet: 0x32fcf748e4dcebd1081bfcccb94eb721101f27c0 (I can sign a message to prove ownership) I understand from Rescue Mission Phases 1–3 that recovery of tokens sent directly to upgradeable Aave contracts is technically feasible via a governance-approved implementation upgrade, with claims distributed through the AaveMerkleDistributor to the original sending address. Request to BGD Labs / ACI / the community: could this transfer be registered for inclusion in a future rescue phase covering the V3 Pool? Happy to provide any additional verification needed. Thank you. 2 posts - 2 participants Read full topic

Read full article on Aave_blog →

DeFi Intel is an entity-graph aggregator: we curate, tag and link crypto news to a typed knowledge graph of protocols, tokens, people and incidents. We do not republish the full article body. Use the link above to read the original report at Aave_blog.

Want the full article?

Continue reading on Aave_blog →

Entities mentioned

Stay current on entity-tagged crypto news

Get the weekly DeFi Intel brief — entity-graph intelligence covering protocols, tokens and incidents, free to your inbox.