Closed ghost closed 8 months ago
I will test this on my pricenode.
Tested ACK
After restart with this pr 492b04d:
For about 20 sec it showed btcTxFee: 10
. (far to low)
But then it showed btcTxFee: 107
while another price node shows btcTxFee: 58
The default tx fee (10) is shown until there is some data from providers.
When a provider is offline the default fee rate of 10 sats/vB was being used. In a high fee environment. this pulls down the average calculated from all providers. e.g. at the moment fees are 89 sats/vB and when a provider is offline, the resultant average fee shown on Bisq is 69 sats/vB:
To address this, the offline provider should not pull down the average:
The default fee rate should be chosen only when all providers are offline:
See: https://github.com/bisq-network/bisq-pricenode/blob/6073a3948e7567359adf9f167c27d65a7e352d9a/src/main/java/bisq/price/mining/FeeRateService.java#L78-L81