[bisq-network/bisq] Add tx broadcast to mempool explorer api (#4943)

[chimp1984]

Sure can be all added, just today EOD is code freeze for 1.5.2....

But to bring that into the right context: 
The privacy issue here is that node operators could track which transactions are from Bisq. For trade txs that is pretty irrelevant as the trade txs have a pretty significant fingerprint from their structure. For withdrawal txs that more of a concern.

But the Bitcoin node operators are in the same position anyway (much worse if we would use the public network as bloomfilters are terribly broken privacy wise). So for those who do not run their own node there is not much of a change. 

But adding a simple option in the settings might be problematic as well as it requires some conext about the problem to make any informed decision. If users deactivate it and end up with failed trades it also impacts the trade peer (and cause lot of cost for Bisq from supports side).
So to find the right solution here is not as trivial...

-- 
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/pull/4943#issuecomment-745632242
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20201215/f25f51a7/attachment.htm>