sqrrm

## 2019.02 report CVE-2018–20587 reported, decided that no action was needed. @KanoczTomas planning on taking over as secondary node maintainer https://github.com/bisq-network/compensation/issues/228#issue-415543390

## 2019.03 report Nothing to report for March https://github.com/bisq-network/compensation/issues/253

## May 2018 report Paying for a bitcoinaverage sub used by manfred. Compensation request at https://github.com/bisq-network/compensation/issues/77

## May 2018 report Ran two full instances, both onion and clearnet with no issues. Compensation request at https://github.com/bisq-network/compensation/issues/77

@cbeams @ManfredKarrer I feel I should take this one. My organizational skills are really not made for any kind of admin role but this one seems pretty manageable.

## 2018.06 report - 2018-06-07 restarted tor service on 3r44ddzjitznyahw.onion as it was not reliably accepting tor connections, looks good after tor restart ### End of month No further issues...

## 2018.07 report Run two instances with both clear net and onion. No issues to report.

## 2018.08 report i3a5xtzfm4xwtybd.onion had a hard drive crash. After replacing the hard drive it also stopped spontaneously, seemingly due to a tor issue and had to be restarted. ##...

## 2018.09 report Running 2 instances, both onion and clear net. Upgraded to v0.16.3 due to bitcoind bug.

## 2018.10 report 2018-10-23: Updated nodes i3a5xtzfm4xwtybd.onion, 3r44ddzjitznyahw.onion to version 0.17.0