What is this pool's policy on hopping?
Hoppers are not welcome here.
This policy is not yet added to the pool rules because my hopping-detection routine is not ready. When I'll be able to detect poolhoppers with low enough number of false positives, this policy may become forced.
I know that some people call proportional method "flawed", but since there are lots of users that like this method, I have to protect them from evil ones.
What is a "low enough number of false positives" - meaning: How many % of legitimate users are you willing to screw over?!
It is NOT "evil" to start and stop mining whenever you please! It is "evil" however to have a payout system that is mathematically proven to be flawed(!) and taking counter measures that will always also impact users that don't even know of pool hopping at all.
Many of your users are completely new and unaware of any 50% attacks, that other pools are also existing (because many forum threads that were started some time ago only mention deepbit, as it was nearly the only pool around) or that there are alternatives to prop + PPS. Please reconsider delaying stats + forcing policies that won't be able to only hit pool hoppers (and which most likely will be circumventable) and switching to a proven secure payout system instead.
PPLNS for example still lets users earn more if the pool has a luck streak (no crazy 0.07 BTC shares most likely though...), is dead simple to explain and is actually more "proportional" than prop., as it takes the hash rate into account more.
fuck this rant! this is all bullshit. i want a simple payout system, which we have here. i don't want some exotic variations that will fuck me over if my miner goes down. nor am i interested in debating this.
the "solution/s" , as I read about them on different post, are too frikin complicated. thus never ready for prime time.
All in all, the simplest solution is the best one.
Simple solution:
- post the rules. now anyone still hopping on deepbit is violating TOS.
- identify hopping behavior (very easy to do) and suspend the account.
- when the person logs in, tell them that their account has been flagged as hopping.
- give them another opportunity to Agree to TOS that spell out: "not going to hop"
- if they violate again. suspend the account.
since this would be automated, let them open a million accounts. and get a million accounts banned. an automated system won't get tired. a hopper, will on the other hand.