It's not just a giveaway. He wanted an explanation of 5Nd and/or PPLNS in general... with pictures even!

Well the simplest explanation of 5Nd is that its 5*Nd where Nd currently = 3,007,383,866,429.7 and so 5Nd = 15,036,919,332,148.5

But if you mean the whole of PPLNS, its basically a moving average window.

The foundations you have to get first are:

- mining is done in shares.

- shares have difficulty

- a single, 100-difficulty share is (for PoW purposes) roughly equal to 100, 1-difficulty shares.

- Nd is the expected amount of work to be done in order to find a block (but this is an expected statistical average, meaning IN GENERAL and AT THIS POINT IN TIME, if you do 3,007,383,866,429.7 shares of work, you will solve block). When we talk about these % that get higher, Nd (or 1Nd, same thing) = 100%

So on kano.is when a block is solved, it looks at work done by all members in a window the size of 5Nd numbers of shares backwards in time, and splits the rewards of the newly solved block proportionally among the work done in that window (after skimming the pool fee of 0.9% off the top).

Here are some pictures

Scenario A:



In this scenario, 1Nd = 700 shares. When block AA is solved, the pool looks back 5Nd worth of shares, calculates the total shares, then divides the block rewards accordingly.

Total shares = 3500 ... Miner 1 = 500 ... Miner 2 = 1000 ... Miner 3 = 2000

Miner 1 = 14.28% ... Miner 2 = 28.57% ... Miner 3 = 57.14%

So if block reward is, say, 13 BTC, then

Miner 1 gets 1.83 BTC ... Miner 2 gets 3.68 BTC ... Miner 3 gets 7.36 BTC ... pool gets 0.117 BTC


-----

Scenario B



In this scenario, when block Z is solved, the pool looks back 5Nd worth of shares (as above), calculates the total shares, then divides the block rewards accordingly.

Total shares = 3500 ... Miner 1 = 1775 ... Miner 2 = 900 ... Miner 3 = 825

So if block reward is 13 BTC again

Miner 1 gets 6.53 BTC ... Miner 2 gets 3.31 BTC ... Miner 3 gets 3.03 BTC ... pool gets 0.117 BTC

-----

Note that these scenarios are simplified and the 5Nd window doesn't always end on the same time a block is found. I just did that to make things simple. I believe Kano does the 5Nd calculation by the shifts, which is explained on the help page https://www.kano.is/index.php?k=payout. Roughly, though, shifts are every 50 min or less and are defined by work changes, block solves, or pool restarts. Specifically though, shifts are NOT defined by amount of work done.

So realistically, there should be even smaller verticals inside each block-solve worth of work that are the shifts. It's just that in my examples, the 5Nd worth of work done in shifts would fit nicely into the block-solves worth of work.

Ninja edit2: someone please correct me if any of the above is wrong, but I'm 99% sure I've explained accurately. Whether it was simple enough... well... who knows.

You set rules and mentioned an answer but didn't mention a question, so im gonna assume the answer is 42.

EDIT: WATCH OUT NOW HERE WE COME...!

If we don't solve this block before I get home I'll happily move all of my lottery miners over. Can the pool go to a low enough share difficulty to allow 102 GH/s workers?

Yeah I mean technically I suppose there is no upper limit to how much work a miner or a pool can do before finding a block, while there is technically a lower limit. Not sure what the luck number would be for a block solved on the first share of work done. Would love to find out though.

But the sample size of the data set of shares is so big that you're unlikely to get into a situation of impossibly high luck over a long term. And if you do, there's probably something else at play, like technical issues or bad actors somewhere.

Since there seem to be a lot of n00bs here asking about luck and such...

Its worth pointing out bad luck has more of a psychological impact than good luck.

Imagine 3 blocks solved.

Scenario 1 - each block takes 100% of expected work.

Scenario 2 - first block takes 50% of expected luck (high luck), block 2 takes 100% expected work, block 3 takes 150% expected luck

If hash rate stays the same, both scenarios in total take the same amount of time.

But the 150% block seems worse because it's bad luck for a long amount of time (when hashrate is constant, amount of work = amount of time). While the 50% block seems good but not as good as the 150% block is bad, since its good luck but for a short amount of time.

Basically the good times are short and the bad times are long. You gotta think logically and not let emotions confuse you.

Focus on the long term luck stats. And don't shoot yourself in the foot by pool hopping. Just set it and forget it.

Assuming nothing has changed for the worse with the pool back end, kano (and before that kano + -ck... sorry to hear about the disagreements...) this pool is optimised and transparent to the point that it puts its members in the best possible situation to get lucky.

Does tmax behave like ttli in claymore?

I'm back after 2 years gone. Maybe I'll turn the luck around. Thought about mining at slush, but after 5 min browsing his site I still couldn't determine what his fees are. Lame.

Its not a lot, but +11TH/s from me.

(also saying 11 TH/s isn't a lot sure sounds crazy given what hashrates were 2 years ago...)

Are you guys tweaking frequency as well or just voltage?

Not really sure why by it freezes up my machine when I start it.

To be fair, I'm running with a sempron 145 or something like that. Very low power. Any chance you can make a GatelessGateSharp Lite? haha.

Also, on 2.1.16 performance wise, my 2 rx 470 were about 2-4 mh/s (10-20%) and my r9 390 was a whopping 9-10 mh/s slower (30-35%). The 470s have modded bios, yes, but not the 390.

Miner works well on my 1080TI. About as fast as Claymore. But It eats about 30% CPU usage. Not good for power consumption. What's going on with that?

disregarding capacity issues, can 2 instances of ckpool (of course, one splns one "solo") run off a single bitcoind?

not sure about how easy it would be to script, but the last step in buying from blokforge had a captcha on it. I'm pretty sure the sole purpose of those is to stop people from scripting the pages.

Honestly I've been in lines waiting for tickets, waiting for products, and now waiting for products on line. There's no ideal solution.

Anything you can think of is probably easily manipulated and will likely come down to just as much luck as what just happened (minus the PayPal b.s.)

I'm just happy Blokforge's servers didn't melt.

not true. Only when you get the confirmation email you're golden.

got one about 2 min ago. keep trying.

did they have more than 2 for sale?

I LOL'd 

OK will do.

If/when I ever get a donation or find a block I'll send something your way too.

So I'm pretty sure I know your stance on the subject, but FYI I (re-)launched luckypool.co running on ckpool-splns. Its a Bitcoin Cash mining pool backed by a Bitcoin Unlimited node. No Segwit, so not sure how that will affect ckpool (if at all). I did test on testnet and it worked as expected. blockmaxweight is something specific to segwit.

Let me know if you'd like a blurb at the bottom of my pool's home page (which is somewhat inspired by ckpool.org, although, when you're going for the simple look, there aren't a ton of options... maybe I'll add a splash of color).