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

Good thing 5nd is finally below the 12-14 days period though.   

The pool hash rate for the last day is roughly 108.88PHs which means the 5Nd 'ramp' is roughly 7days 22hrs.


Practically 8 days now. 

Its just hash rate math.  The higher our hashrate, the more likely we are to find a block.  Of course, finding blocks is purely random, so block finds are expressed as a percentage after-the-fact.  E.g.  If we expect to find a block in 2 days, and one pops up in 1 day, that is a 50% block.  If it pops up in 2 days its a 100% block.  If it pops up in 4 days its a 200% block.  Normal random distribution rules hold.  e.g.  Its about 1 in 7.4 that we will have 200% blocks, and 1 in 10,721 we would have a 928% block (those stats happen to have come up in a recent conversation on the IRC channel).

Over time, like 500 blocks, things tend to average out towards 100%.  Its just like rolling dice.  Hard to say over a dozen rolls how many 1s, 2s, etc. you will get, but over 600 rolls its pretty likely you will have about 100 of each.  Actually fairly unlikely you would have EXACTLY 100 of each though.

One thing to advise your readers:  Kano has a longer ramp up time than most.  Its fair, you get it all back if you ever leave, but its 5nD approach (see "Payouts" under the help section on the pool website) has that effect.

Just 1 user name and BTC address.
That said, if both miners use the same name then you will be seeing the result of both miners added together.
Fine and dandy but if you want to track each miner then just use  name.miner
eg for me I use:
Fuzzy.Avalon741_1
Fuzzy.Avalon721_1
Fuzzy.Avalon821_1
Fuzzy.Avalon741_CM
Fuzzy.GimpyAnt77r4b6
and so on

Now total stats and stats per-miner are available

Same...no reason to split them up.

Just joined Kano with about 23th/s 😊👍🏻 Should i use 2 diffrent worker name with same btc adress or one worker name with one btc adress? 2 miners btw

Also, when I started, dust was around 300-400 GH/s. My napkin now says it's somewhere around 750-950, depending.

Bread crumbs are better than dust!

Yeah, really! A third of the way to 100% expected in just ~12 hours... Nice!

It was around there. But I guess the guys now that has 1 Th or so probably have only a bread crumb.    But.. a mouse could survive on bread crumbs.

I don't know why, but it stuck in my mind when we had 1444 users on the pool before. We were at ~40PH.   It looks a little different today.   


Be patient ... and MINE ON!!!

Right, I was referring to the "workers hourly shifts Inv Diff column", I am a bit less than .170 as well.

Hi Kano-san, or anyone from the team, i wanted to promote the pool via a personal blog post, but before i can do that, i need to fully grasp the idea on how we run.  Question, how do we calculate the "expected" blocks.  I assume it is based on the pool hash rate, but is there such a formula to it?  Please help to clarify on how we exactly get the total number of expected blocks as from what i can see, when pool hash increases, our expected block should increase since we need more blocks to reach the 100% expected target.  Or in other words, the more miners here, we are expected to hit more blocks in order to balance the share per hash of expected 100%.

Thank you in advance!

Once Invalid Shares leaves zero, it can never come back to zero for that block. You may still, however, have zero invalid-share shifts within a block.

When we solve a block and start on the next one, Invalids resets to zero (no shares submitted, yet). Ideally, you want to keep it there.
Noobs like me ask, "Why?"   Especially since Invalid shares don't affect your rewards. The short answer: efficiency. If your miner is  submitting shares that it should "know" are out-of spec, it is wasting hashes. Almost every machine will produce Invalid shares at start-up; your miner only "knows" what's in its configuration. Once it handshakes and joins the pool to get feedback, things go "normal".

To keep Invalids as close to zero as possible requires that you adjust your miner's settings (pool node you're pointed at, frequency, voltage, etc). Your miner's status page (general info), and Kano Pool's Shifts page (~50 minute reference window for time)  and Workers>Workers (check Show Details For Invalids) (specific types of Invalids (is the issue network or miner config?)) are helpful here.

For folks running new, out-of-the-box, state-of-the-art gear, this isn't too bad. When you have a garden of mostly someone else's problem children or older machines, like I do, it gets fun.


Also, a big  SHOUT OUT to Interinfinty for making that last block come in under 200%!!



MINE ON!!!

Billy Joel likes them "in the middle of the night" too.

He's talking about each individual shift.  Sometimes your Inv Diff is 0 (very good).


TIME FOR 1-2 MORE BLOCKS BEFORE END OF MONTH/QUARTER!

MINE ON WITH KANO-SAN!

He's talking about the Inv Diff column on the Workers/Shifts page.

https://www.kano.is/index.php?k=shifts

Love the overnight block action!

How'd you get it to 0? i'm at .118% invalid and .170% block with 180th/s. I'd love me some 0 invalids!

So glad you're almost fully ramped! Still humbled to think I had an influence in you mining here.

Best of luck!

All good, shares running at at least 6 rewards still...

Though now I've dropped into #63 ranking - which is a good thing for the pool

Let's not wait a day for the next block please (and maybe I can make it to the acclaim board...)

Ahhhhh, the sweet smell of a block in the morning!

Good work everyone--especially our army of noisy metal shoeboxes.

Edit: To Interinfinity and beyond!!! Thank you too.