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:09.470 align:start position:0% [Music] 00:00:09.470 --> 00:00:09.480 align:start position:0% [Music] 00:00:09.480 --> 00:00:13.230 align:start position:0% [Music] hello<00:00:10.480> um<00:00:10.920> welcome<00:00:11.280> back<00:00:11.880> um 00:00:13.230 --> 00:00:13.240 align:start position:0% hello um welcome back um 00:00:13.240 --> 00:00:16.670 align:start position:0% hello um welcome back um so<00:00:14.240> today<00:00:14.960> I<00:00:15.200> I<00:00:15.280> would<00:00:15.480> be<00:00:15.599> talking<00:00:15.920> about 00:00:16.670 --> 00:00:16.680 align:start position:0% so today I I would be talking about 00:00:16.680 --> 00:00:19.790 align:start position:0% so today I I would be talking about Phantom<00:00:17.160> Zone<00:00:18.119> uh<00:00:18.359> but<00:00:18.920> before<00:00:19.279> I<00:00:19.400> sort<00:00:19.560> of 00:00:19.790 --> 00:00:19.800 align:start position:0% Phantom Zone uh but before I sort of 00:00:19.800 --> 00:00:21.310 align:start position:0% Phantom Zone uh but before I sort of like<00:00:20.039> dive<00:00:20.320> deep<00:00:20.560> into<00:00:20.720> Phantom<00:00:21.039> Zone<00:00:21.199> and 00:00:21.310 --> 00:00:21.320 align:start position:0% like dive deep into Phantom Zone and 00:00:21.320 --> 00:00:23.230 align:start position:0% like dive deep into Phantom Zone and talk<00:00:21.480> about<00:00:21.640> the<00:00:21.760> rest<00:00:21.880> of<00:00:22.000> the<00:00:22.160> things<00:00:23.119> I 00:00:23.230 --> 00:00:23.240 align:start position:0% talk about the rest of the things I 00:00:23.240 --> 00:00:26.269 align:start position:0% talk about the rest of the things I would<00:00:23.840> uh<00:00:24.599> sort<00:00:24.840> of<00:00:25.519> walk<00:00:25.760> you<00:00:25.920> through<00:00:26.119> the 00:00:26.269 --> 00:00:26.279 align:start position:0% would uh sort of walk you through the 00:00:26.279 --> 00:00:31.710 align:start position:0% would uh sort of walk you through the motivation<00:00:26.960> behind<00:00:27.279> Phantom<00:00:28.119> Zone<00:00:29.119> so 00:00:31.710 --> 00:00:31.720 align:start position:0% motivation behind Phantom Zone so 00:00:31.720 --> 00:00:34.110 align:start position:0% motivation behind Phantom Zone so if<00:00:31.840> you<00:00:32.000> guys<00:00:32.160> are<00:00:32.320> familiar<00:00:32.759> with<00:00:33.600> globally 00:00:34.110 --> 00:00:34.120 align:start position:0% if you guys are familiar with globally 00:00:34.120 --> 00:00:37.430 align:start position:0% if you guys are familiar with globally mutually<00:00:34.559> trusted<00:00:34.920> third 00:00:37.430 --> 00:00:37.440 align:start position:0% 00:00:37.440 --> 00:00:40.069 align:start position:0% party<00:00:38.440> I<00:00:38.640> would<00:00:38.840> want<00:00:39.000> to<00:00:39.160> introduce<00:00:39.640> this<00:00:39.920> you 00:00:40.069 --> 00:00:40.079 align:start position:0% party I would want to introduce this you 00:00:40.079 --> 00:00:41.430 align:start position:0% party I would want to introduce this you to<00:00:40.239> this<00:00:40.399> idea<00:00:40.640> of<00:00:40.760> globally<00:00:41.079> mutually 00:00:41.430 --> 00:00:41.440 align:start position:0% to this idea of globally mutually 00:00:41.440 --> 00:00:43.069 align:start position:0% to this idea of globally mutually trusted<00:00:41.840> third 00:00:43.069 --> 00:00:43.079 align:start position:0% trusted third 00:00:43.079 --> 00:00:45.630 align:start position:0% trusted third party<00:00:44.079> what<00:00:44.239> is<00:00:44.399> this<00:00:44.640> m<00:00:44.920> globally<00:00:45.280> mutually 00:00:45.630 --> 00:00:45.640 align:start position:0% party what is this m globally mutually 00:00:45.640 --> 00:00:48.670 align:start position:0% party what is this m globally mutually trusted<00:00:45.960> third<00:00:46.280> party<00:00:47.120> well<00:00:47.480> it<00:00:47.960> provides<00:00:48.360> you 00:00:48.670 --> 00:00:48.680 align:start position:0% trusted third party well it provides you 00:00:48.680 --> 00:00:49.910 align:start position:0% trusted third party well it provides you three 00:00:49.910 --> 00:00:49.920 align:start position:0% three 00:00:49.920 --> 00:00:52.510 align:start position:0% three guarantees<00:00:50.920> the<00:00:51.079> first<00:00:51.320> thing<00:00:51.480> that<00:00:51.640> it<00:00:51.760> says 00:00:52.510 --> 00:00:52.520 align:start position:0% guarantees the first thing that it says 00:00:52.520 --> 00:00:55.430 align:start position:0% guarantees the first thing that it says is<00:00:52.719> that<00:00:53.120> whatever<00:00:53.559> information<00:00:54.559> you<00:00:54.800> send<00:00:55.160> to 00:00:55.430 --> 00:00:55.440 align:start position:0% is that whatever information you send to 00:00:55.440 --> 00:00:58.470 align:start position:0% is that whatever information you send to this<00:00:56.120> third<00:00:56.559> party<00:00:57.320> it<00:00:57.440> will<00:00:57.719> always<00:00:58.199> keep 00:00:58.470 --> 00:00:58.480 align:start position:0% this third party it will always keep 00:00:58.480 --> 00:01:03.149 align:start position:0% this third party it will always keep that<00:00:58.719> private<00:00:59.280> it<00:00:59.399> would<00:00:59.559> not<00:01:00.000> leak<00:01:00.239> it<00:01:00.359> to 00:01:03.149 --> 00:01:03.159 align:start position:0% 00:01:03.159 --> 00:01:05.350 align:start position:0% anyone<00:01:04.159> the<00:01:04.320> second<00:01:04.640> guarantee<00:01:05.040> that<00:01:05.159> it 00:01:05.350 --> 00:01:05.360 align:start position:0% anyone the second guarantee that it 00:01:05.360 --> 00:01:07.030 align:start position:0% anyone the second guarantee that it provides<00:01:05.920> is 00:01:07.030 --> 00:01:07.040 align:start position:0% provides is 00:01:07.040 --> 00:01:09.670 align:start position:0% provides is that<00:01:08.040> all<00:01:08.200> the<00:01:08.400> information<00:01:09.159> that<00:01:09.320> it<00:01:09.439> has 00:01:09.670 --> 00:01:09.680 align:start position:0% that all the information that it has 00:01:09.680 --> 00:01:11.749 align:start position:0% that all the information that it has collected<00:01:10.400> over<00:01:10.720> time<00:01:10.960> from<00:01:11.280> different 00:01:11.749 --> 00:01:11.759 align:start position:0% collected over time from different 00:01:11.759 --> 00:01:14.710 align:start position:0% collected over time from different people<00:01:12.759> you<00:01:12.880> know<00:01:13.080> we<00:01:13.200> have<00:01:13.320> been<00:01:13.439> suing<00:01:13.880> this 00:01:14.710 --> 00:01:14.720 align:start position:0% people you know we have been suing this 00:01:14.720 --> 00:01:16.910 align:start position:0% people you know we have been suing this globally<00:01:15.240> mutually<00:01:15.680> trusted<00:01:16.040> third<00:01:16.320> party 00:01:16.910 --> 00:01:16.920 align:start position:0% globally mutually trusted third party 00:01:16.920 --> 00:01:18.870 align:start position:0% globally mutually trusted third party all<00:01:17.119> the<00:01:17.320> information<00:01:17.799> let's<00:01:18.000> say<00:01:18.119> for<00:01:18.240> a<00:01:18.360> year 00:01:18.870 --> 00:01:18.880 align:start position:0% all the information let's say for a year 00:01:18.880 --> 00:01:20.950 align:start position:0% all the information let's say for a year all<00:01:19.040> the<00:01:19.200> information<00:01:19.640> is<00:01:19.799> collected<00:01:20.159> for<00:01:20.720> all 00:01:20.950 --> 00:01:20.960 align:start position:0% all the information is collected for all 00:01:20.960 --> 00:01:22.469 align:start position:0% all the information is collected for all these<00:01:21.200> years<00:01:21.600> it<00:01:21.680> would<00:01:21.880> always<00:01:22.119> keep<00:01:22.320> the 00:01:22.469 --> 00:01:22.479 align:start position:0% these years it would always keep the 00:01:22.479 --> 00:01:24.069 align:start position:0% these years it would always keep the private<00:01:22.799> and<00:01:22.920> would<00:01:23.079> not<00:01:23.240> allow<00:01:23.560> anyone<00:01:23.880> to 00:01:24.069 --> 00:01:24.079 align:start position:0% private and would not allow anyone to 00:01:24.079 --> 00:01:26.789 align:start position:0% private and would not allow anyone to poke<00:01:24.439> inside<00:01:24.720> its<00:01:24.960> tight<00:01:25.640> inside<00:01:25.920> its 00:01:26.789 --> 00:01:26.799 align:start position:0% poke inside its tight inside its 00:01:26.799 --> 00:01:29.230 align:start position:0% poke inside its tight inside its memory<00:01:27.799> and<00:01:27.960> the<00:01:28.119> third<00:01:28.439> guarantee<00:01:29.000> that<00:01:29.119> it 00:01:29.230 --> 00:01:29.240 align:start position:0% memory and the third guarantee that it 00:01:29.240 --> 00:01:30.830 align:start position:0% memory and the third guarantee that it provides<00:01:29.600> is<00:01:29.720> Mak<00:01:29.920> makes<00:01:30.320> this<00:01:30.479> particular 00:01:30.830 --> 00:01:30.840 align:start position:0% provides is Mak makes this particular 00:01:30.840 --> 00:01:33.109 align:start position:0% provides is Mak makes this particular party<00:01:31.119> very<00:01:31.320> magical<00:01:32.159> is<00:01:32.320> that<00:01:32.520> it<00:01:32.720> you<00:01:32.880> can<00:01:33.000> it 00:01:33.109 --> 00:01:33.119 align:start position:0% party very magical is that it you can it 00:01:33.119 --> 00:01:35.789 align:start position:0% party very magical is that it you can it can<00:01:33.280> compute<00:01:33.840> any<00:01:34.200> arbitary<00:01:34.720> function<00:01:35.560> we 00:01:35.789 --> 00:01:35.799 align:start position:0% can compute any arbitary function we 00:01:35.799 --> 00:01:37.389 align:start position:0% can compute any arbitary function we want<00:01:36.119> it<00:01:36.280> to 00:01:37.389 --> 00:01:37.399 align:start position:0% want it to 00:01:37.399 --> 00:01:40.670 align:start position:0% want it to compute<00:01:38.399> as<00:01:38.560> long<00:01:38.799> as<00:01:39.600> we<00:01:39.799> provided<00:01:40.360> enough 00:01:40.670 --> 00:01:40.680 align:start position:0% compute as long as we provided enough 00:01:40.680 --> 00:01:42.310 align:start position:0% compute as long as we provided enough authorization<00:01:41.320> to<00:01:41.439> be<00:01:41.560> able<00:01:41.720> to<00:01:41.840> compute<00:01:42.159> that 00:01:42.310 --> 00:01:42.320 align:start position:0% authorization to be able to compute that 00:01:42.320 --> 00:01:44.030 align:start position:0% authorization to be able to compute that function<00:01:43.000> and<00:01:43.119> we<00:01:43.360> only<00:01:43.600> output<00:01:43.920> the 00:01:44.030 --> 00:01:44.040 align:start position:0% function and we only output the 00:01:44.040 --> 00:01:48.389 align:start position:0% function and we only output the necessary 00:01:48.389 --> 00:01:48.399 align:start position:0% 00:01:48.399 --> 00:01:50.910 align:start position:0% outputs<00:01:49.399> usually<00:01:49.920> I<00:01:50.040> sort<00:01:50.200> of<00:01:50.360> like<00:01:50.479> refer<00:01:50.759> to 00:01:50.910 --> 00:01:50.920 align:start position:0% outputs usually I sort of like refer to 00:01:50.920 --> 00:01:53.230 align:start position:0% outputs usually I sort of like refer to this<00:01:51.280> this<00:01:51.799> mutually<00:01:52.240> Tred<00:01:52.560> third<00:01:52.799> party<00:01:53.000> as<00:01:53.119> a 00:01:53.230 --> 00:01:53.240 align:start position:0% this this mutually Tred third party as a 00:01:53.240 --> 00:01:55.389 align:start position:0% this this mutually Tred third party as a mutually<00:01:53.600> shared<00:01:54.040> computer<00:01:54.920> and<00:01:55.040> if<00:01:55.119> you<00:01:55.280> guys 00:01:55.389 --> 00:01:55.399 align:start position:0% mutually shared computer and if you guys 00:01:55.399 --> 00:01:56.749 align:start position:0% mutually shared computer and if you guys are<00:01:55.600> familiar<00:01:56.039> with<00:01:56.200> something<00:01:56.479> called<00:01:56.640> the 00:01:56.749 --> 00:01:56.759 align:start position:0% are familiar with something called the 00:01:56.759 --> 00:02:00.670 align:start position:0% are familiar with something called the god<00:01:57.039> protocol<00:01:57.920> this<00:01:58.159> is<00:01:58.360> the<00:01:58.479> god<00:01:58.759> protocol 00:02:00.670 --> 00:02:00.680 align:start position:0% god protocol this is the god protocol 00:02:00.680 --> 00:02:03.270 align:start position:0% god protocol this is the god protocol this<00:02:00.759> is<00:02:00.880> a<00:02:01.000> picture<00:02:01.240> from<00:02:01.439> xabo<00:02:01.960> back<00:02:02.039> in 00:02:03.270 --> 00:02:03.280 align:start position:0% this is a picture from xabo back in 00:02:03.280 --> 00:02:05.429 align:start position:0% this is a picture from xabo back in 1987 00:02:05.429 --> 00:02:05.439 align:start position:0% 1987 00:02:05.439 --> 00:02:09.229 align:start position:0% 1987 um<00:02:06.439> so<00:02:07.280> first<00:02:07.600> observation<00:02:08.160> to<00:02:08.360> make<00:02:08.800> is<00:02:09.000> that 00:02:09.229 --> 00:02:09.239 align:start position:0% um so first observation to make is that 00:02:09.239 --> 00:02:12.350 align:start position:0% um so first observation to make is that if<00:02:09.360> you<00:02:09.640> really<00:02:10.000> want<00:02:11.000> these<00:02:11.599> three 00:02:12.350 --> 00:02:12.360 align:start position:0% if you really want these three 00:02:12.360 --> 00:02:15.470 align:start position:0% if you really want these three guarantees<00:02:13.360> uh<00:02:13.560> to<00:02:13.879> be<00:02:14.879> if<00:02:14.959> you<00:02:15.120> really<00:02:15.280> want 00:02:15.470 --> 00:02:15.480 align:start position:0% guarantees uh to be if you really want 00:02:15.480 --> 00:02:16.990 align:start position:0% guarantees uh to be if you really want this<00:02:15.640> party<00:02:15.920> to<00:02:16.040> be<00:02:16.200> globally<00:02:16.599> mutually 00:02:16.990 --> 00:02:17.000 align:start position:0% this party to be globally mutually 00:02:17.000 --> 00:02:19.589 align:start position:0% this party to be globally mutually trusted<00:02:18.000> we<00:02:18.160> want<00:02:18.440> this<00:02:18.599> party<00:02:18.840> to<00:02:19.000> be<00:02:19.360> party 00:02:19.589 --> 00:02:19.599 align:start position:0% trusted we want this party to be party 00:02:19.599 --> 00:02:21.070 align:start position:0% trusted we want this party to be party to<00:02:19.680> be<00:02:19.840> able<00:02:20.040> to<00:02:20.280> prove<00:02:20.680> these<00:02:20.879> three 00:02:21.070 --> 00:02:21.080 align:start position:0% to be able to prove these three 00:02:21.080 --> 00:02:23.229 align:start position:0% to be able to prove these three guarantees<00:02:21.519> to<00:02:21.800> any<00:02:22.080> individual<00:02:22.959> without 00:02:23.229 --> 00:02:23.239 align:start position:0% guarantees to any individual without 00:02:23.239 --> 00:02:25.229 align:start position:0% guarantees to any individual without requiring<00:02:23.640> any<00:02:23.879> additional<00:02:24.239> interaction 00:02:25.229 --> 00:02:25.239 align:start position:0% requiring any additional interaction 00:02:25.239 --> 00:02:27.070 align:start position:0% requiring any additional interaction which<00:02:25.400> is<00:02:25.599> why<00:02:25.760> we<00:02:25.920> require<00:02:26.280> cryptography<00:02:26.959> we 00:02:27.070 --> 00:02:27.080 align:start position:0% which is why we require cryptography we 00:02:27.080 --> 00:02:28.710 align:start position:0% which is why we require cryptography we cannot<00:02:27.400> just<00:02:27.519> make<00:02:27.680> it<00:02:27.800> on<00:02:28.120> certain<00:02:28.440> legal 00:02:28.710 --> 00:02:28.720 align:start position:0% cannot just make it on certain legal 00:02:28.720 --> 00:02:30.390 align:start position:0% cannot just make it on certain legal agreements<00:02:29.120> or<00:02:29.239> something<00:02:29.440> like<00:02:29.640> that<00:02:30.160> we 00:02:30.390 --> 00:02:30.400 align:start position:0% agreements or something like that we 00:02:30.400 --> 00:02:32.630 align:start position:0% agreements or something like that we require<00:02:30.800> cryptography<00:02:31.360> for<00:02:31.680> building<00:02:32.120> this 00:02:32.630 --> 00:02:32.640 align:start position:0% require cryptography for building this 00:02:32.640 --> 00:02:34.910 align:start position:0% require cryptography for building this the<00:02:32.920> building<00:02:33.319> this<00:02:33.800> um<00:02:34.120> globally<00:02:34.519> mutually 00:02:34.910 --> 00:02:34.920 align:start position:0% the building this um globally mutually 00:02:34.920 --> 00:02:36.790 align:start position:0% the building this um globally mutually trusted<00:02:35.280> shared 00:02:36.790 --> 00:02:36.800 align:start position:0% trusted shared 00:02:36.800 --> 00:02:39.509 align:start position:0% trusted shared computer<00:02:37.800> and<00:02:38.239> we<00:02:38.360> started<00:02:38.760> to<00:02:38.840> build<00:02:39.080> Phantom 00:02:39.509 --> 00:02:39.519 align:start position:0% computer and we started to build Phantom 00:02:39.519 --> 00:02:42.030 align:start position:0% computer and we started to build Phantom Zone<00:02:40.400> to<00:02:40.640> eventually<00:02:41.080> build<00:02:41.480> the<00:02:41.640> god 00:02:42.030 --> 00:02:42.040 align:start position:0% Zone to eventually build the god 00:02:42.040 --> 00:02:44.949 align:start position:0% Zone to eventually build the god protocol<00:02:43.040> but<00:02:43.720> to<00:02:43.920> stick<00:02:44.239> within<00:02:44.480> the<00:02:44.599> Realms 00:02:44.949 --> 00:02:44.959 align:start position:0% protocol but to stick within the Realms 00:02:44.959 --> 00:02:47.149 align:start position:0% protocol but to stick within the Realms of<00:02:45.159> practicality<00:02:46.159> we<00:02:46.280> could<00:02:46.480> only<00:02:46.720> build<00:02:46.959> an 00:02:47.149 --> 00:02:47.159 align:start position:0% of practicality we could only build an 00:02:47.159 --> 00:02:48.910 align:start position:0% of practicality we could only build an Abridged<00:02:47.640> version<00:02:47.959> of 00:02:48.910 --> 00:02:48.920 align:start position:0% Abridged version of 00:02:48.920 --> 00:02:51.470 align:start position:0% Abridged version of it<00:02:49.920> so<00:02:50.080> for<00:02:50.200> the<00:02:50.319> rest<00:02:50.480> of<00:02:50.599> the<00:02:50.760> talk<00:02:51.159> I<00:02:51.280> would 00:02:51.470 --> 00:02:51.480 align:start position:0% it so for the rest of the talk I would 00:02:51.480 --> 00:02:54.910 align:start position:0% it so for the rest of the talk I would be<00:02:51.640> talking<00:02:51.920> about<00:02:52.319> a<00:02:52.840> what<00:02:52.959> is<00:02:53.159> fundom<00:02:53.920> zone 00:02:54.910 --> 00:02:54.920 align:start position:0% be talking about a what is fundom zone 00:02:54.920 --> 00:02:57.070 align:start position:0% be talking about a what is fundom zone why<00:02:55.080> it<00:02:55.239> is<00:02:55.360> an<00:02:55.560> a<00:02:55.680> bridged<00:02:56.080> version<00:02:56.760> of<00:02:56.920> this 00:02:57.070 --> 00:02:57.080 align:start position:0% why it is an a bridged version of this 00:02:57.080 --> 00:02:58.110 align:start position:0% why it is an a bridged version of this God 00:02:58.110 --> 00:02:58.120 align:start position:0% God 00:02:58.120 --> 00:03:00.149 align:start position:0% God protocol<00:02:59.120> and<00:02:59.239> the<00:02:59.360> second<00:02:59.840> important<00:03:00.040> thing 00:03:00.149 --> 00:03:00.159 align:start position:0% protocol and the second important thing 00:03:00.159 --> 00:03:01.589 align:start position:0% protocol and the second important thing that<00:03:00.239> we're<00:03:00.400> talking<00:03:00.640> about<00:03:00.879> is<00:03:01.159> how<00:03:01.319> can<00:03:01.480> we 00:03:01.589 --> 00:03:01.599 align:start position:0% that we're talking about is how can we 00:03:01.599 --> 00:03:04.229 align:start position:0% that we're talking about is how can we push<00:03:01.800> the<00:03:01.920> Frontiers<00:03:02.680> to<00:03:03.120> eventually<00:03:03.920> build 00:03:04.229 --> 00:03:04.239 align:start position:0% push the Frontiers to eventually build 00:03:04.239 --> 00:03:06.990 align:start position:0% push the Frontiers to eventually build the<00:03:04.400> god 00:03:06.990 --> 00:03:07.000 align:start position:0% 00:03:07.000 --> 00:03:10.390 align:start position:0% protocol<00:03:08.000> okay<00:03:08.239> so<00:03:08.799> Phantom<00:03:09.239> Zone<00:03:10.200> The 00:03:10.390 --> 00:03:10.400 align:start position:0% protocol okay so Phantom Zone The 00:03:10.400 --> 00:03:12.750 align:start position:0% protocol okay so Phantom Zone The Abridged<00:03:10.840> version<00:03:11.760> the<00:03:11.879> key<00:03:12.080> idea<00:03:12.319> in<00:03:12.440> Phantom 00:03:12.750 --> 00:03:12.760 align:start position:0% Abridged version the key idea in Phantom 00:03:12.760 --> 00:03:16.509 align:start position:0% Abridged version the key idea in Phantom Zone<00:03:13.480> is<00:03:13.640> something<00:03:14.000> called<00:03:14.360> multiparty<00:03:14.959> fph 00:03:16.509 --> 00:03:16.519 align:start position:0% Zone is something called multiparty fph 00:03:16.519 --> 00:03:19.309 align:start position:0% Zone is something called multiparty fph encryption<00:03:17.519> and<00:03:17.680> for<00:03:17.879> you<00:03:18.000> to<00:03:18.280> describe<00:03:19.159> for 00:03:19.309 --> 00:03:19.319 align:start position:0% encryption and for you to describe for 00:03:19.319 --> 00:03:22.750 align:start position:0% encryption and for you to describe for me<00:03:19.440> to<00:03:19.640> describe<00:03:20.120> you<00:03:20.879> multiart<00:03:21.519> f<00:03:22.120> encryption 00:03:22.750 --> 00:03:22.760 align:start position:0% me to describe you multiart f encryption 00:03:22.760 --> 00:03:24.149 align:start position:0% me to describe you multiart f encryption I'll<00:03:22.920> have<00:03:23.040> to<00:03:23.159> eventually<00:03:23.519> describe<00:03:23.920> what<00:03:24.040> is 00:03:24.149 --> 00:03:24.159 align:start position:0% I'll have to eventually describe what is 00:03:24.159 --> 00:03:26.149 align:start position:0% I'll have to eventually describe what is single<00:03:24.480> party<00:03:24.720> F 00:03:26.149 --> 00:03:26.159 align:start position:0% single party F 00:03:26.159 --> 00:03:29.550 align:start position:0% single party F encryption<00:03:27.159> in<00:03:27.319> single<00:03:27.599> party<00:03:27.840> F<00:03:28.560> encryption 00:03:29.550 --> 00:03:29.560 align:start position:0% encryption in single party F encryption 00:03:29.560 --> 00:03:31.869 align:start position:0% encryption in single party F encryption you<00:03:29.799> you<00:03:30.000> have<00:03:30.400> a<00:03:30.560> single<00:03:30.959> client<00:03:31.599> you<00:03:31.720> know 00:03:31.869 --> 00:03:31.879 align:start position:0% you you have a single client you know 00:03:31.879 --> 00:03:34.190 align:start position:0% you you have a single client you know this<00:03:32.040> guy<00:03:32.200> over<00:03:32.439> here<00:03:32.959> they<00:03:33.080> hold<00:03:33.280> a<00:03:33.480> secret 00:03:34.190 --> 00:03:34.200 align:start position:0% this guy over here they hold a secret 00:03:34.200 --> 00:03:36.550 align:start position:0% this guy over here they hold a secret they<00:03:34.400> keep<00:03:34.599> the<00:03:34.760> secret<00:03:35.080> private<00:03:35.360> to<00:03:35.560> them 00:03:36.550 --> 00:03:36.560 align:start position:0% they keep the secret private to them 00:03:36.560 --> 00:03:38.190 align:start position:0% they keep the secret private to them they<00:03:36.680> can<00:03:36.840> encrypt<00:03:37.239> their<00:03:37.400> information<00:03:38.080> which 00:03:38.190 --> 00:03:38.200 align:start position:0% they can encrypt their information which 00:03:38.200 --> 00:03:40.390 align:start position:0% they can encrypt their information which is<00:03:38.360> a<00:03:38.720> here<00:03:39.159> with<00:03:39.319> the<00:03:39.480> secret<00:03:39.879> and<00:03:40.000> produce<00:03:40.239> an 00:03:40.390 --> 00:03:40.400 align:start position:0% is a here with the secret and produce an 00:03:40.400 --> 00:03:42.589 align:start position:0% is a here with the secret and produce an F<00:03:40.799> Cipher<00:03:41.159> text<00:03:41.840> and<00:03:41.920> then<00:03:42.080> they<00:03:42.200> can<00:03:42.360> send 00:03:42.589 --> 00:03:42.599 align:start position:0% F Cipher text and then they can send 00:03:42.599 --> 00:03:45.190 align:start position:0% F Cipher text and then they can send this<00:03:42.760> F<00:03:43.120> Cipher<00:03:43.439> text<00:03:43.640> to<00:03:43.840> any<00:03:44.120> server<00:03:44.920> and<00:03:45.040> the 00:03:45.190 --> 00:03:45.200 align:start position:0% this F Cipher text to any server and the 00:03:45.200 --> 00:03:47.869 align:start position:0% this F Cipher text to any server and the server<00:03:45.439> can<00:03:45.640> evaluate<00:03:46.599> an<00:03:46.879> any<00:03:47.200> arbitrary 00:03:47.869 --> 00:03:47.879 align:start position:0% server can evaluate an any arbitrary 00:03:47.879 --> 00:03:50.670 align:start position:0% server can evaluate an any arbitrary function<00:03:48.879> on<00:03:49.239> their<00:03:49.720> private<00:03:50.040> input<00:03:50.400> which<00:03:50.519> is 00:03:50.670 --> 00:03:50.680 align:start position:0% function on their private input which is 00:03:50.680 --> 00:03:52.630 align:start position:0% function on their private input which is a<00:03:50.879> and<00:03:51.000> produce<00:03:51.280> an<00:03:51.439> output<00:03:51.760> Cipher<00:03:52.120> text<00:03:52.480> and 00:03:52.630 --> 00:03:52.640 align:start position:0% a and produce an output Cipher text and 00:03:52.640 --> 00:03:55.670 align:start position:0% a and produce an output Cipher text and that<00:03:53.120> the<00:03:54.120> and<00:03:54.400> the<00:03:54.599> client<00:03:54.959> can<00:03:55.200> receive<00:03:55.560> the 00:03:55.670 --> 00:03:55.680 align:start position:0% that the and the client can receive the 00:03:55.680 --> 00:03:57.869 align:start position:0% that the and the client can receive the output<00:03:56.000> surface<00:03:56.400> and<00:03:56.560> decrypt<00:03:57.000> it<00:03:57.519> so<00:03:57.680> this<00:03:57.760> is 00:03:57.869 --> 00:03:57.879 align:start position:0% output surface and decrypt it so this is 00:03:57.879 --> 00:04:00.630 align:start position:0% output surface and decrypt it so this is single<00:03:58.159> party<00:03:58.400> FG 00:04:00.630 --> 00:04:00.640 align:start position:0% single party FG 00:04:00.640 --> 00:04:03.470 align:start position:0% single party FG coming<00:04:00.879> to<00:04:01.000> multiparty<00:04:01.720> F<00:04:02.720> Well<00:04:02.959> the<00:04:03.120> key<00:04:03.280> idea 00:04:03.470 --> 00:04:03.480 align:start position:0% coming to multiparty F Well the key idea 00:04:03.480 --> 00:04:05.429 align:start position:0% coming to multiparty F Well the key idea in<00:04:03.560> multiparty<00:04:04.040> fig<00:04:04.439> is<00:04:04.560> that<00:04:04.680> you<00:04:04.840> split<00:04:05.239> this 00:04:05.429 --> 00:04:05.439 align:start position:0% in multiparty fig is that you split this 00:04:05.439 --> 00:04:07.910 align:start position:0% in multiparty fig is that you split this secret<00:04:06.159> which<00:04:06.280> is<00:04:06.480> held<00:04:06.920> private<00:04:07.280> by<00:04:07.400> a<00:04:07.519> single 00:04:07.910 --> 00:04:07.920 align:start position:0% secret which is held private by a single 00:04:07.920 --> 00:04:10.229 align:start position:0% secret which is held private by a single client<00:04:08.159> in<00:04:08.280> single<00:04:08.560> party<00:04:08.760> F<00:04:09.480> among<00:04:09.879> many 00:04:10.229 --> 00:04:10.239 align:start position:0% client in single party F among many 00:04:10.239 --> 00:04:13.110 align:start position:0% client in single party F among many clients<00:04:10.879> so<00:04:11.079> you<00:04:11.239> have<00:04:11.360> s0<00:04:11.799> S1<00:04:12.159> S2<00:04:12.560> as<00:04:12.760> secret 00:04:13.110 --> 00:04:13.120 align:start position:0% clients so you have s0 S1 S2 as secret 00:04:13.120 --> 00:04:14.949 align:start position:0% clients so you have s0 S1 S2 as secret Shard<00:04:13.519> split<00:04:13.879> among<00:04:14.200> these<00:04:14.439> three<00:04:14.680> people 00:04:14.949 --> 00:04:14.959 align:start position:0% Shard split among these three people 00:04:14.959 --> 00:04:17.069 align:start position:0% Shard split among these three people over 00:04:17.069 --> 00:04:17.079 align:start position:0% over 00:04:17.079 --> 00:04:20.189 align:start position:0% over here<00:04:18.079> the<00:04:18.239> first<00:04:18.519> step<00:04:18.840> in<00:04:18.959> multiparty<00:04:19.519> F<00:04:20.079> is 00:04:20.189 --> 00:04:20.199 align:start position:0% here the first step in multiparty F is 00:04:20.199 --> 00:04:22.430 align:start position:0% here the first step in multiparty F is something<00:04:20.479> called<00:04:20.720> Collective<00:04:21.239> p<00:04:21.880> uh<00:04:22.000> public 00:04:22.430 --> 00:04:22.440 align:start position:0% something called Collective p uh public 00:04:22.440 --> 00:04:24.430 align:start position:0% something called Collective p uh public generation<00:04:23.120> so<00:04:23.320> all<00:04:23.520> these<00:04:23.759> three<00:04:24.000> parties 00:04:24.430 --> 00:04:24.440 align:start position:0% generation so all these three parties 00:04:24.440 --> 00:04:26.150 align:start position:0% generation so all these three parties come<00:04:24.800> together<00:04:25.400> and<00:04:25.520> they<00:04:25.680> generate<00:04:26.000> the 00:04:26.150 --> 00:04:26.160 align:start position:0% come together and they generate the 00:04:26.160 --> 00:04:28.550 align:start position:0% come together and they generate the collective 00:04:28.550 --> 00:04:28.560 align:start position:0% collective 00:04:28.560 --> 00:04:31.070 align:start position:0% collective publicy<00:04:29.560> and<00:04:29.720> and<00:04:29.919> then<00:04:30.400> all<00:04:30.639> these<00:04:30.840> three 00:04:31.070 --> 00:04:31.080 align:start position:0% publicy and and then all these three 00:04:31.080 --> 00:04:33.350 align:start position:0% publicy and and then all these three parties<00:04:31.560> using<00:04:31.880> the<00:04:32.080> collective<00:04:32.560> public<00:04:32.880> key 00:04:33.350 --> 00:04:33.360 align:start position:0% parties using the collective public key 00:04:33.360 --> 00:04:35.629 align:start position:0% parties using the collective public key encryp<00:04:33.800> their<00:04:34.000> private<00:04:34.320> inputs<00:04:35.160> and<00:04:35.280> produce 00:04:35.629 --> 00:04:35.639 align:start position:0% encryp their private inputs and produce 00:04:35.639 --> 00:04:38.909 align:start position:0% encryp their private inputs and produce F<00:04:36.080> Cipher<00:04:36.560> text<00:04:37.560> and<00:04:37.800> then<00:04:38.039> they<00:04:38.639> then<00:04:38.800> they 00:04:38.909 --> 00:04:38.919 align:start position:0% F Cipher text and then they then they 00:04:38.919 --> 00:04:41.909 align:start position:0% F Cipher text and then they then they send<00:04:39.120> their<00:04:39.280> F<00:04:39.639> cotex<00:04:40.400> to<00:04:40.600> the<00:04:40.759> server<00:04:41.479> server 00:04:41.909 --> 00:04:41.919 align:start position:0% send their F cotex to the server server 00:04:41.919 --> 00:04:44.590 align:start position:0% send their F cotex to the server server executes<00:04:42.320> a<00:04:42.479> Mary<00:04:42.919> function<00:04:43.479> on<00:04:43.680> the<00:04:43.800> F<00:04:44.160> cotex 00:04:44.590 --> 00:04:44.600 align:start position:0% executes a Mary function on the F cotex 00:04:44.600 --> 00:04:48.189 align:start position:0% executes a Mary function on the F cotex and<00:04:44.680> produce<00:04:44.960> an<00:04:45.039> F<00:04:46.000> uh<00:04:46.400> produce<00:04:46.680> an<00:04:46.800> F 00:04:48.189 --> 00:04:48.199 align:start position:0% and produce an F uh produce an F 00:04:48.199 --> 00:04:50.909 align:start position:0% and produce an F uh produce an F output<00:04:49.199> the<00:04:49.360> key<00:04:49.520> thing<00:04:49.680> to<00:04:49.840> notice<00:04:50.240> here<00:04:50.720> is 00:04:50.909 --> 00:04:50.919 align:start position:0% output the key thing to notice here is 00:04:50.919 --> 00:04:53.670 align:start position:0% output the key thing to notice here is that<00:04:51.600> all<00:04:51.919> these<00:04:52.240> parties<00:04:52.840> would<00:04:53.120> have<00:04:53.320> to 00:04:53.670 --> 00:04:53.680 align:start position:0% that all these parties would have to 00:04:53.680 --> 00:04:56.749 align:start position:0% that all these parties would have to produce<00:04:54.080> a<00:04:54.280> decryption<00:04:54.800> share<00:04:55.800> to<00:04:56.360> eventually 00:04:56.749 --> 00:04:56.759 align:start position:0% produce a decryption share to eventually 00:04:56.759 --> 00:04:59.350 align:start position:0% produce a decryption share to eventually decrypt<00:04:57.160> the<00:04:57.560> output<00:04:57.919> cext<00:04:58.520> here<00:04:59.080> so<00:04:59.240> they 00:04:59.350 --> 00:04:59.360 align:start position:0% decrypt the output cext here so they 00:04:59.360 --> 00:05:00.990 align:start position:0% decrypt the output cext here so they produce<00:04:59.840> the<00:04:59.919> decryption<00:05:00.280> share<00:05:00.560> using<00:05:00.800> the 00:05:00.990 --> 00:05:01.000 align:start position:0% produce the decryption share using the 00:05:01.000 --> 00:05:03.110 align:start position:0% produce the decryption share using the secret<00:05:01.320> shards<00:05:02.160> and<00:05:02.360> then<00:05:02.560> they<00:05:02.680> send<00:05:02.880> it<00:05:03.000> to 00:05:03.110 --> 00:05:03.120 align:start position:0% secret shards and then they send it to 00:05:03.120 --> 00:05:05.310 align:start position:0% secret shards and then they send it to each<00:05:03.280> other<00:05:03.639> and<00:05:03.800> then<00:05:04.039> only<00:05:04.479> they're<00:05:04.680> able<00:05:04.880> to 00:05:05.310 --> 00:05:05.320 align:start position:0% each other and then only they're able to 00:05:05.320 --> 00:05:07.070 align:start position:0% each other and then only they're able to uh<00:05:05.479> decrypt<00:05:05.800> the<00:05:05.880> art<00:05:06.080> with<00:05:06.199> Cipher<00:05:06.520> text 00:05:07.070 --> 00:05:07.080 align:start position:0% uh decrypt the art with Cipher text 00:05:07.080 --> 00:05:08.590 align:start position:0% uh decrypt the art with Cipher text because<00:05:07.280> in<00:05:07.440> this<00:05:07.600> case<00:05:07.880> the<00:05:08.039> secret<00:05:08.400> was 00:05:08.590 --> 00:05:08.600 align:start position:0% because in this case the secret was 00:05:08.600 --> 00:05:10.749 align:start position:0% because in this case the secret was split<00:05:08.919> among<00:05:09.160> all<00:05:09.320> these 00:05:10.749 --> 00:05:10.759 align:start position:0% split among all these 00:05:10.759 --> 00:05:13.749 align:start position:0% split among all these parties<00:05:11.759> so<00:05:12.600> why<00:05:12.800> is<00:05:13.000> Phantom<00:05:13.400> Zone<00:05:13.560> an<00:05:13.639> a 00:05:13.749 --> 00:05:13.759 align:start position:0% parties so why is Phantom Zone an a 00:05:13.759 --> 00:05:18.230 align:start position:0% parties so why is Phantom Zone an a bridged<00:05:14.400> version<00:05:15.400> well<00:05:15.880> because<00:05:16.639> Phantom 00:05:18.230 --> 00:05:18.240 align:start position:0% bridged version well because Phantom 00:05:18.240 --> 00:05:21.070 align:start position:0% bridged version well because Phantom Zone<00:05:19.240> assuming<00:05:19.840> that<00:05:20.199> in<00:05:20.319> the<00:05:20.400> future<00:05:20.720> we<00:05:20.880> able 00:05:21.070 --> 00:05:21.080 align:start position:0% Zone assuming that in the future we able 00:05:21.080 --> 00:05:23.029 align:start position:0% Zone assuming that in the future we able to<00:05:21.199> add<00:05:21.360> publicly<00:05:21.840> vable<00:05:22.360> Effigy<00:05:22.800> to<00:05:22.919> a 00:05:23.029 --> 00:05:23.039 align:start position:0% to add publicly vable Effigy to a 00:05:23.039 --> 00:05:26.430 align:start position:0% to add publicly vable Effigy to a Phantom<00:05:23.360> Zone<00:05:24.360> can<00:05:24.600> only<00:05:25.000> guarantee<00:05:25.919> the 00:05:26.430 --> 00:05:26.440 align:start position:0% Phantom Zone can only guarantee the 00:05:26.440 --> 00:05:28.550 align:start position:0% Phantom Zone can only guarantee the three<00:05:26.720> guarantees<00:05:27.160> that<00:05:27.280> I<00:05:27.440> talk<00:05:27.720> about<00:05:28.440> in 00:05:28.550 --> 00:05:28.560 align:start position:0% three guarantees that I talk about in 00:05:28.560 --> 00:05:31.070 align:start position:0% three guarantees that I talk about in the<00:05:28.800> god<00:05:29.080> protocol<00:05:29.919> to<00:05:30.120> only<00:05:30.360> the<00:05:30.520> holders<00:05:30.960> of 00:05:31.070 --> 00:05:31.080 align:start position:0% the god protocol to only the holders of 00:05:31.080 --> 00:05:34.150 align:start position:0% the god protocol to only the holders of the<00:05:31.280> secret<00:05:31.680> shots<00:05:32.479> it<00:05:32.680> cannot<00:05:33.639> guarantee 00:05:34.150 --> 00:05:34.160 align:start position:0% the secret shots it cannot guarantee 00:05:34.160 --> 00:05:36.469 align:start position:0% the secret shots it cannot guarantee these<00:05:34.400> three<00:05:34.720> guarantees<00:05:35.680> to<00:05:36.039> everyone 00:05:36.469 --> 00:05:36.479 align:start position:0% these three guarantees to everyone 00:05:36.479 --> 00:05:37.909 align:start position:0% these three guarantees to everyone around<00:05:36.680> the 00:05:37.909 --> 00:05:37.919 align:start position:0% around the 00:05:37.919 --> 00:05:40.189 align:start position:0% around the globe<00:05:38.919> which<00:05:39.039> is<00:05:39.199> why<00:05:39.360> Phantom<00:05:39.720> Zone<00:05:39.919> is<00:05:40.039> just 00:05:40.189 --> 00:05:40.199 align:start position:0% globe which is why Phantom Zone is just 00:05:40.199 --> 00:05:42.469 align:start position:0% globe which is why Phantom Zone is just an<00:05:40.360> abised<00:05:40.800> version<00:05:41.080> of 00:05:42.469 --> 00:05:42.479 align:start position:0% an abised version of 00:05:42.479 --> 00:05:46.110 align:start position:0% an abised version of it<00:05:43.479> okay<00:05:44.120> so<00:05:44.280> you<00:05:44.479> might<00:05:44.680> wonder<00:05:45.680> how<00:05:45.840> do<00:05:45.960> we 00:05:46.110 --> 00:05:46.120 align:start position:0% it okay so you might wonder how do we 00:05:46.120 --> 00:05:47.830 align:start position:0% it okay so you might wonder how do we build<00:05:46.400> towards<00:05:46.680> the<00:05:46.840> god<00:05:47.080> protocol<00:05:47.600> like<00:05:47.720> how 00:05:47.830 --> 00:05:47.840 align:start position:0% build towards the god protocol like how 00:05:47.840 --> 00:05:50.189 align:start position:0% build towards the god protocol like how do<00:05:47.960> we<00:05:48.080> even<00:05:48.280> do 00:05:50.189 --> 00:05:50.199 align:start position:0% do we even do 00:05:50.199 --> 00:05:52.110 align:start position:0% do we even do it 00:05:52.110 --> 00:05:52.120 align:start position:0% it 00:05:52.120 --> 00:05:54.469 align:start position:0% it well<00:05:53.120> what<00:05:53.360> I<00:05:53.440> would<00:05:53.680> like<00:05:53.840> to<00:05:54.000> say<00:05:54.199> at<00:05:54.319> the 00:05:54.469 --> 00:05:54.479 align:start position:0% well what I would like to say at the 00:05:54.479 --> 00:05:56.189 align:start position:0% well what I would like to say at the moment<00:05:54.800> is<00:05:55.160> you<00:05:55.280> know<00:05:55.560> I<00:05:55.639> would<00:05:55.759> have<00:05:55.880> loved<00:05:56.120> to 00:05:56.189 --> 00:05:56.199 align:start position:0% moment is you know I would have loved to 00:05:56.199 --> 00:05:57.390 align:start position:0% moment is you know I would have loved to say<00:05:56.440> that<00:05:56.600> you<00:05:56.680> know<00:05:56.840> after<00:05:57.039> a<00:05:57.120> lot<00:05:57.280> of 00:05:57.390 --> 00:05:57.400 align:start position:0% say that you know after a lot of 00:05:57.400 --> 00:05:59.029 align:start position:0% say that you know after a lot of research<00:05:57.720> and<00:05:58.000> a<00:05:58.080> lot<00:05:58.199> of<00:05:58.360> like<00:05:58.520> five<00:05:58.720> years<00:05:58.880> of 00:05:59.029 --> 00:05:59.039 align:start position:0% research and a lot of like five years of 00:05:59.039 --> 00:06:00.390 align:start position:0% research and a lot of like five years of research<00:05:59.319> we<00:05:59.440> have<00:05:59.639> figured<00:05:59.880> of<00:06:00.000> the<00:06:00.120> solution 00:06:00.390 --> 00:06:00.400 align:start position:0% research we have figured of the solution 00:06:00.400 --> 00:06:03.909 align:start position:0% research we have figured of the solution to<00:06:00.600> get<00:06:00.759> build<00:06:00.960> the<00:06:01.080> god<00:06:01.720> protocol<00:06:02.720> but<00:06:03.440> now 00:06:03.909 --> 00:06:03.919 align:start position:0% to get build the god protocol but now 00:06:03.919 --> 00:06:06.270 align:start position:0% to get build the god protocol but now like<00:06:04.199> there<00:06:04.400> no<00:06:04.560> at<00:06:04.720> lightening<00:06:05.039> thoughts 00:06:06.270 --> 00:06:06.280 align:start position:0% like there no at lightening thoughts 00:06:06.280 --> 00:06:09.150 align:start position:0% like there no at lightening thoughts here<00:06:07.280> and<00:06:07.440> there's<00:06:07.759> one<00:06:08.000> obvious<00:06:08.400> answer<00:06:08.960> to 00:06:09.150 --> 00:06:09.160 align:start position:0% here and there's one obvious answer to 00:06:09.160 --> 00:06:10.710 align:start position:0% here and there's one obvious answer to building<00:06:09.560> to<00:06:09.720> eventually<00:06:10.039> building<00:06:10.319> the<00:06:10.440> god 00:06:10.710 --> 00:06:10.720 align:start position:0% building to eventually building the god 00:06:10.720 --> 00:06:15.469 align:start position:0% building to eventually building the god protocol<00:06:11.680> which<00:06:11.840> is<00:06:12.120> program 00:06:15.469 --> 00:06:15.479 align:start position:0% 00:06:15.479 --> 00:06:18.110 align:start position:0% officiation<00:06:16.479> what's<00:06:16.720> program 00:06:18.110 --> 00:06:18.120 align:start position:0% officiation what's program 00:06:18.120 --> 00:06:20.309 align:start position:0% officiation what's program officiation<00:06:19.120> well<00:06:19.360> to<00:06:19.560> Simply<00:06:19.880> describe<00:06:20.199> your 00:06:20.309 --> 00:06:20.319 align:start position:0% officiation well to Simply describe your 00:06:20.319 --> 00:06:21.150 align:start position:0% officiation well to Simply describe your program 00:06:21.150 --> 00:06:21.160 align:start position:0% program 00:06:21.160 --> 00:06:23.469 align:start position:0% program officiation<00:06:22.160> let's<00:06:22.319> just<00:06:22.560> assume<00:06:23.160> that<00:06:23.319> you 00:06:23.469 --> 00:06:23.479 align:start position:0% officiation let's just assume that you 00:06:23.479 --> 00:06:26.749 align:start position:0% officiation let's just assume that you have<00:06:23.680> function<00:06:24.440> f<00:06:25.440> right<00:06:26.199> what<00:06:26.319> you<00:06:26.400> can<00:06:26.560> do 00:06:26.749 --> 00:06:26.759 align:start position:0% have function f right what you can do 00:06:26.759 --> 00:06:28.550 align:start position:0% have function f right what you can do with<00:06:26.880> program<00:06:27.240> ofation<00:06:27.759> is<00:06:27.880> you<00:06:28.080> take<00:06:28.400> this 00:06:28.550 --> 00:06:28.560 align:start position:0% with program ofation is you take this 00:06:28.560 --> 00:06:30.550 align:start position:0% with program ofation is you take this function<00:06:29.000> f<00:06:29.639> and<00:06:29.840> perform<00:06:30.280> some 00:06:30.550 --> 00:06:30.560 align:start position:0% function f and perform some 00:06:30.560 --> 00:06:32.870 align:start position:0% function f and perform some Transformations<00:06:31.560> on<00:06:31.759> this<00:06:31.919> function<00:06:32.319> f<00:06:32.720> and 00:06:32.870 --> 00:06:32.880 align:start position:0% Transformations on this function f and 00:06:32.880 --> 00:06:35.150 align:start position:0% Transformations on this function f and produce<00:06:33.199> an<00:06:33.400> offs<00:06:33.639> skated 00:06:35.150 --> 00:06:35.160 align:start position:0% produce an offs skated 00:06:35.160 --> 00:06:37.830 align:start position:0% produce an offs skated circuit<00:06:36.160> you<00:06:36.280> can<00:06:36.479> give<00:06:36.720> this<00:06:36.880> off<00:06:37.360> circuit<00:06:37.639> to 00:06:37.830 --> 00:06:37.840 align:start position:0% circuit you can give this off circuit to 00:06:37.840 --> 00:06:40.990 align:start position:0% circuit you can give this off circuit to someone<00:06:38.280> else<00:06:39.280> and<00:06:39.520> program<00:06:39.880> Association 00:06:40.990 --> 00:06:41.000 align:start position:0% someone else and program Association 00:06:41.000 --> 00:06:43.070 align:start position:0% someone else and program Association guarantees<00:06:42.000> that<00:06:42.199> the<00:06:42.360> only<00:06:42.680> thing<00:06:42.840> that<00:06:42.960> you 00:06:43.070 --> 00:06:43.080 align:start position:0% guarantees that the only thing that you 00:06:43.080 --> 00:06:45.070 align:start position:0% guarantees that the only thing that you can<00:06:43.240> learn<00:06:43.680> from<00:06:44.000> that<00:06:44.160> offset<00:06:44.680> circuit<00:06:44.960> is 00:06:45.070 --> 00:06:45.080 align:start position:0% can learn from that offset circuit is 00:06:45.080 --> 00:06:48.029 align:start position:0% can learn from that offset circuit is the<00:06:45.240> input<00:06:45.639> to<00:06:45.840> Output<00:06:46.240> map<00:06:46.520> and<00:06:46.720> nothing 00:06:48.029 --> 00:06:48.039 align:start position:0% the input to Output map and nothing 00:06:48.039 --> 00:06:50.430 align:start position:0% the input to Output map and nothing else<00:06:49.039> now<00:06:49.319> you<00:06:49.440> might<00:06:49.639> be<00:06:49.759> wondering<00:06:50.160> why<00:06:50.319> is 00:06:50.430 --> 00:06:50.440 align:start position:0% else now you might be wondering why is 00:06:50.440 --> 00:06:52.589 align:start position:0% else now you might be wondering why is this<00:06:50.639> useful<00:06:51.479> because<00:06:51.759> if<00:06:51.880> the<00:06:52.039> function<00:06:52.400> is 00:06:52.589 --> 00:06:52.599 align:start position:0% this useful because if the function is 00:06:52.599 --> 00:06:54.830 align:start position:0% this useful because if the function is Trivial<00:06:53.280> then<00:06:53.479> you<00:06:53.639> can<00:06:53.919> e<00:06:54.160> easily<00:06:54.479> learn<00:06:54.720> it 00:06:54.830 --> 00:06:54.840 align:start position:0% Trivial then you can e easily learn it 00:06:54.840 --> 00:06:56.469 align:start position:0% Trivial then you can e easily learn it from<00:06:55.000> the<00:06:55.120> input<00:06:55.440> to<00:06:55.560> Output 00:06:56.469 --> 00:06:56.479 align:start position:0% from the input to Output 00:06:56.479 --> 00:06:59.869 align:start position:0% from the input to Output map<00:06:57.479> program<00:06:57.879> OBS<00:06:58.080> cation<00:06:58.479> becomes<00:06:59.120> easy 00:06:59.869 --> 00:06:59.879 align:start position:0% map program OBS cation becomes easy 00:06:59.879 --> 00:07:02.790 align:start position:0% map program OBS cation becomes easy become<00:07:00.319> becomes<00:07:00.800> very<00:07:01.360> interesting<00:07:02.360> when<00:07:02.560> you 00:07:02.790 --> 00:07:02.800 align:start position:0% become becomes very interesting when you 00:07:02.800 --> 00:07:05.589 align:start position:0% become becomes very interesting when you sort<00:07:03.039> of<00:07:03.319> like<00:07:04.280> OBS<00:07:04.599> secate<00:07:04.919> a<00:07:05.120> program<00:07:05.479> that 00:07:05.589 --> 00:07:05.599 align:start position:0% sort of like OBS secate a program that 00:07:05.599 --> 00:07:08.270 align:start position:0% sort of like OBS secate a program that is<00:07:05.680> a<00:07:05.840> cryptographic<00:07:06.520> function<00:07:07.120> for<00:07:07.319> example 00:07:08.270 --> 00:07:08.280 align:start position:0% is a cryptographic function for example 00:07:08.280 --> 00:07:11.230 align:start position:0% is a cryptographic function for example let's<00:07:08.479> just<00:07:08.680> say<00:07:09.080> that<00:07:09.680> I<00:07:10.000> take 00:07:11.230 --> 00:07:11.240 align:start position:0% let's just say that I take 00:07:11.240 --> 00:07:14.150 align:start position:0% let's just say that I take uh<00:07:12.240> I<00:07:12.360> take<00:07:12.479> a<00:07:12.680> function<00:07:13.400> I<00:07:13.560> take<00:07:13.680> a<00:07:13.800> function 00:07:14.150 --> 00:07:14.160 align:start position:0% uh I take a function I take a function 00:07:14.160 --> 00:07:16.430 align:start position:0% uh I take a function I take a function that<00:07:14.280> is<00:07:14.479> that<00:07:14.639> decrypts<00:07:15.639> any<00:07:15.879> Cipher<00:07:16.199> text 00:07:16.430 --> 00:07:16.440 align:start position:0% that is that decrypts any Cipher text 00:07:16.440 --> 00:07:18.589 align:start position:0% that is that decrypts any Cipher text that<00:07:16.520> is<00:07:16.639> encrypted<00:07:17.039> to<00:07:17.160> my<00:07:17.319> public<00:07:17.639> key<00:07:18.440> right 00:07:18.589 --> 00:07:18.599 align:start position:0% that is encrypted to my public key right 00:07:18.599 --> 00:07:20.950 align:start position:0% that is encrypted to my public key right so<00:07:18.720> I<00:07:18.840> take<00:07:18.960> a<00:07:19.120> function<00:07:19.840> and<00:07:20.000> this<00:07:20.160> function 00:07:20.950 --> 00:07:20.960 align:start position:0% so I take a function and this function 00:07:20.960 --> 00:07:23.589 align:start position:0% so I take a function and this function has<00:07:21.160> my<00:07:21.319> secret<00:07:21.720> key<00:07:22.000> and<00:07:22.120> it<00:07:22.280> decrypts<00:07:23.280> any 00:07:23.589 --> 00:07:23.599 align:start position:0% has my secret key and it decrypts any 00:07:23.599 --> 00:07:25.710 align:start position:0% has my secret key and it decrypts any cyhex<00:07:24.120> that<00:07:24.199> was<00:07:24.360> encrypted<00:07:24.759> to<00:07:24.919> me<00:07:25.240> using<00:07:25.520> my 00:07:25.710 --> 00:07:25.720 align:start position:0% cyhex that was encrypted to me using my 00:07:25.720 --> 00:07:26.550 align:start position:0% cyhex that was encrypted to me using my public 00:07:26.550 --> 00:07:26.560 align:start position:0% public 00:07:26.560 --> 00:07:28.430 align:start position:0% public key<00:07:27.560> and<00:07:27.680> I<00:07:27.800> perform<00:07:28.160> certain 00:07:28.430 --> 00:07:28.440 align:start position:0% key and I perform certain 00:07:28.440 --> 00:07:30.390 align:start position:0% key and I perform certain Transformations<00:07:29.039> using<00:07:29.280> prog<00:07:29.720> tication<00:07:30.240> to 00:07:30.390 --> 00:07:30.400 align:start position:0% Transformations using prog tication to 00:07:30.400 --> 00:07:34.270 align:start position:0% Transformations using prog tication to this<00:07:30.560> function<00:07:31.160> and<00:07:31.319> produce<00:07:31.680> an<00:07:32.280> obic 00:07:34.270 --> 00:07:34.280 align:start position:0% this function and produce an obic 00:07:34.280 --> 00:07:36.629 align:start position:0% this function and produce an obic circuit<00:07:35.280> I<00:07:35.440> give<00:07:35.639> this<00:07:35.759> obic<00:07:36.240> circuit<00:07:36.520> to 00:07:36.629 --> 00:07:36.639 align:start position:0% circuit I give this obic circuit to 00:07:36.639 --> 00:07:38.629 align:start position:0% circuit I give this obic circuit to someone<00:07:36.919> else<00:07:37.720> what<00:07:37.879> they<00:07:38.000> can<00:07:38.120> do<00:07:38.319> is<00:07:38.479> that 00:07:38.629 --> 00:07:38.639 align:start position:0% someone else what they can do is that 00:07:38.639 --> 00:07:40.550 align:start position:0% someone else what they can do is that they<00:07:38.759> can<00:07:38.919> decrypt<00:07:39.599> any<00:07:39.840> Cipher<00:07:40.240> text<00:07:40.479> that 00:07:40.550 --> 00:07:40.560 align:start position:0% they can decrypt any Cipher text that 00:07:40.560 --> 00:07:43.070 align:start position:0% they can decrypt any Cipher text that was<00:07:40.720> encrypted<00:07:41.160> to<00:07:41.319> me<00:07:41.639> using<00:07:41.960> this<00:07:42.120> obus 00:07:43.070 --> 00:07:43.080 align:start position:0% was encrypted to me using this obus 00:07:43.080 --> 00:07:45.869 align:start position:0% was encrypted to me using this obus circuit<00:07:44.080> but<00:07:44.280> they<00:07:44.400> can<00:07:44.639> never<00:07:45.159> ever<00:07:45.520> learn 00:07:45.869 --> 00:07:45.879 align:start position:0% circuit but they can never ever learn 00:07:45.879 --> 00:07:48.469 align:start position:0% circuit but they can never ever learn what<00:07:46.039> the<00:07:46.240> secret<00:07:47.120> is<00:07:47.479> inside<00:07:47.919> that<00:07:48.080> circuit 00:07:48.469 --> 00:07:48.479 align:start position:0% what the secret is inside that circuit 00:07:48.479 --> 00:07:50.749 align:start position:0% what the secret is inside that circuit they<00:07:48.599> can<00:07:48.720> never<00:07:48.919> learn<00:07:49.159> my<00:07:49.280> secret 00:07:50.749 --> 00:07:50.759 align:start position:0% they can never learn my secret 00:07:50.759 --> 00:07:52.270 align:start position:0% they can never learn my secret key 00:07:52.270 --> 00:07:52.280 align:start position:0% key 00:07:52.280 --> 00:07:53.909 align:start position:0% key and 00:07:53.909 --> 00:07:53.919 align:start position:0% and 00:07:53.919 --> 00:07:56.350 align:start position:0% and um<00:07:54.919> and<00:07:55.159> this<00:07:55.280> is<00:07:55.599> these<00:07:55.720> are<00:07:55.879> the<00:07:56.000> class<00:07:56.240> of 00:07:56.350 --> 00:07:56.360 align:start position:0% um and this is these are the class of 00:07:56.360 --> 00:07:57.990 align:start position:0% um and this is these are the class of functions<00:07:56.720> where<00:07:56.879> program<00:07:57.199> autic<00:07:57.720> becomes 00:07:57.990 --> 00:07:58.000 align:start position:0% functions where program autic becomes 00:07:58.000 --> 00:08:00.990 align:start position:0% functions where program autic becomes useful<00:07:58.599> and<00:07:58.759> I'll<00:07:59.080> tie<00:07:59.319> it<00:07:59.879> to<00:08:00.479> to<00:08:00.720> building 00:08:00.990 --> 00:08:01.000 align:start position:0% useful and I'll tie it to to building 00:08:01.000 --> 00:08:04.070 align:start position:0% useful and I'll tie it to to building the<00:08:01.120> god<00:08:01.319> protocol<00:08:01.720> later<00:08:02.080> in<00:08:02.159> the 00:08:04.070 --> 00:08:04.080 align:start position:0% the god protocol later in the 00:08:04.080 --> 00:08:08.430 align:start position:0% the god protocol later in the slides<00:08:05.080> uh<00:08:05.960> okay<00:08:06.159> so<00:08:06.479> now<00:08:07.240> assume<00:08:07.840> that<00:08:08.120> we<00:08:08.240> can 00:08:08.430 --> 00:08:08.440 align:start position:0% slides uh okay so now assume that we can 00:08:08.440 --> 00:08:11.309 align:start position:0% slides uh okay so now assume that we can only<00:08:08.720> build<00:08:09.039> program<00:08:09.440> officiation<00:08:10.120> for<00:08:10.960> some 00:08:11.309 --> 00:08:11.319 align:start position:0% only build program officiation for some 00:08:11.319 --> 00:08:13.550 align:start position:0% only build program officiation for some limited<00:08:11.800> class<00:08:12.000> of<00:08:12.199> functions<00:08:12.879> you<00:08:13.000> know<00:08:13.360> not 00:08:13.550 --> 00:08:13.560 align:start position:0% limited class of functions you know not 00:08:13.560 --> 00:08:15.270 align:start position:0% limited class of functions you know not for<00:08:13.800> General<00:08:14.319> class<00:08:14.520> of<00:08:14.639> functions<00:08:15.000> but<00:08:15.159> like 00:08:15.270 --> 00:08:15.280 align:start position:0% for General class of functions but like 00:08:15.280 --> 00:08:17.149 align:start position:0% for General class of functions but like limited<00:08:15.680> class<00:08:15.879> of 00:08:17.149 --> 00:08:17.159 align:start position:0% limited class of 00:08:17.159 --> 00:08:19.390 align:start position:0% limited class of functions<00:08:18.159> I'll<00:08:18.400> tell<00:08:18.560> you<00:08:18.840> one<00:08:19.080> way<00:08:19.280> of 00:08:19.390 --> 00:08:19.400 align:start position:0% functions I'll tell you one way of 00:08:19.400 --> 00:08:21.029 align:start position:0% functions I'll tell you one way of building<00:08:19.720> the<00:08:19.919> pro<00:08:20.319> um<00:08:20.440> building<00:08:20.720> the<00:08:20.840> god 00:08:21.029 --> 00:08:21.039 align:start position:0% building the pro um building the god 00:08:21.039 --> 00:08:26.029 align:start position:0% building the pro um building the god protocol<00:08:21.400> using<00:08:21.599> program 00:08:26.029 --> 00:08:26.039 align:start position:0% 00:08:26.039 --> 00:08:27.830 align:start position:0% appication<00:08:27.039> step 00:08:27.830 --> 00:08:27.840 align:start position:0% appication step 00:08:27.840 --> 00:08:30.710 align:start position:0% appication step one<00:08:28.840> modify<00:08:29.280> the<00:08:29.560> F<00:08:29.919> scheme<00:08:30.120> that<00:08:30.199> we<00:08:30.360> using 00:08:30.710 --> 00:08:30.720 align:start position:0% one modify the F scheme that we using 00:08:30.720 --> 00:08:33.149 align:start position:0% one modify the F scheme that we using before<00:08:31.280> to<00:08:31.440> become<00:08:31.759> publicly<00:08:32.200> verifiable 00:08:33.149 --> 00:08:33.159 align:start position:0% before to become publicly verifiable 00:08:33.159 --> 00:08:36.110 align:start position:0% before to become publicly verifiable what<00:08:33.279> do<00:08:33.399> I<00:08:33.519> mean<00:08:33.719> by<00:08:33.880> that 00:08:36.110 --> 00:08:36.120 align:start position:0% what do I mean by that 00:08:36.120 --> 00:08:39.029 align:start position:0% what do I mean by that well<00:08:37.120> a<00:08:37.320> publicly<00:08:37.760> verifiable<00:08:38.279> F<00:08:38.599> schemes 00:08:39.029 --> 00:08:39.039 align:start position:0% well a publicly verifiable F schemes 00:08:39.039 --> 00:08:41.670 align:start position:0% well a publicly verifiable F schemes does<00:08:39.279> those<00:08:39.599> things<00:08:40.279> it<00:08:40.599> evaluates<00:08:41.159> the<00:08:41.279> F 00:08:41.670 --> 00:08:41.680 align:start position:0% does those things it evaluates the F 00:08:41.680 --> 00:08:43.509 align:start position:0% does those things it evaluates the F function<00:08:42.240> which<00:08:42.560> you<00:08:42.680> know<00:08:42.800> a<00:08:42.919> normal<00:08:43.200> F 00:08:43.509 --> 00:08:43.519 align:start position:0% function which you know a normal F 00:08:43.519 --> 00:08:45.470 align:start position:0% function which you know a normal F scheme<00:08:43.800> does<00:08:44.320> in<00:08:44.480> addition<00:08:44.760> to<00:08:44.959> evaluating 00:08:45.470 --> 00:08:45.480 align:start position:0% scheme does in addition to evaluating 00:08:45.480 --> 00:08:48.750 align:start position:0% scheme does in addition to evaluating the<00:08:45.880> function<00:08:46.640> it<00:08:46.880> also<00:08:47.240> produces<00:08:47.640> a<00:08:47.920> proof<00:08:48.519> of 00:08:48.750 --> 00:08:48.760 align:start position:0% the function it also produces a proof of 00:08:48.760 --> 00:08:51.350 align:start position:0% the function it also produces a proof of correct<00:08:49.480> evaluation<00:08:50.480> so<00:08:50.680> that<00:08:50.839> anyone<00:08:51.200> can 00:08:51.350 --> 00:08:51.360 align:start position:0% correct evaluation so that anyone can 00:08:51.360 --> 00:08:53.190 align:start position:0% correct evaluation so that anyone can verify<00:08:51.760> this<00:08:51.959> proof<00:08:52.200> with<00:08:52.320> the<00:08:52.399> output<00:08:52.720> CeX 00:08:53.190 --> 00:08:53.200 align:start position:0% verify this proof with the output CeX 00:08:53.200 --> 00:08:56.269 align:start position:0% verify this proof with the output CeX and<00:08:53.320> be<00:08:53.600> assured<00:08:54.600> that<00:08:55.040> the<00:08:55.200> server<00:08:55.959> that<00:08:56.080> sort 00:08:56.269 --> 00:08:56.279 align:start position:0% and be assured that the server that sort 00:08:56.279 --> 00:08:59.470 align:start position:0% and be assured that the server that sort of<00:08:56.600> executed<00:08:57.120> this<00:08:57.320> F<00:08:57.800> function<00:08:58.600> EXA<00:08:59.000> executed 00:08:59.470 --> 00:08:59.480 align:start position:0% of executed this F function EXA executed 00:08:59.480 --> 00:09:01.470 align:start position:0% of executed this F function EXA executed did<00:08:59.600> it 00:09:01.470 --> 00:09:01.480 align:start position:0% did it 00:09:01.480 --> 00:09:03.470 align:start position:0% did it correctly<00:09:02.480> and<00:09:02.640> which<00:09:02.760> I<00:09:02.920> usually<00:09:03.200> referred 00:09:03.470 --> 00:09:03.480 align:start position:0% correctly and which I usually referred 00:09:03.480 --> 00:09:07.110 align:start position:0% correctly and which I usually referred to<00:09:03.680> as<00:09:03.880> proof<00:09:04.240> Pi<00:09:04.440> of<00:09:04.600> correct 00:09:07.110 --> 00:09:07.120 align:start position:0% 00:09:07.120 --> 00:09:09.829 align:start position:0% evaluation<00:09:08.120> step<00:09:08.399> two<00:09:09.200> replace<00:09:09.640> the 00:09:09.829 --> 00:09:09.839 align:start position:0% evaluation step two replace the 00:09:09.839 --> 00:09:11.550 align:start position:0% evaluation step two replace the collective<00:09:10.279> key<00:09:10.480> generation<00:09:11.040> operation<00:09:11.440> that 00:09:11.550 --> 00:09:11.560 align:start position:0% collective key generation operation that 00:09:11.560 --> 00:09:14.990 align:start position:0% collective key generation operation that we<00:09:11.720> did<00:09:12.040> in<00:09:12.240> the<00:09:12.920> multiparty<00:09:13.760> F<00:09:14.760> with<00:09:14.880> a 00:09:14.990 --> 00:09:15.000 align:start position:0% we did in the multiparty F with a 00:09:15.000 --> 00:09:17.630 align:start position:0% we did in the multiparty F with a trusted<00:09:15.480> setup<00:09:16.480> in<00:09:16.600> The<00:09:16.720> Trusted<00:09:17.160> setup<00:09:17.519> you 00:09:17.630 --> 00:09:17.640 align:start position:0% trusted setup in The Trusted setup you 00:09:17.640 --> 00:09:19.630 align:start position:0% trusted setup in The Trusted setup you have<00:09:17.800> arbitary<00:09:18.279> number<00:09:18.480> of<00:09:18.600> people<00:09:18.920> here<00:09:19.480> they 00:09:19.630 --> 00:09:19.640 align:start position:0% have arbitary number of people here they 00:09:19.640 --> 00:09:22.190 align:start position:0% have arbitary number of people here they perform<00:09:20.000> some<00:09:20.200> MPC<00:09:20.640> protocol<00:09:21.040> to<00:09:21.200> produce<00:09:21.560> FH 00:09:22.190 --> 00:09:22.200 align:start position:0% perform some MPC protocol to produce FH 00:09:22.200 --> 00:09:24.750 align:start position:0% perform some MPC protocol to produce FH Keys<00:09:23.200> the<00:09:23.399> two<00:09:23.600> types<00:09:23.800> of<00:09:23.920> FG<00:09:24.279> Keys<00:09:24.480> which<00:09:24.600> are 00:09:24.750 --> 00:09:24.760 align:start position:0% Keys the two types of FG Keys which are 00:09:24.760 --> 00:09:26.310 align:start position:0% Keys the two types of FG Keys which are very<00:09:24.959> important<00:09:25.720> public<00:09:26.000> key<00:09:26.160> and<00:09:26.240> the 00:09:26.310 --> 00:09:26.320 align:start position:0% very important public key and the 00:09:26.320 --> 00:09:28.069 align:start position:0% very important public key and the bootstrapping<00:09:26.839> key<00:09:27.120> bootstrapping<00:09:27.680> key<00:09:27.880> is 00:09:28.069 --> 00:09:28.079 align:start position:0% bootstrapping key bootstrapping key is 00:09:28.079 --> 00:09:29.829 align:start position:0% bootstrapping key bootstrapping key is usually<00:09:28.399> used<00:09:28.640> for<00:09:28.800> some<00:09:28.959> sort<00:09:29.120> of<00:09:29.240> like<00:09:29.480> F 00:09:29.829 --> 00:09:29.839 align:start position:0% usually used for some sort of like F 00:09:29.839 --> 00:09:31.990 align:start position:0% usually used for some sort of like F operations<00:09:30.240> that<00:09:30.360> you<00:09:30.440> can<00:09:30.600> completely 00:09:31.990 --> 00:09:32.000 align:start position:0% operations that you can completely 00:09:32.000 --> 00:09:34.110 align:start position:0% operations that you can completely blackbox<00:09:33.000> the<00:09:33.160> key<00:09:33.360> thing<00:09:33.560> here<00:09:33.720> is<00:09:33.880> that<00:09:34.040> no 00:09:34.110 --> 00:09:34.120 align:start position:0% blackbox the key thing here is that no 00:09:34.120 --> 00:09:35.750 align:start position:0% blackbox the key thing here is that no one<00:09:34.279> knows<00:09:34.519> the<00:09:34.640> ideal<00:09:34.959> secret<00:09:35.279> key<00:09:35.560> because 00:09:35.750 --> 00:09:35.760 align:start position:0% one knows the ideal secret key because 00:09:35.760 --> 00:09:37.350 align:start position:0% one knows the ideal secret key because we're<00:09:35.959> generating<00:09:36.399> a<00:09:36.640> we're<00:09:36.760> doing<00:09:36.920> a<00:09:37.040> trusted 00:09:37.350 --> 00:09:37.360 align:start position:0% we're generating a we're doing a trusted 00:09:37.360 --> 00:09:40.829 align:start position:0% we're generating a we're doing a trusted setup<00:09:37.600> in<00:09:37.720> NPC<00:09:38.079> to<00:09:38.160> generate<00:09:38.519> these<00:09:38.640> two 00:09:40.829 --> 00:09:40.839 align:start position:0% setup in NPC to generate these two 00:09:40.839 --> 00:09:43.750 align:start position:0% setup in NPC to generate these two keys<00:09:41.839> the<00:09:42.000> third<00:09:42.360> step<00:09:42.920> is<00:09:43.200> modify<00:09:43.640> the 00:09:43.750 --> 00:09:43.760 align:start position:0% keys the third step is modify the 00:09:43.760 --> 00:09:46.670 align:start position:0% keys the third step is modify the trusted<00:09:44.160> setup<00:09:44.760> to<00:09:45.000> also<00:09:45.399> output<00:09:46.160> an 00:09:46.670 --> 00:09:46.680 align:start position:0% trusted setup to also output an 00:09:46.680 --> 00:09:49.230 align:start position:0% trusted setup to also output an officiated<00:09:47.680> conditional<00:09:48.079> decryption<00:09:48.560> Oracle 00:09:49.230 --> 00:09:49.240 align:start position:0% officiated conditional decryption Oracle 00:09:49.240 --> 00:09:51.470 align:start position:0% officiated conditional decryption Oracle okay<00:09:49.399> that's<00:09:49.519> a<00:09:49.640> mouthful<00:09:50.399> I<00:09:50.560> sort<00:09:50.680> of<00:09:50.880> like<00:09:51.240> go 00:09:51.470 --> 00:09:51.480 align:start position:0% okay that's a mouthful I sort of like go 00:09:51.480 --> 00:09:53.870 align:start position:0% okay that's a mouthful I sort of like go into<00:09:51.720> it<00:09:51.880> one<00:09:52.079> deep<00:09:52.600> one<00:09:52.760> level<00:09:53.000> deeper<00:09:53.760> what 00:09:53.870 --> 00:09:53.880 align:start position:0% into it one deep one level deeper what 00:09:53.880 --> 00:09:56.630 align:start position:0% into it one deep one level deeper what is<00:09:54.079> an<00:09:54.320> obsc<00:09:55.079> conditional<00:09:55.440> decryptor<00:09:56.440> this 00:09:56.630 --> 00:09:56.640 align:start position:0% is an obsc conditional decryptor this 00:09:56.640 --> 00:09:58.430 align:start position:0% is an obsc conditional decryptor this particular<00:09:57.160> conditional<00:09:57.399> decryptor<00:09:58.160> is<00:09:58.279> an 00:09:58.430 --> 00:09:58.440 align:start position:0% particular conditional decryptor is an 00:09:58.440 --> 00:10:00.150 align:start position:0% particular conditional decryptor is an obsc<00:09:59.000> program<00:09:59.480> of<00:09:59.600> the<00:09:59.720> following 00:10:00.150 --> 00:10:00.160 align:start position:0% obsc program of the following 00:10:00.160 --> 00:10:02.310 align:start position:0% obsc program of the following functionality<00:10:01.160> what<00:10:01.279> it<00:10:01.440> does<00:10:01.760> is<00:10:01.920> that<00:10:02.120> takes 00:10:02.310 --> 00:10:02.320 align:start position:0% functionality what it does is that takes 00:10:02.320 --> 00:10:04.230 align:start position:0% functionality what it does is that takes an<00:10:02.480> output<00:10:02.760> Cipher<00:10:03.120> text<00:10:03.519> and<00:10:03.640> a<00:10:03.839> proof<00:10:04.079> of 00:10:04.230 --> 00:10:04.240 align:start position:0% an output Cipher text and a proof of 00:10:04.240 --> 00:10:06.190 align:start position:0% an output Cipher text and a proof of correct<00:10:04.560> evaluation<00:10:05.000> of<00:10:05.160> FG 00:10:06.190 --> 00:10:06.200 align:start position:0% correct evaluation of FG 00:10:06.200 --> 00:10:08.750 align:start position:0% correct evaluation of FG circuit<00:10:07.200> it<00:10:07.440> verifies<00:10:07.959> whether<00:10:08.160> the<00:10:08.279> proof<00:10:08.519> is 00:10:08.750 --> 00:10:08.760 align:start position:0% circuit it verifies whether the proof is 00:10:08.760 --> 00:10:11.750 align:start position:0% circuit it verifies whether the proof is valid<00:10:09.680> and<00:10:09.880> decrypts<00:10:10.440> the<00:10:10.560> output<00:10:10.920> cyhex<00:10:11.560> if 00:10:11.750 --> 00:10:11.760 align:start position:0% valid and decrypts the output cyhex if 00:10:11.760 --> 00:10:14.110 align:start position:0% valid and decrypts the output cyhex if and<00:10:11.920> only<00:10:12.320> if<00:10:12.720> the<00:10:12.839> proof<00:10:13.120> is 00:10:14.110 --> 00:10:14.120 align:start position:0% and only if the proof is 00:10:14.120 --> 00:10:16.949 align:start position:0% and only if the proof is valid<00:10:15.120> and<00:10:15.360> this<00:10:15.519> sort<00:10:15.680> of<00:10:15.920> like<00:10:16.320> tells<00:10:16.640> you 00:10:16.949 --> 00:10:16.959 align:start position:0% valid and this sort of like tells you 00:10:16.959 --> 00:10:18.829 align:start position:0% valid and this sort of like tells you why<00:10:17.279> did<00:10:17.480> we<00:10:17.640> assume<00:10:17.920> in<00:10:18.040> the<00:10:18.200> first<00:10:18.480> place 00:10:18.829 --> 00:10:18.839 align:start position:0% why did we assume in the first place 00:10:18.839 --> 00:10:21.190 align:start position:0% why did we assume in the first place that<00:10:19.240> program<00:10:19.640> autic<00:10:20.160> may<00:10:20.279> be<00:10:20.399> feasible<00:10:20.920> only 00:10:21.190 --> 00:10:21.200 align:start position:0% that program autic may be feasible only 00:10:21.200 --> 00:10:23.110 align:start position:0% that program autic may be feasible only for<00:10:21.440> like<00:10:21.600> limited<00:10:21.959> class<00:10:22.200> of<00:10:22.320> functions 00:10:23.110 --> 00:10:23.120 align:start position:0% for like limited class of functions 00:10:23.120 --> 00:10:25.990 align:start position:0% for like limited class of functions because<00:10:23.600> to<00:10:23.760> build<00:10:23.920> the<00:10:24.079> god<00:10:24.480> protocol<00:10:25.480> like 00:10:25.990 --> 00:10:26.000 align:start position:0% because to build the god protocol like 00:10:26.000 --> 00:10:28.310 align:start position:0% because to build the god protocol like to<00:10:26.360> to<00:10:26.480> build<00:10:26.640> the<00:10:26.800> got<00:10:27.040> protocol<00:10:27.440> using<00:10:27.760> the<00:10:27.880> F 00:10:28.310 --> 00:10:28.320 align:start position:0% to to build the got protocol using the F 00:10:28.320 --> 00:10:31.509 align:start position:0% to to build the got protocol using the F route<00:10:28.959> we<00:10:29.360> only<00:10:29.600> need<00:10:30.200> program<00:10:30.600> ofation<00:10:31.200> to<00:10:31.320> be 00:10:31.509 --> 00:10:31.519 align:start position:0% route we only need program ofation to be 00:10:31.519 --> 00:10:33.150 align:start position:0% route we only need program ofation to be practical<00:10:31.959> for<00:10:32.279> this<00:10:32.480> officiated 00:10:33.150 --> 00:10:33.160 align:start position:0% practical for this officiated 00:10:33.160 --> 00:10:34.629 align:start position:0% practical for this officiated conditional 00:10:34.629 --> 00:10:34.639 align:start position:0% conditional 00:10:34.639 --> 00:10:38.030 align:start position:0% conditional decryptor<00:10:35.639> so<00:10:36.120> we<00:10:36.240> modify<00:10:36.639> the<00:10:36.720> TR<00:10:37.079> setup<00:10:37.680> to 00:10:38.030 --> 00:10:38.040 align:start position:0% decryptor so we modify the TR setup to 00:10:38.040 --> 00:10:40.509 align:start position:0% decryptor so we modify the TR setup to also<00:10:38.399> output<00:10:39.240> this<00:10:39.519> offc<00:10:40.279> conditional 00:10:40.509 --> 00:10:40.519 align:start position:0% also output this offc conditional 00:10:40.519 --> 00:10:42.670 align:start position:0% also output this offc conditional decryptor<00:10:41.320> and<00:10:41.480> that's<00:10:41.639> it<00:10:42.120> and<00:10:42.440> another 00:10:42.670 --> 00:10:42.680 align:start position:0% decryptor and that's it and another 00:10:42.680 --> 00:10:43.910 align:start position:0% decryptor and that's it and another thing<00:10:42.800> to<00:10:42.920> noce<00:10:43.240> that<00:10:43.360> this<00:10:43.639> conditional 00:10:43.910 --> 00:10:43.920 align:start position:0% thing to noce that this conditional 00:10:43.920 --> 00:10:45.910 align:start position:0% thing to noce that this conditional decryptor<00:10:44.399> also<00:10:44.680> has<00:10:44.839> the<00:10:45.079> secret<00:10:45.600> key<00:10:45.839> the 00:10:45.910 --> 00:10:45.920 align:start position:0% decryptor also has the secret key the 00:10:45.920 --> 00:10:47.990 align:start position:0% decryptor also has the secret key the ideal<00:10:46.279> secret<00:10:46.639> key<00:10:46.839> that<00:10:46.920> no<00:10:47.040> one<00:10:47.240> knows 00:10:47.990 --> 00:10:48.000 align:start position:0% ideal secret key that no one knows 00:10:48.000 --> 00:10:50.590 align:start position:0% ideal secret key that no one knows embedded<00:10:48.440> inside 00:10:50.590 --> 00:10:50.600 align:start position:0% embedded inside 00:10:50.600 --> 00:10:53.910 align:start position:0% embedded inside it<00:10:51.600> okay<00:10:51.880> so<00:10:52.040> the<00:10:52.120> end<00:10:52.320> to<00:10:52.399> end<00:10:52.600> flow<00:10:52.920> is<00:10:53.560> you<00:10:53.720> do 00:10:53.910 --> 00:10:53.920 align:start position:0% it okay so the end to end flow is you do 00:10:53.920 --> 00:10:56.710 align:start position:0% it okay so the end to end flow is you do MPC<00:10:54.320> to<00:10:54.480> generate<00:10:55.160> three<00:10:55.440> things<00:10:56.120> public<00:10:56.440> key 00:10:56.710 --> 00:10:56.720 align:start position:0% MPC to generate three things public key 00:10:56.720 --> 00:10:59.509 align:start position:0% MPC to generate three things public key bootstrapping<00:10:57.360> key<00:10:57.839> and<00:10:58.040> the<00:10:58.760> um<00:10:59.279> and<00:10:59.399> the 00:10:59.509 --> 00:10:59.519 align:start position:0% bootstrapping key and the um and the 00:10:59.519 --> 00:11:01.870 align:start position:0% bootstrapping key and the um and the offc<00:11:00.160> conditional<00:11:00.399> decryptor<00:11:01.360> which<00:11:01.560> I<00:11:01.720> now 00:11:01.870 --> 00:11:01.880 align:start position:0% offc conditional decryptor which I now 00:11:01.880 --> 00:11:04.430 align:start position:0% offc conditional decryptor which I now realize<00:11:02.200> is<00:11:02.360> somewhat<00:11:02.639> of<00:11:03.279> mouthful<00:11:04.279> uh<00:11:04.360> I 00:11:04.430 --> 00:11:04.440 align:start position:0% realize is somewhat of mouthful uh I 00:11:04.440 --> 00:11:06.550 align:start position:0% realize is somewhat of mouthful uh I should<00:11:04.600> have<00:11:04.760> chosen<00:11:05.040> some<00:11:05.200> other<00:11:05.399> term 00:11:06.550 --> 00:11:06.560 align:start position:0% should have chosen some other term 00:11:06.560 --> 00:11:10.110 align:start position:0% should have chosen some other term anyways<00:11:07.560> the<00:11:07.680> second<00:11:07.959> flow<00:11:08.320> is<00:11:08.639> now<00:11:09.200> anyone 00:11:10.110 --> 00:11:10.120 align:start position:0% anyways the second flow is now anyone 00:11:10.120 --> 00:11:12.550 align:start position:0% anyways the second flow is now anyone can<00:11:10.360> encrypt<00:11:10.839> their<00:11:11.120> private<00:11:11.480> inputs<00:11:12.240> using 00:11:12.550 --> 00:11:12.560 align:start position:0% can encrypt their private inputs using 00:11:12.560 --> 00:11:14.150 align:start position:0% can encrypt their private inputs using the<00:11:12.760> public<00:11:13.079> key<00:11:13.360> that<00:11:13.480> is<00:11:13.600> the<00:11:13.680> output<00:11:13.959> of<00:11:14.079> the 00:11:14.150 --> 00:11:14.160 align:start position:0% the public key that is the output of the 00:11:14.160 --> 00:11:16.310 align:start position:0% the public key that is the output of the MPC<00:11:14.560> protocol<00:11:15.000> so<00:11:15.160> you<00:11:15.360> multiple<00:11:15.720> Cipher<00:11:16.040> Texs 00:11:16.310 --> 00:11:16.320 align:start position:0% MPC protocol so you multiple Cipher Texs 00:11:16.320 --> 00:11:18.949 align:start position:0% MPC protocol so you multiple Cipher Texs here<00:11:17.320> and<00:11:17.480> then<00:11:17.760> they<00:11:17.880> can<00:11:18.000> send<00:11:18.200> it<00:11:18.320> to<00:11:18.440> the<00:11:18.560> F 00:11:18.949 --> 00:11:18.959 align:start position:0% here and then they can send it to the F 00:11:18.959 --> 00:11:21.949 align:start position:0% here and then they can send it to the F server<00:11:19.639> F<00:11:20.000> server<00:11:20.279> evaluates<00:11:20.720> the<00:11:20.800> F<00:11:21.160> function 00:11:21.949 --> 00:11:21.959 align:start position:0% server F server evaluates the F function 00:11:21.959 --> 00:11:23.910 align:start position:0% server F server evaluates the F function outputs<00:11:22.399> the<00:11:22.519> encrypted<00:11:22.920> output<00:11:23.480> in<00:11:23.639> addition 00:11:23.910 --> 00:11:23.920 align:start position:0% outputs the encrypted output in addition 00:11:23.920 --> 00:11:26.509 align:start position:0% outputs the encrypted output in addition it<00:11:24.079> produces<00:11:24.440> a<00:11:24.680> proof<00:11:25.160> because<00:11:25.720> the<00:11:25.880> F<00:11:26.240> server 00:11:26.509 --> 00:11:26.519 align:start position:0% it produces a proof because the F server 00:11:26.519 --> 00:11:28.670 align:start position:0% it produces a proof because the F server is<00:11:26.680> evaluating<00:11:27.160> a<00:11:27.399> publicly<00:11:27.800> verifiable<00:11:28.320> F 00:11:28.670 --> 00:11:28.680 align:start position:0% is evaluating a publicly verifiable F 00:11:28.680 --> 00:11:30.550 align:start position:0% is evaluating a publicly verifiable F scheme 00:11:30.550 --> 00:11:30.560 align:start position:0% scheme 00:11:30.560 --> 00:11:34.230 align:start position:0% scheme um<00:11:30.880> and<00:11:31.040> then<00:11:31.240> we<00:11:31.480> Pro<00:11:31.920> we<00:11:32.120> we<00:11:33.040> plugged<00:11:33.440> in<00:11:34.000> the 00:11:34.230 --> 00:11:34.240 align:start position:0% um and then we Pro we we plugged in the 00:11:34.240 --> 00:11:36.310 align:start position:0% um and then we Pro we we plugged in the proof<00:11:34.720> as<00:11:34.880> well<00:11:35.000> as<00:11:35.160> the<00:11:35.279> output<00:11:35.920> to<00:11:36.079> the<00:11:36.240> to 00:11:36.310 --> 00:11:36.320 align:start position:0% proof as well as the output to the to 00:11:36.320 --> 00:11:38.629 align:start position:0% proof as well as the output to the to the<00:11:36.440> offc<00:11:37.040> conditional<00:11:37.320> decryptor<00:11:38.200> and<00:11:38.360> the 00:11:38.629 --> 00:11:38.639 align:start position:0% the offc conditional decryptor and the 00:11:38.639 --> 00:11:40.310 align:start position:0% the offc conditional decryptor and the conditional<00:11:38.880> decryptor<00:11:39.360> would<00:11:39.519> only<00:11:39.839> output 00:11:40.310 --> 00:11:40.320 align:start position:0% conditional decryptor would only output 00:11:40.320 --> 00:11:42.550 align:start position:0% conditional decryptor would only output the<00:11:40.920> uh<00:11:41.040> would<00:11:41.200> only<00:11:41.399> decrypt<00:11:41.839> the<00:11:42.120> encrypted 00:11:42.550 --> 00:11:42.560 align:start position:0% the uh would only decrypt the encrypted 00:11:42.560 --> 00:11:44.629 align:start position:0% the uh would only decrypt the encrypted output<00:11:43.360> if<00:11:43.480> and<00:11:43.600> only<00:11:43.839> if<00:11:43.920> the<00:11:44.040> proof<00:11:44.240> is 00:11:44.629 --> 00:11:44.639 align:start position:0% output if and only if the proof is 00:11:44.639 --> 00:11:46.949 align:start position:0% output if and only if the proof is wallid<00:11:45.639> so<00:11:45.839> this<00:11:45.920> is<00:11:46.120> one<00:11:46.360> way<00:11:46.480> of<00:11:46.639> building 00:11:46.949 --> 00:11:46.959 align:start position:0% wallid so this is one way of building 00:11:46.959 --> 00:11:49.430 align:start position:0% wallid so this is one way of building the<00:11:47.120> god<00:11:47.399> protocol<00:11:48.160> using<00:11:48.959> publicly 00:11:49.430 --> 00:11:49.440 align:start position:0% the god protocol using publicly 00:11:49.440 --> 00:11:52.910 align:start position:0% the god protocol using publicly verifiable<00:11:50.320> F<00:11:51.320> and<00:11:51.880> program<00:11:52.240> ofation<00:11:52.760> for 00:11:52.910 --> 00:11:52.920 align:start position:0% verifiable F and program ofation for 00:11:52.920 --> 00:11:55.389 align:start position:0% verifiable F and program ofation for officed<00:11:53.560> conditional 00:11:55.389 --> 00:11:55.399 align:start position:0% officed conditional 00:11:55.399 --> 00:11:58.949 align:start position:0% officed conditional decryptor<00:11:56.800> so<00:11:57.800> there's<00:11:58.079> one<00:11:58.320> way<00:11:58.680> which<00:11:58.800> I've 00:11:58.949 --> 00:11:58.959 align:start position:0% decryptor so there's one way which I've 00:11:58.959 --> 00:12:01.430 align:start position:0% decryptor so there's one way which I've just<00:11:59.240> shown<00:11:59.480> you<00:11:59.800> but<00:11:59.959> we<00:12:00.079> need<00:12:00.320> new<00:12:00.600> ideas<00:12:01.200> to 00:12:01.430 --> 00:12:01.440 align:start position:0% just shown you but we need new ideas to 00:12:01.440 --> 00:12:03.629 align:start position:0% just shown you but we need new ideas to push<00:12:01.680> the<00:12:01.800> Frontiers<00:12:02.320> and<00:12:02.440> to<00:12:02.560> finally<00:12:02.959> build 00:12:03.629 --> 00:12:03.639 align:start position:0% push the Frontiers and to finally build 00:12:03.639 --> 00:12:05.990 align:start position:0% push the Frontiers and to finally build the<00:12:04.639> uh<00:12:04.880> to<00:12:05.120> to<00:12:05.240> finally<00:12:05.519> build<00:12:05.720> program 00:12:05.990 --> 00:12:06.000 align:start position:0% the uh to to finally build program 00:12:06.000 --> 00:12:07.550 align:start position:0% the uh to to finally build program officiation<00:12:06.639> or<00:12:06.839> indistinguishability 00:12:07.550 --> 00:12:07.560 align:start position:0% officiation or indistinguishability 00:12:07.560 --> 00:12:10.190 align:start position:0% officiation or indistinguishability officiation<00:12:08.279> if<00:12:08.360> you're<00:12:08.480> familiar<00:12:08.800> with<00:12:09.200> that 00:12:10.190 --> 00:12:10.200 align:start position:0% officiation if you're familiar with that 00:12:10.200 --> 00:12:13.069 align:start position:0% officiation if you're familiar with that here<00:12:10.560> I've<00:12:10.680> showed<00:12:10.959> you<00:12:11.160> just<00:12:11.399> one<00:12:11.760> way<00:12:12.760> but<00:12:12.959> if 00:12:13.069 --> 00:12:13.079 align:start position:0% here I've showed you just one way but if 00:12:13.079 --> 00:12:14.990 align:start position:0% here I've showed you just one way but if you're<00:12:13.320> able<00:12:13.480> to<00:12:13.600> come<00:12:13.720> up<00:12:13.839> with<00:12:14.040> new<00:12:14.279> ideas 00:12:14.990 --> 00:12:15.000 align:start position:0% you're able to come up with new ideas 00:12:15.000 --> 00:12:16.550 align:start position:0% you're able to come up with new ideas then<00:12:15.279> probably<00:12:15.639> we<00:12:15.760> can<00:12:15.959> make<00:12:16.240> program 00:12:16.550 --> 00:12:16.560 align:start position:0% then probably we can make program 00:12:16.560 --> 00:12:20.150 align:start position:0% then probably we can make program officiation<00:12:17.120> more<00:12:17.440> practical<00:12:18.440> for<00:12:19.399> General 00:12:20.150 --> 00:12:20.160 align:start position:0% officiation more practical for General 00:12:20.160 --> 00:12:22.310 align:start position:0% officiation more practical for General circuits<00:12:20.680> not<00:12:20.880> just<00:12:21.000> for<00:12:21.240> like<00:12:21.720> limited<00:12:22.120> class 00:12:22.310 --> 00:12:22.320 align:start position:0% circuits not just for like limited class 00:12:22.320 --> 00:12:24.870 align:start position:0% circuits not just for like limited class of<00:12:22.440> functions<00:12:22.760> that<00:12:22.880> we<00:12:23.000> use<00:12:23.720> before<00:12:24.720> and 00:12:24.870 --> 00:12:24.880 align:start position:0% of functions that we use before and 00:12:24.880 --> 00:12:26.949 align:start position:0% of functions that we use before and probably<00:12:25.680> we<00:12:25.800> can<00:12:26.000> directly<00:12:26.320> build<00:12:26.560> the<00:12:26.680> Cod 00:12:26.949 --> 00:12:26.959 align:start position:0% probably we can directly build the Cod 00:12:26.959 --> 00:12:32.030 align:start position:0% probably we can directly build the Cod protocols<00:12:27.680> from<00:12:28.000> program<00:12:28.320> officiation 00:12:32.030 --> 00:12:32.040 align:start position:0% 00:12:32.040 --> 00:12:35.430 align:start position:0% okay<00:12:33.120> so<00:12:34.120> while<00:12:34.320> I<00:12:34.480> was<00:12:34.639> exploring<00:12:35.040> this<00:12:35.160> field 00:12:35.430 --> 00:12:35.440 align:start position:0% okay so while I was exploring this field 00:12:35.440 --> 00:12:38.310 align:start position:0% okay so while I was exploring this field of<00:12:35.600> program<00:12:35.920> officiation<00:12:36.760> and 00:12:38.310 --> 00:12:38.320 align:start position:0% of program officiation and 00:12:38.320 --> 00:12:42.150 align:start position:0% of program officiation and iio<00:12:39.320> one<00:12:39.560> key<00:12:39.760> observation<00:12:40.199> that<00:12:40.320> I<00:12:40.480> made<00:12:41.480> um 00:12:42.150 --> 00:12:42.160 align:start position:0% iio one key observation that I made um 00:12:42.160 --> 00:12:44.829 align:start position:0% iio one key observation that I made um this<00:12:43.160> uh<00:12:43.320> one<00:12:43.480> key<00:12:43.639> observation<00:12:44.240> that<00:12:44.360> I<00:12:44.480> made 00:12:44.829 --> 00:12:44.839 align:start position:0% this uh one key observation that I made 00:12:44.839 --> 00:12:46.870 align:start position:0% this uh one key observation that I made was<00:12:45.040> that<00:12:45.639> it's<00:12:45.839> really<00:12:46.079> hard<00:12:46.279> to<00:12:46.440> get 00:12:46.870 --> 00:12:46.880 align:start position:0% was that it's really hard to get 00:12:46.880 --> 00:12:48.990 align:start position:0% was that it's really hard to get efficient<00:12:47.360> program<00:12:47.760> officiation<00:12:48.760> from 00:12:48.990 --> 00:12:49.000 align:start position:0% efficient program officiation from 00:12:49.000 --> 00:12:50.509 align:start position:0% efficient program officiation from standard 00:12:50.509 --> 00:12:50.519 align:start position:0% standard 00:12:50.519 --> 00:12:52.710 align:start position:0% standard assumptions<00:12:51.519> and<00:12:51.720> we<00:12:51.839> would<00:12:52.079> inevitably 00:12:52.710 --> 00:12:52.720 align:start position:0% assumptions and we would inevitably 00:12:52.720 --> 00:12:55.150 align:start position:0% assumptions and we would inevitably require<00:12:53.480> exotic<00:12:53.920> assumptions<00:12:54.800> and<00:12:54.920> I'll<00:12:55.040> tell 00:12:55.150 --> 00:12:55.160 align:start position:0% require exotic assumptions and I'll tell 00:12:55.160 --> 00:12:56.189 align:start position:0% require exotic assumptions and I'll tell you<00:12:55.279> what<00:12:55.399> are<00:12:55.519> standard<00:12:55.800> assumptions<00:12:56.120> what 00:12:56.189 --> 00:12:56.199 align:start position:0% you what are standard assumptions what 00:12:56.199 --> 00:12:57.990 align:start position:0% you what are standard assumptions what are<00:12:56.279> exotic<00:12:56.600> assumptions<00:12:57.440> well<00:12:57.560> a<00:12:57.680> standard 00:12:57.990 --> 00:12:58.000 align:start position:0% are exotic assumptions well a standard 00:12:58.000 --> 00:12:59.750 align:start position:0% are exotic assumptions well a standard assumption<00:12:58.360> is<00:12:58.560> assumption<00:12:59.279> that<00:12:59.440> has<00:12:59.560> been 00:12:59.750 --> 00:12:59.760 align:start position:0% assumption is assumption that has been 00:12:59.760 --> 00:13:01.829 align:start position:0% assumption is assumption that has been there<00:12:59.920> for<00:13:00.079> a<00:13:00.199> while<00:13:00.440> for<00:13:00.600> example<00:13:00.920> dlog<00:13:01.639> the 00:13:01.829 --> 00:13:01.839 align:start position:0% there for a while for example dlog the 00:13:01.839 --> 00:13:03.550 align:start position:0% there for a while for example dlog the street<00:13:02.120> log 00:13:03.550 --> 00:13:03.560 align:start position:0% street log 00:13:03.560 --> 00:13:06.430 align:start position:0% street log problem<00:13:04.560> there's<00:13:04.839> also<00:13:05.279> there<00:13:05.440> also<00:13:05.760> exists 00:13:06.430 --> 00:13:06.440 align:start position:0% problem there's also there also exists 00:13:06.440 --> 00:13:08.590 align:start position:0% problem there's also there also exists additional<00:13:06.920> incentive<00:13:07.560> for<00:13:07.800> people<00:13:08.040> to<00:13:08.279> break 00:13:08.590 --> 00:13:08.600 align:start position:0% additional incentive for people to break 00:13:08.600 --> 00:13:10.750 align:start position:0% additional incentive for people to break these<00:13:08.839> stand<00:13:09.399> uh<00:13:09.480> standard 00:13:10.750 --> 00:13:10.760 align:start position:0% these stand uh standard 00:13:10.760 --> 00:13:12.870 align:start position:0% these stand uh standard assumptions<00:13:11.760> and<00:13:11.959> exotic<00:13:12.360> assumptions<00:13:12.720> are 00:13:12.870 --> 00:13:12.880 align:start position:0% assumptions and exotic assumptions are 00:13:12.880 --> 00:13:14.550 align:start position:0% assumptions and exotic assumptions are somewhat<00:13:13.160> newer<00:13:13.480> assumptions<00:13:14.160> like<00:13:14.440> they 00:13:14.550 --> 00:13:14.560 align:start position:0% somewhat newer assumptions like they 00:13:14.560 --> 00:13:15.990 align:start position:0% somewhat newer assumptions like they have<00:13:14.720> been<00:13:14.839> only<00:13:15.040> there<00:13:15.199> for<00:13:15.360> like<00:13:15.560> five<00:13:15.760> years 00:13:15.990 --> 00:13:16.000 align:start position:0% have been only there for like five years 00:13:16.000 --> 00:13:19.750 align:start position:0% have been only there for like five years or<00:13:16.360> not<00:13:16.519> even<00:13:16.760> five<00:13:16.920> years<00:13:17.120> like<00:13:17.240> two<00:13:17.399> to<00:13:17.560> three 00:13:19.750 --> 00:13:19.760 align:start position:0% or not even five years like two to three 00:13:19.760 --> 00:13:22.269 align:start position:0% or not even five years like two to three years 00:13:22.269 --> 00:13:22.279 align:start position:0% years 00:13:22.279 --> 00:13:25.710 align:start position:0% years uh<00:13:23.279> what<00:13:23.480> we<00:13:23.600> can<00:13:23.839> do<00:13:24.079> as<00:13:24.199> a<00:13:24.360> community<00:13:25.079> to<00:13:25.480> you 00:13:25.710 --> 00:13:25.720 align:start position:0% uh what we can do as a community to you 00:13:25.720 --> 00:13:28.829 align:start position:0% uh what we can do as a community to you know<00:13:26.720> realizing<00:13:27.399> that<00:13:27.680> we<00:13:27.880> might<00:13:28.160> inevitably 00:13:28.829 --> 00:13:28.839 align:start position:0% know realizing that we might inevitably 00:13:28.839 --> 00:13:30.470 align:start position:0% know realizing that we might inevitably need<00:13:29.120> need<00:13:29.279> newer<00:13:29.600> assumptions<00:13:30.079> to<00:13:30.199> build 00:13:30.470 --> 00:13:30.480 align:start position:0% need need newer assumptions to build 00:13:30.480 --> 00:13:32.949 align:start position:0% need need newer assumptions to build practical<00:13:30.839> program<00:13:31.440> modification 00:13:32.949 --> 00:13:32.959 align:start position:0% practical program modification 00:13:32.959 --> 00:13:36.389 align:start position:0% practical program modification is<00:13:33.959> we<00:13:34.079> can<00:13:34.360> start<00:13:35.240> examining<00:13:35.920> these<00:13:36.079> newer 00:13:36.389 --> 00:13:36.399 align:start position:0% is we can start examining these newer 00:13:36.399 --> 00:13:38.430 align:start position:0% is we can start examining these newer assumptions<00:13:36.880> start<00:13:37.199> breaking<00:13:37.600> them<00:13:38.079> start 00:13:38.430 --> 00:13:38.440 align:start position:0% assumptions start breaking them start 00:13:38.440 --> 00:13:40.509 align:start position:0% assumptions start breaking them start testing<00:13:38.880> them<00:13:39.600> or<00:13:39.959> we<00:13:40.079> can<00:13:40.199> build 00:13:40.509 --> 00:13:40.519 align:start position:0% testing them or we can build 00:13:40.519 --> 00:13:41.990 align:start position:0% testing them or we can build applications<00:13:41.000> using<00:13:41.279> this<00:13:41.440> assumption<00:13:41.839> so 00:13:41.990 --> 00:13:42.000 align:start position:0% applications using this assumption so 00:13:42.000 --> 00:13:44.509 align:start position:0% applications using this assumption so that<00:13:42.079> we<00:13:42.199> can<00:13:42.399> incentivize<00:13:43.120> people<00:13:43.959> to<00:13:44.160> break 00:13:44.509 --> 00:13:44.519 align:start position:0% that we can incentivize people to break 00:13:44.519 --> 00:13:46.230 align:start position:0% that we can incentivize people to break them<00:13:45.079> and<00:13:45.199> tell<00:13:45.360> us<00:13:45.519> whether<00:13:45.720> they're<00:13:45.920> broken 00:13:46.230 --> 00:13:46.240 align:start position:0% them and tell us whether they're broken 00:13:46.240 --> 00:13:48.910 align:start position:0% them and tell us whether they're broken or<00:13:46.399> not<00:13:47.199> and<00:13:47.279> then<00:13:47.480> eventually<00:13:48.040> in<00:13:48.240> like<00:13:48.680> few 00:13:48.910 --> 00:13:48.920 align:start position:0% or not and then eventually in like few 00:13:48.920 --> 00:13:50.389 align:start position:0% or not and then eventually in like few years<00:13:49.480> we<00:13:49.600> would<00:13:49.800> have<00:13:49.959> candidate 00:13:50.389 --> 00:13:50.399 align:start position:0% years we would have candidate 00:13:50.399 --> 00:13:52.790 align:start position:0% years we would have candidate assumptions<00:13:51.399> that<00:13:51.560> are<00:13:51.720> newer<00:13:52.079> assumptions 00:13:52.790 --> 00:13:52.800 align:start position:0% assumptions that are newer assumptions 00:13:52.800 --> 00:13:55.790 align:start position:0% assumptions that are newer assumptions but<00:13:53.360> they<00:13:53.560> have<00:13:53.800> become<00:13:54.160> then<00:13:54.519> standard<00:13:55.480> using 00:13:55.790 --> 00:13:55.800 align:start position:0% but they have become then standard using 00:13:55.800 --> 00:13:57.550 align:start position:0% but they have become then standard using which<00:13:55.920> we<00:13:56.040> can<00:13:56.160> build<00:13:56.560> practical<00:13:57.199> program 00:13:57.550 --> 00:13:57.560 align:start position:0% which we can build practical program 00:13:57.560 --> 00:14:01.509 align:start position:0% which we can build practical program vestigation 00:14:01.509 --> 00:14:01.519 align:start position:0% 00:14:01.519 --> 00:14:02.990 align:start position:0% okay 00:14:02.990 --> 00:14:03.000 align:start position:0% okay 00:14:03.000 --> 00:14:05.590 align:start position:0% okay uh<00:14:04.000> and<00:14:04.199> taking<00:14:04.399> a<00:14:04.560> first<00:14:04.759> step<00:14:04.959> towards<00:14:05.320> this 00:14:05.590 --> 00:14:05.600 align:start position:0% uh and taking a first step towards this 00:14:05.600 --> 00:14:07.990 align:start position:0% uh and taking a first step towards this we<00:14:05.839> launching<00:14:06.160> a<00:14:06.279> py<00:14:06.680> program<00:14:07.160> for<00:14:07.360> program<00:14:07.839> to 00:14:07.990 --> 00:14:08.000 align:start position:0% we launching a py program for program to 00:14:08.000 --> 00:14:10.069 align:start position:0% we launching a py program for program to break<00:14:08.399> one<00:14:08.600> of<00:14:08.759> the<00:14:08.880> candidate<00:14:09.279> assumptions 00:14:10.069 --> 00:14:10.079 align:start position:0% break one of the candidate assumptions 00:14:10.079 --> 00:14:11.629 align:start position:0% break one of the candidate assumptions which<00:14:10.199> is<00:14:10.360> called<00:14:10.560> program<00:14:10.920> appication<00:14:11.440> via 00:14:11.629 --> 00:14:11.639 align:start position:0% which is called program appication via 00:14:11.639 --> 00:14:14.430 align:start position:0% which is called program appication via local<00:14:12.320> mixing<00:14:13.320> the<00:14:13.440> way<00:14:13.600> I<00:14:13.759> think<00:14:13.959> about<00:14:14.279> this 00:14:14.430 --> 00:14:14.440 align:start position:0% local mixing the way I think about this 00:14:14.440 --> 00:14:16.629 align:start position:0% local mixing the way I think about this particular<00:14:14.839> assumption<00:14:15.320> is<00:14:15.519> that<00:14:16.199> you 00:14:16.629 --> 00:14:16.639 align:start position:0% particular assumption is that you 00:14:16.639 --> 00:14:19.310 align:start position:0% particular assumption is that you they're<00:14:16.880> taking<00:14:17.320> take<00:14:17.839> they're<00:14:18.040> taking<00:14:18.320> more 00:14:19.310 --> 00:14:19.320 align:start position:0% they're taking take they're taking more 00:14:19.320 --> 00:14:21.509 align:start position:0% they're taking take they're taking more computational<00:14:20.079> complexity<00:14:20.880> approach<00:14:21.240> than 00:14:21.509 --> 00:14:21.519 align:start position:0% computational complexity approach than 00:14:21.519 --> 00:14:23.629 align:start position:0% computational complexity approach than taking<00:14:22.199> like<00:14:22.320> the<00:14:22.440> traditional<00:14:22.839> approach<00:14:23.160> of 00:14:23.629 --> 00:14:23.639 align:start position:0% taking like the traditional approach of 00:14:23.639 --> 00:14:25.829 align:start position:0% taking like the traditional approach of using<00:14:24.320> algebraic<00:14:24.880> structures<00:14:25.360> to<00:14:25.519> build 00:14:25.829 --> 00:14:25.839 align:start position:0% using algebraic structures to build 00:14:25.839 --> 00:14:27.509 align:start position:0% using algebraic structures to build program 00:14:27.509 --> 00:14:27.519 align:start position:0% program 00:14:27.519 --> 00:14:30.310 align:start position:0% program officiation<00:14:28.519> the<00:14:28.639> goal<00:14:28.839> of<00:14:28.920> the<00:14:29.160> Bounty<00:14:29.920> is 00:14:30.310 --> 00:14:30.320 align:start position:0% officiation the goal of the Bounty is 00:14:30.320 --> 00:14:32.470 align:start position:0% officiation the goal of the Bounty is that<00:14:30.519> we've<00:14:30.759> provided<00:14:31.120> you<00:14:31.240> an<00:14:31.399> offc<00:14:32.040> circuit 00:14:32.470 --> 00:14:32.480 align:start position:0% that we've provided you an offc circuit 00:14:32.480 --> 00:14:34.550 align:start position:0% that we've provided you an offc circuit with<00:14:32.639> roughly<00:14:33.000> like<00:14:33.160> 240,000 00:14:34.550 --> 00:14:34.560 align:start position:0% with roughly like 240,000 00:14:34.560 --> 00:14:37.509 align:start position:0% with roughly like 240,000 Gates<00:14:35.560> which<00:14:35.800> was<00:14:36.040> offcut<00:14:36.720> from<00:14:36.880> an<00:14:37.120> original 00:14:37.509 --> 00:14:37.519 align:start position:0% Gates which was offcut from an original 00:14:37.519 --> 00:14:40.550 align:start position:0% Gates which was offcut from an original circuits<00:14:38.000> with<00:14:38.160> roughly<00:14:38.560> thousand<00:14:39.399> Gates<00:14:40.399> and 00:14:40.550 --> 00:14:40.560 align:start position:0% circuits with roughly thousand Gates and 00:14:40.560 --> 00:14:42.389 align:start position:0% circuits with roughly thousand Gates and you<00:14:40.720> have<00:14:40.839> to<00:14:40.959> find<00:14:41.160> the<00:14:41.279> original<00:14:41.680> circuit 00:14:42.389 --> 00:14:42.399 align:start position:0% you have to find the original circuit 00:14:42.399 --> 00:14:44.710 align:start position:0% you have to find the original circuit you<00:14:42.560> can<00:14:42.759> learn<00:14:43.079> more<00:14:43.360> about<00:14:43.639> the<00:14:44.199> Bounty 00:14:44.710 --> 00:14:44.720 align:start position:0% you can learn more about the Bounty 00:14:44.720 --> 00:14:47.509 align:start position:0% you can learn more about the Bounty atopia<00:14:45.639> too<00:14:46.360> if<00:14:46.480> you<00:14:46.560> know<00:14:46.720> what<00:14:46.880> off<00:14:47.079> estopia 00:14:47.509 --> 00:14:47.519 align:start position:0% atopia too if you know what off estopia 00:14:47.519 --> 00:14:49.870 align:start position:0% atopia too if you know what off estopia is<00:14:48.040> off<00:14:48.199> estopia<00:14:48.560> means<00:14:48.759> that<00:14:48.880> we<00:14:49.040> living<00:14:49.320> in<00:14:49.720> a 00:14:49.870 --> 00:14:49.880 align:start position:0% is off estopia means that we living in a 00:14:49.880 --> 00:14:52.629 align:start position:0% is off estopia means that we living in a world<00:14:50.160> where<00:14:50.360> officiation<00:14:51.000> is<00:14:51.519> practical<00:14:52.519> uh 00:14:52.629 --> 00:14:52.639 align:start position:0% world where officiation is practical uh 00:14:52.639 --> 00:14:55.230 align:start position:0% world where officiation is practical uh and<00:14:52.759> the<00:14:52.880> Bounty<00:14:53.440> is<00:14:53.560> 10K<00:14:54.440> and<00:14:54.639> this<00:14:54.800> bounty<00:14:55.160> is 00:14:55.230 --> 00:14:55.240 align:start position:0% and the Bounty is 10K and this bounty is 00:14:55.240 --> 00:14:57.030 align:start position:0% and the Bounty is 10K and this bounty is launched<00:14:55.560> in<00:14:55.680> collaboration<00:14:56.320> with<00:14:56.720> um 00:14:57.030 --> 00:14:57.040 align:start position:0% launched in collaboration with um 00:14:57.040 --> 00:15:00.670 align:start position:0% launched in collaboration with um etherum<00:14:57.399> foundation<00:14:57.720> and<00:14:57.839> ZX<00:14:58.199> Park 00:15:00.670 --> 00:15:00.680 align:start position:0% etherum foundation and ZX Park 00:15:00.680 --> 00:15:04.949 align:start position:0% etherum foundation and ZX Park um<00:15:01.360> okay<00:15:02.360> so<00:15:02.800> before<00:15:03.079> I<00:15:03.279> break<00:15:04.240> um<00:15:04.519> and<00:15:04.680> I<00:15:04.800> think 00:15:04.949 --> 00:15:04.959 align:start position:0% um okay so before I break um and I think 00:15:04.959 --> 00:15:07.310 align:start position:0% um okay so before I break um and I think that<00:15:05.079> I<00:15:05.120> have<00:15:05.240> a<00:15:05.320> bunch<00:15:05.480> of<00:15:05.680> time<00:15:06.639> okay<00:15:07.079> before 00:15:07.310 --> 00:15:07.320 align:start position:0% that I have a bunch of time okay before 00:15:07.320 --> 00:15:10.230 align:start position:0% that I have a bunch of time okay before I<00:15:07.440> break<00:15:07.759> I<00:15:07.839> would<00:15:08.000> want<00:15:08.160> to<00:15:08.399> make<00:15:09.199> one 00:15:10.230 --> 00:15:10.240 align:start position:0% I break I would want to make one 00:15:10.240 --> 00:15:12.350 align:start position:0% I break I would want to make one conjecture<00:15:11.240> and<00:15:11.360> the<00:15:11.519> conjecture<00:15:11.959> goes<00:15:12.199> as 00:15:12.350 --> 00:15:12.360 align:start position:0% conjecture and the conjecture goes as 00:15:12.360 --> 00:15:14.749 align:start position:0% conjecture and the conjecture goes as follows<00:15:13.360> I<00:15:13.480> think<00:15:13.639> the<00:15:13.759> god<00:15:14.079> protocol<00:15:14.519> is<00:15:14.639> the 00:15:14.749 --> 00:15:14.759 align:start position:0% follows I think the god protocol is the 00:15:14.759 --> 00:15:18.269 align:start position:0% follows I think the god protocol is the convergence<00:15:15.199> of 00:15:18.269 --> 00:15:18.279 align:start position:0% 00:15:18.279 --> 00:15:20.269 align:start position:0% cryptography<00:15:19.279> probably<00:15:19.600> building<00:15:19.920> the<00:15:20.040> god 00:15:20.269 --> 00:15:20.279 align:start position:0% cryptography probably building the god 00:15:20.279 --> 00:15:21.990 align:start position:0% cryptography probably building the god protocol<00:15:20.680> would<00:15:20.880> require<00:15:21.320> certain<00:15:21.680> sort<00:15:21.839> of 00:15:21.990 --> 00:15:22.000 align:start position:0% protocol would require certain sort of 00:15:22.000 --> 00:15:24.790 align:start position:0% protocol would require certain sort of like<00:15:22.360> f<00:15:23.360> that<00:15:23.480> is<00:15:23.639> just<00:15:23.800> one<00:15:24.040> route<00:15:24.399> but<00:15:24.600> like 00:15:24.790 --> 00:15:24.800 align:start position:0% like f that is just one route but like 00:15:24.800 --> 00:15:27.829 align:start position:0% like f that is just one route but like publicly<00:15:25.680> F<00:15:26.079> and<00:15:26.199> other<00:15:26.399> things<00:15:26.680> like<00:15:26.800> MPC<00:15:27.160> for 00:15:27.829 --> 00:15:27.839 align:start position:0% publicly F and other things like MPC for 00:15:27.839 --> 00:15:29.790 align:start position:0% publicly F and other things like MPC for it<00:15:28.000> setup<00:15:28.279> and<00:15:28.360> so<00:15:28.480> on<00:15:28.560> and<00:15:28.639> so<00:15:28.759> forth<00:15:29.399> but<00:15:29.600> once 00:15:29.790 --> 00:15:29.800 align:start position:0% it setup and so on and so forth but once 00:15:29.800 --> 00:15:31.430 align:start position:0% it setup and so on and so forth but once we<00:15:29.920> have<00:15:30.040> built<00:15:30.240> the<00:15:30.360> god 00:15:31.430 --> 00:15:31.440 align:start position:0% we have built the god 00:15:31.440 --> 00:15:33.790 align:start position:0% we have built the god protocol<00:15:32.440> I<00:15:32.519> think<00:15:32.680> it<00:15:32.880> compasses<00:15:33.440> everything 00:15:33.790 --> 00:15:33.800 align:start position:0% protocol I think it compasses everything 00:15:33.800 --> 00:15:35.389 align:start position:0% protocol I think it compasses everything it<00:15:33.920> gives<00:15:34.079> us<00:15:34.279> everything<00:15:34.600> that<00:15:34.720> we<00:15:34.839> have<00:15:35.319> we 00:15:35.389 --> 00:15:35.399 align:start position:0% it gives us everything that we have we 00:15:35.399 --> 00:15:37.230 align:start position:0% it gives us everything that we have we have<00:15:35.519> been<00:15:35.720> like<00:15:35.959> wanting<00:15:36.319> for<00:15:36.560> for<00:15:36.720> a<00:15:36.839> while 00:15:37.230 --> 00:15:37.240 align:start position:0% have been like wanting for for a while 00:15:37.240 --> 00:15:38.910 align:start position:0% have been like wanting for for a while it<00:15:37.360> gives<00:15:37.560> us<00:15:37.720> witness<00:15:38.040> encryption<00:15:38.639> it<00:15:38.720> gives 00:15:38.910 --> 00:15:38.920 align:start position:0% it gives us witness encryption it gives 00:15:38.920 --> 00:15:40.870 align:start position:0% it gives us witness encryption it gives us<00:15:39.040> Z<00:15:39.279> knowledge<00:15:39.480> proves<00:15:39.759> bya<00:15:39.959> signatures<00:15:40.759> it 00:15:40.870 --> 00:15:40.880 align:start position:0% us Z knowledge proves bya signatures it 00:15:40.880 --> 00:15:43.189 align:start position:0% us Z knowledge proves bya signatures it gives<00:15:41.079> us<00:15:41.279> MPC<00:15:42.120> multiparty<00:15:42.680> computation<00:15:43.120> it 00:15:43.189 --> 00:15:43.199 align:start position:0% gives us MPC multiparty computation it 00:15:43.199 --> 00:15:45.309 align:start position:0% gives us MPC multiparty computation it gives<00:15:43.399> us<00:15:43.560> Fe<00:15:44.040> fun<00:15:44.440> functional<00:15:44.759> encryption 00:15:45.309 --> 00:15:45.319 align:start position:0% gives us Fe fun functional encryption 00:15:45.319 --> 00:15:46.910 align:start position:0% gives us Fe fun functional encryption all<00:15:45.600> all<00:15:45.720> of<00:15:45.920> these<00:15:46.319> things<00:15:46.519> that<00:15:46.639> we've<00:15:46.800> been 00:15:46.910 --> 00:15:46.920 align:start position:0% all all of these things that we've been 00:15:46.920 --> 00:15:48.790 align:start position:0% all all of these things that we've been demanding<00:15:47.240> for<00:15:47.399> a 00:15:48.790 --> 00:15:48.800 align:start position:0% demanding for a 00:15:48.800 --> 00:15:51.189 align:start position:0% demanding for a while<00:15:49.800> and<00:15:50.120> this<00:15:50.240> is<00:15:50.440> also<00:15:50.639> one<00:15:50.759> of<00:15:50.839> the<00:15:50.959> major 00:15:51.189 --> 00:15:51.199 align:start position:0% while and this is also one of the major 00:15:51.199 --> 00:15:52.629 align:start position:0% while and this is also one of the major reasons<00:15:51.519> that<00:15:51.680> we<00:15:51.759> should<00:15:51.959> start 00:15:52.629 --> 00:15:52.639 align:start position:0% reasons that we should start 00:15:52.639 --> 00:15:55.110 align:start position:0% reasons that we should start investigating<00:15:53.639> much<00:15:53.839> more<00:15:54.079> seriously<00:15:54.839> how<00:15:54.959> to 00:15:55.110 --> 00:15:55.120 align:start position:0% investigating much more seriously how to 00:15:55.120 --> 00:15:56.990 align:start position:0% investigating much more seriously how to get<00:15:55.319> practical<00:15:55.680> program<00:15:56.000> officiation<00:15:56.839> and 00:15:56.990 --> 00:15:57.000 align:start position:0% get practical program officiation and 00:15:57.000 --> 00:15:59.470 align:start position:0% get practical program officiation and finally<00:15:57.279> build<00:15:57.480> the<00:15:57.600> god<00:15:57.839> protocol 00:15:59.470 --> 00:15:59.480 align:start position:0% finally build the god protocol 00:15:59.480 --> 00:16:05.470 align:start position:0% finally build the god protocol and<00:15:59.639> that's<00:15:59.800> it<00:16:00.240> thank 00:16:05.470 --> 00:16:05.480 align:start position:0% 00:16:05.480 --> 00:16:08.389 align:start position:0% you<00:16:06.480> all<00:16:06.680> right<00:16:07.040> thank<00:16:07.240> you<00:16:07.399> for<00:16:07.600> the<00:16:07.800> talk<00:16:08.240> we 00:16:08.389 --> 00:16:08.399 align:start position:0% you all right thank you for the talk we 00:16:08.399 --> 00:16:13.269 align:start position:0% you all right thank you for the talk we do<00:16:08.680> have<00:16:08.880> some<00:16:09.240> questions<00:16:09.680> rolling<00:16:10.120> in 00:16:13.269 --> 00:16:13.279 align:start position:0% 00:16:13.279 --> 00:16:16.069 align:start position:0% uh<00:16:14.279> yeah<00:16:14.600> uh<00:16:14.759> let's<00:16:15.120> go<00:16:15.319> through<00:16:15.600> some<00:16:15.759> of<00:16:15.920> the 00:16:16.069 --> 00:16:16.079 align:start position:0% uh yeah uh let's go through some of the 00:16:16.079 --> 00:16:17.949 align:start position:0% uh yeah uh let's go through some of the questions<00:16:16.959> uh<00:16:17.079> let's<00:16:17.240> start<00:16:17.480> with<00:16:17.600> the<00:16:17.759> first 00:16:17.949 --> 00:16:17.959 align:start position:0% questions uh let's start with the first 00:16:17.959 --> 00:16:21.189 align:start position:0% questions uh let's start with the first one<00:16:18.880> can<00:16:19.040> we<00:16:19.279> Implement<00:16:19.720> threshold<00:16:20.240> ecdsa 00:16:21.189 --> 00:16:21.199 align:start position:0% one can we Implement threshold ecdsa 00:16:21.199 --> 00:16:22.870 align:start position:0% one can we Implement threshold ecdsa with<00:16:21.360> Phantom 00:16:22.870 --> 00:16:22.880 align:start position:0% with Phantom 00:16:22.880 --> 00:16:26.309 align:start position:0% with Phantom Zone<00:16:23.880> at<00:16:24.000> the<00:16:24.160> moment<00:16:25.040> yes<00:16:25.399> because<00:16:25.680> you<00:16:25.759> can 00:16:26.309 --> 00:16:26.319 align:start position:0% Zone at the moment yes because you can 00:16:26.319 --> 00:16:28.150 align:start position:0% Zone at the moment yes because you can express<00:16:26.720> every<00:16:27.199> like<00:16:27.440> practical<00:16:28.000> like 00:16:28.150 --> 00:16:28.160 align:start position:0% express every like practical like 00:16:28.160 --> 00:16:29.670 align:start position:0% express every like practical like theoretically<00:16:28.680> yes<00:16:29.000> but<00:16:29.120> it<00:16:29.199> would<00:16:29.360> be<00:16:29.480> very 00:16:29.670 --> 00:16:29.680 align:start position:0% theoretically yes but it would be very 00:16:29.680 --> 00:16:31.189 align:start position:0% theoretically yes but it would be very impractical<00:16:30.160> to<00:16:30.240> implement<00:16:30.560> ecds<00:16:31.120> with 00:16:31.189 --> 00:16:31.199 align:start position:0% impractical to implement ecds with 00:16:31.199 --> 00:16:33.269 align:start position:0% impractical to implement ecds with Phantom<00:16:31.480> Zone<00:16:31.639> at<00:16:31.759> the<00:16:31.839> moment<00:16:32.160> because<00:16:32.639> ecds 00:16:33.269 --> 00:16:33.279 align:start position:0% Phantom Zone at the moment because ecds 00:16:33.279 --> 00:16:35.110 align:start position:0% Phantom Zone at the moment because ecds is<00:16:33.480> like<00:16:33.800> you're<00:16:33.920> doing<00:16:34.160> eptic<00:16:34.720> operations 00:16:35.110 --> 00:16:35.120 align:start position:0% is like you're doing eptic operations 00:16:35.120 --> 00:16:37.430 align:start position:0% is like you're doing eptic operations which<00:16:35.199> is<00:16:35.319> a<00:16:35.440> lot<00:16:35.560> of<00:16:35.839> operations<00:16:36.839> um<00:16:37.199> as<00:16:37.319> far 00:16:37.430 --> 00:16:37.440 align:start position:0% which is a lot of operations um as far 00:16:37.440 --> 00:16:39.790 align:start position:0% which is a lot of operations um as far as<00:16:37.560> I<00:16:38.000> understand<00:16:38.680> threshold<00:16:39.120> ecds<00:16:39.600> is 00:16:39.790 --> 00:16:39.800 align:start position:0% as I understand threshold ecds is 00:16:39.800 --> 00:16:43.150 align:start position:0% as I understand threshold ecds is possible<00:16:40.800> it<00:16:40.959> takes<00:16:41.240> two<00:16:41.519> days<00:16:42.120> to<00:16:42.800> generate 00:16:43.150 --> 00:16:43.160 align:start position:0% possible it takes two days to generate 00:16:43.160 --> 00:16:44.590 align:start position:0% possible it takes two days to generate one<00:16:43.319> single 00:16:44.590 --> 00:16:44.600 align:start position:0% one single 00:16:44.600 --> 00:16:47.430 align:start position:0% one single signature<00:16:45.600> all<00:16:45.759> right<00:16:45.959> so<00:16:46.319> next<00:16:46.639> question<00:16:47.319> can 00:16:47.430 --> 00:16:47.440 align:start position:0% signature all right so next question can 00:16:47.440 --> 00:16:49.710 align:start position:0% signature all right so next question can you<00:16:47.600> tell<00:16:47.839> us<00:16:48.040> a<00:16:48.160> little<00:16:48.360> bit<00:16:48.600> more<00:16:49.040> about<00:16:49.480> the 00:16:49.710 --> 00:16:49.720 align:start position:0% you tell us a little bit more about the 00:16:49.720 --> 00:16:53.509 align:start position:0% you tell us a little bit more about the definition<00:16:50.519> of<00:16:51.480> obfuscation<00:16:52.480> as<00:16:52.680> a<00:16:53.000> virtual 00:16:53.509 --> 00:16:53.519 align:start position:0% definition of obfuscation as a virtual 00:16:53.519 --> 00:16:55.069 align:start position:0% definition of obfuscation as a virtual black 00:16:55.069 --> 00:16:55.079 align:start position:0% black 00:16:55.079 --> 00:16:58.389 align:start position:0% black box<00:16:56.079> that's<00:16:56.240> the<00:16:56.480> first<00:16:56.759> question<00:16:57.120> over<00:16:57.399> here 00:16:58.389 --> 00:16:58.399 align:start position:0% box that's the first question over here 00:16:58.399 --> 00:17:00.350 align:start position:0% box that's the first question over here isn't<00:16:58.920> definition<00:16:59.360> ofation<00:16:59.839> as<00:16:59.920> a<00:17:00.040> virtual 00:17:00.350 --> 00:17:00.360 align:start position:0% isn't definition ofation as a virtual 00:17:00.360 --> 00:17:05.429 align:start position:0% isn't definition ofation as a virtual blackbox 00:17:05.429 --> 00:17:05.439 align:start position:0% 00:17:05.439 --> 00:17:08.669 align:start position:0% impossible<00:17:06.439> I<00:17:06.760> I<00:17:06.880> am<00:17:07.079> not<00:17:07.360> posing<00:17:07.959> officiation 00:17:08.669 --> 00:17:08.679 align:start position:0% impossible I I am not posing officiation 00:17:08.679 --> 00:17:12.150 align:start position:0% impossible I I am not posing officiation as<00:17:08.799> a<00:17:08.919> virtual<00:17:09.520> blackbox<00:17:10.520> um<00:17:11.439> I<00:17:11.640> I<00:17:11.760> did<00:17:11.919> not 00:17:12.150 --> 00:17:12.160 align:start position:0% as a virtual blackbox um I I did not 00:17:12.160 --> 00:17:14.029 align:start position:0% as a virtual blackbox um I I did not mean<00:17:12.360> to<00:17:12.480> say<00:17:12.760> officiation<00:17:13.199> is<00:17:13.280> a<00:17:13.400> virtual 00:17:14.029 --> 00:17:14.039 align:start position:0% mean to say officiation is a virtual 00:17:14.039 --> 00:17:16.510 align:start position:0% mean to say officiation is a virtual blackbox<00:17:15.039> uh<00:17:15.240> by<00:17:15.360> the<00:17:15.480> way<00:17:15.799> the<00:17:16.000> impossibility 00:17:16.510 --> 00:17:16.520 align:start position:0% blackbox uh by the way the impossibility 00:17:16.520 --> 00:17:18.390 align:start position:0% blackbox uh by the way the impossibility resolve<00:17:16.799> for<00:17:16.919> virtual<00:17:17.160> blackbox<00:17:17.760> is<00:17:18.000> only<00:17:18.199> for 00:17:18.390 --> 00:17:18.400 align:start position:0% resolve for virtual blackbox is only for 00:17:18.400 --> 00:17:20.150 align:start position:0% resolve for virtual blackbox is only for like<00:17:18.559> certain<00:17:18.959> very<00:17:19.240> restricted<00:17:19.760> class<00:17:20.000> of 00:17:20.150 --> 00:17:20.160 align:start position:0% like certain very restricted class of 00:17:20.160 --> 00:17:22.470 align:start position:0% like certain very restricted class of programs<00:17:21.079> it's<00:17:21.280> not<00:17:21.520> for<00:17:21.760> like<00:17:21.880> General<00:17:22.280> class 00:17:22.470 --> 00:17:22.480 align:start position:0% programs it's not for like General class 00:17:22.480 --> 00:17:24.909 align:start position:0% programs it's not for like General class of<00:17:22.600> programs<00:17:23.439> eventually<00:17:23.959> you<00:17:24.079> can<00:17:24.400> aim<00:17:24.640> for 00:17:24.909 --> 00:17:24.919 align:start position:0% of programs eventually you can aim for 00:17:24.919 --> 00:17:27.710 align:start position:0% of programs eventually you can aim for virtual<00:17:25.240> blackbox<00:17:25.799> with<00:17:25.959> certain<00:17:26.439> caveats<00:17:27.439> um 00:17:27.710 --> 00:17:27.720 align:start position:0% virtual blackbox with certain caveats um 00:17:27.720 --> 00:17:30.110 align:start position:0% virtual blackbox with certain caveats um but<00:17:28.480> against<00:17:28.919> saying<00:17:29.200> that<00:17:29.400> my<00:17:29.600> my<00:17:29.760> definition 00:17:30.110 --> 00:17:30.120 align:start position:0% but against saying that my my definition 00:17:30.120 --> 00:17:34.190 align:start position:0% but against saying that my my definition of<00:17:30.280> officiation<00:17:30.919> is<00:17:31.080> not<00:17:31.360> virtual<00:17:32.120> blackbox 00:17:34.190 --> 00:17:34.200 align:start position:0% of officiation is not virtual blackbox 00:17:34.200 --> 00:17:37.350 align:start position:0% of officiation is not virtual blackbox um<00:17:35.200> all<00:17:35.360> right<00:17:35.880> and<00:17:36.080> what<00:17:36.240> can<00:17:36.400> be<00:17:36.559> done<00:17:36.880> today 00:17:37.350 --> 00:17:37.360 align:start position:0% um all right and what can be done today 00:17:37.360 --> 00:17:38.750 align:start position:0% um all right and what can be done today with<00:17:37.640> Phantom 00:17:38.750 --> 00:17:38.760 align:start position:0% with Phantom 00:17:38.760 --> 00:17:41.750 align:start position:0% with Phantom Zone<00:17:39.760> at<00:17:39.919> the<00:17:40.039> moment<00:17:40.840> as<00:17:40.919> I<00:17:41.080> said<00:17:41.400> Phantom 00:17:41.750 --> 00:17:41.760 align:start position:0% Zone at the moment as I said Phantom 00:17:41.760 --> 00:17:43.549 align:start position:0% Zone at the moment as I said Phantom Zone<00:17:42.000> is<00:17:42.080> an<00:17:42.240> Abridged<00:17:42.679> version<00:17:42.919> of<00:17:43.080> this<00:17:43.240> God 00:17:43.549 --> 00:17:43.559 align:start position:0% Zone is an Abridged version of this God 00:17:43.559 --> 00:17:46.110 align:start position:0% Zone is an Abridged version of this God protocol<00:17:44.559> it<00:17:44.679> does<00:17:44.960> not<00:17:45.120> even<00:17:45.440> have<00:17:45.919> a 00:17:46.110 --> 00:17:46.120 align:start position:0% protocol it does not even have a 00:17:46.120 --> 00:17:48.510 align:start position:0% protocol it does not even have a publicly<00:17:46.559> byi<00:17:47.000> ref<00:17:47.400> scheme<00:17:47.880> so<00:17:48.039> it<00:17:48.160> does<00:17:48.360> not 00:17:48.510 --> 00:17:48.520 align:start position:0% publicly byi ref scheme so it does not 00:17:48.520 --> 00:17:49.870 align:start position:0% publicly byi ref scheme so it does not give<00:17:48.640> you<00:17:48.799> all<00:17:48.919> the<00:17:49.039> three<00:17:49.280> guarantees<00:17:49.799> the 00:17:49.870 --> 00:17:49.880 align:start position:0% give you all the three guarantees the 00:17:49.880 --> 00:17:51.830 align:start position:0% give you all the three guarantees the only<00:17:50.120> guarantee<00:17:50.480> that<00:17:50.559> it<00:17:50.679> gives<00:17:50.919> you<00:17:51.400> is<00:17:51.600> that 00:17:51.830 --> 00:17:51.840 align:start position:0% only guarantee that it gives you is that 00:17:51.840 --> 00:17:54.270 align:start position:0% only guarantee that it gives you is that it<00:17:51.919> will<00:17:52.160> execute<00:17:52.559> the<00:17:53.039> function<00:17:54.039> that<00:17:54.160> you 00:17:54.270 --> 00:17:54.280 align:start position:0% it will execute the function that you 00:17:54.280 --> 00:17:57.149 align:start position:0% it will execute the function that you ask<00:17:54.480> it<00:17:54.600> to<00:17:54.880> execute<00:17:55.880> while<00:17:56.240> input<00:17:56.720> while 00:17:57.149 --> 00:17:57.159 align:start position:0% ask it to execute while input while 00:17:57.159 --> 00:17:58.470 align:start position:0% ask it to execute while input while private<00:17:57.520> information<00:17:57.919> can<00:17:58.039> be<00:17:58.159> coming<00:17:58.360> from 00:17:58.470 --> 00:17:58.480 align:start position:0% private information can be coming from 00:17:58.480 --> 00:18:00.710 align:start position:0% private information can be coming from multiple<00:17:59.159> people<00:18:00.159> you'll<00:18:00.400> keep<00:18:00.600> the 00:18:00.710 --> 00:18:00.720 align:start position:0% multiple people you'll keep the 00:18:00.720 --> 00:18:02.029 align:start position:0% multiple people you'll keep the information<00:18:01.159> private<00:18:01.520> but<00:18:01.640> you'll<00:18:01.799> have<00:18:01.919> to 00:18:02.029 --> 00:18:02.039 align:start position:0% information private but you'll have to 00:18:02.039 --> 00:18:03.390 align:start position:0% information private but you'll have to trust<00:18:02.280> it<00:18:02.400> for<00:18:02.559> it<00:18:02.679> so<00:18:02.799> you<00:18:02.919> have<00:18:03.039> to<00:18:03.120> trust 00:18:03.390 --> 00:18:03.400 align:start position:0% trust it for it so you have to trust 00:18:03.400 --> 00:18:05.390 align:start position:0% trust it for it so you have to trust this<00:18:03.640> particular<00:18:04.000> server<00:18:04.520> to<00:18:04.760> always<00:18:05.159> keep 00:18:05.390 --> 00:18:05.400 align:start position:0% this particular server to always keep 00:18:05.400 --> 00:18:06.710 align:start position:0% this particular server to always keep the<00:18:05.559> information<00:18:05.960> private<00:18:06.240> and<00:18:06.320> not<00:18:06.480> send<00:18:06.640> it 00:18:06.710 --> 00:18:06.720 align:start position:0% the information private and not send it 00:18:06.720 --> 00:18:09.710 align:start position:0% the information private and not send it to<00:18:06.840> anyone<00:18:07.559> else<00:18:08.559> perfect<00:18:09.000> and<00:18:09.159> we<00:18:09.280> do<00:18:09.520> have 00:18:09.710 --> 00:18:09.720 align:start position:0% to anyone else perfect and we do have 00:18:09.720 --> 00:18:11.789 align:start position:0% to anyone else perfect and we do have one<00:18:09.960> last<00:18:10.280> question<00:18:10.760> oh<00:18:10.960> cool<00:18:11.200> more<00:18:11.480> questions 00:18:11.789 --> 00:18:11.799 align:start position:0% one last question oh cool more questions 00:18:11.799 --> 00:18:14.669 align:start position:0% one last question oh cool more questions rolling<00:18:12.159> in<00:18:12.799> can<00:18:13.120> obus<00:18:13.720> skating<00:18:14.159> programs 00:18:14.669 --> 00:18:14.679 align:start position:0% rolling in can obus skating programs 00:18:14.679 --> 00:18:17.190 align:start position:0% rolling in can obus skating programs undermine<00:18:15.320> open-<00:18:15.640> Source<00:18:16.039> transparency<00:18:17.039> and 00:18:17.190 --> 00:18:17.200 align:start position:0% undermine open- Source transparency and 00:18:17.200 --> 00:18:19.950 align:start position:0% undermine open- Source transparency and make<00:18:17.360> it<00:18:17.600> harder<00:18:18.000> to<00:18:18.240> verify<00:18:18.799> the<00:18:19.039> absence<00:18:19.559> of 00:18:19.950 --> 00:18:19.960 align:start position:0% make it harder to verify the absence of 00:18:19.960 --> 00:18:21.549 align:start position:0% make it harder to verify the absence of malicious 00:18:21.549 --> 00:18:21.559 align:start position:0% malicious 00:18:21.559 --> 00:18:26.510 align:start position:0% malicious code<00:18:23.039> uh<00:18:24.039> I<00:18:24.360> see<00:18:25.360> make<00:18:25.559> it<00:18:25.720> harder<00:18:26.000> to<00:18:26.120> verify 00:18:26.510 --> 00:18:26.520 align:start position:0% code uh I see make it harder to verify 00:18:26.520 --> 00:18:28.190 align:start position:0% code uh I see make it harder to verify absence<00:18:26.799> of<00:18:26.919> malicious<00:18:27.360> code<00:18:27.720> well<00:18:27.880> that<00:18:28.000> is 00:18:28.190 --> 00:18:28.200 align:start position:0% absence of malicious code well that is 00:18:28.200 --> 00:18:30.350 align:start position:0% absence of malicious code well that is assuming<00:18:28.520> that<00:18:28.799> the<00:18:28.880> entire<00:18:29.200> program<00:18:29.520> is 00:18:30.350 --> 00:18:30.360 align:start position:0% assuming that the entire program is 00:18:30.360 --> 00:18:33.830 align:start position:0% assuming that the entire program is officiated<00:18:31.360> um<00:18:32.080> when<00:18:32.240> I<00:18:32.520> say<00:18:32.880> officiation<00:18:33.679> we 00:18:33.830 --> 00:18:33.840 align:start position:0% officiated um when I say officiation we 00:18:33.840 --> 00:18:35.350 align:start position:0% officiated um when I say officiation we require<00:18:34.159> officiation<00:18:34.640> for<00:18:34.799> certain<00:18:35.039> parts<00:18:35.240> of 00:18:35.350 --> 00:18:35.360 align:start position:0% require officiation for certain parts of 00:18:35.360 --> 00:18:36.830 align:start position:0% require officiation for certain parts of the<00:18:35.480> program<00:18:35.840> which<00:18:36.000> can<00:18:36.159> interact<00:18:36.559> with<00:18:36.679> a 00:18:36.830 --> 00:18:36.840 align:start position:0% the program which can interact with a 00:18:36.840 --> 00:18:38.350 align:start position:0% the program which can interact with a public<00:18:37.159> program<00:18:37.520> and<00:18:37.640> a<00:18:37.799> private<00:18:38.080> program 00:18:38.350 --> 00:18:38.360 align:start position:0% public program and a private program 00:18:38.360 --> 00:18:41.230 align:start position:0% public program and a private program which<00:18:38.480> is<00:18:39.039> obic<00:18:40.039> I<00:18:40.400> understand<00:18:40.520> that<00:18:40.679> obic<00:18:41.120> can 00:18:41.230 --> 00:18:41.240 align:start position:0% which is obic I understand that obic can 00:18:41.240 --> 00:18:42.909 align:start position:0% which is obic I understand that obic can be<00:18:41.320> used<00:18:41.520> for<00:18:41.640> many<00:18:41.840> malicious<00:18:42.400> purposes<00:18:42.799> as 00:18:42.909 --> 00:18:42.919 align:start position:0% be used for many malicious purposes as 00:18:42.919 --> 00:18:45.710 align:start position:0% be used for many malicious purposes as well<00:18:43.159> like<00:18:43.320> for<00:18:43.480> example<00:18:43.840> you<00:18:44.360> know<00:18:45.360> like 00:18:45.710 --> 00:18:45.720 align:start position:0% well like for example you know like 00:18:45.720 --> 00:18:46.909 align:start position:0% well like for example you know like there<00:18:45.880> there's<00:18:46.039> several<00:18:46.280> reasons<00:18:46.600> why<00:18:46.720> people 00:18:46.909 --> 00:18:46.919 align:start position:0% there there's several reasons why people 00:18:46.919 --> 00:18:48.590 align:start position:0% there there's several reasons why people might<00:18:47.120> be<00:18:47.360> interested<00:18:47.679> in<00:18:47.760> OBS<00:18:47.960> cation<00:18:48.320> but<00:18:48.440> we 00:18:48.590 --> 00:18:48.600 align:start position:0% might be interested in OBS cation but we 00:18:48.600 --> 00:18:50.149 align:start position:0% might be interested in OBS cation but we can<00:18:48.760> as<00:18:48.840> a<00:18:48.960> community<00:18:49.320> make<00:18:49.480> sure<00:18:49.799> that 00:18:50.149 --> 00:18:50.159 align:start position:0% can as a community make sure that 00:18:50.159 --> 00:18:51.310 align:start position:0% can as a community make sure that there's<00:18:50.320> an<00:18:50.480> interaction<00:18:50.919> between<00:18:51.159> the 00:18:51.310 --> 00:18:51.320 align:start position:0% there's an interaction between the 00:18:51.320 --> 00:18:52.909 align:start position:0% there's an interaction between the public<00:18:51.600> interfaces<00:18:52.360> and<00:18:52.480> the<00:18:52.600> private 00:18:52.909 --> 00:18:52.919 align:start position:0% public interfaces and the private 00:18:52.919 --> 00:18:54.789 align:start position:0% public interfaces and the private interfaces<00:18:53.360> which<00:18:53.440> are 00:18:54.789 --> 00:18:54.799 align:start position:0% interfaces which are 00:18:54.799 --> 00:18:58.830 align:start position:0% interfaces which are obsc<00:18:55.799> all<00:18:56.000> right<00:18:56.760> and<00:18:57.559> why<00:18:57.760> do<00:18:57.919> you<00:18:58.159> call<00:18:58.400> the 00:18:58.830 --> 00:18:58.840 align:start position:0% obsc all right and why do you call the 00:18:58.840 --> 00:19:01.909 align:start position:0% obsc all right and why do you call the publicly<00:18:59.480> verifiable<00:19:00.400> FH<00:19:01.000> circuit 00:19:01.909 --> 00:19:01.919 align:start position:0% publicly verifiable FH circuit 00:19:01.919 --> 00:19:05.510 align:start position:0% publicly verifiable FH circuit obfuscated<00:19:02.919> doesn't<00:19:03.520> the<00:19:04.000> require<00:19:04.840> solidity 00:19:05.510 --> 00:19:05.520 align:start position:0% obfuscated doesn't the require solidity 00:19:05.520 --> 00:19:09.190 align:start position:0% obfuscated doesn't the require solidity verifier<00:19:06.240> or<00:19:06.480> something<00:19:07.159> which<00:19:07.320> is 00:19:09.190 --> 00:19:09.200 align:start position:0% verifier or something which is 00:19:09.200 --> 00:19:13.190 align:start position:0% verifier or something which is public<00:19:10.200> uh<00:19:10.880> no<00:19:11.880> uh<00:19:12.280> I<00:19:12.400> think<00:19:12.679> once<00:19:12.840> I<00:19:13.000> give<00:19:13.120> you 00:19:13.190 --> 00:19:13.200 align:start position:0% public uh no uh I think once I give you 00:19:13.200 --> 00:19:14.990 align:start position:0% public uh no uh I think once I give you off<00:19:13.440> secar<00:19:13.760> circuit<00:19:14.520> there<00:19:14.760> certain 00:19:14.990 --> 00:19:15.000 align:start position:0% off secar circuit there certain 00:19:15.000 --> 00:19:16.350 align:start position:0% off secar circuit there certain guarantees<00:19:15.400> that<00:19:15.520> you<00:19:15.640> can<00:19:15.840> learn<00:19:16.120> from<00:19:16.240> the 00:19:16.350 --> 00:19:16.360 align:start position:0% guarantees that you can learn from the 00:19:16.360 --> 00:19:17.990 align:start position:0% guarantees that you can learn from the obate<00:19:16.799> circuit<00:19:17.080> itself<00:19:17.520> that<00:19:17.640> it<00:19:17.720> does<00:19:17.840> not 00:19:17.990 --> 00:19:18.000 align:start position:0% obate circuit itself that it does not 00:19:18.000 --> 00:19:19.470 align:start position:0% obate circuit itself that it does not reveal<00:19:18.320> anything<00:19:18.760> as<00:19:18.880> long<00:19:19.039> as<00:19:19.159> youve<00:19:19.320> done 00:19:19.470 --> 00:19:19.480 align:start position:0% reveal anything as long as youve done 00:19:19.480 --> 00:19:22.430 align:start position:0% reveal anything as long as youve done the<00:19:19.559> OBS<00:19:19.760> cation<00:19:20.280> correctly<00:19:21.280> all<00:19:21.440> right<00:19:22.120> and 00:19:22.430 --> 00:19:22.440 align:start position:0% the OBS cation correctly all right and 00:19:22.440 --> 00:19:24.190 align:start position:0% the OBS cation correctly all right and do<00:19:22.600> you<00:19:22.799> have<00:19:23.080> evidence<00:19:23.640> that<00:19:23.840> the 00:19:24.190 --> 00:19:24.200 align:start position:0% do you have evidence that the 00:19:24.200 --> 00:19:26.230 align:start position:0% do you have evidence that the conditional<00:19:24.520> decryption<00:19:25.200> functionality<00:19:25.960> is 00:19:26.230 --> 00:19:26.240 align:start position:0% conditional decryption functionality is 00:19:26.240 --> 00:19:29.510 align:start position:0% conditional decryption functionality is imposs<00:19:26.960> uh<00:19:27.159> is<00:19:27.400> possible<00:19:27.919> using<00:19:28.360> IO 00:19:29.510 --> 00:19:29.520 align:start position:0% imposs uh is possible using IO 00:19:29.520 --> 00:19:31.710 align:start position:0% imposs uh is possible using IO yes<00:19:30.159> uh<00:19:30.559> there<00:19:30.679> is<00:19:31.080> there<00:19:31.280> theoretical 00:19:31.710 --> 00:19:31.720 align:start position:0% yes uh there is there theoretical 00:19:31.720 --> 00:19:32.870 align:start position:0% yes uh there is there theoretical results<00:19:32.120> and<00:19:32.240> we're<00:19:32.360> trying<00:19:32.559> to<00:19:32.640> make<00:19:32.760> it 00:19:32.870 --> 00:19:32.880 align:start position:0% results and we're trying to make it 00:19:32.880 --> 00:19:33.950 align:start position:0% results and we're trying to make it practical<00:19:33.280> as 00:19:33.950 --> 00:19:33.960 align:start position:0% practical as 00:19:33.960 --> 00:19:36.390 align:start position:0% practical as well<00:19:34.960> all<00:19:35.120> right<00:19:35.559> uh<00:19:35.720> can<00:19:35.840> you<00:19:36.000> give<00:19:36.159> one 00:19:36.390 --> 00:19:36.400 align:start position:0% well all right uh can you give one 00:19:36.400 --> 00:19:39.669 align:start position:0% well all right uh can you give one example<00:19:36.960> each<00:19:37.280> on<00:19:37.600> how<00:19:37.960> IO<00:19:38.360> can<00:19:38.559> replace<00:19:38.960> ZK 00:19:39.669 --> 00:19:39.679 align:start position:0% example each on how IO can replace ZK 00:19:39.679 --> 00:19:43.230 align:start position:0% example each on how IO can replace ZK MPC<00:19:40.720> fhe<00:19:41.720> okay<00:19:41.919> so<00:19:42.080> for<00:19:42.280> ZK<00:19:42.760> what<00:19:42.840> you<00:19:42.960> can<00:19:43.080> do 00:19:43.230 --> 00:19:43.240 align:start position:0% MPC fhe okay so for ZK what you can do 00:19:43.240 --> 00:19:45.110 align:start position:0% MPC fhe okay so for ZK what you can do is<00:19:43.440> like<00:19:43.919> you<00:19:44.080> can<00:19:44.240> embed<00:19:44.520> a<00:19:44.679> secret<00:19:45.000> key 00:19:45.110 --> 00:19:45.120 align:start position:0% is like you can embed a secret key 00:19:45.120 --> 00:19:47.350 align:start position:0% is like you can embed a secret key inside<00:19:45.360> this<00:19:45.720> secr<00:19:46.039> circuit<00:19:46.440> the<00:19:46.600> god 00:19:47.350 --> 00:19:47.360 align:start position:0% inside this secr circuit the god 00:19:47.360 --> 00:19:50.470 align:start position:0% inside this secr circuit the god protocol<00:19:48.360> and<00:19:48.880> uh<00:19:49.440> a<00:19:49.600> Zer<00:19:49.880> knowledge<00:19:50.120> proof<00:19:50.360> is 00:19:50.470 --> 00:19:50.480 align:start position:0% protocol and uh a Zer knowledge proof is 00:19:50.480 --> 00:19:52.430 align:start position:0% protocol and uh a Zer knowledge proof is just<00:19:50.640> a<00:19:50.799> signature<00:19:51.280> from<00:19:51.440> this<00:19:51.640> God<00:19:51.840> protocol 00:19:52.430 --> 00:19:52.440 align:start position:0% just a signature from this God protocol 00:19:52.440 --> 00:19:54.549 align:start position:0% just a signature from this God protocol they<00:19:52.679> whatever<00:19:53.000> the<00:19:53.080> secr<00:19:53.640> whatever<00:19:53.919> secret 00:19:54.549 --> 00:19:54.559 align:start position:0% they whatever the secr whatever secret 00:19:54.559 --> 00:19:56.750 align:start position:0% they whatever the secr whatever secret exists<00:19:54.880> inside<00:19:55.240> this<00:19:55.400> particular<00:19:55.840> server<00:19:56.559> or 00:19:56.750 --> 00:19:56.760 align:start position:0% exists inside this particular server or 00:19:56.760 --> 00:19:58.750 align:start position:0% exists inside this particular server or this<00:19:56.919> God<00:19:57.159> protocol<00:19:57.679> or<00:19:57.840> this<00:19:58.000> F<00:19:58.280> Circuit<00:19:58.520> of 00:19:58.750 --> 00:19:58.760 align:start position:0% this God protocol or this F Circuit of 00:19:58.760 --> 00:19:59.630 align:start position:0% this God protocol or this F Circuit of SEC 00:19:59.630 --> 00:19:59.640 align:start position:0% SEC 00:19:59.640 --> 00:20:02.669 align:start position:0% SEC circuit<00:20:00.640> a<00:20:00.799> signature<00:20:01.360> by<00:20:01.679> that<00:20:01.919> thing 00:20:02.669 --> 00:20:02.679 align:start position:0% circuit a signature by that thing 00:20:02.679 --> 00:20:04.310 align:start position:0% circuit a signature by that thing becomes<00:20:03.039> the<00:20:03.159> zero<00:20:03.400> knowledge<00:20:03.640> proofs<00:20:04.080> so<00:20:04.240> you 00:20:04.310 --> 00:20:04.320 align:start position:0% becomes the zero knowledge proofs so you 00:20:04.320 --> 00:20:05.630 align:start position:0% becomes the zero knowledge proofs so you do<00:20:04.440> not<00:20:04.600> require<00:20:04.880> zero<00:20:05.159> knowledge<00:20:05.400> on<00:20:05.520> the 00:20:05.630 --> 00:20:05.640 align:start position:0% do not require zero knowledge on the 00:20:05.640 --> 00:20:10.190 align:start position:0% do not require zero knowledge on the client<00:20:06.000> side<00:20:06.640> uh<00:20:07.159> anymore<00:20:08.159> for<00:20:08.720> NPC<00:20:09.720> again 00:20:10.190 --> 00:20:10.200 align:start position:0% client side uh anymore for NPC again 00:20:10.200 --> 00:20:12.270 align:start position:0% client side uh anymore for NPC again it's<00:20:10.320> a<00:20:10.799> globally<00:20:11.200> mutually<00:20:11.600> trusted<00:20:12.000> third 00:20:12.270 --> 00:20:12.280 align:start position:0% it's a globally mutually trusted third 00:20:12.280 --> 00:20:14.830 align:start position:0% it's a globally mutually trusted third party<00:20:12.679> all<00:20:12.799> of<00:20:12.960> us<00:20:13.200> encrypt<00:20:13.799> our<00:20:14.120> private 00:20:14.830 --> 00:20:14.840 align:start position:0% party all of us encrypt our private 00:20:14.840 --> 00:20:17.830 align:start position:0% party all of us encrypt our private inputs<00:20:15.840> with<00:20:16.080> the<00:20:16.559> public<00:20:16.919> key<00:20:17.320> corresponding 00:20:17.830 --> 00:20:17.840 align:start position:0% inputs with the public key corresponding 00:20:17.840 --> 00:20:19.430 align:start position:0% inputs with the public key corresponding to<00:20:17.960> the<00:20:18.120> secret<00:20:18.440> key<00:20:18.640> that<00:20:18.760> lives<00:20:19.039> inside<00:20:19.320> this 00:20:19.430 --> 00:20:19.440 align:start position:0% to the secret key that lives inside this 00:20:19.440 --> 00:20:21.350 align:start position:0% to the secret key that lives inside this off<00:20:19.760> gate<00:20:19.960> circuit<00:20:20.559> and<00:20:20.679> we<00:20:20.799> send<00:20:21.000> a<00:20:21.120> private 00:20:21.350 --> 00:20:21.360 align:start position:0% off gate circuit and we send a private 00:20:21.360 --> 00:20:23.990 align:start position:0% off gate circuit and we send a private inputs<00:20:21.679> to<00:20:21.880> this<00:20:22.240> it<00:20:22.400> decrypts<00:20:22.919> that<00:20:23.640> performs 00:20:23.990 --> 00:20:24.000 align:start position:0% inputs to this it decrypts that performs 00:20:24.000 --> 00:20:26.350 align:start position:0% inputs to this it decrypts that performs some<00:20:24.200> function<00:20:24.840> and<00:20:25.039> produces<00:20:25.520> the<00:20:25.679> output<00:20:26.159> so 00:20:26.350 --> 00:20:26.360 align:start position:0% some function and produces the output so 00:20:26.360 --> 00:20:28.350 align:start position:0% some function and produces the output so that's<00:20:26.520> one<00:20:26.679> way<00:20:26.799> of<00:20:26.919> replacing<00:20:27.520> MPC<00:20:28.159> and<00:20:28.280> the 00:20:28.350 --> 00:20:28.360 align:start position:0% that's one way of replacing MPC and the 00:20:28.360 --> 00:20:32.149 align:start position:0% that's one way of replacing MPC and the same<00:20:28.919> for<00:20:29.159> FG<00:20:30.159> cool<00:20:30.760> uh<00:20:31.000> we<00:20:31.159> can<00:20:31.440> stay<00:20:31.760> here<00:20:31.919> for 00:20:32.149 --> 00:20:32.159 align:start position:0% same for FG cool uh we can stay here for 00:20:32.159 --> 00:20:34.390 align:start position:0% same for FG cool uh we can stay here for maybe<00:20:32.480> another<00:20:32.799> 10<00:20:33.039> seconds<00:20:33.600> if<00:20:33.799> there<00:20:34.080> are 00:20:34.390 --> 00:20:34.400 align:start position:0% maybe another 10 seconds if there are 00:20:34.400 --> 00:20:45.950 align:start position:0% maybe another 10 seconds if there are any<00:20:34.720> new<00:20:34.960> questions<00:20:35.360> rolling 00:20:45.950 --> 00:20:45.960 align:start position:0% 00:20:45.960 --> 00:20:50.600 align:start position:0% in<00:20:46.960> all<00:20:47.120> right<00:20:47.360> cool<00:20:47.960> um<00:20:48.120> let's<00:20:48.320> give