Thanks
Topic: Where to mine with 36Ths 24/7? (Read 1942 times)
This is my last configuration. I have the best ping with de.kano.is then nl.kano.is then stratum.kano.is that way I configured.
Thanks
Thanks
My final decision is I will leave my miners at first pool kano.is for one month and will update.
These are my configuration of my miners atm and will be for one month.
0 stratum+tcp://stratum.kano.is:3333
1 stratum+tcp://stratum.antpool.com:443
2 stratum+tcp://stratum.antpool.com:25
Thanks
These are my configuration of my miners atm and will be for one month.
0 stratum+tcp://stratum.kano.is:3333
1 stratum+tcp://stratum.antpool.com:443
2 stratum+tcp://stratum.antpool.com:25
Thanks
Depending on where you are located, kano's pool has other locations that may be a better option for you. The best way to figure out which one works best (i.e.: is closest) for you is to ping them and check the response times.
Kano's nodes are:
- US: stratum.kano.is
- US: nya.kano.is
- DE: de.kano.is
- SG: sg.kano.is
- JP: jp.kano.is
- NL: nl.kano.is
and all of the nodes listen on these ports:
- 3333
- 80
- 81
- 443
- 8080
in case you have issues getting through firewalls.
I live in the US on the east coast so I'd consider using stratum.kano.is and nya.kano.is:
Code:
ping -c 10 stratum.kano.is
PING stratum.kano.is (104.194.28.194): 56 data bytes
64 bytes from 104.194.28.194: icmp_seq=0 ttl=54 time=100.933 ms
64 bytes from 104.194.28.194: icmp_seq=1 ttl=54 time=100.200 ms
64 bytes from 104.194.28.194: icmp_seq=2 ttl=54 time=100.376 ms
64 bytes from 104.194.28.194: icmp_seq=3 ttl=54 time=100.377 ms
64 bytes from 104.194.28.194: icmp_seq=4 ttl=54 time=100.882 ms
64 bytes from 104.194.28.194: icmp_seq=5 ttl=54 time=100.505 ms
64 bytes from 104.194.28.194: icmp_seq=6 ttl=54 time=100.561 ms
64 bytes from 104.194.28.194: icmp_seq=7 ttl=54 time=100.863 ms
64 bytes from 104.194.28.194: icmp_seq=8 ttl=54 time=100.172 ms
64 bytes from 104.194.28.194: icmp_seq=9 ttl=54 time=100.743 ms
--- stratum.kano.is ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 100.172/100.561/100.933/0.268 ms
Code:
ping -c 10 nya.kano.is
PING nya.kano.is (104.207.132.42): 56 data bytes
64 bytes from 104.207.132.42: icmp_seq=0 ttl=53 time=34.476 ms
64 bytes from 104.207.132.42: icmp_seq=1 ttl=54 time=34.157 ms
64 bytes from 104.207.132.42: icmp_seq=2 ttl=54 time=34.907 ms
64 bytes from 104.207.132.42: icmp_seq=3 ttl=54 time=34.257 ms
64 bytes from 104.207.132.42: icmp_seq=4 ttl=54 time=35.185 ms
64 bytes from 104.207.132.42: icmp_seq=5 ttl=54 time=34.080 ms
64 bytes from 104.207.132.42: icmp_seq=6 ttl=54 time=34.635 ms
64 bytes from 104.207.132.42: icmp_seq=7 ttl=53 time=33.699 ms
64 bytes from 104.207.132.42: icmp_seq=8 ttl=54 time=34.291 ms
64 bytes from 104.207.132.42: icmp_seq=9 ttl=53 time=33.556 ms
--- nya.kano.is ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 33.556/34.324/35.185/0.477 ms
So for me it would be better to use nya.kano.is, but I would then put one of the other nodes as a backup pool, and then for my third pool pick a different pool altogether, and now knowing what I know about p2pool, I'd use one of the public p2pool nodes.
edit: added port info
Best ping i get is from de.kano.is with time=37 ms
Should i configure it with stratum.de.kano.is:3333 ?
My final decision is I will leave my miners at first pool kano.is for one month and will update.
These are my configuration of my miners atm and will be for one month.
0 stratum+tcp://stratum.kano.is:3333
1 stratum+tcp://stratum.antpool.com:443
2 stratum+tcp://stratum.antpool.com:25
Thanks
These are my configuration of my miners atm and will be for one month.
0 stratum+tcp://stratum.kano.is:3333
1 stratum+tcp://stratum.antpool.com:443
2 stratum+tcp://stratum.antpool.com:25
Thanks
Depending on where you are located, kano's pool has other locations that may be a better option for you. The best way to figure out which one works best (i.e.: is closest) for you is to ping them and check the response times.
Kano's nodes are:
- US: stratum.kano.is
- US: nya.kano.is
- DE: de.kano.is
- SG: sg.kano.is
- JP: jp.kano.is
- NL: nl.kano.is
and all of the nodes listen on these ports:
- 3333
- 80
- 81
- 443
- 8080
in case you have issues getting through firewalls.
I live in the US on the east coast so I'd consider using stratum.kano.is and nya.kano.is:
Code:
ping -c 10 stratum.kano.is
PING stratum.kano.is (104.194.28.194): 56 data bytes
64 bytes from 104.194.28.194: icmp_seq=0 ttl=54 time=100.933 ms
64 bytes from 104.194.28.194: icmp_seq=1 ttl=54 time=100.200 ms
64 bytes from 104.194.28.194: icmp_seq=2 ttl=54 time=100.376 ms
64 bytes from 104.194.28.194: icmp_seq=3 ttl=54 time=100.377 ms
64 bytes from 104.194.28.194: icmp_seq=4 ttl=54 time=100.882 ms
64 bytes from 104.194.28.194: icmp_seq=5 ttl=54 time=100.505 ms
64 bytes from 104.194.28.194: icmp_seq=6 ttl=54 time=100.561 ms
64 bytes from 104.194.28.194: icmp_seq=7 ttl=54 time=100.863 ms
64 bytes from 104.194.28.194: icmp_seq=8 ttl=54 time=100.172 ms
64 bytes from 104.194.28.194: icmp_seq=9 ttl=54 time=100.743 ms
--- stratum.kano.is ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 100.172/100.561/100.933/0.268 ms
Code:
ping -c 10 nya.kano.is
PING nya.kano.is (104.207.132.42): 56 data bytes
64 bytes from 104.207.132.42: icmp_seq=0 ttl=53 time=34.476 ms
64 bytes from 104.207.132.42: icmp_seq=1 ttl=54 time=34.157 ms
64 bytes from 104.207.132.42: icmp_seq=2 ttl=54 time=34.907 ms
64 bytes from 104.207.132.42: icmp_seq=3 ttl=54 time=34.257 ms
64 bytes from 104.207.132.42: icmp_seq=4 ttl=54 time=35.185 ms
64 bytes from 104.207.132.42: icmp_seq=5 ttl=54 time=34.080 ms
64 bytes from 104.207.132.42: icmp_seq=6 ttl=54 time=34.635 ms
64 bytes from 104.207.132.42: icmp_seq=7 ttl=53 time=33.699 ms
64 bytes from 104.207.132.42: icmp_seq=8 ttl=54 time=34.291 ms
64 bytes from 104.207.132.42: icmp_seq=9 ttl=53 time=33.556 ms
--- nya.kano.is ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 33.556/34.324/35.185/0.477 ms
So for me it would be better to use nya.kano.is, but I would then put one of the other nodes as a backup pool, and then for my third pool pick a different pool altogether, and now knowing what I know about p2pool, I'd use one of the public p2pool nodes.
edit: added port info
I'm gonna do this today and will let you know.
You guys are the best.
Thanks
Questions/answers about the pool would be best in the pool thread 
So anyone with the same question might see the answer
https://bitcointalksearch.org/topic/kanopool-kanois-lowest-09-fee-since-2014-worldwide-2432-blocks-789369
So anyone with the same question might see the answer
https://bitcointalksearch.org/topic/kanopool-kanois-lowest-09-fee-since-2014-worldwide-2432-blocks-789369
LOL. Agreed.
I will be moving my miners back to Kano in a couple weeks after my current experiment. It will be nice to use a node closer to home. NYA should be very good for my ping time. See ya'll again soon!
Questions/answers about the pool would be best in the pool thread
So anyone with the same question might see the answer
https://bitcointalksearch.org/topic/kanopool-kanois-lowest-09-fee-since-2014-worldwide-2432-blocks-789369
So anyone with the same question might see the answer
https://bitcointalksearch.org/topic/kanopool-kanois-lowest-09-fee-since-2014-worldwide-2432-blocks-789369
Kano's nodes are:
I live in the US on the east coast so I'd consider using stratum.kano.is and nya.kano.is:
So for me it would be better to use nya.kano.is, but I would then put one of the other nodes as a backup pool, and then for my third pool pick a different pool altogether, and now knowing what I know about p2pool, I'd use one of the public p2pool nodes.
- US: stratum.kano.is
- US: nya.kano.is
- DE: de.kano.is
- SG: sg.kano.is
- JP: jp.kano.is
- NL: nl.kano.is
I live in the US on the east coast so I'd consider using stratum.kano.is and nya.kano.is:
So for me it would be better to use nya.kano.is, but I would then put one of the other nodes as a backup pool, and then for my third pool pick a different pool altogether, and now knowing what I know about p2pool, I'd use one of the public p2pool nodes.
I was unaware Kano has two nodes in the US. Is the NYA node new? Does that stand for New York area or something to that effect? I'm on the East coast also.
Thanks!
Yes. He added it in December:
https://bitcointalksearch.org/topic/m.17238254
Thanks much!!
Kano's nodes are:
I live in the US on the east coast so I'd consider using stratum.kano.is and nya.kano.is:
So for me it would be better to use nya.kano.is, but I would then put one of the other nodes as a backup pool, and then for my third pool pick a different pool altogether, and now knowing what I know about p2pool, I'd use one of the public p2pool nodes.
- US: stratum.kano.is
- US: nya.kano.is
- DE: de.kano.is
- SG: sg.kano.is
- JP: jp.kano.is
- NL: nl.kano.is
I live in the US on the east coast so I'd consider using stratum.kano.is and nya.kano.is:
So for me it would be better to use nya.kano.is, but I would then put one of the other nodes as a backup pool, and then for my third pool pick a different pool altogether, and now knowing what I know about p2pool, I'd use one of the public p2pool nodes.
I was unaware Kano has two nodes in the US. Is the NYA node new? Does that stand for New York area or something to that effect? I'm on the East coast also.
Thanks!
Yes. He added it in December:
https://bitcointalksearch.org/topic/m.17238254
Kano's nodes are:
I live in the US on the east coast so I'd consider using stratum.kano.is and nya.kano.is:
So for me it would be better to use nya.kano.is, but I would then put one of the other nodes as a backup pool, and then for my third pool pick a different pool altogether, and now knowing what I know about p2pool, I'd use one of the public p2pool nodes.
- US: stratum.kano.is
- US: nya.kano.is
- DE: de.kano.is
- SG: sg.kano.is
- JP: jp.kano.is
- NL: nl.kano.is
I live in the US on the east coast so I'd consider using stratum.kano.is and nya.kano.is:
So for me it would be better to use nya.kano.is, but I would then put one of the other nodes as a backup pool, and then for my third pool pick a different pool altogether, and now knowing what I know about p2pool, I'd use one of the public p2pool nodes.
I was unaware Kano has two nodes in the US. Is the NYA node new? Does that stand for New York area or something to that effect? I'm on the East coast also.
Thanks!
My final decision is I will leave my miners at first pool kano.is for one month and will update.
These are my configuration of my miners atm and will be for one month.
0 stratum+tcp://stratum.kano.is:3333
1 stratum+tcp://stratum.antpool.com:443
2 stratum+tcp://stratum.antpool.com:25
Thanks
These are my configuration of my miners atm and will be for one month.
0 stratum+tcp://stratum.kano.is:3333
1 stratum+tcp://stratum.antpool.com:443
2 stratum+tcp://stratum.antpool.com:25
Thanks
Depending on where you are located, kano's pool has other locations that may be a better option for you. The best way to figure out which one works best (i.e.: is closest) for you is to ping them and check the response times.
Kano's nodes are:
- US: stratum.kano.is
- US: nya.kano.is
- DE: de.kano.is
- SG: sg.kano.is
- JP: jp.kano.is
- NL: nl.kano.is
and all of the nodes listen on these ports:
- 3333
- 80
- 81
- 443
- 8080
in case you have issues getting through firewalls.
I live in the US on the east coast so I'd consider using stratum.kano.is and nya.kano.is:
Code:
ping -c 10 stratum.kano.is
PING stratum.kano.is (104.194.28.194): 56 data bytes
64 bytes from 104.194.28.194: icmp_seq=0 ttl=54 time=100.933 ms
64 bytes from 104.194.28.194: icmp_seq=1 ttl=54 time=100.200 ms
64 bytes from 104.194.28.194: icmp_seq=2 ttl=54 time=100.376 ms
64 bytes from 104.194.28.194: icmp_seq=3 ttl=54 time=100.377 ms
64 bytes from 104.194.28.194: icmp_seq=4 ttl=54 time=100.882 ms
64 bytes from 104.194.28.194: icmp_seq=5 ttl=54 time=100.505 ms
64 bytes from 104.194.28.194: icmp_seq=6 ttl=54 time=100.561 ms
64 bytes from 104.194.28.194: icmp_seq=7 ttl=54 time=100.863 ms
64 bytes from 104.194.28.194: icmp_seq=8 ttl=54 time=100.172 ms
64 bytes from 104.194.28.194: icmp_seq=9 ttl=54 time=100.743 ms
--- stratum.kano.is ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 100.172/100.561/100.933/0.268 ms
PING stratum.kano.is (104.194.28.194): 56 data bytes
64 bytes from 104.194.28.194: icmp_seq=0 ttl=54 time=100.933 ms
64 bytes from 104.194.28.194: icmp_seq=1 ttl=54 time=100.200 ms
64 bytes from 104.194.28.194: icmp_seq=2 ttl=54 time=100.376 ms
64 bytes from 104.194.28.194: icmp_seq=3 ttl=54 time=100.377 ms
64 bytes from 104.194.28.194: icmp_seq=4 ttl=54 time=100.882 ms
64 bytes from 104.194.28.194: icmp_seq=5 ttl=54 time=100.505 ms
64 bytes from 104.194.28.194: icmp_seq=6 ttl=54 time=100.561 ms
64 bytes from 104.194.28.194: icmp_seq=7 ttl=54 time=100.863 ms
64 bytes from 104.194.28.194: icmp_seq=8 ttl=54 time=100.172 ms
64 bytes from 104.194.28.194: icmp_seq=9 ttl=54 time=100.743 ms
--- stratum.kano.is ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 100.172/100.561/100.933/0.268 ms
Code:
ping -c 10 nya.kano.is
PING nya.kano.is (104.207.132.42): 56 data bytes
64 bytes from 104.207.132.42: icmp_seq=0 ttl=53 time=34.476 ms
64 bytes from 104.207.132.42: icmp_seq=1 ttl=54 time=34.157 ms
64 bytes from 104.207.132.42: icmp_seq=2 ttl=54 time=34.907 ms
64 bytes from 104.207.132.42: icmp_seq=3 ttl=54 time=34.257 ms
64 bytes from 104.207.132.42: icmp_seq=4 ttl=54 time=35.185 ms
64 bytes from 104.207.132.42: icmp_seq=5 ttl=54 time=34.080 ms
64 bytes from 104.207.132.42: icmp_seq=6 ttl=54 time=34.635 ms
64 bytes from 104.207.132.42: icmp_seq=7 ttl=53 time=33.699 ms
64 bytes from 104.207.132.42: icmp_seq=8 ttl=54 time=34.291 ms
64 bytes from 104.207.132.42: icmp_seq=9 ttl=53 time=33.556 ms
--- nya.kano.is ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 33.556/34.324/35.185/0.477 ms
PING nya.kano.is (104.207.132.42): 56 data bytes
64 bytes from 104.207.132.42: icmp_seq=0 ttl=53 time=34.476 ms
64 bytes from 104.207.132.42: icmp_seq=1 ttl=54 time=34.157 ms
64 bytes from 104.207.132.42: icmp_seq=2 ttl=54 time=34.907 ms
64 bytes from 104.207.132.42: icmp_seq=3 ttl=54 time=34.257 ms
64 bytes from 104.207.132.42: icmp_seq=4 ttl=54 time=35.185 ms
64 bytes from 104.207.132.42: icmp_seq=5 ttl=54 time=34.080 ms
64 bytes from 104.207.132.42: icmp_seq=6 ttl=54 time=34.635 ms
64 bytes from 104.207.132.42: icmp_seq=7 ttl=53 time=33.699 ms
64 bytes from 104.207.132.42: icmp_seq=8 ttl=54 time=34.291 ms
64 bytes from 104.207.132.42: icmp_seq=9 ttl=53 time=33.556 ms
--- nya.kano.is ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 33.556/34.324/35.185/0.477 ms
So for me it would be better to use nya.kano.is, but I would then put one of the other nodes as a backup pool, and then for my third pool pick a different pool altogether, and now knowing what I know about p2pool, I'd use one of the public p2pool nodes.
edit: added port info
Ive gone back to P2POOL mining, where I started a good while ago.
Ive mined at kano.is for a good few months this year, hit on their lucky streak and it paid very well.
Its a great pool, kano is a true professional and the pool is well run.
I just cant keep away from p2pool though.
I run my own p2pool node in the same building as my miners so p2pool is kind of running your own pool, nearly.
I have to keep an eye on the node (running under Centos as I love linux) and you can tweak things with bitcoind and p2pool.
So you do have some work to do almost as your own system admin.
Payouts are varied. At the moment the pool gets a block in the region of three to four days between so variance is large.
Could be longer, could be shorter. Who knows.
Its almost solo mining but not exactly if that makes any sense.
Payouts are slightly more than I normally earn on any other pool.
The slightly more makes it worth my while.
Incidentally i am running 2 X S7's and 2 X S9's, same as you.
If the variance doesn't bother you and you don't mind waiting a while for a payout, p2pool is probably the way to go.
Its tempting to jump ship after a couple of days but if you work out everything you earn over say six months, it should (normally does) just earn that little bit more.
With p2pool patience is definitely a virtue.
Ive mined at kano.is for a good few months this year, hit on their lucky streak and it paid very well.
Its a great pool, kano is a true professional and the pool is well run.
I just cant keep away from p2pool though.
I run my own p2pool node in the same building as my miners so p2pool is kind of running your own pool, nearly.
I have to keep an eye on the node (running under Centos as I love linux) and you can tweak things with bitcoind and p2pool.
So you do have some work to do almost as your own system admin.
Payouts are varied. At the moment the pool gets a block in the region of three to four days between so variance is large.
Could be longer, could be shorter. Who knows.
Its almost solo mining but not exactly if that makes any sense.
Payouts are slightly more than I normally earn on any other pool.
The slightly more makes it worth my while.
Incidentally i am running 2 X S7's and 2 X S9's, same as you.
If the variance doesn't bother you and you don't mind waiting a while for a payout, p2pool is probably the way to go.
Its tempting to jump ship after a couple of days but if you work out everything you earn over say six months, it should (normally does) just earn that little bit more.
With p2pool patience is definitely a virtue.
My final decision is I will leave my miners at first pool kano.is for one month and will update.
These are my configuration of my miners atm and will be for one month.
0 stratum+tcp://stratum.kano.is:3333
1 stratum+tcp://stratum.antpool.com:443
2 stratum+tcp://stratum.antpool.com:25
Thanks
These are my configuration of my miners atm and will be for one month.
0 stratum+tcp://stratum.kano.is:3333
1 stratum+tcp://stratum.antpool.com:443
2 stratum+tcp://stratum.antpool.com:25
Thanks
Wise decision!
The main point when making deceisions is to avoid CHINESE pools at all cost.
Good luck to you
My final decision is I will leave my miners at first pool kano.is for one month and will update.
These are my configuration of my miners atm and will be for one month.
0 stratum+tcp://stratum.kano.is:3333
1 stratum+tcp://stratum.antpool.com:443
2 stratum+tcp://stratum.antpool.com:25
Thanks
These are my configuration of my miners atm and will be for one month.
0 stratum+tcp://stratum.kano.is:3333
1 stratum+tcp://stratum.antpool.com:443
2 stratum+tcp://stratum.antpool.com:25
Thanks
If you have 36TH and are considering investing to double or triple your capacity but don't know some fundamentals about pools, their pay out structures and operational procedures.
May I suggest you take some time and research everything, understand it properly. Don't take the word of people on a forum who you don't know. Whether the advice is good or bad, you should still do some ground work and understand the business yourself before embarking on the adventure. Make sense ?
May I suggest you take some time and research everything, understand it properly. Don't take the word of people on a forum who you don't know. Whether the advice is good or bad, you should still do some ground work and understand the business yourself before embarking on the adventure. Make sense ?
No one has mention Slush (slushpool.com) -- their fees are a little higher than Kano; however, they do signal segwit (if that is important for you) -- and you can set payout thresholds rather than receiving many small amount payouts. They also have a very user friendly interface.
I also like Kano (with the two exceptions that I stated above).
Bitminter is a terrific pool with unfortunate low hash rate -- I wish he could pick up a couple of big hashers, I'd move my machines over to his pool in a heartbeat if he could somehow attract a higher base hash.
And, as someone previously mentioned, Johnny Bravo runs an awesome pool (bravo-mining.com) and has super cool contests. For some reason, I have connectivity issues with his pool that we haven't been able to figure out -- even though he spent a couple of hours with me one day on IIRC trying to trouble shoot.
I also like Kano (with the two exceptions that I stated above).
Bitminter is a terrific pool with unfortunate low hash rate -- I wish he could pick up a couple of big hashers, I'd move my machines over to his pool in a heartbeat if he could somehow attract a higher base hash.
And, as someone previously mentioned, Johnny Bravo runs an awesome pool (bravo-mining.com) and has super cool contests. For some reason, I have connectivity issues with his pool that we haven't been able to figure out -- even though he spent a couple of hours with me one day on IIRC trying to trouble shoot.
Do you understand how the PPLNS payout method works?
To be honest not really
.PPLNS is a "Hop Proof" payout method. Here is a link to a good explanation.
https://kano.is/index.php?k=payout
When you start mining your shares are stored in shifts. When a block is found the payout is distributed among a certain number of those shifts. At first you don't have shares in all of the shifts that get paid so you don't get paid for shifts that you didn't contribute shares to. So over time, 3 to 4 days, you contribute shares to all shifts that are being paid and when a block is found you then get a full payment for all open shifts. If luck is good then the payment will be better. When you stop mining the past shifts that you contributed to continue to get paid for 3 or so days. So the ramp up and ramp down even out.
With PPLNS it is possible to get paid better than 100% if luck is good. With PPS you get paid a flat rate which is 100% minus a the fee, which will always be less than a 100%.
Do you understand how the PPLNS payout method works?
To be honest not really
.
Do you understand how the PPLNS payout method works?
I pointed all 4 of my miners 36/THS at kano.is I will leave it for 4+1 = 5 days and let's see I hope for best and trusting on good review of kano.is got at bitcointalk.
If it will better ofc I will continue mining at kano.
Thanks
[/quote]
That's kind of pointless since it takes5 4 days to start getting maximum rewards on kano.is ckpool.
[/quote]
And he'll continue to get new rewards for blocks found for ~4 days after he stops mining on kano.is
[/quote]
If it will better ofc I will continue mining at kano.
Thanks
[/quote]
That's kind of pointless since it takes
[/quote]
And he'll continue to get new rewards for blocks found for ~4 days after he stops mining on kano.is
[/quote]
I did split my ths equal to antpool and ckpool. I will leave it for 3 days to see how it goes.
60ths is enough to have my own pool or what should be enough. I'm planing to extend soon even more.
Thanks for your time.
That's kind of pointless since it takes 60ths is enough to have my own pool or what should be enough. I'm planing to extend soon even more.
Thanks for your time.
I did split my ths equal to antpool and ckpool. I will leave it for 3 days to see how it goes.
60ths is enough to have my own pool or what should be enough. I'm planing to extend soon even more.
Thanks for your time.
That's kind of pointless since it takes 5 days to start getting maximum rewards on kano.is ckpool. 60ths is enough to have my own pool or what should be enough. I'm planing to extend soon even more.
Thanks for your time.
Jump to: