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

wiz notifications at github.com
Fri Nov 1 18:35:24 UTC 2019


Thanks for typing this up, just to update from my side I'm working on #1 and #2 already:

For #1, we have a self-hosted mempool fee estimation API service ready for all btcnode operators to deploy immediately, it's the backend we run on https://mempool.space/api/v1/fees/recommended we just need to serve it on a Tor hidden service from each btcnode as well.

For #2, we can have btcnode operators run the self-hosted electrs backend on their btcnode and serve the block explorer REST API over a tor hidden service so Bisq can query these btcnodes if the TXID is in the Bitcoin mempool or not.

For #3 and #4 are you working on implement these already?

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


More information about the bisq-github mailing list