Semaphore Wallet

Customers: There will be more innovative applications that are built for privacy due to the promising trend of ZK tech stack, but it’s more and more important for clients to keep their own secrets (e.g. trapdoor, nullifier) in order to stay anonymous for these applications.

Developers: Each DApp has to build their own ZK applications and bridgings. Each may take time and effort to develop (and maintain!). They may all have their own implementation.

What if we can support ZK proof generation & verification at the wallet side instead so that the tech stack can be shared?

iOS Secure Enclave to maximize security

• Generate randomized string by hardware rather than javascript client to produce, when first creating the deterministic identity
• Use asymmetric key pair to decrypt identity messages, where private key never leaves the device

ERC-4337 (Account Abstraction) compliant

• Smart contract wallets can be in-built with semaphore identity
• Semaphore proof & signaling can be used for authenticating on-chain transactions
• Anonymous actions (e.g. voting) can be done natively using the wallet where ID commitment stays with the mobile phone
• Making it in wallet form will introduce larger member base to further enhance anonymity