firetreeactual
Legendary
Offline
Activity: 952
Merit: 1003
|
|
February 23, 2016, 02:16:13 AM |
|
OK...I've never had a transaction from kano.is get hung up. It happened with Slush twice, but never here. I'm only in favor of sending payments once a day if it (1) saves Kano money up front, (2) is easier for him to handle, and (3) quiets the masses.
|
To infinity and beyond...on two 741s and one of only 3...nope, make that 4...full nodes in Hawaii...on <30A. (I have other gear on the Hoth ice planet)
|
|
|
hurricandave
Legendary
Offline
Activity: 966
Merit: 1003
|
|
February 23, 2016, 02:36:46 AM |
|
The tricky part of removing the pay-per-block is it makes a Hot wallet/Cold storage become a necessity. Hot Wallets have their own vulnerability to thieves and cold storage adds more work and book keeping and accounting files. Just ask Eleuthria, its do'able but takes time to get it right.
|
|
|
|
hoosier_13
Member
Offline
Activity: 62
Merit: 10
|
|
February 23, 2016, 02:47:24 AM |
|
I would prefer the current method, it ain't broke, don't fix it
|
Bitrated user: TICH13.
|
|
|
sjc1490
|
|
February 23, 2016, 02:59:24 AM |
|
The tricky part of removing the pay-per-block is it makes a Hot wallet/Cold storage become a necessity. Hot Wallets have their own vulnerability to thieves and cold storage adds more work and book keeping and accounting files. Just ask Eleuthria, its do'able but takes time to get it right.
+1 I agree, I know folks mean well but I don't think they understand the xtra work they would be creating for Kano who already spends a ton of time and $$ to run this pool.
|
BTC ADDRESS: 12Qwd8VKLQ4xF44ytHXBpCAKuF9VknG4X2
|
|
|
thedreamer
Legendary
Offline
Activity: 1694
Merit: 1002
Go Big or Go Home.....
|
|
February 23, 2016, 03:04:07 AM |
|
Whatever makes the pool owner who already puts in quite a lot of his time to inform us of everything and runs a pool that makes $$$ for all of us the least amount of work, is fine by me.
|
Go Big or Go Home.
|
|
|
clgrissom3
Legendary
Offline
Activity: 1722
Merit: 1032
Carl, aka Sonny :)
|
|
February 23, 2016, 03:25:13 AM |
|
Whatever makes the pool owner who already puts in quite a lot of his time to inform us of everything and runs a pool that makes $$$ for all of us the least amount of work, is fine by me.
I agree. Kano's method works fine and I don't mind if he keeps it that way. I don't mind if he did zero fees and just waited until our own blocks confirmed the transactions even if it took longer to go through. It is the slow and steady way that works for mining. 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.
|
|
|
|
philipma1957
Legendary
Offline
Activity: 4284
Merit: 8755
'The right to privacy matters'
|
|
February 23, 2016, 03:52:27 AM |
|
The tricky part of removing the pay-per-block is it makes a Hot wallet/Cold storage become a necessity. Hot Wallets have their own vulnerability to thieves and cold storage adds more work and book keeping and accounting files. Just ask Eleuthria, its do'able but takes time to get it right.
At times there are 6 blocks in the wallet.
|
|
|
|
hurricandave
Legendary
Offline
Activity: 966
Merit: 1003
|
|
February 23, 2016, 04:18:48 AM |
|
The tricky part of removing the pay-per-block is it makes a Hot wallet/Cold storage become a necessity. Hot Wallets have their own vulnerability to thieves and cold storage adds more work and book keeping and accounting files. Just ask Eleuthria, its do'able but takes time to get it right.
At times there are 6 blocks in the wallet. Yes 1 block, 6 blocks, 12 blocks. How ever many. That's a far cry from the complexity of 5000 Users, each using the pool as a sort of wallet/bank. The real time holding will grow with every block we solve. A dozen blocks waiting for 100 confirms before distribution will become a small slice of a pools wallet system.
|
|
|
|
Legacy2005
|
|
February 23, 2016, 04:22:24 AM |
|
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).
|
|
|
|
philipma1957
Legendary
Offline
Activity: 4284
Merit: 8755
'The right to privacy matters'
|
|
February 23, 2016, 04:55:07 AM |
|
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
|
|
|
|
wikkidtt
|
|
February 23, 2016, 05:51:26 AM |
|
Added another 10th. Keeping my garage nice and warm
|
|
|
|
fubly
|
|
February 23, 2016, 06:47:06 AM |
|
de.kano.is:3333 at 6:45 utc DEAD and all other too?
|
each time you send a transaction don't forget to use a new address, each time you receive one also!
|
|
|
kano (OP)
Legendary
Offline
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
|
|
February 23, 2016, 07: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 UTC All's ok again (2 minutes later)
|
|
|
|
fubly
|
|
February 23, 2016, 07: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 UTC All's ok again (2 minutes later) Do you never sleep ?
|
each time you send a transaction don't forget to use a new address, each time you receive one also!
|
|
|
VirosaGITS
Legendary
Offline
Activity: 1302
Merit: 1068
|
|
February 23, 2016, 07: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 UTC All's ok again (2 minutes later) Do you never sleep ? He has military sirens to wake him up at the first signs of troubles.
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
|
|
February 23, 2016, 07: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)
|
|
|
|
citronick
Legendary
Offline
Activity: 1834
Merit: 1080
---- winter*juvia -----
|
|
February 23, 2016, 08:40:36 AM Last edit: February 23, 2016, 08:56:20 AM by citronick |
|
I think there another failover seconds ago - sg node is down, but failover triggered. Seems all back to normal now.
|
If I provided you good and useful info or just a smile to your day, consider sending me merit points to further validate this Bitcointalk account ~ useful for future account recovery...
|
|
|
omega015
|
|
February 23, 2016, 09: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) 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).
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
|
|
February 23, 2016, 09: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. 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.
|
|
|
|
kano (OP)
Legendary
Offline
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
|
|
February 23, 2016, 09: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. 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)
|
|
|
|
|