[Core Protocol] Retrieving Tokens from L1StandardBridge After Failed Bridging #338
-
Did you check the documentation?
Did you read the specs?
Did you check for duplicate questions?
Issue DescriptionSuppose an attempt to bridge an ERC20 succeeds on L1 but fails on L2. Funds have been successfully transferred to the The Is it possible to withdraw these stuck funds? Alternatively, if these are transferred automatically back to the sender at some point, what mechanism is responsible for that? Additional InformationNo response FeedbackNo response |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
Hey @ed-iv, sorry for the delayed response. This is a very good question and I'm not sure of the answer. Please let me ask around and see if I can find someone to answer this. |
Beta Was this translation helpful? Give feedback.
-
Hey @ed-iv, I spoke to a smart contract engineer and found out that this is an outdated note. I've opened a PR to remove it from the contract source code. If a token is bridged with no corresponding token contract on the other side, the deposit will get stuck. |
Beta Was this translation helpful? Give feedback.
-
Hello soyboy
I made a question about finalize bridge withdrawal tx. How they can , ?
Tx on github, the problem if i used another bridge like wormhole they can
create another smartcontract so i can bridge back to L1 , how i can push
this problem , team , blast is ask me to the optimism, bcs they created the
contract ,
Br dika
…On Tue, 4 Jun 2024 at 20.58 soyboy ***@***.***> wrote:
Hey @kayabossq <https://github.com/kayabossq>, unfortunately if you've
bridged to a non-existent or the wrong contract, the tokens will be stuck.
If you're bridging the tokens, its highly recommended to using a bridge UI
and to not interact directly with the contracts on a blockchain explorer.
I'm sorry for your loss of tokens.
—
Reply to this email directly, view it on GitHub
<#338 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIT3GDNIPJXJ6ONBJEI6LLDZFXBZFAVCNFSM6AAAAABFXUPR5WVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TMNRVGM2TS>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
.com>
|
Beta Was this translation helpful? Give feedback.
Hey @ed-iv, I spoke to a smart contract engineer and found out that this is an outdated note. I've opened a PR to remove it from the contract source code. If a token is bridged with no corresponding token contract on the other side, the deposit will get stuck.