[bisq-network/bisq] Stuck transaction even post-arbitrator cancellation. (#3335)

[wiz]

hey @ifarnung do you remember if you set custom fees to 1 sat/byte in your settings at the time this bug occurred? there seems to be 2 bugs causing TX fail to broadcast, one for "dust" and one for "fee too low", but the latter would only occur if you set fees to 1 sat/byte because default is 10 sats/byte minimum so just want to get more information to help investigation thanks

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/issues/3335#issuecomment-536859108
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190930/6ebc0468/attachment.html>