Block! by cobramining 
A7v2
A7v2
Wohoo! 2nd of the day!
Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 1054. (Read 5352445 times)
February 24, 2017, 10:49:03 AM
February 24, 2017, 10:36:25 AM
Block by cobrafarming, a big block again!
Our Hashrate is increasing. It is great!
Our Hashrate is increasing. It is great!
February 24, 2017, 10:26:11 AM
Another juicy, fat block brought to you by King cobramining, premium block cracker!
February 24, 2017, 10:16:20 AM
Block! by cobramining
A7v2
A7v2
February 24, 2017, 10:08:38 AM
Wow, our last blocks have been 14+ BTC. Love it! 
Also looks like our pool hash rate has been climbing steadily lately, I'm guessing our latest lucky streak gets the credit.
Also looks like our pool hash rate has been climbing steadily lately, I'm guessing our latest lucky streak gets the credit.
February 24, 2017, 09:01:49 AM
Quote
Hi Kano,
Would my IP have gotten blocked sometime overnight? All of my miners were hashing away when I went to bed and this morning all are showing 0 hash. I have rebooted them all and I get the message "Socket connect failed: Connection refused".
I'll PM you my IP if that might be the case. Also, why would they be blocked? Thanks for a quick response so I can make pool changes if need be before I go to work.
Thank you.
Edit: Username: whirledps
Would my IP have gotten blocked sometime overnight? All of my miners were hashing away when I went to bed and this morning all are showing 0 hash. I have rebooted them all and I get the message "Socket connect failed: Connection refused".
I'll PM you my IP if that might be the case. Also, why would they be blocked? Thanks for a quick response so I can make pool changes if need be before I go to work.
Thank you.
Edit: Username: whirledps
I have seen a few posts over at bitmains forum with people haveing problems with there antminers giving them a "Socket connect failed: Connection refused" error.. Tho I Have not seen many solutions other then people haveing to send there miners back to bitmain for chips on the hash boards going bad and it seems to be a problem with many of the later ones that have auto turn frequency. Such as the newer batchs of s9s and R4s and some sort of firmware issue as being the real culprit. Being that some have reported being able to find old firmware that bitmain dont put out any more to get there miners up and working again.
I have had many issues with my s9's. If you get a ton of rejects upon restarting try putting just one pool no backups. I don't know why that works. It seems it has issues with multiple pools. Doesn't do it with other pools. But seems to on Kano and ck solo.
BR
February 24, 2017, 08:48:55 AM
Quote
Hi Kano,
Would my IP have gotten blocked sometime overnight? All of my miners were hashing away when I went to bed and this morning all are showing 0 hash. I have rebooted them all and I get the message "Socket connect failed: Connection refused".
I'll PM you my IP if that might be the case. Also, why would they be blocked? Thanks for a quick response so I can make pool changes if need be before I go to work.
Thank you.
Edit: Username: whirledps
Would my IP have gotten blocked sometime overnight? All of my miners were hashing away when I went to bed and this morning all are showing 0 hash. I have rebooted them all and I get the message "Socket connect failed: Connection refused".
I'll PM you my IP if that might be the case. Also, why would they be blocked? Thanks for a quick response so I can make pool changes if need be before I go to work.
Thank you.
Edit: Username: whirledps
I have seen a few posts over at bitmains forum with people haveing problems with there antminers giving them a "Socket connect failed: Connection refused" error.. Tho I Have not seen many solutions other then people haveing to send there miners back to bitmain for chips on the hash boards going bad and it seems to be a problem with many of the later ones that have auto turn frequency. Such as the newer batchs of s9s and R4s and some sort of firmware issue as being the real culprit. Being that some have reported being able to find old firmware that bitmain dont put out any more to get there miners up and working again.
February 24, 2017, 07:51:49 AM
Here is a growing list of sites affected
https://github.com/pirate/sites-using-cloudflare/blob/master/README.md
BR
Half the planet uses cloudflare, no need to try making a list of them https://github.com/pirate/sites-using-cloudflare/blob/master/README.md
BR
Yea they are up to 22mb for the full list. They did however list some of the btc related sites towards the bottom to save some time
BR
February 24, 2017, 07:48:17 AM
Here is a growing list of sites affected
https://github.com/pirate/sites-using-cloudflare/blob/master/README.md
BR
Half the planet uses cloudflare, no need to try making a list of them https://github.com/pirate/sites-using-cloudflare/blob/master/README.md
BR
February 24, 2017, 07:43:38 AM
Here is a growing list of sites affected
https://github.com/pirate/sites-using-cloudflare/blob/master/README.md
BR
https://github.com/pirate/sites-using-cloudflare/blob/master/README.md
BR
February 24, 2017, 07:21:13 AM
... and related to the above, I don't use cloud flare (or any other service) for the web site or anything else on kano.is
I run everything
(so problems only exist if are were issues with the companies I use to provide servers)
I run everything
(so problems only exist if are were issues with the companies I use to provide servers)
February 24, 2017, 07:14:11 AM
FYI. For those that may have missed it. Cloud fare has been hacked. All sites using this need to reset their passwords.
BR
d57heinz
From kraken exchange
A bug was recently discovered with Cloudflare, which Kraken and many other websites use for DoS protection and other services. Due to the nature of the bug, we recommend as a precaution that you change your Kraken security credentials:
Change your password
Change your two-factor authentication (remove and re-enable it)
Clients who use API keys should generate a new set of keys
BR
d57heinz
From kraken exchange
A bug was recently discovered with Cloudflare, which Kraken and many other websites use for DoS protection and other services. Due to the nature of the bug, we recommend as a precaution that you change your Kraken security credentials:
Change your password
Change your two-factor authentication (remove and re-enable it)
Clients who use API keys should generate a new set of keys
February 24, 2017, 07:00:54 AM
Hi Kano,
Would my IP have gotten blocked sometime overnight? All of my miners were hashing away when I went to bed and this morning all are showing 0 hash. I have rebooted them all and I get the message "Socket connect failed: Connection refused".
I'll PM you my IP if that might be the case. Also, why would they be blocked? Thanks for a quick response so I can make pool changes if need be before I go to work.
Thank you.
Edit: Username: whirledps
There's no bans or blocks on your IPWould my IP have gotten blocked sometime overnight? All of my miners were hashing away when I went to bed and this morning all are showing 0 hash. I have rebooted them all and I get the message "Socket connect failed: Connection refused".
I'll PM you my IP if that might be the case. Also, why would they be blocked? Thanks for a quick response so I can make pool changes if need be before I go to work.
Thank you.
Edit: Username: whirledps
Must be a routing problem local to you I guess.
Edit: if you look at your workers page you'll see it happened about 5 hours ago.
Thank you. Working on the problem. All of the miners seem like they just stopped 5+ hours a go. I was asleep, so couldn't have done anything to screw them up then. LOL
Thus it's some problem where your miners are.
February 24, 2017, 06:49:39 AM
Hi Kano,
Would my IP have gotten blocked sometime overnight? All of my miners were hashing away when I went to bed and this morning all are showing 0 hash. I have rebooted them all and I get the message "Socket connect failed: Connection refused".
I'll PM you my IP if that might be the case. Also, why would they be blocked? Thanks for a quick response so I can make pool changes if need be before I go to work.
Thank you.
Edit: Username: whirledps
There's no bans or blocks on your IPWould my IP have gotten blocked sometime overnight? All of my miners were hashing away when I went to bed and this morning all are showing 0 hash. I have rebooted them all and I get the message "Socket connect failed: Connection refused".
I'll PM you my IP if that might be the case. Also, why would they be blocked? Thanks for a quick response so I can make pool changes if need be before I go to work.
Thank you.
Edit: Username: whirledps
Must be a routing problem local to you I guess.
Edit: if you look at your workers page you'll see it happened about 5 hours ago.
Thank you. Working on the problem. All of the miners seem like they just stopped 5+ hours a go. I was asleep, so couldn't have done anything to screw them up then. LOL
February 24, 2017, 06:34:07 AM
Hi Kano,
Would my IP have gotten blocked sometime overnight? All of my miners were hashing away when I went to bed and this morning all are showing 0 hash. I have rebooted them all and I get the message "Socket connect failed: Connection refused".
I'll PM you my IP if that might be the case. Also, why would they be blocked? Thanks for a quick response so I can make pool changes if need be before I go to work.
Thank you.
Edit: Username: whirledps
There's no bans or blocks on your IPWould my IP have gotten blocked sometime overnight? All of my miners were hashing away when I went to bed and this morning all are showing 0 hash. I have rebooted them all and I get the message "Socket connect failed: Connection refused".
I'll PM you my IP if that might be the case. Also, why would they be blocked? Thanks for a quick response so I can make pool changes if need be before I go to work.
Thank you.
Edit: Username: whirledps
Must be a routing problem local to you I guess.
Edit: if you look at your workers page you'll see it happened about 5 hours ago.
February 24, 2017, 06:07:03 AM
Hi Kano,
Would my IP have gotten blocked sometime overnight? All of my miners were hashing away when I went to bed and this morning all are showing 0 hash. I have rebooted them all and I get the message "Socket connect failed: Connection refused".
I'll PM you my IP if that might be the case. Also, why would they be blocked? Thanks for a quick response so I can make pool changes if need be before I go to work.
Thank you.
Edit: Username: whirledps
Would my IP have gotten blocked sometime overnight? All of my miners were hashing away when I went to bed and this morning all are showing 0 hash. I have rebooted them all and I get the message "Socket connect failed: Connection refused".
I'll PM you my IP if that might be the case. Also, why would they be blocked? Thanks for a quick response so I can make pool changes if need be before I go to work.
Thank you.
Edit: Username: whirledps
February 24, 2017, 05:25:54 AM
Block! by 1JQN...
Probably an S7
Edit: and 454315's payout of course.
Probably an S7
Edit: and 454315's payout of course.
February 24, 2017, 04:41:37 AM
NL just did a failover 09:26 UTC - seems that most of the miners on NL have DE as the backup, which is a good choice, so they failed over to DE, then back again to NL a few minutes later.
All OK again.
Just a point to note for anyone who may be unsure about these events that I've been reporting (for years) and what they mean:
Basically a failover means that a group of miners switched to their backup pool, then switched back again to their first choice pool.
Usually it's immediate, but sometimes can take up to 5 minutes of mining on the backup pool, your 2nd pool configured in the web miner web interface, before switching back to your first choice pool in your miner.
It's a very minor inconvenience, but if your miner is setup properly with backups, it should be no real down time for the miner.
All OK again.
Just a point to note for anyone who may be unsure about these events that I've been reporting (for years) and what they mean:
Basically a failover means that a group of miners switched to their backup pool, then switched back again to their first choice pool.
Usually it's immediate, but sometimes can take up to 5 minutes of mining on the backup pool, your 2nd pool configured in the web miner web interface, before switching back to your first choice pool in your miner.
It's a very minor inconvenience, but if your miner is setup properly with backups, it should be no real down time for the miner.
February 24, 2017, 03:57:51 AM
just a quick curiosity question. how long does it take for payments to be processed after a block is found?
As the payouts page implies, less than 100 blocks.The coinbase reward in a bitcoin block cannot be spent until 101 confirms i.e. I can't send it until 100 blocks after the block
(which of course I've already done for 454315, it's txnid is 71d174643fef28f78fcdae7ca93a0320cf6249e023dfda498cc133ad01963003)
Thus as it says on the bottom of Help->Payouts on the web site https://kano.is/index.php?k=payout
Quote
When are payments sent out?
The block 'Status' must first reach '+101 Confirms' on the Blocks page, and then is flagged as 'Matured', before the reward is distributed.
The block reward transaction is created manually before the block matures, and sent out automatically a minute after the block matures.
The payout uses a zero fee transaction, so we will confirm it with the next block we find after the transaction is sent out.
The block 'Status' must first reach '+101 Confirms' on the Blocks page, and then is flagged as 'Matured', before the reward is distributed.
The block reward transaction is created manually before the block matures, and sent out automatically a minute after the block matures.
The payout uses a zero fee transaction, so we will confirm it with the next block we find after the transaction is sent out.
February 24, 2017, 03:46:22 AM
just a quick curiosity question. how long does it take for payments to be processed after a block is found?
Jump to: