# \[Recovery Request\] Accidental Direct USDT Transfer to Aave Contract on Celo — rescueTokens Assistance Needed

**URL:** <https://governance.aave.com/t/recovery-request-accidental-direct-usdt-transfer-to-aave-contract-on-celo-rescuetokens-assistance-needed/25196>\
**Category:** Other\
**Created:** [June 22, 2026, 8:59am UTC](https://governance.aave.com/t/recovery-request-accidental-direct-usdt-transfer-to-aave-contract-on-celo-rescuetokens-assistance-needed/25196 "2026-06-22T08:59:06Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![andrewkimjoseph](https://dub1.discourse-cdn.com/flex013/user_avatar/governance.aave.com/andrewkimjoseph/32/15084_2.png) [@andrewkimjoseph](https://governance.aave.com/u/andrewkimjoseph)\
**Post date:** [June 22, 2026, 8:59am UTC](https://governance.aave.com/t/recovery-request-accidental-direct-usdt-transfer-to-aave-contract-on-celo-rescuetokens-assistance-needed/25196/1 "2026-06-22T08:59:06Z")

</div>

# [Recovery Request] Accidental Direct USDT Transfer to Aave Contract on Celo — `rescueTokens` Assistance Needed

**Date of Incident:** June 20, 2026 **Network:** Celo **Posted by:** Andrew Kim Joseph

* * *

## Summary

I previously submitted this request via email to [wecare@aave.com](mailto:wecare@aave.com) and am following up here to ensure visibility with the broader community and relevant stakeholders.

While attempting to supply USDT to Aave on the Celo network, I mistakenly performed a direct ERC-20 token transfer to an Aave-related contract address instead of calling the appropriate `supply` or `supplyWithPermit` function. As a result, the tokens were sent directly to the contract without minting the corresponding aTokens, and the funds are now effectively locked.

I am reaching out to the Aave community and governance to inquire whether recovery is possible via the `rescueTokens` function, and to request that this be reviewed by the relevant parties.

## Transaction Details

| Field | Value |
| --- | --- |
| **Transaction Hash** | [`0xc26b32a3bb84a8b1672337596fe7cb2906857e70426f4e494e83f07b4406e6ce`](https://celoscan.io/tx/0xc26b32a3bb84a8b1672337596fe7cb2906857e70426f4e494e83f07b4406e6ce) |
| **Network** | Celo |
| **Token** | USDT |
| **Amount** | 52 USDT |
| **Sender Address** | `0xbA34711e2F23cCdb893FF2166f7A71f200E76b80` |
| **Destination Address** | `0x3E59A31363E2ad014dcbc521c4a0d5757d9f3402` |

## What Happened

The transfer was made during an attempt to interact with the Aave protocol on Celo. Instead of invoking the `supply` or `supplyWithPermit` function on the Pool contract, a raw ERC-20 `transfer` was executed directly to the contract address. This resulted in the USDT arriving at the contract without triggering the deposit logic, and no aTokens were minted in return.

## Recovery Request

I understand that recovery of mistakenly transferred tokens is not always possible and is subject to governance processes. However, given that:

- The transfer occurred in the context of a direct Aave protocol interaction
- The destination is an Aave-related contract that may hold recoverable token balances
- The `rescueTokens` function exists in Aave contracts for situations such as this

I am kindly requesting that the Aave team or governance review this transaction and advise on whether a `rescueTokens` call is feasible and appropriate.

## Additional Information

I am the owner of the sending address (`0xbA34711e2F23cCdb893FF2166f7A71f200E76b80`) and am happy to provide any additional verification or information required to assist with the investigation.

_Thank you for your time and consideration. I look forward to any guidance the community or Aave team can offer._

**— Andrew Kim Joseph** 📧 [andrewkimjoseph@gmail.com](mailto:andrewkimjoseph@gmail.com)