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.150 align:start position:0% [Music] 00:00:09.150 --> 00:00:09.160 align:start position:0% [Music] 00:00:09.160 --> 00:00:11.950 align:start position:0% [Music] yeah<00:00:09.320> we're<00:00:09.480> going<00:00:09.559> to<00:00:09.719> talk<00:00:09.920> about<00:00:10.280> data 00:00:11.950 --> 00:00:11.960 align:start position:0% yeah we're going to talk about data 00:00:11.960 --> 00:00:14.869 align:start position:0% yeah we're going to talk about data um<00:00:12.960> so<00:00:13.480> to<00:00:13.759> kind<00:00:13.880> of<00:00:14.000> like<00:00:14.160> situate<00:00:14.519> ourselves 00:00:14.869 --> 00:00:14.879 align:start position:0% um so to kind of like situate ourselves 00:00:14.879 --> 00:00:18.070 align:start position:0% um so to kind of like situate ourselves a<00:00:14.960> little<00:00:15.200> bit<00:00:15.519> in<00:00:16.359> I<00:00:16.440> have<00:00:16.640> 60<00:00:17.000> slides<00:00:17.760> you 00:00:18.070 --> 00:00:18.080 align:start position:0% a little bit in I have 60 slides you 00:00:18.080 --> 00:00:19.790 align:start position:0% a little bit in I have 60 slides you can't<00:00:18.400> go<00:00:18.560> through<00:00:18.800> 60<00:00:19.119> slides<00:00:19.520> without 00:00:19.790 --> 00:00:19.800 align:start position:0% can't go through 60 slides without 00:00:19.800 --> 00:00:21.269 align:start position:0% can't go through 60 slides without knowing<00:00:20.160> why<00:00:20.359> you're<00:00:20.560> here<00:00:21.080> because 00:00:21.269 --> 00:00:21.279 align:start position:0% knowing why you're here because 00:00:21.279 --> 00:00:23.029 align:start position:0% knowing why you're here because otherwise<00:00:21.600> you'll<00:00:21.840> just<00:00:22.080> like<00:00:22.760> lose 00:00:23.029 --> 00:00:23.039 align:start position:0% otherwise you'll just like lose 00:00:23.039 --> 00:00:26.429 align:start position:0% otherwise you'll just like lose attention<00:00:23.359> and<00:00:23.560> collect<00:00:23.840> frogs<00:00:24.760> so<00:00:25.400> um<00:00:25.840> zerp 00:00:26.429 --> 00:00:26.439 align:start position:0% attention and collect frogs so um zerp 00:00:26.439 --> 00:00:28.589 align:start position:0% attention and collect frogs so um zerp thesis<00:00:26.720> for<00:00:26.920> Data<00:00:27.199> Systems<00:00:27.760> is<00:00:27.920> that 00:00:28.589 --> 00:00:28.599 align:start position:0% thesis for Data Systems is that 00:00:28.599 --> 00:00:30.790 align:start position:0% thesis for Data Systems is that essentially<00:00:29.199> in<00:00:29.439> like<00:00:30.080> one<00:00:30.279> sentence 00:00:30.790 --> 00:00:30.800 align:start position:0% essentially in like one sentence 00:00:30.800 --> 00:00:32.670 align:start position:0% essentially in like one sentence programmable<00:00:31.359> cryptography<00:00:31.920> so<00:00:32.119> zero<00:00:32.399> Notch 00:00:32.670 --> 00:00:32.680 align:start position:0% programmable cryptography so zero Notch 00:00:32.680 --> 00:00:35.270 align:start position:0% programmable cryptography so zero Notch proof<00:00:33.000> FH<00:00:33.559> officiation<00:00:34.559> enables<00:00:35.040> what<00:00:35.160> we 00:00:35.270 --> 00:00:35.280 align:start position:0% proof FH officiation enables what we 00:00:35.280 --> 00:00:37.350 align:start position:0% proof FH officiation enables what we call<00:00:35.440> the<00:00:35.559> universal<00:00:36.040> data<00:00:36.320> adapter<00:00:37.120> which<00:00:37.239> is 00:00:37.350 --> 00:00:37.360 align:start position:0% call the universal data adapter which is 00:00:37.360 --> 00:00:38.910 align:start position:0% call the universal data adapter which is in<00:00:37.520> some<00:00:37.719> way<00:00:37.960> like<00:00:38.079> the<00:00:38.200> touring<00:00:38.600> machine 00:00:38.910 --> 00:00:38.920 align:start position:0% in some way like the touring machine 00:00:38.920 --> 00:00:40.630 align:start position:0% in some way like the touring machine moment<00:00:39.280> for<00:00:39.520> data<00:00:40.120> what<00:00:40.200> I<00:00:40.280> mean<00:00:40.480> by<00:00:40.559> the 00:00:40.630 --> 00:00:40.640 align:start position:0% moment for data what I mean by the 00:00:40.640 --> 00:00:42.790 align:start position:0% moment for data what I mean by the touring<00:00:40.920> machine<00:00:41.200> moment<00:00:41.559> is<00:00:41.680> it's<00:00:42.360> we<00:00:42.520> think 00:00:42.790 --> 00:00:42.800 align:start position:0% touring machine moment is it's we think 00:00:42.800 --> 00:00:45.389 align:start position:0% touring machine moment is it's we think we<00:00:43.039> basically<00:00:43.719> finally<00:00:44.239> have<00:00:44.600> an<00:00:44.800> abstraction 00:00:45.389 --> 00:00:45.399 align:start position:0% we basically finally have an abstraction 00:00:45.399 --> 00:00:47.430 align:start position:0% we basically finally have an abstraction that's<00:00:45.640> powerful<00:00:46.160> enough<00:00:46.559> such<00:00:46.800> that<00:00:47.280> it's 00:00:47.430 --> 00:00:47.440 align:start position:0% that's powerful enough such that it's 00:00:47.440 --> 00:00:49.470 align:start position:0% that's powerful enough such that it's not<00:00:47.600> like<00:00:47.719> a<00:00:47.879> marginal<00:00:48.440> Improvement<00:00:49.320> it's 00:00:49.470 --> 00:00:49.480 align:start position:0% not like a marginal Improvement it's 00:00:49.480 --> 00:00:51.270 align:start position:0% not like a marginal Improvement it's like<00:00:49.600> an<00:00:49.760> order<00:00:50.039> of<00:00:50.199> magnitude<00:00:50.680> improvements 00:00:51.270 --> 00:00:51.280 align:start position:0% like an order of magnitude improvements 00:00:51.280 --> 00:00:53.549 align:start position:0% like an order of magnitude improvements the<00:00:51.399> same<00:00:51.600> way<00:00:52.199> electrical<00:00:52.840> circuits 00:00:53.549 --> 00:00:53.559 align:start position:0% the same way electrical circuits 00:00:53.559 --> 00:00:56.549 align:start position:0% the same way electrical circuits basically<00:00:54.399> got<00:00:54.559> turn<00:00:54.800> into<00:00:55.079> like<00:00:56.039> extremely 00:00:56.549 --> 00:00:56.559 align:start position:0% basically got turn into like extremely 00:00:56.559 --> 00:00:58.430 align:start position:0% basically got turn into like extremely powerful<00:00:57.039> beasts<00:00:57.559> when<00:00:57.719> we<00:00:57.840> figured<00:00:58.160> out<00:00:58.359> how 00:00:58.430 --> 00:00:58.440 align:start position:0% powerful beasts when we figured out how 00:00:58.440 --> 00:01:00.189 align:start position:0% powerful beasts when we figured out how to<00:00:58.680> program<00:00:59.079> them<00:00:59.199> and<00:00:59.320> make<00:00:59.440> them<00:00:59.559> General<00:01:00.120> it 00:01:00.189 --> 00:01:00.199 align:start position:0% to program them and make them General it 00:01:00.199 --> 00:01:01.270 align:start position:0% to program them and make them General it was<00:01:00.320> not<00:01:00.440> like<00:01:00.559> an<00:01:00.680> improvement<00:01:01.039> at<00:01:01.160> the 00:01:01.270 --> 00:01:01.280 align:start position:0% was not like an improvement at the 00:01:01.280 --> 00:01:02.670 align:start position:0% was not like an improvement at the physics<00:01:01.600> level<00:01:01.840> it<00:01:01.960> was<00:01:02.079> an<00:01:02.199> improvement<00:01:02.559> at 00:01:02.670 --> 00:01:02.680 align:start position:0% physics level it was an improvement at 00:01:02.680 --> 00:01:05.789 align:start position:0% physics level it was an improvement at the<00:01:02.800> mental<00:01:03.120> model<00:01:03.440> level<00:01:04.280> so<00:01:05.239> um<00:01:05.439> another<00:01:05.680> way 00:01:05.789 --> 00:01:05.799 align:start position:0% the mental model level so um another way 00:01:05.799 --> 00:01:07.149 align:start position:0% the mental model level so um another way to<00:01:05.920> say<00:01:06.040> that<00:01:06.159> is<00:01:06.240> we<00:01:06.360> think<00:01:06.479> cryptography<00:01:07.080> is 00:01:07.149 --> 00:01:07.159 align:start position:0% to say that is we think cryptography is 00:01:07.159 --> 00:01:09.590 align:start position:0% to say that is we think cryptography is a<00:01:07.280> way<00:01:07.400> to<00:01:07.520> get<00:01:07.680> more<00:01:08.000> out<00:01:08.119> of<00:01:08.320> data<00:01:09.040> and<00:01:09.320> most 00:01:09.590 --> 00:01:09.600 align:start position:0% a way to get more out of data and most 00:01:09.600 --> 00:01:10.830 align:start position:0% a way to get more out of data and most people<00:01:09.799> will<00:01:09.960> tell<00:01:10.080> you<00:01:10.200> that<00:01:10.320> cryptography 00:01:10.830 --> 00:01:10.840 align:start position:0% people will tell you that cryptography 00:01:10.840 --> 00:01:12.749 align:start position:0% people will tell you that cryptography is<00:01:10.920> a<00:01:11.040> way<00:01:11.159> to<00:01:11.560> make<00:01:11.759> data<00:01:12.000> more<00:01:12.280> private<00:01:12.600> or 00:01:12.749 --> 00:01:12.759 align:start position:0% is a way to make data more private or 00:01:12.759 --> 00:01:14.270 align:start position:0% is a way to make data more private or whatever<00:01:13.200> I<00:01:13.320> think<00:01:13.520> that<00:01:13.720> that's<00:01:13.880> a<00:01:14.040> great 00:01:14.270 --> 00:01:14.280 align:start position:0% whatever I think that that's a great 00:01:14.280 --> 00:01:15.950 align:start position:0% whatever I think that that's a great side<00:01:14.520> effect<00:01:14.880> but<00:01:15.240> deeper<00:01:15.600> than<00:01:15.720> that 00:01:15.950 --> 00:01:15.960 align:start position:0% side effect but deeper than that 00:01:15.960 --> 00:01:18.270 align:start position:0% side effect but deeper than that cryptography<00:01:16.439> is<00:01:16.520> a<00:01:16.640> way<00:01:16.759> to<00:01:17.080> get<00:01:17.400> more<00:01:17.799> out<00:01:18.040> of 00:01:18.270 --> 00:01:18.280 align:start position:0% cryptography is a way to get more out of 00:01:18.280 --> 00:01:20.190 align:start position:0% cryptography is a way to get more out of data<00:01:18.880> essentially<00:01:19.280> make<00:01:19.479> data<00:01:19.920> more 00:01:20.190 --> 00:01:20.200 align:start position:0% data essentially make data more 00:01:20.200 --> 00:01:22.069 align:start position:0% data essentially make data more interoperable<00:01:21.000> be<00:01:21.079> able<00:01:21.240> to<00:01:21.360> get<00:01:21.520> data<00:01:21.759> out<00:01:21.920> of 00:01:22.069 --> 00:01:22.079 align:start position:0% interoperable be able to get data out of 00:01:22.079 --> 00:01:23.990 align:start position:0% interoperable be able to get data out of their<00:01:22.240> silos<00:01:22.799> reap<00:01:23.159> more<00:01:23.439> economical 00:01:23.990 --> 00:01:24.000 align:start position:0% their silos reap more economical 00:01:24.000 --> 00:01:25.670 align:start position:0% their silos reap more economical benefits<00:01:24.400> out<00:01:24.520> of<00:01:24.680> data<00:01:25.200> and<00:01:25.320> it's<00:01:25.479> pretty 00:01:25.670 --> 00:01:25.680 align:start position:0% benefits out of data and it's pretty 00:01:25.680 --> 00:01:26.910 align:start position:0% benefits out of data and it's pretty important<00:01:26.079> because<00:01:26.240> we<00:01:26.360> live<00:01:26.479> in<00:01:26.600> a<00:01:26.720> world 00:01:26.910 --> 00:01:26.920 align:start position:0% important because we live in a world 00:01:26.920 --> 00:01:28.590 align:start position:0% important because we live in a world where<00:01:27.079> the<00:01:27.240> value<00:01:27.479> of<00:01:27.600> data<00:01:27.880> keeps<00:01:28.119> increasing 00:01:28.590 --> 00:01:28.600 align:start position:0% where the value of data keeps increasing 00:01:28.600 --> 00:01:31.350 align:start position:0% where the value of data keeps increasing over<00:01:28.880> time<00:01:29.799> um<00:01:30.360> one<00:01:30.520> way<00:01:30.720> we<00:01:30.880> we<00:01:31.000> like<00:01:31.119> to<00:01:31.240> put 00:01:31.350 --> 00:01:31.360 align:start position:0% over time um one way we we like to put 00:01:31.360 --> 00:01:32.789 align:start position:0% over time um one way we we like to put it<00:01:31.479> is<00:01:31.640> we<00:01:31.759> take<00:01:31.920> data<00:01:32.159> out<00:01:32.240> of<00:01:32.360> their<00:01:32.520> data 00:01:32.789 --> 00:01:32.799 align:start position:0% it is we take data out of their data 00:01:32.799 --> 00:01:34.590 align:start position:0% it is we take data out of their data prison<00:01:33.399> today<00:01:33.680> if<00:01:33.799> you<00:01:33.880> want<00:01:34.000> your<00:01:34.159> data<00:01:34.360> to<00:01:34.439> be 00:01:34.590 --> 00:01:34.600 align:start position:0% prison today if you want your data to be 00:01:34.600 --> 00:01:37.069 align:start position:0% prison today if you want your data to be safe<00:01:34.799> and<00:01:34.960> secure<00:01:35.520> it's<00:01:35.759> useless<00:01:36.759> uh<00:01:36.840> you<00:01:36.960> have 00:01:37.069 --> 00:01:37.079 align:start position:0% safe and secure it's useless uh you have 00:01:37.079 --> 00:01:38.870 align:start position:0% safe and secure it's useless uh you have to<00:01:37.320> like<00:01:37.759> kind<00:01:37.920> of<00:01:38.079> like<00:01:38.360> keep<00:01:38.560> it<00:01:38.680> for 00:01:38.870 --> 00:01:38.880 align:start position:0% to like kind of like keep it for 00:01:38.880 --> 00:01:40.990 align:start position:0% to like kind of like keep it for yourself<00:01:39.439> and<00:01:39.640> and<00:01:39.759> it<00:01:39.920> applies<00:01:40.439> equally<00:01:40.759> for 00:01:40.990 --> 00:01:41.000 align:start position:0% yourself and and it applies equally for 00:01:41.000 --> 00:01:42.990 align:start position:0% yourself and and it applies equally for like<00:01:41.560> individuals<00:01:42.200> who<00:01:42.320> want<00:01:42.479> to<00:01:42.600> do<00:01:42.720> self 00:01:42.990 --> 00:01:43.000 align:start position:0% like individuals who want to do self 00:01:43.000 --> 00:01:45.030 align:start position:0% like individuals who want to do self custody<00:01:43.360> but<00:01:43.479> also<00:01:43.680> for<00:01:43.880> companies<00:01:44.439> like<00:01:44.799> why 00:01:45.030 --> 00:01:45.040 align:start position:0% custody but also for companies like why 00:01:45.040 --> 00:01:46.950 align:start position:0% custody but also for companies like why keep<00:01:45.200> your<00:01:45.399> data<00:01:45.600> on<00:01:45.759> your<00:01:46.200> Linux<00:01:46.560> server<00:01:46.880> if 00:01:46.950 --> 00:01:46.960 align:start position:0% keep your data on your Linux server if 00:01:46.960 --> 00:01:48.510 align:start position:0% keep your data on your Linux server if you<00:01:47.079> can<00:01:47.200> put<00:01:47.320> it<00:01:47.399> in<00:01:47.520> the<00:01:47.640> one<00:01:47.840> big<00:01:48.079> database 00:01:48.510 --> 00:01:48.520 align:start position:0% you can put it in the one big database 00:01:48.520 --> 00:01:49.950 align:start position:0% you can put it in the one big database you<00:01:48.640> know<00:01:48.880> because<00:01:49.079> the<00:01:49.159> one<00:01:49.320> big<00:01:49.520> database 00:01:49.950 --> 00:01:49.960 align:start position:0% you know because the one big database 00:01:49.960 --> 00:01:51.510 align:start position:0% you know because the one big database will<00:01:50.159> like<00:01:50.479> give<00:01:50.600> you<00:01:50.759> more<00:01:50.960> value<00:01:51.240> out<00:01:51.360> of 00:01:51.510 --> 00:01:51.520 align:start position:0% will like give you more value out of 00:01:51.520 --> 00:01:53.590 align:start position:0% will like give you more value out of that<00:01:52.240> so<00:01:52.600> there's<00:01:52.840> kind<00:01:52.960> of<00:01:53.119> like<00:01:53.240> this<00:01:53.399> push 00:01:53.590 --> 00:01:53.600 align:start position:0% that so there's kind of like this push 00:01:53.600 --> 00:01:55.389 align:start position:0% that so there's kind of like this push and<00:01:53.719> pull<00:01:54.040> between<00:01:54.640> people<00:01:54.880> want<00:01:55.040> to<00:01:55.200> keep 00:01:55.389 --> 00:01:55.399 align:start position:0% and pull between people want to keep 00:01:55.399 --> 00:01:57.590 align:start position:0% and pull between people want to keep their<00:01:55.640> data<00:01:56.000> kind<00:01:56.119> of<00:01:56.280> like<00:01:56.479> away<00:01:57.240> in<00:01:57.399> some 00:01:57.590 --> 00:01:57.600 align:start position:0% their data kind of like away in some 00:01:57.600 --> 00:01:59.709 align:start position:0% their data kind of like away in some sense<00:01:58.000> in<00:01:58.240> in<00:01:58.479> in<00:01:58.560> a<00:01:58.680> secure<00:01:59.039> environment<00:01:59.560> but 00:01:59.709 --> 00:01:59.719 align:start position:0% sense in in in a secure environment but 00:01:59.719 --> 00:02:00.950 align:start position:0% sense in in in a secure environment but that<00:01:59.880> it's<00:02:00.000> equivalent<00:02:00.320> to<00:02:00.399> a<00:02:00.520> prison<00:02:00.880> you 00:02:00.950 --> 00:02:00.960 align:start position:0% that it's equivalent to a prison you 00:02:00.960 --> 00:02:02.910 align:start position:0% that it's equivalent to a prison you know<00:02:01.119> you<00:02:01.280> can't<00:02:01.719> go<00:02:01.920> screw<00:02:02.280> with<00:02:02.399> the<00:02:02.520> inmates 00:02:02.910 --> 00:02:02.920 align:start position:0% know you can't go screw with the inmates 00:02:02.920 --> 00:02:05.670 align:start position:0% know you can't go screw with the inmates but<00:02:03.119> inmates<00:02:03.399> are<00:02:03.520> not<00:02:03.680> useful<00:02:03.960> to<00:02:04.240> society<00:02:05.240> um 00:02:05.670 --> 00:02:05.680 align:start position:0% but inmates are not useful to society um 00:02:05.680 --> 00:02:07.149 align:start position:0% but inmates are not useful to society um and<00:02:05.920> and<00:02:06.079> another<00:02:06.360> way<00:02:06.520> yet<00:02:06.640> to<00:02:06.759> say<00:02:06.920> that<00:02:07.000> is 00:02:07.149 --> 00:02:07.159 align:start position:0% and and another way yet to say that is 00:02:07.159 --> 00:02:09.029 align:start position:0% and and another way yet to say that is enables<00:02:07.520> more<00:02:07.680> interoperability<00:02:08.399> in<00:02:08.759> usage 00:02:09.029 --> 00:02:09.039 align:start position:0% enables more interoperability in usage 00:02:09.039 --> 00:02:09.869 align:start position:0% enables more interoperability in usage of 00:02:09.869 --> 00:02:09.879 align:start position:0% of 00:02:09.879 --> 00:02:12.510 align:start position:0% of data<00:02:10.879> um<00:02:11.080> so<00:02:11.280> our<00:02:11.480> goal<00:02:11.720> is<00:02:11.840> to<00:02:12.000> create<00:02:12.280> more 00:02:12.510 --> 00:02:12.520 align:start position:0% data um so our goal is to create more 00:02:12.520 --> 00:02:14.830 align:start position:0% data um so our goal is to create more total<00:02:12.920> valuee<00:02:13.480> out<00:02:13.640> of<00:02:13.879> this<00:02:14.280> and<00:02:14.400> at<00:02:14.519> the<00:02:14.640> same 00:02:14.830 --> 00:02:14.840 align:start position:0% total valuee out of this and at the same 00:02:14.840 --> 00:02:16.910 align:start position:0% total valuee out of this and at the same time<00:02:15.000> enable<00:02:15.319> a<00:02:15.519> pragmatic<00:02:16.120> route<00:02:16.519> towards 00:02:16.910 --> 00:02:16.920 align:start position:0% time enable a pragmatic route towards 00:02:16.920 --> 00:02:18.670 align:start position:0% time enable a pragmatic route towards data<00:02:17.120> ownership<00:02:17.599> in<00:02:17.680> a<00:02:17.840> world<00:02:18.160> where<00:02:18.400> data 00:02:18.670 --> 00:02:18.680 align:start position:0% data ownership in a world where data 00:02:18.680 --> 00:02:20.270 align:start position:0% data ownership in a world where data keeps<00:02:18.879> increasing<00:02:19.280> in<00:02:19.480> value<00:02:19.959> because<00:02:20.120> if 00:02:20.270 --> 00:02:20.280 align:start position:0% keeps increasing in value because if 00:02:20.280 --> 00:02:22.190 align:start position:0% keeps increasing in value because if data<00:02:20.519> keeps<00:02:20.760> increasing<00:02:21.120> in<00:02:21.319> value<00:02:21.959> the 00:02:22.190 --> 00:02:22.200 align:start position:0% data keeps increasing in value the 00:02:22.200 --> 00:02:24.229 align:start position:0% data keeps increasing in value the burden<00:02:22.519> of<00:02:22.800> proof<00:02:23.400> for<00:02:23.640> going<00:02:23.879> through<00:02:24.080> that 00:02:24.229 --> 00:02:24.239 align:start position:0% burden of proof for going through that 00:02:24.239 --> 00:02:27.350 align:start position:0% burden of proof for going through that route<00:02:24.599> keeps<00:02:24.879> increasing<00:02:25.840> okay<00:02:26.239> so<00:02:27.080> this<00:02:27.200> is 00:02:27.350 --> 00:02:27.360 align:start position:0% route keeps increasing okay so this is 00:02:27.360 --> 00:02:29.309 align:start position:0% route keeps increasing okay so this is kind<00:02:27.480> of<00:02:27.560> like<00:02:27.680> the<00:02:27.760> tldr<00:02:28.319> on<00:02:28.680> the<00:02:28.840> data<00:02:29.040> stack 00:02:29.309 --> 00:02:29.319 align:start position:0% kind of like the tldr on the data stack 00:02:29.319 --> 00:02:32.150 align:start position:0% kind of like the tldr on the data stack we<00:02:29.440> have<00:02:29.560> so<00:02:29.680> far<00:02:30.000> far<00:02:30.680> um<00:02:31.000> we<00:02:31.200> have<00:02:31.640> pods<00:02:32.040> which 00:02:32.150 --> 00:02:32.160 align:start position:0% we have so far far um we have pods which 00:02:32.160 --> 00:02:34.949 align:start position:0% we have so far far um we have pods which are<00:02:32.879> essentially<00:02:33.640> specially<00:02:34.160> issued<00:02:34.640> packets 00:02:34.949 --> 00:02:34.959 align:start position:0% are essentially specially issued packets 00:02:34.959 --> 00:02:36.470 align:start position:0% are essentially specially issued packets of<00:02:35.160> cryptographic<00:02:35.760> data<00:02:36.080> almost<00:02:36.280> like<00:02:36.400> a 00:02:36.470 --> 00:02:36.480 align:start position:0% of cryptographic data almost like a 00:02:36.480 --> 00:02:38.949 align:start position:0% of cryptographic data almost like a record<00:02:36.760> in<00:02:36.879> a<00:02:37.040> database<00:02:38.040> we<00:02:38.160> have<00:02:38.360> these 00:02:38.949 --> 00:02:38.959 align:start position:0% record in a database we have these 00:02:38.959 --> 00:02:40.910 align:start position:0% record in a database we have these cryptographic<00:02:39.519> machines<00:02:39.879> called<00:02:40.120> gpcs<00:02:40.720> that 00:02:40.910 --> 00:02:40.920 align:start position:0% cryptographic machines called gpcs that 00:02:40.920 --> 00:02:42.949 align:start position:0% cryptographic machines called gpcs that ingest<00:02:41.400> pods<00:02:41.680> and<00:02:41.840> make<00:02:42.040> claims<00:02:42.480> about<00:02:42.760> them 00:02:42.949 --> 00:02:42.959 align:start position:0% ingest pods and make claims about them 00:02:42.959 --> 00:02:45.030 align:start position:0% ingest pods and make claims about them using<00:02:43.200> zero<00:02:43.480> knowledge<00:02:43.800> proof<00:02:44.640> and<00:02:44.879> the 00:02:45.030 --> 00:02:45.040 align:start position:0% using zero knowledge proof and the 00:02:45.040 --> 00:02:45.990 align:start position:0% using zero knowledge proof and the really<00:02:45.239> interesting<00:02:45.560> thing<00:02:45.680> with<00:02:45.879> this 00:02:45.990 --> 00:02:46.000 align:start position:0% really interesting thing with this 00:02:46.000 --> 00:02:47.470 align:start position:0% really interesting thing with this system<00:02:46.280> is<00:02:46.400> it's<00:02:46.599> performant<00:02:47.040> enough<00:02:47.200> to<00:02:47.319> run 00:02:47.470 --> 00:02:47.480 align:start position:0% system is it's performant enough to run 00:02:47.480 --> 00:02:49.470 align:start position:0% system is it's performant enough to run on<00:02:47.680> mobile<00:02:48.000> browsers<00:02:48.920> uh<00:02:49.080> while<00:02:49.239> being 00:02:49.470 --> 00:02:49.480 align:start position:0% on mobile browsers uh while being 00:02:49.480 --> 00:02:50.990 align:start position:0% on mobile browsers uh while being flexible<00:02:50.239> and<00:02:50.360> it's<00:02:50.519> close<00:02:50.720> to<00:02:50.800> being 00:02:50.990 --> 00:02:51.000 align:start position:0% flexible and it's close to being 00:02:51.000 --> 00:02:53.149 align:start position:0% flexible and it's close to being production<00:02:51.360> ready<00:02:52.080> and<00:02:52.519> all<00:02:52.680> of<00:02:52.800> you<00:02:52.920> guys<00:02:53.040> are 00:02:53.149 --> 00:02:53.159 align:start position:0% production ready and all of you guys are 00:02:53.159 --> 00:02:55.630 align:start position:0% production ready and all of you guys are using<00:02:53.440> it<00:02:54.080> uh<00:02:54.239> Zupas<00:02:54.840> where<00:02:55.000> your<00:02:55.159> tickets<00:02:55.440> are 00:02:55.630 --> 00:02:55.640 align:start position:0% using it uh Zupas where your tickets are 00:02:55.640 --> 00:02:57.350 align:start position:0% using it uh Zupas where your tickets are and<00:02:55.760> your<00:02:55.840> frogs<00:02:56.200> are<00:02:56.480> are<00:02:56.800> is<00:02:56.879> running<00:02:57.159> on 00:02:57.350 --> 00:02:57.360 align:start position:0% and your frogs are are is running on 00:02:57.360 --> 00:02:59.990 align:start position:0% and your frogs are are is running on pods<00:02:57.640> and<00:02:57.800> gpcs<00:02:58.680> so<00:02:58.920> as<00:02:59.000> an<00:02:59.120> example<00:02:59.519> def 00:02:59.990 --> 00:03:00.000 align:start position:0% pods and gpcs so as an example def 00:03:00.000 --> 00:03:02.509 align:start position:0% pods and gpcs so as an example def ticket<00:03:00.239> is<00:03:00.319> a<00:03:00.480> pod<00:03:00.760> a<00:03:00.879> frog<00:03:01.200> is<00:03:01.280> a<00:03:01.480> pod<00:03:02.080> I<00:03:02.239> use 00:03:02.509 --> 00:03:02.519 align:start position:0% ticket is a pod a frog is a pod I use 00:03:02.519 --> 00:03:04.470 align:start position:0% ticket is a pod a frog is a pod I use GPC<00:03:02.920> to<00:03:03.040> log<00:03:03.239> in<00:03:03.360> into<00:03:03.560> the<00:03:03.760> telegram<00:03:04.200> group 00:03:04.470 --> 00:03:04.480 align:start position:0% GPC to log in into the telegram group 00:03:04.480 --> 00:03:06.070 align:start position:0% GPC to log in into the telegram group where<00:03:04.599> you<00:03:04.720> had<00:03:04.840> to<00:03:04.920> prove<00:03:05.120> you<00:03:05.239> had<00:03:05.360> a<00:03:05.519> ticket 00:03:06.070 --> 00:03:06.080 align:start position:0% where you had to prove you had a ticket 00:03:06.080 --> 00:03:07.710 align:start position:0% where you had to prove you had a ticket when<00:03:06.200> you<00:03:06.280> enter<00:03:06.560> the<00:03:06.680> Frog<00:03:06.959> Zone<00:03:07.280> downstair 00:03:07.710 --> 00:03:07.720 align:start position:0% when you enter the Frog Zone downstair 00:03:07.720 --> 00:03:09.750 align:start position:0% when you enter the Frog Zone downstair you<00:03:07.840> also<00:03:08.000> make<00:03:08.159> a<00:03:08.239> GPC<00:03:08.959> so<00:03:09.159> this<00:03:09.280> stuff<00:03:09.560> just 00:03:09.750 --> 00:03:09.760 align:start position:0% you also make a GPC so this stuff just 00:03:09.760 --> 00:03:12.670 align:start position:0% you also make a GPC so this stuff just works<00:03:10.319> and<00:03:10.680> there's<00:03:11.280> a<00:03:11.480> huge<00:03:11.920> like<00:03:12.200> not<00:03:12.400> huge 00:03:12.670 --> 00:03:12.680 align:start position:0% works and there's a huge like not huge 00:03:12.680 --> 00:03:14.030 align:start position:0% works and there's a huge like not huge but<00:03:12.799> there's<00:03:13.120> there's<00:03:13.280> definitely<00:03:13.560> a<00:03:13.680> list<00:03:13.840> of 00:03:14.030 --> 00:03:14.040 align:start position:0% but there's there's definitely a list of 00:03:14.040 --> 00:03:16.070 align:start position:0% but there's there's definitely a list of like<00:03:14.720> on<00:03:14.920> top<00:03:15.080> of<00:03:15.159> that<00:03:15.319> like<00:03:15.480> third<00:03:15.799> party 00:03:16.070 --> 00:03:16.080 align:start position:0% like on top of that like third party 00:03:16.080 --> 00:03:18.030 align:start position:0% like on top of that like third party application<00:03:16.599> that<00:03:16.720> is<00:03:17.159> built<00:03:17.480> on<00:03:17.599> top<00:03:17.760> of<00:03:17.879> this 00:03:18.030 --> 00:03:18.040 align:start position:0% application that is built on top of this 00:03:18.040 --> 00:03:21.830 align:start position:0% application that is built on top of this system<00:03:18.360> mostly<00:03:18.599> from<00:03:18.720> the<00:03:18.879> zalu<00:03:20.000> ecosystem<00:03:21.000> so 00:03:21.830 --> 00:03:21.840 align:start position:0% system mostly from the zalu ecosystem so 00:03:21.840 --> 00:03:24.229 align:start position:0% system mostly from the zalu ecosystem so here's<00:03:22.040> the<00:03:22.159> tldr<00:03:23.000> the<00:03:23.120> way<00:03:23.239> it<00:03:23.319> works<00:03:23.599> is<00:03:23.959> some 00:03:24.229 --> 00:03:24.239 align:start position:0% here's the tldr the way it works is some 00:03:24.239 --> 00:03:26.550 align:start position:0% here's the tldr the way it works is some authority<00:03:24.720> attests<00:03:25.080> to<00:03:25.239> some<00:03:25.440> data<00:03:26.080> and<00:03:26.239> signs 00:03:26.550 --> 00:03:26.560 align:start position:0% authority attests to some data and signs 00:03:26.560 --> 00:03:29.149 align:start position:0% authority attests to some data and signs it<00:03:26.879> via<00:03:27.200> an<00:03:27.519> EDSA<00:03:28.159> signature<00:03:28.519> on<00:03:28.640> the<00:03:28.720> jobjob 00:03:29.149 --> 00:03:29.159 align:start position:0% it via an EDSA signature on the jobjob 00:03:29.159 --> 00:03:31.509 align:start position:0% it via an EDSA signature on the jobjob curve<00:03:29.599> this<00:03:29.840> gives<00:03:30.000> you<00:03:30.120> a<00:03:30.239> pod<00:03:30.920> you<00:03:31.239> take<00:03:31.400> a 00:03:31.509 --> 00:03:31.519 align:start position:0% curve this gives you a pod you take a 00:03:31.519 --> 00:03:33.390 align:start position:0% curve this gives you a pod you take a bunch<00:03:31.720> of<00:03:31.879> PODS<00:03:32.159> you<00:03:32.319> put<00:03:32.439> them<00:03:32.599> into<00:03:32.799> a<00:03:32.920> GPC 00:03:33.390 --> 00:03:33.400 align:start position:0% bunch of PODS you put them into a GPC 00:03:33.400 --> 00:03:35.390 align:start position:0% bunch of PODS you put them into a GPC and<00:03:33.519> you<00:03:33.599> make<00:03:33.760> a<00:03:33.920> claim<00:03:34.319> that<00:03:34.439> is<00:03:34.640> verifiable 00:03:35.390 --> 00:03:35.400 align:start position:0% and you make a claim that is verifiable 00:03:35.400 --> 00:03:36.789 align:start position:0% and you make a claim that is verifiable and<00:03:35.480> then<00:03:35.599> you<00:03:35.680> can<00:03:35.920> get<00:03:36.080> hand<00:03:36.239> that<00:03:36.400> over<00:03:36.560> to<00:03:36.680> a 00:03:36.789 --> 00:03:36.799 align:start position:0% and then you can get hand that over to a 00:03:36.799 --> 00:03:39.509 align:start position:0% and then you can get hand that over to a verifier<00:03:37.360> that's<00:03:37.959> essentially<00:03:38.319> how<00:03:38.480> it<00:03:38.560> works 00:03:39.509 --> 00:03:39.519 align:start position:0% verifier that's essentially how it works 00:03:39.519 --> 00:03:41.910 align:start position:0% verifier that's essentially how it works um<00:03:39.799> we'll<00:03:40.000> go<00:03:40.120> into<00:03:40.280> the<00:03:40.439> details<00:03:40.959> so<00:03:41.680> the 00:03:41.910 --> 00:03:41.920 align:start position:0% um we'll go into the details so the 00:03:41.920 --> 00:03:44.830 align:start position:0% um we'll go into the details so the issuer<00:03:42.920> basically<00:03:43.280> calls<00:03:43.720> this<00:03:43.959> like<00:03:44.280> pod. 00:03:44.830 --> 00:03:44.840 align:start position:0% issuer basically calls this like pod. 00:03:44.840 --> 00:03:47.110 align:start position:0% issuer basically calls this like pod. sign<00:03:45.120> method<00:03:45.480> on<00:03:45.599> a<00:03:45.760> bunch<00:03:45.920> of<00:03:46.040> key<00:03:46.239> value<00:03:46.560> data 00:03:47.110 --> 00:03:47.120 align:start position:0% sign method on a bunch of key value data 00:03:47.120 --> 00:03:49.670 align:start position:0% sign method on a bunch of key value data you<00:03:47.280> get<00:03:47.439> out<00:03:47.560> of<00:03:47.720> it<00:03:48.239> this<00:03:48.480> thing<00:03:49.040> with<00:03:49.159> a 00:03:49.670 --> 00:03:49.680 align:start position:0% you get out of it this thing with a 00:03:49.680 --> 00:03:52.309 align:start position:0% you get out of it this thing with a signature<00:03:50.680> that<00:03:50.799> is<00:03:50.959> on<00:03:51.400> the<00:03:51.599> content<00:03:51.959> ID 00:03:52.309 --> 00:03:52.319 align:start position:0% signature that is on the content ID 00:03:52.319 --> 00:03:53.789 align:start position:0% signature that is on the content ID we'll<00:03:52.519> focus<00:03:52.760> on<00:03:52.879> the<00:03:53.000> date<00:03:53.159> of<00:03:53.319> birth<00:03:53.519> here 00:03:53.789 --> 00:03:53.799 align:start position:0% we'll focus on the date of birth here 00:03:53.799 --> 00:03:55.390 align:start position:0% we'll focus on the date of birth here for<00:03:53.920> the<00:03:54.040> sake<00:03:54.200> of<00:03:54.280> the<00:03:54.439> example<00:03:55.120> then<00:03:55.239> you 00:03:55.390 --> 00:03:55.400 align:start position:0% for the sake of the example then you 00:03:55.400 --> 00:03:57.550 align:start position:0% for the sake of the example then you configure<00:03:55.799> a<00:03:55.959> GPC<00:03:56.439> config<00:03:57.000> which<00:03:57.159> makes<00:03:57.360> a 00:03:57.550 --> 00:03:57.560 align:start position:0% configure a GPC config which makes a 00:03:57.560 --> 00:03:59.270 align:start position:0% configure a GPC config which makes a claim<00:03:57.879> about<00:03:58.120> the<00:03:58.239> date<00:03:58.400> of<00:03:58.519> birth<00:03:58.920> for<00:03:59.120> this 00:03:59.270 --> 00:03:59.280 align:start position:0% claim about the date of birth for this 00:03:59.280 --> 00:04:01.789 align:start position:0% claim about the date of birth for this example<00:03:59.920> here<00:04:00.400> it's<00:04:00.640> not<00:04:00.879> revealed<00:04:01.519> and<00:04:01.640> we 00:04:01.789 --> 00:04:01.799 align:start position:0% example here it's not revealed and we 00:04:01.799 --> 00:04:03.350 align:start position:0% example here it's not revealed and we prove<00:04:02.079> that<00:04:02.200> it's<00:04:02.400> between<00:04:02.680> a<00:04:02.799> minimum<00:04:03.120> and<00:04:03.239> a 00:04:03.350 --> 00:04:03.360 align:start position:0% prove that it's between a minimum and a 00:04:03.360 --> 00:04:06.589 align:start position:0% prove that it's between a minimum and a maximum<00:04:04.120> and<00:04:04.360> finally<00:04:04.720> a<00:04:05.319> verifier<00:04:06.319> receives 00:04:06.589 --> 00:04:06.599 align:start position:0% maximum and finally a verifier receives 00:04:06.599 --> 00:04:08.229 align:start position:0% maximum and finally a verifier receives the<00:04:06.760> artifact<00:04:07.280> from<00:04:07.480> the<00:04:07.680> proof<00:04:07.959> and<00:04:08.079> can 00:04:08.229 --> 00:04:08.239 align:start position:0% the artifact from the proof and can 00:04:08.239 --> 00:04:09.869 align:start position:0% the artifact from the proof and can verify<00:04:08.599> that<00:04:08.760> claim<00:04:09.239> and<00:04:09.360> a<00:04:09.480> really<00:04:09.640> cool 00:04:09.869 --> 00:04:09.879 align:start position:0% verify that claim and a really cool 00:04:09.879 --> 00:04:11.149 align:start position:0% verify that claim and a really cool thing<00:04:10.040> is<00:04:10.200> you<00:04:10.319> don't<00:04:10.439> need<00:04:10.560> any<00:04:10.720> new<00:04:10.920> zero 00:04:11.149 --> 00:04:11.159 align:start position:0% thing is you don't need any new zero 00:04:11.159 --> 00:04:12.910 align:start position:0% thing is you don't need any new zero knowledge<00:04:11.400> circuits<00:04:11.959> it's<00:04:12.159> pretty<00:04:12.439> flexible 00:04:12.910 --> 00:04:12.920 align:start position:0% knowledge circuits it's pretty flexible 00:04:12.920 --> 00:04:14.910 align:start position:0% knowledge circuits it's pretty flexible and<00:04:13.040> also<00:04:13.280> extremely<00:04:13.720> performant<00:04:14.319> right<00:04:14.760> so 00:04:14.910 --> 00:04:14.920 align:start position:0% and also extremely performant right so 00:04:14.920 --> 00:04:16.189 align:start position:0% and also extremely performant right so we<00:04:15.040> have<00:04:15.200> this<00:04:15.360> system<00:04:15.640> we've<00:04:15.840> been<00:04:16.000> working 00:04:16.189 --> 00:04:16.199 align:start position:0% we have this system we've been working 00:04:16.199 --> 00:04:19.749 align:start position:0% we have this system we've been working on<00:04:16.280> it<00:04:16.400> for<00:04:16.519> a<00:04:16.680> year<00:04:17.560> um<00:04:18.359> and<00:04:18.799> you<00:04:18.959> can<00:04:19.359> go<00:04:19.560> check 00:04:19.749 --> 00:04:19.759 align:start position:0% on it for a year um and you can go check 00:04:19.759 --> 00:04:22.030 align:start position:0% on it for a year um and you can go check it<00:04:19.919> out<00:04:20.239> tomorrow<00:04:21.079> uh<00:04:21.199> at<00:04:21.359> classroom<00:04:21.759> B<00:04:21.919> at 00:04:22.030 --> 00:04:22.040 align:start position:0% it out tomorrow uh at classroom B at 00:04:22.040 --> 00:04:26.390 align:start position:0% it out tomorrow uh at classroom B at 2:30<00:04:22.479> p.m.<00:04:23.479> um<00:04:24.320> but<00:04:25.000> last<00:04:25.280> summer<00:04:25.880> we<00:04:26.040> wanted 00:04:26.390 --> 00:04:26.400 align:start position:0% 2:30 p.m. um but last summer we wanted 00:04:26.400 --> 00:04:27.990 align:start position:0% 2:30 p.m. um but last summer we wanted more<00:04:26.680> out<00:04:26.880> of<00:04:27.000> our<00:04:27.199> system<00:04:27.560> like<00:04:27.720> this<00:04:27.840> is 00:04:27.990 --> 00:04:28.000 align:start position:0% more out of our system like this is 00:04:28.000 --> 00:04:30.550 align:start position:0% more out of our system like this is pretty<00:04:28.400> sweet<00:04:29.039> but<00:04:29.240> we<00:04:29.360> think<00:04:29.919> this<00:04:30.039> is<00:04:30.320> far 00:04:30.550 --> 00:04:30.560 align:start position:0% pretty sweet but we think this is far 00:04:30.560 --> 00:04:33.790 align:start position:0% pretty sweet but we think this is far from<00:04:30.759> being<00:04:31.000> the<00:04:31.120> best<00:04:31.400> we<00:04:31.520> can<00:04:32.120> do<00:04:33.120> so<00:04:33.479> if<00:04:33.600> we 00:04:33.790 --> 00:04:33.800 align:start position:0% from being the best we can do so if we 00:04:33.800 --> 00:04:35.950 align:start position:0% from being the best we can do so if we look<00:04:34.080> back<00:04:34.280> at<00:04:34.720> this<00:04:35.039> Paradigm<00:04:35.479> I<00:04:35.600> just<00:04:35.680> showed 00:04:35.950 --> 00:04:35.960 align:start position:0% look back at this Paradigm I just showed 00:04:35.960 --> 00:04:38.070 align:start position:0% look back at this Paradigm I just showed you<00:04:36.320> um<00:04:36.520> there's<00:04:36.720> a<00:04:36.800> bunch<00:04:36.960> of<00:04:37.080> limitations 00:04:38.070 --> 00:04:38.080 align:start position:0% you um there's a bunch of limitations 00:04:38.080 --> 00:04:39.909 align:start position:0% you um there's a bunch of limitations the<00:04:38.199> first<00:04:38.400> one<00:04:38.600> is<00:04:38.880> we<00:04:39.039> need<00:04:39.360> specially 00:04:39.909 --> 00:04:39.919 align:start position:0% the first one is we need specially 00:04:39.919 --> 00:04:41.670 align:start position:0% the first one is we need specially issued<00:04:40.360> data<00:04:40.720> what<00:04:40.840> this<00:04:40.960> means<00:04:41.199> is<00:04:41.360> we<00:04:41.520> need 00:04:41.670 --> 00:04:41.680 align:start position:0% issued data what this means is we need 00:04:41.680 --> 00:04:43.670 align:start position:0% issued data what this means is we need to<00:04:41.880> convince<00:04:42.240> data<00:04:42.639> testers<00:04:43.039> to<00:04:43.199> like<00:04:43.360> change 00:04:43.670 --> 00:04:43.680 align:start position:0% to convince data testers to like change 00:04:43.680 --> 00:04:45.029 align:start position:0% to convince data testers to like change the<00:04:43.800> way<00:04:43.919> they<00:04:44.039> issue<00:04:44.320> data<00:04:44.639> which<00:04:44.759> is<00:04:44.880> not 00:04:45.029 --> 00:04:45.039 align:start position:0% the way they issue data which is not 00:04:45.039 --> 00:04:47.270 align:start position:0% the way they issue data which is not very<00:04:45.240> pragmatic<00:04:46.240> it's<00:04:46.400> limited<00:04:46.720> to<00:04:46.880> one<00:04:47.039> round 00:04:47.270 --> 00:04:47.280 align:start position:0% very pragmatic it's limited to one round 00:04:47.280 --> 00:04:49.350 align:start position:0% very pragmatic it's limited to one round of<00:04:47.440> computation<00:04:48.000> you<00:04:48.120> can<00:04:48.240> take<00:04:48.479> pods<00:04:49.080> put<00:04:49.240> a 00:04:49.350 --> 00:04:49.360 align:start position:0% of computation you can take pods put a 00:04:49.360 --> 00:04:50.990 align:start position:0% of computation you can take pods put a GPC<00:04:49.759> on<00:04:49.919> top<00:04:50.160> but<00:04:50.280> what<00:04:50.400> you<00:04:50.479> get<00:04:50.639> out<00:04:50.759> of<00:04:50.880> is 00:04:50.990 --> 00:04:51.000 align:start position:0% GPC on top but what you get out of is 00:04:51.000 --> 00:04:52.710 align:start position:0% GPC on top but what you get out of is not<00:04:51.160> another<00:04:51.479> pod<00:04:51.840> it's<00:04:52.039> like<00:04:52.199> this<00:04:52.440> thing 00:04:52.710 --> 00:04:52.720 align:start position:0% not another pod it's like this thing 00:04:52.720 --> 00:04:54.550 align:start position:0% not another pod it's like this thing that<00:04:52.840> you<00:04:52.960> can't<00:04:53.240> keep<00:04:53.440> Computing<00:04:53.880> over<00:04:54.440> and 00:04:54.550 --> 00:04:54.560 align:start position:0% that you can't keep Computing over and 00:04:54.560 --> 00:04:55.990 align:start position:0% that you can't keep Computing over and finally<00:04:54.880> it's<00:04:55.039> very<00:04:55.199> much<00:04:55.320> limited<00:04:55.639> to<00:04:55.759> single 00:04:55.990 --> 00:04:56.000 align:start position:0% finally it's very much limited to single 00:04:56.000 --> 00:04:58.150 align:start position:0% finally it's very much limited to single player<00:04:56.280> use<00:04:56.560> cases<00:04:57.160> what<00:04:57.280> I<00:04:57.360> mean<00:04:57.600> is<00:04:57.840> when<00:04:57.960> you 00:04:58.150 --> 00:04:58.160 align:start position:0% player use cases what I mean is when you 00:04:58.160 --> 00:05:00.150 align:start position:0% player use cases what I mean is when you create<00:04:58.479> this<00:04:58.639> GPC<00:04:59.120> proof<00:04:59.720> you<00:04:59.840> actually<00:05:00.000> need 00:05:00.150 --> 00:05:00.160 align:start position:0% create this GPC proof you actually need 00:05:00.160 --> 00:05:02.629 align:start position:0% create this GPC proof you actually need to<00:05:00.320> know<00:05:00.600> all<00:05:00.759> the<00:05:00.880> input<00:05:01.240> pods<00:05:02.199> which<00:05:02.320> means 00:05:02.629 --> 00:05:02.639 align:start position:0% to know all the input pods which means 00:05:02.639 --> 00:05:04.110 align:start position:0% to know all the input pods which means that<00:05:02.800> if<00:05:02.919> you<00:05:03.080> try<00:05:03.240> to<00:05:03.360> do<00:05:03.479> it<00:05:03.720> together<00:05:03.960> with 00:05:04.110 --> 00:05:04.120 align:start position:0% that if you try to do it together with 00:05:04.120 --> 00:05:06.110 align:start position:0% that if you try to do it together with multiple<00:05:04.560> people<00:05:05.120> one<00:05:05.320> person<00:05:05.600> will<00:05:05.759> know<00:05:05.960> all 00:05:06.110 --> 00:05:06.120 align:start position:0% multiple people one person will know all 00:05:06.120 --> 00:05:09.070 align:start position:0% multiple people one person will know all the<00:05:06.360> inputs<00:05:07.360> so<00:05:08.039> this<00:05:08.199> is<00:05:08.360> not<00:05:08.600> compatible 00:05:09.070 --> 00:05:09.080 align:start position:0% the inputs so this is not compatible 00:05:09.080 --> 00:05:10.830 align:start position:0% the inputs so this is not compatible with<00:05:09.199> the<00:05:09.320> world<00:05:09.600> we're<00:05:10.000> in<00:05:10.160> today<00:05:10.479> if<00:05:10.600> we're 00:05:10.830 --> 00:05:10.840 align:start position:0% with the world we're in today if we're 00:05:10.840 --> 00:05:12.670 align:start position:0% with the world we're in today if we're pragmatic<00:05:11.360> about<00:05:11.560> deploying<00:05:12.039> this<00:05:12.240> Beyond 00:05:12.670 --> 00:05:12.680 align:start position:0% pragmatic about deploying this Beyond 00:05:12.680 --> 00:05:15.950 align:start position:0% pragmatic about deploying this Beyond you<00:05:12.800> know<00:05:13.160> things<00:05:13.360> like<00:05:13.520> zalu<00:05:14.160> Defcon<00:05:14.680> Etc<00:05:15.680> um 00:05:15.950 --> 00:05:15.960 align:start position:0% you know things like zalu Defcon Etc um 00:05:15.960 --> 00:05:17.469 align:start position:0% you know things like zalu Defcon Etc um first<00:05:16.199> there's<00:05:16.400> a<00:05:16.560> lot<00:05:16.720> of<00:05:16.840> cryptographic 00:05:17.469 --> 00:05:17.479 align:start position:0% first there's a lot of cryptographic 00:05:17.479 --> 00:05:19.790 align:start position:0% first there's a lot of cryptographic data<00:05:17.840> yet<00:05:17.960> it's<00:05:18.240> very<00:05:18.639> heterogeneous<00:05:19.639> um 00:05:19.790 --> 00:05:19.800 align:start position:0% data yet it's very heterogeneous um 00:05:19.800 --> 00:05:20.950 align:start position:0% data yet it's very heterogeneous um stuff<00:05:20.000> that<00:05:20.120> comes<00:05:20.319> out<00:05:20.440> of<00:05:20.560> trusted 00:05:20.950 --> 00:05:20.960 align:start position:0% stuff that comes out of trusted 00:05:20.960 --> 00:05:23.230 align:start position:0% stuff that comes out of trusted execution<00:05:21.400> environment<00:05:21.919> blockchains<00:05:22.520> email 00:05:23.230 --> 00:05:23.240 align:start position:0% execution environment blockchains email 00:05:23.240 --> 00:05:24.950 align:start position:0% execution environment blockchains email transport<00:05:23.680> layer<00:05:23.960> Security<00:05:24.400> National<00:05:24.720> ID 00:05:24.950 --> 00:05:24.960 align:start position:0% transport layer Security National ID 00:05:24.960 --> 00:05:27.070 align:start position:0% transport layer Security National ID systems<00:05:25.400> Etc<00:05:25.960> all<00:05:26.080> of<00:05:26.199> this<00:05:26.280> is<00:05:26.440> cryptographic 00:05:27.070 --> 00:05:27.080 align:start position:0% systems Etc all of this is cryptographic 00:05:27.080 --> 00:05:28.270 align:start position:0% systems Etc all of this is cryptographic but<00:05:27.160> it<00:05:27.240> follows<00:05:27.560> different<00:05:27.759> schemas 00:05:28.270 --> 00:05:28.280 align:start position:0% but it follows different schemas 00:05:28.280 --> 00:05:30.830 align:start position:0% but it follows different schemas different<00:05:28.479> signature<00:05:28.840> schemes<00:05:29.199> Etc<00:05:30.120> um<00:05:30.520> basic 00:05:30.830 --> 00:05:30.840 align:start position:0% different signature schemes Etc um basic 00:05:30.840 --> 00:05:32.710 align:start position:0% different signature schemes Etc um basic use<00:05:31.160> cases<00:05:31.479> often<00:05:31.759> require<00:05:32.120> more<00:05:32.319> than<00:05:32.520> two 00:05:32.710 --> 00:05:32.720 align:start position:0% use cases often require more than two 00:05:32.720 --> 00:05:34.029 align:start position:0% use cases often require more than two rounds<00:05:32.960> of<00:05:33.080> transformation<00:05:33.759> like<00:05:33.840> you<00:05:33.919> want 00:05:34.029 --> 00:05:34.039 align:start position:0% rounds of transformation like you want 00:05:34.039 --> 00:05:35.469 align:start position:0% rounds of transformation like you want to<00:05:34.160> transform<00:05:34.479> your<00:05:34.560> data<00:05:34.759> multiple<00:05:35.160> time 00:05:35.469 --> 00:05:35.479 align:start position:0% to transform your data multiple time 00:05:35.479 --> 00:05:37.309 align:start position:0% to transform your data multiple time across<00:05:35.759> multiple<00:05:36.160> people<00:05:36.759> and<00:05:36.840> we<00:05:37.000> think<00:05:37.160> that 00:05:37.309 --> 00:05:37.319 align:start position:0% across multiple people and we think that 00:05:37.319 --> 00:05:38.790 align:start position:0% across multiple people and we think that there's<00:05:37.479> a<00:05:37.680> whole<00:05:37.840> world<00:05:38.080> that<00:05:38.199> might<00:05:38.360> open<00:05:38.560> up 00:05:38.790 --> 00:05:38.800 align:start position:0% there's a whole world that might open up 00:05:38.800 --> 00:05:40.430 align:start position:0% there's a whole world that might open up if<00:05:39.120> it's<00:05:39.319> actually<00:05:39.600> possible<00:05:39.960> to<00:05:40.080> go<00:05:40.280> more 00:05:40.430 --> 00:05:40.440 align:start position:0% if it's actually possible to go more 00:05:40.440 --> 00:05:41.830 align:start position:0% if it's actually possible to go more than<00:05:40.560> two<00:05:40.759> rounds<00:05:41.240> if<00:05:41.319> you<00:05:41.440> think<00:05:41.600> about<00:05:41.759> the 00:05:41.830 --> 00:05:41.840 align:start position:0% than two rounds if you think about the 00:05:41.840 --> 00:05:43.710 align:start position:0% than two rounds if you think about the internet<00:05:42.160> today<00:05:42.520> we<00:05:42.800> we<00:05:42.960> never<00:05:43.240> have<00:05:43.479> like 00:05:43.710 --> 00:05:43.720 align:start position:0% internet today we we never have like 00:05:43.720 --> 00:05:45.150 align:start position:0% internet today we we never have like platforms<00:05:44.160> that<00:05:44.280> go<00:05:44.440> more<00:05:44.560> than<00:05:44.680> two<00:05:44.840> levels 00:05:45.150 --> 00:05:45.160 align:start position:0% platforms that go more than two levels 00:05:45.160 --> 00:05:46.550 align:start position:0% platforms that go more than two levels deep<00:05:45.600> you<00:05:45.720> know<00:05:45.840> it's<00:05:45.960> like<00:05:46.039> we're<00:05:46.199> building 00:05:46.550 --> 00:05:46.560 align:start position:0% deep you know it's like we're building 00:05:46.560 --> 00:05:48.189 align:start position:0% deep you know it's like we're building on<00:05:46.759> on<00:05:46.880> top<00:05:47.039> of<00:05:47.120> mud<00:05:47.400> huts<00:05:47.680> and<00:05:47.759> we<00:05:47.880> dream<00:05:48.080> of 00:05:48.189 --> 00:05:48.199 align:start position:0% on on top of mud huts and we dream of 00:05:48.199 --> 00:05:49.670 align:start position:0% on on top of mud huts and we dream of skyscrapers<00:05:49.039> we<00:05:49.120> don't<00:05:49.280> really<00:05:49.400> know<00:05:49.520> what's 00:05:49.670 --> 00:05:49.680 align:start position:0% skyscrapers we don't really know what's 00:05:49.680 --> 00:05:51.070 align:start position:0% skyscrapers we don't really know what's going<00:05:49.800> to<00:05:49.919> happen<00:05:50.120> if<00:05:50.240> we<00:05:50.360> can<00:05:50.479> go<00:05:50.600> deeper<00:05:50.880> than 00:05:51.070 --> 00:05:51.080 align:start position:0% going to happen if we can go deeper than 00:05:51.080 --> 00:05:53.749 align:start position:0% going to happen if we can go deeper than that<00:05:51.840> um<00:05:52.319> there<00:05:52.440> is<00:05:52.600> a<00:05:52.759> lot<00:05:52.880> of<00:05:53.039> work<00:05:53.199> on<00:05:53.360> domain 00:05:53.749 --> 00:05:53.759 align:start position:0% that um there is a lot of work on domain 00:05:53.759 --> 00:05:55.749 align:start position:0% that um there is a lot of work on domain specific<00:05:54.199> system<00:05:54.880> uh<00:05:55.000> from<00:05:55.120> the<00:05:55.240> cryptography 00:05:55.749 --> 00:05:55.759 align:start position:0% specific system uh from the cryptography 00:05:55.759 --> 00:05:57.110 align:start position:0% specific system uh from the cryptography perspective<00:05:56.160> but<00:05:56.280> yet<00:05:56.400> there<00:05:56.520> is<00:05:56.680> absolutely 00:05:57.110 --> 00:05:57.120 align:start position:0% perspective but yet there is absolutely 00:05:57.120 --> 00:05:58.830 align:start position:0% perspective but yet there is absolutely no<00:05:57.280> interoperability<00:05:58.080> over<00:05:58.240> the<00:05:58.360> last<00:05:58.520> 18 00:05:58.830 --> 00:05:58.840 align:start position:0% no interoperability over the last 18 00:05:58.840 --> 00:06:01.150 align:start position:0% no interoperability over the last 18 months<00:05:59.319> none<00:05:59.720> of<00:05:59.880> the<00:06:00.080> ZK<00:06:00.479> ID<00:06:00.800> systems 00:06:01.150 --> 00:06:01.160 align:start position:0% months none of the ZK ID systems 00:06:01.160 --> 00:06:02.870 align:start position:0% months none of the ZK ID systems actually<00:06:01.360> work<00:06:01.600> with<00:06:01.759> each<00:06:01.880> other<00:06:02.400> you<00:06:02.520> know 00:06:02.870 --> 00:06:02.880 align:start position:0% actually work with each other you know 00:06:02.880 --> 00:06:05.870 align:start position:0% actually work with each other you know so<00:06:03.039> it's<00:06:03.199> pretty<00:06:03.440> interesting<00:06:03.919> like<00:06:04.199> why<00:06:05.000> and 00:06:05.870 --> 00:06:05.880 align:start position:0% so it's pretty interesting like why and 00:06:05.880 --> 00:06:07.430 align:start position:0% so it's pretty interesting like why and from<00:06:06.039> the<00:06:06.199> programable<00:06:06.919> cryptography 00:06:07.430 --> 00:06:07.440 align:start position:0% from the programable cryptography 00:06:07.440 --> 00:06:09.749 align:start position:0% from the programable cryptography perspective<00:06:08.120> the<00:06:08.280> unlock<00:06:08.759> of<00:06:08.919> zero<00:06:09.199> n<00:06:09.520> proof 00:06:09.749 --> 00:06:09.759 align:start position:0% perspective the unlock of zero n proof 00:06:09.759 --> 00:06:12.070 align:start position:0% perspective the unlock of zero n proof is<00:06:10.080> trustless<00:06:10.680> refactoring<00:06:11.240> and<00:06:11.479> import 00:06:12.070 --> 00:06:12.080 align:start position:0% is trustless refactoring and import 00:06:12.080 --> 00:06:13.270 align:start position:0% is trustless refactoring and import right<00:06:12.240> that's<00:06:12.520> that's<00:06:12.680> the<00:06:12.840> right<00:06:13.000> way<00:06:13.120> to 00:06:13.270 --> 00:06:13.280 align:start position:0% right that's that's the right way to 00:06:13.280 --> 00:06:15.070 align:start position:0% right that's that's the right way to think<00:06:13.479> about<00:06:13.639> it<00:06:13.880> not<00:06:14.120> as<00:06:14.319> like<00:06:14.440> a<00:06:14.560> way<00:06:14.680> to<00:06:14.840> hide 00:06:15.070 --> 00:06:15.080 align:start position:0% think about it not as like a way to hide 00:06:15.080 --> 00:06:17.990 align:start position:0% think about it not as like a way to hide data<00:06:15.319> in<00:06:15.400> my<00:06:15.599> opinion<00:06:16.599> um<00:06:17.080> and<00:06:17.400> you<00:06:17.560> can<00:06:17.720> use<00:06:17.880> it 00:06:17.990 --> 00:06:18.000 align:start position:0% data in my opinion um and you can use it 00:06:18.000 --> 00:06:19.749 align:start position:0% data in my opinion um and you can use it to<00:06:18.160> now<00:06:18.319> create<00:06:18.520> a<00:06:18.680> universal<00:06:19.280> system<00:06:19.560> for 00:06:19.749 --> 00:06:19.759 align:start position:0% to now create a universal system for 00:06:19.759 --> 00:06:21.670 align:start position:0% to now create a universal system for making<00:06:20.039> Claim<00:06:20.360> about<00:06:20.560> the<00:06:20.639> world's<00:06:20.960> data<00:06:21.560> and 00:06:21.670 --> 00:06:21.680 align:start position:0% making Claim about the world's data and 00:06:21.680 --> 00:06:23.790 align:start position:0% making Claim about the world's data and the<00:06:21.800> unlock<00:06:22.199> of<00:06:22.759> um<00:06:22.960> fully<00:06:23.240> homomorphic 00:06:23.790 --> 00:06:23.800 align:start position:0% the unlock of um fully homomorphic 00:06:23.800 --> 00:06:25.710 align:start position:0% the unlock of um fully homomorphic encryption<00:06:24.199> or<00:06:24.400> coar<00:06:24.919> NPCs<00:06:25.319> now<00:06:25.479> you<00:06:25.560> can 00:06:25.710 --> 00:06:25.720 align:start position:0% encryption or coar NPCs now you can 00:06:25.720 --> 00:06:27.710 align:start position:0% encryption or coar NPCs now you can combine<00:06:26.080> that<00:06:26.240> data<00:06:26.479> confidentially<00:06:27.360> so<00:06:27.560> we 00:06:27.710 --> 00:06:27.720 align:start position:0% combine that data confidentially so we 00:06:27.720 --> 00:06:29.309 align:start position:0% combine that data confidentially so we want<00:06:27.880> to<00:06:28.039> put<00:06:28.280> together<00:06:28.479> a<00:06:28.639> system<00:06:29.000> that<00:06:29.120> makes 00:06:29.309 --> 00:06:29.319 align:start position:0% want to put together a system that makes 00:06:29.319 --> 00:06:31.550 align:start position:0% want to put together a system that makes you<00:06:29.680> of<00:06:29.800> these<00:06:29.960> Primitives<00:06:30.680> and<00:06:30.840> is<00:06:31.240> like 00:06:31.550 --> 00:06:31.560 align:start position:0% you of these Primitives and is like 00:06:31.560 --> 00:06:34.150 align:start position:0% you of these Primitives and is like situated<00:06:32.000> in<00:06:32.120> a<00:06:32.319> world<00:06:33.160> like<00:06:33.400> this<00:06:33.880> without 00:06:34.150 --> 00:06:34.160 align:start position:0% situated in a world like this without 00:06:34.160 --> 00:06:35.950 align:start position:0% situated in a world like this without being<00:06:34.360> wishful<00:06:34.800> thinking<00:06:35.120> about<00:06:35.400> like<00:06:35.639> oh<00:06:35.800> no 00:06:35.950 --> 00:06:35.960 align:start position:0% being wishful thinking about like oh no 00:06:35.960 --> 00:06:37.550 align:start position:0% being wishful thinking about like oh no the<00:06:36.080> whole<00:06:36.280> world<00:06:36.520> is<00:06:36.680> going<00:06:36.759> to<00:06:36.960> like<00:06:37.120> issue 00:06:37.550 --> 00:06:37.560 align:start position:0% the whole world is going to like issue 00:06:37.560 --> 00:06:39.790 align:start position:0% the whole world is going to like issue pods<00:06:37.840> with<00:06:38.000> EDSA<00:06:38.639> JJ<00:06:39.080> signature<00:06:39.520> whatever 00:06:39.790 --> 00:06:39.800 align:start position:0% pods with EDSA JJ signature whatever 00:06:39.800 --> 00:06:42.629 align:start position:0% pods with EDSA JJ signature whatever like<00:06:39.960> that's<00:06:40.080> not<00:06:40.199> going<00:06:40.280> to<00:06:40.400> happen<00:06:41.319> so<00:06:42.319> um 00:06:42.629 --> 00:06:42.639 align:start position:0% like that's not going to happen so um 00:06:42.639 --> 00:06:44.230 align:start position:0% like that's not going to happen so um what<00:06:42.759> we<00:06:42.880> want<00:06:43.039> is<00:06:43.199> we<00:06:43.319> want<00:06:43.520> verifiable<00:06:44.080> and 00:06:44.230 --> 00:06:44.240 align:start position:0% what we want is we want verifiable and 00:06:44.240 --> 00:06:45.870 align:start position:0% what we want is we want verifiable and interoperable<00:06:44.840> computational<00:06:45.319> graph<00:06:45.680> so<00:06:45.800> we 00:06:45.870 --> 00:06:45.880 align:start position:0% interoperable computational graph so we 00:06:45.880 --> 00:06:47.790 align:start position:0% interoperable computational graph so we want<00:06:46.000> to<00:06:46.160> import<00:06:46.599> data<00:06:47.160> as<00:06:47.280> think<00:06:47.440> it's<00:06:47.560> about 00:06:47.790 --> 00:06:47.800 align:start position:0% want to import data as think it's about 00:06:47.800 --> 00:06:50.390 align:start position:0% want to import data as think it's about emails<00:06:48.560> API<00:06:49.000> calls<00:06:49.720> this<00:06:49.840> is<00:06:49.960> like<00:06:50.080> a<00:06:50.160> mobile 00:06:50.390 --> 00:06:50.400 align:start position:0% emails API calls this is like a mobile 00:06:50.400 --> 00:06:51.550 align:start position:0% emails API calls this is like a mobile driver<00:06:50.720> license<00:06:51.039> from<00:06:51.160> the<00:06:51.280> state<00:06:51.440> of 00:06:51.550 --> 00:06:51.560 align:start position:0% driver license from the state of 00:06:51.560 --> 00:06:53.150 align:start position:0% driver license from the state of California<00:06:52.280> we<00:06:52.360> want<00:06:52.479> to<00:06:52.560> turn<00:06:52.759> that<00:06:52.880> into 00:06:53.150 --> 00:06:53.160 align:start position:0% California we want to turn that into 00:06:53.160 --> 00:06:56.070 align:start position:0% California we want to turn that into pods<00:06:53.880> we<00:06:53.960> want<00:06:54.080> to<00:06:54.319> compute<00:06:55.199> an<00:06:55.440> arbitrary 00:06:56.070 --> 00:06:56.080 align:start position:0% pods we want to compute an arbitrary 00:06:56.080 --> 00:06:57.550 align:start position:0% pods we want to compute an arbitrary depth<00:06:56.440> with<00:06:56.560> an<00:06:56.720> arbitrary<00:06:57.120> number<00:06:57.360> of 00:06:57.550 --> 00:06:57.560 align:start position:0% depth with an arbitrary number of 00:06:57.560 --> 00:06:59.869 align:start position:0% depth with an arbitrary number of participants<00:06:58.160> on<00:06:58.400> this<00:06:58.599> data<00:06:59.120> and<00:06:59.319> find<00:06:59.759> want 00:06:59.869 --> 00:06:59.879 align:start position:0% participants on this data and find want 00:06:59.879 --> 00:07:02.309 align:start position:0% participants on this data and find want to<00:07:00.080> export<00:07:00.479> a<00:07:00.680> view<00:07:01.120> of<00:07:01.319> this<00:07:01.479> data<00:07:02.039> to<00:07:02.199> a 00:07:02.309 --> 00:07:02.319 align:start position:0% to export a view of this data to a 00:07:02.319 --> 00:07:04.430 align:start position:0% to export a view of this data to a verifier<00:07:02.879> that<00:07:03.000> can<00:07:03.199> check<00:07:03.479> the<00:07:03.639> Integrity<00:07:04.319> of 00:07:04.430 --> 00:07:04.440 align:start position:0% verifier that can check the Integrity of 00:07:04.440 --> 00:07:05.790 align:start position:0% verifier that can check the Integrity of all<00:07:04.599> the<00:07:04.720> computational<00:07:05.319> graph<00:07:05.599> and<00:07:05.720> the 00:07:05.790 --> 00:07:05.800 align:start position:0% all the computational graph and the 00:07:05.800 --> 00:07:07.990 align:start position:0% all the computational graph and the Integrity<00:07:06.199> of<00:07:06.360> all<00:07:06.520> the<00:07:06.639> Imports<00:07:07.479> VI<00:07:07.800> like<00:07:07.879> a 00:07:07.990 --> 00:07:08.000 align:start position:0% Integrity of all the Imports VI like a 00:07:08.000 --> 00:07:09.749 align:start position:0% Integrity of all the Imports VI like a single<00:07:08.319> succinct<00:07:08.840> proof<00:07:09.280> right<00:07:09.440> that's<00:07:09.639> where 00:07:09.749 --> 00:07:09.759 align:start position:0% single succinct proof right that's where 00:07:09.759 --> 00:07:12.110 align:start position:0% single succinct proof right that's where we<00:07:09.879> want<00:07:10.000> to<00:07:10.160> get<00:07:10.280> to<00:07:11.160> and<00:07:11.560> so<00:07:11.840> that<00:07:11.960> that's 00:07:12.110 --> 00:07:12.120 align:start position:0% we want to get to and so that that's 00:07:12.120 --> 00:07:13.510 align:start position:0% we want to get to and so that that's putting<00:07:12.360> it<00:07:12.560> together<00:07:12.840> again<00:07:13.039> the<00:07:13.160> goal<00:07:13.319> for<00:07:13.400> a 00:07:13.510 --> 00:07:13.520 align:start position:0% putting it together again the goal for a 00:07:13.520 --> 00:07:14.629 align:start position:0% putting it together again the goal for a second<00:07:13.759> version<00:07:13.960> of<00:07:14.039> the<00:07:14.199> stack<00:07:14.400> is<00:07:14.479> we<00:07:14.560> want 00:07:14.629 --> 00:07:14.639 align:start position:0% second version of the stack is we want 00:07:14.639 --> 00:07:16.110 align:start position:0% second version of the stack is we want to<00:07:14.680> be<00:07:14.759> able<00:07:14.879> to<00:07:14.960> introduce<00:07:15.319> anything 00:07:16.110 --> 00:07:16.120 align:start position:0% to be able to introduce anything 00:07:16.120 --> 00:07:18.189 align:start position:0% to be able to introduce anything trustless<00:07:16.639> Le<00:07:17.080> and<00:07:17.199> the<00:07:17.319> reason<00:07:17.599> trustless<00:07:18.039> is 00:07:18.189 --> 00:07:18.199 align:start position:0% trustless Le and the reason trustless is 00:07:18.199 --> 00:07:20.550 align:start position:0% trustless Le and the reason trustless is important<00:07:18.639> it's<00:07:18.879> not<00:07:19.199> because<00:07:19.800> we<00:07:20.000> think<00:07:20.280> that 00:07:20.550 --> 00:07:20.560 align:start position:0% important it's not because we think that 00:07:20.560 --> 00:07:22.830 align:start position:0% important it's not because we think that oh<00:07:20.800> like<00:07:21.639> you're<00:07:21.759> going<00:07:21.879> to<00:07:22.000> be<00:07:22.160> censored<00:07:22.720> when 00:07:22.830 --> 00:07:22.840 align:start position:0% oh like you're going to be censored when 00:07:22.840 --> 00:07:24.430 align:start position:0% oh like you're going to be censored when you<00:07:23.000> like<00:07:23.199> import<00:07:23.560> your<00:07:23.720> like<00:07:23.840> RuneScape 00:07:24.430 --> 00:07:24.440 align:start position:0% you like import your like RuneScape 00:07:24.440 --> 00:07:25.629 align:start position:0% you like import your like RuneScape character<00:07:24.759> or<00:07:24.919> something<00:07:25.199> like<00:07:25.360> that<00:07:25.520> it's 00:07:25.629 --> 00:07:25.639 align:start position:0% character or something like that it's 00:07:25.639 --> 00:07:26.749 align:start position:0% character or something like that it's more<00:07:25.800> like<00:07:25.919> if<00:07:26.000> it's<00:07:26.160> trustless<00:07:26.639> it's 00:07:26.749 --> 00:07:26.759 align:start position:0% more like if it's trustless it's 00:07:26.759 --> 00:07:28.670 align:start position:0% more like if it's trustless it's scalable<00:07:27.360> because<00:07:27.560> any<00:07:27.720> computer<00:07:28.080> can<00:07:28.199> do<00:07:28.360> it 00:07:28.670 --> 00:07:28.680 align:start position:0% scalable because any computer can do it 00:07:28.680 --> 00:07:29.830 align:start position:0% scalable because any computer can do it as<00:07:28.800> opposed<00:07:29.039> to<00:07:29.160> having<00:07:29.360> like<00:07:29.639> some 00:07:29.830 --> 00:07:29.840 align:start position:0% as opposed to having like some 00:07:29.840 --> 00:07:31.629 align:start position:0% as opposed to having like some bottleneck<00:07:30.280> in<00:07:30.360> the<00:07:30.479> system<00:07:30.759> somewhere<00:07:31.479> we 00:07:31.629 --> 00:07:31.639 align:start position:0% bottleneck in the system somewhere we 00:07:31.639 --> 00:07:33.550 align:start position:0% bottleneck in the system somewhere we want<00:07:31.840> deep<00:07:32.039> computational<00:07:32.599> graphs<00:07:33.039> because 00:07:33.550 --> 00:07:33.560 align:start position:0% want deep computational graphs because 00:07:33.560 --> 00:07:35.150 align:start position:0% want deep computational graphs because actually<00:07:33.800> today<00:07:34.039> we've<00:07:34.280> never<00:07:34.560> really<00:07:34.759> seen 00:07:35.150 --> 00:07:35.160 align:start position:0% actually today we've never really seen 00:07:35.160 --> 00:07:37.189 align:start position:0% actually today we've never really seen what<00:07:35.319> would<00:07:35.560> happen<00:07:36.240> if<00:07:36.440> many<00:07:36.759> parties<00:07:37.080> were 00:07:37.189 --> 00:07:37.199 align:start position:0% what would happen if many parties were 00:07:37.199 --> 00:07:38.629 align:start position:0% what would happen if many parties were to<00:07:37.319> be<00:07:37.400> able<00:07:37.599> to<00:07:37.720> operate<00:07:38.000> on<00:07:38.080> a<00:07:38.199> piece<00:07:38.360> of<00:07:38.479> data 00:07:38.629 --> 00:07:38.639 align:start position:0% to be able to operate on a piece of data 00:07:38.639 --> 00:07:40.270 align:start position:0% to be able to operate on a piece of data and<00:07:38.759> kind<00:07:38.879> of<00:07:39.000> like<00:07:39.160> pass<00:07:39.319> it<00:07:39.479> along<00:07:40.120> right 00:07:40.270 --> 00:07:40.280 align:start position:0% and kind of like pass it along right 00:07:40.280 --> 00:07:41.430 align:start position:0% and kind of like pass it along right most<00:07:40.440> of<00:07:40.560> the<00:07:40.639> time<00:07:40.759> you<00:07:40.840> have<00:07:40.960> data<00:07:41.160> that<00:07:41.280> gets 00:07:41.430 --> 00:07:41.440 align:start position:0% most of the time you have data that gets 00:07:41.440 --> 00:07:43.749 align:start position:0% most of the time you have data that gets ingested<00:07:41.840> by<00:07:42.000> one<00:07:42.560> big<00:07:42.800> group<00:07:43.039> of<00:07:43.199> people<00:07:43.639> and 00:07:43.749 --> 00:07:43.759 align:start position:0% ingested by one big group of people and 00:07:43.759 --> 00:07:46.390 align:start position:0% ingested by one big group of people and then<00:07:44.080> it<00:07:44.199> gets<00:07:44.400> consumed<00:07:44.800> and<00:07:44.919> that's<00:07:45.080> it<00:07:45.800> um 00:07:46.390 --> 00:07:46.400 align:start position:0% then it gets consumed and that's it um 00:07:46.400 --> 00:07:47.670 align:start position:0% then it gets consumed and that's it um and<00:07:46.520> we<00:07:46.639> also<00:07:46.800> want<00:07:46.879> to<00:07:47.000> do<00:07:47.120> it<00:07:47.400> between 00:07:47.670 --> 00:07:47.680 align:start position:0% and we also want to do it between 00:07:47.680 --> 00:07:48.830 align:start position:0% and we also want to do it between multiple<00:07:48.039> people<00:07:48.280> while<00:07:48.440> maintaining 00:07:48.830 --> 00:07:48.840 align:start position:0% multiple people while maintaining 00:07:48.840 --> 00:07:50.550 align:start position:0% multiple people while maintaining confidentiality<00:07:49.599> because<00:07:49.919> we<00:07:50.039> think<00:07:50.280> this<00:07:50.360> is 00:07:50.550 --> 00:07:50.560 align:start position:0% confidentiality because we think this is 00:07:50.560 --> 00:07:52.469 align:start position:0% confidentiality because we think this is how<00:07:50.680> you<00:07:50.800> can<00:07:50.960> tap<00:07:51.199> into<00:07:51.800> much<00:07:52.080> bigger 00:07:52.469 --> 00:07:52.479 align:start position:0% how you can tap into much bigger 00:07:52.479 --> 00:07:54.950 align:start position:0% how you can tap into much bigger economic<00:07:53.280> output<00:07:54.280> okay<00:07:54.400> so<00:07:54.560> the<00:07:54.720> first 00:07:54.950 --> 00:07:54.960 align:start position:0% economic output okay so the first 00:07:54.960 --> 00:07:56.550 align:start position:0% economic output okay so the first challenge<00:07:55.360> we<00:07:55.520> had<00:07:55.759> when<00:07:55.879> we<00:07:56.000> faced<00:07:56.319> this 00:07:56.550 --> 00:07:56.560 align:start position:0% challenge we had when we faced this 00:07:56.560 --> 00:07:57.749 align:start position:0% challenge we had when we faced this which<00:07:56.680> I<00:07:56.759> think<00:07:57.039> not<00:07:57.240> many<00:07:57.400> people<00:07:57.639> have 00:07:57.749 --> 00:07:57.759 align:start position:0% which I think not many people have 00:07:57.759 --> 00:07:58.749 align:start position:0% which I think not many people have thought<00:07:57.919> about<00:07:58.120> this<00:07:58.240> is<00:07:58.319> probably<00:07:58.560> the<00:07:58.599> most 00:07:58.749 --> 00:07:58.759 align:start position:0% thought about this is probably the most 00:07:58.759 --> 00:07:59.950 align:start position:0% thought about this is probably the most interesting<00:07:59.080> challenge<00:07:59.520> is<00:07:59.639> program 00:07:59.950 --> 00:07:59.960 align:start position:0% interesting challenge is program 00:07:59.960 --> 00:08:02.430 align:start position:0% interesting challenge is program composability<00:08:00.680> so<00:08:01.680> imagine<00:08:01.960> you<00:08:02.080> have<00:08:02.159> a<00:08:02.280> list 00:08:02.430 --> 00:08:02.440 align:start position:0% composability so imagine you have a list 00:08:02.440 --> 00:08:04.990 align:start position:0% composability so imagine you have a list of<00:08:02.560> friends<00:08:03.560> um<00:08:04.199> it's<00:08:04.360> probably<00:08:04.639> like<00:08:04.720> a<00:08:04.840> list 00:08:04.990 --> 00:08:05.000 align:start position:0% of friends um it's probably like a list 00:08:05.000 --> 00:08:06.390 align:start position:0% of friends um it's probably like a list of<00:08:05.159> PODS<00:08:05.440> that<00:08:05.560> if<00:08:05.639> you<00:08:05.759> receive<00:08:06.080> like<00:08:06.159> each<00:08:06.280> of 00:08:06.390 --> 00:08:06.400 align:start position:0% of PODS that if you receive like each of 00:08:06.400 --> 00:08:07.629 align:start position:0% of PODS that if you receive like each of your<00:08:06.520> friends<00:08:06.720> sign<00:08:07.000> something<00:08:07.479> saying 00:08:07.629 --> 00:08:07.639 align:start position:0% your friends sign something saying 00:08:07.639 --> 00:08:09.029 align:start position:0% your friends sign something saying they're<00:08:07.800> your<00:08:07.919> friend<00:08:08.319> you<00:08:08.400> can<00:08:08.560> put<00:08:08.720> in<00:08:08.840> a 00:08:09.029 --> 00:08:09.039 align:start position:0% they're your friend you can put in a 00:08:09.039 --> 00:08:10.710 align:start position:0% they're your friend you can put in a program<00:08:09.479> here<00:08:09.599> it's<00:08:09.759> some<00:08:10.000> Rust<00:08:10.319> but<00:08:10.479> anyone 00:08:10.710 --> 00:08:10.720 align:start position:0% program here it's some Rust but anyone 00:08:10.720 --> 00:08:12.430 align:start position:0% program here it's some Rust but anyone can<00:08:10.879> read<00:08:11.120> this<00:08:11.520> which<00:08:11.720> counts<00:08:12.000> the<00:08:12.080> amount<00:08:12.280> of 00:08:12.430 --> 00:08:12.440 align:start position:0% can read this which counts the amount of 00:08:12.440 --> 00:08:14.350 align:start position:0% can read this which counts the amount of best<00:08:12.680> friend<00:08:12.919> you<00:08:13.080> have<00:08:13.560> best<00:08:13.759> friend<00:08:14.000> is<00:08:14.159> just 00:08:14.350 --> 00:08:14.360 align:start position:0% best friend you have best friend is just 00:08:14.360 --> 00:08:16.589 align:start position:0% best friend you have best friend is just like<00:08:14.560> a<00:08:14.800> a<00:08:15.000> property<00:08:15.360> of<00:08:15.599> friend<00:08:16.280> and<00:08:16.360> you<00:08:16.479> get 00:08:16.589 --> 00:08:16.599 align:start position:0% like a a property of friend and you get 00:08:16.599 --> 00:08:19.350 align:start position:0% like a a property of friend and you get out<00:08:17.120> 13<00:08:18.120> now<00:08:18.280> you<00:08:18.440> take<00:08:18.720> this<00:08:18.919> and<00:08:19.039> you<00:08:19.159> put 00:08:19.350 --> 00:08:19.360 align:start position:0% out 13 now you take this and you put 00:08:19.360 --> 00:08:21.189 align:start position:0% out 13 now you take this and you put into<00:08:19.599> another<00:08:19.879> function<00:08:20.319> that<00:08:20.479> says<00:08:20.840> hey<00:08:21.080> do 00:08:21.189 --> 00:08:21.199 align:start position:0% into another function that says hey do 00:08:21.199 --> 00:08:22.670 align:start position:0% into another function that says hey do you<00:08:21.280> have<00:08:21.400> a<00:08:21.520> great<00:08:21.720> friend<00:08:21.960> groups<00:08:22.520> which 00:08:22.670 --> 00:08:22.680 align:start position:0% you have a great friend groups which 00:08:22.680 --> 00:08:23.909 align:start position:0% you have a great friend groups which counts<00:08:22.960> how<00:08:23.039> many<00:08:23.240> best<00:08:23.479> friend<00:08:23.639> you<00:08:23.759> have 00:08:23.909 --> 00:08:23.919 align:start position:0% counts how many best friend you have 00:08:23.919 --> 00:08:25.350 align:start position:0% counts how many best friend you have here<00:08:24.120> just<00:08:24.319> can't<00:08:24.560> say<00:08:24.720> is<00:08:24.840> it<00:08:25.000> bigger<00:08:25.240> or 00:08:25.350 --> 00:08:25.360 align:start position:0% here just can't say is it bigger or 00:08:25.360 --> 00:08:27.270 align:start position:0% here just can't say is it bigger or equal<00:08:25.639> than<00:08:25.800> three<00:08:26.199> and<00:08:26.319> you<00:08:26.440> get<00:08:26.520> a<00:08:26.599> bullan 00:08:27.270 --> 00:08:27.280 align:start position:0% equal than three and you get a bullan 00:08:27.280 --> 00:08:30.430 align:start position:0% equal than three and you get a bullan true<00:08:27.479> or<00:08:27.599> false<00:08:28.280> okay<00:08:28.520> seems<00:08:28.840> simple<00:08:29.159> enough 00:08:30.430 --> 00:08:30.440 align:start position:0% true or false okay seems simple enough 00:08:30.440 --> 00:08:31.869 align:start position:0% true or false okay seems simple enough here's<00:08:30.639> how<00:08:30.800> it<00:08:30.879> looks<00:08:31.080> like<00:08:31.199> more<00:08:31.400> abstractly 00:08:31.869 --> 00:08:31.879 align:start position:0% here's how it looks like more abstractly 00:08:31.879 --> 00:08:33.190 align:start position:0% here's how it looks like more abstractly you<00:08:31.960> have<00:08:32.080> some<00:08:32.200> parts<00:08:32.479> that<00:08:32.560> go<00:08:32.680> into<00:08:32.880> program 00:08:33.190 --> 00:08:33.200 align:start position:0% you have some parts that go into program 00:08:33.200 --> 00:08:35.469 align:start position:0% you have some parts that go into program a<00:08:33.640> gets<00:08:33.800> a<00:08:33.959> part<00:08:34.159> out<00:08:34.399> go<00:08:34.560> into<00:08:34.760> program<00:08:35.039> B<00:08:35.360> get 00:08:35.469 --> 00:08:35.479 align:start position:0% a gets a part out go into program B get 00:08:35.479 --> 00:08:37.509 align:start position:0% a gets a part out go into program B get a<00:08:35.599> part<00:08:35.839> out<00:08:36.279> okay<00:08:36.399> so<00:08:36.640> assuming<00:08:37.039> we<00:08:37.159> can<00:08:37.279> do 00:08:37.509 --> 00:08:37.519 align:start position:0% a part out okay so assuming we can do 00:08:37.519 --> 00:08:39.550 align:start position:0% a part out okay so assuming we can do this<00:08:37.880> cryptographically<00:08:38.880> what<00:08:39.120> problem 00:08:39.550 --> 00:08:39.560 align:start position:0% this cryptographically what problem 00:08:39.560 --> 00:08:41.990 align:start position:0% this cryptographically what problem remains<00:08:40.000> well<00:08:40.719> the<00:08:40.839> main<00:08:41.120> issue<00:08:41.519> is<00:08:41.760> if<00:08:41.839> you 00:08:41.990 --> 00:08:42.000 align:start position:0% remains well the main issue is if you 00:08:42.000 --> 00:08:44.670 align:start position:0% remains well the main issue is if you have<00:08:42.120> a<00:08:42.320> program<00:08:43.080> that<00:08:43.919> operates<00:08:44.320> over<00:08:44.560> the 00:08:44.670 --> 00:08:44.680 align:start position:0% have a program that operates over the 00:08:44.680 --> 00:08:46.750 align:start position:0% have a program that operates over the output<00:08:45.000> of<00:08:45.080> a<00:08:45.200> different<00:08:45.519> program<00:08:46.200> you<00:08:46.360> need 00:08:46.750 --> 00:08:46.760 align:start position:0% output of a different program you need 00:08:46.760 --> 00:08:49.590 align:start position:0% output of a different program you need program<00:08:47.200> B<00:08:47.440> to<00:08:47.880> understand<00:08:48.120> program<00:08:48.480> a<00:08:49.080> right 00:08:49.590 --> 00:08:49.600 align:start position:0% program B to understand program a right 00:08:49.600 --> 00:08:51.550 align:start position:0% program B to understand program a right either<00:08:49.839> via<00:08:50.120> static<00:08:50.440> analysis<00:08:51.040> either<00:08:51.279> via 00:08:51.550 --> 00:08:51.560 align:start position:0% either via static analysis either via 00:08:51.560 --> 00:08:54.230 align:start position:0% either via static analysis either via vmer<00:08:52.000> proofs<00:08:52.360> but<00:08:52.839> program<00:08:53.360> B<00:08:53.640> needs<00:08:53.880> to<00:08:54.000> know 00:08:54.230 --> 00:08:54.240 align:start position:0% vmer proofs but program B needs to know 00:08:54.240 --> 00:08:56.550 align:start position:0% vmer proofs but program B needs to know what<00:08:54.399> program<00:08:54.680> a<00:08:54.959> does<00:08:55.560> so<00:08:55.760> unless<00:08:56.040> you<00:08:56.200> write 00:08:56.550 --> 00:08:56.560 align:start position:0% what program a does so unless you write 00:08:56.560 --> 00:08:58.470 align:start position:0% what program a does so unless you write program<00:08:56.880> B<00:08:57.120> after<00:08:57.360> having<00:08:57.720> written<00:08:58.040> program<00:08:58.320> a 00:08:58.470 --> 00:08:58.480 align:start position:0% program B after having written program a 00:08:58.480 --> 00:08:59.790 align:start position:0% program B after having written program a and<00:08:58.600> kind<00:08:58.720> of<00:08:58.800> like<00:08:58.959> hardcode<00:08:59.480> the<00:08:59.560> link 00:08:59.790 --> 00:08:59.800 align:start position:0% and kind of like hardcode the link 00:08:59.800 --> 00:09:01.110 align:start position:0% and kind of like hardcode the link between<00:09:00.120> them<00:09:00.320> it's<00:09:00.480> really<00:09:00.680> hard<00:09:00.839> for<00:09:00.959> a 00:09:01.110 --> 00:09:01.120 align:start position:0% between them it's really hard for a 00:09:01.120 --> 00:09:02.550 align:start position:0% between them it's really hard for a program<00:09:01.440> to<00:09:01.560> make<00:09:01.720> sense<00:09:01.920> of<00:09:02.079> the<00:09:02.160> output<00:09:02.440> of 00:09:02.550 --> 00:09:02.560 align:start position:0% program to make sense of the output of 00:09:02.560 --> 00:09:05.750 align:start position:0% program to make sense of the output of another<00:09:02.880> program<00:09:03.399> if<00:09:03.519> I<00:09:03.640> tell<00:09:03.839> you<00:09:04.399> 42<00:09:05.399> and<00:09:05.519> I 00:09:05.750 --> 00:09:05.760 align:start position:0% another program if I tell you 42 and I 00:09:05.760 --> 00:09:07.230 align:start position:0% another program if I tell you 42 and I tell<00:09:05.880> you<00:09:06.000> how<00:09:06.120> it<00:09:06.200> was<00:09:06.360> computed<00:09:06.959> it's<00:09:07.079> really 00:09:07.230 --> 00:09:07.240 align:start position:0% tell you how it was computed it's really 00:09:07.240 --> 00:09:08.509 align:start position:0% tell you how it was computed it's really hard<00:09:07.440> for<00:09:07.560> you<00:09:07.680> to<00:09:07.800> know<00:09:07.959> even<00:09:08.200> what<00:09:08.320> the 00:09:08.509 --> 00:09:08.519 align:start position:0% hard for you to know even what the 00:09:08.519 --> 00:09:10.670 align:start position:0% hard for you to know even what the significance<00:09:09.040> of<00:09:09.200> that<00:09:09.399> output<00:09:09.880> is<00:09:10.360> we<00:09:10.480> don't 00:09:10.670 --> 00:09:10.680 align:start position:0% significance of that output is we don't 00:09:10.680 --> 00:09:12.630 align:start position:0% significance of that output is we don't really<00:09:10.959> think<00:09:11.680> like<00:09:11.880> that<00:09:12.040> most<00:09:12.200> of<00:09:12.320> the<00:09:12.440> time 00:09:12.630 --> 00:09:12.640 align:start position:0% really think like that most of the time 00:09:12.640 --> 00:09:14.470 align:start position:0% really think like that most of the time like<00:09:12.760> when<00:09:12.920> people<00:09:13.120> say<00:09:13.320> oh<00:09:13.480> we'll<00:09:13.680> have<00:09:14.079> ZK 00:09:14.470 --> 00:09:14.480 align:start position:0% like when people say oh we'll have ZK 00:09:14.480 --> 00:09:16.350 align:start position:0% like when people say oh we'll have ZK VMS<00:09:14.800> and<00:09:15.000> we<00:09:15.079> can<00:09:15.160> solve<00:09:15.519> everything<00:09:15.880> the<00:09:16.040> main 00:09:16.350 --> 00:09:16.360 align:start position:0% VMS and we can solve everything the main 00:09:16.360 --> 00:09:18.190 align:start position:0% VMS and we can solve everything the main issue<00:09:16.760> is<00:09:16.920> that<00:09:17.200> yeah<00:09:17.440> good<00:09:17.600> luck<00:09:17.800> now<00:09:18.000> doing 00:09:18.190 --> 00:09:18.200 align:start position:0% issue is that yeah good luck now doing 00:09:18.200 --> 00:09:19.590 align:start position:0% issue is that yeah good luck now doing static<00:09:18.560> analysis<00:09:18.959> and<00:09:19.120> kind<00:09:19.240> of<00:09:19.320> like<00:09:19.440> trying 00:09:19.590 --> 00:09:19.600 align:start position:0% static analysis and kind of like trying 00:09:19.600 --> 00:09:21.550 align:start position:0% static analysis and kind of like trying to<00:09:19.680> make<00:09:19.839> sense<00:09:20.040> of<00:09:20.200> other<00:09:20.519> programs<00:09:21.240> and<00:09:21.440> at 00:09:21.550 --> 00:09:21.560 align:start position:0% to make sense of other programs and at 00:09:21.560 --> 00:09:22.670 align:start position:0% to make sense of other programs and at the<00:09:21.640> end<00:09:21.760> of<00:09:21.839> the<00:09:21.880> day<00:09:22.000> it<00:09:22.079> reduces<00:09:22.440> to<00:09:22.560> the 00:09:22.670 --> 00:09:22.680 align:start position:0% the end of the day it reduces to the 00:09:22.680 --> 00:09:25.350 align:start position:0% the end of the day it reduces to the holding<00:09:23.079> problem<00:09:23.760> so<00:09:24.680> what<00:09:24.800> we<00:09:24.920> did<00:09:25.079> is<00:09:25.200> we 00:09:25.350 --> 00:09:25.360 align:start position:0% holding problem so what we did is we 00:09:25.360 --> 00:09:27.190 align:start position:0% holding problem so what we did is we threw<00:09:25.600> away<00:09:25.760> the<00:09:25.880> CPU<00:09:26.279> model<00:09:26.600> and<00:09:26.680> we<00:09:26.800> went<00:09:26.920> to 00:09:27.190 --> 00:09:27.200 align:start position:0% threw away the CPU model and we went to 00:09:27.200 --> 00:09:29.829 align:start position:0% threw away the CPU model and we went to logic<00:09:28.200> um<00:09:28.600> and<00:09:28.720> we<00:09:28.839> threw<00:09:29.040> away<00:09:29.160> the<00:09:29.519> codes<00:09:29.720> and 00:09:29.829 --> 00:09:29.839 align:start position:0% logic um and we threw away the codes and 00:09:29.839 --> 00:09:31.990 align:start position:0% logic um and we threw away the codes and we<00:09:29.920> move<00:09:30.079> to<00:09:30.240> logical<00:09:30.600> operation<00:09:31.399> so<00:09:31.720> instead 00:09:31.990 --> 00:09:32.000 align:start position:0% we move to logical operation so instead 00:09:32.000 --> 00:09:34.069 align:start position:0% we move to logical operation so instead of<00:09:32.120> a<00:09:32.320> virtual<00:09:32.680> machine<00:09:33.000> built<00:09:33.320> on<00:09:33.560> risk<00:09:33.839> five 00:09:34.069 --> 00:09:34.079 align:start position:0% of a virtual machine built on risk five 00:09:34.079 --> 00:09:35.230 align:start position:0% of a virtual machine built on risk five or<00:09:34.160> something<00:09:34.399> like<00:09:34.480> that<00:09:34.560> we<00:09:34.680> build<00:09:34.839> a<00:09:34.959> logic 00:09:35.230 --> 00:09:35.240 align:start position:0% or something like that we build a logic 00:09:35.240 --> 00:09:37.470 align:start position:0% or something like that we build a logic virtual<00:09:35.560> machine<00:09:36.160> we<00:09:36.320> replaced<00:09:36.760> memory<00:09:37.040> slots 00:09:37.470 --> 00:09:37.480 align:start position:0% virtual machine we replaced memory slots 00:09:37.480 --> 00:09:39.790 align:start position:0% virtual machine we replaced memory slots with<00:09:37.680> logical<00:09:38.120> statements<00:09:39.000> so<00:09:39.320> statements 00:09:39.790 --> 00:09:39.800 align:start position:0% with logical statements so statements 00:09:39.800 --> 00:09:41.350 align:start position:0% with logical statements so statements like<00:09:39.959> a<00:09:40.120> is<00:09:40.240> greater<00:09:40.480> than<00:09:40.600> b<00:09:40.760> or<00:09:40.920> there<00:09:41.079> exists 00:09:41.350 --> 00:09:41.360 align:start position:0% like a is greater than b or there exists 00:09:41.360 --> 00:09:44.190 align:start position:0% like a is greater than b or there exists C<00:09:41.560> such<00:09:41.800> that<00:09:41.959> c<00:09:42.360> is<00:09:42.519> part<00:09:42.680> of<00:09:42.800> D<00:09:43.320> we<00:09:43.480> replace<00:09:43.920> up 00:09:44.190 --> 00:09:44.200 align:start position:0% C such that c is part of D we replace up 00:09:44.200 --> 00:09:46.269 align:start position:0% C such that c is part of D we replace up code<00:09:44.399> with<00:09:44.519> logical<00:09:44.920> operation<00:09:45.760> so<00:09:46.040> as<00:09:46.120> an 00:09:46.269 --> 00:09:46.279 align:start position:0% code with logical operation so as an 00:09:46.279 --> 00:09:48.710 align:start position:0% code with logical operation so as an example<00:09:46.959> a<00:09:47.120> is<00:09:47.200> smaller<00:09:47.560> than<00:09:47.720> b<00:09:48.000> implies<00:09:48.440> a<00:09:48.600> is 00:09:48.710 --> 00:09:48.720 align:start position:0% example a is smaller than b implies a is 00:09:48.720 --> 00:09:50.829 align:start position:0% example a is smaller than b implies a is not<00:09:48.880> equal<00:09:49.200> b<00:09:49.680> or<00:09:49.800> if<00:09:49.920> you<00:09:50.000> have<00:09:50.160> a<00:09:50.399> defined<00:09:50.720> as 00:09:50.829 --> 00:09:50.839 align:start position:0% not equal b or if you have a defined as 00:09:50.839 --> 00:09:52.710 align:start position:0% not equal b or if you have a defined as 10<00:09:51.040> and<00:09:51.160> B<00:09:51.320> defined<00:09:51.600> as<00:09:51.720> 10<00:09:52.000> you<00:09:52.079> can<00:09:52.240> derive<00:09:52.560> a 00:09:52.710 --> 00:09:52.720 align:start position:0% 10 and B defined as 10 you can derive a 00:09:52.720 --> 00:09:54.550 align:start position:0% 10 and B defined as 10 you can derive a equals<00:09:53.040> B<00:09:53.360> all<00:09:53.480> of<00:09:53.560> these<00:09:53.680> are<00:09:53.800> like<00:09:54.000> B<00:09:54.320> basic 00:09:54.550 --> 00:09:54.560 align:start position:0% equals B all of these are like B basic 00:09:54.560 --> 00:09:56.990 align:start position:0% equals B all of these are like B basic logical<00:09:54.959> operations<00:09:55.920> uh<00:09:56.079> data<00:09:56.360> becomes 00:09:56.990 --> 00:09:57.000 align:start position:0% logical operations uh data becomes 00:09:57.000 --> 00:09:59.910 align:start position:0% logical operations uh data becomes theorems<00:09:58.000> uh<00:09:58.279> programs<00:09:58.720> become<00:09:58.959> proofs 00:09:59.910 --> 00:09:59.920 align:start position:0% theorems uh programs become proofs 00:09:59.920 --> 00:10:01.550 align:start position:0% theorems uh programs become proofs uh<00:10:00.040> not<00:10:00.240> the<00:10:00.360> kind<00:10:00.519> of<00:10:00.640> proofs<00:10:01.120> that<00:10:01.240> you<00:10:01.360> know 00:10:01.550 --> 00:10:01.560 align:start position:0% uh not the kind of proofs that you know 00:10:01.560 --> 00:10:02.829 align:start position:0% uh not the kind of proofs that you know about<00:10:01.839> if<00:10:01.959> you're<00:10:02.079> a<00:10:02.200> cryptographer<00:10:02.720> a 00:10:02.829 --> 00:10:02.839 align:start position:0% about if you're a cryptographer a 00:10:02.839 --> 00:10:03.910 align:start position:0% about if you're a cryptographer a different<00:10:03.079> kind<00:10:03.200> of<00:10:03.320> proofs<00:10:03.600> now<00:10:03.720> we're<00:10:03.839> going 00:10:03.910 --> 00:10:03.920 align:start position:0% different kind of proofs now we're going 00:10:03.920 --> 00:10:06.350 align:start position:0% different kind of proofs now we're going to<00:10:04.000> mix<00:10:04.200> all<00:10:04.279> the<00:10:04.399> words<00:10:04.760> together<00:10:05.600> um<00:10:06.240> it's 00:10:06.350 --> 00:10:06.360 align:start position:0% to mix all the words together um it's 00:10:06.360 --> 00:10:08.030 align:start position:0% to mix all the words together um it's like<00:10:06.480> a<00:10:06.600> pretty<00:10:06.800> interesting<00:10:07.519> way<00:10:07.640> to<00:10:07.800> look<00:10:07.920> at 00:10:08.030 --> 00:10:08.040 align:start position:0% like a pretty interesting way to look at 00:10:08.040 --> 00:10:09.990 align:start position:0% like a pretty interesting way to look at the<00:10:08.200> system<00:10:08.519> essentially<00:10:08.959> what<00:10:09.120> we<00:10:09.240> have<00:10:09.440> is 00:10:09.990 --> 00:10:10.000 align:start position:0% the system essentially what we have is 00:10:10.000 --> 00:10:12.069 align:start position:0% the system essentially what we have is data<00:10:10.240> that<00:10:10.360> gets<00:10:10.560> imported<00:10:11.000> our<00:10:11.200> axioms 00:10:12.069 --> 00:10:12.079 align:start position:0% data that gets imported our axioms 00:10:12.079 --> 00:10:14.269 align:start position:0% data that gets imported our axioms they're<00:10:12.360> combined<00:10:13.279> into<00:10:13.480> a<00:10:13.600> logic<00:10:14.160> like 00:10:14.269 --> 00:10:14.279 align:start position:0% they're combined into a logic like 00:10:14.279 --> 00:10:15.430 align:start position:0% they're combined into a logic like through<00:10:14.480> logic<00:10:14.760> proof<00:10:14.959> they<00:10:15.040> get<00:10:15.160> combined 00:10:15.430 --> 00:10:15.440 align:start position:0% through logic proof they get combined 00:10:15.440 --> 00:10:17.150 align:start position:0% through logic proof they get combined into<00:10:15.560> a<00:10:15.680> theorem<00:10:16.120> and<00:10:16.200> then<00:10:16.480> more<00:10:16.680> theorems 00:10:17.150 --> 00:10:17.160 align:start position:0% into a theorem and then more theorems 00:10:17.160 --> 00:10:19.150 align:start position:0% into a theorem and then more theorems can<00:10:17.279> build<00:10:17.600> theorems<00:10:18.160> right<00:10:18.760> so<00:10:19.000> the 00:10:19.150 --> 00:10:19.160 align:start position:0% can build theorems right so the 00:10:19.160 --> 00:10:20.550 align:start position:0% can build theorems right so the interesting<00:10:19.519> thing<00:10:19.720> with<00:10:19.880> that<00:10:20.000> is<00:10:20.200> all<00:10:20.360> of 00:10:20.550 --> 00:10:20.560 align:start position:0% interesting thing with that is all of 00:10:20.560 --> 00:10:22.110 align:start position:0% interesting thing with that is all of mathematics<00:10:21.120> is<00:10:21.279> already<00:10:21.519> built<00:10:21.800> on<00:10:21.959> that 00:10:22.110 --> 00:10:22.120 align:start position:0% mathematics is already built on that 00:10:22.120 --> 00:10:23.550 align:start position:0% mathematics is already built on that principle<00:10:22.600> which<00:10:22.680> is<00:10:22.839> every<00:10:23.000> time<00:10:23.120> we<00:10:23.240> prove 00:10:23.550 --> 00:10:23.560 align:start position:0% principle which is every time we prove 00:10:23.560 --> 00:10:25.030 align:start position:0% principle which is every time we prove something<00:10:23.800> we<00:10:23.880> can<00:10:24.000> prove<00:10:24.279> more<00:10:24.480> out<00:10:24.600> of<00:10:24.760> it 00:10:25.030 --> 00:10:25.040 align:start position:0% something we can prove more out of it 00:10:25.040 --> 00:10:26.350 align:start position:0% something we can prove more out of it and<00:10:25.160> we<00:10:25.240> don't<00:10:25.399> need<00:10:25.519> to<00:10:25.920> understand<00:10:26.079> what<00:10:26.200> has 00:10:26.350 --> 00:10:26.360 align:start position:0% and we don't need to understand what has 00:10:26.360 --> 00:10:28.710 align:start position:0% and we don't need to understand what has been<00:10:26.560> done<00:10:26.839> so<00:10:27.079> far<00:10:27.600> like<00:10:27.839> mathematics<00:10:28.399> is 00:10:28.710 --> 00:10:28.720 align:start position:0% been done so far like mathematics is 00:10:28.720 --> 00:10:30.790 align:start position:0% been done so far like mathematics is truly<00:10:29.040> inter<00:10:29.440> operable<00:10:30.240> in<00:10:30.320> a<00:10:30.480> way<00:10:30.640> that 00:10:30.790 --> 00:10:30.800 align:start position:0% truly inter operable in a way that 00:10:30.800 --> 00:10:34.190 align:start position:0% truly inter operable in a way that programs<00:10:31.160> are<00:10:31.480> not<00:10:32.480> um<00:10:33.279> so<00:10:33.560> if<00:10:33.640> we<00:10:33.800> get<00:10:33.959> back<00:10:34.079> to 00:10:34.190 --> 00:10:34.200 align:start position:0% programs are not um so if we get back to 00:10:34.200 --> 00:10:35.509 align:start position:0% programs are not um so if we get back to this<00:10:34.399> example<00:10:34.839> you<00:10:34.959> know<00:10:35.120> after<00:10:35.320> we've 00:10:35.509 --> 00:10:35.519 align:start position:0% this example you know after we've 00:10:35.519 --> 00:10:36.990 align:start position:0% this example you know after we've counted<00:10:35.800> how<00:10:35.920> many<00:10:36.279> best<00:10:36.480> friends<00:10:36.720> you<00:10:36.839> have 00:10:36.990 --> 00:10:37.000 align:start position:0% counted how many best friends you have 00:10:37.000 --> 00:10:38.230 align:start position:0% counted how many best friends you have and<00:10:37.160> want<00:10:37.320> to<00:10:37.440> know<00:10:37.720> whether<00:10:37.959> you<00:10:38.079> have<00:10:38.160> a 00:10:38.230 --> 00:10:38.240 align:start position:0% and want to know whether you have a 00:10:38.240 --> 00:10:40.150 align:start position:0% and want to know whether you have a great<00:10:38.440> friend<00:10:38.680> group<00:10:39.320> what<00:10:39.480> this<00:10:39.639> turns<00:10:39.880> into 00:10:40.150 --> 00:10:40.160 align:start position:0% great friend group what this turns into 00:10:40.160 --> 00:10:41.550 align:start position:0% great friend group what this turns into is<00:10:40.240> you<00:10:40.360> have<00:10:40.440> a<00:10:40.560> theorem<00:10:41.160> and<00:10:41.320> through 00:10:41.550 --> 00:10:41.560 align:start position:0% is you have a theorem and through 00:10:41.560 --> 00:10:43.509 align:start position:0% is you have a theorem and through another<00:10:41.880> logic<00:10:42.200> proof<00:10:42.560> you<00:10:42.720> get<00:10:43.040> yet<00:10:43.240> another 00:10:43.509 --> 00:10:43.519 align:start position:0% another logic proof you get yet another 00:10:43.519 --> 00:10:45.430 align:start position:0% another logic proof you get yet another theorem<00:10:43.880> in<00:10:44.040> plain<00:10:44.279> English<00:10:44.600> you<00:10:44.680> would<00:10:44.880> have 00:10:45.430 --> 00:10:45.440 align:start position:0% theorem in plain English you would have 00:10:45.440 --> 00:10:49.150 align:start position:0% theorem in plain English you would have theorem<00:10:46.240> blue<00:10:46.959> I<00:10:47.079> have<00:10:47.279> 12<00:10:47.639> best<00:10:47.959> friends<00:10:48.959> uh 00:10:49.150 --> 00:10:49.160 align:start position:0% theorem blue I have 12 best friends uh 00:10:49.160 --> 00:10:51.069 align:start position:0% theorem blue I have 12 best friends uh implies<00:10:49.720> theorem<00:10:50.120> green<00:10:50.519> I<00:10:50.639> have<00:10:50.760> more<00:10:50.920> than 00:10:51.069 --> 00:10:51.079 align:start position:0% implies theorem green I have more than 00:10:51.079 --> 00:10:54.110 align:start position:0% implies theorem green I have more than three<00:10:51.279> best<00:10:51.480> friends<00:10:52.079> makes<00:10:52.360> sense<00:10:52.760> right<00:10:53.519> um 00:10:54.110 --> 00:10:54.120 align:start position:0% three best friends makes sense right um 00:10:54.120 --> 00:10:55.430 align:start position:0% three best friends makes sense right um so<00:10:54.279> now<00:10:54.399> we<00:10:54.480> have<00:10:54.600> two<00:10:54.720> kinds<00:10:54.920> of<00:10:55.000> proof<00:10:55.240> in<00:10:55.320> the 00:10:55.430 --> 00:10:55.440 align:start position:0% so now we have two kinds of proof in the 00:10:55.440 --> 00:10:56.829 align:start position:0% so now we have two kinds of proof in the system<00:10:55.680> we<00:10:55.760> have<00:10:55.839> a<00:10:55.959> formal<00:10:56.320> proof<00:10:56.639> and<00:10:56.720> we 00:10:56.829 --> 00:10:56.839 align:start position:0% system we have a formal proof and we 00:10:56.839 --> 00:10:58.629 align:start position:0% system we have a formal proof and we have<00:10:56.920> a<00:10:57.000> zero<00:10:57.320> knowledge<00:10:57.600> proof<00:10:57.880> the<00:10:58.000> Z<00:10:58.399> proof 00:10:58.629 --> 00:10:58.639 align:start position:0% have a zero knowledge proof the Z proof 00:10:58.639 --> 00:11:00.710 align:start position:0% have a zero knowledge proof the Z proof is<00:10:58.760> used<00:10:59.480> to<00:10:59.680> show<00:11:00.000> that<00:11:00.120> the<00:11:00.200> formal<00:11:00.519> proof 00:11:00.710 --> 00:11:00.720 align:start position:0% is used to show that the formal proof 00:11:00.720 --> 00:11:02.990 align:start position:0% is used to show that the formal proof was<00:11:01.240> computed<00:11:01.639> correctly<00:11:02.120> and<00:11:02.440> hide<00:11:02.800> some 00:11:02.990 --> 00:11:03.000 align:start position:0% was computed correctly and hide some 00:11:03.000 --> 00:11:04.509 align:start position:0% was computed correctly and hide some inputs<00:11:03.399> about<00:11:03.600> it<00:11:04.000> right<00:11:04.120> you<00:11:04.200> want<00:11:04.320> to<00:11:04.440> be 00:11:04.509 --> 00:11:04.519 align:start position:0% inputs about it right you want to be 00:11:04.519 --> 00:11:05.790 align:start position:0% inputs about it right you want to be able<00:11:04.680> to<00:11:04.800> say<00:11:05.040> I<00:11:05.160> have<00:11:05.279> more<00:11:05.399> than<00:11:05.560> three 00:11:05.790 --> 00:11:05.800 align:start position:0% able to say I have more than three 00:11:05.800 --> 00:11:07.590 align:start position:0% able to say I have more than three friends<00:11:06.440> without<00:11:06.720> showing<00:11:07.000> who<00:11:07.120> your<00:11:07.279> friends 00:11:07.590 --> 00:11:07.600 align:start position:0% friends without showing who your friends 00:11:07.600 --> 00:11:11.230 align:start position:0% friends without showing who your friends are<00:11:08.360> right<00:11:09.360> so<00:11:10.160> um<00:11:10.480> and<00:11:10.560> you<00:11:10.680> can<00:11:10.880> you<00:11:10.959> can<00:11:11.120> kind 00:11:11.230 --> 00:11:11.240 align:start position:0% are right so um and you can you can kind 00:11:11.240 --> 00:11:12.750 align:start position:0% are right so um and you can you can kind of<00:11:11.360> like<00:11:11.480> go<00:11:11.600> arbitrarily<00:11:12.120> deep<00:11:12.440> here<00:11:12.639> you 00:11:12.750 --> 00:11:12.760 align:start position:0% of like go arbitrarily deep here you 00:11:12.760 --> 00:11:14.829 align:start position:0% of like go arbitrarily deep here you have<00:11:12.920> theorems<00:11:13.360> you<00:11:13.480> make<00:11:13.680> proofs<00:11:14.600> out<00:11:14.720> of 00:11:14.829 --> 00:11:14.839 align:start position:0% have theorems you make proofs out of 00:11:14.839 --> 00:11:16.110 align:start position:0% have theorems you make proofs out of that<00:11:14.959> you<00:11:15.000> get<00:11:15.120> a<00:11:15.200> new<00:11:15.360> theorem<00:11:15.720> you<00:11:15.839> combine 00:11:16.110 --> 00:11:16.120 align:start position:0% that you get a new theorem you combine 00:11:16.120 --> 00:11:17.389 align:start position:0% that you get a new theorem you combine that<00:11:16.240> with<00:11:16.320> a<00:11:16.440> previous<00:11:16.720> theorem<00:11:17.079> maybe<00:11:17.279> for 00:11:17.389 --> 00:11:17.399 align:start position:0% that with a previous theorem maybe for 00:11:17.399 --> 00:11:18.910 align:start position:0% that with a previous theorem maybe for someone<00:11:17.639> else<00:11:17.800> to<00:11:17.920> make<00:11:18.079> more<00:11:18.240> theorem<00:11:18.639> and<00:11:18.760> so 00:11:18.910 --> 00:11:18.920 align:start position:0% someone else to make more theorem and so 00:11:18.920 --> 00:11:20.910 align:start position:0% someone else to make more theorem and so forth<00:11:19.760> here's<00:11:19.959> how<00:11:20.120> it<00:11:20.200> looks<00:11:20.399> like<00:11:20.519> in<00:11:20.600> a<00:11:20.760> very 00:11:20.910 --> 00:11:20.920 align:start position:0% forth here's how it looks like in a very 00:11:20.920 --> 00:11:22.509 align:start position:0% forth here's how it looks like in a very early<00:11:21.200> version<00:11:21.440> of<00:11:21.519> our<00:11:21.680> system<00:11:22.000> so<00:11:22.120> these<00:11:22.240> are 00:11:22.509 --> 00:11:22.519 align:start position:0% early version of our system so these are 00:11:22.519 --> 00:11:24.150 align:start position:0% early version of our system so these are statements<00:11:23.079> these<00:11:23.240> are<00:11:23.399> the<00:11:23.560> actual<00:11:23.880> things 00:11:24.150 --> 00:11:24.160 align:start position:0% statements these are the actual things 00:11:24.160 --> 00:11:26.030 align:start position:0% statements these are the actual things that<00:11:24.279> are<00:11:24.399> inside<00:11:24.639> a<00:11:24.800> pod<00:11:25.320> so<00:11:25.480> the<00:11:25.600> most<00:11:25.800> basic 00:11:26.030 --> 00:11:26.040 align:start position:0% that are inside a pod so the most basic 00:11:26.040 --> 00:11:27.470 align:start position:0% that are inside a pod so the most basic statement<00:11:26.399> is<00:11:26.519> the<00:11:26.639> value<00:11:26.880> of<00:11:27.079> statement 00:11:27.470 --> 00:11:27.480 align:start position:0% statement is the value of statement 00:11:27.480 --> 00:11:29.670 align:start position:0% statement is the value of statement which<00:11:27.600> is<00:11:27.720> that<00:11:27.880> the<00:11:28.079> value<00:11:28.360> of<00:11:28.480> an<00:11:28.639> entry<00:11:29.440> is 00:11:29.670 --> 00:11:29.680 align:start position:0% which is that the value of an entry is 00:11:29.680 --> 00:11:32.269 align:start position:0% which is that the value of an entry is this<00:11:30.040> like<00:11:30.320> the<00:11:30.519> value<00:11:30.880> of<00:11:31.279> is<00:11:31.600> best<00:11:31.839> friend<00:11:32.120> is 00:11:32.269 --> 00:11:32.279 align:start position:0% this like the value of is best friend is 00:11:32.279 --> 00:11:35.030 align:start position:0% this like the value of is best friend is true<00:11:32.600> in<00:11:32.760> the<00:11:32.959> specific<00:11:33.279> pod<00:11:34.240> this<00:11:34.360> is<00:11:34.639> how 00:11:35.030 --> 00:11:35.040 align:start position:0% true in the specific pod this is how 00:11:35.040 --> 00:11:36.829 align:start position:0% true in the specific pod this is how most<00:11:35.360> people<00:11:35.600> think<00:11:35.760> of<00:11:35.920> cryptographic<00:11:36.519> data 00:11:36.829 --> 00:11:36.839 align:start position:0% most people think of cryptographic data 00:11:36.839 --> 00:11:38.230 align:start position:0% most people think of cryptographic data they<00:11:37.000> just<00:11:37.120> have<00:11:37.320> the<00:11:37.480> value<00:11:37.680> of<00:11:37.839> statement 00:11:38.230 --> 00:11:38.240 align:start position:0% they just have the value of statement 00:11:38.240 --> 00:11:39.829 align:start position:0% they just have the value of statement they<00:11:38.320> don't<00:11:38.480> have<00:11:38.639> anything<00:11:38.920> else<00:11:39.600> but<00:11:39.720> then 00:11:39.829 --> 00:11:39.839 align:start position:0% they don't have anything else but then 00:11:39.839 --> 00:11:41.269 align:start position:0% they don't have anything else but then we<00:11:39.959> added<00:11:40.200> a<00:11:40.279> bunch<00:11:40.480> of<00:11:40.560> other<00:11:40.760> stuff<00:11:41.000> like<00:11:41.160> the 00:11:41.269 --> 00:11:41.279 align:start position:0% we added a bunch of other stuff like the 00:11:41.279 --> 00:11:42.829 align:start position:0% we added a bunch of other stuff like the equal<00:11:41.600> statement<00:11:42.040> which<00:11:42.120> is<00:11:42.320> this<00:11:42.480> entry<00:11:42.760> is 00:11:42.829 --> 00:11:42.839 align:start position:0% equal statement which is this entry is 00:11:42.839 --> 00:11:44.870 align:start position:0% equal statement which is this entry is equals<00:11:43.200> that<00:11:43.360> entry<00:11:44.120> uh<00:11:44.200> or<00:11:44.360> the<00:11:44.480> sum<00:11:44.720> of 00:11:44.870 --> 00:11:44.880 align:start position:0% equals that entry uh or the sum of 00:11:44.880 --> 00:11:46.430 align:start position:0% equals that entry uh or the sum of statement<00:11:45.320> which<00:11:45.440> says<00:11:45.639> that<00:11:45.800> the<00:11:45.920> sum<00:11:46.120> of<00:11:46.320> the 00:11:46.430 --> 00:11:46.440 align:start position:0% statement which says that the sum of the 00:11:46.440 --> 00:11:49.310 align:start position:0% statement which says that the sum of the two<00:11:47.440> um<00:11:47.920> the<00:11:48.160> entry<00:11:48.480> number<00:11:48.720> two<00:11:48.920> and<00:11:49.079> three<00:11:49.240> in 00:11:49.310 --> 00:11:49.320 align:start position:0% two um the entry number two and three in 00:11:49.320 --> 00:11:51.590 align:start position:0% two um the entry number two and three in the<00:11:49.440> two<00:11:49.639> pole<00:11:49.839> equals<00:11:50.200> entry<00:11:50.519> number<00:11:50.760> one<00:11:51.320> and 00:11:51.590 --> 00:11:51.600 align:start position:0% the two pole equals entry number one and 00:11:51.600 --> 00:11:53.269 align:start position:0% the two pole equals entry number one and this<00:11:51.720> is<00:11:52.079> like<00:11:52.240> a<00:11:52.320> very<00:11:52.519> early<00:11:52.839> version<00:11:53.120> that 00:11:53.269 --> 00:11:53.279 align:start position:0% this is like a very early version that 00:11:53.279 --> 00:11:54.910 align:start position:0% this is like a very early version that we<00:11:53.440> had<00:11:53.639> but<00:11:53.760> you<00:11:53.880> can<00:11:54.079> imagine<00:11:54.440> extending 00:11:54.910 --> 00:11:54.920 align:start position:0% we had but you can imagine extending 00:11:54.920 --> 00:11:56.230 align:start position:0% we had but you can imagine extending this<00:11:55.079> to<00:11:55.279> something<00:11:55.560> that<00:11:55.680> is<00:11:55.839> powerful 00:11:56.230 --> 00:11:56.240 align:start position:0% this to something that is powerful 00:11:56.240 --> 00:11:57.829 align:start position:0% this to something that is powerful enough<00:11:56.399> to<00:11:56.560> essentially<00:11:56.920> prove<00:11:57.160> anything<00:11:57.440> in 00:11:57.829 --> 00:11:57.839 align:start position:0% enough to essentially prove anything in 00:11:57.839 --> 00:12:00.190 align:start position:0% enough to essentially prove anything in first<00:11:58.079> or<00:11:58.200> second<00:11:58.440> order<00:11:58.720> logic<00:11:59.600> um<00:11:59.920> and<00:12:00.079> these 00:12:00.190 --> 00:12:00.200 align:start position:0% first or second order logic um and these 00:12:00.200 --> 00:12:01.990 align:start position:0% first or second order logic um and these are<00:12:00.360> our<00:12:00.519> up<00:12:00.800> codes<00:12:01.240> as<00:12:01.360> an<00:12:01.480> example<00:12:01.760> we<00:12:01.880> have 00:12:01.990 --> 00:12:02.000 align:start position:0% are our up codes as an example we have 00:12:02.000 --> 00:12:03.750 align:start position:0% are our up codes as an example we have the<00:12:02.120> equality<00:12:02.480> from<00:12:02.800> entries<00:12:03.160> up<00:12:03.399> code<00:12:03.639> which 00:12:03.750 --> 00:12:03.760 align:start position:0% the equality from entries up code which 00:12:03.760 --> 00:12:05.550 align:start position:0% the equality from entries up code which says<00:12:04.079> hey<00:12:04.399> if<00:12:04.519> you<00:12:04.600> have<00:12:04.720> entry<00:12:05.000> one<00:12:05.160> and<00:12:05.240> entry 00:12:05.550 --> 00:12:05.560 align:start position:0% says hey if you have entry one and entry 00:12:05.560 --> 00:12:07.350 align:start position:0% says hey if you have entry one and entry two<00:12:06.120> you<00:12:06.200> can<00:12:06.399> apply<00:12:06.680> the<00:12:06.800> equality<00:12:07.200> from 00:12:07.350 --> 00:12:07.360 align:start position:0% two you can apply the equality from 00:12:07.360 --> 00:12:09.509 align:start position:0% two you can apply the equality from entries<00:12:07.680> OB<00:12:07.920> code<00:12:08.200> only<00:12:08.600> if<00:12:08.800> entry<00:12:09.079> 1<00:12:09.240> equals 00:12:09.509 --> 00:12:09.519 align:start position:0% entries OB code only if entry 1 equals 00:12:09.519 --> 00:12:11.030 align:start position:0% entries OB code only if entry 1 equals entry<00:12:09.760> two<00:12:10.000> to<00:12:10.120> get<00:12:10.240> a<00:12:10.360> statement<00:12:10.720> that<00:12:10.800> says 00:12:11.030 --> 00:12:11.040 align:start position:0% entry two to get a statement that says 00:12:11.040 --> 00:12:15.350 align:start position:0% entry two to get a statement that says entry<00:12:11.279> 1<00:12:11.440> equals<00:12:11.720> entry<00:12:11.959> two<00:12:12.839> uh<00:12:13.880> so<00:12:14.880> what<00:12:15.240> what 00:12:15.350 --> 00:12:15.360 align:start position:0% entry 1 equals entry two uh so what what 00:12:15.360 --> 00:12:16.590 align:start position:0% entry 1 equals entry two uh so what what we<00:12:15.480> had<00:12:15.600> to<00:12:15.680> do<00:12:15.800> from<00:12:15.920> a<00:12:16.040> cryptography 00:12:16.590 --> 00:12:16.600 align:start position:0% we had to do from a cryptography 00:12:16.600 --> 00:12:17.790 align:start position:0% we had to do from a cryptography perspective<00:12:16.959> is<00:12:17.079> essentially<00:12:17.440> build<00:12:17.639> a 00:12:17.790 --> 00:12:17.800 align:start position:0% perspective is essentially build a 00:12:17.800 --> 00:12:19.350 align:start position:0% perspective is essentially build a circuit<00:12:18.440> that<00:12:18.639> instead<00:12:18.880> of<00:12:19.000> proving<00:12:19.279> the 00:12:19.350 --> 00:12:19.360 align:start position:0% circuit that instead of proving the 00:12:19.360 --> 00:12:21.509 align:start position:0% circuit that instead of proving the state<00:12:19.639> transition<00:12:20.000> of<00:12:20.120> a<00:12:20.199> CPR<00:12:20.639> architecture 00:12:21.509 --> 00:12:21.519 align:start position:0% state transition of a CPR architecture 00:12:21.519 --> 00:12:23.310 align:start position:0% state transition of a CPR architecture proves<00:12:21.800> The<00:12:22.000> Logical<00:12:22.480> operations<00:12:23.079> on 00:12:23.310 --> 00:12:23.320 align:start position:0% proves The Logical operations on 00:12:23.320 --> 00:12:25.110 align:start position:0% proves The Logical operations on statement<00:12:23.680> is<00:12:23.800> done<00:12:24.000> correctly<00:12:24.600> right<00:12:24.720> it's<00:12:24.839> a 00:12:25.110 --> 00:12:25.120 align:start position:0% statement is done correctly right it's a 00:12:25.120 --> 00:12:26.590 align:start position:0% statement is done correctly right it's a cryptographically<00:12:25.839> verified<00:12:26.240> theorem 00:12:26.590 --> 00:12:26.600 align:start position:0% cryptographically verified theorem 00:12:26.600 --> 00:12:28.590 align:start position:0% cryptographically verified theorem prover<00:12:26.920> if<00:12:27.000> you<00:12:27.120> want<00:12:27.800> okay<00:12:27.920> so<00:12:28.079> the<00:12:28.360> Second 00:12:28.590 --> 00:12:28.600 align:start position:0% prover if you want okay so the Second 00:12:28.600 --> 00:12:31.230 align:start position:0% prover if you want okay so the Second Challenge<00:12:28.920> we<00:12:29.040> have<00:12:29.399> is<00:12:30.040> um<00:12:30.720> we<00:12:30.880> want<00:12:31.000> to<00:12:31.120> be 00:12:31.230 --> 00:12:31.240 align:start position:0% Challenge we have is um we want to be 00:12:31.240 --> 00:12:33.069 align:start position:0% Challenge we have is um we want to be able<00:12:31.399> to<00:12:31.560> import<00:12:32.000> data<00:12:32.240> from<00:12:32.399> The<00:12:32.519> Real<00:12:32.720> World 00:12:33.069 --> 00:12:33.079 align:start position:0% able to import data from The Real World 00:12:33.079 --> 00:12:34.710 align:start position:0% able to import data from The Real World because<00:12:33.199> we<00:12:33.320> don't<00:12:33.560> expect<00:12:34.000> people<00:12:34.320> changing 00:12:34.710 --> 00:12:34.720 align:start position:0% because we don't expect people changing 00:12:34.720 --> 00:12:36.310 align:start position:0% because we don't expect people changing the<00:12:34.839> way<00:12:35.000> they<00:12:35.120> issue<00:12:35.399> data<00:12:35.760> it<00:12:35.839> was<00:12:35.959> already 00:12:36.310 --> 00:12:36.320 align:start position:0% the way they issue data it was already 00:12:36.320 --> 00:12:38.790 align:start position:0% the way they issue data it was already sufficiently<00:12:36.880> hard<00:12:37.160> to<00:12:37.279> get<00:12:37.399> them<00:12:37.519> to<00:12:38.440> export 00:12:38.790 --> 00:12:38.800 align:start position:0% sufficiently hard to get them to export 00:12:38.800 --> 00:12:40.590 align:start position:0% sufficiently hard to get them to export cryptographic<00:12:39.360> data<00:12:39.560> in<00:12:39.639> the<00:12:39.800> first<00:12:40.079> place 00:12:40.590 --> 00:12:40.600 align:start position:0% cryptographic data in the first place 00:12:40.600 --> 00:12:41.710 align:start position:0% cryptographic data in the first place good<00:12:40.760> luck<00:12:40.959> coming<00:12:41.199> back<00:12:41.360> to<00:12:41.480> them<00:12:41.600> and 00:12:41.710 --> 00:12:41.720 align:start position:0% good luck coming back to them and 00:12:41.720 --> 00:12:43.470 align:start position:0% good luck coming back to them and telling<00:12:41.920> them<00:12:42.040> they<00:12:42.199> did<00:12:42.320> it<00:12:42.440> the<00:12:42.600> wrong<00:12:42.800> way 00:12:43.470 --> 00:12:43.480 align:start position:0% telling them they did it the wrong way 00:12:43.480 --> 00:12:44.990 align:start position:0% telling them they did it the wrong way so<00:12:43.880> what<00:12:44.000> this<00:12:44.160> turns<00:12:44.399> into<00:12:44.639> is<00:12:44.720> you<00:12:44.800> want<00:12:44.920> to 00:12:44.990 --> 00:12:45.000 align:start position:0% so what this turns into is you want to 00:12:45.000 --> 00:12:46.670 align:start position:0% so what this turns into is you want to be<00:12:45.079> able<00:12:45.240> to<00:12:45.320> turn<00:12:45.560> any<00:12:45.760> verifiable<00:12:46.360> piece<00:12:46.519> of 00:12:46.670 --> 00:12:46.680 align:start position:0% be able to turn any verifiable piece of 00:12:46.680 --> 00:12:48.910 align:start position:0% be able to turn any verifiable piece of data<00:12:46.959> into<00:12:47.120> a<00:12:47.279> set<00:12:47.440> of<00:12:47.639> value<00:12:47.920> of<00:12:48.120> statement 00:12:48.910 --> 00:12:48.920 align:start position:0% data into a set of value of statement 00:12:48.920 --> 00:12:51.470 align:start position:0% data into a set of value of statement with<00:12:49.199> special<00:12:49.560> metadata<00:12:50.120> as<00:12:50.240> an<00:12:50.399> example<00:12:51.240> who 00:12:51.470 --> 00:12:51.480 align:start position:0% with special metadata as an example who 00:12:51.480 --> 00:12:53.829 align:start position:0% with special metadata as an example who signed<00:12:51.880> it<00:12:52.440> what<00:12:52.560> was<00:12:52.720> the<00:12:52.880> URL<00:12:53.440> if<00:12:53.519> it<00:12:53.639> comes 00:12:53.829 --> 00:12:53.839 align:start position:0% signed it what was the URL if it comes 00:12:53.839 --> 00:12:56.350 align:start position:0% signed it what was the URL if it comes from<00:12:54.160> like<00:12:54.240> a<00:12:54.399> web<00:12:54.680> proof<00:12:55.320> when<00:12:55.560> was<00:12:55.680> it<00:12:55.839> signed 00:12:56.350 --> 00:12:56.360 align:start position:0% from like a web proof when was it signed 00:12:56.360 --> 00:12:58.389 align:start position:0% from like a web proof when was it signed Etc<00:12:57.040> right<00:12:57.440> and<00:12:57.639> then<00:12:57.760> you<00:12:57.880> can<00:12:58.000> further 00:12:58.389 --> 00:12:58.399 align:start position:0% Etc right and then you can further 00:12:58.399 --> 00:13:00.590 align:start position:0% Etc right and then you can further combine<00:12:58.760> these<00:12:59.240> into<00:12:59.519> any<00:12:59.720> other<00:13:00.000> pod<00:13:00.360> using 00:13:00.590 --> 00:13:00.600 align:start position:0% combine these into any other pod using 00:13:00.600 --> 00:13:02.430 align:start position:0% combine these into any other pod using the<00:13:00.760> logic<00:13:01.519> um<00:13:01.839> so<00:13:01.959> what<00:13:02.040> if<00:13:02.160> I<00:13:02.240> want<00:13:02.320> to 00:13:02.430 --> 00:13:02.440 align:start position:0% the logic um so what if I want to 00:13:02.440 --> 00:13:04.150 align:start position:0% the logic um so what if I want to compute<00:13:02.720> with<00:13:02.839> one<00:13:02.959> of<00:13:03.040> my<00:13:03.199> frog<00:13:03.720> right<00:13:04.000> you 00:13:04.150 --> 00:13:04.160 align:start position:0% compute with one of my frog right you 00:13:04.160 --> 00:13:05.629 align:start position:0% compute with one of my frog right you guys<00:13:04.279> have<00:13:04.480> frogs<00:13:04.920> I<00:13:05.000> hope<00:13:05.120> you<00:13:05.199> have<00:13:05.320> frogs<00:13:05.560> if 00:13:05.629 --> 00:13:05.639 align:start position:0% guys have frogs I hope you have frogs if 00:13:05.639 --> 00:13:06.870 align:start position:0% guys have frogs I hope you have frogs if you<00:13:05.720> don't<00:13:05.880> have<00:13:05.959> frogs<00:13:06.240> you're<00:13:06.320> a<00:13:06.440> loser<00:13:06.760> you 00:13:06.870 --> 00:13:06.880 align:start position:0% you don't have frogs you're a loser you 00:13:06.880 --> 00:13:09.750 align:start position:0% you don't have frogs you're a loser you need<00:13:07.000> to<00:13:07.160> go<00:13:07.279> get<00:13:07.399> frogs<00:13:08.320> um<00:13:08.920> frogs<00:13:09.279> are<00:13:09.480> pod 00:13:09.750 --> 00:13:09.760 align:start position:0% need to go get frogs um frogs are pod 00:13:09.760 --> 00:13:12.230 align:start position:0% need to go get frogs um frogs are pod ones<00:13:10.519> pod<00:13:10.760> ones<00:13:11.279> as<00:13:11.399> I<00:13:11.480> was<00:13:11.600> showing<00:13:11.880> earlier 00:13:12.230 --> 00:13:12.240 align:start position:0% ones pod ones as I was showing earlier 00:13:12.240 --> 00:13:13.310 align:start position:0% ones pod ones as I was showing earlier was<00:13:12.399> the<00:13:12.560> first<00:13:12.800> version<00:13:13.040> of<00:13:13.160> our 00:13:13.310 --> 00:13:13.320 align:start position:0% was the first version of our 00:13:13.320 --> 00:13:15.990 align:start position:0% was the first version of our cryptographic<00:13:14.079> uh<00:13:14.199> data<00:13:14.600> system<00:13:15.600> from<00:13:15.839> the 00:13:15.990 --> 00:13:16.000 align:start position:0% cryptographic uh data system from the 00:13:16.000 --> 00:13:17.750 align:start position:0% cryptographic uh data system from the perspective<00:13:16.399> of<00:13:16.560> pod<00:13:16.800> two<00:13:17.000> they're<00:13:17.240> foreign 00:13:17.750 --> 00:13:17.760 align:start position:0% perspective of pod two they're foreign 00:13:17.760 --> 00:13:19.069 align:start position:0% perspective of pod two they're foreign cryptographic<00:13:18.399> objects<00:13:18.760> they're<00:13:18.920> on 00:13:19.069 --> 00:13:19.079 align:start position:0% cryptographic objects they're on 00:13:19.079 --> 00:13:20.829 align:start position:0% cryptographic objects they're on different<00:13:19.360> curves<00:13:19.800> with<00:13:19.959> different<00:13:20.519> signing 00:13:20.829 --> 00:13:20.839 align:start position:0% different curves with different signing 00:13:20.839 --> 00:13:22.430 align:start position:0% different curves with different signing algorithms<00:13:21.320> they're<00:13:21.480> merized<00:13:22.040> in<00:13:22.240> in<00:13:22.320> a 00:13:22.430 --> 00:13:22.440 align:start position:0% algorithms they're merized in in a 00:13:22.440 --> 00:13:24.509 align:start position:0% algorithms they're merized in in a different<00:13:22.760> way<00:13:23.360> yet<00:13:23.519> they<00:13:23.639> can<00:13:23.760> be<00:13:23.920> imported 00:13:24.509 --> 00:13:24.519 align:start position:0% different way yet they can be imported 00:13:24.519 --> 00:13:26.670 align:start position:0% different way yet they can be imported via<00:13:25.000> what<00:13:25.120> we<00:13:25.240> call<00:13:25.360> an<00:13:25.480> introduction<00:13:26.000> Gadget 00:13:26.670 --> 00:13:26.680 align:start position:0% via what we call an introduction Gadget 00:13:26.680 --> 00:13:28.590 align:start position:0% via what we call an introduction Gadget so<00:13:27.120> you<00:13:27.279> have<00:13:27.480> this<00:13:27.600> introduction<00:13:28.120> Gadget 00:13:28.590 --> 00:13:28.600 align:start position:0% so you have this introduction Gadget 00:13:28.600 --> 00:13:30.230 align:start position:0% so you have this introduction Gadget that<00:13:28.800> is<00:13:28.920> going<00:13:29.000> to<00:13:29.120> going<00:13:29.199> to<00:13:29.399> verify<00:13:29.800> the 00:13:30.230 --> 00:13:30.240 align:start position:0% that is going to going to verify the 00:13:30.240 --> 00:13:32.590 align:start position:0% that is going to going to verify the EDSA<00:13:30.880> Sig<00:13:31.120> is<00:13:31.279> correct<00:13:31.680> it's<00:13:31.800> going<00:13:31.880> to<00:13:32.240> store 00:13:32.590 --> 00:13:32.600 align:start position:0% EDSA Sig is correct it's going to store 00:13:32.600 --> 00:13:34.310 align:start position:0% EDSA Sig is correct it's going to store the<00:13:32.720> signer<00:13:33.120> into<00:13:33.320> a<00:13:33.440> value<00:13:33.720> of<00:13:33.880> statement 00:13:34.310 --> 00:13:34.320 align:start position:0% the signer into a value of statement 00:13:34.320 --> 00:13:36.269 align:start position:0% the signer into a value of statement with<00:13:34.480> key<00:13:34.680> undor<00:13:35.120> signer<00:13:35.720> and<00:13:35.839> it's<00:13:35.959> going<00:13:36.079> to 00:13:36.269 --> 00:13:36.279 align:start position:0% with key undor signer and it's going to 00:13:36.279 --> 00:13:38.269 align:start position:0% with key undor signer and it's going to copy<00:13:36.600> each<00:13:36.760> of<00:13:36.880> the<00:13:37.079> Pod<00:13:37.240> one<00:13:37.440> entry<00:13:37.959> into<00:13:38.199> a 00:13:38.269 --> 00:13:38.279 align:start position:0% copy each of the Pod one entry into a 00:13:38.279 --> 00:13:39.430 align:start position:0% copy each of the Pod one entry into a value<00:13:38.480> of<00:13:38.600> statement<00:13:38.959> and<00:13:39.040> then<00:13:39.120> you<00:13:39.199> get<00:13:39.320> a 00:13:39.430 --> 00:13:39.440 align:start position:0% value of statement and then you get a 00:13:39.440 --> 00:13:40.990 align:start position:0% value of statement and then you get a pod<00:13:40.040> and<00:13:40.120> the<00:13:40.240> cool<00:13:40.399> thing<00:13:40.519> is<00:13:40.680> now<00:13:40.800> you<00:13:40.880> can 00:13:40.990 --> 00:13:41.000 align:start position:0% pod and the cool thing is now you can 00:13:41.000 --> 00:13:42.550 align:start position:0% pod and the cool thing is now you can take<00:13:41.160> two<00:13:41.320> frogs<00:13:41.680> you<00:13:41.800> can<00:13:41.920> introduce<00:13:42.399> them 00:13:42.550 --> 00:13:42.560 align:start position:0% take two frogs you can introduce them 00:13:42.560 --> 00:13:43.870 align:start position:0% take two frogs you can introduce them and<00:13:42.680> then<00:13:42.800> you<00:13:42.880> can<00:13:43.000> make<00:13:43.120> a<00:13:43.199> proof<00:13:43.480> about<00:13:43.720> them 00:13:43.870 --> 00:13:43.880 align:start position:0% and then you can make a proof about them 00:13:43.880 --> 00:13:45.990 align:start position:0% and then you can make a proof about them you<00:13:43.959> can<00:13:44.120> say<00:13:44.720> uh<00:13:44.880> Tod<00:13:45.240> is<00:13:45.360> more<00:13:45.560> beautiful 00:13:45.990 --> 00:13:46.000 align:start position:0% you can say uh Tod is more beautiful 00:13:46.000 --> 00:13:47.829 align:start position:0% you can say uh Tod is more beautiful that<00:13:46.199> the<00:13:46.320> ma<00:13:46.680> mustache<00:13:47.079> toad<00:13:47.680> that's 00:13:47.829 --> 00:13:47.839 align:start position:0% that the ma mustache toad that's 00:13:47.839 --> 00:13:49.030 align:start position:0% that the ma mustache toad that's something<00:13:48.079> you<00:13:48.160> can<00:13:48.320> prove<00:13:48.519> with<00:13:48.639> the<00:13:48.760> system 00:13:49.030 --> 00:13:49.040 align:start position:0% something you can prove with the system 00:13:49.040 --> 00:13:51.990 align:start position:0% something you can prove with the system after<00:13:49.320> you<00:13:49.440> have<00:13:49.600> introduced<00:13:50.040> the<00:13:50.199> data<00:13:51.199> um 00:13:51.990 --> 00:13:52.000 align:start position:0% after you have introduced the data um 00:13:52.000 --> 00:13:53.629 align:start position:0% after you have introduced the data um and<00:13:52.639> the<00:13:52.720> first<00:13:52.880> thing<00:13:53.079> we<00:13:53.160> want<00:13:53.279> to<00:13:53.360> do<00:13:53.440> is<00:13:53.560> be 00:13:53.629 --> 00:13:53.639 align:start position:0% and the first thing we want to do is be 00:13:53.639 --> 00:13:56.150 align:start position:0% and the first thing we want to do is be able<00:13:53.800> to<00:13:53.920> import<00:13:54.399> emails<00:13:55.399> um<00:13:55.759> we<00:13:55.839> want<00:13:55.959> to<00:13:56.079> be 00:13:56.150 --> 00:13:56.160 align:start position:0% able to import emails um we want to be 00:13:56.160 --> 00:13:58.670 align:start position:0% able to import emails um we want to be able<00:13:56.320> to<00:13:56.480> import<00:13:56.880> like<00:13:57.160> regular<00:13:57.680> API<00:13:58.120> calls 00:13:58.670 --> 00:13:58.680 align:start position:0% able to import like regular API calls 00:13:58.680 --> 00:14:01.590 align:start position:0% able to import like regular API calls and<00:13:59.160> and<00:13:59.519> probably<00:14:00.279> deal<00:14:00.639> with<00:14:00.800> one<00:14:00.959> of<00:14:01.199> the 00:14:01.590 --> 00:14:01.600 align:start position:0% and and probably deal with one of the 00:14:01.600 --> 00:14:04.470 align:start position:0% and and probably deal with one of the the<00:14:02.279> the<00:14:02.399> government<00:14:02.800> issued<00:14:03.199> ID<00:14:03.519> system<00:14:04.360> uh 00:14:04.470 --> 00:14:04.480 align:start position:0% the the government issued ID system uh 00:14:04.480 --> 00:14:05.790 align:start position:0% the the government issued ID system uh but<00:14:04.560> then<00:14:04.720> over<00:14:04.959> time<00:14:05.199> you<00:14:05.320> can<00:14:05.480> imagine 00:14:05.790 --> 00:14:05.800 align:start position:0% but then over time you can imagine 00:14:05.800 --> 00:14:07.470 align:start position:0% but then over time you can imagine importing<00:14:06.199> things<00:14:06.360> from<00:14:06.519> ethereum<00:14:07.120> importing 00:14:07.470 --> 00:14:07.480 align:start position:0% importing things from ethereum importing 00:14:07.480 --> 00:14:08.910 align:start position:0% importing things from ethereum importing things<00:14:07.639> from<00:14:07.839> Virtual<00:14:08.199> Worlds<00:14:08.560> importing 00:14:08.910 --> 00:14:08.920 align:start position:0% things from Virtual Worlds importing 00:14:08.920 --> 00:14:10.509 align:start position:0% things from Virtual Worlds importing bank<00:14:09.199> accounts<00:14:09.560> receipts<00:14:09.959> or<00:14:10.120> even<00:14:10.360> like 00:14:10.509 --> 00:14:10.519 align:start position:0% bank accounts receipts or even like 00:14:10.519 --> 00:14:12.470 align:start position:0% bank accounts receipts or even like actual<00:14:10.839> mathematical<00:14:11.360> proofs<00:14:11.639> and<00:14:12.079> keeping 00:14:12.470 --> 00:14:12.480 align:start position:0% actual mathematical proofs and keeping 00:14:12.480 --> 00:14:14.870 align:start position:0% actual mathematical proofs and keeping generating<00:14:12.959> statement<00:14:13.480> about<00:14:13.759> these<00:14:14.639> Okay 00:14:14.870 --> 00:14:14.880 align:start position:0% generating statement about these Okay 00:14:14.880 --> 00:14:16.230 align:start position:0% generating statement about these Okay the<00:14:15.079> third<00:14:15.240> challenge<00:14:15.519> we<00:14:15.639> had<00:14:15.759> is<00:14:15.920> making 00:14:16.230 --> 00:14:16.240 align:start position:0% the third challenge we had is making 00:14:16.240 --> 00:14:18.949 align:start position:0% the third challenge we had is making building<00:14:16.720> easy<00:14:17.600> um<00:14:18.040> this<00:14:18.160> is<00:14:18.399> what<00:14:18.560> it<00:14:18.720> looks 00:14:18.949 --> 00:14:18.959 align:start position:0% building easy um this is what it looks 00:14:18.959 --> 00:14:20.550 align:start position:0% building easy um this is what it looks like<00:14:19.160> to<00:14:19.399> put<00:14:19.680> together<00:14:19.880> a<00:14:20.040> sequence<00:14:20.399> of 00:14:20.550 --> 00:14:20.560 align:start position:0% like to put together a sequence of 00:14:20.560 --> 00:14:22.629 align:start position:0% like to put together a sequence of logical<00:14:20.959> up<00:14:21.240> codes<00:14:21.720> and<00:14:21.880> it's<00:14:22.160> extremely 00:14:22.629 --> 00:14:22.639 align:start position:0% logical up codes and it's extremely 00:14:22.639 --> 00:14:24.389 align:start position:0% logical up codes and it's extremely gnarly<00:14:23.199> don't<00:14:23.440> ask<00:14:23.600> us<00:14:23.880> why<00:14:24.040> why<00:14:24.160> we<00:14:24.279> have 00:14:24.389 --> 00:14:24.399 align:start position:0% gnarly don't ask us why why we have 00:14:24.399 --> 00:14:26.389 align:start position:0% gnarly don't ask us why why we have strings<00:14:24.800> it<00:14:24.920> should<00:14:25.079> be<00:14:25.240> pointers<00:14:26.000> um<00:14:26.120> it's<00:14:26.240> a 00:14:26.389 --> 00:14:26.399 align:start position:0% strings it should be pointers um it's a 00:14:26.399 --> 00:14:29.790 align:start position:0% strings it should be pointers um it's a whole<00:14:26.720> story<00:14:27.639> um<00:14:27.959> and<00:14:28.279> making<00:14:28.560> sense<00:14:28.839> of<00:14:29.240> pods 00:14:29.790 --> 00:14:29.800 align:start position:0% whole story um and making sense of pods 00:14:29.800 --> 00:14:31.749 align:start position:0% whole story um and making sense of pods or<00:14:30.079> crafting<00:14:30.480> them<00:14:30.680> becomes<00:14:31.079> very<00:14:31.320> tedious 00:14:31.749 --> 00:14:31.759 align:start position:0% or crafting them becomes very tedious 00:14:31.759 --> 00:14:33.710 align:start position:0% or crafting them becomes very tedious and<00:14:31.880> easy<00:14:32.079> to<00:14:32.240> get<00:14:32.360> wrong<00:14:32.759> right<00:14:33.120> the<00:14:33.240> users<00:14:33.560> of 00:14:33.710 --> 00:14:33.720 align:start position:0% and easy to get wrong right the users of 00:14:33.720 --> 00:14:35.470 align:start position:0% and easy to get wrong right the users of the<00:14:33.880> system<00:14:34.199> need<00:14:34.360> to<00:14:34.600> craft<00:14:34.880> a<00:14:35.000> sequence<00:14:35.320> of 00:14:35.470 --> 00:14:35.480 align:start position:0% the system need to craft a sequence of 00:14:35.480 --> 00:14:37.389 align:start position:0% the system need to craft a sequence of logical<00:14:35.800> up<00:14:36.000> code<00:14:36.160> to<00:14:36.279> make<00:14:36.360> a<00:14:36.480> new<00:14:36.639> pods<00:14:37.279> but 00:14:37.389 --> 00:14:37.399 align:start position:0% logical up code to make a new pods but 00:14:37.399 --> 00:14:38.509 align:start position:0% logical up code to make a new pods but on<00:14:37.560> top<00:14:37.720> of<00:14:37.839> that<00:14:37.959> they<00:14:38.040> need<00:14:38.160> to<00:14:38.240> make<00:14:38.360> sure 00:14:38.509 --> 00:14:38.519 align:start position:0% on top of that they need to make sure 00:14:38.519 --> 00:14:39.870 align:start position:0% on top of that they need to make sure that<00:14:38.639> the<00:14:38.800> statements<00:14:39.240> they<00:14:39.399> get<00:14:39.519> out<00:14:39.720> when 00:14:39.870 --> 00:14:39.880 align:start position:0% that the statements they get out when 00:14:39.880 --> 00:14:41.389 align:start position:0% that the statements they get out when they<00:14:40.000> receive<00:14:40.240> a<00:14:40.399> pod<00:14:40.720> actually<00:14:40.959> match<00:14:41.279> what 00:14:41.389 --> 00:14:41.399 align:start position:0% they receive a pod actually match what 00:14:41.399 --> 00:14:43.310 align:start position:0% they receive a pod actually match what they're<00:14:41.600> asking<00:14:41.839> to<00:14:41.959> be<00:14:42.120> proven<00:14:42.759> if<00:14:42.880> you<00:14:43.040> get 00:14:43.310 --> 00:14:43.320 align:start position:0% they're asking to be proven if you get 00:14:43.320 --> 00:14:45.150 align:start position:0% they're asking to be proven if you get this<00:14:43.920> you<00:14:44.040> know<00:14:44.360> all<00:14:44.480> of<00:14:44.600> these<00:14:44.759> logical 00:14:45.150 --> 00:14:45.160 align:start position:0% this you know all of these logical 00:14:45.160 --> 00:14:47.069 align:start position:0% this you know all of these logical statements<00:14:45.680> like<00:14:45.959> how<00:14:46.120> do<00:14:46.440> like<00:14:46.560> it's<00:14:46.759> hard<00:14:46.920> to 00:14:47.069 --> 00:14:47.079 align:start position:0% statements like how do like it's hard to 00:14:47.079 --> 00:14:48.710 align:start position:0% statements like how do like it's hard to know<00:14:47.360> whether<00:14:47.600> this<00:14:47.759> actually<00:14:48.040> proves<00:14:48.440> that 00:14:48.710 --> 00:14:48.720 align:start position:0% know whether this actually proves that 00:14:48.720 --> 00:14:50.949 align:start position:0% know whether this actually proves that the<00:14:48.920> person<00:14:49.639> matches<00:14:50.360> the<00:14:50.480> claim<00:14:50.759> you're 00:14:50.949 --> 00:14:50.959 align:start position:0% the person matches the claim you're 00:14:50.959 --> 00:14:53.509 align:start position:0% the person matches the claim you're trying<00:14:51.160> to<00:14:51.320> like<00:14:51.480> verify<00:14:52.240> so<00:14:53.000> what<00:14:53.160> we<00:14:53.279> did<00:14:53.399> is 00:14:53.509 --> 00:14:53.519 align:start position:0% trying to like verify so what we did is 00:14:53.519 --> 00:14:56.670 align:start position:0% trying to like verify so what we did is we<00:14:54.000> put<00:14:54.279> together<00:14:54.560> a<00:14:55.240> a<00:14:55.360> little<00:14:55.600> lisp<00:14:56.360> it's<00:14:56.480> a 00:14:56.670 --> 00:14:56.680 align:start position:0% we put together a a little lisp it's a 00:14:56.680 --> 00:14:58.030 align:start position:0% we put together a a little lisp it's a logic<00:14:57.040> programming<00:14:57.399> language<00:14:57.680> to<00:14:57.839> create 00:14:58.030 --> 00:14:58.040 align:start position:0% logic programming language to create 00:14:58.040 --> 00:15:00.069 align:start position:0% logic programming language to create pods<00:14:58.279> and<00:14:58.399> verify<00:14:58.759> them<00:14:59.399> uh<00:14:59.519> it's<00:14:59.600> a<00:14:59.759> list 00:15:00.069 --> 00:15:00.079 align:start position:0% pods and verify them uh it's a list 00:15:00.079 --> 00:15:01.710 align:start position:0% pods and verify them uh it's a list because<00:15:00.279> it's<00:15:00.440> really<00:15:00.680> easy<00:15:00.880> to<00:15:01.040> write<00:15:01.199> a<00:15:01.320> list 00:15:01.710 --> 00:15:01.720 align:start position:0% because it's really easy to write a list 00:15:01.720 --> 00:15:03.230 align:start position:0% because it's really easy to write a list versus<00:15:02.320> other<00:15:02.600> kinds<00:15:02.759> of<00:15:02.880> programming 00:15:03.230 --> 00:15:03.240 align:start position:0% versus other kinds of programming 00:15:03.240 --> 00:15:04.749 align:start position:0% versus other kinds of programming languages<00:15:03.920> and<00:15:04.040> it<00:15:04.120> has<00:15:04.240> an<00:15:04.320> interactive 00:15:04.749 --> 00:15:04.759 align:start position:0% languages and it has an interactive 00:15:04.759 --> 00:15:07.350 align:start position:0% languages and it has an interactive development<00:15:05.199> Loop<00:15:06.000> um<00:15:06.680> here's<00:15:06.920> what<00:15:07.079> it<00:15:07.160> looks 00:15:07.350 --> 00:15:07.360 align:start position:0% development Loop um here's what it looks 00:15:07.360 --> 00:15:08.870 align:start position:0% development Loop um here's what it looks like<00:15:07.519> so<00:15:07.680> here<00:15:07.839> I'm<00:15:07.959> just<00:15:08.120> making<00:15:08.360> a<00:15:08.560> pod 00:15:08.870 --> 00:15:08.880 align:start position:0% like so here I'm just making a pod 00:15:08.880 --> 00:15:10.069 align:start position:0% like so here I'm just making a pod technically<00:15:09.240> this<00:15:09.320> is<00:15:09.440> an<00:15:09.560> introduction 00:15:10.069 --> 00:15:10.079 align:start position:0% technically this is an introduction 00:15:10.079 --> 00:15:12.069 align:start position:0% technically this is an introduction Gadget<00:15:10.720> because<00:15:10.920> I'm<00:15:11.120> making<00:15:11.480> data<00:15:11.720> out<00:15:11.880> of 00:15:12.069 --> 00:15:12.079 align:start position:0% Gadget because I'm making data out of 00:15:12.079 --> 00:15:15.790 align:start position:0% Gadget because I'm making data out of nowhere<00:15:12.759> so<00:15:13.000> I<00:15:13.160> I<00:15:13.240> say<00:15:13.560> hey<00:15:14.440> key<00:15:14.720> AG<00:15:15.000> is<00:15:15.120> 26<00:15:15.560> zip 00:15:15.790 --> 00:15:15.800 align:start position:0% nowhere so I I say hey key AG is 26 zip 00:15:15.800 --> 00:15:17.670 align:start position:0% nowhere so I I say hey key AG is 26 zip code<00:15:15.959> is<00:15:16.120> such<00:15:16.360> ID<00:15:16.680> is<00:15:16.800> such<00:15:17.199> and<00:15:17.320> what<00:15:17.440> I<00:15:17.560> get 00:15:17.670 --> 00:15:17.680 align:start position:0% code is such ID is such and what I get 00:15:17.680 --> 00:15:19.389 align:start position:0% code is such ID is such and what I get is<00:15:17.800> a<00:15:17.920> bunch<00:15:18.120> of<00:15:18.279> value<00:15:18.560> off<00:15:18.759> statements 00:15:19.389 --> 00:15:19.399 align:start position:0% is a bunch of value off statements 00:15:19.399 --> 00:15:21.030 align:start position:0% is a bunch of value off statements including<00:15:19.839> a<00:15:20.000> magic<00:15:20.360> one<00:15:20.639> you<00:15:20.720> know<00:15:20.959> the 00:15:21.030 --> 00:15:21.040 align:start position:0% including a magic one you know the 00:15:21.040 --> 00:15:22.710 align:start position:0% including a magic one you know the underscore<00:15:21.519> signer<00:15:21.880> one<00:15:22.120> which<00:15:22.240> ones<00:15:22.480> to<00:15:22.600> who 00:15:22.710 --> 00:15:22.720 align:start position:0% underscore signer one which ones to who 00:15:22.720 --> 00:15:24.710 align:start position:0% underscore signer one which ones to who created<00:15:23.120> it<00:15:23.680> and<00:15:23.800> then<00:15:23.920> I<00:15:24.040> can<00:15:24.160> make<00:15:24.279> more<00:15:24.480> pods 00:15:24.710 --> 00:15:24.720 align:start position:0% created it and then I can make more pods 00:15:24.720 --> 00:15:26.550 align:start position:0% created it and then I can make more pods out<00:15:24.839> of<00:15:25.000> it<00:15:25.160> so<00:15:25.560> let's<00:15:25.720> go<00:15:25.839> through<00:15:25.959> an<00:15:26.079> example 00:15:26.550 --> 00:15:26.560 align:start position:0% out of it so let's go through an example 00:15:26.560 --> 00:15:29.110 align:start position:0% out of it so let's go through an example here<00:15:26.959> I'm<00:15:27.079> going<00:15:27.240> to<00:15:27.360> make<00:15:27.480> a<00:15:27.680> pod<00:15:28.000> that<00:15:28.160> says<00:15:28.680> I 00:15:29.110 --> 00:15:29.120 align:start position:0% here I'm going to make a pod that says I 00:15:29.120 --> 00:15:32.430 align:start position:0% here I'm going to make a pod that says I have<00:15:29.720> both<00:15:30.199> an<00:15:30.519> ID<00:15:30.920> card<00:15:31.240> and<00:15:31.360> a<00:15:31.519> payub<00:15:32.240> where 00:15:32.430 --> 00:15:32.440 align:start position:0% have both an ID card and a payub where 00:15:32.440 --> 00:15:34.949 align:start position:0% have both an ID card and a payub where the<00:15:32.560> user<00:15:32.800> ID<00:15:33.040> is<00:15:33.199> the<00:15:33.319> same<00:15:33.560> on<00:15:33.800> both<00:15:34.519> and<00:15:34.720> my 00:15:34.949 --> 00:15:34.959 align:start position:0% the user ID is the same on both and my 00:15:34.959 --> 00:15:37.829 align:start position:0% the user ID is the same on both and my age<00:15:35.199> is<00:15:35.360> over<00:15:35.720> 18<00:15:36.720> and<00:15:37.319> uh<00:15:37.440> I<00:15:37.519> think<00:15:37.680> that's 00:15:37.829 --> 00:15:37.839 align:start position:0% age is over 18 and uh I think that's 00:15:37.839 --> 00:15:39.870 align:start position:0% age is over 18 and uh I think that's about<00:15:38.040> it<00:15:38.199> and<00:15:38.279> I<00:15:38.399> reveal<00:15:38.720> my<00:15:38.839> salary<00:15:39.399> right<00:15:39.720> so 00:15:39.870 --> 00:15:39.880 align:start position:0% about it and I reveal my salary right so 00:15:39.880 --> 00:15:41.269 align:start position:0% about it and I reveal my salary right so first<00:15:40.079> what<00:15:40.199> I'll<00:15:40.360> do<00:15:40.480> is<00:15:40.560> I'll<00:15:40.720> query<00:15:41.000> for<00:15:41.160> a 00:15:41.269 --> 00:15:41.279 align:start position:0% first what I'll do is I'll query for a 00:15:41.279 --> 00:15:42.710 align:start position:0% first what I'll do is I'll query for a pod<00:15:41.519> using<00:15:41.759> the<00:15:41.959> Pod<00:15:42.240> question<00:15:42.480> mark 00:15:42.710 --> 00:15:42.720 align:start position:0% pod using the Pod question mark 00:15:42.720 --> 00:15:44.269 align:start position:0% pod using the Pod question mark statement<00:15:43.079> saying<00:15:43.319> I<00:15:43.399> want<00:15:43.480> a<00:15:43.600> pod<00:15:43.839> that<00:15:43.959> has 00:15:44.269 --> 00:15:44.279 align:start position:0% statement saying I want a pod that has 00:15:44.279 --> 00:15:46.430 align:start position:0% statement saying I want a pod that has an<00:15:44.519> age<00:15:44.959> value<00:15:45.279> a<00:15:45.399> zip<00:15:45.600> code<00:15:45.759> value<00:15:45.959> and<00:15:46.040> an<00:15:46.160> ID 00:15:46.430 --> 00:15:46.440 align:start position:0% an age value a zip code value and an ID 00:15:46.440 --> 00:15:47.790 align:start position:0% an age value a zip code value and an ID value<00:15:46.680> and<00:15:46.759> I<00:15:46.839> don't<00:15:47.240> I<00:15:47.319> don't<00:15:47.440> care<00:15:47.600> about 00:15:47.790 --> 00:15:47.800 align:start position:0% value and I don't I don't care about 00:15:47.800 --> 00:15:49.509 align:start position:0% value and I don't I don't care about anything<00:15:48.040> else<00:15:48.519> and<00:15:48.639> I<00:15:48.759> bind<00:15:49.040> them<00:15:49.160> to<00:15:49.319> these 00:15:49.509 --> 00:15:49.519 align:start position:0% anything else and I bind them to these 00:15:49.519 --> 00:15:51.430 align:start position:0% anything else and I bind them to these variables<00:15:50.240> then<00:15:50.360> I<00:15:50.480> do<00:15:50.639> the<00:15:50.759> same<00:15:51.079> thing<00:15:51.240> for 00:15:51.430 --> 00:15:51.440 align:start position:0% variables then I do the same thing for 00:15:51.440 --> 00:15:53.350 align:start position:0% variables then I do the same thing for another<00:15:51.720> part<00:15:51.959> that<00:15:52.040> has<00:15:52.160> a<00:15:52.279> salary<00:15:53.040> a<00:15:53.160> Time 00:15:53.350 --> 00:15:53.360 align:start position:0% another part that has a salary a Time 00:15:53.360 --> 00:15:55.110 align:start position:0% another part that has a salary a Time stem<00:15:53.560> issue<00:15:53.759> in<00:15:53.880> an<00:15:54.000> ID<00:15:54.639> and<00:15:54.759> I'm<00:15:54.880> going<00:15:54.959> to 00:15:55.110 --> 00:15:55.120 align:start position:0% stem issue in an ID and I'm going to 00:15:55.120 --> 00:15:57.470 align:start position:0% stem issue in an ID and I'm going to reveal<00:15:55.560> zip<00:15:55.839> code<00:15:56.040> salary<00:15:56.399> time<00:15:56.600> stem<00:15:56.800> issued 00:15:57.470 --> 00:15:57.480 align:start position:0% reveal zip code salary time stem issued 00:15:57.480 --> 00:15:59.389 align:start position:0% reveal zip code salary time stem issued by<00:15:57.800> with<00:15:57.959> the<00:15:58.079> same<00:15:58.319> key<00:15:58.600> name<00:15:59.079> and<00:15:59.199> I'm<00:15:59.279> going 00:15:59.389 --> 00:15:59.399 align:start position:0% by with the same key name and I'm going 00:15:59.399 --> 00:16:01.069 align:start position:0% by with the same key name and I'm going to<00:15:59.480> make<00:15:59.600> some<00:15:59.800> assertions<00:16:00.399> that<00:16:00.600> ages<00:16:00.880> over 00:16:01.069 --> 00:16:01.079 align:start position:0% to make some assertions that ages over 00:16:01.079 --> 00:16:03.269 align:start position:0% to make some assertions that ages over 18<00:16:01.480> and<00:16:01.560> then<00:16:01.680> I<00:16:01.800> do<00:16:01.920> a<00:16:02.000> drawing<00:16:02.399> I<00:16:02.519> say<00:16:02.759> ID<00:16:03.040> card 00:16:03.269 --> 00:16:03.279 align:start position:0% 18 and then I do a drawing I say ID card 00:16:03.279 --> 00:16:05.509 align:start position:0% 18 and then I do a drawing I say ID card ID<00:16:03.519> and<00:16:03.600> P<00:16:03.839> tub<00:16:04.040> ID<00:16:04.240> are<00:16:04.399> the<00:16:04.519> same<00:16:05.160> the<00:16:05.279> cool 00:16:05.509 --> 00:16:05.519 align:start position:0% ID and P tub ID are the same the cool 00:16:05.519 --> 00:16:07.389 align:start position:0% ID and P tub ID are the same the cool thing<00:16:05.800> is<00:16:06.160> I'm<00:16:06.279> going<00:16:06.399> to<00:16:06.480> able<00:16:06.720> to<00:16:07.000> to<00:16:07.160> prove 00:16:07.389 --> 00:16:07.399 align:start position:0% thing is I'm going to able to to prove 00:16:07.399 --> 00:16:09.350 align:start position:0% thing is I'm going to able to to prove that<00:16:07.560> ID<00:16:07.839> cord<00:16:08.079> ID<00:16:08.279> and<00:16:08.360> ptop<00:16:08.720> ID<00:16:08.920> are<00:16:09.040> the<00:16:09.120> same 00:16:09.350 --> 00:16:09.360 align:start position:0% that ID cord ID and ptop ID are the same 00:16:09.360 --> 00:16:10.910 align:start position:0% that ID cord ID and ptop ID are the same without<00:16:09.600> revealing<00:16:09.959> the<00:16:10.079> ID<00:16:10.680> that's<00:16:10.839> the 00:16:10.910 --> 00:16:10.920 align:start position:0% without revealing the ID that's the 00:16:10.920 --> 00:16:12.150 align:start position:0% without revealing the ID that's the thing<00:16:11.079> that's<00:16:11.240> very<00:16:11.399> powerful<00:16:11.759> about<00:16:11.920> it<00:16:12.079> what 00:16:12.150 --> 00:16:12.160 align:start position:0% thing that's very powerful about it what 00:16:12.160 --> 00:16:14.590 align:start position:0% thing that's very powerful about it what I<00:16:12.240> get<00:16:12.360> out<00:16:12.519> is<00:16:12.600> a<00:16:12.680> bunch<00:16:12.839> of<00:16:12.959> statements<00:16:13.880> and 00:16:14.590 --> 00:16:14.600 align:start position:0% I get out is a bunch of statements and 00:16:14.600 --> 00:16:16.069 align:start position:0% I get out is a bunch of statements and um<00:16:14.759> you<00:16:14.959> kind<00:16:15.079> of<00:16:15.199> have<00:16:15.279> to<00:16:15.399> trust<00:16:15.639> me<00:16:15.759> on<00:16:15.880> this 00:16:16.069 --> 00:16:16.079 align:start position:0% um you kind of have to trust me on this 00:16:16.079 --> 00:16:17.629 align:start position:0% um you kind of have to trust me on this because<00:16:16.199> it's<00:16:16.319> small<00:16:16.560> enough<00:16:16.959> but<00:16:17.160> the<00:16:17.279> ID<00:16:17.560> is 00:16:17.629 --> 00:16:17.639 align:start position:0% because it's small enough but the ID is 00:16:17.639 --> 00:16:19.509 align:start position:0% because it's small enough but the ID is not<00:16:17.800> revealed<00:16:18.079> in<00:16:18.160> the<00:16:18.279> Pod<00:16:18.519> itself<00:16:19.440> the 00:16:19.509 --> 00:16:19.519 align:start position:0% not revealed in the Pod itself the 00:16:19.519 --> 00:16:21.309 align:start position:0% not revealed in the Pod itself the fourth<00:16:19.800> challenge<00:16:20.120> we<00:16:20.240> had<00:16:20.440> is<00:16:20.800> multiparty 00:16:21.309 --> 00:16:21.319 align:start position:0% fourth challenge we had is multiparty 00:16:21.319 --> 00:16:23.509 align:start position:0% fourth challenge we had is multiparty POD<00:16:21.560> creation<00:16:22.319> so<00:16:22.519> today<00:16:22.920> if<00:16:23.040> you're<00:16:23.160> on<00:16:23.279> the 00:16:23.509 --> 00:16:23.519 align:start position:0% POD creation so today if you're on the 00:16:23.519 --> 00:16:25.230 align:start position:0% POD creation so today if you're on the right<00:16:23.800> side<00:16:24.160> like<00:16:24.319> the<00:16:24.440> little<00:16:24.600> Smiley<00:16:25.000> guy 00:16:25.230 --> 00:16:25.240 align:start position:0% right side like the little Smiley guy 00:16:25.240 --> 00:16:27.509 align:start position:0% right side like the little Smiley guy there<00:16:25.680> the<00:16:25.839> red<00:16:26.040> pods<00:16:26.279> are<00:16:26.519> private<00:16:27.079> right<00:16:27.399> you 00:16:27.509 --> 00:16:27.519 align:start position:0% there the red pods are private right you 00:16:27.519 --> 00:16:29.470 align:start position:0% there the red pods are private right you only<00:16:27.720> see<00:16:28.000> what's<00:16:28.160> in<00:16:28.279> the<00:16:28.440> yellow<00:16:28.720> pod 00:16:29.470 --> 00:16:29.480 align:start position:0% only see what's in the yellow pod 00:16:29.480 --> 00:16:31.430 align:start position:0% only see what's in the yellow pod but<00:16:29.880> if<00:16:30.000> you're<00:16:30.199> the<00:16:30.319> person<00:16:30.560> on<00:16:30.680> the<00:16:30.880> left<00:16:31.360> and 00:16:31.430 --> 00:16:31.440 align:start position:0% but if you're the person on the left and 00:16:31.440 --> 00:16:33.470 align:start position:0% but if you're the person on the left and you're<00:16:32.040> putting<00:16:32.440> the<00:16:32.639> proof<00:16:33.040> together<00:16:33.279> you 00:16:33.470 --> 00:16:33.480 align:start position:0% you're putting the proof together you 00:16:33.480 --> 00:16:35.110 align:start position:0% you're putting the proof together you actually<00:16:33.839> leak<00:16:34.199> you<00:16:34.319> get<00:16:34.480> leaked<00:16:34.880> the<00:16:35.000> the 00:16:35.110 --> 00:16:35.120 align:start position:0% actually leak you get leaked the the 00:16:35.120 --> 00:16:37.430 align:start position:0% actually leak you get leaked the the input<00:16:35.519> pods<00:16:36.519> so<00:16:36.720> what<00:16:36.880> we<00:16:36.959> want<00:16:37.040> to<00:16:37.120> be<00:16:37.240> able<00:16:37.360> to 00:16:37.430 --> 00:16:37.440 align:start position:0% input pods so what we want to be able to 00:16:37.440 --> 00:16:40.110 align:start position:0% input pods so what we want to be able to do<00:16:37.560> is<00:16:37.720> ENT<00:16:38.040> put<00:16:38.160> a<00:16:38.360> box<00:16:38.839> around<00:16:39.480> proof 00:16:40.110 --> 00:16:40.120 align:start position:0% do is ENT put a box around proof 00:16:40.120 --> 00:16:41.829 align:start position:0% do is ENT put a box around proof calculation<00:16:41.120> I'm<00:16:41.240> I'm<00:16:41.399> talking<00:16:41.600> about<00:16:41.759> the 00:16:41.829 --> 00:16:41.839 align:start position:0% calculation I'm I'm talking about the 00:16:41.839 --> 00:16:44.189 align:start position:0% calculation I'm I'm talking about the formal<00:16:42.240> proof<00:16:42.519> not<00:16:42.639> the<00:16:42.759> Z<00:16:43.120> proof<00:16:43.720> such<00:16:44.040> that 00:16:44.189 --> 00:16:44.199 align:start position:0% formal proof not the Z proof such that 00:16:44.199 --> 00:16:45.790 align:start position:0% formal proof not the Z proof such that the<00:16:44.319> input<00:16:44.560> pots<00:16:44.759> are<00:16:44.880> not<00:16:45.000> leaked<00:16:45.399> across<00:16:45.680> the 00:16:45.790 --> 00:16:45.800 align:start position:0% the input pots are not leaked across the 00:16:45.800 --> 00:16:49.069 align:start position:0% the input pots are not leaked across the party<00:16:46.279> right<00:16:46.959> and<00:16:47.959> um<00:16:48.279> we<00:16:48.399> were<00:16:48.600> hoping<00:16:48.839> to<00:16:48.959> get 00:16:49.069 --> 00:16:49.079 align:start position:0% party right and um we were hoping to get 00:16:49.079 --> 00:16:51.350 align:start position:0% party right and um we were hoping to get a<00:16:49.199> demo<00:16:49.440> of<00:16:49.519> this<00:16:49.680> by<00:16:49.800> defon<00:16:50.319> but<00:16:50.480> of<00:16:50.600> course<00:16:51.160> um 00:16:51.350 --> 00:16:51.360 align:start position:0% a demo of this by defon but of course um 00:16:51.360 --> 00:16:53.150 align:start position:0% a demo of this by defon but of course um it<00:16:51.480> did<00:16:51.639> not<00:16:51.839> happen<00:16:52.319> the<00:16:52.440> rest<00:16:52.680> happened<00:16:53.040> but 00:16:53.150 --> 00:16:53.160 align:start position:0% it did not happen the rest happened but 00:16:53.160 --> 00:16:55.710 align:start position:0% it did not happen the rest happened but not<00:16:53.399> that<00:16:54.160> um<00:16:54.480> so<00:16:54.920> the<00:16:55.000> way<00:16:55.120> you<00:16:55.240> solve<00:16:55.519> this<00:16:55.639> is 00:16:55.710 --> 00:16:55.720 align:start position:0% not that um so the way you solve this is 00:16:55.720 --> 00:16:57.150 align:start position:0% not that um so the way you solve this is you<00:16:55.839> execute<00:16:56.199> logical<00:16:56.560> operation<00:16:56.920> into 00:16:57.150 --> 00:16:57.160 align:start position:0% you execute logical operation into 00:16:57.160 --> 00:16:59.189 align:start position:0% you execute logical operation into either<00:16:57.399> multiparty<00:16:57.920> fhe<00:16:58.399> or<00:16:58.600> or<00:16:58.959> something 00:16:59.189 --> 00:16:59.199 align:start position:0% either multiparty fhe or or something 00:16:59.199 --> 00:17:01.069 align:start position:0% either multiparty fhe or or something like<00:16:59.360> verifiable<00:16:59.839> Garb<00:17:00.079> build<00:17:00.279> circuit<00:17:00.680> or<00:17:00.839> or 00:17:01.069 --> 00:17:01.079 align:start position:0% like verifiable Garb build circuit or or 00:17:01.079 --> 00:17:03.790 align:start position:0% like verifiable Garb build circuit or or coark<00:17:02.079> um<00:17:02.519> in<00:17:02.639> order<00:17:02.880> to<00:17:03.000> do<00:17:03.199> this<00:17:03.399> you<00:17:03.600> also 00:17:03.790 --> 00:17:03.800 align:start position:0% coark um in order to do this you also 00:17:03.800 --> 00:17:05.429 align:start position:0% coark um in order to do this you also need<00:17:03.959> to<00:17:04.120> crack<00:17:04.480> verifiable<00:17:05.079> fully 00:17:05.429 --> 00:17:05.439 align:start position:0% need to crack verifiable fully 00:17:05.439 --> 00:17:06.909 align:start position:0% need to crack verifiable fully homomorphic<00:17:05.919> encryption<00:17:06.600> without 00:17:06.909 --> 00:17:06.919 align:start position:0% homomorphic encryption without 00:17:06.919 --> 00:17:08.829 align:start position:0% homomorphic encryption without multiplicative<00:17:07.520> overhead<00:17:07.959> which<00:17:08.079> is<00:17:08.199> tricky 00:17:08.829 --> 00:17:08.839 align:start position:0% multiplicative overhead which is tricky 00:17:08.839 --> 00:17:10.230 align:start position:0% multiplicative overhead which is tricky I<00:17:08.919> won't<00:17:09.120> talk<00:17:09.280> too<00:17:09.400> much<00:17:09.600> about<00:17:09.839> this<00:17:10.039> but<00:17:10.160> if 00:17:10.230 --> 00:17:10.240 align:start position:0% I won't talk too much about this but if 00:17:10.240 --> 00:17:11.350 align:start position:0% I won't talk too much about this but if you're<00:17:10.439> interested<00:17:10.880> come<00:17:11.039> to<00:17:11.199> the 00:17:11.350 --> 00:17:11.360 align:start position:0% you're interested come to the 00:17:11.360 --> 00:17:13.710 align:start position:0% you're interested come to the programmable<00:17:11.839> cryptography<00:17:12.360> Cs<00:17:12.799> on<00:17:12.919> Friday 00:17:13.710 --> 00:17:13.720 align:start position:0% programmable cryptography Cs on Friday 00:17:13.720 --> 00:17:16.029 align:start position:0% programmable cryptography Cs on Friday so<00:17:14.520> that<00:17:14.720> spot<00:17:15.000> two<00:17:15.240> it's<00:17:15.360> a<00:17:15.480> system<00:17:15.760> that<00:17:15.880> can 00:17:16.029 --> 00:17:16.039 align:start position:0% so that spot two it's a system that can 00:17:16.039 --> 00:17:18.470 align:start position:0% so that spot two it's a system that can import<00:17:16.480> data<00:17:17.360> um<00:17:17.720> that<00:17:17.839> is<00:17:17.959> cryptographic 00:17:18.470 --> 00:17:18.480 align:start position:0% import data um that is cryptographic 00:17:18.480 --> 00:17:20.270 align:start position:0% import data um that is cryptographic regardless<00:17:18.959> where<00:17:19.079> it<00:17:19.160> comes<00:17:19.400> from<00:17:19.880> enables 00:17:20.270 --> 00:17:20.280 align:start position:0% regardless where it comes from enables 00:17:20.280 --> 00:17:21.990 align:start position:0% regardless where it comes from enables deep<00:17:20.520> computational<00:17:21.120> graphs<00:17:21.679> and<00:17:21.799> then<00:17:21.919> you 00:17:21.990 --> 00:17:22.000 align:start position:0% deep computational graphs and then you 00:17:22.000 --> 00:17:23.630 align:start position:0% deep computational graphs and then you can<00:17:22.400> you<00:17:22.480> can<00:17:22.640> export<00:17:23.079> whatever<00:17:23.360> view<00:17:23.559> you 00:17:23.630 --> 00:17:23.640 align:start position:0% can you can export whatever view you 00:17:23.640 --> 00:17:25.630 align:start position:0% can you can export whatever view you want<00:17:23.760> on<00:17:23.839> the<00:17:24.000> data<00:17:24.480> with<00:17:24.600> a<00:17:24.720> six<00:17:25.120> proof<00:17:25.319> to<00:17:25.400> a 00:17:25.630 --> 00:17:25.640 align:start position:0% want on the data with a six proof to a 00:17:25.640 --> 00:17:28.429 align:start position:0% want on the data with a six proof to a verifier<00:17:26.640> um<00:17:26.880> it's<00:17:27.079> logic<00:17:27.439> based<00:17:28.120> both<00:17:28.319> for 00:17:28.429 --> 00:17:28.439 align:start position:0% verifier um it's logic based both for 00:17:28.439 --> 00:17:31.230 align:start position:0% verifier um it's logic based both for its<00:17:28.559> claim<00:17:28.960> its<00:17:29.440> operation<00:17:30.440> um<00:17:30.799> and<00:17:30.960> has<00:17:31.120> a 00:17:31.230 --> 00:17:31.240 align:start position:0% its claim its operation um and has a 00:17:31.240 --> 00:17:32.470 align:start position:0% its claim its operation um and has a bunch<00:17:31.400> of<00:17:31.480> cool<00:17:31.640> features<00:17:31.960> it's<00:17:32.080> in<00:17:32.240> active 00:17:32.470 --> 00:17:32.480 align:start position:0% bunch of cool features it's in active 00:17:32.480 --> 00:17:34.029 align:start position:0% bunch of cool features it's in active development<00:17:33.000> right<00:17:33.120> now<00:17:33.400> we<00:17:33.520> hope<00:17:33.720> we'll<00:17:33.919> have 00:17:34.029 --> 00:17:34.039 align:start position:0% development right now we hope we'll have 00:17:34.039 --> 00:17:36.630 align:start position:0% development right now we hope we'll have a<00:17:34.200> production<00:17:34.840> ready<00:17:35.160> version<00:17:35.559> by<00:17:35.760> end<00:17:35.960> of<00:17:36.120> 25 00:17:36.630 --> 00:17:36.640 align:start position:0% a production ready version by end of 25 00:17:36.640 --> 00:17:37.870 align:start position:0% a production ready version by end of 25 and<00:17:36.919> we'll<00:17:37.080> probably<00:17:37.280> go<00:17:37.400> through<00:17:37.520> a<00:17:37.600> bunch<00:17:37.760> of 00:17:37.870 --> 00:17:37.880 align:start position:0% and we'll probably go through a bunch of 00:17:37.880 --> 00:17:39.310 align:start position:0% and we'll probably go through a bunch of pilot<00:17:38.160> throughout<00:17:38.400> the<00:17:38.520> year<00:17:39.080> if<00:17:39.160> you're 00:17:39.310 --> 00:17:39.320 align:start position:0% pilot throughout the year if you're 00:17:39.320 --> 00:17:41.590 align:start position:0% pilot throughout the year if you're interested<00:17:39.679> to<00:17:39.799> learn<00:17:40.039> more<00:17:40.280> about<00:17:40.520> it<00:17:41.320> uh<00:17:41.440> so 00:17:41.590 --> 00:17:41.600 align:start position:0% interested to learn more about it uh so 00:17:41.600 --> 00:17:42.789 align:start position:0% interested to learn more about it uh so first<00:17:41.799> if<00:17:41.880> you're<00:17:42.000> interested<00:17:42.280> in<00:17:42.400> pod<00:17:42.600> one 00:17:42.789 --> 00:17:42.799 align:start position:0% first if you're interested in pod one 00:17:42.799 --> 00:17:44.310 align:start position:0% first if you're interested in pod one which<00:17:42.919> you<00:17:43.000> can<00:17:43.120> use<00:17:43.440> right<00:17:43.640> now<00:17:43.799> to<00:17:43.960> build 00:17:44.310 --> 00:17:44.320 align:start position:0% which you can use right now to build 00:17:44.320 --> 00:17:46.350 align:start position:0% which you can use right now to build stuff<00:17:45.000> it's<00:17:45.200> tomorrow<00:17:45.559> at<00:17:45.720> classroom<00:17:46.080> B<00:17:46.240> at 00:17:46.350 --> 00:17:46.360 align:start position:0% stuff it's tomorrow at classroom B at 00:17:46.360 --> 00:17:48.350 align:start position:0% stuff it's tomorrow at classroom B at 2:30<00:17:46.840> pm<00:17:47.280> and<00:17:47.360> if<00:17:47.440> you're<00:17:47.600> interested<00:17:47.919> in<00:17:48.080> part 00:17:48.350 --> 00:17:48.360 align:start position:0% 2:30 pm and if you're interested in part 00:17:48.360 --> 00:17:50.990 align:start position:0% 2:30 pm and if you're interested in part two<00:17:48.600> and<00:17:48.840> PEX<00:17:49.520> we're<00:17:49.720> running<00:17:50.000> a<00:17:50.440> pretty<00:17:50.679> long 00:17:50.990 --> 00:17:51.000 align:start position:0% two and PEX we're running a pretty long 00:17:51.000 --> 00:17:53.270 align:start position:0% two and PEX we're running a pretty long and<00:17:51.280> interesting<00:17:52.039> uh<00:17:52.160> workshop<00:17:52.679> on<00:17:52.919> Friday<00:17:53.200> at 00:17:53.270 --> 00:17:53.280 align:start position:0% and interesting uh workshop on Friday at 00:17:53.280 --> 00:17:55.149 align:start position:0% and interesting uh workshop on Friday at 12:30<00:17:53.799> p.m.<00:17:54.280> at<00:17:54.480> the<00:17:54.640> programmable 00:17:55.149 --> 00:17:55.159 align:start position:0% 12:30 p.m. at the programmable 00:17:55.159 --> 00:17:57.630 align:start position:0% 12:30 p.m. at the programmable cryptography<00:17:55.679> CLS<00:17:56.280> so<00:17:56.440> I'll<00:17:56.600> keep<00:17:56.880> the<00:17:57.240> the<00:17:57.360> C 00:17:57.630 --> 00:17:57.640 align:start position:0% cryptography CLS so I'll keep the the C 00:17:57.640 --> 00:17:59.470 align:start position:0% cryptography CLS so I'll keep the the C codes<00:17:58.000> up<00:17:58.200> for<00:17:58.360> a<00:17:58.440> little<00:17:58.640> bit 00:17:59.470 --> 00:17:59.480 align:start position:0% codes up for a little bit 00:17:59.480 --> 00:18:03.200 align:start position:0% codes up for a little bit um<00:17:59.760> and<00:17:59.880> then<00:18:00.200> I'll<00:18:00.320> be<00:18:00.480> done<00:18:00.720> so<00:18:00.919> thanks 00:18:03.200 --> 00:18:03.210 align:start position:0% um and then I'll be done so thanks 00:18:03.210 --> 00:18:06.909 align:start position:0% um and then I'll be done so thanks [Applause] 00:18:06.909 --> 00:18:06.919 align:start position:0% [Applause] 00:18:06.919 --> 00:18:09.789 align:start position:0% [Applause] guys<00:18:07.919> thank<00:18:08.120> you<00:18:08.320> so<00:18:08.520> much<00:18:08.799> Justin<00:18:09.360> and<00:18:09.640> we 00:18:09.789 --> 00:18:09.799 align:start position:0% guys thank you so much Justin and we 00:18:09.799 --> 00:18:11.549 align:start position:0% guys thank you so much Justin and we have<00:18:10.080> a<00:18:10.240> ton<00:18:10.520> of<00:18:10.720> questions<00:18:11.080> so<00:18:11.280> looking 00:18:11.549 --> 00:18:11.559 align:start position:0% have a ton of questions so looking 00:18:11.559 --> 00:18:13.230 align:start position:0% have a ton of questions so looking through<00:18:11.760> the<00:18:11.919> questions<00:18:12.360> and<00:18:12.840> start 00:18:13.230 --> 00:18:13.240 align:start position:0% through the questions and start 00:18:13.240 --> 00:18:17.149 align:start position:0% through the questions and start answering<00:18:13.679> them<00:18:14.120> we<00:18:14.240> have<00:18:14.400> 3 00:18:17.149 --> 00:18:17.159 align:start position:0% 00:18:17.159 --> 00:18:19.029 align:start position:0% minutes<00:18:18.159> oh<00:18:18.320> so<00:18:18.440> you're<00:18:18.559> not<00:18:18.679> going<00:18:18.760> to<00:18:18.880> read 00:18:19.029 --> 00:18:19.039 align:start position:0% minutes oh so you're not going to read 00:18:19.039 --> 00:18:20.830 align:start position:0% minutes oh so you're not going to read the<00:18:19.159> question<00:18:19.400> I<00:18:19.480> have<00:18:19.559> to<00:18:19.640> do<00:18:19.760> the<00:18:19.880> work<00:18:20.280> okay 00:18:20.830 --> 00:18:20.840 align:start position:0% the question I have to do the work okay 00:18:20.840 --> 00:18:23.270 align:start position:0% the question I have to do the work okay cool<00:18:21.840> all<00:18:22.000> right<00:18:22.480> uh<00:18:22.600> you<00:18:22.799> mentioned<00:18:23.080> first 00:18:23.270 --> 00:18:23.280 align:start position:0% cool all right uh you mentioned first 00:18:23.280 --> 00:18:25.110 align:start position:0% cool all right uh you mentioned first order<00:18:23.600> logic<00:18:23.919> also<00:18:24.159> second<00:18:24.400> order<00:18:24.840> those<00:18:24.960> are 00:18:25.110 --> 00:18:25.120 align:start position:0% order logic also second order those are 00:18:25.120 --> 00:18:26.510 align:start position:0% order logic also second order those are not<00:18:25.320> computable<00:18:25.840> Logics<00:18:26.159> they're<00:18:26.360> just 00:18:26.510 --> 00:18:26.520 align:start position:0% not computable Logics they're just 00:18:26.520 --> 00:18:28.110 align:start position:0% not computable Logics they're just computable<00:18:26.919> and<00:18:27.039> numerable<00:18:27.799> what<00:18:27.919> am<00:18:28.000> I 00:18:28.110 --> 00:18:28.120 align:start position:0% computable and numerable what am I 00:18:28.120 --> 00:18:29.870 align:start position:0% computable and numerable what am I missing<00:18:28.440> then<00:18:28.840> your<00:18:28.960> Computing<00:18:29.280> for<00:18:29.440> sure 00:18:29.870 --> 00:18:29.880 align:start position:0% missing then your Computing for sure 00:18:29.880 --> 00:18:32.350 align:start position:0% missing then your Computing for sure this<00:18:30.080> this<00:18:30.200> is<00:18:30.480> true<00:18:31.120> so<00:18:31.400> our<00:18:31.640> logic<00:18:31.919> so<00:18:32.120> far<00:18:32.280> is 00:18:32.350 --> 00:18:32.360 align:start position:0% this this is true so our logic so far is 00:18:32.360 --> 00:18:34.950 align:start position:0% this this is true so our logic so far is a<00:18:32.520> bastard<00:18:33.120> logic<00:18:33.760> it's<00:18:33.880> a<00:18:34.039> logic<00:18:34.440> that<00:18:34.559> is<00:18:34.760> not 00:18:34.950 --> 00:18:34.960 align:start position:0% a bastard logic it's a logic that is not 00:18:34.960 --> 00:18:36.070 align:start position:0% a bastard logic it's a logic that is not actually<00:18:35.200> the<00:18:35.320> kind<00:18:35.480> of<00:18:35.600> logic<00:18:35.919> that 00:18:36.070 --> 00:18:36.080 align:start position:0% actually the kind of logic that 00:18:36.080 --> 00:18:38.470 align:start position:0% actually the kind of logic that logicians<00:18:36.559> use<00:18:37.240> so<00:18:37.559> an<00:18:37.760> active<00:18:38.080> area<00:18:38.360> of 00:18:38.470 --> 00:18:38.480 align:start position:0% logicians use so an active area of 00:18:38.480 --> 00:18:41.110 align:start position:0% logicians use so an active area of research<00:18:38.880> is<00:18:39.039> figuring<00:18:39.400> out<00:18:39.840> how<00:18:40.000> do<00:18:40.159> we 00:18:41.110 --> 00:18:41.120 align:start position:0% research is figuring out how do we 00:18:41.120 --> 00:18:43.070 align:start position:0% research is figuring out how do we essentially<00:18:41.720> like<00:18:42.039> have<00:18:42.200> a<00:18:42.320> logical<00:18:42.760> system 00:18:43.070 --> 00:18:43.080 align:start position:0% essentially like have a logical system 00:18:43.080 --> 00:18:44.950 align:start position:0% essentially like have a logical system that<00:18:43.200> is<00:18:43.360> also<00:18:43.600> computable<00:18:44.240> in<00:18:44.360> a<00:18:44.480> way<00:18:44.640> that<00:18:44.799> is 00:18:44.950 --> 00:18:44.960 align:start position:0% that is also computable in a way that is 00:18:44.960 --> 00:18:47.070 align:start position:0% that is also computable in a way that is like<00:18:45.159> as<00:18:45.320> sound<00:18:45.559> and<00:18:45.679> complete<00:18:46.039> as<00:18:46.240> possible 00:18:47.070 --> 00:18:47.080 align:start position:0% like as sound and complete as possible 00:18:47.080 --> 00:18:48.590 align:start position:0% like as sound and complete as possible and<00:18:47.520> um<00:18:47.720> if<00:18:47.840> you<00:18:47.919> have<00:18:48.080> asked<00:18:48.240> that<00:18:48.400> question 00:18:48.590 --> 00:18:48.600 align:start position:0% and um if you have asked that question 00:18:48.600 --> 00:18:49.830 align:start position:0% and um if you have asked that question please<00:18:48.760> come<00:18:48.960> talk<00:18:49.120> to<00:18:49.200> me<00:18:49.400> because<00:18:49.559> we're 00:18:49.830 --> 00:18:49.840 align:start position:0% please come talk to me because we're 00:18:49.840 --> 00:18:54.630 align:start position:0% please come talk to me because we're very<00:18:50.039> interested<00:18:50.440> in<00:18:50.640> that<00:18:51.480> so<00:18:51.760> great 00:18:54.630 --> 00:18:54.640 align:start position:0% 00:18:54.640 --> 00:18:56.549 align:start position:0% question<00:18:55.640> running<00:18:55.919> this<00:18:56.080> is<00:18:56.159> the<00:18:56.280> browser 00:18:56.549 --> 00:18:56.559 align:start position:0% question running this is the browser 00:18:56.559 --> 00:18:57.590 align:start position:0% question running this is the browser means<00:18:56.720> you<00:18:56.799> need<00:18:56.919> to<00:18:57.000> trust<00:18:57.200> the<00:18:57.280> server<00:18:57.520> to 00:18:57.590 --> 00:18:57.600 align:start position:0% means you need to trust the server to 00:18:57.600 --> 00:18:59.909 align:start position:0% means you need to trust the server to serve<00:18:57.840> a<00:18:57.919> non-compromised<00:18:58.480> version<00:18:58.840> of<00:18:59.000> the 00:18:59.909 --> 00:18:59.919 align:start position:0% serve a non-compromised version of the 00:18:59.919 --> 00:19:01.750 align:start position:0% serve a non-compromised version of the software<00:19:00.919> uh<00:19:01.000> how<00:19:01.159> will<00:19:01.320> this<00:19:01.440> work<00:19:01.600> in 00:19:01.750 --> 00:19:01.760 align:start position:0% software uh how will this work in 00:19:01.760 --> 00:19:02.789 align:start position:0% software uh how will this work in practice<00:19:02.039> are<00:19:02.120> we<00:19:02.240> going<00:19:02.360> to<00:19:02.440> have<00:19:02.559> an<00:19:02.640> open 00:19:02.789 --> 00:19:02.799 align:start position:0% practice are we going to have an open 00:19:02.799 --> 00:19:06.909 align:start position:0% practice are we going to have an open ster<00:19:03.200> for<00:19:03.400> pod<00:19:03.880> processing<00:19:05.039> um<00:19:06.039> okay<00:19:06.280> so<00:19:06.640> if<00:19:06.799> we 00:19:06.909 --> 00:19:06.919 align:start position:0% ster for pod processing um okay so if we 00:19:06.919 --> 00:19:08.669 align:start position:0% ster for pod processing um okay so if we go<00:19:07.120> down<00:19:07.280> to<00:19:07.440> the<00:19:07.559> level<00:19:07.840> of<00:19:08.080> like<00:19:08.440> well<00:19:08.600> you 00:19:08.669 --> 00:19:08.679 align:start position:0% go down to the level of like well you 00:19:08.679 --> 00:19:10.430 align:start position:0% go down to the level of like well you have<00:19:08.760> to<00:19:08.880> trust<00:19:09.120> the<00:19:09.240> software<00:19:09.600> you<00:19:09.720> use<00:19:10.320> I 00:19:10.430 --> 00:19:10.440 align:start position:0% have to trust the software you use I 00:19:10.440 --> 00:19:12.310 align:start position:0% have to trust the software you use I have<00:19:10.520> a<00:19:10.679> bad<00:19:10.840> news<00:19:11.039> for<00:19:11.240> you<00:19:11.640> which<00:19:11.760> is<00:19:12.000> it's<00:19:12.120> a 00:19:12.310 --> 00:19:12.320 align:start position:0% have a bad news for you which is it's a 00:19:12.320 --> 00:19:14.909 align:start position:0% have a bad news for you which is it's a problem<00:19:12.640> for<00:19:13.039> all<00:19:13.240> of<00:19:13.760> the<00:19:13.880> industry<00:19:14.280> so<00:19:14.480> far 00:19:14.909 --> 00:19:14.919 align:start position:0% problem for all of the industry so far 00:19:14.919 --> 00:19:16.230 align:start position:0% problem for all of the industry so far so<00:19:15.159> the<00:19:15.240> way<00:19:15.360> you'll<00:19:15.559> solve<00:19:15.799> this<00:19:15.919> is<00:19:16.039> the<00:19:16.159> way 00:19:16.230 --> 00:19:16.240 align:start position:0% so the way you'll solve this is the way 00:19:16.240 --> 00:19:17.390 align:start position:0% so the way you'll solve this is the way you'll<00:19:16.400> solve<00:19:16.640> everything<00:19:16.880> else<00:19:17.120> so<00:19:17.240> I<00:19:17.280> don't 00:19:17.390 --> 00:19:17.400 align:start position:0% you'll solve everything else so I don't 00:19:17.400 --> 00:19:19.510 align:start position:0% you'll solve everything else so I don't think<00:19:17.520> I<00:19:17.600> want<00:19:17.679> to<00:19:17.799> answer<00:19:18.080> this 00:19:19.510 --> 00:19:19.520 align:start position:0% think I want to answer this 00:19:19.520 --> 00:19:22.350 align:start position:0% think I want to answer this question<00:19:20.520> what's 00:19:22.350 --> 00:19:22.360 align:start position:0% question what's 00:19:22.360 --> 00:19:24.750 align:start position:0% question what's next<00:19:23.360> can<00:19:23.440> you<00:19:23.559> scroll<00:19:23.919> or 00:19:24.750 --> 00:19:24.760 align:start position:0% next can you scroll or 00:19:24.760 --> 00:19:27.149 align:start position:0% next can you scroll or something<00:19:25.760> no<00:19:25.919> they'll<00:19:26.120> scroll<00:19:26.400> it<00:19:26.520> from 00:19:27.149 --> 00:19:27.159 align:start position:0% something no they'll scroll it from 00:19:27.159 --> 00:19:30.230 align:start position:0% something no they'll scroll it from there<00:19:28.159> I<00:19:28.240> got<00:19:28.400> there<00:19:28.799> late<00:19:29.039> what<00:19:29.159> is<00:19:29.320> this<00:19:29.480> for 00:19:30.230 --> 00:19:30.240 align:start position:0% there I got there late what is this for 00:19:30.240 --> 00:19:33.029 align:start position:0% there I got there late what is this for um<00:19:31.120> it's<00:19:31.240> for<00:19:31.440> making<00:19:31.720> data<00:19:32.039> useful<00:19:32.520> Beyond 00:19:33.029 --> 00:19:33.039 align:start position:0% um it's for making data useful Beyond 00:19:33.039 --> 00:19:34.350 align:start position:0% um it's for making data useful Beyond this<00:19:33.200> stuff<00:19:33.480> that<00:19:33.559> we<00:19:33.720> have<00:19:33.919> right<00:19:34.039> now<00:19:34.200> where 00:19:34.350 --> 00:19:34.360 align:start position:0% this stuff that we have right now where 00:19:34.360 --> 00:19:35.830 align:start position:0% this stuff that we have right now where we<00:19:34.520> just<00:19:34.640> store<00:19:34.919> them<00:19:35.000> in<00:19:35.159> databases<00:19:35.640> and<00:19:35.720> we 00:19:35.830 --> 00:19:35.840 align:start position:0% we just store them in databases and we 00:19:35.840 --> 00:19:41.110 align:start position:0% we just store them in databases and we sell<00:19:36.039> them<00:19:36.159> to<00:19:36.280> open 00:19:41.110 --> 00:19:41.120 align:start position:0% 00:19:41.120 --> 00:19:43.909 align:start position:0% AI<00:19:42.120> okay<00:19:42.320> I<00:19:42.400> think<00:19:42.559> that's<00:19:42.760> it<00:19:43.039> thank<00:19:43.240> you<00:19:43.760> all 00:19:43.909 --> 00:19:43.919 align:start position:0% AI okay I think that's it thank you all 00:19:43.919 --> 00:19:45.909 align:start position:0% AI okay I think that's it thank you all right<00:19:44.120> thank<00:19:44.240> you<00:19:44.360> so<00:19:44.559> much<00:19:44.799> Justin<00:19:45.159> for<00:19:45.679> this 00:19:45.909 --> 00:19:45.919 align:start position:0% right thank you so much Justin for this 00:19:45.919 --> 00:19:48.760 align:start position:0% right thank you so much Justin for this session