The problem lives in the number itself

Ask someone for their bank account details and watch what happens. They reach for their phone, open their banking app, navigate through two or three menus, find the account screen, and then either read a string of digits aloud while the other person types them out — pausing, repeating, correcting — or they copy and paste, hoping nothing slips in the transfer.

In Australia, a standard bank payment requires at minimum a six-digit BSB number and a separate account number that can be anywhere from six to ten digits long. If the payment crosses borders, you add a SWIFT code on top of that. Together, these identifiers can constitute more than twenty characters of completely arbitrary, unmemorable information. None of it tells you anything about the person you’re paying. None of it is pronounceable. None of it sticks in the mind after you’ve used it.

This is the fundamental state of modern payment addressing — and almost nobody talks about it, because we’ve all quietly accepted it as just the way things are.

We think it’s worth talking about.

What a number is, and what it isn’t

A bank account number is a pointer. It points to a specific account held at a specific institution, registered in a specific jurisdiction, governed by a specific set of rules. The number itself carries no meaning to a human being. It was never designed to. It was designed for machines — for routing systems, for clearinghouses, for the invisible plumbing of interbank settlement. The number exists to satisfy infrastructure, not people.

That’s not a criticism of the banking system. The infrastructure works. Money moves. But the account number as a human-facing identifier was never the point of its design — it was an accident of exposure. The machines needed a reference. Humans inherited it.

The result is a payment experience that is, at its foundation, hostile to human memory and human communication. You cannot tell a stranger your bank account number over the phone with any confidence that they will get it right. You cannot write it on a business card without worrying it will be transcribed incorrectly. You cannot expect your clients, your customers, or your friends to remember it from one payment to the next. Every single time a payment needs to happen, the full ritual of retrieval and verification starts again.

We think about this a lot — not because we’re obsessed with payments infrastructure, but because we’re obsessed with what ownership and identity mean when they move onchain. And the account number problem is one of the clearest illustrations of a deeper truth: when addressing systems are designed for machines rather than people, people pay a hidden tax in friction, error, and cognitive load every single time they use them.

The parallel problem on the blockchain

If the bank account number problem seems like a legacy issue — something that the old financial world inflicted on us before anyone cared about user experience — we should be honest about the fact that the early blockchain world reproduced exactly the same mistake, and made it worse.

A raw blockchain wallet address looks something like this: a string of forty-two alphanumeric characters, mixing upper and lower case, beginning with “0x” and proceeding into what is, for all practical purposes, visual noise. There is nothing human about it. There is no way to remember it. There is no way to communicate it reliably in conversation, over the phone, or in a brief message. And unlike a bank account number — where a mis-digit typically causes a failed transaction that can be investigated and reversed — a mis-typed blockchain address can mean funds dispatched into the void, permanently and irrecoverably.

The early blockchain community dealt with this the same way the banking world dealt with account numbers: they made copy-paste the default, treated error as a user problem rather than a design problem, and moved on. For years, the friction of raw wallet addresses was accepted as a necessary cost of participating in an open financial system.

We don’t accept that framing. We never did. And neither, eventually, did the broader onchain ecosystem — which is why the entire field of human-readable blockchain addressing exists at all.

What human-readable addressing actually changes

The shift from a raw wallet address to a name-based address is not cosmetic. It is architectural. It changes what is possible, not just what is convenient.

When you replace a forty-two character hexadecimal string with something like yourname.qld, several things happen simultaneously.

The address becomes memorable. A name, particularly one tied to a place or an identity, can be held in working memory, repeated accurately in conversation, written on physical materials without risk of catastrophic error, and recalled days or weeks later. A random string of characters cannot do any of these things.

The address becomes communicable. You can say yourname.qld over the phone, in a meeting, in a voice message, in a social media bio, or on the back of a business card. You can expect a reasonable person to hear it once and get it right. The address enters the category of things that humans can pass between each other through ordinary language — which is the category that bank account numbers, despite decades of use, have never successfully occupied.

The address becomes meaningful. This is perhaps the most underappreciated part. A .qld address doesn’t just route payments — it says something. It locates you. It identifies you. It connects your financial presence to your geographic, cultural, and personal identity in a way that 063-000 / 12345678 simply cannot. An address that means something is an address that people are more likely to remember, more likely to trust, and more likely to use without hesitation.

And critically: the address becomes permanent. Not permanent in the sense of “valid until cancelled” or “active while the account is open” — permanent in the sense of immutable, onchain, yours for life. That permanence changes the relationship between the address and the person who holds it in ways we want to explore carefully.

The tyranny of impermanence

One of the most underexamined costs of the current payment system is the cost of change. Bank accounts close. BSB numbers become obsolete when branches merge. Businesses restructure and acquire new account numbers. People move between banks for better rates, better features, or better service — and every time they do, every payment arrangement they’ve built has to be rebuilt from scratch.

This is not a minor inconvenience. It represents a continuous, recurring cost imposed on the entire economic ecosystem around a person or business. Every client, every supplier, every employer or contractor who had your old details needs to be updated. Every direct debit, every standing order, every automated payment needs to be reconfigured. Mistakes happen. Payments fail. Relationships are strained. And all of it because the identifier — the address — was tied to a specific account at a specific institution rather than to you, the person.

A .qld address is tied to you. Not to your bank. Not to your wallet provider. Not to any platform. To you, permanently, on the chain. If you change your underlying wallet, your .qld address stays the same. If you move your funds, your .qld address stays the same. Anyone who has ever sent to yourname.qld can send to it again tomorrow, next year, or a decade from now, and it will still resolve to wherever you’ve directed it.

This is what permanence actually means in practice: the elimination of the change cost. The identifier is decoupled from the infrastructure it points to, which means the infrastructure can change freely — can be upgraded, migrated, optimised — while the human-facing address stays stable. That’s not just convenient. It’s a fundamentally different relationship between people and their payment addresses than anything the traditional banking system has ever offered.

Why identity and payment belong together

There’s a temptation to think of a payment address and an identity address as two separate things that happen to be useful to combine. We’d push back on that framing. We think they’re the same thing, and always should have been.

When you give someone your bank account number, you’re not really giving them an identity. You’re giving them a routing key that unlocks the ability to send funds in one direction. It carries no context, no reputation, no history of interaction. The number tells them nothing about who you are, and your name — the actual thing that identifies you — appears separately, attached to the transaction by convention, not by architecture.

An onchain name like yourname.qld collapses that separation. The name is the address. The identity is the payment route. There is no gap between “who you are” and “where to send it.” They are the same string of characters, resolving to the same place, held by the same person.

This convergence matters enormously for trust. When someone receives a payment request from a raw account number, they are trusting the contextual information around the number — the email it arrived in, the invoice it appeared on, the verbal instruction given over the phone. The number itself is trust-neutral. It proves nothing.

When someone receives a payment request with a .qld address, the address carries its own implicit verification. It is either yourname.qld or it is not. It resolves onchain to wherever you’ve directed it, deterministically and without ambiguity. The identity and the address are one thing, and that one thing is either correct or incorrect — there’s no ambiguity about whether the number might have been written down wrong, transposed, or slightly different to last time.

This is what we mean when we say a payment address that is also an identity address is more powerful than either alone. Combined, they create something that neither could create separately: a payment route that also builds a relationship, and an identity that is immediately actionable in financial terms.

The simplicity argument isn’t just about convenience

We want to be careful here, because when people talk about “simplicity” in payment systems they often mean convenience — fewer taps, faster flows, a marginally smoother experience. That’s real, and it matters. But simplicity in addressing is not just about convenience. It runs deeper.

Complex addressing systems impose a cognitive tax. Every time you pay someone through the traditional system, you expend real mental effort retrieving, checking, and verifying a string of numbers that carries no inherent meaning. Most of the time this works. Occasionally it fails, and when it fails the consequences range from mildly annoying to genuinely damaging. But even when it works, the mental effort is real. It has been so normalised that most people don’t register it as effort anymore — but remove it, and people notice immediately. The absence of friction is one of the most powerful user experiences available, precisely because its presence was so thoroughly invisible.

Simple addressing also reduces exclusion. Payment systems that require multi-step verification of arbitrary numerical strings are harder to use for people with cognitive differences, people with limited literacy, people operating in a second language, people who are older, people who are anxious or in a hurry. When the address is a readable, meaningful name — especially one tied to a familiar geographic identity like Queensland — the barrier to use drops materially for a much wider range of people.

Simple addressing also enables trust at a distance. One of the genuine barriers to commerce between strangers is the question of whether payment details can be trusted. A .qld address, being permanent and onchain, can be shared on a public profile, on a website, on a physical sign, on a social media bio — and the person receiving it can verify that it resolves correctly without any additional communication. That’s a meaningful reduction in the trust overhead that currently accompanies every commercial transaction between parties who haven’t dealt with each other before.

The Queensland dimension

We could have built addresses on a generic onchain namespace. We chose not to, because we believe place still matters — and we think the relationship between identity and place is undervalued in a world that talks mostly about the borderless nature of digital assets.

Queensland is a real place with a specific culture, a specific economy, a specific community of people who identify with it. When someone owns yourname.qld, that address carries a geographic signal that is immediately legible to anyone in Australia and to many people internationally. It says: this person or this business is part of Queensland. It locates them in a way that a generic handle does not.

That signal is commercially valuable. Businesses that operate in Queensland, that want their Queensland customers to know they are local, that want to participate in a local digital economy rather than an undifferentiated global one — for those businesses, the .qld extension is not merely a namespace. It is a statement of community membership.

And for individual Queenslanders who simply want a permanent, readable payment address that reflects who they are and where they’re from, yourname.qld does something that no bank account number has ever done and no generic onchain address has ever done: it makes your financial address feel like yours.

Permanence at scale

We want to think briefly about what a world looks like where permanent, human-readable addresses are widely held — where people in Queensland have owned their yourname.qld for years, have shared it widely, have built commercial relationships through it, and rely on it as confidently as they rely on an email address or a phone number.

In that world, the payment friction we described at the start — the app-opening, the string-reading, the double-checking, the correcting — is essentially gone for transactions that happen between people who know each other’s addresses. Those addresses don’t change. They don’t expire. There’s no annual subscription that could lapse and break the address, leaving recipients stranded. Once given, once received, the address works for life.

At scale, this changes behaviour. When sending money is as simple as typing a name you already know — when the address is as stable and familiar as a phone number, but shorter and more meaningful — people use it more. The activation energy for a transaction drops. Casual payments, small business invoices, community fundraising, peer-to-peer settlement of shared costs — all of these happen more readily when the addressing overhead is minimal.

This is not a prediction. It’s an observation about what frictionless systems tend to produce: more participation, more volume, and more inclusion of people who were previously put off by the overhead.

Ownership is the thing underneath simplicity

We’ve spent most of this piece talking about usability — about the practical case for a short, meaningful, permanent address versus a long, opaque, temporary one. But there’s something underneath the usability argument that we think deserves its own space.

Ownership.

When you own a .qld address, you own it in a way that is qualitatively different from any payment address you’ve held before. You do not hold it on behalf of an institution that could close your account. You do not rent it from a registry that could change its pricing model, sell its assets, or simply go out of business. You do not depend on an annual renewal to prevent it from expiring and being claimed by someone else.

You hold it as a permanent onchain asset, recorded immutably on the blockchain, transferable only with your explicit action. Nobody can take it. Nobody can revoke it. Nobody can increase the price of holding it, because there is no price of holding it — only a one-time registration fee, paid once, and then it is yours.

This form of ownership is new. It hasn’t existed before in the context of payment addressing. Traditional bank accounts are, in a fundamental sense, products you use under someone else’s terms. Your account number belongs to the bank’s system, not to you. The day the bank decides your account is closed, your payment address is gone.

A .qld address belongs to you. That’s not marketing language. It’s an architectural description of how the system works. The address is recorded on the chain against your wallet. It resolves to where you direct it. It persists regardless of what happens to any company, institution, or platform. This is ownership without the asterisk — and we think it matters enormously, in ways that will only become clearer as more people experience the difference.

The price as signal

We priced entry to the Queensland namespace starting at five dollars, paid once. There are no annual fees. There is no renewal. You pay five dollars and you own your address for life.

We made that choice deliberately, and not primarily for commercial reasons. We made it because we believe that a payment and identity address should be something any Queenslander can own — not a premium product for early adopters with high risk tolerance and significant disposable income. The five-dollar entry is a statement about who this infrastructure is for.

But there’s something else the price communicates, which is perhaps more interesting: it frames the address as infrastructure rather than subscription. When you pay a monthly or annual fee for something, you are implicitly in a rental relationship — the address exists at the pleasure of someone else’s business model. When you pay once and own permanently, the relationship is different. The address is yours in the same way a domain you’ve purchased outright feels different from a service you’re subscribed to.

People treat things they own differently from things they rent. They invest in them, share them more widely, build more around them, and rely on them more deeply. A permanent address that cost you five dollars once is an address you’ll give to everyone, put in your email signature, print on your business card, include in your invoice footer, and expect to use for the rest of your life. A rental address is something you hedge on, just in case the subscription model changes.

We want people to commit to their .qld addresses. We want those addresses to become infrastructure for real lives and real businesses. Making them permanently owned, rather than temporarily leased, is the foundation of that intent.

What onchain means for trust

It’s worth spending a moment on the word “onchain,” because we use it often and it carries real meaning that can get lost in the noise of how the word is sometimes deployed.

When we say a .qld address is onchain, we mean that the record of ownership exists on a public blockchain — not in a company’s private database, not in a centralised registry controlled by a single organisation, but in an open, distributed ledger that anyone can read and nobody can unilaterally alter.

This has direct implications for trust. An address that exists in a company’s database is only as trustworthy as that company. If the company changes its policies, is acquired, or ceases to operate, the address is at risk. An onchain address exists independently of any company, including ours. The Queensland Foundation could cease to exist tomorrow, and every .qld address already registered would continue to resolve correctly, permanently, because the records live on the chain — not in our offices.

We think this matters for a payment address in particular, because payment addresses are the kind of thing people build their lives and businesses around. They get printed on materials, embedded in systems, shared with hundreds of people, cited in contracts. The infrastructure underneath them needs to be trustworthy not just today, but for the entire duration of an economic life. Onchain infrastructure, properly implemented, provides that durability in a way that no private registry ever can.

The comparison, restated simply

We started with a simple framing: a bank account number is long, opaque, and unmemorable. A .qld address is short, meaningful, and permanent. Let’s close by sitting with what those contrasts actually mean.

Long versus short: The cognitive overhead of a twelve-to-eighteen digit account identifier, compared to a name of your own choosing followed by three characters, is not marginal. It’s the difference between an identifier designed for a routing system and one designed for a person.

Opaque versus meaningful: 063-000 / 12345678 tells you nothing about who is at the other end. yourname.qld tells you it’s you, from Queensland, at a permanent onchain address. One is a code. The other is a name.

Unmemorable versus memorable: You will not remember your counterpart’s BSB and account number after a single payment. You will remember yourname.qld after hearing it once. Memory is the silent currency of trust-building, and a payment address that people can remember is a payment address they’ll use again without friction.

And impermanent versus permanent: Bank account numbers change when accounts close, when banks merge, when people switch institutions. A .qld address doesn’t change, ever, because it’s not attached to an institution. It’s attached to you.

The case for yourname.qld as a payment address isn’t complicated. It’s simpler than a bank account number in every dimension that matters to a human being: cognitively, communicatively, meaningfully, and temporally. It’s simpler not because we engineered an especially clever interface, but because we built something that was designed for people from the start — a permanent, readable, owned address that is both an identity and a payment route, anchored in the place where its holder actually lives.

That’s what we built. And we think it’s long overdue.