The Question We Had to Answer Honestly

Before we built anything, before we registered anything, before we wrote a single line of code or had a single conversation with anyone about what Queensland Foundation could become, we had to sit with a question that deserved a serious answer.

Why blockchain?

Not “why blockchain” in the way that question gets asked at conferences, where someone in the audience is trying to catch a speaker out, trying to expose the hype beneath the pitch. We asked it of ourselves, privately, rigorously, and with genuine willingness to arrive at a different answer. We had no interest in building on blockchain infrastructure simply because blockchain is interesting, or because it lends a project an air of novelty, or because it lets you use certain words in a whitepaper that make investors lean forward in their chairs.

We asked the question the way engineers ask it when they are choosing between two materials for a bridge. Which one actually holds? Which one does what we need it to do, at the scale we need it done, for the duration we are promising?

The duration we were promising was forever.

That changes the question considerably.

When you are building something that you intend to last not for a year, not for a decade, but permanently — when you are making a promise to people that what they own will still be theirs in fifty years, regardless of what happens to any company, any government policy, any funding round, any leadership team — the infrastructure question stops being a technical question and becomes a values question.

What kind of system is honest enough to hold that promise?

That is what this post is about. Not the mechanics of how blockchain works. Not a tutorial. Not a glossary. This is an account of how we thought about the choice, what we rejected and why, and what it means — actually means, in practice, for the people who own a Queensland address — that we chose the infrastructure we chose.

What We Were Actually Building

To understand why blockchain was the right answer, you have to understand what we were building with precision.

We were not building a website directory. We were not building a search engine. We were not building a social network, a marketplace, or a content platform. All of those things have something in common: they are services. And services, by their nature, are managed. Someone runs them. Someone maintains the database. Someone pays the server bills. Someone makes decisions about who gets to stay and who gets removed. Services are relationships between a user and a provider, and like all relationships, they can end.

What we were building was ownership.

Specifically, we were building permanent, individual ownership of onchain addresses tied to Queensland — addresses like .queensland, .qld, .brisbane, .surfersparadise, .gold-coast, and .brisbane2032. We wanted Queenslanders, and anyone connected to Queensland, to be able to own a piece of their place in a way that was genuinely theirs. Not licensed. Not rented. Not contingent on a subscription. Not held in trust by a corporation that could be acquired, that could change its terms of service, that could go bankrupt, that could simply decide one day that the product was being wound down.

Owned. The way you own land. The way you own the name on your letterbox.

The moment we defined the problem that way, the universe of possible infrastructure shrank dramatically. Most of the options that seemed reasonable at first glance turned out to be solutions to a different problem — solutions to the problem of hosting a service, not the problem of enabling ownership.

What We Looked At and Why It Fell Short

We did not arrive at blockchain by default. We arrived at it by elimination, and the elimination process was thorough.

Traditional domain infrastructure was the first thing we considered. The global domain name system is the most obvious analogue to what we were doing — it is a namespace, it maps names to destinations, it has been doing this for decades. It works. But the moment you look at it closely, you see that it is not really an ownership system. It is a rental system with very good branding.

Every traditional domain you have ever owned, you have not owned. You have leased it, typically for one or two years at a time, from a registrar, who holds your registration in a database they control, subject to policies set by ICANN and its associated bodies, subject to local laws, subject to disputes that can be resolved by panels you did not choose, subject to the registrar going out of business or being acquired by someone with different values. You pay every year or you lose the name. The infrastructure for enforcing that payment is entirely in someone else’s hands. Your “ownership” exists as a record in a database, and the people who control the database can, under various circumstances, alter that record.

We could not build a permanent ownership product on infrastructure that was designed from the ground up as a rental system. The mismatch was too fundamental. We would have been asking people to trust our promise of permanence while building on a foundation that was structurally impermanent.

A private database was the next thing we looked at. Build our own system, run our own servers, maintain our own records. This is not as naive as it sounds — plenty of serious companies run serious infrastructure on databases they control, and plenty of those databases are reliable, secure, and well-maintained.

But a private database, no matter how well-run, has an irreducible problem: it is only as permanent as the organisation that runs it. If Queensland Foundation ceases to exist — if we are acquired, if we run out of funding, if key people leave, if a legal challenge forces us to close, if the world simply moves on — the database goes with us. The addresses stored in it go with us. The ownership records, the transfers, the history — all of it is contingent on our continued existence and our continued goodwill.

We could not ask people to pay for permanent ownership and then quietly attach an asterisk that said “permanent, as long as we’re around.” That is not a promise of permanence. That is a promise of intentions, which is a very different thing.

We also thought seriously about what it would mean, over decades, to be the custodians of a database that contains other people’s property. The pressure that would accumulate. The legal requests. The disputes. The moment a government agency writes to us asking us to modify or remove a record. The moment a large corporation decides that someone’s address infringes on their trademark and they want it transferred. If all the records live in our database, all of that pressure lands on us, and we become the single point of failure — and the single point of potential compromise — for thousands or eventually hundreds of thousands of people who trusted us with something they believed was theirs.

That is a position we did not want to be in, not because we would necessarily fold under that pressure, but because the existence of that pressure is itself a threat to the promise. Even if we never buckle, the possibility that we might is a flaw in the product. Permanence with an asterisk is not permanence.

A federated or distributed database was the third option. If the problem with a private database is single-point control, then distribute the control. Run nodes in multiple jurisdictions. Require consensus before records can be altered. This is a more sophisticated version of the same idea, and it addresses some of the weaknesses.

But it introduces a different problem: governance. Who decides the rules of the federation? Who can join the network of nodes? Who can be expelled? How are disputes resolved? How are upgrades rolled out? Every federated system, no matter how well-designed, eventually comes back to a group of people making decisions. And that group of people, however distributed they appear, is still a trusted third party. They are just a committee rather than a single company.

We were not interested in replacing a single point of trust with a committee of trust. We were interested in removing the requirement for trust entirely.

A government-run registry was something we thought about briefly, and then thought about less. The idea has surface appeal — governments manage land registries, they manage business registries, they have long institutional experience with maintaining records of ownership. But governments change. Policies change. Jurisdictions change. What is protected today can be rescinded tomorrow through legislation, through administrative action, through budget cuts that eliminate the department that runs the registry. Government infrastructure also comes with the full weight of government control — the ability to freeze assets, to transfer ownership by court order, to delete records for reasons that have nothing to do with the original agreement.

We also want to be honest about something more fundamental: we were building something for Queenslanders, but we were also building something that we believe could matter beyond Queensland, and we were building it with a long enough horizon that we had no idea what the political landscape would look like when the people who buy addresses today are passing them to their children. Tying permanent ownership to any single government’s willingness to maintain it is simply not compatible with the promise we wanted to make.

Why Blockchain Is Honest Infrastructure

After that process of elimination, we came to blockchain. But we want to be precise about what we mean, because “blockchain” is a word that has been used to mean many things, some of them good and some of them not.

What blockchain gives us — what nothing else gives us in the same way — is a record that no single party controls.

When an address is registered on a public blockchain, the record of that registration exists across thousands of computers simultaneously. It is not stored in our database. It is not stored in a government database. It is not stored in any single place that can be seized, altered, or deleted by any single actor. The record is the consensus of the network, and changing it requires doing something that is, in practical terms, computationally impossible for any individual, company, or government acting alone.

This is not a marketing claim. It is a structural property of how the technology works. And it is the only structural property we know of that makes the promise of permanent, unconditioned ownership honest.

When we say that the address you buy is yours permanently, with no renewals, no expiry, and no annual fees, we are not asking you to trust us. We are telling you that the record of your ownership exists in a form that we ourselves cannot alter. We cannot take your address back. We cannot modify the record. We cannot “decide” that the product is being discontinued and quietly wipe the database. The infrastructure does not permit it.

That is an unusual thing to be able to say, and it is the thing that made blockchain not just the best option but the only option. Every alternative we considered involved us — or someone like us — retaining ultimate control over the records. Every alternative involved asking people to trust a promise rather than a system. Blockchain let us encode the promise into the system itself.

Permanence Is a Moral Commitment, Not Just a Feature

We want to dwell on something that we think gets underappreciated in discussions about blockchain and ownership: the moral dimension of permanence.

When someone pays for something and is told it is theirs permanently, they are making a decision based on that representation. They might make other decisions downstream of it. They might build something on top of their address. They might use it to anchor an identity, a business, a community. They might, years from now, pass it to someone they love.

If the permanence you promised them was conditional — if it depended on your continued existence, your continued goodwill, your continued ability to resist external pressure — then you were not selling permanent ownership. You were selling something that looked like permanent ownership but was actually a different product. That is a misrepresentation, even if it was not intentional, even if you fully meant the promise at the time.

We were not willing to make a promise we might not be able to keep. We were not willing to build a product where the permanence was a hope rather than a guarantee.

Infrastructure that lets us encode permanence into the record itself — where permanence is not contingent on our survival or our integrity but is a property of the system — is the only infrastructure that lets us make the promise honestly. We chose blockchain because we chose honesty.

Ownership Without a Landlord

There is another way to think about what blockchain makes possible that we find clarifying.

Throughout history, the ability to own something permanently has generally required a landlord of some kind. Not a landlord in the residential sense, necessarily, but an authority — an institution, a government, a church, a corporation — that serves as the ultimate guarantor of the ownership record. When you own land, the government maintains the title registry. When you own a company, the government maintains the corporate register. When you own a domain name, ICANN and its network of registrars maintain the namespace. The authority behind the ownership is always, ultimately, a human institution.

Human institutions are impermanent. They exist in time. They have interests. They have vulnerabilities. The fact that they have existed for a long time does not mean they will exist forever, and it does not mean that while they exist, their interests will always align with yours.

Blockchain represents the first time in human history that it has been technically possible to maintain an ownership record without any human institution as the ultimate authority. The authority behind the record is mathematics — specifically, the properties of cryptographic hash functions and the consensus mechanisms that blockchain networks use to validate new entries. Mathematics does not change its mind. It does not get acquired. It does not receive letters from government agencies. It does not run out of funding. It does not make exceptions for important customers.

This is genuinely new. It is not an incremental improvement on what came before. It is a different category of thing — a type of record-keeping that, for the first time, removes the requirement for a trusted human custodian.

We built Queensland Foundation on this infrastructure because we believed that the people of Queensland deserved to own something that was genuinely theirs — not held in trust by us, not contingent on our goodwill, not revocable by any party with sufficient legal or financial leverage. Theirs.

What We Gave Up and Why It Was Worth It

We want to be honest about what blockchain does not give you, and why we accepted those trade-offs.

Blockchain infrastructure is less flexible than a private database. If we want to make certain kinds of changes to the system, we cannot simply push an update to our servers. Some changes require working with the underlying protocol, or deploying new smart contracts, or navigating the governance processes of the network we build on. This is real friction, and it is a meaningful cost.

Blockchain infrastructure is also less familiar to most people. The experience of managing a wallet, of understanding how keys work, of knowing what it means to hold something onchain — this is not intuitive for most users today. There is an education burden. There is a user experience burden. Every step in the direction of true onchain ownership is a step away from the familiar friction-free interfaces that people are used to.

We accepted both of these trade-offs because we believed the alternative — building on infrastructure we fully controlled, making it easier to use in the short term but hollow in terms of the ownership promise — was not actually a product we wanted to build.

There is a version of Queensland Foundation that runs on a private database, that has a sleek login experience, that feels like any other web product. It might even have more users in the short term, because it is easier to use. But it would not be delivering what it claimed to deliver. It would be a registry wearing the costume of ownership. We did not want to build that. So we accepted the trade-offs.

We also believe — and this is a bet on the future rather than a description of the present — that the friction of blockchain-based ownership will decrease over time. The tooling is improving. The user experience is improving. The concepts are becoming more familiar. The version of this product that exists in ten or twenty years will be much easier to use than the version that exists today, and the ownership properties will be identical, because they were built into the infrastructure from the start.

The Question of Trust

Something we return to often, in conversations among ourselves and in conversations with people who are trying to understand what we built, is the question of trust.

Every product asks you to extend some amount of trust. When you sign up for a service, you trust that the company will honour its terms, that it will protect your data, that it will not change the rules in ways that harm you. We are not naive enough to claim that blockchain eliminates all trust — you still have to trust that the smart contracts we deployed do what we say they do, that the network we built on is sound, that the broader ecosystem continues to function.

But there is an important difference between the kind of trust blockchain requires and the kind of trust a private database requires.

With a private database, you trust an institution and the people who run it. That trust is personal, historical, relational. It requires you to believe that the people in charge today are good, and that the people who replace them will also be good, and that the incentives will remain aligned, and that no external force will compromise the institutional goodwill you are counting on. That is a lot of trust. It is the kind of trust that erodes over time, that gets strained by acquisitions and leadership changes and economic pressure and legal challenges.

With a blockchain, you trust mathematics and open-source code. The code is publicly auditable — anyone can read it, and many people do. The mathematics do not change. The guarantees that the infrastructure provides today are the same guarantees it will provide in twenty years, because they are not dependent on anyone’s intentions. They are dependent on properties of the system that are stable.

We are not saying blockchain is trustless in an absolute sense. We are saying it requires a fundamentally different and fundamentally more durable kind of trust — trust in systems rather than trust in institutions. That difference matters enormously when you are promising permanence.

What Queensland Means, and Why It Belongs Onchain

We want to step back from the technical and the philosophical for a moment, and talk about Queensland.

Queensland is a place with a particular relationship to space and permanence. It is a state defined, in the popular imagination, by its geography — the coast, the reef, the red earth of the outback, the tropical north, and the dense subtropical south. People who are from Queensland carry that geography with them, even when they leave. The names of its places — Brisbane, the Gold Coast, Surfers Paradise — are not just administrative designations. They are identities. They are things people feel ownership of, in the way you feel ownership of a place that shaped you.

We built Queensland Foundation because we believed those names, those places, deserved a permanent onchain representation. A place for Queenslanders to plant a flag in the digital landscape that was as permanent as the place itself. Not a social media handle that can be deleted. Not a web domain that expires. A name that is genuinely, inalienably theirs.

The TLDs we secured — .queensland, .qld, .brisbane, .surfersparadise, .gold-coast, .brisbane2032 — are not products in the conventional sense. They are a namespace. They are the onchain equivalent of the names on the map. And we believed that namespace deserved to exist on infrastructure that matched the permanence of the places it represents.

Queensland has been here for a very long time, and it will be here for a very long time after every company that exists today has been acquired, dissolved, or forgotten. The infrastructure that carries Queensland’s onchain identity should have the same relationship to time. It should not be contingent on any company’s survival. It should not require renewal. It should simply exist, as the place itself simply exists.

Blockchain is the only infrastructure we know of that can make that true.

A Note on What We Are Not Claiming

We want to be careful here, because there is a version of this post that would veer into the kind of breathless blockchain evangelism that has done real damage to the credibility of genuinely useful technology.

We are not claiming that blockchain solves all problems. We are not claiming that every product should be built on blockchain. We are not claiming that blockchain is inherently better than other infrastructure for applications where permanence and trustless ownership are not the core requirements.

For many applications — a news website, a social network, a search engine, a streaming platform — traditional databases are excellent infrastructure. They are fast, flexible, inexpensive to operate, and well-understood. If we were building a content platform, we would probably not use blockchain. The properties it offers would not be relevant to what we were trying to do.

What we are claiming is specific: for the problem of permanent, individual ownership of digital addresses, where the promise of permanence must not be contingent on any single institution’s survival or goodwill, blockchain infrastructure is the only honest solution we have found. Every alternative we considered either failed to deliver genuine permanence or required placing trust in a human institution that could not reasonably be expected to exist and remain aligned with users’ interests indefinitely.

That is a narrow claim, but it is a firm one. And it is the claim that underlies every decision we made in building Queensland Foundation.

The Infrastructure Is the Promise

We want to close with something that we think is the most important thing we have to say.

When we tell you that your Queensland address is permanent — that you buy it once, that it never expires, that there are no renewals, that no annual fee will ever come due — we are not asking you to trust us. We are not asking you to trust that Queensland Foundation will be well-run, that the people behind it have good intentions, that the organisation will survive whatever comes next.

We are asking you to look at the infrastructure and verify it for yourself.

The record of your ownership is onchain. It is public. It is auditable. It is not stored in our database. We did not retain a key that lets us modify it. We cannot decide, years from now, that the product is shutting down and give everyone thirty days to export their data before the servers go dark. The record exists, and it will continue to exist, on infrastructure that no single party controls.

That is what we built. That is why we made the choices we made. That is what “permanent” actually means when the infrastructure is honest enough to hold the promise.

We chose blockchain because permanence deserved better than a contract with a company. It deserved to be encoded in the infrastructure itself. And that encoding — that decision, made early, when we could have taken easier paths — is the thing we are most proud of.

Everything else we built follows from it.