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!
Thanks for the info and I'm sorry you had problems at work.
Same here, this was a bandwidth exhaustion attack targeting Riecoin nodes.
@gatra
Heres a suggestion to make Riecoin botnet resistant while keeping the classic proof-of-work.
Add double SHA-256 (SHA256d) as an additional constraint to the proof-of-work.
SHA256ds difficulty should be 150s seconds of computation time for an i7 4790k, approximately 4.2 billion hashes.
1). SHA256d(target || nonce) -> offload to GPU
2). Add digest to target
3). Solve proof-of-work puzzle.
4). Submit(256-bit offset, 64-bit nonce).
The idea is simply to add 150 seconds of preprocessing time on a CPU, but only 3-5 seconds on a single GPU.