The Bitcoin core devs are making changes that do not benefit Bitcoin.
Here is some history from myself and others if you want to know more:
nevent1qvzqqqqqqypzp6pmv65w6tfhcp73404xuxcqpg24f8rf2z86f3v824td22c9ymptqyv8wumn8ghj7enfd36x2u3wdehhxarj9emkjmn99uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcprfmhxue69uhhyetvv9ujuem9w3skccne9e3k7mf0wccsqgra6vnf7sc33vj356ak75430ungrulrndajawp3g45y6ndzyu6hwch652na
nevent1qvzqqqqqqypzpprrqa5g5z0vzy5k06c9gnnc485gcj84qufv88k5j8ljkmaqrxhgqy8hwumn8ghj7mn2w4khqtndv5hszythwden5te0dehhxarj9ekxzmny9uqzqvjuuget8yrmhphpp2y9lcj6dd8gfeqd7eh9cfmc5exzh6njlawva7tza6
nevent1qvzqqqqqqypzqpxfzhdwlm3cx9l6wdzyft8w8y9gy607tqgtyfq7tekaxs7lhmxfqqsg0ewq767afwyzhcp6gnmxyrutcvuzy3h2d2y8pvwugn0h6hp8fcq6ve5r3
Login to reply
Replies (4)
Looks like that change is sitting on 41 NAKs and counting. Maintainers tend to steer clear of merging things that controversial. It’s really just a small group pushing hard for it—but we’ll see how it plays out.
Knots is a tricky one. It’s got a modest but real user base and it does implement the Bitcoin protocol. But it also opens up a tough question: what happens when there are two slightly different sets of rules?
On one hand, that increases the risk of a chain split if one set changes and the other doesn’t. On the other, it might slow things down—in a good way—by making it harder to push through changes without broad consensus. aka ossification.
At the end of the day, we’ve got to remember why people run nodes in the first place: to uphold the rules and take part in protecting the network. It’s all about user agency. And we're only just beginning to figure out how to really support that.
Is a chain split a real possibility?
C'mon Mike she just got her node up and running,
You can advise her maybe to not update core for a while until the dust settles 🤣
Thank you for this. It’s like one rabbit hole after another here 😌😅