Brisbane 2032 is the most significant program Queensland will run this decade. Its onchain naming layer already exists — minted, reserved, and waiting for the entities that will carry it.
The Games are not one entity — they are hundreds. Venues, programs, transport, ticketing, volunteers, partners. Each needs an address citizens can trust.
Scattered naming is a liability. Look-alike domains, spoofed ticketing sites and impersonation are a known risk around every major Games. A single sovereign namespace closes that gap by construction.
It only works if it exists early. A naming layer is worth most when it is in place before the program scales — not improvised once it already has.
Every part of the Games issues beneath a single recognised namespace.
A name under the namespace can only be issued by its holder — impersonation is blocked at the root.
In place well before the horizon it serves. Nothing to invent later, only to assign.
Each name issues beneath .brisbane2032 — identity, payment and mail under one root.
Each namespace covers a different scale of the State.
The same three models — assignment, co-administration, transfer — apply to this namespace as to every other.
For the State