Re: [25 PH] ** 5x AVALON6 GIVEAWAY ** Kano CKPool (kano.is) [0.9% PPLNS] US,DE,SG,JP
Meanwhile 
Regarding the pool wallet.
I've had a good think about how I do it and what changes I could make.
It's actually not all that difficult to do as I do already with one change, combine them once a day rather than send each one when it's due.
I like the process I have at the moment of checks and balances - that are beyond what many may expect - but I could simply continue that to get to the point where I'm happy with each individual result, but not send the result, then later run another process that picks a set of payouts from earlier in the process and combines them all, once a day.
That way I already know they've passed all inspections, and it's just dependent on me creating a new step that can add the earlier data correctly - so dust payouts are combined, and dust only not sent if the combination is below 10k satoshi.
Yeah I really don't want a pool bank for everyone, and I think this change would fit in well, and reduce the number of transactions and the payout division caused by our average expected more than one block a day.
Any comments?
(Edit: if anyone didn't notice, the last address in each payout is the total dust in each, which has always been more than zero except once)
Regarding the pool wallet.I've had a good think about how I do it and what changes I could make.
It's actually not all that difficult to do as I do already with one change, combine them once a day rather than send each one when it's due.
I like the process I have at the moment of checks and balances - that are beyond what many may expect
- but I could simply continue that to get to the point where I'm happy with each individual result, but not send the result, then later run another process that picks a set of payouts from earlier in the process and combines them all, once a day.That way I already know they've passed all inspections, and it's just dependent on me creating a new step that can add the earlier data correctly - so dust payouts are combined, and dust only not sent if the combination is below 10k satoshi.
Yeah I really don't want a pool bank for everyone, and I think this change would fit in well, and reduce the number of transactions and the payout division caused by our average expected more than one block a day.
Any comments?
(Edit: if anyone didn't notice, the last address in each payout is the total dust in each, which has always been more than zero except once)
misc comments:
1 - if (big if) anyone has been doing independent auditing, then that will be a bit harder to pair in/out via blocktrail BTC(n). i like the way it is now, but okay with either since more daily blocks (eventually) mean more payout to manage and more dust (many of us don't want to accept we're insignificant yet although we see it coming with diff changes).
2 - maybe a good time to also add confirmed payouts to user payment page if this happens?
3 - side note: iphone app's payout notifications will move to optional config soon but could temporarily glitch until i see the new transaction and make a slight adjust for value verification.
edit - random idea: if you do keep 1-to-1 as due, maybe you can consider using that last dust address as a get out of jail free card to payout a dust user if > some value.