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

[PPOC]

... and one of the top two miners who added multiple PHs hashes on to that evil 666.666% block just found us a block 25 minutes ago

So the top bar of the stats say 1,748 Th, but when I look at the pool stats page, just the top 5 miners make up over 2.5Ph. Which on is correct? Seems like one of those is off. I have actually seen this case several times where the pool stats on the top 5-10 miners are much higher then whats reported as current pool hash on the header bar at the top.

Different rolling time frame. They're all accurate in their own way. Kano can elaborate when he has time.

I see the different hash rates on the stats page, current, 5min, 1hr, 24hr. The list of miners says 5min hash rate, so I would think that list should match the 5min total at top, but it does not. Also, the teal color hash rate next to CKPool in the header, is that current, 5 min or 1 hr? That looks to match the 5min on the stats page, but again the miner list says 5 min and adding it up does not match any of the other totals.

Not a big deal, just curious

[1714772306]

1714772306

[1714772306]

1714772306

[1714772306]

1714772306

[1714772306]

1714772306

[1714772306]

1714772306

[xstr8guy]

Well obviously Kano fixed the pool code, right? 

Hopefully some/most/all of the hash that came to bust that block stays on this pool.

Aannd... It's gone.

[PPOC]

Well obviously Kano fixed the pool code, right? 

Hopefully some/most/all of the hash that came to bust that block stays on this pool.

Aannd... It's gone.

Any idea why these big fish leave? If they would stay it would be a 5ph or larger pool. We are still over 100% long term and top notch code and service. Just don't see where they can do better, I think anything over 100% luck is best you can do compared to the pools you have to choose from. Unless they usually solo mine, just don't get it.

Any insight anyone?

[LoneRangir]

Well obviously Kano fixed the pool code, right?  

Hopefully some/most/all of the hash that came to bust that block stays on this pool.

Aannd... It's gone.

Any idea why these big fish leave? If they would stay it would be a 5ph or larger pool. We are still over 100% long term and top notch code and service. Just don't see where they can do better, I think anything over 100% luck is best you can do compared to the pools you have to choose from. Unless they usually solo mine, just don't get it.

Any insight anyone?

My guess is that these are large solo miners.  They are big enough to go it alone.  One mentioned he was swinging some hashing power over to help us bust the '666' block (it's now legendary!). 

[kano]

Quick question; has anyone tried to change the default setting for 'temperature' in the updated s3 software? Mine appears to stay at default 'true'. Please let me know. Thx!

I'll check it later (haven't got time at the moment)
It's something I've never turned off since ... well ... if it ever hits 80C internally you really don't want it to keep mining ...

Yep it's in the code causing it - I've not sorted out where yet - but the config file, the init script and the web page work as expected.
When the option is not passed to enable it, it's enabled anyway.
I'll sort it out when I do the first S5 release since it's the same code for the first S5 release.

[xstr8guy]

Well obviously Kano fixed the pool code, right?  

Hopefully some/most/all of the hash that came to bust that block stays on this pool.

Aannd... It's gone.

Any idea why these big fish leave? If they would stay it would be a 5ph or larger pool. We are still over 100% long term and top notch code and service. Just don't see where they can do better, I think anything over 100% luck is best you can do compared to the pools you have to choose from. Unless they usually solo mine, just don't get it.

Any insight anyone?

 I imagine that Kano or ck called in a favor to some big fish or it was just some good Samaritans that felt the need to help the pool bust a block. Whatever the reason, thank you!

[kano]

... and one of the top two miners who added multiple PHs hashes on to that evil 666.666% block just found us a block 25 minutes ago

So the top bar of the stats say 1,748 Th, but when I look at the pool stats page, just the top 5 miners make up over 2.5Ph. Which on is correct? Seems like one of those is off. I have actually seen this case several times where the pool stats on the top 5-10 miners are much higher then whats reported as current pool hash on the header bar at the top.

The top left of every page is the 5 minute pool hash rate.
People like to see the pool hash rate change when they add miners, so ... it uses the 5 minute value .. less accurate / more variable.
I used to get it to display the 1hr value if the last pool restart was more than 1 hour ago, but changed it for the above reason.

The stats page shows each of the different pool rates first on the page, thus you can see that the top left on the page matches the 5 minute value.
The user stats are the sum of each individual user's worker's 5 minute values.
Since they are calculated independently and also are only 5 minute values, they don't add up most of the time and will be even more variable when hash rate changes quickly.

The most relevant point in all of this is that the amount you are rewarded is of course based on your shares.
Shares are very inaccurate to use to determine your hash rate since their variance is quite high due to mining difficulty.
But shares are what matter since they determine your reward, and that's what the Shifts and Rewards pages show.

[kano]

666.666 Payout 366781 sent
e69e0f814e2b466ba10a801bd04894f068e44a93a82c4a1c715fa77193216bee
and confirmed

[CapnBDL]

Quick question; has anyone tried to change the default setting for 'temperature' in the updated s3 software? Mine appears to stay at default 'true'. Please let me know. Thx!

I'll check it later (haven't got time at the moment)
It's something I've never turned off since ... well ... if it ever hits 80C internally you really don't want it to keep mining ...

Yep it's in the code causing it - I've not sorted out where yet - but the config file, the init script and the web page work as expected.
When the option is not passed to enable it, it's enabled anyway.
I'll sort it out when I do the first S5 release since it's the same code for the first S5 release.

Ok. Thx! Thought it was just me. Just playing around. I wouldn't run it that hot either.

[Mikestang]

just found us a block 25 minutes ago

Oh my god, a 59% block.  Surely the pool must be broken!

Any idea why these big fish leave? If they would stay it would be a 5ph or larger pool. We are still over 100% long term and top notch code and service. Just don't see where they can do better, I think anything over 100% luck is best you can do compared to the pools you have to choose from. Unless they usually solo mine, just don't get it.

Any insight anyone?

I wonder about this as well.  They would receive a majority of each block reward at this pool, so the payouts would be larger (but less frequent) than if they were at one of the big Chinese pools.  I would love to hear from them and know what their strategy is for where to point >1PH.  With that much gear running I'm sure they have to maintain a pretty decent amount of btc incoming.

[PPOC]

just found us a block 25 minutes ago

Oh my god, a 59% block.  Surely the pool must be broken!

Any idea why these big fish leave? If they would stay it would be a 5ph or larger pool. We are still over 100% long term and top notch code and service. Just don't see where they can do better, I think anything over 100% luck is best you can do compared to the pools you have to choose from. Unless they usually solo mine, just don't get it.

Any insight anyone?

I wonder about this as well.  They would receive a majority of each block reward at this pool, so the payouts would be larger (but less frequent) than if they were at one of the big Chinese pools.  I would love to hear from them and know what their strategy is for where to point >1PH.  With that much gear running I'm sure they have to maintain a pretty decent amount of btc incoming.

Maybe with that much hash, you can't take any variance and need x amount daily to pay the bills. But even with variance, you still need to be at 100% to cover your costs and the big pools are between 98-102 on avg. Over a 30 day period I think you would do good on a smaller pool and help get the hash out of China. I will never mine a China pool, I don't have much hash but if all the under 100th guys mine smaller pools then we can make a dent to decentralize.

[VirosaGITS]

just found us a block 25 minutes ago

Oh my god, a 59% block.  Surely the pool must be broken!

Any idea why these big fish leave? If they would stay it would be a 5ph or larger pool. We are still over 100% long term and top notch code and service. Just don't see where they can do better, I think anything over 100% luck is best you can do compared to the pools you have to choose from. Unless they usually solo mine, just don't get it.

Any insight anyone?

I wonder about this as well.  They would receive a majority of each block reward at this pool, so the payouts would be larger (but less frequent) than if they were at one of the big Chinese pools.  I would love to hear from them and know what their strategy is for where to point >1PH.  With that much gear running I'm sure they have to maintain a pretty decent amount of btc incoming.

Maybe with that much hash, you can't take any variance and need x amount daily to pay the bills. But even with variance, you still need to be at 100% to cover your costs and the big pools are between 98-102 on avg. Over a 30 day period I think you would do good on a smaller pool and help get the hash out of China. I will never mine a China pool, I don't have much hash but if all the under 100th guys mine smaller pools then we can make a dent to decentralize.

I am pretty sure they would be fine, if a good portion of them pointed their PHs to a single solid pool outside china. I also pretty much doubt they need 100%~ on a daily basis. Big business seldom roll on a day to day basis.

[kano]

Payout 366833 sent (80 minutes ago)
497086fb54fb8b36210730f9ad4e202054840520439ab94150b39252aad229fa
and confirmed

[LoneRangir]

Maybe I missed it, I apologize, but why are there two numbers under "Invalids"?

[CapnBDL]

Maybe I missed it, I apologize, but why are there two numbers under "Invalids"?

One is the worker, the bottom is the total. That is if I think we are looking at the same figures.

[os2sam]

Maybe I missed it, I apologize, but why are there two numbers under "Invalids"?

A search for the word invalids found this

Any reason why the invalid share count went up by 10x?

Hmmm ... good spot. My guess is a rejected block (I'll check and see if it was one of my rigs ...)

EDIT: Nope ... best share on of all my rigs is 828,477,642 and biggest cum rejected share 279,149

It's one user who sends "hi" shares after setting a very large diff on his worker.
He's been playing with his worker diff settings for a while ...
Maybe he's trying to game the diff by changing it ... it wont work ... but I'll ban his account if he keeps doing it.

... and I've updated the web site header 'Invalids:' to show share % and diff %
So it's easy for anyone to see that the invalids are being messed with
It resets every block change ... so ... hopefully ... soon

[wcg]

Hope someone finds this wadhole soon . If its causing problems with the pool .may he be banned soon.

[-ck]

Hope someone finds this wadhole soon . If its causing problems with the pool .may he be banned soon.

What are you talking about?

[kano]

Hope someone finds this wadhole soon . If its causing problems with the pool .may he be banned soon.

No it's not causing problems, just it means the Invalid stats where showing higher before than they really were.
Visual only, no effect on the pool.

Since I now show both stats, if they get very far apart it just means someone is messing with the invalid stats.

The first one is the % of invalid shares - so for that to get high someone would have to send a LOT of invalid shares.
The second one is the Diff % invalid - so that can get high on a very few invalid shares if you mess with your worker settings.

[wcg]

Ahh, ok got it .