There is a version of this article that talked about claiming your Queensland address. That article was wrong. Not wrong in its facts — wrong in its frame. Names are not a product to distribute. They are infrastructure. And infrastructure, especially at the scale of a State’s identity, does not belong to whoever happened to mint it first. It belongs to the place.
So let’s start over, properly.
What a Namespace Actually Is
A namespace is not a domain name. It is not a URL, a brand asset, or a handle. A namespace is the structured territory within which names — all names — resolve to something real.
When you say queensland.gov.au, you are not just visiting a website. You are traversing a hierarchy of namespaces: .au delegated to .gov.au, which is delegated to queensland, which resolves to a particular address on a particular server. Every step in that chain is an act of trust. Every step in that chain is also a potential point of failure, expiry, or revocation.
We have built entire digital ecosystems without a native concept of who anyone is. We have long, random strings that accumulate data through activity, but say nothing about who they belong to. These accumulated fragments, when assembled, can structure an identity — but currently, it is opaque, hard to navigate, and nearly impossible to build trust on top of without introducing some core identity primitives.
A namespace is that primitive. It is the ground everything else stands on. Identity stands on it. Payments stand on it — because a name that resolves to a wallet address is how value moves without error. Mail stands on it. Credentials stand on it. Trust stands on it. Pull the namespace and everything built on top of it loses its address. Not just its website. Its address.
This is why a namespace is infrastructure — in exactly the same sense that roads and water mains are infrastructure. You don’t notice it until it fails. And when it fails, nothing above it works.
The Problem with Renting Your Foundation
Traditional domain names — the system almost every government in the world uses — are leased, not owned. You pay a registrar. The registrar pays a registry. The registry operates under a contract with ICANN. And ICANN sits inside a very specific jurisdictional and political context.
The DNS system that routes every web request on the planet is controlled by a single nonprofit in Los Angeles. ICANN, the Internet Corporation for Assigned Names and Numbers, operates under a contract with the United States Department of Commerce. Every domain name, every TLD, every resolution chain ultimately traces back to thirteen root server clusters managed by organisations predominantly based in NATO countries.
That is not sovereignty. That is tenancy at the pleasure of another jurisdiction’s administrative apparatus.
The practical risks of tenancy are not theoretical. The overlooked risk of expiry is not simply about inconvenience. It is about handing over the keys to your digital identity. Entities that fail to protect their domains leave themselves open to attackers eager to exploit trust, recognition, and residual traffic.
In 2014, the Canadian government faced a breach when an old domain, formerly used for governmental email accounts, was allowed to expire. Attackers acquired the domain, intercepting emails that contained sensitive government information, and the breach had to be addressed at a high level to mitigate further privacy risks.
That is not an edge case. That is the architecture. When a name exists only because a registrar has been paid and a contract remains active, the name has a lease, not a title. And a lease can always be terminated — by expiry, by politics, by a jurisdiction asserting authority over the registrar. The risk of revocation is not limited to abuse of power or political disputes. Revocation authority exists for security purposes too — but “security purposes” is defined by whoever holds the revocation key, not by the entity whose identity depends on the name.
A State should not build its digital identity layer on leased land.
What Onchain Ownership Actually Means
Owning a namespace onchain is structurally different in ways that matter:
Permanence. An onchain name is 100% yours. No intermediaries, no bureaucracy. It is your property — uncensored and irrevocable. There is no renewal invoice. There is no registrar to call. There is no grace period before a domain enters the open market. The name resolves because the chain resolves it, and the chain does not care who is in power in Los Angeles.
Resolution. An onchain naming system is not merely a blockchain-based domain registrar. It is a programmable identity layer that maps human-readable names to cryptographic addresses, content hashes, metadata records, and arbitrary key-value pairs. A Queensland namespace minted onchain can resolve to a wallet, a contract, a credential, a DID document, a content hash. It is not a pointer to a website. It is a root-level record that can carry the full weight of institutional identity.
Extensibility without permission. If a project wants to create its own naming system with custom rules, roles, and issuance logic, ENS supports that through subnames. A team can define its own governance, pricing, and eligibility criteria while still anchoring itself to the global ENS namespace. This preserves coherence while allowing for experimentation. A State that controls its own namespace can issue names downward — to agencies, to services, to citizens — on its own terms, under its own governance, without asking permission from any external registry.
Sovereignty. A digital identity infrastructure is a matter of State sovereignty when it is used to access public services and essential services, and to identify and authenticate citizens with official government-issued identity credentials. Onchain infrastructure does not subordinate that sovereignty to a foreign contractual arrangement. The namespace is held by a key, not by a registrar relationship.
The difference between renting and owning, at this layer, is the difference between a digital State that is always one missed payment or one political decision away from losing its name — and a digital State that owns its name the way it owns its territory.
Why This Is the ANCHOR Step
In the kooky framework, SECURE → BUILD → ANCHOR is the sequence that matters.
You secure the foundations: wallets, keys, operational security — the primitives no higher-order work can survive without.
You build: services, integrations, the things that demonstrate what the infrastructure can actually do.
Then you anchor. You set the name layer — the permanent, resolvable, ungovernable-from-outside identifier that everything else will hang off. You do this after secure and build because a namespace is only worth anchoring if there is something real to anchor. A name with nothing behind it is branding. A name with a secured operational stack behind it, with built services resolving through it, with institutional identity encoded into it — that is infrastructure.
The Queensland namespace mint is the ANCHOR step. It is not a product launch. It is not a land grab. It is the act of setting a permanent address for an entire State’s digital existence, before that State has built the apparatus to set it itself.
This matters because infrastructure does not wait. The address either gets set by someone who understands what they are doing and has the long-term interest of the place in mind — or it gets set by whoever gets there first with the wrong intentions. Minting the Queensland namespaces onchain, permanently, with the explicit intention of handing them to the State, is the act of holding a foundation while the building catches up.
Why Queensland Specifically
Queensland is not a random choice. kooky is a Queensland-built project. The people building it know this place — its geography, the way regional Queensland functions differently from Brisbane, the particular texture of how trust and community operate here. You don’t build sovereign infrastructure for a place you have no relationship with. That is not infrastructure. That is speculation.
There is also a concrete temporal anchor: Brisbane 2032. The Olympic and Paralympic Games Brisbane 2032 marks a transformative moment for Queensland, Australia, and the global Olympic and Paralympic movements. As the first Games to be awarded under the International Olympic Committee’s new approach to sustainable and legacy-focused hosting, Brisbane 2032 is more than a sporting event — it is a catalyst for economic, social, and environmental progress across the region.
The vision for Brisbane 2032 is to create inclusive spaces that will drive growth and diversity, ensuring that the Games’ legacy lives on for future generations. The delivery of the Games is a collaborative effort involving multiple tiers of government and independent bodies.
2032 is the horizon. It is the fixed point in the future against which every piece of Queensland infrastructure — physical and digital — is being measured right now. Strategic legacy initiatives are aimed at ensuring the Brisbane 2032 Olympic and Paralympic Games deliver long-term, state-wide benefits across infrastructure, community, economy and environment. A permanent digital namespace for Queensland, set now, resolving now, handed to the State now — that is legacy infrastructure in the same category as a rail line or a stadium. It does not expire in 2033. It is there before the Games and long after them.
That is what “permanent” means. Not “for a while.” Permanent.
What “Handed to the State” Actually Means
This needs to be said plainly, because it is the part most likely to be misread.
kooky minted these namespaces. kooky holds the keys right now. That is a temporary condition, not a permanent one. The intention from day one has been to transfer ownership of the core Queensland namespaces to the Queensland Government — or to whatever institutional body the Queensland Government designates as the appropriate custodian of the State’s digital naming layer.
This is not charity. It is the correct architecture. An independent builder can do things a government cannot: move fast, make irreversible decisions without committee approval, absorb the risk of being early. For government adoption of new technology, there is a critical need for technical expertise, as most public sector organisations lack the in-house knowledge required for blockchain development and maintenance. Often, this means governments need to bring in third-party experts to onboard this technology. An independent builder who has already done the work, already set the namespace, already demonstrated that it resolves — and who then offers the infrastructure to the State rather than extracting value from it — is not a vendor. They are a rail-layer.
Blockchain technology has increasingly drawn the attention of governments seeking to modernize public services through transparent, secure, and efficient digital infrastructures. Drawing on case studies from diverse regions, blockchain’s capacity to establish tamper-evident records, automate verification, and reduce administrative overhead is well-documented. The pattern of independent parties building infrastructure that governments later adopt is well-established. The internet itself followed this sequence. Open protocols, built by researchers and engineers without government mandate, became the substrate that every government’s digital presence now depends on.
The Queensland namespace mint follows that same logic. Build the layer. Make it permanent. Make it resolvable. Make it transferable to the rightful long-term owner. Then hand it over.
There is no revenue model here. There is no subscription. There is no “claim your address” mechanic for citizens. That framing was the mistake of the earlier article, and it is worth being direct about why it was a mistake: it turned a piece of public infrastructure into a retail product. A road is not a retail product. A root nameserver is not a retail product. A State’s permanent digital address is not a retail product.
This is infrastructure. The person who poured the concrete does not own the road.
The Base Layer Everything Else Hangs Off
With integrations into wallets, browsers, social platforms, and DAO tooling, onchain naming is emerging as the identity layer of the next digital era, replacing fragmented logins and usernames with user-owned identities. When you extend that logic to a State — not a user, but an institution with sovereignty, a population, a legal system, and a 2032 Olympic Games arriving in six years — the stakes of getting the naming layer right are proportionally larger.
In our modern societies, citizens do not own their identities. The majority of current digital identities are maintained by Big Tech, which results in potential privacy issues as the digital presence of citizens can be monitored. Furthermore, these digital identities can be revoked at the platform owner’s discretion leading to loss of access to a plethora of other dependent connected services.
A State that routes its digital identity through someone else’s namespace is in exactly that position — dependent on a platform owner, subject to that owner’s terms, vulnerable to that owner’s decisions. The Self-Sovereign Identity concept overcomes these digital and societal issues by relying directly on infrastructure that is not owned by any intermediary. The SSI movement aims to create a standardised identity layer for the Internet, generating digital trust through verifiable identities and putting citizens at the centre of their data.
That is the aspiration. And it starts with a name.
Queensland has one now. It is permanent. It resolves. It has no registrar. It is waiting for the State to pick it up.
kooky is an independent builder working on permanent onchain infrastructure for Queensland. The Queensland namespaces were minted as public infrastructure, not as a commercial product, and are intended for transfer to the Queensland Government or its designated custodian. No claim is made on behalf of the Queensland Government. No endorsement is implied.