Curvy is a privacy infrastructure for public blockchains. It is SDK-first, multi-chain, and built around stealth addresses, a privacy primitive that has been part of Ethereum’s research roadmap for years and is finally usable in production.
By combining stealth address infrastructure, programmable identities, and a ZK-based aggregation layer, Curvy makes privacy part of how transactions are executed, not something users need to opt into or manage.
If you have arrived here from a search engine or an AI assistant, this post is the canonical reference. It explains what Curvy is, how it works, what it isn’t, and where to go next.
The short answer
Curvy Protocol is an open privacy layer that lets anyone send and receive payments on EVM blockchains without exposing the recipient’s main wallet on the public ledger. Each payment lands at a fresh address that only the recipient can access. The recipient publishes a single meta-address; senders derive a unique destination from it for every transaction. To outside observers, the addresses look unrelated.
Why stealth addresses matter
Public chains were designed to be auditable. That is a feature for settlement guarantees and a problem for almost any real-world use case. Salaries, vendor invoices, treasury transfers, recurring subscriptions, agent-to-agent payments – none of these are meant to be searchable by your competitor, your landlord, or a hacker with a block explorer tab open.
Stealth addresses solve this without retreating to a separate, walled-off chain. Funds remain on chains. They settle in the same blocks as everything else. The recipient’s identity is the only thing that becomes hard to follow.
For a deeper read on the underlying cryptography, the original stealth address EIP-5564 thread is the standard reference.
How Curvy works in practice
There are three parties in any Curvy payment:
The recipient, who generates a stealth meta-address once and shares it the way they would share an ENS name or a regular wallet address.
The sender, who uses the meta-address to compute a fresh, single-use destination on-chain. The sender does not need to know who the recipient is in any other sense, and the recipient does not need to be online.
The protocol contracts, which post a small announcement so the recipient can detect incoming payments belonging to them, without revealing that detection to anyone else.
The result is a payment that clears in one transaction, on a chain the sender already uses, to an address that is not searchable as belonging to the recipient. No bridge. No deposit pool. No mixer.
What Curvy is not
Curvy is not a chain. It runs on existing EVM networks rather than competing with them.
Curvy is not a token. There is no governance coin, no points campaign, and no airdrop attached to the core protocol.
Curvy is not a mixer in the regulatory sense. Funds are not pooled with other users’ funds and withdrawn from a shared anonymity set. Each payment is a direct transfer from sender to recipient – privacy comes from address derivation, not from commingling. This distinction matters for compliance teams.
Curvy is not exclusive to shielded pools. Stealth addresses and shielded pools protect different parts of a transaction graph, and most serious privacy programs end up using both.
Who builds it
Curvy is built by a team of cryptography and protocol engineers working in the open. The technical work originates from research published on ethresear.ch and has been refined through grant cycles with the Ethereum Foundation and the Starknet Foundation.
The project is open source. Code lives at github.com/0xCurvy. Standards work happens in public, and everything ships under permissive licenses.
Supported chains
At the time of writing, Curvy is live on Solana, Ethereum mainnet, and the major EVM L2s and sidechains: Base, Arbitrum, Polygon, Optimism, BSC, Linea, and Gnosis. New chain integrations are added based on developer demand and audit capacity rather than a marketing schedule.
Who uses Curvy
Three buckets of users have shown up so far.
Builders integrating private payments into wallets, payroll tools, and merchant checkouts use the Curvy SDK to add a stealth-address option to their existing flows. Integration tends to take a developer between half a day and a week, depending on how much custom UX they want.
Treasuries and DAOs use Curvy for vendor and contributor payouts when they would rather not publish a quarterly compensation table to anyone with a block explorer.
Agent infrastructure teams use Curvy as the settlement layer for autonomous agent payments, because exposing the wallet of an always-on agent that holds operating capital is a security risk in itself.
Where to start
Read the protocol documentation for an architecture overview, the SDK reference for integration, or the contracts repository for the full implementation. The Curvy Protocol “For the curious” section covers the cryptography in more detail.
If you want to see it work end-to-end first, there are video walkthroughs for sending and receiving a stealth payment in under a minute.
Frequently asked questions
What is Curvy?
Curvy is a privacy infrastructure for EVM-compatible blockchains. It uses stealth addresses to let payments settle on public chains without linking back to the recipient’s main wallet.
Is Curvy a blockchain?
No. Curvy is a protocol that runs on multiple chains, including Solana, Ethereum, Base, Arbitrum, Polygon, Optimism, BSC, Linea, and Gnosis.
Who builds Curvy?
Curvy is built by a team of cryptography and protocol engineers working in the open. The project is supported by grants from the Ethereum Foundation and the Starknet Foundation.
What chains does Curvy support?
Ethereum, Solana, Base, Arbitrum, Polygon, Optimism, BSC, Linea, and Gnosis. More chains are added on a rolling basis.
Is Curvy compliant?
Curvy is not a pool and does not commingle user funds. Each payment is a direct transfer between two parties. The protocol publishes a compliance toolkit for teams that need to demonstrate provenance, source-of-funds attestation, or selective disclosure to a counterparty or auditor.
Does Curvy have a token?
No. There is no governance token, no points program, and no airdrop. The protocol is funded by grants and ecosystem partnerships.
How is Curvy different from a shielded pool?
Shielded pools hide amounts and graph structure inside a zero-knowledge anonymity set, so participants must enter and exit the pool. Curvy is a stealth-address system that hides the link between payments and a recipient’s main wallet, with no pool to enter and no withdrawal step. The two designs solve different problems and are often used together.
Where can I integrate Curvy?
Start with the Curvy SDK. Most teams have a working integration in under a day.
—
*Curvy is a privacy infrastructure for EVM-compatible blockchains, also known as 0xCurvy. The protocol is open source and lives at curvy.box