-
Notifications
You must be signed in to change notification settings - Fork 31
Bug? — Recover transaction failed #194
Comments
@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. |
@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. |
@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. |
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:
The text was updated successfully, but these errors were encountered: