-
Notifications
You must be signed in to change notification settings - Fork 728
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
Accidentally sent to the wrong token recipient which caused minting error #268
Comments
I'm surprised any UI would let you do that. Still, you are right there is no way to "rescue" funds for a good reason: This unfortunately means your transfer is irreversible unless you manage to create a token account with the correct mint at that address. |
@hendrikhofstadt Got it. It's my fault that I put the wrong address directly in the etherscan without using any UI. Thanks for answering my question. 🙏 |
@hendrikhofstadt Sorry to bother you again. I'm not really familiar with Solana contract. According to this
I'm wondering if I could close associated account and re-initialize it again with the same address but different main tokens? Like below demonstration: I think I need to get the associated account's private key which I can use it as a signer like above shows. So, is it possible to do that? 🙏 |
Hi developers, I knew here is not a good place to ask about bridge transaction issues.
However, I couldn't find the support team in discord channel. That's why I try to reach out to you guys here.
My issue is that I sent FRAX to my Solana BUSD address as below transaction shows:
(My token didn't mint out because of this line's protection https://github.com/certusone/wormhole/blob/main/solana/bridge/src/processor.rs#L933)
It seems that wormhole contracts didn't have any rescue methods. Is there any way to rescue this stuck tokens? 🙏
Many thanks
The text was updated successfully, but these errors were encountered: