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

Yep another orphan

I've updated the web info.
Looks like I also need to work on the orphan detection code, it does a pretty simple check that seems to not spot it well.
I really never expected to get orphans very often, so it wasn't something I cared too much about, but I guess I should make a few changes there and make it automatically detect them better.

Since now we get around 100 blocks a month, we can of course expect to get more orphans.
The last orphan was 96 blocks ago, so another one now is not really statistically unexpected.

The run down of what happened:

UTC
2016-05-04 15:29:16.334 - eu relay sent BTCC block to the DE node ...0000234618ae...
2016-05-04 15:29:16.341 - we got the block from the miner ...00003e16d314...
2016-05-04 15:29:16.564 - our main bitcoind accepted our block
2016-05-04 15:29:16.647 - us-east relay got our block
2016-05-04 15:29:16.653 - us-west relay got our block
2016-05-04 15:29:17.271 - us-east relay sent BTCC block to us
2016-05-04 15:29:17.281 - us-west relay sent our block back to us
2016-05-04 15:29:17.715 - us-west relay sent BTCC block to us
2016-05-04 15:29:17.854 - eu relay sent our block to the DE node
2016-05-04 15:29:18.136 - us-east relay sent our block back to us

Really only the first 2 lines are needed to explain it all though.
So unfortunately for our block, there was really no 'expectation' to win since our block was actually 7milliseconds after one of our nodes first knew about the BTCC block
A double block would of course made us win, but in this case, while obviously all of 'GFW' was already working on BTCC's block, already some outside GFW would have been working on the BTCC block also.

The next block was by f2pool, so of course, due to the BTCC block actually being just before our block, that meant they confirmed the BTCC block.

Sounds like quite the adventure!  How bad does the dip in your shift graph look?

Wow...on another note...haven't had line power (until now...about 21:55 UTC) for 18 hours. The main breakers on the building kept tripping...and, of course, the first place they go to is mine    However...having done my due diligence, I proved to them that I run no more that 70% of rated capacity on any of the breakers in my panel. Wasn't me.

What it WAS is they discovered that the common water heater for my building (four units), while gas, is solar assisted...and they had the control circuit and circulating pump wired directly into the GFI circuit for my bathroom...so I could be running 70% total load, but not know that there was a 600W circulating pump on the other side of one of my walls, on my feed, and when the pump kicked in the startup draw (which can reach 1200W) blew the main. Wunnerful.

The nice part is that I no longer have to be stealth. They're OK with the mine. The onsite mgr and the master electrician checked out my equipment rack and power distribution, and I got compliments on planning and neatness. It actually showed them an issue with the property they didn't know they had, but would likely have found out more about it the hard way, as other distribution boards blew.

The bad part is I'm going to be limited to (it appears) four S7s (the three I'm running and another) and perhaps a couple of S3s. Theoretically I was going to 5 S7s and four S3s. Not now, 'cuz I've lost two likely circuits due to poor wiring scheme, but I'm blessed to have what I have. It couldn't be better.

Mine on. Baby needs new shoes...and I need another .15+ btc for the last S7.
 

The day after the last orphan we had a big block party. Maybe that will happen again.

How stupid, Blockchain has the orphaned block flagged as a double spend, You'd think they would have the software written to recognize the difference. Oh Well, maybe it's time for another payout addy anyhow.......

So true. Not sure I'd even consider renting hash for another pool, honestly.

I always make sure to leave emotion and impulsive decisions out of it. If you rely on the fact that Kano.is has performed above average from day one and you stay consistent in what you are doing. Profit will come. 

Thanks! It's definitely risky, I knew that going in. Just luck swinging the other way for now (for me) - I did well last time, about a month or so ago. The time even before that I did a much longer stint, closer to a month and it also worked out with a small profit.

This time, the 471% followed closely by the 411% and then 295% block right after put me in a hole. It's made these past few reddish blocks bite a little harder than they normally would.

I do rent from time to time. Renting certainly is a tough game with slim margins. Good luck to you.

Ugh... Starting to feel like I might need to give up on these rentals then. That block was a little mini-savior. Losing way too much on them at this point...

This is the 3rd time that I can remember this happening. Does anyone know why they get it every time?

Well that's no good.

BOOOOOOO!  Look at how fat and juicy that orphaned block is, damn! 

Yep, same here. I think Kano needs to manually update the site to show the orphan

I don't know why this hadn't occurred to me, but I just added it to my full node as well.

I'm not sure why the pool is still showing confirms, but everywhere else I look shows we lost this one.

Looks like the great firewall and chinese mining got us again

... it has 3 confirms, so we are likely winner?

Not so fast, block shows BTCC got it