The Failure of BTC Core’s Changes: A Case Study in Protocol Capture and Manipulation
An Examination of Governance, Economics, and the Subversion of Bitcoin’s Original Design
Keywords
BTC Core, protocol capture, protocol manipulation, digital cash, governance failure, transaction throughput, scalability, miners, protocol ossification, economic incentives, Lightning Network, script removal, transaction malleability, consensus, protocol stability.Subscribe
1. Introduction: Setting the Stage
When Bitcoin was first released, it was not conceived as a speculative vehicle, nor as a symbolic experiment in ideology, but as a practical system of digital cash. Its structure was defined to support everyday use—fast, inexpensive transactions suitable for micropayments as much as larger transfers. The architecture was intentionally extensible, with a scripting system designed to allow conditional payments, escrow arrangements, and a range of contract-like operations. This design was not fragile; it was robust precisely because it was open, permitting growth in both transaction volume and functionality. The scalability model was simple and direct: as hardware, bandwidth, and storage capacity increased, the system would naturally accommodate greater throughput, following the trajectory of technological advancement. Bitcoin’s essence lay in utility—small payments to pay for access, services, or digital goods—an efficient economic engine designed to move beyond the limitations of existing financial rails.
Over time, however, the version now referred to as BTC ceased to embody this vision. Under the stewardship of BTC Core, the group of developers that came to dominate the project’s codebase, a gradual transformation occurred. What was once a scalable micropayment system began to be reframed as something else entirely: a store of value constrained in throughput, artificially limited in block capacity, and stripped of much of its original scripting functionality. These changes were not introduced with open declarations of capture, but rather clothed in the language of safety, neutrality, and “decentralisation.” The rhetoric implied protection of the network, yet the practical outcome was restriction of growth and a fundamental alteration of the economic incentives embedded in the system.
This essay advances the thesis that BTC Core’s modifications amount to a case of protocol capture. Protocol capture describes the process by which actors consolidate influence over the rules of a system while presenting themselves as neutral custodians. The authority claimed is not formalised in law but in code and narrative, yet it functions with similar force, shaping the rules of engagement for all participants. By capturing the protocol, BTC Core imposed its ideological preferences—restricting transaction throughput, eliminating opcodes, and redirecting users towards off-chain systems such as the Lightning Network—while simultaneously claiming fidelity to the original design. The contradiction is not incidental: it is central to the mechanism of capture, where words serve to obscure the reality of manipulation.
The implications of this capture are not merely technical. They are economic, social, and legal. By constraining throughput, BTC Core manufactured artificial scarcity in block space, creating a fee market that runs counter to the original low-cost micropayment model. By removing functional opcodes, the system was diminished in its potential to support programmable contracts, undermining one of the key innovations of Bitcoin’s script. By introducing Segregated Witness and other changes framed as technical necessities, the governance of the system was shifted away from miners—the actors originally incentivised to secure the network—and towards a small clique of developers and ideological supporters. This restructuring echoes phenomena recognised in broader governance studies, particularly regulatory capture in public institutions and monopolistic capture in markets, where concentrated interests bend rules for their own ends under a veil of public interest.
The failure, therefore, is twofold. It is the failure of BTC Core to preserve the integrity of the protocol as designed, and it is the failure of the wider community to resist the capture. By accepting ideological slogans in place of empirical evaluation, by allowing narratives of decentralisation to mask centralisation of control, and by equating restriction with safety, the community facilitated the very manipulation that undermined the system’s original promise.
This essay will explore these themes in depth. It will first trace the mechanisms of capture and consolidation within BTC Core, then examine the specific manipulations of protocol rules and their economic consequences. It will consider the governance failures masked as neutrality and conclude by situating BTC Core’s trajectory within the broader frameworks of law and economics. At its core, the argument is straightforward: BTC Core’s changes do not represent cautious stewardship of Bitcoin’s design, but rather the deliberate capture and distortion of a system that was built to scale, to serve, and to empower global digital cash.
2. The Mechanisms of Capture: How Control Was Consolidated
The consolidation of control by BTC Core cannot be understood as a single decisive event; rather, it was achieved through a series of incremental moves, each framed as a technical safeguard, yet collectively amounting to a radical restructuring of the system. This process resembles the slow entrenchment of monopolistic power, where small restrictions accumulate until a once-open field is rendered inaccessible to all but a privileged group. In the case of Bitcoin, the protocol was designed to scale naturally with technological progress, but under BTC Core, restrictions were deliberately imposed—ostensibly for “safety”—that created artificial scarcity, reshaped incentives, and transferred effective governance from economically invested miners to unelected developers.
Elimination of Original Opcodes
One of the earliest signs of capture was the systematic elimination of original opcodes in Bitcoin’s scripting language. Opcodes such as OP_VERIF and OP_VERIFRETURN were disabled under claims of security concerns, and later others were rendered unusable, narrowing the scope of programmable logic available to participants. This removal was framed as necessary to reduce risk, yet the effect was the deliberate crippling of the system’s versatility. Script had been intended as a lightweight contract language, enabling escrow, payment channels, and complex conditions for transfers. By disabling opcodes, BTC Core imposed a narrowed definition of Bitcoin’s purpose, transforming it from a broad platform for digital cash transactions and contracts into a restricted token transfer system.
This tactic mirrors practices seen in monopolistic capture, where incumbent actors remove features that might expand competition or empower users, under the guise of consumer protection. In antitrust jurisprudence, similar actions have been condemned: cases such as United States v. Microsoft Corp. (253 F.3d 34, D.C. Cir. 2001) recognised how disabling or withholding technical capabilities can serve as exclusionary conduct, undermining competition while masquerading as technical necessity. The parallel is striking—just as Microsoft leveraged its control over the operating system to suppress rival applications, BTC Core leveraged its control over the codebase to suppress Bitcoin’s contractual capacity.
Enforcement of Arbitrary Block-Size Limits
The most visible instrument of capture was the enforcement of an arbitrary block-size cap. Originally, the block-size limit was not a fundamental design element but a temporary safeguard against spam. As computing power and bandwidth increased, the expectation was that this limit would scale to match real-world capacity, ensuring the system could support global use. Instead, BTC Core fixed the block size at 1 MB and resisted every attempt to expand it.
This artificial ceiling created immediate and predictable effects. Transaction throughput was throttled to a fraction of its potential, creating congestion and driving up fees. The system, designed to allow micropayments, was thus transformed into a high-fee environment, directly undermining its original use case. The justification for this was clothed in rhetoric about “decentralisation,” claiming that larger blocks would exclude small participants from running nodes. Yet this argument was both selective and misleading. Nodes were never designed to be passive observers; the system relied on miners to validate blocks, with other nodes serving no critical function in consensus. By equating passive node count with decentralisation, BTC Core reframed the debate, privileging ideology over economics and engineering.
The manipulation here aligns with broader antitrust principles. In Northern Pacific Railway Co. v. United States (356 U.S. 1, 1958), the Supreme Court condemned arrangements that artificially constrained market access for self-serving purposes, even when dressed in neutral language. By restricting block space, BTC Core constrained market access to Bitcoin’s utility, creating scarcity not for technical necessity but for ideological control.
Barriers to Transaction Growth and Narrative Control
Beyond opcodes and block-size limits, BTC Core established barriers to transaction growth by promoting alternative systems that diverted activity away from the base protocol. The most notable was the Lightning Network, positioned as a scaling solution but in reality a separate system with its own set of rules and risks. Rather than enabling Bitcoin to scale directly on-chain as designed, BTC Core enforced a bottleneck and then redirected users toward Lightning as the only path forward. This manoeuvre represents the classic technique of creating a problem and then offering a controlled solution, consolidating authority through engineered dependence.
Alongside these technical restrictions, BTC Core deployed a form of social capture. The group framed itself as the custodian of “safety” and “decentralisation,” wielding these terms as ideological weapons. Those who argued for larger blocks or restoration of functionality were cast as reckless or centralising forces, while BTC Core presented itself as the voice of prudence. The language of neutrality masked the reality of exclusion, and the repeated invocation of slogans created an environment where dissent was marginalised. This dynamic mirrors the way regulatory bodies, once captured, justify their inaction or overreach with appeals to stability and protection, even when such actions entrench monopolistic control.
Consolidation of Authority
What unites these mechanisms is their cumulative effect: the transfer of decision-making power from the network’s economically incentivised participants to a small circle of developers and ideological supporters. Miners, whose role was to secure the system and validate transactions in exchange for rewards, found their authority eroded. Users, who had expected scalable micropayments and programmable contracts, were left with a restricted token and high fees. Meanwhile, BTC Core consolidated its authority not through law or explicit governance structures, but through the subtler forms of narrative dominance, technical control, and ideological framing.
The capture of Bitcoin by BTC Core thus fits within the recognised patterns of monopolistic behaviour. Just as courts have condemned corporations for using their position to impose artificial constraints on markets, so too must we recognise BTC Core’s interventions as manipulations that betrayed the protocol’s design. The elimination of functionality, the enforcement of arbitrary limits, and the creation of barriers to growth were not accidental or neutral acts. They were calculated mechanisms of capture, consolidating control while disguising it beneath the language of safety and decentralisation.
3. The Manipulation of Protocol Rules: Technical Interventions
The consolidation of control by BTC Core did not remain at the level of ideology and rhetoric; it materialised in the manipulation of the protocol itself. Technical interventions were presented as benign corrections or safety measures, yet they functioned as deliberate constraints that reshaped Bitcoin’s trajectory. Script removal, the restrictions on opcodes, and the introduction of Segregated Witness (SegWit) via soft fork were the pivotal tools of this transformation. Far from neutral fixes, these interventions altered the economic incentives, narrowed Bitcoin’s capacity for growth, and diverted its path from a system of scalable digital cash into an artificially constrained ledger.
Script Removal and Restrictions on Opcodes
The original Bitcoin system included a scripting language capable of enabling conditional transactions and programmable logic. It was intentionally designed to be versatile, allowing micropayment channels, escrow mechanisms, and multi-signature contracts. These were not theoretical add-ons but integral features meant to support Bitcoin’s function as a global transaction system with diverse use cases. By removing opcodes such as OP_CAT, OP_SUBSTR, and OP_VERIF, BTC Core narrowed the scope of Bitcoin Script, effectively curtailing its contract functionality.
The justifications for these removals were framed in the language of security—certain opcodes were described as “dangerous” or “untested.” Yet the framing concealed the reality that risk could have been mitigated through careful implementation, rather than wholesale excision. The true effect was the deliberate diminishment of Bitcoin’s potential as a programmable cash system. Script became a skeleton of its intended form, leaving only the narrow capacity to facilitate simple transfers of value. This kind of reductionism functioned to reframe Bitcoin itself: no longer an extensible platform for digital transactions of all kinds, but a static “digital gold” narrative.
Here Wittgenstein’s insights into language and meaning become instructive. In his Philosophical Investigations, Wittgenstein argued that meaning is use, and that distortion arises when words are detached from their proper contexts. BTC Core’s manipulation of terms such as “safety” and “danger” exemplifies this distortion. By repeatedly declaring opcodes “unsafe,” they created a linguistic reality where removal appeared prudent. Yet the practical context—the capacity for scaling and contract formation—was obscured. The distortion of meaning allowed technical mutilation to masquerade as responsible governance.
Segregated Witness: A Soft Fork with Structural Consequences
Segregated Witness (SegWit), introduced as a soft fork in 2017, was presented as a solution to the issue of transaction malleability. Malleability refers to the ability to alter a transaction ID without changing its content, a characteristic that existed in the original protocol but did not constitute a critical flaw. Rather, it was a condition that could be addressed through standardised practices, such as not relying on transaction IDs for contract finality until confirmation. Instead of such procedural measures, BTC Core leveraged malleability as a justification to restructure the protocol.
SegWit separated transaction signatures (witness data) from transaction content, moving them into a separate data structure. While this change was marketed as an elegant fix, its deeper effect was to alter Bitcoin’s transaction format and redefine block capacity. SegWit enabled BTC Core to maintain the nominal 1 MB block limit while introducing a new accounting system, where certain data was counted differently towards block weight. The result was not genuine scaling but an accounting sleight of hand, allowing the narrative of innovation to persist while preserving the artificial constraints on transaction throughput.
The soft-fork nature of SegWit also carried political implications. A soft fork is an asymmetric change—nodes adopting it can continue to interact with older nodes, but dissenters are forced into compliance if miners enforce the fork. By choosing a soft fork rather than a hard fork, BTC Core engineered a scenario where its rules became the default, regardless of consensus among users or miners. This method bypassed the need for explicit agreement, replacing open governance with coercive compatibility. What was framed as consensus was in fact a unilateral imposition disguised as continuity.
The Narrative of Transaction Malleability
The role of transaction malleability in this intervention underscores the depth of narrative manipulation. Malleability was elevated from a manageable characteristic to a supposedly existential flaw, creating urgency for structural changes that conveniently aligned with BTC Core’s agenda. This rhetorical inflation echoes broader instances of definitional distortion in governance, where a manageable issue is amplified into a crisis, thereby legitimising extraordinary interventions.
From a Wittgensteinian perspective, the manipulation lay not in the existence of malleability but in its reframing. The “grammar” of the word was altered: what once meant “an identifiable property of transaction IDs” was reinterpreted as “a critical vulnerability requiring redesign.” The alteration of language restructured the debate itself, placing dissenters at a disadvantage. If one accepts the new definition of malleability, opposition to SegWit appears reckless. By redefining terms, BTC Core controlled not only the protocol but also the conceptual field in which discussion took place.
Economic and Structural Consequences
These technical interventions reshaped Bitcoin’s economic model. By reducing script functionality, BTC Core removed opportunities for transaction complexity and smart contracts, narrowing Bitcoin’s appeal as a programmable system. By maintaining restrictive block capacity under the veneer of SegWit, BTC Core reinforced artificial scarcity, ensuring high fees and congestion. By leveraging malleability as a justification, they created a narrative of necessity that disguised the consolidation of control.
In each case, the manipulation of protocol rules was not incidental but deliberate. The changes did not arise from necessity but from preference, reflecting BTC Core’s ideological commitment to framing Bitcoin as a restricted, high-fee, low-throughput store of value. The distortion of language—safety, danger, malleability, consensus—served as the vehicle by which these preferences were enacted and defended. The system that emerged bore little resemblance to the original design of scalable digital cash. Instead, it was the product of capture, where technical interventions were tools of control, and rhetoric was the weapon that masked their intent.
4. Economic Consequences: Transaction Throughput and Fee Market Engineering
The most visible outcome of BTC Core’s interventions was the economic distortion that arose from artificially restricting transaction throughput. By maintaining the one-megabyte block size limit and resisting any attempts to scale on-chain, BTC Core engineered scarcity not as a product of natural demand but as a function of imposed supply constraints. In doing so, they transformed Bitcoin from a system designed to process vast numbers of inexpensive micropayments into one where transaction space became a premium commodity. The economic model of digital cash was inverted: instead of lowering the marginal cost of payments to near zero, users were confronted with a fee market shaped by contrivance rather than efficiency.
Artificial Scarcity and Manufactured Fee Markets
In economic terms, scarcity is legitimate when it reflects the limits of production or natural constraints. Yet artificial scarcity, created by regulatory or monopolistic fiat, produces inefficiency and consumer harm. By fixing block space at one megabyte despite technological advances in bandwidth, storage, and computing power, BTC Core imposed a ceiling that forced transactions to compete for limited slots. As demand increased, fees rose, but this was not the result of organic scarcity; it was the predictable outcome of restricting capacity far below what was technically possible.
This practice mirrors examples in classical antitrust literature, where monopolies restrict output to inflate prices. In United States v. Aluminum Co. of America (148 F.2d 416, 2d Cir. 1945), Judge Learned Hand condemned the practice of output limitation as anticompetitive, recognising that the deliberate restriction of supply undermines the function of free markets. Likewise, BTC Core’s enforcement of a strict throughput ceiling had no economic justification other than to reshape Bitcoin’s use case, driving it away from everyday payments toward a high-fee environment reserved for larger transfers.
The Failure of Scaling Caps
Scaling caps represented an economic failure in two dimensions. First, they contradicted the principle of technological progression, whereby increased capacity in infrastructure should lower costs and enable greater participation. Second, they violated the original system’s alignment of incentives, in which miners profited by processing larger volumes of transactions rather than by extracting scarcity rents from limited block space.
The high-fee environment that emerged stifled utility. Ordinary users found that small payments, once central to Bitcoin’s design, became uneconomic. Micropayments of a few cents could not be justified when fees exceeded the value of the transaction. This outcome amounted to the systematic dismantling of the very function Bitcoin was meant to serve. Where the system promised inclusion and low-cost transactions, BTC Core engineered exclusion and high-barrier access.
Comparisons to Restricted Industries
Similar dynamics have occurred in industries where capacity restriction was deliberately imposed. In the airline sector, for example, the Civil Aeronautics Board in mid-20th century America restricted routes and fares under the guise of stability, resulting in higher prices and reduced consumer choice. In energy markets, cartels such as OPEC have historically limited production to maintain elevated prices, despite available capacity to increase supply. In both cases, artificial restrictions diminished efficiency and shifted benefits from consumers to controlling actors. BTC Core’s imposition of block caps belongs to this same pattern: restriction for control, not necessity, and harm to the user base in the name of ideological stewardship.
Lightning Network as Substitute, Not Solution
The fee market created by these restrictions was not left without a prescribed remedy. BTC Core promoted the Lightning Network as the “solution” to Bitcoin’s scaling problem. Yet Lightning is not an extension of the base protocol; it is an entirely separate system that relies on pre-funded payment channels and complex routing mechanisms. It introduces counterparty risk, liquidity constraints, and significant barriers to usability, while lacking the simplicity of direct on-chain payments.
Positioning Lightning as a substitute served BTC Core’s objectives. By restricting throughput on-chain, they created the pressure necessary to push users toward Lightning. But this was not genuine scaling—it was a redirection. The original design allowed Bitcoin to expand on-chain with the growth of global infrastructure, enabling millions of transactions per second as hardware advanced. Lightning replaced this path with an alternative that preserved the artificial scarcity of the base chain while offering a tightly controlled, technically fragile substitute. The incentive structure was distorted: what should have been a system of growth and utility became a system of scarcity and diversion.
Consequences for Bitcoin’s Economic Identity
The ultimate consequence of these engineered constraints was the transformation of Bitcoin’s economic identity. What had been a digital cash system was rebranded as “digital gold,” a static asset whose value derived from holding rather than use. The shift was not organic but manufactured by technical restrictions and narrative manipulation. By creating artificial scarcity, BTC Core curtailed Bitcoin’s function, producing an economic structure at odds with both classical theories of efficiency and the system’s original purpose.
The creation of a fee market through block-space restriction did not represent innovation but regression. It turned a system designed for abundance into one of contrived limitation. As in other industries where output restriction has been condemned as anticompetitive, the harm here was borne by users—those who sought affordable, scalable payments but were instead given a constrained, manipulated system that served the interests of its custodians rather than its participants.
5. Governance Failure: Ideology Masquerading as Neutrality
The governance failure of BTC Core is most clearly seen in the dissonance between its rhetoric and its practice. Publicly, the group styled itself as a neutral steward of the protocol, defending ideals of “safety,” “consensus,” and “decentralisation.” In practice, however, these ideals were weaponised as tools of exclusion. Rather than serving the broader community of miners, businesses, and users, BTC Core substituted ideological preferences for technical necessity and enforced those preferences through social mechanisms that bypassed the intended incentives of the system. The result was a form of governance capture: a system ostensibly leaderless and neutral that, in reality, came to be dominated by a small clique of actors whose decisions ossified the protocol and redirected its purpose.
Ossification of the Protocol
Central to BTC Core’s claim of neutrality was the concept of protocol ossification—the idea that the rules of the system should be frozen to guarantee predictability and safety. On the surface, ossification appeared reasonable: a stable protocol allows businesses and users to operate with confidence, knowing the rules will not shift unexpectedly. Yet ossification, as imposed by BTC Core, was not stability but paralysis. It froze the system not at its intended scalable state but at an artificially restricted one. By maintaining the one-megabyte block limit and refusing to restore disabled opcodes, BTC Core locked the system into a narrow form, presenting this as a virtue rather than an abdication of growth.
In economic and legal contexts, stability is valued when it fosters innovation, but ossification imposed at an immature stage is equivalent to freezing a market in its infancy. The analogy is clear: a legal system that froze commercial law in the eighteenth century would be heralded as stable, but it would also be unfit for the complexity of modern commerce. BTC Core’s ossification similarly elevated predictability over functionality, ensuring that Bitcoin could never scale to meet its original purpose.
Blocking Miner-Led Scaling Initiatives
The second mechanism of governance failure was the active obstruction of miner-led initiatives to scale the system. Miners, who bore the economic responsibility for securing the network, had strong incentives to increase throughput and support growth. Larger blocks meant more transactions, higher revenues, and greater utility for users. When miners sought to raise block limits, however, BTC Core consistently resisted, framing such efforts as reckless attacks on decentralisation.
This inversion of roles subverted the system’s intended balance of incentives. In the original design, miners were to act as the economic decision-makers, their investment in hardware and energy giving them both the incentive and authority to grow the network. BTC Core, however, positioned itself as the arbiter of what was acceptable, disempowering miners and replacing economic governance with ideological governance. The conflict over scaling during the so-called “block size wars” epitomised this dynamic: miners and businesses pressed for growth, but their initiatives were dismissed or undermined by a developer clique claiming neutrality.
Reliance on Social Signalling
Alongside protocol ossification and obstruction of scaling, BTC Core relied heavily on social signalling to enforce its decisions. Rather than grounding changes in technical necessity or open economic incentives, decisions were framed in terms of community consensus as interpreted by the developers themselves. Concepts such as “running your own node” were elevated to ideological imperatives, despite passive nodes having no functional role in transaction validation or block creation. The slogan “everyone can verify” was repeated as a hallmark of decentralisation, yet this conflated symbolic participation with actual authority.
By privileging social signalling over economic reality, BTC Core restructured governance into a performative exercise. Users were encouraged to identify with ideological markers—supporting small blocks, rejecting miner influence, championing “neutrality”—while real authority remained concentrated among developers. This mirrored the techniques of regulatory capture, where agencies claim to represent the public interest while in fact privileging specific actors. The governance of Bitcoin became less about functional efficiency and more about adherence to a creed dictated by its custodians.
Broader Lessons in Open-Source Governance
The failure revealed here is not unique to Bitcoin; it reflects a broader vulnerability in open-source projects. Without formal accountability mechanisms, authority accrues to those who control the codebase and the narrative. When such authority is exercised with restraint and transparency, open-source governance can thrive. But when concentrated actors present their ideology as neutrality, the result is capture. BTC Core exemplifies this danger. By cloaking restrictions in the language of safety and consensus, they reshaped the system without open agreement, replacing a structure of incentives with a structure of slogans.
In the end, the governance of BTC Core was not neutral but partisan. Its claim to neutrality functioned as a mask for ideological imposition, and its invocation of consensus concealed the displacement of decision-making from miners and businesses to a developer elite. This inversion marked a profound failure of governance: a system designed to grow through aligned incentives was redirected through concentrated control, its neutrality distorted into dogma, and its potential sacrificed to ideology.
6. Case Study Implications: Lessons for Systems of Law and Economics
The failure of BTC Core cannot be understood in isolation as a matter of technical debate. Its significance lies in how it mirrors and exemplifies broader phenomena of governance failure long recognised in law and economics. The imposition of artificial scarcity, the displacement of economic decision-making, and the entrenchment of ideology under the guise of neutrality place BTC Core’s conduct firmly within the conceptual frameworks of regulatory capture and monopolistic manipulation. By examining these analogies, the case demonstrates that what occurred in Bitcoin is not a technical quirk but a systemic failure, condemned in every other sphere where law and economics intersect.
Protocol Capture and Regulatory Capture
At its core, protocol capture in Bitcoin functions analogously to regulatory capture in public institutions. Regulatory capture occurs when agencies established to serve the public interest become dominated by the very interests they are meant to regulate. In cases such as Federal Communications Commission v. RCA Communications (346 U.S. 86, 1953), courts acknowledged how regulatory bodies may be co-opted by industry players, resulting in outcomes contrary to their original purpose. The parallels to BTC Core are clear: developers presented themselves as neutral custodians of Bitcoin, only to impose ideological restrictions that served their own narrative of small blocks and digital scarcity, directly undermining the system’s intended purpose of scalable digital cash.
Protocol capture in this case reflects the same structural weakness. Without formal checks and balances, those who control the codebase exercise disproportionate influence. Just as captured regulators claim to act for safety or fairness while entrenching specific interests, BTC Core invoked the rhetoric of decentralisation and neutrality to enforce its preferences. The absence of institutional accountability allowed ideological aims to replace economic incentives, producing outcomes identical in structure to the failures of captured regulatory regimes.
Monopolistic Capture and Antitrust Principles
The artificial block-size cap imposed by BTC Core maps directly onto the practices condemned under antitrust law. Courts have consistently held that restricting output to inflate prices constitutes anticompetitive behaviour. In Northern Pacific Railway Co. v. United States (356 U.S. 1, 1958), the Supreme Court denounced arrangements that forced artificial scarcity and distorted consumer choice. Similarly, in United States v. Microsoft Corp. (253 F.3d 34, D.C. Cir. 2001), Microsoft’s suppression of technical features to maintain control was deemed exclusionary conduct.
BTC Core’s restriction of block space, coupled with the removal of functional opcodes, reflects the same logic of monopolistic capture. By curtailing throughput, they engineered congestion and created a manufactured fee market. By disabling Script functions, they excluded potential innovations in digital contracts. These practices limited competition not among firms but within the possibilities of the protocol itself, substituting the open field of scalable micropayments with a tightly constrained environment. Were such behaviour to occur in a regulated industry, it would fall squarely within the ambit of antitrust condemnation.
Contract Law and Fiduciary Duty Analogies
The failure also resonates with principles drawn from contract law and fiduciary duty. In contract law, parties are bound to act in good faith, honouring the spirit as well as the letter of agreements. By capturing the protocol while claiming fidelity to its design, BTC Core acted in bad faith, presenting itself as steward while undermining the contractual expectations of participants who entered the system on the promise of scalable digital cash.
The analogy to fiduciary duty is equally apt. Fiduciaries are required to act in the best interest of their beneficiaries, avoiding conflicts of interest and self-dealing. BTC Core, by contrast, imposed changes that privileged its own ideological vision over the interests of miners, businesses, and users who depended on the system’s original utility. In corporate law, such conduct would be recognised as a breach of duty, voiding legitimacy and inviting remedy.
Lessons for Systems of Governance
The case of BTC Core underscores the fragility of governance in open-source systems when unchecked by external accountability. Just as regulatory agencies require oversight to prevent capture, and markets require antitrust enforcement to prevent monopolistic abuse, protocols require mechanisms to ensure fidelity to their foundational principles. Without such safeguards, control accrues to concentrated actors who can reshape systems under rhetorical cover, producing outcomes contrary to both design and interest.
The broader lesson is that neutrality in governance must be distinguished from the appearance of neutrality. BTC Core cloaked its conduct in the language of safety and consensus, but the substance was ideological imposition. This mirrors failures in government and markets, where slogans obscure capture and harm is inflicted under the guise of public service. Recognition of this dynamic is critical if digital systems are to avoid repeating the same failures that law and economics have long identified elsewhere.
Conclusion
BTC Core’s changes to Bitcoin represent a textbook case of protocol capture and manipulation. By enforcing arbitrary restrictions, disabling functionality, and imposing ideological preferences, they transformed a system designed for global digital cash into a restricted and manipulated financial experiment. The legal and economic analogies are clear: their actions echo regulatory capture in government, monopolistic restriction in markets, and breaches of good faith in contractual and fiduciary relationships. In every analogous domain, such conduct is condemned as failure. That Bitcoin was subject to the same dynamic demonstrates not only the betrayal of its founding principles but also the necessity of recognising protocol capture as a governance hazard of the highest order.