Boom and there's another one.
Thank you blockbot, love hearing from you. Let's hope it's another fat one
Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 55. (Read 5352119 times)
March 07, 2019, 10:10:25 PM
March 07, 2019, 10:09:53 PM
Block by 16vV8!
This is our 1st of BLOCK FRIDAY!
And 3 pretty quick blocks over the past 14 hours!
This is our 1st of BLOCK FRIDAY!
And 3 pretty quick blocks over the past 14 hours!
March 07, 2019, 01:03:59 PM
Nice to see 5x growth of this pool! Will we see 1000 Ph once?
March 07, 2019, 09:09:21 AM
our second block today! found by 16vV8JJ6rHFmo7gcNxDqyUb5wdpJVQkU7W
Nice! That's 16vV8's 2nd KanoPool Block on the Acclaim Board!
Big fat blocks this morning! This one is 13.488+ BTC!
March 07, 2019, 09:06:56 AM
our second block today! found by 16vV8JJ6rHFmo7gcNxDqyUb5wdpJVQkU7W a good sized one too 13.48852845 btc
March 07, 2019, 08:27:31 AM
Block by Fuzzy! 
Nice size too and 13.018704 BTC
Nice size too and 13.018704 BTC
Nice to see one of our regulars get another one
March 07, 2019, 08:15:24 AM
woohoo a block! good way to start Thursday!
March 07, 2019, 03:34:01 AM
Block by Fuzzy!
Nice size too and 13.018704 BTC
Nice size too and 13.018704 BTC
March 06, 2019, 04:18:44 AM
...
I still have problems with this stratum+tcp://or.kano.is:3333 (Oregon)
stratum+tcp://nya.kano.is:3333 (NewYork)
anyone else using oregonmines and which connection do you recommend from there
I've got machines at Oregon Mines and in Seattle, or.kano.is works well for me. Just slightly faster than the main stratum.kano.isI still have problems with this stratum+tcp://or.kano.is:3333 (Oregon)
stratum+tcp://nya.kano.is:3333 (NewYork)
anyone else using oregonmines and which connection do you recommend from there
and since we have a number of users in Oregon saying it works OK - thanks Yrth, rifleman74 and clgrissom3 - and specifically Yrth with miners in the same location, then I'd guess notabeliever's problem is at his end of the link.
I'd suggest trying one of the other ports instead of 3333
e.g. stratum+tcp://or.kano.is:80
and yes as clgrissom3 said, the next closest would be the main one
e.g. stratum+tcp://stratum.kano.is:80
As the home page says, instead of 3333, you can try any of 80, 81, 443 or 8080 also.
March 06, 2019, 03:59:07 AM
I've repointed the UK node to the NL node.
I was planning to do this at some stage anyway, but the UK node caused a failover at 08:40 UTC, so rather than chase down the provider, I simply switched the DNS for uk.kano.is to point to NL and the small number of users on UK were back online.
This is a permanent change, since the NL node is with my preferred provider who has so far been more reliable than all over providers (including AWS),
and their VPS are a lot faster
Mine on!
Edit: and anyone not sure what this means, you don't have to change anything, if your miners were on uk.kano.is they are now on nl.kano.is automagically
I still have problems with this stratum+tcp://or.kano.is:3333 (Oregon)I was planning to do this at some stage anyway, but the UK node caused a failover at 08:40 UTC, so rather than chase down the provider, I simply switched the DNS for uk.kano.is to point to NL and the small number of users on UK were back online.
This is a permanent change, since the NL node is with my preferred provider who has so far been more reliable than all over providers (including AWS),
and their VPS are a lot faster
Mine on!
Edit: and anyone not sure what this means, you don't have to change anything, if your miners were on uk.kano.is they are now on nl.kano.is automagically
stratum+tcp://nya.kano.is:3333 (NewYork)
anyone else using oregonmines and which connection do you recommend from there
March 05, 2019, 01:55:38 PM
...
I still have problems with this stratum+tcp://or.kano.is:3333 (Oregon)
stratum+tcp://nya.kano.is:3333 (NewYork)
anyone else using oregonmines and which connection do you recommend from there
Make sure there is no added whitespace at the beginning or end of the address. Very often when using copy/paste a space (whitespace) is added to the end of the string. I still have problems with this stratum+tcp://or.kano.is:3333 (Oregon)
stratum+tcp://nya.kano.is:3333 (NewYork)
anyone else using oregonmines and which connection do you recommend from there
March 05, 2019, 01:18:41 PM
I've repointed the UK node to the NL node.
I was planning to do this at some stage anyway, but the UK node caused a failover at 08:40 UTC, so rather than chase down the provider, I simply switched the DNS for uk.kano.is to point to NL and the small number of users on UK were back online.
This is a permanent change, since the NL node is with my preferred provider who has so far been more reliable than all over providers (including AWS),
and their VPS are a lot faster
Mine on!
Edit: and anyone not sure what this means, you don't have to change anything, if your miners were on uk.kano.is they are now on nl.kano.is automagically
I still have problems with this stratum+tcp://or.kano.is:3333 (Oregon)I was planning to do this at some stage anyway, but the UK node caused a failover at 08:40 UTC, so rather than chase down the provider, I simply switched the DNS for uk.kano.is to point to NL and the small number of users on UK were back online.
This is a permanent change, since the NL node is with my preferred provider who has so far been more reliable than all over providers (including AWS),
and their VPS are a lot faster
Mine on!
Edit: and anyone not sure what this means, you don't have to change anything, if your miners were on uk.kano.is they are now on nl.kano.is automagically
stratum+tcp://nya.kano.is:3333 (NewYork)
anyone else using oregonmines and which connection do you recommend from there
It works for me and has. You have a correct user name? And no spaces in the address or user name?
March 05, 2019, 11:08:40 AM
I've repointed the UK node to the NL node.
I was planning to do this at some stage anyway, but the UK node caused a failover at 08:40 UTC, so rather than chase down the provider, I simply switched the DNS for uk.kano.is to point to NL and the small number of users on UK were back online.
This is a permanent change, since the NL node is with my preferred provider who has so far been more reliable than all over providers (including AWS),
and their VPS are a lot faster
Mine on!
Edit: and anyone not sure what this means, you don't have to change anything, if your miners were on uk.kano.is they are now on nl.kano.is automagically
I still have problems with this stratum+tcp://or.kano.is:3333 (Oregon)I was planning to do this at some stage anyway, but the UK node caused a failover at 08:40 UTC, so rather than chase down the provider, I simply switched the DNS for uk.kano.is to point to NL and the small number of users on UK were back online.
This is a permanent change, since the NL node is with my preferred provider who has so far been more reliable than all over providers (including AWS),
and their VPS are a lot faster
Mine on!
Edit: and anyone not sure what this means, you don't have to change anything, if your miners were on uk.kano.is they are now on nl.kano.is automagically
stratum+tcp://nya.kano.is:3333 (NewYork)
anyone else using oregonmines and which connection do you recommend from there
Are you saying you have problems with both OR and NYA?
I don't use oregonmines but my host site is in Washington state and I get the least latency with OR and then the main statum. NYA is 3rd for me. Have you tried using stratum+tcp://stratum.kano.is:3333?
March 05, 2019, 09:41:26 AM
I've repointed the UK node to the NL node.
I was planning to do this at some stage anyway, but the UK node caused a failover at 08:40 UTC, so rather than chase down the provider, I simply switched the DNS for uk.kano.is to point to NL and the small number of users on UK were back online.
This is a permanent change, since the NL node is with my preferred provider who has so far been more reliable than all over providers (including AWS),
and their VPS are a lot faster
Mine on!
Edit: and anyone not sure what this means, you don't have to change anything, if your miners were on uk.kano.is they are now on nl.kano.is automagically
I still have problems with this stratum+tcp://or.kano.is:3333 (Oregon)I was planning to do this at some stage anyway, but the UK node caused a failover at 08:40 UTC, so rather than chase down the provider, I simply switched the DNS for uk.kano.is to point to NL and the small number of users on UK were back online.
This is a permanent change, since the NL node is with my preferred provider who has so far been more reliable than all over providers (including AWS),
and their VPS are a lot faster
Mine on!
Edit: and anyone not sure what this means, you don't have to change anything, if your miners were on uk.kano.is they are now on nl.kano.is automagically
stratum+tcp://nya.kano.is:3333 (NewYork)
anyone else using oregonmines and which connection do you recommend from there
March 05, 2019, 04:06:27 AM
I've repointed the UK node to the NL node.
I was planning to do this at some stage anyway, but the UK node caused a failover at 08:40 UTC, so rather than chase down the provider, I simply switched the DNS for uk.kano.is to point to NL and the small number of users on UK were back online.
This is a permanent change, since the NL node is with my preferred provider who has so far been more reliable than all over providers (including AWS),
and their VPS are a lot faster
Mine on!
Edit: and anyone not sure what this means, you don't have to change anything, if your miners were on uk.kano.is they are now on nl.kano.is automagically
I was planning to do this at some stage anyway, but the UK node caused a failover at 08:40 UTC, so rather than chase down the provider, I simply switched the DNS for uk.kano.is to point to NL and the small number of users on UK were back online.
This is a permanent change, since the NL node is with my preferred provider who has so far been more reliable than all over providers (including AWS),
and their VPS are a lot faster
Mine on!
Edit: and anyone not sure what this means, you don't have to change anything, if your miners were on uk.kano.is they are now on nl.kano.is automagically
March 04, 2019, 09:33:24 PM
lol did you see my screenshot above from today though? 227 blocks found on 2/27 and the block from 3/1 - none of which is actually on Kano.is pool - I mean I would love to see us have 227 blocks in a single day lol
I upgraded to mariadb 10.3 last week and discovered that there are several changes that caused some non factual results. I worked on solving the issues today and will fix the block issues tomorrow. Yes, I too would love anywhere near those results!. Mine on with Kano!
March 04, 2019, 11:50:21 AM
Hmm, actually not sure why no one noticed this on the graph posted above a number of days ago from minergain,
but the 12 months going from Feb this year back to March last year has us higher than both slush and viabtc ...
The reason the 13 months including Feb last year was lower (but not much lower) was coz Feb last year was the lowest luck % month on the pool over all time.
So including that as the start point will push the total down.
... and FYI Mar last year isn't the highest, the 2 highest are Nov 2014 and Apr 2017
but the 12 months going from Feb this year back to March last year has us higher than both slush and viabtc ...
The reason the 13 months including Feb last year was lower (but not much lower) was coz Feb last year was the lowest luck % month on the pool over all time.
So including that as the start point will push the total down.
... and FYI Mar last year isn't the highest, the 2 highest are Nov 2014 and Apr 2017
I did notice that
but the graph was posted primarily to show that it pretty much ends up even there are months where one is higher than the other then it flips and now the one that was lower is higher and vice versa. what I like about kano.is is the community of users and hope for hitting a ton of blocks in a single day/week/month lol did you see my screenshot above from today though? 227 blocks found on 2/27 and the block from 3/1 - none of which is actually on Kano.is pool - I mean I would love to see us have 227 blocks in a single day lol
March 04, 2019, 11:16:01 AM
Hmm, actually not sure why no one noticed this on the graph posted above a number of days ago from minergain,
but the 12 months going from Feb this year back to March last year has us higher than both slush and viabtc ...
The reason the 13 months including Feb last year was lower (but not much lower) was coz Feb last year was the lowest luck % month on the pool over all time.
So including that as the start point will push the total down.
... and FYI Mar last year isn't the highest, the 2 highest are Nov 2014 and Apr 2017
but the 12 months going from Feb this year back to March last year has us higher than both slush and viabtc ...
The reason the 13 months including Feb last year was lower (but not much lower) was coz Feb last year was the lowest luck % month on the pool over all time.
So including that as the start point will push the total down.
... and FYI Mar last year isn't the highest, the 2 highest are Nov 2014 and Apr 2017
March 04, 2019, 11:01:59 AM
lol oooh how I wish Minergain was right about this - look at 2/27/2019, says 277 blocks found.
also I for the 3/1/2019 block --- I believe our last block was 2/25/2019
also I for the 3/1/2019 block --- I believe our last block was 2/25/2019
February 26, 2019, 10:13:50 PM
Block! by the new guy xasmer - welcome to the acclaim board!
Ahhh, the power of PPLNS! February is now 0.00005216 BTC/Day/TH
Yeah, not bad at all!!! Don’t you wish it was like that every month?
So anyone mining slush instead of here lost out ... though I still wonder how that is possible, but the numbers are the numbers
Yep, in Slush I’m sure they did miss out
Jump to: