Hi,

I'm hoping BU node operators can give us a bit of quick feedback on the following points (reply in this thread, don't give out identifying details of your nodes e.g. IPs):

1. if you are still running BU 1.0.1.4 nodes, can you tell us what percentage of those you have re-enabled xthinblocks on (i.e. remove 'use-thinblocks=0' from the config) after the last incident?

2. If you have not re-enabled xthinblocks at all and are running 1.0.1.4, what stopped you from upgrading to 1.0.2.0 and re-enabling xthinblocks? Are you aware that the previous exploits are fixed in 1.0.2.0?

3. Could you have a look on your node with the following commands, and report back the numbers of matching peers? (if you are using the GUI you may want to check this using debug console)

   a) bitcoin-cli getpeerinfo -> report total number of (BitcoinUnlimited BitcoinClassic BitcoinXT peers)

   b) In the 'getpeerinfo' output, how many peers in total are showing xthinblock support, i.e. "services": "00...0000015" (all zeroes with '15' at the end)

4. If you are running release 1.0.2.0 or a 'dev' branch build, you could help us by performing a little field test relating to how quickly nodes are able to re-acquire xthin capable peers and whether some parts of the BU node network are isolated in some way. To do this, you would need to stop your client, move away its peers.dat list (make a copy to somewhere and remove it), then restart and measure the numbers for 3(a) and 3(b) after 24 hours, and report the numbers here (along with which version you were running, and it would help if you list any customized parameters you might be using relating to peer connections, e.g. maxconnections, maxoutconnections, min-xthin-nodes).