...
Also, one thing to keep in mind that losing a block due to bad luck and not technical deficiencies has to do how many blocks a pool is subject to find in the first place, Kano pool hardly finds any blocks on the grand scheme of things, I even saw him brag about not mining an empty block in my empty blocks analysis topic , I didn't want to comment on his post in that section to not trigger him there and make members of that section suffer reading his disrespectful replies, it's enough that members of mining board are suffering.
what Kano seems to don't know or ignore is that the probability of him hitting an orphan/empty block is directly related to his chances of hitting a block in the first place, given the tiny hashrate he has compared to the large pools it makes sense why he is unlikely to hit an empty or orphan block, of course, with all technical aspects like having the right code, server, and connection being equal.
...
You post things that you claimAlso, one thing to keep in mind that losing a block due to bad luck and not technical deficiencies has to do how many blocks a pool is subject to find in the first place, Kano pool hardly finds any blocks on the grand scheme of things, I even saw him brag about not mining an empty block in my empty blocks analysis topic , I didn't want to comment on his post in that section to not trigger him there and make members of that section suffer reading his disrespectful replies, it's enough that members of mining board are suffering.
what Kano seems to don't know or ignore is that the probability of him hitting an orphan/empty block is directly related to his chances of hitting a block in the first place, given the tiny hashrate he has compared to the large pools it makes sense why he is unlikely to hit an empty or orphan block, of course, with all technical aspects like having the right code, server, and connection being equal.
...
...
The rest of my reply is general information for everyone, not pointed directly to you.
...
Please post information you can at least substantiate.The rest of my reply is general information for everyone, not pointed directly to you.
...
You are ignoring facts and the most obvious of those is the fact that my pool has found 2429 blocks so far.
No empty blocks in there.
In fact, my code reports ANY work generated that is ever empty, of the work generated once every 30 seconds over the years.
Over the life of my pool, that would amount to less than you can count on one hand.
You obviously do not understand how work is generated by a pool and how a block can be empty, without the pool purposely producing an empty block like most of the large pools still do.
You like to ignore the facts when posted, since it doesn't suit your argument, so I'll post it here:
Quote
Most pools, I imagine work the same as here - we do a call to bitcoind to get a template that already includes all the transactions we will mine.
Some pools may manipulate the transactions in their pool code - but we don't.
It is possible for us to mine an empty block under very rare circumstances out of the pool's control.
But that has never happened here for the 2429 blocks we have found.
Those circumstances are: a pool generates work that contains all the known transactions on the network.
That pool (here or elsewhere) then finds a block. During that short time (30s or less) no other transactions are seen on the network.
Thus after submitting the block found, the next call to get a work template from bitcoind will have no new transactions.
I log whenever the work is empty - I think it's happened less times than you can count on one hand in 6 years
Thus during those very few rare events someone would have to have found a block to produce an empty block out of their control.
So yeah maybe less than half a dozen possible empty blocks in 6 years for all pools on the network - the rest are them doing it on purpose.
Some pools may manipulate the transactions in their pool code - but we don't.
It is possible for us to mine an empty block under very rare circumstances out of the pool's control.
But that has never happened here for the 2429 blocks we have found.
Those circumstances are: a pool generates work that contains all the known transactions on the network.
That pool (here or elsewhere) then finds a block. During that short time (30s or less) no other transactions are seen on the network.
Thus after submitting the block found, the next call to get a work template from bitcoind will have no new transactions.
I log whenever the work is empty - I think it's happened less times than you can count on one hand in 6 years
Thus during those very few rare events someone would have to have found a block to produce an empty block out of their control.
So yeah maybe less than half a dozen possible empty blocks in 6 years for all pools on the network - the rest are them doing it on purpose.
As I have also stated to you before, I make by bitcoin debug.log report the transaction information for each work it generates, and I can also see in the bitcoin debug.log what is available in the first work after any block change.
Please stop posting like you're an expert, and research what you claim, before you decide to post incorrect information to promote your argument.
There is a lot more to the issue of orphans, again that you clearly do not know or understand, or have ignored
