Author

Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 350. (Read 5352229 times)

jr. member
Activity: 76
Merit: 2
member
Activity: 285
Merit: 10
Free mining equipment tracking and reporting
I am just about to join the kano pool with more than 50 TH/s, but what's the difference in payouts to for example slushpool in average?
If you want to see actual historical difference, check out the CDT (Coin per Day per Th/s) values for slush and kano.  Obviously past luck makes a big difference on these but would give you an idea of what you "would have" made if you were mining in one place or another.

*edit - oops, I see that clgrissom3 gave the same answer!
legendary
Activity: 1736
Merit: 1032
Carl, aka Sonny :)
I am just about to join the kano pool with more than 50 TH/s, but what's the difference in payouts to for example slushpool in average?

MinerGain has been following both pools with some interesting (historical) analysis at https://www.minergain.com/
newbie
Activity: 53
Merit: 0
Hello, I am ramping up nicely and it was nice to have such a block filled weekend!

My question is regarding Dragonmint T1 AsicBoost. I see that there are a few pools that support it currently. Will Kano be supporting AB or will I have to point them somewhere else when they arrive?

Appreciate the help and think the pool is great, keep up the marketing guys! or should I say enlightenment  Grin

Brickman
https://bitcointalksearch.org/topic/m.33193546

Thank you Sir........
I appreciate pointing me to the answer.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Hello, I am ramping up nicely and it was nice to have such a block filled weekend!

My question is regarding Dragonmint T1 AsicBoost. I see that there are a few pools that support it currently. Will Kano be supporting AB or will I have to point them somewhere else when they arrive?

Appreciate the help and think the pool is great, keep up the marketing guys! or should I say enlightenment  Grin

Brickman
https://bitcointalksearch.org/topic/m.33193546
newbie
Activity: 53
Merit: 0
Hello, I am ramping up nicely and it was nice to have such a block filled weekend!

My question is regarding Dragonmint T1 AsicBoost. I see that there are a few pools that support it currently. Will Kano be supporting AB or will I have to point them somewhere else when they arrive?

Appreciate the help and think the pool is great, keep up the marketing guys! or should I say enlightenment  Grin

Brickman
member
Activity: 238
Merit: 11
I am just about to join the kano pool with more than 50 TH/s, but what's the difference in payouts to for example slushpool in average?

On average, you get 1.1% more than Slush.

Remember this when bitcoin hits $100,000  Grin
copper member
Activity: 232
Merit: 2
I am just about to join the kano pool with more than 50 TH/s, but what's the difference in payouts to for example slushpool in average?
legendary
Activity: 3234
Merit: 1221
full member
Activity: 350
Merit: 158
#takeminingback
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

legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
...
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 Smiley

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  Wink
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 Smiley
https://bitcointalksearch.org/topic/m.33329486
newbie
Activity: 94
Merit: 0
...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 Smiley

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 Smiley

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 Smiley

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  Wink
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
...
I have everything bad on schedule, I understand it correctly? http://prntscr.com/ixcazz
0.013% is good even if they were all stale Smiley
It's even better coz a lot of them are Hi so they don't matter.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
...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 Smiley

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 Smiley

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 Smiley

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
newbie
Activity: 94
Merit: 0
...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 Smiley

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 Smiley

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
member
Activity: 490
Merit: 16
1xA921 + 1xA741 + Backup-->1xA6 ;)
...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 Smiley

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 Smiley

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.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
...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 Smiley

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 Smiley

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
member
Activity: 490
Merit: 16
1xA921 + 1xA741 + Backup-->1xA6 ;)
...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.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
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
member
Activity: 490
Merit: 16
1xA921 + 1xA741 + Backup-->1xA6 ;)
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.?
Jump to: