Neutral Financial Infrastructure

The thesis

Financial market infrastructure is genuinely hard to build: an exchange-grade order book, a margining system, and a consensus layer that agrees on global state are each multi-year engineering projects on their own. If every team that wants to run a market for a new asset has to build all three from scratch, the economics favor large centralized incumbents and entry barriers stay permanently high. Jeff Yan's answer at Hyperliquid is to build that infrastructure once, hold it neutral, open to anyone and favoring none, and let every builder compose on top of it. A deployer's job shrinks to specifying which market is worth running: they do not build the order book, do not manage margining, and do not worry about consensus security, work that shrinks by what Yan calls several orders of magnitude.¹

Two mechanisms implement it. A permissionless deployment standard lets any deployer launch a perpetual futures market by specifying its parameters, with the infrastructure underneath already provided; the deployer's real contribution is knowing which market is worth deploying, having the distribution to seed liquidity, and maintaining the market's specification. Builder codes let interface builders register a referral code so that users who opt in generate fee revenue for whoever built the interface they used, creating a distinct incentive layer for the separate problem of distribution. A team with strong distribution but no infrastructure, a mobile wallet with millions of users, can plug in through a builder code; a team with a genuinely novel market idea but no distribution can deploy permissionlessly and compete in the open market instead of needing to build a user base first.

Protocol genesis neutrality

The material that develops this furthest adds a deeper claim: for infrastructure meant to be credibly neutral, how it was born matters more than how efficiently it was capitalized. The argument works backward from Bitcoin: it would not be Bitcoin if Satoshi had raised a funding round, even from the best-aligned investors on the cleanest possible terms, because insiders present from day one leave a permanent mark on the record of the thing, regardless of how widely the resulting token later disperses.² This is explicitly not an anti-investor argument; venture capital allocates capital efficiently and has done far more good than harm as an industry. The claim is narrower: when the thing being built is neutral infrastructure for something as consequential as money, neutrality itself is worth more than capital, which makes the decision not to raise venture funding a founding-structure choice rather than a financing preference. Yan is explicit that full replication of Satoshi's example is impossible, since anything built afterward operates in a competitive market that requires real funding and innovation to survive, but treats approximating those ideals, maximum neutrality at genesis, open to any builder, no informational or equity head start for insiders, as still worth striving toward.

Extending to regional builders and incumbent software

A concrete near-term use of the builder-code layer is regional exchanges: rather than pitching decentralized finance abstractly to existing fintech users, adoption spreads through localized applications that speak a country's language, serve users facing a destabilizing or hyperinflating local currency, and provide a path from local currency into an on-chain store of value, with trading volume routed through the shared order book underneath.³ The same logic extends to established software companies with existing distribution: a company that already routes financial transactions for its users can ask why it should rebuild an order book at all, keep its own interface and customer relationship, and simply route the execution layer through infrastructure that already works, something Yan argues only a decentralized system can offer, since a traditional exchange has a direct competitive interest in owning the distribution layer itself and would not make the same arrangement available.⁴

The contrast with vertical integration

Where Fernando de Leon responds to fragmented, unreliable supply chains by building every layer internally, an instance of vertical integration from necessity, Yan strips every layer of financial infrastructure away and makes it available to anyone competent enough to use it. Both are responses to a structural inefficiency, one in physical supply chains and one in market infrastructure, but they run in opposite architectural directions: de Leon accumulates control, Yan distributes it.

Open questions

The trust-based curation argument, that users route to interfaces that have earned trust, may not hold once there are thousands of permissionlessly deployed markets, since evaluating interface trust at that scale exceeds most users' capacity and the lookalike and phishing attack surface grows right along with the number of deployments. Neutral infrastructure also still requires a neutral infrastructure provider that does not front-run, self-deal, or selectively exclude participants, which remains a real trust dependency on the core team's integrity rather than something the architecture eliminates on its own.