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

[omega015]

Seems the pool restarts I did during the problems (testing making sure it wasn't the pool's fault ) had the usual effect
Another block

  waiting for thedreamer to comment on the power of restarts 

[omega015]

quick question if you dont mind kano


Block   Address   Status       BTC                                 when there is nothing under status on the payments page does that mean its not been sent or it has
my address                          my ammount


Thanks

status will always be blank, this is something on kano's to do list one day in a galaxy far away (or with the potential new payout method)

[welshy82]

ok thanks for that  so does that mean its been sent to me or pending cheers

[kano]

Seems the pool restarts I did during the problems (testing making sure it wasn't the pool's fault ) had the usual effect
Another block

  waiting for thedreamer to comment on the power of restarts 

However, seems I'll need to do a ckdb restart because of it - it's noming away all the ram due to the restarts before.
That will be after the next shift summarisation which should be in about 5-10 minutes.
So, yeah, a CKDB restart coming up shortly, no miners will be affected.

Completed - all OK.

[omega015]

ok thanks for that  so does that mean its been sent to me or pending cheers

That depends on the payment for which block your looking at. All payments from block 400400 and earlier have been paid and confirmed. Block 400443 and newer are still in the confirming stage which you can see on the block page.

BTW kano will post on here the payment (and confirmations) as/when he does them. FYI he manually does each payment after 101 block confirmation (assuming he is awake). also sometimes he will delay payment if another block will soon reach the 101 confirms and then he will pay them all together

[maxsettings]

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?

[wikkidtt]

This is a great way to start my Monday!

[Legacy2005]

This is a great way to start my Monday!

waking up to that block notification icon is always a good feeling. but checking the emails and seeing 4 blocks found overnight is even better. definitely not a bad way to start a Monday.

[kano]

...
Any dropouts in pool connectivity have reconnected pretty quickly once the pool restart completed or connectivity issues were resolved.
...

Well, as I mentioned, it was around 45 minutes of problems connecting until the 'upstream' provider fixed their routing problem.
So that was most likely why.

[kano]

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.

[fr4nkthetank]

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

[omega015]

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

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

https://bitcointalk.org/index.php?topic=789369.msg14042677#msg14042677

[AriesIV10]

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

[mtmining2]

Network is getting really loaded down... Time for Kano Pool to chew through some of our famously fat blocks!!

[Legacy2005]

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.

[ShrykeZ]

Exceptionally lucky as of late, brilliant stuff, keep it up everyone!

[yun9999]

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

[omega015]

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)

[WBF1]

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

[WBF1]

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.