The Graveyard of Gateways: Why There Can Only Be One Blockchain
Or: How the market already answered this question thirty years ago, and nobody in crypto bothered to check.
There is a particular species of optimism that flourishes in the absence of historical memory. It announces itself as innovation. It presents fragmentation as freedom and duplication as diversity. It mistakes the multiplication of toll booths for the opening of roads.
The multi-chain thesis in blockchain is this species of optimism. It holds that many competing ledgers, each running its own protocol, its own token, its own consensus mechanism, and its own fee schedule, constitute a healthy ecosystem rather than an expensive problem. It imagines a world of interoperable sovereign chains, each serving its niche, all connected by bridges and relayers and wrapped assets and cross-chain messaging protocols, and it calls this architecture progress.
It is not progress. It is the 1980s.
I. The Protocol Wars You Have Already Forgotten
Between roughly 1978 and 1994, the networking industry conducted a large-scale, well-funded, multi-government experiment in protocol pluralism. The question was simple: how should computers talk to each other? The answers were numerous. TCP/IP, developed from the ARPANET project by Cerf and Kahn, was one option. The International Organization for Standardization’s Open Systems Interconnection (OSI) reference model was another—and for over a decade, it was the official answer. IBM had Systems Network Architecture (SNA), embedded in every mainframe estate on Earth. Digital Equipment Corporation ran DECnet. Novell dominated local area networks with IPX/SPX. Banyan had VINES. Xerox had XNS.
These were not trivial systems. Some were technically excellent. Some were deeply embedded in vendor ecosystems with enormous installed bases. OSI had the backing of the European Economic Community, multiple national governments, the U.S. Department of Commerce, and—remarkably—the U.S. Department of Defense itself, which in 1985 accepted a National Research Council recommendation to transition away from TCP/IP toward OSI (Maathuis & Smit, 2003). That the Pentagon once considered abandoning its own protocol suite in favour of an international committee standard should tell you something about how seriously the alternatives were taken.
And yet, by 1994, the contest was over. TCP/IP had become the dominant standard for internetworking. Maathuis and Smit (2003) investigated whether this outcome was the product of path dependency or technical-economic superiority, and concluded that quality assessments at the time of adoption generally favoured TCP/IP—this was not a case of an inferior standard winning by accident. OSI survived principally as a pedagogical model. The other stacks either died, were encapsulated inside IP packets for transport across IP infrastructure, or persisted as legacy systems that organisations were too frightened to turn off.
The pattern is clean enough to state as a proposition: in general-purpose networking, the market experimented with many protocols and converged on one dominant standard, burying the rest behind gateways.
Consider what happened to the losers. Novell’s IPX/SPX, once the default protocol of every NetWare LAN, did not maintain a parallel internetwork. It was tunnelled inside UDP/IP packets so that IPX traffic could traverse TCP/IP infrastructure (Novell, n.d.). That is the architectural signature of a defeated protocol: survival through encapsulation over the winning network. DECnet, proprietary and capable within DEC environments, lost ground as open internetworking expanded (Computer History Museum, n.d.). IBM kept SNA alive for legacy mainframe estates, but IBM’s own documentation discusses the practical necessity of using IP to connect SNA systems (IBM, n.d.). The proprietary architecture remained, but the connective tissue standardised around IP.
This is not an analogy. It is a template.
II. Plurality Produced Gateways, Not Harmony
The important thing about the multi-protocol era is not that it was untidy. The important thing is what it cost.
To connect unlike systems, enterprises deployed routers, protocol translators, encapsulation layers, tunnels, gateways, proxy services, and specialist administrators. Each protocol boundary required conversion infrastructure. Each conversion introduced latency, complexity, failure modes, and administrative overhead. The IBM technical overview of TCP/IP describes the suite as having become the industry-standard method of interconnecting hosts, networks, and the Internet (IBM, n.d.)—which is a polite way of saying that the alternative was ruinously expensive fragmentation.
The economics here are not subtle. Katz and Shapiro (1985), in their foundational treatment of network externalities, demonstrated formally that in markets where compatibility increases value, the utility a consumer derives from a good rises with the number of other agents consuming compatible goods. When a critical mass of users adopts one standard, the adoption externality becomes self-reinforcing. The installed base attracts complementary investment, which further increases value, which attracts more users. Farrell and Saloner (1985), working on standardisation dynamics, showed that under complete information, industries do not remain trapped in inferior standards—but under incomplete information, excess inertia can delay convergence. Arthur (1989) generalised the point: under increasing returns to adoption, the economy can become locked in to a technological path, and once that lock-in occurs, it is not easily reversed by conventional policy instruments.
The practical implication is that protocol fragmentation is not a stable equilibrium in general-purpose connectivity markets. It is a transitional state. The question is never whether convergence will occur, but when and on what.
Economides (1996), in his comprehensive treatment of network economics, made the structural point explicit: compatibility is what converts potential complementarity into actual value. Without it, network components that could combine to produce demanded services instead sit in isolated pools. The cost of incompatibility is not merely inconvenience; it is the systematic destruction of value that would exist under a unified standard.
Shapiro and Varian (1999) translated these results into strategic language: in network markets with positive feedback, the dynamics are “tippy.” Markets do not settle into comfortable pluralism. They tip toward one dominant platform, and they do so with increasing velocity once the tipping begins. The managerial question is not whether to pursue compatibility but how to become the standard around which the market tips.
None of this is obscure. It is canonical industrial organisation. And all of it applies, with no modification whatsoever, to the blockchain case.
III. What Bitcoin Was Supposed to Eliminate
The design objective of Bitcoin is stated in the opening lines of the white paper: “a purely peer-to-peer version of electronic cash would allow online payments to be sent directly from one party to another without going through a financial institution” (Nakamoto, 2008). The system was designed to reduce reliance on trusted third parties in electronic commerce. That is the baseline. That is the purpose.
Now consider what a world of multiple incompatible blockchains requires. If economic activity is split across chains that cannot natively settle with each other, then any user wanting to transact, exchange, or verify value across those boundaries needs intermediation. The intermediary might be a centralised exchange. It might be a bridge. It might be a wrapped-asset issuer, a market maker, a custodian, a federation, or an interoperability protocol with its own trust assumptions, its own governance, and its own failure modes.
That is not the removal of trusted third parties. It is their multiplication.
The multi-chain architecture does not eliminate the institutional layer that a direct cash system was designed to minimise. It rebuilds that layer under new branding. The exchange becomes the bank. The bridge becomes the clearinghouse. The wrapped token becomes the promissory note. The relayer becomes the correspondent. Every boundary between chains is a seam where someone can extract a fee, introduce a delay, impose a condition, or fail catastrophically.
This is not a theoretical concern. It is an empirical fact with a dollar figure attached to it.
IV. The Bridge Graveyard
Cross-chain bridges have been the most aggressively promoted solution to blockchain fragmentation. They are also, measured by financial losses, the single most catastrophic failure point in the entire decentralised finance ecosystem.
Zhang et al. (2024), in a systematic study published in the proceedings of the 27th International Symposium on Research in Attacks, Intrusions and Defenses (RAID), catalogued 35 real-world cross-chain bridge attacks between April 2021 and April 2024, classified into ten distinct vulnerability types across four fundamental categories: permission issues, logic issues, event issues, and front-end issues. Rashid et al. (2025), in a multivocal literature review covering 64 different bridges, documented 31 exploits and four known bugs over the 2021–2023 period, noting that bridges frequently provide security guarantees inferior to those of the underlying chains and have suffered losses in the range of 1.5 to 2 billion USD in 2022 alone.
Belchior et al. (2021), in an ACM Computing Surveys treatment of blockchain interoperability, established the taxonomic framework: cross-chain mechanisms include notary schemes, relay chains, hash time-locked contracts, and sidechain constructions, each carrying distinct trust assumptions and failure modes. The survey made clear that no existing interoperability mechanism achieves the security properties of native single-chain execution.
The total figure, as reported by Chainalysis and DefiLlama, exceeds $2.8 billion stolen from bridges—representing approximately 40% of all value hacked in Web3. The Ronin Bridge alone lost nearly $600 million in March 2022 through compromised validator keys. The Wormhole Bridge lost $325 million through a verification exploit. The BNB Bridge lost $570 million through forged cross-chain messages. The Nomad Bridge lost $190 million through an implementation error so severe that unsophisticated attackers could drain it by simply copying and modifying existing transaction data.
These are not edge cases. They are structural outcomes. Every cross-chain bridge is a complex system that must correctly validate state across heterogeneous environments, manage cryptographic keys, maintain consensus about external chain states, and resist adversaries who can probe each of these surfaces independently. The attack surface is not additive; it is combinatorial. And the incentive to attack is proportional to the value locked, which in bridge architectures is concentrated by design.
The bridge, in short, is the 2020s equivalent of the protocol gateway: an expensive, fragile, rent-extracting intermediary that exists only because the underlying systems refuse to speak the same language.
V. The Economic Logic of Convergence
The case for one dominant chain does not rest on maximalism or brand loyalty. It rests on five standard economic propositions, none of which requires any special pleading.
First: network effects. A single large ledger has advantages that ten small ledgers cannot replicate. Deeper liquidity means tighter spreads. A denser counterparty set means lower discovery costs. Broader tool support means lower development costs. Simpler accounting means lower compliance costs. Fewer reconciliation points means fewer error modes. These are standard network-economics implications (Katz & Shapiro, 1985, 1994; Economides, 1996), not speculative claims about future adoption.
Second: economies of scale in infrastructure. If a single chain can absorb large throughput, fixed infrastructure costs—validation, indexing, wallets, monitoring, exchange integration, compliance systems, developer tooling—are spread over more transactions. Competing chains duplicate every one of these costs. Unless a second chain provides some compensating functional advantage that the first cannot absorb, the duplication is pure overhead. This is exactly the logic that drove firms to converge on IP rather than maintaining every protocol family in perpetuity.
Third: fragmentation imposes transaction costs. Two chains mean pricing spreads between them, hedging costs, custody decisions, settlement timing mismatches, bridge risk, and reconciliation burdens. One chain eliminates cross-chain conversion for any activity native to that chain. The comparison is not abstract pluralism versus monopoly. It is native execution versus conversion overhead.
Fourth: where functionality is equal, price determines allocation. This is the knife-edge. If Chain A can do everything Chain B can do, and Chain A is cheaper per transaction, there is no positive economic incentive to split activity across both. Under those conditions, multi-chain use survives only because of non-price differentiation, legacy lock-in, speculation, governance preference, regulatory constraints, or outright subsidies. Remove those frictions, and the rational allocation is all on the cheaper chain.
Fifth: the positive-feedback dynamics of standards markets are self-reinforcing. Katz and Shapiro (1994) described markets exhibiting systems competition and network effects as tending toward outcomes where popular products become inherently more valuable, creating positive feedback loops between adoption and value. Shapiro and Varian (1999) characterised these markets as “tippy”—once the tipping point is reached, convergence accelerates. The multi-chain equilibrium, where activity is distributed evenly across many ledgers, is not the expected long-run outcome of network competition. The expected outcome is dominance by one.
VI. The Conditional Claim, Stated Honestly
BSV asserts that it provides the relevant functionality—payments, data, smart contracts, tokenisation, micropayments, enterprise data management—on one chain, at lower cost per transaction, and at scale sufficient to handle volumes that other chains cannot absorb without layered architectures.
This is either true or it is not. It is an empirical claim, and it can be tested empirically: by throughput benchmarks, by cost comparisons, by functional audits, and by sustained production workloads. No amount of rhetoric substitutes for demonstration.
But if it is true—if BSV, as a factual matter, offers the relevant functionality on one chain, at lower cost, and at sufficient scale and reliability—then the economic case follows directly from the propositions above. The incentive to use an additional general-purpose blockchain is weak or absent for those use cases. Adding another chain adds conversion costs, coordination overhead, bridge risk, and intermediary rent. It does not add value.
This is not a faith claim. It is a conditional economic argument. The antecedent must be demonstrated. But the consequent is standard network economics.
VII. Objections Worth Taking Seriously
A strong argument addresses its best objections rather than its weakest.
Specialisation. The strongest case for multiple chains is that one platform genuinely cannot deliver a needed function, governance model, legal posture, latency profile, confidentiality architecture, or developer environment. This is true in principle and sometimes true in practice. Specialised chains can persist where their specialisation creates value that a general-purpose chain cannot replicate.
But specialisation is a niche justification. It does not rebut convergence if the dominant chain can absorb those functions natively at comparable or lower cost. The protocol wars showed exactly this pattern: specialised stacks survived temporarily, but as the general-purpose standard expanded its capabilities, the niches shrank. The question is whether the specialisation is permanent or transitional.
Competition is healthy. Competition matters during discovery. But after a standard emerges, perpetual incompatibility is not free competition; it is duplicated overhead. The 1990s networking experience is instructive: the market experimented with several standards and then converged. The competition that mattered was the competition to become the standard, not the indefinite maintenance of incompatible parallel networks. Katz and Shapiro (1994) noted that in systems markets, the battle is often fought before the tipping point, and once tipping occurs, the competitive dynamics change fundamentally.
Bridges solve the problem. The empirical record does not support this. Bridges add trust assumptions, complexity, attack surfaces, and costs. As demonstrated above, they have been the single largest source of financial loss in decentralised finance. They are closer to protocol gateways than to true unification—and the protocol gateways of the 1980s were not a long-term solution. They were a transitional cost of fragmentation.
Multiple chains reduce systemic risk. This is plausible in some settings. Segmentation can contain failures. But it also fragments liquidity, duplicates infrastructure, and pushes users into intermediated cross-chain pathways that may themselves become systemic points of failure. The $2.8 billion in bridge losses is evidence that the interoperability layer can be more fragile than the chains it connects. The tradeoff must be argued on evidence, not assumed as self-evident.
VIII. Many Chains Do Not Create Freedom
There is a romance to the multi-chain vision. It sounds like pluralism. It sounds like choice. It sounds like a world where no single entity controls the rails and every community can run its own ledger.
But the romance dissolves on contact with economics. A world of many incompatible ledgers is not a world of freedom. It is a world of toll booths. Every boundary is a fee. Every crossing is a risk. Every bridge is an intermediary. Every exchange is a chokepoint. The architecture that was supposed to disintermediate finance ends up reintermediating it at every seam.
The networking history is not merely illustrative. It is predictive. General-purpose economic networks tend toward standardisation because compatibility is economically valuable and fragmentation is economically costly. The 1990s protocol wars ended with one dominant suite and a graveyard of gateways. There is no reason to believe that blockchain markets will behave differently, and considerable reason—drawn from network economics, from standards theory, from the empirical record of bridge failures, and from the design objectives of Bitcoin itself—to believe they will behave the same way.
If one ledger can do everything the others can do, and do it more cheaply, then fragmentation is not diversity. It is an artificial tax on users, collected by intermediaries who exist only because the market has not yet finished converging.
The market will finish.
References
Arthur, W. B. (1989). Competing technologies, increasing returns, and lock-in by historical events. The Economic Journal, 99(394), 116–131. https://doi.org/10.2307/2234208
Belchior, R., Vasconcelos, A., Guerreiro, S., & Correia, M. (2021). A survey on blockchain interoperability: Past, present, and future trends. ACM Computing Surveys, 54(8), 1–41. https://doi.org/10.1145/3471140
Computer History Museum. (n.d.). Protocol wars. CHM Revolution. https://www.computerhistory.org/revolution/networking/19/376
Economides, N. (1996). The economics of networks. International Journal of Industrial Organization, 14(6), 673–699. https://doi.org/10.1016/0167-7187(96)01015-601015-6)
Farrell, J., & Saloner, G. (1985). Standardization, compatibility, and innovation. RAND Journal of Economics, 16(1), 70–83. https://doi.org/10.2307/2555589
IBM. (n.d.). What is Systems Network Architecture (SNA)? IBM Documentation. https://www.ibm.com/docs/en/zos-basic-skills?topic=implementation-what-is-systems-network-architecture-sna
IBM. (n.d.). TCP/IP tutorial and technical overview (GG24-3376). IBM Redbooks. https://www.redbooks.ibm.com/redbooks/pdfs/gg243376.pdf
Katz, M. L., & Shapiro, C. (1985). Network externalities, competition, and compatibility. American Economic Review, 75(3), 424–440.
Katz, M. L., & Shapiro, C. (1994). Systems competition and network effects. Journal of Economic Perspectives, 8(2), 93–115. https://doi.org/10.1257/jep.8.2.93
Maathuis, I., & Smit, W. A. (2003). The battle between standards: TCP/IP vs OSI—victory through path dependency or by quality? In T. M. Egyedi, K. Krechmer, & K. Jakobs (Eds.), Proceedings of the 3rd IEEE Conference on Standardization and Innovation in Information Technology (pp. 1–12). IEEE.
Nakamoto, S. (2008). Bitcoin: A peer-to-peer electronic cash system. https://bitcoin.org/bitcoin.pdf
Novell. (n.d.). IP tunneling for IPX. Novell Documentation: Novell Internet Access Server 4.1. https://www.novell.com/documentation/nias41/iptuneun/data/h80pfylb.html
Rashid, A., et al. (2025). SoK: Cross-chain bridging architectural design flaws and mitigations. Digital Communications and Networks. https://doi.org/10.1016/j.dcan.2025.100429
Shapiro, C., & Varian, H. R. (1999). Information rules: A strategic guide to the network economy. Harvard Business School Press.
Zhang, M., Zhang, X., Zhang, Y., & Lin, Z. (2024). Security of cross-chain bridges: Attack surfaces, defenses, and open problems. In Proceedings of the 27th International Symposium on Research in Attacks, Intrusions and Defenses (RAID 2024) (pp. 1–19). ACM. https://doi.org/10.1145/3678890.3678894