The question that wouldn’t leave us alone

There is a particular kind of restlessness that comes from seeing something clearly that most people haven’t noticed yet. It isn’t comfortable. It doesn’t feel like excitement, at least not at first. It feels more like an itch you can’t quite reach — the persistent, low-grade irritation of knowing something needs to exist and watching it not exist, day after day, week after week.

That was where we started. Not with a pitch deck. Not with a product roadmap. We started with a question that kept surfacing no matter how many times we set it aside: if permanent onchain addresses are going to matter — if the idea of owning a piece of the internet the way you own land is genuinely transformative — then who is going to do this for Queensland?

We’d look at the landscape and see the possibility clearly. The technology existed. The infrastructure could be built. The logic was sound: people should be able to own their digital identity permanently, without the perpetual tax of renewal fees, without the risk of expiry, without depending on the continued goodwill of a registrar who might change their pricing, their policies, or their very existence. A name you own once, for life. That idea wasn’t abstract to us. It felt obvious and overdue.

And yet nobody was doing it for this place. Not for Queensland. Not for Brisbane or the Gold Coast or Surfers Paradise. Not in a way that was permanent, not in a way that was genuinely onchain, not in a way that treated the residents of this state as people who deserved the same quality of digital infrastructure that was beginning to appear elsewhere in the world.

So the question kept returning: who is going to do this?

At some point, the honest answer stopped being someone and started being us.

The space between seeing and doing

It would be a lie to say the decision was clean. There’s a version of this story where two or three people look at each other in a room, nod with solemn purpose, and agree to build the future. That’s not what happened. What happened was messier and more human: a long period of circling, of making the case to ourselves, of poking holes in our own reasoning and then repairing those holes, of talking ourselves into it and then almost talking ourselves back out.

That space between seeing a problem and committing to solve it is uncomfortable in a specific way. You’re not yet responsible for anything, but you feel the weight of potential responsibility pressing against you. Every day you don’t commit, you can still tell yourself you’re being prudent, you’re doing your research, you’re waiting for the right moment. And every day you do that, some part of you knows you’re also just waiting.

The honest question we had to sit with was this: what exactly are we waiting for?

We were waiting, we eventually admitted, for permission. Or for precedent. Or for someone slightly more qualified, slightly better resourced, slightly more officially sanctioned to step forward and do it first. We were waiting for the version of this project that came pre-validated, pre-de-risked, with a clear path already worn into the ground.

That version was never coming. That’s not how new infrastructure gets built. Roads didn’t get built because everyone agreed roads were a good idea in the abstract and then waited for the obvious candidate to emerge. Someone had to decide, under conditions of uncertainty, that the road needed to be here, that it needed to be built now, and that they were the ones who were going to build it.

The moment we stopped looking for permission was the moment the project became real.

What it actually means to take responsibility for infrastructure

We want to be precise about this, because “infrastructure” is a word that gets used loosely.

A product feature is something that makes an existing experience better. A platform is something that lets other people build experiences. Infrastructure is something different again — it’s the substrate. It’s what has to be in place before anything else can happen. When infrastructure works well, nobody thinks about it. It becomes the invisible foundation that everything else stands on.

When we committed to building permanent onchain TLDs for Queensland, we were committing to infrastructure in that full sense. We weren’t building an app on top of something else. We weren’t adding a feature to a platform someone else controlled. We were securing the names themselves — .queensland, .qld, .brisbane, .surfersparadise, .gold-coast, .brisbane2032 — and committing to everything that follows from owning those names.

That includes: building the systems that let people register addresses under those names. Building for permanence, which means building for the possibility that the infrastructure outlives any particular team member, any particular technology trend, any particular moment in the cultural conversation about blockchain. Building in a way that doesn’t create a new dependency where an old one used to be — because the whole point of permanent onchain addresses is that they liberate people from exactly that kind of dependency.

Taking responsibility for that felt different from anything we’d done before. Not because we lacked confidence in our ability to build. But because infrastructure carries a different moral weight than most things you can build. If a product feature doesn’t work well, users find another feature. If infrastructure fails, or gets built badly, or embeds the wrong assumptions at its foundation, the consequences propagate outward in ways that are hard to predict and harder to undo.

We felt that weight. We still feel it. We think that’s appropriate.

Why waiting felt like abdication

There’s a version of responsibility that looks like caution: don’t move until you’re certain, don’t commit until the path is clear, let others prove the concept before you build on it. That version of responsibility has its place. There are contexts where it’s exactly right.

This wasn’t one of them.

The thing about infrastructure is that it has to be built before the demand for it is fully legible. That’s definitionally true. People can’t articulate a need for infrastructure they’ve never seen — they can only articulate the problems they currently have, the friction they currently experience, the limitations they currently work around. The role of infrastructure builders is to see past that, to understand what would become possible if the substrate existed, and to build the substrate in advance of the demand for it.

That means, by definition, that nobody was going to ask us to do this. Nobody was going to commission permanent onchain TLDs for Queensland. No government tender was going to appear. No market research was going to show robust consumer demand for a product category that didn’t yet exist. The validation, if it came, would come later — after the infrastructure existed, after people could see what became possible because of it, after the first generation of people owned permanent addresses and discovered what it meant to have a digital identity that truly belonged to them.

Waiting for that validation before we started building would mean waiting forever. Or waiting until someone else built it — built it elsewhere, built it for some other place, built it with different values or different assumptions embedded at its foundation.

That second possibility is the one that troubled us most. Not the abstract possibility that the project never gets built. The concrete possibility that it gets built by someone who doesn’t care about this place, who doesn’t understand this place, who builds something technically functional but fundamentally misaligned with what Queenslanders actually need.

Digital infrastructure, like physical infrastructure, reflects the values of the people who build it. Road networks encode decisions about who matters and who gets connected. Telecommunications infrastructure encodes decisions about whose access is prioritised. The infrastructure of the internet encodes decisions about who owns what, who controls what, who benefits. Those decisions, once made and embedded in systems at scale, are genuinely hard to reverse.

We didn’t want to wait and then spend the next decade explaining why the infrastructure that someone else built for this place was built wrong.

We’d rather build it ourselves and be accountable for getting it right.

The specific texture of this kind of conviction

Conviction is a strange thing. People talk about it as if it’s a feeling — a surge of certainty that arrives and sustains itself. In our experience, it’s not like that. Conviction isn’t a feeling you have. It’s a position you maintain, repeatedly, under conditions that constantly give you reasons to revise it.

There were moments, early on, when the technical complexity felt genuinely daunting. When we’d be mapping out what “permanent” actually requires at the infrastructure level — not just onchain registration, but the full chain of what it means for an address to truly belong to someone in perpetuity — and the scope would briefly feel like too much. Those weren’t comfortable moments.

There were also moments when the cultural timing felt uncertain. We were building something in a space that not everyone understands yet, for a constituency — the people of Queensland — who hadn’t asked for it and many of whom hadn’t yet formed views on whether they wanted it. That’s a strange position to build from. You’re not responding to demand. You’re placing a bet on what demand will look like when people can see what’s on offer.

And there were moments when the sheer novelty of what we were doing made it hard to explain, even to people whose opinions we valued. “Permanent onchain TLDs for Queensland” is not a sentence that lands immediately for most audiences. The concept requires unpacking. It requires people to first understand what onchain addresses are, then to understand why permanence matters, then to understand why a regional TLD is meaningful as opposed to a generic one. That’s a lot of conceptual unpacking before you even get to the value proposition.

Each of those pressures gave us a reason to wait. To do a bit more research. To see how things developed. To revisit in a quarter.

Conviction, for us, meant noticing those pressures and choosing not to be moved by them. Not because the concerns weren’t real — they were real — but because the alternative was worse. The alternative was a version of ourselves who had seen something important, understood what needed to be built, had the capability to build it, and chose instead to stand at a careful distance and watch.

We didn’t want to be those people.

Permanence as a design constraint and a moral commitment

At some point in the early phase of this project, we had a conversation that changed how we thought about what we were building. It started as a technical discussion — specifically about what “no renewals, no expiry” actually requires architecturally — and it became something larger.

The question was: what does it mean to make a promise of permanence?

Conventional domains work on a rental model. You pay annually. The name is yours for as long as you keep paying, and not a day longer. That model is clean and legible and it puts all the risk on the user — if they forget to renew, if their payment fails, if the registrar changes its pricing beyond what they can afford, they lose the name. The infrastructure is, in this sense, aggressively neutral about whether you keep your address or not.

We wanted to build something different. We wanted to build something where the address genuinely belongs to the person who registers it. Not leased. Owned. And not owned in a way that depends on our continued operation, our continued goodwill, our continued existence as a business entity. Owned in a way that is as permanent as the blockchain itself — which is to say, permanent in a meaningful, durable sense.

That’s a harder thing to build. It requires you to think not just about the system working today but about the system working without you. It requires you to ask: what happens if we’re not here? What do we need to put in place so that the addresses people register today are still theirs in twenty years, regardless of what happens to our organisation?

That question reshaped how we approached everything. It became a design constraint: build nothing that creates a dependency that can’t survive your absence. It also became a moral commitment: if you’re going to make a promise of permanence to someone, you have to mean it in the fullest sense. You have to be willing to be held accountable to it even under conditions you can’t currently predict.

That’s not a comfortable place to build from. Permanence as a genuine commitment — not a marketing claim, not an aspiration, but an actual architectural and organisational commitment — means accepting responsibility for outcomes that extend far beyond any normal product timeline.

We accepted that responsibility. We still accept it. We think it’s what distinguishes infrastructure that deserves trust from infrastructure that merely asks for it.

The tension between urgency and care

One of the ongoing tensions of this project — one we haven’t fully resolved, and perhaps never will — is the tension between the urgency of building and the care that permanence demands.

On one side: the window for securing permanent onchain TLDs for this specific geography is not indefinitely open. The naming landscape is not static. The moment for claiming .queensland and .qld and the rest was a moment that required action, not deliberation in perpetuity. There was a real sense in which moving mattered, in which delay had consequences.

On the other side: getting the foundations right matters more than getting them done quickly. If you embed the wrong assumptions in infrastructure — if you make architectural decisions early that seem expedient but create problems at scale — those decisions are very hard to walk back. The things you build first become the constraints that shape everything built after. Rush the foundations and you rush yourself into a corner.

We navigated this tension imperfectly, as anyone does. There were moments when we moved faster than felt comfortable and had to go back and reinforce something we’d underspecified. There were other moments when we slowed down to think through implications that, in retrospect, we’d already thought through adequately. Perfect calibration between urgency and care is probably not achievable; you aim for good enough and you stay honest about where you made tradeoffs.

What we tried to hold onto, throughout, was a clear hierarchy: permanence first, speed second. When those values were in conflict — when going faster would mean cutting a corner that affected the durability or trustworthiness of what we were building — permanence won. When speed and quality weren’t actually in conflict and we were just being slow out of excessive caution, we pushed ourselves to move.

That hierarchy gave us a way to make decisions quickly even when the decisions were hard. If the question was “does this tradeoff compromise permanence?” the answer was no, and we figured out how to move without making it.

Building for people who don’t know they need this yet

There is something humbling about building infrastructure for a constituency that hasn’t asked for it. It requires a kind of epistemic confidence that can look, from the outside, like arrogance: we understand what you’ll need before you know you’ll need it.

We don’t think of it as arrogance. We think of it as the specific responsibility of people who can see around a corner. Not everyone can see every corner. That’s not a hierarchy of intelligence; it’s a distribution of attention and context. We happened to have the context to see this particular thing clearly. That came with an obligation.

The obligation wasn’t to sell the vision — to convince people that permanent onchain addresses were important before they’d had a chance to experience what they made possible. The obligation was to build it well enough that when people did encounter it, when the idea became legible to them through lived experience rather than explanation, the infrastructure would be there and it would be worthy of their trust.

That’s a different orientation than most product development, which is driven by demand signals — by what people are already asking for, already buying, already using. We were building in front of demand, which means the validation loop is delayed. You build, and you wait, and eventually the world catches up to what you’ve built, and you find out whether you built the right thing.

We think we built the right thing. We think that when Queenslanders understand what it means to own a permanent digital address — not rent it, own it, for life, under a name that means something specific to this place and this community — they will see what we saw when we made the decision to build.

But we also know that belief is something we’re carrying alone for now. That’s what it means to build before anyone is asking.

What this place deserves

We want to say something about why this being Queensland-specific matters to us, because it would be easy to miss.

A generic permanent onchain address is a useful thing. But a permanent address under .queensland or .brisbane or .goldcoast is something more than useful — it’s an expression of identity. It’s a way of saying: I am from here. I am of this place. My presence on the internet is rooted in something specific, something geographical, something cultural.

That matters because identity matters. The places people come from, the communities they’re part of, the specific geography that shapes how they see the world — these things are real, and they belong in the infrastructure of the digital world as much as they belong in the physical world.

When we were deciding whether to build this, the question of place was always present. We weren’t just securing useful TLDs. We were securing the specific names that belong to this part of the world. .queensland isn’t a brand. It’s a place. It has meaning independent of us, meaning that predates our project by hundreds of years of human history and tens of thousands of years of deeper history. We were, in a real sense, taking responsibility for names that carry weight we didn’t give them and can’t fully contain.

That felt important to name. We’re not the authors of what Queensland means. We’re the people who decided that Queensland should be able to exist, permanently and without conditions, in the infrastructure of the digital world. That’s a limited but real act of stewardship. We take it seriously.

Queensland deserves permanent digital infrastructure with its own name on it. Brisbane deserves it. The Gold Coast deserves it. Not as a product feature, not as a novelty, but as a genuine, durable, trustworthy foundation for digital identity in this place.

That was the other thing that kept us from waiting. The idea that this place deserved this, and that someone needed to be the one to build it.

After the decision

There’s a particular kind of clarity that comes after a genuine commitment. Not the false clarity of certainty — uncertainty doesn’t disappear when you commit to something, and anyone who tells you otherwise is describing a different kind of project than this one. But a different kind of clarity: the clarity of knowing where you stand.

Before we committed, every question had an exit. Is this the right time? Maybe we wait. Is this the right approach? Maybe someone else will do it differently. Are we the right people? Maybe not, let’s see.

After we committed, the exit routes closed, and the questions changed shape. Not “is this the right time?” but “how do we use the time we have well?” Not “is this the right approach?” but “how do we make this approach work?” Not “are we the right people?” but “how do we become the people this project requires us to be?”

That shift — from evaluative questions to operational ones — is, we think, what a real commitment feels like. It’s not a feeling of confidence. It’s a change in the structure of the questions you’re asking yourself.

We’re still inside that change. We’re still, in many ways, in the process of becoming the organisation this project requires. The decision to build was the beginning, not the end. Everything since has been the work of living up to what we committed to in that moment.

We don’t regret the commitment. We don’t regret the weight of it.

Building something permanent for the people of Queensland — building it with care, with integrity, with genuine accountability to the people who will eventually depend on it — is work worth doing.

It just required someone to stop waiting and start.