Under The Hood of zkID:
summary
Most web2→web3 identity systems reuse a single ZK circuit: verify a signature and match plaintext criteria (hashing, big-int math, elliptic curves, image/regex checks). Practical builds include zk-creds that cache expensive signature checks in an on-chain Merkle root, Nova/IVC and regex-to-circuit compilers for string matching, and TLS oracles that must either use proxy or key-share designs (creating a designated-verifier weakness). The claim: consolidate tooling—SDKs and cached credentials—cuts repeated client-side cost and enables private contact discovery.
AI-written summary · about
chapters (9)
- 0:00zkID introduction and apps
- 1:52Design patterns in zkID
- 6:04Client-side proof performance
- 7:48TLS oracles with symmetric crypto
- 9:57Optimizing ZK creds generation
- 11:43Privacy-preserving social networks
- 13:08Proof security with signature oracles
- 15:56Oracle-aware security in zkSNARKs
- 18:02Future directions in zkID
related talks
23mHow to overcome AI threat to user authenticity
08mBringing real-world identity on-chain
24mZK: Accelerating DA Interop
24mSelf Workshop
27mShipping zkPassport, Shipping Self Protocol Into Production
20mBusiness Privacy, Harder & More Valuable Than You Think
24mEnhancing Protocol Security With ZK-Oracles
17mZK for the Enterprise - Quod Erit Demonstrandum (What Will Need to be Proven)