Craig Wright has renewed his criticism of Bitcoin’s governance model, arguing that its base protocol should remain permanently fixed and beyond the control of developers, miners, exchanges or foundations. The comments revive a governance dispute shaped as much by Wright’s litigation history as by his technical claims.

Any assessment requires an important legal qualification. The UK High Court ruled in 2024 that Wright is not Satoshi Nakamoto and found that he had relied on extensive forged evidence to support that claim. His public arguments may continue, but his asserted authority over Bitcoin has been comprehensively rejected by the court.

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…

— Dr Craig S Wright (@Dr_CSWright) August 2, 2026

Litigation Targeted Bitcoin’s Human Governance Layer

Wright’s earlier legal campaign targeted Bitcoin Core developers, cryptocurrency companies and other individuals involved in the ecosystem. Those claims sought to establish intellectual-property rights, compel changes to software or otherwise use legal proceedings to validate a proprietary interpretation of an open-source network.

The High Court concluded that Wright’s litigation and threats had deterred Bitcoin and cryptocurrency development. Even unsuccessful claims can impose substantial legal costs, consume contributor time and discourage volunteer participation, making litigation pressure capable of weakening development without altering a single consensus rule.

That campaign is now subject to significant legal restraints. A July 2024 injunction barred Wright from bringing or threatening proceedings based on claims that he is Satoshi or owns specified rights in Bitcoin, its software, blockchain or white paper.

Wright later filed another claim seeking more than £900 billion from Bitcoin-related defendants. The court found that action breached its order, held him in contempt and imposed a 12-month prison sentence suspended for two years, showing the litigation strategy now carries direct personal legal consequences.

His current messaging therefore operates mainly through public advocacy and reputational pressure rather than an unrestricted ability to reopen the same ownership claims. That distinction reduces the immediate Wright-specific litigation threat, although the historical burden on developers remains relevant to Bitcoin governance risk.

Legal Pressure Cannot Directly Rewrite Consensus

Bitcoin Improvement Proposals provide a structured process for discussing technical standards and possible upgrades, but publication of a BIP does not itself change the network. Developers can write code and recommend releases, while actual consensus depends on which rules independently operated nodes accept and enforce.

Miners assemble and propose blocks, but full nodes verify those blocks against locally enforced consensus rules. Exchanges, custodians and other economic actors also decide which software and chain history they recognize, creating a distributed adoption process without a single formal protocol administrator.

A court claim or public campaign cannot directly force every independent node to accept new rules. Legal action can nevertheless influence the people and organizations maintaining implementations, hosting repositories, funding research or operating regulated infrastructure, making Bitcoin technically decentralized but still exposed through its human and institutional dependencies.

The principal risk is resource diversion. Time and money spent defending legal claims are unavailable for code review, testing, vulnerability remediation and release engineering, which can weaken the maintenance capacity supporting critical open-source infrastructure.

These firms must decide which releases to deploy, how upgrades are approved internally and how to respond if competing parties challenge software legitimacy, intellectual-property provenance or transaction treatment.

Operational controls should include documented software-selection policies, reproducible builds, version approval procedures, dependency inventories and clear records showing why a particular implementation was adopted. These measures provide an auditable chain of technical and governance decisions if a dispute reaches regulators or courts.

Institutions should also review vendor agreements and legal contingency plans for node, wallet and custody software. Contractual protections, escalation channels and access to independent technical expertise can reduce the risk that external litigation disrupts custody or settlement operations.

The broader lesson extends beyond Wright. Open-source networks can resist unilateral technical control, yet contributors may remain individually vulnerable to legal expenses, reputational attacks and jurisdictional pressure, making collective legal defense an increasingly important component of decentralized infrastructure.

Wright’s renewed comments may stimulate debate over whether Bitcoin should remain fixed or continue evolving through carefully coordinated upgrades. They do not give him control over the protocol, and the court orders materially restrict his previous legal strategy.

Governance risk should be incorporated into software diligence and operational planning, but it should not be confused with direct control of Bitcoin. Legal pressure can alter participation incentives, while consensus ultimately remains dependent on the rules independently enforced across the network.