Regarding payouts, here's my quick thoughts on it:
Pros of daily payouts:
1 - Less time spent entering payouts into my mining spreadsheet
2 - Smaller transactions out of my wallet when I spend the coins (since my mining is rapidly becoming a smaller and smaller % of the pool I'm looking at hundreds of smaller inputs versus a few dozen larger ones)
3 - Less transaction fee overhead for the pool
Pros of the current per block payout:
1 - Pool holds coins longer and thus more risk
2 - Easy to match blocks to payments in my records (though that really isn't entirely necessary-- I just like knowing I have that data)
Overall, I lean toward the daily payout preference.
Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 1693. (Read 5352367 times)
February 23, 2016, 11:04:16 AM
February 23, 2016, 10:39:16 AM
No issues if things are send with some extra $$ behind it. I always use 8 confirmations at the slowest 10 and haven't had a 'lost' transaction yet.
For testing I sent one with 20 confirmations and it took about 14 hours to finally confirm.
For testing I sent one with 20 confirmations and it took about 14 hours to finally confirm.
yeah but even extra cash for the fees still does not help all of the time.
look at this
this is a hefty fee, and I now need to wait to finish business as those coins are not clearing.
This is not just a kano.is issue.
February 23, 2016, 10:21:25 AM
im fine with however you end up doing the payouts. You know whats best for you and the pool and trust your judgement/decision. You will never make 100% of the people happy with how its done so do what you feel is best.
February 23, 2016, 09:32:34 AM
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.
February 23, 2016, 08:04:07 AM
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)
Seems perfectly fine
February 23, 2016, 07:36:13 AM
Well done Rdawg with your second block
EDIT: and a nice sweet one from manel with his first block
EDIT: and a nice sweet one from manel with his first block
When the small guys find blocks, it's a prelude to a party....
February 23, 2016, 06:56:12 AM
Well Ain't that special
February 23, 2016, 05:42:54 AM
Well done Rdawg with your second block
EDIT: and a nice sweet one from manel with his first block
EDIT: and a nice sweet one from manel with his first block
February 23, 2016, 04:32:10 AM
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)
Daily or bi-daily sound good. Daily works. Sometimes getting paid more often can be nice, but 5 payout is a bit much and if the pool continue to grow in % of total hashrate, it will just get ridiculous.
Then again, if you internally do all the work and only release bundled payments, you'll still get more and more work to do.
February 23, 2016, 04:29:29 AM
...
That sounds like the natural next step for us. As you say your already doing all the checks and balances and just combining each into 1 payment (unless I misunderstood). I assume the rewards page will remain showing each individual block earning, but how about the payments page? will that still be broken down by block or will that change to show the combined payment? or is that part of the to do list?
...
Yeah there's no change to the rewards page since that is always block based.That sounds like the natural next step for us. As you say your already doing all the checks and balances and just combining each into 1 payment (unless I misunderstood). I assume the rewards page will remain showing each individual block earning, but how about the payments page? will that still be broken down by block or will that change to show the combined payment? or is that part of the to do list?
...
The Payments page is actually currently not how it will finally look.
I currently just generate a payout record for each reward record.
Eventually it will all be wiped and I'll get the code to read the real blockchain transactions and record the actual amounts from the transactions there, so your balance would simply be all the rewards minus all the transaction payments in the blockchain, recorded there, that went to you.
That's the 'dust' change that's in a galaxy far far away
(since it will show exactly the balance for everyone including the dust)
February 23, 2016, 04:20:20 AM
I think there another failover seconds ago - sg node is down, but failover triggered.
Seems all back to normal now.
Yeah coincidentally there's been 2 problems.Seems all back to normal now.
The first one a couple of hours ago where the pool server lost connection with the whole planet (for about 2 minutes).
Then since then there's been about 4 similar network problems, not related to that, but in the asia/pacific area.
The 2nd problem has happened about 4 times and for me it's been a complete lock up waiting for data that then appears about 1 minute later.
An MTR showed it was somewhere between me and the USA and thus it's probably the same issue for the approx 20% of connections that have disconnected and reconnected during these 4? times.
February 23, 2016, 04:19:01 AM
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)
That sounds like the natural next step for us. As you say your already doing all the checks and balances and just combining each into 1 payment (unless I misunderstood). I assume the rewards page will remain showing each individual block earning, but how about the payments page? will that still be broken down by block or will that change to show the combined payment? or is that part of the to do list?
Following on from the conversation on TX fee's at the moment with 0.0002/0.0003 those fees are still way below any bank/financial institute so upping the fee slightly shouldn't be too bad at the moment. It's only a bad thing if/when Bitcoin becomes a lot more mainstream and the "value" of BTC increases which means the fee should decrease by a decimal or two. Possibly the fee could be a calculation depending on transactions per day & blocks per day. This way fee's are proportional and should have no trouble being included in blocks, that said this means pools need to stop mining empty blocks and include transactions as this doesn't help the network. Let's also not mention certain pool's not including kano.is transactions in their blocks...... (and stupidly some don't even include their own transactions).
February 23, 2016, 03:40:36 AM
I think there another failover seconds ago - sg node is down, but failover triggered.
Seems all back to normal now.
Seems all back to normal now.
February 23, 2016, 02:49:35 AM
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)
February 23, 2016, 02:22:30 AM
de.kano.is:3333 at 6:45 utc DEAD and all other too?
Yeah the whole pool lost network connection for a bit over 1 minute at 2016-02-23 08:41 UTCAll's ok again (2 minutes later)
Do you never sleep ?
He has military sirens to wake him up at the first signs of troubles.
February 23, 2016, 02:14:02 AM
de.kano.is:3333 at 6:45 utc DEAD and all other too?
Yeah the whole pool lost network connection for a bit over 1 minute at 2016-02-23 08:41 UTCAll's ok again (2 minutes later)
Do you never sleep ?
February 23, 2016, 02:03:49 AM
de.kano.is:3333 at 6:45 utc DEAD and all other too?
Yeah the whole pool lost network connection for a bit over 1 minute at 2016-02-23 08:41 UTCAll's ok again (2 minutes later)
February 23, 2016, 01:47:06 AM
de.kano.is:3333 at 6:45 utc DEAD and all other too?
February 23, 2016, 12:51:26 AM
Added another 10th. Keeping my garage nice and warm
February 22, 2016, 11:55:07 PM
I'm just worried about the future of Bitcoin as a currency. It seems to be getting harder and harder to do everyday business with it.
im thinking the same thing as you if we end up haven't to not only pay for the item + the sales tax and then a transaction fee on top of it an item that started out only costing $15 usd will end up costing $25+ usd worth of btc just to insta pay/leave with the item like we now do with cc or cash. would hate to see this wonderful experiment go up in smoke because daily business (ie buying groceries or lunch with btc wasn't planned for properly).
It is a simple easy fix every 1/2 ing has 2x transaction size .
Since we had a 1/2 ing we can 2x the transaction size on July 1 to two million .
Then next July 1 2x the transaction size to four million.
Finally when the 1/2 ing goes from 12.5 to 6.25 2x the transactions to eight million
Jump to: