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

[chimp1984]

<!--
   SUPPORT REQUESTS: This is for reporting bugs in the Bisq app.
   If you have a support request, please join #support on Bisq's
   Keybase team at https://keybase.io/team/Bisq
-->

### Description

As we have the unresolved issue that sometimes transactions does not get successfully broadcast and we have not managed to find out the issue which causes that (likely a bitcoinj problem as it does conceptual not support well multiple wallets as we use with BSQ and BTC) I suggest that we send the raw transcation to an explorer API for increasing the chances that the tx gets into the mempool.

Bisq contributors run a few mempool space explorer nodes and we could use those as default nodes. We can add a setting that the user could define their own node as well (I guess its not needed for the first version).

Another option would be to use Electrum or send it to Bitcoin core nodes. 
Requires a bit more thought and investigation whats the best option here.

We should also keep in mind that using external APIs for blockchain data can be used for further use cases like look up if a tx is in the mempool, look up if peers trade fee tx is in the mempool and confirmed, lookup miner fees used in peers txs,...
So the choosen model should be usable for those use cases as well.

@wiz Does mempool.space API support broadcast of raw txs?
@jmacxx Would you be interested to work on that?


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