Track trades with failed Bitcoin transaction broadcasts

[cbeams]

This is essentially a follow-on to bisq-network/bisq#1193, which was closed with the release of Bisq v0.6.5. We've now seen a number of similar looking failed trades, where one or more of maker, taker and deposit transactions do not get broadcast. Several log files have been analyzed at this point, and it is not clear what is causing them.

I have seen perhaps 4 or 5 such failed trades in the last couple weeks, but just today I saw the same trader incur this problem three times in a row with trades egloilal, dxwmp and ejpdk. Like other "tracking" issues, we'll keep this one open, and @keo-bisq and I can use it to record incidences of this problem.

Any reimbursement support issues related to this problem should include a reference link back to this issue.

[cbeams]

Note that this is the message I used when closing the trades above:

This trade failed due to technical issues. Any lost mining and trading fees will be reimbursed. Please see and subscribe to the support issue at https://github.com/bisq-network/support/issues/[PUT_ISSUE_NUMBER_HERE] for further details and status updates. Please also note that in order to correct your Bisq wallet balance, you may need to resync your SPV file by going to Settings->Network info->Resync SPV file.

[cbeams]

TKGUVL just showed up with this problem. This trade, along with the other three mentioned above have all been with the same onion address on the seller side. I'm investigating with the seller now about what might be causing the issue.

[Thiagojm]

Fee reimbursement for trade anY1E34k #265

[pazza83]

Closing as stale