Save the Lend tokens that are stucked in the Lend contract

Hey everybody! I know it might be frustrating to keep waiting, but things are progressing nicely!

It’s still WIP but we’ll have more updates down the line. We’ll save those tokens!


good morning Zerodot! I know they are making progress to resolve the issue, but can I know what stage of resolution is?

1 Like

Yes, I am also looking for that answer

1 Like

Considering that releasing tokens stuck in multiple smart contracts of the ecosystem requires different upgrades on critical parts of the system, the solution is being carefully evaluated before proposing to governance.
But as @Zer0dot mentioned, there should be news pretty soon


Thanks for letting us know.
Much appriciated!

Sorry to be a squeaky wheel once again, but is there any timeline for this issue to be brought to a conclusion? I know the AAVE team is juggling multiple and relevant projects at the same time, and I’m afraid that this one may be a low priority. If that’s the case, is fine, but I’d rather not be “hoping” for a solution is there’s not going to be one.
At the end of the day, it was my (back then) rookie error sending a significant amount of money to the wrong address.


For sure there are others & I am one of them patiently waiting for a resolution.


1 Like

Yes, I am also waiting for an update and a timeframe… I have GUSD stuck… hopefully I can get it back at some point. It was just a copy and paste error sending funds into the lending address by accident…

1 Like

I`m waiting the same.

To provide a bit of clarity on why this is taking a bit of time. Even if this can seem like a “trivial” work, the criticality of all systems involved is pretty high, for example the Lend to Aave migrator or the AAVE token itself.
Also, this effort at the moment is purely community-led, and there are multiple other developments in parallel. Considering that funds “locked” are just there and there is no risk of them to be lost, at least for me as member of the community it is understandable that the priority is low compared with the effort needed (considerably high security-wise).
That being said, if anybody from the community wants to lead this initiative to move it forward faster, I would be happy to support technically (and other members of the community too).


I read the dedicated poll and understand that AAVE governance is working on the issue.
I made a similar accidental mistake two days ago. For some unknown reason, the address for sending my USDC funds from metamask got messed up and the funds were sent to the AAVE amUSDC address (Contract Address 0x1a13f4ca1d028320a707d99520abfefca3998b7f | PolygonScan). This is the transaction ID: 0x5b51f2ec1829b39d151a0c8047e6b20de0e25c62a814d137f5bf9c3fc9f6f9ff
I see that this AAVE amUSDC address is the same I used for a previous transaction (maybe 10 minutes earlier) to repay the debt on AAVE. Anyway, the funds are in AAVE’s hands now…
I sincerely hope that AAVE can help retrieve my funds.

Hello @eboado! Thanks for reaching out.

Wasnt @Zer0dot the one who was assigned for the task? Peter, if you can, could you please clarify. Thanks!

Also @MarcZeller have mentioned not once that the task is in the security review stage. And it was a long time ago.

Ofcourse i understand it is not a priority, but still, it seemed as there was a consensus on that issue from the genesis team and the community, and now you are saying that the incentive is purely community-led.

So if genesis team could just clarify on whats going on, would be much appreciated.


1 Like

I share exactly the same as you MUMU. They should give us more sincerity.

add me to the list of people who have made the mistake. The transaction hash is 0x5d4448835bbb09a75ec10689b230e2bcbd97c89558a34ec07f590b1f469c0206 :frowning:

@Zer0dot Have there any news?

Because already have passed one year and four months that the topic began.


1 Like

Hello Everybody,

I don’t know is this a right place but I made a mistake in rush - POLYGON chain Token amDAI is lost.

I felt my wallet might be hacked and wanted to transfer tokens to another MMask wallet. Long story short, I pasted the wrong adress in the transaction adress (after test transaction I added token manually to new MMask, after that didn’t copy wallet adress again in a rush).

Is there any chance to have any help, or where to knock the door for an answer?

Stay safe and wise in DeFi Lands. Besties.

Attn. to the Governance Team

Hello Every one, I mistakenly sent my AAVE tokens to the AAVE smart contract address instead of my Wallet (ON POLYGON CHAIN)…. I kept my 10.34 AAVE for more than 1 year , and i just lost them in one click …by mistake copying the smart contract adress instead of my Wallet one (you know copy/paste)

here is the Transaction Hash → 0xbbfeab7454c0564194738699ca9e532e5fff9740104b5fba8b3751295a8834ff

I don’t know if there is anything you can do about that; I’m so disappointed to have lost my AAVE token like that. Thanks in advance for your support. Jerome

Hey guys!

It’s been a while but a token rescue solution is in the works. It sucks to have lost funds and feel powerless, but with the community’s support (via governance), a solution will be implemented! It’s hard to be patient on something like this!


It is hard NOT to love Your answer. I hope there will be any info about what to do next. I mean If we have to do something/somehow interact with the contract? Or the contracts would recognize this transactions and refunds blocked tokens?
I hope it will happen before next Bull Run :)

Hi all , Zer0dot ; that’s good news ! hopefully I’ll get my token back one day ! It shows how AAVE is getting more an more mature and ready to welcome more mainstream users …! Mistakes happen, Customers (Users) cannot just lost their fund in one click , like that, especially while interacting within the protocol itself. in the future, there must be an official communication governance channel like e-ticket to claim this kind of errors, otherwise mainstream users will never put their funds in Defi.

My ref: 0xbbfeab7454c0564194738699ca9e532e5fff9740104b5fba8b3751295a8834ff

1 Like