[bisq-network/bisq] Potential mining fees issue. Somewhat repeatable. (#3249)

[ifarnung]

I was going to try to better explain the issue I'm having as for me it's repeatable every time I make a second order, but @Wiz and I did some real time troubleshooting with him trying to replicate the issue on his end, and he was able to figure out why it was happening.

While an order that has just been created isn't confirmed on-chain, any subsequent orders will use a higher fee estimate than the initial order.  So this is why the fee on every second order I created would jump even if the mempool was similarly full. 

So now, I can just wait until the order has some confirmations (I think 2 or 3 until the fee goes back to the minimum estimate) and then create a new order.  At least for me, this is a better way to manage blockspace usage.

Thanks @wiz for your help and I will close this issue.

-- 
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/3249#issuecomment-533815798
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190921/ea708f2f/attachment.html>