Yea, apologies for not making an announcement here as well, but @gpedro is correct, I was forced to take the pool down while we work on securing everything. We must again make sure that only the people that we trust have access to the wallets, and information on the pool servers.
There will be a notice when things come back, and we're working to resolve the issues both here and on ninja as quickly as possible, apologies for any inconvenience, but this is very important.
As you know, we never take things down like this without a damn good reason, ninja pool has not had a situation like this in the nearly 3 year time it has been running.
The "v2" of Ninja code is hard to get a hold of basically 3 people have copies of the code that runs the pools.
Haitch = You only get access to the fees wallet Haitch controls everything else
Crow = Hard to get a copy if at all
Focus = hard to get a copy if at all anymore
Huh? If you want to run a Ninja pool, I'll set it up for you - you have access to all 3 accounts. You'll require an ESXi host to run it on though.
Well ESXi is option really its just a vm export it as OVA and your good to go with any hypervisor
@Casse As long as you're careful with calculating your starting nonces, then no - no issue. The AIO bases it's starting nonce off the drive letter and existing nonces - if it sees the same empty C: plots directory, it's going to write the same plot file each time.
@TheTiny I suspect that you're trying to plot beyond the end of the drive. Try reducing the number of nonces by your stagger rounded up to a power of 2 - in your case 32,768 or 65,536 to be extra cautious.
@Energy There's a DDoS going on. I can deal with most but not all of it currently it. I'm looking to be able to handle more, but for now I handle as much as I can - but as I said, the pools are still mining.