The short version: Bitcoin has no board, no CEO and no vote. Changes happen only when nearly everyone independently chooses to run software that agrees — which makes upgrades slow, boring and extremely hard to force. That isn't a flaw in the governance. It is the governance.

There are seven cats at the colony and not one of them is in charge.

There's an older tabby the others defer to at the bowl, but his authority ends there: he can't make anyone sleep somewhere, can't stop the new one using the good corner, and can't change feeding time. What looks like structure is really a set of arrangements each cat has independently decided to go along with, because going along with it works out better than not.

Change one cat's behaviour and nothing changes. Change most of their behaviour at once and the arrangement is simply different now. There was never a meeting.

This is close to the most misunderstood thing about Bitcoin, and the misunderstanding runs in both directions — people think someone is secretly in charge, or they think nobody being in charge means nothing can ever change.

1. What the rules actually are

Bitcoin's rules aren't a document. They're whatever the software that people run enforces.

Your node checks every block against its own copy of the rules: the 21 million limit, the signature requirements, the block size, the halving schedule. If a block breaks any of them, your node rejects it — regardless of how much mining power produced it, who endorsed it, or what any company announced.

So "the rules of Bitcoin" is a shorthand for the overlap between what everyone's software independently accepts. Anything outside that overlap isn't Bitcoin as far as the people outside it are concerned, no matter what it's called.

That's why running a node matters even if you never notice it doing anything. It's not symbolic participation. It's the thing that makes the rules enforceable by you rather than on you.

2. Soft forks: the only practical way in

Two ways to change the rules.

A hard fork loosens them — it makes previously invalid things valid. Old software rejects the new blocks, so everyone must upgrade or the network splits into two chains. In a system with no authority to coordinate "everyone", this is close to impossible to do without a schism, and the attempts have produced exactly that.

A soft fork tightens them — it makes some previously valid things invalid. Old software still accepts the new blocks, because the new rules are a subset of the old ones. Nodes that haven't upgraded carry on, unaware, still in consensus.

Nearly every change Bitcoin has made has been a soft fork, and that isn't a coincidence or a stylistic preference. It's the only kind of change that doesn't require permission from everyone simultaneously. Backwards compatibility is the mechanism that makes evolution possible without a coordinator.

The cost is severe, and it's deliberate: anything that would need loosening a rule is effectively off the table forever. That's not a limitation anyone is working to remove. It's the thing that makes "21 million" a fact rather than a policy.

3. How it actually happens

The process has no official status anywhere, which is why descriptions of it vary. Roughly:

Someone proposes. A written specification, published, discussed on public mailing lists. Anyone may write one. Most go nowhere.

Years of review. Not an exaggeration. Proposals get attacked, rewritten, implemented in test environments, attacked again. The good ones get narrower over time.

Implementation and activation signalling. Miners signal readiness in blocks; node operators choose whether to run software enforcing the new rule. Different activation mechanisms have been used and the choice of mechanism has itself been bitterly contested.

It happens, or it doesn't. There is no deadline and no one to appeal to.

It's slow in a way that frustrates everyone, including the developers. That slowness is the only defence a system without authority has against capture — any process fast enough to be convenient is fast enough to be pushed.

4. Who decides, honestly

The uncomfortable answer: nobody, and that creates a vacuum various groups keep trying to fill.

Developers write the software, which is real influence — but they cannot deploy anything. Code nobody runs is a text file.

Miners order transactions and signal for upgrades, but cannot change the rules. Miners producing blocks your node rejects have produced nothing; they've just spent electricity.

Node operators — including you, if you run one — decide what is valid by choosing what to run. This is where final authority sits, and it's diffuse to the point of being hard to see.

Exchanges, custodians and large holders have enormous practical influence, because most users experience Bitcoin through them. If major custodians adopt a rule, most people follow without a decision. This is the real centralising pressure, and it grows as fewer people hold their own keys.

Users decide what "Bitcoin" means by what they'll accept as payment and what they call it. Ultimately that's the only vote that resolves a genuine dispute — which has been tested, and it settled the question.

5. The uncomfortable half

Rough consensus is a polite name for something messier. There's no defined electorate, no threshold, no tiebreaker. Who counts as "the community" is decided by whoever is arguing. Past disputes were resolved partly by argument and partly by exhaustion, social pressure, and who controlled which forums — and anyone presenting that history as a clean deliberative process is selling you a myth.

Developer influence is more concentrated than the ideology suggests. The number of people who deeply understand the consensus code is small, their funding comes from somewhere, and "nobody is in charge" sits awkwardly beside the reality that a handful of contributors shape what is even considered. That's not corruption; it's expertise, and expertise concentrates. But it's a real centralisation that the standard account glosses over.

Ossification cuts both ways. Celebrating that Bitcoin is hard to change is reasonable right up until something genuinely needs changing — a cryptographic weakness, a long-term fee-market problem. A system that can't be captured is also a system that can't be rescued quickly, and the same people are usually enthusiastic about the first half and quiet about the second.

And most users have opted out of this entirely. All of the above describes authority resting with node operators. The majority of people holding bitcoin don't run a node and would follow whatever their exchange did. The decentralised governance is real at the protocol layer and increasingly theoretical at the human one — which is an argument for running a node that I find more persuasive than any of the usual ones.

The tabby controls the bowl and nothing else, and no one ever elected him to that either. Authority that can't be pointed at is hard to capture — and just as hard to call on when you want something done. 🐾⚡