There is a question that every project building something new eventually has to answer honestly, and it is this: what do you actually think of the people you are building for?

Not what you say about them in pitch decks or on social media. Not the language you use in announcements, where words like “community” and “ecosystem” get deployed with impressive regularity and almost no precision. We mean what you actually believe, structurally, about the role those people play in what you are making.

Because there are really only two answers. You either think of them as an audience — a pool of potential buyers, attention-givers, and word-of-mouth vectors whose value to you is measured by what they do next — or you think of them as infrastructure. As the very ground the thing is built on.

We chose the second answer before we registered a single domain. We want to explain why.

The marketing view of community

Let us be honest about what community-as-marketing looks like, because it is the dominant model and it is worth naming clearly.

In this model, community is a distribution channel. It is an efficient way to reach people who already care, to keep them warm between product launches, to encourage them to bring their friends, and to harvest their enthusiasm into content, referrals, and reviews. The people in the community are valued for their behaviour — their shares, their purchases, their advocacy. When that behaviour slows, the conversation in the boardroom turns to “re-engagement.”

This is not cynical, exactly. It is rational. Companies have limited resources. Marketing teams need to demonstrate ROI. Community programmes that cannot be tied to acquisition or retention metrics tend to get defunded. The logic is coherent.

But here is what this model produces: a community that exists to serve the product, not a product that exists to serve the community. The distinction sounds subtle. It is actually enormous.

When community is a channel, the relationship is inherently extractive, even when everyone involved is warm and well-meaning. The company is the centre of gravity. The community members orbit it. Their value is conditional on continued engagement. If they go quiet, they fall out of the funnel. If enough of them go quiet, the community “fails.”

The community, in this model, has no structural weight of its own. It can be ramped up or wound down as circumstances require. It is, at bottom, a line item.

What infrastructure actually means

Infrastructure is different in kind, not just in degree.

Infrastructure is the thing that other things are built on. It does not need to prove its ROI this quarter because its value is structural and cumulative. A road does not need to justify its existence each time a car drives on it. A water system does not run re-engagement campaigns. The point of infrastructure is permanence: it holds shape over time, it enables things that could not exist without it, and its value accrues in proportion to how many people it serves and how durably it serves them.

When we started Queensland Foundation, we were building with a specific kind of permanence in mind. The six namespaces we hold — .queensland, .qld, .brisbane, .surfersparadise, .gold-coast, and .brisbane2032 — are not products in the conventional sense. They are not software features or content subscriptions. They are addresses. Permanent, onchain, immutable addresses that anchor a person, a business, or an institution to a place.

The people who claim an address under one of those namespaces are not customers in the transactional sense. They are not buying access to a service that we provide and they must keep paying for. They are taking permanent ownership of a piece of geography rendered in code. They pay once, for life. There is no renewal, no annual fee, no relationship with us that they must maintain to keep what is theirs. The address is theirs. Full stop.

That structural fact changes everything about what “community” means for us.

The permanence principle

Most community programmes, even very good ones, rest on a fundamentally impermanent foundation. Membership platforms come and go. Social networks change their algorithms or their ownership. Discord servers get abandoned. The physical spaces where groups gather close. The people who held communities together move on.

And so communities dissolve. Not necessarily because people stopped caring, but because the infrastructure that held them dissipated. The channel went away. The engagement loop broke. The gravity weakened.

Our namespace does not work that way.

When someone registers a .queensland or a .brisbane address, that registration is recorded on a blockchain. It is not stored on our servers. It is not contingent on our company’s continued operation. It is not renewable, which means it cannot lapse through inaction or inability to pay. It is immutable in the sense that no one — not us, not a registrar, not a government authority — can reach into the ledger and revoke it.

The permanence is not a feature we are offering. It is a structural property of the technology. And it means that the community of people who hold these addresses is not a community we manage or maintain. It is a community that exists by virtue of shared, permanent presence in a namespace.

That is a completely different kind of community.

Presence as belonging

There is an old idea in anthropology that shared geography creates shared identity. The people who live on the same street, in the same suburb, in the same city, develop common references, common loyalties, common ways of seeing themselves relative to the rest of the world. This does not require anyone to organise them. It does not require meetings or content calendars or engagement strategies. It emerges from the fact of shared place.

We think about the Queensland namespace in exactly these terms.

When someone registers brisbane.brisbane or their name under .qld, they are not opting into a mailing list. They are not joining a loyalty programme. They are asserting a kind of belonging. They are saying: this place is part of who I am, and I want that identity to be permanent, onchain, mine.

The community that forms around that shared act is not a community we built. It is a community that our infrastructure made possible.

And that distinction matters enormously, because it means the community’s existence does not depend on us. It does not depend on our marketing budget, our social media presence, our event schedule, or our team’s energy on any given Tuesday. The addresses exist. The people hold them. The belonging they express is real whether or not we send a newsletter.

We do send newsletters, of course. We do tell the story of what we are building. But we are under no illusion that this activity is what makes the community real. The community is real because its members have made permanent, verifiable claims to a shared namespace. The communications are a conversation between people who already belong to something, not a mechanism to manufacture belonging.

That is the difference between infrastructure and marketing.

Why this matters for how we build

If you think of community as a marketing channel, your job is to keep it warm. You need content. You need events. You need metrics. You need to keep the engagement numbers pointing up and to the right, because those numbers are the proxy for the channel’s health.

We do not manage our community by those metrics, and here is why.

The value of the Queensland namespace is not measured by how many people open our emails this month. It is measured by how many permanent address holders exist in the namespace — and those address holders do not go away. They do not “churn.” They do not un-register when they get busy or when they feel like we haven’t posted enough lately. Their addresses are permanent. Their presence in the namespace is permanent. The community they collectively constitute is permanent.

This creates a fundamentally different incentive structure for how we build.

When a marketing-driven community team sees engagement drop, they have to fix that problem now, usually with more content or more incentives. When we see the same dynamic, we ask a different question: what matters in ten years? Because in ten years, the people who registered a .brisbane or .surfersparadise address today will still hold those addresses. The namespace will have grown. The addresses will be more meaningful, not less, because more people will share that digital geography.

We are not building toward a quarterly engagement target. We are building something that becomes more valuable over time precisely because of its permanence. That is an infrastructure logic, not a marketing logic.

The failure mode we are consciously avoiding

There is a pattern we have watched play out in project after project, particularly in the blockchain and web3 space, and we want to name it plainly because we think about it often.

A project launches with genuine enthusiasm. The early community is passionate and motivated. The founding team engages constantly, answers questions, builds relationships. For a while, this looks like community. It feels like community.

Then the team gets busy building. The content cadence drops. The Discord gets quieter. The founding team members who used to reply to every post are now in product meetings. The community, which was held together largely by that continuous engagement effort, starts to dissipate. The early adopters drift. The evangelists find other projects to evangelise.

What failed here? Not the product, necessarily. What failed was the assumption that community could be sustained by effort alone — that if the team just kept showing up, kept posting, kept engaging, the community would persist.

We do not believe that.

We believe that a community sustained only by effort is a community one bad quarter away from collapse. The moment the effort slows, the gravity weakens. And in a world where every project is competing for the same finite pool of attention, effort will always slow eventually.

The answer is not to try harder. The answer is to build infrastructure — to create conditions under which the community persists not because of what you do but because of what you have built.

For us, that infrastructure is the namespace itself. The permanence of the addresses. The immutability of ownership. The fact that every person who claims a place in the namespace has made a commitment to Queensland that outlasts any particular content cycle or engagement campaign.

What we ask of our community

This is where things get interesting, because the honest answer is: very little.

We do not need our community members to be active. We do not need them to promote us. We do not need them to show up to events or share our posts or become ambassadors or do any of the things that community marketing programmes typically ask their members to do.

What we need — what we have already received, from every person who holds an address — is presence. The permanent, onchain fact of their belonging.

That is a profound thing to realise. The value of the Queensland namespace does not depend on what our address holders do after they register. It depends on the fact that they registered — that they made a permanent, recorded claim to this geography. The network effect we are building is not a function of engagement. It is a function of presence.

This liberates us from a particular kind of anxiety that we think afflicts most projects managing communities as marketing channels: the anxiety of whether the community is still there, still warm, still ready to be activated.

Our community is always there. It is encoded in the ledger. It cannot go cold because it is not kept warm by our effort — it is maintained by the immutable record of its own existence.

The question of value

We want to address something directly, because it comes up often in conversations about what we are building.

People sometimes ask: if your community members don’t owe you anything, if they don’t need to keep engaging, if they don’t need to renew, what is the business model? Where is the incentive to keep building?

It is a fair question, and the answer is also the answer to why we think about community as infrastructure.

The value of a namespace grows with the number and quality of its registrations. When more Queenslanders hold permanent addresses under .queensland, .qld, .brisbane, .surfersparadise, .gold-coast, and .brisbane2032, each individual address becomes more meaningful. Not just financially — though that is true — but symbolically. To hold a .brisbane address is to share that address space with every other person who has staked their permanent digital identity on Brisbane. The more people who do that, the more that shared identity means.

This is network infrastructure logic. The value of a telephone network is not determined by how often the phone company’s newsletter gets opened. It is determined by how many people are connected. The value accrues to the nodes, not to the management layer.

We are the management layer. We built and hold the TLDs. We set the price and decided on the structure. But the value is held by the people in the namespace. And that means our interests are aligned with theirs in a way that is structural, not just rhetorical.

When we say we want every Queenslander to have a permanent onchain address, we are not saying that as a marketing slogan. We are saying it because it is literally true that the more people are in the namespace, the better the namespace works for everyone in it.

That is infrastructure.

On the price of entry

We want to say something about why we priced these addresses the way we did, because it connects directly to everything we have said about community as infrastructure.

Five dollars, once, forever.

We did not price these addresses at five dollars because we are being generous. We priced them that way because we are being intentional about the shape of the community we are building.

A namespace that costs hundreds of dollars to enter is a namespace that reflects purchasing power, not belonging. It is a namespace whose community is defined by who could afford it rather than who identified with it. That is not the community we want to build, and it is not the infrastructure that Queensland deserves.

Five dollars is a price that almost anyone can pay. It is lower than a monthly streaming subscription, lower than a cup of coffee in most Australian cities. And because there is no renewal, it is a one-time decision with a permanent outcome. You are not renting access. You are not buying into a service. You are permanently inscribing your Queensland identity into a public ledger.

The price is low because the barrier to permanent belonging should be low. The community this builds is broader, more diverse, and more genuinely representative of Queensland than any community built on higher barriers of entry could ever be.

That is an infrastructure decision, not a marketing decision.

The long view

We want to close with something that sounds almost naive in the context of how most technology projects are built and measured, but which we believe with complete sincerity.

We are not building this for the next product cycle. We are not building it for the current market environment or the current state of blockchain technology or the current conversation about digital identity. We are building it for Queensland — for the state, the place, the people — on a timescale that makes quarterly metrics essentially irrelevant.

The addresses we are issuing are permanent. The infrastructure we are building is meant to last. And the community we are accumulating in the namespace is a community that will still be there — still holding their addresses, still participants in Queensland’s digital geography — long after any particular social media platform has come and gone, long after any engagement campaign has run its course, long after we as individuals have moved on to other things.

That is what it means to build infrastructure instead of marketing.

Marketing is how you talk to people today. Infrastructure is what you leave behind for them tomorrow.

We chose infrastructure. And every person who registers an address is, whether they think about it this way or not, choosing it too. They are making a permanent stake in a shared digital geography called Queensland. They are joining a community not by opting into a list but by writing their presence into a ledger that no one can alter.

That permanence is the whole point.

It is not a feature. It is not a selling point. It is the thing itself — the reason we believe this matters, the reason we keep building, and the reason the community we are forming is not something we manage.

It is something we belong to, along with everyone else who has claimed their place.