Topic: Changing N on the fly for a PPLNS system (Read 818 times)
Thanks for the info.
Triplemining already does PPLNSH, only the shares of the last 24h count. So yes.
Has there been any pools that have varied N on the fly. For example, a pool might try to have N be equal to 2 days. N would then depend on the pools hashing rate.
I was thinking of something like the following,
- sort all shares by (age in shares) / (N for share), lowest first
This means that newer shares are processed before older ones. However, it a miner was operating on a higher N, then their share stays active for longer.
- pay each share 1 / (N for share) of the reward, starting from the first in the list until the entire reward is used up
This gives no risk for the pool operator. Each miners gets either a larger payout for shorter time or a smaller payout but stays active for longer.
On an aside, how do pools normally handle startup? That is kind of like switching from N = 0 to an actual N.
[ * ] Age would count in shares submitted
I was thinking of something like the following,
- sort all shares by (age in shares) / (N for share), lowest first
This means that newer shares are processed before older ones. However, it a miner was operating on a higher N, then their share stays active for longer.
- pay each share 1 / (N for share) of the reward, starting from the first in the list until the entire reward is used up
This gives no risk for the pool operator. Each miners gets either a larger payout for shorter time or a smaller payout but stays active for longer.
On an aside, how do pools normally handle startup? That is kind of like switching from N = 0 to an actual N.
[ * ] Age would count in shares submitted
Jump to: