As for pool hopping exploits, I'll be working to find a way to quash those
I'm thinking the cheat proof method that was recently devised...... although I'd have to do some changes as it can cause operator BTC loss (and for a 0% fee pool, that's no so great).
I'm not sure if you're talking about the score based distro outlined in either of the threads I linked, or something else, but to be clear, please just use one of the score based methods. I showed bitcoinpool's attempt at shoehorning proportional distro into pool hop protection as an example of how not to do it
I'm reasonably sure that the potential operator loss can be covered by transaction fees from solved blocks, if any.
The commonly cited issue of miners disconnecting legitimately halfway through a round and getting no credit is a red herring. Over time, a legitimately disconnecting miner will disconnect at an even distribution of points throughout the round, and will not lose or gain anything from doing so.
The only disadvantage of score-based from a miner standpoint, besides the fact that people have tons of misconceptions about it, is that it increases variance slightly for smaller miners. This increase in variance will tend to even out in about 7 days (more or less depending on hashrate).
Glad to hear that you're planning on closing the hole. Doubly so because your pool is open source, so future pools will have a good working implementation of the system from the start
