[bisq-network/bisq] Send raw transactions to explorer API for better redundancy at tx broadcast (#4932)

[chimp1984]

I discussed with @sqrrm the topic to use Eletrum or mempool.space and we got convinced its better to use mempool.space for now.
The reasons are:
- Our use case is very simple and impl. can be done faster more robust and using patterns we already use in other cases (http request over tor)
- The main reason why Electrum was considered was for possible future use cases which require more sophisticated features. So far we have nothing concretely planned for that. The next feature we might integratet is tx look ups but that is easily done by mempool.space as well. Migrating away from BitcoinJ will require an other updated research about best alternatives (back then we ended up with Electrum, but quite some tima has passed and might be Neutrino is ready not to use or there are other new candidates which follow a more decentralized model). Starting with Electurm now would be kind of premature optimizing.
- Adding another library comes with new dependencies. We want to avoid new dependencies as far as possible. A simple http request is much cheaper than to do it via a Electrum client supporting the Electrum protocol. 
- The use case is for getting more redundancy to mitigate proplems from a system which suffers from too high level of complexity (BitcoinJ). Keeping newly added complexity for that "backup" solution at the minimum seems to be the better choice here.
   

-- 
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/bisq/issues/4932#issuecomment-743310532
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20201211/8e0fb743/attachment.htm>