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

[Shazam!!!]

My invalids are down 4% from this morning! Just saying.....

yeaaaaa

Down another .003% since my post.

My ears perked up.


MINE ON!!!

And another .003%........

[1714327727]

1714327727

[1714327727]

1714327727

[1714327727]

1714327727

[lok8nusa]

My invalids are down 4% from this morning! Just saying.....

yeaaaaa

Down another .003% since my post.

My ears perked up.


MINE ON!!!

And another .003%........

I know we're supposed to dance, but I don't think we're supposed to do it on the f5 button.   

[BSGMiner]

I know we're supposed to dance, but I don't think we're supposed to do it on the f5 button.   

Maybe that's what Kano is mistaking for a DDoS attack!

[gaud]

i think the shazam luck streak is over lol

[BSGMiner]

i think the shazam luck streak is over lol

Maybe higher invalids were better after all...

[Shazam!!!]

i think the shazam luck streak is over lol

Maybe,  but it's still going down. Just seems odd.

[rifleman74]

My invalids are down 4% from this morning! Just saying.....

yeaaaaa

Down another .003% since my post.

My ears perked up.


MINE ON!!!

And another .003%........

.092% here, that's about "normal" for me. 

[gaud]

My invalids are down 4% from this morning! Just saying.....

yeaaaaa

Down another .003% since my post.

My ears perked up.


MINE ON!!!

And another .003%........

.092% here, that's about "normal" for me. 

.086 fer me too

[Shazam!!!]

Here it is. Still dropping too. Was much higher earlier. I keep a close eye on it cause, I monitor my miners closely when I'm at home. Wasn't moving around yesterday at all.

[BSGMiner]

Here it is. Still dropping too. Was much higher earlier. I keep a close eye on it cause, I monitor my miners closely when I'm at home. Wasn't moving around yesterday at all.

But, what are the details behind the Invalid %? Are they Stale, Hi, etc.?

[kano]

Here it is. Still dropping too. Was much higher earlier. I keep a close eye on it cause, I monitor my miners closely when I'm at home. Wasn't moving around yesterday at all.

But, what are the details behind the Invalid %? Are they Stale, Hi, etc.?

Yeah there's a lot of Hi so you'd expect that Invalid% to slowly go down until the next block - since Hi are usually caused when you connect - (and also have no expected effect on your reward) - and those stats reset when we find a block

[BSGMiner]

...Hi are usually caused when you connect - (and also have no expected effect on your reward)...

Could you please expand on that part a little bit--Hi Invalids not effecting reward?

I've noticed if I set a Work Diff at, say, 3586 for my Avalon6, it seems to avoid tripping Hi Invalids if I need to restart/reboot. I would think this is a positive effect by not wasting shares. Maybe I'm misunderstanding something.

[kano]

...Hi are usually caused when you connect - (and also have no expected effect on your reward)...

Could you please expand on that part a little bit--Hi Invalids not effecting reward?

I've noticed if I set a Work Diff at, say, 3586 for my Avalon6, it seems to avoid tripping Hi Invalids if I need to restart/reboot. I would think this is a positive effect by not wasting shares. Maybe I'm misunderstanding something.

As an example - rather than the maths - but the example is based on expected reality in the results

Worker starts at diff 1000 but sends based on 100 diff:
101 128 256 524 130 1200 760 930 300 666

So if diff was 100 - they will have got 100x10 = 1000 diff worth of value
However, diff is 1000 - so they all get rejected except the one of 1200 = 1x1000 = 1000 diff worth of value
Same diff

Now those numbers match the expected result - but of course what you actually get is random - but will average out to be the same:
since 1 in 10 of every share greater than or equal to 100 is expected (over a large sample) to be greater than or equal to 1000

[BSGMiner]

...Hi are usually caused when you connect - (and also have no expected effect on your reward)...

Could you please expand on that part a little bit--Hi Invalids not effecting reward?

I've noticed if I set a Work Diff at, say, 3586 for my Avalon6, it seems to avoid tripping Hi Invalids if I need to restart/reboot. I would think this is a positive effect by not wasting shares. Maybe I'm misunderstanding something.

As an example - rather than the maths - but the example is based on expected reality in the results

Worker starts at diff 1000 but sends based on 100 diff:
101 128 256 524 130 1200 760 930 300 666

So if diff was 100 - they will have got 100x10 = 1000 diff worth of value
However, diff is 1000 - so they all get rejected except the one of 1200 = 1x1000 = 1000 diff worth of value
Same diff

Now those numbers match the expected result - but of course what you actually get is random - but will average out to be the same:
since 1 in 10 of every share greater than or equal to 100 is expected (over a large sample) to be greater than or equal to 1000

Thanks! So, sticking with your example, I suppose their worker page would show 9 Hi.

[Nick_01]

...Hi are usually caused when you connect - (and also have no expected effect on your reward)...

Could you please expand on that part a little bit--Hi Invalids not effecting reward?

I've noticed if I set a Work Diff at, say, 3586 for my Avalon6, it seems to avoid tripping Hi Invalids if I need to restart/reboot. I would think this is a positive effect by not wasting shares. Maybe I'm misunderstanding something.

As an example - rather than the maths - but the example is based on expected reality in the results

Worker starts at diff 1000 but sends based on 100 diff:
101 128 256 524 130 1200 760 930 300 666

So if diff was 100 - they will have got 100x10 = 1000 diff worth of value
However, diff is 1000 - so they all get rejected except the one of 1200 = 1x1000 = 1000 diff worth of value
Same diff

Now those numbers match the expected result - but of course what you actually get is random - but will average out to be the same:
since 1 in 10 of every share greater than or equal to 100 is expected (over a large sample) to be greater than or equal to 1000

I have everything bad on schedule, I understand it correctly? http://prntscr.com/ixcazz

[kano]

...Hi are usually caused when you connect - (and also have no expected effect on your reward)...

Could you please expand on that part a little bit--Hi Invalids not effecting reward?

I've noticed if I set a Work Diff at, say, 3586 for my Avalon6, it seems to avoid tripping Hi Invalids if I need to restart/reboot. I would think this is a positive effect by not wasting shares. Maybe I'm misunderstanding something.

As an example - rather than the maths - but the example is based on expected reality in the results

Worker starts at diff 1000 but sends based on 100 diff:
101 128 256 524 130 1200 760 930 300 666

So if diff was 100 - they will have got 100x10 = 1000 diff worth of value
However, diff is 1000 - so they all get rejected except the one of 1200 = 1x1000 = 1000 diff worth of value
Same diff

Now those numbers match the expected result - but of course what you actually get is random - but will average out to be the same:
since 1 in 10 of every share greater than or equal to 100 is expected (over a large sample) to be greater than or equal to 1000

Thanks! So, sticking with your example, I suppose their worker page would show 9 Hi.

No there's more - but 2 things:

1) there's the 'expected result' and the 'actual result'
Like throwing a dice, how many 6s will you get if you roll 12 times - you expect 2 - but you can get 0, 1, 10, whatever - but over a large sample - 6 bazillion rolls, you'd expect to get 1 bazillion 6s

2) However, it depends on what diff his miner is returning shares vs what diff the pool is expecting.
If the pool is expecting A but the miner is sending a lower B then you'd 'expect' B/A % to be OK and the rest to be Hi

[kano]

...
I have everything bad on schedule, I understand it correctly? http://prntscr.com/ixcazz

0.013% is good even if they were all stale
It's even better coz a lot of them are Hi so they don't matter.

[Nick_01]

...Hi are usually caused when you connect - (and also have no expected effect on your reward)...

Could you please expand on that part a little bit--Hi Invalids not effecting reward?

I've noticed if I set a Work Diff at, say, 3586 for my Avalon6, it seems to avoid tripping Hi Invalids if I need to restart/reboot. I would think this is a positive effect by not wasting shares. Maybe I'm misunderstanding something.

As an example - rather than the maths - but the example is based on expected reality in the results

Worker starts at diff 1000 but sends based on 100 diff:
101 128 256 524 130 1200 760 930 300 666

So if diff was 100 - they will have got 100x10 = 1000 diff worth of value
However, diff is 1000 - so they all get rejected except the one of 1200 = 1x1000 = 1000 diff worth of value
Same diff

Now those numbers match the expected result - but of course what you actually get is random - but will average out to be the same:
since 1 in 10 of every share greater than or equal to 100 is expected (over a large sample) to be greater than or equal to 1000

Thanks! So, sticking with your example, I suppose their worker page would show 9 Hi.

No there's more - but 2 things:

1) there's the 'expected result' and the 'actual result'
Like throwing a dice, how many 6s will you get if you roll 12 times - you expect 2 - but you can get 0, 1, 10, whatever - but over a large sample - 6 bazillion rolls, you'd expect to get 1 bazillion 6s

2) However, it depends on what diff his miner is returning shares vs what diff the pool is expecting.
If the pool is expecting A but the miner is sending a lower B then you'd 'expect' B/A % to be OK and the rest to be Hi

understood. Thanks to Kano for not being tired of answering our sometimes stupid and obvious questions ... the slush is clearly far from this pool  

[kano]

...
No there's more - but 2 things:

1) there's the 'expected result' and the 'actual result'
Like throwing a dice, how many 6s will you get if you roll 12 times - you expect 2 - but you can get 0, 1, 10, whatever - but over a large sample - 6 bazillion rolls, you'd expect to get 1 bazillion 6s

2) However, it depends on what diff his miner is returning shares vs what diff the pool is expecting.
If the pool is expecting A but the miner is sending a lower B then you'd 'expect' B/A % to be OK and the rest to be Hi

understood. Thanks to Kano for not being tired of answering our sometimes stupid and obvious questions ... the slush is clearly far from this pool  

I guess I should have added one more point that may be missed.

The miner will eventually switch to the correct work difficulty.
That may only take a few seconds or may take a minute or so, so the number of Hi shares will (usually) stop at that point and not keep increasing.

So the fraction of Hi shares will keep dropping as more shares are submitted without any Hi ones ... which of course explains the original post I made
https://bitcointalk.org/index.php?topic=789369.msg33329486#msg33329486

[Shazam!!!]

This morning its at .172% Must be going down, cause this block is a pain in the arse!!! Hahaha!!!

Worker  stale=922,956/100   dup=20,490/5   hi=32,784/8

Worker2 stale=871,495/94   dup=8,196/2       hi=151,626/37