The part nobody talks about

There is a moment in every project where you realise the name you’ve been using in conversation — the shorthand, the working title, the thing you type into shared documents at midnight — is not actually the name. It’s a placeholder. A habit. A sound you make when you need to refer to the thing before the thing has a real identity.

We had several of those sounds.

We used them for longer than we should have. We argued about them. We talked ourselves in circles. We wrote lists on whiteboards and then photographed the whiteboards and then stared at the photographs at odd hours, trying to feel something definitive.

Eventually we did. But it took longer than we expected, and the process taught us things about the project itself that we hadn’t fully understood until we were forced to name it.

That’s what this post is about — not the final name, which you already know, but the road to it. The names we nearly chose, the reasons we walked away from them, and what we eventually understood that we needed the name to do.

Why naming infrastructure is different

Most products get named after what they do, or how they feel, or who they’re for. You name a productivity app something crisp and forward-moving. You name a consumer brand something warm and approachable. You name a game something evocative. The category gives you cues.

Infrastructure is different.

Infrastructure doesn’t have a user experience in the conventional sense. It has a relationship with time. Roads don’t get refreshed every few years. Bridges don’t rebrand. The electrical grid doesn’t pivot. When you’re building something that is meant to underpin other things — something that is designed to outlast trends, outlast teams, outlast the specific moment in which it was created — the naming logic shifts entirely.

We weren’t building an app. We weren’t building a platform in the Silicon Valley sense of the word, where “platform” means something you grow on top of and then eventually migrate off when the economics change. We were building something that, by design, does not get replaced. Something that, once deployed, exists permanently onchain. Something that people would own — not rent, not subscribe to, not maintain — but simply own, the way you own a piece of land or a family name.

That changes everything about what a name needs to do.

A name for something temporary can afford to be clever. Clever fades well. Clever can become nostalgic. But a name for something permanent has to do more work. It has to communicate the nature of the thing. It has to age without irony. It has to be as legible to someone encountering it for the first time in twenty years as it is to someone encountering it today.

We knew this going in, and it made us slow. Slower than was probably comfortable. But we think that slowness was correct.

The names we almost used

We’re not going to pretend the early names were terrible. Some of them were genuinely compelling. Some of them made it further than they should have, purely because they sounded good in the room at the time.

The geographic plays

The first category of names we explored were straightforwardly geographic. Names that planted a flag. Names that said: this is for here, this is of here, this is from here.

Some of them were literal. Some were abbreviations. Some were portmanteaus of Queensland-specific references — things that would resonate immediately with anyone who grew up here and mean nothing to anyone who didn’t.

We spent a long time in this territory, partly because it felt honest. The project is genuinely, specifically, unapologetically Queenslandian. We weren’t trying to build a global platform with a Queensland flavour. We were trying to build Queensland’s infrastructure — for Queenslanders, anchored to this geography, grounded in this place. So names that were explicitly geographic felt right.

What we kept running into, though, was the question of scope. A name that was too specifically geographic — too tied to one corner of the state, too evocative of one particular reference — would feel like it was excluding someone. And the project isn’t exclusive. It’s for the whole of Queensland. All of it. The coast and the interior. The southeast corner and the Cape. The cities and the towns that don’t make it into travel pieces.

We needed a name that was geographic in identity but not geographic in limitation. And that’s a harder needle to thread than it sounds.

The technical plays

The second category we explored were names that signalled the technology. Words that gestured toward blockchain, toward permanence, toward the onchain nature of the infrastructure.

These names were, to be blunt, the least interesting we considered — and we knew it while we were considering them. They had a certain legibility in the current moment, a fluency in the language of the ecosystem we were building within. But they aged badly even in the imagination. You could feel them becoming dated as you said them. You could see them in a museum of early internet-adjacent naming conventions, next to things that felt very urgent in the year they were coined.

Technology names also do something subtly wrong for infrastructure: they put the emphasis on the mechanism rather than the purpose. They say “this is how it works” rather than “this is what it is and why it exists.” And for something like what we were building, the how is genuinely secondary. The how is important — the onchain nature of it is what makes the permanence real, what makes the ownership real — but the how is not the identity. The identity is the what and the why.

We walked away from the technical names fairly quickly.

The institution plays

This is the category that held us longest, and also the category that eventually gave us our answer.

We looked at names that had the weight of institutions. Names that sounded like they had been around for a long time, or were designed to be around for a long time. Names borrowed from the vocabulary of organisations that society depends on and doesn’t question: archives, registries, councils, trusts, records offices.

These names had an interesting quality. They communicated legitimacy without claiming it explicitly. They didn’t need to explain themselves. When you hear a name that sounds institutional, you don’t reach for context — you simply accept that the institution exists and has a purpose. There’s an assumption of longevity built into the vocabulary.

We found this compelling, but also dangerous in a specific way: institutional names can tip into bureaucracy. They can suggest slowness, inaccessibility, formality for its own sake. And while we wanted to communicate weight and permanence, we didn’t want to communicate distance. The whole point of this project is that it gives something directly to people. It puts ownership in the hands of individuals. It decentralises something that has historically been centralised. An overly institutional name would tell the wrong story about who holds the power in this system.

We needed something that had institutional weight but human purpose.

The action plays

We briefly explored names built around verbs. Names that felt like motion, like claiming, like staking. Names that said: this is what you do here.

These are popular in certain spaces, and for good reason — they’re energetic, they’re memorable, they imply agency.

But for infrastructure, verbs create a problem. Infrastructure is not primarily experienced as an action. You don’t interact with infrastructure continuously; you rely on it constantly. The relationship is not one of doing but one of having, of knowing something is there. A verb-based name would have been appropriate for a marketplace, for a tool, for something people actively use. What we built is something people actively own. That’s different.

Ownership is a state, not an action.

The conversation that changed direction

At some point in the naming process — and we don’t mean this dramatically, it was genuinely just a conversation, the kind that happens when people have been thinking hard about something for long enough that the right thought eventually surfaces — someone said something that reoriented everything.

The point they made was this: we were approaching the naming question as a branding problem. We were asking “what sounds right?” and “what will people remember?” and “what doesn’t date?” All legitimate questions, but they’re the questions you ask when you’re naming something you want people to choose. We weren’t trying to get people to choose us in a crowded market. We were building something that would either be used because it was the right thing for Queensland, or not used because we’d failed to build the right thing. The name wasn’t a selling tool. The name was a declaration.

When you frame it that way, the whole vocabulary shifts.

A declaration doesn’t ask for your attention. A declaration states something. It says: this exists. This is what it is. This is what it’s for. Take it or leave it, but don’t misunderstand it.

We needed a name that was a declaration.

That conversation ruled out half the remaining candidates immediately. Anything that felt like it was trying to be noticed was suddenly the wrong shape. Anything that felt like it was positioning against competitors or angling for a market moment was disqualified. We weren’t in a market. We were building a foundation.

And there it was.

Why “Foundation” is not a metaphor

When you hear the word foundation, you may hear a metaphor. You may hear it the way it gets used in company names across every industry — loosely, aspirationally, to suggest groundedness without actually being grounded in anything. “Foundation” as branding shorthand for “we take this seriously.”

That’s not what it means here. Or rather — that meaning is available, but it’s not doing the primary work.

A foundation, in the architectural sense, is the part of a structure that exists entirely so that other things can exist. It doesn’t serve any purpose by itself. It has no experience from the outside; you don’t look at a building’s foundation and admire it. You don’t know it’s there unless something goes wrong, or unless you’re building. Its entire value is structural. Its entire purpose is to hold.

That is exactly what we built.

We built the part that exists so that other things can exist. The onchain TLDs — .queensland, .qld, .brisbane, .surfersparadise, .gold-coast, .brisbane2032 — are not end products. They are infrastructure. They are the permanent layer on which addresses get built. They are the substrate. The soil. The ground under the structure.

The people who own addresses on this infrastructure are not customers in the traditional sense. They are not subscribers. They are people who have put something permanent into a permanent layer. They own a piece of the foundation in the literal sense: they hold something in it, inscribed on it, recorded on it forever.

So when we say “Foundation,” we’re not reaching for gravitas. We’re describing the architecture. We’re telling you exactly what this is.

What “Queensland” does in the name

The pairing of “Queensland” with “Foundation” is not incidental. Each word does work that the other can’t.

“Foundation” alone would be abstract to the point of emptiness. Whose foundation? For what? Toward what end? “Foundation” by itself is a philosophy, not an identity.

“Queensland” grounds it. Instantly. Unambiguously. Without explanation.

Queensland is not a vague place. It is not a marketing construct. It is a specific geography, a specific community, a specific culture — one of the most recognisable regions in Australia and, in many respects, the world. It has its own character, its own pace, its own relationship to landscape and climate and history. When you say “Queensland,” people know what you mean. Not just Australians — people who have never set foot in the country.

Attaching “Foundation” to “Queensland” does something interesting: it says this permanent, structural thing belongs to this specific place. It is not a neutral piece of infrastructure that Queensland happens to be using. It is Queensland’s infrastructure — built for it, shaped by it, permanently associated with it.

There is also something in the pairing about reciprocity. Queensland gives the Foundation its meaning and its territory. The Foundation gives Queensland a piece of permanent digital infrastructure that it didn’t have before. Each is doing something for the other. The name captures that relationship.

The weight of permanence in a name

We’ve thought a lot about what it means to name something permanent.

Most names don’t need to be permanent. Most things aren’t. The median lifespan of a technology company is short. The median lifespan of a startup is shorter. The median lifespan of a brand, in the modern era of rapid identity refreshes and constant repositioning, can be measured in years rather than decades. We live in a naming culture shaped by impermanence — names that are designed to be energetic now, because there’s an implicit assumption that the thing will be different soon.

We’re working against that assumption by design.

The addresses issued on this infrastructure do not expire. They cannot be revoked. They are permanent. The infrastructure itself is permanent. The whole value proposition rests on the idea that ownership here means something different from ownership in the conventional digital sense — that when we say you own this, we mean it in a way that most digital ownership statements don’t mean.

If the thing is permanent, the name should feel permanent.

We tested candidates against a simple question: how does this name feel in fifty years? Not “will people still understand it?” but more specifically, “does it have the shape of something that belongs in the historical record?”

Most clever names fail that test. Most energetic names fail that test. Most technical names fail it spectacularly. “Queensland Foundation” passes it — not because it’s exciting, but because it has the kind of plain, factual accuracy that ages gracefully. You could encounter it a hundred years from now, knowing nothing about its origin, and still understand what it is. It is the foundation of Queensland’s onchain geography. There is nothing to decode.

The things we gave up by choosing this name

We want to be honest about the tradeoffs, because there were some.

“Queensland Foundation” is not an exciting name. It doesn’t spark. It doesn’t have the kind of linguistic energy that makes people share things or remember things viscerally. In a world where names are increasingly required to do viral work — to function as their own marketing, to be inherently shareable — we chose something that does none of that.

We chose a name that sounds like it belongs in a government registry or a historical archive. That’s not an accident, and we don’t regret it, but it’s worth acknowledging that this choice has costs. We are not going to win any naming awards. We are not going to have our brand identity discussed in design publications.

What we get in exchange is something we valued more: weight.

There’s a kind of trust that comes from a name that doesn’t try too hard. When something sounds like it’s been there for a while — even when it’s new — people relate to it differently. They bring different assumptions. They don’t wonder whether it will still be here next year, because the name doesn’t have the shape of something that would only last next year.

For infrastructure, that trust is load-bearing. It’s not an aesthetic preference. It’s a functional requirement. If you’re asking people to put something permanent into a system, the name of the system has to support the weight of that permanence. “Queensland Foundation” does that. A clever pun would not.

What we learned about naming by doing it wrong first

We went down a lot of wrong paths before we found the right one. We’re glad we did.

The wrong names taught us things. Each one we rejected — for being too clever, too technical, too geographic, too action-oriented — refined our understanding of what the right name needed to be. It’s a process of elimination that is also a process of discovery. You learn what you’re building by learning what it isn’t.

We learned that we weren’t building a brand. We were building a record — something that needed to exist on the same register as place names and public institutions rather than on the same register as apps and services.

We learned that we cared more about legibility than memorability. A memorable name is valuable when you’re competing for attention. A legible name is valuable when you’re building something that needs to explain itself truthfully across decades.

We learned that the name had to carry the mission without explaining it. This was the hardest constraint to hold. It rules out anything descriptive (“Queensland Onchain Registry” would be accurate but lifeless). It rules out anything aspirational (“Queensland Futures” would point forward but say nothing about what the thing is). It demands a name that is the thing, not a name that describes the thing or hopes for the thing.

“Queensland Foundation” is the thing. That’s the whole of why we chose it.

On the burden of carrying a place name

We’ve spoken to people who wonder whether it’s appropriate — whether it’s too much — to put the name of a place into the name of a project. Whether “Queensland” belongs to anyone’s infrastructure project, or whether using it implies something official, something governmental, something that hasn’t been endorsed.

We take that question seriously. We thought about it carefully.

Our view is this: the name of a place belongs to the people of that place. It is not owned by any government or any institution. It is a word in the public language, used freely and appropriately by anyone who is genuinely building for that place, of that place. Businesses, organisations, sports teams, community groups, publications — all of them use place names as part of their identity, and there is nothing inappropriate in that, provided the association is honest.

Our association is honest. We are building permanent onchain infrastructure for Queensland. We are not co-opting the name for something unrelated. We are not using “Queensland” to borrow legitimacy for a project that has nothing to do with the place. The project is the place, in a very real sense. The six TLDs — .queensland, .qld, .brisbane, .surfersparadise, .gold-coast, .brisbane2032 — are Queensland’s place names. They are the digital toponymy of Queensland, permanently recorded onchain.

Putting “Queensland” in our name is not a claim of ownership over the word. It’s a statement of purpose. It says: this is what this is for.

Names as commitments

Here is something we’ve come to believe: naming is not just identity. Naming is commitment.

When you name something, you are making a statement about what it is. And that statement constrains you. It constrains what you can become, what you can do, what is consistent with your identity and what would contradict it. A good name is a kind of promise — not just to the people who use what you’ve built, but to yourself and your team. It keeps you honest. It reminds you, when things are complicated, what you said this was.

“Queensland Foundation” commits us to building something that deserves to be called a foundation. Every time someone encounters that name and gives us a measure of trust, we are reminded that we have to earn it by behaving like a foundation — by being structural, by being permanent, by being something others can build on without worrying that the ground will shift beneath them.

That accountability is not incidental. We wanted it. We chose a name that would hold us to the mission not just at the start, when everyone is energised and aligned, but across time, when circumstances change and it would be easier to drift.

A name that doesn’t constrain you isn’t doing its full job.

The morning we stopped arguing

There was a specific morning when we stopped arguing about the name.

We’d been going around in circles for a while — not because we disagreed dramatically, but because none of us was fully convinced that any option was obviously right. We were in the territory of “probably fine” for several candidates, and none of us wanted to settle for probably fine on something this fundamental.

Then someone said, simply: if we built this thing and then handed it to history — if we put it in a time capsule and imagined someone finding it in the distant future and trying to understand what it was — which name would make the most sense without any surrounding context?

That reframe cut through everything.

Most of our remaining candidates relied on context. They relied on knowing what year it was, or knowing something about the blockchain space, or knowing some piece of Queensland cultural shorthand that might not survive translation across time. They were names that made sense now. “Queensland Foundation” was the only name that would make sense always.

That was the morning we stopped arguing.

Not with great fanfare. Not with a collective exhale and a sense of things clicking into place. Just quietly, the way decisions settle when you’ve finally found the thing that was always going to be the answer — you look at each other and there’s nothing left to argue about.

What we hope the name does

We hope it does the thing good infrastructure names do, which is nothing dramatic.

We hope it sits quietly in the background while everything built on it does its work. We hope that when people encounter it for the first time, they don’t need to be told what it is — that something in the name itself communicates the nature and purpose of the thing.

We hope that in a long time from now, when the project has done what we believe it can do, the name will look like the only name it ever could have been. That’s the mark of a right decision: in retrospect, it looks inevitable.

We hope it carries weight without straining under it.

We hope people feel, when they see their Queensland address paired with this name in their wallet or their profile or wherever they choose to put it, that they are holding something serious — something that was built carefully, named carefully, and is going to be here.

We almost called it something else.

We’re glad we didn’t.