Thread

Replies (39)

- soft forks without consensus result in a chainsplit - bcash was a hard fork with minority support so it trended to zero - more people should use their own bitcoin node, they can run whatever software they want - if the desire is to try to push through a soft fork with legal threats that is lame as fuck and will probably fail
Not every soft fork leads to a chain split. While Taproot and Segwit have dissent, they haven’t resulted in a split. There’s a non-zero probability that CSAM on nodes can be outlawed, which can’t help adoption. While everyone can run their own node, not everyone is savvy enough to patch their bitcoin software, unless you make a highly customizable version.
Orphaning blocks the majority of miners recognize for its economic incentive will result in a chain split from the minority. The debate was over when over 50% of hash rate was in favor of higher OP_Returns. I do not see a world where this doesn't end with 2 chains. Tread the waters carefully because your PoW is stored on the chain that has the hashrate consensus.
Am I too dumb, or am I missing something? I thought that if the majority of people refuse to upgrade to #core30 or decide to run #knots, then the nodes will simply reject the those blocks with the core30 #OP_RETURN increased values as invalid / violarong the prior consensus, keeping the #bitcoin #timechain intact. Thus, if core devs want to still be relevant, they will kinda have to reverse the change. No need of a #softfork; no need of a #hardfork. #btc is freedom, and that means choice. The node-runners are free to choose.