Had some stuff to attend to today, sorry for the delay in responses! Down the list we go!
Wafflepool is not perfect though, and the only thing that bothers me is over/under valuing the profitability of coins like dogecoin, which have variable rewards by design. If the reward for solving a block is truly unknown until after it is solved, then it is improper to assume any block reward value based upon past results. This is basic statistics and simple game theory otherwise known as expected value. For dogecoin, the proper assumed value should likely be statically set to 500,000 when deciding which coin to mine. As I type this message, the expected reward value is currently set to 736,000, which will disappoint almost two times more often than not, and meanwhile we might have passed up mining a more profitable coin with a stable reward value as a result of a bad input into the profitability algorithm.
This is the way most pools do it, and you're absolutely right that statistical averages work out to 500k/block (using doge for the rest of this example). However, the block reward for the block you're _actively_ mining for is known when you're mining it. It is based on the last known block hash.
For example (and its a really ELI5 style example - the actual code is much more complex). But say the next block reward is worth whatever the last digit of the previous block hash was (assume 0-15 for last digit values). Statistically you'd earn 8 coins for the next block, however, if we know for a fact that the last block hash ended in "F" (15), we know that the next block reward is definitively going to be worth 15 coins. Which makes for a _much_ different profitability calculation for if the next block is worth mining. Since the function for generating block rewards is known (in the client), and all the inputs are known (previous block hash, etc), we can use the _actual_ block reward, rather than the statistical average in our calculations. Long term, this should give us better performance in earnings.
Let me know if I can explain it any better
Also, it would be nice to see hash rate per worker broken out in the stats, as well as an historical hash rate chart, but this request is merely display fluff as compared to my other concern. Oh, and the best pools always disclose their current PPLNS target. Thank you for all your hard work!
Yep, per-worker stats/graphs are on the list. Working on the new endpoints first though