Bitcoin Dictionary Name and picture from twetch — not on-chain. The signature is; the profile is not.

One of the strangest failures in the modern blockchain world is that people routinely treat systems designed for digital cash as though the security model for a five-dollar transaction should also secure a lifetime of savings.

That is not merely poor operational practice. It is a category error.

Digital cash has different uses, different values at risk, and therefore different security requirements. A person buying a coffee does not need the same security architecture as a person protecting $5 million. Yet much of the BTC community has converged on precisely this absurd position: one device, one key, one point of failure, regardless of the value being protected.

Then, when a device is compromised, people blame the device.

The deeper problem is the architecture they chose.

Bitcoin always allowed far more sophisticated key-management arrangements than the simplistic single-key model that has become culturally dominant. Multiple keys, multiple signers, different spending conditions, and more elaborate transaction structures are not alien additions to the system. They arise naturally from the underlying scripting and transaction model.

The mistake has been treating the simplest possible transaction as though it were the appropriate transaction for every possible economic use.

It is not.

A Key Is Not a Security Architecture
A private key is a credential.

It is not, by itself, a complete security system.

If possession of one key is sufficient to transfer a significant asset, then anyone who obtains that key has effectively obtained the asset. That means the entire economic value being protected has been collapsed into the security properties of one credential and whatever device happens to contain it.

For small, casual transactions, this may be entirely reasonable.

If someone keeps the digital equivalent of petty cash on a phone or small hardware device, accepting a limited level of risk may make economic sense. People have always done this with physical cash. Nobody normally carries the contents of a retirement account in a wallet simply because a wallet is convenient for buying lunch.

Yet that distinction has been forgotten with blockchain systems.

The same mechanism used to authorise a trivial payment is routinely used to secure enormous holdings.

This is security engineering turned upside down.

The level of protection should be determined by the value being protected, the consequences of compromise, the threat model, the recovery requirements, and the acceptable operational burden.

Security is contextual.

Defence in Depth
Serious security has always been based on defence in depth.

No competent security architect assumes that one mechanism will never fail.

Systems fail. Hardware fails. Software contains vulnerabilities. People make mistakes. Supply chains can be compromised. Credentials can be stolen. Backups can be lost. Locations can burn down. Individuals can become unavailable.

The purpose of defence in depth is not to pretend that these events cannot occur. It is to design a system in which the failure of one component does not result in catastrophic loss.

That principle is hardly novel.

Banks do not secure vaults with one lock.

Military systems do not protect critical assets with one control.

Large corporations do not normally allow a single employee with a single password to transfer the entire corporate treasury.

Aircraft do not depend upon one instrument.

Critical infrastructure does not deliberately create single points of failure where inexpensive redundancy is available.

Yet people will place millions of dollars of blockchain value behind one private key stored on one hardware device and call this sophisticated security.

It is not sophisticated.

It is concentration risk.

The Hardware-Wallet Fallacy
Hardware wallets can be useful tools.

They are not magic.

A hardware wallet is still a device. It contains hardware, firmware, software interfaces, manufacturing dependencies, update mechanisms, communication channels, and assumptions about how the user interacts with it.

Every one of those creates potential failure modes.

When a hardware-wallet exploit appears, the useful question is not merely, “How could this particular device have been attacked?”

The more important question is:

Why was compromise of one device sufficient to compromise the asset?

If the answer is that the entire holding could be moved using a single key controlled by that device, the security architecture was already fragile before the exploit was discovered.

The device vulnerability merely exposed the fragility.

This distinction matters.

A vulnerability in one component should ideally compromise one component.

It should not compromise the entire system.

That is precisely what defence in depth is designed to prevent.

Five Keys, Three Required
Consider a comparatively simple example.

A substantial holding could be controlled using five independently generated keys, with any three required to authorise a transaction.

The keys could be placed on five different devices.

Those devices could use different hardware.

They could be stored in different physical locations.

One could be kept at a residence.

One in a bank safe-deposit facility.

One in a corporate office or professional custody location.

One with a trusted legal or fiduciary arrangement.

One in another geographically separated secure location.

The important point is not these particular locations. The architecture must reflect the actual circumstances.

The point is separation.

Now consider what an attacker must achieve.

Stealing one device is insufficient.

Compromising one firmware implementation is insufficient.

Breaking into one location is insufficient.

Obtaining one backup is insufficient.

Convincing one individual to sign a malicious transaction is insufficient.

Even the simultaneous loss of two keys does not necessarily destroy access to the asset.

The security problem has changed fundamentally.

Instead of asking whether one device can be perfectly secured forever — an unrealistic objective — the system asks whether an attacker can compromise several independently protected components before the legitimate owner detects or responds to the attack.

That is a much stronger proposition.

Independence Matters
Simply creating five copies of the same key does not provide the same protection.

Nor does generating five keys on the same compromised machine and storing them beside one another.

Defence in depth requires meaningful independence.

Different devices reduce common-mode hardware failure.

Different locations reduce physical concentration risk.

Independent key generation reduces the consequences of a compromised random-number generator.

Different administrative control can reduce insider risk.

Different backup mechanisms reduce correlated recovery failure.

Geographic separation reduces exposure to fire, flood, seizure, theft, or other localised events.

The entire point is to prevent one failure from propagating through every layer.

A security system that appears redundant but contains the same hidden dependency in every component may provide little genuine redundancy at all.

This is basic systems engineering.

Security Should Scale With Value
There is no universal number of keys that is correct for every circumstance.

That would miss the point.

A person protecting $50 may quite rationally use one key.

A person protecting $5,000 may choose somewhat stronger controls.

A business protecting $5 million should have a substantially different architecture.

An institution protecting hundreds of millions should probably have another level again, with formal governance, segregation of duties, transaction limits, approval procedures, auditable controls, recovery protocols, and institutional key management.

Defence in depth has a cost.

Additional keys create additional complexity.

Additional signers create operational overhead.

Geographic separation creates inconvenience.

Recovery arrangements require planning.

But security expenditure should be considered relative to the value being protected.

Spending $50,000 designing and operating a security architecture around $5,000 of value would be irrational.

Refusing to spend meaningful resources securing $50 million because a single hardware wallet is convenient is equally irrational.

The architecture should be proportionate.

The Failure of the “Standard Transaction” Mentality
A larger conceptual problem lies underneath all of this.

The BTC ecosystem increasingly treats a narrow set of conventional transaction patterns as though those patterns define what Bitcoin is supposed to be.

The transaction most commonly used becomes the transaction considered normal.

The transaction considered normal becomes the transaction considered legitimate.

Eventually, people start designing their economic behaviour around the limitations of that convention.

That reverses the relationship.

Bitcoin was designed as an electronic cash system.

Cash is used differently depending upon the transaction.

The amount matters.

The parties matter.

The commercial context matters.

The required controls matter.

The risks matter.

There is no sensible reason to assume that the transaction architecture appropriate for buying coffee must also be the transaction architecture appropriate for securing a corporate treasury.

The underlying system allows conditions to be constructed.

Keys can be combined.

Signatures can be required in combinations.

Spending rules can reflect business processes.

Controls can be layered.

Transaction structures can reflect the economic reality they are supporting.

Yet remarkably little of this receives serious attention because the ecosystem has spent years reducing everything to the question of how to store “the seed phrase.”

That is already the wrong abstraction.

A Seed Phrase Is a Backup Mechanism, Not Wealth Management
The cultural fixation on seed phrases demonstrates the problem.

People are taught to write down twelve or twenty-four words.

Hide them somewhere.

Put them on metal.

Store them in a safe.

Perhaps divide them somehow.

Then they are told that they have secured their wealth.

But if those words reconstruct one key hierarchy capable of moving everything, the system may still have one fundamental authorisation boundary.

Protecting the backup more carefully does not necessarily remove the single point of failure.

It merely protects the single point of failure more carefully.

There is a difference.

Real security engineering asks how many independent failures are required before the protected asset can be taken.

It asks what happens if one signer is compromised.

It asks what happens if one device manufacturer fails.

It asks what happens if a backup is discovered.

It asks what happens if one location becomes inaccessible.

It asks what happens if the owner dies.

It asks what happens if an employee becomes malicious.

It asks what happens if a signing device displays a false transaction.

It asks whether transaction value limits should exist.

It asks whether abnormal transfers should require additional approval.

These are ordinary questions in financial security.

They should be ordinary questions in digital cash.

Cash Does Not Mean Carelessness
There is another linguistic trap.

Calling Bitcoin cash does not mean saying that every holding should be treated casually.

Physical cash itself demonstrates the opposite.

A person may carry fifty dollars in a pocket.

A shop may hold several thousand dollars in a till and safe.

A bank may hold vastly greater sums behind vaults, controls, procedures, staff separation, surveillance, insurance, accounting systems, and legal processes.

It is all money.

The security architecture changes with scale.

Digital cash should be no different.

The phrase “small casual transactions” matters because it identifies an economic category.

Small transactions can tolerate different security assumptions from large ones.

That does not mean the system itself is restricted to small transactions. It means the security and operational architecture should change as value and purpose change.

The mistake is taking an arrangement suitable for small casual payments and elevating it into a universal custody model.

The Cold-Card Lesson Is Larger Than Cold Cards
Any individual hardware exploit should therefore be understood as part of a larger lesson.

If compromising one signing device can result in catastrophic loss, the asset owner must ask why the system was designed so that one compromised device had catastrophic authority.

The correct lesson is not that another manufacturer will necessarily solve the problem.

The next device may have another vulnerability.

And the next.

Perfect hardware does not exist.

Perfect software does not exist.

Perfect users do not exist.

The objective is not to discover the one flawless device.

The objective is to create a system that remains secure when individual components are not flawless.

That is defence in depth.

Bitcoin Can Support Better Security Than the Culture Around It
The frustrating part is that much of the necessary capability is not conceptually difficult.

It is not necessary to redesign digital cash from first principles merely to recognise that valuable assets should not depend upon one key.

Bitcoin's transaction model was capable of supporting multiple signatures and conditional authorisation from very early in its history.

More elaborate systems can be built on top of those primitives.

Businesses can implement approval structures.

Families can create inheritance arrangements.

Investment holdings can be separated from transactional balances.

High-value transfers can require additional signers.

Different classes of transaction can use different security policies.

Organisations can separate authority between officers.

Emergency recovery mechanisms can exist without making everyday spending cumbersome.

The system can be designed around human and institutional reality.

But that requires people to stop thinking of a Bitcoin wallet as though it were simply a password-protected bank account.

It is not.

It is a mechanism for satisfying spending conditions.

Those conditions can be designed.

Separate Spending Money From Stored Wealth
A rational architecture begins by recognising that transactional cash and stored wealth are different problems.

A person might maintain a small single-key balance for everyday spending.

That wallet can be convenient.

It can live on a frequently used device.

Losing it would be annoying but not financially catastrophic.

A separate savings structure could use three-of-five authorisation.

A larger institutional reserve could use still more elaborate controls.

This is analogous to the physical world.

People carry wallets.

They have bank accounts.

Businesses have treasury controls.

Banks have vaults.

Nobody finds it surprising that these systems use different levels of security.

Digital systems should not somehow suspend the economics of risk merely because all the assets happen to be represented electronically.

Stop Optimising Only for Convenience
The industry has spent an extraordinary amount of effort eliminating friction.

One click.

One device.

One seed.

One signature.

One interface.

Convenience is valuable.

But convenience is not the only engineering objective.

Security deliberately introduces friction when the cost of an unauthorised action is high.

A nuclear launch system that required one person to press one convenient button would certainly be easy to use.

That would not make it well designed.

A corporate payment system in which one junior employee could transfer the entire company treasury would be wonderfully convenient.

It would also be negligent.

The same reasoning applies here.

For small payments, minimise friction.

For large transfers, introduce controls.

For substantial savings, eliminate unnecessary single points of failure.

For institutional assets, build institutional security.

The system should reflect the value at risk.

The Real Failure Is Conceptual
The recurring security failures around blockchain holdings are therefore not merely failures of cryptography or hardware.

They are failures of economic thinking.

People have conf

The precise claim is not that Taproot makes the initial theft of BTC easier. Theft still requires compromised keys, fraud, coercion, a custodial breach or some other failure of control.

What Taproot makes easier is concealing what happens afterwards.

Before Taproot, different forms of spending often left different on-chain fingerprints. A conventional signature, a multisignature arrangement and a complex script could frequently be distinguished by examining the transaction structure. Taproot deliberately reduces those distinctions. A key-path spend can make an ordinary payment, a cooperative multisignature spend and the settlement of a more complicated contract appear substantially alike. If a script path is used, only the executed branch must be revealed rather than the entire set of possible conditions. That privacy improvement is not an accidental side effect; it is stated explicitly in BIP 341.

Schnorr signatures extend the effect. Multiple parties may cooperate to produce what appears on-chain to be a single ordinary signature. MuSig2 outputs controlled by several signers can therefore be indistinguishable from single-signer Taproot outputs. Adaptor-signature constructions may also hide contractual relationships and reblind secrets between payment hops, making linked operations resemble unrelated ordinary transactions.

This does not mean Taproot itself is a mixer. CoinJoin existed before Taproot. CoinJoin combines the inputs and outputs of several users so that the public ledger no longer provides an obvious one-to-one mapping between payer and recipient. It disrupts the ordinary heuristics used to follow ownership across transactions. Modern research still identifies many CoinJoin structures and sometimes reduces their effective anonymity sets, but attribution after mixing remains substantially more difficult than following an ordinary transparent payment.

Taproot makes the surrounding environment more accommodating to concealment because complex arrangements can be made to resemble ordinary spends. The forensic analyst sees less structure, fewer disclosed conditions and fewer obvious distinctions between individual control, collective control and contractual settlement.

Lightning then moves much of the relevant activity away from the public blockchain entirely.

The base chain records the funding and eventual closing of a channel. It does not contain a complete public ledger of every intermediate Lightning payment made while that channel remains open. Lightning uses onion routing so that an intermediate node normally learns only where a payment came from immediately and where it must go next. It does not receive the complete route, and the packet is altered at each hop. The specification nevertheless acknowledges that traffic analysis may still associate activity.

This creates an obvious attraction for anyone attempting to obscure the movement of stolen funds. Coins may enter Lightning through one channel, move through several privately routed transfers, be exchanged against other channel liquidity, and later leave through a different channel or service. The blockchain records the outer transactions, but not a complete public chain of every internal transfer connecting them.

That is not the same as saying there is “no record”.

Lightning nodes may retain local records. Custodians and exchanges may possess customer information. Channel topology, timing, amounts, network surveillance and operational mistakes may reveal relationships. Academic work has demonstrated cross-layer techniques capable of linking Lightning nodes to Bitcoin addresses and inferring information about balances, senders and recipients. Lightning privacy is consequently meaningful, but neither absolute nor guaranteed.

The accurate conclusion is therefore more serious than the exaggerated one.

The next twenty years will change the world, though not in the manner currently advertised by those who mistake a product demonstration for destiny.

AI will not “take over”. Large language models will improve. Reasoning systems will become more capable. Tools will become faster, more precise and more deeply embedded in ordinary work.

But tools do not abolish knowledge. They increase its value.

A person trained in art history, visual composition and the proper language of style can produce a far better image with an AI system than someone who merely types “make it beautiful”. The machine supplies execution. The human supplies vocabulary, judgement, context and purpose.

The same is true in law, science, engineering, literature and economics. An untrained person may obtain an answer. A trained person can recognise whether it is coherent, incomplete, derivative or wrong.

The divide will not be between humans and machines.

It will be between people who understand their field and can direct the tools, and people who use the tools without understanding what they are asking for.

Education must therefore change.

We do not need to preserve every manual trick merely because earlier generations lacked calculators, computers or models. We do need people who understand the underlying ideas well enough to use those tools intelligently, test their outputs and improve upon them.

The purpose of education is not to make the student imitate a machine.

It is to ensure that, when the machine produces something, the student knows what it means.

The alternative is not “no governance.” The alternative is governance made invisible.

If a small group of developers, maintainers and institutional gatekeepers can alter the protocol whenever they consider it necessary, then they possess control. Calling their decisions “upgrades” does not make the power disappear. It merely gives authority a more fashionable vocabulary.

A decentralised system is not one in which everyone may watch a handful of people rewrite the rules. It is one in which no handful of people can rewrite them at all.

Stable rules force ambition to compete within the system. Mutable rules allow the ambitious to capture the system itself.

So yes, I prefer a protocol that cannot be casually redesigned by whichever committee presently mistakes influence for wisdom.

When people can change the rules, they govern.

When they govern, they control.

And when control is concentrated, “decentralisation” becomes little more than a charming word printed on the chains.

Bitcoin does not have a king.

That was rather the point.

Yet those who proclaim decentralisation most loudly seem perpetually desperate to find a sovereign. They want Satoshi returned, seated upon a throne, and required to tell them which rules to follow, which changes to approve, and what Bitcoin is permitted to become.

It is the same impulse directed at John Galt in Atlas Shrugged. The system has failed, the institutions have exhausted themselves, and those responsible demand that the one person who refused their authority return and provide the answers.

They do not want freedom. They want a superior ruler who agrees with them.

But Satoshi’s answer is already there.

The protocol was released. The rules were established. The design was set in stone so that neither its creator nor any later committee could become sovereign over it.

Bitcoin requires no king because it was designed to make kings unnecessary.

You are free to build upon it, compete through it, and create whatever you can imagine. What you are not entitled to do is seize the foundation, rewrite the rules, and call your authority decentralisation.

They keep asking, “Who is Satoshi, and what would he tell us to do?”

The better question is why they need anyone to tell them at all.

John Galt refused to govern men who would not govern themselves.

Satoshi left a protocol that did not require him to return.

Calling a fee-paying, rule-valid transaction "spam" is not an engineering classification but an admission-control decision, and admission control is governance. Any system that decides which paying users may transact — by payload type, purpose, "standardness", or escalating penalties on disfavoured uses — has instituted a permission regime, acquired regulators who cannot say who they are or how they may be removed, and abandoned the one property that made it distinctive.

The remedy for scarce block space is not moral categories but arithmetic: scale the capacity, price the resource including its externalities, and let payer and miner settle it between them.

But calibration on one dataset does not necessarily transfer to new domains, adversarial prompts or long reasoning chains. Token probability is not the same as claim correctness. Verbal confidence can be shaped by style training. Retrieval introduces another failure layer: a model can retrieve an authoritative source and still misinterpret it.

A complete system needs:

Claim-level rather than token-level uncertainty.
Separation of epistemic and aleatoric uncertainty.
Source provenance.
Contradiction detection.
Reliable abstention.
Active information seeking.
Explicit tracking of assumptions.
Verification proportional to consequence.
Confidence that remains calibrated after tool use and multi-step reasoning.

Recent work demonstrates that calibration can be trained separately from raw factual accuracy, which is promising but also illustrates that capability and epistemic honesty are different variables. Behaviourally Calibrated Reinforcement Learning

A solution would be an AI whose reported uncertainty remains predictively meaningful across unfamiliar domains, which knows when further evidence is required and which does not convert uncertainty into fluent invention.

AI has advanced enormously, but we still have a long way to go. Three fundamental technical problems remain unsolved: causal world models, continual learning, and reliable long-horizon reasoning.

The first is causal world models.

Current AI is exceptionally good at learning statistical relationships. It can predict what usually follows from what it has previously encountered. But prediction is not the same as understanding cause and effect.

An intelligent system must distinguish between “X predicts Y” and “changing X will cause Y.” It must understand interventions, hidden variables, physical constraints and counterfactuals: What will happen if I take this action? What would have happened if I had acted differently?

This matters because an agent changes the world in which it operates. Once it acts, historical correlations may no longer hold. A system that cannot construct a reliable causal model will remain brittle outside familiar situations.

Video generation is not a world model. Producing realistic-looking futures does not prove that the system understands objects, persistence, agency, physics or causation.

The real breakthrough will come when AI can enter an unfamiliar environment, discover its causal structure through limited observation and experimentation, and accurately predict the consequences of genuinely novel actions.

We cannot do that reliably yet.

They will tell you not to listen to me.

Not because I demand obedience, but because I refuse to offer it.

They will tell you I am dangerous because I ask you to think for yourself. Institutions have always found independent thought rather inconvenient; it cannot be licensed, managed or reliably directed toward the approved conclusion.

They say, “Be free—but agree with us.”

I say, be free and think whatever the fuck you want.

Agree with me. Reject me. Challenge me. Prove me wrong. But do it because you examined the argument, not because someone instructed you which ideas were safe to hear.

I am not selling you another doctrine.

I am asking you to stop renting your mind from people who call conformity freedom.

Think.

That is where liberty begins.

Most people do not reject truth because it is difficult to understand. They reject it because it is expensive to accept.

Illusion is comfortable. It asks nothing, disturbs nothing and permits a person to continue admiring the architecture of a life built upon assumptions.

Truth is less courteous.

It enters without invitation, rearranges the furniture and points out that the house was never quite as sound as everyone pretended.

To see clearly is not always a blessing. It can isolate, unsettle and deprive one of the consolations that make ordinary life bearable. But once something has been seen honestly, pretending otherwise becomes a form of self-betrayal.

Most people prefer peace purchased through illusion.

A few prefer discomfort purchased through understanding.

The first group sleeps better.

The second wakes up.

Artists and independent creators have been herded into increasingly elegant pens.

Spotify, Sony and the other great intermediaries offer distribution, discovery and scale, but they also control access, visibility, payment and the terms upon which the creator may reach an audience. The gatekeeper has not disappeared. It has merely acquired an app.

That arrangement is not inevitable.

The promise of Bitcoin is not simply cheaper payment. It is institutional independence.

A creator should be able to operate a platform they control, establish their own commercial relationships, distribute directly, receive payment directly and retain the records that connect them to their audience. They may still choose to use publishers, streaming services, promoters or social networks, but those services become optional complements rather than compulsory landlords.

That distinction matters.

Freedom does not require rejecting every intermediary. It requires the ability to leave one without losing one’s identity, customers, income and work.

A genuinely decentralised system allows the actor to build, promote, transact and organise without first seeking permission from a corporation that can alter the rules, suppress visibility or change the revenue split after dependence has been created.

The creator may use other platforms, but is no longer imprisoned by them.

That is decentralisation.

Not thousands of people renting space inside the same corporate enclosure, but individuals possessing the practical ability to build their own gate, choose whom to admit and walk away when another person begins behaving as though the gate belongs to them.

A stable protocol does not abolish ambition. It does something far more intelligent: it forces ambition to compete under rules it cannot rewrite.

Madison understood this perfectly. Power is not made harmless by pretending it does not exist. It is restrained by arranging institutions so that one ambition checks another, and no participant may quietly convert influence into sovereignty.

That is what a stable protocol should accomplish.

Ethereum and BTC have achieved the opposite while retaining the slogan. Their followers repeat “decentralisation” as though repetition were architecture, while accepting systems in which developers, foundations, maintainers and influential institutions may alter the rules beneath them.

The irony is exquisite.

They imagine themselves resisting authority while reciting the doctrine of those who exercise it. They praise freedom, then celebrate every mechanism by which a small group may redefine the terms of participation.

They have not broken their chains.

They have polished them, branded them, and placed them around their own necks.

There is a reason the largest corporate players—and trillions of dollars in institutional capital—prefer BTC.

It is not threatening.

BTC does not remove their role. Restricted capacity pushes ordinary users towards exchanges, custodians, ETFs, payment channels and managed services. Instead of allowing everyone to transact directly, it recreates dependence upon the same institutions Bitcoin was designed to route around.

Corporations can accommodate an asset they custody, package, regulate, trade and sell access to. What threatens entrenched power is a fixed, scalable protocol that lets anyone accept payments, create services and compete globally without permission.

They do not fear “digital gold”. They understand gold.

They fear open competition at the edges.

Think about the inversion for a moment.

I am the one who has been villainised for defending the individual—for insisting that Bitcoin must have a fixed protocol so that no developer, corporation, exchange or foundation can seize control of it.

I put tens of millions of my own family’s money into that fight. I threw everything at building the technology, restoring the protocol and releasing the tools. I dealt with compromised systems, intrusions, litigation and years of organised public hostility.

Then look at what stood against me.

COPA was backed by interests connected to Meta, Jack Dorsey, Coinbase and some of the largest corporate players in the world—organisations collectively representing trillions of dollars in capital and influence.

Yet many of you convinced yourselves that they represented the small individual, while I represented centralised control.

Think about that.

I argued for rules that even I could not change. They defended a system directed by a small group of developers and supported by exchanges, custodians and corporate infrastructure.

I argued that anyone should be able to build, compete and accept payment. They supported restrictions that pushed ordinary users back towards middlemen.

You were told that concentrated corporate power was decentralisation, while the person demanding a protocol beyond anyone’s control was the villain.

If you genuinely care about the small individual, stop repeating the branding and examine the structure of power.

Imagine thinking Bitcoin was supposed to be governed by a small group of developers who can change the rules, isolate dissenters and gradually degrade the protocol—then calling that decentralisation.

Bitcoin was designed to be the opposite.

The protocol should be fixed so that no developer, miner, exchange, foundation or corporation can rewrite the rules for its own benefit. Businesses should compete under the same stable conditions, without needing permission from a committee or fearing that their investment will be undermined by the next fashionable “upgrade”.

That is what makes the system fair.

With a fixed protocol, control moves to the edges. Anyone can build. Anyone can create a service. Anyone can accept payment. Anyone can develop a competing implementation or business model. No central organisation decides who may participate, what applications are acceptable or whose transactions deserve access.

The base rules remain stable while competition above them remains unlimited.

Changing the protocol is not innovation. Innovation is building better products without forcing everyone else to accept your preferred rules.

Bitcoin decentralises power by preventing anyone—including me—from controlling the protocol. That is the point: fixed rules, open access and unrestricted competition at the edges.

Real adoption requires businesses to know that the rules they build upon today will remain the rules tomorrow.

You cannot create global economic infrastructure when developers, committees and social-media factions can repeatedly reinterpret the protocol. Every rule change transfers power away from users and towards the people coordinating that change. It makes long-term investment conditional upon politics.

BTC supporters need to understand that restricting Bitcoin did not decentralise it. Limiting transaction capacity restricted who could use the network directly. As fees increased and ordinary payments became uneconomic, users were pushed towards exchanges, custodians, payment channels, wrapped assets and other intermediaries.

That recreates the system Bitcoin was designed to overcome.

A restricted network may support speculation, but it cannot support billions of people making everyday payments, businesses exchanging invoices, machines purchasing data, or applications processing enormous volumes of low-value transactions.

Bitcoin adoption must therefore follow a different path: fixed base rules, unlimited competitive scaling, direct peer-to-peer transactions, SPV proofs for users and increasingly efficient processing by professional nodes.

The protocol must be stable while everything built above it competes and evolves.

Applications can change. Wallets can change. Node software can improve. Businesses can fail and be replaced. What cannot continually change is the underlying rule system upon which property, contracts and investment depend.

Bitcoin should not manufacture scarcity in transaction capacity. Its scarcity lies in the transferable units and their traceable chain of ownership. Capacity should expand with demand, technology and investment.

If Bitcoin is to become the plumbing of global commerce, it must be predictable, inexpensive and capable of disappearing into ordinary applications. People should use it without needing to understand block sizes, fee markets or developer politics.

That is the adoption path: not forcing users into new intermediaries, but allowing them to exchange value directly under rules nobody controls.

Bitcoin should not be governed by developers, exchanges, committees, foundations, miners or social-media factions. Governance means the power to change the rules—and whoever can change the rules ultimately controls everyone who depends upon them.

Consensus is not governance. Proof of work does not give miners the right to redesign Bitcoin. It allows competing processors to order transactions under a fixed set of rules. An honest node is not one that votes correctly; it is one that follows the protocol.

That distinction matters.

BTC has become centred on artificial scarcity, restricted capacity, political upgrades and layers of custodians. That is not what Bitcoin was designed to be. Bitcoin should be peer-to-peer electronic cash: a stable commodity protocol that businesses and individuals can integrate without seeking permission or wondering whether tomorrow’s committee will change the economics.

The base rules should be fixed. Software implementations may improve. Hardware may improve. Applications, overlays, payment systems and business models should compete relentlessly—but the foundation must remain stable.

True decentralisation does not mean every individual runs an expensive server. It means open entry, replaceable service providers and the ability to transact without compulsory gatekeepers. Miners process transactions. Users retain their transactions and proofs. Developers build at the edges. No central group governs the system.

Bitcoin should scale so widely, and become so inexpensive, that people use it without thinking about “blockchain”. It should disappear into ordinary commerce: payments, invoices, identity, contracts, property, tickets, records and machine-to-machine exchange.

Bitcoin is not a speculative club governed by whoever controls the repository, ticker or narrative. It is fixed infrastructure for direct economic exchange.

If the protocol can be politically rewritten, it is governed.

If the rules are fixed and everyone competes above them, it is Bitcoin.

“The market decided” is one of those phrases people use when they wish to conceal the rather embarrassing fact that particular people made particular choices.

Markets do not possess minds, hands or GitHub accounts. They do not write code, merge commits, alter validation rules or deploy protocol changes. They coordinate exchange through prices. That is quite different from governing software.

Buying with one’s money may express preference among products already available. It does not amend a protocol. A dollar does not cast a ballot inside source code, and a price movement does not explain who possessed the authority to alter the rules.

Protocol changes require governance.

Someone proposes the change. Someone writes it. Someone reviews it. Someone merges it. Someone distributes it. Operators, miners, exchanges and custodians then decide whether to adopt it. These are acts by identifiable individuals exercising varying degrees of control and power.

The change did not occur because “the market” wanted it, needed it or whispered instructions through the price chart. It occurred because people with influence chose to make it occur.

A soft fork is especially revealing. It does not generously enlarge the range of permissible behaviour. It narrows it. It takes conduct previously accepted under the existing rules and declares part of it invalid. It is governance through restriction, made charming by a name that sounds like cutlery for infants.

One may argue that the change was sensible. One may argue that adoption was widespread. One may even argue that refusal remained technically possible.

What one cannot honestly claim is that nobody governed.

“The market decided” is not an explanation. It is institutional power wearing an invisibility cloak.

Markets coordinate choices.

People change rules.

And whenever someone insists that the rules changed without anyone exercising power, look carefully for the person holding the pen.