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

[firetreeactual]

Nice wakeup call here...

Maybe I'll try "pinging for bitcoin" here in a bit...see if I get any better responses from anywhere other than kano.is. I'm smack in the middle of the Pacific Ocean, so just about any continental land mass...or island, for that matter...is a long way off.

TS Darby turned out to be a fizzle for Kaua'i Island...we're quite OK with that. Dodged the proverbial bullet one more time...but that's quite OK also, as it kicks us in the `okole (Hawaiian for butt) to make sure our disaster response matrix is up to snuff.

Otherwise...belated congrats, Moe! and...

[globalgoldbits1]

Where can one get the different nodes info and addresses...? I read a post some time back that mentioned the DK "stratum+tcp://dk.kano.is:3333" and up until that time I was only aware of the addresses on the web home page so I pinged and pointed my hardware to DK.... So I'm one of the "6" using DK then I think... lol

Would like to get the other nodes addresses and perhaps ping each and see what is best from South Africa... Sounds like NL node is quite popular...? Any guidance please?

I asked the same question some pages ago and this was Kano's answer to it: https://bitcointalk.org/index.php?topic=789369.msg15619454#msg15619454

So, first of all, do some ping tests to see which node appears the fastest to you.   As of now, as I understand, you can try de(sg,jp,fr,nl).ckpool.org:3333

Okay that helped me to get some point to start... I pinged and NL indeed is top of list with DE coming in close in second best...

[globalgoldbits1]

Where can one get the different nodes info and addresses...? I read a post some time back that mentioned the DK "stratum+tcp://dk.kano.is:3333" and up until that time I was only aware of the addresses on the web home page so I pinged and pointed my hardware to DK.... So I'm one of the "6" using DK then I think... lol

Would like to get the other nodes addresses and perhaps ping each and see what is best from South Africa... Sounds like NL node is quite popular...? Any guidance please?

I asked the same question some pages ago and this was Kano's answer to it: https://bitcointalk.org/index.php?topic=789369.msg15619454#msg15619454

So, first of all, do some ping tests to see which node appears the fastest to you.   As of now, as I understand, you can try de(sg,jp,fr,nl).ckpool.org:3333

Okay that helped me to get some point to start... I pinged and NL indeed is top of list with DE coming in close in second best...

Sorry for all the questions but Im new at most of this...
Is it suppose to be nl.ckpool.org:3333 or nl.kano.is:3333 ?

[CryptoBuddha]

Okay that helped me to get some point to start... I pinged and NL indeed is top of list with DE coming in close in second best...

Then, as Kano said, if NL and DE show about the same results, use NL. And I tend to believe him)))  
And don't forget to compare NL and main node ping test results.

On my s7's I use the following failover sequence
- nl.kano.is:3333 (the fastest)
- stratum.kano.is:3333 (in case NL node gets unstable)
- de.ckpool.org:3333 (in case Kano does some restarts or updates, that's a European node for solo mining at solo.ckpool)

Sorry for all the questions but Im new at most of this...
Is it suppose to be nl.ckpool.org:3333 or nl.kano.is:3333 ?

Sorry, it was my mistake in the initial answer, I corrected myself and it should be   nl.kano.is:3333

[clgrissom3]

Okay that helped me to get some point to start... I pinged and NL indeed is top of list with DE coming in close in second best...

Then, as Kano said, if NL and DE show about the same results, use NL. And I tend to believe him)))  
And don't forget to compare NL and main node ping test results.

On my s7's I use the following failover sequence
- nl.kano.is:3333 (the fastest)
- stratum.kano.is:3333 (in case NL node gets unstable)
- de.ckpool.org:3333 (in case Kano does some restarts or updates, that's a European node for solo mining at solo.ckpool)

You can use any of the Kano ports:
stratum+tcp://nl.kano.is:3333
stratum+tcp://nl.kano.is:80
stratum+tcp://nl.kano.is:81
stratum+tcp://nl.kano.is:443
stratum+tcp://nl.kano.is:8080

And you can use any of the nodes listed in the forum title in place of the nl, IE:

Singapore
stratum+tcp://sg.kano.is:3333
stratum+tcp://sg.kano.is:80
stratum+tcp://sg.kano.is:81
stratum+tcp://sg.kano.is:443
stratum+tcp://sg.kano.is:8080

Japan
stratum+tcp://jp.kano.is:3333
stratum+tcp://jp.kano.is:80
stratum+tcp://jp.kano.is:81
stratum+tcp://jp.kano.is:443
stratum+tcp://jp.kano.is:8080

[firetreeactual]

FWIW...sorta kinda what I figgered...the primary (kano.is) is my best bet here, at around 75ms. SG runs over 200ms, JP didn't connect (I think Kano dumped that one, but my memory ain't that super anymore), and when you think about it, I'm probably closer/less hops to the main anyway. Our main Internet backbone in Hawaii is good quality, mainly due to the large military presence here, but does rely on undersea cable to the mainland for the primary.

Mine on...  

EDIT: Geez...did I say "main" enough times? More French press... 

[clgrissom3]

FWIW...sorta kinda what I figgered...the primary (kano.is) is my best bet here, at around 75ms. SG runs over 200ms, JP didn't connect (I think Kano dumped that one, but my memory ain't that super anymore), and when you think about it, I'm probably closer/less hops to the main anyway. Our main Internet backbone in Hawaii is good quality, mainly due to the large military presence here, but does rely on undersea cable to the mainland for the primary.

Mine on...  

EDIT: Geez...did I say "main" enough times? More French press... 

Haha!  That paragraph is definitely full of "main" between main, mainly, and mainland! 

[firetreeactual]

...been paying too much attention to the brokerage commercials..."investing in vests..." etc. 

[moe7865]

Nice wakeup call here...

Maybe I'll try "pinging for bitcoin" here in a bit...see if I get any better responses from anywhere other than kano.is. I'm smack in the middle of the Pacific Ocean, so just about any continental land mass...or island, for that matter...is a long way off.

TS Darby turned out to be a fizzle for Kaua'i Island...we're quite OK with that. Dodged the proverbial bullet one more time...but that's quite OK also, as it kicks us in the `okole (Hawaiian for butt) to make sure our disaster response matrix is up to snuff.

Otherwise...belated congrats, Moe! and...

Thanks
i was excited to see 2 blocks to my name so soon after each other

[yvcea]

Hello,
How can I erase a worker in order to not get the app for iPhone notification that one worker is idle?
thank you!

[clgrissom3]

Hello,
How can I erase a worker in order to not get the app for iPhone notification that one worker is idle?
thank you!

You can't...but if you wait 7 days it will drop off automatically.

[yvcea]

Hello,
How can I erase a worker in order to not get the app for iPhone notification that one worker is idle?
thank you!

You can't...but if you wait 7 days it will drop off automatically.
[/quote

Right now is the day 8. And notification is there... Lets wait!

[ComputerGenie]

Right now is the day 8. And notification is there... Lets wait!

Have you tried going to https://kano.is/index.php?k=workmgt, checking "Active workers (7 days)" and clicking "Update"? That worked for me, I had some weeks-old stragglers from a test group of LNs and that removed them straight away.

[AriesIV10]

Get ready, Bitcoin is getting ready to jump!  Save all of your coins from Kano and keep them in bitcoin; it is going up!

[yvcea]

Right now is the day 8. And notification is there... Lets wait!

Have you tried going to https://kano.is/index.php?k=workmgt, checking "Active workers (7 days)" and clicking "Update"? That worked for me, I had some weeks-old stragglers from a test group of LNs and that removed them straight away.

It worked for me too. Thank you!
BTW: I updated the API key and loaded it again in the iPhone app... then non-active worker is gone...

Thank you!

[traxor]

Get ready, Bitcoin is getting ready to jump!  Save all of your coins from Kano and keep them in bitcoin; it is going up!

I like your enthusiasm -- I'm just curious as to why you would post this.  Is it due to the problems that are happening with Eth?  Is it based on technicals?  I actually agree with your statement -- just not sure about the timeframe.  My guess would have been later in the year.  I haven't been actively trading since I cashed out at $770 -- but, I could certainly turn my focus that way again...

[kano]

Meanwhile, in the land of mining nodes ...

I'm gonna get rid of the DK node in about 10-12 hours.

No one has to do anything to their miners, since, I'll firstly, simply point DK at NL, then about 1/2 an hour or so later send anyone mining on DK a redirect to NL.
Finally, when I stop the pool node itself, anyone still left will reconnect to NL, since DK will be pointing to NL by then.

If you rent and mine to DK, then the rental may give up, since certain rental place's poxy software may not handle a redirect.
Makes you wonder what you are paying that exorbitant fee to them for ... if they cant add that original stratum command.

Right now, NL is ~580THs and DK is only 80THs, so not many people left on the DK node - about 6.
The NL node is faster and better than the DK node, and also gets work from the main Vegas node faster than the DK node, so as I actually mentioned I'd do when I setup the NL node, it's now time to get rid DK.

I'll post again when I'm doing it, but for the ~6 people mining on the DK node, it should just be a reconnect in cgminer.

OK, doing the DK DNS switch now, this has no effect on anyone at all, but just means that if you are one of the few people pointing to DK, if you reconnect 10 minute or more from now, you'll end up on NL.

In about half an hour I'll send the reconnect, to redirect everyone on DK to NL, and then stop the pool node shortly after that, which will force a reconnect for anyone left: i.e. not cgminer or a proxy that ignores reconnects

DK is currently 70THs (NL is 650THs)

Also, anyone wondering about the list of nodes, the thread subject contains the list, but of course there is no us.kano.is

[35+PH] Kano CKPool kano.is 0.9% PPLNS US,DE,SG,JP,FR,NL

--

FWIW...sorta kinda what I figgered...the primary (kano.is) is my best bet here, at around 75ms. SG runs over 200ms, JP didn't connect (I think Kano dumped that one, but my memory ain't that super anymore)
...

JP works fine
But it usually only has a very small hash rate, but that's OK also since all nodes work on distributing our blocks faster also, and it's well placed for that.

[firetreeactual]

I'll try pinging that one again. I can move my S3s over if it's better. I'm sure the Labrador machines should be going to primary.

EDIT: Interesting...ping command on terminal sends a packet to jp.kano.is, gets nothing back...hmmm. SG was 220ms, etc.
However, moved Sneezy (225M) and Dopey (250M) to JP and we'll see how it goes. I've got the other four to look at for comps on HW, stales, etc.

[kano]

Meanwhile, in the land of mining nodes ...

I'm gonna get rid of the DK node in about 10-12 hours.

No one has to do anything to their miners, since, I'll firstly, simply point DK at NL, then about 1/2 an hour or so later send anyone mining on DK a redirect to NL.
Finally, when I stop the pool node itself, anyone still left will reconnect to NL, since DK will be pointing to NL by then.

If you rent and mine to DK, then the rental may give up, since certain rental place's poxy software may not handle a redirect.
Makes you wonder what you are paying that exorbitant fee to them for ... if they cant add that original stratum command.

Right now, NL is ~580THs and DK is only 80THs, so not many people left on the DK node - about 6.
The NL node is faster and better than the DK node, and also gets work from the main Vegas node faster than the DK node, so as I actually mentioned I'd do when I setup the NL node, it's now time to get rid DK.

I'll post again when I'm doing it, but for the ~6 people mining on the DK node, it should just be a reconnect in cgminer.

OK, doing the DK DNS switch now, this has no effect on anyone at all, but just means that if you are one of the few people pointing to DK, if you reconnect 10 minute or more from now, you'll end up on NL.

In about half an hour I'll send the reconnect, to redirect everyone on DK to NL, and then stop the pool node shortly after that, which will force a reconnect for anyone left: i.e. not cgminer or a proxy that ignores reconnects

DK is currently 70THs (NL is 650THs)

Also, anyone wondering about the list of nodes, the thread subject contains the list, but of course there is no us.kano.is

[35+PH] Kano CKPool kano.is 0.9% PPLNS US,DE,SG,JP,FR,NL

...

DK node switch to NL all done.

[wmabern]

Let's start this Wednesday block party off right!!