Skip to content

Commit

Permalink
Increase our mempool fee estimation from "medium" to "high" priority
Browse files Browse the repository at this point in the history
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
  • Loading branch information
wiz committed Oct 1, 2020
1 parent 6c28d1a commit 8e3b727
Showing 1 changed file with 1 addition and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ protected FeeRate doGet() {

private long getEstimatedFeeRate() {
return getFeeRatePredictions()
.filter(p -> p.getKey().equalsIgnoreCase("halfHourFee"))
.filter(p -> p.getKey().equalsIgnoreCase("fastestFee"))
.map(Map.Entry::getValue)
.findFirst()
.map(r -> {
Expand Down

0 comments on commit 8e3b727

Please sign in to comment.