(i.e. both can cause splits, but for different reasons)
-
-
Inaction is indeed often invalid. Otherwise Bitcoin has no rules at all, since light wallets are in a perpetual state of accepting invalid blocks. Otherwise softforks never succeed, since very rarely do 100% of nodes upgrade before activation.
-
Disagreed. The entire point of soft forks is to have a safe way to upgrade by being *backward compatible*. Backward compatibility implies inaction is a valid state. If you don’t care about backward compatibility, why bother with soft forks?
-
Softforks are backward compatible so long as miners are not performing attacks. It's a good attribute to have, but not relevant to the question at hand, where the miners are in fact attacking. During such circumstances, ex-full nodes are simply insecure.
-
The majority of users were not enforcing bip148. Had some miners dare to defy bip148's proposal, there would have been 2 used chains. You can't dictate that I'm an "ex-full node" for not enforcing bip148 against my will.
-
That's where you're wrong. A majority of the users supported BIP148, and even if it turned out not all of them were enforcing, a split would have pushed the supporters who didn't enforce to begin doing so.
-
There are 3 types of users: 1) users who actively supported BIP148 2) users who were aware but not supportive-including many pro-Segwit users. some prefered BIP149. 3) users who were completely unaware BIP148 were coercive & hurt groups 2 & 3. There's nothing "soft" about it.
-
You keep saying "a majority of users supported BIP148", but the truth is that there was no reliable way to measure this, beyond the r/bitcoin tiny community and unreliable Twitter polls- which have biased samples given the inherent nature of Twitter.
-
Also, of the users polled, not only did a majority support BIP148, but those who did not also either opposed Segwit in general, or said they would support BIP148 if Core released it in an official release. So BIP148 effectively had almost same community support as Segwit itself.
- 8 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
