[bisq-network/bisq] Minimum Fee behaving weirdly (#5486)

[Pac]

<!--
   SUPPORT REQUESTS: This is for reporting bugs in the Bisq app.
   If you have a support request, please join #support on Bisq's
   Keybase team over at https://keybase.io/team/Bisq
-->

### Description

I believe that there is something wrong with the fee estimation implemented in  #5235
I cant find what it is, but the final behaviour here is that it gets a value that is not coming from the mempool.space api (is it an average?) and it also has a 10sats/vb hardcoded minimum.
The image below shows that 21sats/vb, but the minimumFee was 1sat/vb (as far as I can tell from the code, it should use 2xminimumFee).
If I try 10sats/vb, it will accept it, but not less.

![image](https://user-images.githubusercontent.com/6444444/117885572-61baee80-b284-11eb-945e-5a4d3315f510.png)


#### Version

1.6.4

### Steps to reproduce

Try to change the minumum fee.

### Expected behaviour

Should accept at least 2 x minimumFee, but stucks to 10 or a number that it takes from an unknown place.




-- 
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/5486
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210511/dedf6565/attachment-0001.htm>