Quote from: daninimmer on October 06, 2017, 07:17:53 AM

I am preparing a pool update (https://masari.superpools.net/) with:
* See the pending mature for account
* Different variable difficulty setting per port
* Maximum hasrate limit in the pool? This is not whether or not you like the community and that's why I ask. And what value would you put? 10kH / s, 50kH / s?

If you have any more ideas, please comment.

I will create a pool of tests, I will ask one of you to change the pool to test these changes (there will be multiple micro-cuts) in exchange for 0% fee and some compensation.

Soon more news, thank you all

Your pool increased the share difficulty even faster than masaripool. 2000H, 12000H, 72000H, then 200007H and remained there.
This is like a DOS attack on the connected miners because they can hardly submit any share before the next block starts and their work stales.
Six hours ago during the recent hashrate surge I guess the attacker got all shares for all blocks while all other miners running at 200007H produced only heat for their owners Grin

Your auto-diff must adjust the share difficulty in such a way that shares get submitted more or less every X seconds. For a 120s blocktime I'd recommend X to be around 12s.
When blocks get faster, it should get lowered. Other pools with other coins typically have one port for auto-diff and other ports for fixed diff.
Flypool allows you to set a fixed diff in the password field.

I think blocking users based on their hashrate is censorship and not acceptable at all. Some pools however block botnets.
When there are many workers mining with the same payment address but from many different IPs, it can only be a botnet or the dev fee for Claymore.
Claymore or any other dev will however contact the pools so their address gets whitelisted.