Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 1934. (Read 5352119 times)
December 17, 2015, 11:57:06 PM
Brought a friend over to the pool. And hopefully another very soon
December 17, 2015, 11:19:32 PM
If for some reason your miners failover to backup pool after pool block found, try stratum thru stratum pasthru mode -P (not -p)
That is what I use and mine have never failed over to backup pool
https://bitcointalksearch.org/topic/m.8907589
This does not make any sense whatsoever. There is nothing in the cgminer, ckpool or ckproxy code that would make you fail over after finding a block on the upstream pool. That is what I use and mine have never failed over to backup pool
https://bitcointalksearch.org/topic/m.8907589
December 17, 2015, 10:52:12 PM
If for some reason your miners failover to backup pool after pool block found, try stratum thru stratum pasthru mode -P (not -p)
That is what I use and mine have never failed over to backup pool
https://bitcointalksearch.org/topic/m.8907589
That is what I use and mine have never failed over to backup pool
https://bitcointalksearch.org/topic/m.8907589
December 17, 2015, 09:39:49 PM
Use "ckpool -P" and you dont drop to failover after pool finds a block.
Explain?
December 17, 2015, 09:13:04 PM
Use "ckpool -P" and you dont drop to failover after pool finds a block.
December 17, 2015, 06:34:13 PM
Phew! Now lets get a few bright green ones 
tSo we get a valid block and almost 1ph leave the pool? Why would one pool hop here with a 5N? Hopping works well at slush, but why here. Don't get it.
Stay after a block and keep hash high to get the next block faster.
That's the strange thing about it.
Often in the past I've seen the hash rate drop after we find a block.
I've no idea why miners leave then.
My hashrate shows lower right now even though all of my miners indicate normal rates. Slowly creeping back up to normal poolside though.
Edit: looks like my miners switched to my backup pool. Maybe that is why 1PH left after the block change, their miners switched to backup pools.
I think this is because of the ckpool restart Kano just performed. I received an alert as well from Zach's website for low hast rate, but my miners show their normal rate.
Since most of these alerts are driven by API provided by the site, when there is a restart it tends to kick out a few false alerts until the site catches back up.......please correct me if I'm wrong
Shortly after we get a block, the hash rate drops.
Yep, helipotte's observations are separate and indeed to do with the ckpool restart.
Some % of miners will failover on a restart, a larger % will simply see a reconnect in cgminer ... if they happen to look at cgminer
ckpool also takes a while to average out the hash rate caused by failovers that then fail back very soon after.
December 17, 2015, 06:19:25 PM
kano is the proxy restricted to only Asic Tubes
...
However, as I mentioned before, I will be doing a 'ckpool' restart shortly.
That will happen in 5 minutes.
Done.However, as I mentioned before, I will be doing a 'ckpool' restart shortly.
That will happen in 5 minutes.
Tubes aren't getting work since exactly that time where you said "Done".
I didn't check the nonce proxy after the restart.
It indeed gave up and stopped handing out work and didn't reconnect to the main ckpool.
I've reset it.
I'll make sure that doesn't happen in the future ... i.e. check the proxy and restart it also since it failed to reconnect.
December 17, 2015, 06:12:13 PM
Phew! Now lets get a few bright green ones
tSo we get a valid block and almost 1ph leave the pool? Why would one pool hop here with a 5N? Hopping works well at slush, but why here. Don't get it.
Stay after a block and keep hash high to get the next block faster.
That's the strange thing about it.
Often in the past I've seen the hash rate drop after we find a block.
I've no idea why miners leave then.
My hashrate shows lower right now even though all of my miners indicate normal rates. Slowly creeping back up to normal poolside though.
Edit: looks like my miners switched to my backup pool. Maybe that is why 1PH left after the block change, their miners switched to backup pools.
I think this is because of the ckpool restart Kano just performed. I received an alert as well from Zach's website for low hast rate, but my miners show their normal rate.
Since most of these alerts are driven by API provided by the site, when there is a restart it tends to kick out a few false alerts until the site catches back up.......please correct me if I'm wrong
December 17, 2015, 06:08:20 PM
kano is the proxy restricted to only Asic Tubes
...
However, as I mentioned before, I will be doing a 'ckpool' restart shortly.
That will happen in 5 minutes.
Done.However, as I mentioned before, I will be doing a 'ckpool' restart shortly.
That will happen in 5 minutes.
Tubes aren't getting work since exactly that time where you said "Done".
December 17, 2015, 05:58:54 PM
Phew! Now lets get a few bright green ones
tSo we get a valid block and almost 1ph leave the pool? Why would one pool hop here with a 5N? Hopping works well at slush, but why here. Don't get it.
Stay after a block and keep hash high to get the next block faster.
That's the strange thing about it.
Often in the past I've seen the hash rate drop after we find a block.
I've no idea why miners leave then.
My hashrate shows lower right now even though all of my miners indicate normal rates. Slowly creeping back up to normal poolside though.
Edit: looks like my miners switched to my backup pool. Maybe that is why 1PH left after the block change, their miners switched to backup pools.
December 17, 2015, 05:57:49 PM
kano is the proxy restricted to only Asic Tubes
December 17, 2015, 05:48:28 PM
...
However, as I mentioned before, I will be doing a 'ckpool' restart shortly.
That will happen in 5 minutes.
Done. However, as I mentioned before, I will be doing a 'ckpool' restart shortly.
That will happen in 5 minutes.
December 17, 2015, 05:47:50 PM
Phew! Now lets get a few bright green ones
tSo we get a valid block and almost 1ph leave the pool? Why would one pool hop here with a 5N? Hopping works well at slush, but why here. Don't get it.
Stay after a block and keep hash high to get the next block faster.
That's the strange thing about it.
Often in the past I've seen the hash rate drop after we find a block.
I've no idea why miners leave then.
Maybe they are hoping that the next block will be solved quickly and they'll get double pay from that block and the next pool's block they are mining at already.
Or.. Just a rental of hash that ended / is suspended until they get payment from the previous blocks.
December 17, 2015, 05:37:30 PM
this shift did not receive a pay that can be seines that something that will correct it self when you do the restart 
edit:5ptq3 charlotte
Yeah that relates to my comment a few days back about how those numbers are calculated only for display, they aren't part of the process to determine your payout.edit:5ptq3 charlotte
However I put a change in the other day to allow me to correct the display (if it happens) when ckdb is running.
... but after just trying it now, it didn't fix it on the live data
so I'll have to sort that out.Yeah the next time I do a ckdb restart will correct the display.
However, as I mentioned before, I will be doing a 'ckpool' restart shortly.
That will happen in 5 minutes.
December 17, 2015, 05:22:13 PM
Phew! Now lets get a few bright green ones
tSo we get a valid block and almost 1ph leave the pool? Why would one pool hop here with a 5N? Hopping works well at slush, but why here. Don't get it.
Stay after a block and keep hash high to get the next block faster.
That's the strange thing about it.
Often in the past I've seen the hash rate drop after we find a block.
I've no idea why miners leave then.
December 17, 2015, 05:16:30 PM
Phew! Now lets get a few bright green ones
tSo we get a valid block and almost 1ph leave the pool? Why would one pool hop here with a 5N? Hopping works well at slush, but why here. Don't get it.
Stay after a block and keep hash high to get the next block faster.
December 17, 2015, 05:13:44 PM
this shift did not receive a pay that can be seines that something that will correct it self when you do the restart
edit:5ptq3 charlotte
edit:5ptq3 charlotte
December 17, 2015, 05:08:13 PM
Yeah that's actually the point of being able to create a new API code for your account.
The old API code is no longer valid if you create a new one, so if you decide to give it out to someone, you can effectively revoke it.
Well, there is one time limit, you have to wait a day after you create it to create a new one, i.e. effectively revoke it.
So if you create a new, then wait a day before giving it to anyone, you can immediately revoke it if there's some issue.
However, it only gives read access to the API data for you and no other access to your account, so it's pretty safe.
The old API code is no longer valid if you create a new one, so if you decide to give it out to someone, you can effectively revoke it.
Well, there is one time limit, you have to wait a day after you create it to create a new one, i.e. effectively revoke it.
So if you create a new, then wait a day before giving it to anyone, you can immediately revoke it if there's some issue.
However, it only gives read access to the API data for you and no other access to your account, so it's pretty safe.
Thanks for the info. Much appreciated.
December 17, 2015, 05:00:13 PM
Hi Zach,
Thanks for the work you've done with the pool hash rate graph and our own hash rate graph.
Also thanks for the low hash notification and found block notification.
By the way, everyone, if you haven't tried out http://ckpoolmonitor.zachmonroe.com you need to. No information you give can harm you. Your email, API [Can generate a new one anytime] and pool username. That's it.
Yeah that's actually the point of being able to create a new API code for your account.Thanks for the work you've done with the pool hash rate graph and our own hash rate graph.
Also thanks for the low hash notification and found block notification.
By the way, everyone, if you haven't tried out http://ckpoolmonitor.zachmonroe.com you need to. No information you give can harm you. Your email, API [Can generate a new one anytime] and pool username. That's it.
The old API code is no longer valid if you create a new one, so if you decide to give it out to someone, you can effectively revoke it.
Well, there is one time limit, you have to wait a day after you create it to create a new one, i.e. effectively revoke it.
So if you create a new, then wait a day before giving it to anyone, you can immediately revoke it if there's some issue.
However, it only gives read access to the API data for you and no other access to your account, so it's pretty safe.
December 17, 2015, 04:42:08 PM
Hi Zach,
Thanks for the work you've done with the pool hash rate graph and our own hash rate graph.
Also thanks for the low hash notification and found block notification.
By the way, everyone, if you haven't tried out http://ckpoolmonitor.zachmonroe.com you need to. No information you give can harm you. Your email, API [Can generate a new one anytime] and pool username. That's it.
Thanks for the work you've done with the pool hash rate graph and our own hash rate graph.
Also thanks for the low hash notification and found block notification.
By the way, everyone, if you haven't tried out http://ckpoolmonitor.zachmonroe.com you need to. No information you give can harm you. Your email, API [Can generate a new one anytime] and pool username. That's it.
Jump to: