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

[usukan]

I always get bored when the pool goes above 30-31

We get less blocks and the block payment plummets

sorry but that's my reality

More than happy to be awakened by a new reality that includes a proportionate amount of blocks with higher hash.

[1714857229]

1714857229

[1714857229]

1714857229

[1714857229]

1714857229

[1714857229]

1714857229

[1714857229]

1714857229

[1714857229]

1714857229

[kano]

I always get bored when the pool goes above 30-31

We get less blocks and the block payment plummets

sorry but that's my reality

More than happy to be awakened by a new reality that includes a proportionate amount of blocks with higher hash.

30? What
It was around 35 last time someone came up with comments about a hash rate jump above that bringing bad luck
I wonder how low it would have to go before that idea disappears ... hopefully wont happen ... ... ...

[-ck]

I always get bored when the pool goes above 30-31

We get less blocks and the block payment plummets

sorry but that's my reality

More than happy to be awakened by a new reality that includes a proportionate amount of blocks with higher hash.

30? What
It was around 35 last time someone came up with comments about a hash rate jump above that bringing bad luck
I wonder how low it would have to go before that idea disappears ... hopefully wont happen ... ... ...

I thought it was 40 before that. Well, any value will do, people love finding associations where there are none.

[usukan]

I always get bored when the pool goes above 30-31

We get less blocks and the block payment plummets

sorry but that's my reality

More than happy to be awakened by a new reality that includes a proportionate amount of blocks with higher hash.

30? What
It was around 35 last time someone came up with comments about a hash rate jump above that bringing bad luck
I wonder how low it would have to go before that idea disappears ... hopefully wont happen ... ... ...

@Kano - I thought you might have guessed PHs

@CK - patterns fascinate me

Obviously a sensitive issue - so I will back off

Lets have some blocks then.......... We will all be happy



Cheers - usukan

[kano]

I always get bored when the pool goes above 30-31

We get less blocks and the block payment plummets

sorry but that's my reality

More than happy to be awakened by a new reality that includes a proportionate amount of blocks with higher hash.

30? What
It was around 35 last time someone came up with comments about a hash rate jump above that bringing bad luck
I wonder how low it would have to go before that idea disappears ... hopefully wont happen ... ... ...

@Kano - I thought you might have guessed PHs

@CK - patterns fascinate me

Obviously a sensitive issue - so I will back off

Lets have some blocks then.......... We will all be happy



Cheers - usukan

Sensitive? No.
Just there is no pattern - even looking at the pool graph shows there is none.
This month has gone: ok just to start, down, up, down a little and that's it so far.
The pool hash rate has no matching pattern to that.
The hash rate this month has peaks in the days of good luck.

P.S. that block now was stale - late to get to the pool.

[HerbPean]

Antpoo  

[kano]

Antpoo  

Nah, nothing to do with orphans, it was simply a stale block/share.

It was at the DE node - but probably came from russia so was a little slow all around.

The pool changed block work at 07:23:08.750

The DE node got the share after that at 07:23:09.135
The main node got the share at 07:23:09.213

As I've mentioned before, ckpool will treat pretty much any block that arrives as a block and try to process it, submit it and always report it to ckdb.
CKDB always shows all such shares - so I then have to check and decide what it really was.
In this case, simply a stale share, not an orphan.

[kano]

...
what was the reason for the sudden drop in everyones hashrate after the "stale" block?

If you mean the pool graph, that's simply because the shift was so short.
Variance increases as the length of shifts get shorter.

In this case, fewer shares than expected got into the shift before it changed. Variance
It went from 33PHs to 29PHs - so about only 88% of expected shares in the short shift.
(the shift was 52s instead of the usual about 45minutes, so about 2% of a normal shift)

[kano]

Block! by 1GT2...
The '2' together is ~330% oh well.

[moe7865]

A little more than an hour ago the rewards page said we had a block 3 hours earlier, but nothing posted on the rewards page like it normally does. About an hour later I arrive at work and see we hit another block 45 minutes ago, but I only see one reward for the day. Do you know why only one reward is showing for today?

The other block was stale

[kano]

A little more than an hour ago the rewards page said we had a block 3 hours earlier, but nothing posted on the rewards page like it normally does. About an hour later I arrive at work and see we hit another block 45 minutes ago, but I only see one reward for the day. Do you know why only one reward is showing for today?

As moe7865 said, but I did post towards the bottom of the page ...
https://bitcointalk.org/index.php?topic=789369.msg16891460#msg16891460

If you look at the blocks page it's there also, struck out, as Stale.

[clgrissom3]

Well, we have one in the queue and the spot price is at $734...a good start this morning! 

[ZACHM]

I was getting notifications from my monitor and saw this:
Block @ approx 280%
Then another less than 5 hours later @ 330% 

I thought I needed to fix something. 
Then I logged in and saw what happened. 

[clgrissom3]

I was getting notifications from my monitor and saw this:
Block @ approx 280%
Then another less than 5 hours later @ 330%  

I thought I needed to fix something.  
Then I logged in and saw what happened.  

I know I was scratching my head on that one until I saw the stale! 

[firetreeactual]

I thought it was 40 before that. Well, any value will do, people love finding associations where there are none.

Got a good chuckle outta that one, Con...that's a concept I had a helluva time getting my grad school students to grasp in Research Methods. Applies everywhere. 

[HerbPean]

Antpoo  

Nah, nothing to do with orphans, it was simply a stale block/share.

It was at the DE node - but probably came from russia so was a little slow all around.

The pool changed block work at 07:23:08.750

The DE node got the share after that at 07:23:09.135
The main node got the share at 07:23:09.213

As I've mentioned before, ckpool will treat pretty much any block that arrives as a block and try to process it, submit it and always report it to ckdb.
CKDB always shows all such shares - so I then have to check and decide what it really was.
In this case, simply a stale share, not an orphan.

Yeah I saw orphan at first then it went to Stale

Thanks for the clarification ;-)

[not.you]

I always get bored when the pool goes above 30-31

We get less blocks and the block payment plummets

sorry but that's my reality

More than happy to be awakened by a new reality that includes a proportionate amount of blocks with higher hash.

30? What
It was around 35 last time someone came up with comments about a hash rate jump above that bringing bad luck
I wonder how low it would have to go before that idea disappears ... hopefully wont happen ... ... ...

I thought it was 40 before that. Well, any value will do, people love finding associations where there are none.

I've noticed that whenever you post in this thread we have a string of good luck... You should post more 

[ZACHM]

I thought it was when he posted less before that. Well, any posting will do, people love finding associations where there are none.


 Sorry, couldn't resist.

[firetreeactual]

Guess I'm sorta broadcasting my screwup, but oh, well...I'm gonna find out today if one can snag a single good hash board from each of two toasted A6s, and build one good A6. Beats cleaning house.  

[VRobb]

Guess I'm sorta broadcasting my screwup, but oh, well...I'm gonna find out today if one can snag a single good hash board from each of two toasted A6s, and build one good A6. Beats cleaning house.  

Don't feel too bad, I was ready to get my current S7 up on the pool, announcing it to all, and in my haste to get it up and running used a CPU connector instead of a PCIe connector (looks the same but + and - are reversed) and promptly smoked my IO card and was down for weeks waiting on a new one...

SO THERE!  Now as soon as the A7(21)s start shipping I should have more hash here again, assuming no smoking is involved...