ZK Email
- Name: ZK Email
- URL: https://zk.email/
- Category: privacy-preserving email-verification middleware / DKIM-backed identity infrastructure / email-native wallet and account-recovery tooling
- Tags: ethereum-ecosystem
- Summary: ZK Email is email-proof middleware, not a cute login demo. The durable thing here is DKIM-backed zero-knowledge verification plus the recovery and wallet plumbing built around it.
- What it does:
- Uses DKIM-signed emails plus zero-knowledge proofs to verify facts about emails without exposing full contents
- Provides verifier libraries, circuits, helpers, contracts, and a higher-level SDK so developers can integrate email proofs without deep zk-circuit expertise
- Operates a proof-registry / blueprint workflow that the team says can deploy proof infrastructure, onchain verifiers, and SDK surfaces for new proof types
- Supports email-based account recovery flows where guardians approve and execute wallet recovery through email commands and zk-email verification
- Maintains an email wallet architecture where users can control wallets and trigger actions through email operations, relayer infrastructure, DKIM registries, token registries, and extension modules
- Publishes additional products and adjacent tooling such as email transaction builders, JWT proofs, DKIM key archive infrastructure, and regex/codegen components
- Key claims:
- The architecture docs say ZK Email authenticates DKIM signatures and validates specific email-content properties without exposing the whole email, enabling trustless and privacy-preserving verification on blockchains using existing email infrastructure
- The docs say proof generation can happen client-side, on ZK Email servers, or on an integrator’s own servers, which is useful for understanding the trust and deployment flexibility
- The SDK overview says developers can integrate ZK proofs for email verification without needing expertise in zk technology because the SDK abstracts circuits, compilation, proving, and contract verification
- The organization profile says the project has a proof registry that can define new proof types and automatically deploy infrastructure, base repositories, onchain verifiers, and SDK access, which makes the ecosystem feel closer to a verification control plane than a standalone library
- The account-recovery architecture docs show concrete recovery infrastructure, including EmailRecoveryManager plus Safe-specific and ERC-7579-style recovery modules, guardian acceptance flows, and recovery command handlers
- The email-wallet contract architecture docs show a much broader operational surface than the name suggests: EmailWalletCore, relayer config, account creation and transport, unclaimed-state handling, extensions, token registry, DKIM registry, price oracle, and multiple proof verifiers
- The main verifier repo and org materials show a large open-source footprint across helpers, circuits, contracts, regex tooling, Noir implementations, account recovery, email wallet, JWT builders, and DKIM archive infrastructure
- Whitepaper: No canonical standalone ZK Email whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official docs, the org profile README, and the main open-source repos around verifier, SDK, account recovery, and email wallet; see
../whitepapers/zk-email-primary-sources-2026-04-27.md. - Sources:
- https://zk.email/
- https://docs.zk.email/introduction
- https://docs.zk.email/architecture/
- https://docs.zk.email/zk-email-sdk/overview
- https://docs.zk.email/account-recovery/architecture
- https://docs.zk.email/email-wallet/contract-architecture
- https://docs.zk.email/sitemap.xml
- https://github.com/zkemail
- https://raw.githubusercontent.com/zkemail/.github/main/profile/README.md
- https://raw.githubusercontent.com/zkemail/zk-email-verify/main/README.md
- https://raw.githubusercontent.com/zkemail/email-wallet/main/README.md
Internal linkages
- Keep this note on the strongest proof-stack reads: tlsnotary, reclaim-protocol, and vlayer.
- That keeps the comparison structural instead of letting the note drift into generic login or wallet-recovery adjacency.
Control surface
-
The leverage sits in proof-registry definitions, proving-location defaults, DKIM key handling, relayer paths, and the recovery or wallet modules built on top.
-
Read ZK Email as email-proof middleware with downstream wallet and recovery packaging, not as a general identity hub.
-
Last reviewed: 2026-06-15 UTC