There is a particular kind of difficult that doesn’t feel difficult at first. The kind where someone puts a proposal in front of you, and on the surface it maps perfectly onto what you’re doing. The language is right. The values they claim are the right values. The timing is right. The commercial terms are genuinely attractive. You sit with it for a day, maybe two, and you think: this is one of those easy decisions. This is one of the ones that looks complicated but isn’t.

Then something shifts.

It isn’t dramatic. There’s no single red flag. Nobody in the room says anything alarming. But there’s a moment — it happens differently each time — where the thing that looked clean begins to feel slightly wrong in a way you can’t immediately articulate. And when that happens, you have a choice. You can rationalise your way past the feeling, because the numbers look good and the partnership looks credible. Or you can sit with the discomfort long enough to actually understand what it’s telling you.

We chose to sit with it.

We said no to the deal. And what that process revealed to us — about ourselves, about what we’re building, about the nature of good decisions made under pressure — is worth writing down. Not because we think we were uniquely wise. But because we suspect other people building things they care about will recognise the experience.

The deal that looked right

We won’t describe the specifics of the other party, the proposal, or the terms. That’s not what this is about. What we will say is that it wasn’t a bad deal with a bad actor. It was a plausible deal with a credible actor who appeared, genuinely, to understand what we’re building.

The proposal was structured well. The partner had reach we didn’t have. They had relationships we would have found genuinely useful. They came with what felt like a sincere enthusiasm for what Queensland Foundation is doing — the idea of permanent onchain addresses, the idea of giving people genuine ownership over a piece of Queensland’s digital future, the idea that you pay once and the thing is yours forever.

The conversation was easy in the early stages. We spoke the same language — or so it seemed. We talked about ownership versus renting. We talked about permanence versus the endless extraction of annual fees. We talked about giving communities an identity infrastructure they could actually trust, not because a company says so, but because the blockchain makes it structurally true. Those conversations felt aligned.

There was commercial upside that was real and not trivial. The kind of upside that, if you strip everything else away, you’d be hard-pressed to justify walking past.

So we didn’t say no immediately. We took it seriously.

What the conversations started to reveal

The more detailed the discussions became, the more a particular pattern began to emerge. It was subtle. But in early-stage projects, you develop a kind of sensitivity to certain frequencies — because you have to. You don’t have the institutional scaffolding that larger organisations use to absorb misalignments. There’s no layer of middle management between the idea and its execution. When something is off, it shows up quickly in the details.

What we started to notice was this: every time the conversation moved toward the nature of permanent ownership, toward the architecture of what we’re actually building, there was a kind of rhetorical soft-shoe. The partner would acknowledge the principle warmly and then immediately reframe it toward the things they wanted to extract from the arrangement. Not dishonestly. They weren’t pretending. It was more that their mental model of what this project could be was genuinely different from ours, and neither of us had fully realised that yet.

They saw this as infrastructure for a product. We see this as a product that is also infrastructure. That sounds like a subtle distinction. It isn’t.

When you see something as infrastructure for a product, the ownership mechanism is a feature — a selling point, a differentiator in the market. You can talk about permanence and mean it, but what you’re really saying is: permanence is a good value proposition. It helps conversion. It reduces churn objections. It’s a feature that earns trust. And all of that is true. Permanence does all of those things.

But when permanence is your actual north star — not a feature but a founding commitment — you make decisions differently. You design things differently. You turn down certain opportunities not because they’re dangerous, but because they would begin to bend the architecture in directions that compromise the thing you promised.

The moment the framing changed

There was a specific point in the conversations where one of us asked a direct question. We asked what would happen to addresses in a scenario where the commercial relationship evolved — where interests diverged, where the party using the infrastructure had reasons to want different outcomes from the party that issued the addresses.

The answer was thoughtful. It was not evasive. It was, honestly, a reasonable answer if you’re building a conventional product. But it revealed something important: the mental model of control was still a model in which control was possible. The idea that there could be a scenario in which addresses might need to be managed — redirected, constrained, or functionally altered — was sitting there, calmly, in the background.

For us, that answer was the answer. Not because we thought the partner had bad intentions. But because a system that can be managed in that way is not permanent. It is long-lasting until it isn’t. And the thing we are building is permanently permanent. Those are not the same thing.

We believe — deeply, and as a founding principle — that an onchain address should function the way a title deed functions. Once it’s yours, it’s yours. Not yours-unless-circumstances-change. Not yours-with-caveats. Not yours-according-to-the-current-terms-of-service. Yours. The way a piece of land is yours. Recorded immutably. Not subject to renewal. Not contingent on continued goodwill from a platform or a partner.

Once we had that articulated clearly in the room, the decision became easier.

The mythology of the good deal

Here’s something we had to confront honestly: part of what made this hard was the mythology of the good deal. In early-stage projects, good deals are rare. Real alignment — shared values, complementary capabilities, genuine trust — is genuinely uncommon. When it appears, even in a form that’s imperfect, there’s a powerful gravitational pull toward making it work.

That pull isn’t irrational. It comes from real experience. From the knowledge of how hard it is to find collaborators who understand what you’re doing. From the very human anxiety about the road ahead. And in this case, it came from the fact that this wasn’t a bad deal dressed up as a good one. It was a genuinely good deal for a slightly different project.

That’s the hardest version of the thing to walk away from. It’s easy to say no to bad deals. It’s even, in a strange way, easy to say no to good deals from wrong people. What’s genuinely hard is saying no to a good deal from people who are right — just not right for this.

We had to resist the instinct to optimise, to find the compromise, to construct the modified proposal that lets both parties have most of what they want. That instinct is not inherently wrong. It’s often how good partnerships are built. But sometimes the act of finding the compromise is itself the mistake — because the compromise version of the thing is not the thing.

What “no” as a design principle looks like

We’ve come to believe that what you decline reveals your values more clearly than what you accept. Acceptance is easy to rationalise — you can always build a case for why a thing serves your mission. Rejection requires you to actually articulate the line. And articulating the line is where you find out what the line actually is.

Before this particular decision, we had a sense of our values. We could describe them in broad terms. Permanence. Ownership. Community. The idea that Queensland’s digital identity shouldn’t be a service that can be switched off or rented back to people who should own it outright.

After this decision, we had something more precise. We had a set of tests.

The first test is the control test. Any partnership, any commercial arrangement, any technical integration — we ask whether it introduces a layer of control that didn’t exist before. Not hypothetical control. Real structural control. If it does, we step back. Not because we distrust the partner. But because the architecture we’re building depends on the absence of that layer. The moment a system can be managed, it’s a managed system. We are building something unmanaged by design.

The second test is the permanence test. We ask whether the arrangement, as structured, is compatible with the promise of permanence. Not compatible in intention — compatible in structure. Good intentions change. Good structures persist. If we can’t describe how the permanence of the product survives a change in the relationship, the relationship isn’t compatible with the product.

The third test is the trust source test. We ask: where does the trust in this product come from? If the answer is “from us” — from our reputation, our goodwill, our ongoing management of the system — then we have built something that requires the continued goodness of a company. That’s not what we’re building. The trust in an address recorded permanently on a blockchain doesn’t come from the goodwill of Queensland Foundation. It comes from the blockchain. Our job is to build the front door well, and to make sure that what happens behind it is genuinely immutable. Any partnership that would shift the trust source from the chain to the company fails this test.

The thing about ownership

There’s a concept that sits at the centre of everything we’re doing, and it’s worth dwelling on it here, because it’s what the decision ultimately turned on.

Ownership is not the same as possession. You can possess something temporarily — you can use it, benefit from it, feel like it’s yours — without actually owning it. The entire internet is built, largely, on this distinction. You have an account. You have a profile. You have a domain name that you’ve been using for fifteen years. But you possess these things on terms set by others. You renew them. You comply with the platform’s policies. You build on infrastructure that can change beneath you. If the company changes its terms, your possession continues but the conditions of that possession have changed.

This isn’t a criticism. It’s simply how most digital systems work. They were built this way because it’s efficient, and because for most purposes it’s fine. Most people’s domain names don’t get taken away. Most accounts aren’t arbitrarily closed.

But we are building something specifically for the people for whom “most” isn’t good enough. The family whose surname becomes part of a permanent Queensland address, passed down through generations. The business that builds its entire identity around a .brisbane or .qld address, not as a marketing decision but as a foundational one. The community group, the institution, the individual who wants one permanent place on the internet that cannot be taken, cannot expire, cannot be renegotiated.

For those people, the distinction between ownership and possession is everything. And anything we do — any partnership we enter, any commercial arrangement we accept — has to be compatible with delivering real ownership. Not possession. Not long-term possession with reasonable terms. Ownership.

The deal we walked away from wasn’t going to compromise possession. People would still have had their addresses. They would still have been able to use them. But the structural architecture of the arrangement introduced a layer that we couldn’t reconcile with genuine ownership. The chain would have recorded it. But something above the chain would have had levers. And that’s not permanent. That’s just well-resourced.

What this taught us about ourselves

Saying no to this deal was uncomfortable. We want to be honest about that. We aren’t writing this from a position of easy confidence. We are a project, not a corporation. The commercial upside we turned down was real. The relationships we chose not to pursue were potentially valuable.

There’s a version of this story where we are fools. Where we held too hard to an abstract principle at the expense of a practical opportunity. We’ve entertained that version. We’ve sat with it seriously.

But here’s what we keep coming back to: the product we’re building is the promise. The promise is the product. When you’re selling someone an address for five dollars with the guarantee that it’s theirs for life and no one can ever take it away, you are not selling a service. You are selling a category of certainty. And that category of certainty is either absolute or it’s nothing.

There is no version of “mostly permanent” that works. There’s no version of “yours forever, within the terms of any third-party arrangement” that delivers what we promised. The moment we introduce that qualifier, we have built a different thing. A good thing, maybe. A useful thing. But a different thing.

And so the decision — uncomfortable as it was — wasn’t actually a hard one, once we had seen it clearly. We couldn’t take the deal without changing what we’d built. And we didn’t want to change what we’d built.

What the process of evaluation revealed

What we hadn’t expected was how useful the evaluation process itself would be. We spent a significant amount of time genuinely attempting to make the deal work — not in a searching-for-the-compromise way, but in an honest attempt to understand whether the concerns we had were real structural concerns or just unfamiliarity. Whether we were being principled or just uncomfortable.

That process forced us to articulate things we had previously only understood intuitively.

We understood the permanence principle. But we hadn’t fully documented what it meant in practice — what decisions it ruled out, what structures it prohibited, what the tests were for any future arrangement. The deal gave us that.

We understood the ownership principle. But we hadn’t fully interrogated the difference between structural ownership and nominal ownership. The deal forced us to draw that line with precision.

We understood that we were building for Queenslanders, not for investors or platforms. But we hadn’t stress-tested what that meant when the financial incentives pointed elsewhere. The deal gave us that stress test.

In a strange way, we are grateful for the proposal. Not because we wish it had gone differently. But because the process of evaluating it — seriously, honestly, with genuine openness — gave us something more valuable than the deal itself. It gave us a clearer picture of what we are.

On the pressure to grow fast

There is a cultural pressure in the project world — and in the blockchain space particularly — to move fast, to scale, to form alliances, to demonstrate momentum. Growth is read as validation. Partnerships are read as endorsement. And there’s a kind of social proof that comes from visible collaboration that can feel, in the short term, more important than it actually is.

We are not immune to this pressure. We feel it. And we want to be honest: part of what made the deal attractive was the relief it seemed to offer from that pressure. A credible partner. Expanded reach. A sense of forward motion.

But we’ve come to believe that momentum and direction are not the same thing. You can move very fast in a direction that takes you away from where you meant to go. And the early stages of a project — particularly one built on a founding promise as specific as ours — are the stages where direction matters more than speed. You can regain speed. You cannot always regain direction, because the decisions you make in the early stages of building something become structural. They become the shape of the thing. They become harder and harder to undo.

The deal would have moved us faster. In a direction that wasn’t ours.

What integrity actually requires

We want to push back gently on a framing we sometimes encounter, which is the idea that holding to your values is always the noble and obvious choice. That saying no to something commercially attractive in service of your principles is straightforwardly heroic.

It isn’t. Or at least, it isn’t in the moment.

In the moment, it feels like loss. It feels like the thing you wanted to have that you’re now giving back. It feels like you might be wrong — like you might be the person who turned down the right deal for bad reasons dressed up as good ones. Pride disguised as integrity. Fear disguised as principle.

We sat with that possibility seriously. We asked ourselves, honestly, whether the discomfort we felt was a signal or a bias. Whether we were genuinely identifying a structural problem or just finding sophisticated language for an emotional reaction. Whether we were protecting the product or protecting ourselves.

We believe we were protecting the product. But we want to acknowledge that this kind of evaluation — the kind where you genuinely interrogate your own motivations — is the part that is usually left out of retrospective accounts of good decisions. Those accounts tend to begin with clarity. Ours didn’t.

What we arrived at was not a comfortable certainty. It was a considered judgment that the structural problems we had identified were real, that they were incompatible with the founding promise, and that no amount of commercial upside justified accepting them. That judgment could be wrong. We are human. But it was the most honest judgment we could make with what we knew.

The longer arc

Here is what we believe, looking forward from this decision.

The things that seem like constraints — the discipline of permanent ownership, the refusal to introduce layers that compromise the architecture, the insistence that the trust in the product comes from the chain and not from us — are not actually constraints. They are the product’s source of strength.

The reason a .queensland or .qld or .brisbane address will mean something to the people who hold it is precisely because the system has no levers. There is no company standing behind it that can change the terms. There is no annual fee cycle that creates a dependency relationship. There is no renewal mechanism through which the address can be allowed to lapse. The address is recorded permanently because that is what the blockchain does. The trust is structural.

That structural trust is not something we can build quickly through partnerships and alliances. It is something we earn, slowly, by being rigorous about the architecture at every decision point — including the uncomfortable ones. And it is something that, once built, is genuinely durable. Not because we promise it will be. Because the structure makes it so.

Every time we say no to something that would compromise that architecture, we are not sacrificing growth for principle. We are building the thing that will, over the long arc, mean what it claims to mean. That is the trade we are making. It is the right trade.

What we would say to anyone in a similar position

If you’re building something with a founding promise at its centre — something where the promise is the product — then the decisions that feel like costs in the short term are often the decisions that preserve the thing you’ve built.

Not always. There are deals worth taking that feel uncomfortable. There are partnerships that challenge your assumptions in ways that make the project better. Not every discomfort is a signal. Not every hesitation should become a veto.

But when the discomfort is structural — when you can trace it, not to fear or unfamiliarity, but to a specific incompatibility between what the arrangement requires and what the product promises — then the discomfort is telling you something true. And the most important thing you can do is sit with it long enough to understand it, rather than rationalising your way past it toward the number that looks attractive.

We said no to a deal that looked right on paper.

We said yes, instead, to the harder work of remaining exactly what we said we would be.

That choice doesn’t make us special. But it does make us consistent. And in a project built on the promise of permanence, consistency is everything.

Queensland Foundation is building permanent onchain addresses for Queensland — .queensland, .qld, .brisbane, .surfersparadise, .gold-coast, and .brisbane2032. One payment. No renewals. Yours forever.