It started the way most of these conversations do — with a message that felt considered rather than cold. Not a templated pitch, not a bulk email, not someone who had clearly never heard of us before firing off a proposal. This was different. The person on the other end had done their homework. They knew what we were building. They referenced the right things. They asked smart questions. And the offer they eventually put on the table was, on its surface, genuinely compelling.

We took the meeting. We took a second one. We spent more time thinking about it than we probably expected to. And then we said no.

This post is about that process — not to relitigate it, not to position ourselves as principled heroes, and certainly not to take a shot at anyone we spoke with. We declined with respect, and we mean that. But we think there’s something worth writing down about what happened in our own thinking, because it forced us to articulate things we had previously left unspoken. Values that lived in our instincts rather than on any document. Criteria for partnership that we had never formally defined because we had never needed to.

We needed to now.

The offer, in broad terms

We won’t describe the partner, the category they operated in, or the specifics of what they proposed. None of that is relevant, and frankly, naming details would shift the focus away from what actually matters in this reflection.

What we will say is that the offer involved attaching the Queensland Foundation name — and by extension, our TLDs — to a commercial context we weren’t comfortable with. The partner would have gained visible association with something rare and, we believe, historically significant. We would have gained distribution, reach, and a degree of financial support that wasn’t insignificant.

The math looked reasonable. The optics looked reasonable. The person making the offer was reasonable. And yet every time we sat with the proposal and tried to imagine actually saying yes, something didn’t move.

It’s worth pausing on that word — something. Because for a while, we couldn’t articulate what the thing was. We had no clean principle to point to. We had no rule that said, clearly, this type of partnership is out of bounds. The discomfort was real but diffuse, and diffuse discomfort is easy to dismiss. Easy to rationalise around. Easy to override with the spreadsheet logic of what a yes would unlock.

So we sat with it longer than we might have otherwise. We talked it through. And what eventually came into focus was not a single objection but a cluster of misalignments, each small enough to negotiate away on its own, but collectively pointing at something we couldn’t in good conscience paper over.

What we are actually building

To understand why we said no, you have to understand how we think about what we’re building — and that requires being honest about the fact that we don’t think about it primarily in commercial terms.

Queensland Foundation exists to do something that has never been done before for this part of the world. We have secured permanent onchain TLDs for Queensland — .queensland, .qld, .brisbane, .surfersparadise, .gold-coast, and .brisbane2032 — and the entire point is to give Queenslanders a form of digital presence that belongs to them, permanently, without any ongoing dependency on us or anyone else. Pay once. Own it forever. No renewals. No expiry. No landlord.

That last part is the part people sometimes don’t fully absorb at first. There is no landlord. When you own a .queensland address, you own it the way you own something tangible. It is recorded on a blockchain. It is immutable. It is transferable. It cannot be revoked, repriced, or recalled by us or by anyone. If Queensland Foundation ceased to exist tomorrow, every address already issued would continue to exist, undisturbed, on the chain. The infrastructure is the guarantee.

This is a fundamentally different relationship between a person and their digital presence than anything that has existed before. The entire domain industry — every .com, every .com.au, every country-code TLD you’ve ever registered — operates on a rental model. You don’t own your domain. You lease it, annually, from a registrar who leases it from a registry who operates under the terms of a governing body that can and does change the rules. You are always one missed renewal, one policy shift, one corporate acquisition away from losing what you thought was yours.

We are not that. We are structurally, contractually, and philosophically the opposite of that.

And so when we think about what kind of organisation Queensland Foundation is and what kind of relationships it should have, the question is never just will this help us grow. The question is always does this preserve the integrity of what we’ve built, and does it deserve to exist alongside it.

Where the misalignment actually lived

The more we talked through the partnership offer, the more clearly we could see that the misalignment wasn’t about the partner’s ethics or the quality of their work. It was more structural than that, and in some ways more uncomfortable, because structural misalignments can’t be fixed by goodwill.

The first misalignment was about permanence.

The partner operated in a context where relationships, offerings, and positioning change regularly. That’s not a criticism — it’s simply the nature of most commercial activity. Markets shift. Products pivot. Priorities evolve. This is normal and often healthy. But permanence is not a feature of what we’re building — it is the foundation. Every promise we make to the people who acquire our TLDs rests on the idea that their ownership is unconditional and unbounded by time. When we associate ourselves with entities or contexts that are inherently temporal, we are not just making a commercial decision. We are making a statement about how we think about time, and implicitly about our own permanence.

We want every decision we make to be coherent with the structure of what we’ve built. A permanent onchain address should come from an organisation that thinks and acts with permanence in mind. That means being selective about whose name appears next to ours, because those associations say something whether we intend them to or not.

The second misalignment was about what the association would have communicated.

Onchain addresses are still a relatively new idea for most people. The public understanding of what it means to own a blockchain-based digital identity is still forming. In that context, the associations we make matter enormously, because they shape the frame through which people encounter us for the first time.

The partner’s context would have framed us in a way that we felt would narrow rather than open people’s understanding of what we’re doing. Not dishonestly — they weren’t asking us to misrepresent anything. But association is its own kind of communication. Standing next to something says something. And what this partnership would have said, to the people most likely to see it, was not the thing we want to say.

We want people to understand that owning a .queensland address is a civic act as much as it is a digital one. It is a statement of belonging, of permanence, of claiming something meaningful in the digital landscape — not just for the individual, but for the state and the community. The partner’s context would have placed us in a category that people associate with different motivations entirely. That framing, once established, is very hard to undo.

The third misalignment was about dependency.

Part of what the partnership would have involved was giving the partner a degree of ongoing influence over how and where our TLDs were presented and discussed. Not control — the word they used was alignment. But alignment that requires ongoing coordination is a form of dependency, and dependency is the thing we are most committed to eliminating from the lives of the people we serve.

We noticed, not without some irony, that we were being asked to accept the kind of relationship for ourselves that we were working to dismantle for our community. A permanent product does not require ongoing dependencies in its ecosystem. We should not introduce them through the back door.

The conversation we had with ourselves

There was a moment in our internal discussions — one we want to try to capture honestly here — where we stopped debating the partnership itself and started asking a harder question.

The question was: why is this even difficult?

If the misalignments were real, why did we need multiple conversations? Why did we need to write things down, test arguments, push back on each other’s hesitations? Why wasn’t the answer simply and immediately no?

The honest answer is that the offer was financially meaningful at a stage when financial meaningfulness is not nothing. We are not indifferent to resources. Building permanent infrastructure requires sustained effort, and sustained effort has costs. The offer would have helped. And there is a version of the conversation where you tell yourself that accepting one imperfect partnership in order to reach the point where you never need to compromise again is a reasonable trade.

We’ve heard that argument. We’ve made it to ourselves. And we understand why it has appeal — because it has a certain logic to it. It says: be pragmatic now so you can be principled later.

But here’s what we’ve come to believe: the moment you accept that logic, you never reach the later. Because the pragmatic compromise is always in the present, and the principled stance is always deferred to a future state that never quite arrives. The organisation that compromises on its first major partnership decision has already established a pattern. It has already signalled, internally and externally, that values are negotiable under the right conditions. And once that signal exists, it is very hard to unsend.

We are not claiming we will never face harder choices than this one. We almost certainly will. But we wanted the first genuinely difficult choice to go the right way. Not for the optics of it, but because first decisions shape the decision-making culture. They set a precedent that people inside the organisation carry forward.

What we actually want in a partner

Saying no to this particular opportunity forced us to articulate, properly and explicitly, what we would say yes to. And that turned out to be a more interesting exercise than we expected.

The criteria we landed on are not complicated, but they are firm.

A partner has to understand what permanence means.

Not just intellectually — not just as a concept they can repeat back to us — but in the way they operate and in the commitments they make. They have to have some experience with the long view. They have to be building something that they expect to still be standing in twenty years. They have to make decisions that reflect that time horizon rather than just paying lip service to it.

This alone rules out a significant portion of the organisations that will approach us. Most commercial entities, even excellent ones, optimise for cycles that are measured in quarters or years, not decades. We understand why. We don’t judge it. But we can’t partner with it.

A partner has to understand what community ownership means.

The people who acquire .queensland addresses are not customers. They are not users. They are not subscribers. They are owners. The relationship is fundamentally different from any commercial relationship, and it creates obligations that are genuinely permanent. A partner must understand and respect that relationship — not just tolerate it, but actually value it. They must be comfortable with the idea that the community of owners has primacy over any commercial consideration.

This is unusual in a business context. Most organisations have stakeholders in a hierarchy, and customers, however valued, are rarely at the top. We are asking potential partners to align with a model where the community is structurally paramount. That’s a meaningful ask, and we’ve found that how people respond to it tells you a great deal about whether a real partnership is possible.

A partner has to be comfortable with what onchain means.

Not everyone who wants to work with us is comfortable with the blockchain infrastructure that underlies our TLDs. Some find it philosophically interesting but practically unfamiliar. Some are openly sceptical. Some have had experiences in adjacent spaces that colour their perception. And some simply don’t understand it well enough yet to have a genuine opinion.

Any of these starting positions can be the beginning of a productive relationship, if the person is genuinely willing to engage. But we have encountered partners who want to work with the outputs of what we’re building — the cultural cachet of permanent digital addresses tied to Queensland identity — without engaging with the infrastructure that makes those outputs possible and meaningful. That doesn’t work for us. You can’t selectively take the parts you find appealing and set aside the parts that require understanding.

A partner has to be honest about their own motivations.

This one sounds obvious, but in practice it’s the one that most often gets blurred. People who approach us wanting to partner do so for reasons, and those reasons are rarely singular. There is usually a mix of genuine interest, commercial opportunity, strategic positioning, and sometimes a degree of opportunism. That’s human. We don’t require pure motives from anyone.

What we do require is honesty about the mix. We want to know what someone is actually hoping to get from working with us, because that knowledge is what allows us to assess whether the relationship is genuinely mutual. A partnership built on opaque motivations is not a partnership — it’s a transaction that one side hasn’t disclosed yet.

On integrity as infrastructure

There’s a way of talking about organisational values that we’ve always found slightly hollow — the framing where values are aspirational statements that describe the organisation you wish you were rather than the organisation you are. You see this everywhere. Mission statements that use words like integrity and community and purpose without any mechanical description of what those words mean in practice. Without any account of a time when those stated values required an actual sacrifice.

We’ve been cautious about that kind of language, partly because we’re sceptical of it in others and would be hypocritical to adopt it ourselves, and partly because we think the blockchain space in particular has a troubled relationship with stated values that don’t match actual behaviour.

But there’s a version of talking about values that we do believe in, and it looks less like a mission statement and more like a description of a decision. It says: here is a situation where we were tested, here is what we did, and here is what that tells you about what we actually believe.

This post is an attempt at that version.

We turned down a partnership because the partner’s way of operating was fundamentally temporal and ours is fundamentally permanent. We turned it down because the association would have communicated the wrong thing to the wrong people at the wrong moment. We turned it down because it would have introduced the kind of dependency into our ecosystem that we exist to remove from other people’s lives. And we turned it down because accepting it would have established a pattern of decision-making that we didn’t want to carry forward.

None of those reasons were about the partner’s character. We want to be clear about that. The people we spoke with were professional, thoughtful, and operating in good faith. The decision was not about them. It was about us — about who we are and what our decisions need to be consistent with.

Integrity, in the sense we mean it here, is not a quality you have or don’t have. It’s a quality you build or erode, one decision at a time. The structure of what we’ve built — permanent, immutable, onchain — is itself an expression of a kind of integrity. The addresses we issue cannot be taken back. The ownership is unconditional. The infrastructure is the promise.

We want our decision-making to be coherent with that structure. We want the organisation to behave the way the technology behaves: without expiry, without exception, without small print.

What this cost us, honestly

We want to be honest about the fact that saying no had a cost. This isn’t a story where the right decision was also the easy one. We passed on something real, and there were moments in the process where that was uncomfortable in the specific way that financial discomfort is uncomfortable — visceral, immediate, not easily philosophised away.

We want to name that because we think it’s important. If this post read as though the decision was effortless, it would be misleading, and it would also be less useful to anyone else who faces a similar situation. The difficulty of a right decision is part of the information it carries. Easy decisions don’t test values. Uncomfortable ones do.

What we can say is that the discomfort of saying no has a different texture than the discomfort we would have felt if we’d said yes. The discomfort of no is clean. It’s the discomfort of having forgone something, which is finite. The discomfort of yes — the discomfort of having made a commitment that you knew wasn’t right and now have to live inside — that discomfort is ongoing. It compounds. It creates small incoherencies that accumulate until they become large ones.

We’ve seen that happen to organisations we respect. We’ve watched good people, building genuine things, make a series of small reasonable compromises that each made sense in isolation and that together created something they didn’t recognise. We are not immune to that trajectory. But we are paying attention to it.

A note on what comes next

We will almost certainly be approached again. Other offers will come, some less obviously misaligned than this one, some more. The question of who we partner with — and who we don’t — will be answered gradually, one conversation at a time, and those answers will accumulate into something that says more about us than any statement of values ever could.

What we want to build toward is a small number of deep partnerships rather than a large number of broad ones. Relationships with organisations that understand permanence, that respect community ownership, that engage honestly with the infrastructure we’ve built, and that are genuinely interested in the long game rather than the next cycle.

We think those partners exist. We are patient.

We are also protective of what we’ve built in a way that we make no apology for. The TLDs we hold — .queensland, .qld, .brisbane, .surfersparadise, .gold-coast, .brisbane2032 — are not inventory. They are not positions in a portfolio. They are names. They are the first permanent digital addresses ever to exist for this part of the world, and the people who own them will own them forever. That means every decision we make about who stands alongside us in this work is a decision that echoes. We don’t take it lightly.

The harder question

We want to end with the question that sat underneath all of this — the one that didn’t go away when we made the decision and hasn’t gone away since.

The question is: what kind of project do we want to have been?

Not what kind of project do we want to be now, but what kind do we want to have been, looking back from a significant distance. When the digital landscape has changed in ways we can’t fully anticipate, when onchain ownership has become either ordinary or historical depending on how things unfold, when the people who own .queensland addresses are doing things with them that we never imagined — what will it mean that we made the choices we made along the way?

We want to have been the kind of project that treated every decision as though it would eventually be visible. Not because we were performing virtue, but because we genuinely believe that the decisions made in the early stages of something like this are the ones that determine whether the later stages are worth anything.

Queensland Foundation exists because Queenslanders deserve to own a piece of the digital landscape permanently, without ongoing costs, without intermediaries, without the quiet insecurity of knowing that your presence online is always technically someone else’s to revoke. That belief is not abstract. It has mechanical expression in the infrastructure we’ve built. And it has to have expression in how we conduct ourselves as an organisation — in who we work with, what we accept, and what we refuse.

We turned down this partnership because saying yes would have cost us something that money cannot replace.

We hope that’s clear. And we hope that over time, through enough decisions like this one, it becomes visible not as something we claim about ourselves but as something others can simply observe.

That’s the only kind of integrity worth having.