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

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!

I was off the mining some times, I would like to ask you what happened that luck for last 250blocks is under 100%?

Quoted here so anyone looking for the info will see it here on this page:

As Oliver Twist would say:

Please sir may I have some more?

 

Block by Meatwad with 58.36THs!  That would be his 2nd Kano block and our 2nd of the day...again!  

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! 

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

.... 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

Block by josephtran2!  That would be his 7th Kano block and our 2nd of the day! 

Thanks man

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. 

Had another disconnect for about 10PH of miners again at around 09:05 UTC for almost 5 minutes.
All OK again.
Unfortunately (fortunately?), again, it's not at any of the servers, but upstream from them, so it's: wait for it to be resolved - which is has already.

Hi all,

I'm new - ex-antpool, ex-slush 

I have been hearing only good things about this pool, so I have been pointing to CKpool for almost 2 weeks now. Hope I see these lucky runs my mates have been telling me about soon.

Yea, hit me block hit me 

It's not just your miners, as I mentioned it's (now) over 1/4 of the pool i.e. about 10PH missing.
(and I see the network disconnects going on also)

Edit: OK most miners have reconnected now, though that happened not long ago and then we lost a lot again.

Just a minor point ... if anyone is mining in Iceland or northern europe, they should have nl.kano.is as their first pool, not the main pool.

Edit2: OK everyone seems to have stayed connected now, looks like the upstream problem is resolved.

Kano. Take a look at what sets the automatics difficulty for miners I think that may be the cause.
As half my workers have dropped of because of difficulty shooting to very high

Having a lot of network drop-outs to nodes and to the pool.
About 1/4 of miners have disconnected.
Looking into the cause ...

Edit: Problem is showing as upstream of the main data centre and getting worse, now below 30PH ...

I'd be happy to paint my truck green if you think that will make a difference

I owned a green Chevy Malibu a 1976 if I recall.

Don't see a lot of green cars any more.

Seeing Grumpy sleeping peacefully..... makes me sleepy...

Seems we lost a few more big irons.... now 41PH at pool...

Hope we can pass this difficult times and get more to come mine at Kano...