The misconception we had to unlearn first

There is a version of this story where we move fast, ship everything, announce loudly, and grow the numbers. We know that version. We’ve watched it play out across dozens of projects in this space. The numbers go up, the community swells with people who arrived because of the numbers, and then the whole thing is held hostage to the momentum it created. You can’t slow down. You can’t reconsider. You can’t admit that something needs to be rebuilt. The machine requires feeding.

We chose a different path, and we want to be honest about what that choice actually looks like from the inside — not as a manifesto, not as a justification, but as a plain account of what it means to build something permanent when the culture around you is obsessed with speed.

The first thing we had to unlearn was the idea that slowness is a symptom of doubt. When we started, the instinct was to interpret every pause as hesitation, every week of quiet as evidence that we weren’t serious enough. We absorbed that framing from the environment around us. Move fast or fall behind. Ship it and fix it later. The window closes.

But the window doesn’t close on the kind of infrastructure we’re building. That’s one of the defining features of permanent onchain addresses — they are not a trend, they are not a race to first-mover advantage in a fleeting moment. They are infrastructure, and infrastructure has a different relationship with time than products do. Roads are not built quickly. Foundations are not poured quickly. The things that are meant to outlast their builders are not, and should not be, rushed.

Once we genuinely understood that — not just intellectually, but in the way we made decisions day to day — the slowness stopped feeling like a symptom. It became a method.

What we mean when we say permanent

It’s worth pausing on what we’re actually building, because the word “permanent” carries a lot of weight and it’s easy to use it loosely.

When we say these addresses are permanent, we mean they are not leased. They are not subscribed to. They are not renewed annually and then quietly expired if the payment lapses. They are not subject to a registrar’s continued goodwill, business continuity, or pricing decisions. They are not entries in a centralised database that can be edited, revoked, or repurposed.

They are onchain. They belong to whoever holds them, permanently, transferable like property. You buy a .queensland address once. You pay once. No annual fees, no renewals, no expiry. It is yours for life, the same way a parcel of land is yours — not because someone is allowing it, but because the record is immutable and decentralised.

That is a fundamentally different thing from what most people have experienced with internet addresses. And because it’s different, it requires being built differently. You cannot rush the foundations of something permanent. If you get it wrong, you cannot quietly patch it next quarter. The stakes of the original decisions are higher precisely because the output is meant to outlast the decisions themselves.

This is not an argument against iteration. We iterate constantly. But there is a category of decisions — infrastructure decisions, architectural decisions, decisions about what kinds of partnerships and commitments you make — where speed is actively dangerous. We learned to identify those decisions and to treat them with the care they deserve.

The decisions that required time

There were moments in this project where we sat with a decision for weeks. Not because we were stuck or afraid, but because the decision mattered enough to warrant that time. We want to talk about some of those categories — not the specific instances, but the shape of the choices.

Partnerships. There were organisations and individuals who came to us early with offers of collaboration. Some of them were genuinely exciting. Some of them were compelling in ways that were hard to argue with — reach, resources, credibility in their own domains. We did not take most of them.

Why? Because a partnership is not just a distribution channel. When you are building permanent infrastructure for a place — for Queensland, for Brisbane, for the Gold Coast, for communities that have identities they’ve spent generations building — the partnerships you take on become part of what you are. They are endorsements in both directions. We will carry the associations we form. And so we asked harder questions than just “does this expand our reach?” We asked: do we believe in what they’re doing? Do their incentives align with ours over a long horizon, not just a short one? Are they building something that will still be standing in a decade, or are they capturing a moment?

Most of the time, that question answered itself quickly. Occasionally it took weeks of conversations, of watching how an organisation behaved, of understanding whether what they said about themselves matched how they operated. We walked away from things that looked like good opportunities by conventional metrics. We don’t regret any of it.

Features. There were features we could have shipped faster. There are features that, technically, were achievable earlier than we shipped them. We chose not to.

This sounds counterintuitive in a world where the conventional wisdom is to release early, gather feedback, and iterate. That advice is sound for many things — for applications, for consumer products, for things where the experience of the product can evolve without the underlying record changing. But when the thing you are releasing is an onchain record, the underlying data structure matters in ways that applications don’t. You cannot easily migrate an onchain record to a new schema once people have built on top of it. You cannot tell people their permanent addresses will work differently next year because you figured out a better architecture.

So we thought harder before we committed. We asked whether a feature was genuinely ready — not just technically functional, but architecturally sound in a way we were willing to stand behind permanently. Sometimes the answer was not yet. Sometimes a feature that looked like a quick win required a longer conversation about second-order effects. We had those conversations. They took time.

The community. This one is more nuanced, but it might be the most important.

There is a version of community building that is really audience acquisition. You find the right channels, you optimise the right messages, you grow the numbers, and you call it community. It’s not, though. It’s an audience. Audiences are passive. Audiences disperse when the content stops being interesting. Audiences have no particular investment in the thing they’re watching.

Community is different. Community is people who have skin in the game — not necessarily financially, but intellectually and reputationally. Community is people who care enough to push back when something isn’t right, to defend the project when it’s misunderstood, to tell their neighbours and their colleagues not because they were asked to but because they genuinely believe in it.

You cannot acquire that. You can only cultivate it, and cultivation is slow by nature. We spent time talking to people individually. We spent time in conversations that had no immediate payoff — no announcement, no launch, no number going up. We spent time listening to people who were sceptical, who had questions we didn’t have clean answers to yet, who needed more than a pitch deck to be convinced. Some of those people became the clearest thinkers in what we’re building around. Some of them challenged assumptions we’d stopped questioning. All of it took time that, from the outside, would have looked like nothing happening.

Why slow is not the opposite of serious

We want to be clear about something, because it’s easy to misread what we’re saying. Slowness is not seriousness. Moving carefully is not the same as caring deeply. You can move slowly and still be unfocused, undisciplined, or directionless.

What we’re describing is not an attitude toward pace. It’s an attitude toward quality and permanence. The slowness is a side effect of a deeper commitment, not the commitment itself.

The commitment is this: we are building something that is meant to outlast us. The addresses that people register on our infrastructure are not products we can discontinue. They are not services we can shut down when the economics stop working. They are permanent records that belong to their holders, and that permanence is the whole point. People who register a .brisbane address are making a decision they expect to hold for life. That is the promise. We take that promise seriously.

Taking it seriously means being serious about the decisions that affect it — decisions about architecture, about partnerships, about what we commit to publicly. And being serious about those decisions requires time that faster-moving projects don’t spend.

This is not a disadvantage. We used to frame it as a trade-off: we move more slowly, but we build more carefully. That framing concedes too much. Moving carefully is not a handicap you accept in exchange for quality. Moving carefully is what produces quality. There is no version of building permanent infrastructure well that involves cutting corners on the decisions that will be hardest to revisit.

The projects that move fastest are often the ones most constrained by their own early decisions. They shipped something, people built on it, and now they cannot change it without breaking things. Their speed became a cage. We chose not to build that cage.

What it looks like from the outside

We should be honest about this: from the outside, careful building is largely invisible.

When you are spending three weeks thinking through the implications of an architectural decision, nobody can see that. When you are evaluating a potential partnership over multiple conversations spanning months, there’s no announcement. When you are cultivating a conversation with someone sceptical rather than acquiring an enthusiastic follower, there’s no metric that captures it.

The outside world measures activity. Announcements, launches, updates, follower counts, engagement numbers. None of those things are bad, and we produce them too. But they are not the substance of what we are doing. They are surface.

The substance is in the decisions we described above — the ones that take time, the ones that don’t produce announcements, the ones where the right outcome is often choosing not to do something. None of that is visible. It looks, from the outside, like not much is happening.

We’ve had to make peace with that. Not because we’re indifferent to how we appear, but because we understand what the alternative is. The alternative is optimising for the appearance of activity. Announcing things before they’re ready. Shipping features that aren’t sound. Taking partnerships that expand our reach but compromise our direction. We have seen, too many times, what happens to projects that do that. They look busy right up until the moment they collapse.

We would rather look quiet and be solid.

The specific weight of building for a place

There is something particular about what we’re doing that adds weight to all of this. We are not building generic infrastructure. We are not creating a namespace for abstract users on the internet. We are building permanent digital infrastructure for Queensland — for Brisbane, for the Gold Coast, for Surfers Paradise, for the communities that have identities rooted in specific places.

That changes the stakes in a way that took us time to fully appreciate.

Place is not a brand. Place is not a product category. Place is identity — layered, complex, contested, beloved. When you attach permanent onchain addresses to a place, you are entering into a relationship with that place’s identity. You are saying: the people who live here, who grew up here, who built their lives here, can now have a permanent digital address that reflects that reality. A .queensland address is not just a technical identifier. It’s a statement of belonging.

That is a significant thing to be responsible for. And it changes how you make decisions. You cannot rush your way into being a trusted steward of a place’s digital identity. You cannot acquire that trust through clever marketing. You earn it by behaving, over time, in ways that are genuinely consistent with what you said you would do.

This is why we think about Queensland not just as a market but as a community we are accountable to. The people who will register .brisbane addresses are not customers in a transactional sense. They are people making a permanent decision about their digital identity. The minimum we owe them is that we built the infrastructure they’re registering on with the same permanence in mind.

We talk about this internally a lot. When a decision comes up — technical, commercial, community-related — we ask whether it serves the long-term health of what we’re building for Queensland, or whether it serves a short-term metric. It’s not always a clean distinction. But asking the question changes how decisions get made.

On not having all the answers

One of the stranger things about building slowly and carefully is that it gives you more time to be uncertain — and uncertainty is uncomfortable.

If you’re moving fast, you don’t have time to sit with the things you don’t know. You make a call, you ship it, you move on. The pace itself is a kind of resolution. Slow building doesn’t give you that. When you take three weeks to think through a decision, you have three weeks to notice everything you’re unsure about.

We’ve sat with a lot of uncertainty. About specific technical choices. About the right way to grow the community without distorting it. About how to communicate what we’re building to people who don’t have context for onchain infrastructure. About what success looks like in a decade, not just next quarter.

We don’t think uncertainty is a problem to be solved. We think it’s a signal that you’re taking the question seriously. The projects that are never uncertain have usually just stopped asking the hard questions. We prefer the discomfort of genuine uncertainty to the false comfort of premature certainty.

What we’ve tried to do with uncertainty is sit in it long enough to distinguish between the things we genuinely don’t know yet and the things we’re avoiding because the answer is hard. Both produce uncertainty, but they require different responses. The first requires patience and continued observation. The second requires honesty and courage.

We’ve tried to be honest with each other about which kind of uncertainty we’re in at any given moment. That’s easier said than done. It requires a culture of directness and a willingness to hear uncomfortable things. We’ve worked on that culture as deliberately as we’ve worked on the infrastructure.

The discipline of not shipping

There is a kind of discipline that nobody talks about in building technology, and that’s the discipline of not shipping.

Every team has things they could release. There are always features in a state that could be described as ready — technically functional, not obviously broken, probably fine. The pressure to release them is real. It comes from investors, from community expectations, from the internal anxiety of feeling like you’re not moving forward.

The discipline of not shipping is the capacity to look at something that is probably fine and ask whether it’s actually right. Not just whether it works, but whether it’s the right thing to build, built in the right way, at the right time. Whether the decision to ship it is a decision you’ll be comfortable with in five years, not just five months.

We’ve held things back that were ready in the narrow technical sense. We’ve delayed announcements for things that were exciting but not yet anchored in the depth of context they needed. We’ve had conversations internally that ended with “not yet” and then continued the work.

This is not perfectionism. Perfectionism is the refusal to ship because nothing is good enough. What we’re describing is more like integrity in the engineering sense — the structural integrity of not cutting corners that will compromise the whole. You can identify a corner that was cut in a building’s foundation by watching how the building behaves over decades. You identify corners cut in infrastructure the same way.

We are building for decades. That changes the threshold.

What the team actually looks like

We want to say something about the people doing this work, without getting specific in ways that would personalise this beyond what’s useful.

This is not a team that is here for a fast exit. That’s worth saying plainly. We are not building this to sell it. We are not building this to flip it. We are not treating Queensland’s digital identity infrastructure as a vehicle for a transaction. The people working on this believe in what permanent onchain addresses can mean for a place, and they’re here for the duration of what it takes to make that real.

That affects everything about how the work gets done. When you know you’re going to be living with the decisions you make today for a long time, you make them differently. When you’re accountable to a community that you’re actually part of — people you’ll encounter, conversations you’ll have — the incentive structure is completely different from a team that is geographically and socially distant from the people they’re serving.

We are Queenslanders building for Queensland. That is not a marketing statement. It is a description of a real accountability relationship. The people building this will be at the events, in the conversations, embedded in the community that these addresses serve. There is no version of this where we build something shoddy and then leave.

That rootedness is slow by nature. It is also, we believe, exactly the right kind of constraint to have.

The long arc

We think about time differently than most technology projects do. The standard planning horizon in technology is quarters — sometimes years, rarely decades. We think in decades.

What does it mean for Queensland to have a permanent layer of digital identity infrastructure? What does it mean when a generation grows up knowing that their address — their .queensland, their .brisbane — is theirs permanently, not leased from a company that could change its terms? What does it mean for the Gold Coast’s digital presence when the infrastructure underlying it is owned by the community it represents, not by a multinational registrar?

We don’t have clean answers to those questions. We’re not sure anyone can. But we hold them, and they shape the decisions we make. Infrastructure that is built for decades is built differently than infrastructure built for this year’s metrics. The materials are different, the foundations are deeper, the pace is slower.

We are comfortable with that. More than comfortable — we think it’s the only way to do this right.

Slow building as a form of respect

We want to close with something that doesn’t often get said in the language of building things, which is that how you build is a form of respect.

Respect for the people who will use what you build — who will register permanent addresses, attach their digital identities to them, build on them. They deserve infrastructure that was built carefully enough to actually be permanent.

Respect for the place whose name you’re building with. Queensland is not a product name. It is a place with history, identity, and people who care about it. Building slowly enough to understand what that means, and to build in a way that honours it, is the minimum standard.

Respect for the permanence you’re promising. When you tell someone that something is permanent, you have made a commitment of the highest order. Permanent does not mean “until we change the model” or “as long as we’re funded” or “unless something better comes along.” Permanent means permanent. Living up to that commitment begins in how you build, long before anyone is using what you’ve made.

And respect for yourselves — for the people on this team who are investing their time and thought and care into something they believe in. Cutting corners is a form of disrespect toward your own work. The discipline of building slowly, of taking the time that hard decisions require, of not shipping things that aren’t right yet — that is a way of saying that the work matters enough to be done well.

We believe it does. We’ve always believed it does. That belief is, in the end, why we build the way we build — not as a strategy, not as a philosophy, but as the only honest response to what it means to build something permanent for a place we love.

Queensland Foundation is building permanent onchain address infrastructure for Queensland, Australia. Six TLDs. One payment. No renewals. No expiry.