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

[bctmke]

Kano CKPool and Solo CKPool with blocks back to back...

Can't go wrong.  Apparently kano and ck are doing something right

Kano,

Did I read correctly earlier in the thread - the remote servers are submitting the blocks directly?  And then they're just passing the data along to the main server for record keeping?

[AriesIV10]

This is my 2nd Day at 5Nd = 3 blocks found at 100%(5Nd)...still looking good!

[nhando]

DOING THE BLOCK DANCE! WOOT!  Great way to start the morning

[wolfen]

Remote nodes == better luck apparently!!  Bring on more blocks!

(I'm just kidding about the luck as that's not how it works )

Correct, there is chicken involved.

[clgrissom3]

Kano and CK...these guys are the bomb!  I have never seen a pool where you can talk about adding something one day and the next day we have nodes in 2 additional countries and everyone was kept informed every step of the way.  You simply cannot find any better than this!  This is the only pool to call home in my book.

[nhando]

Not to mention, very responsive support when you have questions / concerns.  =) 

[727miner]

Kano & Solo back-to-back blocks!! 

[citronick]

Kano & Solo back-to-back blocks!! 

where to see the list blocks found by ckpool?

[omega015]

Kano & Solo back-to-back blocks!!  

where to see the list blocks found by ckpool?

https://blockchain.info/

https://www.blocktrail.com/BTC

EDIT:

solo: https://www.blocktrail.com/BTC/pool/solockpool
Kano: https://www.blocktrail.com/BTC/pool/kano

[wolfen]

canaan has the afterburners on. Yeah buddy!

[jonnybravo0311]

Hey Kano,

Congrats on the recent pool growth!  Seems like every day I log on here you've grown another PH .  I'm glad to see more and more miners turning their hash away from the BFB (bad for bitcoin) pools.

Best of luck and continued success to you.

[baazju]

I love waking up to a new block!

[aarons6]

@ZACHM

is there anyway to get the worker info and in the settings where it says dropped worker have the workers listed with a check box next to them so you can select what ones you want notified if they drop?


say i have rented hash, or one temporarily down on purpose.. the way your site works ill get an email every few minutes for a few days until it drops off the 5N

[Prelude]

Sweet, morning block! Good job BTCWoman.

Here are my stats for the hell of it, from Montreal Canada:

Code:

PING kano.is (104.194.28.196): 56 data bytes
64 bytes from 104.194.28.196: seq=0 ttl=54 time=70.707 ms
64 bytes from 104.194.28.196: seq=1 ttl=54 time=70.431 ms
64 bytes from 104.194.28.196: seq=2 ttl=54 time=70.908 ms
64 bytes from 104.194.28.196: seq=3 ttl=54 time=70.495 ms
64 bytes from 104.194.28.196: seq=4 ttl=54 time=69.929 ms

--- kano.is ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 69.929/70.494/70.908 ms

Code:

PING de.kano.is (139.162.143.142): 56 data bytes
64 bytes from 139.162.143.142: seq=0 ttl=53 time=92.864 ms
64 bytes from 139.162.143.142: seq=1 ttl=53 time=93.255 ms
64 bytes from 139.162.143.142: seq=2 ttl=53 time=92.791 ms
64 bytes from 139.162.143.142: seq=3 ttl=53 time=92.392 ms
64 bytes from 139.162.143.142: seq=4 ttl=53 time=92.902 ms

--- de.kano.is ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 92.392/92.840/93.255 ms

Code:

PING sg.kano.is (139.162.5.112): 56 data bytes
64 bytes from 139.162.5.112: seq=0 ttl=52 time=264.407 ms
64 bytes from 139.162.5.112: seq=1 ttl=52 time=263.256 ms
64 bytes from 139.162.5.112: seq=2 ttl=52 time=262.469 ms
64 bytes from 139.162.5.112: seq=3 ttl=52 time=263.428 ms
64 bytes from 139.162.5.112: seq=4 ttl=52 time=262.611 ms

--- sg.kano.is ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 262.469/263.234/264.407 ms

Any chance we'll ever see an east coast server, kano? Or perhaps relocate the NA server to somewhere more centrally located so that everyone in NA has the best ping possible? Not that 70ms is all that bad for east coasters, mind you.

[clgrissom3]

Congrats to BTCWoman for hitting our last block!  We salute you!

[d57heinz]

Sweet, morning block! Good job BTCWoman.

Here are my stats for the hell of it, from Montreal Canada:

Code:

...

Thought id share my ping results as well. Just for reference.. i live 50 miles N/E from st louis about as centrally located in North america as one can get.  I set a high packet amount just to test.. MTU is 1500 i usually ping test with just under the threshold.. You'd be surprised at how a server can easily handle 64 bytes but when you max out mtu it can really add to ping times.. i tried with both 64 and 1464 and didnt see any difference in response time.

Code:

C:\Users\d57he_000>ping -t -l 1464 de.kano.is

Pinging de.kano.is [139.162.143.142] with 1464 bytes of data
Reply from 139.162.143.142: bytes=1464 time=123ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=119ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=119ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=122ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=119ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=121ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=122ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=124ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=118ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=119ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=118ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=121ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=122ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=120ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=121ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=121ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=121ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=122ms TTL=50

Ping statistics for 139.162.143.142:
    Packets: Sent = 18, Received = 18, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 118ms, Maximum = 124ms, Average = 120ms
Control-C
^C

Code:

C:\Users\d57he_000>ping -t -l 1464 sg.kano.is

Pinging sg.kano.is [139.162.5.112] with 1464 bytes of data:
Reply from 139.162.5.112: bytes=1464 time=245ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=242ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=244ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=242ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=247ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=246ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=242ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=242ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=241ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=247ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=240ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=244ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=249ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=245ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=250ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=246ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=266ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=288ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=291ms TTL=47

Ping statistics for 139.162.5.112:
    Packets: Sent = 19, Received = 19, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 240ms, Maximum = 291ms, Average = 250ms
Control-C
^C

Code:

C:\Users\d57he_000>ping -t -l 1464 kano.is

Pinging kano.is [104.194.28.196] with 1464 bytes of data:
Reply from 104.194.28.196: bytes=1464 time=56ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=56ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=63ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=56ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=56ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=62ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=58ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=58ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=57ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=55ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=61ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=54ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=56ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=57ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=56ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=53ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=75ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=59ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=55ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=59ms TTL=49

Ping statistics for 104.194.28.196:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 53ms, Maximum = 75ms, Average = 58ms
Control-C
^C
C:\Users\d57he_000>

Best regards
d57heinz

[coffeeangst]

Kano you should consider setting up automatic traffic management with a service like NS1, and provide a DNS entry that routes people to the closest pinging server from their location.

[BannedDK]

moved all to de.kano.is except asic tubes.

ping is really good now 

thanks!!


C:\>ping de.kano.is

Pinger de.kano.is [139.162.143.142] med 32 byte data:
Svar fra 139.162.143.142: byte=32 tid=27ms TTL=55
Svar fra 139.162.143.142: byte=32 tid=28ms TTL=55
Svar fra 139.162.143.142: byte=32 tid=27ms TTL=55
Svar fra 139.162.143.142: byte=32 tid=27ms TTL=55

Ping-statistikker for 139.162.143.142:
    Pakker: Sendt = 4, modtaget = 4, tabt = 0 (0% tab),
Beregnet tid for rundtur i millisekunder:
    Minimum = 27ms, Maksimum = 28ms, Gennemsnitlig = 27ms

[citronick]

Is the SG node down? All my miners are back to US  

>> Ping works but it's showing DOWN and failing back to US node.

[yslyung]

chill. I'm sure many are getting better ping now.

let both of them catch their breath.

more will come.

thx again for the nodes.

meanwhile more blocks to come.