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

[wiz]

I agree that fee estimation is a hard problem, and that's why I've been contributing to the [Mempool.space](https://mempool.space) project for the past several months, which is one of the most respected Bitcoin mempool analysis websites available - it's much better than 21 / earn.

[Mempool.space](https://mempool.space) updates its database every few seconds to project the next X blocks that will be mined, and uses this data to estimate fees in the next X blocks. I actually observe the mempool all day every day on a dedicated display, to constantly check if the "next block fee" is accurate or not. What you consider "best" may not be what I consider "best", but since this API updates in realtime from the live mempool state, I think this is a very good starting point, and much better than the current centrally hosted CPOF at earn. This way we can all self-host our fee estimation backend.

-- 
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-548929647
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191101/c88d7bbf/attachment.html>