The weight of a name

Of all the TLDs we hold, .brisbane2032 is the one that keeps us up at night — not with worry, but with possibility.

When we first looked at the six namespaces we wanted to secure for Queensland, the others had a certain clarity to them. .queensland is the state. .qld is how Queenslanders write it in shorthand. .brisbane is the city. .surfersparadise and .gold-coast are places people love, places with feeling and identity baked into them. They all map, more or less, to something that already exists in the world and will continue to exist long after any of us are gone.

But .brisbane2032 is different. It is not just a place. It is a moment. And moments, historically, are the hardest things to hold onto.

There is something unusual about encoding a year into a namespace. The year 2032 is a fixed coordinate in time — one that will always refer to the same thing, no matter when you read this. Long after the event it marks has passed, the name .brisbane2032 will still mean what it means today: Brisbane’s moment on the world stage, the year Queensland welcomed the planet, and the year that a city most people outside Australia once described as a pleasant second-tier metropolis announced itself as something more.

That is what we are holding with this namespace. Not just an address. A timestamp, permanently recorded on-chain, permanently available to anyone who wants to claim a piece of what that moment meant.

What a year can carry

History is full of years that became shorthand for entire chapters of human experience. Not all of them were good. Some were defined by crisis, some by conflict, some by unexpected transformation. But the ones tied to major civic or cultural moments — the ones anchored to something vast and coordinated and visible — carry a particular weight. They become reference points. They become the years people say they were there for.

Brisbane 2032 is shaping up to be one of those years for Queensland. The Olympic and Paralympic Games mark a transformative moment for Queensland, Australia, and the global Olympic and Paralympic movements — and as the first Games to be awarded under the International Olympic Committee’s new approach to sustainable and legacy-focused hosting, Brisbane 2032 is more than a sporting event. It is a catalyst for economic, social, and environmental progress across the region.

We are not in the business of making predictions about sporting outcomes or political decisions. But we are in the business of thinking carefully about how digital infrastructure relates to real places and real events. And what we see, when we look at the arc of what is being planned and built around the Brisbane 2032 Games, is an extraordinary amount of long-term thinking. People are not just planning for the event. They are planning for what comes after. Unlike a typical piece of infrastructure that serves a consistent purpose, Brisbane 2032’s infrastructure must scale from zero to maximum capacity and then to its legacy purpose.

That kind of thinking is rare. It is the kind of thinking that produces infrastructure worth something decades later. And it is exactly the kind of thinking that should, we believe, extend into the digital layer — into the names and addresses and identifiers that will be used to talk about this moment, long after the closing ceremony lights go out.

The problem with forgetting

Every major event in modern history leaves behind a debris field of digital infrastructure that nobody quite knows what to do with. Websites go dark. Official domains lapse. Event-specific URLs redirect to generic institutional pages or, worse, dead-link nowhere. The institutional memory of what happened, where, and why gets scattered across archived pages, broken links, outdated PDFs, and the private hard drives of people who were involved at the time.

This is not a trivial problem. It is a genuine loss. Future researchers, historians, educators, and citizens who want to understand what Brisbane 2032 actually was — what it felt like, what it produced, what it changed — will have to do archaeology through the residue of systems that were never designed to last.

The traditional web was not built for permanence. It was built for convenience and accessibility, which are different things. A .com domain is rented, not owned. Registrars lease traditional domains on an annual basis. In order to maintain ownership, the lessee must renew their membership each year — otherwise, they will lose their domain, which makes it available for others to take it. An institution can hold a domain for twenty years and then, through a missed renewal, a budget cut, or an organisational restructure, lose it overnight. The name dissolves into the pool. Someone else buys it. The connection between the address and the thing it represented is severed, permanently and without recourse.

We built .brisbane2032 to work differently. Unlike traditional domains, which require ongoing fees and centralised registrars, onchain addresses offer permanent ownership — once claimed, they are stored in a wallet like any other digital asset and fully controlled by their owner. There is no annual fee. There is no renewal. There is no registrar who can revoke access or decide the address is no longer worth supporting. What exists on-chain stays on-chain. The address is immutable, transferable, and permanent.

For an event of this significance, that matters more than almost anything else we could say about the namespace.

Who belongs in this space

From the beginning, we have thought about .brisbane2032 differently from the other TLDs in our portfolio. The others are civic and geographic — they belong to the people of Queensland in a broad, democratic sense, and we want as many people as possible to claim a piece of them. A plumber in Cairns can have joe.qld and it means something. A school in Toowoomba can claim students.queensland and carry that identity with them. A surf instructor can live at lessons.surfersparadise and make that address their own. That openness is intentional. Those TLDs are for everyone.

.brisbane2032 carries a different gravity. The year in the name creates a specificity that is more institutional than personal. When someone encounters an address ending in .brisbane2032, the implied claim is not just geographic or cultural — it is historical. It is a claim to have been part of something particular, at a particular time, in a particular place. That claim means more when it is made by entities whose connection to the event is real and verifiable.

We think about the kinds of addresses that could legitimately live under this namespace and feel, in each case, that they should be carrying something of weight. Imagine the official archive of an organising body, permanently accessible at an address within .brisbane2032. Imagine a venue authority maintaining its institutional record — the documentation of what was built, how it was used, and what it became after the Games — at a permanent on-chain address that cannot be revoked. Imagine a cultural programme, a community legacy initiative, a First Nations acknowledgment of the lands that hosted the world, each holding an address in this namespace as a form of permanent recognition.

These are not fanciful ideas. They are the natural next step in how institutions think about digital permanence. The organisations connected to Brisbane 2032 will, over the coming years and decades, face the same problem every post-event institution faces: how do you maintain continuity of identity when the event is over, budgets change, staff turn over, and the institutional priority shifts from delivery to legacy? A permanent on-chain address is one answer. It does not solve every problem, but it solves a particular, important one: the problem of the address itself becoming unavailable.

The architecture of legacy

We spend a lot of time thinking about what legacy actually means in a digital context. The word gets used heavily in the conversations surrounding major events — legacy venues, legacy infrastructure, legacy communities — but the digital layer tends to be treated as an afterthought, something that will sort itself out. It rarely does.

Physical legacy is, in some ways, easier to think about. With many previous hosts being plagued by ‘white elephant’ venues, the London Olympics has been pointed to as a successful example of legacy planning: infrastructure benefits the community long after the athletes have gone home. When a stadium is well-designed for post-event use, it continues to serve the community. You can see it, use it, maintain it. The case for investment is legible and ongoing.

Digital legacy is less visible and, perhaps for that reason, less rigorously planned. But it is not less important. The digital record of an event — the addresses, the archives, the institutional memory, the documentation of what was done and why — shapes how future generations understand what happened. If that record is fragmented, inaccessible, or simply gone, the narrative of what Brisbane 2032 meant becomes harder to reconstruct, less reliable, and more dependent on secondary sources that were never designed to carry the weight.

What .brisbane2032 offers, at its most fundamental level, is a stable namespace in which that record can live. Every address registered under this TLD becomes a fixed point in the digital geography of the event — a point that does not drift, does not disappear, and does not depend on any institution continuing to pay an annual fee to maintain its existence.

Think of it this way: if the physical infrastructure of Brisbane 2032 is being designed with a fifty-year horizon in mind, the digital infrastructure should carry the same ambition. An on-chain namespace is, in practical terms, one of the few digital structures that can actually deliver on that ambition. Unlike traditional DNS, on-chain TLDs offer permanent, censorship-resistant ownership recorded on a public ledger. There is no server to decommission. There is no company to go bankrupt. There is no governance body to dissolve. The record exists because the chain exists, and the chain exists because thousands of independent participants maintain it.

That is not a marketing claim. It is a structural fact about how on-chain addresses work. And it is the core reason we believe .brisbane2032 has a potential significance that extends far beyond what most people currently imagine for digital addresses attached to events.

What permanence actually means

We want to be precise about this, because the word “permanent” gets overused.

We do not mean that the addresses registered under .brisbane2032 will necessarily point to the same content forever. Content changes. Institutions update their records. Archival standards evolve. What we mean by permanence is simpler and more specific: the address itself will not cease to exist. It will not expire. It will not be reassigned without the owner’s consent. It will not be taken offline by a registrar making a commercial decision.

Unlike traditional domains, which are typically rented via annual renewals, Web3 domains are purchased once and owned permanently, with no renewal fees. Ownership is verifiable on-chain, and the domains can be traded just like any other digital asset.

This means that an institution holding an address under .brisbane2032 in the year the Games are held will still hold that address twenty years later, unless they choose to transfer it. The address is theirs. Not leased. Not contingent. Owned, in the same way a physical asset is owned — with the crucial advantage that an on-chain asset cannot be lost to fire, flood, or the passage of time in the way physical assets can.

For archival institutions, this distinction is not academic. It is the difference between a permanent location and a temporary one. And when you are trying to build a digital record meant to outlast the organisation that created it, permanence is everything.

The addresses we imagine

We are going to be speculative for a moment. We think that is appropriate for a namespace this forward-looking.

Imagine a future in which the key institutional actors of Brisbane 2032 — the organising bodies, the delivery authorities, the venue operators, the cultural partners, the community legacy programmes — each hold a permanent on-chain address under .brisbane2032. These are not necessarily websites in the traditional sense. They might be archival repositories, authenticated records, pointers to documentation that lives elsewhere but is referenced from a stable, permanent location. They are, in essence, permanent institutional addresses in a digital space carved out specifically for this moment.

Now imagine that a researcher in the 2050s wants to understand what Brisbane 2032 was. They can navigate to the namespace. They can find addresses that were registered during the event’s active years, addresses whose ownership is verifiable and whose history is legible. They can see which institutions held which names, when they registered them, and what those names pointed to at various points in time. The blockchain record does not lie, does not selectively remember, and does not depend on someone having maintained a server for three decades.

That is an extraordinary thing to be able to offer. Most events leave behind nothing like it.

We also imagine a class of addresses that are less institutional and more commemorative — addresses that individuals or small organisations register as a form of permanent acknowledgment of their connection to the event. A community group that ran a volunteer programme. An arts collective that produced work in the cultural programme. A school that hosted visiting delegations. These are not high-profile institutional actors, but they were part of the fabric of what Brisbane 2032 was. Their claim to an address in this namespace is legitimate and, we think, meaningful. Permanent recognition is one thing that money cannot buy from traditional infrastructure, but on-chain addresses can provide.

The scarcity question

There is an asymmetry at work with .brisbane2032 that is worth naming directly.

Every other major TLD in this namespace — and in similar namespaces attached to other cities and events — operates under conditions of relative abundance. There is no meaningful limit to the number of .com addresses that can be registered. There is no point at which .org becomes full. The scarcity that drives value in traditional domain markets is more about specific desirable names than about the namespace itself.

.brisbane2032 is different. The namespace is permanent and the blockchain is open, but the meaningful names within this TLD are finite in a way that matters. There are a limited number of institutions, programmes, and entities whose connection to Brisbane 2032 is genuine and substantial. There are a limited number of names that will, in retrospect, look like obvious and necessary parts of the namespace. And once those names are taken, they are taken permanently.

This is not meant as a warning or a sales pitch. It is simply a structural observation about how time-specific namespaces work. The moment the Games are over, the character of this namespace changes. Addresses registered during the period of the event’s active life carry a different quality — a different claim — than addresses registered years later by people who had no direct connection to what happened. The timestamp matters. The provenance matters. In on-chain infrastructure, both of these things are verifiable forever.

We find that genuinely interesting. We have never encountered another digital structure in which the time of registration carries this kind of intrinsic meaning. The address itself becomes a form of proof — proof of engagement, proof of presence, proof of having been part of something at the moment it was happening.

The relationship between place and time

We want to explore something that sits at the heart of why .brisbane2032 is, for us, a different kind of namespace.

Place-based TLDs — .london, .paris, .sydney, .brisbane — carry the identity of their geography. They connect digital addresses to physical locations in a way that is intuitive and durable. A .brisbane address will mean Brisbane as long as Brisbane exists. The connection is spatial.

.brisbane2032 introduces a temporal dimension that most namespaces do not have. It connects addresses not just to a place but to a specific moment in that place’s history. This is unusual. It is, in some ways, unprecedented in the domain namespace world. Most TLDs are either purely geographic, purely generic (.com, .org, .net), or purely thematic (.sport, .health, .tech). Very few encode both location and time in a single string.

The ones that do — and Brisbane 2032 is a rare example — end up carrying a peculiar kind of archival weight. An address under this TLD is, by its nature, a claim about relationship to a specific historical moment in a specific place. That is a more complex claim than most digital addresses make. It is a claim with historical dimensions, institutional dimensions, and perhaps eventually legal and archival dimensions as well.

We think about this a lot, because it shapes who should hold addresses in this namespace and why. A generic squatter who registers nothing.brisbane2032 for speculative reasons is not making the same kind of claim as the volunteer coordination body for the Games, or the cultural legacy programme run out of South Bank, or the First Nations advisory council that helped shape how the event engaged with country. The namespace is open in a technical sense, but it is not ethically neutral. The names within it carry weight in proportion to the legitimacy of the claim they make.

That is a form of soft governance that traditional DNS cannot provide, because in traditional DNS, the historical record of why a name was registered is not preserved. On-chain infrastructure preserves it. Every registration carries a provenance. Every transfer carries a history. The record is complete and unalterable, which means that the legitimacy of claims made through this namespace can, in principle, be evaluated long after the fact.

Digital infrastructure as civic memory

Let us come at this from a different angle.

Cities have always struggled with the problem of civic memory. What do you do with the documentation of a city’s life? Physical archives exist — councils maintain records, libraries preserve newspapers, galleries hold artworks. But the digital layer of civic life has always been more fragile, more dispersed, and more dependent on institutional continuity than its physical counterpart.

The pandemic years accelerated a shift that was already underway: more and more of civic life moved online, and more and more of the documentation of civic life became digital-native. Events that once left behind paper trails now leave behind server logs. Decisions that once filled filing cabinets now exist in email threads and shared drives. The institutional memory of a city is increasingly stored in formats that are more brittle, not less, than the paper they replaced.

Major events like Brisbane 2032 are among the most intensively documented episodes in a city’s life. The Brisbane 2032 Olympic and Paralympic Games represent a global sporting spectacle and a catalyst for unprecedented infrastructure development, economic growth, and social impact across the state — and delivering an event of this magnitude requires meticulous planning, advanced digital capabilities, and a workforce equipped to handle complex challenges. Every aspect of the event is planned, documented, reported on, evaluated, and archived. The amount of institutional knowledge generated around a Games is extraordinary.

But that documentation is only as good as the infrastructure that houses it. If the addresses that point to that documentation expire, change hands, or simply disappear, the documentation itself becomes harder to find, less reliable, and more susceptible to loss. A permanent on-chain namespace is one way of ensuring that the address layer of this documentation is as durable as the documentation itself.

We think about the future Queensland State Library archivist trying to compile a comprehensive digital record of Brisbane 2032. We think about the future historian trying to trace the institutional history of how the Games were planned and delivered. We think about the future teacher trying to explain to students what this moment in Queensland’s history actually was. All of them will need stable, reliable, permanent addresses to navigate to. All of them will benefit from a namespace that was designed, from the beginning, with their needs in mind.

That is what we are trying to build with .brisbane2032. Not a product. A piece of civic infrastructure.

What we got right and what we are still learning

We want to be honest about what we know and what we do not.

We know that the technical infrastructure works. On-chain TLDs deliver genuine permanence in a way that traditional DNS cannot. Each top-level domain registered on-chain functions as a sovereign namespace — enabling the creation of second-level domains, decentralised websites, Web3 identities, wallet addresses, and smart contract integrations beneath it. TLD owners retain full control over their namespace, including the ability to issue second-level domains to third parties, build decentralised applications, and integrate their namespace into broader Web3 infrastructure. The structural properties of the technology are well-understood and have been tested across a growing ecosystem of on-chain namespaces globally.

What we are still learning is how institutions adopt these tools. Most of the organisations that should, in our view, hold addresses in .brisbane2032 are not, at this stage, particularly familiar with on-chain infrastructure. They are operating within traditional frameworks — government procurement processes, conventional IT infrastructure, familiar domain registrars. The idea that an address could be permanently owned rather than annually renewed is, for many of them, a genuinely new concept, and new concepts take time to become standard practice.

We are not impatient about this. The best infrastructure often gets adopted slowly and then all at once. The institutions that engage early will have the most meaningful names and the clearest provenance. The ones that come later will fill in the namespace around them. Both groups will have made a genuine decision to participate, and both will be part of the permanent record. The blockchain does not penalise late adopters — it just records the order of events truthfully, which is all we have ever asked of it.

The longer arc

Here is what we believe, at the most fundamental level, about what .brisbane2032 could become.

It could become the permanent digital home of Brisbane’s moment on the world stage — a namespace in which the key institutions, programmes, and actors of the 2032 Games hold stable, verifiable, permanent addresses that outlast every piece of traditional web infrastructure built around the event. It could become a model for how future cities hosting major events approach the question of digital legacy — demonstrating that a permanent on-chain namespace is not a novelty or a gimmick, but a genuinely better form of infrastructure for the specific problem of event-related digital continuity.

It could become a reference point in the history of how Queensland thought about the digital layer of its civic life — evidence that at least some people, at this particular moment, were thinking carefully about what it means to build digital infrastructure that is designed to last, rather than infrastructure that is designed to be convenient now and figured out later.

And, in the most speculative version of this vision, it could become something that future generations genuinely value in ways we cannot fully predict. We are building this in a period in which the importance of on-chain infrastructure is understood by a relatively small group of people. That group is growing. The ideas are spreading. The moment at which on-chain addresses are as familiar to institutions as .com addresses is probably not as far away as it would have seemed five years ago. When that moment arrives, the addresses registered early — the ones with clear provenance, legitimate institutional backing, and a permanent connection to a moment of genuine historical significance — will carry a different quality than the ones registered after the fact.

We do not know exactly what form that value will take. We are not making a financial prediction or a market forecast. We are making a simpler observation: that provenance matters, that permanence matters, and that Brisbane 2032 is the kind of moment that people will want to have been part of — not just in the physical and civic sense, but in the digital sense too.

The things we cannot know

There are things about what .brisbane2032 will become that we genuinely cannot know. We cannot know which institutions will be the first to understand the value of this infrastructure and register accordingly. We cannot know how the broader adoption of on-chain addresses will unfold over the coming years, or which platforms and systems will come to resolve these addresses in ways that make them useful to ordinary users in their daily digital lives. We cannot know how the Games themselves will unfold, what stories will emerge from them, which moments will be remembered and which will fade.

We cannot know whether the vision we have for this namespace — as institutional infrastructure, as civic memory, as permanent record — will be realised in the way we imagine, or whether it will be realised in ways we have not thought of, or whether the most important uses of .brisbane2032 will be things we have not yet conceived.

What we know is that we have done our part. We have secured the namespace. We have built it on infrastructure designed for permanence. We have made it available at a price — five dollars, paid once — that removes any serious economic barrier to participation. We have thought carefully about what the namespace means and who should hold addresses within it. We have tried to design the conditions under which something genuinely valuable can emerge.

The rest is up to the people and institutions whose connection to Brisbane 2032 is real, whose work will shape what this moment in Queensland’s history actually means, and who understand that the addresses they hold today are the foundations of the digital record they will leave behind.

A final thought

We come back, often, to the simplest version of what we are trying to do with all six of our TLDs, but especially with this one.

Brisbane is going to host the world. For a period of weeks, every eye on the planet will be pointed at this city, this region, these people. The athletes and officials and journalists and visitors will come and go. The ceremonies will open and close. The competitions will produce their results. And then the world will move on to the next thing, as it always does, and Brisbane will be left with what every host city is left with: the question of what all of this was for, and what it means to have been the place where it happened.

The physical answers to that question are being worked out by engineers and planners and governments right now. Stadiums are being designed for their post-Games lives. Transport networks are being built to serve communities for generations. A statewide legacy of sporting infrastructure is being delivered through new and upgraded venues with an explicit intention that they serve Queensland long after the competition flags come down.

We are trying to build the digital equivalent of that long-term thinking. An address that lasts. A namespace that holds. A piece of infrastructure that Brisbane’s institutions can plant a flag in, knowing it will still be there when their grandchildren’s grandchildren come looking for it.

That is what .brisbane2032 could become. That is what we are building toward. And we believe, with the particular kind of conviction that comes from having thought about something for a long time and finding that the more you examine it, the more it holds up — we believe this is worth doing.