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

[aarons6]

Before I add it on the web site and every where else:

First remote node up and running, in Singapore

Same username or bitcoin address, everything accounts back to the pool stats, as expected on the main web site at https://kano.is/

Pool address is any of the following, but also IPv4 or IPv6

stratum+tcp://sg.kano.is:3333
stratum+tcp://sg.kano.is:80
stratum+tcp://sg.kano.is:443

Give it a try if you are closer to that and let us know what you think

There's no other services running at that address, just mining.

can this be failover or if the main site is down this is down too?

[-ck]

Before I add it on the web site and every where else:

First remote node up and running, in Singapore

Same username or bitcoin address, everything accounts back to the pool stats, as expected on the main web site at https://kano.is/

Pool address is any of the following, but also IPv4 or IPv6

stratum+tcp://sg.kano.is:3333
stratum+tcp://sg.kano.is:80
stratum+tcp://sg.kano.is:443

Give it a try if you are closer to that and let us know what you think

There's no other services running at that address, just mining.

can this be failover or if the main site is down this is down too?

No it does not make sense to use it as failover. If anything, using the SG server first and the main pool as failover makes sense as the node may go down but the main pool still be up. In case of a DDoS it's hard to know as it depends entirely on what form the DDoS takes and where it's directed.

For people in Oceania be aware that the node being in Singapore doesn't instantly guarantee faster routing as it depends on your ISP and where you are located. Make sure to ping the server to decide which is closer of SG or the main server. Kano and I tested Sydney versus Melbourne and it was faster to SG from Sydney but slower from Melbourne. I think Adelaide, Perth and Darwin would all be closer but test for yourselves.

[dodziu]

running 20min SG location , no issues atm.

[Mikestang]

Over 9PH now, if we get much bigger my little 40GH won't even make the dust threshold any more.   

[-ck]

Over 9PH now

Correction, over 9000 TH

[kano]

Payout 391710 sent (about 1.4hrs ago)
8e7deb1719d58f64f07aba1603b2ded86e521579e31ada454fa5e62430765a04
and confirmed (about 25min ago)

[nhando]

Did we just have another reboot yet again?  It's showing 1 min elapsed time and my hash rate is all screwy again.  That is like 3 reboots total today right?

[-ck]

Did we just have another reboot yet again?  It's showing 1 min elapsed time and my hash rate is all screwy again.  That is like 3 reboots total today right?

No there have been no reboots. There was only the one planned pool software restart 8 hours ago and there was no actual downtime. If you're having connectivity issues it's nothing to do with the pool.

[yslyung]

will try the sg server shortly & report back.

ping to kano.is on avg is 334ms

ping to sg.kano.is avg is 14ms

will be redirecting miners shortly.

thx guys.

it says dead on sg.kano.is:3333

my bad, typo, it is up & running well, all miners redirected to sg.

[nhando]

My network have been up the entire time.  Here's the stats.  Shows Elapsed time as being 22Mins as it's now 22 mins later.

Worker Name:   Work Diff   :Last Share   Shares   :Diff   :Share Rate   «Elapsed   :Invalid   Block %   :Hash Rate
nhando1977.Antminer3   320   3s   10,840   3,631,879   454.35GHs   22m 14s   0.144%   0.005%   434.27GHs
nhando1977.antminer4   335   2s   8,299   3,842,219   473.49GHs   22m 14s   0.143%   0.005%   442.29GHs
nhando1977.avalon1   2.844k   1s   9,941   27,502,542   2.96THs   22m 14s   0.255%   0.037%   3.12THs
nhando1977.nhando   420   1s   9,390   3,973,338   462.47GHs   22m 14s   0.085%   0.005%   463.65GHs
nhando1977.S3Ant2   369   8s   11,389   4,270,657   508.48GHs   22m 14s   0.175%   0.006%   502.12GHs
nhando1977.S7_1   3.659k   1s   11,111   40,051,050   4.64THs   22m 14s   0.248%   0.054%   4.78THs
nhando1977.S7B   5.224k   2s   8,224   40,374,690   4.56THs   22m 14s   0.136%   0.055%   4.57THs
Total: 7      69,194   123,646,375   14.06THs       0.199%   0.168%   14.31THs

P.S I'm going to test a reboot of 1 of the miners and see what it reports, but I don't think this issue was caused by connectivity on my end as my network was up the entire time.

[sorry2xs]

it is reverse for me, i guess kano.is is closer to east coast usa

[nhando]

This is very weird.  Does 1 miner affect all miners under the same username?  Just rebooting 1 worker / miner and the stats is reflected the same for all of them.  See below as they're all reporting as Elapsed 1m 59s versus different stats for each worker / miner.


Worker Name:   Work Diff   :Last Share   Shares   :Diff   :Share Rate   «Elapsed   :Invalid   Block %   :Hash Rate
nhando1977.Antminer3   1.042k   6s   10,890   3,649,323   156.06GHs   1m 59s   0.143%   0.005%   423.74GHs
nhando1977.antminer4   335   9s   8,381   3,869,689   423.18GHs   1m 59s   0.142%   0.005%   443.25GHs
nhando1977.avalon1   2.844k   7s   10,020   27,727,218   3.28THs   1m 59s   0.253%   0.037%   3.13THs
nhando1977.nhando   420   5s   9,457   4,001,478   363.81GHs   1m 59s   0.085%   0.005%   461.06GHs
nhando1977.S3Ant2   369   15s   11,490   4,307,926   519.40GHs   1m 59s   0.173%   0.006%   511.07GHs
nhando1977.S7_1   3.659k   2s   11,190   40,340,111   4.75THs   1m 59s   0.255%   0.054%   4.77THs
nhando1977.S7B   5.224k   1s   8,279   40,662,010   4.15THs   1m 59s   0.135%   0.055%   4.53THs
Total: 7      69,707   124,557,755   13.65THs       0.200%   0.168%   14.27THs

[-ck]

This is very weird.  Does 1 miner affect all miners under the same username?  Just rebooting 1 worker / miner and the stats is reflected the same for all of them.  See below as they're all reporting as Elapsed 1m 59s versus different stats for each worker / miner.

Code:

Worker Name:	Work Diff	:Last Share	Shares	:Diff	:Share Rate	«Elapsed	:Invalid	Block %	:Hash Rate
nhando1977.Antminer3	1.042k	6s	10,890	3,649,323	156.06GHs	1m 59s	0.143%	0.005%	423.74GHs
nhando1977.antminer4	335	9s	8,381	3,869,689	423.18GHs	1m 59s	0.142%	0.005%	443.25GHs
nhando1977.avalon1	2.844k	7s	10,020	27,727,218	3.28THs	1m 59s	0.253%	0.037%	3.13THs
nhando1977.nhando	420	5s	9,457	4,001,478	363.81GHs	1m 59s	0.085%	0.005%	461.06GHs
nhando1977.S3Ant2	369	15s	11,490	4,307,926	519.40GHs	1m 59s	0.173%	0.006%	511.07GHs
nhando1977.S7_1	3.659k	2s	11,190	40,340,111	4.75THs	1m 59s	0.255%	0.054%	4.77THs
nhando1977.S7B	5.224k	1s	8,279	40,662,010	4.15THs	1m 59s	0.135%	0.055%	4.53THs
Total: 7		69,707	124,557,755	13.65THs	 	0.200%	0.168%	14.27THs

Oh I see what you mean. Kano will have to look into that. The pool has been fine all along with no interruption to mining since the restart.

[nhando]

I think the Elapse time is not accurate.  I would close the browser tab and launch it again and it would report lower numbers.  As you can see here, no network interruptions nor reboot of any nodes and it now shows 32s for ELapsed time.  Although I can't duplicate the issue when I tried it the 3rd time in a row.  Let me try rebooting 1 more miner and see if it affects all miners for the stats.

Worker Name:   Work Diff   :Last Share   Shares   :Diff   :Share Rate   «Elapsed   :Invalid   Block %   :Hash Rate
nhando1977.Antminer3   1.042k   0s   10,905   3,664,953   279.71GHs   32s   0.142%   0.005%   419.13GHs
nhando1977.antminer4   335   0s   8,442   3,890,124   494.59GHs   32s   0.141%   0.005%   442.26GHs
nhando1977.avalon1   2.844k   3s   10,064   27,852,354   3.44THs   32s   0.252%   0.037%   3.11THs
nhando1977.nhando   420   3s   9,514   4,025,418   450.97GHs   32s   0.084%   0.005%   463.22GHs
nhando1977.S3Ant2   369   2s   11,559   4,333,387   396.21GHs   32s   0.172%   0.006%   513.11GHs
nhando1977.S7_1   3.659k   7s   11,248   40,552,333   4.91THs   32s   0.254%   0.054%   4.76THs
nhando1977.S7B   5.224k   3s   8,314   40,844,850   4.91THs   32s   0.159%   0.055%   4.51THs
Total: 7      70,046   125,163,419   14.88THs       0.208%   0.168%   14.23THs


Browser = Chrome

[-ck]

will try the sg server shortly & report back.

ping to kano.is on avg is 334ms

ping to sg.kano.is avg is 14ms

will be redirecting miners shortly.

thx guys.

it says dead on sg.kano.is:3333

Working fine for me. Check your syntax please.

it is reverse for me, i guess kano.is is closer to east coast usa

Yes indeed, the main server is in LA.

[nhando]

Seems like this one is consistent.  If 1 of my miner reboots it would affect all 7 Miner's Elapsed time rather than just the stat for itself.  Is this expected or a bug?

Worker Name:   Work Diff   :Last Share   Shares   :Diff   :Share Rate   «Elapsed   :Invalid   Block %   :Hash Rate
nhando1977.Antminer3   318   4s   11,022   3,695,391   512.17GHs   8s   0.141%   0.005%   418.06GHs
nhando1977.antminer4   1.042k   1s   8,516   3,915,621   559.42GHs   8s   0.140%   0.005%   440.07GHs
nhando1977.avalon1   2.844k   3s   10,156   28,114,002   6.11THs   8s   0.250%   0.037%   3.16THs
nhando1977.nhando   420   4s   9,601   4,061,958   225.49GHs   8s   0.083%   0.005%   465.82GHs
nhando1977.S3Ant2   369   1s   11,667   4,373,239   792.42GHs   8s   0.171%   0.006%   517.65GHs
nhando1977.S7_1   3.659k   4s   11,338   40,881,643   1.96THs   8s   0.261%   0.054%   4.76THs
nhando1977.S7B   5.224k   2s   8,378   41,179,186   2.80THs   8s   0.158%   0.055%   4.52THs
Total: 7      70,678   126,221,040   12.97THs       0.209%   0.168%   14.28THs

[-ck]

Seems like this one is consistent.  If 1 of my miner reboots it would affect all 7 Miner's Elapsed time rather than just the stat for itself.  Is this expected or a bug?

Sounds like a bug. Don't worry it won't affect your share counting and reward. Kano will have to look into it, thanks.

[nhando]

Cool.....not worry at all, just trying to understand and this is what makes this pool all that much better.  There is no guessing game, you get the real scoop on what to expect.

[kano]

"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.

[citronick]

Ping test from SG (my rigs are physically in SG).

C:\Users\pipo>ping kano.is
Reply from 104.194.28.196: bytes=32 time=202ms TTL=47
Reply from 104.194.28.196: bytes=32 time=196ms TTL=45
Reply from 104.194.28.196: bytes=32 time=209ms TTL=45
Reply from 104.194.28.196: bytes=32 time=215ms TTL=45
Minimum = 196ms, Maximum = 215ms, Average = 205ms

C:\Users\pipo>ping sg.kano.is
Reply from 139.162.5.112: bytes=32 time=5ms TTL=53
Reply from 139.162.5.112: bytes=32 time=5ms TTL=53
Reply from 139.162.5.112: bytes=32 time=4ms TTL=53
Reply from 139.162.5.112: bytes=32 time=5ms TTL=53
Minimum = 4ms, Maximum = 5ms, Average = 4ms

Switching to Kano@SG in the next hour.

Btw, I assume my 5ND hashes, best shares etc. are intact after I switch over ... I don't think so, but I will be more assured in Kano or CK or other gurus can double confirm this.

Edit:  I THINK so, but I will be more assured in Kano or CK or other gurus can double confirm this.