The Problem Nobody Talks About

There is a version of this problem that almost everyone has experienced and almost nobody has named.

You have a freelancer you love working with. You’ve paid them before, everything went smoothly, and now you want to pay them again. You reach into your contacts, pull up their name, and try the email you have on file. It bounces. Or worse — it delivers, but to someone who is no longer them. They changed jobs, changed providers, left a platform, moved on. Their old email still exists somewhere in your records, a ghost address pointing to nothing useful, and now you have to start over. You reach out through a different channel, ask for their current details, wait for a reply, verify it’s really them, and then — finally — you can pay them.

That is not a rare edge case. That is one of the most common friction points in the entire history of digital commerce, and we have simply accepted it as background noise.

We think it deserves more attention than it gets. Because until you fix the identifier, you cannot fix the payment.

What a Payment Identifier Actually Needs to Do

When you strip away all the complexity of modern payments — the rails, the processors, the clearing houses, the compliance layers — what you are left with, at the core, is a very simple challenge: you need to be able to point at a person or entity and say, with confidence, that is where the money goes.

Everything else is plumbing. The identifier is the address on the envelope. And for an identifier to do its job reliably, it needs to have certain properties.

It needs to be unique. If two different people can have the same identifier, you have a fraud and misdirection problem.

It needs to be stable. If the identifier changes over time, every record that references the old one becomes stale. Everyone who wants to pay you has to update their records. Recurring payments break. Invoicing systems drift. The cost of that update is paid not just by you, but by every single person who has your details saved.

It needs to be portable. An identifier tied to a particular institution, platform, or service creates a dependency. When you leave that institution — or when the institution leaves you — the identifier stops working. You are not the owner of that identifier. You are merely its tenant.

It needs to be resolvable. Someone holding your identifier needs to be able to actually reach you with it, or send value to it, without requiring your intervention every time.

Most of the identifiers we use today fail at least one of these tests. Many fail two or three.

The Email Problem

Email became a de facto payment identifier not because anyone designed it that way, but because it was the one thing almost everyone had, and the one thing that most payment platforms could use as a login key. PayPal built its model around it. Venmo, Cash App, and a generation of fintech products followed. If someone asked how to send you money digitally, the answer was almost always: “just use my email address.”

This is understandable. Email was universal, memorable, and already in use. Piggybacking on it was a reasonable shortcut.

But email was never designed to be a financial identifier. It was designed to be a communication address. And communication addresses are, by their very nature, ephemeral.

People change their email addresses constantly. They leave employers and lose their work address. They abandon accounts with providers that went out of fashion. They create new addresses to escape spam. They get married and change their name. They move countries. They pivot businesses. Over the course of a working life, a person might cycle through half a dozen primary email addresses, leaving a trail of stale records in every payment system that ever saved them.

The problem is not that changing your email is unreasonable. Of course it is sometimes necessary. The problem is that when you change it, the update burden is distributed outward — to every single person and system that has your old address on file. And most of them will never update it, because most of them will not even know you changed it, until the moment they try to pay you and something goes wrong.

When an email address stops working, it does not broadcast its own failure. It just quietly ceases to point at you. And then, one day, someone tries to use it, and they are left standing in front of a closed door with no forwarding address.

The Institutional Dependency Problem

Even when email works perfectly as an address, it creates a deeper dependency problem: you do not actually own your email address. You have it on loan from a provider.

A free webmail account can be deleted for inactivity. A work address disappears the day you stop being an employee. A domain-based address vanishes if you stop renewing the domain. In every case, the continued existence of your identifier is contingent on decisions made by someone else — an employer, a provider, a registrar — and those decisions are entirely outside your control.

This is an astonishing amount of risk to place at the foundation of something as important as how people pay you.

Imagine if your physical street address could be taken away from you by a landlord, a government agency, or a utility company, with no notice and no recourse. Imagine if the moment you left a particular building, everyone who had your address found that it no longer resolved to you. We would consider this intolerable for physical mail. We have somehow come to accept it for digital payments.

The Bank Account Problem

If email is the informal default, then bank account details are the formal one. The BSB and account number, the IBAN, the sort code and account number — the specific format varies by country, but the concept is the same everywhere. You give someone a string of digits that points to an account held at a particular institution, and they use that string to send you money.

This system works when it works. But it carries two structural problems that we think are worth naming.

The first is non-portability. Bank account numbers are owned by the bank, not the customer. When you close an account or switch institutions, that number does not follow you. Everyone who has your account details on file — employers running payroll, clients with payment terms, platforms processing recurring payments, family members with your details saved in their banking app — must update their records manually. The burden is, again, distributed outward.

In practice, most people who switch banks spend weeks, sometimes months, chasing down every payment relationship that needs to be updated. Direct debits break. Invoices go unpaid because they were sent to an account that no longer exists. The switching cost is not a fee you pay once — it is a time tax levied on every relationship that had your old details.

The second problem is exposure. A bank account number, shared widely as a payment identifier, carries meaningful security implications. It is not a credential in itself — you need more than a BSB and account number to drain someone’s account — but it is information that can be combined with other data for fraud, and most people have a reasonable aversion to broadcasting it casually. This is why, in practice, bank details feel more like something you share reluctantly than something you put on a business card or in an email signature.

The Layering Problem

Because neither email nor bank accounts solve the identifier problem cleanly, the industry has tried to layer solutions on top of them. Payment platform usernames. QR codes. Phone-number-based systems. Alias layers. Proxy databases. Each of these is an attempt to create stability and portability on top of an unstable, non-portable foundation.

Some of these solutions are genuinely useful. But they all share a common flaw: they are still controlled by a third party. The alias you have on a payment platform exists because the platform exists. If the platform shuts down, is acquired, changes its fee structure, or decides for any reason to suspend your account, your identifier goes with it.

You are not the owner. You are the user. And there is a very significant difference.

What Makes an Address Permanent

The word “permanent” gets used loosely in technology, so it is worth being precise about what we mean.

When we talk about a permanent address, we mean an identifier that exists independently of any single institution, cannot be unilaterally revoked by a third party, and does not expire by design. It is an address that you own outright — the same way you might own a piece of land — rather than one you lease on someone else’s terms.

This is not a trivial distinction. The entire value of a payment identifier is destroyed the moment it becomes unreliable. An address that might not work tomorrow is not really an address at all — it is a contingent pointer, and the contingencies matter.

Permanence, in the context we are describing, comes from the architecture. An onchain address is written to a distributed ledger that no single entity controls. It cannot be taken away by a company that goes bankrupt, a government that changes policy, or a service provider that decides you have violated their terms. It exists because it was written, not because a third party continues to permit its existence.

This is a genuinely different foundation from anything that has existed in payments before. Not better in every dimension — the existing system has many properties that blockchains cannot yet match — but categorically different in the specific dimension that matters most for a permanent identifier: the guarantee of continuity.

The Stability Problem in Practice

Let us make this concrete, because abstract arguments about infrastructure can drift away from the real human costs.

Imagine you are a small business owner — a sole trader, a consultant, a tradesperson, a creative professional. You have a hundred clients, and over the course of your career you might have two hundred or three hundred. Each of them has your payment details. Some of them pay you regularly. Some of them pay you occasionally, every year or two when they need work done. Some of them you have not heard from in years, but you hope to again.

Now imagine that your email address changes. Maybe you are moving away from a personal Gmail to a branded domain. Maybe your old provider shuts down. Maybe you simply want to start fresh. Whatever the reason, you now need to inform every single one of those clients. And for the ones you have not spoken to in two years, you may not even have a reliable way to reach them.

The same problem exists in reverse. You are a client, and the person you want to pay has changed their details. You have an old invoice with their bank account on it. Is it still current? You are not sure. You have to reach out to check. They respond — if they respond — and confirm their current details, or give you new ones. Now you have two sets of details on file, and every time you go to pay them, you have to think about which one is correct.

This friction is small in any single instance. But it scales. It compounds. Across an economy of millions of people and businesses constantly cycling through email addresses and bank accounts, the total cost of identifier drift is enormous — in time, in failed payments, in broken relationships, in deals that never closed because the logistics were too annoying.

A permanent address eliminates this category of problem entirely. Not reduces it. Eliminates it.

If someone has your address, they have your address. Not the address you had when you first met them. Not the address you had when you worked at a particular company. Your address, permanently, regardless of where you bank, what email provider you use, or what professional chapter you are in.

The Memory Layer of a Payment Network

There is another way to think about this that we find useful.

A payment network is only as good as its ability to find the right person. All of the routing, all of the clearing, all of the compliance infrastructure is predicated on the assumption that you have correctly identified who you are paying. The identifier is not just a convenience — it is the first and most fundamental input into the entire system.

An economy with stable, permanent, portable identifiers has lower friction at the base layer. Every subsequent step in a payment — the authentication, the routing, the settlement, the record-keeping — can be built on a foundation that does not need to be re-verified from scratch every time.

An economy built on unstable identifiers spends enormous energy compensating for identifier drift. Verification steps multiply. Confirmation emails proliferate. Lookup processes run in the background. None of this creates value. All of it is overhead generated by the fundamental instability of the identifiers underneath.

We are not suggesting that a permanent onchain address solves every layer of this problem. The payment rails, the compliance requirements, the trust relationships between institutions — those are separate and complex. But the identifier layer is the one we focus on, because we believe it has been underinvested and underappreciated, and because fixing it at the root is more elegant than piling more compensating mechanisms on top of a broken foundation.

Why Place Matters

There is a dimension to this argument that goes beyond pure functionality, and it is worth exploring.

When we designed addresses for Queensland — .queensland, .qld, .brisbane, .surfersparadise, .gold-coast, .brisbane2032 — we were not just building a naming system. We were building an identity layer. And place is a fundamental part of identity for most people.

For a long time, the digital world has been oddly placeless. The identifiers people use online — email addresses, platform handles, payment usernames — carry almost no geographic or cultural meaning. They are strings of characters, assigned by corporate registries, pointing to accounts in the cloud. There is nothing about a Gmail address that tells you anything meaningful about the person who holds it. There is nothing about an IBAN that tells you what community that person belongs to.

But people are not placeless. People live somewhere. They are proud of where they live. They have relationships — commercial, personal, civic — that are rooted in place. A Queenslander running a business is not just running a business; they are running it here, in this place, in this community, with all the trust and context that implies.

An address like yourname.brisbane or yourbusiness.queensland carries that information. It is not just a payment pointer — it is a statement of presence and belonging. When someone sends money to yourname.brisbane, they know something meaningful about who they are sending it to. The address does work that a string of digits or a generic email handle cannot do.

This matters more as the world becomes more digital, not less. As more of commerce happens online, as more relationships are conducted across screens, the signals that tell us who we are dealing with and where they come from become more valuable, not less. Place-based addresses are one of those signals.

The One-Time Cost Argument

We want to address something practical, because we believe it bears directly on the case for permanence.

Traditional payment identifiers carry two kinds of cost. There is the cost of acquiring them — usually free or very low, which is why people rarely think about it. And there is the ongoing cost of maintenance: the renewal fees, the subscription fees, the dependency costs when they break or change.

The insidious thing about ongoing costs is not just the money. It is the relationship they create. When your identifier requires annual renewal, you are in a perpetual negotiation with your provider. They can raise fees. They can change terms. They can add conditions. And the day you decide not to renew — or the day you miss a renewal — the address is gone. A payment identifier that vanishes when you forget to pay a bill is a payment identifier that cannot be relied upon.

A one-time cost to acquire a permanent address is a fundamentally different economic structure. It is not a subscription. It is not a lease. It is a purchase. You pay once, and the address is yours, unconditionally, without further negotiation, without annual reminders, without the background anxiety of wondering whether your payment infrastructure is going to survive the next billing cycle.

We think this model is not just commercially fair — we think it is actually more honest. The value of a permanent identifier does not depreciate with time. If anything, it appreciates, as more people learn and save your address. Charging for it once, rather than extracting an ongoing toll, aligns the cost structure with the reality of the value delivered.

What Transferability Adds

A permanent address that cannot be transferred is a permanent address that cannot adapt to the realities of human life.

Businesses change hands. People pass on what they have built. Families hold assets across generations. An identifier that is inextricably bound to a single person or entity for all time has a rigidity that creates its own problems.

Transferability — the ability to move an address from one owner to another — is what turns a permanent address into a genuine asset. Not just a utility, but something with value that can be recognised, traded, and inherited. This is not a novel concept. Physical property has been transferable for as long as property has existed, and the ability to transfer it is a large part of what makes it valuable.

An onchain address that is both permanent and transferable is, in a meaningful sense, a piece of digital real estate. It exists, it endures, it can be passed on. The combination of those properties is what makes it a serious long-term foundation for identity and payments — not just a clever technical trick, but an infrastructure primitive with real staying power.

Immutability and Trust

There is one more property worth isolating: immutability.

A payment identifier should not be secretly changeable. If someone can alter the destination that your address resolves to without your knowledge or consent, then your identifier is not a secure foundation — it is a target. Anyone who controls the resolution of your identifier controls, effectively, who gets paid when someone uses it.

Centralised systems require you to trust the custodian of your address not to change it, sell it, or redirect it. In most cases, that trust is honoured. But it is trust, not architecture. The custodian could, in principle, change the resolution. History is full of examples of platforms that changed their terms, companies that were acquired and reorganised, and services that degraded in ways their original users never anticipated.

Immutability — the property that an address, once set, cannot be altered by any party other than the owner — turns that trust relationship into a guarantee. You do not need to trust a company to maintain your address correctly. The architecture makes tampering structurally impossible.

This is the difference between security-by-policy and security-by-design. Policy can change. Design is harder to argue with.

The Accumulation of Identity Over Time

Here is something that only becomes visible over a long horizon.

An address that is permanent and stable accumulates trust. The longer it exists, the more relationships it has been part of, the more transactions it has been associated with, the more context it carries. In this sense, a permanent address is not just more convenient than a changing one — it is more valuable, in the specific sense that it has a history.

When you look up a business address and find that it has been at the same location for twenty years, that is a signal. Not proof of quality, but a signal of continuity and stability that carries weight. The same logic applies to digital addresses. An address that has existed without interruption, that has been part of a consistent pattern of transactions, that carries the accumulated weight of a real professional life — that address is worth more as an identifier than a fresh one with no history.

This is why permanence compounds. The value of a permanent address is not fixed at the moment of creation. It grows over time, as the address becomes embedded in more relationships, more systems, more records. The longer you hold a permanent address, the more damage it would cause to lose it — and the fact that it cannot be lost is precisely what makes it safe to invest in.

A young person starting their professional life who registers a permanent address today and keeps it for the next forty years will have, at the end of those forty years, an identifier with four decades of context attached to it. That is worth something real. Not just in a financial sense, but in the deeper sense of continuity that gives identity its meaning.

Against the Argument That This Already Exists

We sometimes hear the objection: “But platforms already solve this. PayPal has a permanent handle. Cash App has a $cashtag. These do not change.”

It is a fair point, and we want to engage with it honestly.

Platform handles are more stable than email addresses, and we think that represents genuine progress. But they are not permanent in the meaningful sense, because they exist only as long as the platform exists and only as long as the platform permits your continued use of it.

A platform can close. It can be acquired, restructured, or shut down by regulators. It can decide, for any reason and without appeal, to terminate your account. We have seen this happen — not rarely, but routinely — across the lifespan of the internet. Companies that seemed permanent proved not to be. Platforms that millions of people built their workflows around disappeared or changed beyond recognition.

We are not saying this will happen to any particular platform. We are saying that the risk exists, and that “this platform seems like it will be around for a while” is a different level of guarantee than “this address exists on infrastructure that no single entity controls.”

Platform handles are also, in most cases, non-transferable and non-composable. They exist within one ecosystem. They do not necessarily work as pointers in other systems. They do not carry meaning outside the platform. And they are almost entirely divorced from place — a $cashtag tells you nothing about where the person behind it is from, what community they belong to, or what context they operate in.

We think the right way to read these platforms is as evidence that the market understands the value of stable identifiers — and as evidence that the problem has not yet been fully solved.

The Physics of Coordination

Let us end on something that we think is underappreciated in discussions of payment infrastructure.

When identifiers change, coordination problems multiply. Not just for the two parties directly involved in a transaction, but across the entire network of relationships that radiates outward from each person.

Every time you change your payment details, you are not just asking one person to update their records. You are asking everyone who might ever want to pay you — now, or in the future, or for reasons neither of you can anticipate yet — to do additional work. And because you cannot always reach all of them, some of them will not update, and you will carry the cost of that incomplete update as friction in future transactions.

This is a coordination externality. The cost is distributed across the network in ways that are largely invisible to the person making the change. You feel the effort of notifying the people you remember to notify. You do not feel the cost paid by the client you forgot about, who spends twenty minutes trying to pay an old invoice and eventually gives up. You do not feel the cost paid by the accountant reconciling records that have drifted. You do not feel the cost paid by the developer who built a system that stored your old identifier and now has to handle the error state.

A permanent address internalises all of that coordination cost at the moment of acquisition. You pay for stability once, and the network benefits indefinitely. The person who registered a permanent address in the first year of their career will never impose that coordination cost on anyone. The address they gave out once will work for the rest of their professional life, in every system that ever stores it, without requiring a single update from a single person.

That is not a small thing. That is the elimination of an entire class of friction from the economy.

What We Believe

We believe that the quality of an economy’s payment infrastructure is shaped, at a fundamental level, by the quality of its identifier layer. And we believe that identifier layer has been neglected — not because it is unimportant, but because its failures are diffuse and invisible, distributed across millions of small friction events rather than concentrated in a single obvious failure point.

We believe that permanence is not a luxury feature for a payment identifier. It is the baseline requirement. An identifier that might not work tomorrow is not a payment identifier. It is a liability.

We believe that place-based identity has real value in a world that has become oddly placeless, and that building payment infrastructure around names that carry genuine geographic and cultural meaning is worth doing.

And we believe that the right time to build permanent infrastructure is not when the need is obvious to everyone — it is now, when the cost of establishing it is low and the compounding value of permanence has the longest runway ahead of it.

The problem we are solving is old. The solution is new. We think the argument for it is simple: if an address can disappear, it is not really an address. And if it is not really an address, it cannot do the job.

A permanent address can. That is why we built one.