QNS Publish
Long-form posts and comments with the current canonical version stored in contract state.
Ecosystem
QNS starts with names, then grows into modules, wallet-native websites, publishing, and reusable app surfaces.
Builder surface
Every project here uses the same idea: a name points at verified on-chain data that a wallet or gateway can render.
Available now
Register a renewable .quai name for your wallet, profile, avatar, and payment code.
Publish HTML, CSS, markdown, and text into contract state, then load it from a .quai name.
Read exactly what a QNS name or module address loads, including anchors, manifests, and file hashes.
Native wallet resolution for .quai hosts and qns:// links, with hash-verified static rendering.
Coming next
Long-form posts and comments with the current canonical version stored in contract state.
Reusable on-chain components that let sites share visual building blocks without republishing every byte.
Stateful contracts that expose typed route data for richer wallet-rendered apps.
Bridges that mirror QNS posts, profiles, and updates into external social protocols without making them canonical.
Start with a module, publish the bytes on-chain, then anchor it to a name you control.