Quote from: PCComf on November 18, 2015, 02:35:05 PM

It appeared he was using Microsoft's cloud for his server and mailgun.org for his email. Either of those places should have more info on him, including his payment info, that may help track him down. Just in case anyone is interested.

The longer this goes the more likely it was a scam. Its also possible he got hacked and doesn't own the private key with that coin on it, among other possibilities. The timing of the disappearance and the simultaneous disconnection of other services suggests scam. Considering how much effort he put into the scam it is likely he's obfuscated his information on those sites as well.

I'd just like to point out that the entire premise of this pool was faulty. There are fair and trusted pools that already "help decentralize the network" including kano.is. The problem isn't that there aren't pools, the problem is that there are nearsighted people who have no patience and would rather mine at a larger pool in order to decrease their variance. I'd love to see people flock to a pool like Kano.is so it was hitting blocks more regularly. That's really all that is necessary for many people to bring their hash back from the large PPS pools. A pool like Nexious was harming rather than helping in this regard.

Yeah, I had already looked into the details. He was running on Azure. Nexious.com in reality pointed to nexious.cloudapp.net, which is MS Azure. I tend to agree that the simultaneous disconnection of all services (pool, site, email) does not look good in any way at all. At first I was wondering if he had an issue on his server... maybe something screwed up when the block was found. However, since we had started on the next block without any problem, that theory doesn't hold much weight.

I don't agree with your assertion that a new pool is a problem. Let's face it, last year kano.is was a new pool. Yes, it's very well run and maintained by one of the two guys responsible for writing the code in virtually every BTC miner available. I have nothing but respect for the work kano and -ck have done and continue to do. However, people flocking to kano.is does exactly what you're stating is the problem: centralizing the hash on a single pool. Currently it's AntPool and f2pool. Take their hash and point it at kano and you've still only got a single pool. Of course, I trust kano's pool far more than either AntPool or f2pool, but that doesn't alter the fact that just pointing a ton of hash at a single pool is dangerous. Remember when ghash.io had more than 50% of the global hash rate?