I'm not sure why DDoS would be effective either, except for the idea that if the pool gets knocked off right before the solution is found, then all the hashes for that block from the pool are wasted. Granted, I would think that would require someone to be paying attention to the block chain pretty fiercely but that doesn't really make much sense. The only other thing that makes a bit more sense is a campaign of a hacker who has an axe to grind with religion but really, if that were the case (not suggesting or condoning this) why wouldn't they hit some high profile target like Joel Osteen or The 700 Club. So really, the only thing that makes much sense is a rival coin, which is sad to think about, or someone that doesn't realize no pool all that hash goes solo (and for the short term, that's a zero sum game, maybe long range the lack of a pool drives out other miners, but that's a bit hard to fathom).
We need more pool servers, I've offered as well to buy and run one if the price wasn't outlandish but I think the Dev wants to get a more finished product out there before that sort of thing happens. The counter argument to that is if there were one or two or three other supporters (I won't name anyone at the risk of offending, but I'd wager there's five or six posters in this thread contributing half the posts), like myself, that were willing to buy or at least Co-Lo a pool server under the direction of the Dev with the understanding it would be remotely accessed and upgraded on the short term by him and after his pool software was "prime time", would then become the hosts duty, there would be enough takers.
I can tell you with relative certainty why we're getting ddossed. Anyone who tries to create a 'novel' algorithm and a new pool is a threat to the top 50 coins on coinmarketcap. I think its more of a jealous group or actor than someone trying to extract an edge out of the pool. We need more pool servers, I've offered as well to buy and run one if the price wasn't outlandish but I think the Dev wants to get a more finished product out there before that sort of thing happens. The counter argument to that is if there were one or two or three other supporters (I won't name anyone at the risk of offending, but I'd wager there's five or six posters in this thread contributing half the posts), like myself, that were willing to buy or at least Co-Lo a pool server under the direction of the Dev with the understanding it would be remotely accessed and upgraded on the short term by him and after his pool software was "prime time", would then become the hosts duty, there would be enough takers.
On forking the code and running multiple pools, I agree, it is probably better to give you an early version of the code and have more than one, and have you upgrade later, rather than wait until we have a finished pool. However, I dont view it as 'ready' to check in. It still needs a couple things related to SQL, so, if you can respect the fact that its not ready to check in yet, thats why its too early to fork it to two beta pools. In addition, the alpha version is 65% complete (keeps getting interrupted by these outages) and I may end up checking that in instead, depending on how its received. The alpha version is completely different than the beta version.
there are ready VPSs or dedicated servers with DDOS protection on the market.. did you consider using one or few of them ?
google cloud is available for free now and it has DDOs protection too
