Skip to content
This repository has been archived by the owner on Sep 27, 2023. It is now read-only.

Bug? — Recover transaction failed #194

Open
dafacto opened this issue Apr 6, 2021 · 5 comments
Open

Bug? — Recover transaction failed #194

dafacto opened this issue Apr 6, 2021 · 5 comments

Comments

@dafacto
Copy link

dafacto commented Apr 6, 2021

Six days ago, I bridged the ALCX token, but was unable to complete the transfer as the UI got stuck on "Confirming 0/20".

Today, six days later, I tried to restore the transfer. After entering the transaction hash, I was presented with the "Deposit in NEAR" step (minting).

However, clicking that button resulted in this error:

@mfornet
Copy link

mfornet commented Apr 21, 2021

@dafacto can you confirm if this is still an issue? We fixed a bug in the prover, that was provoking this. If this is working already please close this issue.

@dafacto
Copy link
Author

dafacto commented Apr 22, 2021

@mfornet Still having the issue. I just tried to restore the transaction, and when doing the Deposit to NEAR step, go this:

@mfornet
Copy link

mfornet commented Apr 22, 2021

@mfornet Still having the issue. I just tried to restore the transaction, and when doing the Deposit to NEAR step, go this:

Did you try with a new transfer? if you are trying to finalise a transaction that started more than two weeks ago it is not possible to do it, because relevant ethereum block header for proof was garbage collected.

@dafacto
Copy link
Author

dafacto commented Apr 22, 2021

@mfornet It was with an original transaction, from 22 days ago. I wouldn't know how to reproduce the conditions under which the error was produced, in order to test this again.

@mfornet
Copy link

mfornet commented Apr 22, 2021

@mfornet It was with an original transaction, from 22 days ago. I wouldn't know how to reproduce the conditions under which the error was produced, in order to test this again.

Can you share the hash of the tx in Ethereum when you locked those tokens, to investigate further. Very likely the current error is because the relevant header was garbage collected, but it still worth investigating the previous issue.

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

No branches or pull requests

2 participants