The event ends. Most of the internet around it does too.

There is a pattern that plays out around every major global event, and it is so familiar by now that almost nobody questions it anymore. A city wins the right to host something enormous — the Olympics, a World Cup, a world’s fair. The excitement builds. Committees form. Budgets are approved. And somewhere in that flurry of activity, someone commissions a website.

Then another website. And an app. And a campaign microsite. And a ticketing portal. And a social media handle. And a hashtag strategy. And perhaps, if the budget is generous and the brief is ambitious, a whole suite of “digital engagement tools” that the marketing deck describes with words like “immersive” and “world-class” and “legacy-focused.”

The event happens. It is extraordinary. Athletes perform at the limit of human possibility. Crowds gather. The world watches. Then the closing ceremony ends, the flame is extinguished, and the television crews fold up their cables and fly home.

And the websites? They get archived, if anyone remembers to do it. Or they just quietly disappear — DNS records not renewed, hosting subscriptions lapsed, servers decommissioned. The digital footprint of an event that consumed years of planning and billions in investment evaporates in months. Sometimes weeks.

We found ourselves thinking hard about this problem long before we started building Queensland Foundation. Because when you sit with it honestly, it reveals something uncomfortable about how we have collectively treated the digital dimension of major events: as a communications channel, not as infrastructure. As a temporary broadcast tool, not as a lasting record. As something that serves the event, rather than something the event should serve.

The question we kept returning to was simple, even if the answer turned out to be anything but: what would it look like to build digital infrastructure around a major event that was genuinely designed to last?

The difference between event marketing and event legacy

Before we get into what we built and why, it is worth being precise about this distinction, because it matters enormously and it is blurred almost everywhere.

Event marketing is activity in service of the event itself. It exists to sell tickets, build excitement, inform attendees, manage logistics, promote sponsors, and generate coverage. It is inherently temporary by design — not because anyone is being careless, but because the event has a fixed horizon. The campaign has a launch date and a close date. The app serves a function that ends when the last result is posted. The website answers questions that no longer need answering once the athletes go home.

This is not a criticism. Event marketing is important and often brilliant. The problem is when event marketing is mistaken for event legacy, or when an organisation announces “digital legacy” and then delivers a beautifully designed website that will be decommissioned in three years because the domain renewal wasn’t built into any long-term budget.

Legacy, real legacy, is something different. It is infrastructure that exists independently of the event’s operational lifecycle. It is a thing that the event catalyses but does not contain. Physical legacy looks like stadiums repurposed for community sport, transport networks that serve a city for generations, parklands opened up for public use. The most thoughtful event planning takes exactly this approach — designing for the legacy function first and overlaying the event requirements on top of it.

Digital legacy should follow the same logic. But it almost never does. And the reason, we think, is that the underlying technology of the web has historically made genuine digital permanence almost impossible.

Traditional domains are rented, not owned. You pay a registrar every year to maintain your right to use an address. If you stop paying — because your organisation loses funding, because the project team disbands, because a server migration goes wrong, because the renewal slips through the cracks — you lose the address. Someone else can register it. The link breaks. The record disappears. The thing you built is not just gone from the internet; it is potentially occupied by something entirely unrelated, or worse, something actively harmful.

This is the foundational fragility that sits beneath almost every piece of digital infrastructure built around major events. No matter how well-intentioned the work, no matter how significant the content, the address that points to it is rented on an annual basis from a centralised intermediary. The moment that relationship lapses, the address is gone.

We are not the first people to notice this. But we think we are among the first to do something specifically and structurally different about it, in the context of a place and an event that matters to us personally.

What Brisbane 2032 represents as a moment in time

The Brisbane 2032 Olympic and Paralympic Games is not just a sporting event. It is a generational moment for Queensland — a once-in-decades opportunity to present this state, this region, and this culture to the world. The planning horizon for an event like this is extraordinary in its ambition. Infrastructure decisions being made right now will shape Brisbane’s transport, its stadiums, its urban fabric, and its economy for decades. The physical legacy of the Games is being designed, quite deliberately and explicitly, to outlast the event itself.

We watched this conversation unfold — the genuine seriousness with which planners, engineers, and policymakers were approaching the question of legacy — and we kept asking ourselves: is anyone having this conversation about the digital dimension? Not about the broadcast infrastructure for the Games themselves, not about the operational technology that will run the venues, but about the namespace — the layer of digital addresses and identities that a place and an event accumulate, and what happens to those addresses after the flame goes out?

The answer, as far as we could tell, was no. And that absence seemed to us like both a gap worth filling and, if we were honest about it, an opportunity to do something genuinely new.

Building a permanent namespace

Queensland Foundation has secured six permanent onchain TLDs for Queensland and its defining places: .queensland, .qld, .brisbane, .surfersparadise, .gold-coast, and .brisbane2032. These are not traditional web domains. They are not registered through a centralised registrar on an annual subscription. They are not subject to renewal and cannot expire.

They are permanent onchain addresses — recorded on blockchain infrastructure, immutable, transferable, and owned outright by whoever holds them, for life, with no fees ever again after the initial purchase.

The starting price is five dollars, paid once. No annual fees. No renewal windows. No risk that a lapsed payment causes an address to fall into someone else’s hands.

We want to explain why this matters, and why we think the permanence is not just a feature but the entire point.

When you register an address in the .brisbane2032 namespace, you are not renting a piece of digital real estate that is tied to the operational lifecycle of a Games organising committee. You are not dependent on any organisation maintaining a server or paying a bill. You own a permanent onchain record. That record does not expire when the Games end. It does not expire when organising committees are dissolved. It does not expire when the website hosting your content is migrated or decommissioned. It does not expire at all.

This is the structural difference we set out to create. Not a better event website. Not a more thoughtful campaign microsite. A different kind of infrastructure altogether — one designed explicitly to outlast the event it is built around.

Why the blockchain choice is the right one for this problem

We are aware that “built on blockchain” can sound like jargon in search of an application. So it is worth being specific about why blockchain infrastructure is the right technical choice for this particular problem, rather than just a fashionable one.

The problem we are solving is permanence under conditions of institutional uncertainty. Traditional digital addresses fail to outlast events not because of any technical limitation in the web itself, but because of the institutional arrangements that underpin them. Domains are maintained by registrars. Registrars are businesses. Businesses close, pivot, merge, and deprioritise things that are no longer commercially interesting. Organising committees for events are temporary by design — they are set up to deliver the event and then wound down. No organising committee has a ten-year mandate to maintain digital infrastructure.

Blockchain infrastructure changes this calculation fundamentally. An onchain record is not held by a company or a committee. It is held by a wallet, and the wallet is held by a person or an organisation, and the record persists independently of any third-party service remaining operational. There is no registrar to go out of business. There is no annual fee to forget to pay. There is no centralised server to decommission.

The immutability and decentralisation of blockchain infrastructure make it the only technical substrate we are aware of that can genuinely deliver on the promise of permanence — not as a marketing claim, but as a structural property of how the address works.

There is also something important about the ownership model. Traditional domains are, in a precise legal and technical sense, leased rather than owned. You have a contractual right to use an address for as long as you pay, but that right can be revoked under various circumstances, and it does not function as a transferable asset in the same way a physical property does. An onchain address is different. It is an asset. It can be transferred, inherited, sold, or held indefinitely. The relationship between an owner and their onchain address is structurally more like property ownership than like a subscription service.

For a community, a business, an institution, or an individual trying to establish a permanent digital presence tied to a place or an event, that distinction matters enormously.

The specific texture of building around .brisbane2032

When we began thinking about what a permanent namespace around Brisbane 2032 would look like in practice, we wanted to understand it from the ground up — from the perspective of the people who might actually want to hold an address in this namespace and what it would mean to them.

There are athletes who will compete at these Games and who, long after the closing ceremony, will want a permanent digital record of what they achieved. A verifiable, immutable address that says: this person competed here. Not hosted on a corporate platform that could be acquired, deprecated, or redesigned into something unrecognisable. A permanent onchain address that they own, that carries whatever content they choose to point it to, and that will still exist and still belong to them decades from now.

There are communities in Queensland whose connection to the Games runs deeper than tickets and television coverage — communities involved in its planning, its volunteer programs, its cultural components. Those communities deserve digital infrastructure that is as durable as their contribution, not digital infrastructure that evaporates three years after the closing ceremony because no one budgeted for its maintenance.

There are local businesses in Brisbane and the Gold Coast and across Queensland for whom the Games represents a moment of global visibility that they would like to anchor themselves to in a lasting way. Not a temporary campaign that rides the wave and disappears. A permanent onchain address that says: we were here, we were part of this, and this record will exist as long as we want it to.

And there are institutions — cultural organisations, government bodies, research universities, community foundations — that have genuine long-term reasons to maintain a digital presence tied to Brisbane 2032 as a historical moment. For those institutions, the question is not how to build a website for the Games, but how to build infrastructure that will serve researchers, historians, and communities for the fifty years after the Games end.

The .brisbane2032 TLD exists for all of these purposes. It is not a campaign tool. It is a namespace for a moment in history, designed to remain accessible and meaningful long after that moment has passed.

The white elephant problem, and how it applies to digital infrastructure

Anyone who has thought seriously about major event legacy knows the white elephant problem. It is the most well-documented failure mode in the history of hosting large events: the stadium that costs a fortune to build and then sits half-empty for decades, the athlete village that becomes a ghost town, the infrastructure investment that served a two-week event and then found no community use case.

The physical planning community has developed genuine sophistication in addressing this problem. The most thoughtful approaches now start from the legacy function — what does this community need from this infrastructure over the next twenty years? — and then work backwards to determine how those permanent needs can be met in a way that also serves the event.

The digital equivalent of the white elephant is less visible but just as real. It is the elaborate event website that required a significant investment to design and build, that serves its purpose brilliantly during the event, and that then becomes a maintenance burden nobody wants to own, until eventually the decision is made to take it offline. The content disappears. The investment is wasted. And the community that might have benefited from a permanent record of what happened is left with broken links and archived screenshots.

We built Queensland Foundation, and specifically the .brisbane2032 TLD, as an answer to the digital white elephant problem. The infrastructure we are creating does not become a maintenance burden because it does not require ongoing maintenance to remain accessible. The onchain record simply exists. The address belongs to its owner. The owner decides what it points to, and can change that decision at any time. But the address itself is permanent and requires nothing further from anyone to remain so.

This is a fundamentally different relationship between infrastructure and time. Traditional event websites age. They look dated. Their platforms become deprecated. Their CMS requires updates. Their hosting contracts expire. Eventually they become liabilities rather than assets. An onchain address does not age in this way. It does not have a platform that becomes deprecated. It does not require a CMS update. It simply exists on the blockchain, owned by whoever registered it, pointing to whatever they choose to point it to.

Place as permanent infrastructure

There is another dimension to what we are building that goes beyond the specific moment of Brisbane 2032, and it is worth taking time with because it shapes how we think about the whole project.

Queensland is a place with a distinctive identity — geographically, culturally, and increasingly in the global imagination. The Gold Coast is one of the most recognisable place names in the world. Surfers Paradise is an address that carries weight far beyond its coordinates. Brisbane is a city in the middle of an extraordinary period of growth and international prominence. Queensland as a whole is a name that means something specific and significant to people all over the world.

The idea that the digital addresses associated with these places should be permanent is not just a practical claim about infrastructure. It is a claim about the relationship between a place and its digital representation. A place that exists in the physical world for millennia should not have a digital address that expires because a payment was missed. The permanence of the place should be reflected in the permanence of its digital infrastructure.

When we secured the .queensland, .qld, .brisbane, .surfersparadise, and .gold-coast TLDs alongside .brisbane2032, we were thinking about exactly this. These are not just event-related addresses. They are the foundational layer of Queensland’s permanent digital identity — a namespace that reflects the permanence and significance of the places and communities it represents.

Brisbane 2032 is a moment in that longer story. It is an extraordinary moment — a moment of global significance, of enormous investment, of genuine community pride. But it is a moment. The places where it happens predate it by decades and will outlast it by decades. The digital infrastructure we build around those places should reflect that reality.

What it means for something to be owned, not leased

We have found ourselves returning to this distinction repeatedly, because it is at the heart of why permanence matters and why the onchain model is so different from anything that existed before.

When you lease something, your relationship with it is conditional. It persists only as long as the conditions of the lease are met. You cannot make long-term plans that depend on it, because those plans are contingent on conditions that may change. You cannot treat it as an asset in the same way. You cannot build on it with confidence, because the foundation itself is uncertain.

When you own something, the relationship is different in kind, not just degree. You can make long-term plans. You can invest in it without worrying about the foundation disappearing. You can treat it as an asset — something of lasting value that can be transferred, inherited, or built upon across time horizons that go well beyond any subscription term.

The web has operated on a lease model since its inception. Every domain name is rented. Every year, registrars collect fees that are, in economic terms, closer to property taxes than to market prices — arbitrary ongoing costs that confer no additional value and serve mainly to enrich the intermediary. And every year, a significant number of valuable domain names lapse and disappear because their owners missed a renewal or because the organisation that held them ceased to exist.

The onchain model eliminates this entirely. One payment, once, and the address belongs to you. Not for a year. Not for a decade. Permanently. There is no renewal. There is no expiry. There is no intermediary holding the address on your behalf and requiring annual tribute to continue doing so.

For individuals, this is a meaningful change in how digital identity works. For communities and institutions trying to maintain a permanent digital record of something significant, it is transformational.

The question of what gets built in this namespace

We are sometimes asked what will actually be built on these addresses — what content will live at addresses in the .brisbane2032 and .brisbane and .queensland namespaces. The honest answer is that we do not know in full, and we think that is appropriate.

The namespace is infrastructure. What gets built on infrastructure is determined by the people who own parcels within it, and by the communities and purposes they serve. When a city builds a road network, it does not specify what buildings will be constructed alongside it. When a telecoms company lays fibre, it does not determine what services will be delivered over it. The infrastructure creates possibility. The community fills that possibility with meaning.

What we expect, based on the nature of the communities and institutions connected to Brisbane 2032 and Queensland more broadly, is a rich and varied ecosystem. Personal addresses for athletes, competitors, coaches, and volunteers. Institutional addresses for organisations involved in the Games. Cultural addresses for projects that document and preserve the experience of the event. Commercial addresses for Queensland businesses that want to anchor their identity to this place and this moment in a lasting way. Academic and research addresses for institutions whose work intersects with the Games or with Queensland’s emergence as a global city.

None of this requires our ongoing involvement to happen. That is the point. The infrastructure exists. The namespace is permanent. The people who register addresses within it own them forever. What gets built is up to them.

Thinking in decades, not campaign cycles

One of the habits that shapes how we think about this project is what we might call the fifty-year test. When we are designing something, we ask ourselves: will this still be meaningful in fifty years? Will someone be grateful that this infrastructure exists, or will they be frustrated that it was not built to last?

Event marketing does not need to pass the fifty-year test, and we are not suggesting it should. A ticketing website for Brisbane 2032 is not designed to be meaningful in fifty years and should not be evaluated on that basis. It exists to serve a purpose in a specific window, and it should be excellent at that purpose.

But digital infrastructure is different. If a historian in fifty years wants to understand what Brisbane 2032 meant to the people who lived through it — what businesses existed, what community organisations participated, what individuals were part of the moment — where will they look? The physical record will be there: the stadiums, the parklands, the transport infrastructure. But the digital record, if it was built on traditional infrastructure, will have largely evaporated. Broken links. Decommissioned servers. Expired domains pointing to parking pages.

The onchain addresses in the Queensland Foundation namespaces will still exist in fifty years. They will belong to their owners or to whoever their owners have transferred them to. They will still be resolvable, because the blockchain record is permanent. They will constitute a genuine digital archive of Queensland’s presence at this moment in history — not because we have built a centralised archive, but because the infrastructure we have laid is permanent by design.

This is what it means to think in decades rather than campaign cycles. It is to accept a different set of constraints and a different set of responsibilities. It is to build not for the peak of attention around an event but for the long period of time that follows, when the attention has moved on and the value of permanence becomes most clear.

Why Queensland, and why now

Queensland Foundation is a Queensland project. The people who built it are connected to this place — to its landscape, its communities, its culture. We built it here not because it was the most commercially obvious move but because we believe in Queensland’s significance, and because we wanted the first permanent onchain namespace built around a place and its moment in history to be rooted somewhere we could genuinely speak about with authority and care.

Brisbane 2032 gave us a specific and urgent reason to act. The Games have a fixed date. The window in which to establish permanent infrastructure around that moment is real and finite. Once the event is over, the opportunity to build something that genuinely precedes and outlasts it — something that was there from the beginning, not retrofitted after the fact — will have passed.

But even beyond the specific moment of Brisbane 2032, we think Queensland deserves permanent digital infrastructure that reflects the scale and significance of the place. .queensland and .qld should be the foundational layer of Queensland’s digital identity for the next century. .brisbane should be the permanent onchain namespace for a city that is growing rapidly and taking its place as one of the genuinely significant cities of the Asia-Pacific. .gold-coast and .surfersparadise should anchor the digital identity of places that are already globally recognised.

These are not temporary addresses for temporary purposes. They are permanent digital infrastructure for a permanent, significant, and growing place.

The relationship between physical and digital legacy

We think about the relationship between physical and digital legacy a great deal, because we believe they are more intertwined than the conversation around events typically acknowledges.

When planners think about the physical legacy of Brisbane 2032, they think about what those venues will be used for in the decades after the Games, what transport improvements will serve communities for generations, what urban regeneration will be catalysed by the moment. They are thinking, correctly, about infrastructure that is designed to endure.

We are doing the same thing in the digital dimension. The stadiums being built for Brisbane 2032 will still exist in 2082. The onchain addresses in the .brisbane2032 namespace should still exist in 2082. The community organisations, businesses, and individuals who anchor their digital identity to this moment should be able to do so with the same confidence that the physical infrastructure of the Games will outlast the event itself.

This is not a utopian claim. It is a technical reality that the onchain model makes possible for the first time. The permanence of blockchain infrastructure is not a promise or an aspiration — it is a property of how the system works. And that property, applied to the digital dimension of a major event, creates a completely different kind of legacy.

What we hope this demonstrates

Queensland Foundation is, among other things, a demonstration of what becomes possible when you take digital infrastructure seriously as legacy rather than as operations. It is an argument made in the form of a thing built, rather than in the form of a proposal or a paper.

We hope it demonstrates that the temporary, campaign-oriented approach to digital presence around major events is a choice, not a necessity. The technology now exists to build digital infrastructure that is genuinely permanent — that does not require ongoing institutional support to remain accessible, that cannot be taken down by a missed payment or a decommissioned server, that belongs to its owners permanently and can be transferred and built upon across generational timescales.

We hope it demonstrates that permanence and accessibility are not in tension. These addresses start at five dollars. Owning one forever requires no technical expertise, no ongoing payment, no annual renewal process. The barrier to permanent digital presence in this namespace is as low as we could make it.

And we hope it demonstrates that the places and events that matter most deserve digital infrastructure that reflects how much they matter — infrastructure that is designed, from the start, to outlast the moment that inspired it.

The event ends. The digital infrastructure we are building does not have to end with it. That is the whole point.