The Question We Keep Coming Back To

There is a question we have asked ourselves more times than we can count, and it goes something like this: if we disappeared tomorrow — if the team dissolved, the company folded, the funding dried up — would what we built still be standing?

For most of the history of software, the honest answer to that question is no. Products live and die by the companies behind them. Services shut down. Databases get deleted. Domain names expire. The thing you built your life around, the address you gave to people, the digital identity you spent years cultivating — all of it can vanish the moment the organisation behind it decides it’s no longer worth running.

We didn’t want to build something like that. We didn’t want to create something whose survival depended on us continuing to exist, continuing to care, continuing to have money in the bank. We wanted to build something that, once it existed, would simply keep existing — regardless of what happened to us.

That’s the founding impulse behind Queensland Foundation. And it’s worth spending some time sitting with what that impulse actually means, because it isn’t just a technical preference. It’s a philosophy. It’s a set of beliefs about what building is for, what permanence actually costs, and what we owe to the people who trust us with something as fundamental as their identity.

What Permanence Actually Means

The word “permanent” gets thrown around a lot in technology, and it almost never means what it says. Permanent usually means “for the foreseeable future.” It means “until the business model changes.” It means “as long as we’re around.”

We mean it differently.

When we say the addresses on Queensland Foundation are permanent, we mean they exist on a blockchain — an infrastructure that is decentralised, distributed, and not controlled by any single entity, including us. We mean that the record of ownership is written into a ledger that no one can selectively edit or delete. We mean that an address, once registered, does not expire. There is no renewal. There is no annual fee. There is no relationship you need to maintain with us to keep what is yours.

You pay once. You own it. It’s yours for life.

That is not a marketing phrase. It’s a description of the technical and philosophical architecture of the thing. The permanence is built into the structure, not promised by the people. And that distinction matters enormously.

Think about what it means to own a traditional domain name. You are not really buying the name. You are renting it from a registrar, who is themselves leasing authority from a registry, which operates under a contract with ICANN, which is a non-profit corporation operating under an agreement with the United States government. There are four layers of dependency between you and your address. Any one of them can fail, change their policies, get acquired, face regulatory pressure, or simply decide that your particular name isn’t worth their administrative overhead anymore. The moment any one of those layers breaks, so does your claim to your own identity.

We are not that. We are the opposite of that. We built something where the layers of dependency are as few and as durable as possible — and where the most important layer, the ledger itself, is not ours to control.

That’s what permanence actually means. Not a promise. A structure.

The Long Arc of Things We Build

Human beings have always built things meant to outlast themselves. It is, in some ways, the defining impulse of civilisation. Cathedrals. Aqueducts. Libraries. Roads. Legal systems. Languages. These are things that were built — by people with names, by people with agendas, by people who had no idea how long their work would last — and that continued long after those people were gone.

There is something humbling about that tradition. When you stand in a building that is four hundred years old, you are not thinking about the architect. You are using the building. The building is doing its job. The architect’s name might be on a plaque somewhere, but the building itself doesn’t need the architect to keep existing. It exists because it was built well, from materials that last, in a form that serves a purpose people continue to have.

That’s the model we keep returning to. Not the startup model — build fast, iterate, scale, exit. Not the platform model — acquire users, extract value, maintain leverage. The older model. The one where you build something that serves a genuine human need, you build it as durably as you can with the materials available to you, and then you step back and let it do its work.

In our case, the material is code. The structure is a blockchain. The purpose is identity — the ability of Queenslanders to own a piece of their place in the digital world, tied to the geography they actually live in, that they can hold onto forever without asking anyone’s permission.

We are not the first people to think about permanence this way. But we may be among the first to have the technical tools to actually build it into the foundation rather than just promise it from the top.

Why Identity Deserves Permanence

Let’s talk about why this matters for something specifically like a digital address.

Your address — your name, your location, the handle by which you are known — is not a product. It’s not a service. It is your identity. It is the thing people use to find you, to send things to you, to remember you. It is, in the digital world, closer to your name than it is to your phone number.

And yet for most of digital history, we have treated digital addresses as though they were rental properties. You occupy them at the pleasure of a landlord. You pay rent, and if you stop paying, the landlord can rent them to someone else. The address doesn’t belong to you — it belongs to the system, and you are just the current occupant.

We find this arrangement genuinely strange when you think about it long enough.

Imagine if your name worked this way. Imagine if you had to pay an annual fee to keep your name, and if you missed a payment, someone else could take it, use it, profit from it. The absurdity is obvious. Your name is yours. It is not a service someone provides to you.

A digital identity should work the same way. It should be something you own, not something you rent. It should be tied to you in a way that no third party can dissolve without your consent. And it should be permanent — not because someone promises it will be, but because the structure makes it so.

This is why we chose to build on blockchain infrastructure. Not because blockchains are fashionable, not because we wanted to be in the crypto conversation, but because the blockchain is the first technology that genuinely allows ownership — real ownership, not rental dressed up as ownership — of a digital asset. The record of your ownership is in the ledger. The ledger is not ours. If we disappeared, the ledger would still be there, and your record would still be in it.

That’s the thing that changes everything. Not the technology for its own sake. The ownership model that the technology makes possible.

Building for Someone You’ll Never Meet

Here is one of the stranger thoughts that comes with building for permanence: you are building for people who do not yet exist.

If we build this well — if the infrastructure is sound, if the design is durable, if the underlying blockchain continues to function — then people will be using these addresses long after the current version of this team has moved on, aged, or died. Someone will own a .queensland address in fifty years and will have no knowledge of, or interest in, who built the system they’re using. They will simply be using it, the way we use roads without thinking about the engineers who designed them.

That is a strange kind of responsibility. It is not the responsibility you feel toward a customer you can see and talk to. It is a responsibility toward an abstraction — toward future people, toward the integrity of a system over time, toward a promise you make to people who cannot yet hold you to it.

We think about this a lot. It changes how you make decisions.

When you are building for the short term, for the next product cycle or the next funding round, you can make compromises. You can ship something that works well enough for now and fix it later. You can promise things that you’ll worry about keeping when the time comes. You can optimise for the metric that matters this quarter without thinking too hard about what happens to the system in ten years.

When you are building for permanence, that calculus shifts entirely. The compromises you make now are baked into the structure. The promises you make now are the foundation other things get built on. The decisions you take today will still be doing their work long after you’re in a position to correct them.

This is not a comfortable way to build. It is slower. It requires more honesty about your own limitations. It requires admitting that you might be wrong about something and building in a way that accounts for that possibility. But it is, we believe, the right way to build something that genuinely serves people over time.

What Decentralisation Actually Demands

There is a certain romance around the word “decentralised” in technology circles, and like most romance, it obscures as much as it reveals. Decentralisation is not just a technical property. It is a commitment, and it is one of the most demanding commitments a builder can make.

Here is what it means in practice: when you build on decentralised infrastructure, you are voluntarily giving up control. You are choosing a system where you, the builder, cannot intervene in the way that centralised builders can. You cannot reverse a transaction you disagree with. You cannot delete a record you find inconvenient. You cannot change the rules unilaterally because your circumstances have changed. The system operates according to the rules built into it, not according to your current wishes.

That is a genuinely radical act of institutional humility. It is saying, in structure: we do not trust ourselves with unlimited control over this system, and neither should you. We have chosen to build something where the rules are not ours to bend.

Most organisations are not built this way. Most organisations, even those with good intentions, retain for themselves the ability to change the rules. They have terms of service that can be updated. They have backend systems that an admin can access. They have the technical and legal ability to intervene in the operation of their product whenever they choose. This is, in many ways, convenient. It is also a single point of failure. It means the durability of the system is limited by the durability of the organisation’s intentions and capabilities.

We chose differently. We chose a model where the durability of the system does not depend on our continued good intentions. The rules are in the code. The code is on the chain. The chain is not ours. This is not a constraint we find limiting — it is the whole point. It is the mechanism by which we make our commitment to permanence credible rather than aspirational.

There is also something important about what this choice says to the people who use the system. When you buy an address through Queensland Foundation, you are not trusting us. You are trusting the infrastructure. You are trusting the mathematics and the distributed consensus mechanism and the economic incentives of a decentralised network — none of which require us to be competent or honest or solvent to keep functioning. Your ownership does not depend on our continued goodwill. It is, in the deepest technical sense, independent of us.

We believe this is what genuine trust looks like. Not “trust us, we’re good people.” But “here is a structure that does not require you to trust us at all.”

The Ethics of Building Things That Can’t Be Undone

Immutability is a double-edged concept, and we would be dishonest if we didn’t acknowledge that.

When records are permanent and transactions are irreversible, you are making a bet that the rules you’ve encoded are good rules. You are accepting that you cannot correct your mistakes by deleting the record of them. You are building a structure that will outlast your ability to change it, which means the responsibility you carry at the moment of building is unusually heavy.

This is one of the reasons we approach what we do with a degree of seriousness that might seem disproportionate to outsiders. These aren’t app features we can roll back in a hotfix. These are foundational decisions that will be present in the structure of the system for as long as the system exists.

We ask ourselves hard questions because of this. What does it mean to permanently record ownership of something? What does it mean to have a system that cannot be corrected if a mistake is made? What obligations does that create for us at the design stage?

We don’t have perfect answers to these questions. No one does. But we believe the act of asking them — seriously, repeatedly, with a willingness to sit with discomfort — is itself part of what it means to build responsibly. Immutability is not a feature to be proud of in a vacuum. It is a feature that carries obligations. It demands that you get the foundations right, because you do not get unlimited chances to revise them.

The flipside of this is the extraordinary gift it gives to the people who use what you build. When your ownership is permanently recorded in a ledger that no one controls, you are not dependent on anyone’s continued goodwill to assert that ownership. The record is simply there. It cannot be revised away for someone else’s convenience. It cannot be disputed by a company that has changed its policies. It cannot be lost in a database migration or a corporate restructure. It is yours in a way that nothing in the history of digital identity has previously been yours.

That is worth the difficulty. It is worth the care. It is worth every hard question asked and every compromise refused.

Queensland as a Place Worth Rooting Things In

We should say something about why this matters in a specifically Queensland context, and not just as an abstract philosophical exercise.

Queensland is a place with a distinct identity. It has a geography — the coast, the hinterland, the tropics, the subtropics, the enormous distances and the particular light. It has a character — outdoor, independent, a little rough around the edges, proud of being different from the southern cities. It has a relationship with the future — a city preparing for a global stage, a region that is increasingly aware of its place not just in Australia but in the world.

And yet when Queenslanders move into digital space, they have historically had no way to carry that identity with them. The address system they’ve used has been global and generic — .com, .net, .au — shared with everyone, owned by no one, connected to no particular place.

We believe that should change. We believe that digital identity should be able to be as specific and as rooted as physical identity. That a person from Brisbane should be able to have an address that says so, permanently, without qualification. That a business on the Gold Coast should be able to hold that identity in the same immutable way they hold the title to their premises. That the Surfers Paradise community, and the Queensland community, should be able to exist in digital space with the same permanence and specificity that they exist in physical space.

This is why we chose these particular names — .queensland, .qld, .brisbane, .surfersparadise, .gold-coast, .brisbane2032. Not because they are commercially convenient. Because they are real. They are the names of real places that real people are from, real communities that real people belong to. We wanted to take those names — as they exist in the physical world, with all their weight and history and meaning — and make them available as permanent digital identities that Queenslanders can own.

There is something about anchoring a digital identity to a real place that we find genuinely important. It connects the digital world to the physical one in a way that .com and .xyz and .io simply don’t. Your address means something about where you are from, what community you belong to, what your roots are. That’s not a trivial thing. It’s a significant part of how human identity works — and digital identity should be able to reflect it.

The Price of Entry and What It Signals

We want to be honest about something that might seem like a commercial detail but that we think of as a philosophical statement.

The addresses start at five dollars. Paid once. No renewals. No annual fees. Ever.

We set the price this way deliberately, and not primarily for commercial reasons. We set it this way because we believe that permanent digital identity should not be a luxury. It should not be something only well-funded businesses can afford. It should not be something that people lose when their circumstances change and they can’t afford the renewal.

If permanence is real, it has to be accessible. Otherwise it is just a product feature for the wealthy, and the promise of permanence becomes just another way of sorting people into those who can maintain a digital identity and those who can’t.

Five dollars is the cost of a coffee. It is within reach of almost anyone who wants it. And once paid, it is done. There is nothing more to pay, ever. Your address is yours for your life, regardless of what happens to your finances, regardless of whether Queensland Foundation continues to exist, regardless of anything outside of your own choice to hold it.

This feels, to us, like the right way to treat something as fundamental as identity. You should be able to have it. You should be able to keep it. And the price should not be a recurring gate that the world forces you to keep paying to remain who you are.

What This Demands of the Builders

We have been talking about what we built and why. We want to also talk about what building this way demands of us as people, because we think that’s important and often left out of this kind of conversation.

Building for permanence is not comfortable. It does not fit neatly into the rhythms of a modern technology project. The modern rhythm is: ship fast, learn fast, iterate, pivot when necessary. Move quickly and fix things later. Optimise for growth, then worry about durability.

We cannot operate that way, and the reason is the immutability we’ve already described. When what you build is permanent, you cannot fix it later. Later, the thing is still there. Later, the decisions you made are still structural. You carry, from the very beginning, a responsibility that most technology builders are able to defer.

This demands a certain kind of patience. It demands a willingness to think slowly, to refuse conveniences that might seem harmless now but that create dependencies that compromise permanence later. It demands a kind of intellectual honesty that is hard to sustain in an environment that rewards speed and decisiveness — the honesty to say “we don’t know enough about this yet” and wait until you do.

It also demands a particular relationship with your own ego. Building for permanence means, ultimately, building something that will not need you. The goal is to become unnecessary. The goal is to ship something into the world that can exist without your continued attention, without your continued presence, without your continued existence. For people who build things — who are, in many cases, people who draw significant meaning from being needed by what they build — this is a strange and sometimes uncomfortable goal to hold.

But we think it is the right goal. We think the mark of something well-built is precisely that it does not need its builders to survive. The cathedral does not need the architect. The road does not need the engineer. The blockchain does not need the developer. These things exist in their own right, doing their work, serving their purpose, regardless of what happens to the people who made them possible.

That is what we are aiming for. Not dependence. Not lock-in. Not an ecosystem that only works as long as we’re running it. A thing that is real and permanent and complete — that we contribute to and then step back from, trusting that the structure will hold because we built the structure honestly.

The Responsibility of Being First

There is one more thing worth saying, and it is about the particular weight of doing something that hasn’t been done before.

Queensland Foundation holds six permanent onchain TLDs for Queensland. There has been nothing quite like this before — not for this geography, not in this form, not with this combination of permanence, accessibility, and local specificity. We are, in a meaningful sense, building in territory that has not been mapped.

That is exciting. It is also serious. Because when you are doing something for the first time, the way you do it becomes a precedent. The decisions you make, the values you embody, the standards you set — these don’t just matter for your project. They matter for the category of thing your project represents. They matter for what comes after.

We think about this. We try not to let it paralyse us, because the work still has to be done, and done now, with the knowledge and tools available to us now. But we try to let it motivate a certain level of care. If we are setting a precedent, we want to set a good one. We want the things that come after us — if there are things that come after us — to be built on a foundation that deserves to be built on.

This connects back to the original question. We are building for people we will never meet. We are building for a future we cannot see. We are making decisions that will be present in the structure of something long after we are in a position to revise them. The responsibility this creates is not a burden we carry reluctantly. It is, honestly, part of why we do this.

We believe in building things that outlast their builders. We believe it because it is the only way to build something that genuinely serves the people who use it, rather than the people who built it. We believe it because permanence is the only honest form of a promise. And we believe it because the alternative — building things that need you to survive, that exist only as long as your organisation does, that fold the moment your interest or your funding runs out — is not really building at all. It is renting, dressed up as creating.

We are not interested in renting.

We are interested in building something real — something that belongs to the people who hold it, rooted in a place that is real, existing in a structure that is permanent, and needing nothing from us to continue being exactly what it is.

That is what Queensland Foundation is. That is why we built it the way we did. And that is what we believe about building things that are worth building.