[bisq-network/roles] Bitcoin Node Maintainer (#66)

[wiz]

## Cycle 6 report

After receiving multiple reports from users that Bisq was not broadcasting some transactions to the Bitcoin network, I started investigating the BTCNodes, suspecting that some of them may not be relaying the transactions properly.

I hacked together a [Bitcoin Service Check script](https://github.com/wiz/bitcoin-service-check) for my Icinga2 based monitoring system to periodically check (once per minute) if the BTCNodes hard-coded into Bisq were operating properly. The monitoring system immediately found that several nodes had issues:

For @mrosseel's 2 nodes `btc.vante.me` and `btc2.vante.me` I found that the clearnet IP addresses were out of date, and [updated them with the current DNS resolved IP addresses](https://github.com/bisq-network/bisq/pull/3262).

For @tbocek's node `bitcoin4-fullnode.csg.uzh.ch` I found it was unreliable at times, and [removed it entirely](https://github.com/bisq-network/bisq/pull/3264).

For @KanoczTomas's node `http://btc.ispol.sk` I found it was unreliable at times, and got less reliable under heavy load, suggesting it was resource exhaustion or a rate limit. Since @KanoczTomas was unreachable, [we temporarily disabled it using a network filter](https://github.com/bisq-network/bisq/pull/3263). However, since @KanoczTomas has since returned and fixed his node by removing the connection limit, we are planning to re-add it soon, after verifying it with the monitoring alerts system that it is stable.

/cc https://github.com/bisq-network/compensation/issues/380

-- 
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/roles/issues/66#issuecomment-540637627
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191010/95db97e1/attachment.html>