I for one predict 12 more. 
Don't go jinx'n it now with your predictions..
Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 890. (Read 5352420 times)
July 26, 2017, 06:59:19 AM
Don't go jinx'n it now with your predictions..
July 26, 2017, 06:35:01 AM
Block! by mikese 
That gets us to 54 for the month 52.21 is 100% luck.
So 63 blocks for the month will do the trick.
That means only 9 more needed.
I for one predict 12 more.
or 66 for July
July 26, 2017, 01:49:28 AM
Block! by mikese
July 26, 2017, 01:21:52 AM
Thanks again Kano-san!
Probably more detail than you want to know but ... Web<->CKDB is handled via 2 socat connections through a secure tunnel.
The tunnel avoids constant logging in to the main server for every request, the socat's make a new connection for each message, through the tunnel and at the CKDB end translate the socket into a linux socket as per what CKDB wants.
When the tunnel closes (once in a blue moon) the replies to all the web messages that CKDB is processing, will not be wanted, since the web server will have given up on them and replied with the red "Database is reloading, mining is all OK" message.
This leads to a (possibly large) number of unwanted messages queued in CKDB and trying to be sent back to the web server.
I'll need to get CKDB to not report every one of them, but rather a summary a minute later, since it's OK that they fail, since they are no longer wanted.
However, on the console it looks like CKDB has gone into network cardiac arrest due to so many messages not replied, and I restarted it to clear it
As I mentioned, it's on the TODO list, but since it's ever so rare (happened probably only twice before) it's not urgent.
That's exactly the kinda stuff I like to hear about! While I'm not familiar with Socat, it sounds like CKDB just got into a strange state due to not being able to get replies from the web server, and couldn't recover.
July 26, 2017, 01:11:38 AM
Thanks again Kano-san!
Probably more detail than you want to know but ... Web<->CKDB is handled via 2 socat connections through a secure tunnel.
The tunnel avoids constant logging in to the main server for every request, the socat's make a new connection for each message, through the tunnel and at the CKDB end translate the socket into a linux socket as per what CKDB wants.
When the tunnel closes (once in a blue moon) the replies to all the web messages that CKDB is processing, will not be wanted, since the web server will have given up on them and replied with the red "Database is reloading, mining is all OK" message.
This leads to a (possibly large) number of unwanted messages queued in CKDB and trying to be sent back to the web server.
I'll need to get CKDB to not report every one of them, but rather a summary a minute later, since it's OK that they fail, since they are no longer wanted.
However, on the console it looks like CKDB has gone into network cardiac arrest due to so many messages not replied, and I restarted it to clear it
As I mentioned, it's on the TODO list, but since it's ever so rare (happened probably only twice before) it's not urgent.
July 26, 2017, 12:03:42 AM
Nice green color! I like it, keep them coming guys!
Mine on
Mine on
July 25, 2017, 11:46:50 PM
Thanks again Kano-san!
July 25, 2017, 11:43:40 PM
Had a network glitch in CKDB - so I had to restart it.
Mining is completely unaffected.
Yet again, nothing to do with the recent changes - added to the TODO list to sort out why it happened and fix it
Restartalmost complete.
Mining is completely unaffected.
Yet again, nothing to do with the recent changes - added to the TODO list to sort out why it happened and fix it
Restart
July 25, 2017, 11:40:40 PM
July 25, 2017, 11:30:21 PM
Block! by bobsyouruncle
... and 3 payouts (including the missing one)
... and 3 payouts (including the missing one)
sorry but bob- is- my- cousin not my uncle
July 25, 2017, 11:22:17 PM
July 25, 2017, 11:12:34 PM
Block! by bobsyouruncle
... and 3 payouts (including the missing one)
... and 3 payouts (including the missing one)
July 25, 2017, 08:55:42 PM
looks like the payout from 477443 was sent in that block, but not the one from 477428. or did i miss something?
Same question - did I/we miss/skip the payment for block 447428??
I've put it back in just now and it will be in the next block.
Well ... always fun to note that any change in the work we mine of course (completely randomly) affects the blocks we find.
Could have found more, or less or the same, but at least in this case we found the next block faster than expected
Thanks for staying on top of this and keeping us in the loop, as always!
July 25, 2017, 07:53:11 PM
looks like the payout from 477443 was sent in that block, but not the one from 477428. or did i miss something?
Same question - did I/we miss/skip the payment for block 447428??
I've put it back in just now and it will be in the next block.
Well ... always fun to note that any change in the work we mine of course (completely randomly) affects the blocks we find.
Could have found more, or less or the same, but at least in this case we found the next block faster than expected
July 25, 2017, 07:22:20 PM
It shows on BTC.com as unknown:
477,563 unknown 1,948 988,095 0.00062121 12.5 + 0.61381006 BTC 2017-07-25 14:58:22
Don't know what that means
...
I submitted a pull request to them to fix the "unknown" a few days ago ... after being told by Sarah at Bitmain that I had to do that ... though they ignored my request to fix the icon also ... since it should be '🐈'477,563 unknown 1,948 988,095 0.00062121 12.5 + 0.61381006 BTC 2017-07-25 14:58:22
Don't know what that means
...
https://github.com/btccom/Blockchain-Known-Pools/pull/10
Might be days, weeks or months until they bother
July 25, 2017, 07:18:40 PM
I currently only have 2 R4's for 17.2 TH. I will be adding my 1st S9 later today (on IPS truck for delivery) to increase my TH to 30.7.
Then in a few more weeks, I will be adding another S9 for a total of around 44.2 TH.
Love this pool !
Mine on!!
Then in a few more weeks, I will be adding another S9 for a total of around 44.2 TH.
Love this pool !
Mine on!!
Its a big day for blocks... and adding more pool power! Just fired up my first S9 as well tonight. woot!
Welcome to the pool MAERK!
July 25, 2017, 07:02:10 PM
I currently only have 2 R4's for 17.2 TH. I will be adding my 1st S9 later today (on IPS truck for delivery) to increase my TH to 30.7.
Then in a few more weeks, I will be adding another S9 for a total of around 44.2 TH.
Love this pool !
Mine on!!
Then in a few more weeks, I will be adding another S9 for a total of around 44.2 TH.
Love this pool !
Mine on!!
Its a big day for blocks... and adding more pool power! Just fired up my first S9 as well tonight. woot!
July 25, 2017, 06:17:19 PM
It's coming.
July 25, 2017, 06:12:46 PM
looks like the payout from 477443 was sent in that block, but not the one from 477428. or did i miss something?
Same question - did I/we miss/skip the payment for block 447428??
July 25, 2017, 06:04:54 PM
Appreciate the status update Kano! You're a big reason why I love mining here.
Jump to: