Four scenarios where a sovereign onchain namespace changes how a public function works — the problem as it stands today, and what the namespace does about it.
Today: Paying a public body means copying a BSB and account number, trusting an intermediary to settle, and hoping the details on the invoice are genuine. Mistyped and fraudulent account details are a persistent, costly problem.
A public entity receives value at a named onchain endpoint. There is no account number to mistype and no intermediary settling the transfer — the name resolves to the destination directly, and the payment is final and verifiable.
Today: Anyone can register a look-alike domain and impersonate a department for phishing or fraud. Citizens are told to "check the URL" — but there is nothing structural stopping the fake from existing.
A name under a sovereign namespace can only be issued by the holder of that namespace. A citizen who sees a .queensland address knows, by construction, that it was assigned by the State — not by whoever registered a similar string first.
Today: Large programs improvise their naming as they grow — a patchwork of domains, subdomains and social handles, each a separate thing to secure and a separate opening for impersonation. Brisbane 2032 will be exactly this kind of program.
A single reserved namespace gives the whole program one coherent root from day one. Every part of the program issues beneath it — recognisable, verifiable, and impossible to counterfeit at the namespace level.
Today: A State's official domains are leased through registrars operating under another jurisdiction's rules. In principle, a name can be suspended, disputed or lost to a policy decision made entirely outside Queensland.
An onchain namespace is held outright, not leased. There is no registrar to suspend it and no external authority to answer to. Once the State holds it, the State keeps it — the resolution rules are fixed and cannot be changed against the holder.
The whole register — every namespace above — held by wallets the State controls, resolving with no party in the middle.
Each scenario runs on infrastructure that already resolves. See how the namespace can be placed in the service of the State.
For the State