Appendix F: The Deployment Window
Stable societies with unchanged boundaries tend to accumulate more collusions and organizations for collective action over time.
The thesis developed in this volume rests on an assumption that deserves explicit examination: that receipted infrastructure can reach sufficient adoption before capture mechanisms adapt to foreclose it. This assumption may be wrong. If it is, the Quiet Foreclosure obtains not because the thesis is incorrect but because the deployment window closed before the infrastructure could establish itself.
The Race Condition
Every technological transition creates a window during which new structures can establish themselves before incumbent power adapts. The printing press operated for decades before effective censorship regimes emerged. The early internet was substantially ungoverned before states and corporations developed effective control mechanisms. Bitcoin processed transactions for years before regulatory frameworks coalesced.
The window exists because adaptation takes time. Incumbents must recognize the threat, coordinate a response, develop legal frameworks, build enforcement capacity, and deploy countermeasures. Each step requires resources, attention, and political will. While the incumbent is adapting, the new structure is establishing facts on the ground: users, infrastructure, network effects, and dependencies that make reversal costly.
The thesis assumes this window exists for receipted systems. The assumption has two components:
First, that capture mechanisms operate slower than deployment. If regulators mandate custodial wallets, identity verification, or licensed intermediaries before non-custodial infrastructure reaches critical mass, the receipted order never forms. The infrastructure becomes permissioned at birth.
Second, that once established, network effects create defensive moats. If users adopt self-custodied credentials, if protocols achieve sufficient liquidity, if verification systems become load-bearing infrastructure, reversal becomes prohibitively costly. The capture mechanisms that arrive after establishment must work around the established structure rather than preventing it.
Both assumptions are contestable.
Historical Precedents
The printing press analogy is instructive but not reassuring. Printing presses operated relatively freely in their first decades because the technology was novel, its implications were unclear, and enforcement was expensive. By the mid-sixteenth century, licensing regimes, censorship boards, and print-shop surveillance had emerged throughout Europe. The window existed, but it closed.
What persisted was not the freedom of the early printing press but a contested equilibrium: some speech was controlled, other speech circulated through underground presses, and the boundaries shifted continuously. The printing press did not produce a stable "printing freedom." It produced a new terrain of struggle, with different chokepoints and different capabilities.
The internet followed a similar arc. The early internet—roughly 1990 to 2005—was substantially ungoverned. Jurisdictional arbitrage was effective; end-to-end encryption was legal; platforms had not yet become gatekeepers. By 2020, the terrain had shifted fundamentally. Platform intermediation captured most traffic. State surveillance operated at scale. Terms of service became de facto law for digital participation. The ungoverned internet did not persist; it was replaced by a governed internet with different properties.
Bitcoin's trajectory remains uncertain but suggestive. The protocol launched in 2009 and operated for years in regulatory ambiguity. By 2024, major jurisdictions had developed comprehensive regulatory frameworks. Mining had concentrated. Exchange custody had become the norm for most holders. The protocol remained fork-resistant, but the ecosystem around it had developed substantial centralization. The core remained permissionless; the periphery became permissioned.
The pattern across these cases: the deployment window exists, but it does not guarantee permanence. What emerges from the window is a contested structure, not an achieved utopia.
Capture Mechanisms Already in Motion
Several capture mechanisms are already operating or under active development:
Custodial mandates. The Financial Action Task Force's "Travel Rule" requires virtual asset service providers to collect and transmit identifying information for transactions above threshold amounts. Implemented progressively since 2019(Force 2019)Financial Action Task Force, "Guidance for a Risk-Based Approach to Virtual Assets and Virtual Asset Service Providers" (2019).View in bibliography, the rule makes non-custodial transactions increasingly friction-laden relative to custodial ones. The endpoint, if the trajectory continues, is a regime where practical participation requires institutional intermediation.
Identity verification requirements. Proposed regulations in multiple jurisdictions would require identity verification for wallet creation, smart contract deployment, or participation in certain protocol governance. The European Union's MiCA framework, finalized in 2023(Council 2023)European Parliament and Council, "Regulation (EU) 2023/1114 on markets in crypto-assets (MiCA" (2023).View in bibliography, moves in this direction. Identity requirements foreclose pseudonymous operation, making the reputational portability that the receipted order enables moot.
Stablecoin capture. The dominant stablecoins—Tether and USDC—are issued by centralized entities that can freeze addresses, comply with sanctions, and respond to regulatory pressure. If stablecoins become the practical medium of agent coordination, the settlement layer is already captured regardless of what the underlying blockchain permits.
Hardware chokepoints. Chip manufacturing is concentrated; mobile device platforms are duopolized; network infrastructure requires physical presence in jurisdictions. Even if protocols remain permissionless, the hardware that runs them is subject to capture. An agent cannot execute on a device that will not run its software.
App store gatekeeping. Apple and Google control software distribution on the dominant mobile platforms. Wallet applications, DeFi interfaces, and credential managers require app store approval. Removal from app stores does not make the underlying protocols unusable, but it substantially increases friction and reduces adoption. The Parler precedent demonstrates that infrastructure providers will coordinate exclusion under political pressure.
On-chain analytics. The most direct and already-deployed capture mechanism is transaction surveillance. Firms like Chainalysis and Elliptic have built comprehensive graph-analysis tools that trace Bitcoin and Ethereum transaction flows with high accuracy, linking pseudonymous addresses to identified entities through exchange deposit patterns, clustering heuristics, and cross-referenced intelligence databases. These tools are deployed by law enforcement in every major jurisdiction and increasingly by compliance departments at exchanges, custodians, and financial institutions. The practical consequence is that Bitcoin's pseudonymity—the property that the framework relies on for agent-to-agent coordination without identity disclosure—is substantially eroded for any entity that touches regulated infrastructure at any point in its transaction history. The erosion compounds: each new exchange compliance requirement, each new mandatory reporting threshold, each new partnership between analytics firms and regulators narrows the set of transactions that remain effectively pseudonymous. On-chain analytics do not prevent non-custodial transactions, but they make such transactions traceable after the fact, which changes the risk calculus for any entity (human or agent) whose threat model includes retrospective investigation.
Each mechanism is partial. None forecloses the receipted order entirely. But the cumulative effect is to narrow the deployment window: each additional friction makes non-custodial, permissionless, pseudonymous participation relatively more costly.
The Rate Question
The deployment window is not a fixed interval but a rate comparison: how fast can receipted infrastructure establish itself relative to how fast capture mechanisms can adapt?
On the deployment side, several factors accelerate adoption: the infrastructure is already substantially built (Bitcoin, Ethereum, and competing protocols exist and function), network effects compound (each additional user increases value for existing users), and institutional interest provides capital and expertise. Stablecoin trading volume approaches $100 billion daily (averaging approximately $90 billion in 2025)(CEX.IO 2025)CEX.IO, "Stablecoin Landscape in 2025" (2025).View in bibliography; DeFi protocols hold over one hundred billion dollars in locked value(DefiLlama 2025)DefiLlama, "DeFi" (2025).View in bibliography; blockchain-based credentials are being piloted by governments and corporations.
On the capture side, several factors accelerate adaptation: the stakes are now visible (regulators understand that control of financial infrastructure is control of economic life), coordination mechanisms exist (FATF, BIS, and national regulators have established frameworks for collective action), and precedents are accumulating (each successful enforcement action provides template for subsequent actions).
The rate comparison is not determinable a priori. It depends on:
- How quickly agent-to-agent coordination reaches volumes that make alternative rails impractical
- How thoroughly KYC requirements penetrate protocol interfaces
- Whether hardware manufacturers face pressure to restrict protocol access
- How effectively jurisdictional arbitrage preserves permissionless options
- Whether the political economy shifts toward or away from surveillance requirements
The honest assessment is uncertainty. The deployment window may be closing faster than deployment is occurring. Or deployment may establish sufficient facts on the ground before the window closes. The outcome is not written.
What a Closed Window Means
If the deployment window closes before receipted infrastructure establishes defensive network effects, the consequences are specific:
Permissioned rails prevail. Agent coordination occurs on custodial platforms, through licensed intermediaries, under identity verification requirements. The efficiency gains from automated coordination still materialize, but they flow through capture points that extract rent and impose conditions.
The receipted order becomes gated. Verification-cost reduction benefits those with access to the permissioned infrastructure—primarily large institutions and compliant individuals in major jurisdictions. Those excluded from the permissioned system—the unbanked, the politically disfavored, the jurisdictionally inconvenient—receive the Quiet Foreclosure regardless of what technology permits.
Capture points proliferate. Each layer of the coordination stack develops its gatekeepers: identity providers, custody services, compliance oracles, licensed interfaces. The stack looks superficially different from traditional finance but exhibits the same structural properties: dependency, discretion, and the capacity for arbitrary interference.
The efficiency thesis holds; the freedom thesis fails. Factor Prime may still emerge as a productive force—the thermodynamic economics do not depend on permissionlessness—but its benefits accrue to whoever controls the capture points. The coordination substrate becomes a tool of the existing order rather than an alternative to it.
This outcome is not the failure of the underlying analysis. It is the failure of a specific assumption about timing. The analysis of verification costs, coordination economics, and settlement requirements would remain valid. What would be falsified is the assumption that these dynamics necessarily lead to a receipted order rather than to more efficient domination.
Implications for Strategy
If the deployment window is uncertain, what follows for those who prefer the receipted order to the captured alternative?
Speed and security exist in tension. Infrastructure that exists and functions, even imperfectly, establishes facts that pure design cannot. The protocol with users defeats the protocol with superior architecture but no adoption. Deployment creates constituencies; design creates papers. But this truth coexists with another: insecure systems deployed quickly can discredit the entire approach when they fail. The DAO hack, the various bridge exploits, the cascading DeFi liquidations—each was an instance where speed prioritized over security created vulnerabilities that critics used to justify restrictive regulation. The strategic implication is not "move fast and break things" but "move as fast as security permits, no faster." The deployment window rewards speed; catastrophic failures close it.
Chokepoint resistance is architectural. Systems should be designed assuming capture attempts will occur at every interface. Minimizing dependencies, maximizing exit options, and distributing critical functions across jurisdictions reduces the surface area available for capture.
Parallel infrastructure must be maintained. Even if custodial interfaces dominate by volume, non-custodial options must remain functional. The existence of alternatives, even if minority-used, preserves the possibility of migration if conditions change. A capture that forecloses all alternatives is permanent; a capture that leaves alternatives possible is reversible.
Political economy cannot be ignored. The deployment window is not purely a function of technology but of politics. Regulatory outcomes depend on lobbying, public opinion, and the distribution of political power. Those who prefer the receipted order must engage with politics, not merely with code. What political strategies follow from this recognition? Coalition-building with constituencies that share interests in limiting surveillance (civil liberties groups, privacy advocates, journalists); engagement with regulatory processes before rules are finalized; public argument about the costs of foreclosing permissionless options. The political economy is not a separate domain from the technical; it is the terrain on which the technical is deployed.
The Third Outcome
The analysis so far has framed outcomes as binary: receipted order or captured infrastructure. But a third possibility deserves consideration, and it may be the most probable: captured infrastructure that is nonetheless more efficient, more transparent, and more accountable than the current system.
Consider: permissioned stablecoins settle faster than traditional wire transfers. KYC-compliant exchanges provide better price discovery than opaque OTC markets. Regulated DeFi protocols, if they emerge, might offer more reliable yield than traditional savings accounts. Captured infrastructure could deliver genuine improvements over the status quo while falling short of the receipted order's aspirations.
The question is whether this outcome is a partial win or a trap.
The honest answer is: it depends on a structural feature that the existing literature has largely ignored. The distinction is not between "captured" and "free" but between intermediated-and-constrained and intermediated-and-arbitrary. Infrastructure routed through intermediaries is not inherently objectionable; what matters is whether those intermediaries are subject to structural checks that prevent them from exercising arbitrary power over the participants who depend on them.
This is where Pettit's non-domination criterion, developed in Volume III, provides the analytical framework that Vol II's structural analysis requires but cannot generate on its own. Non-domination, in Pettit's republican formulation, does not require the absence of interference—it requires the absence of arbitrary interference. A citizen governed by laws is not dominated if the laws are non-arbitrary: if they are produced through contestable procedures, if they apply generally, and if the citizen retains standing to challenge their application. A citizen governed by a discretionary authority that can interfere at will, even if it rarely does, is dominated. The distinction is structural, not behavioral. A benevolent dictator who never interferes is still a dominator, because the capacity for arbitrary interference is present.
Applied to captured infrastructure: a stablecoin issuer that freezes addresses according to published criteria, through contestable procedures, with audit trails and appeal mechanisms, is an intermediary exercising constrained power. A stablecoin issuer that freezes addresses at the discretion of its compliance department, with no published criteria, no appeal, and no audit trail, is an intermediary exercising arbitrary power. Both are "captured" in the sense that they route transactions through an identifiable entity. Only the second constitutes domination.
The distinction matters for evaluating the third outcome because captured-but-improved infrastructure sits on a spectrum. At one end, intermediated rails operate under transparent rules, with credible exit to permissionless alternatives, and with receipted coercion (every enforcement action leaves an auditable trace that can be contested). At the other end, intermediated rails operate under opaque discretion, with no functional alternatives, and with unreceipted coercion (freezing without explanation, exclusion without appeal). The first is consistent with the Protocol Republic as Vol III defines it. The second is the Quiet Foreclosure wearing efficiency's clothing.
Three structural tests distinguish adequate intermediation from domination within the third outcome:
Credible exit. Can a participant leave the intermediated system and continue operating through permissionless alternatives without prohibitive cost? If non-custodial wallets remain functional, if peer-to-peer settlement remains possible, if running a node is legal and practical, then exit is credible and the intermediary's power is checked by the threat of departure. If regulation has criminalized or priced out every permissionless alternative, exit is foreclosed and the intermediary holds arbitrary power regardless of how well it currently behaves. The test is not whether anyone currently exercises exit but whether the option exists and is practically accessible.
Receipted coercion. Does every enforcement action—every frozen account, every denied transaction, every excluded participant—leave a verifiable trace that can be audited and contested? Receipted coercion transforms interference from arbitrary to reviewable. If the stablecoin issuer must publish its freeze decisions, if the exchange must explain its exclusions, if the custody provider must account for its collateral decisions, then the intermediary operates within a constraint that approximates the rule of law even without a court's involvement. If enforcement actions are invisible, unexplained, or unreviewable, the system has reintroduced precisely the arbitrary discretion that the receipted order was designed to eliminate.
Structural contestability. Are the intermediaries themselves subject to competitive pressure, regulatory oversight, or governance mechanisms that prevent the consolidation of arbitrary power? A single dominant custodian with no competitors operates differently from one of five custodians competing for deposits. Plural intermediaries constrain each other through competition; monopoly intermediaries answer only to themselves or to regulators who may share their interests. The question is not merely "are intermediaries present?" but "are intermediaries replaceable?"
If the third outcome satisfies all three tests—credible exit, receipted coercion, structural contestability—it may be adequate for non-domination. Infrastructure that is intermediated but constrained is closer to the Protocol Republic than pure permissionlessness that no one can use, because the Protocol Republic is defined not by the absence of intermediaries but by the presence of structural constraints on their power.
If the third outcome fails any of the three tests, it is a trap: a local optimum that delivers efficiency while foreclosing the path to non-domination. The risk is that the efficiency gains make the trap comfortable. Captured infrastructure that works better than the status quo generates constituencies that resist further reform. The intermediaries that profit from the arrangement fund lobbying to preserve it. The users who benefit from faster settlement, better price discovery, and higher yield have no immediate incentive to demand the structural constraints that would limit their intermediaries' power. The trap is self-reinforcing in the way that all comfortable traps are.
Volume III develops the institutional architecture that would make the third outcome adequate rather than dominating—the constitutional mechanisms, the structured discretion architectures, and the sunset provisions that constrain intermediary power while preserving the efficiency gains that intermediation provides. What this appendix establishes is the question: is intermediated-but-constrained infrastructure adequate for non-domination? The answer requires institutional design that Vol II's structural analysis can identify the need for but cannot supply. The bridge between this volume's economic analysis and Vol III's constitutional architecture is the recognition that the third outcome is not an endpoint but a design problem—one that the non-domination criterion makes precise and the structural tests above make evaluable.
The Honest Uncertainty
This appendix does not resolve the race condition. It names it.
The thesis developed in this volume describes the economic logic of verification-cost collapse and the coordination possibilities that follow. That logic is robust; it does not depend on which political equilibrium obtains. What depends on the race condition is which political equilibrium does obtain: whether the receipted order emerges, or whether the same economic forces are channeled through captured infrastructure.
If the deployment window closes, the analysis remains valid but the outcome differs. The economic forces described in Parts I through V still operate. The allocation of their benefits—who captures the surplus, who faces the costs, who gains freedom and who loses it—depends on who controls the infrastructure through which those forces flow.
The race remains open. The uncertainty is real, and acknowledging it is more honest than claiming inevitability. The outcome depends, in part, on choices being made now — by builders, by regulators, by users, by institutions. The deployment window will close eventually. Whether it closes on terms that preserve the receipted order or foreclose it is the most consequential design question of the next decade.