Download presentation
Presentation is loading. Please wait.
1
Our Current Knowledge of Knowledge Assumptions
Nir Bitansky Survey talk Technically light The tree of knowledge discovers where paper comes from
2
A (Somewhat) True Story
\ Galileo (circa 1610) βI have observed saturn 3-formedβ π βI formed the 3-nosed verb suvara β
3
βI am an uber soft 3-d horsed verveβ
Keplerβs Discovery \ Kepler βI am an uber soft 3-d horsed verveβ
4
What a Coincidenceβ¦ π β1 π β1 βI have observed saturn 3-formedβ
βI formed the 3-nosed verb suvara β π β1 βI have observed saturn 3-formedβ \ π β1 βI am an uber soft 3-d horsed verveβ
5
Explanations Challenge: demonstrate knowledge w/o revealing it
βconcurrent and independent workβ βK didn't know what heβs committing toβ \ Challenge: demonstrate knowledge w/o revealing it
6
ZK Proofs of Knowledge [Gloldwasser-Micali-Rackoff, Feige-Shamir, Goldreich-Bellare]
π₯ββ Hide the Witness Efficient Extraction π π Witness We say that an interactive proof is a proof of knowledge if every prover that can convince the verifier of some NP statement, must know a witness. Witness is hidden makes it non-trivial And the way that this is formalize is by requiring an efficient extractor.
7
Knowledge β efficiently extractable from adversary
The Extraction Paradigm Adversary Reduction/Sim Knowledge β efficiently extractable from adversary Extractor So how do we typically capture knowledge? The common paradigm is that a given (perhaps adversarial) entity knows something if we can efficiently extract it out. Such knowledge extraction doesnβt only stand on its own, but itβs commonly used in our security analysis: reduction or simulator. Knowledge
8
Extraction in Cryptographic Analysis
CCA2 encryption ZK simulation . . . . . . Extraction Owner of sk also generates proof of correctness What does correctness mean. The function is generated with a vk. Correctness is consistency input independence In MPC composition
9
How is Knowledge Extracted?
Adversary ? So how do we typically capture knowledge? The common paradigm is that a given (perhaps adversarial) entity knows something if we can efficiently extract it out. Knowledge
10
βfakeβ public parameters
Black-Box Extraction βfakeβ public parameters Adversary + trapdoor Adversary Extractor ? So how do we typically capture knowledge? The common paradigm is that a given (perhaps adversarial) entity knows something if we can efficiently extract it out. Knowledge by rewinding
11
Black-box reductions/simulators have barriers Non-Black-Box Techniques
Limits of Black-Box Extraction Black-box reductions/simulators have barriers [β¦, Goldreich-Krawczyk, β¦,Gentry-Wichs, β¦] Adversary Non-Black-Box Techniques [Barak, β¦ ,B-Kalai-Paneth] ? constant-round public-coin ZK 3-message ZK SNARGs for NP . . . So how do we typically capture knowledge? The common paradigm is that a given (perhaps adversarial) entity knows something if we can efficiently extract it out. Knowledge
12
Knowledge Assumptions
So now I want to get to our main topic which is knowledge assumptions and extractable functions and see how they fit into this picture The tree of knowledge discovers knowledge assumptions (and where violins come from)
13
non-black-box extractor
Knowledge of Exponent Assumption [DamgΓ₯rd] πΊβΌ π π Adversary π π π πΌπ π π non-black-box extractor meaningful assuming DLOG! π Note that this is meaningful only assuming DLOG, or trivial. And this hardness is also why such an extractor must be non-BB. π π πΌ βπ΄ βπΈ : ππ π΄ π, π π = π πΌπ π‘βππ πΈ π, π π =πΌ
14
non-black-box extractor
Abstracting: Extractable Primitives [Canetti-Dakdouk,β¦] Adversary π π π π₯ non-black-box extractor meaningful assuming Hardness! So how do we typically capture knowledge? The common paradigm is that a given (perhaps adversarial) entity knows something if we can efficiently extract it out. EWOF, ECRH, ENC,β¦ π₯ βπ΄ βπΈ : ππ π΄ π = π π (π₯) π‘βππ πΈ π =π₯
15
Other Extraction Beasts
Concurrently extractable OWFs [B-Canetti-Chiesa-Goldwasser-Lin-Rubinstein-Tromer, Gupta-Sahai] Extractable IO (aka differing-input obfuscation) [Barak-Goldreich-Impagliazzo-Rudich-Sahai-Vadhan-Yang, Boyle-Chung-Pass, Ananth-Boneh-Garg-Sahai-Zhandry, Ishai-Pandey-Sahai] Auxiliary-input point obfuscation [Canetti, B-Paneth,β¦] So what we show is that you can combine SKFE with plain PKE to go all the way to PKFE. Not todayβ¦
16
Applications Which is really why extractable functions succeed in achieving applications, where there is not enough interaction to commit the adversary to some normal behavior.
17
Damgard CCA KEA Which is really why extractable functions succeed in achieving applications, where there is not enough interaction to commit the adversary to some normal behavior.
18
KEA CCA EOWF 3-ZK Canetti-Dakdouk B-Canetti-Chiesa-Goldwasser-
Lin-Rubinstein-Tromer KEA 3-ZK Hada-Tanaka, Bellare-Palacio Which is really why extractable functions succeed in achieving applications, where there is not enough interaction to commit the adversary to some normal behavior.
19
Gennaro-Gentry-Parno-Raykova
linear encryption (lattices, factoring) CCA KEA EOWF linear-only encryption ECRH B-Canetti- Chiesa-Tromer 3-ZK B-Chiesa-Ishai- Paneth-Ostrovsky Which is really why extractable functions succeed in achieving applications, where there is not enough interaction to commit the adversary to some normal behavior. SNARKs (NP) Mie, Groth, Lipmaa, Gennaro-Gentry-Parno-Raykova
20
KEA linear encryption (lattices, factoring) CCA EOWF linear-only ECRH
3-ZK Which is really why extractable functions succeed in achieving applications, where there is not enough interaction to commit the adversary to some normal behavior. SNARKs (NP)
21
Applications SNARKs (NP)
Which is really why extractable functions succeed in achieving applications, where there is not enough interaction to commit the adversary to some normal behavior. SNARKs (NP)
22
[Boneh-Ishai-Sahai-Wu]
The Power of SNARKs delegating computation proof-carrying data [Chiesa-Tromer] . . . . . . SNARKs Owner of sk also generates proof of correctness What does correctness mean. The function is generated with a vk. Correctness is consistency efficient obfuscation image authentication crypto currency [ZCash] [Boneh-Ishai-Sahai-Wu] [Tromer-Naveh]
23
Succinct Non-Interactive Argument of Knowledge computationally sound
Whatβs a SNARK? Succinct Non-Interactive Argument of Knowledge πππ π(π₯,π€) (reusable) π(π₯) π computationally sound fast verification |π|βͺ|π€| Which is really why extractable functions succeed in achieving applications, where there is not enough interaction to commit the adversary to some normal behavior.
24
Succinct Non-Interactive Argument of Knowledge non-black-box extractor
Whatβs a SNARK? Succinct Non-Interactive Argument of Knowledge πππ π(π₯,π€) (reusable) π(π₯) π fast verification |π|βͺ|π€| non-black-box extractor Which is really why extractable functions succeed in achieving applications, where there is not enough interaction to commit the adversary to some normal behavior. π€ Variants: short/long crs, privately/publicly verifiable
25
Approach for SNARKs (Oversimplified)
[IKOS,β¦,BCIOP, GGPR,β¦] Linear PCP + So to demonstrate how we could use knowledge to get SNARKs. I want to briefly tell you about a simple paradigm to do this (and this will be somewhat sketchy and oversimplified) Linear-Only Encryption
26
Linear PCP βLPCP w/ quasi-optimal π, βvery simpleβ π π(π₯,π€) π(π₯)
π
β π½ π πβ π½ π β©π,π
βͺ π(π₯,π€) this talk: 1 query π(π₯) Which is really why extractable functions succeed in achieving applications, where there is not enough interaction to commit the adversary to some normal behavior. βLPCP w/ quasi-optimal π, βvery simpleβ π [QSPs: Gentry-Gennaro-Parno-Raykova]
27
Linear-Only Encryption
[Boneh-Segev-Waters] πΈ π₯ 1 β―πΈ( π₯ π ) π΄ linearly-homomorphic, semantic-secure πΈ(π§) βvalidβ non-black-box extractor Which is really why extractable functions succeed in achieving applications, where there is not enough interaction to commit the adversary to some normal behavior. πβ π½ π :π§=β©π,πβͺ candidates from linear schemes + KEA* (also some relaxed formulations)
28
Putting Them Together π(π₯,π€) π(π₯) πΈ(π 1 ),β¦, πΈ(π π )βπ½ πΈ( π
,π )
Which is really why extractable functions succeed in achieving applications, where there is not enough interaction to commit the adversary to some normal behavior.
29
Soundness (Knowledge) Intuition
πΈ(π 1 ),β¦, πΈ(π π )βπ½ π β π(π₯) πΈ( π§ β ) accepts! non-black-box extractor Which is really why extractable functions succeed in achieving applications, where there is not enough interaction to commit the adversary to some normal behavior. π§ β valid PCP answer semantic-security π
β β π½ π : π§ β =β© π
β ,πβͺ decode π€ β© π
β ,πβ²β$βͺ valid w.h.p
30
Was Knowledge So Important Here?
Relaxed βlinear-onlyβ β soundness (SNARG) But, knowledge is crucial when composing! βI know a hash preimageβ βI also know a SNARK of previous preimage β Often needed in applicationsβ¦. bootstrapping SNARKs
31
Knowledge Assumptions?
So Why Donβt We Like Knowledge Assumptions? candidates intuition applications Whatβs missing? So how do we typically capture knowledge? The common paradigm is that a given (perhaps adversarial) entity knows something if we can efficiently extract it out.
32
Hope for explicit non-black-box extractor?
A Hole in the Reduction ZCash Adversary Reduction Extractor collision in SHA βπ΄ βπΈ : ππ π΄ π = π π (π₯) π‘βππ πΈ π =π₯ Hope for explicit non-black-box extractor?
33
Hope for Explicit Extractor?
34
Hope for Explicit Extractor?
βπΈ βπ΄: ππ π΄ π = π π (π₯) π‘βππ πΈ π =π₯ βπ΄ βπΈ Adversary π π π π₯ Universal Extractor π₯
35
Adversaryβs code may be obfuscatedβ¦ Made formal assuming IO
Limitation [Hada-Tanak, Goldreich] Adversaryβs code may be obfuscatedβ¦ Adversary π π π π₯ Universal Extractor π₯ Made formal assuming IO [B-Canetti-Paneh-Rosen]
36
Food for Thought
37
Something We Can Do (std. assumptions)
[B-Canetti-Paneth-Rosen] Uniform Adversary π π π π₯ Universal Extractor π₯ unsatisfying! Q1: Other extractable primitives?
38
Relax the Definition πβ π π π π₯ π₯
Adversary πβ π π π π₯ Universal Extractor π₯ Sufficient for 3ZK if one-way for all π β¦ Q2: Sufficient for SNARKs? Constructions?
39
Non-Uniform Techniques?
βπΈ βπ΄: ππ π΄ π = π π (π₯) π‘βππ πΈ π =π₯ βπ΄ βπΈ Adversary π π π π₯ Extractor π₯ Q3: Prove existence (under better assumption)
40
Non-Uniform Techniques?
βπΈ βπ΄: ππ π΄ π = π π (π₯) π‘βππ πΈ π =π₯ βπ΄ βπΈ Adversary π π π π₯ Extractor π₯ Q4: Disprove existence!
41
Thanks! Recall what is FE In plain, say public-key, encryption
Those w/ the key, others canβt tell one encrypted message from the other
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.