# The Bitcoin Commons - What It Is, What It Isn’t, and Why It Exists Source: https://gilroberts.substack.com/p/the-bitcoin-commons-what-it-is --- ## **TL;DR** _Bitcoin already operates through shared coordination that no one formally governs. Much of this coordination has gone unnamed because consensus remains sovereign and informality has functioned as a kind of protective ambiguity. The term “**commons**” describes that existing reality. **The Bitcoin Commons** is a project built to observe, document, and make sense of those coordination dynamics without claiming authority, enforcement power, or consensus control. Naming a commons is not neutral. It can reduce confusion and make hidden tradeoffs legible, but it can also concentrate soft power, create targets for leverage, and accelerate failure modes that look less like resource depletion and more like coordination erosion. Skepticism toward naming is therefore rational, not reactionary. The unresolved question is whether an unnamed commons can continue to scale as Bitcoin becomes infrastructure, and whether recognition strengthens resilience or quietly undermines it. Answering that requires theory, not instinct._ Subscribe * * * ## **Where Coordination Went** Bitcoin is widely understood as a system designed to minimize trust in institutions. What is less often acknowledged is that Bitcoin did not eliminate the need for human coordination. Software is written by people and nodes are operated by people. Defaults are chosen, documentation is maintained, and legitimacy is inferred long before consensus rules are ever enforced. Coordination did not disappear; it moved. _[The Governance Layer Bitcoin Never Shipped](https://open.substack.com/pub/gilroberts/p/the-governance-layer-bitcoin-never)_ established that this coordination already occurs and that it is tolerated precisely because it cannot override consensus. That condition now has a name, and naming it carries consequences rather than corrections. What has changed is not the existence of coordination, but its scale, visibility, and stakes. As Bitcoin becomes infrastructure rather than experiment, the space where coordination occurs grows more crowded, more consequential, and harder to ignore. Decisions once absorbed quietly by a small technical community now ripple outward into markets, institutions, and layered systems that depend on Bitcoin without controlling it. * * * ## **Bitcoin Already Operates as a “commons”** Bitcoin already exhibits the defining characteristics of a commons, even if the word has rarely been used to describe it. Shared resources exist in the form of open-source codebases, documentation, relay norms, and accumulated social trust around certain practices and contributors. These resources are collectively used and maintained without ownership. No single actor controls access, yet no actor can compel participation. Coordination around these resources is not hypothetical. Developers align around conventions that shape how code is written and reviewed. Node operators converge on defaults that influence network behavior. Economic actors infer legitimacy from social signals long before those signals ever touch consensus or protocol rules. None of this coordination requires formal authority, and none of it can override enforcement. That constraint is not accidental. It is what allows coordination to exist without collapsing into governance. This is a lower-case-c commons. It is descriptive rather than aspirational. It emerges because Bitcoin disperses enforcement while concentrating responsibility at the edges. Informality is not a flaw in the system. It is a structural outcome of a design that enforces rules mechanically while leaving meaning, interpretation, and coordination to humans. The commons persists because it is constrained. Consensus provides a hard boundary that coordination cannot cross. Software can be ignored, defaults can be rejected, and Legitimacy is always provisional. These limits prevent capture, but they do not eliminate influence as it merely shift it into informal channels. Understanding Bitcoin as a commons does not require approving of those channels or celebrating them. It requires recognizing that they exist, that they matter, and that they already shape outcomes at scale. * * * ## **The Benefits and Pathologies of an Unnamed “commons”** The Bitcoin’s unnamed commons has delivered real advantages. It has allowed Bitcoin to adapt without centralized planning, to absorb shocks without institutional rescue, and to accommodate disagreement without permanent fracture. Informality preserved optionality and silence functioned as restraint. Ambiguity reduced the cost of disagreement. At the same time, the costs of informality are visible. Coordination is uneven with influence being opaque. Legitimacy is often contested only after decisions propagate. Disputes recur not because Bitcoin lacks rules, but because rules, themselves, do not resolve questions of meaning, priority, or responsibility. These tensions surface repeatedly in debates over development priorities, relay policies, and defaults. Participants argue past one another not because they disagree on consensus, but because they operate from different assumptions about coordination that remain implicit. Disputes are personalized, politicized, or framed as technical failures (even if they are not) when a shared coordination language is not present. The unnamed commons works precisely because it avoids formalization. That same avoidance makes it difficult to reason about its failure modes. Informality reduces the risk of capture, but it also obscures accountability. Ambiguity protects optionality, but it also makes power harder to see. These outcomes are not evidence of systemic failure. They are the predictable consequences of a commons operating without explicit recognition. The question is not whether these dynamics should exist. They already do. The question is what changes once they are acknowledged rather than assumed. * * * ## **Recognition Is Not Neutral** Naming a commons reshapes perception. Language alters how participants interpret their own behavior and the behavior of others. Expectations harden, boundaries become legible, and silence acquires meaning. What was previously ambient or accidental becomes intentional, even when no formal intent exists. Recognition introduces risk as what was implicit becomes discussable. What was tolerated quietly becomes visible. Participants may coordinate differently once they believe they are part of something named, adjusting behavior in anticipation of scrutiny or influence. External observers may begin to infer authority where none exists, mistaking shared language for shared control. This shift can clarify reality, but it can also destabilize equilibria that depended on ambiguity. Informal restraint may weaken once actions are framed as participation. Disagreement may intensify once coordination is rendered legible. Influence may consolidate once it can be measured. Recognition is therefore not an upgrade but an exposure. It changes the terrain without guaranteeing improvement and redistributes incentives without designing outcomes. Treating naming as neutral obscures these effects and invites unintended consequences. Any serious engagement with the commons must begin by acknowledging that recognition itself alters incentives. Whether that alteration is beneficial or harmful depends on dynamics that cannot be resolved through description alone. * * * ## **How “commons” Is a Dangerous Frame** The term _commons_ provides a way to describe shared resources and coordination without defaulting to ownership or hierarchy. It offers language for collective use without implying centralized control. It helps explain why Bitcoin’s social layer behaves as it does without invoking conspiracy or moral failure. At the same time, the familiarity of the term can lull readers into assuming that what works for other commons will translate cleanly into Bitcoin’s context. Bitcoin is a boundary case that strains classical commons theory. Much of that theory, including the work of Elinor Ostrom, assumes defined boundaries, enforceable rules, and mechanisms for resolving disputes. Bitcoin’s commons is constrained externally by consensus and intentionally incomplete internally. Enforcement is absent by design, and exclusion is not meaningfully available. These absences are not implementation gaps; they are structural properties. The coordination challenges Bitcoin faces also echo the knowledge problem articulated by Friedrich Hayek. Information in Bitcoin is dispersed, local, and often tacit. No central actor can aggregate it without distortion, and no coordinating body can act without discarding critical context. Informal coordination emerges because centralized knowledge is neither available nor desirable, not because it is inefficient or unfinished. These frameworks are useful lenses, not sources of authority. Bitcoin does not confirm them neatly, nor does it falsify them outright. It complicates both by operating at a scale and under constraints they were never designed to address. Importing expectations wholesale risks misunderstanding what makes Bitcoin resilient in the first place, especially when those expectations assume enforceability or stewardship. What makes the commons frame especially dangerous, however, is the risk of sliding toward a familiar failure mode: a tragedy of the commons. In traditional settings, this refers to the overuse or degradation of shared resources when individual incentives diverge from collective outcomes. In Bitcoin, the tragedy would not take the form of resource depletion but instead appear as coordination erosion, in which legitimacy, trust, and shared norms are overdrawn by actors pursuing narrow advantage under the cover of informality. Unlike physical commons, Bitcoin’s shared resources are reputational, interpretive, and social. They degrade not when consumed, but when stretched beyond their capacity to coordinate behavior without enforcement. If every actor treats informal legitimacy as costless to exploit, the commons risks becoming noisy, brittle, or polarized rather than depleted. This failure mode is subtle, cumulative, and difficult to reverse. The danger, then, lies not in using the word _commons_, but in underestimating the fragility it describes. Recognition does not guarantee stewardship, and shared language does not prevent free-riding or capture. The value of the frame is explanatory. The risk is prescriptive drift, complacency, or the assumption that shared resources will regulate themselves indefinitely simply because they have so far. * * * ## **The Bitcoin Commons, as a Named Project** Up to this point, the discussion has focused on Bitcoin commons as a descriptive condition. A shared coordination space that already exists, operates informally, and is constrained by consensus. The Bitcoin Commons, capital-C, emerges from that reality rather than preceding it. It is not an attempt to create coordination where none existed, but to make existing coordination easier to understand, discuss, and examine without converting it into authority. At its core, [The Bitcoin Commons](https://www.TheBitcoinCommons.org) is a sense-making and coordination-adjacent project. It does not intervene in consensus and it does not attempt to resolve disputes. Instead, it operates at the level of shared understanding. Its role is to surface patterns that already shape Bitcoin’s development and operation, to give participants a clearer view of how coordination actually happens, and to provide language that reduces the need to rediscover the same institutional dynamics repeatedly under different names. This distinction matters. Many efforts around Bitcoin coordination fail because they begin with a solution in search of a problem. The Bitcoin Commons begins with the opposite posture. It assumes that coordination is already happening, that it already influences outcomes, and that pretending otherwise does not eliminate power so much as obscure it. The project’s contribution is therefore epistemic rather than procedural. It seeks to improve how coordination is understood, not how it is enforced. Practically, this means The Bitcoin Commons operates as a documentation, analysis, and dialogue layer that sits adjacent to node software, development workflows, and economic decision-making. It does not replace existing forums, repositories, or institutions. It provides connective tissue across them. Where coordination questions arise repeatedly—around defaults, legitimacy, responsibility, or scope—the Commons offers a place to observe those questions as a class rather than as isolated incidents. The project is intentionally lightweight. There are no membership requirements, no formal roles, and no mechanisms for decision-making. Participation is informal and optional. Engagement can range from passive observation to active contribution, and withdrawal carries no penalty. This informality is not an oversight. It is a constraint designed to prevent the Commons from becoming a gatekeeper or authority. The Bitcoin Commons also functions as a boundary object between different constituencies in the ecosystem. Developers, node operators, miners, enterprises, and institutional actors often experience the same coordination pressures but describe them differently. The Commons does not attempt to harmonize those perspectives into a single narrative. It makes their differences legible without forcing resolution. At a higher level, the project serves as a pre-theoretical staging ground. Before disputes can be analyzed through the lenses of economics, political theory, or governance research, they must first be described accurately. Much of the friction in Bitcoin debates comes not from disagreement over goals, but from disagreement over what is actually happening. The Bitcoin Commons exists to slow that process down, to separate observation from prescription, and to create space where questions can be examined before solutions are proposed. Importantly, [The Bitcoin Commons](https://www.TheBitcoinCommons.org) does not necessarily promise improvement. Better understanding can still lead to worse outcomes. Making coordination legible can concentrate influence as easily as it can diffuse confusion. The project’s wager is not that recognition is safe, but that repeated misrecognition carries its own costs as Bitcoin scales. For participants already operating close to the protocol (i.e. maintainers, reviewers, and node operators) The Bitcoin Commons offers a mirror rather than a map. It reflects patterns they already experience but rarely have time to articulate. For enterprises and institutions building on Bitcoin, it provides a clearer picture of why coordination feels fragile even when consensus is stable. For observers and researchers, it offers a living case study of coordination without enforcement. This is why The Bitcoin Commons is best understood not as a platform or institution, but as infrastructure for thought. It does not resolve coordination questions. It makes them harder to ignore and easier to study. Thanks for reading After the Institutions! This post is public so feel free to share it. [Share](https://gilroberts.substack.com/p/the-bitcoin-commons-what-it-is?utm_source=substack&utm_medium=email&utm_content=share&action=share) * * * ## **Legibility, Soft Power, and Institutional Risk** Making coordination legible changes who can act on it. Even when no authority is granted, visibility redistributes influence. Those who articulate shared language gain interpretive power. Those who define categories shape what is considered normal, deviant, or out of scope. In informal systems, power often operates through obscurity. Influence remains deniable. Silence functions as restraint. Once coordination becomes legible, those dynamics shift. Informal leaders become identifiable. Norms harden into expectations. What was once optional begins to feel obligatory, even in the absence of enforcement. The Bitcoin Commons does not eliminate these risks as it foregrounds them. By acknowledging that naming a commons can amplify soft power, the project places constraints on its own role. It avoids claims of representation. It refuses enforcement and resists proceduralization. Still, risk remains. As Bitcoin becomes infrastructure for layered systems and institutions, the demand for clarity increases. Enterprises want predictability. Regulators seek points of contact. Investors look for signals of stability. In this environment, legibility can be mistaken for authority even when none is claimed. This tension cannot be resolved through disclaimers. It must be managed through restraint and transparency about limits. The Bitcoin Commons therefore treats legibility as a tradeoff rather than a virtue. The question is not whether coordination should be visible, but how much visibility a system designed for decentralization can tolerate without undermining itself. * * * ## **Scale and the End of Costless Ambiguity** Bitcoin’s early years benefited from a narrow participant base and relatively low stakes. Coordination failures were local. Defaults could be changed without widespread impact. Informality was not just tolerable; it was protective. That context has changed. Bitcoin now underlies payment networks, corporate treasuries, custodial platforms, and financial products that extend far beyond its original community. Decisions made informally can propagate through layers of dependency, affecting actors who had no role in the original coordination. As scale increases, ambiguity acquires a cost. Silence is interpreted. Defaults ossify. Informal norms become infrastructural. What once felt like healthy decentralization can begin to feel like fragility. This does not imply that formal governance is the answer. It implies that pretending coordination does not exist is no longer free. The unnamed commons was viable under conditions of limited scale. Whether it remains viable as Bitcoin becomes global infrastructure is an open question. The Bitcoin Commons enters the picture not as a solution to scale, but as a response to this shift in conditions. It acknowledges that coordination pressures intensify as systems grow, and that understanding those pressures may be a prerequisite for navigating them without overcorrecting. * * * ## **When Coordination Has No Referee** Disagreements such as those surrounding Bitcoin Core and Bitcoin Knots illustrate how coordination operates without formal resolution. No authority adjudicates legitimacy. No vote settles the matter. Operators must decide which defaults to run, and those decisions aggregate into outcomes that feel collective even though they were never coordinated centrally. These situations are not governance failures. They are expressions of a commons under constraint. Influence emerges through reputation, persistence, and narrative rather than mandate. Responsibility is distributed unevenly, and accountability is diffuse. For some participants, these tensions invite closer examination of coordination itself. For others, they reinforce the value of restraint and minimal intervention. Both responses coexist within the commons. Neither can eliminate the other. The value of recognizing these tensions lies not in resolving them, but in understanding their structure. Once coordination is seen as a persistent feature rather than an anomaly, debates can be reframed away from crisis narratives and toward institutional realism. * * * ## **The Case for Skepticism** Skepticism toward naming and institutional language is deeply rooted in Bitcoin’s history. Many of the system’s most successful defenses against capture relied on refusing to formalize authority or clarify power structures prematurely. Ambiguity functioned as armor, allowing participants to coordinate loosely without creating targets for leverage or consolidation. Those instincts remain valid. Naming creates focal points. Focal points attract leverage. Leverage invites capture. History offers no shortage of examples where well-intentioned coordination structures hardened into brittle institutions once they became legible, enumerable, or representative. In many cases, the act of naming preceded the act of control, even when no control was initially intended. The Bitcoin Commons does not seek to neutralize this skepticism. It incorporates it as a constraint rather than an obstacle. Refusal remains a legitimate response. Non-participation carries no penalty. Silence remains meaningful, and disengagement is not treated as ignorance or bad faith. The unresolved tension is whether skepticism alone can scale. Avoidance worked when coordination costs were low, stakes were limited, and participants were relatively homogeneous. As Bitcoin becomes infrastructural and coordination pressures propagate across layers and institutions, it is no longer clear that refusal by itself is sufficient to preserve resilience. Whether skepticism can remain purely defensive without becoming brittle is an open question. * * * ## **The Unresolved Questions** Can an unnamed commons continue to scale as Bitcoin becomes embedded in global economic systems? And if naming that commons changes behavior, does it improve coordination or undermine the very properties that made Bitcoin resilient? No answers are offered here. The question itself reshapes the terrain by making implicit tradeoffs explicit. Recognition alters incentives, redistributes attention, and reframes responsibility even in the absence of authority. Whether those altered incentives are survivable, stabilizing, or corrosive cannot be assumed. They must be examined. * * * ## **What Recognition Forces Us to Ask** Bitcoin already operates through shared coordination that no one formally governs. The “commons” describes that reality, while The Bitcoin Commons names a project built to observe and understand it without claiming authority. Making this distinction exposes real risks, including legibility, informal power, and capture, while preserving the legitimacy of skepticism. Many participants are already part of these dynamics, whether they acknowledge them or not. Recognition, however, does not resolve tension; it concentrates it. Once a commons is named, questions that could previously be avoided become unavoidable. What counts as coordination rather than coincidence? Where does responsibility attach when outcomes are collective but decisions are individual? How much legibility can a system tolerate before informality collapses into soft governance or quiet capture? Answering those questions requires more than observation or instinct. It requires theory, historical comparison, and an honest examination of institutional failure modes. That deeper work happens in the next article. After the Institutions is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber. Subscribe * * * ## **Citations, Further Reading, & Glossary** ### **Cites** **Hayek, F. A. (1945).** _The use of knowledge in society._American Economic Review, 35(4), 519–530. _Relevance to Article:_ Hayek’s articulation of dispersed, tacit knowledge underpins the article’s claim that Bitcoin coordination emerges informally because centralized aggregation of information is neither possible nor desirable. **Ostrom, E. (1990).** _Governing the commons: The evolution of institutions for collective action._ Cambridge University Press. _Relevance to Article:_ Ostrom’s framework provides the foundational vocabulary for commons analysis, while also highlighting why Bitcoin’s commons is a boundary case that lacks enforcement, defined membership, and formal governance mechanisms. **Nakamoto, S. (2008).** _Bitcoin: A peer-to-peer electronic cash system._ _Relevance to Article:_ The Bitcoin white paper establishes consensus enforcement and trust minimization as design goals, forming the backdrop against which informal coordination and the bitcoin commons emerge. **De Filippi, P., & Loveluck, B. (2016).** _The invisible politics of Bitcoin: Governance crisis of a decentralised infrastructure._Internet Policy Review, 5(4). _Relevance to Article:_ This work documents how governance and coordination inevitably arise in decentralized systems, supporting the article’s claim that Bitcoin already operates through informal but consequential coordination. **Antonopoulos, A. M. (2017).** _Mastering Bitcoin_ (2nd ed.). O’Reilly Media. _Relevance to Article:_ Antonopoulos’s technical exposition of Bitcoin clarifies the boundary between protocol-enforced consensus and human-driven coordination layers referenced throughout the article. **Roberts, G. (2025).** _After the Institutions: Various Articles._ Substack series. _Relevance to Article:_ These prior articles establish the empirical groundwork for this article, documenting Bitcoin’s layered structure, node software dynamics, and existing coordination practices that culminate in the recognition of a commons. **Swift, J. (Unpublished).** _Decoded: Institutional emergence in Bitcoin._ Manuscript. _Relevance to Article:_ Swift’s unpublished work informs the interpretive framing of Bitcoin as an emergent institutional system and provides creator perspective on the motivation for naming and studying The Bitcoin Commons. ### **Further Reading** **Lessig, L. (2006).** _Code: Version 2.0._ Basic Books. _Relevance to Article:_ Lessig’s analysis of how technical architecture regulates behavior without formal law helps frame Bitcoin’s informal coordination layer as a form of governance-by-constraint rather than authority-by-design. **Scott, J. C. (1998).** _Seeing like a state: How certain schemes to improve the human condition have failed._ Yale University Press. _Relevance to Article:_ Scott’s critique of legibility and central planning informs the article’s warning that naming and making coordination visible can introduce new risks, even when done with descriptive rather than prescriptive intent. ## **Glossary (Search & AI Optimized)** **Bitcoin Commons (lowercase “commons”)** The informal, shared coordination space in which Bitcoin development, node operation, defaults, and legitimacy judgments occur without formal authority or enforcement. **The Bitcoin Commons (capital-C project)** A descriptive, coordination-adjacent initiative that documents, analyzes, and contextualizes existing Bitcoin coordination dynamics without claiming governance authority, consensus control, or enforcement power. **Consensus** The protocol-enforced rules of Bitcoin that determine transaction validity and block acceptance, providing hard, mechanical enforcement independent of human discretion. **Coordination (in Bitcoin)** Human-driven alignment around practices, defaults, norms, and interpretations that occurs outside consensus but influences how Bitcoin is built, operated, and understood. **Governance (informal)** Non-binding processes through which influence, legitimacy, and direction emerge in Bitcoin without voting, representation, or formal institutional authority. **Governance-as-infrastructure** The idea that coordination mechanisms, norms, and defaults function as infrastructural constraints rather than explicit decision-making systems. **Legibility** The degree to which coordination dynamics, influence, and norms are visible, nameable, and interpretable by participants and external observers. **Soft Power** Influence exercised through reputation, narrative framing, defaults, and shared language rather than coercion or enforcement. **Defaults** Pre-selected behaviors or configurations in software and systems that shape outcomes unless actively changed by users or operators. **Node Operator** An individual or entity running Bitcoin node software that independently validates transactions and blocks according to consensus rules. **Node Software Diversity** The existence of multiple Bitcoin node implementations and configurations, contributing to decentralization while increasing coordination complexity. **Boundary Object** A concept or artifact that enables communication across different groups without requiring full agreement or uniform interpretation. **Informality** The absence of formal rules, roles, or enforcement mechanisms in coordination, often preserving flexibility but obscuring accountability. **Recognition (of a commons)** The act of naming and explicitly acknowledging an existing coordination space, which alters incentives and behavior even without authority. **Prescriptive Drift** The tendency for descriptive frameworks to evolve unintentionally into normative or governing structures over time. **Tragedy of the Commons (Bitcoin context)** A potential failure mode in which shared legitimacy, trust, and coordination norms are eroded through overuse or exploitation, rather than physical resource depletion. **Coordination Erosion** The gradual weakening of shared norms, trust, and legitimacy that undermines effective informal coordination. **Capture** The process by which informal influence or coordination structures become dominated by narrow interests. **Scale (Bitcoin)** The expansion of Bitcoin’s use across layers, institutions, and global systems, increasing the stakes and impact of coordination decisions. **Institutional Infrastructure** Systems that underpin economic and organizational activity at scale, including payment networks, custody, and settlement layers. **Knowledge Problem** The challenge, articulated by Friedrich Hayek, that information relevant to coordination is dispersed, local, and often tacit, resisting central aggregation. **Commons Recognition Risk** The possibility that naming and making coordination visible introduces new vulnerabilities, including leverage, capture, and misinterpretation.