privacy portal
Curvy Protocol

Curvy Protocol

Curvy is the privacy infrastructure layer for on-chain payments - built for the wallets, applications, and AI agents. On the surface, users get human-readable usernames as a frictionless entry point for receiving crypto. Under the hood, every payment is automatically routed through programmable smart contracts using ZK proofs: a fresh address is generated per transaction, funds are shielded from balance exposure and transaction graph analysis, and time-based correlation attacks are prevented by design. The result is end-to-end cross-chain privacy with a user experience identical to a normal wallet transfer. What makes Curvy distinct is the combination of three properties no existing solution delivers together: invisible UX (privacy requires no action from the user or the agent), embedded compliance and adjustable infrastructure (wallets, DeFi apps, payment platforms, and AI agent frameworks integrate via SDK in minutes).

infrastructurewalletsdefiinfrastructureeth-layer-2
Research snapshot
Mainnet
12/14 evidence fields filled
ActivePrivacy defaultNo KYCOpen sourceNon-custodialP2P
Status
Mainnet
Version mainnet / Mainnet
Evidence
86% complete
12 filled fields out of 14 tracked research fields
Launch
2025-02-28T23:00:00.000Z
Product launch date from Explorer data
Ecosystems
EthereumEthereumSolanaSolanaMultichainMultichain

Openness

Project Phase
mainnet
Launch Day
Feb 28th, 2025
Assets Used
ethusdcusdtother
Native Token
Not available

Not available

Technology

Open Source
Yes
Decentralized Storage
No
Upgradability
Yes
Peer to Peer (P2P)
Supported
Asset Custody
non-custody
Technology Type
Not available

Privacy

Privacy by default
Know Your Customer (KYC)
Not Required
Privacy Policy
Compliance
Curvy is designed to be compatible with regulatory requirements (e.g., OFAC / AML frameworks) through selective disclosure, auditability, and partner-level compliance controls, while the base protocol remains permissionless and non-custodial.
Sign-in Requirements
walletemailseedprivatekey
Collected Data
Wallet address (public interaction layer), transaction metadata required for execution, optional encrypted off-chain communication data. No collection of IP, location, or personal identity data at the protocol level.
Data Usage
Execution of transactions and protocol functionality only (e.g., routing, validation, security, and performance monitoring). No reselling of user data; optional data use may occur at the application or integration layer depending on partners.

Security

Technical Dependency
Not available
Social Dependency
Not available
Third-party Dependency
Li.Fi is used for bridging.

Audits

Media

No media links available for this project.
Coming soon

Articles

Token Info

No token information available for this project.
Not available