-
Notifications
You must be signed in to change notification settings - Fork 195
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
Streaming swaps completion state errors #6086
Comments
Ops was able to recreate and screen record this issue as described above. See the successful "Trade complete Successfully received BTC on Bitcoin" message while the outbound BTC has been sent on chain: Screen.Recording.2024-01-26.at.11.19.16.AM.mov |
@purelycrickets is this the correct screen recording? it seems to be cut short |
Whoops, that was my failed first attempt at recording it. Here is the actual error recorded: |
lol here it is: Screen.Recording.2024-01-26.at.11.19.52.AM.mov |
@purelycrickets that one's a regular thorchain swap. Judging by the BTC showing as received in dropdown at the top of our app (which is totally disjoint to the swapper and runs off blockbook), it the looks the funds were in fact received and it seems the mismatch between us and viewblock is indexing on their viewblock's side - i.e they can take several minutes longer than us to index and display a completed trade. I dont think there is an issue with regular swaps at least. Do we have a recording of the streaming swap issue regarding progress bar not updating? |
summary
When attempting a streaming swap from an EVM to BTC after the initial EVM input transaction was confirmed, the UI showed as Trade Completed / BTC is now in your wallet and the progress bar was still spinning. Even after the BTC was confirmed the progress bar still didn't update.
This was not correct and was much too fast for the outgoing BTC tx to have already been executed.
Will ask operations to recreate and record screen.
Recreation steps
Acceptance Criteria
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response
The text was updated successfully, but these errors were encountered: