All good.
Now to fix the display issue so I don't have to ignore one of my checks that complains about it
Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 2226. (Read 5352527 times)
November 19, 2014, 08:11:37 PM
Payout 330642 sent.
All good.
Now to fix the display issue so I don't have to ignore one of my checks that complains about it
All good.
Now to fix the display issue so I don't have to ignore one of my checks that complains about it
November 19, 2014, 07:20:57 PM
OK, after yesterdays unexpected restart, I'll mention here before hand, so people know before hand.
About to do another restart of ckdb, for the payout fix, so the web will shows 0 stats for a while.
Hopefully this time no unexpected ckpool restart, but we'll see what happens.
I'll of course start it asap if that happens.
All back up.About to do another restart of ckdb, for the payout fix, so the web will shows 0 stats for a while.
Hopefully this time no unexpected ckpool restart, but we'll see what happens.
I'll of course start it asap if that happens.
The problem seems to be just a display problem and not affecting the correct payout.
My change didn't fix the display problem, but it made it clear that's what it probably is.
Will verify for certain then do the payout shortly.
Thanks for your dedication and hard work!!!
November 19, 2014, 07:11:12 PM
OK, after yesterdays unexpected restart, I'll mention here before hand, so people know before hand.
About to do another restart of ckdb, for the payout fix, so the web will shows 0 stats for a while.
Hopefully this time no unexpected ckpool restart, but we'll see what happens.
I'll of course start it asap if that happens.
All back up.About to do another restart of ckdb, for the payout fix, so the web will shows 0 stats for a while.
Hopefully this time no unexpected ckpool restart, but we'll see what happens.
I'll of course start it asap if that happens.
The problem seems to be just a display problem and not affecting the correct payout.
My change didn't fix the display problem, but it made it clear that's what it probably is.
Will verify for certain then do the payout shortly.
November 19, 2014, 05:15:02 PM
Once the pool gets bigger I will of course automate more of those checks, however, they don't take very long, and there will always be a final manual check of the information to help ensure it's correct - for security reasons also.
November 19, 2014, 04:55:24 PM
Once the pool gets bigger I will of course automate more of those checks, however, they don't take very long, and there will always be a final manual check of the information to help ensure it's correct - for security reasons also.
November 19, 2014, 04:54:53 PM
I bet you don't get this level of honesty at any other pool.
I've said it before and I'll say it again. I have never seen this type of transparency in any other pool, not to mention the level of support from the operators. It take's me a ton of motivation to bill my customers much less pay the bills. My thanks to you Kano and CK I can hardly imagine the amount of time running this pool consumes in relation to rewards. Which is why I plan on staying for the duration, because there's no way you're in it for coin.
November 19, 2014, 04:20:16 PM
is the payments tab working on the website or work in progress?
Planned, still not begun. November 19, 2014, 04:17:00 PM
is the payments tab working on the website or work in progress?
November 19, 2014, 03:30:31 PM
I bet you don't get this level of honesty at any other pool.
November 19, 2014, 03:17:46 PM
Hi all, that yesterday's update has caused an error in the calculation for the payout of the current block - no problem with previous payouts of course.
(see git if you are curious)
I've been working on that last night, but only realised just now as I was doing the payout that the change was incorrect for the new block.
Once it's fixed, I'll post up that I'm doing the payout.
Sorry for the delay, but it's part of the manual step of the payout that I check certain things and thus found this problem.
The aim of the final manual checks (and the last step, manual send) are to help avoid pool funds not getting to their correct destinations.
Once the pool gets bigger I will of course automate more of those checks, however, they don't take very long, and there will always be a final manual check of the information to help ensure it's correct - for security reasons also.
(see git if you are curious)
I've been working on that last night, but only realised just now as I was doing the payout that the change was incorrect for the new block.
Once it's fixed, I'll post up that I'm doing the payout.
Sorry for the delay, but it's part of the manual step of the payout that I check certain things and thus found this problem.
The aim of the final manual checks (and the last step, manual send) are to help avoid pool funds not getting to their correct destinations.
Once the pool gets bigger I will of course automate more of those checks, however, they don't take very long, and there will always be a final manual check of the information to help ensure it's correct - for security reasons also.
November 18, 2014, 10:05:58 PM
What happened to Proud Clown he had a ten step plan to becoming a bitcoin billionaire. Sad to see him leave so soon 
I was wondering the same thing... he was rather enthusiastic, and quite frankly his disappearance has me concerned for his well being.. 
November 18, 2014, 09:27:35 PM
What happened to Proud Clown he had a ten step plan to becoming a bitcoin billionaire. Sad to see him leave so soon
Patience must not be one of the steps. 
November 18, 2014, 09:26:24 PM
What happened to Proud Clown he had a ten step plan to becoming a bitcoin billionaire. Sad to see him leave so soon
November 18, 2014, 08:07:34 PM
Thank you Kano for pointing that out. i could see my miners still working but didnt look to see where they were mining.
This is a total newbie question but ... what factors go into making a long 78 +hr block? Is it just down to pool size?
The pool size determines the average expected time to a block.This is a total newbie question but ... what factors go into making a long 78 +hr block? Is it just down to pool size?
100% on the blocks page is an average expected block.
You can work it out if you are interested
First check the current network difficulty ND - the bitcoind getinfo command will tell you that
... hmm I guess it wouldn't hurt to add that on the web site somewhere later if I can find space since it already knows it.
That number on the top left "Shares: NNN (X%)" is using the network diff to display the X%
Using the pool hash rate HR in THs, the expected time to a block is:
ND / (HR * 10^12 / 2^32)
So for example at 1400TH/s and the current (new today) ND of 40300030327.89140320
40300030327.89140320 / (1400 * 10^12 / 2^32) ~= 123634s ~= 34hrs 20min
You can also get that on my pool hash rate page I made years ago
http://tradebtc.net/bitcalc.php
Guess I could add that onto the pool web site at some time.
November 18, 2014, 07:45:17 PM
November 18, 2014, 07:38:12 PM
thanks for update
November 18, 2014, 07:33:50 PM
and confirmed
November 18, 2014, 07:23:02 PM
i must be good luck for you as soon as i turned my first miner toward your pool a block was found... 
thanks...and welcome aboard
November 18, 2014, 07:21:45 PM
i must be good luck for you as soon as i turned my first miner toward your pool a block was found...
Finally got a block ... but waiting on the confirm ... 
November 18, 2014, 07:19:44 PM
i must be good luck for you as soon as i turned my first miner toward your pool a block was found...
Jump to: