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

[nhando]

ANything is possible in the Kano Pool.  At our hash rate 3-4 blocks a day is normal before the jump.  We've seen 300%+ luck so LET'S GO!!!!!  

This alone is showing it's possible.


Description   Time   MeanTx%   Diff%   Mean%   CDF[Erl]   Luck%
Last 5 Blocks   11.4hrs   101.1%   33.74%   33.74%   0.0288   296.41%

[1714692246]

1714692246

[1714692246]

1714692246

[kilo17]

Funny to see all the big hash rentals drop when the difficulty goes up 

[nhando]

2 out of 10 blocks for our Super SUnday!! and So it begins!!

Great Job Romari1987!!!  Under 10TH Miner.   I will match your payout, just PM me to show the Rewards tab with your payout info when it's available.   

[OneInchWonder]

block found

Did not take long with new difficulty.

[baazju]

We always get one early on with the diff change it seems.

[nhando]

It's not Luck.  It's CK and KANO SECRET Sauce I told u.   Don't be surprised if we hit our Super 10 Sunday!

[PPOC]

I know it's way to early to call, but the blocks after diff are still rolling along at the same speed, about 6 in 40-45m. That's stays steady and another 20% in 12 days and halfing is now projected in June. Watch out below

[bctmke]

It's been a very good day so far and that difficulty increase was kinda nuts but not unexpected.

[kano]

I know it's way to early to call, but the blocks after diff are still rolling along at the same speed, about 6 in 40-45m. That's stays steady and another 20% in 12 days and halfing is now projected in June. Watch out below

Yes it's way too early to call.

[Xunknown]

Ouch...Orphan

[wttbs]

I never seen this before... guess something is not 100% OK or perhaps Orphan


#   Height   Block Reward   When   Status   Diff   Diff%   CDF   B
514   397182   25.23924789   2016-02-07 09:01:52+00   New   ~0   ?   ?   1
513   397163   25.09993944   2016-02-07 05:25:11+00   +20 Confirms   53,277,174,830   36.968%   0.309   2
512   397140   25.12460839   2016-02-07 02:15:10+00   +43 Confirms   77,066,132,001   64.204%   0.474   3

[Xunknown]

Bitfury snaked that one out from us.  Bastards!

[SergES]

Now just an orphan
397182   Dsman_S7_3   25.23924789   2016-02-07 09:01:52+00   Orphan   *~0   ?   ?   0

[nhando]

7 More blocks to Super Sunday!  DAMMIT, SCRATCH THAT!! GOT EXCITED FOR NOTHING..  8 MO TO GO! !@#@%@!#$@$%#RS@#$@#$@W@#$@#$@#$@#$@#$@#

[citronick]

Hey Dsman.... upgrade your internet connection speed - LOL- 

I read another thread that, if your internet connection is slow or unstable, this will impact confirmation back to the blockchain that your miner claimed the block. Comments?

[nhando]

Dammit, woke up at 3:16AM for nothing.  Was doing the entire BLOCK DANCE too........................ARGHHHHHHHHHHHHHHHHHHHHHHH

[kano]

Yeah it's actually a stale block, not really an orphan, but I flagged it as an orphan since it was so soon after the block change.
23ms to be exact

Code:

[2016-02-07 20:01:52.443] Block hash changed to 00000000000000000035265ac239027ea0d42d79ab52d0a8e41407ca3b3bf787
[2016-02-07 20:01:52.466] Possible block solve diff 165763508925.062866 !
[2016-02-07 20:01:52.864] SUBMIT BLOCK RETURNED: inconclusive

ckdb said it all

Code:

[2016-02-07 20:01:52.551+11] BLOCK! STALE Diff 115.0% (165763508925/144116447847.3) -- Pool 63712173407.0 63.7G 44.21%

As mentioned before, we submit any block that shows up from the miners, also any block that's within 99.9% of being a block.
All to make sure we never lose one.
This is an example of one of those blocks that was never meant to be, but ckpool tried anyway, and ckdb reports it.

[Xunknown]

So how close do they have to be to be considered orphan.  Less than 10ms?

[marvykkio]

7 More blocks to Super Sunday!  DAMMIT, SCRATCH THAT!! GOT EXCITED FOR NOTHING..  8 MO TO GO! !@#@%@!#$@$%#RS@#$@#$@W@#$@#$@#$@#$@#$@#

but how to count the blocks you?
Sundays are only 2 blocks,
if you count the 24-hour shift and then right

[citronick]

Yeah it's actually a stale block, not really an orphan, but I flagged it as an orphan since it was so soon after the block change.
23ms to be exact

Code:

[2016-02-07 20:01:52.443] Block hash changed to 00000000000000000035265ac239027ea0d42d79ab52d0a8e41407ca3b3bf787
[2016-02-07 20:01:52.466] Possible block solve diff 165763508925.062866 !
[2016-02-07 20:01:52.864] SUBMIT BLOCK RETURNED: inconclusive

ckdb said it all

Code:

[2016-02-07 20:01:52.551+11] BLOCK! STALE Diff 115.0% (165763508925/144116447847.3) -- Pool 63712173407.0 63.7G 44.21%

As mentioned before, we submit any block that shows up from the miners, also any block that's within 99.9% of being a block.
All to make sure we never lose one.
This is an example of one of those blocks that was never meant to be, but ckpool tried anyway, and ckdb reports it.

there was another case Blk 344-345, that was "unworthy" - would that mean it was not even a true block to be claimed, compared to situation above?
what would trigger an "unworthy" block ? miner malfunction?