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

[Sierra8561]

Regardless of pool hash rate, it all works out the same anyway. We end up pocketing the same amount of BTC in the end.

[firetreeactual]

FYI...discovered one of my A6s (the other is more hardy, it seems) doesn't like heat...even if the RPi sez the temps are just fine. It will show a normal hash rate on the LuCI trunk, but will not deliver that out for some reason (AUC issue?). I had to reconfigure my "wind tunnel" that worked for S7s, in order to get the PSUs physically out of the same airflow (the HP 1KW bricks generate as much heat as the A6s). I was losing almost 2TH 'cuz of it...gave it a couple of hours on the new config, and now back to something like normal.

 

[wmabern]

Another ugly, red block. Joy, joy. 

[cybermods]

Somebody will crack it soon enough 

Im just passing the time rebuilding and re-imaging my old HP Proliant DL380 Server.

[wmabern]

Somebody will crack it soon enough  

Im just passing the time rebuilding and re-imaging my old HP Proliant DL380 Server.

"Soon enough" is NEVER soon enough for me when the blocks go over 24-hours. LOL
But I know there's nothing I can do about it other than sit back, relax, and let it happen whenever it gets damn good and ready.

EDIT: And I know Kano says you shouldn't measure blocks by time. We're just lacking some of the horsepower we have had in the past. Not to mention the difficulty increase. And variance.
So, it is what it is.  
Or is it?? 

[CryptoBuddha]

So, it is what it is.  
Or is it?? 

One more step and you'll become a Buddhist 

[wmabern]

So, it is what it is.  
Or is it??  

One more step and you'll become a Buddhist  

Made it smaller!

[firetreeactual]

Here ya go. I used Imgur's utility. It's easier than it used to be.

[wmabern]

Here ya go. I used Imgur's utility. It's easier than it used to be.

Ahhh, I figured out how to do it in the forum! After the opening img tag, add the size, width and height like so "[i mg width=100 height=100]", then the image link, then the closing tag. "[/img]"

[citronick]

[hurricandave]

[firetreeactual]

Ahhh, I figured out how to do it in the forum! After the opening img tag, add the size, width and height like so "[i mg width=100 height=100]", then the image link, then the closing tag. "[/img]"

Geez...that's too easy.

And in keeping with the animals sighting in...

[firetreeactual]

Methinks Carlos Hathcock would agree with that as well...

[cybermods]

Block 

[VRobb]

tich13 punching out 2 of the last 3 blocks!   Now that's totally the chit!! 

[fusion0389]

I wouldn't mind a quick series of 10 (5%) blocks to make up for the crappy luck.

[usukan]

I wouldn't mind a quick series of 10 (5%) blocks to make up for the crappy luck.

THIS - look up above

[kano]

I wouldn't mind a quick series of 10 (5%) blocks to make up for the crappy luck.

THIS - look up above

Yeah, but the problem is that even if we have almost always jumped back with 'reversing' good luck after bad, that's actually not statistically expected.
The statistical expectation is always 100%
What that means is we expect to always converge back to 100%
Good luck doesn't mean we expect bad luck to follow, nor the reverse, bad luck doesn't expect good luck to follow.
Statistically, we always expect average luck to follow, here and every other pool.

Of course what does follow is random ... but that's a completely different thing ... called hindsight

Edit: but yes I still spend the same amount of effort, each time I'm processing payouts, checking for problems with miners ...

Edit2: and luck being luck ... oh well, 2 close ones in the last 16 hours (UTC times)

Code:

[2016-10-02 22:18:10.811+00] Share (432572) ok Diff 95.2% (229666148353/241227200230.0) cl4ud1u Pool 780678214289.0 781G 323.63%
[2016-10-03 13:12:31.985+00] Share (432658) ok Diff 98.6% (237952909840/241227200230.0) citronick Pool 312483746967.0 312G 129.54%

Edit3: I've added to my todo list a page to show share stats in the last 24hrs and maybe longer depending on how much data it takes to keep a week's worth of high diff shares e.g. something like 10%, 25%, 50%, 75%, 90%, 100%+ (=blocks)
and also to add statistics about the numbers expected per diff change - the most relevant being how many blocks we expected per diff change (and up to now) vs how many found.
The changes I'm leading into at the moment relating to having distributed ckdb's, requires a change that will easily lead to having these numbers available - whereas to show them at the moment would require more ram storage (of the data that is already there, just not summarised)

[clgrissom3]

Block by victor889 with 23TH/s!  Welcome to the Acclaim Board with your 1st Kano block!  This is our 2nd block of the day! 

[firetreeactual]

Someone just hit a block on the solo pool...woo-hoo!

EDIT: It occurred to me that we may not hear anything from Canaan until after the China holiday...