i will never ever use minersbest, for any coins in any near future.
wake up this morning to this private message.
hi,
mrc.nut2pools.com have found over 1 hour no blocks, good time to change the pool back to mrc.minersbest.com
minersbest ;-)
WTF, thats low!
minersbest please delete my account, never used it anyways since your pool was shit at launch
I sorry, for you both. Minersbest shouldnt do that sort of guerillia marketing, but i will speak to him today, so this is almost likely not to happen again.
Your pool has not been online at the lauch of this coin but some hours later, so please dont talk about as if you made it better.
How much downtime had your nut-pool during lottocoin release (not saying that thas was your fault).?
Lets work together and promote this coin, no reason to start a "pool war", lets pump it big so we need even more pools for this :-)
Oh dear, this is a sad state of affairs.
Firstly - full disclosure.... Svennand is not part of the Nut2Pools team. He was initially an investor/promoter in the early days when I first started out and we are are both members of the core feathercoin dev team. Now though, he spends his time with his family (as I should). He is a very good personal friend of mine but
HIS OPINIONS ARE HIS OWN AND DO NOT NECESSARILY REFLECT THE VIEWS OF NUT2POOLS.
All that said and done... Minersbest - that was naughty. ALL experienced pool ops know that cron jobs (the scheduled jobs that process blockfinds, payouts, etc) stop from time to time and will only restart after manual intervention. This is to ensure that if any issues are detected with the system, the pools wallets and databases are not destroyed. A fail-safe if you will. They also know that this
DOESN'T AFFECT COINS EARNED as once restarted, they will simply plough through the backlog.
So, the long and short is we WERE finding blocks in that time, miners WERE earning and you guys knew it. Unfortunately you decided to PM my miners and spread FUD. Not very professional... Not very professional at all!
Note to miners: As explained above, the front end systems (web, payouts, etc.) do stall from time to time (usually when I'm sleeping
) but as long as your rigs are submitting shares and you see the "Block: 1a7ff7278d3e8b82... " updating in CGMiner, you are fine. Just carry on and the pool will catchup once i restart the jobs.
As for the 51%, that too is misleading. Technically if someone has more than 51% they could do bad things but it's really not that simple. People kick around the 51% with very little understanding of what it means and the complexities involved. Now sure, people should ensure they have fail-over pools setup in their configs in case we go down but the reality is, there's very little harm in us having over 50%.
Hope that clarifies the situation a little.
Regards
Nut