Thread

nobody can easily change bitcoin many want to control it the value is that they cannot

Core easily changed Bitcoin.

core did not change bitcoin the rules of the network literally did not change

Nope. Not true.

Core changed the fundamental use-case of Bitcoin. It used to be a ledger, now it's storage. Changing the rules of what can be put on the network indirectly and profoundly changed the network.

That’s not true to what was done. I understand we’ve all been fed a ton of different versions but this is fundamentally untrue.

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.

The problem is that core30 adoption is growing quickly, increasing the risks of corrupting the BTC chain for all node runners.

But core30 trying to change Bitcoin network to data storage. Bitcoin is money!

I am using Clark Moody's dashboard (

Clark Moody Bitcoin

Dashboard

The entire Bitcoin economy at a glance

) where core30 is at 7.3%. Wow, that is fast adoption. Boy, was I wrong to assume that node-runners would choose not to upgrade. Let's hope that many would have manually configured the OP_RETUTN max value to the previous limit.

- soft forks without consensus result in a chainsplit - bcash was a hard fork with minority support so it trended to zero

Good parrot.

Whatever you said, Bitcoin is money and I will never allow anyone to dirty my money

Too late.

nope

Ordinals, inscriptions.

Only idiots like you continue with those fake news. But the spammers who exploit those weaknesses are actually scared from policy filters. Policy filters that work and kept OP_RETURN clean of data bigger than 82 Bytes.

No, it objectively is not a hard fork.