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
Describe the bug
The swap backend asb starts a swap, and appears to discover midway through that it does not have enough money to complete the swap, probably due to price fluctuations.
Instead of refunding or cancelling the swap, asb simply waits. In many cases, only when asb is restarted does it start showing messages about cancelling or refunding.
Lost/trapped Funds
Unclear. Taker funds may be stuck until asb restarts, or a timelock expires.
Debug logs
{"timestamp":"2024-02-22T03:08:22.410444973Z","level":"INFO","fields":{"message":"Advancing state","state":"btc is locked","rate":"0.0024472 BTC"},"span":{"id":"f00-b4r","name":"swap"},"spans":[{"id":"f00-b4r","name":"swap"}]}
{"timestamp":"2024-02-22T03:08:23.147506204Z","level":"ERROR","fields":{"error":"JSON-RPC request failed with code -17: not enough money"},"span":{"id":"f00-b4r","name":"swap"},"spans":[{"id":"f00-b4r","name":"swap"}]}
{"timestamp":"2024-02-22T03:08:23.147607349Z","level":"ERROR","fields":{"message":"Swap failed: JSON-RPC request failed with code -17: not enough money: JSON-RPC request failed with code -17: not enough money","swap_id":"f00-b4r"}}
Platform (please complete the following information):
ASB
Software Version 0.12.3
Operating System: Debian
The text was updated successfully, but these errors were encountered:
Describe the bug
The swap backend
asb
starts a swap, and appears to discover midway through that it does not have enough money to complete the swap, probably due to price fluctuations.Instead of refunding or cancelling the swap,
asb
simply waits. In many cases, only whenasb
is restarted does it start showing messages about cancelling or refunding.Lost/trapped Funds
Unclear. Taker funds may be stuck until
asb
restarts, or a timelock expires.Debug logs
Platform (please complete the following information):
The text was updated successfully, but these errors were encountered: