This change has been implemented and is now live.

Just for reference. Below is a link to the code calculating miner balances from shares. All of our pools use the exact same piece of code. 

The outer loop goes over every single share submitted by all miners in reverse chronological order (newest to oldest). The window parameter is currently 1 for all pools. The share.Difficulty is the miner's difficulty setting when the share was submitted. The actual reward of the miner is calculated in Line 166 where blockReward is the exact same amount shown in the "Reward" column of the "Blocks" table on the website.

https://github.com/coinfoundry/miningcore/blob/master/src/MiningCore/Payments/PayoutSchemes/PayPerLastNShares.cs#L119

Sent you an invite.

Sent you a slack invite. :-)

@Ben: The most important part of your analysis is the final part where you go into the potential of handing out the same job to multiple miners. This would be deadly indeed but fortunately this is covered by the extranonce assigned to each miner. Slush described this in his Stratum Whitepaper. Coincidently, I'm working on improving the vardiff implementation right now. Will keep you posted.

Done.

You spent the better part of the last afternoon spamming this place with hate comments. Then you've announced that you would leave the site for good. Yet you are still here posting negative comments everywhere. Make up your mind please.

I've deleted this account for toxic behavior. Regarding your crusade towards the pool, by all means do it.

Would be possible if it was primarily meant as quicker way to communicate for the miners. I'm already struggling to keep up with this site, let alone be around in a chat channel all the time.

@te4336: Roughly 12h ago the load on the pools became so high that the server struggled to keep up. The vital parts did but some components were showing flaky behavior. This happened while I was asleep (had another 18 hour day here).