iPhone - App Sneak Peek.
conquering APN.
ETA: 1-31
conquering APN.
ETA: 1-31
Nice and I am interested in it
Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 1880. (Read 5352140 times)
January 06, 2016, 02:04:15 PM
Nice and I am interested in it
January 06, 2016, 02:03:49 PM
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.
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.
January 06, 2016, 01:42:58 PM
It's the GFW causing problems again... or North Korea H-bomb test 
LOL - likely answer #1
However I do enjoy answer #2 !
January 06, 2016, 01:00:41 PM
It's the GFW causing problems again... or North Korea H-bomb test
January 06, 2016, 12:53:14 PM
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
..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
January 06, 2016, 12:17:06 PM
iPhone - App Sneak Peek.
conquering APN.
ETA: 1-31
conquering APN.
ETA: 1-31
January 06, 2016, 11:49:34 AM
i see this when i ping sg.kano.is
---
no ip address ?
---
---
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
January 06, 2016, 11:44:53 AM
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.
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
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
January 06, 2016, 11:44:00 AM
i see this when i ping sg.kano.is
---
no ip address ?
---
---
no ip address ?
---
IPv6 address.
January 06, 2016, 11:43:53 AM
That looks like an IPv6 address... here's what I get when I ping sg.kano.is:
Yeah, I'm currently in Florida, so hence the ping time
Code:
ping sg.kano.is
PING sg.kano.is (139.162.5.112): 56 data bytes
64 bytes from 139.162.5.112: icmp_seq=0 ttl=49 time=303.637 ms
64 bytes from 139.162.5.112: icmp_seq=1 ttl=49 time=243.941 ms
64 bytes from 139.162.5.112: icmp_seq=2 ttl=49 time=380.693 ms
64 bytes from 139.162.5.112: icmp_seq=3 ttl=49 time=341.515 ms
64 bytes from 139.162.5.112: icmp_seq=4 ttl=49 time=260.073 ms
64 bytes from 139.162.5.112: icmp_seq=5 ttl=49 time=293.206 ms
64 bytes from 139.162.5.112: icmp_seq=6 ttl=49 time=248.775 ms
^C
--- sg.kano.is ping statistics ---
7 packets transmitted, 7 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 243.941/295.977/380.693/47.120 ms
Yeah, I'm currently in Florida, so hence the ping time
January 06, 2016, 11:41:36 AM
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.
happened about 3 & 1/2 hour ago from current post.
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.
happened about 3 & 1/2 hour ago from current post.
January 06, 2016, 10:55:12 AM
What is a reason for manual diff settings? CKPool VarDiff works like a charm. Do not change anything and just mine. 1042 is start value and it will be automatically adjusted within 10-20 minutes.
I am sure CKPool handles vardiff very well, just seems Ant s2s does not, and tries to throw a fit with vardiff at some point, no idea why though..
Thanks for the tip, will give those lower values a try as well to see if performance can be even better than with 1000..
Appreciated !
January 06, 2016, 10:40:59 AM
What is a reason for manual diff settings? CKPool VarDiff works like a charm. Do not change anything and just mine. 1042 is start value and it will be automatically adjusted within 10-20 minutes.
I am sure CKPool handles vardiff very well, just seems Ant s2s does not, and tries to throw a fit with vardiff at some point, no idea why though..
January 06, 2016, 10:36:43 AM
What is a reason for manual diff settings? CKPool VarDiff works like a charm. Do not change anything and just mine. 1042 is start value and it will be automatically adjusted within 10-20 minutes.
I am sure CKPool handles vardiff very well, just seems Ant s2s does not, and tries to throw a fit with vardiff at some point, no idea why though..
January 06, 2016, 10:29:06 AM
I was browsing the current workday on Blockchain.info and it seemed that there was an unusually low number of blocks for that large SPV pool that starts with an "A". I looked at their stats page and they are officially under 100% on all categories now. Wow.
24 Hours 3 Day 1 Week 2 Weeks 1 Month 3 Months All
83.00% 99.00% 99.00% 96.00% 96.00% 97.00% 99.00%
EDIT: I did see that someone hit a block on Solo CKPool overnight. Way to go!
24 Hours 3 Day 1 Week 2 Weeks 1 Month 3 Months All
83.00% 99.00% 99.00% 96.00% 96.00% 97.00% 99.00%
EDIT: I did see that someone hit a block on Solo CKPool overnight. Way to go!
January 06, 2016, 10:26:56 AM
If/when de .DE server works fine and is an option for us living in Europe, please write somethimg on the homepage or something.
I have 45 kilometres to my miners in serverrom, so changing server is a "big deal" and need to know why and that it works before i do the trip.
I know many users read every post in this thread, I try to do but not always time so easily missing out info about new servers and how they work and what would be better.
I have 45 kilometres to my miners in serverrom, so changing server is a "big deal" and need to know why and that it works before i do the trip.
I know many users read every post in this thread, I try to do but not always time so easily missing out info about new servers and how they work and what would be better.
January 06, 2016, 10:12:22 AM
What is a reason for manual diff settings? CKPool VarDiff works like a charm. Do not change anything and just mine. 1042 is start value and it will be automatically adjusted within 10-20 minutes.
January 06, 2016, 09:42:40 AM
Will test a bit longer and report back when I have something more substantial
Hmm while testing as I wanted all things to be "equal" once I set the diff offered on Kano pool to 1000 (the same that solo pool is offering) the Ants2 is way more happy and hash rate has climbed back up and not getting as many hw errors either.. So no problem with DE node or anything it seems as far as I am considered..
Weird though that ant s2s dont seem to like the 1042 default which is being offered if I left the worker diff setting to 0 and let it auto adjust.. (if anyone knows of a better setting than 1000 please do tell) but yeah, that seemed to do the trick to get it to perform the same as in solo pool..
January 06, 2016, 09:41:03 AM
Come on miners, this is our block I feel sad when I see no blocks waiting to be matured 
I feel sad when I see no blocks waiting to be matured January 06, 2016, 09:39:34 AM
Confirmed, DE server works perfect. Changed all except 1 miner from the main to the DE server yesterday, no issues, same hashrate.
Test Now
Jump to: