Author

Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 1888. (Read 5352140 times)

legendary
Activity: 1834
Merit: 1080
---- winter*juvia -----
Kano & Solo back-to-back blocks!!  Grin

where to see the list blocks found by ckpool?
hero member
Activity: 543
Merit: 500
Kano & Solo back-to-back blocks!!  Grin
full member
Activity: 196
Merit: 100
Not to mention, very responsive support when you have questions / concerns.  =) 
legendary
Activity: 1736
Merit: 1032
Carl, aka Sonny :)
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.
hero member
Activity: 770
Merit: 523
Remote nodes == better luck apparently!!  Bring on more blocks!

(I'm just kidding about the luck as that's not how it works Smiley)
Correct, there is chicken involved.
full member
Activity: 196
Merit: 100
DOING THE BLOCK DANCE! WOOT!  Great way to start the morning
legendary
Activity: 1260
Merit: 1006
Mine for a Bit
This is my 2nd Day at 5Nd = 3 blocks found at 100%(5Nd)...still looking good!
sr. member
Activity: 294
Merit: 250
Kano CKPool and Solo CKPool with blocks back to back...

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

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?

legendary
Activity: 1736
Merit: 1032
Carl, aka Sonny :)
Kano CKPool and Solo CKPool with blocks back to back...
sr. member
Activity: 294
Merit: 250
Remote nodes == better luck apparently!!  Bring on more blocks!

(I'm just kidding about the luck as that's not how it works Smiley)
legendary
Activity: 1778
Merit: 1026
Free WSPU2 Token or real dollars
congratz!!!
now i'm rich.
hero member
Activity: 770
Merit: 523
newbie
Activity: 20
Merit: 0

Second remote node up and running, in Germany

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

Again all with IPv4 or IPv6


Wow you're on a roll.
full member
Activity: 196
Merit: 100
"Share Rate" and "«Elapsed" are initialised when the miner first connects.
"Share Rate" and "«Elapsed" reset every network block.

Their aim is to inform you: if you are connecting properly and sending shares properly.

"Share Rate" is the number of shares you have submitted in "«Elapsed" then converted to a hash rate.
The very first second that you connect to the pool, they will report the shares you have submitted since "«Elapsed"
Thus it has high variance, but has the specific use of being able to see the shares you are submitting, immediately.
They are not trying to tell you your accurate hash rate.
They are telling you that you are connected to the pool properly and sending shares properly.


We haven't found a block for the last 17hrs but my Elapsed time have resetted 6 times since.  One of which is for your server reboot, two of which are part of my test by rebooting 1 Miner to confirm that 1 miner reset would affect all miners elapsed time stat under the same user account.  As a matter of fact it just reset again few minutes ago.  My share rate surely can not be only 12.85TH when my Hash rate is 14.21-15TH and the systems have been running for a long time on Kano pool not just connected.  If this keeps on happening to my account, my reported share rate reported may not be accurate right?  I don't have any network connectivity issues as I've been working online all night, however, how can I be certain my miners are not having connectivity issues to Kano servers?  
You're not understanding. Elapsed time is time elapsed since the last network block was found, not the last pool block.

Ahhhh................that makes more sense.  Yes, it seems to match the Network block info above.  Thanks for the clarification. 
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
"Share Rate" and "«Elapsed" are initialised when the miner first connects.
"Share Rate" and "«Elapsed" reset every network block.

Their aim is to inform you: if you are connecting properly and sending shares properly.

"Share Rate" is the number of shares you have submitted in "«Elapsed" then converted to a hash rate.
The very first second that you connect to the pool, they will report the shares you have submitted since "«Elapsed"
Thus it has high variance, but has the specific use of being able to see the shares you are submitting, immediately.
They are not trying to tell you your accurate hash rate.
They are telling you that you are connected to the pool properly and sending shares properly.


We haven't found a block for the last 17hrs but my Elapsed time have resetted 6 times since.  One of which is for your server reboot, two of which are part of my test by rebooting 1 Miner to confirm that 1 miner reset would affect all miners elapsed time stat under the same user account.  As a matter of fact it just reset again few minutes ago.  My share rate surely can not be only 12.85TH when my Hash rate is 14.21-15TH and the systems have been running for a long time on Kano pool not just connected.  If this keeps on happening to my account, my reported share rate reported may not be accurate right?  I don't have any network connectivity issues as I've been working online all night, however, how can I be certain my miners are not having connectivity issues to Kano servers?  
You're not understanding. Elapsed time is time elapsed since the last network block was found, not the last pool block.
full member
Activity: 196
Merit: 100
"Share Rate" and "«Elapsed" are initialised when the miner first connects.
"Share Rate" and "«Elapsed" reset every network block.

Their aim is to inform you: if you are connecting properly and sending shares properly.

"Share Rate" is the number of shares you have submitted in "«Elapsed" then converted to a hash rate.
The very first second that you connect to the pool, they will report the shares you have submitted since "«Elapsed"
Thus it has high variance, but has the specific use of being able to see the shares you are submitting, immediately.
They are not trying to tell you your accurate hash rate.
They are telling you that you are connected to the pool properly and sending shares properly.


We haven't found a block for the last 17hrs but my Elapsed time have resetted 6 times since.  One of which is for your server reboot, two of which are part of my test by rebooting 1 Miner to confirm that 1 miner reset would affect all miners elapsed time stat under the same user account.  As a matter of fact it just reset again few minutes ago.  My share rate surely can not be only 12.85TH when my Hash rate is 14.21-15TH and the systems have been running for a long time on Kano pool not just connected.  If this keeps on happening to my account, my reported share rate reported may not be accurate right?  I don't have any network connectivity issues as I've been working online all night, however, how can I be certain my miners are not having connectivity issues to Kano servers?  

Worker Name:   Work Diff   :Last Share   Shares   :Diff   :Share Rate   «Elapsed   :Invalid   Block %   :Hash Rate
nhando1977.Antminer3   318   2s   18,970   6,222,855   435.81GHs   5m 51s   0.140%   0.005%   429.38GHs
nhando1977.antminer4   418   0s   16,511   6,529,335   491.02GHs   5m 51s   0.113%   0.005%   447.76GHs
nhando1977.avalon1   2.844k   6s   16,777   46,944,126   2.75THs   5m 51s   0.228%   0.036%   3.10THs
nhando1977.nhando   420   5s   16,036   6,764,658   503.65GHs   5m 51s   0.075%   0.005%   460.84GHs
nhando1977.S3Ant2   492   9s   19,424   7,326,961   457.54GHs   5m 51s   0.212%   0.006%   507.70GHs
nhando1977.S7_1   3.659k   6s   18,708   67,848,473   4.12THs   5m 51s   0.200%   0.052%   4.46THs
nhando1977.S7B   3.447k   9s   15,151   68,582,794   4.09THs   5m 51s   0.133%   0.053%   4.80THs
Total: 7      121,577   210,219,202   12.85THs       0.176%   0.162%   14.21THs


P.S I've seen it fluctuate from 10TH to 15TH from yesterday until this morning.  I just hit refresh on the browser and it now shows Elapsed time as 1Minute 27.  There is no consistency at all with this Elapsed time data.  Noticed it's only a few minutes but now it's reporting 17.13TH instead of 12.85TH

Worker Name:   Work Diff   :Last Share   Shares   :Diff   :Share Rate   «Elapsed   :Invalid   Block %   :Hash Rate
nhando1977.Antminer3   318   2s   19,352   6,344,331   565.16GHs   1m 27s   0.142%   0.005%   427.17GHs
nhando1977.antminer4   418   0s   16,843   6,668,111   412.71GHs   1m 27s   0.117%   0.005%   461.44GHs
nhando1977.avalon1   2.844k   7s   17,077   47,797,326   2.53THs   1m 27s   0.230%   0.036%   3.08THs
nhando1977.nhando   420   9s   16,366   6,903,258   601.30GHs   1m 27s   0.079%   0.005%   468.84GHs
nhando1977.S3Ant2   492   5s   19,698   7,461,769   388.62GHs   1m 27s   0.215%   0.006%   495.93GHs
nhando1977.S7_1   3.659k   1s   19,087   69,235,234   6.68THs   1m 27s   0.201%   0.052%   4.56THs
nhando1977.S7B   3.447k   2s   15,568   70,020,193   5.96THs   1m 27s   0.140%   0.053%   4.88THs
Total: 7      123,991   214,430,222   17.13THs       0.180%   0.162%   14.37THs
newbie
Activity: 41
Merit: 0
thx for the DE server  Smiley

Seconded ! DE server brings much improvement to European miners:

PING kano.is (104.194.28.196) 56(84) bytes of data.
64 bytes from u3a196.iporg.org (104.194.28.196): icmp_seq=1 ttl=52 time=215 ms

PING sg.kano.is (139.162.5.112) 56(84) bytes of data.
64 bytes from sg.kano.is (139.162.5.112): icmp_seq=1 ttl=52 time=389 ms

PING de.kano.is (139.162.143.142) 56(84) bytes of data.
64 bytes from li1410-142.members.linode.com (139.162.143.142): icmp_seq=1 ttl=53 time=50.0 ms

Thank you Kano & CK !
yxt
legendary
Activity: 3528
Merit: 1116
thx for the DE server  Smiley
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Will the asic tubes Work on "de" server? I live in Denmark so im gonna switch over
No they won't at this stage. We may consider adding extra ports for them though.
Jump to: