Curvy Protocol hits mainnet - multichain private transactions

Curvy Protocol is a privacy infrastructure project that just went on mainnet. If you haven't come across it, here's how it works:

Every user gets an ENS username. When someone sends you a payment, the protocol derives a fresh one-time receiving address using your stealth meta-keys. The sender just types your username. They don't run anything, generate proofs, or know how the privacy layer works. You scan for incoming payments with a viewing key. Spends use ZK proofs so you can move funds out without revealing which stealth address you're spending from.

What this gets you is basically no balance aggregation, no time correlation, it's multichain, so the privacy doesn't break the moment you move across networks.

And the sender experience is identical to a normal transfer. I mean, stealth addresses have been a known primitive for a long time (Vitalik's writeup, Umbra, the EIP work, etc) but adoption stayed low because the sender flow was messed up and you had to do some crazy stuff to do it. This thing is much better, like a normal transaction.

Check curvy.box if you want to look at the docs.

Links:

Web3PrivacyNow page - https://explorer.web3privacy.info/project/curvy-protocol

GitHub - https://github.com/0xCurvy

Audit - https://github.com/0xCurvy/contracts/blob/develop/audits/Curvy%202026%20Audit%20Report%20Final.pdf

Press - https://www.prleap.com/pr/311820/curvy-protocol-completes-security-audit-and-exits-beta-bringing-production-ready-privacy-infrastructure-to-on-chain-payments