Author

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

legendary
Activity: 1500
Merit: 1002
Mine Mine Mine
is the frontend working for you guys ?
legendary
Activity: 4354
Merit: 9201
'The right to privacy matters'
I put BTC in my NH wallet with only one confirmation from coinbase. eeek!

It's been really bogged down today! It took about 2 hours for my deposit to reach 2 confirmations - not unheard of but definitely longer than normal.

The last two payments from Kano are still sitting in my wallet waffling between "unverified" and 0 confirmations...  Undecided

this is good news not bad news.  it translates to a negative difficulty increase.

and as long as coin prices stay over 420 usd .  I will take a - diff adjustment over and over and over .

I would love to see a stretch like this below

Jun 28 2015   49,402,014,931   -0.58%   353,633,397 GH/s
Jun 14 2015   49,692,386,355   4.42%   355,711,957 GH/s
May 31 2015   47,589,591,154   -2.50%   340,659,563 GH/s
May 17 2015   48,807,487,245   2.44%   349,377,603 GH/s
May 03 2015   47,643,398,018   0.07%   341,044,727 GH/s
Apr 19 2015   47,610,564,513   -3.71%   340,809,696 GH/s
Apr 05 2015   49,446,390,688   5.84%   353,951,052 GH/s

from april 5 2015 to June 28 2015   more then 80 days and we dropped about ½ of 1 %

and since the jump after june 28 was july 11

we did 97 days at about - 0.5%

price on april 5th was 259 price on july 12 was 314.

I would love for us  to do 90 days with -0.5% in diff and +20% in price.
member
Activity: 84
Merit: 10
I put BTC in my NH wallet with only one confirmation from coinbase. eeek!

It's been really bogged down today! It took about 2 hours for my deposit to reach 2 confirmations - not unheard of but definitely longer than normal.

The last two payments from Kano are still sitting in my wallet waffling between "unverified" and 0 confirmations...  Undecided
member
Activity: 84
Merit: 10
Yep, my NH rental kicked down to the red area at 3am for 4 hours.
I cancelled it and resubmitted it. The new rental has also been stuck for 4 hours.

WBF1, thanks for the 2048 diff tip. That fixed the stuck NH rental on kano after restarting the rental.
Kano, I wonder why this changed? The difficulty on the workers management page?  AAAHHH!

Anyone have issues connecting NiceHash rental to Kano pool today?  Tried stratum 80, 81, and 3333 still no luck

I'm not sure if this is new, but you need to increase minimum difficulty to 2048 for your nicehash worker in the kano.is workers page.

After that, you probably need to restart your rental.


I saw reference to changing worker diff but thought it needs to be done at NH side which is greyed out. That works.  Thanks!

from what I can tell, the diff setting on NH shows 127 => 2048 which means diff can start at 127 as long as it increases to 2048 after some time.

problem might have occurred if workers disconnected from the pool, pool started difficulty extremely low (below 127) and never tried to increase it because no work was being done. Just one of those weird hiccups that can happen. also possible something happened pool side that reset min diff settings for workers, but kano or ck would have to confirm that. all is good now though. just make sure any nh workers have a min diff in the pool settings of 2048.

Yeah - this is what worked for me as well. They'd been in the red for hours which didn't seem right, even after canceling/resubmitting. Once I tried the pool verificator on the NH site it said everything was fine, but also popped out a message at the bottom of the page saying that the minimum diff at the pool was too low. When I set my worker diff on the pool to 2048 it fixed everything almost instantly - didn't even need to cancel and resubmit. Just seemed odd since this has never happened before with many pool restarts and other disconnects for whatever reason.

Glad to hear that everyone else was able to fix theirs by doing this. I'm pretty hesitant to mess with the pool worker diff settings - I guess something on the NH end changed though, so at least this fixed the issue.
hero member
Activity: 770
Merit: 523
I put BTC in my NH wallet with only one confirmation from coinbase. eeek!
sr. member
Activity: 419
Merit: 250
Yep, my NH rental kicked down to the red area at 3am for 4 hours.
I cancelled it and resubmitted it. The new rental has also been stuck for 4 hours.

WBF1, thanks for the 2048 diff tip. That fixed the stuck NH rental on kano after restarting the rental.
Kano, I wonder why this changed? The difficulty on the workers management page?  AAAHHH!

Anyone have issues connecting NiceHash rental to Kano pool today?  Tried stratum 80, 81, and 3333 still no luck

I'm not sure if this is new, but you need to increase minimum difficulty to 2048 for your nicehash worker in the kano.is workers page.

After that, you probably need to restart your rental.


I saw reference to changing worker diff but thought it needs to be done at NH side which is greyed out. That works.  Thanks!

from what I can tell, the diff setting on NH shows 127 => 2048 which means diff can start at 127 as long as it increases to 2048 after some time.

problem might have occurred if workers disconnected from the pool, pool started difficulty extremely low (below 127) and never tried to increase it because no work was being done. Just one of those weird hiccups that can happen. also possible something happened pool side that reset min diff settings for workers, but kano or ck would have to confirm that. all is good now though. just make sure any nh workers have a min diff in the pool settings of 2048.
sr. member
Activity: 294
Merit: 250
Love coming in on a Monday to a pile of blocks from the weekend and a new competition starting up!
sr. member
Activity: 414
Merit: 251
Anyone have issues connecting NiceHash rental to Kano pool today?  Tried stratum 80, 81, and 3333 still no luck

I'm not sure if this is new, but you need to increase minimum difficulty to 2048 for your nicehash worker in the kano.is workers page.

After that, you probably need to restart your rental.


I saw reference to changing worker diff but thought it needs to be done at NH side which is greyed out. That works.  Thanks!
hero member
Activity: 770
Merit: 523
Yep, my NH rental kicked down to the red area at 3am for 4 hours.
I cancelled it and resubmitted it. The new rental has also been stuck for 4 hours.

WBF1, thanks for the 2048 diff tip. That fixed the stuck NH rental on kano after restarting the rental.
Kano, I wonder why this changed? The difficulty on the workers management page?  AAAHHH!
sr. member
Activity: 419
Merit: 250
Anyone have issues connecting NiceHash rental to Kano pool today?  Tried stratum 80, 81, and 3333 still no luck

I'm not sure if this is new, but you need to increase minimum difficulty to 2048 for your nicehash worker in the kano.is workers page.

After that, you probably need to restart your rental.
sr. member
Activity: 419
Merit: 250
Looks like all my rentals died while I was asleep and never came back. Woke up and saw we'd had some dropouts/restart while I was sleeping, but usually  everything bounces back once things get back to normal. This time only my S3 had managed to reconnect and was hashing.

After doing a little research, the problem was that since I had my diff at the pool set for all workers to 0, the minimum starting pool diff on the rentals was 1042, which is below the minimum on NH. Once I set my minimum diff on the workers page at the pool to 2084 they all came back to life.

Anyone else notice this? I've never had this become an issue before. Any dropouts in pool connectivity have reconnected pretty quickly once the pool restart completed or connectivity issues were resolved. Maybe NH recently updated their minimum pool difficulty setting?

happened to me too. Maybe they changed the min diff
full member
Activity: 182
Merit: 100
Anyone have issues connecting NiceHash rental to Kano pool today?  Tried stratum 80, 81, and 3333 still no luck

I've not validated any actual hashing but using NH pool verification shows its all ok (tested using stratum80.kano.is)
sr. member
Activity: 414
Merit: 251
Anyone have issues connecting NiceHash rental to Kano pool today?  Tried stratum 80, 81, and 3333 still no luck
hero member
Activity: 630
Merit: 500
Exceptionally lucky as of late, brilliant stuff, keep it up everyone! Smiley
sr. member
Activity: 266
Merit: 250
March is going to be an interesting month with diff going down. (crosses fingers) and the new contest. would be nice to strike a block in march and at least have my hat in the ring for the A6 but im just glad to be in the pool with everyone. in the end we are all winners as each block brings in the fat loot.

although an A6 would add more heat to the already warm area im trying to remove heat from. might have to upgrade from my carpet drying barrel fan to something more industrial. Sad
newbie
Activity: 35
Merit: 0
Network is getting really loaded down... Time for Kano Pool to chew through some of our famously fat blocks!!
legendary
Activity: 1260
Merit: 1006
Mine for a Bit
Great week in front of us.  Contest for an Avalon and Hopefully we will get a drop in difficulty:

Bitcoin Difficulty:   163,491,654,909
Estimated Next Difficulty:   158,205,408,409 (-3.23%)
Adjust time:   After 628 Blocks, About 4.5 days
full member
Activity: 182
Merit: 100
so...contest starts tomorrow for the avalon w00t w00t - are the rules changed ?  best share block for the month or something ?  You know it would be so much simpler if you just gave it to me Smiley

And now for the details of the March version of the AVALON6 GIVEAWAY Smiley

https://bitcointalksearch.org/topic/m.14042677
legendary
Activity: 2294
Merit: 1182
Now the money is free, and so the people will be
so...contest starts tomorrow for the avalon w00t w00t - are the rules changed ?  best share block for the month or something ?  You know it would be so much simpler if you just gave it to me Smiley
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
ok thanks for that  so does that mean its been sent to me or pending cheers
As it says on the bottom of the Help page, (Help->Payouts)
After they reach +101 and then Matured, I manually send them soon after that.
Just sent 400443 and 400445 a short while ago, but they're not yet confirmed.
Next one will be in the morning.
Jump to: