[bisq-network/bisq] Increase our mempool fee estimation from "medium" to "high" priority (#4585)

[wiz]

<img width="554" alt="Screen Shot 2020-10-02 at 5 15 00" src="https://user-images.githubusercontent.com/232186/94858600-3fe7c680-046e-11eb-9120-ffd65a458c47.png">

Bisq currently uses the mempool.space API for fee estimation, selecting
the "medium" priority fee, which generally works very well. However, if
your timing is bad, sometimes the mempool can quickly fill up and your
TX can get stuck for several hours or even days, which degrades the UX
of Bisq.

This PR changes the Pricenode code to always use "high" priority fees,
which would at the time of writing use 99 sat/vB instead of 85 sat/vB,
and hopefully prevent the above-mentioned issue from occuring. Of
course if the mempool is empty the minimum fees would still be used, as
this only changes the "priority" from medium to high.

Fee estimates: https://mempool.space/
API endpoint: https://mempool.space/api/v1/fees/recommended
You can view, comment on, or merge this pull request online at:

  https://github.com/bisq-network/bisq/pull/4585

-- Commit Summary --

  * Increase our mempool fee estimation from "medium" to "high" priority

-- File Changes --

    M pricenode/src/main/java/bisq/price/mining/providers/MempoolFeeRateProvider.java (2)

-- Patch Links --

https://github.com/bisq-network/bisq/pull/4585.patch
https://github.com/bisq-network/bisq/pull/4585.diff

-- 
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/pull/4585
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20201001/1744fb40/attachment.html>