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

[Oscar Guindzberg]

I think the broadcasting problems we had recently are not really broadcasting problems, but a consequence of a previous problem that made bisq to create invalid txs.

In any case, it is good to be on the safe side.

Broadcasting means exposing privacy to the server. 

Electrum seems a good trade-off.
Ideal solution:
- nodes provided by trustworthy persons of the bisq community
- nodes behind tor
- using SSL to communicate to the server

I wrote a java API to communicate to an electrum server: https://github.com/electrumj/electrumj/
This is the method for broadcasting a tx: https://github.com/electrumj/electrumj/blob/main/src/main/java/org/electrumj/ElectrumClient.java#L385



-- 
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-742640657
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20201210/3edeacf0/attachment.htm>