And I have officially been here at Kano.is for 1000 blocks!
Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 1255. (Read 5352229 times)
August 31, 2016, 11:21:34 AM
Block by Jays86! That is his 38th Kano block and our 4th of the day!
And I have officially been here at Kano.is for 1000 blocks!
And I have officially been here at Kano.is for 1000 blocks!
August 31, 2016, 11:02:34 AM
And this is exactly why my mining power (albeit small) is pointed at this pool!! Thanks again to Kano!!!
+1
August 31, 2016, 10:15:46 AM
Quoted here so anyone looking for the info will see it here on this page:
The block was after our block on ALL relays, even in china.
I'll get the details of it worked out in a while ...
Edit: So the details as follows.
The block before was network block 427668 hash 004e5228... at 13:13 UTC
Our block 427668 hash ...00231688... came first on all the relays
Bitfury 427668 hash ...00213d62... came in after
So as usual for an orphan race, the winner is decided by the next block.
Bitfury confirmed their own block, so they won it by luck.
Unfortunately impossible to get around that, we sent out our block, as usual, as fast as possible to all nodes and all over the world, but since they sent out their block slower than us, the only way we could expect to lose would be them confirming their own block ... which is what happened.
A list of relay timestamps:
Beijing: they were 20/22 seconds after us:
[2016-08-31 13:18:10.687+00] ...00231688... sent, size 988035 with 631996 bytes on the wire
[2016-08-31 13:18:12.038+00] ...00231688... recv'd, size 988011 with 98578 bytes on the wire
[2016-08-31 13:18:32.955+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
HongKong: they were 14/15 seconds after us:
[2016-08-31 13:18:10.466+00] ...00231688... sent, size 988035 with 629157 bytes on the wire
[2016-08-31 13:18:11.989+00] ...00231688... recv'd, size 988011 with 107615 bytes on the wire
[2016-08-31 13:18:25.206+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
Europe: they were 0.8 seconds after us:
[2016-08-31 13:18:10.787+00] ...00231688... recv'd, size 988011 with 129878 bytes on the wire
[2016-08-31 13:18:11.559+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
Japan: they were 2.6/2.7 seconds after us:
[2016-08-31 13:18:10.729+00] ...00231688... sent, size 988035 with 631996 bytes on the wire
[2016-08-31 13:18:10.840+00] ...00231688... recv'd, size 988011 with 107615 bytes on the wire
[2016-08-31 13:18:13.405+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
US East: they were 0.9 seconds after us
[2016-08-31 13:18:10.150+00] ...00231688... sent, size 988035 with 631996 bytes on the wire
[2016-08-31 13:18:11.043+00] ...00231688... recv'd, size 988011 with 107159 bytes on the wire
[2016-08-31 13:18:13.164+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
US West: they were 2/1.7 seconds after us
[2016-08-31 13:18:10.158+00] ...00231688... sent, size 988035 with 631996 bytes on the wire
[2016-08-31 13:18:10.814+00] ...00231688... recv'd, size 988011 with 98578 bytes on the wire
[2016-08-31 13:18:12.868+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
... and we just got another block
I'll get the details of it worked out in a while ...
Edit: So the details as follows.
The block before was network block 427668 hash 004e5228... at 13:13 UTC
Our block 427668 hash ...00231688... came first on all the relays
Bitfury 427668 hash ...00213d62... came in after
So as usual for an orphan race, the winner is decided by the next block.
Bitfury confirmed their own block, so they won it by luck.
Unfortunately impossible to get around that, we sent out our block, as usual, as fast as possible to all nodes and all over the world, but since they sent out their block slower than us, the only way we could expect to lose would be them confirming their own block ... which is what happened.
A list of relay timestamps:
Beijing: they were 20/22 seconds after us:
[2016-08-31 13:18:10.687+00] ...00231688... sent, size 988035 with 631996 bytes on the wire
[2016-08-31 13:18:12.038+00] ...00231688... recv'd, size 988011 with 98578 bytes on the wire
[2016-08-31 13:18:32.955+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
HongKong: they were 14/15 seconds after us:
[2016-08-31 13:18:10.466+00] ...00231688... sent, size 988035 with 629157 bytes on the wire
[2016-08-31 13:18:11.989+00] ...00231688... recv'd, size 988011 with 107615 bytes on the wire
[2016-08-31 13:18:25.206+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
Europe: they were 0.8 seconds after us:
[2016-08-31 13:18:10.787+00] ...00231688... recv'd, size 988011 with 129878 bytes on the wire
[2016-08-31 13:18:11.559+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
Japan: they were 2.6/2.7 seconds after us:
[2016-08-31 13:18:10.729+00] ...00231688... sent, size 988035 with 631996 bytes on the wire
[2016-08-31 13:18:10.840+00] ...00231688... recv'd, size 988011 with 107615 bytes on the wire
[2016-08-31 13:18:13.405+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
US East: they were 0.9 seconds after us
[2016-08-31 13:18:10.150+00] ...00231688... sent, size 988035 with 631996 bytes on the wire
[2016-08-31 13:18:11.043+00] ...00231688... recv'd, size 988011 with 107159 bytes on the wire
[2016-08-31 13:18:13.164+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
US West: they were 2/1.7 seconds after us
[2016-08-31 13:18:10.158+00] ...00231688... sent, size 988035 with 631996 bytes on the wire
[2016-08-31 13:18:10.814+00] ...00231688... recv'd, size 988011 with 98578 bytes on the wire
[2016-08-31 13:18:12.868+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
... and we just got another block
And this is exactly why my mining power (albeit small) is pointed at this pool!! Thanks again to Kano!!!
August 31, 2016, 10:15:09 AM
Block by babycicak with 83.45THs! Welcome to the Acclaim Board with your 1st Kano block! That is our 3rd of the day!
Back to back blocks!
Back to back blocks!
LOL.... what a name "babycicak" - geli oh! Congrats all the same!
maybe cicak is his pest
and "babycicak" Happy Merdeka day
August 31, 2016, 10:06:56 AM
Block by josephtran2! That would be his 7th Kano block and our 2nd of the day!
.... and there it goes to orphan land.... poof!
.... this is actually a positive moment.... usually we will have luck swings after a few orphans
#lookingatpositives #dontdrinkratpoison #waitforavalon7
Haha! it does seem that orphans punctuate our low luck stretches sometimes...and that is when we start rebounding. I just realized that I have been here on Kano.is for 997 blocks...just 3 away from 1000 blocks! How's that for a milestone! My lifetime miner performance here is at 107%, right in line with the Block Statistics page.
Of course, when I started the Pool N Avg was 1.79PHs and I only saw 7 blocks total in the first month I was here!
Okay, I have been here on Kano.is now for 999 blocks...one more for 1000! A nice Green one would be a great way to hit it...and even better if it were one of my own miners!
August 31, 2016, 09:53:56 AM
I am here for the LONG run! I have conducted due diligence of most other pools and found CKPool(Kano.is) to be the most profitable!
Now, onto more Blocks!
Now, onto more Blocks!
August 31, 2016, 09:49:54 AM
I was off the mining some times, I would like to ask you what happened that luck for last 250blocks is under 100%?
As it says there on the blocks page:Code:
Last 250 Blocks 8.7wks 103.4% 103.80% 103.51% 0.7157 96.61% 98.99%
So the luck was 96.61% for 250 blocks with a CDF[Erl] of 0.7157 ... so not all that unexpected.The PPS reward over that 250 blocks averaged out around 98.99% PPS after removing pool fees ... so ... yeah not really all that bad ...
August 31, 2016, 09:34:31 AM
Block by babycicak with 83.45THs! Welcome to the Acclaim Board with your 1st Kano block! That is our 3rd of the day!
Back to back blocks!
Back to back blocks!
LOL.... what a name "babycicak" - geli oh! Congrats all the same!
August 31, 2016, 09:32:32 AM
... and we just confirmed our own block
oh yeah baby yeah!!!
can we confirm some more of our own blocks!
August 31, 2016, 09:26:26 AM
... and we just confirmed our own block
August 31, 2016, 09:26:13 AM
Block by babycicak with 83.45THs! Welcome to the Acclaim Board with your 1st Kano block! That is our 3rd of the day!
Back to back blocks!
Back to back blocks!
August 31, 2016, 09:26:00 AM
I was off the mining some times, I would like to ask you what happened that luck for last 250blocks is under 100%?
August 31, 2016, 09:21:26 AM
Quoted here so anyone looking for the info will see it here on this page:
The block was after our block on ALL relays, even in china.
I'll get the details of it worked out in a while ...
Edit: So the details as follows.
The block before was network block 427668 hash 004e5228... at 13:13 UTC
Our block 427668 hash ...00231688... came first on all the relays
Bitfury 427668 hash ...00213d62... came in after
So as usual for an orphan race, the winner is decided by the next block.
Bitfury confirmed their own block, so they won it by luck.
Unfortunately impossible to get around that, we sent out our block, as usual, as fast as possible to all nodes and all over the world, but since they sent out their block slower than us, the only way we could expect to lose would be them confirming their own block ... which is what happened.
A list of relay timestamps:
Beijing: they were 20/22 seconds after us:
[2016-08-31 13:18:10.687+00] ...00231688... sent, size 988035 with 631996 bytes on the wire
[2016-08-31 13:18:12.038+00] ...00231688... recv'd, size 988011 with 98578 bytes on the wire
[2016-08-31 13:18:32.955+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
HongKong: they were 14/15 seconds after us:
[2016-08-31 13:18:10.466+00] ...00231688... sent, size 988035 with 629157 bytes on the wire
[2016-08-31 13:18:11.989+00] ...00231688... recv'd, size 988011 with 107615 bytes on the wire
[2016-08-31 13:18:25.206+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
Europe: they were 0.8 seconds after us:
[2016-08-31 13:18:10.787+00] ...00231688... recv'd, size 988011 with 129878 bytes on the wire
[2016-08-31 13:18:11.559+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
Japan: they were 2.6/2.7 seconds after us:
[2016-08-31 13:18:10.729+00] ...00231688... sent, size 988035 with 631996 bytes on the wire
[2016-08-31 13:18:10.840+00] ...00231688... recv'd, size 988011 with 107615 bytes on the wire
[2016-08-31 13:18:13.405+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
US East: they were 0.9 seconds after us
[2016-08-31 13:18:10.150+00] ...00231688... sent, size 988035 with 631996 bytes on the wire
[2016-08-31 13:18:11.043+00] ...00231688... recv'd, size 988011 with 107159 bytes on the wire
[2016-08-31 13:18:13.164+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
US West: they were 2/1.7 seconds after us
[2016-08-31 13:18:10.158+00] ...00231688... sent, size 988035 with 631996 bytes on the wire
[2016-08-31 13:18:10.814+00] ...00231688... recv'd, size 988011 with 98578 bytes on the wire
[2016-08-31 13:18:12.868+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
... and we just got another block
I'll get the details of it worked out in a while ...
Edit: So the details as follows.
The block before was network block 427668 hash 004e5228... at 13:13 UTC
Our block 427668 hash ...00231688... came first on all the relays
Bitfury 427668 hash ...00213d62... came in after
So as usual for an orphan race, the winner is decided by the next block.
Bitfury confirmed their own block, so they won it by luck.
Unfortunately impossible to get around that, we sent out our block, as usual, as fast as possible to all nodes and all over the world, but since they sent out their block slower than us, the only way we could expect to lose would be them confirming their own block ... which is what happened.
A list of relay timestamps:
Beijing: they were 20/22 seconds after us:
[2016-08-31 13:18:10.687+00] ...00231688... sent, size 988035 with 631996 bytes on the wire
[2016-08-31 13:18:12.038+00] ...00231688... recv'd, size 988011 with 98578 bytes on the wire
[2016-08-31 13:18:32.955+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
HongKong: they were 14/15 seconds after us:
[2016-08-31 13:18:10.466+00] ...00231688... sent, size 988035 with 629157 bytes on the wire
[2016-08-31 13:18:11.989+00] ...00231688... recv'd, size 988011 with 107615 bytes on the wire
[2016-08-31 13:18:25.206+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
Europe: they were 0.8 seconds after us:
[2016-08-31 13:18:10.787+00] ...00231688... recv'd, size 988011 with 129878 bytes on the wire
[2016-08-31 13:18:11.559+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
Japan: they were 2.6/2.7 seconds after us:
[2016-08-31 13:18:10.729+00] ...00231688... sent, size 988035 with 631996 bytes on the wire
[2016-08-31 13:18:10.840+00] ...00231688... recv'd, size 988011 with 107615 bytes on the wire
[2016-08-31 13:18:13.405+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
US East: they were 0.9 seconds after us
[2016-08-31 13:18:10.150+00] ...00231688... sent, size 988035 with 631996 bytes on the wire
[2016-08-31 13:18:11.043+00] ...00231688... recv'd, size 988011 with 107159 bytes on the wire
[2016-08-31 13:18:13.164+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
US West: they were 2/1.7 seconds after us
[2016-08-31 13:18:10.158+00] ...00231688... sent, size 988035 with 631996 bytes on the wire
[2016-08-31 13:18:10.814+00] ...00231688... recv'd, size 988011 with 98578 bytes on the wire
[2016-08-31 13:18:12.868+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
... and we just got another block
August 31, 2016, 09:13:30 AM
As Oliver Twist would say:
Please sir may I have some more?
Please sir may I have some more?
August 31, 2016, 09:09:47 AM
Block by Meatwad with 58.36THs! That would be his 2nd Kano block and our 2nd of the day...again!
August 31, 2016, 09:09:30 AM
Block by josephtran2! That would be his 7th Kano block and our 2nd of the day!
.... and there it goes to orphan land.... poof!
.... this is actually a positive moment.... usually we will have luck swings after a few orphans
#lookingatpositives #dontdrinkratpoison #waitforavalon7
Haha! it does seem that orphans punctuate our low luck stretches sometimes...and that is when we start rebounding. I just realized that I have been here on Kano.is for 997 blocks...just 3 away from 1000 blocks! How's that for a milestone! My lifetime miner performance here is at 107%, right in line with the Block Statistics page.
Of course, when I started the Pool N Avg was 1.79PHs and I only saw 7 blocks total in the first month I was here!
August 31, 2016, 08:27:00 AM
The block was after our block on ALL relays, even in china.
I'll get the details of it worked out in a while ...
Edit: So the details as follows.
The block before was network block 427668 hash 004e5228... at 13:13 UTC
Our block 427668 hash ...00231688... came first on all the relays
Bitfury 427668 hash ...00213d62... came in after
So as usual for an orphan race, the winner is decided by the next block.
Bitfury confirmed their own block, so they won it by luck.
Unfortunately impossible to get around that, we sent out our block, as usual, as fast as possible to all nodes and all over the world, but since they sent out their block slower than us, the only way we could expect to lose would be them confirming their own block ... which is what happened.
A list of relay timestamps:
Beijing: they were 20/22 seconds after us:
[2016-08-31 13:18:10.687+00] ...00231688... sent, size 988035 with 631996 bytes on the wire
[2016-08-31 13:18:12.038+00] ...00231688... recv'd, size 988011 with 98578 bytes on the wire
[2016-08-31 13:18:32.955+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
HongKong: they were 14/15 seconds after us:
[2016-08-31 13:18:10.466+00] ...00231688... sent, size 988035 with 629157 bytes on the wire
[2016-08-31 13:18:11.989+00] ...00231688... recv'd, size 988011 with 107615 bytes on the wire
[2016-08-31 13:18:25.206+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
Europe: they were 0.8 seconds after us:
[2016-08-31 13:18:10.787+00] ...00231688... recv'd, size 988011 with 129878 bytes on the wire
[2016-08-31 13:18:11.559+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
Japan: they were 2.6/2.7 seconds after us:
[2016-08-31 13:18:10.729+00] ...00231688... sent, size 988035 with 631996 bytes on the wire
[2016-08-31 13:18:10.840+00] ...00231688... recv'd, size 988011 with 107615 bytes on the wire
[2016-08-31 13:18:13.405+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
US East: they were 0.9 seconds after us
[2016-08-31 13:18:10.150+00] ...00231688... sent, size 988035 with 631996 bytes on the wire
[2016-08-31 13:18:11.043+00] ...00231688... recv'd, size 988011 with 107159 bytes on the wire
[2016-08-31 13:18:13.164+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
US West: they were 2/1.7 seconds after us
[2016-08-31 13:18:10.158+00] ...00231688... sent, size 988035 with 631996 bytes on the wire
[2016-08-31 13:18:10.814+00] ...00231688... recv'd, size 988011 with 98578 bytes on the wire
[2016-08-31 13:18:12.868+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
... and we just got another block
I'll get the details of it worked out in a while ...
Edit: So the details as follows.
The block before was network block 427668 hash 004e5228... at 13:13 UTC
Our block 427668 hash ...00231688... came first on all the relays
Bitfury 427668 hash ...00213d62... came in after
So as usual for an orphan race, the winner is decided by the next block.
Bitfury confirmed their own block, so they won it by luck.
Unfortunately impossible to get around that, we sent out our block, as usual, as fast as possible to all nodes and all over the world, but since they sent out their block slower than us, the only way we could expect to lose would be them confirming their own block ... which is what happened.
A list of relay timestamps:
Beijing: they were 20/22 seconds after us:
[2016-08-31 13:18:10.687+00] ...00231688... sent, size 988035 with 631996 bytes on the wire
[2016-08-31 13:18:12.038+00] ...00231688... recv'd, size 988011 with 98578 bytes on the wire
[2016-08-31 13:18:32.955+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
HongKong: they were 14/15 seconds after us:
[2016-08-31 13:18:10.466+00] ...00231688... sent, size 988035 with 629157 bytes on the wire
[2016-08-31 13:18:11.989+00] ...00231688... recv'd, size 988011 with 107615 bytes on the wire
[2016-08-31 13:18:25.206+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
Europe: they were 0.8 seconds after us:
[2016-08-31 13:18:10.787+00] ...00231688... recv'd, size 988011 with 129878 bytes on the wire
[2016-08-31 13:18:11.559+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
Japan: they were 2.6/2.7 seconds after us:
[2016-08-31 13:18:10.729+00] ...00231688... sent, size 988035 with 631996 bytes on the wire
[2016-08-31 13:18:10.840+00] ...00231688... recv'd, size 988011 with 107615 bytes on the wire
[2016-08-31 13:18:13.405+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
US East: they were 0.9 seconds after us
[2016-08-31 13:18:10.150+00] ...00231688... sent, size 988035 with 631996 bytes on the wire
[2016-08-31 13:18:11.043+00] ...00231688... recv'd, size 988011 with 107159 bytes on the wire
[2016-08-31 13:18:13.164+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
US West: they were 2/1.7 seconds after us
[2016-08-31 13:18:10.158+00] ...00231688... sent, size 988035 with 631996 bytes on the wire
[2016-08-31 13:18:10.814+00] ...00231688... recv'd, size 988011 with 98578 bytes on the wire
[2016-08-31 13:18:12.868+00] ...00213d62... recv'd, size 998200 with 972026 bytes on the wire
... and we just got another block
August 31, 2016, 08:25:03 AM
Block by josephtran2! That would be his 7th Kano block and our 2nd of the day!
.... and there it goes to orphan land.... poof!
.... this is actually a positive moment.... usually we will have luck swings after a few orphans
#lookingatpositives #dontdrinkratpoison #waitforavalon7
August 31, 2016, 08:18:42 AM
Block by josephtran2! That would be his 7th Kano block and our 2nd of the day!
August 31, 2016, 08:01:43 AM
Hi all,
Welcome, i have a similar story. I started off with Slushpool and Antpool because of the pretty GUI along with the high pool hashrate. Kano has been a great experience so far, there will be more time between blocks but in the end its all worth it.
Thanks man
Jump to: