We have been thinking about this question for a long time, and we have not found a clean answer. That is not a failure — it is, we think, the honest condition of anyone who holds a namespace that belongs, in some meaningful sense, to a real community of real people in a real place.

The question is this: when you own a top-level domain that carries the name of a city, a region, a place that millions of people call home — what exactly do you own? What do you owe? And what is the difference between that and a water utility, a power grid, a road?

We are going to try to work through it here. Not to arrive at a tidy conclusion, but because the working-through matters. If you hold a namespace and you have not asked yourself these questions, you are probably holding it wrong.

What a TLD Actually Is

A top-level domain is the suffix at the end of an address. It is the part after the last dot. In the traditional internet, top-level domains are administered by a single global body, which licenses them to registry operators, who sell registrations to registrants on an annual basis. The registrant never truly owns anything — they lease access to a record in a centralised database, and that lease expires unless renewed.

This is so normalised that most people never question it. You rent your address. Year after year. If you stop paying, or if the registry operator fails, or if the political winds shift and a regulatory body decides your address is inconvenient — your address goes away. The web has been built on this impermanence, and most of it has simply accepted the terms.

What we have built is structurally different. Unlike traditional DNS, onchain TLDs offer permanent, censorship-resistant ownership recorded on a public ledger. When someone registers an address beneath one of our TLDs — beneath .queensland or .brisbane or .gold-coast — ownership is controlled by the private key of the wallet that holds the token, so there are no annual renewals or registrar lock-ins, and records cannot be altered without the owner’s signature. The address is theirs, once, for life. No renewal. No expiry. No intermediary who can pull the rug out from under them.

That is the technical reality. But it does not answer the deeper question, which is about the nature of what we hold at the top level — the TLD itself. Not the second-level addresses, but the namespace as a whole. .queensland. .qld. .brisbane. .surfersparadise. .gold-coast. .brisbane2032. These six strings are not just products. They are names. And names carry weight.

What a Public Utility Is

A public utility is an organisation that maintains the infrastructure for a public service, often also providing a service using that infrastructure. Think water. Think electricity. Think roads, sewage, communications networks. Public utilities are meant to supply goods and services that are considered essential.

The core logic of a utility is not complicated. The concept is rooted in the recognition that certain services are so necessary for health, safety, and economic function that they cannot be left solely to the whims of an unregulated market. Because of this, a consequence of this monopoly is that federal, state, and local governments regulate public utilities to ensure that they provide a reasonable level of service at a fair price. And in some cases, the government agency limits how much the public utility can charge consumers, and may insist that even those who cannot afford to pay the market price are still supplied — this is called a universal service obligation.

The utility model rests on a few consistent pillars. First, essentialness — the service must be something people genuinely cannot do without. Second, monopoly — because typically a public utility has a monopoly on the service it provides; it is more economically efficient to have only one business provide the service because the infrastructure required to produce and deliver a product such as electricity or water is very expensive to build and maintain. Third, accountability — because when you hold a monopoly on something essential, you carry obligations to the public that purely commercial actors do not.

These industries share a common network structure, in that they have an extensive distribution system of lines, pipes, or routes requiring the use of public rights of way, often with strong physical linkages between component parts. That physical embeddedness is part of what makes a utility a utility. The infrastructure is buried under the streets, stretched across the sky, built into the fabric of the place it serves.

Now ask yourself: does a TLD fit this description?

Where a TLD Sits on the Spectrum

The answer is: partly. Uncomfortably. And it depends which TLD you are talking about.

A generic commercial TLD — let us say, a TLD that is just a product category or a brand name — is almost entirely a private product. There is no community whose identity is embedded in it. There is no place it represents. It is a commercial asset that happens to be structured as a namespace, and the operator owes its users good service and honest dealing, but not much more than that. The obligations are contractual, not civic.

A country-code TLD sits at the other end. ccTLDs are associated with specific countries or territories and are suitable for entities targeting a specific geographic audience, fostering trust and relevance within that region. The string itself — .au, .uk, .de — carries national identity. It is not just a product; it is a representation of a people and a place in the global namespace. The operator of a ccTLD is, in a real sense, a custodian of national digital identity. That comes with obligations that most commercial operators would not recognise.

Geographic TLDs — city names, regional names, place names — occupy a middle position that is genuinely unstable and genuinely interesting. The emergence of community top-level domains represents a distinct category within the broader framework of TLD governance. Unlike generic TLDs, which are often commercially driven, or country-code TLDs, which are geographically bound, community TLDs are proposed and operated on behalf of a clearly delineated group of people with a common interest, purpose, or affiliation.

We hold six of these geographic TLDs. And we sit, deliberately and consciously, somewhere between the purely commercial and the quasi-governmental. That position is not a compromise — it is a conviction.

Why the Name Changes Everything

There is a question worth sitting with here: why does it matter that our TLDs carry Queensland’s name?

The answer is that names are not neutral. When a namespace carries the name of a real place, it draws on the legitimacy, the identity, and the emotional investment that people already have in that place. Someone who registers a .brisbane address is not just choosing a technical string — they are making a statement about belonging, about local identity, about their relationship to a city. That name carries meaning that existed long before we came along, and it will carry meaning long after.

This is fundamentally different from a namespace that invented its own identity from scratch. We did not create the value of the word Queensland. That value was built over generations by the people who live there, who built things there, who call it home. What we did was secure that word as a permanent onchain namespace so that Queenslanders could own addresses beneath it, permanently, without asking anyone’s permission year after year.

That matters, because it means the value in our TLDs is not ours alone. We hold the string. We control the registry. But the meaning — the thing that makes someone want a .queensland address in the first place — belongs to Queensland.

These TLDs are designed not simply to offer a digital namespace, but to empower their communities through participatory governance, tailored policy frameworks, and mission-aligned operations. We believe that. We did not start this project to extract value from a community name. We started it because we believed Queenslanders deserved a permanent, owned, onchain home for their digital identity — and that the permanent, immutable nature of blockchain infrastructure was the right way to provide it.

The DNS System and Its Discontents

To understand why we think about these obligations the way we do, it helps to understand the system we are building alongside — and, in important ways, departing from.

The traditional domain name system is a hierarchy. At the top, a single body coordinates which strings exist as TLDs and under what conditions they operate. Below that, registry operators run the back-end databases. Below that, registrars sell registrations to the public. Participation in a global public resource is mediated by private law and market capacity, not by principles of equality, due process, or distributive fairness.

This has been the subject of serious debate for a long time. The legal character of the DNS root has long rested on the fiction that private contracts can adequately manage what is, in essence, a public global utility. The people who run the DNS know this. The people who study it know it. The tension has never been fully resolved, because the DNS sits at exactly the intersection we are discussing here — it is technically infrastructure, but it is owned and operated by a mixture of private and quasi-public entities, and the accountability mechanisms are imperfect.

What blockchain infrastructure does is sidestep part of that problem. When ownership is recorded on a public ledger, its ownership record is public, permanent, and verifiable on the blockchain — independent of any organisation, platform, or commercial intermediary. The immutability of the record means that no single actor — not us, not a government, not a regulator — can simply revoke what someone owns. That is a meaningful improvement on the current system, where annual renewal and centralised control mean that every domain name is, fundamentally, conditional.

But immutability does not resolve the question of stewardship. Permanence at the technical layer does not automatically translate into responsibility at the human layer. It just means the infrastructure is reliable. The question of what obligations the namespace operator carries — that is still a human question, and it demands a human answer.

The Monopoly Problem in Namespaces

Here is a structural fact about named TLDs that is worth stating plainly: there is only one .queensland. There is only one .brisbane. There is only one .gold-coast.

That is not a commercial accident. It is the nature of namespace. A top-level domain is, by definition, a unique string. Once it is held, no one else can hold the same string. There is no competitive market for .queensland, because .queensland can only exist once. Anyone who wants a .queensland address must come to us.

This is structurally identical to the monopoly condition that defines public utilities. The nature of these services often leads to monopolies, particularly due to the high costs associated with infrastructure development. In the case of a named geographic TLD, the monopoly is definitional — it is baked into the nature of namespaces. There cannot be two .brisbanes any more than there can be two Brisbane rivers.

We take this seriously. A monopoly on a community name is not a normal commercial position. It is a position that comes with obligations. If we chose to price addresses at a level that locked most Queenslanders out, we would be using a monopoly on their community’s identity to extract from them. If we chose to abandon the project, or to sell the TLDs to an operator with different values, we would be handing someone else control over a Queensland identity namespace without the community’s consent.

The price we charge — starting at five dollars, paid once, no renewals, no fees — is not a marketing decision. It is a statement about what kind of operator we are choosing to be. Access to a permanent onchain address beneath a Queensland TLD should not be a luxury. It should be something any Queenslander can afford. That is the closest thing to a universal service obligation that our model allows, and we mean it.

What We Are Not

Let us be clear about what we are not, because that matters too.

We are not a government body. We were not appointed by any level of government. We did not go through a public procurement process. We are a private team that secured these TLDs through the available infrastructure and built a project around them. That is the honest origin story, and we are not going to dress it up.

We are not a public utility in the formal, regulated sense. Public utilities are subject to forms of public control and regulation ranging from local community-based groups to statewide government monopolies. We are not subject to rate regulation by a public utilities commission. We do not have a legislative mandate. We cannot be compelled to provide service to anyone, and no government body oversees our pricing.

We are also not a purely commercial domain registry. We did not choose Queensland’s name because it would generate revenue. We chose it because we believed Queenslanders should own permanent onchain addresses beneath their own community’s name. The commercial structure — the $5 price, the one-time payment model — is in service of that belief, not the other way around.

These requirements were more stringent than those applied to standard applicants, reflecting the importance of legitimacy, representation, and accountability in community-based namespaces. We hold ourselves to that spirit, even without a formal governance mechanism requiring us to.

The Obligations That Come With a Community Name

So where does that leave us? If we are not a utility, not a government body, not a purely commercial registry — what are we, and what do we owe?

We have arrived at a way of thinking about this that feels honest to us.

We are custodians of a community namespace. Not owners in the full, unencumbered, do-whatever-we-like sense. Custodians. The distinction matters.

Ownership implies that you can extract maximum value from an asset, turn it into whatever serves you, sell it to the highest bidder, abandon it when it stops being profitable. Custodianship implies something different. It implies that the thing you hold has meaning beyond you — that it carries the identity, the investment, the pride of people who did not choose to entrust it to you, but whose community name is nonetheless part of what makes it valuable.

When you hold a community name as a namespace, you carry a set of obligations that we think about in terms of four principles.

Permanence. The addresses issued beneath our TLDs must be permanent. If we issue someone a .queensland address and they pay for it once, that address must remain theirs for as long as the blockchain infrastructure exists. We cannot introduce renewal fees. We cannot revoke addresses for commercial reasons. We cannot deprecate the namespace because our business model changes. The permanence of the address is a promise we make to every person who registers, and that promise has to be unconditional.

Accessibility. If the word Queensland belongs, in any meaningful sense, to all Queenslanders — and we believe it does — then the barrier to owning a .queensland address must be as low as we can make it. The five-dollar price is a floor, not a floor we intend to raise. The one-time structure means there is no compounding cost over time. The model is designed so that the permanence of the address is not offset by a compounding financial burden.

Integrity. We must not weaponise the namespace against the community it names. We must not use our control over the TLD to extract rent from people who have no alternative, to discriminate arbitrarily in who can register, or to operate the registry in a way that serves our interests at the direct expense of the community’s. This is not regulated. It is a choice. And it is the kind of choice that, in a public utility, would be mandated by law. We are making it because we think it is right.

Longevity. A namespace that represents a community has to be designed to outlast its founders. The blockchain infrastructure we have built on is permanent. The addresses are immutable. But the organisational and commercial structures around the TLD need to be equally durable. We think about this in terms of how we build, how we price, and how we document what we are doing. If this project passes to other hands, the people who come next need to understand what obligations come with it.

The Tension Between Stewardship and Commerce

It would be dishonest not to acknowledge the tension here. We are not a charity. We are not a government department. We need the project to be commercially viable, because a commercially unviable project does not serve anyone — it just closes.

The tension between stewardship and commerce is not unique to us. Public utilities can be publicly or privately owned, with publicly owned utilities typically focusing on community service without profit motives, while private utilities operate for profit. The history of utilities is largely the history of trying to manage this tension — how do you keep essential infrastructure accessible and fair when the entity running it also needs to cover its costs?

Traditional utilities resolve this through regulation. A regulator sets the rates, approves the investment plans, and ensures the monopoly does not become predatory. We do not have that. What we have instead is structural design — a pricing model that is deliberately low, a permanence model that prevents us from creating compounding revenue through renewals, and a public commitment to the principles above.

We think this is a reasonable substitute for formal regulation in a context where formal regulation does not yet exist for onchain namespaces. But we are not naïve about its limits. Structural design only works as long as the people running the structure remain committed to the principles behind it. That is a human constraint, not a technical one.

The blockchain layer solves the ownership problem beautifully. Once you own your address, it is yours. No one can take it. But it does not solve the governance problem at the TLD level. The TLD itself is still controlled by whoever holds the registry operator keys. The trustworthiness of the namespace depends, in the end, on the trustworthiness of the operator.

We think about this openly, and we think other namespace operators should too.

Place Identity as Digital Infrastructure

There is a larger argument here about what geographic namespaces are for, and we want to make it explicitly.

Digital identity is increasingly where human life happens. Work, communication, commerce, civic participation — these have all migrated, at least partly, into digital space. And the addresses people use in digital space are not just technical strings. They are identifiers. They signal affiliation, belonging, community.

For most of internet history, Queenslanders who wanted a digital address had three choices: a generic namespace that said nothing about where they came from (.com, .net, .org), a national namespace that said something about the country but nothing about the region (.com.au), or a custom business domain that was personal but not communal. There was no permanent, owned, onchain address that said specifically: this is Queensland. This is Brisbane. This is the Gold Coast.

We think that absence was a gap. Not a catastrophic one — people managed. But a gap nonetheless. GeoTLDs enable a significant improvement in the communication and findability of services through internet addresses which are brief and descriptive. More than that, they provide a commons — a shared namespace where community identity can take root.

A community that has no persistent digital address infrastructure is a community that is, in a real sense, absent from the layer of the internet where identity is constructed. It may have websites. It may have social media presence. But it does not have a permanent, immutable, owned piece of the address layer — the deepest, most foundational layer of how the internet organises itself.

That is what we are trying to provide. Not just a product. An infrastructure. A digital home for Queensland that works the way a home should work: you own it, it stays yours, no one can take it away.

The Question of Legitimacy

We want to address something that might be in the back of your mind. Did anyone ask us to do this? Did Queensland, as a community, choose us?

No. They did not. There was no referendum, no public consultation, no democratic mandate. We identified an opportunity — the emergence of permanent onchain TLD infrastructure — and we moved to secure Queensland’s names within it. The alternative was to leave those names unsecured, which would have meant they might be held by someone with no connection to Queensland at all, or no commitment to accessible pricing, or no interest in permanence.

Applicants seeking to operate a community TLD were required to demonstrate that the proposed string was strongly associated with a clearly defined community, that the community supported the application, and that the policies and registration eligibility criteria would restrict use of the TLD to members of that community. We hold ourselves to the spirit of that standard even though the onchain context does not require it procedurally.

The legitimacy question is real, and we do not dismiss it. What we say is this: legitimacy is not only conferred by mandate. It can also be earned, over time, through conduct. The way we price, the way we operate, the permanence we offer, the principles we hold ourselves to — these are the instruments through which we intend to earn legitimacy as custodians of Queensland’s digital namespace.

We are also realistic about what that requires. It requires consistency. It requires that the principles we articulate here are reflected in every decision we make about how the TLDs operate. It requires that we resist the commercial temptations that come with holding a monopoly on a community name. And it requires that we remain open about what we are doing and why — not to perform transparency, but because communities have a right to understand who holds their name and on what terms.

What Permanence Means for Obligation

The onchain nature of what we have built adds a layer to the obligation question that is worth thinking about carefully.

In the traditional domain system, the temporary nature of registrations means that the worst outcome of operator failure is predictable: your domain expires. You lose continuity. That is bad, but it is recoverable. You re-register somewhere else.

The permanent model creates a different relationship. When someone pays once for a .queensland address and that address is meant to be theirs forever, the stakes of operator failure are different. Permanence is the promise. If we fail to honour it — not through technical failure, because the blockchain handles that, but through organisational failure or a change in direction — we break a commitment of a different magnitude than the annual renewal model ever makes.

The TLD registered on the blockchain is a permanent blockchain-recorded asset — structurally distinct from conventional domain names, which are leased from registries on an annual basis. That structural distinction is what makes our model powerful for the registrant. And it is also what makes the obligations at the registry level more serious, not less.

We have thought about this in terms of what we are asking people to trust. In the renewal model, your trust is annual. You check in each year, you evaluate whether the registry is still worth using, you renew or you do not. In the permanent model, you trust once. That trust is forward-looking in a way that annual trust is not. It assumes we will still be here, still operating on the same terms, still holding to the same principles, indefinitely.

That is a profound ask. It is the kind of ask that public utilities make, in their way. The water company does not ask you to decide each year whether you want running water. The infrastructure is assumed to be permanent. Your trust in it is structural, not transactional.

We have accepted that weight knowingly. The permanence of the model is also a permanence of the obligation.

Toward a New Category

We suspect we are not the only people thinking about this. As onchain namespaces mature, as more community names and geographic identifiers become available as permanent registrations, more operators will face the question we are wrestling with here. And the existing categories — public utility, private product — will not be sufficient to describe what they are.

We would propose a new category, even if it is informal: the community namespace custodian. An entity that holds a namespace that represents a real community, operates it on terms designed to serve rather than extract, and holds itself to obligations that go beyond contractual minimums, without being regulated by any government body.

This is not a formal legal category. It is a posture. A way of understanding what you hold and what that means for how you hold it. A defining feature of community TLD governance is the inclusion of representative governance structures that give stakeholders meaningful oversight and input into policy development and operational decisions. We believe in the spirit of that, even where the formal structures are not yet built.

The obligations of a community namespace custodian are not enforced by regulation. They are enforced by the community’s willingness to trust, and by the custodian’s own sense of what is right. That is a thinner protection than a public utilities commission. We acknowledge that. But it is the protection available in this space, right now, and we think it is better than nothing — and better than pretending the obligations do not exist.

A Final Thought

There is something we find meaningful about the fact that the addresses beneath our TLDs are immutable. Once someone owns a .queensland address, it is theirs. It lives on the blockchain. It does not require our continued good conduct to remain theirs. The permanence belongs to them, not to us.

We find that meaningful not as a technical fact but as a philosophical one. It means that the power relationship between registry operator and registrant has shifted. In the traditional model, the operator holds the key to your address’s continued existence. In the onchain model, you hold the key. Literally. The private key in your wallet is the instrument of your ownership.

What we retain is the stewardship of the namespace as a whole. The curation of the TLD, the maintenance of its integrity, the commitment to keeping the second-level space accessible and honest. That is what we hold. And it is precisely the part that carries obligations — not to us, but to the community whose name we are custodians of.

That is, in the end, what distinguishes a TLD with a community name from a purely commercial product. The product can be sold, abandoned, repriced, rebranded. The community name cannot. The community was there before us, and it will be there after us, and the name carries the whole weight of that continuity.

We are just the people who made sure Queenslanders could own it, permanently, for five dollars, once, for life.

We think that is worth something. And we think it comes with obligations we intend to keep.