Documentation
QNS in a nutshell
QNS gives a wallet a renewable .quai name. A name can carry a profile, a payment code, and an avatar — and with modules, it can resolve to a real website read straight from the chain.
Two layers
QNS is built in two parts. You can use the first without ever touching the second.
- The name registry (QNNS). Register a
.quainame, bind it to your wallet, and point it at an address, a Qi payment code, an avatar, and social profiles. The live registry uses one-year terms with a 30-day grace period. - The module loader. Optionally attach a module to your name so it resolves to a website, a redirect, or an app — rendered from on-chain data, not a hosting provider.
What is a module?
A module is the answer to “what should this name load?” Your name resolves to a tiny on-chain pointer called an anchor; the anchor points to a module contract; the module tells a wallet or gateway how to render the page. The bytes live on Quai, so the site has no server to go down.
Where to go next
How modules work →Anchors, manifests, the loader, and the topologies a name can resolve to.
Deploy a module →Publish a fully on-chain static site and bind it to your name from the CLI.
Module inspector →Paste a name or address and see exactly what it loads on-chain.