You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is from makers perspective. What happened: taker filled our sell eth/btc order, taker's eth side needed to be collateralized which caused the connext eth payment to timeout (60s) as well as the xud swap (90s) and the eth payment was never sent.
Due to lack of #1708, xud currently doesn't know about the status of the connext htlc, thus assumes it's up and throws the swap into swap recovery. So far correct.
But then when I went ahead and restarted xud, swap recovery was not monitoring the swap anymore. Checking the xud db, the swap state changed to 1 (errored). We need to find out what changed the swap state to 1 and prevent that from happening so that swap recovery continues monitoring the swap.
This is from makers perspective. What happened: taker filled our
sell eth/btc
order, taker's eth side needed to be collateralized which caused the connext eth payment to timeout (60s) as well as the xud swap (90s) and the eth payment was never sent.Due to lack of #1708,
xud
currently doesn't know about the status of the connext htlc, thus assumes it's up and throws the swap into swap recovery. So far correct.But then when I went ahead and restarted
xud
, swap recovery was not monitoring the swap anymore. Checking the xud db, the swap state changed to1
(errored). We need to find out what changed the swap state to1
and prevent that from happening so that swap recovery continues monitoring the swap.xud log: https://paste.ubuntu.com/p/Y8ZzWhwZJk/
The text was updated successfully, but these errors were encountered: