Would it be super quick and easy to add pool N hashrate and user N hashrate to the api in addition to the 5m and 1h that are already there?
ETA: even if it's just a snapshot as of the time of the last pool block, doesn't need to be real-time during shifts
It would have to be a snapshot as at the last block since calculating that at any time is slow.
I'll add it to the TODO list - since yeah I'm rather busy at the moment
--
FYI (for anyone) I am actually still running in parallel the backup server, switched to the old code, while running the new code on the live server.
This way each time I process payouts I can compare the payout data and make sure it is EXACTLY the same on both.
If the payouts are the same, then all the share, shift and reward processing required to generate the payouts must also be the same, or good enough to produce exactly the same payouts, which is all that matters
This has been the case will all the new blocks since my DB code update.