Author

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

legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Of course S9v2 is the best result, but you can't make a miner designed to get more blocks than expected, you CAN make a miner that doesn't.
In theory you actually could have a miner that gets more blocks than expected for its measured hashrate. For example you could have a bug that causes low diff shares to be thrown out but not any high diff block finding shares(effectively the reverse of a block withholding miner).
Yes well, then no one would buy it and bitmain would have gone broke long ago - since in that case you would be getting underpaid on every non-solo pool and see that very quickly.
bitmain wouldn't gain from that either.

Of course my spec on how to design a miner covers that issue ...
https://bitcointalksearch.org/topic/optimal-firmwarehardware-design-for-mining-with-cgminer-294499
(the last item)
hero member
Activity: 777
Merit: 1003
In theory you actually could have a miner that gets more blocks than expected for its measured hashrate. For example you could have a bug that causes low diff shares to be thrown out but not any high diff block finding shares(effectively the reverse of a block withholding miner).

I don't think that would be considered a bug, that would be considered working correctly.  Wink
legendary
Activity: 1736
Merit: 1032
Carl, aka Sonny :)
Block by cobramining!  This is his 12th Kano block and our 1st of the day!  Cheesy

EDIT: Removed comment  Wink
It was a DE block and DE processed it faster than the main pool did.
That of course also means that it got onto the relay and out to the rest of the world first from DE.

The duplicate message was actually caused by the miner submitting the same share twice.
I see this every so often, duplicate shares submitted, and often the 2nd one is indeed quite a bit later.
When it's a block, you see it like that.

We don't hide anything about the good or bad blocks, so they come thru and get processed in the same way.
However, CKDB doesn't bother showing the same block twice (since it should only pay it once Tongue), so you don't see it twice on the web site.
(and of course the duplicate was a duplicate stale and unrewarded share)

After I posted the comment about it I finally remembered seeing this happen before so I removed the it.  I was a little slow catching on to that one! Grin
sr. member
Activity: 261
Merit: 257
Of course S9v2 is the best result, but you can't make a miner designed to get more blocks than expected, you CAN make a miner that doesn't.
In theory you actually could have a miner that gets more blocks than expected for its measured hashrate. For example you could have a bug that causes low diff shares to be thrown out but not any high diff block finding shares(effectively the reverse of a block withholding miner).
legendary
Activity: 3234
Merit: 1220
Monthly Statistics

UTC Month-----   Pool Avg---   Blocks   Expected   Mean Diff%   MeanTx%   Luck%   PPS%
2017 Jan…..   23.01PHs..   15.....   14.33   95.56%.....   105.84%   104.65%   109.76%


Okay  so  how many of us pulled the s9 version 1's and pointed them to f2pool------ I did that

or upgraded the s9 version 1 to version 2?


104.65% luck  not counting fees

109.76% luck with fees.

@ kano  is the avalon 7  picking up the pace?

I didn't I just upgraded the v1's to v2's and kept them here.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Block by cobramining!  This is his 12th Kano block and our 1st of the day!  Cheesy

Wow, a C1 got a block! Good news that the older gear can still knock one out every now and then. Way to go cobramining!
Heh, no, it was an A7v1 Smiley
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
...
@ kano  is the avalon 7  picking up the pace?
Last time I processed payouts:
Code:
 CDF[Erl] |Miner |    DiffAcc
 0.997230 | S9v1 | 27,341.28G | 111.65718138 BDR | 84 Blocks
 0.694527 | A7v2 |    375.22G |   1.18589504 BDR |  1 Blocks
 0.586133 | A7v1 |  2,655.81G |   9.32341696 BDR |  9 Blocks
 0.146084 | S9v2 |  5,267.95G |  18.02093093 BDR | 23 Blocks
All time forever totals.

Edit: corrected Tongue that was the ratio, not the CDF[Erl] - fixed.

Edit2: and the important point for anyone looking at that ... ONLY the top S9v1 number matters.
The rest are good - and you cannot fault them in any way.
Of course S9v2 is the best result, but you can't make a miner designed to get more blocks than expected, you CAN make a miner that doesn't.

Edit3:
cobramining's block was an A7v1
steve1's block was probably an S7
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Block by cobramining!  This is his 12th Kano block and our 1st of the day!  Cheesy

EDIT: Removed comment  Wink
It was a DE block and DE processed it faster than the main pool did.
That of course also means that it got onto the relay and out to the rest of the world first from DE.

The duplicate message was actually caused by the miner submitting the same share twice.
I see this every so often, duplicate shares submitted, and often the 2nd one is indeed quite a bit later.
When it's a block, you see it like that.

We don't hide anything about the good or bad blocks, so they come thru and get processed in the same way.
However, CKDB doesn't bother showing the same block twice (since it should only pay it once Tongue), so you don't see it twice on the web site.
(and of course the duplicate was a duplicate stale and unrewarded share)
legendary
Activity: 1834
Merit: 1080
---- winter*juvia -----
Monthly Statistics

UTC Month-----   Pool Avg---   Blocks   Expected   Mean Diff%   MeanTx%   Luck%   PPS%
2017 Jan…..   23.01PHs..   15.....   14.33   95.56%.....   105.84%   104.65%   109.76%


Okay  so  how many of us pulled the s9 version 1's and pointed them to f2pool------ I did that

or upgraded the s9 version 1 to version 2?


104.65% luck  not counting fees

109.76% luck with fees.

@ kano  is the avalon 7  picking up the pace?

A few months ago, I have pulled out all the Juvia-S9s (108 x S9v1) to another PPLNS pool.

In the weekend, re-routed Gray-A7 farm (120 x A721) to Kano.

It will be interesting to see the impact of the above, esp. removing a large number of S9v1s away from the pool.
legendary
Activity: 4326
Merit: 8950
'The right to privacy matters'
Monthly Statistics

UTC Month-----   Pool Avg---   Blocks   Expected   Mean Diff%   MeanTx%   Luck%   PPS%
2017 Jan…..   23.01PHs..   15.....   14.33   95.56%.....   105.84%   104.65%   109.76%


Okay  so  how many of us pulled the s9 version 1's and pointed them to f2pool------ I did that

or upgraded the s9 version 1 to version 2?


104.65% luck  not counting fees

109.76% luck with fees.

@ kano  is the avalon 7  picking up the pace?
hero member
Activity: 658
Merit: 500
Visualize whirledps
Good job, Kanoians! January is working well for the pool even with the decreased hash. Keep up the great work!! Smiley Smiley
legendary
Activity: 1736
Merit: 1032
Carl, aka Sonny :)
Very nice. A little green for the cold weather on the east coast Smiley

Amen to that!  Green blocks to soothe my aching back from shoveling so much snow! Grin
member
Activity: 136
Merit: 11
Very nice. A little green for the cold weather on the east coast Smiley
legendary
Activity: 1736
Merit: 1032
Carl, aka Sonny :)
Block by steve1!  This is his 10th Kano block and our 2nd very early in the day!  Cheesy Cheesy
sr. member
Activity: 277
Merit: 250
Block by cobramining!  This is his 12th Kano block and our 1st of the day!  Cheesy

Wow, a C1 got a block! Good news that the older gear can still knock one out every now and then. Way to go cobramining!
legendary
Activity: 1736
Merit: 1032
Carl, aka Sonny :)
Block by cobramining!  This is his 12th Kano block and our 1st of the day!  Cheesy

EDIT: Removed comment  Wink
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
http://tradebtc.net/bitcalc.php Smiley

(which e.g. says at the moment 24PHs is ~1.5 blocks a day)
hero member
Activity: 1610
Merit: 538
I'm in BTC XTC
Sure, if you want to know what the pool's expected blocks per day based on current hashrate that's easy. Plugging that into a calculator at present difficulty I get just a touch over 1.5 blocks per day expected.  Variance, on the other hand, will make the ride bumpy!

If you want to know what days we'll hit 3 or 4 or 5 blocks you'll have to consult some chickens.  Wink
member
Activity: 126
Merit: 10
I miss those 5 block days...

I would love 2. How can we know what are the chances that kano.is will find more then 2/3/4/5/6 blocks for a day. In next days or weekss  Are there any calculations that can predict at least suppose.
sr. member
Activity: 324
Merit: 250
I miss those 5 block days...
Jump to: