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

I'm not a pessimist by nature and always champion the little guy when I can, but every year more miners are being made so every year things change.   I don't doubt you will find another block, but it seems like it could be like this more and more.

That's the number on the top left of the web site pages.
Currently 312.11%

Any calculations on how we are looking mathematically on expected kano?  I enjoy those posts where you breakdown the pool stats.

Lets hope we smash a block soon I could really use a payday!

Every single hash that everyone does has the same chance of finding a block.
If someone is hashing 100x faster than you, then they 'expect' to find 100x the blocks you do.

It's not a race to get a block, since each hash you do has no effect on the previous one.
KanoPool sends you new work every time a bitcoin network block is found, so you just keep on hashing.

The 'expected' time per block is 100% difficulty of mining shares.
That mining does not care if you were only mining on 1 block, or 1000 blocks, as long as you keep switching work quickly each time a bitcoin network block changes, you keep counting those hashes.
When you are too slow to switch work, that's called a 'stale' share.
Of course some 'stale' shares can't be avoided - but the pool average shown at the moment is 0.18%
The % of your own shares that will be 'stale' will depend on how far you are from the node you mine to and how quickly your miner can switch work when told to.

Help->Luck explains the statistics.
https://kano.is/index.php?k=poisson

Correct me if im wrong, but if those huge farms with 10, 100, 1000x times the hash rates we have are getting blocks, is it possible were not getting any because of that? Like think of it in terms of us being a single S9 and them being 1000 S9's and were both solo mining?

A block will be found. Like the 2432 blocks before it.
Alas the timing of when it will be found is uncertain, like on any pool.
The difference here at the moment is that the pool hash rate makes the 'expected' time to a block a few months.
See Help->Luck on the web site to understand block finding probabilities: https://kano.is/index.php?k=poisson

Is there a danger that if a block isn't found, all the last year's hash power will be for nothing for the miners involved? (I realize it would at least be circulating the blockchain).

Also, because of the way bitcoin mining works, we might find a block 3 days after you start mining! 

Well, it's a case of long term between blocks due to the current small size of the pool.
If we can get some more sizeable miners to join, the time between blocks would reduce dramatically.

With respect to earnings, you'd currently get about a 3 month payout if you mine for more than 3 days before the next block.
The 'current' block is always your share of the work of the 3 days before it's found.

Hello Kano,

I wouId like to join your pool, I really like the principes and what you did for the network.

But if I join you now, I am affraid of earning "nothing" : the pool is actually over 300% shares for the current block. If I join you with my "small" hashrate, I will earn almost nothing, because I will no have the time to share suffisantly shares. Am I right ?  (= nothing on the current block + next in long time to wait for)

Yea it will. I’m hoping I get a notification while im away on a Stag weekend. Usually get a block when I’m on holiday lol.

403d without a block starting to wonder if one will ever come round again   

Thank you for detailed information @ wavelengthsf and kano

One has to ask: Why?
Even a RasPi-3 has a 64-bit CPU. What, does someone want to run the software on a Pentium under Win95?

No.

Being able to find a share is not enough proof that a miner works.
A testnet block is actually pretty much the same as a bitcoin pool share.
A miner needs to be able to handle 64 bit shares before it is at least considered tested.
Their code is hidden, so you can't check it either.

A block is just a share with much higher difficulty, the miner doesn't need to know when a share is a block.

Genesis, running buggy software that didn't handle 64 bit shares, was the reason slush lost 28 blocks in a month back in Dec 2015

Alas the apollo team has already claimed that being able to mine any share is good enough testing of their miner.
It's certainly a concern that they sell a miner that isn't even properly tested but leave testing up to the people who buy the miner.

However, I do already know that it works for greater than 32 bit shares.
Someone else has run the miner long enough solo mining on my pool to prove that.
I wonder what their response would have been if I had found proof that the miner didn't handle 64 bit shares ...

Alas apollo has stated that they will create a 32 bit version of their miner, and who knows if that will work, or how to identify the 32bit version.
So until I can see that the 32 bit versions also works, it will continue to be restricted to solo.

The risk is that a share for the mainnet needs a 64 bit number, and without looking at the source of the miner, you don't know they're handling it well. I've gotten shares as high as 17G with my apollo on the mainnet.

User „wavelengthsf“ said he found a block on the testnet. Isn‘t this enought to confirm that the Apollo can find a block?

last block was a year ago (359 days 20h 7m) but the pool is very small - and is due for a block any day. If the pool was to increase in hash the variance between blocks would decrease

How many blocks/day/week/month are you solving now? I am pool shopping.

I was asked about how to use a rental here on Solo, and after much digging and watching the data packets between Craphash and the pool,
I discovered that the problem with doing that with ckpool, is that ckpool does the miner connection badly.
It always sends the pool default work difficulty before the miner validates their username/address and before sending the account difficulty setting.
For a miner this doesn't really matter, but for mining on Craphash, they look at the first work difficulty and thus wont allow it.

Clearly a certain person knew about this since it's his code, and he's had to allow Craphash mining on his solo pool, but he never bothered to fix the code.

Sooooo ... I ran some proxy rental runs using Craphash, since I guessed a proxy in front of the pool would work around this bug.

As mentioned in Discord on various occasions, while there are 2 KanoPool account types people can get: PPLNS and Solo, I have a 3rd account type called Override that gets no rewards, the shares are ignored when calculating rewards, but any blocks it finds goes to everyone on PPLNS.
i.e. live testing that has no negative effect on the miners, but a possible positive effect if it finds a block
I used about a 1 in 66 gamble in multiple runs, but alas no high enough share.

But anyway, the actual point of this post is to point out that Craphash steals between 2% and 3% of your BTC, so I don't suggest anyone should use them.
When you make an order, they take 3% as their start fee, however the actual amount of work you get, in all of the multiple runs I did, received between 2% and 3% less hashes than the 97% it should have.

You can of course work out what you should get quite simply.
If you are paying, say a high 0.0095 BTC/PH/Day and you use 0.2 BTC, then the amount of work you've paid for is:
0.97 * (0.2 / 0.0095) * 10^15 * (60 * 60 * 24) / (2^32) Diff
(3% fee) * BTC you paid * PH * 1Day / 1Diff
So in this case, 423.5G Diff

Alas you will find you will get less than 415G Diff (-2%)
Your worker will show these numbers if it's a new worker that starts at zero and you add :Diff + Invalid
(or write down what it was before you start mining the rental to it)

All pool, miner, proxy or accounting systems calculate hash rate from Diff, so they know how much Diff you are getting and use that to determine when to disconnect you.
They choose to disconnect you very much early between 2% and 3% early to be exact.

Oh well.