QNS is Quantova's post-quantum name service — human-readable .qtov names (like
jason.qtov) that resolve to Quantova accounts and records, registered and owned
through post-quantum-signed transactions on the Quantova Virtual Machine (QVM).
You buy a name at Qname.io by connecting your QMask wallet and paying in QTOV, the native asset of Quantova. This repository explains how QNS works, why it is quantum-secure, and how it ties into the Quantova address scheme — and includes a runnable demo that proves how a purchase is post-quantum signed and verified.
A name service is only as trustworthy as the signatures that authorize its registrations and updates. On classical name services, the keys that own a name are elliptic-curve keys — the same keys a quantum computer can eventually forge. If the signing layer falls, names can be silently transferred or repointed.
QNS is post-quantum at the authorization layer. Registering a name, transferring
it, or changing its records is a transaction signed with a NIST post-quantum
scheme (CRYSTALS-Dilithium, Falcon, or SPHINCS+) and verified by the Quantova
runtime's QSignature type. There is no elliptic-curve path to take ownership of a
.qtov name — so a name registered today cannot be forged out from under its owner
by a future quantum adversary. See
docs/post-quantum-security.md.
Names are organized under the branded root TLD qtov. A name like jason.qtov
is reduced to a 32-byte node with the EIP-137 namehash over keccak-256 — the
QVM's standard hashing — which is the key under which the registry stores the
domain's owner, resolver, and records. Sub-domains are registered with a
commit-reveal flow (so a pending name cannot be front-run), priced by label
length and term in QTOV, and owned by a Quantova account whose address is
derived from a post-quantum public key. Resolution maps a name to an address;
reverse resolution maps an address back to its primary name.
- Install QMask (Chrome / Firefox / Brave) and create a quantum-resistant
Quantova account — your address begins with
Q. See docs/buying-a-domain.md. - Go to Qname.io and connect your QMask wallet.
- Search for the name you want (e.g.
jason.qtov) and check availability and price. - Purchase in QTOV — you need QTOV (the native Quantova asset) to register a name. QMask asks you to post-quantum-sign the registration; approve it.
- The name is registered to your Quantova address and resolvable on-chain.
QTOV is required for every purchase — registration is a native Quantova transaction, paid in QTOV and signed by your post-quantum key.
| Document | What it covers |
|---|---|
| docs/architecture.md | The QNS structure on the QVM: roots, domains, records, namehash, commit-reveal, resolution |
| docs/post-quantum-security.md | Why QNS is quantum-secure and how it preserves that security through the QVM tech stack |
| docs/address-scheme.md | How .qtov names connect to the Quantova address scheme (the Q address and namehash) |
| docs/buying-a-domain.md | Step-by-step purchase on Qname.io with QMask and QTOV |
| demo/README.md | The runnable purchase demo and security back-test |
The demo folder contains two runnable, dependency-free programs:
cd demo
python purchase_demo.py # full .qtov purchase: namehash, PQ-sign, verify
python back_test.py # 12 security-property checks (incl. tamper detection)purchase_demo.py derives a Q address from a post-quantum key, namehashes the
domain, builds the QTOV-priced purchase, post-quantum-signs it, and verifies both
the signature and that the signer matches the owning address. back_test.py proves
the guarantees — including that a tampered owner, price, or label, or a wrong key,
all fail verification. The namehash is cross-checked against the published EIP-137
vector, so it is provably the real algorithm. See demo/README.md.
Licensed under the Business Source License 1.1 (BUSL-1.1), © 2026 Quantova Inc. See LICENSE and LICENSE-OVERVIEW.md.