Sovereign

Websites that live on the network. Nobody can take them down.

Sovereign is the browser built into the MoneroUSD wallet. Sites are published to the network's own nodes, owned by a key in your wallet, and checked byte by byte against the chain before they're shown.

Site records & verified serving built · .mud names, sharded hosting & private reads in design

Browse

Type a name like kai.mud and the site opens. Nobody — not your internet provider, not the node that serves it — learns which site you opened.

Publish

Pick a template or drop a folder, choose a name, see the price in dollars, tap Publish. No server, registrar, hosting account, DNS or certificate.

Own

The site belongs to the key in your wallet. Only you can change it, and nobody can roll it back or seize it.

How a name resolves

Two lookups, both answered from the chain.

A site name is your @username, so flame.mud is @flame's site and your payment handle and site share one name. Resolving it takes two steps: the name gives the owner's key; the owner's key gives the latest site root published on chain. Every node can answer both from its own state, so resolving a name asks nobody anything.

Look-alike names are refused by consensus, and the browser shows the verified owner beside the address.

Hosting

Sharded so nodes stay small.

A site is cut into 256 KB chunks, each addressed by its hash. Each chunk is held by the four nodes nearest its hash, so per-node storage falls as nodes join. Every epoch, holders answer a random-chunk challenge drawn from the block hash; only holders that answer are paid. A node that serves a wrong byte is caught and the browser asks the next holder.

Popular sites are cached by whoever fetched them, like any web cache — caching never changes the root.

What you payProposed priceKept
Storage$0.50 per MB, once (a 2 MB site ≈ $1)Forever — nothing to renew
An updateOnly the new chunksForever
A .mud nameAbout $10 a year ($5 in a site's first year)While renewed
BrowsingFreeHistory on your device only

Proposed prices from the design; final prices are set before launch and are always shown in dollars before you publish.

Safety

Private by construction.

  • No phoning home. Sites run in a sandbox whose only network is the Veil — no clearnet requests and no WebRTC, so a site can't leak a visitor's IP.
  • Private reads. Pages are fetched with private information retrieval, so the serving node doesn't learn which page you read. Visit counts exist only on the owner's own node.
  • Post-quantum. ML-DSA site records, ML-KEM links, hash-addressed chunks.

The trade-off, stated.

A published site can't be removed from the network — only replaced by a newer version — which also means nobody can take content down globally. Each node may refuse to serve a chunk on a local, opt-in list. That is a local choice, not global censorship, and the publish screen warns you plainly before anything goes live.

What exists today

The wallet already has a Sovereign browser tab, signed site records with versioned roots, and a server on your own node that checks every file against its on-chain root before serving it. Next: .mud name resolution, chunked and sharded hosting with storage proofs, private reads, and redesigned Browse, Publish, My Sites and Hosting screens.