Bitcoin Forum
November 15, 2024, 04:15:30 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 [362] 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 ... 2250 »
  Print  
Author Topic: KanoPool since 2014 🐈 - PPLNS and Solo 0.5% fee - Worldwide - 2438 blocks  (Read 5352036 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic. (50 posts by 3+ users deleted.)
yslyung
Legendary
*
Offline Offline

Activity: 1500
Merit: 1002


Mine Mine Mine


View Profile
January 05, 2016, 07:39:40 AM
 #7221

cit u live next to the node ? lol

i thought it was good for me 14 ms.

really happy as per request & comes the node. much faster for us at this part of the world !

including downunder
e46btc
Full Member
***
Offline Offline

Activity: 157
Merit: 103


View Profile
January 05, 2016, 07:44:50 AM
 #7222

citronick, do not worry and you will lost nothing. all calc at main pool
So everything the same but much better connectivity

https://txid.io https://double-spending.com - Automatic BTC double-spending tool.  Legacy, Segwit and Bech32 supported.
https://dgb256.online - Digibyte mining pool , https://combine.dgb256.online - DGB mining payouts consolidation service.
https://sha256.io , https://solomining.io - DGB, BTC, BCH SOLO pools, Instant payouts, AsicBoost supported
usukan
Legendary
*
Offline Offline

Activity: 1590
Merit: 1002



View Profile
January 05, 2016, 07:55:46 AM
Last edit: January 05, 2016, 08:10:23 AM by usukan
 #7223

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 Huh

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


interesting that from a little island out in the Pacific Ocean off the east coast of Australia

kano.is is average 154ms

sg.kano.is is average 254ms

Would have expected SG to be far better from here?

Will stay where I am



C:\Users\xxxx>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=250ms TTL=50
Reply from 139.162.5.112: bytes=32 time=245ms TTL=50
Reply from 139.162.5.112: bytes=32 time=243ms TTL=50
Reply from 139.162.5.112: bytes=32 time=244ms TTL=50

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

C:\Users\xxxx>ping kano.is

Pinging kano.is [104.194.28.196] with 32 bytes of data:
Reply from 104.194.28.196: bytes=32 time=154ms TTL=55
Reply from 104.194.28.196: bytes=32 time=155ms TTL=55
Reply from 104.194.28.196: bytes=32 time=154ms TTL=55
Reply from 104.194.28.196: bytes=32 time=154ms TTL=55

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





--


--
RobbieRoor
Member
**
Offline Offline

Activity: 97
Merit: 10


View Profile
January 05, 2016, 08:05:31 AM
 #7224

Woo the pool broke the 9th mark early this morning! It seems like the hashing power has jumped 2ph this week alone. Love seeing this pool grow! Keep up the awesome stuffs everyone!
-ck
Legendary
*
Offline Offline

Activity: 4284
Merit: 1645


Ruu \o/


View Profile WWW
January 05, 2016, 08:13:29 AM
 #7225

interesting that from a little island out in the Pacific Ocean off the east coast of Australia

kano.is is average 154ms

sg.kano.is is average 254ms

Would have expected SG to be far better from here?

This is what I was trying to say here:
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.

For reasons to do with cheaper connectivity by different internet providers they may actually not choose the fastest route to an IP address, so you must test yourself to see what route they take to get there.

Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel
2% Fee Solo mining at solo.ckpool.org
-ck
-ck
Legendary
*
Offline Offline

Activity: 4284
Merit: 1645


Ruu \o/


View Profile WWW
January 05, 2016, 08:31:03 AM
 #7226

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.
Yes, all your base are belong to us all hashes go to kano ckpool regardless of which node you mine on.

Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel
2% Fee Solo mining at solo.ckpool.org
-ck
kano (OP)
Legendary
*
Offline Offline

Activity: 4620
Merit: 1851


Linux since 1997 RedHat 4


View Profile
January 05, 2016, 12:20:52 PM
 #7227

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 Smiley

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

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

--

When using either of these servers as your first mining server, I'd recommend you use the main server as your first backup.
If the remote servers go down due to 'unforeseen circumstances' the main server may still be fine
(as a temporary solution until the remote server problem is resolved)

The reverse is actually also possible, but not as likely, that the remote server could be mining ok if the normal access to the main server is under attack, but the remote server connections are just out of the line of fire.

As mentioned earlier, all your shares to each server show up in the one place, on the main web site.

Pool: https://kano.is - low 0.5% fee PPLNS 3 Days - Most reliable Solo with ONLY 0.5% fee   Bitcointalk thread: Forum
Discord support invite at https://kano.is/ Majority developer of the ckpool code - k for kano
The ONLY active original developer of cgminer. Original master git: https://github.com/kanoi/cgminer
kano (OP)
Legendary
*
Offline Offline

Activity: 4620
Merit: 1851


Linux since 1997 RedHat 4


View Profile
January 05, 2016, 12:47:12 PM
 #7228

Payout 391757 sent
2fc05a4702bba96c6e42f6dd0c28b0a288474b3e674b285933f352effcbab53c
and confirmed

Pool: https://kano.is - low 0.5% fee PPLNS 3 Days - Most reliable Solo with ONLY 0.5% fee   Bitcointalk thread: Forum
Discord support invite at https://kano.is/ Majority developer of the ckpool code - k for kano
The ONLY active original developer of cgminer. Original master git: https://github.com/kanoi/cgminer
BannedDK
Member
**
Offline Offline

Activity: 109
Merit: 10


View Profile
January 05, 2016, 01:04:17 PM
 #7229

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 Smiley

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

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

--

When using either of these servers as your first mining server, I'd recommend you use the main server as your first backup.
If the remote servers go down due to 'unforeseen circumstances' the main server may still be fine
(as a temporary solution until the remote server problem is resolved)

The reverse is actually also possible, but not as likely, that the remote server could be mining ok if the normal access to the main server is under attack, but the remote server connections are just out of the line of fire.

As mentioned earlier, all your shares to each server show up in the one place, on the main web site.

Will the asic tubes Work on "de" server? I live in Denmark so im gonna switch over
-ck
Legendary
*
Offline Offline

Activity: 4284
Merit: 1645


Ruu \o/


View Profile WWW
January 05, 2016, 01:11:26 PM
 #7230

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.

Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel
2% Fee Solo mining at solo.ckpool.org
-ck
yxt
Legendary
*
Offline Offline

Activity: 3528
Merit: 1116



View Profile
January 05, 2016, 01:14:03 PM
 #7231

thx for the DE server  Smiley

BTCKano Pool██ ██
██ ██
██ ██
██ ██
██ ██
██ ██
██ ██
██ ██
██ ██
██
██
██
██
██ ██ ██
██ ██ ██
██ ██ ██
██ ██ ██
██ ██ ██
██ ██ ██
██ ██ ██
██ ██ ██
██ ██ ██
   ██
   ██
   ██
   ██
██ ██
██ ██
██ ██
██ ██
██ ██
██ ██
██ ██
██ ██
██ ██
   ██
   ██
   ██
   ██
zahzin
Newbie
*
Offline Offline

Activity: 41
Merit: 0


View Profile
January 05, 2016, 01:47:27 PM
 #7232

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 !
nhando
Full Member
***
Offline Offline

Activity: 196
Merit: 100


View Profile
January 05, 2016, 01:56:12 PM
 #7233

"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

Just "Mining" my own business.
-ck
Legendary
*
Offline Offline

Activity: 4284
Merit: 1645


Ruu \o/


View Profile WWW
January 05, 2016, 02:01:52 PM
 #7234

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

Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel
2% Fee Solo mining at solo.ckpool.org
-ck
nhando
Full Member
***
Offline Offline

Activity: 196
Merit: 100


View Profile
January 05, 2016, 02:06:10 PM
 #7235

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

Just "Mining" my own business.
coffeeangst
Newbie
*
Offline Offline

Activity: 20
Merit: 0


View Profile
January 05, 2016, 02:09:48 PM
 #7236


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.
wolfen
Hero Member
*****
Offline Offline

Activity: 770
Merit: 523


View Profile
January 05, 2016, 02:16:59 PM
 #7237

block baby!

For those about to block we salute you! AC->BTC
winspiral
Legendary
*
Offline Offline

Activity: 1778
Merit: 1026


Free WSPU2 Token or real dollars


View Profile WWW
January 05, 2016, 02:18:50 PM
 #7238

congratz!!!
now i'm rich.

bctmke
Sr. Member
****
Offline Offline

Activity: 294
Merit: 250


View Profile
January 05, 2016, 02:21:13 PM
 #7239

Remote nodes == better luck apparently!!  Bring on more blocks!

(I'm just kidding about the luck as that's not how it works Smiley)

NXS is on the move!   Come subscribe to our subreddit  https://www.reddit.com/r/nexusearth/
Come mine NXS at http://nxsminingpool.com
clgrissom3
Legendary
*
Offline Offline

Activity: 1722
Merit: 1032


Carl, aka Sonny :)


View Profile
January 05, 2016, 02:24:37 PM
 #7240

Kano CKPool and Solo CKPool with blocks back to back...
Pages: « 1 ... 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 [362] 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 ... 2250 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!