The question we kept asking ourselves

Before we wrote a single line of infrastructure, before we locked in the TLD names, before we agreed on anything about how this project would work in practice, we kept circling back to one question: what is this thing we are actually building?

An address, obviously. A permanent onchain address tied to a place — to Queensland. But what does an address do? What has an address always done, in the deepest sense of the word?

An address tells the world where you are. It tells someone who wants to find you: come here. It tells a courier, a letter, a bank statement, a friend: this is where you reach this person. An address is simultaneously a statement of identity — I am here — and a statement of receivability — things can come to me here.

We sat with that for a long time. And the more we sat with it, the more uncomfortable we became with the idea of building an onchain address that only did half of that job.

If we built a Queensland Foundation address that gave you identity — a name, a permanent record, something that said this is who I am and where I belong — but left the payment capability to be bolted on later as a feature, we would be building something that was fundamentally incomplete. Not just incomplete in a technical sense. Incomplete in the philosophical sense. We would be building half an address.

So we made a decision early, and we made it with clarity: payment capability goes in from day one. Not as a feature. Not as an upgrade. Not as a phase-two promise. As part of the address itself. As inseparable from the address as the name on the front of it.

This post is about why we made that decision, what it means in practice, and why we think the separation of identity and payment in most digital infrastructure is one of the great unresolved mistakes of the internet age.

How the web taught us to separate things that should be together

To understand why we built this the way we did, it helps to understand the problem we were building against.

The traditional internet gave us domain names. Domain names are remarkable — the idea that you could type a word and be taken somewhere, that a human-readable label could point to a machine-readable location, was genuinely transformational. But domain names were built for a specific purpose: they were built to point to websites. They were navigation tools. You typed an address, a page loaded.

Payments were never part of that model. Payments on the internet were always a layer sitting on top of the addressing system, not embedded within it. You navigated to a website, and then somewhere on that website, there might be a payment processor, a checkout flow, a third-party gateway. The address and the payment destination were always two different things, operated by different systems, often controlled by different companies.

This created a world where your identity online and your ability to receive value online are perpetually disconnected. Your domain name is one thing. Your bank account is another thing. Your PayPal handle is a third thing. Your crypto wallet address, if you have one, is a fourth thing — a long, machine-generated string of characters that nobody can remember and that bears no relationship whatsoever to who you actually are.

We built the web this way not because it was the right way, but because it was the only way available at the time. The technologies to do otherwise didn’t exist. The naming layer and the financial layer had to be separate because they were managed by entirely different systems with entirely different architectures.

That constraint no longer exists. And yet so much of the infrastructure being built today still behaves as though it does — still treats identity and payment as two separate problems, two separate layers, two separate products.

We refused to accept that.

What onchain infrastructure actually makes possible

The reason we could make this decision — the reason it was available to us at all — is that onchain infrastructure collapses the distance between identity and value in a way that simply wasn’t possible before.

When something lives on a blockchain, it is not just a record. It is a record that can hold relationships to other things. An address on a blockchain is not just a label. It is a node in a live system. It can point to a name, to a wallet, to a history of transactions, to a profile, to a set of permissions — all at once, all from the same root identifier.

This is what makes it fundamentally different from a domain name as the internet has historically understood one. A traditional domain name is a pointer. It points somewhere. It is inert by itself. An onchain address is a participant. It exists in a system that is always running, always verifiable, always capable of sending and receiving.

When we registered the Queensland TLDs — .queensland, .qld, .brisbane, .surfersparadise, .gold-coast, and .brisbane2032 — we were registering them on this kind of infrastructure. We were registering them as participants in a live onchain system, not as static pointers in a lookup table.

That meant we had a choice that previous generations of infrastructure builders never had: we could define, from the beginning, what it means to own one of these addresses. We could say: owning yourname.queensland means you own something that is your identity and your payment destination simultaneously and inseparably.

We said that. And we meant it.

The problem with “we’ll add it later”

There is a very tempting approach to building infrastructure, and we have watched it play out across technology for decades. It goes like this: start with the simplest possible version of the thing, prove it works, get adoption, and then add more capability later. This approach has a name — it is called iterative development, and it is often entirely sensible.

But there is a category of decisions where the “add it later” logic breaks down. Those are decisions about foundational architecture. About the shape of the thing at the base level. Because once you have adoption, once you have real people using the thing you built, the shape of the base becomes extremely difficult to change. You are no longer building a product. You are maintaining infrastructure. And infrastructure change at scale is one of the hardest problems in technology.

If we had launched Queensland Foundation addresses without payment capability, and those addresses spread across Queensland — across families, businesses, creators, communities — we would have created an identity layer with no financial layer attached. And then trying to retrofit that financial layer later would mean two things, both bad.

First, it would mean asking everyone who already owned an address to update their setup, connect a wallet, configure resolution records, understand new concepts they hadn’t needed before. You would be asking people to do work. People with lives and businesses and better things to worry about than reconnecting infrastructure they already thought was finished.

Second, and more importantly, it would mean that during the period between launch and retrofit, people would have been building habits and mental models around addresses that didn’t include payment. They would have learned to think of a Queensland address as an identity thing, separate from money. Once that mental model is set, it is very hard to unset. You are no longer adding a feature. You are trying to change how people conceptually categorise an object they already own and use.

We have seen this failure mode before. We have watched platforms try to graft payment rails onto identity systems and identity systems onto payment rails and end up with something that feels awkward in both directions — never quite identity, never quite payment, always apologising for the seam between the two.

We did not want to build something with that seam in it.

What it means to own both at once

Let us be precise about what we built and why it matters.

When someone claims a Queensland Foundation address — say, james.queensland — they are not just registering a name. They are establishing a permanent onchain record that resolves to both their identity and their payment destination simultaneously. The same address that says this is James also says this is where you can send James value.

This is not a trivial design decision. It is a statement about what an address fundamentally is.

Think about the most enduring addressing systems in the physical world. Your street address does not just tell people where you live. It also tells couriers where to deliver packages, tells the bank where to send statements, tells the government where to direct correspondence. The address is not just a label. It is a fully functional point of contact for the world. Things arrive at an address. That is what addresses do.

We wanted to build the digital equivalent of that. Not a name tag. Not a profile page. Not a navigation pointer. A genuine address — a place where your identity lives and where the world can reach you, including financially.

When the payment layer is built in from the start rather than added later, something important happens: the address becomes a complete object. It has integrity. It does not need to be supplemented or enriched or connected to something else before it becomes fully useful. You claim it, and it works. Identity and receivability come together in the same moment of ownership.

That completeness matters enormously when you think about who we are building this for. We are not building primarily for people who are deeply comfortable with blockchain technology and have already set up wallets and explored onchain infrastructure extensively. We are building for Queenslanders — for people who identify with this place and want a permanent digital address that reflects that. Many of those people are encountering onchain infrastructure for the first time. The last thing we want is to present them with a two-step process: first get your identity, then come back and attach the financial layer. That is two friction points where there should be one. Two moments of confusion where there should be none. Two processes to understand where the address itself should be the simple, singular, complete thing.

Why “payment address” is not the same as “payment gateway”

We should be clear about something, because the word “payment” tends to conjure a specific image — checkout flows, merchant accounts, payment processors, the infrastructure of commerce.

That is not exactly what we mean when we say a Queensland Foundation address is a payment destination.

A payment destination, in the onchain sense, is something more elemental than a gateway. A gateway is a piece of infrastructure you pass through. A payment destination is a place value can arrive at directly, without needing to be routed through anything.

When your address resolves to a wallet, you are not routing through a gateway. You are being paid directly. There is no merchant account to apply for. There is no processor taking a percentage. There is no approval required from a financial institution. There is no jurisdiction deciding whether your type of business, your type of person, your type of transaction is acceptable. There is just an address, and a wallet, and a direct line between them.

This is qualitatively different from having a PayPal link in your bio. It is qualitatively different from having a Stripe account attached to your website. Those are gateways. They sit between the person paying and the person being paid, and they exercise judgment and take fees and can be turned off.

An onchain payment destination is not a gateway. It is a destination. The address and the wallet are the same thing, structurally. There is nothing sitting in between.

We think this distinction matters a great deal, especially for the kinds of people and the kinds of communities that Queensland Foundation addresses are meant to serve. Small businesses. Freelancers. Creators. Market stall operators. Artists. Anyone whose economic life does not fit neatly into the commercial infrastructure that was designed for large, established, easily categorised economic actors.

For those people, having a permanent address that is also a direct payment destination — not a gateway, not a third-party service, but an actual destination that resolves from the same identifier as their identity — is not a convenience. It is a genuinely different kind of economic participation.

The relationship between permanence and payment

There is another reason why the payment capability had to be foundational rather than added later, and it has to do with the nature of permanent infrastructure.

Queensland Foundation addresses do not expire. There are no renewal fees. Once you own the address, you own it. Forever. It is immutable on the blockchain, tied to your wallet, transferable if you choose to transfer it, but never at risk of expiry, never dependent on your remembering to pay an annual fee, never vulnerable to being taken from you by an expiring credit card or a lapsed subscription.

This permanence has a particular relationship with payment capability. If we were building something temporary — something that had to be renewed each year, something that lived in a traditional DNS registrar’s database — then perhaps the argument for foundational payment capability would be weaker. Temporary infrastructure can be augmented, modified, rebuilt. You are not making a permanent commitment; you are just making a current decision.

But permanent infrastructure is different. Permanent infrastructure is the kind of infrastructure that people build lives around. That businesses put on business cards. That communities organise around. That people share with confidence because they know the address will still work in twenty years.

When you build permanent infrastructure with a payment capability gap — with identity but no receivability — you are baking that gap into something that will persist indefinitely. You are not deciding to add payment capability later. You are deciding that the permanent record, the record that will outlast you and your team and possibly the company that built it, is a record of identity without economic functionality.

We found that unacceptable. If an address is going to be permanent, it needs to be permanently complete.

The two functions — identity and payment — need to be permanent together. They need to have been there from the start, so that the permanent record is not a record of a half-finished thing. It is a record of a complete address that was designed to last and designed to work.

The signals we pay attention to when building

When we were making this decision, we were also paying attention to the broader trajectory of how digital infrastructure is evolving. Not because we follow trends for the sake of it — we do not — but because it is useful to understand where the weight of evidence is pointing.

The evidence is pointing in one direction very clearly: the separation between identity and payment in digital infrastructure is collapsing. Not slowly and not reluctantly. Rapidly and by design.

Across the entire onchain naming ecosystem, the story keeps repeating itself. Human-readable names that map to both identity and wallet. Addresses that resolve to who you are and where you receive value. The dominant use case everywhere this infrastructure exists is not navigation. It is not replacing URLs. It is the unification of identity and payment destination.

This convergence is happening because it reflects something true about what people actually need from digital infrastructure. People do not lead parallel digital lives — one life as an identity holder and another life as a payment recipient. They are the same person making the same claims in the same spaces. The infrastructure should reflect that unity.

When we watched that pattern emerge across the ecosystem, and then looked at what we were building for Queensland, the conclusion was obvious. We were not going to build against the direction of travel. We were not going to build a naming system and leave the payment question for later, knowing that everyone around us had already understood that the payment question is always part of the same question as the identity question.

We were going to build with that understanding baked in from the first line of infrastructure.

What this means for how people experience their address

We have talked a lot about the philosophical and architectural dimensions of this decision. Let us talk about the human dimension.

When someone opens their Queensland Foundation address and sets it up, the experience we want them to have is one of completeness. Not the experience of: here is your name, now go and figure out the other things you need to connect to it. Not the experience of: here is step one, here are five more steps. Not the experience of: your identity is ready, your economic functionality is a separate process.

The experience we want them to have is simpler and more satisfying than any of that: here is your address. It is complete. Your name is on it. Your wallet is attached. You can share it with anyone. When someone needs to find you, this is where they come. When someone needs to pay you, this is where they come. One address. One place. You.

That simplicity is not accidental. It is the result of a foundational decision that we made deliberately, before anyone owned an address, before the infrastructure was live, before there was any pressure to launch quickly or cut scope or defer hard problems.

The hard problem of unifying identity and payment was not deferred. It was the first problem we solved.

Why this matters more in regional places

Something we thought about carefully as we built this for Queensland specifically — not as a generic global product, but as infrastructure rooted in a particular place — is that the need for unified identity and payment capability is often most acute in regional, non-metropolitan communities.

Large cities and their economies tend to be well-served by existing financial infrastructure. Payment gateways are built assuming a certain kind of business, a certain kind of customer, a certain kind of transaction. If your economic life fits that mould — if you are a business with reliable turnover, an established credit history, a fixed physical location — the existing systems work reasonably well for you. You can get a merchant account. You can access payment rails. You can build commercial infrastructure on top of what already exists.

But Queensland is not only large cities. It is the Gold Coast and Brisbane and Surfers Paradise, yes, but it is also the people behind those places — the small operators, the creatives, the community builders, the families — and it is also the parts of Queensland that do not fit neatly into the commercial models that most payment infrastructure was built for.

For those people, an address that is also a direct payment destination is not a convenience upgrade. It is access to a kind of economic participation that was previously unavailable to them without navigating a complex set of approvals, fees, and institutional gatekeepers.

When a creator in regional Queensland can share their name.queensland and know that it is simultaneously their identity and the place where they can receive direct payment — without a merchant account, without a payment processor, without annual fees or application processes or anyone deciding whether they qualify — that is a meaningful expansion of economic access.

We built payment capability into the address from the start partly because it was the right architectural decision. And partly because of exactly this: we knew who we were building for, and we knew that for them, having a complete address from day one was not a nice-to-have. It was the whole point.

On the question of trust

There is one more dimension of this decision that we want to be honest about, because it touches on something more personal about why we built things the way we did.

Infrastructure that handles payments is infrastructure that people trust with their economic lives. And trust is not something you earn by having good intentions. Trust is something you earn by making good decisions, consistently, over time — especially the decisions that nobody is watching closely, the decisions you make before there is any external pressure to make them one way or another.

The decision to include payment capability in Queensland Foundation addresses from the start was one of those decisions. Nobody was demanding it. Nobody would have complained if we had launched without it and promised to add it later. We could have moved faster. We could have launched a simpler product earlier.

We chose not to.

We chose to do the harder thing, because the harder thing was the right thing. Because building incomplete infrastructure and calling it complete is a form of dishonesty that compounds over time. Because the people who trust us with their identity and their economic participation deserve infrastructure that was built with full respect for what it needs to be — not half-respect, not good-intentions-with-caveats, but full respect.

When someone claims theirname.queensland, they are trusting us that the thing they own is what it says it is: a complete address. An address that does the full job of an address. An address that will be there forever, working the way it was supposed to work from day one.

That trust was what shaped every architectural decision we made. Including this one.

Two functions, one object

We want to end with the simplest version of what we have spent all these words explaining.

An address is identity and receivability simultaneously. Those two functions have always been inseparable in the most enduring addressing systems in the physical world. The best digital infrastructure should reflect that same unity.

Queensland Foundation addresses were built to reflect it. Not because we were told to. Not because it was the obvious commercial choice. But because when we asked ourselves what this thing we were building actually was — what an address, properly understood, needs to be able to do — we could not find a convincing reason to build anything less than the full answer.

The full answer is: identity and payment capability, together, in one object, from the first day anyone ever owns it.

That is what we built. That is why.