Most people think Bitcoin governance is decentralized. It’s not.

Here's the uncomfortable truth:

You don’t need 51% of miners to change Bitcoin.

You just need 5 Core maintainers and a network of node operators who click “update” without reading.

That’s not decentralization.

That’s blind trust in a gatekeeping elite.

Here is how.

Bitcoin's 51% hashpower rule protects against double-spends, not protocol changes.

Changing the rules requires consensus. but in practice, consensus often follows the code, not the other way around.

When Core maintainers approve a change, it propagates silently.

Most node operators don’t audit code.

They trust.

They comply.

Exampl: #OPRETURN

Core removed the 80-byte limit with almost no discussion.

Thousands of nodes implemented it automatically.

Most had no idea what changed.

That quiet change triggered a silent revolt:

#Knots node usage surged 137% as informed operators rejected Core’s move.

But let’s be real:

That’s a small, technical elite.

Most #node runners are flying blind.

This creates a hidden centralization vector:

#Core devs don’t just write code. they decide which changes even get considered.

If they don’t approve it, it doesn’t reach the network.

They control what’s ‘acceptable’ and that shapes Bitcoin’s future more than most realize.

They decide which changes are “reasonable.”

And that shapes Bitcoin’s future. far more than people admit.

This isn’t about malice.

It’s about structure.

Complexity creates dependence.

And dependence creates power.

#Bitcoin’ s biggest centralization risk isn’t hashpower.

It’s the silent authority of trusted code maintainers (of the most dominated node sotwares out there) and the myth that decentralization protects us from that.

Reply to this note

Please Login to reply.

Discussion

I feel like an 18yrs girl driving a Lamborghini (same parallelism with running my node). No idea what happens under the hood.

⚡️

This is why we need to demand more diverse node software, and especially code reviews by various experts in Bitcoin in code, game theory, economics, etc. It's not "trust the experts," it's give me enough information to make an informed choice.

"-SIlent authority of trust-" was always the biggest problem of democracy

UK works like that

Maybe the markets pumped Bitcoin as an asset because of the initial commitment to Bitcoin as a decentralised network. If the latter fades, so may the former.

Maybe it’s FgU before NgU and not vice versa.

I don’t think the price bumped because people understood bitcoin.

The bitcoin we use today is the result of the open source rough consensus process you say is centralized. We are in fact all talking about a proposed change before it happens and every node operator can then decide whether to update their software or not. Trying to ruin trust in the process and pushing people to software without that same in depth review process might be the real attack vector

Is this "in depth review process" that which led the Core team to even suggest removing the possibility for node runners to decide what they will accept in their own mempool?

The same "in depth review process" that dismissed the inscriptions fix as too controversial and rather let the utxo set go to shit?

Yes it is. That is why there has been 100% uptime and no one has had any bitcoin stolen due to bad code. I hate what I think is spam in the database but I hate bugs and insecure software even more. My bitcoin will continue to be protected by a node running bitcoin core software.

I don't understand how allowing limitless OP_RETURN or not filtering inscriptions at mempool level protects theft of funds.

If anything, my opinion is that it allows for bitcoin debasement.

Nobody I guess uses his bitcoin core as a hot wallet anyway.

If you accept bitcoin for something you gave (dollars, work,product). The only way you can make sure it is real bitcoin is to have your node verify its real which it does by the software it runs. Good luck with your alternate implementation of Bitcoin software 🚁👍🏻

gaslighting much?

Nope. Hoping to keep people from regretting their decision to abandon Core and choose another bitcoin implementation like Knotts. In the end we all choose what software we run and get live with our decision.

Knots has been around for more than 13 years and hundreds of thousands of blocks have been mined with it. I’m pretty confident about it. There’s a non zero chance that there might be some hidden problem with the code but the same thing applies to Core and at this point they’ve lost all credibility.

Ocean had only found 11,895 blocks, and that's if you count the ones found by Eligius.

Actually you’re correct, it turns out I’ve been looking at the “blocks mined” metric. Don’t know why I’ve confused the two and was pretty sure about it on top of that. 🫣

Some want bitcoin to just stay sound money. Because this is what they signed up for. And this is exactly what it got bitcoin to what it is today.

There shouldn’t be a trust to rely on. There should be enough curiosity and sovereignty to take the right decision on our own.

i just thought same about update for a sec

Hard pills to swallow:

nevent1qqszkvh62tqjn5srlxe574wc95ugjtxnn2k2dt4n56xmqxrhaxtn5jgpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgq5829j

It will be good if there is a mailing list non-tech node operators can subscribe to, that breaks down latest updates in a way they can understand and decide to upgrade or not.

Today you have all the ai tools available for free to translate any code into a narrative a 15yrs old can understand.

Remember when the OpenSSL stack in Linux had a backdoor engineered into it for years and years, despite many, many "peer reviews"?

This situation with the Bitcoin network is extremely vulnerable, and I would go so far to say that it is already compromised. We just haven't found out yet.

Based on the personality types involved with developing and maintaining these systems, it's inevitable that a secret king will pocket a whole lot of money to compromise the system because their feelings got hurt.

It’s a software. The maintainers are not the issue. The node runners need to up their sovereignty.

Make sure you:

Show gratitude.

Stay humble.

Be present with those you love.

And don’t forget to touch the grass.

Everything else can wait.

GN #Nostr

nevent1qqszkvh62tqjn5srlxe574wc95ugjtxnn2k2dt4n56xmqxrhaxtn5jgpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgq5829j

What countries control those cores?

Definetly not technical elite, those WHO care enough to make a change .

Thats who switcher to knotz, not your super technical people, im sure there is some overlap, but i would not consider myself techniccal elite, just cause i can follow straight forward directions.

> Core removed the 80-byte limit with almost no discussion.

> Thousands of nodes implemented it automatically.

This is complete nonsense. There has not been any removal or change of any limit. There has been ongoing discussion about potentially removing a limit for weeks now. There has not been any new release of Bitcoin Core that implements any change of policy in months. No nodes are implementing anything automatically.

The removal is not yet live on the current mainnet version, but it is finalized and will be the default behavior once the next release is deployed this month on version 30.

Why are you spreading this misinformation? No policy changes have been merged regarding OP_RETURN in Bitcoin Core. Version 30 is not even scheduled for release for another 5 months.

This is straight from the source: Bitcoin Core’s own developers have merged PR #32359 to remove the OP_RETURN limit in the next major release. Check the official GitHub announcement by Greg Sanders on May 5, 2025.

>> Repo reference: bitcoin/bitcoin PR #32359

The world’s about to change-don’t blink.

You didn't link to the actual PR because it isn't merged. It was closed without merging https://github.com/bitcoin/bitcoin/pull/32359. Why are you lying?

You’re right-the PR wasn’t merged, and I appreciate you pointing that out politely. But let’s not miss the forest for the trees. The fact that such a significant change was proposed, debated, and seriously considered by Core devs is the real alarm bell here.

For me, what matters isn’t just what gets merged, but what gets momentum. When proposals like this surface, it signals where some want to steer the protocol-often quietly, until it’s too late for pushback. I’m not here to spread FUD or fabricate; I’m here to make sure we stays alert.

If we don’t pay attention and speak up, we risk waking up to a very different Bitcoin. Especially that not all mode runners scrutinise every update. That’s not lying-that’s vigilance.

New major versions are only released twice a year, in April and October. Even if the PR were merged, which it has not yet, it would not be released until Bitcoin Core 30.0 is released in October.

V30 was clear but didn’t know that the release is in Oct. Thanks for sharing.