Thread

Replies (69)

- Soft fork with consensus could still result in a chainsplit (but maybe very short period of time) - Chainsplit created by soft fork is NOT meant to be permanent. - Nobody is talking about hard fork - Nobody is trying to PUSH this softfork with legal thereat. (Stop taking sentences out of the context and improve your reading comprehension skill) - On that note, feedback has been provided by @Bitcoin Mechanic to change the language Good job being CORECUCK image
A soft fork without consensus does *not* lead to a (lasting) chain split if and when a majority of hash power mines the soft fork chain. The non-soft fork chain will be re-org'ed out of existence every time the soft fork chain becomes longer, because non-upgraded nodes will switch to it. If users/miners on the non-soft fork chain want to prevent this, they need to take action to reject the soft fork chain. Luke is right about that.
🛡️
--> "A soft fork without consensus does *not* lead to a (lasting) chain split if and when a majority of hash power mines the soft fork chain" If the majority of hash mines, the software chain, then it's kind of back-in consensus, right? Theoretically: All forks eventually *get resolved* it's a matter of when. As they're being *resolved*, they are _out of consensus_
Do you have any good resources you can point me towards to understand your arguments here? Relatively new bitcoiner and I am having trouble navigating this debate to choose the software I want my node to run on. I think I understand the core pov. I think I understand the knots pov. Both from a semi technical perspective. What I am struggling with is reconciliating the governance methods. Core v30's decision to "censor" the debate on GitHub, and Dashjr's decision to soft fork or whatever he wants to do. I don't think I understand why either camps took these measures. Neither of them seem like a gesture of good faith and/or rational thinking.
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.
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.