forks happen without the need for every node user to form consensus. this is done by rejecting old style blocks to only accept new block formats. thus the only blocks that propagate are the new style. this causes old nodes still listening to old blocks to get forked off..
You are telling only part of the truth that suits your agenda.Nodes accept all blocks that are valid before the set target and check how many of those block are signalling for the change. If the total number is bigger than an agreed percentage (usually more than 95% which is the case with SegWit) they consider the change locked-in and if the remaining minuscule minority (ie. 5%) goes against the change their block will be rejected.
If they see that the threshold is not reached (eg. 94% signalling) they will go ahead as before without enforcing the change and reject any block that goes ahead with the fork.
Quote
you might want to check devs own wording of bip148
https://github.com/bitcoin/bips/blob/master/bip-0148.mediawiki
mandatory 'activation day flag" is mentioned a few times
BIP-148 was never used to activate anything and I personally consider it an attack against bitcoin.https://github.com/bitcoin/bips/blob/master/bip-0148.mediawiki
mandatory 'activation day flag" is mentioned a few times
You bringing up here as an argument is another reason why people consider your posts FUD.
Quote
the NYA signalling threshold which activated the bip 148
This is a lie.Quote
that then disregarded old blocks to fake a 100% listing of bip9 segwit blocks
You keep repeating the same lie but "disregarding a block" means chain split. Show us the chain split that happened in 2017 with the blocks that weren't signalling and were disregarded? You can't because there was no such thing.Quote
i even sent you the pretty picture many times
this image is not some made up gameplay. its graph is actual references to actual flags in block data. and the flags are reference numbers used by actual bips. which actually activated feature in actual code
And it contradicts what you said 2 sentences above about miners signalling BIP148 which they are clearly signalling something else!this image is not some made up gameplay. its graph is actual references to actual flags in block data. and the flags are reference numbers used by actual bips. which actually activated feature in actual code
Quote
and look. boom loads got onboard.. WITHIN DAYS(literal vertical line straight up)
If you bother to look at any other fork, they look pretty much similar. From BIP16 (P2SH) to BIP340-3412 (Taproot) they activated in more or less a similar way where miners wait until last moment and suddenly they all signal within days to get the 95% threshold (or the high threshold required for that fork) and remain up for the next 2 weeks.