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

Yep, I don't know of a single time the pool has went down since 2015 when I started here.  The worst was recently when all but two nodes dropped off.  I have since put all nodes in my failover list.  I still have a solo pool at the end of that list too.  This is the most reliable pool I've ever experienced.  Knock on wood!

Not sure if the pool has ever gone down. Given its age I expect that it has but I certainly do not remember such an event.
Nodes dropping out - ja that does happen every so often but thanks to Kano's diligence they are back up ASAP, usually within minutes. As long as your backups point to a different node (not just a different port) mining continues uninterrupted.

Yep, that's what he has said in this thread.  Won't work for failover purposes when mining PPLNS on kano.is.

Since I don't do discord I don't know when the kano solo pool is scheduled to be available.  As many here do, I set a backup solo pool for when the main pool I mine to (kano) goes down. But if the backup solo pool is also kano will that make it moot? I believe I read previously that the difference on kano between pooled and solo will be virtual, not physical. True?  Makes economic sense certainly.

me too i think 13 is unlucky

Who says 13 is unlucky??

"I don't believe in superstition because it's bad luck"!! 

nice! gotta love them blocks. lets go for a hat trick this month!

Starting to feel like old times.

Thanks Biffa!

#14 Got off the unlucky 13 spot.. now to get some more!

BOOM!  Killing the blocks here on kanopool!  Yee Haw!!   BTC

Biffa nails another one!  Hell yeah.

BLOCK!

By me

so join us increase/join in our luck

I know - that is awesome, very nice payout for you guys

i did say "if" lol though we have found 1 a month the last 3 months with quite a bit less than 15 ph

If you found one block a month, consistently, at 15PH that would be incredible luck...!

Just a quick update about the KDB code

I've already told everyone this in Discord, but in case anyone doesn't go there:
I updated KDB last night, this was for the addition to the txn/payments to identify the new Owed+Block payments separately for the standard Block payment.
You get one of these if you have an outstanding dust balance when you've also earned above dust in the current reward.
That's all running OK now and yesterday's block is also showing fully on the Payments page.
The Rewards page of course has always been up to date.

This update also included a couple other things people may (or may not) notice on the web site:

The block difficulty calculation is now correct ...
Alas once we fell into the realms of a small pool, taking multiple diff changes per block, using BlockWork/CurrentDiff is going to get more and more incorrect.
What you'll see now, when there is a Diff change, is the % will not suddenly jump up or down, but continue on from the value it was at the time just before the diff change.
Some time in the future I'll update the block stats of the past year or so, where this fix should make a noticeable difference for those blocks.
The change I made for this is to make the running diff total also do a running diff% total - i.e. add the diff% per each share as it arrives.
This does lead to an issue with the accuracy of the largest floating point number in C, so it can get out by a small amount after about 4-5 decimal places if there are a lot of low diff shares - which here the diff is limited to 442.
But as has always happened with KDB, the % shown is always recalculated after the block is confirmed, and that recalculation overcomes the accuracy issue.
In the (distant) future, as difficulty rises, this will become more of an issue with the running total diff%, but the recalculation itself will still be ok.
KDB also reports to me on the console, the floating point accuracy for the current difficulty, when KDB starts.

On your workers page, I've adjusted the calculation for "Invalid"
It no longer includes "Hi" or "Dup" in the "Invalid" calculation, since they have no expected effect on rewards.
They're caused by the firmware in your miner, not the pool.
"Dup" is of course when your miner sends the same share more than once.
"Hi" is when your miner is sending shares above and below the difficulty specified - it counts the ones below.
Of course you can still see the "Hi" and "Dup" values, same as before.

The above change has also been applied to the pool "Invalids:" number at the top left of every page.

The solo changes are the next main update ... as yet unknown when, though a lot of those changes are already in the code now live, since I've tested that they're ok for just normal pplns before doing this update.

your 5ph would be close to 1/3rd the pool's hash and would then also ensure we find blocks sooner as well - the more hash, the more blocks - at least usually even if we found 1 a month, if you got 1/3rd the payout that would be a nice payout and sure as hell beat any pps.

That's true - however if I had joined a few days back, perhaps this block wouldn't have been found as I'm assuming my participation would have changed the shares etc.

I'm keeping an eye on the website regularly, but for me the total hashrate is too small at the moment (100% luck would make the pay-outs too sporadic). 30PH total on the pool would work for me. I have 5PH of gear, and will be 7PH by end of July. So if the pool hits around 23PH regular support I'll be happy to join and bring it to 30PH.

Never too late to start!

I should have taken your advice and joined the pool when you said hahah!