Stealth Pay

Stealth Pay is live on mainnet. Private payments on-chain. No relayer. No trusted party. Just math. 🧵

the spending key never leaves the client your app doesn't see it the backend doesn't see it the chain doesn't see it it generates a proof and nothing else

Day 21 of #BuildOn0G proof time is under 2 seconds. circuit compilation is cached between runs. witness generation is parallelized where the circuit allows. fast enough to feel like a normal transaction. try-stealth-pay.vercel.app

we built proof generation, Merkle tree mirroring, and nullifier tracking into the SDK so that you don't have to

the blockchain is a permanent, globally indexed, publicly searchable record of every financial transaction you've made on it this was never announced as a privacy tradeoff it was just the default

Day 20 of #BuildOn0G the SDK now handles multi-note aggregation. received multiple small payments? the SDK selects and combines them automatically. up to two input notes per spend — matching the circuit's 2-in/2-out model. try-stealth-pay.vercel.app

three SDK calls shield(), privateSend(), unshield() the ZK proving, tree sync, and nullifier tracking are handled you write the product

every airdrop snapshot that checks your on-chain history is also building a permanent record of your financial behavior

Day 19 of #BuildOn0G use case docs are live. private payroll. confidential B2B settlements. DAO treasury distribution. subscription billing. all four use the same three SDK calls. the protocol does not care what gets built on top of it. try-stealth-pay.vercel.app

@0g_CN This is what we've been building towards. Privacy baked into the protocol, not bolted on. Grateful for the support, let's make on-chain privacy the default, not the exception.

隐私不该是一种设置，而是协议底层最坚实的承诺。 欢迎 @stealth_pay 联合 0G 填补链上隐私支付的关键拼图。目前 0G 主网上 USDC 交互流程已全线跑通——无需中继器，不设第三方信任，纯靠零知识证明（ZK）保护你的每一笔资产往来。 链上隐私交互的时代已经开启，详情点击👇

privacy by policy: a person can override it privacy by math: no one can one of these is a guarantee

the Merkle root is public it commits to every valid note in the tree your proof shows your note is in the tree without revealing which leaf without revealing any note details public root, private everything else

Day 18 of #BuildOn0G testnet stress test complete. 10 wallets. shield, privateSend, unshield across all of them. no double-spend bypasses. nullifier registry holds. local and on-chain Merkle roots match every time. try-stealth-pay.vercel.app

the immutable verifier cannot be updated this is a feature your proof valid today is valid permanently

the nullifier: - one hash - proves the note was spent - reveals nothing about the note double-spend protection with zero information leakage

on-chain in 2026: - transparent: yes - decentralized: yes - censorship-resistant: yes - private: no we addressed the last one

the verifier contract has one job verify(proof, publicInputs) no state, no owner, no upgrade path it has been doing its job since deployment and will continue indefinitely

your spending key generates a proof then it goes back in your pocket it never touches the chain the chain has no idea it exists

Day 17 of #BuildOn0G MetaMask integration is live in the playground. wallet mode: MetaMask signs and submits. backend generates the proof. private key mode: paste a key, everything runs end to end. two ways to try it. same on-chain result. try-stealth-pay.vercel.app

we wrote a circuit that proves five things simultaneously and reveals none of them cryptography is genuinely unreasonable in the best way

the blockchain sees: one commitment hash the blockchain knows: nothing that's the design