Zero Knowledge: you can't leak what you don't know
summary
Describes a concrete zero‑knowledge SaaS design for banking: profile blobs store per-account key pairs (private keys passphrase‑protected on the server), transactions get encrypted with account public keys, and client devices fetch keys, decrypt, categorize and re‑encrypt — a poor-man's homomorphic encryption alternative after dismissing full homomorphic encryption (works on numbers, not strings). Covers sharing by encrypting for multiple public keys, and practical risks: server‑stored private keys, XSS or rogue JS, device CPU/battery limits.
AI-written summary · about
chapters (6)
- 0:00Start
- 5:53Software as a Service
- 7:49Zero Knowledge
- 15:38Public Private Keys
- 21:01Homomorphic Encryption
- 22:47Client Side Processing
related talks
44mZero Knowledge Architecture
27mBuilding Zero-Knowledge Backends
45mZero Knowledge; Meeting the Growing Demand for Security and Privacy
47mIs a Secured (Web) App Possible?
26mApplications of Zero Knowledge Proofs in the Banking Industry
44mZero-Knowledge Proofs: Simultaneously ensuring integrity and privacy
28mDeveloping zero-knowledge solutions with JavaScript
28mPasswordless zero-knowledge services