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

So.... umm I hear that This Year More People Have Been Killed By Selfies Than Sharks..

oddly enough nobody has been killed taking a selfie with a shark though... so that's good !

Too far. We need the restart goodness now..

Working on more changes that will prolly not be ready for another day or so ... then I'll restart to add them in

And a side of chicken...   

Guess I'll have to fix up some buffalo chicken after work

Restart please....

Well there's a table of CDF values I posted last week.
That tells you what to expect in history (that we've done better than expected in history)
https://bitcointalksearch.org/topic/m.12461942

However, the expected average time to the next block depends on the pool hash rate.
2PHs would expect, on average, to find a block roughly about every 1.5 days

So using the CDF table you can get a rough idea of the % there vs the number of days to get to that % - 2PH means multiply the % roughly by 1.5

So if we stayed around 2PH and the current block total took 200% Diff, then that would take about 3days.
100% Diff, about 1.5 days
300% Diff, about 4.5 days
50% Diff, about 0.75 days
etc

I have a web site I wrote years ago to work out the 100% expected averages:
http://tradebtc.net/bitcalc.php

Of course the expected block finding statistics are the same for all pools, the differences are of course
a) the hash rate, which does affects how often payouts occur on all pools that don't use true PPS, but does not affect how much BTC you average over time
b) and how often they lose blocks (that you don't know about)

Blocks are lost a few ways:
1) The obvious network orphans - fewer means a better connected pool
2) The hidden pool orphans when the bitcoind test says it got a network block, but the pool got it's block just after that, but before the pool software knew about the network block change (these show up on our pool - our 2nd orphan was like that - but most pools don't show these)
3) The lost stale blocks due to processing of work by the pool being too slow after a network block came in - due to slow pool processing
4) The lost stale blocks due to the miner getting the block to the pool after the pool knows about the next network block - due to a slow miner network, a slow pool network or slow pool processing

the formula is   time = difficulty * 2**32 / hashrate  (source Bitcoin Wiki )

the first line on kanos.is website is the pools hashrate and the current difficulty is 59,335,351,234 

you can get a better understanding by looking at the bitcoin wiki but this really is just an estimate of time based on whatever the hashrate is vs the difficulty

it really boils down to luck.. however we can calculate pretty close..  if you look at the block page... Some take a longer amount of time, and some get discovered quicker, however after a year this pool is pretty darn close to the calculated time..

with all that said... the same rule applies no matter what PPLNS Pool you choose.  Rule: stay with the pool  - ( pool hopping does not pay )

There's odds that one can calculate given a hash rate, time frame, and the network difficulty.  Mostly it's just waiting, though.

I predict it'll get solved within 7 days. 

On that note. I just ask for pool restarts as that seems to have good effect on pool luck.. 

Is there a way to predict how long a block will take or is it just waiting and see when it's done?

Coz we all get another reward due for a payout

Hmmm, in that case I probably have to change my name.....

Your name will appear on the acclaim page, your own very name on the Hall of Fame of Kano Pool... Forever! (Maybe)
Anyways, here, at least for now ;
https://www.kano.is/index.php?k=userinfo

Somehow you need to be logged in to see it, however.

everybody is thankful 

What if your miner finds a block?

I think I should go buy a lottery ticket now!

Thanks for the great pool Kano!

Payout 375221 sent
ee9ba925426f040c6fc9d60feb6a7797b21c9b906a13eae2016069d4a0d5896c
and confirmed

Furry nice!

Yeah the rewards count updates when the payout data is generated.
But that waits until after a confirm, which in this case took 69 minutes.

Edit: I've put the numbers back since they are back to being correct with that block.
I'll look into the problem later since it's only a displayed number and has no effect on any important calculations or any other stats.

Looks like the rewards column is not updating either
NM ITS WORKING