The Question Nobody Asks Until It’s Too Late

Every major global event generates an enormous amount of digital energy. Websites are built, social handles are claimed, hashtags take on a life of their own, apps are launched in a rush of ambition and then quietly shelved. Entire digital ecosystems spring up around a single moment in time — and almost all of them vanish.

We’ve been thinking about this problem for a long time. Not in an abstract, academic way, but in a very practical one: what actually survives the event? What gets built that lasts? And more specifically — who owns the digital name of that moment, and what does that ownership really mean?

Those aren’t easy questions to sit with, because the honest answer is that very little survives. The official websites redirect or go dark. The apps are deprecated. The campaign URLs expire and get quietly absorbed into registrar parking pages or snapped up by speculators. The social accounts lose their verification and their following migrates on. The moment — which was genuinely enormous, genuinely world-historic — dissolves into digital noise, with almost nothing permanent left behind that ordinary people can actually hold onto.

We built Queensland Foundation because we believed something different was possible. We secured six permanent onchain TLDs — .queensland, .qld, .brisbane, .surfersparadise, .gold-coast, and .brisbane2032 — because we believe that place deserves to be permanent in the digital world, and that the people who belong to that place deserve to own addresses within it. But it was .brisbane2032 that made us think hardest about the question of namespace. Because the stakes around a global event are unique. And the opportunity that gets missed, over and over again, is almost heartbreaking once you see it clearly.

What Actually Gets Built Around a Global Event

Let’s be honest about what the digital infrastructure around a major global event typically looks like.

There’s an official website — usually well-funded, professionally designed, and built to last precisely as long as the organising body needs it. It serves a bureaucratic function more than a cultural one. It holds schedules, press releases, ticketing information, volunteer portals. It is, fundamentally, a logistics document masquerading as a home. When the event ends, the logistics document has served its purpose, and the question of what it becomes next is rarely answered well.

There are sponsor microsites. Built to drive campaign engagement over a defined window, designed to look exciting, and engineered to expire. There are countdown apps that count down to zero and then sit abandoned on phone screens, gradually removed with each software update until they’re simply gone. There are social accounts with millions of followers that, once the event ends, have nothing left to post, and slowly hollow out.

There are hashtags — and this is worth pausing on, because hashtags feel permanent but aren’t. A hashtag is not infrastructure. It’s a convention. It belongs to no one. It can be hijacked, satirised, abandoned, or simply buried beneath newer content until it becomes functionally invisible. The hashtag for any given global event will, within a few years of that event, return essentially nothing useful when searched. The content it indexed has aged, the platform’s algorithm has moved on, and the cultural moment it represented has been categorised as history.

Then there are the domain names. The traditional DNS domains — the .com, the .org, the country-code variants — that were registered for the event. These are perhaps the most instructive example of how broken the existing system is. A domain name in the traditional system is not permanent ownership. It is a lease. You register it for a year, or two, or ten, and then you pay again. Or you don’t, and it expires. And when it expires, it goes back to the pool. It can be re-registered by anyone. The name that carried the weight of an entire global event, the name that appeared in broadcast graphics and on the side of buses and in newspapers around the world, can be snapped up by a domain speculator twelve months after the closing ceremony. It happens constantly. It is a structural flaw in how we’ve built the internet — and most people simply don’t see it, because it happens quietly, after everyone has moved on.

This is the world we inherited. And it’s the world we decided to build something different inside of.

Why the Name of a Moment Carries More Weight Than We Admit

We talk a lot about physical legacy in the context of global events. The venues, the transport infrastructure, the urban renewal. These are important. They are real and they are lasting, and the communities that host major global events are rightly focused on making sure that physical investment turns into generational benefit. The stadium that’s still in use. The rail line that changed how people move through a city. The precinct that transformed a neglected industrial zone into a living neighbourhood. These are the legacies we celebrate, and we should.

But we rarely have the same conversation about digital legacy, and we think that’s a gap that needs to be addressed — not in the future, but now, before the event, while there’s still time to build something that will actually last.

The name of a moment carries enormous cultural weight. Think about what it means for something to be described with a particular name — a name that is tied not just to a place but to a specific point in time. That name will be searched for, referenced, and returned to for generations. Students will write about it. Journalists will reference it. Researchers will trace its legacy. The people who were there — who competed, who volunteered, who watched from the stands, who built the venues, who served the athletes, who watched on screens around the world — will use that name to locate and orient their own memories.

The name is a container. And the question that almost no one is asking, but that we think is essential, is: what is that container made of? Is it made of something permanent, or is it made of something that will silently expire?

In the traditional web, the answer is almost always that it’s made of something that will expire. That is not a metaphor. It is a literal technical fact. The domains will lapse. The hosting will stop being paid. The infrastructure will be decommissioned. The name will persist in memory and in reference, but the digital address associated with it will become a dead end.

We think that’s wrong. We think it’s wrong practically, and we think it’s wrong symbolically. A name that important should have an address that is permanent. Not permanent in the sense of “we’ll keep paying for it for a long time.” Permanent in the sense of: it cannot expire, it cannot be taken away, it has been recorded immutably on a blockchain, and it will exist for as long as that chain exists.

The Difference Between a Campaign and an Address

This is a distinction that matters a great deal to us, and we want to be clear about it, because it can seem subtle from the outside.

A campaign has a lifecycle. It has a beginning, a middle, and an end. It is designed to serve a particular purpose over a particular window of time. It may be excellent — beautifully designed, emotionally resonant, technically sophisticated. And when it ends, it ends. That’s not a failure. That’s what campaigns are supposed to do.

An address is different. An address is infrastructure. It exists independently of what is built on top of it. It persists regardless of whether the campaign that used it has concluded. It can be handed down, transferred, built upon, and referenced across generations. A physical address for a building doesn’t expire when the current tenant leaves. The street doesn’t disappear when the business closes. The infrastructure underneath is persistent, and everything built on top of it is built on a foundation that will still be there.

When we think about the digital infrastructure around a global event, we’ve been building campaigns when we should have been building addresses. We’ve been creating content when we should have been creating infrastructure. And the difference, compounded over time, is enormous.

Permanent onchain addresses change this equation entirely. When someone registers a .brisbane2032 address, they are not renting space on a server. They are not subscribing to a service. They are not participating in a campaign. They are claiming a permanent piece of digital infrastructure, recorded on the blockchain, that belongs to them — for life, with no renewals, no fees, no gatekeepers. That address exists independently of any organisation’s budget cycles or strategic priorities. It cannot be reclaimed by a registrar. It cannot be bought out from under the owner. It is theirs.

That is a fundamentally different relationship between a person and their digital address. And it’s a fundamentally different relationship between a community and the digital name of its most significant cultural moment.

What Gets Forgotten, and Why

We’ve been thinking about what gets forgotten, and the pattern is instructive.

What gets forgotten is almost always the unofficial layer. The small businesses that built their identity around the event. The artists who created work inspired by it. The community groups who organised around it. The individuals who had a specific, personal connection to it and wanted to express that connection in a form that would outlast the moment itself.

The official infrastructure has resources. The organising committees, the major sponsors, the broadcasters — these entities have the budgets and the teams to maintain a presence for years after the event. Even their maintenance is likely to be more thoroughgoing than what came before, because they have reputational reasons to care about legacy.

But the unofficial ecosystem — the one that gives any major event its real cultural texture and its genuine community character — has no such resources. The small business that named itself after the event. The fan who built a tribute website. The former volunteer who wanted to document their experience. The local school that developed a curriculum around it. These are the human-scale stories that make a global event feel like something more than a logistics exercise, and they are the stories that get lost.

In the traditional domain system, this community layer has nowhere permanent to live. Individuals and small organisations can register domains, but those registrations are leases that need to be renewed, and the renewal burden compounds over time. When life gets busy, when circumstances change, when the person who owned the account is no longer around to manage it — the registration lapses, the site goes dark, and the story is lost.

Permanent onchain addresses change this. When a Queenslander registers a .brisbane2032 address, they pay once, and that address is theirs for life. There is no renewal. There is no annual reminder that makes the ongoing maintenance feel like a tax. The address simply exists, permanently, in the public record of the blockchain. It is owned. It is traceable. It is the owner’s to use, hold, or transfer as they see fit, for as long as they choose.

That means the community layer — the human-scale, unofficial, culturally rich ecosystem that surrounds any major event — has the infrastructure it needs to persist. For the first time, the small story has the same permanence as the large one.

The Strategic Logic of Building Before the Event

There is a timing question here that we feel strongly about, and it comes down to the basic principle that infrastructure is most valuable when it’s built before the moment it needs to serve.

The analogy to physical infrastructure is useful again. You don’t build the transport network after the athletes have already arrived. You don’t pour the foundations of the venues the week before the opening ceremony. The physical infrastructure exists before the event, because the event’s success depends on it being there. The same logic applies to digital infrastructure, but it’s a lesson that the digital world has been slow to absorb.

Campaign websites get built close to the event because they’re campaigns — they’re designed to build to a peak of engagement and then wind down. But permanent digital infrastructure, the kind that will carry the name and the legacy of the event forward for decades, needs to be established early. Not because early registration is inherently valuable as a speculative exercise, but because the infrastructure that serves a community takes time to grow, to be adopted, to be understood, to become genuinely useful.

A namespace that is claimed after the event has already happened is, in some ways, a namespace claimed in retrospect. It can still be valuable. The record is still permanent. The addresses can still be issued and owned. But the opportunity to build the community layer before the moment of global attention — to have the infrastructure in place so that, when the world is watching, the digital identity of the place is already rich and deep and permanent — that opportunity is time-sensitive in a way that most digital opportunities are not.

We built Queensland Foundation and secured these TLDs early for this reason. We’re not interested in the speculative dimension of early registration. We’re interested in the community dimension. We want Queenslanders to have permanent digital addresses before their city takes the world stage, so that when that moment comes, the namespace around it is a living document of community ownership, not a collection of official pages and expired campaign URLs.

What “Permanent” Actually Means

We want to be careful about how we use the word “permanent,” because it’s a word that gets thrown around loosely, and we want to be precise.

In the traditional domain system, nothing is permanent. Everything is leased. The apparent stability of a long-held domain address is an illusion — or more precisely, it’s a product of continued payment and continued institutional will. Large organisations with long histories and stable finances can maintain the illusion of permanence for a very long time. But it is always contingent. It always depends on someone, somewhere, continuing to pay.

Blockchain-based infrastructure is different in a specific and important way. An onchain record is immutable. Once it is written, it cannot be altered or removed by any central authority. The record of who owns a particular address is public, verifiable, and cryptographically secured. There is no registrar who can reclaim it, no hosting company who can shut it down, no organisation whose budget pressures can cause it to lapse. The ownership is recorded on a distributed ledger, and it persists as long as that ledger exists.

This is not a small difference. It is a structural difference in the nature of the ownership relationship. And for something as culturally significant as the digital name of a global event, that structural difference matters enormously.

When we say that .brisbane2032 addresses are permanent, we mean that they are recorded on the blockchain and cannot be taken away. When we say that they are owned, we mean that they are cryptographically controlled by their holders and can only be transferred with the holder’s consent. When we say that they are free from renewals, we mean that there is no mechanism by which continued ownership requires continued payment. The ownership is total, and it is permanent.

That is a different kind of digital address. It is an address that can carry legacy in the truest sense — not legacy as a marketing concept, but legacy as a lived, transferable, permanent piece of digital infrastructure.

The Cultural Argument

We want to make a cultural argument here, not just a technical or strategic one, because we think the cultural dimension is where this conversation ultimately needs to land.

Every major global event is a story. It’s a story about a place, and a community, and a moment in time when the world turned its attention in one direction and found something worth celebrating. The stories that attach to that moment — the individual stories, the small stories, the stories that aren’t in the official broadcast but that are the true texture of the event — are the stories that make it meaningful, not just impressive.

Those stories deserve to be told, and they deserve to be told in a place that will endure. Not in a social media post that will be buried by the algorithm within forty-eight hours. Not on a platform whose business model may change, whose ownership may shift, whose terms of service may evolve in ways that make the content inaccessible or invisible. Not on a campaign website that will redirect in eighteen months to a corporate homepage.

In a permanent digital address. In a namespace that is explicitly and irrevocably tied to the moment those stories belong to. In a record that is public, verifiable, and lasting.

We think about the people who will look back on this event from ten, twenty, fifty years in the future. We think about the researcher trying to understand what it meant to live in Brisbane during this particular chapter of history. We think about the former volunteer trying to show their grandchildren what they were part of. We think about the small business owner who built something meaningful in the wake of a moment that changed their city, and who wants that story to exist somewhere that will still be findable long after they’re gone.

These are not abstract hypotheticals. They are the people for whom permanent digital infrastructure matters most. And they are the people who, in every previous version of this story, have been failed by infrastructure that treated their presence as temporary by default.

What a Namespace Is, When You Look Closely

We want to say something about what a namespace actually is, because we think the word obscures its own significance.

A namespace is a defined and bounded territory of meaning. When you create a namespace — when you say, “all addresses ending in .brisbane2032 belong to this particular context” — you are doing something that looks technical but is actually cultural. You are drawing a boundary around a community. You are saying: the things within this namespace are related to each other in a meaningful way. They share a context. They belong to the same world.

The power of that is easy to underestimate. In the traditional domain system, namespaces are generic and global. A .com address carries almost no cultural signal about the nature of its contents. It tells you that the thing behind the address is a commercial entity, approximately, and nothing more. It belongs to everywhere and therefore to nowhere.

A .brisbane2032 address is different in kind. It carries cultural information by its very existence. It tells you that the thing behind the address has a relationship to a specific place and a specific moment in time. That relationship might be direct — an official archive, a commemoration site — or it might be personal — a former athlete’s tribute page, a volunteer’s record of their experience, a local business’s story about what that period meant for them. But the relationship is signalled by the namespace itself. The address is a piece of cultural context, not just a technical pointer.

When we secured .brisbane2032 as a permanent onchain namespace, we were doing more than reserving a string of characters. We were creating the conditions under which a community of addresses could exist — addresses that are explicitly and permanently related to one of the most significant cultural moments in Queensland’s history. That community of addresses is a kind of cultural infrastructure. It is a defined space in which stories can be told, records can be kept, and ownership can be exercised — permanently, by the people who belong to that story.

The Gap Between Official and Community

There is always a gap between the official record of a major event and the community record. The official record is important — it documents what happened, who won, how it was organised, what it cost, what it produced. The community record is different. It documents what it felt like. What it meant to individuals. How it changed specific lives and specific places in ways that don’t show up in the official tallies.

We are interested in both, but we are especially interested in the community record, because that is the one that has historically been most at risk of being lost.

The official record has institutional backing. It has archivists and historians and well-funded legacy programmes. It will survive, in some form, because powerful organisations have reputational reasons to ensure that it does. The community record has none of that. It has individuals, and small groups, and memories that live on hard drives and in browser bookmarks and in accounts on platforms that may not exist in twenty years.

Permanent onchain addresses are, among other things, an attempt to give the community record a more durable home. When an individual can register a permanent digital address in a namespace that is explicitly tied to the cultural moment they were part of, they are not just claiming a piece of digital real estate. They are contributing to the permanent, public record of what it meant to belong to that community at that time. Their address exists in perpetuity, as a data point in the larger story, even if the content behind it changes over time or eventually falls silent.

That is not nothing. That is, in fact, quite a lot. The record of ownership itself — the fact that a particular person or organisation registered a .brisbane2032 address at a particular point in time — is a kind of testament. It says: we were here. We were part of this. This moment mattered enough to us that we wanted to hold a permanent piece of its name.

Why We Think About This Differently

We want to explain why we come at this question differently from most of the conversations happening around global events and digital legacy.

Most of those conversations are about content. What content should be preserved, what content should be archived, what content should be made accessible for future generations. These are important questions, and they deserve serious attention. But they are downstream of a more fundamental question: what is the infrastructure on which that content will live?

If the infrastructure is temporary, the content is temporary, regardless of how good the archiving intentions are. Content migrates, degrades, and eventually becomes inaccessible not usually because anyone decides to delete it, but because the infrastructure beneath it quietly expires. The hosting bill goes unpaid. The domain lapses. The platform changes its API. The format becomes obsolete. The content is still out there somewhere, in some sense, but it is no longer where it was, and the path to finding it has become a set of redirects and dead ends and archived snapshots that require effort and expertise to navigate.

Permanent onchain infrastructure changes the conversation, because it separates the infrastructure question from the content question. The infrastructure — the address itself — cannot expire. The content behind that address can change, can migrate, can evolve, as it always will. But the address remains. The name remains. The record that this address exists, and is owned by a particular party, remains. That is a different foundation to build on.

And when we think about the significance of having that foundation in place around a moment as large as a global event, we find it hard to overstate what it means. It means that the digital name of that moment — the namespace that will be searched, referenced, and returned to for generations — is built on something that will not quietly disappear. It is built on something that is owned by the community, permanently, by the people who chose to be part of it.

What We Believe About Place

We want to end with something that is, for us, the heart of why we built what we built.

We believe that place matters. Not just as geography, not just as a collection of addresses and postcodes and coordinates on a map, but as a form of identity. People who come from Queensland carry Queensland with them. The way a city sounds and smells and feels. The particular quality of light on the river. The way communities have grown up around specific neighbourhoods and specific events and specific moments of shared experience. These things are real, and they are worth preserving, and they deserve to be expressed in a digital form that is as permanent as the places themselves.

We are aware that the digital world has, for most of its history, been structurally indifferent to the specificity of place. The domain system is global and generic. The major platforms have no interest in the particularity of a specific city or a specific cultural moment — they are interested in scale and universality. The infrastructure of the internet was not built to honour the distinctiveness of a place like Brisbane, or the significance of a moment like the Games it will one day host.

We built Queensland Foundation to change that. To say that Queensland deserves a permanent presence in the digital world — not a campaign presence, not a temporary presence, not a presence that is contingent on the budget cycles of distant organisations, but a permanent, community-owned, blockchain-recorded presence that belongs to Queenslanders and endures as long as the digital world endures.

The namespace around a global event matters because the event matters. Because the place matters. Because the people who were there matter, and their stories matter, and those stories deserve to be told in a place that will still exist when the campaign websites have long gone dark.

That is what we built. That is what .brisbane2032 is. Not a campaign URL. Not a temporary domain. A permanent piece of the digital record, tied irrevocably to the most significant moment in Queensland’s history, available to every Queenslander who wants to hold a piece of it — for life, with no renewals, and no expiry.

We believe that’s the right thing to build. And we believe that, when you look clearly at the history of what gets built and what gets forgotten around global events, it becomes hard to argue for anything less.