mirror of
https://github.com/bisq-network/bisq.git
synced 2024-11-19 09:52:23 +01:00
Increase our mempool fee estimation from "medium" to "high" priority
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
This commit is contained in:
parent
6c28d1a097
commit
8e3b727d07
@ -91,7 +91,7 @@ abstract class MempoolFeeRateProvider extends FeeRateProvider {
|
||||
|
||||
private long getEstimatedFeeRate() {
|
||||
return getFeeRatePredictions()
|
||||
.filter(p -> p.getKey().equalsIgnoreCase("halfHourFee"))
|
||||
.filter(p -> p.getKey().equalsIgnoreCase("fastestFee"))
|
||||
.map(Map.Entry::getValue)
|
||||
.findFirst()
|
||||
.map(r -> {
|
||||
|
Loading…
Reference in New Issue
Block a user