WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:13.430 align:start position:0% [Music] 00:00:13.430 --> 00:00:13.440 align:start position:0% 00:00:13.440 --> 00:00:16.349 align:start position:0% hello<00:00:14.120> everyone<00:00:15.120> so<00:00:15.320> in<00:00:15.440> the<00:00:15.559> next<00:00:15.719> 20<00:00:15.920> minutes 00:00:16.349 --> 00:00:16.359 align:start position:0% hello everyone so in the next 20 minutes 00:00:16.359 --> 00:00:18.550 align:start position:0% hello everyone so in the next 20 minutes we're<00:00:16.560> going<00:00:16.720> to<00:00:16.840> be<00:00:17.119> talking<00:00:17.480> about<00:00:18.199> the<00:00:18.359> role 00:00:18.550 --> 00:00:18.560 align:start position:0% we're going to be talking about the role 00:00:18.560 --> 00:00:22.189 align:start position:0% we're going to be talking about the role of<00:00:19.240> programmable<00:00:19.840> cryptography<00:00:20.680> in<00:00:21.199> DC 00:00:22.189 --> 00:00:22.199 align:start position:0% of programmable cryptography in DC 00:00:22.199 --> 00:00:23.509 align:start position:0% of programmable cryptography in DC programmable<00:00:22.760> cryptography<00:00:23.240> has<00:00:23.359> been 00:00:23.509 --> 00:00:23.519 align:start position:0% programmable cryptography has been 00:00:23.519 --> 00:00:25.509 align:start position:0% programmable cryptography has been talked<00:00:23.800> about<00:00:24.000> in<00:00:24.119> this<00:00:24.279> conference<00:00:25.119> um<00:00:25.400> you 00:00:25.509 --> 00:00:25.519 align:start position:0% talked about in this conference um you 00:00:25.519 --> 00:00:27.390 align:start position:0% talked about in this conference um you know<00:00:25.800> in<00:00:25.920> relation<00:00:26.240> to<00:00:26.439> ethereum<00:00:26.960> consistent 00:00:27.390 --> 00:00:27.400 align:start position:0% know in relation to ethereum consistent 00:00:27.400 --> 00:00:30.910 align:start position:0% know in relation to ethereum consistent protocols<00:00:27.960> and<00:00:28.119> trust<00:00:28.640> mization<00:00:29.640> and<00:00:30.279> um<00:00:30.640> I<00:00:30.759> I 00:00:30.910 --> 00:00:30.920 align:start position:0% protocols and trust mization and um I I 00:00:30.920 --> 00:00:33.590 align:start position:0% protocols and trust mization and um I I just<00:00:31.039> want<00:00:31.199> to<00:00:31.560> perhaps<00:00:31.840> add<00:00:32.040> the<00:00:32.280> stage<00:00:33.280> um<00:00:33.399> to 00:00:33.590 --> 00:00:33.600 align:start position:0% just want to perhaps add the stage um to 00:00:33.600 --> 00:00:36.350 align:start position:0% just want to perhaps add the stage um to say<00:00:33.879> that<00:00:34.640> cryptography<00:00:35.640> is<00:00:35.920> fundamentally 00:00:36.350 --> 00:00:36.360 align:start position:0% say that cryptography is fundamentally 00:00:36.360 --> 00:00:39.430 align:start position:0% say that cryptography is fundamentally about<00:00:36.559> trust<00:00:37.120> minimization<00:00:38.120> and<00:00:38.640> there<00:00:38.920> is<00:00:39.079> a 00:00:39.430 --> 00:00:39.440 align:start position:0% about trust minimization and there is a 00:00:39.440 --> 00:00:42.630 align:start position:0% about trust minimization and there is a new<00:00:40.440> category<00:00:40.879> a<00:00:41.039> new<00:00:41.200> wave<00:00:41.680> of<00:00:42.000> cryptographic 00:00:42.630 --> 00:00:42.640 align:start position:0% new category a new wave of cryptographic 00:00:42.640 --> 00:00:45.549 align:start position:0% new category a new wave of cryptographic schemes<00:00:43.320> that<00:00:43.440> can<00:00:43.680> help<00:00:43.920> us<00:00:44.360> better<00:00:45.079> minimize 00:00:45.549 --> 00:00:45.559 align:start position:0% schemes that can help us better minimize 00:00:45.559 --> 00:00:48.510 align:start position:0% schemes that can help us better minimize trust<00:00:45.960> in<00:00:46.079> different<00:00:46.360> settings<00:00:47.360> and<00:00:48.120> uh<00:00:48.239> maybe 00:00:48.510 --> 00:00:48.520 align:start position:0% trust in different settings and uh maybe 00:00:48.520 --> 00:00:49.990 align:start position:0% trust in different settings and uh maybe perhaps<00:00:48.840> the<00:00:49.120> the<00:00:49.239> first<00:00:49.399> thing<00:00:49.719> that<00:00:49.800> we'll 00:00:49.990 --> 00:00:50.000 align:start position:0% perhaps the the first thing that we'll 00:00:50.000 --> 00:00:52.709 align:start position:0% perhaps the the first thing that we'll do<00:00:50.320> here<00:00:50.520> is<00:00:50.640> to<00:00:50.920> introduce<00:00:51.559> our<00:00:51.840> our<00:00:52.039> panelist 00:00:52.709 --> 00:00:52.719 align:start position:0% do here is to introduce our our panelist 00:00:52.719 --> 00:00:55.389 align:start position:0% do here is to introduce our our panelist muu<00:00:53.520> and<00:00:53.680> muu<00:00:54.079> has<00:00:54.239> worked<00:00:54.640> for<00:00:54.840> over<00:00:55.000> a<00:00:55.120> decade 00:00:55.389 --> 00:00:55.399 align:start position:0% muu and muu has worked for over a decade 00:00:55.399 --> 00:00:58.189 align:start position:0% muu and muu has worked for over a decade in<00:00:55.640> cryptography<00:00:56.640> and<00:00:56.840> maybe<00:00:57.840> can<00:00:57.920> you<00:00:58.039> tell 00:00:58.189 --> 00:00:58.199 align:start position:0% in cryptography and maybe can you tell 00:00:58.199 --> 00:01:00.229 align:start position:0% in cryptography and maybe can you tell us<00:00:58.359> briefly<00:00:58.680> about<00:00:58.840> your<00:00:59.000> background<00:00:59.600> and<00:01:00.160> you 00:01:00.229 --> 00:01:00.239 align:start position:0% us briefly about your background and you 00:01:00.239 --> 00:01:01.750 align:start position:0% us briefly about your background and you know<00:01:00.399> your<00:01:00.640> experiences<00:01:01.199> in<00:01:01.359> in<00:01:01.519> these 00:01:01.750 --> 00:01:01.760 align:start position:0% know your experiences in in these 00:01:01.760 --> 00:01:04.509 align:start position:0% know your experiences in in these cryptographic<00:01:02.480> Primitives<00:01:03.399> yeah<00:01:04.000> uh<00:01:04.199> thanks 00:01:04.509 --> 00:01:04.519 align:start position:0% cryptographic Primitives yeah uh thanks 00:01:04.519 --> 00:01:07.550 align:start position:0% cryptographic Primitives yeah uh thanks V<00:01:05.199> uh<00:01:05.320> my<00:01:05.439> name<00:01:05.600> is<00:01:05.720> Mutu<00:01:06.560> uh<00:01:06.720> I'm<00:01:06.880> a<00:01:07.040> professor 00:01:07.550 --> 00:01:07.560 align:start position:0% V uh my name is Mutu uh I'm a professor 00:01:07.560 --> 00:01:10.109 align:start position:0% V uh my name is Mutu uh I'm a professor at<00:01:08.000> Josh<00:01:08.320> toown<00:01:08.759> University<00:01:09.479> and<00:01:09.680> founder<00:01:10.000> of 00:01:10.109 --> 00:01:10.119 align:start position:0% at Josh toown University and founder of 00:01:10.119 --> 00:01:12.950 align:start position:0% at Josh toown University and founder of a<00:01:10.240> zero<00:01:10.520> knowledge<00:01:10.799> company<00:01:11.119> Le<00:01:11.479> hero<00:01:12.479> um<00:01:12.799> I 00:01:12.950 --> 00:01:12.960 align:start position:0% a zero knowledge company Le hero um I 00:01:12.960 --> 00:01:17.510 align:start position:0% a zero knowledge company Le hero um I did<00:01:13.159> my<00:01:13.360> PhD<00:01:14.000> back<00:01:14.400> in<00:01:15.640> 2004<00:01:16.640> uh<00:01:16.759> under<00:01:17.040> Rafael 00:01:17.510 --> 00:01:17.520 align:start position:0% did my PhD back in 2004 uh under Rafael 00:01:17.520 --> 00:01:20.990 align:start position:0% did my PhD back in 2004 uh under Rafael Pas<00:01:17.759> who<00:01:17.840> is<00:01:18.320> a<00:01:18.439> student<00:01:18.920> of<00:01:19.360> Sylvio<00:01:19.880> mikali<00:01:20.880> uh 00:01:20.990 --> 00:01:21.000 align:start position:0% Pas who is a student of Sylvio mikali uh 00:01:21.000 --> 00:01:22.350 align:start position:0% Pas who is a student of Sylvio mikali uh I've<00:01:21.119> been<00:01:21.360> doing<00:01:21.640> research<00:01:21.960> in<00:01:22.079> zero 00:01:22.350 --> 00:01:22.360 align:start position:0% I've been doing research in zero 00:01:22.360 --> 00:01:24.190 align:start position:0% I've been doing research in zero knowledge<00:01:22.600> and<00:01:22.720> multiparty<00:01:23.200> computation<00:01:23.680> for 00:01:24.190 --> 00:01:24.200 align:start position:0% knowledge and multiparty computation for 00:01:24.200 --> 00:01:28.069 align:start position:0% knowledge and multiparty computation for I<00:01:24.280> think<00:01:24.479> two<00:01:24.759> decades<00:01:25.560> uh<00:01:25.720> now<00:01:26.680> and 00:01:28.069 --> 00:01:28.079 align:start position:0% I think two decades uh now and 00:01:28.079 --> 00:01:31.630 align:start position:0% I think two decades uh now and um<00:01:29.079> I<00:01:29.200> think<00:01:29.600> uh<00:01:30.040> one<00:01:30.159> of<00:01:30.320> the<00:01:30.920> things<00:01:31.240> for<00:01:31.400> me 00:01:31.630 --> 00:01:31.640 align:start position:0% um I think uh one of the things for me 00:01:31.640 --> 00:01:33.270 align:start position:0% um I think uh one of the things for me just<00:01:31.920> blockchain<00:01:32.439> ecosystem<00:01:33.000> and<00:01:33.159> the 00:01:33.270 --> 00:01:33.280 align:start position:0% just blockchain ecosystem and the 00:01:33.280 --> 00:01:35.910 align:start position:0% just blockchain ecosystem and the ethereum<00:01:33.799> ecosystem<00:01:34.439> is<00:01:34.640> that<00:01:35.280> these<00:01:35.680> these 00:01:35.910 --> 00:01:35.920 align:start position:0% ethereum ecosystem is that these these 00:01:35.920 --> 00:01:37.749 align:start position:0% ethereum ecosystem is that these these Primitives<00:01:36.399> that<00:01:36.560> we<00:01:36.640> have<00:01:36.799> studied<00:01:37.200> that<00:01:37.320> was 00:01:37.749 --> 00:01:37.759 align:start position:0% Primitives that we have studied that was 00:01:37.759 --> 00:01:40.510 align:start position:0% Primitives that we have studied that was discovered<00:01:38.119> in<00:01:38.240> the<00:01:38.360> 80s<00:01:39.200> are<00:01:39.439> really<00:01:39.840> coming 00:01:40.510 --> 00:01:40.520 align:start position:0% discovered in the 80s are really coming 00:01:40.520 --> 00:01:43.389 align:start position:0% discovered in the 80s are really coming uh<00:01:40.640> to<00:01:40.880> life<00:01:41.720> uh<00:01:41.840> but<00:01:42.000> today<00:01:42.439> I<00:01:42.680> I<00:01:42.840> guess<00:01:43.200> uh<00:01:43.280> we 00:01:43.389 --> 00:01:43.399 align:start position:0% uh to life uh but today I I guess uh we 00:01:43.399 --> 00:01:45.789 align:start position:0% uh to life uh but today I I guess uh we are<00:01:43.479> going<00:01:43.600> to<00:01:43.759> talk<00:01:43.960> about<00:01:44.200> more<00:01:44.719> advanced 00:01:45.789 --> 00:01:45.799 align:start position:0% are going to talk about more advanced 00:01:45.799 --> 00:01:48.389 align:start position:0% are going to talk about more advanced Primitives<00:01:46.799> um<00:01:47.119> which<00:01:47.320> I<00:01:47.399> would<00:01:47.600> also<00:01:47.880> include 00:01:48.389 --> 00:01:48.399 align:start position:0% Primitives um which I would also include 00:01:48.399 --> 00:01:51.230 align:start position:0% Primitives um which I would also include like<00:01:48.600> from<00:01:48.880> FHA<00:01:49.439> to<00:01:49.640> Fe<00:01:50.040> witness<00:01:50.399> encryption 00:01:51.230 --> 00:01:51.240 align:start position:0% like from FHA to Fe witness encryption 00:01:51.240 --> 00:01:54.389 align:start position:0% like from FHA to Fe witness encryption and<00:01:51.479> indistinguishability<00:01:52.200> of<00:01:53.200> fation<00:01:54.200> yeah 00:01:54.389 --> 00:01:54.399 align:start position:0% and indistinguishability of fation yeah 00:01:54.399 --> 00:01:56.350 align:start position:0% and indistinguishability of fation yeah so<00:01:54.600> perhaps<00:01:55.040> let's<00:01:55.240> dive<00:01:55.479> straight<00:01:55.759> into<00:01:55.960> it 00:01:56.350 --> 00:01:56.360 align:start position:0% so perhaps let's dive straight into it 00:01:56.360 --> 00:01:58.709 align:start position:0% so perhaps let's dive straight into it so<00:01:56.600> I<00:01:56.680> think<00:01:57.320> um<00:01:57.520> most<00:01:57.759> of<00:01:58.039> of<00:01:58.200> us<00:01:58.360> here 00:01:58.709 --> 00:01:58.719 align:start position:0% so I think um most of of us here 00:01:58.719 --> 00:02:01.389 align:start position:0% so I think um most of of us here probably<00:01:59.280> have<00:01:59.439> heard<00:01:59.920> CK<00:02:00.479> zero<00:02:00.799> knowledge 00:02:01.389 --> 00:02:01.399 align:start position:0% probably have heard CK zero knowledge 00:02:01.399 --> 00:02:03.429 align:start position:0% probably have heard CK zero knowledge and<00:02:01.640> MPC<00:02:02.280> multi<00:02:02.640> party 00:02:03.429 --> 00:02:03.439 align:start position:0% and MPC multi party 00:02:03.439 --> 00:02:05.950 align:start position:0% and MPC multi party computation<00:02:04.439> and<00:02:04.840> uh<00:02:04.960> to<00:02:05.560> probably<00:02:05.799> to<00:02:05.880> a 00:02:05.950 --> 00:02:05.960 align:start position:0% computation and uh to probably to a 00:02:05.960 --> 00:02:07.749 align:start position:0% computation and uh to probably to a certain<00:02:06.159> extent<00:02:06.479> FH<00:02:06.960> right<00:02:07.079> fully<00:02:07.320> homeor 00:02:07.749 --> 00:02:07.759 align:start position:0% certain extent FH right fully homeor 00:02:07.759 --> 00:02:09.910 align:start position:0% certain extent FH right fully homeor encryption<00:02:08.440> can<00:02:08.560> you<00:02:08.759> explain<00:02:09.640> um<00:02:09.800> the 00:02:09.910 --> 00:02:09.920 align:start position:0% encryption can you explain um the 00:02:09.920 --> 00:02:12.589 align:start position:0% encryption can you explain um the landscape<00:02:10.479> there<00:02:10.879> and<00:02:11.039> and<00:02:11.239> also<00:02:12.239> uh 00:02:12.589 --> 00:02:12.599 align:start position:0% landscape there and and also uh 00:02:12.599 --> 00:02:14.910 align:start position:0% landscape there and and also uh functional<00:02:13.000> encryption<00:02:13.680> winess<00:02:14.040> encryption 00:02:14.910 --> 00:02:14.920 align:start position:0% functional encryption winess encryption 00:02:14.920 --> 00:02:17.190 align:start position:0% functional encryption winess encryption and<00:02:15.280> inity<00:02:16.160> officiation<00:02:16.840> what<00:02:16.920> do<00:02:17.080> these 00:02:17.190 --> 00:02:17.200 align:start position:0% and inity officiation what do these 00:02:17.200 --> 00:02:18.309 align:start position:0% and inity officiation what do these things<00:02:17.440> actually 00:02:18.309 --> 00:02:18.319 align:start position:0% things actually 00:02:18.319 --> 00:02:22.430 align:start position:0% things actually do<00:02:19.319> so<00:02:20.120> when<00:02:20.239> you<00:02:20.360> think<00:02:20.519> of<00:02:20.800> encryption<00:02:21.800> it<00:02:21.959> is 00:02:22.430 --> 00:02:22.440 align:start position:0% do so when you think of encryption it is 00:02:22.440 --> 00:02:25.270 align:start position:0% do so when you think of encryption it is one<00:02:22.640> way<00:02:22.760> to<00:02:22.959> look<00:02:23.120> at<00:02:23.280> it<00:02:23.599> is<00:02:23.920> that<00:02:24.920> uh<00:02:25.040> with<00:02:25.160> a 00:02:25.270 --> 00:02:25.280 align:start position:0% one way to look at it is that uh with a 00:02:25.280 --> 00:02:27.350 align:start position:0% one way to look at it is that uh with a secret<00:02:25.680> key<00:02:25.879> you<00:02:26.040> get<00:02:26.239> sort<00:02:26.440> of<00:02:26.599> an<00:02:26.840> All<00:02:27.080> or 00:02:27.350 --> 00:02:27.360 align:start position:0% secret key you get sort of an All or 00:02:27.360 --> 00:02:29.070 align:start position:0% secret key you get sort of an All or Nothing<00:02:27.760> functionality<00:02:28.599> if<00:02:28.720> you<00:02:28.840> have<00:02:28.959> the 00:02:29.070 --> 00:02:29.080 align:start position:0% Nothing functionality if you have the 00:02:29.080 --> 00:02:31.309 align:start position:0% Nothing functionality if you have the secret<00:02:29.440> key<00:02:29.599> you<00:02:29.920> can<00:02:30.360> retrieve<00:02:30.800> the<00:02:30.920> entire 00:02:31.309 --> 00:02:31.319 align:start position:0% secret key you can retrieve the entire 00:02:31.319 --> 00:02:34.030 align:start position:0% secret key you can retrieve the entire message<00:02:32.319> if<00:02:32.400> you<00:02:32.560> don't<00:02:33.080> you<00:02:33.200> don't<00:02:33.440> you<00:02:33.599> get 00:02:34.030 --> 00:02:34.040 align:start position:0% message if you don't you don't you get 00:02:34.040 --> 00:02:36.309 align:start position:0% message if you don't you don't you get nothing<00:02:35.040> these<00:02:35.280> Primitives<00:02:35.920> functional 00:02:36.309 --> 00:02:36.319 align:start position:0% nothing these Primitives functional 00:02:36.319 --> 00:02:38.309 align:start position:0% nothing these Primitives functional encryption<00:02:36.720> and<00:02:36.840> witness<00:02:37.160> encryption<00:02:38.160> you 00:02:38.309 --> 00:02:38.319 align:start position:0% encryption and witness encryption you 00:02:38.319 --> 00:02:41.910 align:start position:0% encryption and witness encryption you know<00:02:38.920> push<00:02:39.640> these<00:02:40.040> encryption<00:02:40.599> schemes<00:02:41.120> to 00:02:41.910 --> 00:02:41.920 align:start position:0% know push these encryption schemes to 00:02:41.920 --> 00:02:44.309 align:start position:0% know push these encryption schemes to what<00:02:42.360> we<00:02:42.560> like<00:02:42.720> to<00:02:42.920> call<00:02:43.200> now<00:02:43.519> programmable 00:02:44.309 --> 00:02:44.319 align:start position:0% what we like to call now programmable 00:02:44.319 --> 00:02:46.589 align:start position:0% what we like to call now programmable cryptography<00:02:45.319> so<00:02:45.560> let's<00:02:45.879> start<00:02:46.120> with<00:02:46.360> W 00:02:46.589 --> 00:02:46.599 align:start position:0% cryptography so let's start with W 00:02:46.599 --> 00:02:48.350 align:start position:0% cryptography so let's start with W witness<00:02:46.959> encryption<00:02:47.599> so<00:02:47.720> what<00:02:47.840> does<00:02:48.040> witness 00:02:48.350 --> 00:02:48.360 align:start position:0% witness encryption so what does witness 00:02:48.360 --> 00:02:51.030 align:start position:0% witness encryption so what does witness encryption<00:02:48.840> allow<00:02:49.080> you<00:02:49.200> to<00:02:49.360> do<00:02:50.040> is<00:02:50.239> to<00:02:50.560> encrypt 00:02:51.030 --> 00:02:51.040 align:start position:0% encryption allow you to do is to encrypt 00:02:51.040 --> 00:02:55.470 align:start position:0% encryption allow you to do is to encrypt a<00:02:51.599> message<00:02:52.599> with<00:02:53.000> say<00:02:53.239> a<00:02:53.480> puzzle<00:02:54.480> and<00:02:54.640> the<00:02:54.840> idea 00:02:55.470 --> 00:02:55.480 align:start position:0% a message with say a puzzle and the idea 00:02:55.480 --> 00:02:57.710 align:start position:0% a message with say a puzzle and the idea is<00:02:55.680> that<00:02:55.879> you'd<00:02:56.159> be<00:02:56.400> able<00:02:56.640> to<00:02:56.879> decrypt<00:02:57.519> this 00:02:57.710 --> 00:02:57.720 align:start position:0% is that you'd be able to decrypt this 00:02:57.720 --> 00:03:00.190 align:start position:0% is that you'd be able to decrypt this encryption<00:02:58.680> only<00:02:59.159> if<00:02:59.280> you<00:02:59.400> know<00:02:59.560> the<00:02:59.879> solution 00:03:00.190 --> 00:03:00.200 align:start position:0% encryption only if you know the solution 00:03:00.200 --> 00:03:01.830 align:start position:0% encryption only if you know the solution to<00:03:00.319> the<00:03:00.480> puzzle<00:03:01.159> and<00:03:01.360> this<00:03:01.440> is<00:03:01.599> really 00:03:01.830 --> 00:03:01.840 align:start position:0% to the puzzle and this is really 00:03:01.840 --> 00:03:03.270 align:start position:0% to the puzzle and this is really beautiful<00:03:02.319> because<00:03:02.599> you<00:03:02.720> don't<00:03:02.879> need<00:03:03.000> to<00:03:03.159> give 00:03:03.270 --> 00:03:03.280 align:start position:0% beautiful because you don't need to give 00:03:03.280 --> 00:03:05.670 align:start position:0% beautiful because you don't need to give a<00:03:03.400> secret<00:03:03.720> key<00:03:03.920> to<00:03:04.080> anybody<00:03:04.720> the<00:03:04.840> secret<00:03:05.239> key 00:03:05.670 --> 00:03:05.680 align:start position:0% a secret key to anybody the secret key 00:03:05.680 --> 00:03:08.750 align:start position:0% a secret key to anybody the secret key is<00:03:06.040> the<00:03:06.239> solution<00:03:06.640> to<00:03:06.799> the<00:03:07.400> puzzle<00:03:08.400> now<00:03:08.640> what 00:03:08.750 --> 00:03:08.760 align:start position:0% is the solution to the puzzle now what 00:03:08.760 --> 00:03:10.190 align:start position:0% is the solution to the puzzle now what could<00:03:08.959> this<00:03:09.120> puzzle<00:03:09.480> be<00:03:09.680> in<00:03:09.799> the<00:03:09.959> in<00:03:10.040> the 00:03:10.190 --> 00:03:10.200 align:start position:0% could this puzzle be in the in the 00:03:10.200 --> 00:03:13.110 align:start position:0% could this puzzle be in the in the context<00:03:10.599> of<00:03:11.159> let's<00:03:11.360> say<00:03:11.920> uh<00:03:12.080> Bitcoins<00:03:12.599> Etc<00:03:13.040> you 00:03:13.110 --> 00:03:13.120 align:start position:0% context of let's say uh Bitcoins Etc you 00:03:13.120 --> 00:03:15.550 align:start position:0% context of let's say uh Bitcoins Etc you could<00:03:13.319> imagine<00:03:13.879> that<00:03:14.519> you<00:03:14.640> know<00:03:15.040> I<00:03:15.200> want<00:03:15.400> to 00:03:15.550 --> 00:03:15.560 align:start position:0% could imagine that you know I want to 00:03:15.560 --> 00:03:17.550 align:start position:0% could imagine that you know I want to lock<00:03:16.000> some<00:03:16.200> amount<00:03:16.480> of<00:03:16.599> money<00:03:16.879> for<00:03:17.080> anyone<00:03:17.440> who 00:03:17.550 --> 00:03:17.560 align:start position:0% lock some amount of money for anyone who 00:03:17.560 --> 00:03:21.110 align:start position:0% lock some amount of money for anyone who can<00:03:17.959> solve<00:03:18.959> uh<00:03:19.159> say<00:03:19.400> the<00:03:19.519> reman<00:03:19.920> hypothesis<00:03:20.879> so 00:03:21.110 --> 00:03:21.120 align:start position:0% can solve uh say the reman hypothesis so 00:03:21.120 --> 00:03:23.350 align:start position:0% can solve uh say the reman hypothesis so now<00:03:21.599> you<00:03:21.720> can<00:03:21.959> imagine<00:03:22.360> that<00:03:22.560> anyone<00:03:23.000> who<00:03:23.159> can 00:03:23.350 --> 00:03:23.360 align:start position:0% now you can imagine that anyone who can 00:03:23.360 --> 00:03:25.350 align:start position:0% now you can imagine that anyone who can solve<00:03:23.640> it<00:03:23.840> gets<00:03:24.080> the<00:03:24.239> solution<00:03:24.959> and<00:03:25.120> can 00:03:25.350 --> 00:03:25.360 align:start position:0% solve it gets the solution and can 00:03:25.360 --> 00:03:27.869 align:start position:0% solve it gets the solution and can decrypt<00:03:26.200> and<00:03:26.599> get<00:03:26.760> a<00:03:26.959> message<00:03:27.360> which<00:03:27.519> is<00:03:27.680> a 00:03:27.869 --> 00:03:27.879 align:start position:0% decrypt and get a message which is a 00:03:27.879 --> 00:03:30.630 align:start position:0% decrypt and get a message which is a transaction<00:03:28.760> paying<00:03:29.040> you<00:03:29.200> some<00:03:29.400> amount<00:03:30.159> so 00:03:30.630 --> 00:03:30.640 align:start position:0% transaction paying you some amount so 00:03:30.640 --> 00:03:32.589 align:start position:0% transaction paying you some amount so witness<00:03:31.000> encryption<00:03:31.799> pushes<00:03:32.159> the<00:03:32.239> boundary 00:03:32.589 --> 00:03:32.599 align:start position:0% witness encryption pushes the boundary 00:03:32.599 --> 00:03:35.270 align:start position:0% witness encryption pushes the boundary of<00:03:32.760> encryption<00:03:33.360> to<00:03:33.560> the<00:03:33.879> point<00:03:34.280> where<00:03:34.920> I<00:03:35.040> can 00:03:35.270 --> 00:03:35.280 align:start position:0% of encryption to the point where I can 00:03:35.280 --> 00:03:37.149 align:start position:0% of encryption to the point where I can now<00:03:35.599> not<00:03:35.799> give<00:03:35.959> a<00:03:36.120> secret<00:03:36.439> key<00:03:36.720> but<00:03:36.879> just<00:03:37.040> be 00:03:37.149 --> 00:03:37.159 align:start position:0% now not give a secret key but just be 00:03:37.159 --> 00:03:38.750 align:start position:0% now not give a secret key but just be able<00:03:37.360> to<00:03:37.519> decrypt<00:03:38.000> if<00:03:38.080> I<00:03:38.200> know<00:03:38.319> the<00:03:38.439> solution 00:03:38.750 --> 00:03:38.760 align:start position:0% able to decrypt if I know the solution 00:03:38.760 --> 00:03:40.990 align:start position:0% able to decrypt if I know the solution to<00:03:38.920> a<00:03:39.040> puzzle<00:03:39.720> functional<00:03:40.200> encryption<00:03:40.799> and 00:03:40.990 --> 00:03:41.000 align:start position:0% to a puzzle functional encryption and 00:03:41.000 --> 00:03:42.869 align:start position:0% to a puzzle functional encryption and indistinguishability<00:03:41.599> of<00:03:42.000> vcation<00:03:42.519> I'd<00:03:42.680> say 00:03:42.869 --> 00:03:42.879 align:start position:0% indistinguishability of vcation I'd say 00:03:42.879 --> 00:03:45.190 align:start position:0% indistinguishability of vcation I'd say is<00:03:43.080> like<00:03:43.760> a<00:03:43.840> little<00:03:44.080> bit<00:03:44.239> of<00:03:44.439> mother<00:03:44.760> of<00:03:44.959> all 00:03:45.190 --> 00:03:45.200 align:start position:0% is like a little bit of mother of all 00:03:45.200 --> 00:03:47.710 align:start position:0% is like a little bit of mother of all Primitives<00:03:45.840> like<00:03:46.560> they<00:03:46.879> you<00:03:47.000> can<00:03:47.239> construct 00:03:47.710 --> 00:03:47.720 align:start position:0% Primitives like they you can construct 00:03:47.720 --> 00:03:49.949 align:start position:0% Primitives like they you can construct one<00:03:47.920> from<00:03:48.200> another<00:03:48.920> and<00:03:49.120> also<00:03:49.319> do<00:03:49.519> a<00:03:49.640> lot<00:03:49.799> of 00:03:49.949 --> 00:03:49.959 align:start position:0% one from another and also do a lot of 00:03:49.959 --> 00:03:52.350 align:start position:0% one from another and also do a lot of things<00:03:50.360> so<00:03:50.560> functional<00:03:51.000> encryption<00:03:51.920> allows 00:03:52.350 --> 00:03:52.360 align:start position:0% things so functional encryption allows 00:03:52.360 --> 00:03:55.869 align:start position:0% things so functional encryption allows you<00:03:52.599> to<00:03:53.360> generate<00:03:54.200> like<00:03:54.760> a<00:03:55.120> programmable 00:03:55.869 --> 00:03:55.879 align:start position:0% you to generate like a programmable 00:03:55.879 --> 00:03:58.309 align:start position:0% you to generate like a programmable secret<00:03:56.319> key<00:03:56.760> this<00:03:56.879> is<00:03:57.040> how<00:03:57.200> I<00:03:57.360> think<00:03:57.560> about<00:03:57.799> it 00:03:58.309 --> 00:03:58.319 align:start position:0% secret key this is how I think about it 00:03:58.319 --> 00:04:00.309 align:start position:0% secret key this is how I think about it so<00:03:58.920> what<00:03:59.079> happens<00:03:59.360> is<00:03:59.519> that<00:03:59.799> in<00:03:59.920> a<00:04:00.000> functional 00:04:00.309 --> 00:04:00.319 align:start position:0% so what happens is that in a functional 00:04:00.319 --> 00:04:02.429 align:start position:0% so what happens is that in a functional encryption<00:04:00.760> I<00:04:00.840> can<00:04:00.959> encrypt<00:04:01.360> a<00:04:01.480> message<00:04:02.200> and 00:04:02.429 --> 00:04:02.439 align:start position:0% encryption I can encrypt a message and 00:04:02.439 --> 00:04:05.710 align:start position:0% encryption I can encrypt a message and then<00:04:03.079> I<00:04:03.200> can<00:04:03.480> generate<00:04:03.879> a<00:04:04.000> secret<00:04:04.439> key<00:04:04.799> for<00:04:05.519> a 00:04:05.710 --> 00:04:05.720 align:start position:0% then I can generate a secret key for a 00:04:05.720 --> 00:04:09.149 align:start position:0% then I can generate a secret key for a Target<00:04:06.360> functionality<00:04:07.360> and<00:04:07.879> this<00:04:08.040> secret<00:04:08.519> key 00:04:09.149 --> 00:04:09.159 align:start position:0% Target functionality and this secret key 00:04:09.159 --> 00:04:12.149 align:start position:0% Target functionality and this secret key will<00:04:09.439> allow<00:04:09.760> me<00:04:09.920> to<00:04:10.159> decrypt<00:04:10.879> any<00:04:11.319> encrypted 00:04:12.149 --> 00:04:12.159 align:start position:0% will allow me to decrypt any encrypted 00:04:12.159 --> 00:04:15.830 align:start position:0% will allow me to decrypt any encrypted message<00:04:13.159> to<00:04:13.360> reveal<00:04:14.040> just<00:04:14.840> the<00:04:15.040> function 00:04:15.830 --> 00:04:15.840 align:start position:0% message to reveal just the function 00:04:15.840 --> 00:04:19.550 align:start position:0% message to reveal just the function applied<00:04:16.400> on<00:04:16.600> the<00:04:16.759> message<00:04:17.600> so<00:04:18.600> if<00:04:18.759> I<00:04:19.040> say<00:04:19.359> some 00:04:19.550 --> 00:04:19.560 align:start position:0% applied on the message so if I say some 00:04:19.560 --> 00:04:21.749 align:start position:0% applied on the message so if I say some function<00:04:20.000> f<00:04:20.359> i<00:04:20.440> can<00:04:20.639> generate<00:04:21.000> a<00:04:21.160> secret<00:04:21.479> key 00:04:21.749 --> 00:04:21.759 align:start position:0% function f i can generate a secret key 00:04:21.759 --> 00:04:25.469 align:start position:0% function f i can generate a secret key secret<00:04:22.160> key<00:04:22.400> F<00:04:23.160> that<00:04:23.479> if<00:04:23.600> I<00:04:23.840> hold<00:04:24.199> this<00:04:24.720> for<00:04:25.040> any 00:04:25.469 --> 00:04:25.479 align:start position:0% secret key F that if I hold this for any 00:04:25.479 --> 00:04:27.310 align:start position:0% secret key F that if I hold this for any Cipher<00:04:25.919> text<00:04:26.160> or<00:04:26.280> any<00:04:26.479> message<00:04:26.880> that's<00:04:27.040> been 00:04:27.310 --> 00:04:27.320 align:start position:0% Cipher text or any message that's been 00:04:27.320 --> 00:04:29.990 align:start position:0% Cipher text or any message that's been encrypted<00:04:27.840> in<00:04:27.960> the<00:04:28.160> scheme<00:04:28.759> I<00:04:28.880> can<00:04:29.039> learn<00:04:29.320> F<00:04:29.520> of 00:04:29.990 --> 00:04:30.000 align:start position:0% encrypted in the scheme I can learn F of 00:04:30.000 --> 00:04:32.749 align:start position:0% encrypted in the scheme I can learn F of F<00:04:31.000> now<00:04:31.440> when<00:04:31.639> this<00:04:31.759> was<00:04:32.120> discovered<00:04:32.400> or<00:04:32.560> when 00:04:32.749 --> 00:04:32.759 align:start position:0% F now when this was discovered or when 00:04:32.759 --> 00:04:35.390 align:start position:0% F now when this was discovered or when this<00:04:32.919> was<00:04:33.280> defined<00:04:33.840> Etc<00:04:34.560> one<00:04:34.680> of<00:04:34.800> the<00:04:34.960> classic 00:04:35.390 --> 00:04:35.400 align:start position:0% this was defined Etc one of the classic 00:04:35.400 --> 00:04:39.230 align:start position:0% this was defined Etc one of the classic examples<00:04:36.080> is<00:04:36.680> uh<00:04:37.039> spam<00:04:37.400> filtering<00:04:38.320> so<00:04:38.759> I<00:04:38.840> can 00:04:39.230 --> 00:04:39.240 align:start position:0% examples is uh spam filtering so I can 00:04:39.240 --> 00:04:42.950 align:start position:0% examples is uh spam filtering so I can have<00:04:39.520> the<00:04:39.720> cloud<00:04:40.720> just<00:04:41.440> have<00:04:41.680> a<00:04:41.960> targeted<00:04:42.720> sort 00:04:42.950 --> 00:04:42.960 align:start position:0% have the cloud just have a targeted sort 00:04:42.960 --> 00:04:45.430 align:start position:0% have the cloud just have a targeted sort of<00:04:43.160> secret<00:04:43.639> key<00:04:44.160> to<00:04:44.320> see<00:04:44.680> whether<00:04:45.120> when<00:04:45.240> an 00:04:45.430 --> 00:04:45.440 align:start position:0% of secret key to see whether when an 00:04:45.440 --> 00:04:47.749 align:start position:0% of secret key to see whether when an encrypted<00:04:46.000> message<00:04:46.360> or<00:04:47.000> uh<00:04:47.160> comes<00:04:47.400> to<00:04:47.560> my 00:04:47.749 --> 00:04:47.759 align:start position:0% encrypted message or uh comes to my 00:04:47.759 --> 00:04:51.510 align:start position:0% encrypted message or uh comes to my inbox<00:04:48.520> to<00:04:48.680> do<00:04:48.919> spam<00:04:49.600> uh<00:04:49.720> filtering<00:04:50.680> but<00:04:51.120> as<00:04:51.280> you 00:04:51.510 --> 00:04:51.520 align:start position:0% inbox to do spam uh filtering but as you 00:04:51.520 --> 00:04:53.150 align:start position:0% inbox to do spam uh filtering but as you as<00:04:51.639> we<00:04:51.720> will<00:04:51.919> talk<00:04:52.120> today<00:04:52.400> you<00:04:52.479> will<00:04:52.680> also<00:04:52.919> see 00:04:53.150 --> 00:04:53.160 align:start position:0% as we will talk today you will also see 00:04:53.160 --> 00:04:55.110 align:start position:0% as we will talk today you will also see that<00:04:53.400> this<00:04:53.560> functional<00:04:54.000> encryption<00:04:54.560> also<00:04:54.840> has 00:04:55.110 --> 00:04:55.120 align:start position:0% that this functional encryption also has 00:04:55.120 --> 00:04:59.189 align:start position:0% that this functional encryption also has other<00:04:55.919> uh<00:04:56.320> powerful<00:04:57.320> uh<00:04:57.840> uh<00:04:58.039> applications<00:04:59.039> now 00:04:59.189 --> 00:04:59.199 align:start position:0% other uh powerful uh uh applications now 00:04:59.199 --> 00:05:01.710 align:start position:0% other uh powerful uh uh applications now industry<00:04:59.680> inability<00:05:00.240> of<00:05:00.400> fation<00:05:01.199> I<00:05:01.320> would<00:05:01.680> I 00:05:01.710 --> 00:05:01.720 align:start position:0% industry inability of fation I would I 00:05:01.720 --> 00:05:03.230 align:start position:0% industry inability of fation I would I would<00:05:01.919> say<00:05:02.160> probably<00:05:02.560> is<00:05:02.759> higher<00:05:03.080> than 00:05:03.230 --> 00:05:03.240 align:start position:0% would say probably is higher than 00:05:03.240 --> 00:05:04.590 align:start position:0% would say probably is higher than witness<00:05:03.560> encryption<00:05:03.960> and<00:05:04.080> functional 00:05:04.590 --> 00:05:04.600 align:start position:0% witness encryption and functional 00:05:04.600 --> 00:05:07.070 align:start position:0% witness encryption and functional encryption<00:05:05.600> it<00:05:05.919> actually<00:05:06.320> has<00:05:06.520> this<00:05:06.720> promise 00:05:07.070 --> 00:05:07.080 align:start position:0% encryption it actually has this promise 00:05:07.080 --> 00:05:08.710 align:start position:0% encryption it actually has this promise that<00:05:07.240> I<00:05:07.320> can<00:05:07.479> take<00:05:07.759> any<00:05:08.039> program<00:05:08.520> and 00:05:08.710 --> 00:05:08.720 align:start position:0% that I can take any program and 00:05:08.720 --> 00:05:10.469 align:start position:0% that I can take any program and obfuscate<00:05:09.320> meaning<00:05:09.600> that<00:05:09.800> I<00:05:09.919> can<00:05:10.120> give<00:05:10.240> it<00:05:10.360> to 00:05:10.469 --> 00:05:10.479 align:start position:0% obfuscate meaning that I can give it to 00:05:10.479 --> 00:05:12.390 align:start position:0% obfuscate meaning that I can give it to you<00:05:10.600> in<00:05:10.720> a<00:05:10.840> way<00:05:11.000> that<00:05:11.120> you<00:05:11.320> cannot<00:05:11.960> reverse 00:05:12.390 --> 00:05:12.400 align:start position:0% you in a way that you cannot reverse 00:05:12.400 --> 00:05:14.350 align:start position:0% you in a way that you cannot reverse engineer<00:05:12.880> the<00:05:13.000> original<00:05:13.440> code<00:05:14.039> now<00:05:14.240> you 00:05:14.350 --> 00:05:14.360 align:start position:0% engineer the original code now you 00:05:14.360 --> 00:05:16.710 align:start position:0% engineer the original code now you should<00:05:14.520> take<00:05:14.639> it<00:05:14.759> with<00:05:14.840> a<00:05:14.960> grain<00:05:15.199> of<00:05:15.320> salt<00:05:16.160> pure 00:05:16.710 --> 00:05:16.720 align:start position:0% should take it with a grain of salt pure 00:05:16.720 --> 00:05:18.710 align:start position:0% should take it with a grain of salt pure obfuscation<00:05:17.360> is<00:05:17.600> impossible<00:05:18.160> so<00:05:18.319> if<00:05:18.440> someone 00:05:18.710 --> 00:05:18.720 align:start position:0% obfuscation is impossible so if someone 00:05:18.720 --> 00:05:20.110 align:start position:0% obfuscation is impossible so if someone comes<00:05:18.919> and<00:05:19.039> says<00:05:19.360> hey<00:05:19.479> can<00:05:19.600> I<00:05:19.720> use 00:05:20.110 --> 00:05:20.120 align:start position:0% comes and says hey can I use 00:05:20.120 --> 00:05:21.830 align:start position:0% comes and says hey can I use indistinguishability<00:05:20.800> obfuscation<00:05:21.639> to 00:05:21.830 --> 00:05:21.840 align:start position:0% indistinguishability obfuscation to 00:05:21.840 --> 00:05:26.550 align:start position:0% indistinguishability obfuscation to replace<00:05:22.560> tees<00:05:23.440> this<00:05:23.560> is<00:05:23.840> not<00:05:24.039> true<00:05:25.400> so<00:05:26.400> yeah<00:05:26.479> I 00:05:26.550 --> 00:05:26.560 align:start position:0% replace tees this is not true so yeah I 00:05:26.560 --> 00:05:28.469 align:start position:0% replace tees this is not true so yeah I think<00:05:26.680> there's<00:05:26.800> a<00:05:26.919> lot<00:05:27.080> to<00:05:27.240> unpack<00:05:28.080> unpack 00:05:28.469 --> 00:05:28.479 align:start position:0% think there's a lot to unpack unpack 00:05:28.479 --> 00:05:30.510 align:start position:0% think there's a lot to unpack unpack there<00:05:29.039> continue 00:05:30.510 --> 00:05:30.520 align:start position:0% there continue 00:05:30.520 --> 00:05:34.070 align:start position:0% there continue um<00:05:31.400> so<00:05:32.400> indistinguishability<00:05:33.120> ofation<00:05:34.000> I 00:05:34.070 --> 00:05:34.080 align:start position:0% um so indistinguishability ofation I 00:05:34.080 --> 00:05:37.629 align:start position:0% um so indistinguishability ofation I want<00:05:34.199> to<00:05:34.400> say<00:05:34.720> is<00:05:34.960> that<00:05:35.240> it's<00:05:35.440> something<00:05:35.919> that 00:05:37.629 --> 00:05:37.639 align:start position:0% want to say is that it's something that 00:05:37.639 --> 00:05:40.350 align:start position:0% want to say is that it's something that um<00:05:38.639> it<00:05:38.840> tries<00:05:39.120> to<00:05:39.280> find<00:05:39.520> the<00:05:39.680> right<00:05:39.919> definition 00:05:40.350 --> 00:05:40.360 align:start position:0% um it tries to find the right definition 00:05:40.360 --> 00:05:43.070 align:start position:0% um it tries to find the right definition of<00:05:40.560> obfuscation<00:05:41.240> that<00:05:41.360> is<00:05:41.520> both<00:05:42.080> realizable 00:05:43.070 --> 00:05:43.080 align:start position:0% of obfuscation that is both realizable 00:05:43.080 --> 00:05:46.469 align:start position:0% of obfuscation that is both realizable and<00:05:44.000> um<00:05:45.000> actually<00:05:45.280> does<00:05:45.560> have<00:05:45.919> meaningful 00:05:46.469 --> 00:05:46.479 align:start position:0% and um actually does have meaningful 00:05:46.479 --> 00:05:48.110 align:start position:0% and um actually does have meaningful consequences<00:05:47.400> I'll<00:05:47.520> just<00:05:47.680> stop<00:05:47.880> with<00:05:48.000> the 00:05:48.110 --> 00:05:48.120 align:start position:0% consequences I'll just stop with the 00:05:48.120 --> 00:05:49.350 align:start position:0% consequences I'll just stop with the definition<00:05:48.479> of<00:05:48.639> indistinguishability 00:05:49.350 --> 00:05:49.360 align:start position:0% definition of indistinguishability 00:05:49.360 --> 00:05:53.510 align:start position:0% definition of indistinguishability obfuscation<00:05:50.360> it<00:05:50.479> says<00:05:50.919> that<00:05:51.919> I<00:05:52.120> can<00:05:52.880> obfuscate 00:05:53.510 --> 00:05:53.520 align:start position:0% obfuscation it says that I can obfuscate 00:05:53.520 --> 00:05:55.990 align:start position:0% obfuscation it says that I can obfuscate programs<00:05:54.039> in<00:05:54.160> a<00:05:54.360> way<00:05:55.039> that<00:05:55.319> I<00:05:55.400> will<00:05:55.600> not<00:05:55.800> be 00:05:55.990 --> 00:05:56.000 align:start position:0% programs in a way that I will not be 00:05:56.000 --> 00:05:57.909 align:start position:0% programs in a way that I will not be able<00:05:56.240> to<00:05:56.440> distinguish<00:05:56.960> the<00:05:57.080> obfuscation<00:05:57.720> of 00:05:57.909 --> 00:05:57.919 align:start position:0% able to distinguish the obfuscation of 00:05:57.919 --> 00:06:00.150 align:start position:0% able to distinguish the obfuscation of two<00:05:58.240> programs<00:05:59.080> that<00:05:59.240> have<00:05:59.639> identical 00:06:00.150 --> 00:06:00.160 align:start position:0% two programs that have identical 00:06:00.160 --> 00:06:03.230 align:start position:0% two programs that have identical functionality<00:06:01.080> and<00:06:01.560> it<00:06:01.680> seems<00:06:02.360> pretty<00:06:02.840> weak 00:06:03.230 --> 00:06:03.240 align:start position:0% functionality and it seems pretty weak 00:06:03.240 --> 00:06:05.309 align:start position:0% functionality and it seems pretty weak but<00:06:03.479> this<00:06:03.960> this<00:06:04.199> form<00:06:04.440> of<00:06:04.600> obfuscation 00:06:05.309 --> 00:06:05.319 align:start position:0% but this this form of obfuscation 00:06:05.319 --> 00:06:07.309 align:start position:0% but this this form of obfuscation already<00:06:06.120> can<00:06:06.280> give<00:06:06.440> you<00:06:06.560> witness<00:06:06.919> encryption 00:06:07.309 --> 00:06:07.319 align:start position:0% already can give you witness encryption 00:06:07.319 --> 00:06:09.749 align:start position:0% already can give you witness encryption functional<00:06:07.759> encryption<00:06:08.639> and<00:06:09.080> uh<00:06:09.240> a<00:06:09.360> lot<00:06:09.560> of 00:06:09.749 --> 00:06:09.759 align:start position:0% functional encryption and uh a lot of 00:06:09.759 --> 00:06:12.029 align:start position:0% functional encryption and uh a lot of other<00:06:10.039> things<00:06:11.039> so<00:06:11.240> just<00:06:11.360> to<00:06:11.520> recap<00:06:11.800> at<00:06:11.919> the 00:06:12.029 --> 00:06:12.039 align:start position:0% other things so just to recap at the 00:06:12.039 --> 00:06:14.270 align:start position:0% other things so just to recap at the high<00:06:12.240> level<00:06:12.960> if<00:06:13.199> we<00:06:13.400> have 00:06:14.270 --> 00:06:14.280 align:start position:0% high level if we have 00:06:14.280 --> 00:06:16.909 align:start position:0% high level if we have officiation<00:06:15.280> then<00:06:15.400> that<00:06:15.639> implies<00:06:16.560> winess 00:06:16.909 --> 00:06:16.919 align:start position:0% officiation then that implies winess 00:06:16.919 --> 00:06:19.629 align:start position:0% officiation then that implies winess encryption<00:06:17.800> and<00:06:17.960> functional<00:06:18.479> encryption<00:06:19.479> um 00:06:19.629 --> 00:06:19.639 align:start position:0% encryption and functional encryption um 00:06:19.639 --> 00:06:21.589 align:start position:0% encryption and functional encryption um what<00:06:19.759> about<00:06:19.960> the<00:06:20.039> other<00:06:20.240> way<00:06:20.440> can<00:06:20.599> can<00:06:20.720> you 00:06:21.589 --> 00:06:21.599 align:start position:0% what about the other way can can you 00:06:21.599 --> 00:06:23.870 align:start position:0% what about the other way can can you some<00:06:21.800> of<00:06:21.880> the<00:06:22.000> landscape<00:06:22.479> so<00:06:23.160> actually<00:06:23.520> a 00:06:23.870 --> 00:06:23.880 align:start position:0% some of the landscape so actually a 00:06:23.880 --> 00:06:26.670 align:start position:0% some of the landscape so actually a strong<00:06:24.199> again<00:06:24.680> uh<00:06:24.919> with<00:06:25.240> just<00:06:25.479> like<00:06:25.680> with<00:06:26.039> aisc 00:06:26.670 --> 00:06:26.680 align:start position:0% strong again uh with just like with aisc 00:06:26.680 --> 00:06:28.589 align:start position:0% strong again uh with just like with aisc even<00:06:26.960> functional<00:06:27.400> encryption<00:06:28.280> there<00:06:28.400> are 00:06:28.589 --> 00:06:28.599 align:start position:0% even functional encryption there are 00:06:28.599 --> 00:06:29.990 align:start position:0% even functional encryption there are different<00:06:28.919> definitions<00:06:29.639> are<00:06:29.759> different 00:06:29.990 --> 00:06:30.000 align:start position:0% different definitions are different 00:06:30.000 --> 00:06:32.189 align:start position:0% different definitions are different levels<00:06:30.280> of<00:06:30.479> security<00:06:31.240> if<00:06:31.360> you<00:06:31.479> go<00:06:31.639> for<00:06:31.880> like 00:06:32.189 --> 00:06:32.199 align:start position:0% levels of security if you go for like 00:06:32.199 --> 00:06:33.710 align:start position:0% levels of security if you go for like sometimes<00:06:32.440> the<00:06:32.680> strongest<00:06:32.960> form<00:06:33.160> of<00:06:33.319> security 00:06:33.710 --> 00:06:33.720 align:start position:0% sometimes the strongest form of security 00:06:33.720 --> 00:06:36.150 align:start position:0% sometimes the strongest form of security it<00:06:33.840> becomes<00:06:34.199> impossible<00:06:35.039> but<00:06:35.319> for<00:06:35.560> a<00:06:35.759> certain 00:06:36.150 --> 00:06:36.160 align:start position:0% it becomes impossible but for a certain 00:06:36.160 --> 00:06:37.749 align:start position:0% it becomes impossible but for a certain kind<00:06:36.360> of<00:06:36.520> functional<00:06:36.880> encryption<00:06:37.360> actually 00:06:37.749 --> 00:06:37.759 align:start position:0% kind of functional encryption actually 00:06:37.759 --> 00:06:39.390 align:start position:0% kind of functional encryption actually you<00:06:37.919> can<00:06:38.240> construct<00:06:38.680> in<00:06:38.880> distinguishability 00:06:39.390 --> 00:06:39.400 align:start position:0% you can construct in distinguishability 00:06:39.400 --> 00:06:41.950 align:start position:0% you can construct in distinguishability of<00:06:39.840> vcation<00:06:40.560> so<00:06:40.759> in<00:06:40.919> that<00:06:41.120> sense<00:06:41.400> I<00:06:41.520> would<00:06:41.720> put 00:06:41.950 --> 00:06:41.960 align:start position:0% of vcation so in that sense I would put 00:06:41.960 --> 00:06:43.670 align:start position:0% of vcation so in that sense I would put both<00:06:42.120> of<00:06:42.240> them<00:06:42.360> in<00:06:42.479> the<00:06:42.599> same<00:06:42.840> category<00:06:43.520> and 00:06:43.670 --> 00:06:43.680 align:start position:0% both of them in the same category and 00:06:43.680 --> 00:06:46.270 align:start position:0% both of them in the same category and both<00:06:43.880> of<00:06:44.000> them<00:06:44.240> imply<00:06:44.599> witness<00:06:45.280> encryption 00:06:46.270 --> 00:06:46.280 align:start position:0% both of them imply witness encryption 00:06:46.280 --> 00:06:47.950 align:start position:0% both of them imply witness encryption and<00:06:46.520> going<00:06:46.840> back<00:06:47.000> from<00:06:47.199> witness<00:06:47.520> encryption 00:06:47.950 --> 00:06:47.960 align:start position:0% and going back from witness encryption 00:06:47.960 --> 00:06:50.029 align:start position:0% and going back from witness encryption to<00:06:48.160> these<00:06:48.360> things<00:06:48.560> are<00:06:48.800> harder<00:06:49.720> got<00:06:49.840> it<00:06:49.960> so 00:06:50.029 --> 00:06:50.039 align:start position:0% to these things are harder got it so 00:06:50.039 --> 00:06:51.469 align:start position:0% to these things are harder got it so witness<00:06:50.319> encryption<00:06:50.800> is<00:06:51.199> kind<00:06:51.319> of<00:06:51.400> the 00:06:51.469 --> 00:06:51.479 align:start position:0% witness encryption is kind of the 00:06:51.479 --> 00:06:52.990 align:start position:0% witness encryption is kind of the easiest<00:06:51.800> to<00:06:51.960> get<00:06:52.360> and<00:06:52.440> then<00:06:52.599> functional 00:06:52.990 --> 00:06:53.000 align:start position:0% easiest to get and then functional 00:06:53.000 --> 00:06:56.070 align:start position:0% easiest to get and then functional encryption<00:06:53.919> iio<00:06:54.919> alisation<00:06:55.560> could<00:06:55.720> be 00:06:56.070 --> 00:06:56.080 align:start position:0% encryption iio alisation could be 00:06:56.080 --> 00:06:57.950 align:start position:0% encryption iio alisation could be equivalent<00:06:56.720> depending<00:06:57.000> on<00:06:57.080> that<00:06:57.360> definition 00:06:57.950 --> 00:06:57.960 align:start position:0% equivalent depending on that definition 00:06:57.960 --> 00:06:59.790 align:start position:0% equivalent depending on that definition so<00:06:58.120> perhaps<00:06:58.440> let's<00:06:58.639> zoom<00:06:58.879> in<00:06:59.000> on<00:06:59.560> wi 00:06:59.790 --> 00:06:59.800 align:start position:0% so perhaps let's zoom in on wi 00:06:59.800 --> 00:07:02.909 align:start position:0% so perhaps let's zoom in on wi encryption<00:07:00.599> uh<00:07:00.919> for<00:07:01.160> now<00:07:02.160> and<00:07:02.440> I<00:07:02.520> think<00:07:02.720> one 00:07:02.909 --> 00:07:02.919 align:start position:0% encryption uh for now and I think one 00:07:02.919 --> 00:07:05.629 align:start position:0% encryption uh for now and I think one use<00:07:03.240> case<00:07:03.720> that<00:07:04.000> really<00:07:04.199> spark<00:07:04.599> my<00:07:04.800> interest 00:07:05.629 --> 00:07:05.639 align:start position:0% use case that really spark my interest 00:07:05.639 --> 00:07:07.550 align:start position:0% use case that really spark my interest uh<00:07:05.720> in<00:07:05.879> actually<00:07:06.120> looking<00:07:06.319> at<00:07:06.440> wi<00:07:06.680> encryption 00:07:07.550 --> 00:07:07.560 align:start position:0% uh in actually looking at wi encryption 00:07:07.560 --> 00:07:11.270 align:start position:0% uh in actually looking at wi encryption is<00:07:08.759> um<00:07:09.759> uh<00:07:10.000> and<00:07:10.560> actually<00:07:10.759> being<00:07:10.960> able<00:07:11.120> to 00:07:11.270 --> 00:07:11.280 align:start position:0% is um uh and actually being able to 00:07:11.280 --> 00:07:13.670 align:start position:0% is um uh and actually being able to extend<00:07:11.840> the<00:07:12.000> existing<00:07:12.360> protocols<00:07:13.319> without 00:07:13.670 --> 00:07:13.680 align:start position:0% extend the existing protocols without 00:07:13.680 --> 00:07:15.830 align:start position:0% extend the existing protocols without actually<00:07:13.879> running<00:07:14.160> MPC<00:07:14.800> so<00:07:14.960> one<00:07:15.199> example<00:07:15.599> of 00:07:15.830 --> 00:07:15.840 align:start position:0% actually running MPC so one example of 00:07:15.840 --> 00:07:18.270 align:start position:0% actually running MPC so one example of this<00:07:16.199> is<00:07:16.919> uh<00:07:17.039> in<00:07:17.199> ethereum<00:07:17.680> we<00:07:17.840> have<00:07:17.960> B 00:07:18.270 --> 00:07:18.280 align:start position:0% this is uh in ethereum we have B 00:07:18.280 --> 00:07:20.150 align:start position:0% this is uh in ethereum we have B signatures<00:07:18.800> we<00:07:19.000> have<00:07:19.599> already<00:07:19.840> a<00:07:19.960> lot<00:07:20.080> of 00:07:20.150 --> 00:07:20.160 align:start position:0% signatures we have already a lot of 00:07:20.160 --> 00:07:22.830 align:start position:0% signatures we have already a lot of Auditors<00:07:20.759> with<00:07:21.240> existing<00:07:21.840> infrastructure 00:07:22.830 --> 00:07:22.840 align:start position:0% Auditors with existing infrastructure 00:07:22.840 --> 00:07:25.230 align:start position:0% Auditors with existing infrastructure and<00:07:23.199> and<00:07:23.680> uh<00:07:23.800> and<00:07:24.319> and<00:07:24.479> the<00:07:24.639> question<00:07:24.879> is<00:07:25.080> can 00:07:25.230 --> 00:07:25.240 align:start position:0% and and uh and and the question is can 00:07:25.240 --> 00:07:28.510 align:start position:0% and and uh and and the question is can we<00:07:25.479> actually<00:07:25.720> encrypt<00:07:26.440> to<00:07:27.440> uh<00:07:28.080> a<00:07:28.240> side<00:07:28.400> of 00:07:28.510 --> 00:07:28.520 align:start position:0% we actually encrypt to uh a side of 00:07:28.520 --> 00:07:30.070 align:start position:0% we actually encrypt to uh a side of these<00:07:28.680> valuators 00:07:30.070 --> 00:07:30.080 align:start position:0% these valuators 00:07:30.080 --> 00:07:32.749 align:start position:0% these valuators and<00:07:30.319> and<00:07:30.599> there<00:07:31.199> the<00:07:32.000> condition<00:07:32.440> right<00:07:32.639> the 00:07:32.749 --> 00:07:32.759 align:start position:0% and and there the condition right the 00:07:32.759 --> 00:07:34.070 align:start position:0% and and there the condition right the puzzle<00:07:33.080> that<00:07:33.199> that<00:07:33.280> you<00:07:33.400> described<00:07:33.759> before 00:07:34.070 --> 00:07:34.080 align:start position:0% puzzle that that you described before 00:07:34.080 --> 00:07:37.110 align:start position:0% puzzle that that you described before would<00:07:34.240> be<00:07:34.800> has<00:07:35.360> enough<00:07:35.680> notes<00:07:36.039> signed<00:07:36.360> a 00:07:37.110 --> 00:07:37.120 align:start position:0% would be has enough notes signed a 00:07:37.120 --> 00:07:39.189 align:start position:0% would be has enough notes signed a message<00:07:38.120> um<00:07:38.280> so<00:07:38.479> that<00:07:38.639> you<00:07:38.720> would<00:07:38.879> then<00:07:39.080> be 00:07:39.189 --> 00:07:39.199 align:start position:0% message um so that you would then be 00:07:39.199 --> 00:07:42.830 align:start position:0% message um so that you would then be able<00:07:39.680> to<00:07:40.080> to<00:07:40.400> decrypt<00:07:41.400> um<00:07:41.639> and<00:07:41.759> so<00:07:42.560> I<00:07:42.680> think 00:07:42.830 --> 00:07:42.840 align:start position:0% able to to decrypt um and so I think 00:07:42.840 --> 00:07:44.909 align:start position:0% able to to decrypt um and so I think that's<00:07:43.080> one<00:07:43.360> application<00:07:43.960> where<00:07:44.479> people<00:07:44.720> have 00:07:44.909 --> 00:07:44.919 align:start position:0% that's one application where people have 00:07:44.919 --> 00:07:46.790 align:start position:0% that's one application where people have proposed<00:07:45.479> where<00:07:45.639> we<00:07:45.759> could<00:07:46.039> use<00:07:46.440> wi 00:07:46.790 --> 00:07:46.800 align:start position:0% proposed where we could use wi 00:07:46.800 --> 00:07:48.230 align:start position:0% proposed where we could use wi encryption<00:07:47.440> so<00:07:47.639> just<00:07:47.759> looking<00:07:47.960> at<00:07:48.120> this 00:07:48.230 --> 00:07:48.240 align:start position:0% encryption so just looking at this 00:07:48.240 --> 00:07:49.670 align:start position:0% encryption so just looking at this particular<00:07:48.560> use<00:07:48.800> case<00:07:49.000> can<00:07:49.120> you<00:07:49.280> describe<00:07:49.599> to 00:07:49.670 --> 00:07:49.680 align:start position:0% particular use case can you describe to 00:07:49.680 --> 00:07:52.270 align:start position:0% particular use case can you describe to us<00:07:49.840> is<00:07:50.000> this<00:07:50.440> is<00:07:50.639> is<00:07:50.879> this<00:07:51.599> uh<00:07:51.720> feasible<00:07:52.159> right 00:07:52.270 --> 00:07:52.280 align:start position:0% us is this is is this uh feasible right 00:07:52.280 --> 00:07:54.629 align:start position:0% us is this is is this uh feasible right now<00:07:52.440> do<00:07:52.560> we<00:07:52.680> need<00:07:53.120> custom<00:07:53.680> scheme<00:07:54.120> or<00:07:54.400> do<00:07:54.520> we 00:07:54.629 --> 00:07:54.639 align:start position:0% now do we need custom scheme or do we 00:07:54.639 --> 00:07:58.230 align:start position:0% now do we need custom scheme or do we need<00:07:54.879> generalized<00:07:55.440> wi<00:07:56.159> encryption<00:07:57.159> um<00:07:57.800> so<00:07:58.199> I 00:07:58.230 --> 00:07:58.240 align:start position:0% need generalized wi encryption um so I 00:07:58.240 --> 00:08:01.230 align:start position:0% need generalized wi encryption um so I mean<00:07:58.520> just<00:07:58.960> uh<00:07:59.520> probably<00:07:59.840> before<00:08:00.080> the<00:08:00.240> tldr<00:08:01.039> is 00:08:01.230 --> 00:08:01.240 align:start position:0% mean just uh probably before the tldr is 00:08:01.240 --> 00:08:03.149 align:start position:0% mean just uh probably before the tldr is that<00:08:01.520> actually<00:08:01.840> this<00:08:01.960> is<00:08:02.159> one<00:08:02.280> of<00:08:02.599> the<00:08:02.759> recent 00:08:03.149 --> 00:08:03.159 align:start position:0% that actually this is one of the recent 00:08:03.159 --> 00:08:05.350 align:start position:0% that actually this is one of the recent advancements<00:08:03.919> where<00:08:04.520> witness<00:08:04.879> encryption 00:08:05.350 --> 00:08:05.360 align:start position:0% advancements where witness encryption 00:08:05.360 --> 00:08:07.869 align:start position:0% advancements where witness encryption for<00:08:05.520> a<00:08:05.759> specific<00:08:06.360> language<00:08:07.000> can<00:08:07.240> enable 00:08:07.869 --> 00:08:07.879 align:start position:0% for a specific language can enable 00:08:07.879 --> 00:08:09.950 align:start position:0% for a specific language can enable exactly<00:08:08.280> this<00:08:08.520> functionality<00:08:09.479> which<00:08:09.639> is<00:08:09.759> that 00:08:09.950 --> 00:08:09.960 align:start position:0% exactly this functionality which is that 00:08:09.960 --> 00:08:11.670 align:start position:0% exactly this functionality which is that let's<00:08:10.120> say<00:08:10.280> that<00:08:10.400> I<00:08:10.520> have<00:08:10.680> n<00:08:11.039> signers<00:08:11.440> for 00:08:11.670 --> 00:08:11.680 align:start position:0% let's say that I have n signers for 00:08:11.680 --> 00:08:13.469 align:start position:0% let's say that I have n signers for something<00:08:12.240> and<00:08:12.599> I<00:08:12.720> want<00:08:12.840> to<00:08:13.000> be<00:08:13.120> able<00:08:13.319> to 00:08:13.469 --> 00:08:13.479 align:start position:0% something and I want to be able to 00:08:13.479 --> 00:08:16.110 align:start position:0% something and I want to be able to decrypt<00:08:13.960> something<00:08:14.400> as<00:08:14.639> long<00:08:14.919> as<00:08:15.120> I<00:08:15.280> have<00:08:15.879> say 00:08:16.110 --> 00:08:16.120 align:start position:0% decrypt something as long as I have say 00:08:16.120 --> 00:08:18.670 align:start position:0% decrypt something as long as I have say t<00:08:16.360> out<00:08:16.520> of<00:08:16.680> n<00:08:16.960> signatures<00:08:17.800> I<00:08:17.919> can<00:08:18.080> encrypt<00:08:18.520> a 00:08:18.670 --> 00:08:18.680 align:start position:0% t out of n signatures I can encrypt a 00:08:18.680 --> 00:08:21.469 align:start position:0% t out of n signatures I can encrypt a message<00:08:19.400> and<00:08:19.560> the<00:08:19.720> puzzle<00:08:20.159> really<00:08:20.680> is<00:08:21.000> that<00:08:21.400> I 00:08:21.469 --> 00:08:21.479 align:start position:0% message and the puzzle really is that I 00:08:21.479 --> 00:08:23.710 align:start position:0% message and the puzzle really is that I need<00:08:21.639> to<00:08:21.840> have<00:08:22.000> t<00:08:22.240> out<00:08:22.400> of<00:08:22.520> end<00:08:22.759> signatures<00:08:23.560> and 00:08:23.710 --> 00:08:23.720 align:start position:0% need to have t out of end signatures and 00:08:23.720 --> 00:08:25.550 align:start position:0% need to have t out of end signatures and there<00:08:23.919> has<00:08:24.240> been<00:08:24.440> a<00:08:24.599> recent<00:08:24.960> construction 00:08:25.550 --> 00:08:25.560 align:start position:0% there has been a recent construction 00:08:25.560 --> 00:08:27.749 align:start position:0% there has been a recent construction even<00:08:25.879> implemented<00:08:26.440> to<00:08:26.599> show<00:08:26.919> that<00:08:27.479> this 00:08:27.749 --> 00:08:27.759 align:start position:0% even implemented to show that this 00:08:27.759 --> 00:08:30.670 align:start position:0% even implemented to show that this functionality<00:08:28.680> is<00:08:29.120> uh<00:08:29.520> is<00:08:29.599> feasible<00:08:30.360> but<00:08:30.560> let 00:08:30.670 --> 00:08:30.680 align:start position:0% functionality is uh is feasible but let 00:08:30.680 --> 00:08:32.389 align:start position:0% functionality is uh is feasible but let me<00:08:30.840> just<00:08:30.960> say<00:08:31.159> that<00:08:31.360> general<00:08:31.720> purpose<00:08:32.080> witness 00:08:32.389 --> 00:08:32.399 align:start position:0% me just say that general purpose witness 00:08:32.399 --> 00:08:35.149 align:start position:0% me just say that general purpose witness encryption<00:08:32.959> would<00:08:33.120> be<00:08:33.640> to<00:08:33.919> ask<00:08:34.440> can<00:08:34.599> I<00:08:34.760> do<00:08:35.000> this 00:08:35.149 --> 00:08:35.159 align:start position:0% encryption would be to ask can I do this 00:08:35.159 --> 00:08:38.190 align:start position:0% encryption would be to ask can I do this for<00:08:35.599> an<00:08:35.959> arbitrary<00:08:36.839> puzzle<00:08:37.640> and<00:08:37.760> the<00:08:37.880> answer 00:08:38.190 --> 00:08:38.200 align:start position:0% for an arbitrary puzzle and the answer 00:08:38.200 --> 00:08:40.310 align:start position:0% for an arbitrary puzzle and the answer is<00:08:38.680> today<00:08:39.039> we<00:08:39.159> only<00:08:39.360> know<00:08:39.560> how<00:08:39.680> to<00:08:39.839> construct 00:08:40.310 --> 00:08:40.320 align:start position:0% is today we only know how to construct 00:08:40.320 --> 00:08:43.269 align:start position:0% is today we only know how to construct that<00:08:40.800> from<00:08:41.159> obfuscation<00:08:42.000> itself<00:08:42.440> so<00:08:42.839> G 00:08:43.269 --> 00:08:43.279 align:start position:0% that from obfuscation itself so G 00:08:43.279 --> 00:08:45.150 align:start position:0% that from obfuscation itself so G purpose<00:08:43.560> witness<00:08:43.880> encryption<00:08:44.320> is<00:08:44.480> still<00:08:44.880> far 00:08:45.150 --> 00:08:45.160 align:start position:0% purpose witness encryption is still far 00:08:45.160 --> 00:08:47.389 align:start position:0% purpose witness encryption is still far from<00:08:45.519> being<00:08:46.240> practical<00:08:46.720> but<00:08:46.880> for<00:08:47.160> this 00:08:47.389 --> 00:08:47.399 align:start position:0% from being practical but for this 00:08:47.399 --> 00:08:49.750 align:start position:0% from being practical but for this specific<00:08:47.920> application<00:08:48.880> it<00:08:49.000> is<00:08:49.279> possible<00:08:49.600> to 00:08:49.750 --> 00:08:49.760 align:start position:0% specific application it is possible to 00:08:49.760 --> 00:08:51.550 align:start position:0% specific application it is possible to do<00:08:49.880> it<00:08:50.040> and<00:08:50.399> I<00:08:50.480> want<00:08:50.600> to<00:08:50.720> say<00:08:50.920> that<00:08:51.040> if<00:08:51.120> you<00:08:51.320> also 00:08:51.550 --> 00:08:51.560 align:start position:0% do it and I want to say that if you also 00:08:51.560 --> 00:08:53.990 align:start position:0% do it and I want to say that if you also Trace<00:08:51.920> history<00:08:52.600> witness<00:08:52.959> encryption<00:08:53.600> it<00:08:53.720> goes 00:08:53.990 --> 00:08:54.000 align:start position:0% Trace history witness encryption it goes 00:08:54.000 --> 00:08:55.949 align:start position:0% Trace history witness encryption it goes back<00:08:54.120> to<00:08:54.360> even<00:08:54.640> like<00:08:54.800> when<00:08:54.880> you<00:08:55.000> think<00:08:55.160> of<00:08:55.279> cca2 00:08:55.949 --> 00:08:55.959 align:start position:0% back to even like when you think of cca2 00:08:55.959 --> 00:08:58.110 align:start position:0% back to even like when you think of cca2 encryption<00:08:56.800> it<00:08:57.040> was<00:08:57.240> a<00:08:57.399> limited<00:08:57.760> form<00:08:57.959> of 00:08:58.110 --> 00:08:58.120 align:start position:0% encryption it was a limited form of 00:08:58.120 --> 00:09:00.150 align:start position:0% encryption it was a limited form of witness<00:08:58.440> encryption<00:08:59.200> and<00:08:59.480> since<00:08:59.720> then<00:08:59.920> there 00:09:00.150 --> 00:09:00.160 align:start position:0% witness encryption and since then there 00:09:00.160 --> 00:09:02.030 align:start position:0% witness encryption and since then there have<00:09:00.320> been<00:09:00.560> some<00:09:00.880> progress<00:09:01.600> but<00:09:01.720> I<00:09:01.800> want<00:09:01.920> to 00:09:02.030 --> 00:09:02.040 align:start position:0% have been some progress but I want to 00:09:02.040 --> 00:09:03.910 align:start position:0% have been some progress but I want to say<00:09:02.160> general<00:09:02.560> purpose<00:09:02.839> witness<00:09:03.240> encryption 00:09:03.910 --> 00:09:03.920 align:start position:0% say general purpose witness encryption 00:09:03.920 --> 00:09:07.190 align:start position:0% say general purpose witness encryption is<00:09:04.120> still<00:09:04.680> uh<00:09:04.880> far<00:09:05.160> way<00:09:05.560> out<00:09:06.560> well<00:09:06.800> definitely 00:09:07.190 --> 00:09:07.200 align:start position:0% is still uh far way out well definitely 00:09:07.200 --> 00:09:09.670 align:start position:0% is still uh far way out well definitely zooming<00:09:07.560> on<00:09:07.720> that<00:09:08.160> um<00:09:08.440> in<00:09:08.560> a<00:09:08.680> later<00:09:09.000> question 00:09:09.670 --> 00:09:09.680 align:start position:0% zooming on that um in a later question 00:09:09.680 --> 00:09:12.590 align:start position:0% zooming on that um in a later question but<00:09:09.839> so<00:09:10.120> let's<00:09:10.560> go<00:09:10.800> to<00:09:11.519> functional<00:09:11.920> encryption 00:09:12.590 --> 00:09:12.600 align:start position:0% but so let's go to functional encryption 00:09:12.600 --> 00:09:15.509 align:start position:0% but so let's go to functional encryption and<00:09:13.040> appication<00:09:14.040> I<00:09:14.120> think<00:09:14.360> one<00:09:14.480> of<00:09:14.600> the<00:09:15.120> more 00:09:15.509 --> 00:09:15.519 align:start position:0% and appication I think one of the more 00:09:15.519 --> 00:09:17.949 align:start position:0% and appication I think one of the more recent<00:09:16.200> uh<00:09:16.399> proposals<00:09:17.399> that<00:09:17.640> applies 00:09:17.949 --> 00:09:17.959 align:start position:0% recent uh proposals that applies 00:09:17.959 --> 00:09:20.110 align:start position:0% recent uh proposals that applies functional<00:09:18.240> encryption<00:09:18.800> is<00:09:19.000> to<00:09:19.839> actually 00:09:20.110 --> 00:09:20.120 align:start position:0% functional encryption is to actually 00:09:20.120 --> 00:09:22.470 align:start position:0% functional encryption is to actually adds<00:09:20.440> features<00:09:20.760> to<00:09:20.959> bitcoin<00:09:21.440> to<00:09:22.000> for<00:09:22.240> it<00:09:22.320> to 00:09:22.470 --> 00:09:22.480 align:start position:0% adds features to bitcoin to for it to 00:09:22.480 --> 00:09:24.350 align:start position:0% adds features to bitcoin to for it to become<00:09:22.720> more<00:09:22.880> like<00:09:23.000> ethereum<00:09:23.760> right<00:09:23.880> so<00:09:24.160> there 00:09:24.350 --> 00:09:24.360 align:start position:0% become more like ethereum right so there 00:09:24.360 --> 00:09:26.230 align:start position:0% become more like ethereum right so there this<00:09:24.440> thing<00:09:24.600> called<00:09:24.800> Bitcoin<00:09:25.120> Covenant<00:09:26.040> which 00:09:26.230 --> 00:09:26.240 align:start position:0% this thing called Bitcoin Covenant which 00:09:26.240 --> 00:09:30.389 align:start position:0% this thing called Bitcoin Covenant which is<00:09:27.240> not<00:09:27.839> uh<00:09:28.000> feasible<00:09:29.000> on<00:09:29.079> bitcoin<00:09:29.519> today<00:09:30.200> and 00:09:30.389 --> 00:09:30.399 align:start position:0% is not uh feasible on bitcoin today and 00:09:30.399 --> 00:09:31.949 align:start position:0% is not uh feasible on bitcoin today and people<00:09:30.640> have<00:09:30.760> been<00:09:31.040> proposing<00:09:31.519> to<00:09:31.720> use 00:09:31.949 --> 00:09:31.959 align:start position:0% people have been proposing to use 00:09:31.959 --> 00:09:33.550 align:start position:0% people have been proposing to use functional<00:09:32.320> encryption<00:09:32.920> to<00:09:33.240> to<00:09:33.399> get 00:09:33.550 --> 00:09:33.560 align:start position:0% functional encryption to to get 00:09:33.560 --> 00:09:35.350 align:start position:0% functional encryption to to get confidence<00:09:33.880> for<00:09:34.000> Bitcoin<00:09:34.680> and<00:09:34.760> the<00:09:34.880> use<00:09:35.120> case 00:09:35.350 --> 00:09:35.360 align:start position:0% confidence for Bitcoin and the use case 00:09:35.360 --> 00:09:38.630 align:start position:0% confidence for Bitcoin and the use case there<00:09:35.560> is<00:09:35.720> to<00:09:36.000> say<00:09:36.320> that<00:09:36.640> ecd<00:09:37.200> signing<00:09:37.640> key 00:09:38.630 --> 00:09:38.640 align:start position:0% there is to say that ecd signing key 00:09:38.640 --> 00:09:41.389 align:start position:0% there is to say that ecd signing key must<00:09:38.880> be<00:09:39.000> used<00:09:39.279> in<00:09:39.360> a<00:09:39.519> certain<00:09:39.839> way<00:09:40.600> uh<00:09:40.800> only<00:09:41.160> if 00:09:41.389 --> 00:09:41.399 align:start position:0% must be used in a certain way uh only if 00:09:41.399 --> 00:09:43.310 align:start position:0% must be used in a certain way uh only if a<00:09:41.760> condition<00:09:42.040> on<00:09:42.200> the<00:09:42.360> signing<00:09:42.680> messages<00:09:43.120> is 00:09:43.310 --> 00:09:43.320 align:start position:0% a condition on the signing messages is 00:09:43.320 --> 00:09:46.790 align:start position:0% a condition on the signing messages is true<00:09:44.320> so<00:09:44.560> this<00:09:44.720> requires<00:09:45.519> computation<00:09:46.519> on<00:09:46.680> the 00:09:46.790 --> 00:09:46.800 align:start position:0% true so this requires computation on the 00:09:46.800 --> 00:09:48.509 align:start position:0% true so this requires computation on the message<00:09:47.120> to<00:09:47.200> be<00:09:47.320> signed<00:09:47.880> a<00:09:48.120> condition<00:09:48.279> to<00:09:48.399> be 00:09:48.509 --> 00:09:48.519 align:start position:0% message to be signed a condition to be 00:09:48.519 --> 00:09:51.389 align:start position:0% message to be signed a condition to be checked<00:09:49.480> and<00:09:50.200> uh<00:09:50.440> a<00:09:50.600> signature<00:09:51.079> to<00:09:51.200> be 00:09:51.389 --> 00:09:51.399 align:start position:0% checked and uh a signature to be 00:09:51.399 --> 00:09:53.750 align:start position:0% checked and uh a signature to be generated<00:09:52.399> as<00:09:52.720> as<00:09:52.920> the<00:09:53.079> the<00:09:53.200> function<00:09:53.519> to<00:09:53.600> be 00:09:53.750 --> 00:09:53.760 align:start position:0% generated as as the the function to be 00:09:53.760 --> 00:09:55.990 align:start position:0% generated as as the the function to be computed<00:09:54.760> um<00:09:54.959> can<00:09:55.079> you<00:09:55.200> comment<00:09:55.440> briefly<00:09:55.880> on 00:09:55.990 --> 00:09:56.000 align:start position:0% computed um can you comment briefly on 00:09:56.000 --> 00:09:57.310 align:start position:0% computed um can you comment briefly on this<00:09:56.160> particular<00:09:56.440> use<00:09:56.680> case<00:09:56.800> and<00:09:57.000> whether 00:09:57.310 --> 00:09:57.320 align:start position:0% this particular use case and whether 00:09:57.320 --> 00:10:00.030 align:start position:0% this particular use case and whether that<00:09:57.480> is<00:09:57.680> feasible<00:09:58.320> currently<00:09:58.880> using 00:10:00.030 --> 00:10:00.040 align:start position:0% that is feasible currently using 00:10:00.040 --> 00:10:02.269 align:start position:0% that is feasible currently using uh<00:10:00.120> using<00:10:00.440> alisation<00:10:01.200> or<00:10:01.680> functional 00:10:02.269 --> 00:10:02.279 align:start position:0% uh using alisation or functional 00:10:02.279 --> 00:10:05.030 align:start position:0% uh using alisation or functional encryption<00:10:03.279> okay<00:10:03.959> um<00:10:04.399> it's<00:10:04.560> going<00:10:04.680> to<00:10:04.760> be<00:10:04.880> hard 00:10:05.030 --> 00:10:05.040 align:start position:0% encryption okay um it's going to be hard 00:10:05.040 --> 00:10:07.750 align:start position:0% encryption okay um it's going to be hard to<00:10:05.200> comment<00:10:05.600> but<00:10:05.760> I<00:10:05.839> will<00:10:06.079> say<00:10:06.440> that<00:10:07.240> um<00:10:07.519> if<00:10:07.640> you 00:10:07.750 --> 00:10:07.760 align:start position:0% to comment but I will say that um if you 00:10:07.760 --> 00:10:09.829 align:start position:0% to comment but I will say that um if you look<00:10:07.880> at<00:10:08.000> the<00:10:08.200> construction<00:10:09.200> I<00:10:09.320> want<00:10:09.560> someone 00:10:09.829 --> 00:10:09.839 align:start position:0% look at the construction I want someone 00:10:09.839 --> 00:10:11.509 align:start position:0% look at the construction I want someone to<00:10:10.040> implement<00:10:10.440> it<00:10:10.600> to<00:10:10.760> really<00:10:11.040> see<00:10:11.360> the 00:10:11.509 --> 00:10:11.519 align:start position:0% to implement it to really see the 00:10:11.519 --> 00:10:14.230 align:start position:0% to implement it to really see the overhead<00:10:12.399> although<00:10:12.800> just<00:10:13.040> looking<00:10:13.440> at<00:10:13.839> how<00:10:14.079> I 00:10:14.230 --> 00:10:14.240 align:start position:0% overhead although just looking at how I 00:10:14.240 --> 00:10:16.550 align:start position:0% overhead although just looking at how I have<00:10:14.399> to<00:10:14.959> implement<00:10:15.480> the<00:10:15.640> circuit<00:10:16.160> I<00:10:16.279> need<00:10:16.399> to 00:10:16.550 --> 00:10:16.560 align:start position:0% have to implement the circuit I need to 00:10:16.560 --> 00:10:18.630 align:start position:0% have to implement the circuit I need to embed<00:10:16.920> arithmetization<00:10:17.480> of<00:10:17.959> One<00:10:18.200> Prime<00:10:18.440> to 00:10:18.630 --> 00:10:18.640 align:start position:0% embed arithmetization of One Prime to 00:10:18.640 --> 00:10:20.150 align:start position:0% embed arithmetization of One Prime to another<00:10:19.000> Prime<00:10:19.240> for<00:10:19.399> elliptic<00:10:19.800> curve 00:10:20.150 --> 00:10:20.160 align:start position:0% another Prime for elliptic curve 00:10:20.160 --> 00:10:22.630 align:start position:0% another Prime for elliptic curve operations<00:10:21.160> I<00:10:21.279> think<00:10:21.480> the<00:10:21.680> overhead<00:10:22.519> the 00:10:22.630 --> 00:10:22.640 align:start position:0% operations I think the overhead the 00:10:22.640 --> 00:10:24.829 align:start position:0% operations I think the overhead the margins<00:10:23.040> are<00:10:23.200> going<00:10:23.440> to<00:10:23.600> be<00:10:23.760> a<00:10:23.920> lot<00:10:24.279> but<00:10:24.720> that 00:10:24.829 --> 00:10:24.839 align:start position:0% margins are going to be a lot but that 00:10:24.839 --> 00:10:27.590 align:start position:0% margins are going to be a lot but that should<00:10:25.040> not<00:10:25.200> deter<00:10:25.720> people<00:10:26.079> from<00:10:26.440> trying<00:10:26.760> to 00:10:27.590 --> 00:10:27.600 align:start position:0% should not deter people from trying to 00:10:27.600 --> 00:10:30.389 align:start position:0% should not deter people from trying to uh<00:10:28.320> uh<00:10:28.519> implement<00:10:29.040> this<00:10:29.480> but<00:10:29.800> just<00:10:29.920> to<00:10:30.120> maybe 00:10:30.389 --> 00:10:30.399 align:start position:0% uh uh implement this but just to maybe 00:10:30.399 --> 00:10:32.750 align:start position:0% uh uh implement this but just to maybe give<00:10:30.760> a<00:10:30.880> rough<00:10:31.160> idea<00:10:31.720> of<00:10:32.440> not<00:10:32.600> the 00:10:32.750 --> 00:10:32.760 align:start position:0% give a rough idea of not the 00:10:32.760 --> 00:10:35.310 align:start position:0% give a rough idea of not the construction<00:10:33.480> but<00:10:34.320> um<00:10:34.600> where<00:10:34.760> it<00:10:34.920> comes<00:10:35.120> from 00:10:35.310 --> 00:10:35.320 align:start position:0% construction but um where it comes from 00:10:35.320 --> 00:10:37.509 align:start position:0% construction but um where it comes from functional<00:10:35.680> encryption<00:10:36.240> is<00:10:36.440> that<00:10:36.800> so 00:10:37.509 --> 00:10:37.519 align:start position:0% functional encryption is that so 00:10:37.519 --> 00:10:39.190 align:start position:0% functional encryption is that so functional<00:10:37.959> encryption<00:10:38.639> again<00:10:38.880> just<00:10:39.040> like 00:10:39.190 --> 00:10:39.200 align:start position:0% functional encryption again just like 00:10:39.200 --> 00:10:40.670 align:start position:0% functional encryption again just like witness<00:10:39.560> encryption<00:10:40.040> if<00:10:40.120> you<00:10:40.279> want<00:10:40.480> for 00:10:40.670 --> 00:10:40.680 align:start position:0% witness encryption if you want for 00:10:40.680 --> 00:10:42.509 align:start position:0% witness encryption if you want for general<00:10:41.079> purpose<00:10:41.440> polinomial<00:10:41.959> size 00:10:42.509 --> 00:10:42.519 align:start position:0% general purpose polinomial size 00:10:42.519 --> 00:10:44.949 align:start position:0% general purpose polinomial size computation<00:10:43.519> you<00:10:43.920> the<00:10:44.040> only<00:10:44.279> way<00:10:44.440> we<00:10:44.600> know<00:10:44.839> is 00:10:44.949 --> 00:10:44.959 align:start position:0% computation you the only way we know is 00:10:44.959 --> 00:10:46.590 align:start position:0% computation you the only way we know is to<00:10:45.120> do<00:10:45.360> it<00:10:45.480> from<00:10:45.680> indistinguishability 00:10:46.590 --> 00:10:46.600 align:start position:0% to do it from indistinguishability 00:10:46.600 --> 00:10:50.150 align:start position:0% to do it from indistinguishability ofation<00:10:47.600> but<00:10:48.120> uh<00:10:48.240> a<00:10:48.399> very<00:10:48.639> restricted<00:10:49.240> form<00:10:49.760> of 00:10:50.150 --> 00:10:50.160 align:start position:0% ofation but uh a very restricted form of 00:10:50.160 --> 00:10:52.870 align:start position:0% ofation but uh a very restricted form of functionality<00:10:51.079> is<00:10:51.279> an<00:10:51.440> inner<00:10:51.880> product<00:10:52.600> okay<00:10:52.760> I 00:10:52.870 --> 00:10:52.880 align:start position:0% functionality is an inner product okay I 00:10:52.880 --> 00:10:54.269 align:start position:0% functionality is an inner product okay I take<00:10:53.040> two<00:10:53.279> vectors<00:10:53.600> I<00:10:53.720> want<00:10:53.800> to<00:10:53.920> compute<00:10:54.200> the 00:10:54.269 --> 00:10:54.279 align:start position:0% take two vectors I want to compute the 00:10:54.279 --> 00:10:57.310 align:start position:0% take two vectors I want to compute the inner<00:10:54.639> product<00:10:55.200> can<00:10:55.360> I<00:10:55.480> do<00:10:55.720> this<00:10:55.959> under<00:10:56.959> uh<00:10:57.120> can 00:10:57.310 --> 00:10:57.320 align:start position:0% inner product can I do this under uh can 00:10:57.320 --> 00:10:59.389 align:start position:0% inner product can I do this under uh can this<00:10:57.480> be<00:10:57.680> the<00:10:57.839> function<00:10:58.519> and<00:10:58.680> can<00:10:58.800> I<00:10:58.880> do<00:10:59.040> this 00:10:59.389 --> 00:10:59.399 align:start position:0% this be the function and can I do this 00:10:59.399 --> 00:11:01.629 align:start position:0% this be the function and can I do this under<00:11:00.000> uh<00:11:00.120> functional<00:11:00.560> encryption<00:11:01.360> and<00:11:01.519> there 00:11:01.629 --> 00:11:01.639 align:start position:0% under uh functional encryption and there 00:11:01.639 --> 00:11:04.030 align:start position:0% under uh functional encryption and there are<00:11:01.920> constructions<00:11:02.720> actually<00:11:03.160> there<00:11:03.320> are<00:11:03.920> I 00:11:04.030 --> 00:11:04.040 align:start position:0% are constructions actually there are I 00:11:04.040 --> 00:11:06.310 align:start position:0% are constructions actually there are I want<00:11:04.200> to<00:11:04.320> say<00:11:04.560> feasible<00:11:05.279> constructions<00:11:05.920> to<00:11:06.120> do 00:11:06.310 --> 00:11:06.320 align:start position:0% want to say feasible constructions to do 00:11:06.320 --> 00:11:08.670 align:start position:0% want to say feasible constructions to do this<00:11:06.959> now<00:11:07.120> this<00:11:07.360> recent<00:11:07.639> work<00:11:07.839> that<00:11:08.000> has<00:11:08.120> shown 00:11:08.670 --> 00:11:08.680 align:start position:0% this now this recent work that has shown 00:11:08.680 --> 00:11:11.069 align:start position:0% this now this recent work that has shown that<00:11:09.079> we<00:11:09.279> can<00:11:09.600> implement<00:11:10.320> this<00:11:10.480> functionality 00:11:11.069 --> 00:11:11.079 align:start position:0% that we can implement this functionality 00:11:11.079 --> 00:11:14.389 align:start position:0% that we can implement this functionality that<00:11:11.279> we<00:11:11.519> said<00:11:11.839> where<00:11:12.560> if<00:11:13.440> um<00:11:13.720> a<00:11:13.839> certain 00:11:14.389 --> 00:11:14.399 align:start position:0% that we said where if um a certain 00:11:14.399 --> 00:11:15.910 align:start position:0% that we said where if um a certain condition<00:11:14.760> and<00:11:14.920> this<00:11:15.279> condition<00:11:15.560> really<00:11:15.839> you 00:11:15.910 --> 00:11:15.920 align:start position:0% condition and this condition really you 00:11:15.920 --> 00:11:17.550 align:start position:0% condition and this condition really you can<00:11:16.120> think<00:11:16.279> of<00:11:16.440> it<00:11:16.600> as<00:11:16.760> verifying<00:11:17.160> a<00:11:17.279> zero 00:11:17.550 --> 00:11:17.560 align:start position:0% can think of it as verifying a zero 00:11:17.560 --> 00:11:21.110 align:start position:0% can think of it as verifying a zero knowledge<00:11:18.160> proof<00:11:19.160> then<00:11:19.959> I 00:11:21.110 --> 00:11:21.120 align:start position:0% knowledge proof then I 00:11:21.120 --> 00:11:24.949 align:start position:0% knowledge proof then I will<00:11:22.120> sign<00:11:22.639> a<00:11:22.839> particular<00:11:23.639> message<00:11:24.240> and<00:11:24.720> this 00:11:24.949 --> 00:11:24.959 align:start position:0% will sign a particular message and this 00:11:24.959 --> 00:11:27.550 align:start position:0% will sign a particular message and this can<00:11:25.160> be<00:11:25.399> again<00:11:25.680> translated<00:11:26.480> into<00:11:27.160> whatever 00:11:27.550 --> 00:11:27.560 align:start position:0% can be again translated into whatever 00:11:27.560 --> 00:11:29.829 align:start position:0% can be again translated into whatever functionality<00:11:28.240> you<00:11:28.399> want<00:11:28.680> in<00:11:28.800> the<00:11:28.880> under 00:11:29.829 --> 00:11:29.839 align:start position:0% functionality you want in the under 00:11:29.839 --> 00:11:32.310 align:start position:0% functionality you want in the under uh<00:11:30.000> blockchain<00:11:30.440> layer<00:11:31.120> and<00:11:31.560> just<00:11:31.800> using<00:11:32.160> this 00:11:32.310 --> 00:11:32.320 align:start position:0% uh blockchain layer and just using this 00:11:32.320 --> 00:11:35.190 align:start position:0% uh blockchain layer and just using this inner<00:11:32.720> product<00:11:33.040> functional<00:11:33.959> encryption<00:11:34.959> you 00:11:35.190 --> 00:11:35.200 align:start position:0% inner product functional encryption you 00:11:35.200 --> 00:11:38.350 align:start position:0% inner product functional encryption you can<00:11:36.000> construct<00:11:37.000> uh<00:11:37.120> one<00:11:37.480> that<00:11:37.639> can<00:11:37.920> do<00:11:38.160> this 00:11:38.350 --> 00:11:38.360 align:start position:0% can construct uh one that can do this 00:11:38.360 --> 00:11:40.790 align:start position:0% can construct uh one that can do this functionality<00:11:39.320> which<00:11:39.440> is<00:11:39.760> verify<00:11:40.200> a<00:11:40.399> certain 00:11:40.790 --> 00:11:40.800 align:start position:0% functionality which is verify a certain 00:11:40.800 --> 00:11:43.590 align:start position:0% functionality which is verify a certain kind<00:11:41.079> of<00:11:41.279> proof<00:11:41.959> and<00:11:42.160> then<00:11:42.560> sign<00:11:43.079> say<00:11:43.360> under 00:11:43.590 --> 00:11:43.600 align:start position:0% kind of proof and then sign say under 00:11:43.600 --> 00:11:45.069 align:start position:0% kind of proof and then sign say under the<00:11:43.720> Snore<00:11:44.079> signatures<00:11:44.560> which<00:11:44.680> are<00:11:44.800> needed 00:11:45.069 --> 00:11:45.079 align:start position:0% the Snore signatures which are needed 00:11:45.079 --> 00:11:47.750 align:start position:0% the Snore signatures which are needed for<00:11:45.839> uh<00:11:45.959> the<00:11:46.079> Bitcoin<00:11:46.519> protocol<00:11:47.320> again<00:11:47.560> I<00:11:47.639> want 00:11:47.750 --> 00:11:47.760 align:start position:0% for uh the Bitcoin protocol again I want 00:11:47.760 --> 00:11:50.030 align:start position:0% for uh the Bitcoin protocol again I want to<00:11:47.880> say<00:11:48.120> that<00:11:48.519> um<00:11:49.160> the<00:11:49.360> fact<00:11:49.600> that<00:11:49.800> these 00:11:50.030 --> 00:11:50.040 align:start position:0% to say that um the fact that these 00:11:50.040 --> 00:11:52.430 align:start position:0% to say that um the fact that these Primitives<00:11:50.639> can<00:11:50.839> be<00:11:51.040> useful<00:11:51.440> for<00:11:51.760> these<00:11:52.279> is 00:11:52.430 --> 00:11:52.440 align:start position:0% Primitives can be useful for these is 00:11:52.440 --> 00:11:56.910 align:start position:0% Primitives can be useful for these is not<00:11:52.680> surprising<00:11:53.680> these<00:11:53.920> are<00:11:54.480> like<00:11:54.760> really<00:11:55.920> um 00:11:56.910 --> 00:11:56.920 align:start position:0% not surprising these are like really um 00:11:56.920 --> 00:11:58.990 align:start position:0% not surprising these are like really um uh<00:11:57.120> very<00:11:57.639> strong<00:11:57.920> Primitives<00:11:58.480> that<00:11:58.680> have<00:11:58.920> you 00:11:58.990 --> 00:11:59.000 align:start position:0% uh very strong Primitives that have you 00:11:59.000 --> 00:12:01.509 align:start position:0% uh very strong Primitives that have you know<00:11:59.360> really<00:11:59.600> a<00:11:59.800> vast<00:12:00.079> range<00:12:00.320> of<00:12:00.560> applications 00:12:01.509 --> 00:12:01.519 align:start position:0% know really a vast range of applications 00:12:01.519 --> 00:12:03.430 align:start position:0% know really a vast range of applications but<00:12:01.920> discovering<00:12:02.360> where<00:12:02.639> it<00:12:02.760> is<00:12:03.040> practical 00:12:03.430 --> 00:12:03.440 align:start position:0% but discovering where it is practical 00:12:03.440 --> 00:12:05.790 align:start position:0% but discovering where it is practical and<00:12:03.800> feasible<00:12:04.800> uh<00:12:04.920> is<00:12:05.079> still<00:12:05.360> really<00:12:05.639> an 00:12:05.790 --> 00:12:05.800 align:start position:0% and feasible uh is still really an 00:12:05.800 --> 00:12:07.310 align:start position:0% and feasible uh is still really an ongoing<00:12:06.600> uh 00:12:07.310 --> 00:12:07.320 align:start position:0% ongoing uh 00:12:07.320 --> 00:12:09.710 align:start position:0% ongoing uh research<00:12:08.320> got<00:12:08.440> it<00:12:08.720> so<00:12:08.959> perhaps<00:12:09.240> let's<00:12:09.480> zoom 00:12:09.710 --> 00:12:09.720 align:start position:0% research got it so perhaps let's zoom 00:12:09.720 --> 00:12:12.590 align:start position:0% research got it so perhaps let's zoom out<00:12:10.279> um<00:12:10.639> a<00:12:10.720> little<00:12:10.880> bit<00:12:11.040> more<00:12:11.240> to<00:12:11.880> more<00:12:12.160> diac 00:12:12.590 --> 00:12:12.600 align:start position:0% out um a little bit more to more diac 00:12:12.600 --> 00:12:15.670 align:start position:0% out um a little bit more to more diac the<00:12:12.720> con<00:12:12.959> of<00:12:13.040> DC<00:12:13.800> more<00:12:14.000> broadly<00:12:14.839> I<00:12:14.920> think<00:12:15.480> one 00:12:15.670 --> 00:12:15.680 align:start position:0% the con of DC more broadly I think one 00:12:15.680 --> 00:12:17.829 align:start position:0% the con of DC more broadly I think one way<00:12:15.800> to<00:12:16.000> look<00:12:16.160> at<00:12:16.680> where<00:12:16.920> we<00:12:17.079> can<00:12:17.279> apply 00:12:17.829 --> 00:12:17.839 align:start position:0% way to look at where we can apply 00:12:17.839 --> 00:12:20.949 align:start position:0% way to look at where we can apply programmable<00:12:18.600> cryptography<00:12:19.600> is<00:12:19.839> wherever<00:12:20.800> a 00:12:20.949 --> 00:12:20.959 align:start position:0% programmable cryptography is wherever a 00:12:20.959 --> 00:12:23.030 align:start position:0% programmable cryptography is wherever a te<00:12:21.519> has<00:12:21.639> been<00:12:21.839> used<00:12:22.519> right<00:12:22.600> so<00:12:22.760> there's<00:12:22.880> two 00:12:23.030 --> 00:12:23.040 align:start position:0% te has been used right so there's two 00:12:23.040 --> 00:12:25.829 align:start position:0% te has been used right so there's two angle<00:12:23.320> to<00:12:23.480> this<00:12:24.120> um<00:12:24.519> if<00:12:24.680> a<00:12:24.839> te<00:12:25.320> is<00:12:25.519> currently 00:12:25.829 --> 00:12:25.839 align:start position:0% angle to this um if a te is currently 00:12:25.839 --> 00:12:29.629 align:start position:0% angle to this um if a te is currently needed<00:12:26.360> can<00:12:26.480> we<00:12:26.680> remove<00:12:27.519> that<00:12:28.519> uh<00:12:29.199> Reliance<00:12:29.560> on 00:12:29.629 --> 00:12:29.639 align:start position:0% needed can we remove that uh Reliance on 00:12:29.639 --> 00:12:32.590 align:start position:0% needed can we remove that uh Reliance on the<00:12:29.839> te<00:12:30.839> and<00:12:31.279> you<00:12:31.399> know<00:12:31.560> we're<00:12:32.000> else<00:12:32.279> can<00:12:32.440> we 00:12:32.590 --> 00:12:32.600 align:start position:0% the te and you know we're else can we 00:12:32.600 --> 00:12:35.389 align:start position:0% the te and you know we're else can we insert<00:12:32.959> this<00:12:33.440> trust<00:12:33.800> execution<00:12:34.399> environment 00:12:35.389 --> 00:12:35.399 align:start position:0% insert this trust execution environment 00:12:35.399 --> 00:12:37.389 align:start position:0% insert this trust execution environment um<00:12:36.079> where<00:12:36.480> it's<00:12:36.720> actually<00:12:37.079> could<00:12:37.240> actually 00:12:37.389 --> 00:12:37.399 align:start position:0% um where it's actually could actually 00:12:37.399 --> 00:12:39.389 align:start position:0% um where it's actually could actually use<00:12:37.600> cryptography<00:12:38.440> right<00:12:38.800> and<00:12:38.920> so<00:12:39.120> can<00:12:39.240> you 00:12:39.389 --> 00:12:39.399 align:start position:0% use cryptography right and so can you 00:12:39.399 --> 00:12:40.870 align:start position:0% use cryptography right and so can you actually<00:12:39.639> comment 00:12:40.870 --> 00:12:40.880 align:start position:0% actually comment 00:12:40.880 --> 00:12:43.150 align:start position:0% actually comment on<00:12:41.880> the<00:12:42.079> difference<00:12:42.440> between<00:12:42.839> trust 00:12:43.150 --> 00:12:43.160 align:start position:0% on the difference between trust 00:12:43.160 --> 00:12:45.150 align:start position:0% on the difference between trust execution<00:12:43.560> environments<00:12:43.920> trust<00:12:44.240> Hardware 00:12:45.150 --> 00:12:45.160 align:start position:0% execution environments trust Hardware 00:12:45.160 --> 00:12:48.069 align:start position:0% execution environments trust Hardware versus<00:12:46.000> programmable<00:12:46.639> cryptography<00:12:47.199> using 00:12:48.069 --> 00:12:48.079 align:start position:0% versus programmable cryptography using 00:12:48.079 --> 00:12:50.670 align:start position:0% versus programmable cryptography using officiation<00:12:49.079> so<00:12:49.399> as<00:12:49.480> I<00:12:49.600> mentioned<00:12:50.040> before 00:12:50.670 --> 00:12:50.680 align:start position:0% officiation so as I mentioned before 00:12:50.680 --> 00:12:53.829 align:start position:0% officiation so as I mentioned before right<00:12:51.000> te<00:12:51.639> can<00:12:51.920> give<00:12:52.079> you<00:12:52.560> what<00:12:52.720> is<00:12:52.920> called<00:12:53.680> uh 00:12:53.829 --> 00:12:53.839 align:start position:0% right te can give you what is called uh 00:12:53.839 --> 00:12:55.870 align:start position:0% right te can give you what is called uh close<00:12:54.120> to<00:12:54.320> what's<00:12:54.519> called<00:12:54.800> a<00:12:55.000> blackbox<00:12:55.600> of 00:12:55.870 --> 00:12:55.880 align:start position:0% close to what's called a blackbox of 00:12:55.880 --> 00:12:58.110 align:start position:0% close to what's called a blackbox of fisc<00:12:56.440> and<00:12:56.720> that's<00:12:56.839> a<00:12:57.000> technical<00:12:57.440> term<00:12:57.959> but 00:12:58.110 --> 00:12:58.120 align:start position:0% fisc and that's a technical term but 00:12:58.120 --> 00:13:00.110 align:start position:0% fisc and that's a technical term but what<00:12:58.240> it<00:12:58.440> really<00:12:58.680> means<00:12:59.240> that<00:12:59.480> it<00:12:59.600> can<00:12:59.920> give 00:13:00.110 --> 00:13:00.120 align:start position:0% what it really means that it can give 00:13:00.120 --> 00:13:04.629 align:start position:0% what it really means that it can give you<00:13:00.519> access<00:13:00.800> to<00:13:01.000> a<00:13:01.600> just<00:13:02.120> the<00:13:02.320> input<00:13:03.160> output<00:13:04.160> uh 00:13:04.629 --> 00:13:04.639 align:start position:0% you access to a just the input output uh 00:13:04.639 --> 00:13:07.269 align:start position:0% you access to a just the input output uh behavior<00:13:05.199> of<00:13:05.320> a<00:13:05.600> functionality<00:13:06.600> now<00:13:07.000> in 00:13:07.269 --> 00:13:07.279 align:start position:0% behavior of a functionality now in 00:13:07.279 --> 00:13:09.030 align:start position:0% behavior of a functionality now in general<00:13:07.800> if<00:13:07.880> you<00:13:08.000> want<00:13:08.160> to<00:13:08.320> realize<00:13:08.720> it 00:13:09.030 --> 00:13:09.040 align:start position:0% general if you want to realize it 00:13:09.040 --> 00:13:11.030 align:start position:0% general if you want to realize it without<00:13:09.560> any<00:13:09.800> hardware<00:13:10.240> assumptions<00:13:10.839> it's 00:13:11.030 --> 00:13:11.040 align:start position:0% without any hardware assumptions it's 00:13:11.040 --> 00:13:13.910 align:start position:0% without any hardware assumptions it's impossible<00:13:12.000> so<00:13:12.680> uh<00:13:12.800> indistinguishability<00:13:13.480> of 00:13:13.910 --> 00:13:13.920 align:start position:0% impossible so uh indistinguishability of 00:13:13.920 --> 00:13:18.189 align:start position:0% impossible so uh indistinguishability of fation<00:13:14.560> cannot<00:13:15.160> serve<00:13:15.760> as<00:13:16.120> a<00:13:16.320> replacement<00:13:17.240> for 00:13:18.189 --> 00:13:18.199 align:start position:0% fation cannot serve as a replacement for 00:13:18.199 --> 00:13:21.629 align:start position:0% fation cannot serve as a replacement for uh<00:13:18.279> for<00:13:18.880> tees<00:13:19.880> but<00:13:20.399> uh<00:13:20.720> I<00:13:20.800> think<00:13:21.120> maybe<00:13:21.360> I<00:13:21.480> want 00:13:21.629 --> 00:13:21.639 align:start position:0% uh for tees but uh I think maybe I want 00:13:21.639 --> 00:13:24.670 align:start position:0% uh for tees but uh I think maybe I want to<00:13:21.800> make<00:13:22.000> a<00:13:22.120> Spiel<00:13:22.519> here<00:13:23.360> of<00:13:23.480> a<00:13:23.639> larger<00:13:24.120> point 00:13:24.670 --> 00:13:24.680 align:start position:0% to make a Spiel here of a larger point 00:13:24.680 --> 00:13:26.910 align:start position:0% to make a Spiel here of a larger point in<00:13:24.800> general<00:13:25.120> in<00:13:25.279> this<00:13:25.440> area<00:13:26.079> and<00:13:26.279> also 00:13:26.910 --> 00:13:26.920 align:start position:0% in general in this area and also 00:13:26.920 --> 00:13:28.629 align:start position:0% in general in this area and also probably<00:13:27.320> because<00:13:27.720> of<00:13:27.959> my<00:13:28.240> sort<00:13:28.480> of 00:13:28.629 --> 00:13:28.639 align:start position:0% probably because of my sort of 00:13:28.639 --> 00:13:31.310 align:start position:0% probably because of my sort of background<00:13:29.240> here<00:13:29.440> is<00:13:29.639> that<00:13:30.639> uh<00:13:30.760> when<00:13:30.920> we<00:13:31.120> all 00:13:31.310 --> 00:13:31.320 align:start position:0% background here is that uh when we all 00:13:31.320 --> 00:13:33.150 align:start position:0% background here is that uh when we all studyed<00:13:31.720> like<00:13:31.880> zero<00:13:32.120> knowledge<00:13:32.399> and<00:13:32.519> MPC 00:13:33.150 --> 00:13:33.160 align:start position:0% studyed like zero knowledge and MPC 00:13:33.160 --> 00:13:36.310 align:start position:0% studyed like zero knowledge and MPC actually<00:13:33.600> MPC<00:13:34.360> in<00:13:34.519> my<00:13:34.720> mind<00:13:35.079> can<00:13:35.360> solve<00:13:36.079> most 00:13:36.310 --> 00:13:36.320 align:start position:0% actually MPC in my mind can solve most 00:13:36.320 --> 00:13:38.430 align:start position:0% actually MPC in my mind can solve most of<00:13:36.480> the<00:13:36.639> things<00:13:36.839> that<00:13:37.079> we<00:13:37.240> want<00:13:37.920> now<00:13:38.079> witness 00:13:38.430 --> 00:13:38.440 align:start position:0% of the things that we want now witness 00:13:38.440 --> 00:13:40.430 align:start position:0% of the things that we want now witness encryption<00:13:38.880> functional<00:13:39.279> encryption<00:13:39.839> IO<00:13:40.320> all 00:13:40.430 --> 00:13:40.440 align:start position:0% encryption functional encryption IO all 00:13:40.440 --> 00:13:44.389 align:start position:0% encryption functional encryption IO all of<00:13:40.680> these<00:13:41.279> help<00:13:41.839> to<00:13:42.560> address 00:13:44.389 --> 00:13:44.399 align:start position:0% of these help to address 00:13:44.399 --> 00:13:49.470 align:start position:0% of these help to address certain<00:13:45.399> adversary<00:13:46.360> or<00:13:46.839> certain<00:13:48.320> um<00:13:49.320> uh 00:13:49.470 --> 00:13:49.480 align:start position:0% certain adversary or certain um uh 00:13:49.480 --> 00:13:52.189 align:start position:0% certain adversary or certain um uh certain<00:13:49.920> kinds<00:13:50.279> of<00:13:50.639> attacks<00:13:51.160> on<00:13:51.320> the<00:13:51.480> protocol 00:13:52.189 --> 00:13:52.199 align:start position:0% certain kinds of attacks on the protocol 00:13:52.199 --> 00:13:54.230 align:start position:0% certain kinds of attacks on the protocol actually<00:13:52.480> it<00:13:52.600> can<00:13:52.720> minimize<00:13:53.240> interaction<00:13:54.120> it 00:13:54.230 --> 00:13:54.240 align:start position:0% actually it can minimize interaction it 00:13:54.240 --> 00:13:55.590 align:start position:0% actually it can minimize interaction it can<00:13:54.440> help<00:13:54.639> you<00:13:54.800> interact<00:13:55.160> with<00:13:55.320> smart 00:13:55.590 --> 00:13:55.600 align:start position:0% can help you interact with smart 00:13:55.600 --> 00:13:58.629 align:start position:0% can help you interact with smart contracts<00:13:56.040> better<00:13:56.320> Etc<00:13:57.120> but<00:13:57.639> I<00:13:57.759> think<00:13:58.399> if<00:13:58.519> you 00:13:58.629 --> 00:13:58.639 align:start position:0% contracts better Etc but I think if you 00:13:58.639 --> 00:14:01.949 align:start position:0% contracts better Etc but I think if you look<00:13:58.800> at<00:13:59.320> MPC<00:13:59.880> on<00:14:00.040> its<00:14:00.320> own<00:14:00.920> can<00:14:01.160> solve<00:14:01.680> a<00:14:01.800> lot 00:14:01.949 --> 00:14:01.959 align:start position:0% look at MPC on its own can solve a lot 00:14:01.959 --> 00:14:03.710 align:start position:0% look at MPC on its own can solve a lot of<00:14:02.160> these<00:14:02.399> so<00:14:02.759> when<00:14:02.920> we<00:14:03.079> think<00:14:03.279> about<00:14:03.519> these 00:14:03.710 --> 00:14:03.720 align:start position:0% of these so when we think about these 00:14:03.720 --> 00:14:05.749 align:start position:0% of these so when we think about these Primitives<00:14:04.279> we<00:14:04.440> also<00:14:04.639> need<00:14:04.800> to<00:14:05.240> understand<00:14:05.639> is 00:14:05.749 --> 00:14:05.759 align:start position:0% Primitives we also need to understand is 00:14:05.759 --> 00:14:09.189 align:start position:0% Primitives we also need to understand is it<00:14:06.040> that<00:14:06.639> this<00:14:06.959> attack<00:14:07.440> Vector<00:14:07.920> is<00:14:08.279> why<00:14:08.920> these 00:14:09.189 --> 00:14:09.199 align:start position:0% it that this attack Vector is why these 00:14:09.199 --> 00:14:11.749 align:start position:0% it that this attack Vector is why these Primitives<00:14:09.800> are<00:14:10.079> crucial<00:14:10.920> again<00:14:11.160> I<00:14:11.240> mean<00:14:11.519> I<00:14:11.680> I 00:14:11.749 --> 00:14:11.759 align:start position:0% Primitives are crucial again I mean I I 00:14:11.759 --> 00:14:13.069 align:start position:0% Primitives are crucial again I mean I I don't<00:14:11.920> want<00:14:12.040> to<00:14:12.160> comment<00:14:12.440> on<00:14:12.639> that<00:14:12.839> but<00:14:12.959> this 00:14:13.069 --> 00:14:13.079 align:start position:0% don't want to comment on that but this 00:14:13.079 --> 00:14:14.910 align:start position:0% don't want to comment on that but this is<00:14:13.240> something<00:14:13.560> that<00:14:13.759> people<00:14:14.399> have<00:14:14.519> to 00:14:14.910 --> 00:14:14.920 align:start position:0% is something that people have to 00:14:14.920 --> 00:14:16.910 align:start position:0% is something that people have to understand<00:14:15.279> and<00:14:16.079> even<00:14:16.279> when<00:14:16.399> you<00:14:16.600> have<00:14:16.720> to 00:14:16.910 --> 00:14:16.920 align:start position:0% understand and even when you have to 00:14:16.920 --> 00:14:18.430 align:start position:0% understand and even when you have to implement<00:14:17.360> things<00:14:17.560> like<00:14:17.720> witness<00:14:18.000> encryption 00:14:18.430 --> 00:14:18.440 align:start position:0% implement things like witness encryption 00:14:18.440 --> 00:14:20.110 align:start position:0% implement things like witness encryption and<00:14:18.560> functional<00:14:18.920> encryption<00:14:19.600> there<00:14:19.759> is<00:14:19.920> going 00:14:20.110 --> 00:14:20.120 align:start position:0% and functional encryption there is going 00:14:20.120 --> 00:14:23.310 align:start position:0% and functional encryption there is going to<00:14:20.240> be<00:14:20.399> a<00:14:20.560> dkg<00:14:21.199> component<00:14:21.920> the<00:14:22.040> dkg<00:14:22.639> assumption 00:14:23.310 --> 00:14:23.320 align:start position:0% to be a dkg component the dkg assumption 00:14:23.320 --> 00:14:24.949 align:start position:0% to be a dkg component the dkg assumption is<00:14:23.600> no<00:14:23.839> different<00:14:24.240> than<00:14:24.440> what<00:14:24.560> you<00:14:24.639> will<00:14:24.839> have 00:14:24.949 --> 00:14:24.959 align:start position:0% is no different than what you will have 00:14:24.959 --> 00:14:27.189 align:start position:0% is no different than what you will have to<00:14:25.120> make<00:14:25.320> for<00:14:25.560> MPC<00:14:26.360> from<00:14:26.519> a<00:14:26.720> security 00:14:27.189 --> 00:14:27.199 align:start position:0% to make for MPC from a security 00:14:27.199 --> 00:14:28.710 align:start position:0% to make for MPC from a security standpoint<00:14:27.639> you're<00:14:27.800> going<00:14:27.920> to<00:14:28.040> say<00:14:28.279> hey<00:14:28.480> up<00:14:28.600> to 00:14:28.710 --> 00:14:28.720 align:start position:0% standpoint you're going to say hey up to 00:14:28.720 --> 00:14:30.310 align:start position:0% standpoint you're going to say hey up to n<00:14:29.120> minus<00:14:29.320> one<00:14:29.480> of<00:14:29.600> the<00:14:29.720> parties<00:14:29.959> are<00:14:30.120> going<00:14:30.240> to 00:14:30.310 --> 00:14:30.320 align:start position:0% n minus one of the parties are going to 00:14:30.320 --> 00:14:32.990 align:start position:0% n minus one of the parties are going to be<00:14:30.480> corrupted<00:14:31.199> or<00:14:31.680> up<00:14:31.880> to<00:14:32.279> like<00:14:32.519> half<00:14:32.680> of<00:14:32.839> them 00:14:32.990 --> 00:14:33.000 align:start position:0% be corrupted or up to like half of them 00:14:33.000 --> 00:14:35.230 align:start position:0% be corrupted or up to like half of them are<00:14:33.160> going<00:14:33.320> to<00:14:33.480> be<00:14:33.639> corrupted<00:14:34.160> so<00:14:34.680> from<00:14:35.120> at 00:14:35.230 --> 00:14:35.240 align:start position:0% are going to be corrupted so from at 00:14:35.240 --> 00:14:38.430 align:start position:0% are going to be corrupted so from at least<00:14:35.480> from<00:14:35.639> a<00:14:36.000> number<00:14:36.320> of<00:14:36.560> collusions<00:14:37.440> Etc 00:14:38.430 --> 00:14:38.440 align:start position:0% least from a number of collusions Etc 00:14:38.440 --> 00:14:40.509 align:start position:0% least from a number of collusions Etc these<00:14:38.880> like<00:14:39.040> when<00:14:39.199> you<00:14:39.360> compare<00:14:39.759> MPC<00:14:40.360> and 00:14:40.509 --> 00:14:40.519 align:start position:0% these like when you compare MPC and 00:14:40.519 --> 00:14:41.990 align:start position:0% these like when you compare MPC and witness<00:14:40.880> encryption<00:14:41.440> and<00:14:41.600> functional 00:14:41.990 --> 00:14:42.000 align:start position:0% witness encryption and functional 00:14:42.000 --> 00:14:43.790 align:start position:0% witness encryption and functional encryption<00:14:42.480> for<00:14:42.680> these<00:14:42.880> things<00:14:43.399> you<00:14:43.560> can't 00:14:43.790 --> 00:14:43.800 align:start position:0% encryption for these things you can't 00:14:43.800 --> 00:14:45.509 align:start position:0% encryption for these things you can't put<00:14:43.959> them<00:14:44.120> on<00:14:44.240> the<00:14:44.360> same<00:14:44.560> place<00:14:44.920> and<00:14:45.079> I'll<00:14:45.279> also 00:14:45.509 --> 00:14:45.519 align:start position:0% put them on the same place and I'll also 00:14:45.519 --> 00:14:49.590 align:start position:0% put them on the same place and I'll also say<00:14:45.800> that<00:14:46.199> MPC<00:14:46.839> today<00:14:47.399> is<00:14:48.000> far<00:14:48.360> more<00:14:49.040> efficient 00:14:49.590 --> 00:14:49.600 align:start position:0% say that MPC today is far more efficient 00:14:49.600 --> 00:14:51.269 align:start position:0% say that MPC today is far more efficient than<00:14:49.800> it<00:14:49.959> was<00:14:50.360> I<00:14:50.440> want<00:14:50.600> to<00:14:50.720> say<00:14:50.880> like<00:14:51.000> when<00:14:51.160> I 00:14:51.269 --> 00:14:51.279 align:start position:0% than it was I want to say like when I 00:14:51.279 --> 00:14:54.710 align:start position:0% than it was I want to say like when I started<00:14:51.680> studying<00:14:52.600> uh<00:14:52.720> MPC<00:14:53.560> so<00:14:54.000> when<00:14:54.440> when<00:14:54.600> we 00:14:54.710 --> 00:14:54.720 align:start position:0% started studying uh MPC so when when we 00:14:54.720 --> 00:14:56.550 align:start position:0% started studying uh MPC so when when we are<00:14:54.920> thinking<00:14:55.279> about<00:14:55.560> these<00:14:55.800> applications 00:14:56.550 --> 00:14:56.560 align:start position:0% are thinking about these applications 00:14:56.560 --> 00:14:59.150 align:start position:0% are thinking about these applications and<00:14:56.839> these<00:14:57.079> great<00:14:57.519> Primitives<00:14:58.519> uh<00:14:58.639> I<00:14:58.759> would 00:14:59.150 --> 00:14:59.160 align:start position:0% and these great Primitives uh I would 00:14:59.160 --> 00:15:01.150 align:start position:0% and these great Primitives uh I would post<00:14:59.480> this<00:14:59.680> question<00:15:00.079> that<00:15:00.519> hey<00:15:00.759> can<00:15:00.920> we 00:15:01.150 --> 00:15:01.160 align:start position:0% post this question that hey can we 00:15:01.160 --> 00:15:03.550 align:start position:0% post this question that hey can we device<00:15:01.519> first<00:15:01.800> an<00:15:01.959> MPC<00:15:02.519> solution<00:15:03.240> can<00:15:03.399> we 00:15:03.550 --> 00:15:03.560 align:start position:0% device first an MPC solution can we 00:15:03.560 --> 00:15:06.629 align:start position:0% device first an MPC solution can we deploy<00:15:04.000> it<00:15:04.199> can<00:15:04.320> we<00:15:04.639> see<00:15:05.639> is<00:15:05.800> this<00:15:06.040> enough<00:15:06.440> like 00:15:06.629 --> 00:15:06.639 align:start position:0% deploy it can we see is this enough like 00:15:06.639 --> 00:15:09.230 align:start position:0% deploy it can we see is this enough like is<00:15:06.800> this<00:15:07.199> are<00:15:07.519> already<00:15:08.040> going<00:15:08.279> to<00:15:08.519> give<00:15:08.680> you 00:15:09.230 --> 00:15:09.240 align:start position:0% is this are already going to give you 00:15:09.240 --> 00:15:11.509 align:start position:0% is this are already going to give you certain<00:15:09.680> meaningful<00:15:10.360> privacy<00:15:10.839> guarantees 00:15:11.509 --> 00:15:11.519 align:start position:0% certain meaningful privacy guarantees 00:15:11.519 --> 00:15:13.870 align:start position:0% certain meaningful privacy guarantees yes<00:15:11.920> at<00:15:12.079> the<00:15:12.279> cost<00:15:12.560> of<00:15:12.800> maybe<00:15:13.120> some<00:15:13.320> denial<00:15:13.720> of 00:15:13.870 --> 00:15:13.880 align:start position:0% yes at the cost of maybe some denial of 00:15:13.880 --> 00:15:16.670 align:start position:0% yes at the cost of maybe some denial of service<00:15:14.279> attacks<00:15:15.040> but<00:15:15.600> uh<00:15:15.759> I<00:15:15.839> do<00:15:16.079> think<00:15:16.320> that 00:15:16.670 --> 00:15:16.680 align:start position:0% service attacks but uh I do think that 00:15:16.680 --> 00:15:18.910 align:start position:0% service attacks but uh I do think that in<00:15:16.839> terms<00:15:17.160> of<00:15:17.399> even<00:15:17.680> realizing<00:15:18.240> the<00:15:18.399> potential 00:15:18.910 --> 00:15:18.920 align:start position:0% in terms of even realizing the potential 00:15:18.920 --> 00:15:20.550 align:start position:0% in terms of even realizing the potential that<00:15:19.040> we<00:15:19.120> are<00:15:19.240> seeing<00:15:19.519> of<00:15:19.720> these<00:15:19.920> things<00:15:20.360> to 00:15:20.550 --> 00:15:20.560 align:start position:0% that we are seeing of these things to 00:15:20.560 --> 00:15:25.470 align:start position:0% that we are seeing of these things to look<00:15:20.720> at<00:15:21.160> uh<00:15:21.639> MPC<00:15:22.800> so<00:15:23.800> is<00:15:24.000> it<00:15:25.000> correct<00:15:25.240> to<00:15:25.360> say 00:15:25.470 --> 00:15:25.480 align:start position:0% look at uh MPC so is it correct to say 00:15:25.480 --> 00:15:28.629 align:start position:0% look at uh MPC so is it correct to say that<00:15:25.600> there<00:15:25.720> a<00:15:25.959> spectrum<00:15:26.959> uh<00:15:27.240> from<00:15:27.639> trust 00:15:28.629 --> 00:15:28.639 align:start position:0% that there a spectrum uh from trust 00:15:28.639 --> 00:15:31.189 align:start position:0% that there a spectrum uh from trust trust<00:15:29.399> it<00:15:30.399> something<00:15:30.639> that<00:15:30.759> requires<00:15:31.040> a<00:15:31.120> lot 00:15:31.189 --> 00:15:31.199 align:start position:0% trust it something that requires a lot 00:15:31.199 --> 00:15:32.629 align:start position:0% trust it something that requires a lot of<00:15:31.319> trust<00:15:31.600> to<00:15:31.800> something<00:15:32.000> that's<00:15:32.240> very<00:15:32.399> trust 00:15:32.629 --> 00:15:32.639 align:start position:0% of trust to something that's very trust 00:15:32.639 --> 00:15:35.110 align:start position:0% of trust to something that's very trust minimized<00:15:33.160> where<00:15:33.839> uh<00:15:33.920> you<00:15:34.079> know<00:15:34.519> we<00:15:34.959> we 00:15:35.110 --> 00:15:35.120 align:start position:0% minimized where uh you know we we 00:15:35.120 --> 00:15:37.030 align:start position:0% minimized where uh you know we we actually<00:15:35.279> rely<00:15:35.519> on<00:15:35.720> math<00:15:36.399> in<00:15:36.480> the<00:15:36.600> middle<00:15:36.839> is 00:15:37.030 --> 00:15:37.040 align:start position:0% actually rely on math in the middle is 00:15:37.040 --> 00:15:39.389 align:start position:0% actually rely on math in the middle is NPC<00:15:37.720> right<00:15:38.040> NPC<00:15:38.399> still<00:15:38.560> realiz<00:15:38.920> on 00:15:39.389 --> 00:15:39.399 align:start position:0% NPC right NPC still realiz on 00:15:39.399 --> 00:15:42.189 align:start position:0% NPC right NPC still realiz on mathematical<00:15:39.880> assumptions<00:15:40.720> but<00:15:40.920> we<00:15:41.199> actually 00:15:42.189 --> 00:15:42.199 align:start position:0% mathematical assumptions but we actually 00:15:42.199 --> 00:15:44.509 align:start position:0% mathematical assumptions but we actually ask<00:15:42.560> certain<00:15:42.880> notes<00:15:43.160> to<00:15:43.240> be<00:15:43.399> honest<00:15:44.000> right<00:15:44.360> and 00:15:44.509 --> 00:15:44.519 align:start position:0% ask certain notes to be honest right and 00:15:44.519 --> 00:15:46.110 align:start position:0% ask certain notes to be honest right and there's<00:15:45.079> ways<00:15:45.240> to<00:15:45.440> hold<00:15:45.680> them<00:15:45.800> to<00:15:45.920> be 00:15:46.110 --> 00:15:46.120 align:start position:0% there's ways to hold them to be 00:15:46.120 --> 00:15:47.470 align:start position:0% there's ways to hold them to be accountable<00:15:46.560> if<00:15:46.839> if<00:15:46.920> they<00:15:47.040> behave 00:15:47.470 --> 00:15:47.480 align:start position:0% accountable if if they behave 00:15:47.480 --> 00:15:50.590 align:start position:0% accountable if if they behave dishonestly<00:15:48.480> which<00:15:48.600> is<00:15:49.240> actually<00:15:50.240> quite<00:15:50.399> open 00:15:50.590 --> 00:15:50.600 align:start position:0% dishonestly which is actually quite open 00:15:50.600 --> 00:15:52.710 align:start position:0% dishonestly which is actually quite open research<00:15:50.920> area<00:15:51.720> the<00:15:51.839> notion<00:15:52.079> of<00:15:52.240> accountable 00:15:52.710 --> 00:15:52.720 align:start position:0% research area the notion of accountable 00:15:52.720 --> 00:15:55.350 align:start position:0% research area the notion of accountable MPC<00:15:53.199> which<00:15:53.319> I<00:15:53.399> think<00:15:53.800> is<00:15:54.800> is<00:15:55.000> actually<00:15:55.240> you 00:15:55.350 --> 00:15:55.360 align:start position:0% MPC which I think is is actually you 00:15:55.360 --> 00:15:58.309 align:start position:0% MPC which I think is is actually you know<00:15:55.480> within<00:15:55.839> the<00:15:56.120> the<00:15:56.279> the<00:15:56.399> same<00:15:56.600> category<00:15:57.319> of 00:15:58.309 --> 00:15:58.319 align:start position:0% know within the the the same category of 00:15:58.319 --> 00:16:02.430 align:start position:0% know within the the the same category of program<00:15:59.160> graphy<00:16:00.519> um<00:16:01.519> we<00:16:01.600> should<00:16:02.160> do 00:16:02.430 --> 00:16:02.440 align:start position:0% program graphy um we should do 00:16:02.440 --> 00:16:04.550 align:start position:0% program graphy um we should do applications<00:16:03.040> first<00:16:03.399> using<00:16:03.880> you<00:16:03.959> know<00:16:04.120> more 00:16:04.550 --> 00:16:04.560 align:start position:0% applications first using you know more 00:16:04.560 --> 00:16:07.670 align:start position:0% applications first using you know more trusted<00:16:05.560> uh<00:16:06.079> w<00:16:06.399> Battle<00:16:06.680> tested<00:16:07.040> Primitives 00:16:07.670 --> 00:16:07.680 align:start position:0% trusted uh w Battle tested Primitives 00:16:07.680 --> 00:16:09.829 align:start position:0% trusted uh w Battle tested Primitives and<00:16:07.839> then<00:16:08.000> move<00:16:08.279> to<00:16:08.519> things<00:16:08.800> like 00:16:09.829 --> 00:16:09.839 align:start position:0% and then move to things like 00:16:09.839 --> 00:16:12.389 align:start position:0% and then move to things like obilation<00:16:10.839> um<00:16:11.160> so<00:16:11.399> maybe<00:16:11.800> in<00:16:11.920> the<00:16:12.079> in<00:16:12.160> the<00:16:12.279> last 00:16:12.389 --> 00:16:12.399 align:start position:0% obilation um so maybe in the in the last 00:16:12.399 --> 00:16:14.749 align:start position:0% obilation um so maybe in the in the last couple<00:16:12.680> minutes<00:16:13.440> um<00:16:13.720> let's<00:16:14.040> explore<00:16:14.519> the 00:16:14.749 --> 00:16:14.759 align:start position:0% couple minutes um let's explore the 00:16:14.759 --> 00:16:16.509 align:start position:0% couple minutes um let's explore the actual<00:16:15.240> feasibility<00:16:16.000> of<00:16:16.160> these<00:16:16.319> more 00:16:16.509 --> 00:16:16.519 align:start position:0% actual feasibility of these more 00:16:16.519 --> 00:16:20.829 align:start position:0% actual feasibility of these more advanced<00:16:17.000> Primitives<00:16:18.279> um<00:16:19.279> I<00:16:19.399> think<00:16:19.959> the<00:16:20.480> first 00:16:20.829 --> 00:16:20.839 align:start position:0% advanced Primitives um I think the first 00:16:20.839 --> 00:16:23.110 align:start position:0% advanced Primitives um I think the first result<00:16:21.360> that's<00:16:21.720> peer<00:16:21.959> reviewed<00:16:22.480> and<00:16:22.759> accepted 00:16:23.110 --> 00:16:23.120 align:start position:0% result that's peer reviewed and accepted 00:16:23.120 --> 00:16:25.550 align:start position:0% result that's peer reviewed and accepted by<00:16:23.279> The<00:16:23.920> Wider<00:16:24.279> cryptographic<00:16:24.839> community 00:16:25.550 --> 00:16:25.560 align:start position:0% by The Wider cryptographic community 00:16:25.560 --> 00:16:28.430 align:start position:0% by The Wider cryptographic community that<00:16:25.680> says<00:16:26.000> IO<00:16:26.920> tication<00:16:27.440> is<00:16:27.600> possible<00:16:28.240> came 00:16:28.430 --> 00:16:28.440 align:start position:0% that says IO tication is possible came 00:16:28.440 --> 00:16:31.749 align:start position:0% that says IO tication is possible came from<00:16:29.040> 21<00:16:29.519> right<00:16:30.040> and<00:16:30.319> can<00:16:30.440> you<00:16:30.560> comment<00:16:30.920> on 00:16:31.749 --> 00:16:31.759 align:start position:0% from 21 right and can you comment on 00:16:31.759 --> 00:16:33.590 align:start position:0% from 21 right and can you comment on what<00:16:31.920> has<00:16:32.079> happened<00:16:32.440> since<00:16:32.720> then<00:16:33.319> uh<00:16:33.440> has 00:16:33.590 --> 00:16:33.600 align:start position:0% what has happened since then uh has 00:16:33.600 --> 00:16:35.949 align:start position:0% what has happened since then uh has people<00:16:34.000> implemented<00:16:35.000> this<00:16:35.279> this<00:16:35.480> primitive 00:16:35.949 --> 00:16:35.959 align:start position:0% people implemented this this primitive 00:16:35.959 --> 00:16:38.550 align:start position:0% people implemented this this primitive and<00:16:36.120> and<00:16:36.279> what<00:16:36.399> is<00:16:36.519> the<00:16:36.639> performers<00:16:37.120> like<00:16:38.079> uh 00:16:38.550 --> 00:16:38.560 align:start position:0% and and what is the performers like uh 00:16:38.560 --> 00:16:41.069 align:start position:0% and and what is the performers like uh yeah<00:16:38.839> actually<00:16:39.600> um<00:16:40.040> my<00:16:40.279> when<00:16:40.399> I<00:16:40.519> was<00:16:40.639> doing<00:16:40.880> my 00:16:41.069 --> 00:16:41.079 align:start position:0% yeah actually um my when I was doing my 00:16:41.079 --> 00:16:44.470 align:start position:0% yeah actually um my when I was doing my PhD<00:16:41.600> my<00:16:41.759> PhD<00:16:42.319> classmate<00:16:43.240> uh<00:16:43.399> hu<00:16:43.959> Lynn<00:16:44.199> she<00:16:44.319> is 00:16:44.470 --> 00:16:44.480 align:start position:0% PhD my PhD classmate uh hu Lynn she is 00:16:44.480 --> 00:16:47.470 align:start position:0% PhD my PhD classmate uh hu Lynn she is one<00:16:44.600> of<00:16:44.720> the<00:16:44.880> authors<00:16:45.399> of<00:16:45.639> this<00:16:46.000> 2021<00:16:47.000> uh<00:16:47.120> paper 00:16:47.470 --> 00:16:47.480 align:start position:0% one of the authors of this 2021 uh paper 00:16:47.480 --> 00:16:49.670 align:start position:0% one of the authors of this 2021 uh paper that<00:16:47.600> solved<00:16:47.959> indistinguishability<00:16:48.680> ofation 00:16:49.670 --> 00:16:49.680 align:start position:0% that solved indistinguishability ofation 00:16:49.680 --> 00:16:51.110 align:start position:0% that solved indistinguishability ofation but<00:16:49.880> one<00:16:50.000> needs<00:16:50.199> to<00:16:50.399> actually<00:16:50.880> understand 00:16:51.110 --> 00:16:51.120 align:start position:0% but one needs to actually understand 00:16:51.120 --> 00:16:53.670 align:start position:0% but one needs to actually understand what<00:16:51.279> did<00:16:51.480> they<00:16:51.639> solve<00:16:52.480> right<00:16:53.160> when<00:16:53.279> you<00:16:53.399> say 00:16:53.670 --> 00:16:53.680 align:start position:0% what did they solve right when you say 00:16:53.680 --> 00:16:55.350 align:start position:0% what did they solve right when you say that<00:16:53.920> can<00:16:54.079> I<00:16:54.199> realize<00:16:54.560> in<00:16:54.680> distinguishability 00:16:55.350 --> 00:16:55.360 align:start position:0% that can I realize in distinguishability 00:16:55.360 --> 00:16:58.430 align:start position:0% that can I realize in distinguishability ofation<00:16:56.360> it<00:16:56.480> was<00:16:56.800> like<00:16:57.399> you<00:16:57.519> know<00:16:57.959> at<00:16:58.120> least<00:16:58.279> a 00:16:58.430 --> 00:16:58.440 align:start position:0% ofation it was like you know at least a 00:16:58.440 --> 00:17:00.670 align:start position:0% ofation it was like you know at least a decade<00:16:59.040> back<00:16:59.240> they<00:16:59.360> showed<00:17:00.160> the<00:17:00.319> first 00:17:00.670 --> 00:17:00.680 align:start position:0% decade back they showed the first 00:17:00.680 --> 00:17:02.949 align:start position:0% decade back they showed the first candidate<00:17:01.199> construction<00:17:02.199> based<00:17:02.600> on 00:17:02.949 --> 00:17:02.959 align:start position:0% candidate construction based on 00:17:02.959 --> 00:17:05.429 align:start position:0% candidate construction based on multilinear<00:17:03.680> maps<00:17:04.520> but<00:17:04.679> then<00:17:05.000> after<00:17:05.280> that 00:17:05.429 --> 00:17:05.439 align:start position:0% multilinear maps but then after that 00:17:05.439 --> 00:17:07.350 align:start position:0% multilinear maps but then after that there<00:17:05.559> was<00:17:05.720> this<00:17:05.919> huge<00:17:06.199> cycle<00:17:06.520> of<00:17:06.720> people<00:17:07.240> you 00:17:07.350 --> 00:17:07.360 align:start position:0% there was this huge cycle of people you 00:17:07.360 --> 00:17:09.590 align:start position:0% there was this huge cycle of people you know<00:17:07.520> trying<00:17:07.839> to<00:17:08.480> Define<00:17:09.160> what<00:17:09.280> is<00:17:09.439> the 00:17:09.590 --> 00:17:09.600 align:start position:0% know trying to Define what is the 00:17:09.600 --> 00:17:12.110 align:start position:0% know trying to Define what is the security<00:17:10.000> of<00:17:10.160> multilinear<00:17:10.760> maps<00:17:11.480> it<00:17:11.720> you<00:17:11.799> know 00:17:12.110 --> 00:17:12.120 align:start position:0% security of multilinear maps it you know 00:17:12.120 --> 00:17:13.309 align:start position:0% security of multilinear maps it you know there<00:17:12.240> were<00:17:12.480> constructions<00:17:13.079> they<00:17:13.160> were 00:17:13.309 --> 00:17:13.319 align:start position:0% there were constructions they were 00:17:13.319 --> 00:17:14.590 align:start position:0% there were constructions they were broken<00:17:13.679> there<00:17:13.799> were<00:17:13.959> constructions<00:17:14.520> they 00:17:14.590 --> 00:17:14.600 align:start position:0% broken there were constructions they 00:17:14.600 --> 00:17:17.069 align:start position:0% broken there were constructions they were<00:17:14.720> broken<00:17:15.520> the<00:17:15.679> officiation<00:17:16.400> construction 00:17:17.069 --> 00:17:17.079 align:start position:0% were broken the officiation construction 00:17:17.079 --> 00:17:19.350 align:start position:0% were broken the officiation construction itself<00:17:17.760> wasn't<00:17:18.160> broken<00:17:18.600> but<00:17:18.760> the<00:17:18.919> Assumption 00:17:19.350 --> 00:17:19.360 align:start position:0% itself wasn't broken but the Assumption 00:17:19.360 --> 00:17:21.710 align:start position:0% itself wasn't broken but the Assumption was<00:17:19.559> broken<00:17:20.160> so<00:17:20.439> really<00:17:20.839> in<00:17:21.000> the<00:17:21.120> theoretical 00:17:21.710 --> 00:17:21.720 align:start position:0% was broken so really in the theoretical 00:17:21.720 --> 00:17:24.510 align:start position:0% was broken so really in the theoretical Community<00:17:22.319> it<00:17:22.439> was<00:17:22.679> about<00:17:23.079> trying<00:17:23.400> to<00:17:23.720> find 00:17:24.510 --> 00:17:24.520 align:start position:0% Community it was about trying to find 00:17:24.520 --> 00:17:26.710 align:start position:0% Community it was about trying to find the<00:17:24.720> falsifiable<00:17:25.600> Assumption<00:17:26.199> based<00:17:26.520> on 00:17:26.710 --> 00:17:26.720 align:start position:0% the falsifiable Assumption based on 00:17:26.720 --> 00:17:28.710 align:start position:0% the falsifiable Assumption based on which<00:17:26.880> you<00:17:27.000> can<00:17:27.160> construct<00:17:27.559> OB<00:17:27.760> fation<00:17:28.520> and 00:17:28.710 --> 00:17:28.720 align:start position:0% which you can construct OB fation and 00:17:28.720 --> 00:17:31.950 align:start position:0% which you can construct OB fation and the<00:17:29.000> JIS<00:17:29.559> paper<00:17:29.880> in<00:17:30.080> 21<00:17:31.039> came<00:17:31.320> up<00:17:31.559> with<00:17:31.720> the 00:17:31.950 --> 00:17:31.960 align:start position:0% the JIS paper in 21 came up with the 00:17:31.960 --> 00:17:34.430 align:start position:0% the JIS paper in 21 came up with the first<00:17:32.320> set<00:17:32.600> of<00:17:32.760> falsifiable<00:17:33.480> assumptions<00:17:34.080> and 00:17:34.430 --> 00:17:34.440 align:start position:0% first set of falsifiable assumptions and 00:17:34.440 --> 00:17:36.230 align:start position:0% first set of falsifiable assumptions and I<00:17:34.520> just<00:17:34.640> want<00:17:34.760> to<00:17:34.880> say<00:17:35.039> as<00:17:35.120> a<00:17:35.280> cryptographer 00:17:36.230 --> 00:17:36.240 align:start position:0% I just want to say as a cryptographer 00:17:36.240 --> 00:17:38.230 align:start position:0% I just want to say as a cryptographer for<00:17:36.440> us<00:17:36.679> our<00:17:36.919> bread<00:17:37.160> and<00:17:37.320> butter<00:17:37.760> is<00:17:37.960> about 00:17:38.230 --> 00:17:38.240 align:start position:0% for us our bread and butter is about 00:17:38.240 --> 00:17:39.870 align:start position:0% for us our bread and butter is about getting<00:17:38.600> things<00:17:38.880> using<00:17:39.200> falsifiable 00:17:39.870 --> 00:17:39.880 align:start position:0% getting things using falsifiable 00:17:39.880 --> 00:17:42.029 align:start position:0% getting things using falsifiable assumptions<00:17:40.720> and<00:17:41.160> that<00:17:41.280> was<00:17:41.480> the<00:17:41.679> huge 00:17:42.029 --> 00:17:42.039 align:start position:0% assumptions and that was the huge 00:17:42.039 --> 00:17:44.870 align:start position:0% assumptions and that was the huge breakthrough<00:17:42.600> in<00:17:42.760> JLS<00:17:43.280> 21<00:17:44.080> that<00:17:44.400> you<00:17:44.559> could 00:17:44.870 --> 00:17:44.880 align:start position:0% breakthrough in JLS 21 that you could 00:17:44.880 --> 00:17:47.350 align:start position:0% breakthrough in JLS 21 that you could construct<00:17:45.440> aisc<00:17:46.200> based<00:17:46.520> on<00:17:46.720> falsifiable 00:17:47.350 --> 00:17:47.360 align:start position:0% construct aisc based on falsifiable 00:17:47.360 --> 00:17:49.270 align:start position:0% construct aisc based on falsifiable assumptions<00:17:48.200> but<00:17:48.600> if<00:17:48.720> you<00:17:48.840> look<00:17:48.960> at<00:17:49.080> this 00:17:49.270 --> 00:17:49.280 align:start position:0% assumptions but if you look at this 00:17:49.280 --> 00:17:51.230 align:start position:0% assumptions but if you look at this construction<00:17:49.880> it<00:17:50.039> requires<00:17:50.559> four<00:17:50.919> different 00:17:51.230 --> 00:17:51.240 align:start position:0% construction it requires four different 00:17:51.240 --> 00:17:55.029 align:start position:0% construction it requires four different things<00:17:51.799> LPN<00:17:52.440> LW<00:17:53.240> bilinear<00:17:53.799> Maps<00:17:54.200> like<00:17:54.640> several 00:17:55.029 --> 00:17:55.039 align:start position:0% things LPN LW bilinear Maps like several 00:17:55.039 --> 00:17:57.789 align:start position:0% things LPN LW bilinear Maps like several cryptographic<00:17:55.720> assumptions<00:17:56.280> went<00:17:56.799> into 00:17:57.789 --> 00:17:57.799 align:start position:0% cryptographic assumptions went into 00:17:57.799 --> 00:18:00.230 align:start position:0% cryptographic assumptions went into constructing<00:17:58.440> this<00:17:58.960> and<00:17:59.120> now<00:17:59.360> since<00:17:59.720> then 00:18:00.230 --> 00:18:00.240 align:start position:0% constructing this and now since then 00:18:00.240 --> 00:18:01.950 align:start position:0% constructing this and now since then what<00:18:00.400> people<00:18:00.600> are<00:18:00.760> trying<00:18:01.000> to<00:18:01.120> do<00:18:01.440> which<00:18:01.640> again 00:18:01.950 --> 00:18:01.960 align:start position:0% what people are trying to do which again 00:18:01.960 --> 00:18:04.149 align:start position:0% what people are trying to do which again is<00:18:02.120> one<00:18:02.280> of<00:18:02.480> the<00:18:02.720> other<00:18:03.480> sort<00:18:03.679> of<00:18:03.840> really 00:18:04.149 --> 00:18:04.159 align:start position:0% is one of the other sort of really 00:18:04.159 --> 00:18:06.230 align:start position:0% is one of the other sort of really motivating<00:18:04.720> questions<00:18:05.000> in<00:18:05.200> cryptography<00:18:06.120> is 00:18:06.230 --> 00:18:06.240 align:start position:0% motivating questions in cryptography is 00:18:06.240 --> 00:18:07.669 align:start position:0% motivating questions in cryptography is to<00:18:06.440> minimize<00:18:06.960> the<00:18:07.080> cryptographic 00:18:07.669 --> 00:18:07.679 align:start position:0% to minimize the cryptographic 00:18:07.679 --> 00:18:09.390 align:start position:0% to minimize the cryptographic assumptions<00:18:08.159> you<00:18:08.240> don't<00:18:08.440> want<00:18:08.600> to<00:18:09.000> assume 00:18:09.390 --> 00:18:09.400 align:start position:0% assumptions you don't want to assume 00:18:09.400 --> 00:18:11.590 align:start position:0% assumptions you don't want to assume four<00:18:09.720> different<00:18:10.080> things<00:18:10.720> and<00:18:10.919> a<00:18:11.039> more<00:18:11.280> recent 00:18:11.590 --> 00:18:11.600 align:start position:0% four different things and a more recent 00:18:11.600 --> 00:18:14.029 align:start position:0% four different things and a more recent line<00:18:11.799> of<00:18:11.960> work<00:18:12.200> is<00:18:12.400> trying<00:18:12.640> to<00:18:12.880> get<00:18:13.480> another 00:18:14.029 --> 00:18:14.039 align:start position:0% line of work is trying to get another 00:18:14.039 --> 00:18:16.310 align:start position:0% line of work is trying to get another flavor<00:18:14.679> of<00:18:14.919> a<00:18:15.039> single<00:18:15.360> assumption<00:18:15.960> which<00:18:16.080> is<00:18:16.200> a 00:18:16.310 --> 00:18:16.320 align:start position:0% flavor of a single assumption which is a 00:18:16.320 --> 00:18:18.310 align:start position:0% flavor of a single assumption which is a latus<00:18:16.679> based<00:18:16.960> assumption<00:18:17.679> to<00:18:17.919> construct 00:18:18.310 --> 00:18:18.320 align:start position:0% latus based assumption to construct 00:18:18.320 --> 00:18:20.549 align:start position:0% latus based assumption to construct officiation<00:18:18.960> there<00:18:19.080> are<00:18:19.320> again<00:18:19.679> candidates 00:18:20.549 --> 00:18:20.559 align:start position:0% officiation there are again candidates 00:18:20.559 --> 00:18:21.950 align:start position:0% officiation there are again candidates but<00:18:20.720> it's<00:18:20.919> kind<00:18:21.080> of<00:18:21.200> going<00:18:21.440> a<00:18:21.559> little<00:18:21.720> bit<00:18:21.840> in 00:18:21.950 --> 00:18:21.960 align:start position:0% but it's kind of going a little bit in 00:18:21.960 --> 00:18:24.909 align:start position:0% but it's kind of going a little bit in the<00:18:22.080> cycle<00:18:22.360> of<00:18:22.480> multi-linear<00:18:23.240> maps<00:18:23.919> where 00:18:24.909 --> 00:18:24.919 align:start position:0% the cycle of multi-linear maps where 00:18:24.919 --> 00:18:26.630 align:start position:0% the cycle of multi-linear maps where they<00:18:25.159> Define<00:18:25.559> something<00:18:25.880> it<00:18:26.039> gets<00:18:26.240> broken 00:18:26.630 --> 00:18:26.640 align:start position:0% they Define something it gets broken 00:18:26.640 --> 00:18:28.390 align:start position:0% they Define something it gets broken they<00:18:26.760> Define<00:18:27.159> something<00:18:27.559> but<00:18:27.760> you<00:18:27.880> know<00:18:28.280> this 00:18:28.390 --> 00:18:28.400 align:start position:0% they Define something but you know this 00:18:28.400 --> 00:18:30.110 align:start position:0% they Define something but you know this is<00:18:28.480> a<00:18:28.799> cycle<00:18:29.159> that<00:18:29.320> you<00:18:29.400> know<00:18:29.520> Theory<00:18:29.880> people 00:18:30.110 --> 00:18:30.120 align:start position:0% is a cycle that you know Theory people 00:18:30.120 --> 00:18:32.590 align:start position:0% is a cycle that you know Theory people are<00:18:30.280> used<00:18:30.600> to<00:18:31.280> uh<00:18:31.400> in<00:18:31.559> terms<00:18:31.840> of<00:18:32.080> these<00:18:32.480> uh 00:18:32.590 --> 00:18:32.600 align:start position:0% are used to uh in terms of these uh 00:18:32.600 --> 00:18:34.710 align:start position:0% are used to uh in terms of these uh constructions<00:18:33.240> but<00:18:33.720> just<00:18:33.840> to<00:18:34.400> uh<00:18:34.520> you<00:18:34.600> know 00:18:34.710 --> 00:18:34.720 align:start position:0% constructions but just to uh you know 00:18:34.720 --> 00:18:37.110 align:start position:0% constructions but just to uh you know wrap<00:18:34.960> up<00:18:35.120> with<00:18:35.240> the<00:18:35.400> Practical<00:18:36.320> feasibility 00:18:37.110 --> 00:18:37.120 align:start position:0% wrap up with the Practical feasibility 00:18:37.120 --> 00:18:40.310 align:start position:0% wrap up with the Practical feasibility of<00:18:37.320> this<00:18:37.799> we<00:18:37.960> are<00:18:38.200> far<00:18:38.679> from<00:18:39.120> alisation<00:18:39.880> being 00:18:40.310 --> 00:18:40.320 align:start position:0% of this we are far from alisation being 00:18:40.320 --> 00:18:42.149 align:start position:0% of this we are far from alisation being practical<00:18:40.760> I<00:18:40.840> want<00:18:40.960> to<00:18:41.080> say<00:18:41.280> that<00:18:41.679> there<00:18:41.799> was<00:18:41.960> a 00:18:42.149 --> 00:18:42.159 align:start position:0% practical I want to say that there was a 00:18:42.159 --> 00:18:45.310 align:start position:0% practical I want to say that there was a paper<00:18:42.480> I<00:18:42.600> forget<00:18:42.960> now<00:18:43.640> maybe<00:18:44.640> six<00:18:44.880> to<00:18:45.039> seven 00:18:45.310 --> 00:18:45.320 align:start position:0% paper I forget now maybe six to seven 00:18:45.320 --> 00:18:47.430 align:start position:0% paper I forget now maybe six to seven years<00:18:45.559> back<00:18:45.720> in<00:18:45.880> crypto<00:18:46.640> where<00:18:46.880> they<00:18:47.000> showed 00:18:47.430 --> 00:18:47.440 align:start position:0% years back in crypto where they showed 00:18:47.440 --> 00:18:49.390 align:start position:0% years back in crypto where they showed they<00:18:47.559> did<00:18:47.799> construct<00:18:48.200> an<00:18:48.360> offis<00:18:49.080> that<00:18:49.200> could 00:18:49.390 --> 00:18:49.400 align:start position:0% they did construct an offis that could 00:18:49.400 --> 00:18:51.990 align:start position:0% they did construct an offis that could do<00:18:50.159> five<00:18:50.679> operations<00:18:51.320> and<00:18:51.480> I<00:18:51.559> mean<00:18:51.799> like 00:18:51.990 --> 00:18:52.000 align:start position:0% do five operations and I mean like 00:18:52.000 --> 00:18:55.110 align:start position:0% do five operations and I mean like really<00:18:52.360> five<00:18:52.799> gates<00:18:53.799> uh<00:18:54.039> of<00:18:54.720> uh<00:18:54.919> of 00:18:55.110 --> 00:18:55.120 align:start position:0% really five gates uh of uh of 00:18:55.120 --> 00:18:57.669 align:start position:0% really five gates uh of uh of computation<00:18:56.000> and<00:18:56.159> that<00:18:56.320> took<00:18:56.559> like<00:18:56.799> hours<00:18:57.559> uh 00:18:57.669 --> 00:18:57.679 align:start position:0% computation and that took like hours uh 00:18:57.679 --> 00:19:00.549 align:start position:0% computation and that took like hours uh hours<00:18:57.960> to<00:18:58.120> run<00:18:58.360> using<00:18:59.159> uh<00:18:59.280> multilinear<00:18:59.960> maps 00:19:00.549 --> 00:19:00.559 align:start position:0% hours to run using uh multilinear maps 00:19:00.559 --> 00:19:02.470 align:start position:0% hours to run using uh multilinear maps and<00:19:00.919> that<00:19:01.080> being<00:19:01.320> said<00:19:01.640> you<00:19:01.720> know<00:19:02.080> definitely 00:19:02.470 --> 00:19:02.480 align:start position:0% and that being said you know definitely 00:19:02.480 --> 00:19:05.430 align:start position:0% and that being said you know definitely research<00:19:02.880> should<00:19:03.080> still<00:19:03.440> go<00:19:04.120> into<00:19:05.120> uh<00:19:05.320> you 00:19:05.430 --> 00:19:05.440 align:start position:0% research should still go into uh you 00:19:05.440 --> 00:19:07.710 align:start position:0% research should still go into uh you know<00:19:05.720> making<00:19:06.159> these<00:19:06.360> things<00:19:06.960> both<00:19:07.240> reducing 00:19:07.710 --> 00:19:07.720 align:start position:0% know making these things both reducing 00:19:07.720 --> 00:19:09.710 align:start position:0% know making these things both reducing the<00:19:07.840> assumptions<00:19:08.440> but<00:19:08.679> also<00:19:08.960> trying<00:19:09.200> to<00:19:09.480> find 00:19:09.710 --> 00:19:09.720 align:start position:0% the assumptions but also trying to find 00:19:09.720 --> 00:19:12.430 align:start position:0% the assumptions but also trying to find out<00:19:10.320> in<00:19:10.440> a<00:19:10.679> limited<00:19:11.159> form<00:19:11.559> can<00:19:11.919> the<00:19:12.200> these 00:19:12.430 --> 00:19:12.440 align:start position:0% out in a limited form can the these 00:19:12.440 --> 00:19:14.549 align:start position:0% out in a limited form can the these things<00:19:12.720> still<00:19:12.960> be<00:19:13.200> practically 00:19:14.549 --> 00:19:14.559 align:start position:0% things still be practically 00:19:14.559 --> 00:19:17.270 align:start position:0% things still be practically constructed<00:19:15.559> so<00:19:16.400> you<00:19:16.520> know<00:19:16.720> a<00:19:16.840> counter<00:19:17.120> part 00:19:17.270 --> 00:19:17.280 align:start position:0% constructed so you know a counter part 00:19:17.280 --> 00:19:19.630 align:start position:0% constructed so you know a counter part of<00:19:17.440> that<00:19:17.600> is<00:19:17.720> if<00:19:17.840> you<00:19:17.919> look<00:19:18.080> at<00:19:18.320> 10<00:19:18.640> years<00:19:19.159> ago 00:19:19.630 --> 00:19:19.640 align:start position:0% of that is if you look at 10 years ago 00:19:19.640 --> 00:19:22.669 align:start position:0% of that is if you look at 10 years ago you<00:19:19.919> know<00:19:20.919> maybe<00:19:21.200> 15<00:19:21.480> years<00:19:21.640> ago<00:19:22.280> people<00:19:22.480> said 00:19:22.669 --> 00:19:22.679 align:start position:0% you know maybe 15 years ago people said 00:19:22.679 --> 00:19:26.070 align:start position:0% you know maybe 15 years ago people said the<00:19:22.799> same<00:19:22.960> thing<00:19:23.120> about<00:19:23.320> a<00:19:24.000> and<00:19:24.240> nck<00:19:25.240> and<00:19:25.919> you 00:19:26.070 --> 00:19:26.080 align:start position:0% the same thing about a and nck and you 00:19:26.080 --> 00:19:28.270 align:start position:0% the same thing about a and nck and you know<00:19:26.480> the<00:19:26.880> land<00:19:27.280> has<00:19:27.400> really<00:19:27.600> changed<00:19:28.120> do<00:19:28.200> you 00:19:28.270 --> 00:19:28.280 align:start position:0% know the land has really changed do you 00:19:28.280 --> 00:19:30.149 align:start position:0% know the land has really changed do you think<00:19:28.440> the<00:19:28.760> same<00:19:28.919> thing<00:19:29.039> will<00:19:29.280> happen<00:19:29.720> for 00:19:30.149 --> 00:19:30.159 align:start position:0% think the same thing will happen for 00:19:30.159 --> 00:19:32.310 align:start position:0% think the same thing will happen for ofation<00:19:31.120> and<00:19:31.360> and<00:19:31.720> are<00:19:31.880> there<00:19:32.039> enough 00:19:32.310 --> 00:19:32.320 align:start position:0% ofation and and are there enough 00:19:32.320 --> 00:19:34.350 align:start position:0% ofation and and are there enough cryptographers<00:19:33.000> actually<00:19:33.200> working<00:19:33.440> on 00:19:34.350 --> 00:19:34.360 align:start position:0% cryptographers actually working on 00:19:34.360 --> 00:19:37.430 align:start position:0% cryptographers actually working on this<00:19:35.360> um<00:19:35.720> that's<00:19:35.880> a<00:19:36.080> great<00:19:36.280> question<00:19:36.840> I<00:19:36.919> will<00:19:37.360> I 00:19:37.430 --> 00:19:37.440 align:start position:0% this um that's a great question I will I 00:19:37.440 --> 00:19:39.029 align:start position:0% this um that's a great question I will I will<00:19:37.640> first<00:19:37.880> say<00:19:38.080> that<00:19:38.240> I<00:19:38.320> will<00:19:38.480> not<00:19:38.720> bet 00:19:39.029 --> 00:19:39.039 align:start position:0% will first say that I will not bet 00:19:39.039 --> 00:19:40.950 align:start position:0% will first say that I will not bet against<00:19:39.520> cryptography<00:19:40.360> I<00:19:40.440> know<00:19:40.640> all<00:19:40.799> the 00:19:40.950 --> 00:19:40.960 align:start position:0% against cryptography I know all the 00:19:40.960 --> 00:19:42.990 align:start position:0% against cryptography I know all the researchers<00:19:41.520> in<00:19:41.720> this<00:19:41.880> field<00:19:42.360> they're<00:19:42.600> making 00:19:42.990 --> 00:19:43.000 align:start position:0% researchers in this field they're making 00:19:43.000 --> 00:19:45.909 align:start position:0% researchers in this field they're making tremendous<00:19:43.600> progress<00:19:44.320> uh<00:19:44.440> in<00:19:44.679> doing<00:19:45.039> this<00:19:45.559> but 00:19:45.909 --> 00:19:45.919 align:start position:0% tremendous progress uh in doing this but 00:19:45.919 --> 00:19:47.950 align:start position:0% tremendous progress uh in doing this but will<00:19:46.159> it<00:19:46.520> accelerate<00:19:47.159> as<00:19:47.280> much<00:19:47.480> as<00:19:47.679> zero 00:19:47.950 --> 00:19:47.960 align:start position:0% will it accelerate as much as zero 00:19:47.960 --> 00:19:50.390 align:start position:0% will it accelerate as much as zero knowledge<00:19:48.360> and<00:19:48.559> MPC<00:19:49.559> uh<00:19:49.720> I<00:19:49.840> think<00:19:50.039> that's<00:19:50.280> a 00:19:50.390 --> 00:19:50.400 align:start position:0% knowledge and MPC uh I think that's a 00:19:50.400 --> 00:19:52.430 align:start position:0% knowledge and MPC uh I think that's a little<00:19:50.600> bit<00:19:50.760> of<00:19:50.880> a<00:19:51.039> different<00:19:51.440> question<00:19:52.280> it 00:19:52.430 --> 00:19:52.440 align:start position:0% little bit of a different question it 00:19:52.440 --> 00:19:55.350 align:start position:0% little bit of a different question it really<00:19:52.919> comes<00:19:53.280> from<00:19:54.159> is<00:19:54.520> the<00:19:54.679> community 00:19:55.350 --> 00:19:55.360 align:start position:0% really comes from is the community 00:19:55.360 --> 00:19:57.830 align:start position:0% really comes from is the community invested<00:19:56.080> in<00:19:56.320> solving<00:19:56.799> that<00:19:57.039> problem<00:19:57.559> let's 00:19:57.830 --> 00:19:57.840 align:start position:0% invested in solving that problem let's 00:19:57.840 --> 00:19:59.350 align:start position:0% invested in solving that problem let's take<00:19:58.120> the<00:19:58.320> the<00:19:58.440> bit<00:19:58.679> bit<00:19:58.799> coin<00:19:59.000> signing 00:19:59.350 --> 00:19:59.360 align:start position:0% take the the bit bit coin signing 00:19:59.360 --> 00:20:01.310 align:start position:0% take the the bit bit coin signing example<00:19:59.840> you<00:19:59.960> don't<00:20:00.320> have<00:20:00.600> this<00:20:00.840> particular 00:20:01.310 --> 00:20:01.320 align:start position:0% example you don't have this particular 00:20:01.320 --> 00:20:03.270 align:start position:0% example you don't have this particular op<00:20:01.600> code<00:20:01.880> that<00:20:02.000> you<00:20:02.159> want<00:20:02.720> that<00:20:02.840> will<00:20:03.000> allow 00:20:03.270 --> 00:20:03.280 align:start position:0% op code that you want that will allow 00:20:03.280 --> 00:20:05.470 align:start position:0% op code that you want that will allow you<00:20:03.440> to<00:20:03.640> verify<00:20:04.000> zero<00:20:04.280> knowledge<00:20:04.640> proofs<00:20:05.360> uh 00:20:05.470 --> 00:20:05.480 align:start position:0% you to verify zero knowledge proofs uh 00:20:05.480 --> 00:20:07.789 align:start position:0% you to verify zero knowledge proofs uh in<00:20:05.640> my<00:20:05.840> opinion<00:20:06.480> well<00:20:06.880> if<00:20:07.240> the<00:20:07.360> Bitcoin 00:20:07.789 --> 00:20:07.799 align:start position:0% in my opinion well if the Bitcoin 00:20:07.799 --> 00:20:10.350 align:start position:0% in my opinion well if the Bitcoin Community<00:20:08.360> are<00:20:08.600> willing<00:20:08.880> to<00:20:09.039> bring<00:20:09.400> opcat<00:20:10.240> you 00:20:10.350 --> 00:20:10.360 align:start position:0% Community are willing to bring opcat you 00:20:10.360 --> 00:20:13.029 align:start position:0% Community are willing to bring opcat you can<00:20:10.600> now<00:20:11.039> verify<00:20:11.679> uh<00:20:11.799> zero<00:20:12.080> knowledge<00:20:12.400> proofs 00:20:13.029 --> 00:20:13.039 align:start position:0% can now verify uh zero knowledge proofs 00:20:13.039 --> 00:20:15.830 align:start position:0% can now verify uh zero knowledge proofs that<00:20:13.280> is<00:20:13.760> uh<00:20:13.880> to<00:20:14.000> me<00:20:14.200> an<00:20:14.360> easier<00:20:14.840> path<00:20:15.080> towards 00:20:15.830 --> 00:20:15.840 align:start position:0% that is uh to me an easier path towards 00:20:15.840 --> 00:20:18.310 align:start position:0% that is uh to me an easier path towards that<00:20:16.159> particular<00:20:16.760> goal<00:20:17.360> than<00:20:17.600> trying<00:20:17.880> to<00:20:18.080> make 00:20:18.310 --> 00:20:18.320 align:start position:0% that particular goal than trying to make 00:20:18.320 --> 00:20:21.950 align:start position:0% that particular goal than trying to make a<00:20:18.480> functional<00:20:18.919> encryption<00:20:19.960> problem<00:20:20.960> uh 00:20:21.950 --> 00:20:21.960 align:start position:0% a functional encryption problem uh 00:20:21.960 --> 00:20:25.320 align:start position:0% a functional encryption problem uh solve<00:20:22.960> well<00:20:23.120> I<00:20:23.200> think