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

[clgrissom3]

I really like this pool. But I'm concerned about my profit. At 20th what would be a estimated payout per block? Some how I keep getting different calculations. And currently I have half my gear pointed else where so I can cover my daily electric cost which is only about $4 as a lot of my miners are on free power

I'm running ~20THs and here is what I've gotten over the past 13 blocks...as I reached my 5Nd, it was 0.148 but that is also when the pool hash rate started exploding.  With the current pool size, 20THs should be ~0.11 on each block for you.

Thanks that's what I was looking for

I've had to shift my thinking to a bigger picture...like looking at the month as a whole instead of daily payouts.  For the first half December, we've hit 19 blocks.  If we hit 28 for the month, I will have exceeded my goal which blows away the earnings I was getting at the big box pools...and that is only 9 more blocks for the second half of the month.  So the current block is taking too long...meh...we will have several more days where we'll hit 2 or even 3 blocks.

[ZACHM]

Here is a little bigger picture, my December payouts so far, this shows daily total, daily BTC/TH, and 3, 7 and 14 day average BTC/TH:



Overall average for the month =  2.23858315 BTC / 15.84 THs / 16 days = 0.008832793 BTC/THs/Day

[vh]

the elusive block is here.   woot.

[727miner]

Phew! Now lets get a few bright green ones 

[bctmke]

Just noticed the email!   woooo

[kano]

... and confirmed
Looks like the stale block made a mess of the stats.
I'll have to fix that up with a ckdb restart a little later.

Also, there's another ckpool change in the works that I'll do a ckpool restart in an hour.
This one is to fix another few hundred milliseconds that can on rare occasions delay the block change.
Gotta make sure we have one of the fastest block change times around and -ck is making sure of that

[thesmokingman]

... and confirmed
Looks like the stale block made a mess of the stats.
I'll have to fix that up with a ckdb restart a little later.

Also, there's another ckpool change in the works that I'll do a ckpool restart in an hour.
This one is to fix another few hundred milliseconds that can on rare occasions delay the block change.
Gotta make sure we have one of the fastest block change times around and -ck is making sure of that

Thank you to you both. I, no we, appreciate all you do in support of this pool.

[kano]

... and confirmed
Looks like the stale block made a mess of the stats.
I'll have to fix that up with a ckdb restart a little later.

Also, there's another ckpool change in the works that I'll do a ckpool restart in an hour.
This one is to fix another few hundred milliseconds that can on rare occasions delay the block change.
Gotta make sure we have one of the fastest block change times around and -ck is making sure of that

Thank you to you both. I, no we, appreciate all you do in support of this pool.

Oh heh, even I jumped the gun on that one
My ckdb code fixed it - always gotta wait for that '~' to go away - that's when it's recalculated everything.
Well the block did wake me up ... I'll claim that grogginess as my excuse for jumping the gun on that one

Also note as per explanations and comments a while back that some probably haven't seen before, the actual block line stats show the stats just for each 'item' so for a block that includes a stale, invalid, orphan etc you'd have to add up the two rows to see that block's total shares.

There's an item in my todo to add a checkbox at the top that will say something like:
"Hide the bad information like other pools do" (checkbox)
That will only show the valid blocks with the multiple invalid lines summarised into the one block line.

Edit: but of course the ckpool restart will be going ahead as planned.

[elduderino]

Phew! Now lets get a few bright green ones 

Agreed! Let's light it up like a Christmas tree!

[dmwardjr]

Hi Zach,

Thanks for the work you've done with the pool hash rate graph and our own hash rate graph.  

Also thanks for the low hash notification and found block notification.

By the way, everyone, if you haven't tried out http://ckpoolmonitor.zachmonroe.com you need to.  No information you give can harm you.  Your email, API [Can generate a new one anytime] and pool username.  That's it.

[kano]

Hi Zach,

Thanks for the work you've done with the pool hash rate graph and our own hash rate graph.  

Also thanks for the low hash notification and found block notification.

By the way, everyone, if you haven't tried out http://ckpoolmonitor.zachmonroe.com you need to.  No information you give can harm you.  Your email, API [Can generate a new one anytime] and pool username.  That's it.

Yeah that's actually the point of being able to create a new API code for your account.

The old API code is no longer valid if you create a new one, so if you decide to give it out to someone, you can effectively revoke it.

Well, there is one time limit, you have to wait a day after you create it to create a new one, i.e. effectively revoke it.
So if you create a new, then wait a day before giving it to anyone, you can immediately revoke it if there's some issue.

However, it only gives read access to the API data for you and no other access to your account, so it's pretty safe.

[dmwardjr]

Yeah that's actually the point of being able to create a new API code for your account.

The old API code is no longer valid if you create a new one, so if you decide to give it out to someone, you can effectively revoke it.

Well, there is one time limit, you have to wait a day after you create it to create a new one, i.e. effectively revoke it.
So if you create a new, then wait a day before giving it to anyone, you can immediately revoke it if there's some issue.

However, it only gives read access to the API data for you and no other access to your account, so it's pretty safe.

Thanks for the info.  Much appreciated.

[sorry2xs]

this shift did not receive a pay that can be seines that something that will correct it self when you do the restart
edit:5ptq3 charlotte

[PPOC]

Phew! Now lets get a few bright green ones 

t

So we get a valid block and almost 1ph leave the pool? Why would one pool hop here with a 5N? Hopping works well at slush, but why here. Don't get it.

Stay after a block and keep hash high to get the next block faster.

[kano]

Phew! Now lets get a few bright green ones  

t

So we get a valid block and almost 1ph leave the pool? Why would one pool hop here with a 5N? Hopping works well at slush, but why here. Don't get it.

Stay after a block and keep hash high to get the next block faster.

It's nothing new actually.
That's the strange thing about it.
Often in the past I've seen the hash rate drop after we find a block.
I've no idea why miners leave then.

[kano]

this shift did not receive a pay that can be seines that something that will correct it self when you do the restart
edit:5ptq3 charlotte

Yeah that relates to my comment a few days back about how those numbers are calculated only for display, they aren't part of the process to determine your payout.

However I put a change in the other day to allow me to correct the display (if it happens) when ckdb is running.
... but after just trying it now, it didn't fix it on the live data so I'll have to sort that out.
Yeah the next time I do a ckdb restart will correct the display.

However, as I mentioned before, I will be doing a 'ckpool' restart shortly.
That will happen in 5 minutes.

[thedreamer]

Phew! Now lets get a few bright green ones  

t

So we get a valid block and almost 1ph leave the pool? Why would one pool hop here with a 5N? Hopping works well at slush, but why here. Don't get it.

Stay after a block and keep hash high to get the next block faster.

It's nothing new actually.
That's the strange thing about it.
Often in the past I've seen the hash rate drop after we find a block.
I've no idea why miners leave then.

Maybe they are hoping that the next block will be solved quickly and they'll get double pay from that block and the next pool's block they are mining at already.

Or.. Just a rental of hash that ended / is suspended until they get payment from the previous blocks.

[kano]

...
However, as I mentioned before, I will be doing a 'ckpool' restart shortly.
That will happen in 5 minutes.

Done.

[sorry2xs]

kano is the proxy restricted to only Asic Tubes

[helipotte]

Phew! Now lets get a few bright green ones  

t

So we get a valid block and almost 1ph leave the pool? Why would one pool hop here with a 5N? Hopping works well at slush, but why here. Don't get it.

Stay after a block and keep hash high to get the next block faster.

It's nothing new actually.
That's the strange thing about it.
Often in the past I've seen the hash rate drop after we find a block.
I've no idea why miners leave then.

My hashrate shows lower right now even though all of my miners indicate normal rates.  Slowly creeping back up to normal poolside though.

Edit:  looks like my miners switched to my backup pool.  Maybe that is why 1PH left after the block change, their miners switched to backup pools.