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

[zahzin]

i see this when i ping sg.kano.is
---
no ip address ?

---

IPv6 address.

[ryen123]

i see this when i ping sg.kano.is

C:\Users\User>ping sg.kano.is

Pinging sg.kano.is [2400:8901::f03c:91ff:fef1:5056] with 32 bytes of data:
Reply from 2400:8901::f03c:91ff:fef1:5056: time=12ms
Reply from 2400:8901::f03c:91ff:fef1:5056: time=13ms
Reply from 2400:8901::f03c:91ff:fef1:5056: time=14ms
Reply from 2400:8901::f03c:91ff:fef1:5056: time=13ms

Ping statistics for 2400:8901::f03c:91ff:fef1:5056:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 12ms, Maximum = 14ms, Average = 13ms

no ip address ?

main kano.is is ok

de is also ok

dash says it's dead & alive time to time but when it's back, miner hangs & does not failover.

That's ipv6 address (2400:8901::f03c:91ff:fef1:5056)

This is what I've got

Code:

Pinging sg.kano.is [139.162.5.112] with 32 bytes of data:
Reply from 139.162.5.112: bytes=32 time=169ms TTL=56
Reply from 139.162.5.112: bytes=32 time=170ms TTL=56
Reply from 139.162.5.112: bytes=32 time=170ms TTL=56
Reply from 139.162.5.112: bytes=32 time=169ms TTL=56

Ping statistics for 139.162.5.112:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 169ms, Maximum = 170ms, Average = 169ms

[yslyung]

i see this when i ping sg.kano.is
---
no ip address ?

---

IPv6 address.

now it's back to normal at home i see the normal ip add:


C:\Users\xxx>ping sg.kano.is

Pinging sg.kano.is [139.162.5.112] with 32 bytes of data:
Reply from 139.162.5.112: bytes=32 time=38ms TTL=53
Reply from 139.162.5.112: bytes=32 time=36ms TTL=53
Reply from 139.162.5.112: bytes=32 time=35ms TTL=53
Reply from 139.162.5.112: bytes=32 time=36ms TTL=53

Ping statistics for 139.162.5.112:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 35ms, Maximum = 38ms, Average = 36ms

at dc :

C:\Users\User>ping sg.kano.is

Pinging sg.kano.is [2400:8901::f03c:91ff:fef1:5056] with 32 bytes of data
Reply from 2400:8901::f03c:91ff:fef1:5056: time=13ms
Reply from 2400:8901::f03c:91ff:fef1:5056: time=15ms
Reply from 2400:8901::f03c:91ff:fef1:5056: time=12ms
Reply from 2400:8901::f03c:91ff:fef1:5056: time=12ms

Ping statistics for 2400:8901::f03c:91ff:fef1:5056:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 12ms, Maximum = 15ms, Average = 13ms

maybe thats the problem causing miner not to hash or getting frozen ?

ck & kano shud be zzz now. let's see what happens. i'll just use my proxy for now.

thx for response guys

[vh]

iPhone - App Sneak Peek.

conquering APN.




 
ETA: 1-31 

[d57heinz]

block propagation is ugly atm.. wonder if that has anything to do with the nodes not having work to do.. Dont know enough about it tho.  When kano awakes im sure he will get on the spv pool to release their blocks ..Starting to become a common occurrence it seems.. Its taking us atm around 35 seconds avg to see new blocks.  http://poolbench.antminer.link/#

Kano got a question could this be due to the bitcoind taking longer to verify "full" blocks vs smaller blocks.. i read this article a while back and was thinking that maybe this could be part of the reason that some nodes take so long to verify and pass on new blocks..  

http://rusty.ozlabs.org/?p=522
https://bitcointalk.org/?topic=140078

It does seem to make a good argument that if a 1 mb block can take up to 25 seconds to verify (worse case scenario) then what happens when blocksize increases to a threshold where it takes longer than 10 min to verify the block?. Interested in your thoughts on this and if this is even a concern.  Thanks in advance

Best Regards
d57heinz

[jonnybravo0311]

It's the GFW causing problems again... or North Korea H-bomb test

[bctmke]

It's the GFW causing problems again... or North Korea H-bomb test

LOL - likely answer #1 

However I do enjoy answer #2 !

[ZACHM]

I have been mining on Kano.is for 1 year!

My results are as follows:
Total BTC = 28.07750352
Average Hashrate = 9.446 TH/s
Average BTC/Day/THs = 0.00812159

The above is from http://ckpoolmonitor.zachmonroe.com Rewards Feature.

If anyone wants to bulk import rewards information instead of one by one, you can do the following steps:

1. Log into Kano.is and go to your rewards page
2. Select all of the rewards that you have not yet entered
3. Copy into Excel (or similar) and save as a *.csv file
4. email the file to me and I will import it for you.

Eventually I plan on making this more automatic, but for now this will work.
Any questions let me know.

[aurel57]

iPhone - App Sneak Peek.

conquering APN.




 
ETA: 1-31 

Nice and I am interested in it

[hawkfish007]

I have been mining on Kano.is for 1 year!

My results are as follows:
Total BTC = 28.07750352
Average Hashrate = 9.446 TH/s
Average BTC/Day/THs = 0.00812159

That's impressive return from 9.446 TH/s.

[ZACHM]

I have been mining on Kano.is for 1 year!

My results are as follows:
Total BTC = 28.07750352
Average Hashrate = 9.446 TH/s
Average BTC/Day/THs = 0.00812159

That's impressive return from 9.446 TH/s.

That is my average for the year, currently I'm at about 17.5 TH/s.

[baazju]

I smell a block.

[ZemCoin]

I smell a block.

Will be nice...

[-ck]

now it's back to normal at home i see the normal ip add:


C:\Users\xxx>ping sg.kano.is

Pinging sg.kano.is [139.162.5.112] with 32 bytes of data:
Reply from 139.162.5.112: bytes=32 time=38ms TTL=53
Reply from 139.162.5.112: bytes=32 time=36ms TTL=53
Reply from 139.162.5.112: bytes=32 time=35ms TTL=53
Reply from 139.162.5.112: bytes=32 time=36ms TTL=53

Ping statistics for 139.162.5.112:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 35ms, Maximum = 38ms, Average = 36ms

at dc :

C:\Users\User>ping sg.kano.is

Pinging sg.kano.is [2400:8901::f03c:91ff:fef1:5056] with 32 bytes of data
Reply from 2400:8901::f03c:91ff:fef1:5056: time=13ms
Reply from 2400:8901::f03c:91ff:fef1:5056: time=15ms
Reply from 2400:8901::f03c:91ff:fef1:5056: time=12ms
Reply from 2400:8901::f03c:91ff:fef1:5056: time=12ms

Ping statistics for 2400:8901::f03c:91ff:fef1:5056:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 12ms, Maximum = 15ms, Average = 13ms

maybe thats the problem causing miner not to hash or getting frozen ?

ck & kano shud be zzz now. let's see what happens. i'll just use my proxy for now.

thx for response guys

Ok perhaps there are miners or gateways out there with broken IPV6 implementations and they're intermittently switching from the IPV4 to the IPV6 server unintentionally. I'll disable IPV6 and we'll see if your problems all go away.

EDIT: Alternatively try mining directly to the IPV4 address of 139.162.5.112 till the IPV6 gets forgotten by the network.

[bctmke]

I have been mining on Kano.is for 1 year!

My results are as follows:
Total BTC = 28.07750352
Average Hashrate = 9.446 TH/s
Average BTC/Day/THs = 0.00812159

The above is from http://ckpoolmonitor.zachmonroe.com Rewards Feature.

If anyone wants to bulk import rewards information instead of one by one, you can do the following steps:

1. Log into Kano.is and go to your rewards page
2. Select all of the rewards that you have not yet entered
3. Copy into Excel (or similar) and save as a *.csv file
4. email the file to me and I will import it for you.

Eventually I plan on making this more automatic, but for now this will work.
Any questions let me know.

Awesome - incoming .csv

[VRobb]

Alright, 24hrs and no block cracked yet, time to pull out the big guns...!  I didn't mention it yesterday, but right after I ate some cheese/chicken/crackers for lunch we hit the double whammy. 

I'm eating some cheese/chicken/crackers again right now!  You are doomed, block.  Doomed I tell you...

[wolfen]

Any birthdays coming up?
Have two chicken roasters from Costco.
That should kick it loose.
Eat baby!

[ZACHM]

Awesome - incoming .csv

Should be all set.

[wolfen]

Have to take the wolfpack off the chain.
Let 'em sniff

[wolfen]

Two s3's powered with two chickens
This should do it.
Notice the quartz crystal.
Full voodoo