Confidential Transactions with Zero Knowledge Proof in Trusted Execution Environments
summary
An open-source runtime compiles code to WebAssembly runtime and loads it into a CPU-backed enclave so only CPU vendor firmware must be trusted; attestation measures and sealed keys validate the runtime. The demo runs non-interactive Bulletproofs as a range proof: secret 7 with bit-width 8 verifies, secret 286 with bit-width 8 rejects, proving the workflow for prover → verifier works. This reduces external trust and moves confidential ZKP execution into TEEs.
AI-written summary · about
chapters (10)
- 0:00Enacts and zero knowledge proofs
- 1:43Limitations of trusted execution environments
- 3:12Enacts limitations solved
- 3:55Enacts development workflow
- 4:41Enacts architecture components
- 6:04ZKP demo setup
- 6:46Zero knowledge proof example
- 8:11Bulletproof ZKP implementation
- 9:33ZKP in finance use cases
- 12:25Q&A
related talks
42mSponsored Session: Confidential Computing - New Capabilities for New Workloads
28mSealed for All: Multi-Party Confidential Computing, No Trust
30mPractical Zero Knowledge Proofs
35mVeracruz: Privacy-preserving mutliparty computation using trusted hardware
37mIt's All About Trust: Why Confidential Computing Matters
40mDoing the Safety Dance: Will Trusted Execution Environments Protect Us?
44mZero-Knowledge Proofs: Simultaneously ensuring integrity and privacy- 37mIt's All About Trust: Why Confidential Computing Matters