There is a version of Queensland Foundation that does not exist. It is bigger, louder, and more complicated than the one we built. It has more features, more partnerships, more revenue streams, more flexibility. It speaks to more audiences and promises more things to more people. It is the version we almost built, many times, before we learned to say no.

That version would have been a mistake.

Every project carries within it a ghost of what it could have been. A shadow-self made from the decisions not taken, the ideas shelved, the partnerships declined, the features cut. Most teams never talk about that ghost. They talk about what they built, what they launched, what they added. The additions feel like progress. The removals feel like failure, or at best, like something to be embarrassed about — evidence that you considered something and then couldn’t make it work.

We think about it the opposite way. The things we cut are the things we are most proud of. Not because we enjoy saying no, but because every no we said with clarity and intention made the yes we eventually said more honest, more durable, and more true to the reason we started in the first place.

This post is about those cuts. What we removed, what we considered and rejected, and what those decisions collectively say about what we are actually trying to build.

Why cutting is so hard

Before we get to the specifics, it is worth being honest about why cutting is difficult — because if it were easy, every project would do it well, and they do not.

The pressure to add is constant and comes from every direction. It comes from potential partners who want to see their idea incorporated before they commit. It comes from early supporters who suggest features that would make the product more useful for their particular use case. It comes from adjacent projects who want to collaborate in ways that require you to expand your scope. It comes from competitive anxiety — the fear that if you do not add a feature that another project has, you will lose.

There is also a subtler internal pressure that is harder to name. When you believe in something, you want it to succeed. And because success feels uncertain, you find yourself wanting to hedge — to build escape routes, to keep options open, to make the project a little more like the things that have already succeeded. Adding features feels like adding safety. Narrowing feels dangerous.

We felt all of this. Every single pull of it.

The discipline we had to develop was not about becoming immune to those pressures. It was about learning to interrogate each pressure carefully enough to understand whether it was pointing toward something true or toward something merely comfortable.

A feature request is not automatically wrong. A partnership opportunity is not automatically a compromise. The question is always: does this move us toward the thing we actually believe, or does it move us away from it? And answering that question honestly, consistently, over a long period of time, while people are pushing and the stakes feel real — that is where character gets built.

The subscription model we could have built

Let us start with the most obvious one, because it is the one that surprised people most when we explained our decision.

We could have built Queensland Foundation as a subscription business. Almost every comparable infrastructure project in this space charges annual fees. It is a defensible model. It generates predictable recurring revenue. It gives the project ongoing financial justification for continued development. It aligns, on the surface, with how most people understand software businesses to work.

We looked at that model seriously. We ran the numbers. We understood the mechanics. And then we cut it.

The reason we cut it is not primarily financial, although the financial logic of our actual model is sound. The reason we cut it is that annual fees are philosophically incompatible with what we believe about ownership.

When you pay annually for something, you do not own it. You lease it. The distinction matters more than it might initially appear. A lease is always conditional. It depends on your continued payment, on the continued existence and goodwill of the lessor, on your ability to maintain the relationship indefinitely. The moment you stop paying — for any reason, because of financial hardship, because you forget, because the company changes its pricing, because you die and your estate does not know about the renewal — the thing disappears. It was never yours.

We are building onchain addresses that we want Queenslanders to own. Not use. Not access. Own. The moment we attached a renewal requirement to that ownership, we would have been lying about what it is. We would have been calling something ownership that was actually tenancy.

So we cut the subscription model. We cut it knowing that it would limit our short-term revenue ceiling. We cut it knowing that some investors would be sceptical. We cut it because keeping it would have required us to be dishonest about the nature of the thing we were building, and we were not willing to do that.

The discipline here was refusing to let revenue logic override mission logic. Those two things should ideally align. When they do not, you have to decide which one is primary. We made that decision once, clearly, and we have not revisited it.

The national expansion we did not pursue

At some point in the early thinking around this project, someone asked: why limit this to Queensland?

It is a reasonable question. The infrastructure we are building is not physically constrained by geography. There is nothing technical stopping us from securing onchain TLDs for every Australian state, or for Australian cities outside Queensland, or for regions in other countries. The playbook would be similar. The technology is the same. The market would be larger.

We thought about it. We talked about it at some length. And then we cut it entirely.

Here is why. What we are doing is not primarily a technology project, even though it is built on technology. It is a place-based identity project. It is about giving a specific community — Queenslanders — a form of digital belonging that is rooted in where they actually are, where they grew up, where they chose to live. That rootedness is not incidental to the project. It is the project.

The moment you expand to every state, you dilute that. You become a generic infrastructure provider. You become the company that does this for anyone. And when you are the company that does it for anyone, you are not particularly committed to the people you are doing it for. There is no genuine investment in the community, only in the category.

We wanted to be genuinely invested in Queensland. In the culture here, the history, the way Queenslanders think about themselves and their place in the world. That investment requires constraint. It requires saying: we are not for everywhere. We are for here.

There is also something more practical at work. Focus creates quality. When you have a single, bounded scope, you can go deep rather than wide. You can think carefully about what the community you are serving actually values. You can get things right in a way that is impossible when you are simultaneously trying to serve dozens of different communities with different histories, different identities, and different needs.

Expanding nationally would have made us bigger. It would not have made us better. And in a project where better matters more than bigger, that is a cut worth making.

The features that would have added complexity

This is perhaps the category where we made the most decisions, because the surface area of possible features is enormous and the temptation to build them is constant.

Subdomain marketplaces. We considered building an integrated marketplace where holders of top-level addresses could subdivide and sell or rent subdomains. The economics looked interesting. The demand would plausibly be real. We cut it because it would have transformed the nature of what we are building — from a simple, permanent ownership instrument into a platform with ongoing complexity, disputes, and the need for governance mechanisms we did not want to create. We are building addresses, not real estate businesses. The moment we built a marketplace, we became a landlord infrastructure provider. We did not want that.

Expiry and resale mechanisms. Some projects in adjacent spaces build in expiry — if you do not use an address within a certain period, it returns to the pool and can be claimed again. The argument for this is efficiency. Addresses that are not being used should not be locked away from people who would use them. It is a reasonable argument. We rejected it because it reintroduces conditionality into ownership. If your address can expire because of inactivity, you do not fully own it. You own it contingently. We were not willing to build contingent ownership. Permanent means permanent.

Profile and identity layers. At various points we discussed building richer identity features on top of the address infrastructure — profile pages, linked social accounts, reputation systems, attestations. These are genuinely interesting problems. Some of them are being worked on by smart people elsewhere in the ecosystem. We decided not to build them, not because they are bad ideas, but because they are not our idea. Our idea is the address — the permanent, onchain, place-based identifier. Everything else is built on top of that, and it should be built by the people with the right expertise and the right focus for those specific problems. We chose to be excellent at the thing we are building rather than mediocre at a longer list of things.

Governance tokens. We were asked several times why we were not issuing governance tokens — a mechanism that would give holders some form of voting power over the direction of the project. There are good arguments for decentralised governance in some contexts. We decided against it, primarily because governance tokens in practice often serve to complicate rather than clarify decision-making, and because we did not want to introduce financial instruments that could distort the incentives around what we are building. We want people to value their Queensland address because it is a meaningful piece of identity, not because they are speculating on the governance potential of a related token.

Tiered pricing based on perceived value. The question of whether premium names — short names, famous names, names with obvious commercial value — should be priced differently from standard names is not a trivial one. There is a credible argument that a single-character address or a name like brisbane.brisbane is worth more than a long arbitrary string and should be priced accordingly. We thought about tiered pricing seriously. We cut it for a few reasons. The first is simplicity — a single price for all addresses is easier to understand and easier to trust. The second is equity — we did not want to create a world where access to meaningful Queensland identity is gatekept by the ability to pay a premium. The third is that value is subjective and personal. The address that matters most to one person may seem worthless to another. We did not want to be in the business of pre-assigning meaning to names.

The partnerships we declined

Partnerships are seductive. They feel like growth, like legitimacy, like proof that what you are doing matters to other people. And some partnerships genuinely are those things. But many are not, and the discipline of telling the difference is something you have to develop over time.

We were approached by parties who wanted to co-brand the project. To attach their identity to ours in ways that would give them a piece of what we were building in exchange for visibility, distribution, or capital. We declined every version of this conversation.

The reason is straightforward. Co-branding is not just a marketing arrangement. It is a statement about what the project is. If Queensland Foundation becomes Queensland Foundation in partnership with [entity], the nature of the project changes. The addresses we are building are supposed to represent something genuine — a connection to Queensland as a place and a community. If they become associated with a corporate or commercial entity that has its own interests, its own agenda, and its own needs, that connection becomes muddied. The addresses start to mean something different.

We also declined partnerships that would have required us to give third parties influence over which addresses were available, how they were allocated, or what they could be used for. The permanence and neutrality of the addresses depends on our not having made deals that compromise those properties. Every carveout, every exclusive arrangement, every reservation made for a partner’s benefit is a hairline fracture in the integrity of the system.

We are aware that declining these arrangements has costs. It means less early capital, less early distribution, less early credibility from borrowed legitimacy. We accepted those costs because the alternative — building a project whose integrity we could not fully stand behind — was worse.

There were also partnerships we declined not because they were compromising but simply because they were distracting. Good ideas that were adjacent to what we are doing but not central to it. Projects whose values were fine but whose focus was different from ours. Collaborations that would have been interesting but would have required us to spend time and attention on things that were not our core work. The discipline here is recognising that not every distraction is bad, and that you can decline a good idea without that being a rejection of the idea itself.

The audiences we chose not to speak to

This is perhaps the most counterintuitive cut of all, but it is one of the most important.

A natural impulse when building something is to make it legible to as many audiences as possible. To explain it in the language that resonates with investors, and also in the language that resonates with developers, and also in the language that resonates with mainstream consumers who have no background in blockchain infrastructure. To be all things to all people.

We cut that impulse.

The primary audience for Queensland Foundation is Queenslanders — people who feel a genuine connection to this place and for whom a permanent, onchain Queensland address means something personal. That is not a small audience in absolute terms, but it is a specific one in character. Speaking to that audience well requires a different register than speaking to crypto-native investors, or enterprise blockchain buyers, or technology journalists.

When you try to speak to all those audiences simultaneously, what you end up with is a voice that speaks clearly to none of them. You develop a kind of communicative mush — language that hedges in every direction, that tries to signal sophistication to the sophisticated while remaining accessible to the newcomer, that uses enough crypto terminology to seem credible in those circles while carefully explaining everything in case someone has never heard of a blockchain.

We decided to speak to the people we are actually building for. To write and communicate as if the reader is someone who lives in Queensland, who cares about Queensland, and who might be curious about what it means to own a piece of their home’s digital future. If crypto-native investors find that compelling, wonderful. If they do not, we are not trying to move them.

The discipline here is resisting the pressure to inflate your audience in your own mind. It is tempting to believe that you are building for everyone, because believing that makes the project feel more important. But building for everyone is building for no one. The specificity of your audience is part of what makes your work meaningful to the people who are inside it.

The urgency we refused to manufacture

One of the quieter cuts we made was a decision about how to think about and communicate time.

There is a well-established playbook in both marketing and product development for manufacturing urgency. Limited-time offers. Scarcity mechanics. Countdown clocks. The implication — sometimes explicit, sometimes atmospheric — that if you do not act now, you will lose something. This playbook works. It generates action. It compresses decision-making timelines.

We cut it completely.

The reason is that manufactured urgency is a form of dishonesty. It is telling people that something matters more right now than it actually does, in order to influence their behaviour. And more importantly, it is philosophically incompatible with what we are building.

A permanent address — something you own for life, with no renewal, no expiry, no ongoing cost — is the opposite of urgent. It is patient. It is there when you want it. The value of it does not diminish because you waited a month or a year to claim it. If anything, the permanence of the infrastructure means that claiming it later is only marginally different from claiming it now, in any practical sense.

We are not interested in pressure. We are interested in genuine conviction. We would rather someone claim their Queensland address because they have thought about it and decided it means something to them than because a countdown timer made them anxious. The former is a real relationship with the project. The latter is a transaction driven by anxiety.

This cut has implications for how we write, how we communicate, and how we think about the pace of our own growth. We accept that growth driven by genuine conviction is slower than growth driven by artificial urgency. We think it is more honest, more durable, and more aligned with the kind of project we want to be.

The complexity we refused to hide

There is a version of this project that pretends the underlying technology does not exist. That papers over the blockchain infrastructure with a friendly consumer interface and never mentions the words “onchain,” “smart contract,” or “immutability.” That tries to be so seamless that the user never has to think about what is underneath.

We considered this approach. It has real appeal. Complexity is a barrier to entry. Many people who might genuinely value what we are building are put off by the vocabulary and conceptual overhead of blockchain infrastructure.

But we cut the “hide the complexity” approach for a reason that goes to the heart of what we believe.

The permanence, the immutability, the transferability — these are not just features. They are properties that arise directly from the nature of the infrastructure. They are meaningful precisely because of what is underneath. If we hide the infrastructure, we also obscure the reason to trust the properties. We are asking people to believe that their address is permanent and will never be taken away. The honest answer to the question “why should I believe that?” is: because of how it is built. Because it is onchain. Because no single entity, including us, can revoke it.

If we hide the technology, we are asking for a kind of trust that is essentially faith in us as a company — which is exactly the kind of trust that the technology is designed to make unnecessary.

So we did not hide it. We made a commitment to explain it clearly, in plain English, without jargon where jargon is avoidable, but without pretending the infrastructure is not there. This means some people will bounce because the concept is unfamiliar to them. We accept that. The people who stay and engage are doing so with a real understanding of what they are getting, and that understanding is part of what makes the relationship genuine.

What the cuts say about what we believe

Read together, these decisions form a kind of implicit manifesto. Not one we set out to write, but one that emerged from consistently applying the same values to different decisions over time.

We believe in genuine ownership — which means we cut anything that made ownership conditional.

We believe in place-based identity — which means we cut anything that diluted our commitment to Queensland specifically.

We believe in simplicity as a virtue — which means we cut features that added complexity without adding meaning.

We believe in honest communication — which means we cut urgency tactics, hidden complexity, and language designed to manipulate rather than inform.

We believe in focus — which means we cut partnerships, markets, and audiences that would have spread our attention beyond what we can do well.

None of these cuts were easy. Most of them had real costs in the short term. All of them, we believe, made the project more coherent, more honest, and more worth building.

The ongoing discipline

Here is the thing about cutting: it is not something you do once, at the start, and then move on. It is a continuous practice. The pressures to add, to expand, to hedge, to accommodate — they do not stop. Every week brings new ideas, new opportunities, new arguments for why this particular exception to the principles is actually fine.

The work is not to become rigid or dogmatic. Principles should be revisited. Cuts should be interrogated. It is possible to have said no to something at one point and to discover later that the no was wrong and that the right move is to revisit it. We are not building a monument to our own consistency. We are building something we want to work.

But the default posture — the starting assumption in any conversation about adding or changing something — has to be scepticism. Has to be: what are we giving up if we add this? What is the cost, not just in resources or time, but in clarity of purpose? Does this move us toward the thing we believe, or away from it?

That posture is not natural. It is developed. It is something you build through practice, through having made the wrong call a few times and understanding why, through having said yes to something that should have been a no and feeling the consequences of that in the way the project drifted.

We are still developing it. We will be developing it for as long as we are building.

On the ghost of what we could have been

We return, at the end, to that larger, louder, more complicated version of Queensland Foundation that does not exist.

It is easy to romanticise that version. To imagine the additional revenue, the broader reach, the more impressive deck. To wonder whether we were too conservative, too principled, too unwilling to compromise.

But when we think carefully about what we are actually trying to do — give Queenslanders a permanent piece of their digital home, built on infrastructure that cannot be taken away, priced honestly and owned genuinely — none of the things we cut would have made that better. They would have made it different. And different, in this case, means less true.

The ghost is not something we mourn. It is a reference point. A reminder that every decision to cut is also a decision to keep — to keep the thing that actually matters, free from the weight of everything that would have diluted it.

Cutting is building. It is just building by removal rather than addition. And sometimes, the most important work you do is the work of deciding what not to make.