We’ve been asked, more than once, when we’re launching. It’s a fair question. It’s the natural question. When you hear about a project — especially one that involves technology, infrastructure, ownership, something new — the instinct is to ask when it becomes real. When does it go live? When can I get involved? When is the moment?

We don’t have an answer to that question. Not because we haven’t thought about it, and not because we’re disorganised or uncertain about what we’re doing. We don’t have a launch date because we’ve thought carefully about what a launch date actually implies — and we’ve decided that framing doesn’t fit what we’re building.

This post is an attempt to explain that decision honestly. Not to spin it or make it sound more strategic than it is. Just to say, plainly, what we think about timelines, momentum, permanence, and why direction has turned out to be a more honest and more useful concept than any date we could have written on a whiteboard.

What a launch date actually says

When a project announces a launch date, it’s making a specific kind of claim. It’s saying: there is a before, and there will be an after. On this side of the line, we’re preparing. On the other side, we’re ready.

That framing works well for certain things. A product that ships. A film that premieres. A restaurant that opens its doors. There’s a genuine threshold — the thing does not exist, and then it does. The work of preparation ends and the work of operation begins. The date marks something real.

But it also carries implications that go beyond the calendar. A launch date implies completeness. It suggests that the thing being launched has been finished to a point where it can be handed to the world. It implies a kind of finality — this is the version we’re offering. It implies a before-and-after relationship with the audience too: you were waiting, and now you can stop waiting.

And perhaps most importantly, a launch date implies that the period after the date is fundamentally different in nature from the period before it. That the hard creative work, the foundational decisions, the architecture — all of that happened in the lead-up, and what follows is delivery and maintenance.

For software products, for apps, for tools with features and releases and versioning, this framing is at least partially true. There are genuinely different phases. The launch date marks a threshold that has meaning.

For what we’re building, it doesn’t.

What we’re actually building

Let’s be clear about what Queensland Foundation is, at its core. We’ve secured six permanent onchain top-level domains: .queensland, .qld, .brisbane, .surfersparadise, .gold-coast, and .brisbane2032. These are not website addresses in the traditional sense. They are not rented from a registrar, subject to expiry, dependent on annual renewal fees, or controlled by a centralised authority that can revoke them.

They are permanent onchain addresses. When someone acquires one, they own it — fully, permanently, with no ongoing cost and no expiry date. The address is immutable and transferable. It belongs to them the way property belongs to a person: not as a subscription, not as a licence, but as an owned asset.

The price starts at five dollars, paid once. There are no annual fees. Not now, not later.

When you sit with that for a moment, you start to understand why the launch date framing breaks down. What we’ve built is not a product that ships and then stabilises. It’s infrastructure. It’s a substrate. And infrastructure, by its nature, doesn’t have a launch date in the way a product does — it has a construction period, and then it has an indefinite existence during which people build things on top of it and with it.

Think about roads. Think about the electrical grid. Think about the internet itself. These things were not launched on a date. They were built incrementally, extended, improved, connected — and at some point they crossed a threshold from experimental to functional to indispensable. But no single date marked that transition in a way that felt clean or final, because the transition wasn’t clean or final. It was gradual, uneven, and ongoing.

We are building infrastructure for Queensland’s digital identity. The ambition is permanent. The foundation is permanent. The addresses we’ve secured are permanent. Why would the timeline be the thing we rushed?

The trap of deadline-driven thinking

There’s a particular kind of pressure that comes with announcing a launch date, and it’s worth being honest about what that pressure does to a project.

When you commit to a date, you’re making a promise to an audience. That promise creates accountability, which can be healthy. But it also creates a different kind of force: the force of the calendar. Suddenly, every decision gets filtered through the question of whether it can be done in time. Complexity gets avoided. Corners get cut. Features get descoped. The question shifts from “what should this be?” to “what can this be by the date?”

We’ve all seen this play out. A project announces with fanfare. The community gets excited. The date approaches and it’s clear things aren’t ready, so either the date slips — which erodes trust — or the thing launches in a state that doesn’t represent what it was meant to be. Both outcomes damage the project. Both were predictable. Both were caused, at least in part, by the launch date framing itself.

We chose to avoid that trap. Not because we’re afraid of accountability — we want to be held accountable, just to the right things — but because we think the launch date is the wrong unit of accountability for this kind of work.

If we’d announced a launch date, we’d have been accountable to a calendar. Instead, we’re accountable to a direction. Is the infrastructure sound? Is the ownership model genuinely permanent? Are we being honest about what this is and what it isn’t? Are we making decisions that will hold up not just for the next quarter but for the next decade?

Those are the questions we want to be measured against. A date on a calendar doesn’t measure any of them.

What direction means

We talk about having a direction rather than a launch date, and we want to be precise about what we mean by that. It’s not a euphemism for “we haven’t figured it out yet.” It’s not a way of avoiding commitment.

Direction means: we know what we’re building, we know why we’re building it, we know what success looks like at a meaningful scale, and we are moving toward that with intention — without having attached an arbitrary deadline to it that would force us to compromise the work.

Direction means we’ve defined the destination clearly, even if the arrival time is genuinely uncertain.

The destination, in our case, is this: a robust, widely understood, widely used layer of permanent digital identity infrastructure for Queensland and Queenslanders. A system in which a person, a business, a community, or an institution can own a permanent onchain address that represents who they are and where they’re from — without paying rent, without depending on any single company, without risk of it disappearing if a registrar goes under or changes its terms.

That destination is clear. It doesn’t require a launch date to be clear. In fact, attaching a launch date to it would make it less clear, because it would imply we expected to arrive fully by a certain point — when what we’re actually doing is building something that will be used and built upon and extended for decades.

Direction also means we’re honest about the sequence of things. There are phases to this work. There is infrastructure that has to exist before certain things are possible. There are decisions that have to be made before others can be made. We’re not floating through the work without structure — we have a sense of what comes first, what depends on what, and where we are at any given moment. But we’re not going to pretend that sequence resolves into a single date of completion, because it doesn’t.

On permanence as a design principle

One of the things that makes this project genuinely different from most things being built right now — in blockchain or outside it — is the commitment to permanence.

The ownership model we’ve built around is not: pay us regularly and we’ll keep your address alive. It’s: pay once, own forever. That’s a different philosophy. It’s a philosophy that prioritises the owner’s interests over our own recurring revenue. It requires us to think differently about how the project sustains itself over time, and it requires us to be honest about what we’re offering.

But permanence as a design principle also has implications for how we think about the project’s own timeline.

If the addresses we’re selling are meant to last forever — if they’re genuinely meant to be permanent assets that people own for life — then the project itself has to be oriented toward the long term. We’re not building something we plan to wind up in five years. We’re not building something whose value depends on us being around and active and interested indefinitely. We’re building something that, ideally, becomes part of the fabric of Queensland’s digital identity in a way that outlasts any individual decision we make.

That kind of ambition is incompatible with launch-date thinking. Launch-date thinking is, by its nature, short-term. It asks: when do we flip the switch? It treats the project as a series of deliverables rather than as a living thing that will grow and change and be used in ways we can’t fully predict.

We’d rather build the living thing.

The difference between urgency and rush

We want to be careful here, because there’s a misunderstanding we’ve encountered when we explain our position on launch dates. People sometimes hear “we’re not rushing” and interpret it as “we have no urgency.” Those are very different things.

We have urgency. We’re aware that the window for securing permanent onchain TLDs for Queensland was not infinitely open — it required action, and we took that action. We’re aware that the longer we take to build genuine utility into this infrastructure, the harder certain things become. We’re aware that the world moves fast and that there are other players doing other things that are relevant to what we’re doing.

Urgency means we move with intention and we don’t let the important things slide. Urgency means we care about the work and we care about getting it right. Urgency means we understand that the opportunity we’ve created is real, and that squandering it through complacency would be a failure we’d carry.

Rush is different. Rush is urgency in the absence of clarity — moving fast without being sure you’re moving in the right direction. Rush is what produces the launch-date problems we described earlier: the cut corners, the compromised features, the promises made to a calendar rather than to the work.

We’ve tried to maintain urgency without rush. It’s not always easy. There’s a constant tension between the desire to share what we’ve built with the world and the discipline required to build it properly. We feel that tension. We’ve chosen, repeatedly, to resolve it in favour of discipline.

Because here’s what we believe: the project that holds up is more valuable than the project that launches early. Not more valuable in some abstract reputational sense — more valuable in the literal sense that it creates more benefit for more people over more time. A permanent digital address that works as promised, that holds its value, that does what we said it would do — that is worth more than a fast launch that creates confusion and erodes trust.

What infrastructure looks like from the inside

People who build products have a certain relationship with their work. There are features. There are releases. There are users who can tell you, in real time, whether something works. The feedback loop is tight.

Infrastructure is different. Infrastructure is something you largely experience through absence — when it’s working well, you don’t notice it. When the road is smooth, you don’t think about the road. When the electricity stays on, you don’t think about the grid. Infrastructure becomes visible primarily when it fails.

Building infrastructure means that much of your most important work is invisible to the people who will eventually depend on it. The decisions that matter most — the architecture choices, the ownership model, the permanence mechanisms, the standards you hold yourself to — these are not things you can demo in a video. They don’t produce visual outputs that you can share in a launch announcement.

This creates a communication challenge that we’ve had to sit with. When someone asks us “what have you been working on?” the honest answer is often: the foundation. The things that have to be right before the visible things can be right. The layer beneath the layer.

That’s not a satisfying answer for people who are used to the rhythm of product development. But it’s the true answer, and we’ve decided that honesty about the nature of the work is more important than performing a kind of progress that looks more legible.

Infrastructure development also means your timelines are genuinely harder to predict. When you’re adding a feature to a product, you can estimate the work with reasonable accuracy. When you’re building foundational systems — especially foundational systems on relatively new technology — the uncertainty is real. Things that seem straightforward reveal complexity. Dependencies create constraints. Decisions that seemed minor turn out to have significant downstream implications.

We’d rather acknowledge that complexity honestly than paper over it with a confident date that we then have to walk back.

What we owe the people who are paying attention

There’s a version of “we have a direction, not a date” that is a dodge. A way of avoiding accountability by making the goalposts permanently movable. We want to be honest about that risk and explain why we don’t think we’ve fallen into it.

We owe the people paying attention something real. Not a date, but something. And what we believe we owe them is honesty about what we’re building, why it matters, and whether we’re still moving toward the thing we said we were building.

That’s a different kind of accountability, but it’s not weaker accountability. In some ways it’s harder. A date lets you off the hook once you hit it — you launched, you did what you said, the box is checked. Direction-based accountability is ongoing. Every time we communicate about the project, every decision we make, every thing we ship or don’t ship — all of it is either consistent with the direction we’ve described or it isn’t.

We think that’s the right kind of accountability for this kind of project. Because what we’re building isn’t something that can be evaluated at a launch date and then set aside. It’s something that has to prove itself over time. The permanence we’re promising isn’t delivered at launch — it’s demonstrated over years.

So when people ask us how they should evaluate whether we’re doing what we said we’d do, we tell them: watch the decisions. Watch whether the ownership model stays genuinely permanent. Watch whether the price remains fair and accessible. Watch whether the infrastructure we build is actually being built on sound principles rather than convenient ones. Watch whether the choices we make in moments of pressure are consistent with the philosophy we’ve articulated.

That’s the accountability we’re inviting. Not a date.

Why Queensland

It’s worth pausing here to say something about why this work is rooted in a specific place, and why that specificity matters to how we think about timelines and permanence.

Queensland is not just a marketing angle. We’re not using a location as a brand attribute the way a startup might name itself after a city to seem relatable. Queensland is the actual subject of what we’re building. The .queensland and .qld and .brisbane and .surfersparadise and .gold-coast and .brisbane2032 addresses are not decorative — they are expressions of a genuine belief that place matters in digital identity, and that Queensland specifically deserves its own permanent layer of onchain identity infrastructure.

Why Queensland? Because it’s a real place with a distinct identity. Because it has a growing digital economy, a significant international profile, a unique culture, and a future that includes events and developments that will raise its global visibility considerably. Because Queenslanders have an attachment to where they’re from that is genuine and deep — the kind of attachment that makes a permanent onchain address with a Queensland-specific extension meaningful rather than arbitrary.

And because no one else had done it. The window was open. We saw it and we moved.

But grounding this in a real place also means we feel the weight of what we’re doing differently than if we’d built something purely abstract. These are not fictional addresses. They correspond to real places that real people care about. When someone owns a .brisbane address, they’re connecting their digital identity to a city that exists, that has history, that matters to them personally. That’s not nothing.

The permanence we’re building into the system has to be worthy of that meaning. You don’t build permanent infrastructure for real places on a rushed timeline. You build it carefully, because the stakes are proportionate to the depth of what it represents.

On being early

There’s a concept in technology and infrastructure development that we think about often: being early. Not being wrong — being early. The distinction matters.

When you’re building something genuinely new on relatively new technology, the gap between “this is clearly correct” and “this is clearly used by many people” can be years. That gap is not evidence of failure. It’s the nature of building foundational things. The people who built the early web were not wrong because it took years for the web to become what it became. They were early. The infrastructure they built was sound. The world caught up to it.

We believe we’re early. We believe permanent onchain addresses for specific places are going to seem obvious — inevitable, even — in a way that they don’t quite yet. We believe the combination of permanence, genuine ownership, and geographic specificity is a set of properties that will come to be seen as the right way to anchor digital identity to real-world identity.

Being early means the work we do now shapes what people expect later. It means the standards we set — for how addresses are owned, for what permanence means, for what the ownership experience looks like — will influence the landscape as it develops. That’s a responsibility we take seriously.

It also means we’re comfortable with the fact that the world isn’t fully ready for this yet. We’re not building for an audience that already exists in its final form — we’re building for an audience that will grow into understanding what this is and why it matters. Some of the people who will eventually own a .queensland address and think of it as a basic, obvious thing to have — those people don’t fully know they want it yet. That’s fine. We’re building for them anyway.

The honest version of where we are

We’ve talked a lot about philosophy and framing in this post. It seems right to also say something plainly about what that means in practice.

We are building. The work is ongoing. The foundation has been secured — the six TLDs are ours, permanently, and the ownership model is established. What we are doing now is building the layer on top of that foundation: the systems, the experience, the clarity of communication, the infrastructure that makes these addresses genuinely useful and genuinely accessible.

We don’t know the exact date when everything we’re imagining will be in place. We don’t think that uncertainty is a failure of planning. We think it’s the honest acknowledgement that building something permanent and foundational is not a project with a tidy end date.

What we know is our direction. We know what we’re building and why. We know the principles we won’t compromise. We know the kind of thing this needs to be to fulfil its potential and to deserve the trust of the people who participate in it.

We move toward that direction every day. Sometimes visibly, sometimes in ways that won’t be apparent for a while. We try to communicate honestly about where we are and what we’re working on without manufacturing false milestones or performing progress we haven’t made.

What we’re actually inviting people into

A launch date invites people to wait. It says: hold on, it’s not time yet, but on this date, you can arrive.

A direction invites people to pay attention. It says: we’re moving toward something real, and if you believe in what we’re building, you can watch it become what we’ve described.

We’re aware that the second invitation is less satisfying in the short term. Waiting has a shape — you know when it ends. Paying attention doesn’t. It requires ongoing interest and ongoing faith that the project is moving in the right direction.

We think the second invitation is more honest. We think it’s more respectful of the people paying attention. And we think it’s more appropriate to the nature of what we’re building — something that isn’t meant to arrive on a date and then be done, but to become, gradually and then significantly, part of how Queensland’s digital identity is understood and expressed.

That’s what we’re working toward. Not a launch. A becoming.

Why this is worth saying out loud

We’ve written this post because we think it’s worth being honest about something that the technology space in particular tends to obscure: the tension between the rhythms of communication and the rhythms of building.

The rhythm of communication wants dates. It wants milestones. It wants moments you can point to and say: here, this happened, this is the before and this is the after. Those moments make for clear announcements, clear stories, clear evidence of progress.

The rhythm of building doesn’t always produce those moments cleanly. Especially when you’re building infrastructure. Especially when the whole point is permanence.

We’ve chosen to honour the rhythm of building, even when it makes the rhythm of communication harder. We’ve chosen to say “we have a direction” even knowing that it’s a less satisfying answer than a date. We’ve chosen to be honest about uncertainty rather than manufacture confidence we don’t have.

We believe that choice will prove to have been right. Not because it’s strategically smart — though we think it is — but because it’s true. And building something that’s meant to last has to start with being honest about what it is.

We’re building permanent infrastructure for Queensland’s digital identity. We know where we’re going. We’re not there yet. We’re moving.

That’s the whole story, told as plainly as we know how to tell it.