Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 1743. (Read 5352322 times)
February 07, 2016, 08:35:14 AM
Block Difficulty 144116447847
February 07, 2016, 07:39:49 AM
5 payouts sent and confirmed in the last 10hrs:
Payout 397045 sent 9.5hrs ago
2b8d10dce862a791d7a07f51a158eacbff1d65d9b24a2c63b3dde399c42b6372
Payout 397061 sent 7hrs ago
09454b962373f41a0782aea02f0663a0d9160d043581530947e0be89ec48234f
Payout 397073 sent 5hrs ago
f6e856ac2b8c257611b3d361425f2583f2dc46cd5238cb8efdcc8a8a0335154d
Payout 397102 sent 1.25hrs ago
c0517a7b81d33cfe2645820e749d934f7c60c0f6851154efb82e12c1fcd1f8c2
Payout 397104 sent 1hr ago
20963e73228a4807b16ea023eb49ff9cb26404cb63537950e5156b20efc2f75a
All confirmed.
2 more in the queue.
Next one I'll send in the morning since it will be around 4am my time
So if there's anything I can say about that stale block - if we have to have one, it's way better to see one when luck is this good, than when luck is low
Payout 397045 sent 9.5hrs ago
2b8d10dce862a791d7a07f51a158eacbff1d65d9b24a2c63b3dde399c42b6372
Payout 397061 sent 7hrs ago
09454b962373f41a0782aea02f0663a0d9160d043581530947e0be89ec48234f
Payout 397073 sent 5hrs ago
f6e856ac2b8c257611b3d361425f2583f2dc46cd5238cb8efdcc8a8a0335154d
Payout 397102 sent 1.25hrs ago
c0517a7b81d33cfe2645820e749d934f7c60c0f6851154efb82e12c1fcd1f8c2
Payout 397104 sent 1hr ago
20963e73228a4807b16ea023eb49ff9cb26404cb63537950e5156b20efc2f75a
All confirmed.
2 more in the queue.
Next one I'll send in the morning since it will be around 4am my time
So if there's anything I can say about that stale block - if we have to have one, it's way better to see one when luck is this good, than when luck is low
February 07, 2016, 07:22:06 AM
Nope.
Where we gonna fit 109 numbers for bitminerpro ...
Where we gonna fit 109 numbers for bitminerpro ...
Just one number, last known hasrate/shift so it works if someone has left the pool for exemple ?
of course it may not be accurate if someone has found 1 block with 1Ghs and then got more. His last hashrate may not be representatative of the hasrate he/she had when he/she discovered the block.
but globally, I think there's a certain consistency in hasrate for a given user.
One doesn't go from Mhs to Phs very fast (unless renting, but that doesn't last long)
Anyway, I'm not arguing, you're the boss
February 07, 2016, 06:17:29 AM
It looks like block 397163 was hit by another small miner, Romari1987 with 9THs...he gets on the Kano Acclaim board for the first time!
\o/ !
it'd be cool if the acclaim table would show the Hash Rate too
(Current or average at the time the block is found or... ? )Where we gonna fit 109 numbers for bitminerpro ...
February 07, 2016, 05:43:28 AM
It looks like block 397163 was hit by another small miner, Romari1987 with 9THs...he gets on the Kano Acclaim board for the first time!
\o/ !
it'd be cool if the acclaim table would show the Hash Rate too
(Current or average at the time the block is found or... ? ) 
February 07, 2016, 05:27:21 AM
It looks like block 397163 was hit by another small miner, Romari1987 with 9THs...he gets on the Kano Acclaim board for the first time!
February 07, 2016, 04:45:44 AM
...
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?
If you click on the blue ? it tells you 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?
"Share diff was VERY close
so we tested it,
but it wasn't worthy"
i.e. we test any share within 99.9% of being a block.
We used to test 99% but adjusted that up to 99.9% recently.
It was an "Unworthy" share - not worthy of being a block, not good enough difficulty, but we submit it in case of any rounding/math errors.
February 07, 2016, 04:41:33 AM
citronick, it is because of floating point operations rounding inaccuracies, kano.is checkes also blocks that are within 99.9% of required difficulty. So to my understanding it is deliberate process.
February 07, 2016, 04:39:29 AM
So how close do they have to be to be considered orphan. Less than 10ms?
Any other pool will probably only report an orphan if they successfully submitted the block to the network and it loses an orphan race.i.e. if the block goes out and people find out about it
So in our case a true orphan would get a normal block reply like the previous 397163 one:
Code:
[2016-02-07 16:25:11.651] Possible block solve diff 821005982664.717041 !
[2016-02-07 16:25:11.927] BLOCK ACCEPTED!
But then it would have to fail an orphan race on the network.[2016-02-07 16:25:11.927] BLOCK ACCEPTED!
In this case we already knew the network had another block (23ms earlier) so it didn't even start an orphan race.
February 07, 2016, 04:36:51 AM
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
ckdb said it all
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.
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?
February 07, 2016, 04:29:25 AM
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
February 07, 2016, 04:27:29 AM
So how close do they have to be to be considered orphan. Less than 10ms?
February 07, 2016, 04:20:50 AM
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
ckdb said it all
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.
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.
February 07, 2016, 04:16:58 AM
Dammit, woke up at 3:16AM for nothing. Was doing the entire BLOCK DANCE too........................ARGHHHHHHHHHHHHHHHHHHHHHHH
February 07, 2016, 04:15:22 AM
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?
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?
February 07, 2016, 04:12:25 AM
7 More blocks to Super Sunday! DAMMIT, SCRATCH THAT!! GOT EXCITED FOR NOTHING.. 8 MO TO GO! !@#@%@!#$@$%#RS@#$@#$@W@#$@#$@#$@#$@#$@#
February 07, 2016, 04:09:34 AM
Now just an orphan
397182 Dsman_S7_3 25.23924789 2016-02-07 09:01:52+00 Orphan *~0 ? ? 0
397182 Dsman_S7_3 25.23924789 2016-02-07 09:01:52+00 Orphan *~0 ? ? 0
February 07, 2016, 04:08:49 AM
Bitfury snaked that one out from us. Bastards!
February 07, 2016, 04:06:35 AM
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
# 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
February 07, 2016, 04:05:42 AM
Ouch...Orphan
Jump to: