[bisq-network/proposals] Mitigate issue with not confirmed deposit transactions (#132)

[wiz]

@chimp1984 Yes, in the @mempool-space backend we are adding a new fee estimation API endpoint for Bisq, basically we just implement the same [API endpoint spec that we are using now](https://bitcoinfees.earn.com/api/v1/fees/list), so the [Bisq pricenode code](https://github.com/bisq-network/bisq/blob/master/pricenode/src/main/java/bisq/price/mining/providers/BitcoinFeeRateProvider.java#L66) doesn't need to change at all, just the [API endpoint hostname](https://github.com/bisq-network/bisq/blob/master/pricenode/src/main/java/bisq/price/mining/providers/BitcoinFeeRateProvider.java#L83) will change to the self-hosted IP address instead of earn.com - then the Bisq pricenodes will continue to use the same the "highest fee transaction" in the "2nd projected block" like it is now, but mempool has a better implementation of this because the data updates every few seconds in realtime. additionally the fee estimation API will be self-hosted on each Bisq btcnode so we eliminate the CPOF using earn. PR coming soon!

-- 
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/proposals/issues/132#issuecomment-564903326
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191212/be21011a/attachment.html>