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

Oh I thought the not so worthy block turned into a orphans or stale. Which both have different meanings I know. So this would be a first for me to see a block that just wasn't good enough. Is there a way to detect this from the start? I am sure if there was we would have gotten it in the first place. But I mean as whole really, I mean if the block-chain sees this type of transaction is there a way to broadcast the failure and tell the miners to change over to the next block or is that what already happened?

Yeah a few high Diff blocks right next to each other makes it tough.

No orphans or stales, but an unworthy 'not quite good enough' block doesn't help either

Only one orphan in the last '12 months' means either I'm doing something right or we're lucky

Yea it is, was nice to see we didn't have to wait another 80 hours for a block to show up. Just glad it wasn't another stale or orphan block. Always hurts to see almost 80 hours go by and get hit with one of those.

Good start of the week!

It should correct the numbers after the next network block ... thus the '~'

please confirm... please confirm... please confirm...   

No, it wasn't a block.
It was (as I said above) a share that didn't meet network difficulty.
You could look at it another way if you don't follow the meaning, it is simply one of the eleventy-billion shares found so far that wasn't a block.
In terms of usefulness, it's the same as a 1042 Diff share.

ckpool checks all shares within 1% (or better) of being a block to be sure of no rounding errors or problems.
It was within 1% of being a block, but wasn't good enough to be a block.
It got checked anyway, and bitcoind replied "high-hash" meaning no good.

As I've mentioned a number of pages back, my ckdb shows something for all the attempts to submit blocks to bitcoind.
Orphans, Stale, High-Diff, Valid and anything else that bitcoind might reply
By default, if it fails, it will end up being listed as an orphan if I don't intervene before the next network block shows up.

In this case I flagged it as Unworthy since it wasn't actually a block to start with.

so the previous block was an orphan or what?

At any particular point in time, no matter when the last block was found or how many blocks a pool has found, a pool is expected to find a block 100% Diff from 'now'

So at 1.8PHs that's ~40hrs.
We may find it sooner, or we may find it later, but that's simply the expected time at 1.8PHs

If an hour passes, independent of it we find 0, 1 or 20 blocks in the next hour, the next block will be expected ~40hrs after that.

Another 80 hours?

Whoah. that is insane.
I would say what are the odds, but, someone will calculate them

378389   bitminerpro_S4.78A504B8AF0F   25.01764342   2015-10-11 06:59:36+00   ?     Unworthy   *129,706,365,253   213.286%   0.882   0
45 min
deplorably

Must have been the day for near misses dammit with one so similar on solo it's scary

We will get a quick pop now 

Oh well, seems it was our turn for another 'Unworthy' share close to being a block, but not quite good enough.


Current diff is (of course) 60813224039.44034576
Close but no block

Thanks for the response, I kind of figured that also, but what made me consider this is a pool that has say 100Ph, and for them SOMETIMES blocks hit with VERY low diff and at 100Ph, even a few seconds makes a difference. So if they hit the last one, then switch to next one at 100Ph, they can find another block and maybe another within seconds. Pretty much before other pools have switched to the next block. When you looks at the history of some of these large pools, its 2,3,4 in a row and sometimes seconds apart. Anyway, thats what made me think of this scenario.

Now imagine what damage we could be with your code, top of the line servers, flash storage and backbone fiber links and 100PH.....Unstoppable

Kind of like high frequency stock trading with servers across the hall from NADAQ servers but in the mining space.

Heh I replied last night but as is often the case, the forum timed out.
The post didn't arrive and I didn't check it did

Anyway, regarding ckpool/kano.is, our block handling is very fast and our network connectivity is excellent.
I can't really see a 'reasonable' block size increase causing much detriment for us.
I can see it causing problems for other pools ...

By reasonable, I mean megabytes, not gigabytes ...

Block switching, for any good pool, is a quick thing and being only a few seconds makes very little difference to the chances of finding the next block.
A pool with 15% of the network is expected on average to find one block every 4000 seconds, so even a large 4s extra is a small 1 in a 1000.

However, if there was a cartel of pools, then that cartel has the same risk of destroying BTC if they had 51% of the network, as a single pool with 51% would have.
If a group of pools was stupid enough to do such a thing ... then ... well they can say goodbye to their pool like everyone else.
Who know if they think ahead or not ... though the fact that pools SPV mine and mine empty blocks shows that certain pool operators don't care how long bitcoin lasts and would be better gone from the bitcoin landscape.

-

Payouts 377918 and 377920 sent
09d038ee8a868b97b899e268af6cb127108f46af4c705118fbbea13abc7a6d1c
40e5283e9ad6b4c82680ce5d42eff0788bbdfc404ad3b325515aa14505a025be
and confirmed 20 minutes ago

I believe it is already pretty known. It is one of the better and more reasonable arguments against increasing the block size too much that I've heard, in my opinion anyway. As blocks get bigger, the propagation time would also increase and amplify the effect you describe. It puts pools on slower connections or with inferior software/hardware at a greater disadvantage. Or, even the opposite, for example, a large pool or set of pools in China could build blocks off themselves or each other faster than they could propagate it elsewhere.

A general answer to your general question, pools that are coded to optimize block changes and get new work faster have better chances of having their solved blocks confirmed and not become an orphan.