The question we get asked most

People ask us a lot of questions about the technology. They ask about the blockchain infrastructure, about how permanence actually works, about what it means to own an address with no renewal and no expiry. Those are good questions and we enjoy answering them.

But the question we get asked most often — by potential partners, by people inside our own network, by people who want to introduce us to someone — is simpler than all of that. It goes something like this: why are you so hard to work with?

We want to be clear: we do not think of ourselves as difficult. But we understand why the perception exists. We have turned down partnerships that looked attractive on the surface. We have said no to organisations with large audiences. We have declined introductions that came with significant upside attached, at least in the conventional sense. We have walked away from conversations that were going well right up until the moment we realised they were not going anywhere we wanted to go.

We want to explain why. Not to justify ourselves — we are comfortable with the decisions we have made — but because the reasoning matters. If you understand why we are selective, you understand something important about what we are building and why it has to be built a certain way.

What we are actually building

Before we can explain our partnership philosophy, we need to say something about the nature of this project, because it is genuinely different from most things people compare it to.

Queensland Foundation has secured six permanent onchain TLDs: .queensland, .qld, .brisbane, .surfersparadise, .gold-coast, and .brisbane2032. These are not domains in the traditional sense. They are not leased. They are not subject to renewal cycles. They are not controlled by a centralised registry that can revoke them or reassign them or discontinue them if the business model changes. They are permanent onchain addresses, owned once, for life, with no ongoing cost.

When someone registers a .queensland or a .brisbane address, they own it the way they own property — not the way they own a subscription. The address is immutable and transferable. It exists on the blockchain, not on our servers. We do not hold it for them. We cannot take it back. We cannot charge them again for the same thing. The economics are simple: you pay once, starting at five dollars, and the address is yours permanently.

This matters enormously for how we think about partnerships. Most digital infrastructure projects can absorb a bad partnership, rebrand, pivot, and move on. We cannot do that in the same way. The addresses people register under our TLDs are permanent. The trust people place in us when they make that one-time purchase is not a trial. It is a decision made on the basis of who we are and who they understand us to be. If we compromise that trust — if we associate this project with things that damage its credibility or contradict its values — we cannot simply issue a correction and reset.

The permanence that makes this project valuable is the same permanence that makes our reputation load-bearing. Every partnership decision we make is a decision about what kind of foundation this infrastructure is built on. We take that seriously.

What a bad partnership looks like

We have thought a lot about this. We have had conversations that started well and ended badly. We have been in rooms where the incentive structures were pulling everyone toward a deal that, when we interrogated it honestly, we did not want to be part of. So we have a fairly clear picture of what a bad partnership looks like for a project like ours.

It starts with misaligned values, not misaligned KPIs.

Most partnership conversations in the technology space are about metrics. Audience size, reach, conversion rates, co-marketing potential. Those conversations are fine, as far as they go. But the deepest incompatibilities we have encountered have not been about numbers. They have been about something more fundamental: what this project is for.

We believe that people — Queenslanders specifically, but people more broadly — should have the right to own a piece of permanent digital infrastructure. Not rent it. Own it. The onchain model exists precisely because the traditional model, built on annual fees and centralised control, creates a kind of permanent dependency. You do not own your domain. You lease it, year after year, from an organisation that can change its terms, raise its prices, or simply cease to exist. We built something different because we believe the dependency model is wrong.

When we sit across from a potential partner whose business model depends on that same dependency — on the idea that digital presence should be rented rather than owned, on the recurring revenue that comes from renewing things that should have been yours from day one — the conversation has a fundamental tension at its centre. We can try to work around it. We can find language that makes the incompatibility less visible. But it does not go away. And over time, an association with that kind of organisation does not just create awkwardness. It erodes the clarity of what we are building. It makes our message harder to understand and easier to dismiss.

We have walked away from those conversations. We will continue to.

Then there is the pressure to soften the mission.

This one is subtler, and in some ways more dangerous, because it does not always arrive as an explicit demand. It arrives as a series of small suggestions. Could you frame it this way instead? Could you avoid mentioning that? Could you position the permanent ownership angle as a feature rather than the entire point?

Every one of those suggestions, in isolation, might sound reasonable. And sometimes they are — we are not so rigid that we cannot adapt our communication to different contexts. But there is a version of this process that, if you follow it to its logical end, produces something that sounds like Queensland Foundation but no longer means what Queensland Foundation means. The mission gets softened until it disappears. The clarity that made the project compelling gets rounded off into something inoffensive and forgettable.

We have seen this happen to other projects. Not through any single dramatic betrayal, but through the slow accumulation of small compromises, each of which seemed defensible at the time. A partnership that requires you to stop talking clearly about what you believe is not a partnership. It is a gradual acquisition of your voice by someone who did not pay for it.

And then there is the trust dimension.

This is the one that matters most, and it is the hardest to talk about without sounding precious. So we will try to say it plainly.

The people who register a .queensland or a .brisbane address are making a decision based on their trust in us. Not just trust in the technology — though that matters — but trust in the project. Trust that we are who we say we are. Trust that the infrastructure they are buying into is built by people with integrity. Trust that we will not, at some later point, do something that makes them regret their association with us.

That trust is not easy to earn and it is very easy to lose. And it can be lost by association just as surely as it can be lost by action. If we partner with an organisation that later becomes a liability — that is exposed as having acted badly, or that operates in a way that contradicts the values we have staked our reputation on — the damage is not contained. It spreads. People who trusted us start to wonder whether they were right to. And once that question is in the air, it is very difficult to put back.

We are not paranoid about this. We do not run every potential partner through a risk analysis that treats them as a threat. But we are honest about the fact that associations carry weight, and we choose our associations carefully.

The criteria we actually use

So if those are the failure modes, what does a genuine partnership look like? What criteria do we actually apply when we evaluate someone who wants to work with us?

We have never written this down as a formal policy document. It has evolved through experience, through conversations, through the decisions we have made and the ones we have revisited. But when we look at the partnerships we have been glad to pursue, and the ones we have been glad to decline, a set of consistent principles emerges.

First: shared belief in ownership over access.

The most fundamental alignment we look for is philosophical. Do the people we are talking to believe, genuinely, that permanent ownership is a better model than perpetual rental? Not as a marketing position — as an actual conviction about how digital infrastructure should work.

This might sound like a high bar. It is. Most of the organisations operating in the digital space have built their business models on access, on subscription, on the recurring revenue that comes from things you never fully own. We are not hostile to those organisations. We understand why those models exist and why they have been commercially successful. But we are building something that runs counter to that paradigm, and a partner who does not share the underlying conviction will always be, at some level, in tension with what we are doing.

When we find organisations that genuinely believe in what we believe — that permanent, ownable, onchain infrastructure is the right model, not just an interesting feature — those conversations are different. There is no tension at the centre. We can talk about practical alignment because the philosophical alignment is already there.

Second: understanding of the blockchain context without the baggage.

This project is built on blockchain infrastructure. That is not incidental — it is the reason permanence and immutability are possible. The blockchain is the technical foundation that makes the ownership model work.

But the word “blockchain” carries a lot of baggage. It evokes the speculative frenzy of cryptocurrency cycles. It brings to mind projects that were launched without substance, that made promises they could not keep, that left a trail of disappointed people behind them. We understand why people have learned to be sceptical. That scepticism is, in many cases, earned.

What we look for in a partner is the ability to separate the technology from the noise around it. The blockchain infrastructure we use is not a speculative bet. It is a tool — a very specific tool that enables a very specific thing, which is permanent, immutable, transferable ownership of digital addresses. A partner who can engage with that clearly, who neither overclaims (treating it as a magical solution to everything) nor underclaims (dismissing it because of the baggage), is a partner we can work with.

What we cannot do is partner with organisations that use the blockchain framing to confuse rather than clarify. There are projects in this space that use technical complexity as a substitute for substance. We do not want to be associated with that approach. Our technology is real, our use case is specific, and we would rather explain it plainly than impress people with vocabulary.

Third: genuine connection to Queensland.

This is one that might seem obvious, but it is worth saying explicitly. Our TLDs are Queensland TLDs. The project is rooted in a specific place with a specific identity. .queensland is not a generic digital product. It is an expression of belonging, of regional identity, of the desire to own something that represents where you come from and where you are building.

When we look at potential partners, we ask whether there is a genuine connection to Queensland — to its communities, its institutions, its culture, its future. Not a superficial connection. Not a strategic decision to use Queensland as a market. A real relationship with the place.

This matters because the people who will find the most meaning in owning a .queensland or a .brisbane address are the people who feel that the place means something. A partner who shares that genuine connection will amplify the project in ways that feel authentic. A partner who is simply using Queensland as a geography will produce associations that feel hollow, and people will sense that.

We have said no to organisations that had reach in Queensland but no real relationship with it. The reach is not worth the hollowness.

Fourth: patience with the long arc.

We are building something permanent. That word — permanent — is not just a product feature. It is a description of our orientation toward the project itself. We are not building this to flip it. We are not building this to hit a metric and move on. We are building infrastructure that is meant to outlast the moment it was created in, to become part of how Queensland and Queenslanders identify themselves in digital space for a very long time.

That kind of project requires partners who can think in the same timeframe. And in our experience, not many organisations can. The commercial world runs on short cycles — quarterly targets, annual reviews, campaign windows. The pressure to show results quickly is enormous and constant. We understand it. We are not oblivious to commercial reality.

But a partner who is going to pressure us to make short-term decisions that compromise the long-term integrity of the project is not a partner we can sustain a relationship with. We need collaborators who understand that the value of what we are building compounds over time, and who are willing to be patient with that arc.

We have found those partners. They exist. But they are rarer than the organisations that can talk about long-term thinking while their incentives push them in the other direction.

Why we say no more often than yes

We want to be honest about this: we have said no far more often than we have said yes. The ratio is not close. And we think it is worth explaining why that is not a failure mode.

There is a version of this story where saying no a lot is a sign of arrogance, or naivety, or an inability to operate pragmatically in the real world. We have heard that criticism, gently delivered by well-meaning people who think we are leaving opportunity on the table.

We think about it differently. The value of what we are building is not additive in a simple way. It is not the case that every partnership we add makes the project more valuable. Some partnerships, entered into carelessly, would make it less valuable — not in a financial sense, necessarily, but in the deeper sense that matters more: the sense of integrity, of clarity, of coherent purpose.

A project like ours earns trust slowly. It earns it through consistency — through doing what it says it will do, year after year. Through the absence of the things people have been burned by before: the sudden price increases, the service discontinuations, the pivots that invalidate prior commitments. We have deliberately built a model that avoids all of those things, because those things damage trust and trust is the foundation of everything.

When we say no to a partnership, we are protecting that foundation. We are saying: this association would make it harder for us to be consistent. It would create noise around our message. It would introduce incentives that pull in directions we do not want to go. The no is not about pride. It is about maintenance. You have to maintain the thing you are building, and sometimes maintenance means declining the offer that looks attractive today but would cost you something important tomorrow.

The conversations we have not finished having

We want to be clear about something: our criteria are not a wall. They are not designed to keep people out. They are designed to ensure that when we bring someone in, it is for the right reasons and with the right foundation.

We are genuinely open to partnership conversations. We are looking for organisations, communities, and individuals who share our belief in what permanent onchain ownership means. We are looking for people who have a real connection to Queensland — to its identity, its communities, its future. We are looking for collaborators who can think in long arcs and who understand that the most durable things are built with patience and integrity.

When those conversations happen, they are among the best we have. There is a particular quality to a conversation with someone who gets it — who understands not just what we are doing but why the way we are doing it matters. Those conversations move quickly because there is no translation required. The values are already shared. The orientation is already aligned. What is left is the practical work of figuring out how to build something together that serves both missions.

We have had more of those conversations than people might expect, given how selective we are. Because when you are clear about what you are looking for, the right people tend to find you.

On the integrity of no

There is something we want to say about the act of saying no, because we think it is undervalued in most institutional contexts.

Organisations are generally rewarded for saying yes. Yes to partnerships, yes to growth, yes to new revenue streams, yes to the next interesting thing. The structural incentives almost always point toward expansion. The person who says yes is seen as proactive and commercially minded. The person who says no is seen as obstructive, or precious, or bad at business.

We have felt that pressure. It is real. And we have learned, through experience, that the pressure does not come only from outside. It comes from inside too — from the natural human desire to be liked, to be seen as good to work with, to not disappoint the person sitting across from you who clearly wants a different answer.

Learning to say no clearly, directly, and without excessive explanation is genuinely hard. It requires confidence in your own criteria — confidence that is hard to maintain when the world around you is constantly suggesting that your criteria are too strict. It requires being willing to leave the room with the relationship intact but the deal undone, which is a skill that takes practice.

We have gotten better at it. We have learned to say no earlier, before the conversations develop so much momentum that the no becomes a kind of rupture. We have learned to say it clearly, without hedging it into something that sounds like a maybe. And we have learned to mean it — not as a negotiating position, but as a genuine answer.

Because a no said clearly is more respectful than a maybe that drags on. It gives the other person the clarity they need to move forward. And it maintains the integrity of the yes, when the yes eventually comes.

What we have learned about trust

We started this project with strong convictions about what we were building and why. Those convictions have not changed. But we have learned things along the way that have deepened our understanding of what it means to build something trustworthy, and partnership decisions have been one of the main sources of that learning.

The first thing we learned is that trust is not announced. You cannot claim to be trustworthy. You demonstrate it through the accumulation of decisions that are consistent with your stated values, made over time, including and especially when those decisions are costly. Saying no to a commercially attractive partnership because it does not align with your values is a demonstration of trustworthiness. Not a loud one. Not one that will make the news. But real.

The second thing we learned is that clarity is a form of respect. When we are clear about what we are — about what this project is for, about what we will and will not do — we give people the information they need to make real decisions about whether to trust us. The alternative is a kind of strategic vagueness that allows people to project onto us whatever they want to see. That might reduce friction in the short term. But it creates a worse problem later, when the reality and the projection collide.

The third thing we learned is that the people who trust us most are often the ones who have watched us say no to something. Not because they enjoy seeing rejection, but because it signals something to them. It signals that the yes, when it comes, means something. That we are not saying it to everyone. That when we commit to a relationship or an association, it is because we have genuinely evaluated it and decided it is right.

That signal matters. In a world full of projects that will say yes to anything, the selective no is a kind of proof of work.

The long view

We are playing a long game. We know that. We have built something permanent and we intend to behave with the same permanence — to make decisions that will look right not just this year but in ten years, in twenty years, when the infrastructure has become ordinary and taken for granted in the way that all genuinely useful infrastructure eventually is.

In that context, partnership decisions are not tactical. They are part of the foundation. Every organisation we associate ourselves with, every relationship we build, every collaboration we enter — these things become part of the record of what Queensland Foundation is. Not a PR record. Not a marketing record. The actual record of what we chose to do and who we chose to do it with when the choices were real and the stakes were genuine.

We want that record to be clear. We want the people who register a .queensland or a .brisbane address to be able to look at who we have partnered with and feel confirmed in their decision. We want the communities and institutions of Queensland to be able to look at our associations and see something coherent — a consistent set of values, expressed through consistent choices, over a long period of time.

That is not something you can build in a single partnership decision. It is the product of many decisions, made consistently, over time. Each no that protects the integrity of the project, each yes that genuinely extends it — they add up. They become the thing itself.

We take that seriously. We will keep taking it seriously. And when the right partners find us — as they do, more often than people might expect — we will be glad we waited for them.