The word we kept coming back to

Every project has a name, and most names are chosen quickly. A word sounds right, a domain is available, someone nods, and that’s it. The name gets printed on things and after a while it stops meaning anything at all — it just becomes a label, a handle, a thing to put on a logo.

We didn’t want that.

When we were working out what to call this project, we kept circling back to the same word. Not because it was the obvious choice, or because it tested well, or because some branding exercise spat it out. We came back to it because every time we tried to describe what we were actually building — what we actually believed about it — the word kept showing up. We’d use it in sentences without realising. We’d write it in notes and then look at it later and think: there it is again.

The word was foundation.

And the more we sat with it, the more we realised it wasn’t just a name. It was a description of intent. It was a quiet promise about how we would behave, what we would build, and what we expected of ourselves. It was the right word not because it sounded good, but because it was true.

So we want to take some time here — real time, not a tagline — to explain what that word means to us. What we think about when we say it. What it asks of us. What we hope it signals to the people who use what we’ve built and the people who will build on top of it.

Because a name shapes a culture. And we think it’s worth being honest about what culture we’re trying to shape.

Foundations of a building

Start with the literal thing. A foundation, in the oldest and most physical sense of the word, is what goes in the ground before anything else. It’s the part nobody sees. It’s dug before the walls go up, before the roof goes on, before anyone looks at the building and says that’s beautiful or that’s home. The foundation is invisible by the time the building is finished, and that’s exactly the point.

We think about this a lot.

When you pour a foundation, you’re not thinking about what the building will look like from the street. You’re thinking about load. You’re thinking about what the soil does in wet weather and dry weather. You’re thinking about what happens if the ground shifts slightly, and slightly again, over decades. You’re thinking about how to make something that will still be solid when no one who poured it is alive anymore.

There is nothing glamorous about this work. The people who pour concrete foundations are not celebrated. They don’t get to stand at the end and say: I made this. Someone else builds the walls. Someone else puts in the windows. Someone else hangs the art and fills the shelves and calls it theirs. The people who poured the foundation just move on to the next site.

And yet.

Without that work — without the unglamorous, invisible, deeply considered work of getting the foundation right — nothing that comes after holds. The beautiful rooms collapse. The careful details crack. The thing that was supposed to last a generation or two crumbles in decades instead of centuries. Every shortcut taken at the foundation level is paid for by everyone who comes after. Every corner cut in the ground becomes a fault in the wall fifty years later.

This is the standard we hold ourselves to. Not because it sounds noble, but because it’s the honest consequence of choosing this word. If we call ourselves a foundation, we are making a claim about the quality of what goes in the ground. We are saying: we have thought about the load. We have thought about the wet years and the dry years. We have thought about what happens if things shift. We are not building the beautiful rooms — or not yet, and not only — we are making sure the ground holds.

That is a different kind of ambition than most technology projects admit to. Most technology projects want to be the beautiful rooms. They want to be what people see and use and share and love. And there’s nothing wrong with that. The rooms matter. But someone has to care about the foundation, and if nobody does, the rooms don’t last.

We care about the foundation.

What permanence actually means

There’s a version of the word permanent that people use loosely, and we want to distinguish it from the version we mean.

Loosely: permanent means for a long time or for the foreseeable future or until we change it. Most things described as permanent are actually just sticky. They’re hard to undo, or they’re inconvenient to change, or the company behind them hasn’t found a reason to change them yet. But there is always a company behind them. There is always a decision that could be made. There is always a moment when that company gets acquired, or runs out of money, or changes strategy, or simply decides that the old product no longer serves the new direction. And then the thing that was permanent stops.

We mean something different.

The addresses we’ve helped bring into existence — the .queensland addresses, the .qld addresses, the .brisbane and .surfersparadise and .gold-coast and .brisbane2032 addresses — are permanent in the harder sense. They’re not permanent because we say so. They’re not permanent because we’ve committed to keeping the servers running or the company solvent or the team intact. They’re permanent because they exist on infrastructure that doesn’t depend on us continuing to exist. They’re recorded on a chain that doesn’t require our permission to persist. Once they’re minted, they’re there. They belong to whoever owns them. Full stop.

This is worth sitting with, because it’s genuinely unusual. We’ve grown so accustomed to renting our digital identities — to paying annually for domain names, to having accounts that can be suspended, to owning usernames on platforms that can deactivate them — that we’ve almost forgotten the alternative exists. We treat digital ownership as inherently provisional. You have it until you don’t renew, or until the platform changes its policies, or until the company folds.

What we’ve built rejects that model at the foundation level. An address on this infrastructure is owned the way land is owned, not the way a lease is signed. You buy it once. You hold it. You pass it on if you choose. Nobody can take it because nobody has the authority to take it — not us, not a government, not a future company that acquires whatever company we eventually become. The ownership is structural, not contractual.

This changes how people relate to their digital address. We’ve seen it, and it makes sense. When you know a thing is truly yours — truly permanent — you treat it differently. You think about what it means. You think about what you want it to say. You think about whether you want to pass it on one day. You stop thinking about it as a product you’re subscribing to and start thinking about it as something you own.

That shift — from subscriber to owner — is one of the quiet things we were trying to make happen.

The foundation as infrastructure

There’s another way to understand the word foundation, and it’s the one that lives closest to how engineers and architects talk. Not the physical concrete in the ground, but the foundational layer of a system. The layer that everything else depends on without needing to know the details of.

When you turn on a tap, you don’t think about the pipe network under the city. When you flip a switch, you don’t think about the grid. When you send a message, you don’t think about the protocols running underneath the protocol. These things are infrastructure. They are foundational in the technical sense: they make everything else possible, and their design determines what’s possible above them.

This is the domain we’re operating in.

An onchain address is infrastructure. It’s not the product someone builds on top of it — it’s the layer that product sits on. It’s the thing that says: this identity is real, it’s verified, it belongs to this person, and it will be here tomorrow. When a developer builds an application that needs to know who a user is, or where to send something, or how to address a transaction to a person rather than a string of random characters — they reach for the infrastructure layer. They reach for the address.

By securing six permanent onchain TLDs for Queensland, we’ve been involved in laying infrastructure. Not the applications. Not the services. Not the products that people will use in ways we can’t predict yet. The infrastructure. The layer that makes those things addressable and possible.

This is also, by the way, why the price is set where it is. Five dollars, once, for life. We made that choice not as a marketing decision but as an infrastructure decision. Infrastructure that only wealthy people can access isn’t really infrastructure. Infrastructure that requires ongoing payments isn’t really ownership. If the foundational layer is going to be genuinely foundational — genuinely available to anyone in Queensland who wants a permanent address — it has to be accessible. The price point is a design choice rooted in values, not in what the market would bear.

We could have charged more. The technology doesn’t change at a lower price point. The permanence doesn’t diminish. But the meaning of the word foundation would have changed, because a foundation that only some people can access isn’t really carrying the weight it claims to carry.

Foundations as organisations

There’s a third meaning, and it’s the most human one.

A foundation, in the organisational sense, is an institution built for the long term. It’s not a startup chasing growth. It’s not a company optimising for quarterly returns. A foundation is built around a mission — something it believes is worth doing for its own sake, over a time horizon that extends beyond the people currently running it. Foundations plant trees they won’t sit under. They make decisions that don’t pay off for a generation. They accept that the measure of their success might not be visible until long after the people who started them are gone.

This model appeals to us deeply, and not in an abstract, aspirational way. In a concrete way that shapes how we make decisions.

When you run something that’s optimised for near-term outcomes, every decision gets measured against the same question: does this help us grow faster, sooner? That’s not a bad question. But it’s not the only question, and it can crowd out more important ones. It can crowd out: does this hold? And: is this right? And: what will someone who uses this thing in thirty years think of the choices we made at the beginning?

Those are the questions a foundation asks. Or should ask. Or, at least, that we try to ask.

We think about the person who buys a .queensland address today and hands it to their kid twenty years from now. We think about the developer who builds something on this infrastructure and needs to know it’ll still be there in a decade. We think about the small business in regional Queensland that sets up an onchain address and uses it as the permanent foundation of their digital presence — not because they understand the blockchain, but because someone told them it would be there forever and they believed it.

These are not abstract users. These are people whose trust we’re asking for. And trust — real trust, not the kind you earn with slick UX and good copywriting, but the kind that holds under pressure over years — is only built by behaving like a foundation. By making decisions that make sense over long time horizons. By not taking shortcuts in the ground.

The weight of the word

We want to be honest about something: choosing a name like this is a form of accountability.

When you call yourself a foundation, you are inviting a particular kind of scrutiny. People will notice — consciously or not — when your behaviour is inconsistent with what the name implies. They will notice if you optimise for the short term when the name suggests a long horizon. They will notice if the infrastructure isn’t solid, if the permanence isn’t real, if the organisation starts making decisions that feel like a company trying to extract value rather than an institution trying to build it.

We chose this name knowing that. We chose it partly because it creates accountability. Because we wanted to be held to a standard that we couldn’t easily wriggle out of. Because naming something is a commitment, and we wanted to be committed.

There’s a version of this project where we called it something exciting and flexible. Something that could mean whatever we needed it to mean as the strategy shifted. Something that gave us room to pivot. We didn’t want that room. We didn’t want a name that gave us an out. We wanted a name that told us clearly what we had to be.

Foundation.

And when we’re making decisions — about pricing, about governance, about what features to build and which to leave alone, about how to respond when something doesn’t go as planned — the name is genuinely in the room with us. Not as a slogan. As a standard.

Does this decision hold? Does it carry weight? Is this the kind of thing a foundation does?

Sometimes the answer is uncomfortable. Sometimes the right decision for the long term is not the easy decision in the moment. Sometimes being a foundation means accepting slower growth, or less revenue, or more complexity, because the alternative would be a shortcut in the ground.

We accept that.

Queensland, specifically

We want to say something about the geography here, because it matters and because the meaning of foundation bends slightly when you hold it against a specific place.

Queensland is not a small place. It’s enormous — geographically, ecologically, economically, culturally. It is a place of extraordinary range, from the dense subtropical energy of Brisbane to the quiet coastlines of the far north. It has industries that are the backbone of entire regions, and communities that are defined by place in a way that urban centres sometimes aren’t. It has an identity that is real and particular and not reducible to a postcode or a tourism slogan.

It also, like every place, is navigating a future that is increasingly digital. The question of how a place maintains its identity in a digital world — how it refuses to be homogenised, how it remains itself even when the platforms and protocols it operates on are global and owned elsewhere — is not a small question. It is, in fact, a foundational one.

We think the addresses we’ve helped secure are part of an answer to that question. Not the whole answer. Not by themselves. But part of it. When a Queenslander owns a .queensland address, they own something that says: I am here. This is where I’m from. This is mine. When a Brisbane business builds on a .brisbane address, they are planting a flag in digital space that is specifically, permanently theirs and specifically, permanently here.

This is not nationalism. It’s not parochialism. It’s just what it looks like when a place refuses to have its digital identity be abstract and generic and owned by someone else. It’s what it looks like when the infrastructure reflects the community it serves.

And if the word foundation carries weight in the context of a building, or a system, or an organisation — it carries a different, slower, older weight in the context of a place. The foundations of a community are the things that hold it together across generations. The stories, the land, the names, the shared sense of what this place is and why it matters. We think permanent onchain addresses can be part of that. Not because we’ve decided they should be, but because we’ve listened to what people do with them, and we’ve seen what it means to someone when they own a piece of digital infrastructure that is genuinely, permanently theirs and genuinely, permanently here.

On building for others to build on

There’s something we’ve had to make peace with, and it’s worth naming.

Most of what we build will be invisible. Most of the value we create will be created by other people, using what we’ve laid. We will not be the ones making the beautiful things. We are the people who poured the concrete, and the concrete is already buried.

This is fine. More than fine — it’s the right shape of ambition for what we’re doing.

We’re not trying to build everything. We’re trying to build the thing that makes it possible for others to build anything. The difference matters enormously, and it shapes decisions all the way down.

If you’re building a product, you make choices based on what the product needs. If you’re building infrastructure, you make choices based on what the widest possible range of builders might need, now and in the future. You make things more open than you need to for your immediate purposes. You make things more durable than the immediate use case demands. You resist the temptation to lock things in ways that serve you now but limit others later. You accept that the infrastructure will be used in ways you can’t predict and probably wouldn’t have designed for.

This is a different kind of discipline. It requires a kind of generosity that doesn’t always feel natural in a competitive environment. It requires trusting that the right thing to do is to make the foundation as good as it can be, and then let go.

We trust that. We don’t always find it easy, but we trust it.

What we owe the word

We’ll end here, with something direct.

We did not choose the word foundation lightly, and we don’t hold it lightly. We understand that it’s a claim — a specific, weight-bearing claim about what we are and how we behave. We understand that it creates expectations we’re responsible for meeting. We understand that if we behave inconsistently with what the word implies, the word doesn’t protect us — it indicts us.

We know what it means for something to be foundational. We know what it looks like when foundations are done properly and what it looks like when they’re done cheaply. We’ve seen infrastructure built to last and infrastructure built to look like it lasts. We know the difference, and we’ve tried to be honest with ourselves about which one we’re building.

The permanence is real. The addresses don’t expire. They can’t be taken. They belong to whoever holds them, and that ownership is structural, not provisional.

The accessibility is real. The price is not a token gesture — it is a design decision rooted in a belief that foundational infrastructure should be available to everyone, not just those with the budget for it.

The long horizon is real. We’re not building for the next product cycle. We’re building for the person who’ll be using this infrastructure in a context we can’t imagine yet, for a purpose we haven’t thought of, in a Queensland that looks different from the Queensland we know now.

Foundation. It’s not just a name. It’s the whole story told in a single word — the weight of the ground under everything, the discipline of the invisible work, the time horizon of something built to last.

That’s what we mean when we say it. That’s what we hold ourselves to. That’s the standard we chose when we chose the word.

And we chose it knowing full well that choosing a word like that means you have to become it.

We’re working on that. Every day.