“I think the best use of ZK is connecting Web2 identity with Web3 - proving credentials and compliance without exposing any personal data.” - @stakedeve, Head of BD at @aztecnetwork At Verifying Intelligence (@token2049, Singapore), Aztec Head of BD Steve Kenny explained how ZK lets you bridge Web2 identity (IDs, KYC, attestations, OAuth signatures) to on-chain accounts without leaking underlying PII. A verifier checks a zero-knowledge proof that you hold a specific credential (e.g. “is over 18", “passed KYC with provider X”, “resides in jurisdiction Y”, “owns email/account Z”, etc) while the raw data, issuer payload, and name never leave the client. This enables compliant access control, allowlists, and per-jurisdiction gating as selective disclosures tied to your wallet. Steve’s key points: • Treat identity as attestations → generate ZK proofs client-side, bind them to your wallet, and publish only the proof. • Protect all three privacy surfaces: transaction data (amount/asset), identity data (sender/receiver), and transaction logic (called contracts/call-stack). Leaks on any layer de-anonymize users. • EVM metadata leaks are hard to avoid; purpose-built stacks (e.g. private VMs + shielded state + call-stack privacy) are needed for end-to-end protection. The result: institutions get verifiable compliance signals on-chain; users keep control of their identity. Watch the full panel on Privacy and Compliance, in partnership with @googlecloud & @boundless_xyz: