Sergio, you raise an interesting question.
I had seen your message to the list related to this idea before [1],
so I went back to research what the viewpoints and conclusions were,
if any.
I didn't find anything too conclusive, but I did find some persuasive
points by Dave Hudson [2] [3] [4] [5]
Does that not sound like a useful check-and-balance? It does to me.
In a scenario where these network limitations and miner rate
distributions are the same to begin, and the block and transaction
size limits are raised or removed, your observation would seem to
indicate that blocks that are outsta
I think your "hardfork bit" proposal is clever.
It addresses the particular valid concern of re-org facing users of a
fork that a small/near/fluctuating majority, or less, of mining power
supported.
While the "economic majority" argument may be enough on its own in
that case, it still has some aspe
>> Ok, so set the bit and then include BIP-GIT-HASH of the canonical BIP on
>> github in the coinbase?
>
>
> I guess the git hash is not known until the code is written? (correct me if
> I'm wrong) As the coinbase message is consensus-critical, it must be part of
> the source code and therefore you
