There is a moment, early in any serious project, when you have to decide what kind of thing you are building. Not the technical kind — that question has a thousand adequate answers. The harder question is the one underneath it: what is this for? Who does it serve? What does it owe the people who depend on it? And what happens to those people if it fails, or if the people running it change their minds?

We asked ourselves those questions when we set out to secure permanent onchain TLDs for Queensland. The answers we arrived at — the ones that have shaped every decision since — all trace back to a single framing that we keep returning to: the namespace is civic infrastructure.

That phrase carries weight. It is not a marketing claim. It is a commitment, and one that costs something to honour. To understand why we think about it this way, and why that framing matters, it helps to start by understanding what infrastructure actually is, and why the civic version of it demands more than the ordinary kind.

What infrastructure actually means

When people talk about infrastructure, they usually mean physical things: roads, water pipes, electrical grids, sewage systems, rail lines. These systems share a set of defining characteristics that matter enormously.

First, they are foundational. They do not sit on top of society — they sit underneath it. Everything else depends on them. Commerce, communication, healthcare, education, the ordinary routines of daily life: all of it rests on the assumption that infrastructure will work. When it does work, no one thinks about it. When it fails, everything fails with it.

Second, they are not optional for the people who need them. A road is not a luxury. A water supply is not a preference. Once a community has been built around a piece of infrastructure, the people in that community are dependent on it whether they chose to be or not. This dependency is part of what makes the word meaningful, and part of what makes the obligations of those who build and run infrastructure so serious.

Third, they are designed to last. Not to last until the business model changes. Not to last until a better offer comes along. To last in the way that a bridge lasts — with the expectation that it will still be there for the people who come after us.

And fourth — this is the part that gets overlooked — infrastructure exists to serve. Not the people who built it. Not the shareholders of the company that owns it. The community it connects. That is the whole point.

Civic infrastructure adds another dimension to all of this. It is infrastructure that is specifically oriented toward collective life, toward the spaces and systems that allow a society to know itself and act as a society. Libraries. Public squares. The postal address system. The shared conventions that allow strangers to find each other, communicate, and participate in public life. Civic infrastructure is what makes a collection of individuals into a community. It is the connective tissue of place.

Why a namespace fits this description

A namespace — the structured system of names and addresses that allows people and organisations to identify themselves and be found — is infrastructure in every sense of the word.

Think about what it means, in practice, to have an address. A street address is not just a technical convenience. It is a claim to existence in public space. It is how an institution signals that it is real, that it is present, that it can be found and held accountable. It is how a person says: I am here, and you can reach me here. The address system — the whole apparatus of streets and numbering and postcodes — is infrastructure. Nobody owns it in the way they own a product. It belongs, in some fundamental sense, to the community it serves.

A digital address works the same way. When a business registers a domain, when a community organisation puts its name on the internet, when a local government creates an online presence — they are claiming a position in public digital space. They are saying: we exist, we are here, and this is how you find us. That act of claiming space is civic. It is a participation in public life, conducted through the medium of a name.

This is why a namespace that serves a specific community — a place, a people, a set of shared identities — is not just a technical layer. It is a piece of the fabric of that community’s public life. And that means it carries civic obligations.

The problem with treating namespaces as products

Most namespaces, for most of the internet’s history, have been treated as products. You lease a name. You pay annually. The registry collects the fees. If you stop paying, you lose the name. The registry can change its pricing. The registry can be acquired. The registry can decide, for business reasons, to sunset certain extensions or change the terms under which names are held. You, the holder of the name, are a customer. Customers can be managed, repriced, and churned.

This model works, in a narrow commercial sense. Registries can be profitable businesses. Names get registered. The internet functions.

But the product model has a problem: it is fundamentally misaligned with the actual role that names play in people’s lives and in community life. Because names, once they become associated with institutions, businesses, and civic presences, accumulate value and dependency that goes far beyond the name itself. A local council’s address is printed on letterheads, embedded in legislation, memorised by residents. A small business’s domain is on their signage, their invoices, their customers’ address books. A community organisation’s name is part of its identity in the deepest sense. These are not interchangeable assets. They are not things you can simply swap out if the pricing changes or the registry gets acquired.

When a name becomes load-bearing — when people and organisations depend on it in the way they depend on a postal address — treating it like a product creates fragility. The holder of the name is perpetually subject to the decisions of a third party who has no particular obligation to the community the name serves. The registry might raise prices. It might be sold to an acquirer with different priorities. It might simply shut down. And the name — and everything that depended on it — becomes precarious.

The history of the traditional domain name system is full of exactly these moments. Prices have been raised after acquisition. Registries have been sold to parties whose interests diverged from the communities that had built their digital lives inside those extensions. Extensions have been launched, gained communities, and then been deprioritised. None of this was necessarily malicious. It was just the product model doing what the product model does: optimising for the benefit of the owner, not the people served.

When we look at this history and ask what we owe to the communities who will build their digital identities within the Queensland namespace, we find that the product model is simply not adequate. The stakes are too high. The dependencies are too deep. The community deserves better.

What the civic infrastructure framing demands

When we made the decision to think of the Queensland namespace as civic infrastructure, it immediately changed the texture of every decision we faced. Infrastructure framing is not rhetorical — it has practical teeth, and those teeth bite.

Permanence becomes non-negotiable.

Infrastructure is not temporary. A bridge built with a thirty-year lifespan, after which the community must renegotiate access, is not really infrastructure. It is a lease dressed up as infrastructure. The defining promise of infrastructure — the thing that makes it possible to build community life around it — is that it will be there. Not probably. Not as long as the business model holds. There.

This is why we designed the Queensland namespace around permanent ownership from the beginning. A name registered here is owned, not leased. There are no renewal fees, no annual renegotiations, no moment at which the holder’s claim to their address is put back in question. The blockchain architecture is not a feature — it is an expression of a commitment. The permanence is structural. It cannot be undone by a business decision, an acquisition, or a change of management, because it does not depend on our continued goodwill. It is written into the protocol.

This is what civic infrastructure demands. Not a promise of permanence, but permanence itself — built into the system so that the community does not have to trust us, year after year, to honour the promise.

Accessibility becomes a founding principle.

Infrastructure that only some members of the community can access is not civic infrastructure. A road that only wealthy people can use is not a public road. A namespace that only organisations with significant resources can participate in is not serving the community — it is serving the part of the community that already has power.

This is why we set the price of a Queensland name at five dollars, paid once. Not because we could not charge more. Because the framing demands it. If the namespace is infrastructure, then barriers to entry are barriers to participation in public digital life. They are exclusions. And an infrastructure that systematically excludes people based on their ability to pay is not doing the thing that makes infrastructure worth building in the first place.

Five dollars is not free. We thought carefully about that. There is something important about a minimal act of claiming — about the holder having made a positive choice, an investment however small, in their digital presence. But five dollars is a threshold that almost anyone can cross. A small business in regional Queensland. A community sporting club. A neighbourhood association. A school group. A young person just starting out. The price is set at the level where it is not a filter, just a door handle.

Accountability shifts from market to community.

When you build a product, you are accountable to your customers through the mechanism of the market. If your customers are unhappy, they go elsewhere. If they leave, the product fails. The accountability relationship is mediated by the transaction.

Infrastructure does not work that way. Once a community is built around a piece of infrastructure, they cannot simply go elsewhere. The switching costs are too high. The dependencies are too deep. The accountability relationship must therefore be different — not market accountability, but something more like stewardship. The infrastructure builder is not accountable to a market of customers. They are accountable to the community the infrastructure serves.

This means we think about our role differently than we would if we were building a product. We are not trying to maximise the number of names sold, or to optimise the revenue per user, or to grow our way to an exit. We are trying to build something that Queensland can depend on — a layer of its digital life that is durable, accessible, and governed in the interest of the community it represents.

That is a different set of objectives, and it requires a different set of decisions.

The geography of it matters enormously

There is a reason the Queensland namespace is specifically Queensland’s, and that specificity is not incidental. It is central to why the civic infrastructure framing applies.

Generic namespaces — the .coms and .nets and .orgs of the world — serve no particular community. They are placeless. Their holders have no special relationship to the geographic, cultural, or civic life of any place. The namespace is simply a technical layer, useful for anyone, meaningful to no one in particular.

A Queensland namespace is different. The extensions — .queensland, .qld, .brisbane, .surfersparadise, .gold-coast, .brisbane2032 — carry place in them. They are not just addresses. They are affiliations. When someone registers a .brisbane name, they are making a statement about their relationship to a city, a community, a place on the earth. When a Gold Coast business registers a .gold-coast name, they are locating themselves in a specific cultural geography that has meaning to the people who live and work there.

This geographic specificity is what makes the civic dimension of the namespace real. Civic life is always local in some sense — it is the life of people who share a place, who have common interests in the places they inhabit, who are bound together by proximity and history and the overlapping of their daily lives. A namespace that reflects that geography becomes part of the civic fabric of the place. It is not just a technical address system. It is a way for the community to represent itself to itself and to the world.

Queensland has an identity. Brisbane has an identity. Surfers Paradise has an identity. These are not abstract categories — they are lived realities, cultures, places that Queenslanders are proud of and attached to. The namespace is a way for that identity to be expressed in digital space, by the people who actually belong to it.

That is a civic act. And it demands civic stewardship.

On the question of permanence and what it really means

We want to dwell on permanence a little longer, because we think it is more important and more interesting than it might initially appear.

Permanence is not just about convenience. It is about trust at scale, and about the relationship between individuals and institutions over time.

Think about what it means to have a street address that you know will still be your address in fifty years. Not probably. Not unless you move or sell. Your address. The number on the building, the street, the suburb — those things have a kind of stability that allows commerce, community, and civic life to function at a level of depth that would be impossible without it. Businesses build reputations at addresses. People develop relationships with places. Institutions accrue legitimacy through their long presence in specific locations. None of this would be possible if addresses were leased on annual terms and subject to the ongoing goodwill of whoever happened to own the address registry that year.

The same logic applies to digital addresses, but with a complication that makes permanence even more important in the digital case: the cost of entry into the traditional domain system has been low enough that many organisations have accumulated large numbers of names, and the renewal overhead of managing them has made dropping names a routine occurrence. Names get lost. Institutions dissolve. The addresses that pointed to them go dark, or worse, get acquired by squatters and pointed at something else entirely. The digital namespace is haunted by the former presences of things that once existed there.

Onchain permanence solves this at the root. A name that is permanently owned does not expire. The organisation that held it may dissolve, but the name is a held asset with a clear chain of title, not a leased entry in a third-party database. The holder can transfer it, sell it, or leave it in perpetuity to a successor. What they cannot do is simply let it lapse into ambiguity through non-renewal.

This matters enormously for institutions. A council that holds its .queensland name permanently can build digital infrastructure around it with full confidence that the foundation will not shift. A business that builds its brand on a .gold-coast name is not renegotiating its claim to that identity every year. A community organisation whose entire digital identity is wrapped up in a .brisbane name knows that identity is theirs — not contingent, not provisional, theirs.

Infrastructure should feel like that. Solid. Assumed. Present in the way that the ground under your feet is present. The moment you start thinking of your address as something you hold on sufferance from a third party, you have introduced a fragility into the foundation that will limit everything you try to build on it.

The long arc of civic naming

It is worth stepping back and thinking about naming as a civic practice, because it has a long history that illuminates what we are doing and why it matters.

Naming places is one of the oldest and most fundamental civic acts. When a community names a street, a suburb, a river, or a mountain, it is doing several things at once. It is asserting a relationship to that place. It is creating a shared reference that allows members of the community to communicate about where they are and where they are going. It is inscribing the community’s values, history, and identity into the geography it inhabits. Place names are not neutral technical labels — they are acts of collective self-expression.

The digital namespace is an extension of this practice into a new medium. When we give Queensland its own extensions — when .brisbane becomes a real and permanent thing in the digital world — we are doing something analogous to the act of naming a street or a suburb. We are creating reference points that allow Queenslanders to locate themselves in digital space, to say this is where we are in a way that carries the weight of their actual place.

This is why we take the naming of the extensions themselves seriously. .queensland and .qld are not interchangeable with .com.au. They carry different meaning. They assert Queensland’s presence not as a commercial entity seeking a domain slot, but as a place with its own identity, its own community, its own claim to digital space. .brisbane2032 carries a specific temporal meaning — an association with a moment of global attention and community pride that belongs to Brisbane and to Queensland. These names are not just utilities. They are statements.

The civic framing insists that we handle this naming responsibility with care. We do not treat the extensions as arbitrary technical strings that happen to have a Queensland flavour. We treat them as words that belong to a community, that represent that community, and that carry obligations toward that community as a result.

Stewardship versus ownership

There is a distinction that sits at the heart of how we think about our own role, and it is worth making explicit.

We are not the owners of the Queensland namespace in the sense that a product company owns its product. We are the stewards of it. Those two words — owner and steward — imply very different relationships to what you hold.

An owner holds something for their own benefit. Their primary obligation runs to themselves, or to their shareholders. Decisions about what to do with the owned thing are made by asking what maximises value for the owner.

A steward holds something on behalf of others. Their primary obligation runs to the community the held thing serves. Decisions about what to do with the stewarded thing are made by asking what best serves the community.

The distinction is not semantic. It is the difference between a registry that raises prices when it can because it is profit-maximising and a namespace that keeps prices at five dollars because the community it serves deserves accessible participation in its own digital space. It is the difference between a registry that can be sold to a buyer with different priorities and a namespace whose permanence is structural rather than dependent on the goodwill of current management. It is the difference between treating the people who hold names as customers and treating them as community members with rights.

We hold the Queensland TLDs. We secured them. We will maintain the infrastructure. But the namespace belongs to Queensland, and every decision we make about it has to be answerable to that fact.

This is what civic infrastructure demands of those who build and run it. Not just technical competence. Not just commercial sustainability. Accountability to community. A sense that what you hold is not yours to do with as you please, but yours in trust, for as long as it takes to hand it on in better condition than you received it.

What the onchain architecture makes possible

We want to be clear about why the blockchain infrastructure is not incidental here — why it is actually essential to the civic framing, and not just a technical preference.

The permanence we are committed to would be very difficult to guarantee under a traditional registry model. In a traditional model, the permanence of a name depends, ultimately, on the ongoing commitment of a company. Companies can be acquired. Companies can change their strategies. Companies can fail. And even a company with the best intentions in the world cannot bind its successors to its commitments in any technically enforceable way.

An onchain architecture changes this. The records are not stored in a corporate database that can be modified or deleted by a business decision. They are written into a public ledger, where ownership is verifiable by anyone and controlled by no one except the holder. The commitment to permanence is not a policy — it is a structural fact. The holder’s ownership of their name is not contingent on our continued operation. It is their asset, encoded in the protocol.

This matters enormously for civic infrastructure. Infrastructure is only as trustworthy as the mechanisms that guarantee its permanence. A road that depends on a single landowner’s goodwill is not infrastructure. A water supply that can be turned off by a private decision is not infrastructure. The onchain architecture for the Queensland namespace is the technical realisation of a civic commitment: the names belong to their holders, permanently, without qualification.

There is also a deeper alignment between the onchain model and the civic framing. Blockchain infrastructure is, in its best expressions, a form of public infrastructure — not owned by any single party, not controlled by any single authority, maintained by distributed participation. When we build the Queensland namespace on this foundation, we are building on infrastructure that itself has civic characteristics. The ownership chain is transparent. The rules are public. The records are immutable. Trust is not required of any single party, because the system itself provides the verifiable ground.

The obligations that follow

If we accept the civic infrastructure framing — and we do — then certain obligations follow that we take seriously and want to be explicit about.

We have an obligation to accessibility. This means keeping the cost of entry low, permanently. Not just at launch, while we are trying to attract adoption. Permanently. If the namespace is infrastructure, then pricing it out of reach of ordinary community members is a failure of stewardship, not a legitimate business decision.

We have an obligation to the names already held. Once someone has registered a name, that name is theirs. Not subject to review. Not contingent on ongoing payment. Not available to be reassigned because we decide their use case is no longer aligned with our strategy. The permanence we promise is not conditional.

We have an obligation to the integrity of the namespace. We hold six TLDs that carry Queensland’s identity. We have an obligation not to use that positioning irresponsibly — not to register names in bad faith, not to manipulate the namespace in ways that would benefit us at the expense of the community, not to allow the extensions to be degraded through practices that would undermine the trust and meaning they carry.

We have an obligation to longevity. We are building for generations, not quarters. The decisions we make now will shape the digital landscape of Queensland for as long as the onchain infrastructure persists — which is to say, indefinitely. That is a weight we feel, and one that disciplines our thinking about what we are doing and why.

We have an obligation to transparency. Communities can only hold stewards accountable if they know what the stewards are doing. We believe in being clear about our reasoning, our commitments, and our constraints. The people who build their digital lives inside the Queensland namespace deserve to understand the basis on which it is run.

Why this matters now

There is a window of time, in the development of any new kind of infrastructure, during which the foundational choices are being made. After that window closes, the choices calcify. The architecture is set. The norms are established. The communities that have built their lives around the infrastructure make it increasingly difficult to change the fundamental terms of how it works.

We are in that window, for Queensland’s digital namespace. The choices being made now — about permanence, about pricing, about accountability, about the relationship between the namespace and the community it serves — will shape the digital landscape of Queensland for decades. The habits of thought that get established now, the precedents that get set, the norms that get built into the way people think about Queensland’s digital addresses — all of this will echo forward.

This is why the civic infrastructure framing is not just a philosophical nicety. It is a practical guide for decision-making in a formative moment. Every time we face a choice about how to build or run the namespace, we can ask: what would a piece of civic infrastructure do here? And the answer to that question disciplines us in ways that the product framing never would.

A product would optimise for revenue. Infrastructure optimises for durability and service.

A product would treat its users as customers. Infrastructure treats them as community members.

A product would evolve its pricing to reflect what the market will bear. Infrastructure keeps the door open because the community needs it open.

A product would be owned by its builders. Infrastructure is stewarded for the community it serves.

These are not abstract principles. They are the practical content of what we believe, and of what we are trying to build. Queensland deserves a digital namespace that functions the way good infrastructure functions — present, reliable, accessible, and permanently oriented toward the people it exists to serve.

A word about what we are not claiming

We want to be honest about the limits of our framing, because intellectual honesty is part of what civic stewardship demands.

We are not claiming to be a government agency, or to carry formal public authority over the Queensland digital namespace. We are a project that secured these TLDs and that is committed to stewarding them in the interest of the community. The legitimacy of that stewardship comes from the quality of our commitments and our faithfulness to them, not from any official mandate.

We are not claiming that the civic infrastructure framing resolves every tension or answers every question. There are hard decisions in running a namespace — about abuse, about disputed names, about the relationship between different kinds of holders — and the framing guides us without eliminating the difficulty.

And we are not claiming that the civic framing is unique to us, or that we invented it. Every serious piece of public digital infrastructure is grappling with versions of these questions. What we are doing is applying those questions, deliberately and explicitly, to a specific place and a specific community — Queensland — and letting the answers shape how we build.

In the end, it is about belonging

We come back, often, to a simple image: a Queenslander opening a laptop, registering a name that carries their city in it, and knowing that name is theirs — permanently, unconditionally, with no one who can take it from them and no ongoing fee that puts it at risk. A small business in Townsville. A surf school on the Gold Coast. A community garden in inner-city Brisbane. A young artist from a regional town who wants a digital address that says, unambiguously, where they are from.

That act of claiming a name in your own community’s namespace is a civic act. It is a participation in the shared digital life of a place. It is a way of saying: I am here, I belong here, and this is where you find me.

Infrastructure is what makes belonging possible at scale. Roads make belonging to a city possible by connecting its parts. Libraries make belonging to a community possible by providing shared access to knowledge. The postal address system makes belonging to a neighbourhood possible by giving everyone in it a recognisable place.

The Queensland namespace, built and stewarded as civic infrastructure, can do the same thing in digital space. It can give Queenslanders a layer of the internet that is genuinely theirs — not leased from a global corporation, not priced out of reach of ordinary people, not subject to the decisions of a distant acquirer with no stake in Queensland’s future. Theirs. Permanently. With all the rootedness that that word implies.

That is what we are building. And it is why we think about the namespace as civic infrastructure — not as a metaphor, but as a commitment, and one that we intend to keep.