Compliant privacy
Private transactions, with compliance built into the architecture
Curvy Protocol shields your on-chain activity and gives the parties you authorize a way to verify it. You choose what to disclose and to whom.
Stealth-address payments that public observers cannot link to you
View keys let auditors and compliance reconstruct your activity without exposing it publicly
Independently audited by Ethernal, with the report public on GitHub
Backed by the Ethereum Foundation, Starknet Foundation, and Arbitrum Foundation
Public chains expose everything by default
Balances, counterparties, and payment history are readable by anyone. That makes on-chain operations hard to run for any team that handles customer funds or has reporting duties.
Tools that hide everything from everyone create the opposite problem. They leave compliance teams with nothing to work with, so they get avoided or blocked.
Curvy Protocol keeps transactions private from the public and legible to the people you authorize. These are separate controls you configure, not a single switch.
How the compliance primitives work
Selective disclosure with view keys. Share a view key with finance, an auditor, or a regulator and they can reconstruct your history. Public observers still cannot.
Transaction screening. Global Ledger provides know-your-transaction checks, with Extended Screening layered on top.
Deposit Address Tainting. Encrypted OriginAddresses lineage travels with funds, so tainted sources can be identified.
Optional identity. An optional KYC hook through the Name Registry, for setups that require it.
Claim-back on rejection. A rejected transaction lets the sender claim funds back rather than leaving them stuck.
What each party sees
| Detail | Public observer | Authorized party (view key) |
|---|---|---|
| Counterparties | Nothing linkable | Full reconstruction |
| Amounts | Hidden | Visible |
| Balances | Hidden | Visible |
| Payment history | Unlinkable | Auditable |
Frequently asked questions
Does this mean Curvy Protocol can see my transactions?
No. The protocol is non-custodial and disclosure is controlled by your view key. You decide who gets one.
Is a stealth-address payment legal?
It is a normal token transfer at the protocol level, indexed by block explorers like any other transfer. The difference is who can link payments together.
What happens if a transaction is flagged?
Rejected transactions can be claimed back by the sender rather than blocked outright.
Can an auditor verify our books?
Yes. A view key lets finance or auditors reconstruct payments without making the ledger public.
Run on-chain without putting everything on display
Private by default. Auditable when you choose.