We didn’t expect this. We should be honest about that upfront.

When we started talking to people about what we’d built — permanent onchain addresses for Queensland, owned once, for life, no renewals, no expiry, yours forever — we assumed the conversation would land easiest with developers. With the tech-curious, the crypto-adjacent, the people who already live in a browser tab and understand that the internet is infrastructure. We thought the farmers would take some convincing. We thought the tradie with a ute and a toolbox and a business built on word of mouth and a battered business card would need a long explanation. We thought the mum who runs a cake business out of her kitchen in Toowoomba would need us to back up and start from basics.

We were wrong. Completely, instructively, beautifully wrong.

It is the farmers who get it in thirty seconds. It is the tradies who nod along before we’ve even finished the sentence. It is the small business owners, the families, the people with deep roots in one place and a clear-eyed understanding of what it means to own something, who hear “you buy it once, it’s yours forever, no one can take it, no renewal fees, ever” and say: “Right. Yeah. Obviously. Where do I sign?”

And it is the tech people — the developers, the digital marketers, the startup founders, the people who live online — who furrow their brow, tilt their head, and say, “But how does it work without ICANN? Who’s the registrar? What’s the resolver infrastructure? What happens if the blockchain forks?”

That contrast has taught us more about what we built than anything else.

The Burden of Knowing How Things Work

There is a peculiar kind of blindness that comes from deep technical knowledge. It is not stupidity — far from it. It is something more like the opposite: an inability to unknow. When you spend years inside a system, the system’s architecture becomes your reality. Its assumptions become your assumptions. Its limitations stop looking like limitations and start looking like laws of nature.

The traditional domain industry has worked a particular way for decades. You rent a name. You pay every year. If you stop paying, you lose it. The registrar holds the key. ICANN sits at the top of the pyramid. The whole thing is a giant, centralised permission structure, dressed up to look neutral.

For non-technical people, this was always just a vague inconvenience — an annual bill that showed up in the inbox, slightly annoying, easy to forget. They never interrogated the system. They just paid the renewal and moved on.

But for technical people — for developers, for digital professionals — this system became the water they swam in. The rental model wasn’t a flaw to be solved. It was just how domains work. How they’ve always worked. How they must work, structurally, for everything else to function.

So when we describe a permanent onchain address — something you own, not rent; something recorded on-chain, not held in a registrar’s database; something that cannot expire, cannot be revoked, cannot be “reclaimed” by anyone — the technical brain does something interesting. It tries to fit the new thing into the old framework. And when it can’t, it generates friction.

The non-technical brain has no framework to defend. It hears “own it forever for one payment” and processes that through the most universal framework available: property.

Property Is the Oldest Technology

Ask a farmer what it means to own land and they won’t give you a theory. They’ll tell you about the title. The piece of paper — or these days, the entry in a land registry — that says this paddock is yours. Not leased. Not licensed. Not rented. Owned. With your name on it. Transferable to your kids if you choose. Permanent in a way that transcends your own lifetime.

That farmer understands, in their bones, the difference between a lease and a title. They know that a lease can expire. A lease can have conditions. A lease can be terminated if the landlord decides to sell, or change the terms, or go out of business. A title, by contrast, is a different category of thing. It does not expire. It does not need renewal. It is recorded, witnessed, immutable.

When we describe what a permanent onchain address is — recorded on the blockchain, immutable, transferable, owned not rented — that farmer hears “title.” They hear it instantly. The metaphor isn’t even a metaphor for them. It just maps onto something they already know and live by.

We’ve had conversations where we barely finished explaining and the person on the other side was already asking whether they could pass their address to their children. Not because we prompted the question. But because the concept of permanence immediately raises the concept of inheritance. Of legacy. Of something worth holding.

That is a profoundly human response to the idea of ownership. And it tells you something important: we built something that speaks to a deep and ancient human instinct — the instinct to claim a place, to name it, to make it yours.

Tradies Understand Assets. Not Subscriptions.

If you run a plumbing business or an electrical contracting company in Queensland, you have a very particular relationship with your tools and your gear. Your van. Your drill. Your test equipment. You paid for them once. They’re yours. You can use them, lend them, sell them, pass them on. The value you got from that purchase doesn’t require a monthly fee. The drill doesn’t stop working when a subscription lapses.

Tradies, as a professional class, are acutely attuned to the difference between a capital cost and a running cost. They price their quotes to account for both. They understand immediately that owning a thing is structurally different from renting a thing. They’ve made that calculation on every piece of gear they carry.

So when we talk to a sparky or a plumber about permanent onchain addresses, we sometimes describe it this way: it’s the difference between buying your drill and leasing it. When you buy it, you own it. When you lease it, you’re always on the hook for next month’s payment. The moment you stop paying, someone else can lease your drill out from underneath you.

That framing resonates immediately. Not because we’re dumbing it down — but because we’re reaching for the right analogy. The right analogy isn’t “web3” or “blockchain infrastructure” or “decentralised naming protocol.” The right analogy is: this is a thing you own, not a thing you rent.

The tradie doesn’t need the architecture explained. They need the ownership model explained. And the ownership model is, in its essence, simple: you pay once, it’s yours, end of story.

Small Business Owners Understand What’s at Stake

There is a particular kind of vulnerability that small business owners have with the traditional web. It’s not always visible until something goes wrong.

A café owner in Brisbane’s inner north spends years building their presence under a particular address. Customers bookmark it. It shows up in Google. It’s on the menus, the business cards, the window sticker. And then one year the renewal notice lands in a spam folder. Or the card on file expires. Or the registrar gets acquired and the interface changes and the reminder doesn’t arrive the way it used to. And suddenly, quietly, the address lapses. And someone else registers it. And the years of accumulated trust evaporate.

This is not a hypothetical. It happens. It has happened to businesses that had been trading under a name for a decade.

The small business owner understands this risk viscerally. They’ve known other businesses it happened to. They’ve felt the anxiety of the annual renewal. They’ve made a mental note to set a calendar reminder and then forgotten to set it. They know, in a way the technical person often doesn’t, how much can go wrong in the gap between now and twelve months from now.

When we describe a permanent address — something that doesn’t expire, doesn’t require renewal, doesn’t have a next invoice — the small business owner doesn’t ask how the blockchain works. They ask: “So it’s mine forever? I can never lose it?” And when we confirm that yes, that is exactly right, the response is often something close to relief.

Not excitement. Relief. The excitement comes later, when they start thinking about what they can do with it. But the first response is relief. The anxiety of the renewal model, the quiet dread of it, dissolves the moment permanence becomes real.

That is the response of someone who understands what is actually at stake when you build a business on a rented foundation.

Families Think Across Generations

Something we didn’t anticipate was how quickly families start thinking about time horizons.

A family isn’t primarily thinking about a quarterly campaign or a product cycle. A family is thinking about decades. They name their children with a view to those names lasting a lifetime. They think about what they’ll leave behind. They buy houses not just as investments but as homes — things their children might grow up in, might inherit, might bring their own children to.

When a family encounters the concept of a permanent onchain address, they often go somewhere immediately generational. “So I could register our family name under .queensland and it would be there permanently?” Yes. “And I could give it to my kids someday?” Yes. “And they could keep it, or sell it, or use it how they wanted?” Yes.

The idea of claiming a family name in the Queensland digital namespace — permanently, irrevocably, with no risk of expiry — resonates with something deep in the way families think about legacy. We’ve heard people use words like “heirloom” in conversations we didn’t expect that word to appear in. Not because we planted it. Because permanence, once truly understood, naturally calls up that language.

There is a reason land has been such an enduring form of family wealth across human history. It doesn’t decay. It doesn’t expire. It can be passed on. A family name registered permanently in a digital namespace shares those qualities in a way that a rented domain name simply does not.

The technical person worries about whether the blockchain will still exist in forty years. The family thinks about whether their name will still be there when their grandchildren are old enough to use it. Those are related concerns but they orient entirely differently. One is a question about infrastructure. The other is a question about legacy.

Why Technical Fluency Creates Blind Spots

We want to be careful here, because we have enormous respect for technical people. Many of us are technical people. And the questions technical people ask — about infrastructure, about resolver architecture, about the long-term sustainability of any given blockchain — are not bad questions. They are in many cases important questions.

But fluency in a domain, any domain, creates assumptions. And those assumptions can function as a kind of resistance to new ideas that don’t conform to the established model.

The traditional DNS system — the Domain Name System that underlies all conventional web addresses — is a particular kind of thing. It is centralised. It is hierarchical. It is managed by human organisations that can be pressured, acquired, hacked, or simply changed. It was designed in an era of very different assumptions about how the internet would work, who would control it, and what the appropriate relationship between users and infrastructure would be.

For decades, the domain industry built on top of this architecture. The rental model — pay annually or lose your name — wasn’t a conscious choice to extract ongoing revenue from users. It was an emergent property of a system where the ongoing operation of infrastructure genuinely did require ongoing resources. The registrar had to keep the lights on. The renewal fee was how that happened.

For someone who grew up in that world, the permanent model initially raises an engineering question: if there’s no ongoing fee, who maintains the infrastructure? It’s a reasonable question. The answer, in the case of onchain infrastructure, is that the blockchain itself handles the persistence — the protocol, not a company, maintains the record. But before the person can receive that answer, they have to let go of the assumption that ongoing payment and ongoing maintenance are permanently linked.

That’s a harder cognitive step than it looks. Not because the technical person is slow. But because the assumption is so deeply embedded it’s nearly invisible.

The non-technical person was never enrolled in that assumption. They never had it to begin with. So they don’t need to unlearn anything. They just hear the thing we’re describing and evaluate it on its own terms.

The Question They Don’t Ask

Here is one of the most telling patterns we’ve observed in these conversations.

Non-technical people almost never ask us about the underlying technology. They don’t ask about consensus mechanisms or smart contracts or wallet infrastructure. They ask about the ownership. They ask about the permanence. They ask about what they can do with the address. They ask about their name. They ask about whether it’s really, truly theirs.

Technical people ask about everything except that. They ask about ICANN recognition. They ask about browser resolution. They ask about the stability of the underlying chain. They ask about the tokenomics. They ask about custody models. These are all, in various ways, questions about the machinery.

And there is something revealing in that inversion. Because at the end of the day, what we’ve built is not primarily a technology. The technology is the substrate. What we’ve built is a form of ownership. A new way for Queenslanders to hold a piece of digital territory with the same permanence and security that they’d hold a piece of physical territory.

The technology enables the ownership. But the ownership is the point. And the people who most clearly see that are the ones who haven’t been trained to focus on the machinery.

A farmer doesn’t think about the legal architecture of the Torrens title system when they hold their land title. They don’t need to understand the doctrine of indefeasibility to know that their name is on the register and the land is theirs. The machinery is invisible to them, as it should be. The ownership is visible.

That’s the place we’re trying to get to with permanent onchain addresses. The blockchain should be invisible. The ownership should be obvious.

What This Tells Us About Our Audience

We’ve spent a lot of time sitting with this observation, turning it over, examining its implications. Because it’s not just an interesting anecdote about who grasps the concept fastest. It’s a meaningful signal about who this product is actually for, and how we should think about it.

Queensland is a place defined by its relationship to land, to place, to permanence. Its farmers, its graziers, its miners, its fishing families — these are people with an elemental understanding of what it means to own a piece of this earth. Its tradies and its small business owners understand capital and assets in a way that is direct and practical and unsentimental. Its families are rooted in ways that span generations.

These are the people who were always the audience for permanent digital addresses. Not because we designed the product for them. But because the nature of permanence speaks most clearly to people who already understand permanence. Who live it. Who have staked something on it.

The tech person comes to permanence as an idea, an engineering property, a feature. The Queenslander with their boots in the soil comes to it as a lived reality, a thing they already know in their body, and they recognise its digital expression immediately because the underlying logic is identical.

Own it once. It’s yours. Pass it on. No one can take it from you.

That’s not a pitch. That’s a description of property. And Queenslanders understand property.

The Simplicity on the Other Side of Complexity

There is a concept in intellectual life — the idea that simplicity exists on both sides of complexity. On one side is the naive simplicity of someone who doesn’t know much: things seem simple because they don’t know enough to see the complications. On the other side is the profound simplicity of someone who has worked all the way through the complexity and arrived at clarity: things seem simple because they now understand why the complications don’t actually change the essential truth.

Technical people, encountering permanent onchain addresses for the first time, are often sitting in the middle of complexity. They know enough about DNS and blockchain and registrar infrastructure to see a thousand potential complications. They can enumerate the failure modes. They can list the assumptions that would need to hold for the thing to work the way we describe. They are not wrong to see those complications.

But they are sometimes stuck in the middle, unable to see through to the simplicity on the other side.

The farmer is sitting on the other side. Not because they went through the complexity — but because they never entered it. They hold their land title and they understand permanence directly, without intermediation. They are, in a paradoxical way, closer to the profound simplicity than the technical person sitting in the middle of the machinery.

That’s not a knock on technical knowledge. We need technical knowledge. We need the people who understand the machinery, because the machinery has to work. But the people who understand the machinery should not confuse the machinery with the thing the machinery enables. The machinery enables ownership. The ownership is what matters.

And when the farmer says “Right, yeah, obviously” and reaches for the simplest and most natural version of what we’ve described — something you own, not rent; something permanent, not temporary; something with your name on it, not theirs — that farmer is right. They’ve arrived at the correct conclusion by the most direct path.

The Gap Between Knowing About Technology and Knowing What Technology Is For

We think about this distinction a lot: knowing about technology versus knowing what technology is for.

Knowing about technology means understanding how it works. How the blocks are chained. How the consensus is reached. How the resolver maps an address to a resource. This knowledge is real and valuable and necessary for the people who build and maintain the infrastructure.

Knowing what technology is for means understanding its human purpose. What problem does it solve? What relationship does it enable? Whose life does it change, and how?

These two kinds of knowledge are often held by different people. The people who know about the technology don’t always have the clearest view of what it’s for. And the people who most clearly understand what it’s for are often people who have no interest in how it works.

We’ve come to believe that permanent onchain addresses are fundamentally about one thing: giving Queenslanders the same permanence and security in their digital address that they have in their physical address. Your home address doesn’t expire. Your street number doesn’t get reassigned because you missed a payment. Your suburb doesn’t change its name because the council switched DNS registrars.

But your web address can do all of those things, under the current system. It’s fragile in a way your physical address isn’t. It’s rentable in a way your home isn’t. It’s subject to third-party decisions in a way that a title-held property is not.

Permanent onchain addresses fix that fragility. They do for digital addresses what the title system did for land: they transform a tenancy into an ownership.

The technical person asks how. The Queenslander with their feet on the ground asks: so it’s actually mine? And when the answer is yes, they move on. Because they already understood what that means. They just needed to know whether it was real.

What We Learned About Building Things That Last

There’s a quiet humility we’ve had to develop through this process. A willingness to be corrected by the evidence of real conversations.

We came in thinking we were building a technology product. We were, in a technical sense. The infrastructure is built on blockchain. The addresses are onchain. The mechanism is genuinely novel.

But what we learned, in all those conversations with people who understood immediately, was that we were actually building something much older than blockchain. We were building a form of permanent belonging. A digital claim to place. Something that says: this is mine, this is Queensland, and I am from here.

The farmer who registers their family name under .queensland isn’t thinking about smart contracts. They’re thinking about the land they farm, the name their grandparents carried, the permanence of the place they love. The .queensland address is an extension of that. A way to carry their Queensland identity into the digital world with the same permanence they expect in the physical one.

The tradie who registers their business name isn’t thinking about blockchain infrastructure. They’re thinking about the van they paid off, the tools they bought, the reputation they built over twenty years of showing up and doing good work. A permanent address that belongs to them, that can’t be taken away by a missed renewal, is just another piece of gear that’s theirs.

The family that registers their name isn’t thinking about tokenomics. They’re thinking about the generations before them and the generations to come. About a name that persists. About something worth keeping.

These are the people we built this for, whether we fully knew it at the time or not. And their immediate, instinctive understanding of what we built is the clearest confirmation we have that we got the fundamental thing right.

A Note on What “Getting It” Actually Means

We want to be precise about something, because it’s easy to misread the observation we’re making.

When we say non-technical people “get it” faster, we don’t mean they understand all of it. They don’t understand the blockchain architecture. They don’t understand how the address resolves. They don’t understand the technical distinction between onchain persistence and conventional hosting.

But they understand the essential thing. The thing that matters most. The thing that makes this different from every other domain product that has ever existed.

They understand that it’s theirs.

That is the irreducible core of what we built. Everything else — the blockchain infrastructure, the resolver architecture, the smart contract mechanics, the wallet integration — is the machinery that makes the ownership real and permanent and trustless. It is important machinery. But it is in service of the essential thing, which is ownership.

And the people who grasp that essential thing immediately, without needing the machinery explained, are the people who most clearly understand what the machinery is for.

The Broader Truth

We think this observation — that non-technical people often grasp permanent digital ownership faster than technical people — points toward something broader about how we tend to talk about and think about blockchain and web3 and onchain infrastructure in general.

The conversation around these technologies is often dominated by the technical dimension. By the architecture. By the protocol debates and the infrastructure decisions and the custody models and the security assumptions. This is important conversation. It needs to happen.

But it can crowd out the human dimension. The question of what any of this is actually for, at a human level. What problem it solves for a real person living a real life in a real place.

The farmer in western Queensland doesn’t need to care about consensus mechanisms. They need to know that their digital address is as permanent as their land title. The café owner in West End doesn’t need to understand smart contracts. They need to know that the name they’ve built their business on can never be taken from them by a missed renewal or an expiring credit card.

When we get the framing right — when we speak in the language of ownership and permanence and belonging rather than in the language of protocols and infrastructure — something opens up. The conversation becomes a human conversation. The concept becomes intuitive. The value becomes obvious.

And then the farmer says “Right, yeah, obviously.” And the tradie nods. And the family starts thinking about their name, their kids, the thing they want to leave behind.

And in those moments we understand clearly that we didn’t just build a technology product. We built something that was always meant for them.