Private transactions
with zero-knowledge proofs and a gasless user experience.
ZPCash is a privacy protocol designed for the Ethereum ecosystem. It combines privacy pools, zero-knowledge proofs, and compliance aware infrastructure. to enable confidential transfers without compromising usability.
Why ZPCash
Built on Ethereum for security, ecosystem compatibility, and scalable privacy infrastructure.
- • Hidden sender, recipient, and transfer amount.
- • Commitment and nullifier trees for each asset.
- • Partial withdrawals with automatic change notes.
- • Optional stealth recipient addresses.
- • Risk labels applied without revealing identities.
- • Zero-knowledge verification of compliance thresholds.
- • Replaceable ASP providers governed by the protocol.
- • Ragequit mechanism protects users from ASP censorship.
- • No ETH required.
- • Browser-based identity (username + fingerprint phrase).
- • Relayer marketplace planned for decentralized operation.
Protocol Workflow
ZPCash enables a fully private transaction lifecycle on Ethereum.
- • Blue Orb = your asset moving through each phase.
- • Active steps will glow and highlight text.
- • Click a step to jump manually and read details.
Four Layer Architecture
ZPCash separates protocol components into four independent layers.
User interfaces and relayer APIs.
- • Web and mobile interfaces
- • Username + fingerprint identity
- • Transaction history and note management
Core protocol contracts deployed on Ethereum.
- • Asset-specific privacy pools
- • Append-only Merkle trees
- • Nullifier registry preventing double spends
- • ZK proof verification
Halo2 circuits responsible for deposit and withdrawal proofs
- • Browser-based proof generation
- • On-chain verification
- • Support for partial spending
Independent compliance providers publishing risk-label Merkle roots.
- • Multiple ASP operators
- • periodic root updates
- • governance-controlled allowlists
User Flow – End-to-End
From login to ragequit, every step is designed for a UX as simple as "login, enter amount, click withdraw".
- • Login: username + fingerprint → regenerate keys.
- • Generate commitment + encrypted note.
- • Send ETH/ERC-20 to privacy pool with commitment.
- • Browser generates Halo2 proof (8-12s).
- • Fetch Merkle path & ASP root.
- • Send proof + intent to relayer (HTTPS).
- • Relayer pays ETH, user receives clean asset.
- • If ASP blocks: wait 7 days → ragequit.
- • Everything remains self-custody, fully non-custodial.
Developer Integration
ZPCash can function as a privacy layer for financial infrastructure built on Ethereum.
Potential integrations include:
- • Multiple ASP operators
- • periodic root updates
- • governance-controlled allowlists
- • Solidity SDK
- • TypeScript client library
- • Relayer reference implementation
- • ASP integration framework
- • viewing-key delegation
- • zero-knowledge compliance reporting
- • Post-quantum signature support
- • Decentralized relayer marketplace
- • Cross-chain privacy bridging