Quote from: gatra on December 22, 2016, 06:16:48 PM

Hi people,

It is clear that the large reorganisations are caused by riepool having more than 50% "hashrate", but I don't think Simba84 is doing it on purpose.
If his pool node gets isolated from the network but the pool keeps running then when he connects back, his blocks will most likely cause all the blocks from the other miners to get orphaned. If he was "unlucky" and did not generate more work than the rest of the network then HIS blocks will get orphaned that's why he complains that sometimes he has many orphans in a row too.
Simba84, please make sure that ALL your nodes are always connected to the rest of the network, and that your pool is not mining with one or two nodes that are connected between them but isolated to the rest of the network. This should avoid all the orphans seen in the network.
If your nodes are being attacked maybe you can whitelist a couple of good nodes and only let your node connect to those. If it's a problem with the nodes being DDoS'ed then I could generate a new version based on 0.13.1, that's supposed to be more robust.

We have more than 30 nodes, I don't think that just adding more nodes would fix the problems.

I ask all miners to please spread the hashes, change pools or go solo, but don't let any pool (riepool or xpoolx or anyone) have more than 50% of the mining power.

It's unfortunate that we are being attacked by DDoS, but we have to deal with the fact that a CPU coin attracts botnets and botnets are many times used for DDoS attacks. Sometimes I wish we had a GPU miner and the attacks would go away.

Thank you all and best regards,
Gatra

Just spotted this - I'd been trying to figure out why my office was being DDoS'd, and taking down parts of the CMU network along with it. I'd kept a riecoin node going for the last two years despite not really being in crypto any more, but I can't let this prevent everyone in my building from working.

The DoS wasn't a matter of a new version - in my case, they were sending 5Gbps of NTP reflector traffic at my IP address. Carnegie Mellon was not amused. It was a pretty serious attack.

Sorry to hear about the problems. Hope they get resolved!