We had a choice early on. Almost every technology project faces it, usually without naming it explicitly. You can build quietly — heads down, doors closed, nothing shared until it’s ready — or you can build in the open, letting people see the work as it happens, the thinking as it forms, the mistakes as they occur.

We chose to build in public. This is an attempt to explain why, what that has meant in practice, and what we’ve learned about the tension between openness and care when the thing you’re building is meant to serve as infrastructure for a place and a people.

The Temptation to Build in Secret

There is a seductive logic to the closed approach. You control the narrative. You control the timing. You can fix the mistakes before anyone sees them. You can present something polished, confident, and complete — and the world’s first impression of your work is its best version.

We understood that temptation deeply. There were moments in the early period of this project where the closed approach felt not just tempting but obviously correct. We were working on something genuinely new. Permanent onchain addresses for Queensland — .queensland, .qld, .brisbane, .surfersparadise, .gold-coast, .brisbane2032 — are not an iteration on something that already exists. They are not a slightly better version of a web domain. They are a different kind of thing entirely: a permanent, immutable, transferable record of identity and place that a person can own once, for life, with no renewals and no one who can take it away.

When you’re building something that doesn’t have a clear predecessor, you are also building the vocabulary for explaining it, the mental models people will use to understand it, and the trust architecture that will make people believe it’s real and worth caring about. Doing all of that in the open, before it’s finished, before you’ve worked out your own answers, is genuinely frightening.

So we understood the closed approach. We just didn’t take it.

What Building in Public Actually Means

Before we go further, it’s worth being precise about what we mean, because “building in public” has become a phrase that gets used loosely.

For some projects, it means a founder posting updates on social media. For others, it means open-source code. For others still, it means a public roadmap or a changelog. All of these are legitimate expressions of the idea. But none of them, on their own, capture what we were actually committing to.

What we committed to was something more uncomfortable than a changelog. We committed to sharing the reasoning behind decisions, not just the decisions themselves. We committed to naming the things we weren’t sure about. We committed to letting the process of thinking through hard problems happen in front of people rather than behind closed doors, even when that process was messy and slow and included wrong turns.

This is harder than it sounds. There is a significant difference between sharing your conclusions and sharing your thinking. Conclusions are clean. Thinking is not. Sharing your thinking means occasionally sharing conclusions that you later revise, which opens you to the charge of inconsistency. It means sharing doubts, which opens you to the charge of uncertainty. It means letting people see that you didn’t know something before you figured it out, which opens you to the charge of having been unqualified.

These are real costs. We accepted them because we believed the alternative cost was higher.

Why Civic Infrastructure Cannot Be Built in Secret

Queensland Foundation is not a consumer product. It is not a game, a social network, or a marketplace. What we are building is infrastructure — a naming layer for Queensland that is designed to persist for as long as the blockchain infrastructure beneath it persists, which is to say: for as long as anything digital persists.

When something is infrastructure, the relationship between the builder and the user is fundamentally different from the relationship between a product and its customer. A customer buys a product and evaluates it on its own terms. A community builds its identity on top of infrastructure and stakes something of itself on the reliability and integrity of that infrastructure. The stakes are different. The expectation of accountability is different.

Think about the other kinds of infrastructure Queenslanders rely on. Roads. Water. Power grids. None of these were built in secret. Their construction was public, regulated, documented, debated, and scrutinised. The accountability wasn’t just a nice feature — it was intrinsic to the trust that made it possible for people to build their lives on top of them.

We believe onchain naming infrastructure deserves the same treatment. If someone registers a .queensland address, they are making a decision to associate part of their identity — professional, civic, personal — with a permanent record. That permanence is the entire value proposition. But permanence only matters if the foundation it rests on is trustworthy. And trust, when it comes to infrastructure, cannot be manufactured after the fact. It has to be built in, and the building has to be visible.

This is not a philosophical position we arrived at after careful deliberation. It’s a practical conclusion that emerged from asking ourselves a simple question: would we register a permanent address with a project that had given us no window into how it was built, what it had decided, and why? The honest answer was no. And if we wouldn’t, we had no business expecting anyone else to.

The Specific Tension We Navigated

Building in public does not mean building carelessly. This is the tension we’ve had to navigate most carefully, and it’s worth being honest about how real it is.

There are things that cannot be shared while they’re in process without creating harm. Legal considerations. Security architecture. Conversations with partners that are confidential by mutual agreement. Technical implementations where premature disclosure creates vulnerability. These aren’t excuses for secrecy — they are legitimate constraints that anyone building real infrastructure has to respect.

The line we tried to hold was this: we would be transparent about the nature of our decisions, even when we couldn’t be transparent about every detail of those decisions. If we were working through a legal question, we would say we were working through a legal question, describe the shape of it in general terms, and explain why it mattered, even if we couldn’t share the specifics of the advice we’d received or the exact resolution we’d landed on. If we were navigating a technical challenge, we would describe the challenge, explain its significance, and share what we’d learned — even if the specific implementation details needed to remain private for security reasons.

This distinction between transparency of intent and transparency of detail is important and often overlooked. Radical transparency that exposes security vulnerabilities is not a virtue. But transparency about the existence of challenges, about the reasoning behind choices, about the values that are guiding the work — this is always possible, and always worth doing.

The other tension is speed. Building in public is slower. Every piece of thinking you share has to be considered before it’s shared. Not polished into corporate smoothness, but considered — honest, clear, and fair to the complexity of what you’re actually dealing with. This takes time. There were moments when we wanted to move faster than our commitment to openness allowed.

We chose to accept that slower pace because we believed it would produce something more durable. Not just more trusted by people outside the project, but more sound in its internal reasoning. When you know your decisions will be visible, you make better decisions. Not because you’re performing for an audience, but because the discipline of articulation — of being able to explain your reasoning clearly to someone who doesn’t already share your context — is one of the most effective tests of whether the reasoning is actually good.

What We Learned About Trust

We learned something about trust that we hadn’t fully anticipated when we started.

Trust in a new kind of infrastructure — something that has no direct predecessor, something people are encountering for the first time — does not accumulate through declarations. You cannot say “trust us, this is permanent and secure” and have people believe it. That’s not how trust works. It doesn’t matter how sincerely you mean it.

Trust accumulates through repeated, verifiable demonstrations of integrity over time. It accumulates when people can see that you said you would do something, and then you did it. It accumulates when people can see that you encountered a difficult situation, and you described it honestly rather than managing it into a positive-sounding announcement. It accumulates when people can see the texture of how decisions get made, not just the outcomes.

Building in public is, fundamentally, a trust-generation mechanism. Not a marketing mechanism — a trust mechanism. These are not the same thing. Marketing optimises for persuasion. Trust-building optimises for accuracy. When you’re building infrastructure that people will stake part of their identity on, accuracy is the asset you need to accumulate, not persuasion.

There is a version of “building in public” that is actually a form of marketing — a curated stream of exciting updates, milestones presented as breakthroughs, challenges framed as proof of the team’s resilience. We tried hard not to do that. Not because we have anything against excitement or milestones, but because the moment your public transparency becomes a performance, you’ve lost the thing that makes it valuable.

The way you know you’re doing it honestly is that it sometimes feels uncomfortable. The discomfort of sharing something you’re not sure about, or describing a setback accurately rather than reframing it into a learning opportunity, or admitting in public that you’ve changed your mind — that discomfort is the sign that you’re doing it right.

Queensland, and Why Place Matters

There is something specific to this project that shaped our thinking about transparency in ways that a generic infrastructure project might not encounter.

We are building for a place. A specific, real, inhabited place. Queensland is not an abstract jurisdiction — it is a community of people with a shared geography, a shared culture, a shared history, and a shared future. The TLDs we secured — .queensland, .qld, .brisbane, .surfersparadise, .gold-coast, .brisbane2032 — are not just strings of characters. They are references to real places that real people are attached to in deep and personal ways.

When you build infrastructure that is bound to a place in this way, you are not a neutral party. You are a steward of something that belongs, in a meaningful sense, to the people of that place. That stewardship carries obligations. One of the most fundamental of those obligations is to be accountable to the community you are building for.

Accountability, in this context, is not just about being answerable when things go wrong. It is about keeping the community informed and engaged in the work as it happens — so that when it’s complete, it is genuinely something they had a hand in, or at least a view into, rather than something handed to them by strangers who made all the decisions behind closed doors.

This is especially important because of the nature of what we’re building. Permanent onchain addresses are not reversible. When someone registers a .brisbane address, that registration is immutable. It persists. It is theirs. The permanence is the point. But permanence also means that the decisions made in building the underlying infrastructure are baked in. There is no patch for a bad architectural decision ten years from now if the architecture is permanent. The only way to ensure the permanence is worth trusting is to build the architecture right, in the open, with people watching.

We felt the weight of that. We still do. It is not comfortable to build something permanent in public, because it means that your public record — the reasoning, the decisions, the moments of uncertainty — is also, in a sense, permanent. But we decided that the discomfort was appropriate. It was the right kind of accountability for the right kind of project.

The Relationship Between Openness and Craft

One thing we want to push back on is the idea that building in public is somehow in tension with craft — with the care and quality of the work itself. We’ve heard this argument: “If you spend time writing about what you’re doing, you’re taking time away from doing it. Build first, explain later.”

We don’t believe this. In our experience, the relationship runs the other way. The discipline of articulating your work publicly — of describing what you’ve built, why you built it that way, what trade-offs you made, what you’d do differently — is itself a form of quality control. It forces clarity. It surfaces assumptions. It makes implicit decisions explicit, which is when you discover that some of those decisions weren’t as deliberate as you thought.

There were several occasions in this project where the act of writing about a decision revealed that the decision wasn’t as well-considered as it had felt in the moment. The process of describing it clearly exposed a gap in the reasoning. And because we’d committed to building in public, we had to actually address the gap rather than hope no one noticed it.

This is an underappreciated benefit of the open approach. It’s not just that people outside the project get better information. It’s that the people inside the project are forced to do better thinking. The audience, real or imagined, creates an accountability structure that raises the quality of the work.

There is also something to be said for craft in communication itself. Writing clearly and honestly about a complex technical and civic project is a skill, and it is part of the work. Understanding how to explain a permanent onchain address to someone who has never thought about blockchain infrastructure — without condescending to them, without drowning them in technical detail, without oversimplifying into inaccuracy — is genuinely difficult, and getting it right matters enormously. If people cannot understand what we’ve built, they cannot evaluate it. If they cannot evaluate it, they cannot trust it. And if they cannot trust it, the whole enterprise fails regardless of how technically sound the underlying infrastructure is.

So we put real effort into communication, not as an afterthought or a marketing function, but as a core part of the work. And we believe that effort is inseparable from the commitment to building in public.

The Moments That Tested It

We want to be honest about the moments where our commitment to openness was hardest to hold.

The hardest moments were not when we had bad news to share. Sharing difficulty is uncomfortable, but it’s usually the right call, and once you’ve done it a few times you develop a kind of muscle memory for it. The hardest moments were when we had made a decision that we knew would be misunderstood, and we had to choose between explaining it badly in public — risking the misunderstanding — and staying quiet, which would look like opacity.

The instinct in those moments is to wait. Wait until the decision has played out. Wait until you have a full story to tell. Wait until the potential for misunderstanding has passed. This instinct is understandable, but we’ve learned to be suspicious of it. “Wait until we have more to say” is often indistinguishable, from the outside, from “we’re not going to tell you about this.” The distinction is invisible. And trust, once damaged by the appearance of opacity, is extremely slow to rebuild.

So our general rule became: if we’re uncertain about whether to share something, we share it, and we share our uncertainty about it too. “We’re working through something complex and we’re not ready to explain it fully, but here’s the shape of it” is better than silence. Not always comfortable. But better.

Another testing moment was early in the project, when we were still forming some of the fundamental decisions about scope and infrastructure, and we encountered perspectives — from people paying attention to what we were doing — that challenged assumptions we’d made without fully examining them. The open approach meant we had to engage with those perspectives honestly, in public, in real time, rather than absorbing them quietly and adjusting behind closed doors.

This was humbling. It was also useful. Some of those challenges led to better decisions. Others we worked through and reaffirmed our original thinking, but in doing so made the reasoning more rigorous. Either way, the engagement was valuable. And it only happened because we were visible.

What We Owe the Future

There is a temporal dimension to this that we think about a lot.

The people who will ultimately use Queensland Foundation — who will register .queensland or .qld or .brisbane addresses — are not just the people who are paying attention right now. They are also people who will discover the project years from now, who will evaluate it with the benefit of hindsight, who will look at the record of how it was built and draw conclusions about whether it can be trusted.

Building in public creates that record. The decisions we’ve made, the reasoning behind them, the challenges we’ve navigated — all of it is documented. Not perfectly, not exhaustively, but in enough depth that someone reading it years from now can reconstruct the spirit in which the work was done. They can see what we prioritised and what we were willing to sacrifice. They can see whether the commitments we made in the early period were consistent with the commitments we made later. They can see whether we were honest about hard things.

This matters enormously for a project that deals in permanence. We are asking people to make permanent decisions — to register addresses that will be theirs for life, with no expiry and no renewal. The confidence required to make a permanent decision of that kind rests partly on confidence in the permanence and integrity of the infrastructure beneath it. That confidence cannot be generated by claims about permanence and integrity. It has to be supported by evidence. The public record of how we built this is part of that evidence.

We think of it as a form of temporal accountability. We are not only accountable to people watching us now. We are accountable to people who will evaluate this work in the future, when we cannot shape their perception with a well-timed announcement or a carefully framed update. The record will speak for itself. That is exactly as it should be.

On the Mechanics of Blockchain and Transparency

It would be incomplete to write about building this project in public without noting that there is a layer of structural transparency built into the technology itself.

Blockchain infrastructure is, by its nature, a public ledger. Transactions are visible. Registrations are verifiable. The state of the system at any point in time is, in principle, auditable by anyone with the tools and the inclination to look. This is one of the properties that makes onchain infrastructure genuinely different from traditional web domains, where the registry is controlled by a private entity and the terms of that control can change.

We want to be honest about what this structural transparency does and doesn’t do. It guarantees that the data is visible. It does not, by itself, guarantee that the project is governed with integrity, that the community is served fairly, or that the decisions made in building the system were made for the right reasons. Structural transparency is necessary but not sufficient. The human layer — the decisions, the reasoning, the values — also has to be transparent, and that’s not something the technology provides automatically.

This is why we believe that the technical transparency of the blockchain and the narrative transparency of building in public are complementary rather than redundant. The blockchain ensures the data is honest. Building in public ensures that the people behind the data are honest. You need both.

Why We Would Make the Same Choice Again

We’ve tried in this piece to be honest about the costs of the open approach as well as the benefits. The costs are real: it’s slower, it’s uncomfortable at times, it creates vulnerabilities to misunderstanding, and it requires a discipline of articulation that takes genuine effort.

But we would make the same choice again. Not reluctantly, but with more confidence than we had the first time.

The reason is simple: we built something we believe in. We believe in the permanence of what Queenslanders will own when they register an address here. We believe in the value of place-based digital identity. We believe in the idea that a piece of Queensland infrastructure should be built with Queensland values: directness, durability, and a genuine relationship with the community it serves.

Those beliefs are not compatible with building in secret. If you believe the thing you’re building is genuinely good — not just good for a certain metric in a certain window of time, but good in a lasting, principled sense — then you should be willing to let people see how it was made. The quality of the process is part of the quality of the product. And if the process can’t stand the light, neither can the product.

There’s a version of this project that could have been built quietly, launched with a press release, and evaluated purely on its technical merits. We chose a different version. One where the merits are not just technical but moral. One where the community we’re building for is also the community we’re accountable to. One where the record of how we got here is part of what we’re offering.

We don’t think building in public makes us unusual or virtuous. We think it makes us appropriate to the kind of project this is. Infrastructure built for a community should be built in front of that community. That’s not an innovation. It’s just what accountability looks like when you take it seriously.

What We’re Still Figuring Out

This post would not be honest if it ended on a note of complete resolution. We’re still figuring things out. That’s true of any live project, but it’s worth naming specifically in the context of a post about transparency.

We are still figuring out the right cadence of public communication — how often to share, what level of detail is genuinely useful versus noise, how to make the record accessible to people who are encountering it for the first time without boring people who have been following closely.

We are still figuring out how to handle genuine disagreement in public — how to represent conflict or uncertainty within the project in a way that is honest without being disruptive or alarming to people who are trying to decide whether to trust what we’ve built.

We are still figuring out what it means for the project to mature over time in terms of how it communicates. The openness of an early-stage project — where almost everything is uncertain and the value of sharing thinking is very high — may need to evolve as the project stabilises. We don’t think stability means opacity. But we’re still working out what it means.

We share these uncertainties not to undermine confidence in the project, but because sharing them is consistent with the reason we wrote this post in the first place. Building in public doesn’t end when the project reaches a certain milestone. It’s an ongoing commitment. And like any commitment, it requires continual re-examination of what it means to honour it.

A Final Thought

If you’ve read this far, you’ve read a long piece about process and values rather than features and functionality. We hope that’s not frustrating. The features matter, and we’ve written about them elsewhere. But process and values are upstream of features. They shape everything else. And for a project like this one — building permanent infrastructure for a real place, asking people to stake a piece of their identity on its integrity — they matter more than usual.

We built this in public because we believed it was right. Not right in a vague aspirational way, but practically right — the only way of doing this that was consistent with what we were actually trying to achieve. Civic infrastructure requires civic accountability. Permanent infrastructure requires a transparent record. A project that asks for trust has to earn it, and earning it means being visible.

That’s why we built this in public. And that’s why we’ll keep doing it.