I'd love to see some kind of anti pool hopping. I admit that I (manually) hopped a bit for a while, but now with bithopper and stuff being widely adapted there's no way for a non hopper or even a casual manual hopper (like I was) to come out even.

I'd suggest going with the tried and true delayed block announcements that deepbit and now btcguild also use - people already know this method and it's easy enough for the non mathematical mind to understand, so they'd probably trust it more than other solutions such as pay per last N shares.

With your pool size you'd probably need more than one hour for it to be reasonably effective, maybe four hours or so.

Otherwise, keep up the good work! From here in northern Germany, MtRed's server is among the very fastest as far as time between establishing the HTTP connection and receiving the getwork or getting confirmation of the share submission is concerned, only some small German pools such as the new (and I fear non-viable) BTCpool24 are faster. I like that as it keeps miners running more smoothly. Also your stale rates are pretty low.