Tips and Tricks for Improved User Experience with ZKPs
summary
Prototype implements a ZKP-backed transfer of physical firearm tokens with encrypted serial + random nonce and a digital commitment that enforces physical+digital two‑factor consent. Naive membership proof takes ~45 minutes to generate; goal is ~3 minutes by offloading heavy work and using proof splitting plus reusable authorization proofs on a one‑week layer‑2 cycle. Design adds an authorization view hash and token view key to prevent preimage attacks; uses libSTARK and secp256‑style curve tooling. Approach reduces on‑hand latency but increases protocol complexity and replay‑risk tradeoffs.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:07What Do We Need to Prove?
- 3:18Challenge
- 4:30Solution: Break up the Proofs!
- 5:43Modified Proof Architecture
- 6:16Modifications to Auth Proof
- 6:50Modifications to Recv/Send Proofs
- 7:51Takeaways
related talks
24mZK: Accelerating DA Interop
33mAn Introduction to Zero Knowledge Proofs
51mPanel: Zero Knowledge in the Enterprise
26mState of ZK
23mYour Game Will Suck Without Zero Knowledge Proofs
33mEducational Challenges in the Ever-Evolving Space of Zero-Knowledge
37mZK Compression
01h 35mSTARK – Zero-Knowledge Proof Protocol