Author

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

full member
Activity: 143
Merit: 100
Damn my 3rd block in the pool one with ahumaidan and 2 with mhumaidan

Split personality?  Grin

Congrats!!!    Cheesy Cheesy Cheesy

🤣🤣 Nah. I manage the miners, buy miners and theirs PSUs, wiring, replacements and monitoring for my family as well as maintenance. Finally, I get a % of the funds of each.

Thanks!
hero member
Activity: 658
Merit: 500
Visualize whirledps
Damn my 3rd block in the pool one with ahumaidan and 2 with mhumaidan

Split personality?  Grin

Congrats!!!    Cheesy Cheesy Cheesy
full member
Activity: 143
Merit: 100
Damn my 3rd block in the pool one with ahumaidan and 2 with mhumaidan
hero member
Activity: 658
Merit: 500
Visualize whirledps
Block by mhumaidan with 32TH/s!  This is your 2nd Kano block and our 1st of BLOCK THURSDAY!  Cheesy

There are also 2 payouts hitting our wallets!  Cheesy Cheesy

Damn, only 15.2 block reward. WTH?  Wink



 Grin


legendary
Activity: 1736
Merit: 1032
Carl, aka Sonny :)
Block by mhumaidan with 32TH/s!  This is your 2nd Kano block and our 1st of BLOCK THURSDAY!  Cheesy

There are also 2 payouts hitting our wallets!  Cheesy Cheesy
legendary
Activity: 952
Merit: 1003
This becomes a game of statistics.  You want a larger pool as it would decrease our variance or  inconsistency of blocks.  I believe when I was talking to Kano, he said our pool size needs to be 5% of the total bitcoin hash rate to bring it statistically within the parameters that would eliminate the long periods of time that we go without finding a block.  Another way of looking at it, is right now if you plotted our blocks on a chart you would have huge spikes and then nothing (for the hours we wait in between) for a time another spike and so on.  At 5% we would have a more consistent smooth line.  Yes we would all sacrifice rewards per block, but make up for it in multiple blocks per day.  In the end of the day, you would make as much or more with a larger pool.  Right now to hit 5% I believe we need to be around 220 PH and that is a moving target as the network grows. 


I wish there was a "like" button or similar...I've not heard this said more clearly. Perhaps we'll see more well-resourced miners finding the advantage of how this pool operates. We "little(r) fish" will continue to pump our 25 Satoshis' worth to help...  Cool
member
Activity: 84
Merit: 10
What is the advantage of a larger pool? If payout is distributed among pool members it seems to me that the individual payout would roughly stay the same. Then again I'm not a pool or payout expert.

This becomes a game of statistics.  You want a larger pool as it would decrease our variance or  inconsistency of blocks.  I believe when I was talking to Kano, he said our pool size needs to be 5% of the total bitcoin hash rate to bring it statistically within the parameters that would eliminate the long periods of time that we go without finding a block.  Another way of looking at it, is right now if you plotted our blocks on a chart you would have huge spikes and then nothing (for the hours we wait in between) for a time another spike and so on.  At 5% we would have a more consistent smooth line.  Yes we would all sacrifice rewards per block, but make up for it in multiple blocks per day.  In the end of the day, you would make as much or more with a larger pool.  Right now to hit 5% I believe we need to be around 220 PH and that is a moving target as the network grows. 

legendary
Activity: 1736
Merit: 1032
Carl, aka Sonny :)
What is the advantage of a larger pool? If payout is distributed among pool members it seems to me that the individual payout would roughly stay the same. Then again I'm not a pool or payout expert.

Yes, your expected payout should always be the same based on your hash rate but the pool variance should be lower with larger pools.
newbie
Activity: 48
Merit: 0
What is the advantage of a larger pool? If payout is distributed among pool members it seems to me that the individual payout would roughly stay the same. Then again I'm not a pool or payout expert.
legendary
Activity: 952
Merit: 1003
Well yesterdays reward didn't suck, but then again we don't complain about any block that is found.  Grin

Indeed...  Kiss
legendary
Activity: 952
Merit: 1003
Wow...that was interesting. I've only got five machines online...two at home and three at CryptoBoreas...and all of them disconnected, but only for a few minutes apparently (I was asleep).

I thought perhaps it was just Labrador and NLHydro with minor "leftovers" issues...until I saw via ckpool monitor that my home machines also dropped, so I knew it wasn't an actual power issue.

Wasn't until I came on the board I "saw da light!"

Nice handling, Kano.

Mine on...
newbie
Activity: 28
Merit: 0
sr. member
Activity: 508
Merit: 250
Yep all back to normal, thanks Kano!  There was a lot of beeping going on here!  Smiley
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
ckpool was doing a core dump so until that completed I couldn't restart it - a linux core dump is 'unstoppable'.
All OK again now.
I'll edit this post with more details shortly.
At 13:34 UTC there was a strange world wide network problem on all of my servers.
Every single node lost connection with all the fibre relays, most of the miners lost connection with the main passthru and some miners dropped off on the nodes also.
Since it was worldwide and every one of the pool servers on multiple server providers I use, I can't really hazard a guess at all what happened.

The worker count on ckpool kept dropping down after the nodes all reconnected to the fibre relay, so I decided to restart ckpool since it can sometimes get into a weird network state and take a long time to recover.
I stopped it with Ctrl-C and it core dumped - worst thing that can happen - since I have to wait for it to complete the core dump before I can restart it.
Linux effectively locks a process completely while it core dumps.

It took 17 minutes to core dump, so during those 17mins everyone will have failed over to their backups.
The passthru (stratum.kano.is) still wasn't working once I'd restarted ckpool (it also gets into strange network states sometimes) but that ended up requiring a restart to get it to reconnect to the main ckpool, which I did at 13:55

Everyone who wasn't on a node and already failed back, will have failed back by 14:00 - unless there's problems with your miner handling failovers (which it would seem sometimes they do)

All is OK again now and the hash rate is back close to 60PHs so I guess we had a few PHs of rentals that dropped off and didn't reconnect - as happens with rentals.
newbie
Activity: 8
Merit: 0
Yep - all 104 of the miners I manage went offline (that's a fun alert to get) but only for a few minutes - Kano's got it sorted - best pool on the network
legendary
Activity: 1736
Merit: 1032
Carl, aka Sonny :)
Everything is back to normal on my end! Cheesy
newbie
Activity: 83
Merit: 0
Kano always has the answer before I have a chance to notice something wrong lol

 Wink Wink
hero member
Activity: 1610
Merit: 538
I'm in BTC XTC
As always, kano-san's on the case! Thx for the update.
sr. member
Activity: 508
Merit: 250
All of my 12 miners are off and the Kano.is is showing 35 TH now!  Sad  Shocked Huh
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
ckpool was doing a core dump so until that completed I couldn't restart it - a linux core dump is 'unstoppable'.
All OK again now.
I'll edit this post with more details shortly.
Jump to: