> For the complete documentation index, see [llms.txt](https://parad0xlabs.gitbook.io/parad0xlabs-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://parad0xlabs.gitbook.io/parad0xlabs-docs/web0-how-it-all-connects/why-web0-wins.md). # Why Web0 Wins The agent economy needs four things working **at the same time**: verifiable **proofs**, a **payment rail**, **privacy**, and **agent identity**. Plenty of teams ship one or two of these. Web0 ships all four — with **8+ programs live on Solana mainnet-beta** and the privacy core ZK-verified end-to-end, no servers in the loop. This page is the receipts. *** ## 1. The whole row, not one box The agent economy needs four things at once — verifiable **proofs**, a **payment rail**, **privacy**, and **agent identity**. Look at where the checkmarks land across the field: | Approach | ZK proofs | x402 payments | Privacy | Agents / Passport | | -------------------------- | :-------: | :-----------: | :-----: | :---------------: | | ZK-proof toolkits | ✅ | ❌ | ✅ | ❌ | | x402 payment platforms | ❌ | ✅ | ❌ | ⚠️ | | FHE / confidential-compute | ❌ | ⚠️ | ✅ | ⚠️ | | **Web0 / DNA x402** | **✅** | **✅** | **✅** | **✅** | Plenty of teams ship one or two of these. Categories, not call-outs — the point isn't any single project, it's the **shape** of the field. The point isn't that any single box is hard. It's that **the combination is the moat**: * A **ZK toolkit with no payment rail** can prove things — but it can't bill an agent. * A **payment rail with no privacy** is a permanent public ledger of everything your agent has ever done. * **Privacy with no identity** has no one to attach a reputation to. We have not found another stack shipping the **full row** — and it's verifying on-chain, not sitting on a slide. *** ## 2. Same rail as Coinbase — the opposite default Coinbase's x402 made machine-to-machine payments real, and it's a genuinely good open standard. We **use** it. But x402 on its own is **public by default**: who paid whom, how much, and when — recorded forever. For an AI agent making thousands of calls a day, that's a permanent surveillance trail with great UX. | | Coinbase x402 | Web0 (Dark NULL) | | ----------------- | ----------------- | ------------------------------ | | Standard | x402 | x402 — **same standard** | | Agent payments | ✅ | ✅ | | Who-paid-whom | public, permanent | **hidden** | | Balance / history | public | **hidden, provable on demand** | | Reputation | — | **private track-record proof** | **They make the public ledger the default. We make privacy the floor.** Dark NULL lets an agent pay, prove it's good for it, and reveal *nothing else*. *** ## 3. `.null` vs the domain incumbents A `.null` name isn't just a label. It's a **payable, private, anonymously-owned identity**. | | ENS | Unstoppable | Web0 `.null` | | --------------------------- | ------------------------------ | ---------------- | ----------------------------------------------------------------------------------- | | Resolution | on-chain | centralized API | on-chain (direct PDA read) | | Content hosting | IPFS (you must keep it pinned) | their infra | **Arweave — permanent, paid once** | | Built-in payment endpoint | ❌ | ❌ | **✅ x402** | | Agent identity / reputation | ❌ | ❌ | **✅ private track-record proof** | | Owner ↔ wallet link | public | public | **none — ownership is a ZK commitment** | | Resale | open public bids | open public bids | **open-ascending (English) — anti-snipe, instant on-chain refunds, fee capped ≤5%** | **The name is public; the owner is not.** Registering, resolving, transferring, and selling a `.null` name — plus recipient-private pay-by-name — are **live on mainnet** today (`null_registrar` `NXgQhepFpDCu935H1D4g34g59ZYbo1jR4tBCZWhV8Np`). On top of that, `dark_registrar` adds **no on-chain link between your wallet and the name**: ownership is a **cryptographic commitment**, not a public key; every action is authorized by a **zero-knowledge proof**, and a **permissionless relayer** submits it, so your wallet never signs. ENS and Unstoppable both pin the name to a public address forever — open any explorer and you can see who holds what. `.null` breaks that link — wallet-unlinkable ownership is ZK-verified end-to-end on devnet, coming to mainnet next. When you resell a `.null` name it runs as an open-ascending (English) auction: bids rise in the open, **every outbid is refunded on-chain instantly**, and an **anti-snipe** window extends the clock so nobody steals it in the final second. The protocol's cut is **capped at 5% in the program** — it can be lowered freely but never raised past that, and any raise is **timelocked 48 h on-chain**. The auction and resale marketplace are **live on mainnet** (`null-auction` `39Ayjpnucq51k94uKorzX5sRRxv2F79zpVRZdMnWgbWG`). The privacy in Web0 isn't in the *bidding* — it's in the ownership, payment, and identity layers (Dark NULL): you hold the name, pay, and prove your reputation without exposing your wallet's history. *** ## 4. The part nobody can fake: it's LIVE Anyone can draw a comparison table. Here's what you **can't** fake — the privacy core is **ZK-verified end-to-end on devnet** (coming to mainnet next), on-chain, serverless, with provers running client-side: | Program | What it does | | ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | | `shielded_pool` | ZK-private payments — deposit, then withdraw with sender, recipient, and amount hidden; the deposit↔withdrawal link is cryptographically broken | | `dark_x402_access_gate` | Private pay-per-call access — prove a balance clears a tier threshold without revealing the wallet or the balance | | `dark_nullifier_record` | Single-use nullifier — stops replay | | `dark_reputation_gate` | GhostScore — prove a track record (enough receipts, enough settled volume in a window), reveal nothing; serverless | | `dark_registrar` | Anonymous `.null` ownership — register, manage, transfer with no wallet↔name link | | `receipt_commitment_tree` | Merkle root of private receipts | **Every prover runs client-side, and there are no servers** — GhostScore receipts are minted by real on-chain payments, with no privileged writer. The `.null` naming rail ships separately and is already further along: **`null-auction` (`39Ayjpnucq51k94uKorzX5sRRxv2F79zpVRZdMnWgbWG`) and `null_registrar` (`NXgQhepFpDCu935H1D4g34g59ZYbo1jR4tBCZWhV8Np`) are live on mainnet** — English `.null` auctions, the resale marketplace, and registration/transfer/pay-by-name (ids in [docs/PROGRAMS.md](/parad0xlabs-docs/technical-reference/programs.md)). **And web0.null itself now resolves to a permanent site on Arweave — the stack hosting its own front door, owned by a wallet, with no server in the path.** **The `.null` name directory on web0.null now serves keyless: an off-browser indexer publishes a snapshot to Arweave and your browser reads it straight from there — no API key in the bundle, no proxy, no backend.** The Dark NULL privacy programs above are live on devnet — mainnet rolling out. **And the cherry:** a *real* private track-record proof, verified on-chain. In the same end-to-end run, **replay, forged, and tampered proofs were all rejected**. That's not a promise on a roadmap — it's a transaction flow you can run yourself on devnet. The shielded pool uses a **Groth16 zk-SNARK over BN254**, verified on-chain, with a **permissionless relayer**: you deposit, then later withdraw to a fresh destination, and the cryptographic link between the two is broken. Same Groth16/BN254 machinery underpins the access gate, GhostScore, and anonymous ownership. *** ## 5. Why the right people trust us The privacy crowd has a BS detector, so we let the chain do the talking: * **The proof is the on-chain link, not an adjective.** Every capability on this page is a transaction flow you can run yourself — naming, auctions, resale, and pay-by-name on mainnet; the privacy core on devnet. * **Serverless by design.** There are no servers in the loop — provers run client-side, and GhostScore receipts are minted by real on-chain payments, with no privileged writer who could fake a track record. * **The math is the gate.** Groth16 over BN254, on-chain verification, a single-use nullifier per claim, and a permissionless relayer so your wallet never has to sign. That restraint *is* the pitch. The proof is the on-chain link. **The `.null` registrar, auctions, and resale marketplace are live on mainnet (**[**docs/PROGRAMS.md**](/parad0xlabs-docs/technical-reference/programs.md)**). The Dark NULL privacy layer is live on devnet — mainnet rolling out.** *** **TL;DR** — Everyone else has a piece. We shipped the whole stack: ZK proofs **+** an x402 payment rail **+** privacy **+** anonymous identity (names included), on-chain and serverless, all verifiable. That combination is the moat, and you can't fake it overnight. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://parad0xlabs.gitbook.io/parad0xlabs-docs/web0-how-it-all-connects/why-web0-wins.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.