-
Notifications
You must be signed in to change notification settings - Fork 79
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
Swaps failed without sending a transfer proof #651
Comments
Swap
|
Swap
Important note I just realized -- both only refunded (or were seen by the ASB as refunded) after restarting the ASB client. |
Unsure what to do about this, we may want to configure the electron client to do more retries in case the connection gets closed. |
We added more retried to the electrum client in 0.8.2. Has the issue been resolved after upgrading. Would like to close this issue if so. |
I unfortunately cannot test ATM, but retries should correct the issue as it was always resolved after an ASB restart (forcing a reconnection attempt to Electrum). |
Hi there,
I've been running on mainnet and so far have had two swaps fail completely.
Here are the relevant logs (AFAICT) on both:
Swap dbf32b87-2a14-4848-a1a5-9bddd3e752da:
Swap 2c5487d-e29d-4753-9a19-49a64e40cb20:
(For further context on this swap, see #648)
My ASB was up and reachable AFAICT throughout both swaps, though I saw similar lines to the below for each swap:
Let me know if there is any other data I can gather or provide around this.
Version: running the x86_64 artifact from https://github.com/comit-network/xmr-btc-swap/actions/runs/1141616002 to test the fix in #649.
The text was updated successfully, but these errors were encountered: