There’s a version of this project that doesn’t exist, and we think about it often.

In that version, we got greedy. We looked at the map of Queensland — a state so vast it is larger than all but sixteen countries on earth — and we saw not six opportunities but sixty. We registered .sunshine-coast and .cairns and .townsville and .toowoomba and .rockhampton and .mackay and .noosa and .coolangatta and .broadbeach and .burleigh and on and on, one coastal suburb after another, one regional city after another, until we had assembled something that looked less like a curated namespace and more like a land grab. That version of this project would have moved faster. It would have looked bigger. It probably would have been easier to pitch to a certain kind of investor.

It also would have been wrong.

We want to explain why we stopped at six — not because we ran out of ideas, but because six is exactly the right number. To do that, we need to talk about what a namespace actually is, what happens when one sprawls, and what we believe the TLDs we secured actually represent. This is not a technical post. It is a post about judgment, about curation, about the responsibility that comes with putting a place name on a blockchain and calling it permanent.

What a namespace is, and what it isn’t

Most people think of a namespace the way they think of a filing cabinet. You have drawers, and inside the drawers you have folders, and inside the folders you have documents, and the whole point is to hold as much as possible in an organised way. More drawers means more capacity. More capacity means more value. This is the logic that leads projects in our space to register hundreds of TLDs, or to create frameworks where anyone can register a new TLD for a fee, flooding the ecosystem with extensions that nobody asked for and nobody uses.

That is not what a namespace is. Or rather, that is the least interesting thing a namespace can be.

A namespace is, at its core, a claim about what matters. When you decide that something deserves its own top-level domain, you are saying: this thing is real, it has weight, it is worth being the rightmost word in an address. You are saying that the identity expressed by this string is substantial enough to anchor everything that comes before it. A TLD is not a folder. A TLD is a flag. And flags mean something only when there are not too many of them.

In the traditional web, ICANN has spent decades grappling with this exact problem. The expansion of the generic TLD namespace opened the door to hundreds of new extensions — .shop, .online, .website, .store, .site — and the result has been widespread confusion, low recognition, and a general sense that the new extensions lack the weight of the old ones. Users default to .com not because it is technically superior but because it is legible. Everyone knows what .com is. Most people cannot name three of the new gTLDs released in the last decade, let alone remember which ones are active.

The lesson from that experience is not a complicated one: when you add a TLD to a namespace, you are borrowing from the attention and recognition that every other TLD in that namespace has built. Each new addition dilutes the whole. This is not a zero-sum game in the narrow sense — one TLD does not literally steal recognition from another — but it is true in the aggregate. A namespace with five hundred equally weighted members gives each member one five-hundredth of the available attention. A namespace with six members, each chosen carefully, gives each member something much more valuable: the possibility of being remembered.

We chose six. We want to tell you what that felt like, and what it cost us.

The list we didn’t keep

The working list was long. We are not going to reproduce it here because some of those names are still available on-chain and we have no interest in triggering a secondary rush. But we want to be honest about the scope of what we considered and walked away from, because the walking away is the point.

Queensland’s coastline alone could have generated dozens of defensible TLDs. Noosa is a place of genuine identity — it has a distinct culture, a fiercely protective community, a character that sets it apart even from other parts of the Sunshine Coast. Broadbeach sits just south of Surfers Paradise and has developed its own personality as a dining and entertainment precinct within the Gold Coast. Burleigh Heads has arguably the most passionate local identity on the entire Gold Coast, a surf community that has resisted high-rise development with a tenacity that most coastal towns have not managed. Palm Beach, Coolangatta, Currumbin — each of these has a case.

Further up the coast, Cairns anchors the entire tropical north. It is the gateway to the Great Barrier Reef and Cape York. It has its own economy, its own tourism identity, its own reason to exist as a digital address. Townsville is the largest city in regional Queensland and has long chafed against being treated as an afterthought to the south-east corner. Toowoomba sits in the ranges above Brisbane with a civic pride that punches well above its size. Mackay. Rockhampton. The Whitsundays. Magnetic Island.

We thought about all of them. We had conversations about all of them. In some cases we sketched out what a community of addresses under those TLDs might look like.

And then we stopped. Not because the places are unworthy. They are not unworthy. Every single one of those communities deserves recognition and we mean that without condescension. We stopped because we recognised that the act of registration is not the same as the act of stewardship. Registering a TLD and building a meaningful namespace around it are two entirely different things. The first takes an afternoon. The second takes years of sustained attention, community trust, and genuine investment.

We could register .cairns. We could not — with honesty — promise .cairns the same depth of commitment we are giving to the six TLDs we did secure. To register a name and then neglect it is not neutrality. It is a particular kind of disrespect. It is planting a flag in someone else’s yard and then never coming back.

Why these six

So if we were going to stop at six, why these six? The answer is not random, but it is also not purely technical. It is a mixture of signal strength, cultural layering, and something harder to define — a sense of which names have earned the right to be permanent.

.queensland is the state itself. It is, in a sense, the root from which everything else in this namespace derives its meaning. Queensland is one of the most geographically distinctive and culturally specific states in Australia — a place with its own accent, its own political history, its own relationship to the heat and the coast and the tropics. It is larger than most countries and more diverse than most people who have never been there realise. The full name has weight. It is not an abbreviation. It does not need to be decoded. If you see something.queensland, you know exactly where it is from.

.qld is the state in the form that Queenslanders themselves use. The abbreviation QLD is not an external imposition — it is how residents write the state’s name on envelopes, in text messages, on the back of jerseys. It is the intimate, shorthand version of Queensland identity, the one that belongs to insiders. There is a meaningful distinction between the full name and the abbreviation, and we wanted to hold both. Not to prevent the other from being used — we hold both because together they form a complete picture of how this identity is expressed at different registers of formality. A business might want something.queensland for its full geographic authority. A person might prefer something.qld because that is just how they talk.

.brisbane is the state capital and, by any reasonable measure, one of the most dynamic cities in the southern hemisphere right now. It is the anchor of the fastest-growing region in Australia, a city that has spent decades throwing off its reputation as a big country town and has emerged as something genuinely metropolitan — with an arts precinct, a river that defines the city’s form, a skyline that changes faster than almost anywhere in the country. Brisbane has always been self-aware about its position in the Australian imagination, caught between Sydney’s financial gravity and Melbourne’s cultural prestige and finding its own identity in the gap between them. That identity deserves its own permanent address.

.gold-coast is one of the most recognised place names in Australian culture — and arguably one of the most complex. The Gold Coast is simultaneously Australia’s spiritual home of beach lifestyle and a city that has spent considerable energy trying to prove it is more than that. It is a place that was built almost entirely by private enterprise, on the simple premise that people want to be near the ocean, and it has outgrown that premise while never quite leaving it behind. The Gold Coast is both a city and a brand, and sometimes those two things sit in tension with each other. That tension is interesting. The name earns its place.

.surfersparadise deserves its own paragraph, and we will give it one.

And .brisbane2032 is not a TLD we would have invented if it were not for the Olympics. But the Olympics are coming, and they have changed what Brisbane means — not just for Australians but for the world. The Games represent a horizon moment for Queensland, a point at which the global gaze turns toward this corner of the continent and holds. A dedicated TLD for that moment is not a commercial play. It is a record. It is a permanent address that will exist in the onchain namespace long after the closing ceremony, as documentation that Brisbane held this event and meant it. The year in the TLD is not a limitation; it is a timestamp, and timestamps matter.

The Surfers Paradise question

We want to spend some time on .surfersparadise because it is the TLD that generates the most interesting conversations.

The name Surfers Paradise has a specific and somewhat unusual origin. What was once a small coastal settlement called Elston was renamed — first informally, then officially — around the identity of a hotel and the surf culture that grew around it. The name went from a marketing act to a lived identity over the course of decades. By the time official maps and government documents had caught up, everyone already called it Surfers Paradise. The name stuck because it was accurate.

That is a fascinating way for a place to come into existence. Most places are named before they know what they are — they get a founder’s name, or a geographic description, or a colonial imposition. Surfers Paradise named itself from the inside, through the accumulated decisions of the people who lived there and visited there and chose to define it by the thing they loved most about it. The surf. The coast. The sense that this was, for a specific kind of person in a specific kind of mood, exactly where they wanted to be.

That process of self-naming gives the place a particular kind of cultural authority. Surfers Paradise is not simply a suburb of the Gold Coast. It is an idea that has been tested against reality for nearly a century and has not collapsed. The high-rises came. The meter maids came. The theme parks and the nightclubs and the international hotel chains came. And through all of it, the name persisted, because the thing it describes — a place built around the experience of being near the ocean and living accordingly — persisted underneath all the development.

When we decided to secure .surfersparadise, we were recognising that this is a name with genuine cultural thickness. It is not a generic geographic descriptor. It is not a piece of marketing language that has worn thin. It is the kind of name that residents of that place use with pride, even with the specific pride of people who have had to defend what their community is against forces that would flatten it into a generic resort product.

The TLD has length. In the onchain world, that is sometimes seen as a disadvantage. Long names are harder to type. But we are not optimising for typing convenience. We are optimising for identity. And Surfers Paradise has too much identity to be shortened.

What sprawl does to a namespace

We want to return to the question of restraint, because we think it is the most important principle we applied throughout this process.

In the onchain domain world, the temptation to sprawl is structural. There is no external registry body setting limits. There is no application process that imposes friction. If a string is available, it can be secured, often quickly and cheaply. This creates an environment where the rational individual move — capture as much territory as possible — produces a collectively irrational outcome: a namespace so crowded that no single TLD in it has enough gravity to build a real community.

This is not a hypothetical problem. It is visible throughout the broader onchain naming space, where thousands of TLDs have been registered and the vast majority sit essentially unused. The namespace has been treated as a land bank rather than a living thing. Addresses have been minted to be held, not to be built upon. The result is a kind of digital ghost town — lots of registered names, very little activity, and almost no sense that any particular extension stands for something specific.

We did not want to contribute to that problem. We wanted to do the opposite.

When a namespace is kept tight — when the TLDs in it are few and each one carries genuine cultural weight — something happens that does not happen in a sprawling namespace. People start to feel the coherence of the whole. They understand what the namespace is about. They can hold it in their minds. They can explain it to someone else in a sentence: these are the permanent addresses for Queensland, and there are six of them, one for the state, one for the abbreviation, one for the capital, one for the Gold Coast, one for Surfers Paradise, and one for the Olympics. Done. That is a story. You can tell it. You can remember it.

Compare that to a namespace with sixty TLDs. Someone asks you what it is. You start listing names and you can see their attention going somewhere else. The namespace becomes unmemorable not because the individual names are bad but because there are too many of them for any pattern to emerge. Pattern is what makes things legible. Legibility is what makes things usable. Usability is what makes things worth building on.

We wanted people to be able to build on this.

Curation as respect

There is a way to think about what we have done that makes it sound very practical. We selected six TLDs based on a cost-benefit analysis of recognition, cultural weight, and our capacity for ongoing stewardship. That is true, as far as it goes.

But there is another way to think about it that we find more honest.

Every TLD in this namespace is a place where real people live. Queensland is not an abstract concept — it is a state of almost six million people, with the full complexity of human life that six million people bring. Brisbane is a city with neighbourhoods, with a river, with a specific quality of light in the late afternoon, with a collective memory of floods and heat and sporting victories. The Gold Coast has what one academic characterised as a struggle to “affirm a cultural identity” that goes beyond being a tourist resort — a real city emerging behind what might look like a glittering surface. Surfers Paradise has the specific dignity of a place that named itself from the inside and has held that name through a century of change.

These places are not raw material for our namespace. They are the reason the namespace exists. We are not giving Queensland its identity. Queensland has its identity. We are creating permanent addresses that allow people who belong to those places to claim them digitally, in a way that is immutable and owns rather than rents, and that will still be there decades from now when the underlying blockchain is long past its current version and the addresses are simply part of the fabric of how people identify themselves online.

That is a serious thing to be doing. And serious things deserve restraint.

If we had registered sixty TLDs, we would have been treating the place names of Queensland as inventory. We would have been saying: every suburb is equal, every name has the same value, the more we hold the better. We would have been reducing a landscape of genuine cultural difference and depth to a uniform grid of registrable strings. And we would have been making a promise — implicit in every TLD registration — that we could not keep: that we would serve each one of those communities with the same care and attention.

We cannot make that promise for sixty places. We can make it for six.

The names we held back from

It is worth saying directly: we are aware of the places we did not include, and we do not think our exclusion of them diminishes them.

There is no TLD for Cairns in this namespace. Cairns anchors an entire region of the state — the tropical north, the reef, the rainforest, the gateway to Cape York. It is not a lesser place than the ones we included. It is a place with its own coherent identity that we chose not to claim, precisely because we were not prepared to steward it. The same is true for Townsville, which has legitimate grievances about being ignored by the south-east corner of the state and deserves better than a neglected TLD. The same is true for the Sunshine Coast, for Toowoomba, for every regional city that has built a genuine community in the Queensland interior.

Our restraint is not a verdict on those places. It is a verdict on our own capacity.

There is also the question of First Nations names. Queensland’s geography carries layer upon layer of Aboriginal and Torres Strait Islander place names beneath the European ones — Meanjin (Brisbane), Yugambeh Country (the Gold Coast), names and stories that predate the colonial naming system by tens of thousands of years. We are not the right stewards for those names, and we have not sought to be. That is a different kind of project, one that belongs to different hands. We note it here because any honest accounting of what we did and did not secure must acknowledge the names that exist beneath the names we know.

What permanence changes

There is one more dimension to the restraint argument that we want to address, because it is specific to the onchain context.

In a traditional domain registry, TLD sprawl has a natural corrective mechanism: renewal fees. A TLD that nobody uses costs its registrant money every year, and eventually the registrant lets it lapse. The namespace cleans itself up, slowly, through economic pressure. It is inefficient and it takes time, but the mechanism works.

In our namespace, there are no renewal fees. The addresses people register under these TLDs are permanent, paid for once, and will not expire. That is the whole point — it is the core of what makes this different from every domain system that came before. You pay once, you own it forever. No annual reminder that you exist, no expiry date pushing you toward a decision.

That permanence is a feature. But it means that the decision to create a TLD in the first place carries far more weight than it does in a renewable-fee environment. If we had registered sixty TLDs and then realised that forty of them were mistakes, there would be no recovery path. Those names would sit in the namespace permanently, as testament to overreach, as ghost extensions haunting a space that could have been clean.

We thought about this carefully. The immutability that makes the addresses under these TLDs so valuable is the same property that makes the TLD selection decisions irreversible. You cannot unsay a permanent TLD. You can abandon it, stop promoting it, pretend it does not exist — but the record is on the chain, and it will be there long after we are gone.

That weight is clarifying. When you know a decision is permanent, you stop treating it like a default. You stop thinking “we can always clean this up later” because you cannot. The blockchain is not forgiving of errors in the way that renewable systems are. And so the right response to that permanence — the only honest response — is to be more deliberate, not less. To hold back more, not less. To ask, of every potential TLD: does this deserve to exist forever? Does this name have enough cultural reality behind it to justify being a permanent part of the digital landscape?

For the six TLDs we hold, our answer is yes. For the many we chose not to secure, our answer was not no — it was not yet, or not us.

The shape of what we’ve built

Six TLDs sit in a particular relationship to each other that we find meaningful.

Two of them name the state at different levels of formality and familiarity: .queensland and .qld. One names the capital: .brisbane. One names the most famous region: .gold-coast. One names the most iconic precinct within that region: .surfersparadise. And one names a moment that will define Queensland’s relationship with the world for a generation: .brisbane2032.

Together they cover the whole of Queensland’s outward-facing identity without trying to replace it. They are not exhaustive. They are representative. There is a difference.

A map that tries to show everything shows nothing. A map that chooses what to include, and why, is useful. What we have built is closer to a map than a database. It has shape. It has a logic you can grasp. You can stand in front of it and understand what it is trying to do.

That shape matters more than scope. A namespace of sixty TLDs might reach more places, but it would mean less. The six we have secured mean more precisely because they are six, because each one had to earn its place, because the ones that did not make it were excluded for reasons that we are prepared to stand behind.

What comes next, without us

We want to end on something that might sound strange for founders to say.

The goal was never to own Queensland’s digital identity. The goal was to establish the infrastructure through which Queenslanders could own it themselves. The TLDs are the vessels. The addresses people register under them are the content. We chose the vessels carefully, and we will steward the infrastructure they run on. But what the namespace becomes is not up to us.

That is exactly as it should be.

When a person registers an address under .brisbane or .qld, they are not renting space in our project. They are taking permanent ownership of a piece of a namespace that reflects where they are from. They are making a decision that will outlast the original motivations for making it. They may not think about the deliberation that went into selecting those six TLDs. They will simply know their address, and that address will be theirs, permanently, in a way that no annual renewal notice can interrupt.

The restraint we exercised at the TLD level was in service of that permanence. It was in service of the people who will fill these namespaces with meaning we cannot predict. It was in service of the idea that if you are going to build something permanent, you build it on ground you can trust.

Six TLDs. The right six. That was always the answer.