Hi everyone,
We’re building a new ZK rollup that makes privacy as fundamental as scalability, and we’d love to gather early feedback from the Ethereum community.
The Problem:
Layer 2 rollups have solved Ethereum’s throughput bottleneck but not its privacy problem. Today, balances, contract state, and transaction metadata remain public. Since Ethereum uses an account-based model, repeated activity can easily be linked to identities — opening the door to phishing, MEV extraction, reputational risk, and permanent data trails.
Landscape today:
Projects like Aztec and Fhenix are pushing the frontier here but leave key gaps:
-
Aztec doesn’t yet support multi-user inputs and is still not developing full EVM compatibility.
-
Fhenix focuses on encrypted computation but doesn’t provide correctness proofs end-to-end, functioning more like a black box and not support privacy for every type of transaction
Our Approach:
We’re developing a privacy-preserving ZK rollup that is fully EVM-compatible, supports multi-user input, and proves correctness without revealing transaction details. Instead of exposing balances or metadata, we commit encrypted state and ZK proofs back to Ethereum — ensuring finality and security while keeping user data shielded.
Where we’d love your input:
-
What tradeoffs do you see between privacy-by-default and data-availability in rollups?
-
Would you prefer privacy as default or opt-in when using L2 applications?
-
Which use cases most urgently need this (DeFi, DAOs, cross-chain apps, payments)?
-
What design pitfalls should we avoid when keeping privacy while maintaining Ethereum composability?
We want to build with the community, not in isolation. Your insights will help us validate assumptions and shape the right developer and user experience.
Looking forward to your thoughts!
—
Chanderprakash