There is a particular discipline required to build something before anyone has asked for it — to lay rails into territory that looks empty, to string cable across an ocean before the traffic justifies the cost, to mint names when the wallets that will resolve them haven’t been created yet. Most people cannot hold that posture. The market punishes it, at least for a while. The critics are loud. And the patience required is genuinely hard to find in an industry that measures success in ninety-day cycles.
But the thing about infrastructure is that it only looks premature until it doesn’t. And then, almost overnight, it looks inevitable.
You Lay the Rails Before the Train Arrives
Planning for what is now known as the Dwight D. Eisenhower System of Interstate and Defense Highways began in the late 1930s. The cars weren’t filling those roads yet. The suburban sprawl that would come to depend on them utterly hadn’t been built. America was just beginning to see light at the end of the tunnel of the Great Depression, and the Federal Aid Highway Act of 1938 directed the Bureau of Public Roads to study the feasibility of a superhighway network. Nearly two decades of planning, argument, and false starts followed before a single mile was properly funded. It wasn’t until June 29, 1956, that Eisenhower signed the Federal Aid Highway Act, sanctioning a highway system of 41,000 miles, with the goal of being completed by 1975.
What did the highway look like in 1940? Empty. What did it look like in 1970? Essential. The infrastructure didn’t wait for the demand to materialize first. The demand grew into infrastructure that was already there.
The same pattern runs through every technology that came to define modernity. The need for communications has been felt so strongly that new ventures were undertaken as soon as or even before the underlying technology was available — the first land lines had barely been laid when, in 1845, the Brett brothers proposed that an insulated cable be laid across the English Channel. In 1854, Cyrus West Field conceived the idea of the telegraph cable and secured a charter to lay a well-insulated line across the floor of the Atlantic Ocean — before reliable technology existed to make it work, before the commercial volume was there to justify it, before anyone had proven it could be done. Obtaining the aid of British and American naval ships, he made four unsuccessful attempts, beginning in 1857. The first cable that finally worked stopped functioning just weeks after its completion. Despite despair at this catastrophe, the Atlantic Telegraph Company did not give up the ambition of uniting the two continents — lessons had been learned, especially on the need for careful cable manufacture and laying. In 1866, the British ship Great Eastern succeeded in laying the first permanent telegraph line across the Atlantic Ocean, and Cyrus West Field was the object of much praise on both sides of the Atlantic for his persistence in accomplishing what many thought to be an impossible undertaking.
The pattern is always the same: build the thing. Take the failure. Learn. Build it again, better. And eventually the world catches up to what you already put in the ground.
Then there is DNS. The introduction of the Domain Name System in 1983 enabled a scalable, distributed way to organize and access websites — years before the general public had any meaningful access to the internet, years before the World Wide Web existed, years before anyone needed to type a domain name into a browser. In October 1984, RFC 920 established seven generic top-level domains — including .com, .net, .org and .gov — to provide domain space for corporations, non-profits, schools, networks, US government offices, and the military. The first registered domain, Symbolics.com, came in 1985. The infrastructure existed. The population of users hadn’t arrived yet. It didn’t matter. The prior system, relying on a simple HOSTS.TXT file for mappings, had begun to show signs of strain due to the expanding network. DARPA’s push demonstrated an understanding of the necessity for a more structured and scalable system, which DNS provided.
They built the address system before there were enough addresses to need it. That’s the only way it works.
”The Names Already Exist” Is a Stronger Position Than “Coming Soon”
There is a posture I see constantly in this space: the tease. The landing page. The waitlist. The announcement that something is being built, will be minted, is almost ready, will launch soon. And I understand the mechanics — it generates attention, it creates a moment, it gives people something to follow.
But it is fundamentally weaker than the alternative. Because “coming soon” is a promise that can fail to be kept. It is contingent. It depends on execution, on funding, on the market, on the team not falling apart, on a hundred things that can and do go wrong between announcement and delivery.
“The names already exist” is different. It is a statement of completed fact. The work is done. The rails are in the ground. Whatever happens next — adoption, indifference, a ten-year wait — the foundation cannot be unmade.
The core Queensland names are minted. They are resolving. They exist as facts in the chain rather than as intentions in a deck. That is not a minor distinction. That is the entire distinction. Infrastructure that exists cannot be “coming soon.” It already came. The only question remaining is when the world finds out.
This matters because the most durable competitive positions in any infrastructure layer are built by the people who finish first, not the people who announce first. Research documents how contemporary cable routes frequently overlay historical telegraph routes, and how the physical landing sites chosen for new cables tend to be the same sites used for over a century. The routes were established by whoever was willing to do the hard, expensive, premature work of laying them first. That incumbency doesn’t dissolve. It compounds.
Brisbane 2032 Is a Horizon, Not a Countdown
I want to be careful here, because the easy version of this argument turns 2032 into a sales mechanism — a deadline to manufacture urgency, a number to put on a clock to make someone feel like they’re running out of time to buy something. That is not what I’m doing, and it is not what I believe.
Brisbane 2032 is not just a sporting event — it is the heart of a transformational period already driving infrastructure investment, attracting international attention, and reshaping Queensland’s economic landscape. The Brisbane 2032 Olympic and Paralympic Games will deliver the largest infrastructure investment in Queensland’s history. It will provide extraordinary opportunities for communities across Brisbane, Queensland, Australia, and Oceania — making Queensland even more inclusive, sustainable, connected, liveable, and prosperous.
The 2032 Delivery Plan outlines how a $7.1 billion venue capital works program will allow the Games to reach beyond Brisbane and enable Queensland to benefit from the legacy for years after 2032. The transport infrastructure, the digital uplift, the international attention — improved transport network with new rail lines and stations, northern and eastern Brisbane bus corridors, upgrades to the M1, faster rail from Brisbane to the Gold Coast — this is generational reshaping of the region. It is not a moment. It is a decade-long arc of transformation with a fixed horizon date that the world has already agreed to pay attention to.
That horizon matters to me not because it creates purchasing pressure, but because it is a known point at which onchain identity for Queensland places will either exist and be useful, or will not. I have made a bet that it should exist. I made that bet early, and I have done the work to make it real. The horizon validates the early work — it doesn’t create the urgency to do it.
This is how builders should think about meaningful dates. Not as countdowns that force action in others. As fixed stars by which you navigate your own construction schedule.
The Discipline of Looking Premature
Here is the hard part, the part most people in this space genuinely cannot sustain: the period between when infrastructure is built and when it is recognized is uncomfortable in a specific way. It doesn’t look like failure. It looks like irrelevance. That is worse.
Failure is legible. If something breaks, you know what happened. You can explain it. People extend sympathy, or at least understanding. But building something that works, that resolves correctly, that is precisely what it needs to be — and having the world simply not notice yet — that requires a different kind of patience. The infrastructure is doing its job. There are just no trains on the rails yet.
Contemporary cable routes frequently overlay historical telegraph routes, and the physical landing sites chosen for new cables tend to be the same sites used for over a century. This persistence is partly geological but largely political and economic — existing infrastructure, established relationships, and concentrations of capital all favor the same locations that were built first.
The advantage of having been first is not visible until it is suddenly decisive. The telegraph cable operators who survived the early failures and held their routes discovered that their incumbency was nearly impossible to dislodge. The highway system that seemed like overbuilding in the early 1960s became the substrate on which an entire economy ran. DNS — that quiet system built for a small academic network — became the phonebook of the entire human internet. The Domain Name System is one of those internet technologies that often fades into the background. As essential infrastructure, DNS runs silently behind the scenes to connect users to websites and internet services. Yet DNS has a history that mirrors the growth and evolution of the internet itself.
Fading into the background is not failure. It is the signature of infrastructure that is working. Infrastructure is not supposed to be exciting. It is supposed to be there, reliably, when needed.
Why Most Onchain Actors Can’t Do This
The onchain ecosystem selects hard against this kind of patience. Everything is optimized for the cycle — the mint, the floor, the flip, the narrative that burns hot for three months and then dies. The builders who survive are the ones who found a way to ignore that rhythm long enough to finish something real.
Most can’t. Not because they lack intelligence or even vision — many are sharp people with genuine ideas. But the incentive structure is a constant pull toward the short horizon. If you’re not producing visible momentum, you’re not being rewarded, and you may not survive long enough to be vindicated.
This is not a complaint. It is an observation about the selection pressure that determines who actually builds durable infrastructure in this space. The people who mint names for Queensland places when there is no obvious immediate demand for those names, who do the work to make them resolve correctly, who hold them through indifference and keep the infrastructure live — those people are making a bet that looks irrational by the metrics the market uses right now.
Brisbane 2032 is the first Games to be awarded under the International Olympic Committee’s new approach to sustainable and legacy-focused hosting — more than a sporting event, it is a catalyst for economic, social, and environmental progress across the region. That kind of thing — legacy-focused, long-arc, designed to matter after the event rather than just during it — requires exactly the kind of patience the market doesn’t reward in real time.
The rails are in the ground. That is not a small thing. Most people who said they would lay them haven’t. I have.
The Foundation Is Done
Let me be plain about what I am asserting here, because I think clarity matters more than hedging.
The core Queensland names exist. They resolve. They were built before it was obvious that they should exist, before the adoption that will eventually find them, before the horizon event that will make the region legible to a global audience in ways it hasn’t been before. They were built because that is what infrastructure builders do — they build before the demand arrives, so that when the demand arrives, the infrastructure is already there.
“Coming soon” would have been easier to say. It would have generated less criticism, demanded less capital, required less patience, created less of the uncomfortable silence that comes from having built something real in a market that wasn’t yet ready for it.
But “coming soon” is not the same as done.
The names already exist. The foundation is done. Adoption can come later, on its own schedule, at whatever pace the market decides. When it comes, it will find rails already in the ground — not a promise, not a landing page, not a countdown.
Infrastructure. Already built. Quietly resolving.
That is the position I wanted to be in. I am in it now.