Ah, then the difference is most likely due to luck and variance. Windpath's miner stats calculate your hashrate based on how many accepted shares — weighted by share difficulty — you currently have in the P2Pool sharechain relative to the entire pool. It is quite normal for Windpath's stats to differ from your actual miners' hashrate, since Windpath's stats are heavily influenced by your miners' luck and the pool's total hashrate. For example, if a large miner suddenly dumps a significant amount of hashrate on P2Pool and gobbles up a large amount of accepted shares within a short amount of time, expect to see everyone else's hashrate on Windpath's stats drop significantly while the stats readjust to compensate for the large miner's presence. Similarly, when the large miner leaves P2Pool, expect to see your hashrate on Windpath's stats remain at the low end while your miners catch up on the additional shares now available in the large miner's absence.

P2Pool's total hashrate — mainnet, at least — has been fluctuating a lot recently. So the differences you see in Windpath's stats should not be of much concern. What matters most, and what you should be monitoring closely, is your efficiency relative to the pool's.

I'd wager that your miners' P2Pool efficiency is a little bit on the low end. Have a look at this guide to see where else you might be able to eke out a little bit more efficiency from your miners and your P2Pool node.


No. The bug fix was in response to a support ticket that I opened with Canaan. It's still in beta, though, which is probably why there hasn't been any official word from Canaan regarding the fix. But then again, Canaan doesn't have an official thread or account on bitcointalk, as far as I know, nor do they usually announce the release of new software or firmware.

There is an unofficial Avalon A7 thread here.