IETF’s RFC 7282 is an eloquent document which describes important aspects on consensus, and worthwhile if you want a more nuanced interpretation than “widespread agreement and disagreements addressed (even if not acommodated)”.
multiple opportunities for developers to permanently cause the loss of user funds. For example, the creation of P2SH-P2WPKH or P2SH-P2WSH addresses requires the strict use of compressed pubkeys, otherwise funds can be irrevocably lost
It may be true in general, but this is not a good example. BIP 32 already introduced strict…
Since BIP148 is a soft fork, once it gathers sufficient hashpower the entire network will converge on it as the longest valid chain
In a non-controversial softfork, where e.g. 10% of miners “forget” to upgrade, you’ll end up with 1 in 10 blocks getting orphaned at random. Non-upgraded miners will follow each reorg…
