KanoPool since 2014 🐈 - PPLNS and Solo 0.5% fee - Worldwide - 2436 blocks

[kano]

and confirmed

[1715372836]

1715372836

[1715372836]

1715372836

[1715372836]

1715372836

[1715372836]

1715372836

[1715372836]

1715372836

[philipma1957]

thanks for update

[-ck]

[kano]

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.
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.

[Cheeseater]

What happened to Proud Clown he had a ten step plan to becoming a bitcoin billionaire. Sad to see him leave so soon

[hurricandave]

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.

[MrGreenHat]

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..

[kano]

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.

[mrquick]

I bet you don't get this level of honesty at any other pool. 

[TeQ99]

is the payments tab working on the website or work in progress?

[-ck]

is the payments tab working on the website or work in progress?

Planned, still not begun.

[Cheeseater]

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.

[MrGreenHat]

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.

thumbs up! That is very comforting to know, and I wonder if other larger pools that I won't mention by name practice this as part of their protocol...I really appreciate all the effort and time that you and ck have put into developing this wonderful pool. I know your time is valuable. I just want you guys to know it doesn't go unappreciated.  

[norgan]

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.

thumbs up! That is very comforting to know, and I wonder if other larger pools that I won't mention by name practice this as part of their protocol...I really appreciate all the effort and time that you and ck have put into developing this wonderful pool. I know your time is valuable. I just want you guys to know it doesn't go unappreciated.  

yeah ditto, I've always found that transparency is the key to helping your customers understand. It's usually when you try to lie and keep them in the dark that they start to become impatient and unreasonable.

[kano]

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.
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.

[bitwitt]

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.
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!!!   

[kano]

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

[purpl3haze]

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

  got my first dollar ever mining from your pool hah

[Cheeseater]

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

Yeah, first payout in 4 days give or take. While I'm glad it gave you a break from doing multiple payouts everyday, hears to hoping you get back to doing multiple payouts everyday

[MrGreenHat]

Hi,

I left shortly after I noticed my shares said zero in the shares.  Mind you, I had been mining for days before the shares changed from several million to zero in "miner status."  It was a reset of the pool after I read the pool forum a bit ago.

Shortly before leaving [after mining 3 days] I look to make note my expected payout would be .17etc BTC.

I come back about 15 minutes before the block was found to find it down to .10etc...

I found that 3 of my 17 miners went from 60 something thousand shares to 2, 3 and 7 [respectively].  I decided not to say anything about it.  However, I still had expected payout of at least 0.10etc... BTC.

Well, it appears we've had a payout.  Yet, I have not received an email to tell me I've been paid for the DAYS I've mined for this block.  Someone please explain:

This is a PPLNS pool, and the N is the current difficulty. What probably happened is that you stopped mining and more shares were submitted than the current difficulty to solve the most recent block, meaning you would not get paid for the block.