[bisq-network/projects] Migrate Bisq pricenodes from earn.com fee estimation API to our own self-hosted mempool fee estimation API service (#27)

cd2357 notifications at github.com
Sun May 3 13:18:44 UTC 2020


If my understanding is correct, all Bisq nodes have access to Bitcoin Core (either to a local node, or through a service interface exposed by a full node).

In that case, why not just use Bitcoin Core's mechanism for fee estimation? They already expose it through their API: [estimatesmartfee](https://bitcoin.org/en/developer-reference#estimatesmartfee). The fee estimation call can take different parameters: for example, the caller can indicate in how many blocks they wish to have the tx confirmed, or the estimation mode (conservative or not).

Using this API in Bitcoin Core would achieve 2 things for Bisq:
1. one less dependency on a 3rd party, centralized service (earn.com API)
2. a more accurate and flexible fee estimation algorithm

I've already used it in other projects via the [Java interface](https://github.com/Polve/bitcoin-rpc-client/blob/04a442accef8cb3c01349ec5c4a28c172586ec9b/src/main/java/wf/bitcoin/javabitcoindrpcclient/BitcoinJSONRPCClient.java#L471) exposed by [bitcoin-rpc-client](https://github.com/Polve/bitcoin-rpc-client), seems to be a good match for Bisq's use-case.

-- 
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/projects/issues/27#issuecomment-623109044
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200503/757a938f/attachment.html>


More information about the bisq-github mailing list