The namespace is currently held by a single independent operator. That is a starting point, not the intended end state — the infrastructure is built to pass to the State.
This namespace was built by an independent operator working in onchain naming — not by a committee, and not as a speculative land-grab. The Queensland names were secured deliberately, out of a view that a State this significant should hold its own naming layer rather than lease it.
Building it took real work: minting the namespaces, wiring resolution, integrating payment, and proving each part works. Handing it over takes far less. Because everything is onchain, transfer is a defined technical act, not a negotiation over assets held in trust.
The operator's role is to build the infrastructure and to deliver it — on the ground, with the State, on the State's terms.
The namespace sits inside a working practice in onchain naming and payments — the same practice that built the integrations listed in the log.
Active in onchain naming. The Queensland namespace is part of a broader portfolio of onchain names, held and operated through established naming infrastructure.
Live integrations, not slideware. Payment routing, MCP interfaces and wallet-level resolution are shipped and dated — evidence of a working operation, not an intention.
Ready to be on the ground. Delivering this for Queensland means being in Queensland to deliver it — the operator is prepared to do exactly that.
The State is never dependent on the operator to keep the namespace resolving. Once transferred, it stands on its own.
The namespace is offered for assignment or transfer without strings — no licensing scheme, no recurring fee attached to holding it.
Handover and deployment are done with the State directly, on site — not managed remotely from another country.
Every step — what exists, when it was built, how it transfers — is documented and verifiable onchain.
The infrastructure is ready and the operator is ready. The next step is a conversation.
Open a conversation