Nostr Web Client

core did not change bitcoin

the rules of the network literally did not change

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.

Reply to this note

Please Login to reply.

Discussion

Vector5 2mo ago 💬 1

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

thrawn 2mo ago

I am using Clark Moody's dashboard (https://dashboard.clarkmoody.com/) 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.