There is a moment, early in any project like this, when the thing you are building stops feeling theoretical and starts feeling real. For us, that moment came when we secured .brisbane.

Not because it was the most complicated thing we had done, or the most technically demanding. But because of what the word means. Brisbane is not a generic term. It is not a placeholder. It is not a brand name someone invented. It is the name of a capital city — a city that has been shaped by river floods and world wars, by convict labour and free settlers, by sprawling suburban identity and a skyline that keeps growing taller. Securing .brisbane meant taking on a responsibility that no other TLD in our set quite carries in the same way. A capital city is a different kind of weight.

We want to explain, as clearly as we can, why we made that decision — and what we believe it means.

What it means to secure a city’s name

When we started Queensland Foundation, the question was simple: why should the digital identity of a place as specific, as storied, and as alive as Queensland belong to a generic namespace that has nothing to do with where these people actually live?

Every business in Brisbane, every creative, every tradie, every family that has lived in the same suburb for three generations — they are all currently forced into the same system. A system designed for the world in general, not for them in particular. They can register yourname.com.au, or yourname.com, or maybe yourname.net if .com.au is taken, and in every single case they are renting a piece of infrastructure from a company that will charge them again next year, and the year after, and every year until they stop paying or the company changes its terms.

That is not ownership. That is a subscription to someone else’s infrastructure.

Onchain addresses work differently. When someone claims an address under .brisbane, they own it. It is minted on the blockchain, stored in their wallet, and it is theirs permanently. No annual renewal. No registrar holding a lien over their name. No renewal reminder sitting in an inbox. The address cannot be taken away because someone decided to change their pricing model. Once claimed, it belongs to the person who claimed it — immutably, transferably, and without expiry.

We secured .brisbane because that is the right model for a city’s digital identity. A city endures. Its digital namespace should too.

The capital city question

Brisbane became Queensland’s capital in 1859, when the colony separated from New South Wales. It has been the capital ever since — through federation, through two world wars, through floods and expo years and Olympic announcements. The city has always been, in some fundamental way, the point where Queensland’s identity converges.

That gives .brisbane a gravity that, say, a product TLD or a brand TLD does not have. When someone uses an address under .brisbane, they are not just choosing a convenient namespace. They are affiliating with something older and more specific. They are saying: I am of this place.

We thought carefully about whether we were entitled to make that claim — to be the project that secures the name of a capital city. Our answer was this: if we did not do it, someone else would, eventually. And the question of who secures a name like .brisbane matters enormously, because whoever holds the TLD sets the terms under which people can participate in it.

Our terms are simple. We do not believe in gatekeeping. We do not believe in pricing people out of their own city’s namespace. The cost to claim an address under .brisbane starts at five dollars, paid once, with nothing owed ever again. A sole trader in Fortitude Valley has the same access as a corporation in the CBD. A teenager in Inala who wants to put their creative work under a permanent, ownable address has the same access as a law firm in the city. That is what a city’s namespace should look like.

The relationship between .brisbane and .queensland

We secured six TLDs: .queensland, .qld, .brisbane, .surfersparadise, .gold-coast, and .brisbane2032. Each one was a deliberate choice. Together they form a namespace that mirrors the actual geography and identity of this part of the world — a set of permanent onchain addresses that belong to Queensland, not to a generic internet registry with no connection to any of these places.

But within that set, the relationship between .brisbane and .queensland is the most interesting one to think through, because it is not a hierarchy — it is more like a topology.

Queensland is vast. It is the second-largest state in Australia, stretching from the subtropical south-east to the tropical far north. It contains rainforests and reefs and red dirt. It contains cities and towns that feel as different from each other as different countries. Someone in Cairns and someone in Toowoomba are both Queenslanders, but they live in very different worlds. .queensland is the TLD for all of them — the whole state, the whole identity, the full breadth of the place.

.brisbane is something different. It is specific. It is urban. It is capital. When someone chooses .brisbane over .queensland, they are making a precise statement about where they sit in that geography. They are saying: not just Queensland — Brisbane. The river city. The city shaped by the Brisbane River winding through its middle, by the Queenslander houses on the hills, by the South Bank and the CBD and the inner suburbs pushing outward.

These two TLDs do not compete with each other. They coexist the way a city and its state coexist — separately identifiable, but deeply related. A Brisbane business might hold both. A statewide organisation might prefer .queensland. A hyper-local artist might want nothing other than .brisbane. The namespace gives people options that correspond to real distinctions in how they think about themselves and where they belong.

What we were careful never to do is impose a structure. We are not saying that .brisbane is a subdivision of .queensland, or that .queensland is the superior address and .brisbane is merely local. They are peers in the namespace — different in scope, equal in permanence.

What .brisbane makes possible that .com.au never could

This is the question we come back to most often, because it gets to the heart of why any of this matters.

A .com.au address tells you almost nothing. It tells you the business is Australian, broadly. It tells you they could find an available combination of words and numbers that had not already been claimed by someone else. It is a credential issued by a central authority that you pay to maintain, and you can lose it the moment you stop paying. It is infrastructure, not identity.

.brisbane is different in kind, not just degree.

First, it is geographically declarative. An address ending in .brisbane says where you are, where you belong, where your work comes from. That is information a .com.au address is constitutionally incapable of conveying. The extension itself carries meaning before you have even read the word to its left.

Second, it is permanent. The claim you make under .brisbane does not expire. There is no renewal window. There is no scenario in which you forget to pay an invoice and find your address has been snapped up by someone else. When a musician in New Farm puts their catalogue under an address ending in .brisbane, that address is theirs for as long as they want it — not for as long as they keep paying a registrar to hold it for them.

Third, it is ownable in a way that traditional domains are not. In the traditional DNS system — the one that governs .com and .com.au and every other legacy extension — you do not own your domain. You lease it. The registrar holds it. The registry holds the TLD. ICANN, ultimately, has authority over the whole system. You are a licensee, not an owner. If a registrar collapses, if terms change, if a legal dispute arises in a jurisdiction you have no connection to, your address is at risk in ways you cannot fully control.

An address minted onchain under .brisbane is yours in the way that an asset in your wallet is yours. It is recorded on a public blockchain. It is tied to your wallet address. It cannot be taken from you by a registrar’s decision or a change in company policy. You can transfer it if you choose to. You can hold it if you choose to. The decision is yours, not theirs.

Fourth — and this is the dimension we find most interesting to think about — it is place-native in a way the entire internet has never allowed before.

The internet was built without geography. That was partly intentional and partly just a consequence of the era in which it was designed. The assumption was that the network was borderless, that information wanted to be free, that the idea of a Californian company or a Swiss registry administering the names of a place in south-east Queensland was just the way things worked. Nobody designed it to be hostile to place-based identity. It just happened to be indifferent to it.

We are building something that is not indifferent. .brisbane is a namespace that begins with a city and works outward from there. The city is the given. The people who live there, work there, create there — they are the intended participants. Not as an afterthought, not as a regional market segment in someone else’s product strategy, but as the entire point.

The weight of the name

We want to be honest about what we felt when we secured .brisbane, because it was not a purely technical experience.

The city named Brisbane has been called home by the Turrbal and Jagera peoples for tens of thousands of years. It was called Meanjin — a word that speaks to the shape of the land, the place where the river bends. It became a colonial settlement in the 1820s, a municipality in 1859, a city in 1902. It hosted a World Expo that remade its waterfront. It built its South Bank Parklands on the bones of that transformation. It has been flooded and rebuilt. It has been underestimated by Sydney and Melbourne and has responded with something quiet and persistent that amounts to confidence.

We are not historians, and we are not making a historical claim. But we are aware — genuinely aware — that securing the name of a place like this is not like securing a brand name or a product namespace. There is a community attached to this word. There are people who have loved this city their whole lives, who know its suburbs and its river and its particular light, and who have never been given a piece of its digital identity that they could truly call their own.

That is what we are trying to change. Not dramatically. Not with ceremony. Just practically: by making it possible for anyone who calls Brisbane home to claim a permanent onchain address that says so.

Why capital cities deserve their own namespace

Most of the world’s major cities have fought, in one way or another, for a version of this. City-specific domain extensions exist in the legacy DNS world — .london, .tokyo, .sydney — but they exist under the same renewal and registrar framework as everything else. They are better than .com.au in terms of geographic signalling, but they are not better in terms of ownership. You are still renting. The clock is still ticking on your annual fee.

What we have done is different, because the infrastructure is different. .brisbane is not a legacy DNS extension. It is an onchain TLD. The permanence is structural, not just promised. You do not have to trust that the company behind it will keep its word about no renewal fees, because the technology enforces it. The blockchain record does not have a renewal date built into it. The absence of expiry is not a policy choice that can be reversed — it is an architectural fact.

For a capital city, that matters in ways that go beyond convenience.

Think about a small business that has operated in Brisbane for twenty years. They have a .com.au address that they have renewed every year for as long as they have been online. The address has become part of how their customers find them. It is embedded in old receipts and business cards and word of mouth. And every single year, they are one lapsed payment away from losing it.

Now imagine they claim an address under .brisbane. Permanent. No renewal. Theirs for as long as they exist as a business — and transferable to whoever comes next if they ever sell or close. The continuity of that address is not dependent on anyone’s billing cycle. It is dependent on nothing other than the blockchain continuing to exist.

That is a genuine improvement in the condition of small businesses in this city. It is not a large or dramatic improvement. But it is real, and it compounds over time.

The businesses and creators we had in mind

When we thought about who would use .brisbane, we did not think primarily about technology companies or blockchain-native projects. We thought about the people who are already building things in this city, without any particular interest in blockchain, who simply deserve a better model of digital ownership than the one they currently have.

We thought about the restaurant in West End that has been there for fifteen years and whose owner has no idea what an onchain domain is, but who would immediately understand the appeal of paying five dollars once and owning their digital address permanently.

We thought about the independent musician playing shows at the Fortitude Valley venues, whose entire online presence is scattered across social media platforms they do not own and a website at an address they are renting from someone they have never met.

We thought about the tradie in the northern suburbs who has been in the same streets their whole life and who wants to signal, simply and clearly, that they are of this place — that when you hire them, you are hiring someone from Brisbane, not someone who happened to be available.

We thought about the creative agency in the inner suburbs whose work is deeply tied to Brisbane’s specific aesthetic and culture, and who wants an address that says that without having to explain it.

None of these people needed blockchain. They needed permanence. They needed affordable access. They needed an address that means something about where they come from.

.brisbane gives them that.

The question of legitimacy

We anticipated that someone would ask: who gave you the right?

It is a fair question. We are a project, not a government. We did not hold a public consultation. We did not seek the endorsement of the Brisbane City Council or the Queensland Government. We looked at an emerging infrastructure layer — onchain TLDs — and we secured the names that we believed mattered most for this part of the world, before anyone else did, under terms that we believe are fair.

We think that is the right answer to the legitimacy question, but we also think it requires explanation.

The alternative to us securing .brisbane was not that the Brisbane City Council secured it. The alternative was that someone else — potentially someone with no connection to Brisbane, no understanding of the city, and no particular reason to keep prices accessible — secured it instead. In the world of onchain TLDs, names are available on a first-come basis. The question was never whether .brisbane would be secured. It was who would secure it, and on what terms.

We secured it on terms that we believe any Brisbanite could accept: one-time access, starting at five dollars, with no gatekeeping and no hierarchy. The name is for the city. The city is for its people. We are just the project that made the name available on infrastructure that makes ownership real.

We will hold that responsibility carefully.

What comes next for .brisbane

We think about the .brisbane namespace the way you might think about a new piece of public infrastructure — not in the sense that we control it like a government controls a road, but in the sense that it is meant to serve a community over a long time horizon, not to be optimised for short-term revenue.

What we want to see, over time, is a namespace that reflects the full range of what Brisbane is: the creative industries, the small businesses, the communities, the cultural institutions, the individuals who have built their lives here and who want a permanent digital expression of that fact.

We want to see a Brisbane family claim an address under .brisbane and hold it for decades — the same way they might hold the deed to a house in their suburb, as a piece of property that has real continuity.

We want to see a small business in Paddington or Woolloongabba or Carindale claim an address that they never have to think about renewing, because the model does not work that way.

We want to see the idea that digital addresses can be permanent and place-specific become so normal in Brisbane that people forget there was ever a time when you had to rent your own name from a company on the other side of the world.

That is what .brisbane is for.

A final thought on naming things

Names matter. They always have. The land along the river bend was called Meanjin long before it was called Brisbane. The city was called Edenglassie before it was renamed to honour a colonial governor. Every renaming is a statement about who has the authority to define a place.

We are not in the business of renaming Brisbane. The city has its name, and it is a good one. What we are doing is something more modest and more specific: we are giving that name a permanent home in a digital namespace that belongs to the people who live under it.

The infrastructure exists to do this now. It did not exist a decade ago. In another decade, we expect it will be obvious that of course capital cities should have permanent onchain namespaces, and of course those namespaces should be accessible and affordable, and of course the people who live in those cities should be the ones who can claim addresses within them.

We chose not to wait for obvious. We built it now, while it was still early, while the names were still available, and while the infrastructure was still new enough that getting the terms right — truly right, not just right enough — was possible.

.brisbane is ours to steward. It belongs to the city and to the people who claim addresses within it. We are just the project that made it real.