Great to hear, thanks! Let me take a look at this 20% block thing in detail next.
EDIT: Btw, I just realized when you fixed your problem with the removal of the semicolon, the cookie actually contained your password, the one you typed in on the UI, that was not intentional thats a bug, that is supposed to be hashed first. So this will be fixed in the next pool release also so that the password is never stored anywhere.
Haha yes, I was already wondering why the cookie contained my password in "clear type", that did not seem very secure to me.
Still looking into this distinct solved count by the pool.... Honing in on the block template given to every miner at the same time with one pool address in it.