Every decision in this project has flowed from a single question: what does it actually take to put a permanent digital address in the hands of an ordinary Queenslander?

Not a developer. Not someone who already holds cryptocurrency. Not someone who has ever heard the word “blockchain” spoken in a sentence that made sense to them. Someone who runs a business in Cairns, or coaches a football team in Toowoomba, or grew up in Inala and wants something of their own on the internet that nobody can ever take away from them. That person. Always that person.

When we made the decision about which blockchain to build on, we didn’t start with the technology. We started with that person, and we worked backwards. The chain we chose is the answer to a very specific set of requirements — requirements that most blockchain projects never have to think about, because most blockchain projects are not trying to reach the people we are trying to reach.

This post is an attempt to explain that reasoning honestly. Not as a technical document, and not as a sales pitch. Just as people who spent a long time thinking carefully about infrastructure, and who want to share what we were actually weighing.

The first thing we had to accept about blockchain

There is a version of this story where we simply picked the biggest chain, assumed it was the best, and moved on. That is what many projects do. Biggest community, biggest name recognition, most developer tooling, done. But the moment we sat down and mapped out what we actually needed, it became obvious that popularity alone was not a useful selection criterion.

Blockchain technology, broadly, is not designed with the same user in mind that we were designing for. The infrastructure that powers decentralised finance, speculative token trading, and smart contract complexity is extraordinary. It has changed what is technically possible on the internet in fundamental ways. But it was largely built by developers, for developers and early adopters — people who were already comfortable navigating wallets, gas fees, seed phrases, and the general unpredictability of transaction costs that might be twenty cents one day and twenty dollars the next.

That unpredictability mattered enormously to us. Because one of our core commitments — one that is not negotiable, not a marketing position, but a structural fact about how Queensland Foundation works — is that a permanent onchain address should cost five dollars. Once. Not five dollars today and a different amount tomorrow because network congestion happened to spike. Not five dollars plus a gas fee that a new user has no way of anticipating or understanding. Five dollars, total, permanent, done.

That meant the chain we chose had to have transaction costs so low, so stable, and so predictable that we could absorb them entirely and still build something sustainable. Not approximately low. Not usually low. Reliably, structurally, architecturally low — by design, at the protocol level, not just on a good day.

That single requirement eliminated a large portion of the available options before we had even asked any other question.

What permanence actually demands of infrastructure

When we say these addresses are permanent, we mean it in the full weight of that word. Not permanent-until-we-go-broke. Not permanent-unless-the-platform-pivots. Not permanent-as-long-as-you-pay-the-annual-renewal. Permanent in the way that a title deed is permanent, in the way that a name carved in stone is permanent. You acquire it once, it is recorded, and it belongs to you for as long as you want it.

That is a meaningful promise. And it is a promise that places specific demands on the underlying infrastructure that makes it possible.

Permanence on a blockchain is not simply a matter of intent. It requires that the chain itself be built around the idea that records written today will be readable, verifiable, and intact for decades. It requires a network that does not depend on any single company’s continued interest in maintaining it. It requires a consensus model that has been stress-tested over time, that has demonstrated it can hold its state through market crashes, protocol disputes, hardware failures, and the general entropy of complex systems.

We thought hard about what it would mean to make a promise of permanence on infrastructure that had not yet proven it could survive long-term. Newer chains are sometimes faster, sometimes cheaper, sometimes more technically innovative. But a chain that has only existed for a year or two has not yet shown us what it looks like under sustained pressure. It has not demonstrated what happens when the people who built it lose interest, or when a fork decision fractures the community, or when the incentive structures that keep validators online are tested by a prolonged bear market.

We were not building a product for the next funding cycle. We were building infrastructure for Queensland addresses that should still be valid, still owned, still immovable in twenty years. That required us to choose a chain with a track record, not just a roadmap.

The chain we chose has one. It has operated continuously, survived serious tests, maintained its core state without rollbacks or resets, and built an ecosystem of tooling, wallet support, and developer familiarity that makes it genuinely accessible to the people who will need to interact with it now and into the future.

The problem with complexity

Here is something we noticed early in our thinking: the more technically sophisticated a blockchain is, the harder it tends to be to use.

This sounds obvious when you say it out loud. But it is not the way that blockchain projects usually talk about themselves. Most projects in this space lead with capability — look at everything this chain can do, look at the smart contracts it can run, look at the DeFi ecosystem and the layer-2 rollups and the zero-knowledge proofs. And that is genuinely impressive. But capability and accessibility are not the same thing, and in our case they are often in tension.

The person we are building for does not need a chain that can run a decentralised exchange. They need a chain where the transaction that records their address is so simple, so cheap, and so fast that they never have to think about it. They need a chain where minting an address does not require them to first understand gas, then acquire a specific token on a specific exchange, then configure a wallet to the right network, then estimate a fee, then wait an uncertain amount of time for confirmation. The chain we chose processes transactions quickly and cheaply enough that the entire technical layer can be made invisible.

That invisibility is the goal. Not invisibility as a trick or a deception — the blockchain is right there, public and auditable and real — but invisibility as good design. A door handle does not announce its mechanism every time you open a door. Good infrastructure enables people to do the thing they came to do, without making the infrastructure itself into an obstacle.

We chose a chain where the gas cost is so close to nothing that we can present a flat, human-readable price. Five dollars. That is the price. The chain is the reason that price is possible.

Thinking about the people who don’t know they want this yet

There is a category of user that blockchain projects almost never design for: the person who has not yet decided to engage with blockchain technology at all.

Most blockchain product design assumes you’re starting from someone who has already self-selected into the space. They have a wallet. They have some crypto. They know what a private key is. They might be cautious, but they are already here. That is a reasonable assumption for most Web3 products. But it was exactly the wrong assumption for us.

The Queenslanders we are trying to reach — the regional business owner, the community organisation, the family who wants to register their suburb as a permanent address — many of them do not have a wallet. Many of them have heard of crypto only in the context of scams, or speculation, or things that seem technically intimidating and financially risky. Many of them have no mental model of what a blockchain does, and no particular interest in developing one.

Our job is to meet them where they are.

The chain we chose supports the kind of tooling and payment gateway infrastructure that allows us to accept straightforward payment methods — the ones people already use, without requiring them to first navigate a cryptocurrency exchange. The chain has the developer ecosystem, the API support, and the smart contract flexibility needed to build an interface that feels like registering a domain name on any normal website, not like entering the engine room of a decentralised protocol.

This matters more than people who are already comfortable in Web3 tend to appreciate. There is a version of this project that is technically perfect and practically unusable, because it demands that users adopt five new behaviours simultaneously just to complete a purchase. We worked very deliberately to not build that version.

The chain we chose gave us the tools to build something simpler. And simpler, in this context, means more Queenslanders can actually use it.

Ownership as a value, not a feature

We want to say something about ownership that goes beyond the product.

When we talk about permanent onchain addresses, we are not primarily talking about a convenient technical format. We are talking about a shift in what it means for someone to have a digital presence. The traditional web operates on a rental model. Every domain name that anyone has ever registered on the ordinary internet has been a lease. You pay annually. You retain it as long as you keep paying. The moment you stop — through forgetfulness, financial hardship, death, or any other interruption — the thing you built your online identity around can be taken, resold, or simply lost.

That is a strange arrangement when you think about it clearly. We have normalised the idea that your digital address is something you rent from a corporation, under their terms, for as long as they choose to offer the service and you choose to keep paying. But we would find it deeply strange if physical addresses worked the same way — if you had to pay an annual fee to retain the right to be associated with your own street address, and if failure to pay meant that address was reassigned to someone else.

Onchain addresses work differently. Once the record is written to the chain, it belongs to the person whose wallet holds it. There is no annual renewal because there is no centralised party whose continued service is required to maintain the record. The record lives on the chain, which is maintained by a distributed network of validators whose incentives are aligned with keeping the chain running, not with extracting annual payments from address holders.

This is a fundamentally different relationship between a person and their digital identity. It is ownership, not tenancy.

The chain we chose supports this model natively. The ownership model is not a workaround or a hack — it is how the chain is designed to work. Tokens representing ownership are held in wallets, controlled by private keys, transferable by the holder, and readable by anyone. The rules of the chain enforce the ownership. No company, including us, can revoke an address that has been minted. We do not retain a master key. We do not have the ability to decide that your address should belong to someone else. The chain itself is the authority, and the chain is not ours.

That felt important. Not just as a technical property, but as an ethical one.

The question of longevity

One of the harder conversations we had during the design phase of this project was about what happens to an onchain address if the company or foundation that issued it stops operating.

It is an honest question, and it deserves an honest answer. Most digital products are fragile in exactly this way. If the company behind them closes, the product disappears. Email addresses, social media handles, domain names registered through a specific registrar — all of these are contingent on the continued operation of the organisations that administer them.

We designed Queensland Foundation to be different, but we also needed the infrastructure we built on to support that design.

The chain we chose is not dependent on us. When an address is minted onto it, that record exists independently of anything we do or don’t do subsequently. It is a record on a public ledger that is maintained by a distributed global network. We are not the validators. We are not the nodes. We are not the consensus mechanism. We built on top of an existing, functional, decentralised infrastructure — and that means the records we help people create are not hostage to our own continued existence.

That is not a trivial thing to be able to say. It required us to choose a chain that was genuinely decentralised — not chain-branded as decentralised while being operationally dependent on a small group of known parties, but actually distributed in its validation, actually open in its operation, actually indifferent to whether any particular organisation continues to participate in it.

A chain like that is harder to find than you might expect. Much of what gets described as decentralised infrastructure is more accurately described as federated infrastructure — operated by a defined consortium of parties who have agreed to behave in a certain way. That is fine for some use cases. It is not fine for ours, because our use case requires that the permanence we promise to people is not contingent on any party’s goodwill.

Why we thought carefully about immutability

Immutability is one of those words that blockchain projects use often and explain rarely. What it actually means, in the context of what we are building, is this: once your address is on the chain, the record cannot be changed by anyone other than you.

Not by us. Not by a court order directed at us. Not by a competitor who wants your address. Not by a data breach that compromises our systems. The record is yours, it is protected by the cryptographic rules of the chain, and altering it requires your private key — which only you hold.

This is only as strong as the chain’s commitment to maintaining its history. Some chains have, in their histories, executed what are called “rollbacks” — decisions by the validator set to reverse the chain’s history in response to an exploit or a significant loss. These decisions are sometimes defensible in context. But they demonstrate something important: that immutability, on those chains, is conditional. It holds until a sufficiently significant event convinces the validators that it should not.

The chain we chose has maintained an extraordinarily clean record on this front. It has not executed rollbacks. It has maintained its ledger continuously and consistently. There have been difficult moments in its history — as there have been in every chain’s history — and it has navigated them without compromising the integrity of its historical record.

That record mattered to us. Because the permanence we offer people is only as real as the chain’s commitment to preserving what has been written to it.

Thinking about scale, differently

Most discussions about blockchain scalability are about throughput — how many transactions per second can the chain handle at peak load. That is a legitimate question for a chain processing millions of financial transactions. It was not our primary concern.

Our concern about scale was different. We were thinking about what it looks like for this project to succeed over a long time horizon — not in terms of speed, but in terms of cost stability and network health.

A chain that is cheap today because it is lightly used might become expensive tomorrow if it becomes heavily used and the fee market tightens. That is a real pattern, and it has happened on several prominent chains in ways that made them temporarily unusable for small transactions. If our five-dollar price point depends on a chain remaining lightly used, then our price point is not actually stable — it is just lucky.

The chain we chose has a fee structure and a capacity model that allows us to be confident about cost stability not just today but as the project grows. The fees are low by design, not by accident. The architecture is intended to support high transaction volumes without the kind of fee market volatility that would undermine our pricing model.

That structural quality is the difference between a promise we can keep and a promise we hope we can keep.

On trust and what decentralisation actually protects

There is a version of this project that we could have built on centralised infrastructure. A database. A traditional web hosting arrangement. Something we fully controlled, fully understood, and could update at will.

We chose not to, and it is worth being explicit about why.

Centralised databases are powerful and practical. But they concentrate trust in whoever controls the database. If we control the database, you are trusting us — trusting that we will not alter records, not lose data, not be subject to external pressure that forces us to act against the interests of our address holders. That trust might be well-placed. We believe it would be. But it should not be necessary.

The whole point of building on a public blockchain is to shift the source of trust from a specific organisation to a protocol. When your address is on-chain, you are not trusting us. You are trusting mathematics and cryptography and the distributed consensus of a global network. Those are better things to trust than any single organisation, including us.

This is a choice about the structure of power. We are deliberately limiting our own authority over the records we help create, because we think that is the right way to build something that is genuinely in the interest of the people who use it. The chain we chose lets us make that limitation real. It is not just a policy we have adopted. It is enforced by the protocol.

Accessibility as infrastructure

We have talked about accessibility in terms of user experience — making the purchase process simple, accepting familiar payment methods, hiding the technical complexity. But accessibility has another dimension that is just as important: financial accessibility.

Five dollars is a deliberate choice. We chose that number because it is within reach of an enormous range of Queenslanders, regardless of their financial situation. It is less than a cup of coffee at most places along the Gold Coast. It is less than the cost of a public transport trip. It is not a price that requires someone to evaluate whether they can afford it. It is a price that is just available.

To make that price possible, we needed a chain where the cost to write a record to the ledger was negligible. Not low — negligible. A chain where the minting of an address adds a fraction of a cent to our costs, not a fraction of a dollar. That structural fact about the chain makes the five-dollar price point not just viable but sustainable across tens of thousands of addresses without the economics falling apart.

Accessibility here is not a value we hold in addition to the technical choices we made. It is a value that the technical choices were selected to serve. The chain is the instrument through which the price becomes possible, and the price is the instrument through which the mission becomes real.

The relationship between infrastructure and identity

There is something we have thought about a great deal that does not often come up in technical discussions of blockchain infrastructure: what it means for a piece of infrastructure to carry something as personal as an address.

An address is not just a technical pointer. It is identity. It is affiliation. When someone registers a .queensland or a .brisbane address, they are not just acquiring a routing label. They are associating themselves with a place that matters to them, in a form that they will carry indefinitely. That act deserves infrastructure that is worthy of it.

We thought about what it would mean for someone to register their suburb or their city as a permanent onchain address, and then for that record to be lost, or corrupted, or dependent on a system that turned out not to be as permanent as advertised. We thought about what it would mean to make that promise — permanent, yours, for life — and to break it because we chose infrastructure that was cheaper or more convenient but not genuinely durable.

The chain we chose is not the easiest choice, and it is not the cheapest choice in absolute terms. It is the choice that we could defend on a long enough time horizon. It is the choice we could look at in ten years and say: this is still running, the records are still there, the people who registered addresses in the early days still own them, and the infrastructure has proven worthy of the promise we made.

That is a different standard than “it works today.” Most things work today. The question that mattered to us was whether it would work indefinitely.

Why we don’t think of this as a bet

There is a framing we want to resist, which is the idea that choosing a blockchain is like placing a bet. That framing assumes a kind of speculative uncertainty — you are wagering on which chain will “win,” which will attract the most activity, which will appreciate most in value or mindshare over time.

We do not think about it that way, and not because we are naive about the uncertainty that exists in this space.

We think about it the way you think about choosing materials for a building. You are not betting that concrete will win against timber. You are asking: what are the properties of this material, what does it do well, what are its failure modes, how has it performed under load over time, and does it match what the structure needs to do? Those are engineering questions, not speculative ones.

The chain we chose has specific properties that match specific requirements. Low and stable transaction costs. Genuine decentralisation. A long and tested operational history. An ecosystem of tooling that allows non-technical users to be served without exposing them to the complexity underneath. Immutability as a genuine architectural commitment, not a provisional aspiration.

Those properties do not fluctuate based on market sentiment. They are either present or they are not. We evaluated them as carefully as we could, we satisfied ourselves that they were present and durable, and we built.

The long view

Everything about Queensland Foundation is built on the assumption of a long time horizon. The addresses we issue are meant to outlast us. They are meant to be passed down. They are meant to be there for someone’s grandchildren in the same way that a title deed to a piece of land is there for someone’s grandchildren.

That assumption changes almost every decision you make about infrastructure.

A project that is optimising for the next two years chooses infrastructure that is fast, fashionable, and compatible with what other projects are doing right now. A project that is optimising for the next fifty years chooses infrastructure that has demonstrated it can survive things that nobody anticipated — market crashes, protocol disputes, technological shifts, regulatory pressure, and the general unpredictability of a technology space that is still, in the largest sense, new.

We have been transparent with ourselves about the fact that we cannot predict the future with certainty. No one can. The history of technology is full of infrastructure that seemed permanent and turned out not to be. We chose with humility about our own limitations as predictors.

But we also chose with conviction. The chain we built on has properties that make it more likely to be durable than the alternatives we evaluated. It has survived enough of the unpredictable to give us reasonable confidence that it will survive more of it. It was designed with permanence as a property, not an afterthought.

What we want people to understand

When someone registers a .queensland or a .goldcoast address for five dollars, we want them to understand what they are actually getting. Not in technical terms — they don’t need the technical terms. But in real terms.

They are getting something that cannot expire. They are getting something that nobody can take from them without their consent. They are getting something that lives on infrastructure that is not ours to control, not theirs to maintain, and not dependent on either of us doing anything in particular to keep it alive. They are getting a record that will exist as long as the chain exists — and the chain was chosen specifically because we believe it will exist for a very long time.

That is the promise. And the chain we chose is not incidental to that promise. It is the foundation of it.

We chose it because we believed it matched our values: permanence, accessibility, genuine decentralisation, and the structural capacity to serve ordinary people at a price that ordinary people can afford. We will continue to believe that as long as it continues to be true.

And our job, as long as we are here, is to make sure it stays true.