There is a phrase we keep coming back to. We use it in conversations with each other, we reach for it when someone asks what Queensland Foundation is trying to do, and it sits somewhere at the centre of how we think about this whole project. The phrase is building together.

It sounds simple. It sounds like the kind of thing any project might say. And that’s exactly why we want to spend some time unpacking it — because when we say it, we mean something specific. We mean something that took us a long time to understand clearly ourselves, and something we think is worth saying plainly so that the people who are part of this with us know what we actually believe.

This post is our attempt to say it plainly.

How we got here

We didn’t start with a grand theory of community. We started with a conviction about place.

Queensland is not a generic geographic label. It is a living identity — something that people carry with them whether they are standing on the Gold Coast at sunrise or sitting in a flat in another city or another country, holding on to something that feels like home from ten thousand kilometres away. Queensland means something. Brisbane means something. Surfers Paradise means something. These words carry weight. They carry memory, pride, belonging, aspiration.

And yet, for all that weight, there was no permanent digital record of them. No layer of the internet that Queenslanders could claim as their own and hold for life. The traditional domain system gave us .com.au and the rest — useful, functional, but owned and operated by institutions. Subject to annual fees. Subject to renewal. Subject to the risk that one day you forget to pay, or the registry changes its policies, or the organisation that controls the extension decides your use doesn’t fit its rules anymore.

We looked at that situation and felt something was missing. Not just a technical gap, but a conceptual one. If the internet is increasingly where identity lives — where you tell people who you are, where you build your presence, where you plant a flag — then Queenslanders deserved a piece of that ground that was genuinely theirs. Permanent. Unrevocable. Owned at the address level, not rented from above.

That’s what we set out to build. Six onchain TLDs — .queensland, .qld, .brisbane, .surfersparadise, .gold-coast, and .brisbane2032 — permanently secured on blockchain infrastructure, available to anyone who wants to claim an address within them. Once. For life. With no renewals and no annual fees. Pay once, own it forever.

But here’s the thing about building a namespace: the infrastructure is the easy part to describe. You can explain blockchains. You can explain immutability and transferability and permanence. What’s harder to explain — and what matters more — is the question of what fills that infrastructure with meaning. A namespace without inhabitants is just an empty room. The addresses don’t mean anything until people hold them.

That’s where building together begins.

What a namespace actually is

Before we go further, it’s worth being precise about what a namespace is, because the word matters here.

A namespace is a system of addresses. It’s a structured way of giving things names so they can be found, identified, and related to one another. On the internet, the domain name system is a namespace. Your street address is a namespace. Your phone number is a namespace. In each case, the namespace is a shared infrastructure — a common system that only works because everyone agrees to use it and because the addresses within it are distinct from one another.

This has an interesting implication: a namespace is, by its nature, a collective thing. It doesn’t belong to one person. It exists in the relationship between all the addresses within it. Your home address is only meaningful because it sits within a street, a suburb, a postcode, a country — all of which are also addresses, held by others, forming a structure you are part of.

The Queensland namespace works the same way. When someone claims michael.brisbane or currumbin.gold-coast or go.queensland, they are not just getting a string of characters they own. They are becoming part of a structure. They are joining a namespace that is, in part, defined by the fact that they are in it.

This is not a metaphor. It is how namespaces literally function. The meaning of an address is partly intrinsic — it is your name, your brand, your identity — and partly relational. It means something to be a .brisbane address because there are other .brisbane addresses. It means something to hold a piece of the Queensland namespace because other people hold pieces of it too, and together you form something larger than any individual address.

We find this genuinely interesting, because it means that the people who claim addresses in the Queensland namespace are not just customers of an infrastructure. They are, in a real sense, constitutive of the namespace itself. Without them, we have nothing. With them, we have something that will outlast all of us.

The tribe

We use the word tribe carefully, and we want to explain why.

The Queensland namespace is not for everyone. It is, by design, for a specific kind of person: someone who feels a genuine connection to Queensland — to the place, to the identity, to what it means to be from here or to have chosen here. That connection might be birthplace. It might be years of living on the coast. It might be the memory of a childhood summer, or the pride of a business built from scratch in Brisbane, or the simple fact that Queensland is home and has always been home.

What makes someone part of the tribe is not a credential we issue. It is a feeling they already have. We are not creating the tribe. We are giving the tribe a place to be itself online, in a way that is permanent and owned rather than temporary and rented.

And because the tribe is self-selecting — because the people who come to the Queensland namespace come because they genuinely care about Queensland — the quality of presence they bring to the namespace is different from what you would find in a generic domain extension. These are not people who registered an address because it was cheap or because it ranked well in search. They are people who wanted to plant a flag in a place that means something to them.

That matters enormously. It shapes the character of the namespace. It shapes what the addresses in it stand for. And it is something we, as the team behind Queensland Foundation, cannot manufacture. We can build the infrastructure. We can secure the TLDs. We can make it easy and affordable to claim an address. But we cannot manufacture the sense of belonging that makes the namespace meaningful. That comes from the tribe.

This is the first and most important thing we mean by building together: the tribe brings something we cannot bring. Their presence is the substance of the namespace. They are not participants in something we built. They are builders of something we started.

Permanence as a statement

One of the most deliberate decisions we made in designing this project was the pricing model. One price, paid once, no renewals, no annual fees, no expiry.

This decision is not just a commercial choice. It is a philosophical one. It is a statement about what kind of relationship we want to have with the people who join the namespace, and what kind of relationship we think those people deserve to have with their digital identity.

In the traditional domain system, you don’t own your address. You rent it. Every year, you pay again to keep it. If you stop paying — because you forgot, because you ran out of money, because the registrar raised its fees, because you died and no one maintained your account — the address returns to the pool and someone else can take it. Your digital presence is contingent on continued payment to an institution.

We think this is the wrong model for identity. You don’t pay an annual fee to keep your name. You don’t renew your birthplace. You don’t renegotiate your sense of belonging every twelve months. Identity is not a subscription. It is something you have.

Onchain addresses work differently. The address lives on the blockchain. It is controlled by whoever holds the corresponding wallet key. It doesn’t expire. It can’t be taken away by an institution. It can be transferred, sold, or gifted — but that transfer happens on the owner’s terms, not the registrar’s. The address is property, in a real sense that most internet addresses are not.

When someone claims an address in the Queensland namespace, they are claiming something that is genuinely theirs. And because it is genuinely theirs — because it will still be theirs in twenty years without any action on their part — they are making a kind of permanent statement. They are saying: this is who I am, this is where I am from, and I am putting that on record in a way that will not disappear.

That permanence changes the nature of the namespace. It means the namespace is not just a snapshot of who is here today. It is an accumulating record of who has claimed Queensland as part of their identity — a record that grows over time and never shrinks, because addresses don’t expire and addresses don’t go dark.

We find something profound in this. The Queensland namespace, over time, becomes a kind of permanent register of belonging. Every address in it is a declaration. Every holder of an address is a contributor to a record that will outlast the technology that created it, because the blockchain is designed precisely to persist.

Building a permanent record of Queensland belonging — that is something we are doing together. We could not do it alone, and we could not do it at all if the people who join the namespace did not choose to stay.

What feedback actually means

Here is something we want to be honest about.

We don’t have all the answers. We know what we’ve built. We know what we believe. We know the infrastructure we’ve secured and the principles we’ve committed to. But we don’t know everything the Queensland namespace will become — because that is genuinely not something we can know alone.

The namespace will be used in ways we haven’t imagined. It will become meaningful in contexts we haven’t thought of. People will build things on top of it — ways of using onchain addresses that solve problems we haven’t encountered or haven’t thought to solve. And the only way we will know about those uses, those contexts, those problems, is if the people living in the namespace tell us.

This is where building together becomes practical rather than philosophical.

When we talk about feedback shaping the development of the namespace, we don’t mean we run surveys and implement features based on the results. We mean something more fundamental: that the people who use the namespace are closer to the realities of what the namespace needs to be than we are. They are the ones using the addresses. They are the ones discovering what works and what doesn’t, what’s missing and what’s unnecessary, where the friction is and where the experience exceeds expectations.

We have always believed that the best product decisions come from deep attention to how something is actually used — not from the assumptions of its builders. This is true of every technology, but it is especially true of a namespace, because a namespace is used to represent identity, and identity is personal in ways that make generalisation dangerous.

What does it mean to put your business name on a .queensland address? What does it feel like to share your .brisbane address with someone for the first time? What would make the address more useful in your daily life? What does permanence feel like when you hold it, as distinct from when you think about it abstractly?

We don’t know the answers to these questions from the inside. The people in the namespace do. And the relationship we want to have with them — the relationship we think is implied by the phrase building together — is one in which those answers flow back to us, shape what we build next, and result in a namespace that serves Queensland better than it would if we had built it in isolation.

This is not a customer relationship. Customers consume what has been built. The tribe we are talking about contributes to what is being built. That distinction matters to us.

The responsibility it places on us

Building together is not a phrase we use to flatter the people who join the namespace. It is a phrase that describes a relationship, and like all real relationships, it carries obligations on our side too.

If the tribe’s presence gives the namespace its meaning, then we have a responsibility to protect that meaning. We cannot do anything that would undermine the integrity of what people have claimed. We cannot change the rules in ways that betray the trust of people who made permanent decisions based on our commitments.

This is one of the reasons we built on blockchain infrastructure rather than a centralised system. Centralised systems depend on the trustworthiness of the operator. If we are the gatekeepers, then everything depends on us continuing to behave well — and the history of the internet is full of examples of operators who changed their terms, raised their prices, or simply disappeared. We wanted to remove ourselves as the point of failure, to the extent that is possible.

Onchain infrastructure means the addresses exist on the blockchain, not on our servers. Our role is to issue them. Their permanence comes from the chain, not from us. If Queensland Foundation ceased to exist tomorrow, every address that has been claimed would remain valid, owned, and transferable. The namespace would continue. The permanence we promised would persist.

That is an important kind of responsibility: designing things so that our trustworthiness is backed by architecture, not just by intention.

But there are responsibilities that architecture alone can’t carry. The ongoing development of the namespace — the decisions about what tools to build, what integrations to support, what applications to create — those depend on us continuing to act in the interests of the tribe rather than against them. And the only way to sustain that commitment is to keep the relationship honest.

Building together means we tell people what we’re doing and why. It means we explain our thinking, not just our decisions. It means we treat the tribe as people capable of understanding the reasoning behind choices, not as an audience to be managed. And it means that when we’re uncertain — which we sometimes are — we say so.

Why this isn’t just a slogan

We are aware that building together sounds like something any company would say. It sounds like community management language. It sounds like the kind of phrase that gets put on a website and never really examined.

We want to be clear about why we think it’s different here — and the difference comes down to the specific nature of what we’ve built and who we’ve built it for.

Most products are built for users. Users are people who consume a product that exists independently of their participation. The product would be the same whether any given user was there or not. The product’s value doesn’t depend on the character of the people using it.

A namespace is not like that. A namespace’s value is partly a function of who is in it. A .queensland address means something different in a namespace full of people who genuinely care about Queensland than it would in a namespace where addresses had been claimed opportunistically, for speculation, by people with no connection to the place.

We could have made this a pure speculation play. We could have priced addresses higher, targeted investors, encouraged holding rather than using. We didn’t, because we don’t think that would result in a namespace worth having. A namespace full of speculators is not a namespace — it’s a market. We want a namespace. That means we want people who are there because they are genuinely Queenslanders, genuinely connected to these places, genuinely interested in having a permanent piece of digital ground that reflects who they are.

The low price — one payment, starting at five dollars, no annual fees — is a direct expression of this. We want the financial barrier to be as low as possible, because we want the only real qualification to be the connection to Queensland. We want people to claim addresses because they want them, not because they calculated a return on investment. We want permanence to be the point, not liquidity.

And that means the tribe we are building this with is specifically the tribe of people for whom Queensland is meaningful. For those people, building together is not a slogan. It is a description of what we are literally doing. We are building a permanent record of Queensland identity, together with the people whose identity it is.

The namespace as a commons

There is a concept in political philosophy and economics called the commons — shared resources that belong to a community rather than to individuals or institutions. Traditional commons were things like fishing grounds, grazing lands, forests. Things that no one person owned but that everyone in the community depended on and had a stake in.

We think about the Queensland namespace as a kind of digital commons. It is not owned by Queensland Foundation in the way a product is owned by a company. We secured the TLDs. We built the infrastructure. But the namespace itself — the living thing that has meaning — is held in common by the people who inhabit it.

This framing has practical implications. It means our job is not to maximise what we extract from the namespace. Our job is to steward it. To maintain the conditions under which it can thrive. To make good decisions on behalf of the commons, even when those decisions might be easier or more profitable if we made them differently.

The no-annual-fee model is an expression of this stewardship. We made a commitment that the cost of holding an address is the initial claim price and nothing more. That commitment is one-way and permanent. We cannot raise fees. We cannot impose renewals. We cannot use financial pressure to push people out of addresses they have claimed. The commons is theirs. Our job is to protect it.

There is something in the commons framing that also speaks to the tribe’s responsibility. A commons thrives when the people who depend on it take care of it — not in a transactional, rule-following sense, but in a genuine sense of investment in the shared resource. The Queensland namespace will thrive if the people in it treat their addresses as something worth caring for, worth building on, worth sharing with others who have a genuine connection to Queensland.

We cannot mandate that care. We can only create the conditions for it, and trust that the tribe we have described — people who chose the namespace because they genuinely love this place — will bring that care naturally.

What the future holds, and why we’re not anxious about it

We are sometimes asked what the Queensland namespace will look like in ten years, or twenty, or fifty. It’s a question we genuinely enjoy thinking about, because the honest answer is: we don’t fully know, and that’s one of the most exciting things about it.

What we do know is the foundation. The TLDs are secured. The addresses are permanent. The blockchain will persist. Whatever is built on top of that foundation — whatever uses people find for onchain Queensland addresses, whatever applications and integrations and communities emerge — will be built on something solid.

We also know who will be doing the building. The same people who have always been doing it: the tribe, and us, together. The people who hold addresses in the Queensland namespace will continue to find ways to use them that we haven’t imagined. The technology landscape will continue to evolve, and onchain addresses will find applications in that landscape that don’t exist yet. The meaning of digital identity will continue to deepen, and the permanence of what people have claimed will feel more significant, not less, as temporary alternatives come and go.

We are not anxious about this future because we are not trying to control it. We laid a foundation and secured a commons. The future of that commons will be shaped by the people who inhabit it — which means it will be shaped by people who care about Queensland, who have permanently claimed their place in the namespace, and who are invested in making it mean something.

That is as good a foundation as we know how to build.

A note on what this project is not

We want to be honest about the limits of what we are.

We are not a government. We don’t speak for Queensland officially. We are not endorsed by the state or by any institution with formal authority over Queensland’s identity. We are a project that believes in Queensland, that secured the infrastructure to give Queensland a permanent home in the onchain world, and that is building that home with the people who want to live in it.

We are not a platform in the conventional sense. We are not building a social network or a marketplace or an app. We are building infrastructure — the kind of infrastructure that other things can be built on top of. The addresses in the Queensland namespace can be used however their holders choose to use them. We don’t prescribe the use. We make the use possible.

And we are not a community manager or a gatekeeper of Queensland belonging. We don’t decide who is a real Queenslander. We don’t curate the namespace based on our judgement of who deserves to be in it. The namespace is open to anyone who feels the connection to Queensland that makes an address in it meaningful. That openness is part of the point.

What we are is a team that believes deeply in what we’ve built, that is committed to the principles we’ve laid out, and that wants to see the Queensland namespace become everything it can be — which means wanting the people who join it to thrive, to build, and to find it genuinely useful and meaningful for the rest of their lives.

Coming back to the phrase

Building together. Let’s sit with it for a moment before we close.

We are not building for the tribe. That would imply we know what they need, and we do not know what they need better than they do. We are not building with the tribe in a tokenistic sense — inviting them to feel involved while we make all the decisions. We are building together in the most literal sense: the thing we are building is partly constituted by their participation, cannot exist without their presence, and will become something neither we nor they could predict alone.

The Queensland namespace will be what the people in it make of it. We provide the permanent ground. They bring the meaning. We continue to develop the infrastructure. They continue to find new ways to inhabit it. We protect the commons. They enrich it.

This is not a division of labour in the usual sense. It is a relationship between two kinds of builders — the people who lay the foundation and the people who build on it — where both are necessary and neither is sufficient alone.

We started this project with a conviction about place. About the fact that Queensland means something, and that Queenslanders deserve a permanent piece of digital ground that reflects that meaning. Everything we have done has been in service of that conviction.

But we have come to understand, as the project has developed, that the conviction alone was not enough. The infrastructure alone is not enough. The permanence alone is not enough. What makes this whole thing real — what makes it more than a technical project and something closer to a genuine act of community — is the people who choose to be part of it.

They are the co-builders. They always have been.

When we say building together, we mean it in the most serious and literal sense we know how to mean anything. And we hope that everyone who is part of the Queensland namespace — everyone who has claimed an address, everyone who is thinking about it, everyone who will join in the years ahead — knows that their presence here is not incidental to what we are building.

Their presence is what we are building.

That is what we mean.