The easiest version of this project would have looked very different

We could have built this for tech people. It would have been so much easier.

We could have leaned into the language. Talked about smart contracts, about immutable ledgers, about decentralised infrastructure and onchain identity primitives. We could have launched on the forums where crypto-natives gather, posted in the right Discord servers, and gotten early traction from people who already understood what permanent blockchain addresses meant. We’d have had a launch that looked impressive by the metrics those communities use. We’d have had users who didn’t need hand-holding, who’d already set up wallets before breakfast, who’d spread the word in language that resonated with other people exactly like them.

That version of this project would have been faster to build, faster to launch, and easier to explain to anyone who already lived inside that world.

We chose not to build that version.

That choice — made early, made deliberately, and made with full knowledge of what it would cost us — is what this post is about.

Who we actually built this for

When we picture the person we built Queensland Foundation for, we don’t picture someone who knows what a blockchain is. We picture someone who doesn’t, and doesn’t need to.

We picture a cabinet maker on the Sunshine Coast who’s been running his business under his own name for twenty years. He has a website, or maybe just a Facebook page, and he’s quietly aware that neither of those things actually belongs to him. Facebook could change its algorithm tomorrow. His domain name renews every year and the reminder email always catches him off guard. He’s never thought much about digital identity because it’s never felt permanent enough to think about.

We picture a family in Toowoomba who bought land and built a house there and feel a deep, particular pride in being from somewhere specific. Not from Australia in the general sense, not from Queensland in the abstract — from there. From that region, that town, that street. They want their kids to carry something that represents where they come from.

We picture a market gardener out near Stanthorpe, a surf instructor at Surfers Paradise, a childcare worker in Cairns, a retired teacher in Mackay who helped build her community for forty years and would like, quietly, to have something that reflects that.

These are not people who attend blockchain conferences. These are not people who follow crypto Twitter. They are Queenslanders — ordinary, capable, rooted people — and they are exactly who we built this for.

That sounds simple to say. It is not simple to do.

The problem with building for people who aren’t watching you

When you build for tech-savvy early adopters, you benefit from something that is easy to take for granted: your users already want what you’re making. They’re primed for it. They understand the category before you explain your specific take on it. They’ll overlook friction because they’re motivated enough to push through it. They’ll forgive a confusing UI because they’ve seen worse. They’ll figure out the wallet setup, the gas fees, the network switches — not because it’s easy, but because they’re the kind of people who figure things out for the love of the technology itself.

Ordinary people don’t work like that. And we say that with complete respect, because we think ordinary people are right.

If something is hard to use, ordinary people don’t assume they’re the problem. They assume the product is the problem. If they have to read instructions, they assume something went wrong before they started reading. If a screen asks them a question they don’t understand, they don’t search for the answer — they leave. Not because they’re incapable. Because they have other things to do, other priorities, and no particular reason to invest effort in something that hasn’t yet earned their trust.

This means that everything we build has to do the work that, in other contexts, the user’s own enthusiasm would do.

The product has to be self-evident. The language has to be honest and plain. The process has to feel familiar enough that nobody stops to wonder what’s happening beneath it. The moment someone thinks “wait, is this a crypto thing?” — not in a curious way, but in a suspicious, backing-away way — we’ve already lost them.

And we can’t get them back with a FAQ.

Making the infrastructure invisible

Here is the central paradox of what we’re building.

The infrastructure that makes our addresses genuinely different from everything else that currently exists — the blockchain foundation, the onchain permanence, the immutability, the fact that nobody can take this away or let it expire or change the rules on you mid-game — that infrastructure is the entire point.

And yet, the moment we explain that infrastructure to someone who didn’t come looking for it, we risk making them feel like we’re trying to sell them something they don’t understand. Which is the fastest way to lose anyone’s trust.

So the hardest thing we’ve had to learn — and it is genuinely hard, because it cuts against every instinct you have when you’ve spent a long time living close to technology — is that the infrastructure has to be invisible.

Not hidden. Not obscured. Not dishonest. Invisible in the way that electricity is invisible when you turn on a light. You’re not unaware that electricity exists. You’re not confused about the fact that something is happening. You just don’t need to understand the grid topology, the voltage regulation, the substation management — you just need the light to come on when you flip the switch.

The permanence has to feel like permanence. Not like a technical property, not like a feature of a specific blockchain protocol, not like a claim you have to go and verify — just like a thing that is simply, durably, true. You bought this. It’s yours. Forever. Nobody’s coming for it.

When we talk internally about what we’re building, we sometimes describe it as infrastructure that has to be humble enough to hide itself. The technology is extraordinary. The experience should feel ordinary. The gap between those two things is where most of our work happens.

What it meant for how we communicate

Building for ordinary Queenslanders meant we had to be brutally honest about our language.

Early on, we wrote things that made perfect sense to us. We talked about decentralised naming. We talked about onchain addresses. We talked about permanent digital identity. And we’d share those drafts with people outside the team — people who matched our actual target audience — and watch their eyes glaze over not in confusion but in that particular way that signals “I don’t think this is for me.”

That’s the cruelest kind of feedback, because it’s silent. They didn’t say they were confused. They just quietly decided they weren’t the audience. And they were wrong about that — but we were the ones who’d let them make that mistake.

So we started over.

We stopped leading with what the technology is and started leading with what it means. Not “permanent onchain address” but “yours for life.” Not “immutable identity primitive” but “nobody can take it away from you.” Not “decentralised infrastructure” but “doesn’t depend on any company staying in business.”

Every single word was pressure-tested against one question: would a cabinet maker in Noosa read this and think it was written for someone like him?

That question was uncomfortable at first. It felt like we were dumbing things down, and we had to get over that feeling, because it was wrong. Plain language isn’t dumb language. It’s respectful language. It assumes the reader is intelligent enough to understand a clear sentence without needing you to dress it up in terminology that signals your technical credentials.

The cabinet maker doesn’t need to know about blockchain. He needs to know that what he’s buying is actually his, actually permanent, and actually costs less than a single dinner out. Those are the facts that matter to him. Every word we write is either serving those facts or getting in the way of them.

The question of trust, and how it’s earned differently

There’s a way that trust works inside technology communities that doesn’t work anywhere else.

In crypto-native spaces, trust is often established through technical credibility. If you can demonstrate that your smart contracts are solid, that your architecture is sound, that your tokenomics make sense, that your team has the right credentials — people who live in that world will give you a serious look. The signals are legible to them. They can evaluate you on the terms you’re presenting yourself on.

Ordinary people don’t have that framework available to them. They can’t evaluate smart contracts. They’re not going to read a whitepaper. They don’t have a reference class for “is this blockchain project credible or not” — so that framework provides them no signal at all.

What ordinary people use to establish trust is much older and much simpler. They ask: does this feel like it was made by people who understand my life? Does this seem like something that would cause me embarrassment or regret? Is it clear what I’m getting, without any fine print that will surprise me later? Does it feel like the people behind it are honest, or are they trying to be clever?

These are the questions we answer with every design decision, every sentence, every interaction. And they’re not questions you can answer by being technically excellent. You answer them by being genuinely, consistently, demonstrably for the person you say you’re for.

That has meant making our pricing as plain as it can possibly be. One price. Paid once. No annual fees. No renewals. No surprises. No asterisks. We’ve had internal conversations about whether certain additional features should cost more, and in almost every one of those conversations, the deciding factor has been: what does this do to the story? Because the story is “you buy it once and it’s yours forever,” and anything that complicates that story costs more trust than it earns in revenue.

It has also meant being honest about what this is, in the simplest terms. This is a permanent address that lives on a blockchain. The blockchain part is why it’s permanent — that’s the only piece of the technical explanation that earns its place in our communications, because it’s the answer to the question “but how do I know it really lasts forever?” Every other technical detail either goes in the background or doesn’t go anywhere at all.

What success looks like — and why it’s different from what most projects measure

We don’t measure success by the metrics that technology projects typically measure themselves against.

We’re not chasing viral moments in crypto communities. We’re not trying to be the most-discussed project at a blockchain conference. We’re not optimising for the kind of growth that comes from people who are already fluent in this space spreading the word to other people who are already fluent in this space.

What we’re trying to do is something quieter and, we think, harder. We’re trying to build something that becomes part of the texture of life in Queensland. Something that becomes the kind of obvious, unremarkable thing that people do — the way getting a phone number is obvious and unremarkable, the way registering a business name is obvious and unremarkable.

We want the cabinet maker to have a .queensland address that he puts on his business cards without thinking twice about it, the same way he puts his mobile number on there. We want the family in Toowoomba to pass their .qld address down to their kids the way you pass down other things that belong to a family. We want the surf instructor to have a .surfersparadise address that nobody questions, because it’s just what you have if you’re from there and you’ve built something there.

That kind of success doesn’t announce itself loudly. It accumulates quietly. And it requires that the product work so well for ordinary people that nobody has to think about the infrastructure behind it — that it just becomes a natural thing, a Queensland thing, something that belongs here.

On the permanence question — and why it matters so much more to ordinary people than to tech people

Here is something we’ve noticed, and it’s shaped a great deal of how we think about this project.

Tech-savvy early adopters are, generally speaking, comfortable with impermanence. They migrate between platforms. They rebuild their online presence periodically. They’re used to services changing, dying, evolving, being acquired, pivoting. They hold their digital identities loosely because they know how to reconstruct them. There’s almost a pride in that adaptability — a sense that being able to move quickly and not be attached to any particular platform is a mark of sophistication.

Ordinary people are not like that. Ordinary people build slowly and they want what they build to stay built.

The cabinet maker who’s had the same phone number for twenty years isn’t being unsophisticated. He’s being sensible. His customers know that number. It’s on every quote he’s ever sent, every invoice, every referral. The stability of that number has real economic value, even if he’s never thought about it in those terms. The thought of losing it — of having to rebuild those connections, re-educate those customers, update all those records — is genuinely distressing.

Digital addresses have not historically been stable for ordinary people. Domain names expire if you forget to renew them. Social media handles get taken over, platforms shut down, accounts get suspended. The ordinary person has been trained, by accumulated experience, to hold their digital presence loosely — not because they want to, but because they’ve learned it can be taken away.

We are offering something they’ve never actually been offered before: a digital address that genuinely cannot be taken away. That is immutable in the technical sense, which means it’s also immutable in the human sense — it simply is what it is, yours, unchanging, for as long as there’s an internet to speak of.

For tech people, this is an interesting property. For ordinary people, it’s a completely different category of thing. It’s not an interesting feature. It’s a kind of relief.

When we understood that, we understood what we were really building. We’re not building a technical product that happens to be accessible to ordinary people. We’re building something that solves a problem ordinary people have had for as long as the internet has existed, and we happen to be using technical infrastructure to solve it.

That reframing changed everything about how we talk, how we build, and how we think about who we’re for.

The six names, and what they represent

We secured six TLDs: .queensland, .qld, .brisbane, .surfersparadise, .gold-coast, and .brisbane2032.

Every one of those names means something to people who come from here.

.queensland is broad — it’s for people who identify with the whole of it, who feel the word as an identity rather than just a geography. The people who left and still say they’re from Queensland. The businesses that exist because of what Queensland is and means.

.qld is tighter, more familiar. It’s the abbreviation Queenslanders use. It’s the plate on the car. It’s the way Queenslanders refer to their own state in casual speech. There’s an intimacy in it.

.brisbane is for people who feel the city specifically. Not just Queensland — Brisbane. The particular river-and-hilly-suburb quality of it, the way it’s grown, the way it’s stayed itself while becoming something new.

.surfersparadise is an address that could only belong to one place on earth. You could say .surfersparadise anywhere in the world and everyone would know exactly where you meant. For the people who actually live and work there, who have built businesses there, who call it home — that address carries a weight of identity that a generic domain never could.

.gold-coast is the same logic at a broader scale. The Gold Coast has its own culture, its own economy, its own kind of pride. It is not Brisbane. It is not just Queensland. It is specifically, defiantly itself.

.brisbane2032 is different from the others. It’s forward-facing. It carries the energy of what Brisbane is becoming — the event that will reshape the city, the infrastructure being built, the attention that will arrive, the sense that this particular moment in this particular city is historically significant. An address that ends in .brisbane2032 is a statement about where you were, what you built, and what you were part of.

None of these names were chosen for technical reasons. They were chosen because they mean something to people who belong here. The technology makes them permanent. The names make them meaningful. Both things have to be true at once, and we try to hold both of them with equal seriousness.

Why we resist the word “crypto”

We want to be honest about this, because it reflects something real about our choices.

The word “crypto” — and the broader ecosystem of language that surrounds it — carries a lot of freight. For people inside that world, it carries the freight of a particular kind of excitement, a particular kind of possibility, a particular kind of community identity. For people outside that world, it often carries very different freight: scepticism, confusion, a vague sense that something is trying to separate them from their money in ways they don’t fully understand.

We’re not anti-crypto. The infrastructure we’ve built on is blockchain infrastructure. The permanence we’re selling is made possible by the properties of distributed ledgers. We’re not pretending otherwise, and we wouldn’t.

But we are acutely aware that leaning into “crypto” language does something specific to our audience. It tells the cabinet maker that this might not be for him. It tells the farmer that she’d need to understand something complicated before she could use this. It tells the family in Toowoomba that this belongs to a different world, a more technical world, a world where different rules apply.

None of that is true. This is for them. So we don’t use language that says otherwise.

This has been one of the sharpest edges of our communication challenge. How do you talk about something that is genuinely built on blockchain infrastructure without using language that excludes the people you built it for? How do you be honest about the technology without letting the technology become the story?

The answer we’ve found is to talk about consequences, not mechanisms. The consequence is permanence. The consequence is true ownership. The consequence is a price you pay once and never again. The consequence is an address that belongs to you, to your family, to your business — and that nobody can take, let expire, or change the terms on.

The mechanism is blockchain. The mechanism is interesting, and if people want to understand it, we’ll explain it honestly. But the mechanism is not the story. The story is what it means for someone whose life is rooted in Queensland and who wants something that reflects that rootedness permanently.

What we’ve had to let go of

Building for ordinary people means accepting constraints that feel, sometimes, like they’re slowing you down.

We’ve had to let go of being impressive to the people who would most easily be impressed by what we’re doing. There are communities where the technical architecture of Queensland Foundation would generate real enthusiasm — where the permanence model, the onchain TLD infrastructure, the specific blockchain choices we’ve made would all be legible as interesting and worth discussing. We’ve had to deliberately not lead with those communities, because leading with them would pull the project’s identity in a direction that makes it harder to reach the people we actually built it for.

We’ve had to let go of moving at the speed that technical early adoption allows. When your first users are crypto-natives, things move fast. They’re already set up. The friction is low. Growth within that world can be swift and exciting. The slower, more deliberate work of reaching ordinary people — of earning their trust, of building understanding from scratch, of making the product so simple that the question of the underlying technology genuinely doesn’t arise — that takes longer. We’ve had to be comfortable with that.

We’ve had to let go of using our product as a credential within a particular technical community. There’s a kind of legitimacy that comes from being known in the right circles, discussed on the right platforms, cited in the right places. None of that matters to the cabinet maker or the farmer or the family in Toowoomba. Their legitimacy signal is simpler: does this work, does it do what it says, and does it feel like it was built by people who understood what they needed? We’ve had to accept that optimising for the first kind of legitimacy often actively works against the second kind.

None of these are small things to let go of. We’re human, and the pull toward the audience that would most quickly understand and appreciate what we’ve made is real. But every time we feel that pull, we come back to the same question: who is this for?

And the answer is always the same.

The responsibility of building permanent things

There’s something we’ve sat with throughout this project that doesn’t come up in most technology conversations, and it’s this: permanence is a serious thing to offer people.

Most technology products exist in a context where, if the product fails or disappears, the user loses something but can start again. You rebuild your profile, migrate your data, find a new service. There’s inconvenience, maybe real loss, but there’s also the assumption that things are inherently temporary and that recovery is possible.

We are offering something permanent. And permanent means that the responsibility we carry is different.

If a family in Toowoomba buys a .qld address and passes it to their children, and those children pass it to their children — we’ve made a promise that extends far beyond anything most technology companies think about. The infrastructure we’ve built on is designed specifically to honour that promise. Blockchain permanence is not a marketing claim. It’s a technical reality. But the responsibility to live up to it, to maintain it, to make sure that what we’ve built continues to work as a foundation for those permanent addresses — that’s a human commitment, not just a technical one.

We take that seriously. More seriously, perhaps, than any other single aspect of what we’re building.

Because the cabinet maker didn’t buy a product. He bought a piece of his identity. The family didn’t buy a service. They bought something to carry forward. If we get this right, we’re not just building a technology business — we’re building something that becomes part of the way Queensland identifies itself, for generations that haven’t been born yet.

That might sound grand. We don’t mean it grandly. We mean it practically. We mean it in the daily decisions about how to build, what to prioritise, what language to use, and who to think of as the person sitting at the other end of every choice we make.

The long version of why we’re doing this

We believe in place. We believe that where you come from is genuinely part of who you are, and that having things that reflect your place — that carry its name, that belong to it, that are recognisably of it — matters to people in ways that are not trivial.

The internet has not historically been good at place. It’s been good at scale, at reach, at connecting people across distance — but its logic has always pushed toward the universal. Generic TLDs. Addresses that could belong to anyone, from anywhere, selling anything.

We wanted to build something that pushes the other direction. That says: being from Queensland is specific. Being from Brisbane is specific. Being a business built on the Gold Coast is specific. And that specificity should be allowed to exist digitally in the same way it exists physically — with a name that belongs to where it’s from, owned permanently by someone who is genuinely of that place.

The blockchain infrastructure makes that possible in a way that wasn’t possible before. Permanent ownership. No company that can decide to shut it down or change the terms. No annual fee that, if forgotten or unpaid, causes the address to lapse. Just a thing that you own, the way you own a piece of land, held in an infrastructure that doesn’t require anyone’s ongoing goodwill to keep existing.

We built that for a cabinet maker in Noosa. For a farming family in the Darling Downs. For a surf instructor at Surfers Paradise. For anyone in Queensland who wants something permanent, something that belongs to them, something that carries the name of where they’re from.

We didn’t build it for tech people.

We think that’s why it might actually last.