bctmke
|
|
January 05, 2016, 02:27:15 PM |
|
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
Legendary
Offline
Activity: 1260
Merit: 1006
Mine for a Bit
|
|
January 05, 2016, 02:29:15 PM |
|
This is my 2nd Day at 5Nd = 3 blocks found at 100%(5Nd)...still looking good!
|
|
|
|
nhando
|
|
January 05, 2016, 02:39:00 PM |
|
DOING THE BLOCK DANCE! WOOT! Great way to start the morning
|
Just "Mining" my own business.
|
|
|
wolfen
|
|
January 05, 2016, 02:48:00 PM |
|
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.
|
For those about to block we salute you! AC->BTC
|
|
|
clgrissom3
Legendary
Offline
Activity: 1722
Merit: 1032
Carl, aka Sonny :)
|
|
January 05, 2016, 02:51:38 PM |
|
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
|
|
January 05, 2016, 02:53:32 PM |
|
Not to mention, very responsive support when you have questions / concerns. =)
|
Just "Mining" my own business.
|
|
|
727miner
|
|
January 05, 2016, 02:58:19 PM |
|
Kano & Solo back-to-back blocks!!
|
|
|
|
citronick
Legendary
Offline
Activity: 1834
Merit: 1080
---- winter*juvia -----
|
|
January 05, 2016, 03:02:50 PM |
|
Kano & Solo back-to-back blocks!! where to see the list blocks found by ckpool?
|
If I provided you good and useful info or just a smile to your day, consider sending me merit points to further validate this Bitcointalk account ~ useful for future account recovery...
|
|
|
|
wolfen
|
|
January 05, 2016, 03:17:51 PM |
|
canaan has the afterburners on. Yeah buddy!
|
For those about to block we salute you! AC->BTC
|
|
|
jonnybravo0311
Legendary
Offline
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
|
|
January 05, 2016, 03:21:56 PM |
|
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.
|
Jonny's Pool - Mine with us and help us grow! Support a pool that supports Bitcoin, not a hardware manufacturer's pockets! No SPV cheats. No empty blocks.
|
|
|
baazju
Member
Offline
Activity: 98
Merit: 10
|
|
January 05, 2016, 03:28:20 PM |
|
I love waking up to a new block!
|
Beware of scammers.
|
|
|
aarons6
Legendary
Offline
Activity: 1736
Merit: 1006
|
|
January 05, 2016, 03:30:24 PM |
|
@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
Legendary
Offline
Activity: 1596
Merit: 1000
|
|
January 05, 2016, 03:31:10 PM |
|
Sweet, morning block! Good job BTCWoman. Here are my stats for the hell of it, from Montreal Canada: 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 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 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
Legendary
Offline
Activity: 1722
Merit: 1032
Carl, aka Sonny :)
|
|
January 05, 2016, 03:43:02 PM |
|
Congrats to BTCWoman for hitting our last block! We salute you!
|
|
|
|
d57heinz
Legendary
Offline
Activity: 1453
Merit: 1011
Bitcoin Talks Bullshit Walks
|
|
January 05, 2016, 03:58:58 PM |
|
Sweet, morning block! Good job BTCWoman. Here are my stats for the hell of it, from Montreal Canada: 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. 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 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 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
|
As in nature, all is ebb and tide, all is wave motion, so it seems that in all branches of industry, alternating currents - electric wave motion - will have the sway. ~Nikola Tesla~
|
|
|
coffeeangst
Newbie
Offline
Activity: 20
Merit: 0
|
|
January 05, 2016, 04:15:08 PM |
|
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
Member
Offline
Activity: 109
Merit: 10
|
|
January 05, 2016, 04:18:42 PM |
|
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
Legendary
Offline
Activity: 1834
Merit: 1080
---- winter*juvia -----
|
|
January 05, 2016, 04:45:07 PM |
|
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.
|
If I provided you good and useful info or just a smile to your day, consider sending me merit points to further validate this Bitcointalk account ~ useful for future account recovery...
|
|
|
yslyung
Legendary
Offline
Activity: 1500
Merit: 1002
Mine Mine Mine
|
|
January 05, 2016, 04:47:03 PM |
|
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.
|
|
|
|
|