Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WBTC sent to the contract address by mistake #63

Open
limitless59 opened this issue Dec 29, 2023 · 5 comments
Open

WBTC sent to the contract address by mistake #63

limitless59 opened this issue Dec 29, 2023 · 5 comments

Comments

@limitless59
Copy link

limitless59 commented Dec 29, 2023

Hello, Is there a way to recover wBTC from the contract address?

I just sent some wBTC to the contract address by mistake...

The transaction hash is
0x46988612c51b016e2731477dc4b3d78e3d80be65d30429a1f3d75236eeb1242d

Thank you!

@Charlycharly2014
Copy link

Y3s

@Ytiopig
Copy link

Ytiopig commented Aug 1, 2024

Mod menu

@Ytiopig
Copy link

Ytiopig commented Aug 1, 2024

Mod menu to prank kids

@Ytiopig
Copy link

Ytiopig commented Aug 1, 2024

mod menu

@lkim227
Copy link

lkim227 commented Sep 23, 2024

Sadly, in most cases where tokens are sent to a contract address that is not designed to receive tokens, those tokens are irretrievable. This happens because smart contracts typically do not have a way to release or interact with the tokens unless explicitly coded to do so.
While this is a frustrating experience, it emphasizes the importance of double-checking addresses and being cautious when sending transactions in the Web3 space. It’s advisable to avoid sending tokens directly to contract addresses unless you are sure that the contract is designed to receive them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants
@limitless59 @lkim227 @Charlycharly2014 @Ytiopig and others