WEBVTT Kind: captions Language: en 00:00:01.760 --> 00:00:03.909 align:start position:0% I<00:00:01.880> think<00:00:02.040> this<00:00:02.200> works<00:00:02.520> perfect<00:00:02.919> thank<00:00:03.080> you 00:00:03.909 --> 00:00:03.919 align:start position:0% I think this works perfect thank you 00:00:03.919 --> 00:00:08.350 align:start position:0% I think this works perfect thank you okay<00:00:04.240> so<00:00:05.520> we<00:00:06.520> have<00:00:06.720> about<00:00:06.960> an<00:00:07.040> hour<00:00:07.200> and<00:00:07.319> a<00:00:07.439> half 00:00:08.350 --> 00:00:08.360 align:start position:0% okay so we have about an hour and a half 00:00:08.360 --> 00:00:12.230 align:start position:0% okay so we have about an hour and a half um<00:00:09.080> and<00:00:10.080> the<00:00:10.280> content<00:00:10.719> here<00:00:10.920> is<00:00:11.120> one<00:00:11.360> workshop 00:00:12.230 --> 00:00:12.240 align:start position:0% um and the content here is one workshop 00:00:12.240 --> 00:00:15.509 align:start position:0% um and the content here is one workshop for<00:00:12.559> about<00:00:13.480> 50<00:00:13.799> minutes<00:00:14.599> and<00:00:14.679> then<00:00:14.839> we'll<00:00:15.120> have 00:00:15.509 --> 00:00:15.519 align:start position:0% for about 50 minutes and then we'll have 00:00:15.519 --> 00:00:18.710 align:start position:0% for about 50 minutes and then we'll have three<00:00:15.799> Li<00:00:16.039> in<00:00:16.279> talks<00:00:16.800> from<00:00:17.039> my<00:00:17.240> co-hosts<00:00:18.119> Arno 00:00:18.710 --> 00:00:18.720 align:start position:0% three Li in talks from my co-hosts Arno 00:00:18.720 --> 00:00:22.590 align:start position:0% three Li in talks from my co-hosts Arno ahmmad<00:00:19.279> aush<00:00:19.600> Gupta<00:00:19.960> and<00:00:20.080> Kevin<00:00:20.359> quack<00:00:21.480> um<00:00:22.480> I 00:00:22.590 --> 00:00:22.600 align:start position:0% ahmmad aush Gupta and Kevin quack um I 00:00:22.600 --> 00:00:23.910 align:start position:0% ahmmad aush Gupta and Kevin quack um I hope<00:00:22.760> we're<00:00:22.920> going<00:00:23.039> to<00:00:23.160> be<00:00:23.320> able<00:00:23.480> to<00:00:23.599> figure 00:00:23.910 --> 00:00:23.920 align:start position:0% hope we're going to be able to figure 00:00:23.920 --> 00:00:25.029 align:start position:0% hope we're going to be able to figure this<00:00:24.080> one<00:00:24.240> out<00:00:24.480> because<00:00:24.680> otherwise<00:00:24.960> it's 00:00:25.029 --> 00:00:25.039 align:start position:0% this one out because otherwise it's 00:00:25.039 --> 00:00:26.390 align:start position:0% this one out because otherwise it's going<00:00:25.119> to<00:00:25.240> be<00:00:25.359> really<00:00:25.560> awkward<00:00:25.960> you<00:00:26.080> guys<00:00:26.199> will 00:00:26.390 --> 00:00:26.400 align:start position:0% going to be really awkward you guys will 00:00:26.400 --> 00:00:28.310 align:start position:0% going to be really awkward you guys will all<00:00:26.560> have<00:00:26.679> to<00:00:26.840> like<00:00:26.960> sit<00:00:27.199> next<00:00:27.359> to<00:00:27.480> me<00:00:28.000> show<00:00:28.160> you 00:00:28.310 --> 00:00:28.320 align:start position:0% all have to like sit next to me show you 00:00:28.320 --> 00:00:32.350 align:start position:0% all have to like sit next to me show you the<00:00:28.439> screen 00:00:32.350 --> 00:00:32.360 align:start position:0% 00:00:32.360 --> 00:00:36.470 align:start position:0% so<00:00:33.120> um<00:00:33.640> what<00:00:33.760> we'll<00:00:34.000> talk<00:00:34.239> about<00:00:34.520> today<00:00:35.360> is<00:00:36.360> you 00:00:36.470 --> 00:00:36.480 align:start position:0% so um what we'll talk about today is you 00:00:36.480 --> 00:00:38.869 align:start position:0% so um what we'll talk about today is you might<00:00:36.640> have<00:00:36.840> seen<00:00:37.239> from<00:00:37.960> Branch<00:00:38.320> presentation 00:00:38.869 --> 00:00:38.879 align:start position:0% might have seen from Branch presentation 00:00:38.879 --> 00:00:40.549 align:start position:0% might have seen from Branch presentation you<00:00:39.000> know<00:00:39.200> the<00:00:39.440> the<00:00:39.559> last<00:00:39.840> talk<00:00:40.200> during<00:00:40.440> the 00:00:40.549 --> 00:00:40.559 align:start position:0% you know the the last talk during the 00:00:40.559 --> 00:00:43.389 align:start position:0% you know the the last talk during the CLS<00:00:41.039> gup<00:00:41.480> was<00:00:41.600> talking<00:00:41.879> about<00:00:42.160> how<00:00:42.800> um<00:00:43.160> our 00:00:43.389 --> 00:00:43.399 align:start position:0% CLS gup was talking about how um our 00:00:43.399 --> 00:00:45.549 align:start position:0% CLS gup was talking about how um our mental<00:00:43.800> model<00:00:44.120> has<00:00:44.280> evolved<00:00:44.680> over<00:00:44.960> time<00:00:45.360> as 00:00:45.549 --> 00:00:45.559 align:start position:0% mental model has evolved over time as 00:00:45.559 --> 00:00:47.630 align:start position:0% mental model has evolved over time as we've<00:00:45.719> been<00:00:45.840> working<00:00:46.120> on<00:00:46.280> different<00:00:46.640> projects 00:00:47.630 --> 00:00:47.640 align:start position:0% we've been working on different projects 00:00:47.640 --> 00:00:50.229 align:start position:0% we've been working on different projects and<00:00:48.160> one<00:00:48.320> of<00:00:48.480> the<00:00:48.680> big<00:00:49.039> update<00:00:49.559> that<00:00:49.760> happened 00:00:50.229 --> 00:00:50.239 align:start position:0% and one of the big update that happened 00:00:50.239 --> 00:00:53.790 align:start position:0% and one of the big update that happened about<00:00:50.440> a<00:00:50.600> year<00:00:50.800> ago<00:00:51.320> was<00:00:52.320> um<00:00:53.079> making<00:00:53.559> this 00:00:53.790 --> 00:00:53.800 align:start position:0% about a year ago was um making this 00:00:53.800 --> 00:00:57.270 align:start position:0% about a year ago was um making this concept<00:00:54.239> of<00:00:54.440> PCD<00:00:55.359> a<00:00:55.480> bit<00:00:55.680> more<00:00:56.199> usable<00:00:56.840> using 00:00:57.270 --> 00:00:57.280 align:start position:0% concept of PCD a bit more usable using 00:00:57.280 --> 00:01:00.150 align:start position:0% concept of PCD a bit more usable using pods<00:00:58.000> and<00:00:58.199> GBC<00:00:58.760> so<00:00:59.039> the<00:00:59.160> tickets<00:00:59.440> you<00:00:59.519> have<00:00:59.640> for 00:01:00.150 --> 00:01:00.160 align:start position:0% pods and GBC so the tickets you have for 00:01:00.160 --> 00:01:01.509 align:start position:0% pods and GBC so the tickets you have for con<00:01:00.280> the<00:01:00.359> frogs<00:01:00.680> you<00:01:00.760> have<00:01:01.000> for<00:01:01.199> Devcon 00:01:01.509 --> 00:01:01.519 align:start position:0% con the frogs you have for Devcon 00:01:01.519 --> 00:01:03.630 align:start position:0% con the frogs you have for Devcon they're<00:01:01.640> all<00:01:01.920> pods<00:01:02.559> you<00:01:02.680> can<00:01:02.840> operate<00:01:03.160> on<00:01:03.359> pods 00:01:03.630 --> 00:01:03.640 align:start position:0% they're all pods you can operate on pods 00:01:03.640 --> 00:01:06.390 align:start position:0% they're all pods you can operate on pods via<00:01:04.159> these<00:01:04.960> cryptographic<00:01:05.640> machineries 00:01:06.390 --> 00:01:06.400 align:start position:0% via these cryptographic machineries 00:01:06.400 --> 00:01:10.710 align:start position:0% via these cryptographic machineries called<00:01:06.920> GPC<00:01:07.920> and<00:01:08.799> this<00:01:09.040> summer<00:01:09.600> we<00:01:09.759> started 00:01:10.710 --> 00:01:10.720 align:start position:0% called GPC and this summer we started 00:01:10.720 --> 00:01:12.070 align:start position:0% called GPC and this summer we started kind<00:01:10.840> of<00:01:10.960> like<00:01:11.159> being<00:01:11.479> getting<00:01:11.759> a<00:01:11.880> bit 00:01:12.070 --> 00:01:12.080 align:start position:0% kind of like being getting a bit 00:01:12.080 --> 00:01:14.109 align:start position:0% kind of like being getting a bit frustrated<00:01:12.799> with<00:01:13.000> b<00:01:13.200> and<00:01:13.280> GPC<00:01:13.840> because<00:01:14.000> it 00:01:14.109 --> 00:01:14.119 align:start position:0% frustrated with b and GPC because it 00:01:14.119 --> 00:01:17.190 align:start position:0% frustrated with b and GPC because it felt<00:01:14.320> like<00:01:14.479> they<00:01:14.960> were<00:01:15.960> powerful<00:01:16.479> yet<00:01:16.680> brittle 00:01:17.190 --> 00:01:17.200 align:start position:0% felt like they were powerful yet brittle 00:01:17.200 --> 00:01:19.910 align:start position:0% felt like they were powerful yet brittle and<00:01:17.960> not<00:01:18.200> expressive<00:01:18.680> enough<00:01:19.360> so<00:01:19.560> what<00:01:19.680> we've 00:01:19.910 --> 00:01:19.920 align:start position:0% and not expressive enough so what we've 00:01:19.920 --> 00:01:22.069 align:start position:0% and not expressive enough so what we've been<00:01:20.119> working<00:01:20.479> through<00:01:21.320> um<00:01:21.520> over<00:01:21.759> the<00:01:21.920> last 00:01:22.069 --> 00:01:22.079 align:start position:0% been working through um over the last 00:01:22.079 --> 00:01:24.550 align:start position:0% been working through um over the last four<00:01:22.320> months<00:01:23.040> is<00:01:23.159> an<00:01:23.360> upgrade<00:01:23.720> to<00:01:23.840> that<00:01:24.040> system 00:01:24.550 --> 00:01:24.560 align:start position:0% four months is an upgrade to that system 00:01:24.560 --> 00:01:25.789 align:start position:0% four months is an upgrade to that system and<00:01:24.680> there's<00:01:24.840> a<00:01:24.960> lot<00:01:25.079> of<00:01:25.240> like<00:01:25.400> interesting 00:01:25.789 --> 00:01:25.799 align:start position:0% and there's a lot of like interesting 00:01:25.799 --> 00:01:27.749 align:start position:0% and there's a lot of like interesting challenges<00:01:26.280> that<00:01:27.040> that<00:01:27.240> we<00:01:27.320> have<00:01:27.479> had<00:01:27.600> to 00:01:27.749 --> 00:01:27.759 align:start position:0% challenges that that we have had to 00:01:27.759 --> 00:01:29.910 align:start position:0% challenges that that we have had to solve<00:01:28.520> so<00:01:28.920> what<00:01:29.040> I'll<00:01:29.240> go<00:01:29.360> through<00:01:29.520> today<00:01:29.799> is 00:01:29.910 --> 00:01:29.920 align:start position:0% solve so what I'll go through today is 00:01:29.920 --> 00:01:32.069 align:start position:0% solve so what I'll go through today is is<00:01:30.040> kind<00:01:30.159> of<00:01:30.320> talking<00:01:30.920> about<00:01:31.680> how<00:01:31.880> that 00:01:32.069 --> 00:01:32.079 align:start position:0% is kind of talking about how that 00:01:32.079 --> 00:01:33.950 align:start position:0% is kind of talking about how that happened<00:01:32.600> and<00:01:32.720> then<00:01:32.840> we'll<00:01:33.000> do<00:01:33.119> a<00:01:33.240> bunch<00:01:33.479> of 00:01:33.950 --> 00:01:33.960 align:start position:0% happened and then we'll do a bunch of 00:01:33.960 --> 00:01:39.030 align:start position:0% happened and then we'll do a bunch of live<00:01:34.240> coding<00:01:35.320> um<00:01:36.320> that<00:01:36.520> always<00:01:36.759> goes<00:01:37.079> well<00:01:38.040> uh 00:01:39.030 --> 00:01:39.040 align:start position:0% live coding um that always goes well uh 00:01:39.040 --> 00:01:40.870 align:start position:0% live coding um that always goes well uh and<00:01:39.119> then<00:01:39.320> afterwards<00:01:39.960> we'll<00:01:40.240> have<00:01:40.479> our<00:01:40.720> no 00:01:40.870 --> 00:01:40.880 align:start position:0% and then afterwards we'll have our no 00:01:40.880 --> 00:01:43.350 align:start position:0% and then afterwards we'll have our no and<00:01:40.960> aad<00:01:41.520> talk<00:01:41.799> about<00:01:42.240> the<00:01:42.360> circuits<00:01:43.079> that<00:01:43.200> we 00:01:43.350 --> 00:01:43.360 align:start position:0% and aad talk about the circuits that we 00:01:43.360 --> 00:01:44.950 align:start position:0% and aad talk about the circuits that we had<00:01:43.520> to<00:01:43.759> write<00:01:44.000> the<00:01:44.119> zero<00:01:44.320> know<00:01:44.560> circuits<00:01:44.840> that 00:01:44.950 --> 00:01:44.960 align:start position:0% had to write the zero know circuits that 00:01:44.960 --> 00:01:46.510 align:start position:0% had to write the zero know circuits that we<00:01:45.040> had<00:01:45.119> to<00:01:45.240> write<00:01:45.439> to<00:01:45.560> make<00:01:45.759> this<00:01:45.920> new<00:01:46.119> PL<00:01:46.360> two 00:01:46.510 --> 00:01:46.520 align:start position:0% we had to write to make this new PL two 00:01:46.520 --> 00:01:48.830 align:start position:0% we had to write to make this new PL two system<00:01:46.759> work<00:01:47.560> then<00:01:47.719> a<00:01:47.880> US<00:01:48.119> CTA<00:01:48.439> will<00:01:48.560> come<00:01:48.719> and 00:01:48.830 --> 00:01:48.840 align:start position:0% system work then a US CTA will come and 00:01:48.840 --> 00:01:51.590 align:start position:0% system work then a US CTA will come and talk<00:01:49.040> about<00:01:49.240> ZK<00:01:49.600> email<00:01:50.560> um<00:01:50.880> which<00:01:51.000> is<00:01:51.119> a<00:01:51.280> way<00:01:51.399> to 00:01:51.590 --> 00:01:51.600 align:start position:0% talk about ZK email um which is a way to 00:01:51.600 --> 00:01:54.149 align:start position:0% talk about ZK email um which is a way to import<00:01:52.399> emails<00:01:52.920> which<00:01:53.240> actually<00:01:53.520> are 00:01:54.149 --> 00:01:54.159 align:start position:0% import emails which actually are 00:01:54.159 --> 00:01:56.510 align:start position:0% import emails which actually are cryptographically<00:01:54.960> signed<00:01:55.520> in<00:01:55.640> a<00:01:55.799> way<00:01:55.960> we<00:01:56.079> can 00:01:56.510 --> 00:01:56.520 align:start position:0% cryptographically signed in a way we can 00:01:56.520 --> 00:01:58.429 align:start position:0% cryptographically signed in a way we can make<00:01:56.680> use<00:01:56.880> of<00:01:57.079> them<00:01:57.560> and<00:01:57.680> it<00:01:57.880> fits<00:01:58.200> very 00:01:58.429 --> 00:01:58.439 align:start position:0% make use of them and it fits very 00:01:58.439 --> 00:02:00.029 align:start position:0% make use of them and it fits very philosophically<00:01:59.240> with<00:01:59.439> with<00:01:59.520> the<00:01:59.600> rest<00:01:59.920> to 00:02:00.029 --> 00:02:00.039 align:start position:0% philosophically with with the rest to 00:02:00.039 --> 00:02:03.630 align:start position:0% philosophically with with the rest to the<00:02:00.399> system<00:02:01.399> finally<00:02:01.719> we'll<00:02:02.000> have<00:02:02.840> Kevin<00:02:03.119> quar 00:02:03.630 --> 00:02:03.640 align:start position:0% the system finally we'll have Kevin quar 00:02:03.640 --> 00:02:05.830 align:start position:0% the system finally we'll have Kevin quar come<00:02:03.840> and<00:02:04.039> talk<00:02:04.280> about<00:02:04.560> how<00:02:04.920> we<00:02:05.159> build<00:02:05.680> the 00:02:05.830 --> 00:02:05.840 align:start position:0% come and talk about how we build the 00:02:05.840 --> 00:02:07.910 align:start position:0% come and talk about how we build the Cyber<00:02:06.159> frog<00:02:06.840> these<00:02:07.079> little<00:02:07.280> chips<00:02:07.640> you<00:02:07.759> might 00:02:07.910 --> 00:02:07.920 align:start position:0% Cyber frog these little chips you might 00:02:07.920 --> 00:02:10.190 align:start position:0% Cyber frog these little chips you might have<00:02:08.080> used<00:02:08.759> that<00:02:08.879> are<00:02:09.119> framed<00:02:09.720> throughout<00:02:10.039> the 00:02:10.190 --> 00:02:10.200 align:start position:0% have used that are framed throughout the 00:02:10.200 --> 00:02:11.750 align:start position:0% have used that are framed throughout the conference<00:02:10.759> where<00:02:10.879> you<00:02:11.000> can<00:02:11.160> get<00:02:11.280> some<00:02:11.480> rare 00:02:11.750 --> 00:02:11.760 align:start position:0% conference where you can get some rare 00:02:11.760 --> 00:02:14.270 align:start position:0% conference where you can get some rare frogs<00:02:12.200> from<00:02:12.480> so<00:02:12.640> today<00:02:12.879> it's<00:02:13.000> all<00:02:13.160> about<00:02:13.440> pods 00:02:14.270 --> 00:02:14.280 align:start position:0% frogs from so today it's all about pods 00:02:14.280 --> 00:02:16.110 align:start position:0% frogs from so today it's all about pods pod<00:02:14.599> one<00:02:15.000> pod<00:02:15.239> two<00:02:15.560> things<00:02:15.879> that<00:02:15.959> are 00:02:16.110 --> 00:02:16.120 align:start position:0% pod one pod two things that are 00:02:16.120 --> 00:02:17.710 align:start position:0% pod one pod two things that are philosophically<00:02:16.840> pods<00:02:17.160> that<00:02:17.239> we<00:02:17.360> don't<00:02:17.519> call 00:02:17.710 --> 00:02:17.720 align:start position:0% philosophically pods that we don't call 00:02:17.720 --> 00:02:19.910 align:start position:0% philosophically pods that we don't call pods<00:02:18.120> yet<00:02:18.680> it's<00:02:18.879> the<00:02:19.080> Pod 00:02:19.910 --> 00:02:19.920 align:start position:0% pods yet it's the Pod 00:02:19.920 --> 00:02:23.229 align:start position:0% pods yet it's the Pod Singularity<00:02:20.920> so<00:02:21.440> uh<00:02:21.560> that's<00:02:21.760> the<00:02:22.120> agenda<00:02:23.120> uh 00:02:23.229 --> 00:02:23.239 align:start position:0% Singularity so uh that's the agenda uh 00:02:23.239 --> 00:02:25.350 align:start position:0% Singularity so uh that's the agenda uh and<00:02:23.400> the<00:02:23.519> workshop<00:02:24.000> I<00:02:24.080> will<00:02:24.280> go<00:02:24.480> through<00:02:25.080> is 00:02:25.350 --> 00:02:25.360 align:start position:0% and the workshop I will go through is 00:02:25.360 --> 00:02:26.830 align:start position:0% and the workshop I will go through is has<00:02:25.560> three<00:02:25.760> part<00:02:26.040> the<00:02:26.120> first<00:02:26.280> one<00:02:26.440> is<00:02:26.560> I<00:02:26.640> will 00:02:26.830 --> 00:02:26.840 align:start position:0% has three part the first one is I will 00:02:26.840 --> 00:02:28.750 align:start position:0% has three part the first one is I will reuse<00:02:27.200> some<00:02:27.319> of<00:02:27.440> the<00:02:27.519> slides<00:02:27.879> from<00:02:28.040> the<00:02:28.239> talk<00:02:28.560> I 00:02:28.750 --> 00:02:28.760 align:start position:0% reuse some of the slides from the talk I 00:02:28.760 --> 00:02:30.350 align:start position:0% reuse some of the slides from the talk I gave<00:02:29.000> on<00:02:29.200> Wednesday 00:02:30.350 --> 00:02:30.360 align:start position:0% gave on Wednesday 00:02:30.360 --> 00:02:32.070 align:start position:0% gave on Wednesday um<00:02:30.680> if<00:02:30.959> this<00:02:31.040> is<00:02:31.200> boring<00:02:31.560> because<00:02:31.720> you've<00:02:31.920> seen 00:02:32.070 --> 00:02:32.080 align:start position:0% um if this is boring because you've seen 00:02:32.080 --> 00:02:34.110 align:start position:0% um if this is boring because you've seen it<00:02:32.200> already<00:02:32.519> just<00:02:32.720> boo<00:02:33.040> me<00:02:33.400> and<00:02:33.560> we<00:02:33.760> we'll<00:02:33.920> go 00:02:34.110 --> 00:02:34.120 align:start position:0% it already just boo me and we we'll go 00:02:34.120 --> 00:02:36.229 align:start position:0% it already just boo me and we we'll go faster<00:02:35.120> also<00:02:35.360> because<00:02:35.599> this<00:02:35.680> is<00:02:35.800> a<00:02:35.920> small 00:02:36.229 --> 00:02:36.239 align:start position:0% faster also because this is a small 00:02:36.239 --> 00:02:38.229 align:start position:0% faster also because this is a small classroom<00:02:36.720> one<00:02:36.920> affordance<00:02:37.440> we<00:02:37.560> have<00:02:37.680> is<00:02:38.040> feel 00:02:38.229 --> 00:02:38.239 align:start position:0% classroom one affordance we have is feel 00:02:38.239 --> 00:02:39.949 align:start position:0% classroom one affordance we have is feel free<00:02:38.440> to<00:02:38.599> stop<00:02:38.840> me<00:02:38.959> at<00:02:39.080> any<00:02:39.280> time<00:02:39.480> we're<00:02:39.680> not 00:02:39.949 --> 00:02:39.959 align:start position:0% free to stop me at any time we're not 00:02:39.959 --> 00:02:41.869 align:start position:0% free to stop me at any time we're not actually<00:02:40.159> going<00:02:40.280> to<00:02:40.400> do<00:02:40.560> set<00:02:40.879> time<00:02:41.120> Q&A<00:02:41.680> if<00:02:41.800> you 00:02:41.869 --> 00:02:41.879 align:start position:0% actually going to do set time Q&A if you 00:02:41.879 --> 00:02:43.990 align:start position:0% actually going to do set time Q&A if you have<00:02:41.959> a<00:02:42.080> question<00:02:42.319> just<00:02:42.480> raise<00:02:42.680> your<00:02:42.800> hand<00:02:43.640> um 00:02:43.990 --> 00:02:44.000 align:start position:0% have a question just raise your hand um 00:02:44.000 --> 00:02:45.190 align:start position:0% have a question just raise your hand um one<00:02:44.159> of 00:02:45.190 --> 00:02:45.200 align:start position:0% one of 00:02:45.200 --> 00:02:48.430 align:start position:0% one of the<00:02:46.200> the<00:02:46.319> AV<00:02:46.640> people<00:02:46.959> will<00:02:47.080> bring<00:02:47.280> you<00:02:47.720> a<00:02:47.920> a<00:02:48.080> mic 00:02:48.430 --> 00:02:48.440 align:start position:0% the the AV people will bring you a a mic 00:02:48.440 --> 00:02:50.390 align:start position:0% the the AV people will bring you a a mic and<00:02:48.560> we<00:02:48.640> can<00:02:48.760> go<00:02:48.920> through<00:02:49.040> the<00:02:49.200> question<00:02:50.159> um<00:02:50.280> so 00:02:50.390 --> 00:02:50.400 align:start position:0% and we can go through the question um so 00:02:50.400 --> 00:02:51.589 align:start position:0% and we can go through the question um so I'll<00:02:50.560> go<00:02:50.640> through<00:02:50.800> some<00:02:50.920> of<00:02:51.040> these<00:02:51.200> slides 00:02:51.589 --> 00:02:51.599 align:start position:0% I'll go through some of these slides 00:02:51.599 --> 00:02:54.309 align:start position:0% I'll go through some of these slides then<00:02:51.800> I'll<00:02:52.040> pull<00:02:52.239> up<00:02:52.680> uh<00:02:52.800> my<00:02:52.959> trusty<00:02:53.480> PEX<00:02:54.080> PEX 00:02:54.309 --> 00:02:54.319 align:start position:0% then I'll pull up uh my trusty PEX PEX 00:02:54.319 --> 00:02:55.949 align:start position:0% then I'll pull up uh my trusty PEX PEX is<00:02:54.440> a<00:02:54.560> Lis<00:02:54.840> repple<00:02:55.319> that<00:02:55.400> we<00:02:55.519> built<00:02:55.800> that<00:02:55.879> you 00:02:55.949 --> 00:02:55.959 align:start position:0% is a Lis repple that we built that you 00:02:55.959 --> 00:02:58.589 align:start position:0% is a Lis repple that we built that you can<00:02:56.080> use<00:02:56.200> to<00:02:56.360> make<00:02:56.560> pods<00:02:56.840> and<00:02:57.040> modify<00:02:57.440> them<00:02:57.680> Etc 00:02:58.589 --> 00:02:58.599 align:start position:0% can use to make pods and modify them Etc 00:02:58.599 --> 00:03:00.550 align:start position:0% can use to make pods and modify them Etc so<00:02:58.720> we'll<00:02:58.920> do<00:02:59.040> some<00:02:59.200> live<00:02:59.400> codings<00:03:00.200> and<00:03:00.360> if<00:03:00.440> we 00:03:00.550 --> 00:03:00.560 align:start position:0% so we'll do some live codings and if we 00:03:00.560 --> 00:03:02.869 align:start position:0% so we'll do some live codings and if we have<00:03:00.720> enough<00:03:01.040> time<00:03:01.319> I<00:03:01.400> want<00:03:01.519> to<00:03:01.640> show<00:03:01.879> you<00:03:02.319> how 00:03:02.869 --> 00:03:02.879 align:start position:0% have enough time I want to show you how 00:03:02.879 --> 00:03:04.789 align:start position:0% have enough time I want to show you how the<00:03:03.120> greater<00:03:03.560> than<00:03:03.840> logical<00:03:04.239> operation<00:03:04.599> in 00:03:04.789 --> 00:03:04.799 align:start position:0% the greater than logical operation in 00:03:04.799 --> 00:03:06.470 align:start position:0% the greater than logical operation in pod<00:03:05.040> is<00:03:05.159> implemented<00:03:05.640> across<00:03:05.920> the<00:03:06.000> whole<00:03:06.200> code 00:03:06.470 --> 00:03:06.480 align:start position:0% pod is implemented across the whole code 00:03:06.480 --> 00:03:08.430 align:start position:0% pod is implemented across the whole code base<00:03:06.959> to<00:03:07.120> kind<00:03:07.239> of<00:03:07.360> see<00:03:07.599> like<00:03:07.799> what<00:03:07.920> it<00:03:08.040> entails 00:03:08.430 --> 00:03:08.440 align:start position:0% base to kind of see like what it entails 00:03:08.440 --> 00:03:10.270 align:start position:0% base to kind of see like what it entails to<00:03:08.680> to<00:03:08.840> add<00:03:09.000> more<00:03:09.159> to<00:03:09.319> this 00:03:10.270 --> 00:03:10.280 align:start position:0% to to add more to this 00:03:10.280 --> 00:03:12.350 align:start position:0% to to add more to this logic<00:03:11.280> okay 00:03:12.350 --> 00:03:12.360 align:start position:0% logic okay 00:03:12.360 --> 00:03:15.390 align:start position:0% logic okay so<00:03:13.360> to<00:03:13.560> motivate<00:03:14.000> this<00:03:14.120> a<00:03:14.239> little<00:03:14.440> bit<00:03:14.799> our 00:03:15.390 --> 00:03:15.400 align:start position:0% so to motivate this a little bit our 00:03:15.400 --> 00:03:18.350 align:start position:0% so to motivate this a little bit our thesis<00:03:16.400> at<00:03:16.640> Park<00:03:17.000> is<00:03:17.200> that<00:03:17.840> programmable 00:03:18.350 --> 00:03:18.360 align:start position:0% thesis at Park is that programmable 00:03:18.360 --> 00:03:20.670 align:start position:0% thesis at Park is that programmable cryptography<00:03:19.040> enables<00:03:19.920> this<00:03:20.080> thing<00:03:20.319> we<00:03:20.480> call 00:03:20.670 --> 00:03:20.680 align:start position:0% cryptography enables this thing we call 00:03:20.680 --> 00:03:22.789 align:start position:0% cryptography enables this thing we call the<00:03:20.799> universal<00:03:21.319> data<00:03:21.599> adapter<00:03:22.360> almost<00:03:22.599> like<00:03:22.720> a 00:03:22.789 --> 00:03:22.799 align:start position:0% the universal data adapter almost like a 00:03:22.799 --> 00:03:25.070 align:start position:0% the universal data adapter almost like a turing<00:03:23.120> machine<00:03:23.400> moment<00:03:23.799> for<00:03:24.080> data<00:03:24.599> so<00:03:24.840> just 00:03:25.070 --> 00:03:25.080 align:start position:0% turing machine moment for data so just 00:03:25.080 --> 00:03:27.229 align:start position:0% turing machine moment for data so just like<00:03:25.720> we've<00:03:25.959> had<00:03:26.159> electronic<00:03:26.599> circuits<00:03:27.000> for<00:03:27.120> a 00:03:27.229 --> 00:03:27.239 align:start position:0% like we've had electronic circuits for a 00:03:27.239 --> 00:03:29.070 align:start position:0% like we've had electronic circuits for a long<00:03:27.440> time<00:03:27.720> but<00:03:27.840> it<00:03:27.959> took<00:03:28.319> like<00:03:28.560> the<00:03:28.720> correct 00:03:29.070 --> 00:03:29.080 align:start position:0% long time but it took like the correct 00:03:29.080 --> 00:03:31.190 align:start position:0% long time but it took like the correct mental<00:03:29.439> model<00:03:29.920> to<00:03:30.040> squeeze<00:03:30.400> the<00:03:30.560> most<00:03:30.840> out<00:03:31.000> of 00:03:31.190 --> 00:03:31.200 align:start position:0% mental model to squeeze the most out of 00:03:31.200 --> 00:03:32.830 align:start position:0% mental model to squeeze the most out of them<00:03:31.439> by<00:03:31.560> think<00:03:31.799> of<00:03:31.959> them<00:03:32.120> as<00:03:32.280> like<00:03:32.439> this<00:03:32.599> like 00:03:32.830 --> 00:03:32.840 align:start position:0% them by think of them as like this like 00:03:32.840 --> 00:03:34.710 align:start position:0% them by think of them as like this like abstract<00:03:33.360> machine<00:03:33.680> you<00:03:33.799> can<00:03:34.040> program 00:03:34.710 --> 00:03:34.720 align:start position:0% abstract machine you can program 00:03:34.720 --> 00:03:36.910 align:start position:0% abstract machine you can program similarly<00:03:35.159> we've<00:03:35.360> had<00:03:35.560> data<00:03:35.840> for<00:03:35.959> a<00:03:36.120> long<00:03:36.319> time 00:03:36.910 --> 00:03:36.920 align:start position:0% similarly we've had data for a long time 00:03:36.920 --> 00:03:38.750 align:start position:0% similarly we've had data for a long time but<00:03:37.080> it<00:03:37.159> seems<00:03:37.400> like<00:03:37.560> we<00:03:37.760> still<00:03:37.879> haven't<00:03:38.200> found 00:03:38.750 --> 00:03:38.760 align:start position:0% but it seems like we still haven't found 00:03:38.760 --> 00:03:40.550 align:start position:0% but it seems like we still haven't found the<00:03:38.920> right<00:03:39.120> abstraction<00:03:39.640> to<00:03:39.799> make<00:03:40.040> data<00:03:40.319> more 00:03:40.550 --> 00:03:40.560 align:start position:0% the right abstraction to make data more 00:03:40.560 --> 00:03:42.110 align:start position:0% the right abstraction to make data more than<00:03:40.799> dead<00:03:41.080> bits<00:03:41.480> that<00:03:41.599> are<00:03:41.799> hard<00:03:41.959> to 00:03:42.110 --> 00:03:42.120 align:start position:0% than dead bits that are hard to 00:03:42.120 --> 00:03:43.670 align:start position:0% than dead bits that are hard to interpret<00:03:42.640> outside<00:03:42.920> of<00:03:43.040> the<00:03:43.200> context<00:03:43.560> they 00:03:43.670 --> 00:03:43.680 align:start position:0% interpret outside of the context they 00:03:43.680 --> 00:03:46.710 align:start position:0% interpret outside of the context they were<00:03:43.879> created<00:03:44.239> in<00:03:45.239> um<00:03:45.519> and<00:03:46.239> what<00:03:46.480> what<00:03:46.599> we 00:03:46.710 --> 00:03:46.720 align:start position:0% were created in um and what what we 00:03:46.720 --> 00:03:48.830 align:start position:0% were created in um and what what we don't<00:03:46.920> claim<00:03:47.319> we<00:03:47.400> have<00:03:48.280> we<00:03:48.400> have<00:03:48.519> reached<00:03:48.760> the 00:03:48.830 --> 00:03:48.840 align:start position:0% don't claim we have we have reached the 00:03:48.840 --> 00:03:50.429 align:start position:0% don't claim we have we have reached the tring<00:03:49.120> machine<00:03:49.360> moment<00:03:49.640> for<00:03:49.799> data<00:03:50.120> this<00:03:50.200> is 00:03:50.429 --> 00:03:50.439 align:start position:0% tring machine moment for data this is 00:03:50.439 --> 00:03:53.949 align:start position:0% tring machine moment for data this is what<00:03:50.680> we<00:03:50.920> aspire<00:03:51.360> to<00:03:52.280> and<00:03:53.280> another<00:03:53.640> another 00:03:53.949 --> 00:03:53.959 align:start position:0% what we aspire to and another another 00:03:53.959 --> 00:03:55.949 align:start position:0% what we aspire to and another another goal<00:03:54.159> here<00:03:54.280> is<00:03:54.400> to<00:03:54.560> get<00:03:54.799> more<00:03:55.040> out<00:03:55.239> of<00:03:55.439> data<00:03:55.840> we 00:03:55.949 --> 00:03:55.959 align:start position:0% goal here is to get more out of data we 00:03:55.959 --> 00:03:58.069 align:start position:0% goal here is to get more out of data we are<00:03:56.040> in<00:03:56.159> a<00:03:56.319> world<00:03:56.720> that<00:03:57.200> where<00:03:57.400> data<00:03:57.640> gets<00:03:57.920> more 00:03:58.069 --> 00:03:58.079 align:start position:0% are in a world that where data gets more 00:03:58.079 --> 00:04:00.429 align:start position:0% are in a world that where data gets more and<00:03:58.239> more<00:03:58.560> valuable<00:03:59.360> yet<00:03:59.799> at<00:03:59.879> the<00:04:00.000> same<00:04:00.159> time 00:04:00.429 --> 00:04:00.439 align:start position:0% and more valuable yet at the same time 00:04:00.439 --> 00:04:01.869 align:start position:0% and more valuable yet at the same time data<00:04:00.680> gets<00:04:00.879> locked<00:04:01.159> up<00:04:01.280> more<00:04:01.400> and<00:04:01.519> more<00:04:01.640> into 00:04:01.869 --> 00:04:01.879 align:start position:0% data gets locked up more and more into 00:04:01.879 --> 00:04:03.869 align:start position:0% data gets locked up more and more into these<00:04:02.120> data<00:04:02.400> prisons<00:04:03.280> where<00:04:03.519> like<00:04:03.680> people 00:04:03.869 --> 00:04:03.879 align:start position:0% these data prisons where like people 00:04:03.879 --> 00:04:06.030 align:start position:0% these data prisons where like people want<00:04:04.000> to<00:04:04.159> protect<00:04:04.599> the<00:04:04.760> data<00:04:05.480> at<00:04:05.599> the<00:04:05.720> expense 00:04:06.030 --> 00:04:06.040 align:start position:0% want to protect the data at the expense 00:04:06.040 --> 00:04:09.190 align:start position:0% want to protect the data at the expense of<00:04:06.280> getting<00:04:06.640> less<00:04:06.879> out<00:04:07.040> of<00:04:07.159> it<00:04:07.799> one<00:04:08.760> one<00:04:08.920> idea 00:04:09.190 --> 00:04:09.200 align:start position:0% of getting less out of it one one idea 00:04:09.200 --> 00:04:11.750 align:start position:0% of getting less out of it one one idea I've<00:04:09.319> been<00:04:09.480> talking<00:04:09.760> about<00:04:10.640> uh<00:04:11.280> with<00:04:11.480> people 00:04:11.750 --> 00:04:11.760 align:start position:0% I've been talking about uh with people 00:04:11.760 --> 00:04:13.069 align:start position:0% I've been talking about uh with people at<00:04:11.920> Devcon 00:04:13.069 --> 00:04:13.079 align:start position:0% at Devcon 00:04:13.079 --> 00:04:16.469 align:start position:0% at Devcon is<00:04:14.079> Google<00:04:14.680> at<00:04:14.799> least<00:04:15.000> Google<00:04:15.280> search<00:04:16.040> is 00:04:16.469 --> 00:04:16.479 align:start position:0% is Google at least Google search is 00:04:16.479 --> 00:04:19.030 align:start position:0% is Google at least Google search is making<00:04:16.840> use<00:04:17.120> of<00:04:17.400> all<00:04:17.560> of<00:04:17.799> Public's<00:04:18.280> data<00:04:18.759> for 00:04:19.030 --> 00:04:19.040 align:start position:0% making use of all of Public's data for 00:04:19.040 --> 00:04:20.469 align:start position:0% making use of all of Public's data for multiple<00:04:19.519> people<00:04:19.840> you<00:04:19.959> know<00:04:20.079> like<00:04:20.239> what<00:04:20.359> they 00:04:20.469 --> 00:04:20.479 align:start position:0% multiple people you know like what they 00:04:20.479 --> 00:04:22.350 align:start position:0% multiple people you know like what they gave<00:04:20.680> you<00:04:20.799> is<00:04:20.959> like<00:04:21.239> bundling<00:04:21.639> a<00:04:21.799> database 00:04:22.350 --> 00:04:22.360 align:start position:0% gave you is like bundling a database 00:04:22.360 --> 00:04:23.430 align:start position:0% gave you is like bundling a database with<00:04:22.520> with<00:04:22.639> a<00:04:22.759> bunch<00:04:22.919> of<00:04:23.000> data<00:04:23.199> about<00:04:23.360> the 00:04:23.430 --> 00:04:23.440 align:start position:0% with with a bunch of data about the 00:04:23.440 --> 00:04:26.110 align:start position:0% with with a bunch of data about the world<00:04:23.639> that<00:04:23.759> you<00:04:23.880> can<00:04:24.000> query<00:04:24.919> Dropbox<00:04:25.919> is 00:04:26.110 --> 00:04:26.120 align:start position:0% world that you can query Dropbox is 00:04:26.120 --> 00:04:29.749 align:start position:0% world that you can query Dropbox is about<00:04:27.000> private<00:04:27.360> data<00:04:27.600> for<00:04:27.880> yourself<00:04:28.800> right<00:04:29.240> so 00:04:29.749 --> 00:04:29.759 align:start position:0% about private data for yourself right so 00:04:29.759 --> 00:04:32.670 align:start position:0% about private data for yourself right so if<00:04:29.840> we<00:04:30.039> do<00:04:30.280> draw<00:04:30.560> the<00:04:30.720> 2x<00:04:31.120> two<00:04:31.280> mckeny<00:04:31.840> Matrix 00:04:32.670 --> 00:04:32.680 align:start position:0% if we do draw the 2x two mckeny Matrix 00:04:32.680 --> 00:04:34.469 align:start position:0% if we do draw the 2x two mckeny Matrix is<00:04:32.840> there<00:04:33.160> all<00:04:33.360> of<00:04:33.600> private<00:04:33.960> data<00:04:34.199> for 00:04:34.469 --> 00:04:34.479 align:start position:0% is there all of private data for 00:04:34.479 --> 00:04:36.350 align:start position:0% is there all of private data for everybody<00:04:35.360> and<00:04:35.560> of<00:04:35.680> course<00:04:35.919> that<00:04:36.039> seems<00:04:36.280> a 00:04:36.350 --> 00:04:36.360 align:start position:0% everybody and of course that seems a 00:04:36.360 --> 00:04:38.230 align:start position:0% everybody and of course that seems a little<00:04:36.520> bit<00:04:36.680> silly<00:04:36.960> at<00:04:37.120> first<00:04:37.440> but<00:04:37.960> I<00:04:38.039> would 00:04:38.230 --> 00:04:38.240 align:start position:0% little bit silly at first but I would 00:04:38.240 --> 00:04:40.230 align:start position:0% little bit silly at first but I would like<00:04:38.360> to<00:04:38.520> have<00:04:38.639> a<00:04:38.759> system<00:04:39.000> that<00:04:39.160> I<00:04:39.240> can<00:04:39.440> ask<00:04:39.880> hey 00:04:40.230 --> 00:04:40.240 align:start position:0% like to have a system that I can ask hey 00:04:40.240 --> 00:04:42.390 align:start position:0% like to have a system that I can ask hey how<00:04:40.360> many<00:04:40.960> espressos<00:04:41.600> did<00:04:41.800> people<00:04:42.039> drink 00:04:42.390 --> 00:04:42.400 align:start position:0% how many espressos did people drink 00:04:42.400 --> 00:04:45.029 align:start position:0% how many espressos did people drink yesterday<00:04:43.039> and<00:04:43.160> we<00:04:43.280> for<00:04:43.440> sure<00:04:43.759> know<00:04:44.120> that<00:04:44.840> like 00:04:45.029 --> 00:04:45.039 align:start position:0% yesterday and we for sure know that like 00:04:45.039 --> 00:04:46.629 align:start position:0% yesterday and we for sure know that like we<00:04:45.160> we<00:04:45.280> have<00:04:45.440> like<00:04:45.560> a<00:04:45.720> pretty<00:04:45.919> good<00:04:46.160> appr 00:04:46.629 --> 00:04:46.639 align:start position:0% we we have like a pretty good appr 00:04:46.639 --> 00:04:48.070 align:start position:0% we we have like a pretty good appr approximation<00:04:47.199> of<00:04:47.360> this<00:04:47.560> across<00:04:47.840> all<00:04:47.960> the 00:04:48.070 --> 00:04:48.080 align:start position:0% approximation of this across all the 00:04:48.080 --> 00:04:50.430 align:start position:0% approximation of this across all the sqlite<00:04:48.639> databases<00:04:49.160> in<00:04:49.280> the<00:04:49.400> world<00:04:50.080> but<00:04:50.199> it's 00:04:50.430 --> 00:04:50.440 align:start position:0% sqlite databases in the world but it's 00:04:50.440 --> 00:04:52.830 align:start position:0% sqlite databases in the world but it's really<00:04:50.720> hard<00:04:51.000> to<00:04:51.160> be<00:04:51.280> able<00:04:51.479> to<00:04:52.160> ask<00:04:52.440> that 00:04:52.830 --> 00:04:52.840 align:start position:0% really hard to be able to ask that 00:04:52.840 --> 00:04:56.390 align:start position:0% really hard to be able to ask that question<00:04:54.199> because<00:04:55.199> data<00:04:55.600> has<00:04:55.840> these<00:04:56.120> like 00:04:56.390 --> 00:04:56.400 align:start position:0% question because data has these like 00:04:56.400 --> 00:04:57.950 align:start position:0% question because data has these like contradictory<00:04:57.039> push<00:04:57.199> and<00:04:57.360> pull<00:04:57.680> where<00:04:57.800> you're 00:04:57.950 --> 00:04:57.960 align:start position:0% contradictory push and pull where you're 00:04:57.960 --> 00:04:59.670 align:start position:0% contradictory push and pull where you're trying<00:04:58.160> to<00:04:58.360> secure<00:04:58.680> it<00:04:58.919> which<00:04:59.080> like<00:04:59.199> makes<00:04:59.479> it 00:04:59.670 --> 00:04:59.680 align:start position:0% trying to secure it which like makes it 00:04:59.680 --> 00:05:01.469 align:start position:0% trying to secure it which like makes it se<00:04:59.960> you<00:05:00.039> can<00:05:00.160> make<00:05:00.720> like<00:05:00.919> you<00:05:01.039> can<00:05:01.280> you<00:05:01.360> can 00:05:01.469 --> 00:05:01.479 align:start position:0% se you can make like you can you can 00:05:01.479 --> 00:05:03.390 align:start position:0% se you can make like you can you can extract<00:05:01.840> less<00:05:02.039> value<00:05:02.280> out<00:05:02.440> of<00:05:02.560> it<00:05:03.039> and<00:05:03.160> at<00:05:03.280> the 00:05:03.390 --> 00:05:03.400 align:start position:0% extract less value out of it and at the 00:05:03.400 --> 00:05:04.990 align:start position:0% extract less value out of it and at the same<00:05:03.600> time<00:05:03.880> the<00:05:04.000> way<00:05:04.120> to<00:05:04.320> extract<00:05:04.639> more<00:05:04.800> value 00:05:04.990 --> 00:05:05.000 align:start position:0% same time the way to extract more value 00:05:05.000 --> 00:05:06.110 align:start position:0% same time the way to extract more value out<00:05:05.120> of<00:05:05.240> data<00:05:05.479> is<00:05:05.600> to<00:05:05.759> kind<00:05:05.880> of<00:05:06.000> like 00:05:06.110 --> 00:05:06.120 align:start position:0% out of data is to kind of like 00:05:06.120 --> 00:05:07.990 align:start position:0% out of data is to kind of like centralize<00:05:06.639> them<00:05:06.759> in<00:05:06.880> one<00:05:07.160> place<00:05:07.880> which 00:05:07.990 --> 00:05:08.000 align:start position:0% centralize them in one place which 00:05:08.000 --> 00:05:10.550 align:start position:0% centralize them in one place which brings<00:05:08.520> a<00:05:08.639> whole<00:05:08.800> share<00:05:09.080> of<00:05:09.280> problem<00:05:10.120> so<00:05:10.440> yeah 00:05:10.550 --> 00:05:10.560 align:start position:0% brings a whole share of problem so yeah 00:05:10.560 --> 00:05:11.749 align:start position:0% brings a whole share of problem so yeah we<00:05:10.639> want<00:05:10.759> to<00:05:10.880> take<00:05:11.000> data<00:05:11.199> out<00:05:11.280> of<00:05:11.400> their<00:05:11.560> data 00:05:11.749 --> 00:05:11.759 align:start position:0% we want to take data out of their data 00:05:11.759 --> 00:05:13.029 align:start position:0% we want to take data out of their data prison<00:05:12.199> we<00:05:12.320> want<00:05:12.400> to<00:05:12.520> enable<00:05:12.880> more 00:05:13.029 --> 00:05:13.039 align:start position:0% prison we want to enable more 00:05:13.039 --> 00:05:15.710 align:start position:0% prison we want to enable more interoperability<00:05:13.840> and<00:05:13.960> usage<00:05:14.240> of<00:05:14.440> data<00:05:15.440> um 00:05:15.710 --> 00:05:15.720 align:start position:0% interoperability and usage of data um 00:05:15.720 --> 00:05:17.830 align:start position:0% interoperability and usage of data um and<00:05:15.840> in<00:05:15.960> doing<00:05:16.199> that<00:05:16.320> breakdown 00:05:17.830 --> 00:05:17.840 align:start position:0% and in doing that breakdown 00:05:17.840 --> 00:05:20.270 align:start position:0% and in doing that breakdown silos<00:05:18.840> um<00:05:19.240> and<00:05:19.360> one<00:05:19.479> more<00:05:19.680> thing<00:05:19.800> I'll<00:05:19.960> say 00:05:20.270 --> 00:05:20.280 align:start position:0% silos um and one more thing I'll say 00:05:20.280 --> 00:05:22.590 align:start position:0% silos um and one more thing I'll say here<00:05:20.639> is<00:05:20.880> that<00:05:21.479> we<00:05:21.600> want<00:05:21.759> to<00:05:21.880> be<00:05:22.000> able<00:05:22.160> to 00:05:22.590 --> 00:05:22.600 align:start position:0% here is that we want to be able to 00:05:22.600 --> 00:05:24.830 align:start position:0% here is that we want to be able to enable<00:05:22.919> a<00:05:23.160> pragmatic<00:05:23.759> route<00:05:24.199> towards<00:05:24.520> data 00:05:24.830 --> 00:05:24.840 align:start position:0% enable a pragmatic route towards data 00:05:24.840 --> 00:05:26.990 align:start position:0% enable a pragmatic route towards data ownership<00:05:25.840> in<00:05:25.960> the<00:05:26.120> world<00:05:26.360> where<00:05:26.520> data<00:05:26.759> keeps 00:05:26.990 --> 00:05:27.000 align:start position:0% ownership in the world where data keeps 00:05:27.000 --> 00:05:29.670 align:start position:0% ownership in the world where data keeps increasing<00:05:27.400> in<00:05:27.560> value<00:05:28.120> and<00:05:28.240> that<00:05:28.360> is<00:05:29.080> very<00:05:29.319> per 00:05:29.670 --> 00:05:29.680 align:start position:0% increasing in value and that is very per 00:05:29.680 --> 00:05:32.230 align:start position:0% increasing in value and that is very per ious<00:05:30.199> because<00:05:30.880> if<00:05:31.080> data<00:05:31.360> keeps<00:05:31.639> increasing<00:05:32.039> in 00:05:32.230 --> 00:05:32.240 align:start position:0% ious because if data keeps increasing in 00:05:32.240 --> 00:05:34.390 align:start position:0% ious because if data keeps increasing in value<00:05:32.720> yet<00:05:33.080> holding<00:05:33.479> your<00:05:33.639> data<00:05:33.919> means<00:05:34.240> your 00:05:34.390 --> 00:05:34.400 align:start position:0% value yet holding your data means your 00:05:34.400 --> 00:05:36.390 align:start position:0% value yet holding your data means your data<00:05:34.759> does<00:05:34.919> not<00:05:35.120> create<00:05:35.400> any<00:05:35.560> value<00:05:35.880> at<00:05:35.960> all 00:05:36.390 --> 00:05:36.400 align:start position:0% data does not create any value at all 00:05:36.400 --> 00:05:38.309 align:start position:0% data does not create any value at all the<00:05:36.600> incentive<00:05:37.120> to<00:05:37.400> to<00:05:37.520> hold<00:05:37.720> your<00:05:37.840> own<00:05:38.080> data 00:05:38.309 --> 00:05:38.319 align:start position:0% the incentive to to hold your own data 00:05:38.319 --> 00:05:40.550 align:start position:0% the incentive to to hold your own data just<00:05:38.479> keeps<00:05:38.720> decreasing<00:05:39.199> over<00:05:39.440> time<00:05:40.000> you<00:05:40.120> know 00:05:40.550 --> 00:05:40.560 align:start position:0% just keeps decreasing over time you know 00:05:40.560 --> 00:05:42.189 align:start position:0% just keeps decreasing over time you know so<00:05:40.759> we<00:05:40.880> want<00:05:41.000> to<00:05:41.160> be<00:05:41.280> able<00:05:41.440> to<00:05:41.600> like<00:05:41.759> get<00:05:41.880> out<00:05:42.039> of 00:05:42.189 --> 00:05:42.199 align:start position:0% so we want to be able to like get out of 00:05:42.199 --> 00:05:45.550 align:start position:0% so we want to be able to like get out of that<00:05:42.840> Loop<00:05:43.840> um<00:05:44.199> so<00:05:44.680> that's<00:05:44.919> the<00:05:45.080> system<00:05:45.360> we've 00:05:45.550 --> 00:05:45.560 align:start position:0% that Loop um so that's the system we've 00:05:45.560 --> 00:05:48.469 align:start position:0% that Loop um so that's the system we've built<00:05:46.120> over<00:05:46.319> the<00:05:46.479> last<00:05:46.680> year<00:05:47.039> pod<00:05:47.240> and<00:05:47.479> GPC 00:05:48.469 --> 00:05:48.479 align:start position:0% built over the last year pod and GPC 00:05:48.479 --> 00:05:50.150 align:start position:0% built over the last year pod and GPC pods<00:05:48.720> are<00:05:48.919> packets<00:05:49.160> of<00:05:49.319> data<00:05:49.560> that<00:05:49.639> are 00:05:50.150 --> 00:05:50.160 align:start position:0% pods are packets of data that are 00:05:50.160 --> 00:05:51.510 align:start position:0% pods are packets of data that are specially<00:05:50.600> issued<00:05:50.960> so<00:05:51.080> they<00:05:51.160> need<00:05:51.319> to<00:05:51.400> be 00:05:51.510 --> 00:05:51.520 align:start position:0% specially issued so they need to be 00:05:51.520 --> 00:05:53.950 align:start position:0% specially issued so they need to be issued<00:05:51.800> in<00:05:52.000> specific<00:05:52.400> ways<00:05:53.039> and<00:05:53.160> then<00:05:53.280> GPC<00:05:53.759> are 00:05:53.950 --> 00:05:53.960 align:start position:0% issued in specific ways and then GPC are 00:05:53.960 --> 00:05:55.469 align:start position:0% issued in specific ways and then GPC are cryptographic<00:05:54.520> machines<00:05:54.880> that<00:05:55.000> can<00:05:55.120> ingest 00:05:55.469 --> 00:05:55.479 align:start position:0% cryptographic machines that can ingest 00:05:55.479 --> 00:05:56.950 align:start position:0% cryptographic machines that can ingest pods<00:05:55.720> and<00:05:55.840> make<00:05:56.000> claims<00:05:56.319> about<00:05:56.560> them<00:05:56.720> using 00:05:56.950 --> 00:05:56.960 align:start position:0% pods and make claims about them using 00:05:56.960 --> 00:06:00.629 align:start position:0% pods and make claims about them using zkps<00:05:57.840> so<00:05:58.039> claims<00:05:58.440> like<00:05:58.720> hey<00:05:59.000> the<00:05:59.680> entry<00:06:00.160> killed 00:06:00.629 --> 00:06:00.639 align:start position:0% zkps so claims like hey the entry killed 00:06:00.639 --> 00:06:03.110 align:start position:0% zkps so claims like hey the entry killed age<00:06:01.120> in<00:06:01.280> this<00:06:01.560> pod<00:06:01.840> is<00:06:01.960> over<00:06:02.199> a<00:06:02.319> certain<00:06:02.680> number 00:06:03.110 --> 00:06:03.120 align:start position:0% age in this pod is over a certain number 00:06:03.120 --> 00:06:05.110 align:start position:0% age in this pod is over a certain number or<00:06:03.440> my<00:06:03.639> frog<00:06:03.960> is<00:06:04.080> more<00:06:04.280> beautiful<00:06:04.759> than<00:06:04.919> your 00:06:05.110 --> 00:06:05.120 align:start position:0% or my frog is more beautiful than your 00:06:05.120 --> 00:06:06.589 align:start position:0% or my frog is more beautiful than your frog<00:06:05.479> or<00:06:05.639> that<00:06:05.800> kind<00:06:05.919> of<00:06:06.039> stuff<00:06:06.240> these<00:06:06.360> are<00:06:06.479> the 00:06:06.589 --> 00:06:06.599 align:start position:0% frog or that kind of stuff these are the 00:06:06.599 --> 00:06:09.070 align:start position:0% frog or that kind of stuff these are the kind<00:06:06.720> of<00:06:06.800> claims<00:06:07.080> you<00:06:07.160> can<00:06:07.280> make<00:06:07.400> with<00:06:07.800> GPC<00:06:08.800> um 00:06:09.070 --> 00:06:09.080 align:start position:0% kind of claims you can make with GPC um 00:06:09.080 --> 00:06:10.430 align:start position:0% kind of claims you can make with GPC um and<00:06:09.199> it's<00:06:09.360> great<00:06:09.639> because<00:06:09.840> it's<00:06:10.199> quite 00:06:10.430 --> 00:06:10.440 align:start position:0% and it's great because it's quite 00:06:10.440 --> 00:06:12.430 align:start position:0% and it's great because it's quite flexible<00:06:10.919> yet<00:06:11.319> performant<00:06:11.800> enough<00:06:12.000> to<00:06:12.120> run<00:06:12.280> on 00:06:12.430 --> 00:06:12.440 align:start position:0% flexible yet performant enough to run on 00:06:12.440 --> 00:06:15.189 align:start position:0% flexible yet performant enough to run on mobile<00:06:12.759> browsers<00:06:13.680> and<00:06:13.800> it's<00:06:14.199> about 00:06:15.189 --> 00:06:15.199 align:start position:0% mobile browsers and it's about 00:06:15.199 --> 00:06:18.270 align:start position:0% mobile browsers and it's about production<00:06:15.800> ready<00:06:16.440> but<00:06:17.360> um<00:06:17.680> oh<00:06:17.919> yeah<00:06:18.039> and<00:06:18.160> all 00:06:18.270 --> 00:06:18.280 align:start position:0% production ready but um oh yeah and all 00:06:18.280 --> 00:06:20.629 align:start position:0% production ready but um oh yeah and all of<00:06:18.360> you<00:06:18.479> are<00:06:18.599> using<00:06:19.120> it<00:06:20.120> because<00:06:20.240> your<00:06:20.360> tickets 00:06:20.629 --> 00:06:20.639 align:start position:0% of you are using it because your tickets 00:06:20.639 --> 00:06:23.670 align:start position:0% of you are using it because your tickets and<00:06:20.720> your<00:06:20.840> frogs<00:06:21.120> are<00:06:21.240> all<00:06:21.360> pods<00:06:21.599> in<00:06:21.800> GPC<00:06:22.800> so 00:06:23.670 --> 00:06:23.680 align:start position:0% and your frogs are all pods in GPC so 00:06:23.680 --> 00:06:26.029 align:start position:0% and your frogs are all pods in GPC so the<00:06:23.840> T<00:06:24.319> how<00:06:24.479> the<00:06:24.599> system<00:06:24.880> works<00:06:25.199> is<00:06:25.919> an 00:06:26.029 --> 00:06:26.039 align:start position:0% the T how the system works is an 00:06:26.039 --> 00:06:27.950 align:start position:0% the T how the system works is an authority<00:06:26.479> comes<00:06:26.960> together<00:06:27.400> ATT<00:06:27.599> test<00:06:27.840> to 00:06:27.950 --> 00:06:27.960 align:start position:0% authority comes together ATT test to 00:06:27.960 --> 00:06:30.710 align:start position:0% authority comes together ATT test to some<00:06:28.199> data<00:06:28.599> via<00:06:28.800> an<00:06:28.919> EDS<00:06:29.560> job<00:06:29.720> job<00:06:29.919> signature 00:06:30.710 --> 00:06:30.720 align:start position:0% some data via an EDS job job signature 00:06:30.720 --> 00:06:33.350 align:start position:0% some data via an EDS job job signature they<00:06:30.840> get<00:06:31.319> a<00:06:31.479> pod<00:06:32.120> you<00:06:32.319> put<00:06:32.599> a<00:06:32.720> bunch<00:06:32.880> of<00:06:33.000> PODS 00:06:33.350 --> 00:06:33.360 align:start position:0% they get a pod you put a bunch of PODS 00:06:33.360 --> 00:06:34.950 align:start position:0% they get a pod you put a bunch of PODS together<00:06:33.520> into<00:06:33.720> a<00:06:33.840> GPC<00:06:34.199> and<00:06:34.280> you<00:06:34.360> get<00:06:34.479> a<00:06:34.560> GPC 00:06:34.950 --> 00:06:34.960 align:start position:0% together into a GPC and you get a GPC 00:06:34.960 --> 00:06:36.270 align:start position:0% together into a GPC and you get a GPC claim<00:06:35.280> and<00:06:35.360> you<00:06:35.440> can<00:06:35.680> show<00:06:35.919> that<00:06:36.039> to<00:06:36.160> a 00:06:36.270 --> 00:06:36.280 align:start position:0% claim and you can show that to a 00:06:36.280 --> 00:06:38.189 align:start position:0% claim and you can show that to a verifier<00:06:36.720> and<00:06:36.880> convince<00:06:37.199> them<00:06:37.319> of<00:06:37.400> something 00:06:38.189 --> 00:06:38.199 align:start position:0% verifier and convince them of something 00:06:38.199 --> 00:06:40.309 align:start position:0% verifier and convince them of something so<00:06:38.440> the<00:06:38.560> way<00:06:38.680> it<00:06:38.759> looks<00:06:39.039> like<00:06:39.360> is<00:06:39.880> you<00:06:40.039> sign 00:06:40.309 --> 00:06:40.319 align:start position:0% so the way it looks like is you sign 00:06:40.319 --> 00:06:42.510 align:start position:0% so the way it looks like is you sign some<00:06:40.560> data<00:06:41.160> you<00:06:41.280> get<00:06:41.479> some<00:06:41.680> serialized<00:06:42.319> key 00:06:42.510 --> 00:06:42.520 align:start position:0% some data you get some serialized key 00:06:42.520 --> 00:06:44.230 align:start position:0% some data you get some serialized key value<00:06:42.840> data<00:06:43.199> here<00:06:43.400> we<00:06:43.440> will<00:06:43.599> take<00:06:43.759> the<00:06:43.880> date<00:06:44.080> of 00:06:44.230 --> 00:06:44.240 align:start position:0% value data here we will take the date of 00:06:44.240 --> 00:06:47.510 align:start position:0% value data here we will take the date of birth<00:06:44.919> as<00:06:45.039> a<00:06:45.360> specific<00:06:45.840> entry<00:06:46.440> will<00:06:46.800> will<00:06:47.199> will 00:06:47.510 --> 00:06:47.520 align:start position:0% birth as a specific entry will will will 00:06:47.520 --> 00:06:49.909 align:start position:0% birth as a specific entry will will will Trace<00:06:47.919> through<00:06:48.120> this<00:06:48.280> whole<00:06:48.720> computation<00:06:49.720> um 00:06:49.909 --> 00:06:49.919 align:start position:0% Trace through this whole computation um 00:06:49.919 --> 00:06:51.550 align:start position:0% Trace through this whole computation um then<00:06:50.039> you<00:06:50.120> can<00:06:50.240> construct<00:06:50.599> a<00:06:50.680> GPC<00:06:51.080> config<00:06:51.440> that 00:06:51.550 --> 00:06:51.560 align:start position:0% then you can construct a GPC config that 00:06:51.560 --> 00:06:53.990 align:start position:0% then you can construct a GPC config that says<00:06:51.880> hey<00:06:52.039> I'm<00:06:52.160> looking<00:06:52.400> for<00:06:52.599> a<00:06:52.800> pod<00:06:53.400> called<00:06:53.680> ID 00:06:53.990 --> 00:06:54.000 align:start position:0% says hey I'm looking for a pod called ID 00:06:54.000 --> 00:06:55.950 align:start position:0% says hey I'm looking for a pod called ID card<00:06:54.639> with<00:06:54.759> an<00:06:54.880> entry<00:06:55.160> called<00:06:55.319> datea<00:06:55.479> of<00:06:55.639> birth 00:06:55.950 --> 00:06:55.960 align:start position:0% card with an entry called datea of birth 00:06:55.960 --> 00:06:57.230 align:start position:0% card with an entry called datea of birth and<00:06:56.039> I<00:06:56.120> want<00:06:56.199> to<00:06:56.319> make<00:06:56.440> a<00:06:56.560> claim<00:06:56.800> that<00:06:56.919> it's<00:06:57.039> in 00:06:57.230 --> 00:06:57.240 align:start position:0% and I want to make a claim that it's in 00:06:57.240 --> 00:06:59.710 align:start position:0% and I want to make a claim that it's in this<00:06:57.440> range<00:06:58.280> and<00:06:58.440> on<00:06:58.639> top<00:06:58.800> of<00:06:58.960> that<00:06:59.199> there's<00:06:59.599> Al 00:06:59.710 --> 00:06:59.720 align:start position:0% this range and on top of that there's Al 00:06:59.720 --> 00:07:01.510 align:start position:0% this range and on top of that there's Al an<00:06:59.800> entry<00:07:00.080> called<00:07:00.280> card<00:07:00.599> holder<00:07:01.120> which<00:07:01.280> won't 00:07:01.510 --> 00:07:01.520 align:start position:0% an entry called card holder which won't 00:07:01.520 --> 00:07:03.430 align:start position:0% an entry called card holder which won't be<00:07:01.680> revealed<00:07:02.199> and<00:07:02.280> I<00:07:02.360> want<00:07:02.560> this<00:07:02.680> to<00:07:02.879> match<00:07:03.240> a 00:07:03.430 --> 00:07:03.440 align:start position:0% be revealed and I want this to match a 00:07:03.440 --> 00:07:06.390 align:start position:0% be revealed and I want this to match a private<00:07:03.759> key<00:07:03.960> I<00:07:04.080> will<00:07:04.520> put<00:07:04.720> inside<00:07:05.080> this<00:07:05.400> GPC 00:07:06.390 --> 00:07:06.400 align:start position:0% private key I will put inside this GPC 00:07:06.400 --> 00:07:08.270 align:start position:0% private key I will put inside this GPC that<00:07:06.560> makes<00:07:06.840> it<00:07:07.039> such<00:07:07.360> that<00:07:07.720> other<00:07:08.039> people 00:07:08.270 --> 00:07:08.280 align:start position:0% that makes it such that other people 00:07:08.280 --> 00:07:10.110 align:start position:0% that makes it such that other people cannot<00:07:08.520> use<00:07:08.680> your<00:07:08.879> pods<00:07:09.599> and<00:07:09.720> then<00:07:09.840> out<00:07:10.000> of 00:07:10.110 --> 00:07:10.120 align:start position:0% cannot use your pods and then out of 00:07:10.120 --> 00:07:11.909 align:start position:0% cannot use your pods and then out of that<00:07:10.199> you<00:07:10.280> get<00:07:10.400> a<00:07:10.479> bunch<00:07:10.720> of<00:07:11.199> stuff<00:07:11.720> that<00:07:11.840> you 00:07:11.909 --> 00:07:11.919 align:start position:0% that you get a bunch of stuff that you 00:07:11.919 --> 00:07:13.629 align:start position:0% that you get a bunch of stuff that you can<00:07:12.160> plug<00:07:12.440> back<00:07:12.560> into<00:07:12.759> a<00:07:12.879> function<00:07:13.160> to<00:07:13.319> verify 00:07:13.629 --> 00:07:13.639 align:start position:0% can plug back into a function to verify 00:07:13.639 --> 00:07:15.270 align:start position:0% can plug back into a function to verify the<00:07:13.800> claim<00:07:14.000> and<00:07:14.080> you<00:07:14.199> get<00:07:14.280> a<00:07:14.360> booing<00:07:14.759> value<00:07:15.000> out 00:07:15.270 --> 00:07:15.280 align:start position:0% the claim and you get a booing value out 00:07:15.280 --> 00:07:17.150 align:start position:0% the claim and you get a booing value out that's<00:07:15.440> basically<00:07:15.840> how<00:07:16.199> pod<00:07:16.440> one<00:07:16.599> and<00:07:16.720> GPC 00:07:17.150 --> 00:07:17.160 align:start position:0% that's basically how pod one and GPC 00:07:17.160 --> 00:07:19.950 align:start position:0% that's basically how pod one and GPC work<00:07:18.000> it's<00:07:18.160> great<00:07:18.440> because<00:07:18.599> it<00:07:18.759> enables<00:07:19.759> this 00:07:19.950 --> 00:07:19.960 align:start position:0% work it's great because it enables this 00:07:19.960 --> 00:07:22.309 align:start position:0% work it's great because it enables this architecture<00:07:20.639> there<00:07:21.039> which<00:07:21.599> I<00:07:21.680> mean<00:07:22.000> is<00:07:22.199> kind 00:07:22.309 --> 00:07:22.319 align:start position:0% architecture there which I mean is kind 00:07:22.319 --> 00:07:24.270 align:start position:0% architecture there which I mean is kind of<00:07:22.479> General<00:07:23.000> it's<00:07:23.160> it's<00:07:23.280> pretty<00:07:23.560> General<00:07:23.960> most 00:07:24.270 --> 00:07:24.280 align:start position:0% of General it's it's pretty General most 00:07:24.280 --> 00:07:27.350 align:start position:0% of General it's it's pretty General most ID<00:07:24.680> systems<00:07:25.280> actually<00:07:25.599> today<00:07:26.120> use<00:07:26.520> that<00:07:26.919> that 00:07:27.350 --> 00:07:27.360 align:start position:0% ID systems actually today use that that 00:07:27.360 --> 00:07:28.589 align:start position:0% ID systems actually today use that that that<00:07:27.560> kind<00:07:27.680> of<00:07:27.840> like<00:07:27.960> architecture<00:07:28.479> where 00:07:28.589 --> 00:07:28.599 align:start position:0% that kind of like architecture where 00:07:28.599 --> 00:07:30.830 align:start position:0% that kind of like architecture where there's<00:07:28.759> an<00:07:28.919> issue<00:07:29.680> that<00:07:29.879> issues<00:07:30.240> some<00:07:30.639> some 00:07:30.830 --> 00:07:30.840 align:start position:0% there's an issue that issues some some 00:07:30.840 --> 00:07:32.749 align:start position:0% there's an issue that issues some some data<00:07:31.039> to<00:07:31.120> a<00:07:31.319> client<00:07:32.039> and<00:07:32.240> the<00:07:32.360> client<00:07:32.599> will 00:07:32.749 --> 00:07:32.759 align:start position:0% data to a client and the client will 00:07:32.759 --> 00:07:34.550 align:start position:0% data to a client and the client will make<00:07:32.960> claims<00:07:33.240> to<00:07:33.360> a<00:07:33.520> verifier<00:07:33.960> and<00:07:34.160> verifier 00:07:34.550 --> 00:07:34.560 align:start position:0% make claims to a verifier and verifier 00:07:34.560 --> 00:07:37.629 align:start position:0% make claims to a verifier and verifier can<00:07:34.680> verify<00:07:35.000> these<00:07:35.199> claims<00:07:36.199> okay<00:07:36.520> so<00:07:37.319> and<00:07:37.560> and 00:07:37.629 --> 00:07:37.639 align:start position:0% can verify these claims okay so and and 00:07:37.639 --> 00:07:39.110 align:start position:0% can verify these claims okay so and and on<00:07:37.759> top<00:07:37.879> of<00:07:37.960> that<00:07:38.080> it's<00:07:38.160> extremely<00:07:38.560> performant 00:07:39.110 --> 00:07:39.120 align:start position:0% on top of that it's extremely performant 00:07:39.120 --> 00:07:41.189 align:start position:0% on top of that it's extremely performant and<00:07:39.240> you<00:07:39.360> don't<00:07:39.560> need<00:07:39.879> new<00:07:40.080> zero<00:07:40.360> n 00:07:41.189 --> 00:07:41.199 align:start position:0% and you don't need new zero n 00:07:41.199 --> 00:07:43.990 align:start position:0% and you don't need new zero n circuits<00:07:42.199> um<00:07:42.680> and<00:07:42.840> as<00:07:42.960> I<00:07:43.039> said<00:07:43.240> earlier<00:07:43.759> during 00:07:43.990 --> 00:07:44.000 align:start position:0% circuits um and as I said earlier during 00:07:44.000 --> 00:07:46.029 align:start position:0% circuits um and as I said earlier during the<00:07:44.080> summer<00:07:44.319> of<00:07:44.440> 2024<00:07:45.000> we<00:07:45.120> got<00:07:45.400> we<00:07:45.520> wanted<00:07:45.800> more 00:07:46.029 --> 00:07:46.039 align:start position:0% the summer of 2024 we got we wanted more 00:07:46.039 --> 00:07:48.629 align:start position:0% the summer of 2024 we got we wanted more out<00:07:46.240> of<00:07:46.360> our<00:07:46.560> systems<00:07:47.479> um<00:07:48.120> and<00:07:48.240> the<00:07:48.319> reason<00:07:48.560> we 00:07:48.629 --> 00:07:48.639 align:start position:0% out of our systems um and the reason we 00:07:48.639 --> 00:07:50.309 align:start position:0% out of our systems um and the reason we want<00:07:48.840> more<00:07:49.000> out<00:07:49.120> of<00:07:49.240> our<00:07:49.440> system<00:07:49.919> which<00:07:50.199> I 00:07:50.309 --> 00:07:50.319 align:start position:0% want more out of our system which I 00:07:50.319 --> 00:07:53.189 align:start position:0% want more out of our system which I remind<00:07:50.599> you<00:07:50.759> is<00:07:51.039> this<00:07:52.039> is<00:07:52.280> that<00:07:52.639> well<00:07:52.879> first 00:07:53.189 --> 00:07:53.199 align:start position:0% remind you is this is that well first 00:07:53.199 --> 00:07:54.629 align:start position:0% remind you is this is that well first the<00:07:53.280> first<00:07:53.520> limitation<00:07:53.960> is<00:07:54.240> this<00:07:54.360> system 00:07:54.629 --> 00:07:54.639 align:start position:0% the first limitation is this system 00:07:54.639 --> 00:07:56.869 align:start position:0% the first limitation is this system needs<00:07:55.039> specifically<00:07:55.759> issued<00:07:56.240> data<00:07:56.639> so<00:07:56.759> you 00:07:56.869 --> 00:07:56.879 align:start position:0% needs specifically issued data so you 00:07:56.879 --> 00:07:58.510 align:start position:0% needs specifically issued data so you need<00:07:57.039> to<00:07:57.199> go<00:07:57.400> and<00:07:57.599> like<00:07:57.759> get<00:07:57.919> people<00:07:58.080> to<00:07:58.240> issue 00:07:58.510 --> 00:07:58.520 align:start position:0% need to go and like get people to issue 00:07:58.520 --> 00:08:00.270 align:start position:0% need to go and like get people to issue data<00:07:58.720> in<00:07:58.800> a<00:07:58.919> specific<00:07:59.240> way<00:07:59.680> which<00:07:59.879> I<00:07:59.960> mean<00:08:00.159> if 00:08:00.270 --> 00:08:00.280 align:start position:0% data in a specific way which I mean if 00:08:00.280 --> 00:08:01.629 align:start position:0% data in a specific way which I mean if you<00:08:00.400> think<00:08:00.599> about<00:08:00.800> it<00:08:01.039> it's<00:08:01.199> not<00:08:01.360> going<00:08:01.440> to 00:08:01.629 --> 00:08:01.639 align:start position:0% you think about it it's not going to 00:08:01.639 --> 00:08:03.869 align:start position:0% you think about it it's not going to happen<00:08:02.520> second<00:08:02.840> is<00:08:03.039> it's<00:08:03.199> limited<00:08:03.520> to<00:08:03.680> one 00:08:03.869 --> 00:08:03.879 align:start position:0% happen second is it's limited to one 00:08:03.879 --> 00:08:06.469 align:start position:0% happen second is it's limited to one round<00:08:04.120> of<00:08:04.560> computation<00:08:05.560> U<00:08:05.759> and<00:08:05.879> a<00:08:06.000> lot<00:08:06.159> of<00:08:06.280> the 00:08:06.469 --> 00:08:06.479 align:start position:0% round of computation U and a lot of the 00:08:06.479 --> 00:08:10.230 align:start position:0% round of computation U and a lot of the time<00:08:07.039> use<00:08:07.479> cases<00:08:08.280> of<00:08:08.680> data<00:08:09.440> needs<00:08:09.800> more<00:08:10.039> than 00:08:10.230 --> 00:08:10.240 align:start position:0% time use cases of data needs more than 00:08:10.240 --> 00:08:11.869 align:start position:0% time use cases of data needs more than one<00:08:10.440> round<00:08:10.639> of<00:08:10.800> transformation<00:08:11.479> you<00:08:11.599> know<00:08:11.720> one 00:08:11.869 --> 00:08:11.879 align:start position:0% one round of transformation you know one 00:08:11.879 --> 00:08:13.950 align:start position:0% one round of transformation you know one round<00:08:12.039> of<00:08:12.120> transformation<00:08:12.599> is<00:08:12.759> useful<00:08:13.319> but<00:08:13.840> it 00:08:13.950 --> 00:08:13.960 align:start position:0% round of transformation is useful but it 00:08:13.960 --> 00:08:15.350 align:start position:0% round of transformation is useful but it would<00:08:14.080> be<00:08:14.199> great<00:08:14.400> if<00:08:14.479> we<00:08:14.599> could<00:08:14.840> keep 00:08:15.350 --> 00:08:15.360 align:start position:0% would be great if we could keep 00:08:15.360 --> 00:08:17.230 align:start position:0% would be great if we could keep executing<00:08:15.960> more<00:08:16.280> programs<00:08:16.639> on<00:08:16.800> top<00:08:16.919> of<00:08:17.039> our 00:08:17.230 --> 00:08:17.240 align:start position:0% executing more programs on top of our 00:08:17.240 --> 00:08:19.710 align:start position:0% executing more programs on top of our data<00:08:17.680> and<00:08:18.039> maintain<00:08:19.039> the<00:08:19.159> cryptographic 00:08:19.710 --> 00:08:19.720 align:start position:0% data and maintain the cryptographic 00:08:19.720 --> 00:08:21.390 align:start position:0% data and maintain the cryptographic integrity<00:08:20.560> and<00:08:20.680> also<00:08:20.840> it's<00:08:21.000> limited<00:08:21.280> to 00:08:21.390 --> 00:08:21.400 align:start position:0% integrity and also it's limited to 00:08:21.400 --> 00:08:23.270 align:start position:0% integrity and also it's limited to single<00:08:21.680> prer<00:08:21.960> use<00:08:22.240> cases<00:08:22.680> what<00:08:22.800> I<00:08:22.879> mean<00:08:23.080> by 00:08:23.270 --> 00:08:23.280 align:start position:0% single prer use cases what I mean by 00:08:23.280 --> 00:08:23.950 align:start position:0% single prer use cases what I mean by that 00:08:23.950 --> 00:08:23.960 align:start position:0% that 00:08:23.960 --> 00:08:27.469 align:start position:0% that is<00:08:24.960> while<00:08:25.240> the<00:08:25.360> GPC<00:08:26.000> can<00:08:26.319> hide<00:08:27.000> things<00:08:27.280> from 00:08:27.469 --> 00:08:27.479 align:start position:0% is while the GPC can hide things from 00:08:27.479 --> 00:08:30.230 align:start position:0% is while the GPC can hide things from the<00:08:27.639> pods<00:08:27.960> that<00:08:28.080> were<00:08:28.440> put<00:08:28.680> into<00:08:28.960> it<00:08:29.680> um<00:08:30.039> the 00:08:30.230 --> 00:08:30.240 align:start position:0% the pods that were put into it um the 00:08:30.240 --> 00:08:32.389 align:start position:0% the pods that were put into it um the person<00:08:30.599> executing<00:08:31.080> the<00:08:31.240> GPC<00:08:31.800> actually<00:08:32.039> has<00:08:32.159> to 00:08:32.389 --> 00:08:32.399 align:start position:0% person executing the GPC actually has to 00:08:32.399 --> 00:08:34.350 align:start position:0% person executing the GPC actually has to know<00:08:32.919> about<00:08:33.200> all<00:08:33.360> the<00:08:33.519> parts<00:08:33.800> that<00:08:33.919> flow<00:08:34.159> into 00:08:34.350 --> 00:08:34.360 align:start position:0% know about all the parts that flow into 00:08:34.360 --> 00:08:36.350 align:start position:0% know about all the parts that flow into this<00:08:34.519> GPC<00:08:35.320> so<00:08:35.519> if<00:08:35.719> I<00:08:35.800> don't<00:08:35.919> know<00:08:36.080> me<00:08:36.200> and<00:08:36.279> my 00:08:36.350 --> 00:08:36.360 align:start position:0% this GPC so if I don't know me and my 00:08:36.360 --> 00:08:37.709 align:start position:0% this GPC so if I don't know me and my friend<00:08:36.599> are<00:08:36.719> trying<00:08:36.919> to<00:08:37.039> figure<00:08:37.279> out<00:08:37.599> which 00:08:37.709 --> 00:08:37.719 align:start position:0% friend are trying to figure out which 00:08:37.719 --> 00:08:39.469 align:start position:0% friend are trying to figure out which frog<00:08:38.000> is<00:08:38.120> the<00:08:38.240> most<00:08:38.399> beautiful<00:08:39.120> I<00:08:39.240> have<00:08:39.360> to 00:08:39.469 --> 00:08:39.479 align:start position:0% frog is the most beautiful I have to 00:08:39.479 --> 00:08:41.190 align:start position:0% frog is the most beautiful I have to give<00:08:39.680> the<00:08:39.839> Pod<00:08:40.039> to<00:08:40.159> my<00:08:40.320> friend<00:08:40.719> or<00:08:40.880> my<00:08:41.000> friend 00:08:41.190 --> 00:08:41.200 align:start position:0% give the Pod to my friend or my friend 00:08:41.200 --> 00:08:44.070 align:start position:0% give the Pod to my friend or my friend has<00:08:41.320> to<00:08:41.479> give<00:08:41.599> me<00:08:42.080> their<00:08:42.320> pod<00:08:43.120> so<00:08:43.560> it<00:08:43.800> it<00:08:43.959> it 00:08:44.070 --> 00:08:44.080 align:start position:0% has to give me their pod so it it it 00:08:44.080 --> 00:08:45.870 align:start position:0% has to give me their pod so it it it starts<00:08:44.680> becoming<00:08:45.000> a<00:08:45.080> little<00:08:45.240> bit<00:08:45.480> tricky<00:08:45.760> when 00:08:45.870 --> 00:08:45.880 align:start position:0% starts becoming a little bit tricky when 00:08:45.880 --> 00:08:47.590 align:start position:0% starts becoming a little bit tricky when you<00:08:45.959> have<00:08:46.120> multiple<00:08:46.519> people<00:08:46.720> in<00:08:46.920> high<00:08:47.080> stake 00:08:47.590 --> 00:08:47.600 align:start position:0% you have multiple people in high stake 00:08:47.600 --> 00:08:50.509 align:start position:0% you have multiple people in high stake data<00:08:48.600> um<00:08:49.399> the<00:08:49.519> world<00:08:49.760> today<00:08:50.080> has<00:08:50.240> lots<00:08:50.399> of 00:08:50.509 --> 00:08:50.519 align:start position:0% data um the world today has lots of 00:08:50.519 --> 00:08:52.030 align:start position:0% data um the world today has lots of cryptographic<00:08:51.120> data<00:08:51.560> yet<00:08:51.680> it's<00:08:51.880> very 00:08:52.030 --> 00:08:52.040 align:start position:0% cryptographic data yet it's very 00:08:52.040 --> 00:08:54.470 align:start position:0% cryptographic data yet it's very heterogeneous<00:08:52.920> so<00:08:53.240> every<00:08:53.640> anything<00:08:53.959> from 00:08:54.470 --> 00:08:54.480 align:start position:0% heterogeneous so every anything from 00:08:54.480 --> 00:08:56.829 align:start position:0% heterogeneous so every anything from blockchains<00:08:55.000> to<00:08:55.200> email<00:08:55.600> to<00:08:55.800> TLS<00:08:56.320> to<00:08:56.519> national 00:08:56.829 --> 00:08:56.839 align:start position:0% blockchains to email to TLS to national 00:08:56.839 --> 00:08:59.630 align:start position:0% blockchains to email to TLS to national ID<00:08:57.160> systems<00:08:57.760> they're<00:08:57.920> all<00:08:58.680> enry<00:08:59.040> like<00:08:59.440> Cog 00:08:59.630 --> 00:08:59.640 align:start position:0% ID systems they're all enry like Cog 00:08:59.640 --> 00:09:01.310 align:start position:0% ID systems they're all enry like Cog graphic<00:08:59.920> data<00:09:00.279> yet<00:09:00.560> formatted<00:09:01.000> in<00:09:01.160> very 00:09:01.310 --> 00:09:01.320 align:start position:0% graphic data yet formatted in very 00:09:01.320 --> 00:09:02.630 align:start position:0% graphic data yet formatted in very different<00:09:01.600> ways<00:09:01.880> with<00:09:02.040> different<00:09:02.240> signature 00:09:02.630 --> 00:09:02.640 align:start position:0% different ways with different signature 00:09:02.640 --> 00:09:03.829 align:start position:0% different ways with different signature systems 00:09:03.829 --> 00:09:03.839 align:start position:0% systems 00:09:03.839 --> 00:09:06.389 align:start position:0% systems Etc<00:09:04.839> the<00:09:05.000> basic<00:09:05.279> use<00:09:05.560> cases<00:09:05.800> often<00:09:06.079> require 00:09:06.389 --> 00:09:06.399 align:start position:0% Etc the basic use cases often require 00:09:06.399 --> 00:09:07.829 align:start position:0% Etc the basic use cases often require more<00:09:06.519> than<00:09:06.640> two<00:09:06.760> rounds<00:09:06.959> of<00:09:07.079> transformation 00:09:07.829 --> 00:09:07.839 align:start position:0% more than two rounds of transformation 00:09:07.839 --> 00:09:09.470 align:start position:0% more than two rounds of transformation and<00:09:08.240> potentially<00:09:08.640> a<00:09:08.720> whole<00:09:08.880> world<00:09:09.120> might<00:09:09.279> open 00:09:09.470 --> 00:09:09.480 align:start position:0% and potentially a whole world might open 00:09:09.480 --> 00:09:11.430 align:start position:0% and potentially a whole world might open up<00:09:09.720> if<00:09:09.839> we<00:09:09.959> can<00:09:10.440> have<00:09:10.640> data<00:09:10.880> flow<00:09:11.200> through 00:09:11.430 --> 00:09:11.440 align:start position:0% up if we can have data flow through 00:09:11.440 --> 00:09:13.350 align:start position:0% up if we can have data flow through different<00:09:11.760> aggregor<00:09:12.519> aggregators<00:09:13.200> and 00:09:13.350 --> 00:09:13.360 align:start position:0% different aggregor aggregators and 00:09:13.360 --> 00:09:15.870 align:start position:0% different aggregor aggregators and different<00:09:13.640> Services<00:09:14.279> yet<00:09:14.519> not<00:09:14.760> lose<00:09:15.680> their 00:09:15.870 --> 00:09:15.880 align:start position:0% different Services yet not lose their 00:09:15.880 --> 00:09:18.190 align:start position:0% different Services yet not lose their integrity<00:09:16.680> like<00:09:16.839> today<00:09:17.240> most<00:09:17.399> of<00:09:17.519> the<00:09:17.680> time 00:09:18.190 --> 00:09:18.200 align:start position:0% integrity like today most of the time 00:09:18.200 --> 00:09:19.590 align:start position:0% integrity like today most of the time all<00:09:18.320> of<00:09:18.440> the<00:09:18.560> data<00:09:18.800> falls<00:09:19.040> into<00:09:19.240> like<00:09:19.360> a<00:09:19.440> big 00:09:19.590 --> 00:09:19.600 align:start position:0% all of the data falls into like a big 00:09:19.600 --> 00:09:21.110 align:start position:0% all of the data falls into like a big Silo<00:09:19.959> and<00:09:20.040> then<00:09:20.240> gets<00:09:20.519> processed<00:09:20.920> and 00:09:21.110 --> 00:09:21.120 align:start position:0% Silo and then gets processed and 00:09:21.120 --> 00:09:22.710 align:start position:0% Silo and then gets processed and consumed<00:09:21.560> out<00:09:21.680> of<00:09:21.880> that<00:09:22.040> it's<00:09:22.160> very<00:09:22.399> rare<00:09:22.600> for 00:09:22.710 --> 00:09:22.720 align:start position:0% consumed out of that it's very rare for 00:09:22.720 --> 00:09:24.910 align:start position:0% consumed out of that it's very rare for like<00:09:22.880> two<00:09:23.040> silos<00:09:23.760> to<00:09:23.959> ping<00:09:24.200> pong<00:09:24.399> data<00:09:24.640> between 00:09:24.910 --> 00:09:24.920 align:start position:0% like two silos to ping pong data between 00:09:24.920 --> 00:09:26.829 align:start position:0% like two silos to ping pong data between each<00:09:25.040> other<00:09:25.640> that's<00:09:25.839> not<00:09:26.399> that<00:09:26.560> that's<00:09:26.680> not 00:09:26.829 --> 00:09:26.839 align:start position:0% each other that's not that that's not 00:09:26.839 --> 00:09:29.910 align:start position:0% each other that's not that that's not where<00:09:27.000> the<00:09:27.120> things<00:09:27.360> goes<00:09:27.920> usually<00:09:28.920> and<00:09:29.519> um<00:09:29.760> the 00:09:29.910 --> 00:09:29.920 align:start position:0% where the things goes usually and um the 00:09:29.920 --> 00:09:31.670 align:start position:0% where the things goes usually and um the sad<00:09:30.200> thing<00:09:30.440> is<00:09:30.720> there's<00:09:30.920> a<00:09:31.040> lot<00:09:31.160> of<00:09:31.279> works<00:09:31.519> on 00:09:31.670 --> 00:09:31.680 align:start position:0% sad thing is there's a lot of works on 00:09:31.680 --> 00:09:33.910 align:start position:0% sad thing is there's a lot of works on domain<00:09:32.000> specific<00:09:32.399> systems<00:09:32.959> out<00:09:33.240> there<00:09:33.640> for 00:09:33.910 --> 00:09:33.920 align:start position:0% domain specific systems out there for 00:09:33.920 --> 00:09:35.030 align:start position:0% domain specific systems out there for processing<00:09:34.480> all<00:09:34.680> that<00:09:34.800> kind<00:09:34.920> of 00:09:35.030 --> 00:09:35.040 align:start position:0% processing all that kind of 00:09:35.040 --> 00:09:36.670 align:start position:0% processing all that kind of cryptographic<00:09:35.600> data<00:09:35.959> yet<00:09:36.279> zero 00:09:36.670 --> 00:09:36.680 align:start position:0% cryptographic data yet zero 00:09:36.680 --> 00:09:39.069 align:start position:0% cryptographic data yet zero interoperability<00:09:37.680> between<00:09:38.000> them<00:09:38.800> uh<00:09:38.920> and 00:09:39.069 --> 00:09:39.079 align:start position:0% interoperability between them uh and 00:09:39.079 --> 00:09:40.870 align:start position:0% interoperability between them uh and what<00:09:39.200> ends<00:09:39.399> up<00:09:39.560> usually<00:09:39.920> happening<00:09:40.320> is 00:09:40.870 --> 00:09:40.880 align:start position:0% what ends up usually happening is 00:09:40.880 --> 00:09:43.230 align:start position:0% what ends up usually happening is companies<00:09:41.279> or<00:09:41.519> open<00:09:41.800> source<00:09:42.079> groups<00:09:42.680> build<00:09:43.000> a 00:09:43.230 --> 00:09:43.240 align:start position:0% companies or open source groups build a 00:09:43.240 --> 00:09:45.949 align:start position:0% companies or open source groups build a specific<00:09:43.760> import<00:09:44.360> as<00:09:44.440> an<00:09:44.600> example<00:09:45.040> for<00:09:45.560> email 00:09:45.949 --> 00:09:45.959 align:start position:0% specific import as an example for email 00:09:45.959 --> 00:09:47.949 align:start position:0% specific import as an example for email data<00:09:46.240> or<00:09:46.360> for<00:09:46.560> TAS<00:09:46.880> data<00:09:47.079> and<00:09:47.200> build<00:09:47.399> an<00:09:47.560> entire 00:09:47.949 --> 00:09:47.959 align:start position:0% data or for TAS data and build an entire 00:09:47.959 --> 00:09:50.030 align:start position:0% data or for TAS data and build an entire ecosystem<00:09:48.560> on<00:09:48.760> top<00:09:49.120> for<00:09:49.360> consuming<00:09:49.880> that 00:09:50.030 --> 00:09:50.040 align:start position:0% ecosystem on top for consuming that 00:09:50.040 --> 00:09:53.150 align:start position:0% ecosystem on top for consuming that piece<00:09:50.200> of<00:09:50.360> data<00:09:50.839> as<00:09:50.959> opposed<00:09:51.279> to<00:09:51.880> having<00:09:52.880> these 00:09:53.150 --> 00:09:53.160 align:start position:0% piece of data as opposed to having these 00:09:53.160 --> 00:09:54.829 align:start position:0% piece of data as opposed to having these these<00:09:53.399> packets<00:09:53.720> be<00:09:53.839> able<00:09:54.000> to<00:09:54.079> flow<00:09:54.360> through 00:09:54.829 --> 00:09:54.839 align:start position:0% these packets be able to flow through 00:09:54.839 --> 00:09:57.590 align:start position:0% these packets be able to flow through like<00:09:55.000> with<00:09:55.120> each<00:09:55.240> other<00:09:56.160> so<00:09:57.040> one<00:09:57.200> way<00:09:57.320> to<00:09:57.440> think 00:09:57.590 --> 00:09:57.600 align:start position:0% like with each other so one way to think 00:09:57.600 --> 00:09:59.790 align:start position:0% like with each other so one way to think about<00:09:57.760> the<00:09:57.839> unlock<00:09:58.160> of<00:09:58.279> cryptography<00:09:59.040> is<00:09:59.160> that 00:09:59.790 --> 00:09:59.800 align:start position:0% about the unlock of cryptography is that 00:09:59.800 --> 00:10:02.069 align:start position:0% about the unlock of cryptography is that zero<00:10:00.120> Lun<00:10:00.440> proofs<00:10:00.880> enable<00:10:01.519> trustless 00:10:02.069 --> 00:10:02.079 align:start position:0% zero Lun proofs enable trustless 00:10:02.079 --> 00:10:03.949 align:start position:0% zero Lun proofs enable trustless refactoring<00:10:02.640> and<00:10:02.839> import<00:10:03.200> so<00:10:03.320> you<00:10:03.399> can<00:10:03.560> import 00:10:03.949 --> 00:10:03.959 align:start position:0% refactoring and import so you can import 00:10:03.959 --> 00:10:06.230 align:start position:0% refactoring and import so you can import cryptographic<00:10:04.600> data<00:10:05.000> refactor<00:10:05.519> it<00:10:05.760> Etc 00:10:06.230 --> 00:10:06.240 align:start position:0% cryptographic data refactor it Etc 00:10:06.240 --> 00:10:08.710 align:start position:0% cryptographic data refactor it Etc without<00:10:06.440> losing<00:10:06.720> its<00:10:07.240> Integrity<00:10:08.240> um<00:10:08.480> and<00:10:08.600> the 00:10:08.710 --> 00:10:08.720 align:start position:0% without losing its Integrity um and the 00:10:08.720 --> 00:10:10.949 align:start position:0% without losing its Integrity um and the unlock<00:10:09.160> of<00:10:09.600> more<00:10:09.839> interactive<00:10:10.440> technology 00:10:10.949 --> 00:10:10.959 align:start position:0% unlock of more interactive technology 00:10:10.959 --> 00:10:13.790 align:start position:0% unlock of more interactive technology like<00:10:11.160> FH<00:10:11.800> coar<00:10:12.480> MPCs<00:10:13.040> that<00:10:13.160> you<00:10:13.240> can<00:10:13.440> combine 00:10:13.790 --> 00:10:13.800 align:start position:0% like FH coar MPCs that you can combine 00:10:13.800 --> 00:10:16.470 align:start position:0% like FH coar MPCs that you can combine data<00:10:14.120> confidentially<00:10:14.880> across<00:10:15.160> many<00:10:15.480> people 00:10:16.470 --> 00:10:16.480 align:start position:0% data confidentially across many people 00:10:16.480 --> 00:10:18.790 align:start position:0% data confidentially across many people so<00:10:16.800> where<00:10:16.920> we<00:10:17.040> want<00:10:17.160> to<00:10:17.279> get<00:10:17.399> to<00:10:17.720> is<00:10:18.120> is<00:10:18.360> this 00:10:18.790 --> 00:10:18.800 align:start position:0% so where we want to get to is is this 00:10:18.800 --> 00:10:19.990 align:start position:0% so where we want to get to is is this kind<00:10:18.920> of<00:10:19.079> like<00:10:19.279> verifiable<00:10:19.839> and 00:10:19.990 --> 00:10:20.000 align:start position:0% kind of like verifiable and 00:10:20.000 --> 00:10:21.590 align:start position:0% kind of like verifiable and interoperable<00:10:20.640> computational<00:10:21.160> graph<00:10:21.440> we 00:10:21.590 --> 00:10:21.600 align:start position:0% interoperable computational graph we 00:10:21.600 --> 00:10:23.230 align:start position:0% interoperable computational graph we import<00:10:21.959> cryptographic<00:10:22.519> data<00:10:22.760> we<00:10:22.920> compute 00:10:23.230 --> 00:10:23.240 align:start position:0% import cryptographic data we compute 00:10:23.240 --> 00:10:25.949 align:start position:0% import cryptographic data we compute over<00:10:23.560> it<00:10:24.480> uh<00:10:24.680> AV<00:10:25.040> people<00:10:25.399> can<00:10:25.480> you<00:10:25.600> be<00:10:25.720> a<00:10:25.800> bit 00:10:25.949 --> 00:10:25.959 align:start position:0% over it uh AV people can you be a bit 00:10:25.959 --> 00:10:29.870 align:start position:0% over it uh AV people can you be a bit quieter<00:10:26.600> excuse<00:10:26.880> me<00:10:27.760> hey<00:10:28.640> guys 00:10:29.870 --> 00:10:29.880 align:start position:0% quieter excuse me hey guys 00:10:29.880 --> 00:10:32.550 align:start position:0% quieter excuse me hey guys guys<00:10:30.560> quiet<00:10:31.240> it's<00:10:31.360> a 00:10:32.550 --> 00:10:32.560 align:start position:0% guys quiet it's a 00:10:32.560 --> 00:10:35.350 align:start position:0% guys quiet it's a classroom<00:10:33.560> so<00:10:33.920> you<00:10:34.040> can<00:10:34.240> import<00:10:34.640> data<00:10:35.000> compute 00:10:35.350 --> 00:10:35.360 align:start position:0% classroom so you can import data compute 00:10:35.360 --> 00:10:36.949 align:start position:0% classroom so you can import data compute over<00:10:35.519> it<00:10:35.680> recursively<00:10:36.279> and<00:10:36.360> then<00:10:36.519> export<00:10:36.839> it 00:10:36.949 --> 00:10:36.959 align:start position:0% over it recursively and then export it 00:10:36.959 --> 00:10:39.030 align:start position:0% over it recursively and then export it to<00:10:37.079> a<00:10:37.279> verifier 00:10:39.030 --> 00:10:39.040 align:start position:0% to a verifier 00:10:39.040 --> 00:10:41.269 align:start position:0% to a verifier so<00:10:40.040> we<00:10:40.160> think<00:10:40.360> this<00:10:40.519> address<00:10:40.839> the<00:10:40.920> limitations 00:10:41.269 --> 00:10:41.279 align:start position:0% so we think this address the limitations 00:10:41.279 --> 00:10:43.030 align:start position:0% so we think this address the limitations of<00:10:41.399> the<00:10:41.480> AIT<00:10:41.839> system<00:10:42.120> if<00:10:42.240> we<00:10:42.320> can<00:10:42.519> get<00:10:42.720> there 00:10:43.030 --> 00:10:43.040 align:start position:0% of the AIT system if we can get there 00:10:43.040 --> 00:10:44.310 align:start position:0% of the AIT system if we can get there because<00:10:43.360> as<00:10:43.440> I<00:10:43.519> said<00:10:43.680> earlier<00:10:44.000> there's<00:10:44.120> a<00:10:44.200> lot 00:10:44.310 --> 00:10:44.320 align:start position:0% because as I said earlier there's a lot 00:10:44.320 --> 00:10:46.509 align:start position:0% because as I said earlier there's a lot of<00:10:44.399> cryptographic<00:10:45.160> data<00:10:45.440> in<00:10:45.519> the<00:10:45.639> world<00:10:46.240> yet 00:10:46.509 --> 00:10:46.519 align:start position:0% of cryptographic data in the world yet 00:10:46.519 --> 00:10:48.629 align:start position:0% of cryptographic data in the world yet it<00:10:46.600> needs<00:10:46.760> to<00:10:46.839> be<00:10:46.959> transformed<00:10:47.399> to<00:10:47.519> be<00:10:47.680> usable 00:10:48.629 --> 00:10:48.639 align:start position:0% it needs to be transformed to be usable 00:10:48.639 --> 00:10:51.230 align:start position:0% it needs to be transformed to be usable um<00:10:49.040> most<00:10:49.920> use<00:10:50.240> cases<00:10:50.519> require<00:10:50.839> multiple 00:10:51.230 --> 00:10:51.240 align:start position:0% um most use cases require multiple 00:10:51.240 --> 00:10:53.150 align:start position:0% um most use cases require multiple people<00:10:51.399> to<00:10:51.560> compute<00:10:52.000> together<00:10:52.760> most<00:10:52.920> of<00:10:53.040> the 00:10:53.150 --> 00:10:53.160 align:start position:0% people to compute together most of the 00:10:53.160 --> 00:10:55.870 align:start position:0% people to compute together most of the time<00:10:53.399> recursively<00:10:54.200> over<00:10:54.399> many<00:10:54.600> steps<00:10:54.880> of 00:10:55.870 --> 00:10:55.880 align:start position:0% time recursively over many steps of 00:10:55.880 --> 00:10:58.509 align:start position:0% time recursively over many steps of transformation<00:10:56.880> okay<00:10:57.200> so<00:10:57.720> that's<00:10:57.920> it<00:10:58.240> now<00:10:58.399> you 00:10:58.509 --> 00:10:58.519 align:start position:0% transformation okay so that's it now you 00:10:58.519 --> 00:11:00.030 align:start position:0% transformation okay so that's it now you know<00:10:58.760> why<00:10:58.880> you're<00:10:59.079> here 00:11:00.030 --> 00:11:00.040 align:start position:0% know why you're here 00:11:00.040 --> 00:11:04.389 align:start position:0% know why you're here we're<00:11:00.240> trying<00:11:00.480> to<00:11:00.639> solve<00:11:00.959> this<00:11:01.200> problem<00:11:02.519> um<00:11:03.519> so 00:11:04.389 --> 00:11:04.399 align:start position:0% we're trying to solve this problem um so 00:11:04.399 --> 00:11:06.110 align:start position:0% we're trying to solve this problem um so in<00:11:04.519> order<00:11:04.760> to<00:11:04.880> do<00:11:05.079> that<00:11:05.320> we<00:11:05.480> had<00:11:05.600> to<00:11:05.720> solve<00:11:06.000> a 00:11:06.110 --> 00:11:06.120 align:start position:0% in order to do that we had to solve a 00:11:06.120 --> 00:11:07.430 align:start position:0% in order to do that we had to solve a couple<00:11:06.440> problem<00:11:06.720> the<00:11:06.800> first<00:11:06.959> one<00:11:07.079> is<00:11:07.279> the 00:11:07.430 --> 00:11:07.440 align:start position:0% couple problem the first one is the 00:11:07.440 --> 00:11:09.110 align:start position:0% couple problem the first one is the program<00:11:07.839> composability<00:11:08.240> problem<00:11:08.920> what<00:11:09.040> I 00:11:09.110 --> 00:11:09.120 align:start position:0% program composability problem what I 00:11:09.120 --> 00:11:10.670 align:start position:0% program composability problem what I mean<00:11:09.360> by<00:11:09.560> that<00:11:09.920> is<00:11:10.079> that<00:11:10.279> let's<00:11:10.440> say<00:11:10.560> you<00:11:10.600> have 00:11:10.670 --> 00:11:10.680 align:start position:0% mean by that is that let's say you have 00:11:10.680 --> 00:11:12.190 align:start position:0% mean by that is that let's say you have a<00:11:10.760> group<00:11:10.959> of<00:11:11.079> like<00:11:11.160> a<00:11:11.279> bunch<00:11:11.440> of<00:11:11.560> friends<00:11:12.040> and 00:11:12.190 --> 00:11:12.200 align:start position:0% a group of like a bunch of friends and 00:11:12.200 --> 00:11:13.629 align:start position:0% a group of like a bunch of friends and all<00:11:12.320> of<00:11:12.480> these<00:11:12.600> friends<00:11:13.000> issue<00:11:13.279> you<00:11:13.360> a<00:11:13.480> piece 00:11:13.629 --> 00:11:13.639 align:start position:0% all of these friends issue you a piece 00:11:13.639 --> 00:11:16.269 align:start position:0% all of these friends issue you a piece of<00:11:13.720> cryptographic<00:11:14.480> data<00:11:15.480> um<00:11:15.680> so<00:11:15.839> it's<00:11:16.000> like<00:11:16.120> an 00:11:16.269 --> 00:11:16.279 align:start position:0% of cryptographic data um so it's like an 00:11:16.279 --> 00:11:18.710 align:start position:0% of cryptographic data um so it's like an array<00:11:16.800> of<00:11:17.160> of<00:11:17.440> of<00:11:17.600> packets<00:11:18.160> you<00:11:18.360> put<00:11:18.560> this 00:11:18.710 --> 00:11:18.720 align:start position:0% array of of of packets you put this 00:11:18.720 --> 00:11:20.190 align:start position:0% array of of of packets you put this array<00:11:19.040> of<00:11:19.200> packet<00:11:19.480> in<00:11:19.560> a<00:11:19.720> function<00:11:20.079> that 00:11:20.190 --> 00:11:20.200 align:start position:0% array of packet in a function that 00:11:20.200 --> 00:11:22.110 align:start position:0% array of packet in a function that counts<00:11:20.560> how<00:11:20.680> many<00:11:20.880> best<00:11:21.079> friend<00:11:21.360> you<00:11:21.560> have 00:11:22.110 --> 00:11:22.120 align:start position:0% counts how many best friend you have 00:11:22.120 --> 00:11:24.430 align:start position:0% counts how many best friend you have imagine<00:11:22.480> that<00:11:22.639> the<00:11:22.760> friend<00:11:23.120> packet<00:11:23.600> as<00:11:23.720> a<00:11:24.000> as<00:11:24.120> a 00:11:24.430 --> 00:11:24.440 align:start position:0% imagine that the friend packet as a as a 00:11:24.440 --> 00:11:26.990 align:start position:0% imagine that the friend packet as a as a value<00:11:24.800> called<00:11:25.040> is<00:11:25.279> best<00:11:25.880> you<00:11:26.040> get<00:11:26.200> 13<00:11:26.600> out<00:11:26.800> of 00:11:26.990 --> 00:11:27.000 align:start position:0% value called is best you get 13 out of 00:11:27.000 --> 00:11:28.710 align:start position:0% value called is best you get 13 out of that<00:11:27.720> then<00:11:27.839> you<00:11:27.920> want<00:11:28.040> to<00:11:28.160> operate<00:11:28.440> on<00:11:28.600> this 00:11:28.710 --> 00:11:28.720 align:start position:0% that then you want to operate on this 00:11:28.720 --> 00:11:30.670 align:start position:0% that then you want to operate on this further<00:11:29.320> as<00:11:29.440> an<00:11:29.519> example<00:11:29.800> a<00:11:29.959> different<00:11:30.360> person 00:11:30.670 --> 00:11:30.680 align:start position:0% further as an example a different person 00:11:30.680 --> 00:11:32.629 align:start position:0% further as an example a different person or<00:11:30.800> a<00:11:30.920> different<00:11:31.279> company<00:11:31.760> wants<00:11:32.000> to<00:11:32.200> operate 00:11:32.629 --> 00:11:32.639 align:start position:0% or a different company wants to operate 00:11:32.639 --> 00:11:34.870 align:start position:0% or a different company wants to operate on<00:11:32.800> top<00:11:32.959> of<00:11:33.120> this<00:11:33.360> result<00:11:33.760> that<00:11:33.880> you<00:11:34.040> got<00:11:34.760> and 00:11:34.870 --> 00:11:34.880 align:start position:0% on top of this result that you got and 00:11:34.880 --> 00:11:36.509 align:start position:0% on top of this result that you got and they<00:11:35.079> have<00:11:35.240> a<00:11:35.399> function<00:11:35.800> called<00:11:36.000> is<00:11:36.240> grade 00:11:36.509 --> 00:11:36.519 align:start position:0% they have a function called is grade 00:11:36.519 --> 00:11:38.230 align:start position:0% they have a function called is grade friend<00:11:36.800> groups<00:11:37.279> which<00:11:37.440> test<00:11:37.760> how<00:11:37.880> many<00:11:38.040> best 00:11:38.230 --> 00:11:38.240 align:start position:0% friend groups which test how many best 00:11:38.240 --> 00:11:39.430 align:start position:0% friend groups which test how many best friends<00:11:38.480> you<00:11:38.600> have<00:11:38.839> and<00:11:38.920> if<00:11:39.040> you<00:11:39.120> have<00:11:39.240> more 00:11:39.430 --> 00:11:39.440 align:start position:0% friends you have and if you have more 00:11:39.440 --> 00:11:41.590 align:start position:0% friends you have and if you have more than<00:11:39.639> three<00:11:40.000> or<00:11:40.200> or<00:11:40.440> three<00:11:40.959> you<00:11:41.200> consider<00:11:41.519> to 00:11:41.590 --> 00:11:41.600 align:start position:0% than three or or three you consider to 00:11:41.600 --> 00:11:43.310 align:start position:0% than three or or three you consider to have<00:11:41.680> a<00:11:41.800> great<00:11:41.959> friend<00:11:42.240> group<00:11:42.639> it's<00:11:42.760> a<00:11:43.040> pretty 00:11:43.310 --> 00:11:43.320 align:start position:0% have a great friend group it's a pretty 00:11:43.320 --> 00:11:45.750 align:start position:0% have a great friend group it's a pretty basic<00:11:43.680> example<00:11:44.040> of<00:11:44.240> data<00:11:44.480> that<00:11:44.600> flows<00:11:44.959> through 00:11:45.750 --> 00:11:45.760 align:start position:0% basic example of data that flows through 00:11:45.760 --> 00:11:48.389 align:start position:0% basic example of data that flows through multiple<00:11:46.760> uh<00:11:46.920> multiple<00:11:47.399> programs<00:11:48.160> so 00:11:48.389 --> 00:11:48.399 align:start position:0% multiple uh multiple programs so 00:11:48.399 --> 00:11:49.870 align:start position:0% multiple uh multiple programs so abstractly<00:11:48.920> would<00:11:49.079> look<00:11:49.279> like<00:11:49.440> this<00:11:49.600> you<00:11:49.720> have 00:11:49.870 --> 00:11:49.880 align:start position:0% abstractly would look like this you have 00:11:49.880 --> 00:11:51.790 align:start position:0% abstractly would look like this you have a<00:11:50.200> bunch<00:11:50.440> of<00:11:50.600> PODS<00:11:50.800> that<00:11:50.959> come<00:11:51.120> in<00:11:51.519> they<00:11:51.639> go 00:11:51.790 --> 00:11:51.800 align:start position:0% a bunch of PODS that come in they go 00:11:51.800 --> 00:11:53.790 align:start position:0% a bunch of PODS that come in they go through<00:11:51.959> a<00:11:52.120> program<00:11:52.560> you<00:11:52.680> get<00:11:52.839> another<00:11:53.160> pod 00:11:53.790 --> 00:11:53.800 align:start position:0% through a program you get another pod 00:11:53.800 --> 00:11:55.269 align:start position:0% through a program you get another pod you<00:11:53.959> go<00:11:54.120> through<00:11:54.360> yet<00:11:54.519> another<00:11:54.839> program<00:11:55.200> and 00:11:55.269 --> 00:11:55.279 align:start position:0% you go through yet another program and 00:11:55.279 --> 00:11:58.350 align:start position:0% you go through yet another program and you<00:11:55.399> get<00:11:55.519> your<00:11:55.680> final<00:11:56.000> pod<00:11:56.959> so<00:11:57.320> the<00:11:57.480> trick<00:11:58.240> the 00:11:58.350 --> 00:11:58.360 align:start position:0% you get your final pod so the trick the 00:11:58.360 --> 00:12:00.190 align:start position:0% you get your final pod so the trick the tricky<00:11:58.680> thing<00:11:58.920> here<00:11:59.040> is<00:11:59.279> is<00:11:59.720> in<00:11:59.839> order<00:12:00.040> to 00:12:00.190 --> 00:12:00.200 align:start position:0% tricky thing here is is in order to 00:12:00.200 --> 00:12:01.790 align:start position:0% tricky thing here is is in order to implement<00:12:00.680> this<00:12:00.959> you<00:12:01.079> need<00:12:01.279> the<00:12:01.480> second 00:12:01.790 --> 00:12:01.800 align:start position:0% implement this you need the second 00:12:01.800 --> 00:12:04.030 align:start position:0% implement this you need the second program<00:12:02.160> to<00:12:02.639> understand<00:12:02.880> the<00:12:03.040> first<00:12:03.399> program 00:12:04.030 --> 00:12:04.040 align:start position:0% program to understand the first program 00:12:04.040 --> 00:12:06.269 align:start position:0% program to understand the first program right<00:12:04.519> if<00:12:04.639> I<00:12:04.760> were<00:12:04.920> to<00:12:05.040> tell<00:12:05.240> you<00:12:05.560> like 00:12:06.269 --> 00:12:06.279 align:start position:0% right if I were to tell you like 00:12:06.279 --> 00:12:09.750 align:start position:0% right if I were to tell you like 42<00:12:07.279> 42<00:12:07.639> is<00:12:07.720> the<00:12:07.839> output<00:12:08.120> of<00:12:08.200> my<00:12:08.399> program<00:12:09.399> unless 00:12:09.750 --> 00:12:09.760 align:start position:0% 42 42 is the output of my program unless 00:12:09.760 --> 00:12:12.110 align:start position:0% 42 42 is the output of my program unless you<00:12:09.920> know<00:12:10.320> what<00:12:10.600> program<00:12:10.959> I<00:12:11.120> executed<00:12:11.920> this 00:12:12.110 --> 00:12:12.120 align:start position:0% you know what program I executed this 00:12:12.120 --> 00:12:13.870 align:start position:0% you know what program I executed this data<00:12:12.399> type<00:12:12.639> does<00:12:12.760> not<00:12:12.920> mean<00:12:13.199> anything<00:12:13.519> to<00:12:13.680> you 00:12:13.870 --> 00:12:13.880 align:start position:0% data type does not mean anything to you 00:12:13.880 --> 00:12:16.550 align:start position:0% data type does not mean anything to you at<00:12:14.000> all<00:12:14.440> like<00:12:14.720> data<00:12:15.040> type<00:12:15.480> out<00:12:15.639> of<00:12:15.760> its<00:12:16.040> context 00:12:16.550 --> 00:12:16.560 align:start position:0% at all like data type out of its context 00:12:16.560 --> 00:12:19.230 align:start position:0% at all like data type out of its context is<00:12:16.920> basically<00:12:17.399> kind<00:12:17.519> of<00:12:17.720> useless<00:12:18.600> you<00:12:18.720> can<00:12:18.959> add 00:12:19.230 --> 00:12:19.240 align:start position:0% is basically kind of useless you can add 00:12:19.240 --> 00:12:21.230 align:start position:0% is basically kind of useless you can add things<00:12:19.519> like<00:12:19.680> schemas<00:12:20.240> Etc<00:12:20.639> but<00:12:20.760> it<00:12:20.880> becomes 00:12:21.230 --> 00:12:21.240 align:start position:0% things like schemas Etc but it becomes 00:12:21.240 --> 00:12:22.949 align:start position:0% things like schemas Etc but it becomes very<00:12:21.440> brittle<00:12:21.920> very<00:12:22.120> quickly<00:12:22.519> it's<00:12:22.720> really 00:12:22.949 --> 00:12:22.959 align:start position:0% very brittle very quickly it's really 00:12:22.959 --> 00:12:24.750 align:start position:0% very brittle very quickly it's really hard<00:12:23.199> to<00:12:23.480> compose<00:12:23.880> programs<00:12:24.199> on<00:12:24.360> top<00:12:24.480> of<00:12:24.600> each 00:12:24.750 --> 00:12:24.760 align:start position:0% hard to compose programs on top of each 00:12:24.760 --> 00:12:27.550 align:start position:0% hard to compose programs on top of each other<00:12:25.440> so<00:12:26.120> let's<00:12:26.360> say<00:12:26.920> these<00:12:27.079> two<00:12:27.240> programs 00:12:27.550 --> 00:12:27.560 align:start position:0% other so let's say these two programs 00:12:27.560 --> 00:12:28.870 align:start position:0% other so let's say these two programs are<00:12:27.680> built<00:12:27.959> by<00:12:28.120> different<00:12:28.399> people<00:12:28.720> at 00:12:28.870 --> 00:12:28.880 align:start position:0% are built by different people at 00:12:28.880 --> 00:12:30.829 align:start position:0% are built by different people at different<00:12:29.240> point<00:12:29.440> of<00:12:29.720> in<00:12:29.920> time<00:12:30.440> there's<00:12:30.680> one 00:12:30.829 --> 00:12:30.839 align:start position:0% different point of in time there's one 00:12:30.839 --> 00:12:32.230 align:start position:0% different point of in time there's one solution<00:12:31.160> to<00:12:31.360> this<00:12:31.519> which<00:12:31.639> is<00:12:31.800> like<00:12:32.040> every 00:12:32.230 --> 00:12:32.240 align:start position:0% solution to this which is like every 00:12:32.240 --> 00:12:34.110 align:start position:0% solution to this which is like every time<00:12:32.440> a<00:12:32.680> program<00:12:33.160> consumes<00:12:33.639> data<00:12:33.880> from<00:12:34.000> a 00:12:34.110 --> 00:12:34.120 align:start position:0% time a program consumes data from a 00:12:34.120 --> 00:12:36.030 align:start position:0% time a program consumes data from a different<00:12:34.399> program<00:12:34.680> you<00:12:34.880> hardcode<00:12:35.680> the<00:12:35.800> fact 00:12:36.030 --> 00:12:36.040 align:start position:0% different program you hardcode the fact 00:12:36.040 --> 00:12:37.949 align:start position:0% different program you hardcode the fact that<00:12:36.279> hey<00:12:36.399> I<00:12:36.519> know<00:12:36.720> this<00:12:36.880> out<00:12:37.199> program<00:12:37.560> behaves 00:12:37.949 --> 00:12:37.959 align:start position:0% that hey I know this out program behaves 00:12:37.959 --> 00:12:39.230 align:start position:0% that hey I know this out program behaves this<00:12:38.120> way<00:12:38.440> I'm<00:12:38.560> going<00:12:38.639> to<00:12:38.760> interpret<00:12:39.160> the 00:12:39.230 --> 00:12:39.240 align:start position:0% this way I'm going to interpret the 00:12:39.240 --> 00:12:41.470 align:start position:0% this way I'm going to interpret the output<00:12:39.519> in<00:12:39.600> a<00:12:39.880> in<00:12:40.000> that<00:12:40.160> specific<00:12:40.560> way<00:12:41.279> if<00:12:41.399> you 00:12:41.470 --> 00:12:41.480 align:start position:0% output in a in that specific way if you 00:12:41.480 --> 00:12:43.310 align:start position:0% output in a in that specific way if you want<00:12:41.600> to<00:12:41.760> do<00:12:41.920> it<00:12:42.480> just<00:12:42.680> in<00:12:42.880> time<00:12:43.040> or<00:12:43.199> like 00:12:43.310 --> 00:12:43.320 align:start position:0% want to do it just in time or like 00:12:43.320 --> 00:12:46.470 align:start position:0% want to do it just in time or like dynamically<00:12:43.880> you<00:12:43.959> need<00:12:44.160> to<00:12:45.160> start<00:12:45.399> going<00:12:45.600> into 00:12:46.470 --> 00:12:46.480 align:start position:0% dynamically you need to start going into 00:12:46.480 --> 00:12:48.829 align:start position:0% dynamically you need to start going into um<00:12:47.000> systems<00:12:47.399> that<00:12:47.519> are<00:12:47.800> pretty<00:12:48.120> hard<00:12:48.360> to<00:12:48.560> work 00:12:48.829 --> 00:12:48.839 align:start position:0% um systems that are pretty hard to work 00:12:48.839 --> 00:12:50.829 align:start position:0% um systems that are pretty hard to work without<00:12:49.120> human<00:12:49.440> interventions<00:12:50.440> things<00:12:50.680> like 00:12:50.829 --> 00:12:50.839 align:start position:0% without human interventions things like 00:12:50.839 --> 00:12:53.470 align:start position:0% without human interventions things like static<00:12:51.199> analysis<00:12:51.720> formal<00:12:52.120> proofs<00:12:52.480> Etc<00:12:53.240> and<00:12:53.360> we 00:12:53.470 --> 00:12:53.480 align:start position:0% static analysis formal proofs Etc and we 00:12:53.480 --> 00:12:55.269 align:start position:0% static analysis formal proofs Etc and we know<00:12:53.720> from<00:12:54.000> the<00:12:54.120> halting<00:12:54.519> problem<00:12:54.839> theorem 00:12:55.269 --> 00:12:55.279 align:start position:0% know from the halting problem theorem 00:12:55.279 --> 00:12:57.670 align:start position:0% know from the halting problem theorem that<00:12:55.480> in<00:12:55.600> the<00:12:55.800> limit<00:12:56.760> uh<00:12:56.920> it's<00:12:57.120> really<00:12:57.320> hard 00:12:57.670 --> 00:12:57.680 align:start position:0% that in the limit uh it's really hard 00:12:57.680 --> 00:12:59.509 align:start position:0% that in the limit uh it's really hard it's<00:12:57.880> basically<00:12:58.639> uncomputable<00:12:59.320> for<00:12:59.440> a 00:12:59.509 --> 00:12:59.519 align:start position:0% it's basically uncomputable for a 00:12:59.519 --> 00:13:01.550 align:start position:0% it's basically uncomputable for a program<00:12:59.760> to<00:12:59.880> analyze<00:13:00.279> another<00:13:00.600> program<00:13:01.279> or<00:13:01.480> at 00:13:01.550 --> 00:13:01.560 align:start position:0% program to analyze another program or at 00:13:01.560 --> 00:13:04.910 align:start position:0% program to analyze another program or at least<00:13:01.760> for<00:13:01.959> some<00:13:02.199> kind<00:13:02.320> of<00:13:02.680> properties<00:13:03.800> so<00:13:04.800> the 00:13:04.910 --> 00:13:04.920 align:start position:0% least for some kind of properties so the 00:13:04.920 --> 00:13:06.110 align:start position:0% least for some kind of properties so the approach<00:13:05.199> we've<00:13:05.399> taken<00:13:05.680> there<00:13:05.839> is<00:13:05.959> to 00:13:06.110 --> 00:13:06.120 align:start position:0% approach we've taken there is to 00:13:06.120 --> 00:13:08.230 align:start position:0% approach we've taken there is to essentially<00:13:06.519> throw<00:13:06.800> away<00:13:07.000> the<00:13:07.160> CPU<00:13:07.560> model<00:13:08.040> and 00:13:08.230 --> 00:13:08.240 align:start position:0% essentially throw away the CPU model and 00:13:08.240 --> 00:13:11.150 align:start position:0% essentially throw away the CPU model and go<00:13:08.399> towards<00:13:08.760> logic<00:13:09.519> so<00:13:10.360> what<00:13:10.480> I<00:13:10.560> mean<00:13:10.760> by<00:13:10.959> this 00:13:11.150 --> 00:13:11.160 align:start position:0% go towards logic so what I mean by this 00:13:11.160 --> 00:13:13.189 align:start position:0% go towards logic so what I mean by this is<00:13:11.519> instead<00:13:11.800> of<00:13:11.959> as<00:13:12.079> an<00:13:12.199> example<00:13:12.480> executing<00:13:12.920> up 00:13:13.189 --> 00:13:13.199 align:start position:0% is instead of as an example executing up 00:13:13.199 --> 00:13:16.150 align:start position:0% is instead of as an example executing up code<00:13:13.720> in<00:13:13.959> in<00:13:14.079> a<00:13:14.199> virtual<00:13:14.560> risk<00:13:14.839> 5<00:13:15.040> CPU<00:13:15.519> ASM<00:13:15.800> CPU 00:13:16.150 --> 00:13:16.160 align:start position:0% code in in a virtual risk 5 CPU ASM CPU 00:13:16.160 --> 00:13:18.230 align:start position:0% code in in a virtual risk 5 CPU ASM CPU we<00:13:16.279> execute<00:13:16.639> logical<00:13:17.040> operations<00:13:17.519> logical 00:13:18.230 --> 00:13:18.240 align:start position:0% we execute logical operations logical 00:13:18.240 --> 00:13:20.509 align:start position:0% we execute logical operations logical deductions<00:13:19.240> um<00:13:19.560> so<00:13:19.800> you<00:13:19.880> would<00:13:20.079> have 00:13:20.509 --> 00:13:20.519 align:start position:0% deductions um so you would have 00:13:20.519 --> 00:13:22.910 align:start position:0% deductions um so you would have something<00:13:20.959> like<00:13:21.120> a<00:13:21.480> logic<00:13:21.800> virtual<00:13:22.160> machine 00:13:22.910 --> 00:13:22.920 align:start position:0% something like a logic virtual machine 00:13:22.920 --> 00:13:24.629 align:start position:0% something like a logic virtual machine where<00:13:23.040> you<00:13:23.320> replace<00:13:23.760> memory<00:13:24.079> slots<00:13:24.480> with 00:13:24.629 --> 00:13:24.639 align:start position:0% where you replace memory slots with 00:13:24.639 --> 00:13:26.550 align:start position:0% where you replace memory slots with logical<00:13:25.120> statements<00:13:25.720> so<00:13:25.880> instead<00:13:26.160> of<00:13:26.399> this 00:13:26.550 --> 00:13:26.560 align:start position:0% logical statements so instead of this 00:13:26.560 --> 00:13:28.230 align:start position:0% logical statements so instead of this piece<00:13:26.720> of<00:13:26.839> data<00:13:27.040> is<00:13:27.120> at<00:13:27.279> this<00:13:27.399> slot<00:13:27.639> in<00:13:27.720> memory 00:13:28.230 --> 00:13:28.240 align:start position:0% piece of data is at this slot in memory 00:13:28.240 --> 00:13:29.870 align:start position:0% piece of data is at this slot in memory it's<00:13:28.440> like<00:13:28.839> there<00:13:28.959> is<00:13:29.120> is<00:13:29.240> a<00:13:29.320> statement<00:13:29.720> that 00:13:29.870 --> 00:13:29.880 align:start position:0% it's like there is is a statement that 00:13:29.880 --> 00:13:32.870 align:start position:0% it's like there is is a statement that says<00:13:30.680> uh<00:13:30.839> there<00:13:31.000> exist<00:13:31.320> an<00:13:31.480> a<00:13:31.760> such<00:13:32.120> that<00:13:32.639> a 00:13:32.870 --> 00:13:32.880 align:start position:0% says uh there exist an a such that a 00:13:32.880 --> 00:13:36.150 align:start position:0% says uh there exist an a such that a implies<00:13:33.800> whatever<00:13:34.800> um<00:13:35.199> that<00:13:35.399> kind<00:13:35.560> of<00:13:35.760> logical 00:13:36.150 --> 00:13:36.160 align:start position:0% implies whatever um that kind of logical 00:13:36.160 --> 00:13:37.870 align:start position:0% implies whatever um that kind of logical statements<00:13:36.720> you<00:13:36.880> replace<00:13:37.279> up<00:13:37.519> code<00:13:37.720> with 00:13:37.870 --> 00:13:37.880 align:start position:0% statements you replace up code with 00:13:37.880 --> 00:13:40.150 align:start position:0% statements you replace up code with logical<00:13:38.320> operations<00:13:38.760> or<00:13:38.959> deductions<00:13:39.760> so 00:13:40.150 --> 00:13:40.160 align:start position:0% logical operations or deductions so 00:13:40.160 --> 00:13:42.069 align:start position:0% logical operations or deductions so here's<00:13:40.360> a<00:13:40.519> deduction<00:13:40.920> as<00:13:41.040> an<00:13:41.199> example<00:13:41.680> if<00:13:41.839> a<00:13:42.000> is 00:13:42.069 --> 00:13:42.079 align:start position:0% here's a deduction as an example if a is 00:13:42.079 --> 00:13:44.110 align:start position:0% here's a deduction as an example if a is smaller<00:13:42.399> than<00:13:42.560> b<00:13:43.000> you<00:13:43.120> can<00:13:43.240> deduce<00:13:43.639> that<00:13:43.760> a<00:13:44.000> is 00:13:44.110 --> 00:13:44.120 align:start position:0% smaller than b you can deduce that a is 00:13:44.120 --> 00:13:46.750 align:start position:0% smaller than b you can deduce that a is not<00:13:44.279> equal<00:13:44.600> b<00:13:45.240> or<00:13:45.399> if<00:13:45.600> a<00:13:45.760> is<00:13:45.920> defined<00:13:46.240> as<00:13:46.399> 10<00:13:46.639> and 00:13:46.750 --> 00:13:46.760 align:start position:0% not equal b or if a is defined as 10 and 00:13:46.760 --> 00:13:49.069 align:start position:0% not equal b or if a is defined as 10 and B<00:13:46.920> is<00:13:47.000> defined<00:13:47.279> as<00:13:47.440> 10<00:13:47.920> you<00:13:48.000> can<00:13:48.440> deduce<00:13:48.880> a 00:13:49.069 --> 00:13:49.079 align:start position:0% B is defined as 10 you can deduce a 00:13:49.079 --> 00:13:52.590 align:start position:0% B is defined as 10 you can deduce a equals<00:13:49.399> B<00:13:50.360> data<00:13:50.680> becomes<00:13:51.440> theorems<00:13:52.440> uh 00:13:52.590 --> 00:13:52.600 align:start position:0% equals B data becomes theorems uh 00:13:52.600 --> 00:13:54.790 align:start position:0% equals B data becomes theorems uh programs<00:13:53.079> become<00:13:53.360> proofs<00:13:53.920> so<00:13:54.199> mathematical 00:13:54.790 --> 00:13:54.800 align:start position:0% programs become proofs so mathematical 00:13:54.800 --> 00:13:57.189 align:start position:0% programs become proofs so mathematical proofs<00:13:55.759> and<00:13:55.920> your<00:13:56.079> system<00:13:56.480> looks<00:13:56.720> like<00:13:56.920> this 00:13:57.189 --> 00:13:57.199 align:start position:0% proofs and your system looks like this 00:13:57.199 --> 00:13:58.749 align:start position:0% proofs and your system looks like this where<00:13:57.480> you<00:13:57.680> have<00:13:57.839> some<00:13:58.000> pieces<00:13:58.240> of<00:13:58.399> data<00:13:58.639> that 00:13:58.749 --> 00:13:58.759 align:start position:0% where you have some pieces of data that 00:13:58.759 --> 00:14:00.350 align:start position:0% where you have some pieces of data that exist<00:13:59.199> that<00:13:59.279> they'<00:13:59.440> been<00:13:59.560> attested<00:13:59.959> to<00:14:00.240> you 00:14:00.350 --> 00:14:00.360 align:start position:0% exist that they' been attested to you 00:14:00.360 --> 00:14:02.389 align:start position:0% exist that they' been attested to you treat<00:14:00.639> them<00:14:00.759> as<00:14:00.920> axioms<00:14:01.839> and<00:14:01.959> then<00:14:02.160> through 00:14:02.389 --> 00:14:02.399 align:start position:0% treat them as axioms and then through 00:14:02.399 --> 00:14:04.069 align:start position:0% treat them as axioms and then through logical<00:14:02.800> proofs<00:14:03.079> you<00:14:03.240> produce<00:14:03.560> theorems<00:14:03.959> that 00:14:04.069 --> 00:14:04.079 align:start position:0% logical proofs you produce theorems that 00:14:04.079 --> 00:14:06.430 align:start position:0% logical proofs you produce theorems that they<00:14:04.360> themselves<00:14:04.639> produce<00:14:04.920> new<00:14:05.079> theorems<00:14:05.440> Etc 00:14:06.430 --> 00:14:06.440 align:start position:0% they themselves produce new theorems Etc 00:14:06.440 --> 00:14:08.509 align:start position:0% they themselves produce new theorems Etc the<00:14:06.600> reason<00:14:06.920> why<00:14:07.160> this<00:14:07.360> works<00:14:07.680> in<00:14:07.880> theory<00:14:08.360> is 00:14:08.509 --> 00:14:08.519 align:start position:0% the reason why this works in theory is 00:14:08.519 --> 00:14:11.550 align:start position:0% the reason why this works in theory is that<00:14:08.800> math<00:14:09.360> is<00:14:09.639> built<00:14:10.000> to<00:14:10.160> be<00:14:10.440> interoperable<00:14:11.440> I 00:14:11.550 --> 00:14:11.560 align:start position:0% that math is built to be interoperable I 00:14:11.560 --> 00:14:13.189 align:start position:0% that math is built to be interoperable I can<00:14:11.720> give<00:14:11.839> you<00:14:11.959> a<00:14:12.120> theorem<00:14:12.680> if<00:14:12.759> you<00:14:12.920> believe 00:14:13.189 --> 00:14:13.199 align:start position:0% can give you a theorem if you believe 00:14:13.199 --> 00:14:14.470 align:start position:0% can give you a theorem if you believe that<00:14:13.320> theorem<00:14:13.639> has<00:14:13.759> been<00:14:13.920> proven<00:14:14.240> you<00:14:14.320> can 00:14:14.470 --> 00:14:14.480 align:start position:0% that theorem has been proven you can 00:14:14.480 --> 00:14:16.230 align:start position:0% that theorem has been proven you can prove<00:14:14.720> more<00:14:14.920> things<00:14:15.240> using<00:14:15.480> my<00:14:15.639> theorem<00:14:15.959> or<00:14:16.079> my 00:14:16.230 --> 00:14:16.240 align:start position:0% prove more things using my theorem or my 00:14:16.240 --> 00:14:18.870 align:start position:0% prove more things using my theorem or my LMA<00:14:17.000> it's<00:14:17.360> very<00:14:17.639> much<00:14:18.160> different<00:14:18.519> from<00:14:18.720> the 00:14:18.870 --> 00:14:18.880 align:start position:0% LMA it's very much different from the 00:14:18.880 --> 00:14:21.110 align:start position:0% LMA it's very much different from the story<00:14:19.360> with<00:14:19.759> programs<00:14:20.279> and<00:14:20.440> computation<00:14:20.959> in 00:14:21.110 --> 00:14:21.120 align:start position:0% story with programs and computation in 00:14:21.120 --> 00:14:23.110 align:start position:0% story with programs and computation in general<00:14:21.920> so<00:14:22.040> now<00:14:22.199> if<00:14:22.279> we<00:14:22.440> take<00:14:22.680> back<00:14:22.880> this 00:14:23.110 --> 00:14:23.120 align:start position:0% general so now if we take back this 00:14:23.120 --> 00:14:26.350 align:start position:0% general so now if we take back this example<00:14:23.480> I<00:14:23.800> gave<00:14:24.800> um<00:14:25.600> the<00:14:25.720> way<00:14:25.839> you<00:14:25.920> would<00:14:26.079> turn 00:14:26.350 --> 00:14:26.360 align:start position:0% example I gave um the way you would turn 00:14:26.360 --> 00:14:28.790 align:start position:0% example I gave um the way you would turn this<00:14:26.519> into<00:14:26.920> is<00:14:27.720> you<00:14:27.839> have<00:14:27.959> the<00:14:28.079> blue<00:14:28.399> theorem 00:14:28.790 --> 00:14:28.800 align:start position:0% this into is you have the blue theorem 00:14:28.800 --> 00:14:31.189 align:start position:0% this into is you have the blue theorem which<00:14:29.199> is<00:14:29.600> Justin<00:14:30.000> has<00:14:30.160> 13<00:14:30.560> best<00:14:30.720> friends<00:14:31.120> and 00:14:31.189 --> 00:14:31.199 align:start position:0% which is Justin has 13 best friends and 00:14:31.199 --> 00:14:32.550 align:start position:0% which is Justin has 13 best friends and you<00:14:31.279> want<00:14:31.399> to<00:14:31.480> get<00:14:31.560> to<00:14:31.680> the<00:14:31.759> green<00:14:32.000> theorem 00:14:32.550 --> 00:14:32.560 align:start position:0% you want to get to the green theorem 00:14:32.560 --> 00:14:34.310 align:start position:0% you want to get to the green theorem which<00:14:32.639> is<00:14:32.920> Justin<00:14:33.279> is<00:14:33.360> a<00:14:33.480> great<00:14:33.639> friend<00:14:33.880> group 00:14:34.310 --> 00:14:34.320 align:start position:0% which is Justin is a great friend group 00:14:34.320 --> 00:14:35.590 align:start position:0% which is Justin is a great friend group and<00:14:34.399> so<00:14:34.560> if<00:14:34.639> you<00:14:34.759> write<00:14:34.959> this<00:14:35.079> down<00:14:35.240> in<00:14:35.360> plain 00:14:35.590 --> 00:14:35.600 align:start position:0% and so if you write this down in plain 00:14:35.600 --> 00:14:37.389 align:start position:0% and so if you write this down in plain English<00:14:36.240> you<00:14:36.360> would<00:14:36.519> have<00:14:36.680> something<00:14:37.079> like<00:14:37.320> I 00:14:37.389 --> 00:14:37.399 align:start position:0% English you would have something like I 00:14:37.399 --> 00:14:39.269 align:start position:0% English you would have something like I have<00:14:37.519> 12<00:14:37.839> best<00:14:38.000> friends<00:14:38.399> implies<00:14:38.920> I<00:14:39.000> have<00:14:39.120> more 00:14:39.269 --> 00:14:39.279 align:start position:0% have 12 best friends implies I have more 00:14:39.279 --> 00:14:41.550 align:start position:0% have 12 best friends implies I have more than<00:14:39.399> three<00:14:39.600> best<00:14:39.920> friends<00:14:40.920> um<00:14:41.160> so<00:14:41.320> now<00:14:41.440> you 00:14:41.550 --> 00:14:41.560 align:start position:0% than three best friends um so now you 00:14:41.560 --> 00:14:42.949 align:start position:0% than three best friends um so now you get<00:14:41.639> to<00:14:41.759> a<00:14:41.880> system<00:14:42.120> with<00:14:42.240> two<00:14:42.399> kinds<00:14:42.600> of<00:14:42.720> proof 00:14:42.949 --> 00:14:42.959 align:start position:0% get to a system with two kinds of proof 00:14:42.959 --> 00:14:44.470 align:start position:0% get to a system with two kinds of proof formal<00:14:43.320> proofs<00:14:43.560> and<00:14:43.680> zero<00:14:43.880> knowledge<00:14:44.160> proofs 00:14:44.470 --> 00:14:44.480 align:start position:0% formal proofs and zero knowledge proofs 00:14:44.480 --> 00:14:46.069 align:start position:0% formal proofs and zero knowledge proofs the<00:14:44.600> zero<00:14:44.800> knowledge<00:14:45.079> proofs<00:14:45.360> are<00:14:45.519> used<00:14:45.839> to 00:14:46.069 --> 00:14:46.079 align:start position:0% the zero knowledge proofs are used to 00:14:46.079 --> 00:14:47.550 align:start position:0% the zero knowledge proofs are used to both<00:14:46.240> show<00:14:46.519> that<00:14:46.639> the<00:14:46.720> formal<00:14:47.079> proofs<00:14:47.360> were 00:14:47.550 --> 00:14:47.560 align:start position:0% both show that the formal proofs were 00:14:47.560 --> 00:14:49.590 align:start position:0% both show that the formal proofs were executed<00:14:48.040> correctly<00:14:48.600> but<00:14:48.759> also<00:14:48.959> as<00:14:49.079> a<00:14:49.199> way<00:14:49.320> to 00:14:49.590 --> 00:14:49.600 align:start position:0% executed correctly but also as a way to 00:14:49.600 --> 00:14:51.790 align:start position:0% executed correctly but also as a way to remove<00:14:50.519> specific<00:14:50.880> inputs<00:14:51.199> to<00:14:51.320> the<00:14:51.440> formal 00:14:51.790 --> 00:14:51.800 align:start position:0% remove specific inputs to the formal 00:14:51.800 --> 00:14:53.590 align:start position:0% remove specific inputs to the formal proof<00:14:52.399> as<00:14:52.480> an<00:14:52.639> example<00:14:52.920> if<00:14:53.079> I<00:14:53.199> Constructor 00:14:53.590 --> 00:14:53.600 align:start position:0% proof as an example if I Constructor 00:14:53.600 --> 00:14:55.230 align:start position:0% proof as an example if I Constructor formal<00:14:53.920> proof<00:14:54.160> that<00:14:54.279> shows<00:14:54.600> that<00:14:54.759> my<00:14:54.920> age<00:14:55.120> is 00:14:55.230 --> 00:14:55.240 align:start position:0% formal proof that shows that my age is 00:14:55.240 --> 00:14:57.949 align:start position:0% formal proof that shows that my age is over<00:14:55.480> 21<00:14:56.240> I<00:14:56.360> may<00:14:56.519> want<00:14:56.639> to<00:14:56.839> remove<00:14:57.279> the<00:14:57.440> axium 00:14:57.949 --> 00:14:57.959 align:start position:0% over 21 I may want to remove the axium 00:14:57.959 --> 00:14:59.670 align:start position:0% over 21 I may want to remove the axium that<00:14:58.079> says<00:14:58.360> what<00:14:58.480> my<00:14:58.639> age<00:14:58.839> is 00:14:59.670 --> 00:14:59.680 align:start position:0% that says what my age is 00:14:59.680 --> 00:15:01.509 align:start position:0% that says what my age is while<00:14:59.839> you<00:15:00.000> can<00:15:00.160> still<00:15:00.440> audit<00:15:01.120> the<00:15:01.240> audit 00:15:01.509 --> 00:15:01.519 align:start position:0% while you can still audit the audit 00:15:01.519 --> 00:15:04.310 align:start position:0% while you can still audit the audit trail<00:15:01.759> of<00:15:01.880> this<00:15:02.040> axom<00:15:02.399> in<00:15:02.519> the<00:15:02.639> first<00:15:02.920> place<00:15:03.880> so 00:15:04.310 --> 00:15:04.320 align:start position:0% trail of this axom in the first place so 00:15:04.320 --> 00:15:05.550 align:start position:0% trail of this axom in the first place so this<00:15:04.440> is<00:15:04.519> all<00:15:04.639> a<00:15:04.720> little<00:15:04.839> bit<00:15:05.000> abstract<00:15:05.440> that's 00:15:05.550 --> 00:15:05.560 align:start position:0% this is all a little bit abstract that's 00:15:05.560 --> 00:15:07.629 align:start position:0% this is all a little bit abstract that's why<00:15:05.680> we'll<00:15:05.839> do<00:15:06.079> coding<00:15:06.639> after<00:15:06.880> this<00:15:07.320> and<00:15:07.440> we'll 00:15:07.629 --> 00:15:07.639 align:start position:0% why we'll do coding after this and we'll 00:15:07.639 --> 00:15:09.269 align:start position:0% why we'll do coding after this and we'll see<00:15:07.839> it<00:15:08.040> either<00:15:08.279> break<00:15:08.519> or<00:15:08.639> succeed<00:15:09.000> in<00:15:09.079> front 00:15:09.269 --> 00:15:09.279 align:start position:0% see it either break or succeed in front 00:15:09.279 --> 00:15:11.310 align:start position:0% see it either break or succeed in front of<00:15:09.399> our<00:15:09.600> eyes<00:15:10.320> so<00:15:10.480> the<00:15:10.639> great<00:15:10.839> thing<00:15:10.959> with<00:15:11.160> this 00:15:11.310 --> 00:15:11.320 align:start position:0% of our eyes so the great thing with this 00:15:11.320 --> 00:15:13.269 align:start position:0% of our eyes so the great thing with this is<00:15:11.440> that<00:15:11.600> you<00:15:11.680> can<00:15:12.160> kind<00:15:12.279> of<00:15:12.519> compute<00:15:12.880> theorems 00:15:13.269 --> 00:15:13.279 align:start position:0% is that you can kind of compute theorems 00:15:13.279 --> 00:15:14.749 align:start position:0% is that you can kind of compute theorems on<00:15:13.399> top<00:15:13.519> of<00:15:13.600> theorems<00:15:13.959> on<00:15:14.079> top<00:15:14.199> of<00:15:14.320> theorems<00:15:14.680> at 00:15:14.749 --> 00:15:14.759 align:start position:0% on top of theorems on top of theorems at 00:15:14.759 --> 00:15:16.749 align:start position:0% on top of theorems on top of theorems at least<00:15:14.880> if<00:15:15.000> we<00:15:15.120> build<00:15:15.320> the<00:15:15.399> system<00:15:15.759> correctly 00:15:16.749 --> 00:15:16.759 align:start position:0% least if we build the system correctly 00:15:16.759 --> 00:15:18.069 align:start position:0% least if we build the system correctly and<00:15:16.920> as<00:15:17.040> an<00:15:17.199> example<00:15:17.519> I<00:15:17.600> will<00:15:17.720> show<00:15:17.880> you<00:15:18.000> a 00:15:18.069 --> 00:15:18.079 align:start position:0% and as an example I will show you a 00:15:18.079 --> 00:15:19.990 align:start position:0% and as an example I will show you a little<00:15:18.279> bit<00:15:18.560> how<00:15:18.839> a<00:15:19.000> very<00:15:19.199> early<00:15:19.480> version<00:15:19.720> of<00:15:19.839> a 00:15:19.990 --> 00:15:20.000 align:start position:0% little bit how a very early version of a 00:15:20.000 --> 00:15:22.509 align:start position:0% little bit how a very early version of a system<00:15:20.279> works<00:15:20.759> so<00:15:21.720> this<00:15:21.839> is<00:15:21.959> the<00:15:22.120> list<00:15:22.360> of 00:15:22.509 --> 00:15:22.519 align:start position:0% system works so this is the list of 00:15:22.519 --> 00:15:24.069 align:start position:0% system works so this is the list of logical<00:15:23.000> statements<00:15:23.440> that<00:15:23.560> can<00:15:23.680> exist<00:15:23.880> in<00:15:23.959> a 00:15:24.069 --> 00:15:24.079 align:start position:0% logical statements that can exist in a 00:15:24.079 --> 00:15:26.350 align:start position:0% logical statements that can exist in a piece<00:15:24.240> of<00:15:24.399> data<00:15:25.160> this<00:15:25.279> is<00:15:25.399> the<00:15:25.560> most<00:15:25.839> basic<00:15:26.120> one 00:15:26.350 --> 00:15:26.360 align:start position:0% piece of data this is the most basic one 00:15:26.360 --> 00:15:28.990 align:start position:0% piece of data this is the most basic one which<00:15:26.480> is<00:15:26.639> the<00:15:26.880> value<00:15:27.160> of<00:15:27.279> a<00:15:27.480> key<00:15:27.880> is<00:15:28.000> a<00:15:28.279> scalar 00:15:28.990 --> 00:15:29.000 align:start position:0% which is the value of a key is a scalar 00:15:29.000 --> 00:15:31.470 align:start position:0% which is the value of a key is a scalar or<00:15:29.519> a<00:15:29.600> vector<00:15:29.839> of<00:15:29.959> scaler<00:15:30.759> this<00:15:30.880> is<00:15:31.079> basically 00:15:31.470 --> 00:15:31.480 align:start position:0% or a vector of scaler this is basically 00:15:31.480 --> 00:15:33.230 align:start position:0% or a vector of scaler this is basically what<00:15:31.600> you<00:15:31.759> usually<00:15:32.199> have<00:15:32.399> when<00:15:32.519> you<00:15:32.639> have<00:15:32.839> data 00:15:33.230 --> 00:15:33.240 align:start position:0% what you usually have when you have data 00:15:33.240 --> 00:15:35.949 align:start position:0% what you usually have when you have data which<00:15:33.360> is<00:15:33.720> the<00:15:33.839> value<00:15:34.120> of<00:15:34.279> AG<00:15:34.680> is<00:15:34.880> 26<00:15:35.600> or<00:15:35.800> the 00:15:35.949 --> 00:15:35.959 align:start position:0% which is the value of AG is 26 or the 00:15:35.959 --> 00:15:38.710 align:start position:0% which is the value of AG is 26 or the value<00:15:36.480> of<00:15:37.440> I<00:15:37.519> don't<00:15:37.680> know<00:15:37.959> something<00:15:38.240> else<00:15:38.480> is 00:15:38.710 --> 00:15:38.720 align:start position:0% value of I don't know something else is 00:15:38.720 --> 00:15:40.790 align:start position:0% value of I don't know something else is this<00:15:38.959> list<00:15:39.160> of<00:15:39.279> numbers<00:15:40.199> but<00:15:40.319> then<00:15:40.440> on<00:15:40.600> top<00:15:40.720> of 00:15:40.790 --> 00:15:40.800 align:start position:0% this list of numbers but then on top of 00:15:40.800 --> 00:15:41.870 align:start position:0% this list of numbers but then on top of that<00:15:40.920> we<00:15:41.000> have<00:15:41.120> other<00:15:41.319> kind<00:15:41.440> of<00:15:41.560> logical 00:15:41.870 --> 00:15:41.880 align:start position:0% that we have other kind of logical 00:15:41.880 --> 00:15:43.069 align:start position:0% that we have other kind of logical statement<00:15:42.240> so<00:15:42.360> as<00:15:42.440> an<00:15:42.519> example<00:15:42.800> we<00:15:42.880> have<00:15:42.959> an 00:15:43.069 --> 00:15:43.079 align:start position:0% statement so as an example we have an 00:15:43.079 --> 00:15:44.590 align:start position:0% statement so as an example we have an equal<00:15:43.399> statement<00:15:43.759> that<00:15:43.880> says<00:15:44.120> well<00:15:44.279> this<00:15:44.440> key 00:15:44.590 --> 00:15:44.600 align:start position:0% equal statement that says well this key 00:15:44.600 --> 00:15:46.550 align:start position:0% equal statement that says well this key equals<00:15:44.959> that<00:15:45.199> key<00:15:45.720> this<00:15:45.880> seems<00:15:46.120> a<00:15:46.199> little<00:15:46.399> bit 00:15:46.550 --> 00:15:46.560 align:start position:0% equals that key this seems a little bit 00:15:46.560 --> 00:15:48.470 align:start position:0% equals that key this seems a little bit silly<00:15:46.920> because<00:15:47.079> if<00:15:47.199> you<00:15:47.279> see<00:15:47.480> the<00:15:47.680> two<00:15:47.880> keys 00:15:48.470 --> 00:15:48.480 align:start position:0% silly because if you see the two keys 00:15:48.480 --> 00:15:50.110 align:start position:0% silly because if you see the two keys well<00:15:48.680> you<00:15:48.759> can<00:15:49.000> derve<00:15:49.480> they<00:15:49.680> close<00:15:49.920> to<00:15:50.000> each 00:15:50.110 --> 00:15:50.120 align:start position:0% well you can derve they close to each 00:15:50.120 --> 00:15:51.389 align:start position:0% well you can derve they close to each other<00:15:50.319> but<00:15:50.440> what<00:15:50.560> if<00:15:50.680> one<00:15:50.759> of<00:15:50.880> the<00:15:50.959> keys<00:15:51.240> not 00:15:51.389 --> 00:15:51.399 align:start position:0% other but what if one of the keys not 00:15:51.399 --> 00:15:53.389 align:start position:0% other but what if one of the keys not there<00:15:51.560> anymore<00:15:52.199> right<00:15:52.360> and<00:15:52.480> it's<00:15:52.600> using<00:15:52.959> yet 00:15:53.389 --> 00:15:53.399 align:start position:0% there anymore right and it's using yet 00:15:53.399 --> 00:15:56.230 align:start position:0% there anymore right and it's using yet different<00:15:53.800> statements<00:15:54.800> um<00:15:55.440> here's<00:15:55.639> a<00:15:55.759> turnar 00:15:56.230 --> 00:15:56.240 align:start position:0% different statements um here's a turnar 00:15:56.240 --> 00:15:58.470 align:start position:0% different statements um here's a turnar statements<00:15:56.720> which<00:15:56.839> ISS<00:15:57.040> that<00:15:57.199> the<00:15:57.360> sum<00:15:57.839> of 00:15:58.470 --> 00:15:58.480 align:start position:0% statements which ISS that the sum of 00:15:58.480 --> 00:16:00.590 align:start position:0% statements which ISS that the sum of these<00:15:58.639> two<00:15:59.000> Keys<00:15:59.360> equals<00:15:59.680> the<00:15:59.839> third<00:16:00.160> key 00:16:00.590 --> 00:16:00.600 align:start position:0% these two Keys equals the third key 00:16:00.600 --> 00:16:02.269 align:start position:0% these two Keys equals the third key right<00:16:00.959> so<00:16:01.279> you<00:16:01.560> you<00:16:01.639> have<00:16:01.759> to<00:16:01.839> think<00:16:02.000> in<00:16:02.079> terms 00:16:02.269 --> 00:16:02.279 align:start position:0% right so you you have to think in terms 00:16:02.279 --> 00:16:03.949 align:start position:0% right so you you have to think in terms of<00:16:02.399> logic<00:16:02.680> and<00:16:02.800> not<00:16:02.920> in<00:16:03.000> terms<00:16:03.199> of<00:16:03.360> computation 00:16:03.949 --> 00:16:03.959 align:start position:0% of logic and not in terms of computation 00:16:03.959 --> 00:16:06.910 align:start position:0% of logic and not in terms of computation anymore<00:16:04.959> here's<00:16:05.279> a<00:16:05.480> a<00:16:05.600> list<00:16:05.800> of<00:16:05.959> operation<00:16:06.639> so 00:16:06.910 --> 00:16:06.920 align:start position:0% anymore here's a a list of operation so 00:16:06.920 --> 00:16:08.949 align:start position:0% anymore here's a a list of operation so operations<00:16:07.480> remember<00:16:08.000> there<00:16:08.120> are<00:16:08.319> deductions 00:16:08.949 --> 00:16:08.959 align:start position:0% operations remember there are deductions 00:16:08.959 --> 00:16:10.389 align:start position:0% operations remember there are deductions that<00:16:09.079> are<00:16:09.240> applied<00:16:09.519> to<00:16:09.680> statements<00:16:10.240> to 00:16:10.389 --> 00:16:10.399 align:start position:0% that are applied to statements to 00:16:10.399 --> 00:16:13.470 align:start position:0% that are applied to statements to compute<00:16:10.839> new<00:16:11.040> statements<00:16:11.839> so<00:16:12.000> as<00:16:12.120> an<00:16:12.480> example 00:16:13.470 --> 00:16:13.480 align:start position:0% compute new statements so as an example 00:16:13.480 --> 00:16:16.069 align:start position:0% compute new statements so as an example the<00:16:13.639> equality<00:16:14.040> from<00:16:14.279> entry<00:16:14.680> statement<00:16:15.680> takes 00:16:16.069 --> 00:16:16.079 align:start position:0% the equality from entry statement takes 00:16:16.079 --> 00:16:18.110 align:start position:0% the equality from entry statement takes two<00:16:16.519> value<00:16:16.880> of<00:16:17.160> statements<00:16:17.800> and<00:16:17.880> then<00:16:18.000> it 00:16:18.110 --> 00:16:18.120 align:start position:0% two value of statements and then it 00:16:18.120 --> 00:16:19.829 align:start position:0% two value of statements and then it checks<00:16:18.480> the<00:16:18.639> entries<00:16:19.120> within<00:16:19.360> the<00:16:19.480> value<00:16:19.680> of 00:16:19.829 --> 00:16:19.839 align:start position:0% checks the entries within the value of 00:16:19.839 --> 00:16:21.509 align:start position:0% checks the entries within the value of statements<00:16:20.319> and<00:16:20.440> if<00:16:20.560> the<00:16:20.680> entries<00:16:21.000> are<00:16:21.160> indeed 00:16:21.509 --> 00:16:21.519 align:start position:0% statements and if the entries are indeed 00:16:21.519 --> 00:16:23.069 align:start position:0% statements and if the entries are indeed equal<00:16:21.880> it<00:16:22.000> produces<00:16:22.360> a<00:16:22.480> new<00:16:22.680> logical 00:16:23.069 --> 00:16:23.079 align:start position:0% equal it produces a new logical 00:16:23.079 --> 00:16:24.790 align:start position:0% equal it produces a new logical statement<00:16:23.480> that<00:16:23.560> says<00:16:23.920> the<00:16:24.040> two<00:16:24.199> values<00:16:24.680> the 00:16:24.790 --> 00:16:24.800 align:start position:0% statement that says the two values the 00:16:24.800 --> 00:16:28.389 align:start position:0% statement that says the two values the two<00:16:24.920> entries<00:16:25.199> are<00:16:25.360> equal<00:16:25.800> easy<00:16:26.199> right<00:16:27.120> um<00:16:27.560> so 00:16:28.389 --> 00:16:28.399 align:start position:0% two entries are equal easy right um so 00:16:28.399 --> 00:16:31.030 align:start position:0% two entries are equal easy right um so from<00:16:29.000> from<00:16:29.160> a<00:16:29.920> cryptography<00:16:30.600> perspective 00:16:31.030 --> 00:16:31.040 align:start position:0% from from a cryptography perspective 00:16:31.040 --> 00:16:33.030 align:start position:0% from from a cryptography perspective what<00:16:31.120> we<00:16:31.279> had<00:16:31.399> to<00:16:31.519> do<00:16:31.839> is<00:16:32.360> instead<00:16:32.639> of<00:16:32.759> writing 00:16:33.030 --> 00:16:33.040 align:start position:0% what we had to do is instead of writing 00:16:33.040 --> 00:16:35.189 align:start position:0% what we had to do is instead of writing a<00:16:33.279> z<00:16:33.560> zkm<00:16:34.240> that<00:16:34.360> has<00:16:34.519> circuits<00:16:34.880> proving<00:16:35.120> the 00:16:35.189 --> 00:16:35.199 align:start position:0% a z zkm that has circuits proving the 00:16:35.199 --> 00:16:37.189 align:start position:0% a z zkm that has circuits proving the state<00:16:35.440> transition<00:16:35.800> of<00:16:35.920> a<00:16:36.040> CPU<00:16:36.480> architecture 00:16:37.189 --> 00:16:37.199 align:start position:0% state transition of a CPU architecture 00:16:37.199 --> 00:16:39.350 align:start position:0% state transition of a CPU architecture like<00:16:37.360> Risk<00:16:37.639> five<00:16:37.920> or<00:16:38.079> wasm<00:16:38.360> or<00:16:38.480> whatever<00:16:39.199> we 00:16:39.350 --> 00:16:39.360 align:start position:0% like Risk five or wasm or whatever we 00:16:39.360 --> 00:16:40.749 align:start position:0% like Risk five or wasm or whatever we build<00:16:39.560> a<00:16:39.639> virtual<00:16:39.920> machine<00:16:40.160> that<00:16:40.279> a<00:16:40.399> circuits 00:16:40.749 --> 00:16:40.759 align:start position:0% build a virtual machine that a circuits 00:16:40.759 --> 00:16:42.189 align:start position:0% build a virtual machine that a circuits proving<00:16:41.040> The<00:16:41.199> Logical<00:16:41.639> operation<00:16:42.000> on 00:16:42.189 --> 00:16:42.199 align:start position:0% proving The Logical operation on 00:16:42.199 --> 00:16:44.949 align:start position:0% proving The Logical operation on statements<00:16:42.600> is<00:16:42.759> done<00:16:43.199> correctly<00:16:44.199> um<00:16:44.440> it's<00:16:44.600> a 00:16:44.949 --> 00:16:44.959 align:start position:0% statements is done correctly um it's a 00:16:44.959 --> 00:16:46.470 align:start position:0% statements is done correctly um it's a cryptographically<00:16:45.680> verified<00:16:46.079> theor 00:16:46.470 --> 00:16:46.480 align:start position:0% cryptographically verified theor 00:16:46.480 --> 00:16:48.749 align:start position:0% cryptographically verified theor improver<00:16:46.800> if<00:16:46.880> you<00:16:47.000> want<00:16:47.759> so<00:16:47.959> this<00:16:48.079> all<00:16:48.319> seems 00:16:48.749 --> 00:16:48.759 align:start position:0% improver if you want so this all seems 00:16:48.759 --> 00:16:50.230 align:start position:0% improver if you want so this all seems again<00:16:48.959> like<00:16:49.160> very<00:16:49.360> abstract<00:16:49.839> why<00:16:49.959> did<00:16:50.079> you 00:16:50.230 --> 00:16:50.240 align:start position:0% again like very abstract why did you 00:16:50.240 --> 00:16:51.710 align:start position:0% again like very abstract why did you guys<00:16:50.399> go<00:16:50.519> all<00:16:50.680> the<00:16:50.759> way<00:16:50.959> there<00:16:51.120> to<00:16:51.240> show<00:16:51.519> that 00:16:51.710 --> 00:16:51.720 align:start position:0% guys go all the way there to show that 00:16:51.720 --> 00:16:53.509 align:start position:0% guys go all the way there to show that your<00:16:51.920> age<00:16:52.120> is<00:16:52.240> over<00:16:52.560> 18<00:16:52.920> or<00:16:53.079> something<00:16:53.319> like 00:16:53.509 --> 00:16:53.519 align:start position:0% your age is over 18 or something like 00:16:53.519 --> 00:16:56.189 align:start position:0% your age is over 18 or something like that<00:16:54.040> well<00:16:54.440> the<00:16:54.600> reason<00:16:54.920> is<00:16:55.279> you<00:16:55.440> can<00:16:55.959> it's 00:16:56.189 --> 00:16:56.199 align:start position:0% that well the reason is you can it's 00:16:56.199 --> 00:16:57.670 align:start position:0% that well the reason is you can it's very<00:16:56.399> neat<00:16:56.720> because<00:16:56.920> when<00:16:57.040> you<00:16:57.160> get<00:16:57.319> this<00:16:57.480> to 00:16:57.670 --> 00:16:57.680 align:start position:0% very neat because when you get this to 00:16:57.680 --> 00:17:00.150 align:start position:0% very neat because when you get this to work<00:16:58.120> you<00:16:58.279> can<00:16:58.920> wrap<00:16:59.079> it<00:16:59.199> up<00:16:59.720> with<00:17:00.000> a 00:17:00.150 --> 00:17:00.160 align:start position:0% work you can wrap it up with a 00:17:00.160 --> 00:17:01.870 align:start position:0% work you can wrap it up with a programming<00:17:00.560> language<00:17:00.959> that<00:17:01.160> looks<00:17:01.680> like 00:17:01.870 --> 00:17:01.880 align:start position:0% programming language that looks like 00:17:01.880 --> 00:17:03.910 align:start position:0% programming language that looks like what<00:17:02.040> people<00:17:02.360> expect<00:17:02.759> but<00:17:02.920> under<00:17:03.199> the<00:17:03.399> hood 00:17:03.910 --> 00:17:03.920 align:start position:0% what people expect but under the hood 00:17:03.920 --> 00:17:05.590 align:start position:0% what people expect but under the hood operates<00:17:04.280> on<00:17:04.480> logical<00:17:04.880> operations<00:17:05.400> so<00:17:05.520> you 00:17:05.590 --> 00:17:05.600 align:start position:0% operates on logical operations so you 00:17:05.600 --> 00:17:07.069 align:start position:0% operates on logical operations so you can<00:17:05.760> make<00:17:05.919> the<00:17:06.039> user<00:17:06.319> experience<00:17:06.640> of<00:17:06.760> using 00:17:07.069 --> 00:17:07.079 align:start position:0% can make the user experience of using 00:17:07.079 --> 00:17:09.390 align:start position:0% can make the user experience of using this<00:17:07.439> pretty<00:17:07.679> decent<00:17:08.520> but<00:17:08.679> at<00:17:08.799> the<00:17:08.919> same<00:17:09.160> time 00:17:09.390 --> 00:17:09.400 align:start position:0% this pretty decent but at the same time 00:17:09.400 --> 00:17:11.750 align:start position:0% this pretty decent but at the same time now<00:17:09.600> you<00:17:09.799> get<00:17:10.439> pretty<00:17:10.679> good<00:17:10.919> composability<00:17:11.360> at 00:17:11.750 --> 00:17:11.760 align:start position:0% now you get pretty good composability at 00:17:11.760 --> 00:17:13.710 align:start position:0% now you get pretty good composability at the<00:17:11.919> program<00:17:12.319> level<00:17:12.919> as<00:17:13.039> opposed<00:17:13.360> to<00:17:13.480> having 00:17:13.710 --> 00:17:13.720 align:start position:0% the program level as opposed to having 00:17:13.720 --> 00:17:15.390 align:start position:0% the program level as opposed to having these<00:17:13.919> programs<00:17:14.319> that<00:17:14.480> output<00:17:14.880> data<00:17:15.160> types 00:17:15.390 --> 00:17:15.400 align:start position:0% these programs that output data types 00:17:15.400 --> 00:17:17.270 align:start position:0% these programs that output data types that<00:17:15.559> you<00:17:15.720> didn't<00:17:16.039> have<00:17:16.160> to<00:17:16.319> compute<00:17:16.640> over 00:17:17.270 --> 00:17:17.280 align:start position:0% that you didn't have to compute over 00:17:17.280 --> 00:17:18.669 align:start position:0% that you didn't have to compute over without<00:17:17.559> really<00:17:17.720> knowing<00:17:18.120> what<00:17:18.319> the<00:17:18.559> the 00:17:18.669 --> 00:17:18.679 align:start position:0% without really knowing what the the 00:17:18.679 --> 00:17:22.350 align:start position:0% without really knowing what the the previous<00:17:19.039> program<00:17:19.439> did<00:17:20.520> okay<00:17:21.520> um<00:17:22.039> I'll<00:17:22.240> go 00:17:22.350 --> 00:17:22.360 align:start position:0% previous program did okay um I'll go 00:17:22.360 --> 00:17:24.630 align:start position:0% previous program did okay um I'll go through<00:17:22.559> this<00:17:22.919> a<00:17:23.039> bit<00:17:23.559> bit<00:17:23.760> faster<00:17:24.319> because 00:17:24.630 --> 00:17:24.640 align:start position:0% through this a bit bit faster because 00:17:24.640 --> 00:17:26.590 align:start position:0% through this a bit bit faster because this<00:17:24.760> is<00:17:24.839> not<00:17:25.039> really<00:17:25.240> the<00:17:25.400> point<00:17:25.880> of<00:17:26.400> this 00:17:26.590 --> 00:17:26.600 align:start position:0% this is not really the point of this 00:17:26.600 --> 00:17:28.429 align:start position:0% this is not really the point of this Workshop<00:17:27.079> but<00:17:27.240> another<00:17:27.760> challenge<00:17:28.079> we<00:17:28.199> wanted 00:17:28.429 --> 00:17:28.439 align:start position:0% Workshop but another challenge we wanted 00:17:28.439 --> 00:17:30.350 align:start position:0% Workshop but another challenge we wanted to<00:17:28.520> solve<00:17:28.960> is<00:17:29.080> this<00:17:29.200> challenge<00:17:29.520> of<00:17:29.679> imports<00:17:30.240> so 00:17:30.350 --> 00:17:30.360 align:start position:0% to solve is this challenge of imports so 00:17:30.360 --> 00:17:32.590 align:start position:0% to solve is this challenge of imports so we<00:17:30.480> want<00:17:30.600> to<00:17:30.720> turn<00:17:31.039> verifiable<00:17:31.679> data<00:17:32.000> into 00:17:32.590 --> 00:17:32.600 align:start position:0% we want to turn verifiable data into 00:17:32.600 --> 00:17:35.110 align:start position:0% we want to turn verifiable data into value<00:17:32.880> of<00:17:33.039> statements<00:17:33.960> and<00:17:34.080> we're<00:17:34.480> we're 00:17:35.110 --> 00:17:35.120 align:start position:0% value of statements and we're we're 00:17:35.120 --> 00:17:36.870 align:start position:0% value of statements and we're we're happy<00:17:35.480> having<00:17:35.760> some<00:17:36.039> value<00:17:36.240> of<00:17:36.400> statements 00:17:36.870 --> 00:17:36.880 align:start position:0% happy having some value of statements 00:17:36.880 --> 00:17:39.909 align:start position:0% happy having some value of statements have<00:17:37.480> special<00:17:37.840> meaning<00:17:38.240> so<00:17:38.400> as<00:17:38.480> an<00:17:38.799> example<00:17:39.799> uh 00:17:39.909 --> 00:17:39.919 align:start position:0% have special meaning so as an example uh 00:17:39.919 --> 00:17:42.230 align:start position:0% have special meaning so as an example uh if<00:17:40.039> you<00:17:40.120> were<00:17:40.280> to<00:17:40.440> import<00:17:40.720> an<00:17:40.880> email<00:17:41.840> we<00:17:42.000> are 00:17:42.230 --> 00:17:42.240 align:start position:0% if you were to import an email we are 00:17:42.240 --> 00:17:43.950 align:start position:0% if you were to import an email we are okay<00:17:42.640> having<00:17:42.919> some<00:17:43.200> keys<00:17:43.559> that<00:17:43.679> says 00:17:43.950 --> 00:17:43.960 align:start position:0% okay having some keys that says 00:17:43.960 --> 00:17:46.630 align:start position:0% okay having some keys that says underscore<00:17:44.600> from<00:17:45.120> underscore<00:17:45.679> 2core 00:17:46.630 --> 00:17:46.640 align:start position:0% underscore from underscore 2core 00:17:46.640 --> 00:17:48.270 align:start position:0% underscore from underscore 2core timestamp<00:17:47.280> and<00:17:47.360> these<00:17:47.480> are<00:17:47.600> not<00:17:47.799> entries<00:17:48.160> that 00:17:48.270 --> 00:17:48.280 align:start position:0% timestamp and these are not entries that 00:17:48.280 --> 00:17:50.029 align:start position:0% timestamp and these are not entries that can<00:17:48.400> be<00:17:48.559> set<00:17:48.919> by<00:17:49.039> the<00:17:49.160> content<00:17:49.440> of<00:17:49.559> the<00:17:49.640> email 00:17:50.029 --> 00:17:50.039 align:start position:0% can be set by the content of the email 00:17:50.039 --> 00:17:51.190 align:start position:0% can be set by the content of the email these<00:17:50.120> are<00:17:50.240> entries<00:17:50.600> that<00:17:50.760> come<00:17:50.960> from 00:17:51.190 --> 00:17:51.200 align:start position:0% these are entries that come from 00:17:51.200 --> 00:17:53.470 align:start position:0% these are entries that come from metadata<00:17:51.840> about<00:17:52.039> the<00:17:52.160> email<00:17:53.080> the<00:17:53.200> great 00:17:53.470 --> 00:17:53.480 align:start position:0% metadata about the email the great 00:17:53.480 --> 00:17:55.830 align:start position:0% metadata about the email the great things<00:17:54.160> with<00:17:54.480> importing<00:17:55.240> everything<00:17:55.640> as 00:17:55.830 --> 00:17:55.840 align:start position:0% things with importing everything as 00:17:55.840 --> 00:17:57.470 align:start position:0% things with importing everything as value<00:17:56.080> of<00:17:56.280> statements<00:17:56.720> is<00:17:56.880> that<00:17:57.039> all<00:17:57.159> of<00:17:57.280> our 00:17:57.470 --> 00:17:57.480 align:start position:0% value of statements is that all of our 00:17:57.480 --> 00:17:59.630 align:start position:0% value of statements is that all of our Machinery<00:17:58.360> that<00:17:58.559> op<00:17:58.840> operates<00:17:59.080> on<00:17:59.200> entries 00:17:59.630 --> 00:17:59.640 align:start position:0% Machinery that op operates on entries 00:17:59.640 --> 00:18:01.630 align:start position:0% Machinery that op operates on entries can<00:17:59.760> be<00:17:59.960> used<00:18:00.480> to<00:18:00.640> operate<00:18:00.960> on<00:18:01.120> things<00:18:01.400> like 00:18:01.630 --> 00:18:01.640 align:start position:0% can be used to operate on things like 00:18:01.640 --> 00:18:04.710 align:start position:0% can be used to operate on things like public<00:18:02.000> Keys<00:18:02.440> like<00:18:02.600> who<00:18:02.760> sent<00:18:03.039> the<00:18:03.200> email<00:18:03.720> Etc 00:18:04.710 --> 00:18:04.720 align:start position:0% public Keys like who sent the email Etc 00:18:04.720 --> 00:18:05.909 align:start position:0% public Keys like who sent the email Etc um<00:18:04.799> so<00:18:04.960> as<00:18:05.080> example<00:18:05.280> if<00:18:05.360> I<00:18:05.440> want<00:18:05.520> to<00:18:05.640> compute 00:18:05.909 --> 00:18:05.919 align:start position:0% um so as example if I want to compute 00:18:05.919 --> 00:18:09.190 align:start position:0% um so as example if I want to compute with<00:18:06.000> one<00:18:06.080> of<00:18:06.200> my<00:18:06.320> frog<00:18:07.280> frogs<00:18:07.640> are<00:18:07.840> pod<00:18:08.200> ones 00:18:09.190 --> 00:18:09.200 align:start position:0% with one of my frog frogs are pod ones 00:18:09.200 --> 00:18:10.190 align:start position:0% with one of my frog frogs are pod ones in<00:18:09.320> some<00:18:09.480> ways<00:18:09.640> they're<00:18:09.799> foreign 00:18:10.190 --> 00:18:10.200 align:start position:0% in some ways they're foreign 00:18:10.200 --> 00:18:11.789 align:start position:0% in some ways they're foreign cryptographic<00:18:10.840> data<00:18:11.159> from<00:18:11.320> the<00:18:11.440> perspective 00:18:11.789 --> 00:18:11.799 align:start position:0% cryptographic data from the perspective 00:18:11.799 --> 00:18:13.070 align:start position:0% cryptographic data from the perspective of<00:18:11.919> the<00:18:12.039> Pod<00:18:12.240> two<00:18:12.440> system<00:18:12.760> they're<00:18:12.919> on 00:18:13.070 --> 00:18:13.080 align:start position:0% of the Pod two system they're on 00:18:13.080 --> 00:18:14.149 align:start position:0% of the Pod two system they're on different<00:18:13.320> curves<00:18:13.640> different<00:18:13.840> signing 00:18:14.149 --> 00:18:14.159 align:start position:0% different curves different signing 00:18:14.159 --> 00:18:16.470 align:start position:0% different curves different signing algorithms<00:18:14.720> different<00:18:15.120> merization<00:18:16.120> and<00:18:16.200> so 00:18:16.470 --> 00:18:16.480 align:start position:0% algorithms different merization and so 00:18:16.480 --> 00:18:17.549 align:start position:0% algorithms different merization and so what<00:18:16.600> we<00:18:16.679> have<00:18:16.799> to<00:18:16.919> do<00:18:17.000> is<00:18:17.120> we<00:18:17.200> have<00:18:17.280> to<00:18:17.360> build 00:18:17.549 --> 00:18:17.559 align:start position:0% what we have to do is we have to build 00:18:17.559 --> 00:18:19.070 align:start position:0% what we have to do is we have to build what<00:18:17.640> we<00:18:17.720> call<00:18:17.880> an<00:18:18.000> introduction<00:18:18.640> gadget<00:18:18.919> for 00:18:19.070 --> 00:18:19.080 align:start position:0% what we call an introduction gadget for 00:18:19.080 --> 00:18:21.669 align:start position:0% what we call an introduction gadget for this<00:18:19.280> paa<00:18:19.520> one<00:18:19.840> so<00:18:20.400> you<00:18:20.559> you<00:18:20.679> would<00:18:20.840> write<00:18:21.159> a<00:18:21.559> a 00:18:21.669 --> 00:18:21.679 align:start position:0% this paa one so you you would write a a 00:18:21.679 --> 00:18:23.070 align:start position:0% this paa one so you you would write a a circuit<00:18:22.120> that<00:18:22.240> would<00:18:22.440> verify<00:18:22.880> that<00:18:23.000> the 00:18:23.070 --> 00:18:23.080 align:start position:0% circuit that would verify that the 00:18:23.080 --> 00:18:24.510 align:start position:0% circuit that would verify that the signature<00:18:23.440> of<00:18:23.520> the<00:18:23.679> spot<00:18:23.880> is<00:18:24.000> correct<00:18:24.440> it 00:18:24.510 --> 00:18:24.520 align:start position:0% signature of the spot is correct it 00:18:24.520 --> 00:18:26.110 align:start position:0% signature of the spot is correct it would<00:18:24.640> store<00:18:24.919> the<00:18:25.039> signer<00:18:25.440> into<00:18:25.640> a<00:18:25.760> value<00:18:25.960> of 00:18:26.110 --> 00:18:26.120 align:start position:0% would store the signer into a value of 00:18:26.120 --> 00:18:27.870 align:start position:0% would store the signer into a value of statement<00:18:26.440> with<00:18:26.600> Kore<00:18:27.120> signer<00:18:27.400> and<00:18:27.520> it<00:18:27.600> would 00:18:27.870 --> 00:18:27.880 align:start position:0% statement with Kore signer and it would 00:18:27.880 --> 00:18:30.430 align:start position:0% statement with Kore signer and it would copy<00:18:28.440> each<00:18:28.799> but<00:18:28.960> entry<00:18:29.360> into<00:18:29.840> an<00:18:30.000> equivalent 00:18:30.430 --> 00:18:30.440 align:start position:0% copy each but entry into an equivalent 00:18:30.440 --> 00:18:32.270 align:start position:0% copy each but entry into an equivalent value<00:18:30.640> of<00:18:30.799> entry<00:18:31.559> and<00:18:31.640> then<00:18:31.760> you<00:18:31.840> can<00:18:31.960> take<00:18:32.159> two 00:18:32.270 --> 00:18:32.280 align:start position:0% value of entry and then you can take two 00:18:32.280 --> 00:18:34.110 align:start position:0% value of entry and then you can take two frogs<00:18:32.679> you<00:18:32.760> can<00:18:32.960> import<00:18:33.440> them<00:18:33.760> and<00:18:33.840> then<00:18:34.000> you 00:18:34.110 --> 00:18:34.120 align:start position:0% frogs you can import them and then you 00:18:34.120 --> 00:18:36.789 align:start position:0% frogs you can import them and then you can<00:18:35.080> put<00:18:35.360> together<00:18:35.559> a<00:18:35.679> statement<00:18:36.080> that<00:18:36.240> says 00:18:36.789 --> 00:18:36.799 align:start position:0% can put together a statement that says 00:18:36.799 --> 00:18:38.590 align:start position:0% can put together a statement that says Todd<00:18:37.120> is<00:18:37.280> more<00:18:37.480> beautiful<00:18:37.880> than<00:18:38.039> the<00:18:38.159> mustache 00:18:38.590 --> 00:18:38.600 align:start position:0% Todd is more beautiful than the mustache 00:18:38.600 --> 00:18:40.909 align:start position:0% Todd is more beautiful than the mustache frog<00:18:39.120> so<00:18:39.280> if<00:18:39.400> you<00:18:39.559> go<00:18:39.760> through<00:18:40.200> all<00:18:40.360> of<00:18:40.559> this 00:18:40.909 --> 00:18:40.919 align:start position:0% frog so if you go through all of this 00:18:40.919 --> 00:18:42.669 align:start position:0% frog so if you go through all of this this<00:18:41.039> is<00:18:41.159> the<00:18:41.280> kind<00:18:41.440> of<00:18:41.559> stuff<00:18:41.760> you<00:18:41.880> can 00:18:42.669 --> 00:18:42.679 align:start position:0% this is the kind of stuff you can 00:18:42.679 --> 00:18:45.590 align:start position:0% this is the kind of stuff you can do<00:18:43.679> so<00:18:44.320> we<00:18:44.440> want<00:18:44.559> to<00:18:44.720> be<00:18:44.799> able<00:18:44.960> to<00:18:45.080> import<00:18:45.400> all 00:18:45.590 --> 00:18:45.600 align:start position:0% do so we want to be able to import all 00:18:45.600 --> 00:18:48.270 align:start position:0% do so we want to be able to import all kinds<00:18:45.799> of<00:18:45.960> stuff<00:18:46.400> whether<00:18:46.720> it's<00:18:47.559> um<00:18:47.880> data<00:18:48.120> from 00:18:48.270 --> 00:18:48.280 align:start position:0% kinds of stuff whether it's um data from 00:18:48.280 --> 00:18:50.149 align:start position:0% kinds of stuff whether it's um data from the<00:18:48.440> web<00:18:48.679> data<00:18:48.880> from<00:18:49.039> blockchains<00:18:49.640> data<00:18:49.960> from 00:18:50.149 --> 00:18:50.159 align:start position:0% the web data from blockchains data from 00:18:50.159 --> 00:18:52.390 align:start position:0% the web data from blockchains data from Virtual<00:18:50.559> Worlds<00:18:51.440> um<00:18:51.640> even<00:18:51.919> mathematical 00:18:52.390 --> 00:18:52.400 align:start position:0% Virtual Worlds um even mathematical 00:18:52.400 --> 00:18:54.789 align:start position:0% Virtual Worlds um even mathematical proofs<00:18:52.960> themselves<00:18:53.880> and<00:18:54.080> in<00:18:54.200> order<00:18:54.400> to<00:18:54.559> do 00:18:54.789 --> 00:18:54.799 align:start position:0% proofs themselves and in order to do 00:18:54.799 --> 00:18:58.390 align:start position:0% proofs themselves and in order to do that<00:18:55.799> um<00:18:56.799> well<00:18:57.000> we<00:18:57.159> also<00:18:57.320> have<00:18:57.440> to<00:18:57.559> make<00:18:57.720> it<00:18:58.200> not 00:18:58.390 --> 00:18:58.400 align:start position:0% that um well we also have to make it not 00:18:58.400 --> 00:19:01.230 align:start position:0% that um well we also have to make it not too<00:18:58.799> hard<00:18:59.000> to<00:18:59.080> use<00:18:59.320> this<00:18:59.480> system<00:19:00.280> uh<00:19:00.880> if<00:19:00.960> we<00:19:01.120> go 00:19:01.230 --> 00:19:01.240 align:start position:0% too hard to use this system uh if we go 00:19:01.240 --> 00:19:02.430 align:start position:0% too hard to use this system uh if we go back<00:19:01.360> to<00:19:01.480> the<00:19:01.640> place<00:19:01.840> where<00:19:01.919> you<00:19:02.039> need<00:19:02.159> to<00:19:02.240> be<00:19:02.360> a 00:19:02.430 --> 00:19:02.440 align:start position:0% back to the place where you need to be a 00:19:02.440 --> 00:19:04.789 align:start position:0% back to the place where you need to be a cryptographer<00:19:03.320> and<00:19:03.760> an<00:19:03.919> expert<00:19:04.240> in<00:19:04.400> logic<00:19:04.720> in 00:19:04.789 --> 00:19:04.799 align:start position:0% cryptographer and an expert in logic in 00:19:04.799 --> 00:19:07.270 align:start position:0% cryptographer and an expert in logic in order<00:19:04.960> to<00:19:05.080> use<00:19:05.280> this<00:19:05.440> we've<00:19:05.679> regressed<00:19:06.520> so 00:19:07.270 --> 00:19:07.280 align:start position:0% order to use this we've regressed so 00:19:07.280 --> 00:19:09.029 align:start position:0% order to use this we've regressed so it's<00:19:07.440> really<00:19:07.720> important<00:19:08.120> this<00:19:08.240> thing<00:19:08.400> is<00:19:08.520> not 00:19:09.029 --> 00:19:09.039 align:start position:0% it's really important this thing is not 00:19:09.039 --> 00:19:11.070 align:start position:0% it's really important this thing is not extremely<00:19:09.679> difficult<00:19:09.799> to<00:19:09.960> use<00:19:10.520> so<00:19:10.760> this<00:19:10.880> is 00:19:11.070 --> 00:19:11.080 align:start position:0% extremely difficult to use so this is 00:19:11.080 --> 00:19:12.750 align:start position:0% extremely difficult to use so this is what<00:19:11.240> the<00:19:11.440> Assembly<00:19:11.919> of<00:19:12.039> our<00:19:12.200> system<00:19:12.480> look 00:19:12.750 --> 00:19:12.760 align:start position:0% what the Assembly of our system look 00:19:12.760 --> 00:19:15.310 align:start position:0% what the Assembly of our system look like<00:19:12.960> it's<00:19:13.080> a<00:19:13.240> bunch<00:19:13.440> of<00:19:14.159> uh<00:19:14.400> operations<00:19:15.039> don't 00:19:15.310 --> 00:19:15.320 align:start position:0% like it's a bunch of uh operations don't 00:19:15.320 --> 00:19:17.110 align:start position:0% like it's a bunch of uh operations don't ask<00:19:15.480> me<00:19:15.679> why<00:19:15.840> we<00:19:15.960> use<00:19:16.200> strings<00:19:16.640> you<00:19:16.720> can<00:19:16.919> ask 00:19:17.110 --> 00:19:17.120 align:start position:0% ask me why we use strings you can ask 00:19:17.120 --> 00:19:19.310 align:start position:0% ask me why we use strings you can ask Ahmad<00:19:17.799> you<00:19:17.960> will<00:19:18.240> no<00:19:18.400> I'm<00:19:18.559> joking<00:19:18.919> Ahmad<00:19:19.200> has 00:19:19.310 --> 00:19:19.320 align:start position:0% Ahmad you will no I'm joking Ahmad has 00:19:19.320 --> 00:19:20.470 align:start position:0% Ahmad you will no I'm joking Ahmad has been<00:19:19.400> trying<00:19:19.600> to<00:19:19.679> remove<00:19:19.960> the<00:19:20.039> strings<00:19:20.320> from 00:19:20.470 --> 00:19:20.480 align:start position:0% been trying to remove the strings from 00:19:20.480 --> 00:19:23.310 align:start position:0% been trying to remove the strings from the<00:19:20.600> system<00:19:21.600> um<00:19:22.320> and<00:19:22.440> so<00:19:22.840> what<00:19:22.919> you<00:19:23.039> have<00:19:23.120> to<00:19:23.200> do 00:19:23.310 --> 00:19:23.320 align:start position:0% the system um and so what you have to do 00:19:23.320 --> 00:19:24.789 align:start position:0% the system um and so what you have to do as<00:19:23.440> a<00:19:23.559> user<00:19:23.840> of<00:19:23.919> the<00:19:24.080> system<00:19:24.320> is<00:19:24.400> you<00:19:24.520> basically 00:19:24.789 --> 00:19:24.799 align:start position:0% as a user of the system is you basically 00:19:24.799 --> 00:19:26.549 align:start position:0% as a user of the system is you basically have<00:19:24.880> to<00:19:25.080> craft<00:19:25.320> a<00:19:25.440> sequence<00:19:25.760> of<00:19:25.919> logical<00:19:26.320> up 00:19:26.549 --> 00:19:26.559 align:start position:0% have to craft a sequence of logical up 00:19:26.559 --> 00:19:28.230 align:start position:0% have to craft a sequence of logical up codes<00:19:26.799> to<00:19:26.880> make<00:19:27.080> new<00:19:27.280> pods<00:19:27.640> and<00:19:27.760> also<00:19:28.039> when<00:19:28.120> you 00:19:28.230 --> 00:19:28.240 align:start position:0% codes to make new pods and also when you 00:19:28.240 --> 00:19:30.190 align:start position:0% codes to make new pods and also when you get<00:19:28.360> a<00:19:28.520> pod<00:19:28.919> out<00:19:29.400> you<00:19:29.520> have<00:19:29.640> to<00:19:29.799> read<00:19:30.039> The 00:19:30.190 --> 00:19:30.200 align:start position:0% get a pod out you have to read The 00:19:30.200 --> 00:19:31.630 align:start position:0% get a pod out you have to read The Logical<00:19:30.600> statements<00:19:31.039> and<00:19:31.159> make<00:19:31.280> sure<00:19:31.480> they 00:19:31.630 --> 00:19:31.640 align:start position:0% Logical statements and make sure they 00:19:31.640 --> 00:19:33.149 align:start position:0% Logical statements and make sure they actually<00:19:31.880> claim<00:19:32.240> what<00:19:32.320> you<00:19:32.440> want<00:19:32.600> to<00:19:33.000> to 00:19:33.149 --> 00:19:33.159 align:start position:0% actually claim what you want to to 00:19:33.159 --> 00:19:34.710 align:start position:0% actually claim what you want to to verify<00:19:33.600> so<00:19:33.760> this<00:19:33.840> is<00:19:34.000> pretty<00:19:34.159> hard<00:19:34.320> to<00:19:34.480> work 00:19:34.710 --> 00:19:34.720 align:start position:0% verify so this is pretty hard to work 00:19:34.720 --> 00:19:36.950 align:start position:0% verify so this is pretty hard to work with<00:19:35.200> so<00:19:35.400> what<00:19:35.520> we<00:19:35.640> did<00:19:35.799> is<00:19:35.960> we<00:19:36.120> built<00:19:36.480> this 00:19:36.950 --> 00:19:36.960 align:start position:0% with so what we did is we built this 00:19:36.960 --> 00:19:38.510 align:start position:0% with so what we did is we built this this<00:19:37.159> little<00:19:37.400> logic<00:19:37.760> programming<00:19:38.200> language 00:19:38.510 --> 00:19:38.520 align:start position:0% this little logic programming language 00:19:38.520 --> 00:19:40.270 align:start position:0% this little logic programming language to<00:19:38.640> create<00:19:38.919> pods<00:19:39.120> and<00:19:39.280> verify<00:19:39.679> them<00:19:40.080> it's 00:19:40.270 --> 00:19:40.280 align:start position:0% to create pods and verify them it's 00:19:40.280 --> 00:19:41.710 align:start position:0% to create pods and verify them it's currently<00:19:40.600> a<00:19:40.679> list<00:19:41.039> because<00:19:41.240> it's<00:19:41.400> the<00:19:41.480> only 00:19:41.710 --> 00:19:41.720 align:start position:0% currently a list because it's the only 00:19:41.720 --> 00:19:42.789 align:start position:0% currently a list because it's the only kind<00:19:41.840> of<00:19:41.960> programming<00:19:42.320> language<00:19:42.600> you<00:19:42.679> can 00:19:42.789 --> 00:19:42.799 align:start position:0% kind of programming language you can 00:19:42.799 --> 00:19:45.270 align:start position:0% kind of programming language you can write<00:19:42.960> in<00:19:43.120> two<00:19:43.320> weeks<00:19:44.039> but<00:19:44.320> we'll<00:19:44.840> we<00:19:45.039> we<00:19:45.120> could 00:19:45.270 --> 00:19:45.280 align:start position:0% write in two weeks but we'll we we could 00:19:45.280 --> 00:19:46.909 align:start position:0% write in two weeks but we'll we we could have<00:19:45.480> other<00:19:45.720> things<00:19:45.880> in<00:19:46.000> the<00:19:46.120> future<00:19:46.600> and<00:19:46.760> it's 00:19:46.909 --> 00:19:46.919 align:start position:0% have other things in the future and it's 00:19:46.919 --> 00:19:48.390 align:start position:0% have other things in the future and it's great<00:19:47.120> because<00:19:47.280> it<00:19:47.400> do<00:19:47.559> an<00:19:47.720> interactive 00:19:48.390 --> 00:19:48.400 align:start position:0% great because it do an interactive 00:19:48.400 --> 00:19:50.110 align:start position:0% great because it do an interactive development<00:19:48.840> Loop<00:19:49.159> so<00:19:49.480> it's<00:19:49.640> it's<00:19:49.799> easy<00:19:50.000> to 00:19:50.110 --> 00:19:50.120 align:start position:0% development Loop so it's it's easy to 00:19:50.120 --> 00:19:53.070 align:start position:0% development Loop so it's it's easy to play<00:19:50.320> with<00:19:50.480> it<00:19:51.480> um<00:19:52.280> so<00:19:52.520> instead<00:19:52.799> of<00:19:52.880> showing 00:19:53.070 --> 00:19:53.080 align:start position:0% play with it um so instead of showing 00:19:53.080 --> 00:19:54.549 align:start position:0% play with it um so instead of showing you<00:19:53.200> an<00:19:53.360> example<00:19:53.640> of<00:19:53.799> PEX<00:19:54.039> I'm<00:19:54.159> just<00:19:54.240> going<00:19:54.360> to 00:19:54.549 --> 00:19:54.559 align:start position:0% you an example of PEX I'm just going to 00:19:54.559 --> 00:19:59.710 align:start position:0% you an example of PEX I'm just going to like<00:19:54.760> do<00:19:54.919> it<00:19:55.200> live<00:19:56.159> so<00:19:57.159> uh<00:19:57.320> pray<00:19:57.520> for<00:19:57.720> me<00:19:58.760> cool 00:19:59.710 --> 00:19:59.720 align:start position:0% like do it live so uh pray for me cool 00:19:59.720 --> 00:20:03.870 align:start position:0% like do it live so uh pray for me cool so<00:20:00.720> um<00:20:01.000> actually<00:20:01.360> I<00:20:01.480> have<00:20:01.559> a<00:20:01.760> note<00:20:02.200> here<00:20:02.720> of<00:20:03.720> you 00:20:03.870 --> 00:20:03.880 align:start position:0% so um actually I have a note here of you 00:20:03.880 --> 00:20:06.110 align:start position:0% so um actually I have a note here of you can<00:20:04.159> do<00:20:04.440> this<00:20:04.720> with<00:20:04.880> me<00:20:05.080> if<00:20:05.200> you<00:20:05.320> want<00:20:05.640> but<00:20:05.840> no 00:20:06.110 --> 00:20:06.120 align:start position:0% can do this with me if you want but no 00:20:06.120 --> 00:20:07.470 align:start position:0% can do this with me if you want but no guarantee<00:20:06.559> that<00:20:06.720> this<00:20:06.840> will<00:20:07.000> work<00:20:07.159> on<00:20:07.280> your 00:20:07.470 --> 00:20:07.480 align:start position:0% guarantee that this will work on your 00:20:07.480 --> 00:20:10.230 align:start position:0% guarantee that this will work on your computer<00:20:08.039> so<00:20:08.240> if<00:20:08.320> it<00:20:08.480> doesn't<00:20:08.799> don't<00:20:09.240> complain 00:20:10.230 --> 00:20:10.240 align:start position:0% computer so if it doesn't don't complain 00:20:10.240 --> 00:20:13.909 align:start position:0% computer so if it doesn't don't complain um<00:20:10.480> if<00:20:10.559> you<00:20:10.679> go<00:20:10.840> on<00:20:11.080> get<00:20:11.520> up.com<00:20:12.520> zxp<00:20:12.960> parkpark 00:20:13.909 --> 00:20:13.919 align:start position:0% um if you go on get up.com zxp parkpark 00:20:13.919 --> 00:20:16.870 align:start position:0% um if you go on get up.com zxp parkpark net<00:20:14.799> and<00:20:14.919> you<00:20:15.080> have<00:20:15.520> cargo<00:20:16.000> nightly 00:20:16.870 --> 00:20:16.880 align:start position:0% net and you have cargo nightly 00:20:16.880 --> 00:20:19.310 align:start position:0% net and you have cargo nightly specifically<00:20:17.559> this<00:20:17.840> version<00:20:18.799> uh<00:20:18.919> take<00:20:19.080> a 00:20:19.310 --> 00:20:19.320 align:start position:0% specifically this version uh take a 00:20:19.320 --> 00:20:22.110 align:start position:0% specifically this version uh take a picture<00:20:19.600> of<00:20:19.799> it<00:20:20.600> um<00:20:20.960> you<00:20:21.080> can<00:20:21.240> run<00:20:21.559> cargo<00:20:21.880> build 00:20:22.110 --> 00:20:22.120 align:start position:0% picture of it um you can run cargo build 00:20:22.120 --> 00:20:24.310 align:start position:0% picture of it um you can run cargo build in<00:20:22.240> a<00:20:22.400> Pex<00:20:22.679> crate<00:20:22.919> and<00:20:23.120> cargo<00:20:23.440> run--<00:20:24.039> release 00:20:24.310 --> 00:20:24.320 align:start position:0% in a Pex crate and cargo run-- release 00:20:24.320 --> 00:20:25.990 align:start position:0% in a Pex crate and cargo run-- release the<00:20:24.440> D-<00:20:24.799> release<00:20:25.039> is<00:20:25.159> important<00:20:25.559> otherwise 00:20:25.990 --> 00:20:26.000 align:start position:0% the D- release is important otherwise 00:20:26.000 --> 00:20:28.470 align:start position:0% the D- release is important otherwise everything<00:20:26.280> is<00:20:26.400> going<00:20:26.520> to<00:20:26.679> take<00:20:26.919> like<00:20:27.159> 5<00:20:27.480> hours 00:20:28.470 --> 00:20:28.480 align:start position:0% everything is going to take like 5 hours 00:20:28.480 --> 00:20:30.270 align:start position:0% everything is going to take like 5 hours um<00:20:28.679> and<00:20:28.760> you<00:20:28.840> can<00:20:28.960> follow<00:20:29.240> along<00:20:29.520> if<00:20:29.600> it<00:20:29.720> breaks 00:20:30.270 --> 00:20:30.280 align:start position:0% um and you can follow along if it breaks 00:20:30.280 --> 00:20:31.990 align:start position:0% um and you can follow along if it breaks please<00:20:30.480> don't<00:20:30.679> tell<00:20:30.799> me<00:20:31.039> but<00:20:31.200> it<00:20:31.320> doesn't<00:20:31.679> work 00:20:31.990 --> 00:20:32.000 align:start position:0% please don't tell me but it doesn't work 00:20:32.000 --> 00:20:33.149 align:start position:0% please don't tell me but it doesn't work because<00:20:32.159> I<00:20:32.240> won't<00:20:32.440> be<00:20:32.520> able<00:20:32.640> to<00:20:32.760> fix<00:20:32.919> it<00:20:33.039> on 00:20:33.149 --> 00:20:33.159 align:start position:0% because I won't be able to fix it on 00:20:33.159 --> 00:20:35.909 align:start position:0% because I won't be able to fix it on your<00:20:33.320> computer<00:20:33.840> instead<00:20:34.200> you<00:20:34.360> just<00:20:34.760> start 00:20:35.909 --> 00:20:35.919 align:start position:0% your computer instead you just start 00:20:35.919 --> 00:20:37.909 align:start position:0% your computer instead you just start watching<00:20:36.919> but<00:20:37.039> for<00:20:37.200> some<00:20:37.360> of<00:20:37.480> you<00:20:37.640> it<00:20:37.720> will 00:20:37.909 --> 00:20:37.919 align:start position:0% watching but for some of you it will 00:20:37.919 --> 00:20:39.750 align:start position:0% watching but for some of you it will work<00:20:38.360> I<00:20:38.440> know<00:20:38.600> for<00:20:38.760> a<00:20:38.960> fact<00:20:39.120> that<00:20:39.240> on<00:20:39.400> Linux 00:20:39.750 --> 00:20:39.760 align:start position:0% work I know for a fact that on Linux 00:20:39.760 --> 00:20:41.590 align:start position:0% work I know for a fact that on Linux it's<00:20:39.919> really<00:20:40.120> hard<00:20:40.240> to<00:20:40.360> get<00:20:40.480> it<00:20:40.640> working<00:20:41.440> uh 00:20:41.590 --> 00:20:41.600 align:start position:0% it's really hard to get it working uh 00:20:41.600 --> 00:20:42.870 align:start position:0% it's really hard to get it working uh Ahmad<00:20:41.919> has<00:20:42.039> been<00:20:42.120> trying<00:20:42.320> to<00:20:42.400> put<00:20:42.600> together<00:20:42.760> a 00:20:42.870 --> 00:20:42.880 align:start position:0% Ahmad has been trying to put together a 00:20:42.880 --> 00:20:44.510 align:start position:0% Ahmad has been trying to put together a PR<00:20:43.200> because<00:20:43.400> there's<00:20:43.559> a<00:20:43.720> dependency<00:20:44.120> on<00:20:44.240> open 00:20:44.510 --> 00:20:44.520 align:start position:0% PR because there's a dependency on open 00:20:44.520 --> 00:20:45.950 align:start position:0% PR because there's a dependency on open SSL<00:20:45.000> don't<00:20:45.200> ask<00:20:45.360> me<00:20:45.559> why<00:20:45.679> we<00:20:45.760> have<00:20:45.880> a 00:20:45.950 --> 00:20:45.960 align:start position:0% SSL don't ask me why we have a 00:20:45.960 --> 00:20:47.909 align:start position:0% SSL don't ask me why we have a dependency<00:20:46.320> on<00:20:46.480> open<00:20:46.640> SSL<00:20:46.960> that<00:20:47.080> doesn't<00:20:47.320> work 00:20:47.909 --> 00:20:47.919 align:start position:0% dependency on open SSL that doesn't work 00:20:47.919 --> 00:20:50.430 align:start position:0% dependency on open SSL that doesn't work but<00:20:48.240> on<00:20:48.400> Mac<00:20:48.679> it<00:20:48.840> should<00:20:49.200> work<00:20:49.640> and<00:20:49.760> on<00:20:49.880> Windows 00:20:50.430 --> 00:20:50.440 align:start position:0% but on Mac it should work and on Windows 00:20:50.440 --> 00:20:52.350 align:start position:0% but on Mac it should work and on Windows same<00:20:50.679> thing<00:20:50.840> I<00:20:50.919> don't<00:20:51.080> know<00:20:51.240> I<00:20:51.320> mean<00:20:52.039> uh<00:20:52.240> my 00:20:52.350 --> 00:20:52.360 align:start position:0% same thing I don't know I mean uh my 00:20:52.360 --> 00:20:53.750 align:start position:0% same thing I don't know I mean uh my friend<00:20:52.640> here<00:20:52.760> Alex<00:20:53.120> got<00:20:53.240> it<00:20:53.360> working<00:20:53.600> on 00:20:53.750 --> 00:20:53.760 align:start position:0% friend here Alex got it working on 00:20:53.760 --> 00:20:55.789 align:start position:0% friend here Alex got it working on Windows<00:20:54.120> as<00:20:54.240> well<00:20:54.480> so<00:20:54.720> so<00:20:54.880> we<00:20:54.960> can<00:20:55.120> look<00:20:55.280> later 00:20:55.789 --> 00:20:55.799 align:start position:0% Windows as well so so we can look later 00:20:55.799 --> 00:21:01.070 align:start position:0% Windows as well so so we can look later okay<00:20:56.480> so<00:20:56.760> I<00:20:56.840> will<00:20:57.320> put<00:20:57.480> the<00:20:57.640> mic<00:20:58.000> back 00:21:01.070 --> 00:21:01.080 align:start position:0% 00:21:01.080 --> 00:21:03.270 align:start position:0% because<00:21:01.200> I<00:21:01.320> need<00:21:01.600> both<00:21:01.760> of<00:21:01.919> my<00:21:02.120> hands<00:21:02.760> to<00:21:02.960> type 00:21:03.270 --> 00:21:03.280 align:start position:0% because I need both of my hands to type 00:21:03.280 --> 00:21:05.430 align:start position:0% because I need both of my hands to type super<00:21:03.640> fast<00:21:04.400> all 00:21:05.430 --> 00:21:05.440 align:start position:0% super fast all 00:21:05.440 --> 00:21:09.070 align:start position:0% super fast all right<00:21:06.440> um<00:21:07.120> so<00:21:07.320> I<00:21:07.360> will<00:21:07.640> go<00:21:08.200> just<00:21:08.400> like<00:21:08.640> you<00:21:08.919> in 00:21:09.070 --> 00:21:09.080 align:start position:0% right um so I will go just like you in 00:21:09.080 --> 00:21:12.470 align:start position:0% right um so I will go just like you in the<00:21:09.840> PEX<00:21:10.559> crate<00:21:11.559> and<00:21:11.679> I<00:21:11.760> will<00:21:12.000> just<00:21:12.200> run<00:21:12.360> the 00:21:12.470 --> 00:21:12.480 align:start position:0% the PEX crate and I will just run the 00:21:12.480 --> 00:21:16.110 align:start position:0% the PEX crate and I will just run the system<00:21:12.679> in<00:21:12.840> release<00:21:13.279> okay<00:21:14.080> so 00:21:16.110 --> 00:21:16.120 align:start position:0% system in release okay so 00:21:16.120 --> 00:21:19.149 align:start position:0% system in release okay so oh<00:21:17.120> okay<00:21:17.480> so<00:21:17.640> what<00:21:17.799> this<00:21:18.000> does<00:21:18.480> so<00:21:18.799> you<00:21:18.960> might 00:21:19.149 --> 00:21:19.159 align:start position:0% oh okay so what this does so you might 00:21:19.159 --> 00:21:20.710 align:start position:0% oh okay so what this does so you might notice<00:21:19.559> there<00:21:19.640> is<00:21:19.960> a<00:21:20.039> little<00:21:20.240> statement<00:21:20.640> that 00:21:20.710 --> 00:21:20.720 align:start position:0% notice there is a little statement that 00:21:20.720 --> 00:21:22.870 align:start position:0% notice there is a little statement that says<00:21:20.960> Ripple<00:21:21.400> synchronize<00:21:21.919> with<00:21:22.039> other<00:21:22.279> peers 00:21:22.870 --> 00:21:22.880 align:start position:0% says Ripple synchronize with other peers 00:21:22.880 --> 00:21:24.470 align:start position:0% says Ripple synchronize with other peers the<00:21:23.000> fun<00:21:23.240> thing<00:21:23.520> with<00:21:23.679> this<00:21:23.840> lisp<00:21:24.159> is<00:21:24.279> it's 00:21:24.470 --> 00:21:24.480 align:start position:0% the fun thing with this lisp is it's 00:21:24.480 --> 00:21:26.029 align:start position:0% the fun thing with this lisp is it's actually<00:21:24.640> a<00:21:24.760> multiplayer<00:21:25.360> Lis<00:21:25.720> so<00:21:25.840> when<00:21:25.960> you 00:21:26.029 --> 00:21:26.039 align:start position:0% actually a multiplayer Lis so when you 00:21:26.039 --> 00:21:27.390 align:start position:0% actually a multiplayer Lis so when you boot<00:21:26.279> up<00:21:26.400> a<00:21:26.480> reppel<00:21:26.760> you<00:21:26.919> actually<00:21:27.080> connected 00:21:27.390 --> 00:21:27.400 align:start position:0% boot up a reppel you actually connected 00:21:27.400 --> 00:21:28.710 align:start position:0% boot up a reppel you actually connected to<00:21:27.520> all<00:21:27.640> the<00:21:27.720> people<00:21:27.880> that<00:21:28.000> use<00:21:28.159> the<00:21:28.240> reel<00:21:28.640> as 00:21:28.710 --> 00:21:28.720 align:start position:0% to all the people that use the reel as 00:21:28.720 --> 00:21:30.590 align:start position:0% to all the people that use the reel as well<00:21:28.960> so<00:21:29.120> we<00:21:29.200> can<00:21:29.320> do<00:21:29.480> operations<00:21:29.919> on<00:21:30.080> our<00:21:30.240> pods 00:21:30.590 --> 00:21:30.600 align:start position:0% well so we can do operations on our pods 00:21:30.600 --> 00:21:32.990 align:start position:0% well so we can do operations on our pods Etc<00:21:31.440> uh<00:21:31.520> we'll<00:21:31.720> try<00:21:31.919> to<00:21:32.039> get<00:21:32.120> it<00:21:32.279> working<00:21:32.679> here 00:21:32.990 --> 00:21:33.000 align:start position:0% Etc uh we'll try to get it working here 00:21:33.000 --> 00:21:35.470 align:start position:0% Etc uh we'll try to get it working here but<00:21:33.600> it's<00:21:33.799> it's<00:21:33.919> not<00:21:34.120> that<00:21:34.320> important<00:21:35.320> the 00:21:35.470 --> 00:21:35.480 align:start position:0% but it's it's not that important the 00:21:35.480 --> 00:21:37.430 align:start position:0% but it's it's not that important the second<00:21:35.720> thing<00:21:35.840> that<00:21:35.960> takes<00:21:36.159> a<00:21:36.279> while<00:21:36.559> is<00:21:37.279> we 00:21:37.430 --> 00:21:37.440 align:start position:0% second thing that takes a while is we 00:21:37.440 --> 00:21:39.789 align:start position:0% second thing that takes a while is we don't<00:21:38.039> we<00:21:38.320> recreate<00:21:38.880> the<00:21:39.039> parameters<00:21:39.480> of<00:21:39.600> our 00:21:39.789 --> 00:21:39.799 align:start position:0% don't we recreate the parameters of our 00:21:39.799 --> 00:21:41.590 align:start position:0% don't we recreate the parameters of our circuits<00:21:40.440> and<00:21:40.600> the<00:21:40.720> verification<00:21:41.240> key<00:21:41.440> every 00:21:41.590 --> 00:21:41.600 align:start position:0% circuits and the verification key every 00:21:41.600 --> 00:21:42.789 align:start position:0% circuits and the verification key every time<00:21:41.679> we<00:21:41.799> boot<00:21:42.000> it<00:21:42.120> up<00:21:42.320> because<00:21:42.520> we<00:21:42.600> don't<00:21:42.679> want 00:21:42.789 --> 00:21:42.799 align:start position:0% time we boot it up because we don't want 00:21:42.799 --> 00:21:44.110 align:start position:0% time we boot it up because we don't want to<00:21:42.880> serialize<00:21:43.320> them<00:21:43.400> on<00:21:43.559> dis<00:21:43.799> yet<00:21:43.919> because<00:21:44.039> we 00:21:44.110 --> 00:21:44.120 align:start position:0% to serialize them on dis yet because we 00:21:44.120 --> 00:21:46.590 align:start position:0% to serialize them on dis yet because we changed<00:21:44.360> them<00:21:44.480> all<00:21:44.640> the<00:21:44.760> time<00:21:45.240> so<00:21:46.200> um<00:21:46.400> I'm<00:21:46.480> in 00:21:46.590 --> 00:21:46.600 align:start position:0% changed them all the time so um I'm in 00:21:46.600 --> 00:21:48.510 align:start position:0% changed them all the time so um I'm in the<00:21:46.720> rapple<00:21:47.360> you<00:21:47.480> can<00:21:47.600> see<00:21:48.000> I<00:21:48.080> have<00:21:48.159> a<00:21:48.279> public 00:21:48.510 --> 00:21:48.520 align:start position:0% the rapple you can see I have a public 00:21:48.520 --> 00:21:50.110 align:start position:0% the rapple you can see I have a public key<00:21:48.720> I<00:21:48.760> have<00:21:48.840> a<00:21:48.919> little<00:21:49.159> username<00:21:49.600> my<00:21:49.720> username 00:21:50.110 --> 00:21:50.120 align:start position:0% key I have a little username my username 00:21:50.120 --> 00:21:53.470 align:start position:0% key I have a little username my username is<00:21:50.320> pulser<00:21:50.919> Voyager<00:21:51.919> and<00:21:52.080> so<00:21:52.880> what<00:21:53.000> I<00:21:53.120> can<00:21:53.279> do 00:21:53.470 --> 00:21:53.480 align:start position:0% is pulser Voyager and so what I can do 00:21:53.480 --> 00:21:56.390 align:start position:0% is pulser Voyager and so what I can do with<00:21:53.640> this<00:21:53.760> repple<00:21:54.400> is<00:21:54.520> I<00:21:54.679> can<00:21:55.080> create<00:21:55.440> pods<00:21:56.320> I 00:21:56.390 --> 00:21:56.400 align:start position:0% with this repple is I can create pods I 00:21:56.400 --> 00:21:58.950 align:start position:0% with this repple is I can create pods I can<00:21:56.559> either<00:21:56.840> create<00:21:57.159> pods<00:21:57.480> out<00:21:57.640> of<00:21:57.880> nothing<00:21:58.799> uh 00:21:58.950 --> 00:21:58.960 align:start position:0% can either create pods out of nothing uh 00:21:58.960 --> 00:22:00.430 align:start position:0% can either create pods out of nothing uh if<00:21:59.080> you<00:21:59.240> remember<00:21:59.600> my<00:21:59.760> slides<00:22:00.080> it's<00:22:00.240> like 00:22:00.430 --> 00:22:00.440 align:start position:0% if you remember my slides it's like 00:22:00.440 --> 00:22:02.269 align:start position:0% if you remember my slides it's like importing<00:22:00.880> a<00:22:01.039> pod<00:22:01.720> but<00:22:01.840> because<00:22:02.039> we<00:22:02.159> don't 00:22:02.269 --> 00:22:02.279 align:start position:0% importing a pod but because we don't 00:22:02.279 --> 00:22:04.190 align:start position:0% importing a pod but because we don't have<00:22:02.440> any<00:22:02.679> good<00:22:02.880> importing<00:22:03.360> system<00:22:03.760> yet<00:22:03.960> for 00:22:04.190 --> 00:22:04.200 align:start position:0% have any good importing system yet for 00:22:04.200 --> 00:22:05.750 align:start position:0% have any good importing system yet for existing<00:22:04.520> cryptographic<00:22:05.120> data<00:22:05.440> the<00:22:05.559> way<00:22:05.679> I'm 00:22:05.750 --> 00:22:05.760 align:start position:0% existing cryptographic data the way I'm 00:22:05.760 --> 00:22:07.110 align:start position:0% existing cryptographic data the way I'm going<00:22:05.840> to<00:22:05.960> import<00:22:06.320> pods<00:22:06.640> I'm<00:22:06.760> just<00:22:06.880> going<00:22:06.960> to 00:22:07.110 --> 00:22:07.120 align:start position:0% going to import pods I'm just going to 00:22:07.120 --> 00:22:09.390 align:start position:0% going to import pods I'm just going to self<00:22:07.600> sign<00:22:07.840> them<00:22:08.480> but<00:22:08.600> you<00:22:08.720> could<00:22:08.960> imagine 00:22:09.390 --> 00:22:09.400 align:start position:0% self sign them but you could imagine 00:22:09.400 --> 00:22:10.950 align:start position:0% self sign them but you could imagine that<00:22:09.679> if<00:22:09.760> you<00:22:09.840> were<00:22:10.000> to<00:22:10.120> import<00:22:10.400> a<00:22:10.520> pod<00:22:10.679> as<00:22:10.799> well 00:22:10.950 --> 00:22:10.960 align:start position:0% that if you were to import a pod as well 00:22:10.960 --> 00:22:12.430 align:start position:0% that if you were to import a pod as well and<00:22:11.039> you<00:22:11.159> gave<00:22:11.320> me<00:22:11.480> your<00:22:11.720> username<00:22:12.200> we<00:22:12.279> would 00:22:12.430 --> 00:22:12.440 align:start position:0% and you gave me your username we would 00:22:12.440 --> 00:22:13.470 align:start position:0% and you gave me your username we would be<00:22:12.520> able<00:22:12.640> to<00:22:12.760> compute<00:22:13.039> on<00:22:13.159> top<00:22:13.279> of<00:22:13.360> each 00:22:13.470 --> 00:22:13.480 align:start position:0% be able to compute on top of each 00:22:13.480 --> 00:22:15.510 align:start position:0% be able to compute on top of each other's<00:22:13.799> pod<00:22:14.640> what<00:22:14.720> I<00:22:14.840> can<00:22:14.919> do<00:22:15.080> as<00:22:15.200> well<00:22:15.320> is<00:22:15.440> I 00:22:15.510 --> 00:22:15.520 align:start position:0% other's pod what I can do as well is I 00:22:15.520 --> 00:22:17.310 align:start position:0% other's pod what I can do as well is I can<00:22:15.760> create<00:22:16.080> pods<00:22:16.360> from<00:22:16.520> previous<00:22:16.840> pods<00:22:17.200> which 00:22:17.310 --> 00:22:17.320 align:start position:0% can create pods from previous pods which 00:22:17.320 --> 00:22:21.190 align:start position:0% can create pods from previous pods which is<00:22:17.480> really<00:22:17.679> the<00:22:17.840> key<00:22:18.039> of<00:22:18.159> the<00:22:18.320> system<00:22:19.640> so<00:22:20.640> um 00:22:21.190 --> 00:22:21.200 align:start position:0% is really the key of the system so um 00:22:21.200 --> 00:22:24.950 align:start position:0% is really the key of the system so um let's<00:22:21.440> make<00:22:21.559> a<00:22:22.120> pod<00:22:23.120> so<00:22:23.919> also<00:22:24.360> this<00:22:24.559> language 00:22:24.950 --> 00:22:24.960 align:start position:0% let's make a pod so also this language 00:22:24.960 --> 00:22:27.149 align:start position:0% let's make a pod so also this language and<00:22:25.120> also<00:22:25.279> the<00:22:25.440> logic<00:22:25.760> only<00:22:26.080> support<00:22:26.640> numbers 00:22:27.149 --> 00:22:27.159 align:start position:0% and also the logic only support numbers 00:22:27.159 --> 00:22:29.110 align:start position:0% and also the logic only support numbers and<00:22:27.360> list<00:22:27.559> of<00:22:27.760> numbers<00:22:28.520> so<00:22:28.679> there<00:22:28.760> are<00:22:28.880> many 00:22:29.110 --> 00:22:29.120 align:start position:0% and list of numbers so there are many 00:22:29.120 --> 00:22:31.269 align:start position:0% and list of numbers so there are many things<00:22:29.320> I<00:22:29.480> would<00:22:29.600> like<00:22:29.760> to<00:22:29.840> show<00:22:30.279> that<00:22:31.000> don't 00:22:31.269 --> 00:22:31.279 align:start position:0% things I would like to show that don't 00:22:31.279 --> 00:22:32.750 align:start position:0% things I would like to show that don't use<00:22:31.520> numbers<00:22:31.840> and<00:22:32.000> use<00:22:32.200> different<00:22:32.440> kind<00:22:32.559> of 00:22:32.750 --> 00:22:32.760 align:start position:0% use numbers and use different kind of 00:22:32.760 --> 00:22:34.510 align:start position:0% use numbers and use different kind of things<00:22:33.360> so<00:22:33.600> you<00:22:33.679> will<00:22:33.880> see<00:22:34.120> some<00:22:34.240> of<00:22:34.360> my 00:22:34.510 --> 00:22:34.520 align:start position:0% things so you will see some of my 00:22:34.520 --> 00:22:35.990 align:start position:0% things so you will see some of my examples<00:22:34.840> are<00:22:34.919> a<00:22:35.000> little<00:22:35.120> bit<00:22:35.240> contrived<00:22:35.840> but 00:22:35.990 --> 00:22:36.000 align:start position:0% examples are a little bit contrived but 00:22:36.000 --> 00:22:37.590 align:start position:0% examples are a little bit contrived but it's<00:22:36.240> it's<00:22:36.480> because<00:22:36.880> we<00:22:37.000> have<00:22:37.080> to<00:22:37.200> work<00:22:37.400> with 00:22:37.590 --> 00:22:37.600 align:start position:0% it's it's because we have to work with 00:22:37.600 --> 00:22:41.549 align:start position:0% it's it's because we have to work with what<00:22:37.720> we<00:22:38.000> have<00:22:39.000> so<00:22:39.480> um<00:22:40.240> can<00:22:40.640> can<00:22:40.840> people<00:22:41.120> show 00:22:41.549 --> 00:22:41.559 align:start position:0% what we have so um can can people show 00:22:41.559 --> 00:22:44.470 align:start position:0% what we have so um can can people show hands<00:22:42.080> if<00:22:42.279> they<00:22:42.559> have<00:22:42.840> read<00:22:43.320> the<00:22:43.480> list<00:22:43.880> syntax 00:22:44.470 --> 00:22:44.480 align:start position:0% hands if they have read the list syntax 00:22:44.480 --> 00:22:46.510 align:start position:0% hands if they have read the list syntax before<00:22:44.760> or<00:22:44.919> something<00:22:45.279> similar<00:22:45.840> so<00:22:46.080> I<00:22:46.159> can<00:22:46.279> see 00:22:46.510 --> 00:22:46.520 align:start position:0% before or something similar so I can see 00:22:46.520 --> 00:22:48.430 align:start position:0% before or something similar so I can see whether<00:22:46.679> I<00:22:46.760> have<00:22:46.880> to<00:22:46.960> spend<00:22:47.159> a<00:22:47.200> lot<00:22:47.320> of<00:22:47.440> time<00:22:47.559> on 00:22:48.430 --> 00:22:48.440 align:start position:0% whether I have to spend a lot of time on 00:22:48.440 --> 00:22:51.390 align:start position:0% whether I have to spend a lot of time on this<00:22:49.440> okay<00:22:50.200> so<00:22:50.400> one<00:22:50.600> thing<00:22:50.760> to<00:22:50.919> know<00:22:51.120> about 00:22:51.390 --> 00:22:51.400 align:start position:0% this okay so one thing to know about 00:22:51.400 --> 00:22:54.950 align:start position:0% this okay so one thing to know about lisp<00:22:52.080> is<00:22:52.320> that<00:22:53.240> um<00:22:53.840> it's<00:22:53.960> a<00:22:54.159> very<00:22:54.400> simple<00:22:54.760> kind 00:22:54.950 --> 00:22:54.960 align:start position:0% lisp is that um it's a very simple kind 00:22:54.960 --> 00:22:56.430 align:start position:0% lisp is that um it's a very simple kind of<00:22:55.159> programming<00:22:55.559> language<00:22:55.880> it's<00:22:56.039> really<00:22:56.240> easy 00:22:56.430 --> 00:22:56.440 align:start position:0% of programming language it's really easy 00:22:56.440 --> 00:22:58.630 align:start position:0% of programming language it's really easy to<00:22:56.640> parse<00:22:57.080> the<00:22:57.200> way<00:22:57.320> it<00:22:57.480> works<00:22:57.919> is<00:22:58.200> every<00:22:58.520> every 00:22:58.630 --> 00:22:58.640 align:start position:0% to parse the way it works is every every 00:22:58.640 --> 00:23:00.470 align:start position:0% to parse the way it works is every every time<00:22:58.760> you<00:22:58.880> see<00:22:59.120> brackets<00:22:59.760> you<00:22:59.919> try<00:23:00.120> to<00:23:00.240> find 00:23:00.470 --> 00:23:00.480 align:start position:0% time you see brackets you try to find 00:23:00.480 --> 00:23:02.029 align:start position:0% time you see brackets you try to find the<00:23:00.600> closing<00:23:01.000> bracket<00:23:01.400> for<00:23:01.600> this<00:23:01.840> and<00:23:01.919> you 00:23:02.029 --> 00:23:02.039 align:start position:0% the closing bracket for this and you 00:23:02.039 --> 00:23:03.909 align:start position:0% the closing bracket for this and you have<00:23:02.159> to<00:23:02.360> imagine<00:23:02.799> in<00:23:02.919> your<00:23:03.159> head<00:23:03.640> that<00:23:03.799> the 00:23:03.909 --> 00:23:03.919 align:start position:0% have to imagine in your head that the 00:23:03.919 --> 00:23:05.669 align:start position:0% have to imagine in your head that the computer<00:23:04.279> is<00:23:04.400> going<00:23:04.480> to<00:23:04.640> turn<00:23:04.960> this<00:23:05.200> into<00:23:05.400> the 00:23:05.669 --> 00:23:05.679 align:start position:0% computer is going to turn this into the 00:23:05.679 --> 00:23:07.750 align:start position:0% computer is going to turn this into the result<00:23:06.120> of<00:23:06.320> that<00:23:06.520> computation<00:23:07.360> so<00:23:07.520> as<00:23:07.600> an 00:23:07.750 --> 00:23:07.760 align:start position:0% result of that computation so as an 00:23:07.760 --> 00:23:10.470 align:start position:0% result of that computation so as an example<00:23:08.120> if<00:23:08.240> I<00:23:08.360> do<00:23:08.559> plus<00:23:08.840> one<00:23:09.120> two<00:23:09.960> it<00:23:10.080> uses<00:23:10.360> the 00:23:10.470 --> 00:23:10.480 align:start position:0% example if I do plus one two it uses the 00:23:10.480 --> 00:23:12.269 align:start position:0% example if I do plus one two it uses the infix<00:23:10.919> notation<00:23:11.480> instead<00:23:11.799> of<00:23:11.919> sorry<00:23:12.159> the 00:23:12.269 --> 00:23:12.279 align:start position:0% infix notation instead of sorry the 00:23:12.279 --> 00:23:13.750 align:start position:0% infix notation instead of sorry the prefix<00:23:12.640> notation<00:23:13.039> instead<00:23:13.240> of<00:23:13.400> infix 00:23:13.750 --> 00:23:13.760 align:start position:0% prefix notation instead of infix 00:23:13.760 --> 00:23:15.789 align:start position:0% prefix notation instead of infix notation<00:23:14.159> this<00:23:14.240> means<00:23:15.039> the<00:23:15.200> computation<00:23:15.640> I'm 00:23:15.789 --> 00:23:15.799 align:start position:0% notation this means the computation I'm 00:23:15.799 --> 00:23:17.630 align:start position:0% notation this means the computation I'm executing<00:23:16.240> is<00:23:16.440> plus<00:23:16.840> and<00:23:16.960> it's<00:23:17.080> over<00:23:17.320> one<00:23:17.480> and 00:23:17.630 --> 00:23:17.640 align:start position:0% executing is plus and it's over one and 00:23:17.640 --> 00:23:19.549 align:start position:0% executing is plus and it's over one and two<00:23:18.080> so<00:23:18.240> this<00:23:18.320> is<00:23:18.440> going<00:23:18.559> to<00:23:18.720> turn 00:23:19.549 --> 00:23:19.559 align:start position:0% two so this is going to turn 00:23:19.559 --> 00:23:24.230 align:start position:0% two so this is going to turn into<00:23:20.799> three<00:23:21.799> see<00:23:22.039> I<00:23:22.159> get<00:23:22.360> scale<00:23:22.600> or<00:23:22.880> three<00:23:23.760> and 00:23:24.230 --> 00:23:24.240 align:start position:0% into three see I get scale or three and 00:23:24.240 --> 00:23:26.870 align:start position:0% into three see I get scale or three and if<00:23:24.400> I<00:23:24.559> want<00:23:24.760> to<00:23:25.559> do<00:23:26.200> different<00:23:26.480> things<00:23:26.679> with 00:23:26.870 --> 00:23:26.880 align:start position:0% if I want to do different things with 00:23:26.880 --> 00:23:28.510 align:start position:0% if I want to do different things with different<00:23:27.120> orders<00:23:27.640> I<00:23:27.720> can<00:23:27.919> keep<00:23:28.120> putting 00:23:28.510 --> 00:23:28.520 align:start position:0% different orders I can keep putting 00:23:28.520 --> 00:23:32.750 align:start position:0% different orders I can keep putting bracket<00:23:28.880> so<00:23:29.000> as<00:23:29.080> an<00:23:29.279> example<00:23:30.279> if<00:23:30.400> I<00:23:30.720> do<00:23:31.720> uh<00:23:32.080> plus 00:23:32.750 --> 00:23:32.760 align:start position:0% bracket so as an example if I do uh plus 00:23:32.760 --> 00:23:35.669 align:start position:0% bracket so as an example if I do uh plus 3<00:23:33.240> 4<00:23:34.080> what's<00:23:34.279> going<00:23:34.400> to<00:23:34.600> happen<00:23:34.960> here<00:23:35.240> is<00:23:35.480> three 00:23:35.669 --> 00:23:35.679 align:start position:0% 3 4 what's going to happen here is three 00:23:35.679 --> 00:23:37.549 align:start position:0% 3 4 what's going to happen here is three and<00:23:35.799> four<00:23:35.960> are<00:23:36.080> going<00:23:36.159> to<00:23:36.240> be<00:23:36.480> summed<00:23:36.840> first 00:23:37.549 --> 00:23:37.559 align:start position:0% and four are going to be summed first 00:23:37.559 --> 00:23:39.110 align:start position:0% and four are going to be summed first and<00:23:37.720> then<00:23:38.159> it's<00:23:38.320> going<00:23:38.400> to<00:23:38.480> be<00:23:38.600> summed<00:23:38.919> with 00:23:39.110 --> 00:23:39.120 align:start position:0% and then it's going to be summed with 00:23:39.120 --> 00:23:41.230 align:start position:0% and then it's going to be summed with one<00:23:39.440> so<00:23:39.600> we're<00:23:39.720> going<00:23:39.840> to<00:23:40.000> get<00:23:40.480> eight<00:23:40.840> out<00:23:41.039> of 00:23:41.230 --> 00:23:41.240 align:start position:0% one so we're going to get eight out of 00:23:41.240 --> 00:23:43.269 align:start position:0% one so we're going to get eight out of that<00:23:41.600> right<00:23:42.159> so<00:23:42.559> if<00:23:42.640> you<00:23:42.720> don't<00:23:43.159> understand 00:23:43.269 --> 00:23:43.279 align:start position:0% that right so if you don't understand 00:23:43.279 --> 00:23:45.190 align:start position:0% that right so if you don't understand the<00:23:43.440> syntax<00:23:43.840> at<00:23:43.960> any<00:23:44.120> moment<00:23:44.559> tell<00:23:44.760> me<00:23:45.039> and 00:23:45.190 --> 00:23:45.200 align:start position:0% the syntax at any moment tell me and 00:23:45.200 --> 00:23:46.870 align:start position:0% the syntax at any moment tell me and I'll<00:23:45.440> I'll<00:23:45.600> explain<00:23:45.880> you<00:23:46.000> how<00:23:46.120> it<00:23:46.240> works<00:23:46.760> but 00:23:46.870 --> 00:23:46.880 align:start position:0% I'll I'll explain you how it works but 00:23:46.880 --> 00:23:48.830 align:start position:0% I'll I'll explain you how it works but it's<00:23:47.039> not<00:23:47.360> as<00:23:47.559> scary<00:23:47.919> as<00:23:48.000> it<00:23:48.120> seems<00:23:48.640> and<00:23:48.760> the 00:23:48.830 --> 00:23:48.840 align:start position:0% it's not as scary as it seems and the 00:23:48.840 --> 00:23:50.350 align:start position:0% it's not as scary as it seems and the reason<00:23:49.080> why<00:23:49.200> we<00:23:49.279> wrote<00:23:49.480> a<00:23:49.559> list<00:23:49.840> once<00:23:50.039> again<00:23:50.200> is 00:23:50.350 --> 00:23:50.360 align:start position:0% reason why we wrote a list once again is 00:23:50.360 --> 00:23:52.110 align:start position:0% reason why we wrote a list once again is because<00:23:50.520> it's<00:23:50.799> really<00:23:51.039> easy<00:23:51.279> to<00:23:51.440> write<00:23:51.640> a<00:23:51.760> list 00:23:52.110 --> 00:23:52.120 align:start position:0% because it's really easy to write a list 00:23:52.120 --> 00:23:53.870 align:start position:0% because it's really easy to write a list parser<00:23:52.559> and<00:23:52.679> Lexar<00:23:53.000> and<00:23:53.159> interpreter<00:23:53.640> whereas 00:23:53.870 --> 00:23:53.880 align:start position:0% parser and Lexar and interpreter whereas 00:23:53.880 --> 00:23:55.990 align:start position:0% parser and Lexar and interpreter whereas it's<00:23:54.240> really<00:23:54.520> hard<00:23:54.799> to<00:23:54.960> write<00:23:55.159> a<00:23:55.360> parser<00:23:55.720> Lexar 00:23:55.990 --> 00:23:56.000 align:start position:0% it's really hard to write a parser Lexar 00:23:56.000 --> 00:23:58.310 align:start position:0% it's really hard to write a parser Lexar and<00:23:56.120> interpreter<00:23:56.520> for<00:23:56.720> imperative<00:23:57.320> languages 00:23:58.310 --> 00:23:58.320 align:start position:0% and interpreter for imperative languages 00:23:58.320 --> 00:24:00.830 align:start position:0% and interpreter for imperative languages um<00:23:58.559> um<00:23:59.320> okay<00:23:59.480> so<00:23:59.600> let's<00:23:59.799> make<00:23:59.919> some<00:24:00.159> pod<00:24:00.760> the 00:24:00.830 --> 00:24:00.840 align:start position:0% um um okay so let's make some pod the 00:24:00.840 --> 00:24:02.149 align:start position:0% um um okay so let's make some pod the first<00:24:01.080> pod<00:24:01.240> I'm<00:24:01.320> going<00:24:01.480> to<00:24:01.600> make<00:24:01.799> is<00:24:01.960> almost 00:24:02.149 --> 00:24:02.159 align:start position:0% first pod I'm going to make is almost 00:24:02.159 --> 00:24:04.070 align:start position:0% first pod I'm going to make is almost like<00:24:02.279> an<00:24:02.480> ID<00:24:02.840> card<00:24:03.080> for<00:24:03.320> myself<00:24:03.640> so<00:24:03.840> what's 00:24:04.070 --> 00:24:04.080 align:start position:0% like an ID card for myself so what's 00:24:04.080 --> 00:24:05.350 align:start position:0% like an ID card for myself so what's what's<00:24:04.279> this<00:24:04.440> ID<00:24:04.679> card<00:24:04.880> going<00:24:04.960> to<00:24:05.080> have<00:24:05.200> and 00:24:05.350 --> 00:24:05.360 align:start position:0% what's this ID card going to have and 00:24:05.360 --> 00:24:07.630 align:start position:0% what's this ID card going to have and remember<00:24:05.760> we<00:24:05.840> can<00:24:05.960> only<00:24:06.159> use<00:24:06.480> numbers<00:24:07.320> so 00:24:07.630 --> 00:24:07.640 align:start position:0% remember we can only use numbers so 00:24:07.640 --> 00:24:09.630 align:start position:0% remember we can only use numbers so first<00:24:07.880> I<00:24:07.960> have<00:24:08.080> some<00:24:08.240> form<00:24:08.400> of<00:24:08.559> like<00:24:08.799> national 00:24:09.630 --> 00:24:09.640 align:start position:0% first I have some form of like national 00:24:09.640 --> 00:24:11.669 align:start position:0% first I have some form of like national ID<00:24:10.159> it's<00:24:10.320> kind<00:24:10.440> of<00:24:10.559> like<00:24:10.679> my<00:24:10.799> user<00:24:11.080> ID<00:24:11.360> in<00:24:11.520> the 00:24:11.669 --> 00:24:11.679 align:start position:0% ID it's kind of like my user ID in the 00:24:11.679 --> 00:24:14.750 align:start position:0% ID it's kind of like my user ID in the system<00:24:12.679> um<00:24:13.279> I<00:24:13.440> might<00:24:13.640> have<00:24:13.760> an<00:24:13.960> age<00:24:14.200> on<00:24:14.360> it<00:24:14.679> I 00:24:14.750 --> 00:24:14.760 align:start position:0% system um I might have an age on it I 00:24:14.760 --> 00:24:15.909 align:start position:0% system um I might have an age on it I know<00:24:14.919> that<00:24:15.039> the<00:24:15.159> proper<00:24:15.400> way<00:24:15.520> to<00:24:15.640> do<00:24:15.760> this 00:24:15.909 --> 00:24:15.919 align:start position:0% know that the proper way to do this 00:24:15.919 --> 00:24:17.789 align:start position:0% know that the proper way to do this would<00:24:16.080> be<00:24:16.279> date<00:24:16.440> of<00:24:16.600> birth<00:24:17.039> but<00:24:17.240> we'll<00:24:17.480> skip 00:24:17.789 --> 00:24:17.799 align:start position:0% would be date of birth but we'll skip 00:24:17.799 --> 00:24:20.510 align:start position:0% would be date of birth but we'll skip that<00:24:18.000> so<00:24:18.279> I'm<00:24:18.480> 26<00:24:19.080> and<00:24:19.200> also<00:24:19.679> in<00:24:19.799> my<00:24:20.080> in<00:24:20.159> my<00:24:20.279> ID 00:24:20.510 --> 00:24:20.520 align:start position:0% that so I'm 26 and also in my in my ID 00:24:20.520 --> 00:24:23.149 align:start position:0% that so I'm 26 and also in my in my ID card<00:24:20.720> I<00:24:20.799> have<00:24:21.080> the<00:24:21.240> ZIP<00:24:21.480> Code<00:24:21.799> 11<00:24:22.799> I've<00:24:23.000> never 00:24:23.149 --> 00:24:23.159 align:start position:0% card I have the ZIP Code 11 I've never 00:24:23.159 --> 00:24:24.789 align:start position:0% card I have the ZIP Code 11 I've never used<00:24:23.440> zip<00:24:23.679> code<00:24:23.880> this<00:24:24.039> much<00:24:24.159> in<00:24:24.279> my<00:24:24.440> life<00:24:24.679> by 00:24:24.789 --> 00:24:24.799 align:start position:0% used zip code this much in my life by 00:24:24.799 --> 00:24:25.950 align:start position:0% used zip code this much in my life by the<00:24:24.880> way<00:24:25.039> zip<00:24:25.240> codes<00:24:25.440> are<00:24:25.559> great<00:24:25.799> because 00:24:25.950 --> 00:24:25.960 align:start position:0% the way zip codes are great because 00:24:25.960 --> 00:24:27.990 align:start position:0% the way zip codes are great because they're<00:24:26.159> also<00:24:26.399> a<00:24:26.559> number<00:24:27.000> thing<00:24:27.320> about<00:24:27.559> you<00:24:27.760> in 00:24:27.990 --> 00:24:28.000 align:start position:0% they're also a number thing about you in 00:24:28.000 --> 00:24:30.630 align:start position:0% they're also a number thing about you in the<00:24:28.159> most<00:24:28.440> other<00:24:28.720> things<00:24:29.720> okay<00:24:30.120> so<00:24:30.279> I<00:24:30.440> press 00:24:30.630 --> 00:24:30.640 align:start position:0% the most other things okay so I press 00:24:30.640 --> 00:24:32.669 align:start position:0% the most other things okay so I press enter<00:24:30.960> here<00:24:31.279> and<00:24:31.399> I<00:24:31.520> get<00:24:31.640> a<00:24:31.840> pod<00:24:32.360> and<00:24:32.440> you'll 00:24:32.669 --> 00:24:32.679 align:start position:0% enter here and I get a pod and you'll 00:24:32.679 --> 00:24:35.070 align:start position:0% enter here and I get a pod and you'll notice<00:24:33.159> that<00:24:34.159> uh<00:24:34.240> we<00:24:34.360> get<00:24:34.600> like<00:24:34.760> useful 00:24:35.070 --> 00:24:35.080 align:start position:0% notice that uh we get like useful 00:24:35.080 --> 00:24:36.870 align:start position:0% notice that uh we get like useful debugging<00:24:35.559> window<00:24:35.919> here<00:24:36.080> that<00:24:36.240> tells<00:24:36.760> that 00:24:36.870 --> 00:24:36.880 align:start position:0% debugging window here that tells that 00:24:36.880 --> 00:24:39.710 align:start position:0% debugging window here that tells that tells<00:24:37.159> us<00:24:37.640> the<00:24:37.880> type<00:24:38.120> of<00:24:38.240> our<00:24:38.559> pod<00:24:39.000> that<00:24:39.120> is<00:24:39.520> the 00:24:39.710 --> 00:24:39.720 align:start position:0% tells us the type of our pod that is the 00:24:39.720 --> 00:24:41.470 align:start position:0% tells us the type of our pod that is the cryptographic<00:24:40.399> Machinery<00:24:40.919> you<00:24:41.039> have<00:24:41.159> to<00:24:41.279> use 00:24:41.470 --> 00:24:41.480 align:start position:0% cryptographic Machinery you have to use 00:24:41.480 --> 00:24:43.950 align:start position:0% cryptographic Machinery you have to use to<00:24:41.600> verify<00:24:41.960> the<00:24:42.120> Pod<00:24:42.279> is<00:24:42.399> schnor<00:24:42.799> 16<00:24:43.399> so<00:24:43.559> schnor 00:24:43.950 --> 00:24:43.960 align:start position:0% to verify the Pod is schnor 16 so schnor 00:24:43.960 --> 00:24:46.710 align:start position:0% to verify the Pod is schnor 16 so schnor is<00:24:44.039> a<00:24:44.480> signing<00:24:44.919> algorithm<00:24:45.840> so<00:24:46.000> this<00:24:46.080> is<00:24:46.200> a<00:24:46.360> self 00:24:46.710 --> 00:24:46.720 align:start position:0% is a signing algorithm so this is a self 00:24:46.720 --> 00:24:48.549 align:start position:0% is a signing algorithm so this is a self sign<00:24:46.960> pod<00:24:47.200> that<00:24:47.279> I<00:24:47.399> just<00:24:47.520> made<00:24:47.679> about<00:24:47.960> myself 00:24:48.549 --> 00:24:48.559 align:start position:0% sign pod that I just made about myself 00:24:48.559 --> 00:24:50.149 align:start position:0% sign pod that I just made about myself and<00:24:48.679> inside<00:24:48.960> we<00:24:49.080> have<00:24:49.159> a<00:24:49.240> bunch<00:24:49.399> of<00:24:49.559> logical 00:24:50.149 --> 00:24:50.159 align:start position:0% and inside we have a bunch of logical 00:24:50.159 --> 00:24:52.350 align:start position:0% and inside we have a bunch of logical statements<00:24:51.159> all<00:24:51.279> of<00:24:51.440> these<00:24:51.600> statements<00:24:52.039> have 00:24:52.350 --> 00:24:52.360 align:start position:0% statements all of these statements have 00:24:52.360 --> 00:24:54.070 align:start position:0% statements all of these statements have value<00:24:52.640> of<00:24:52.840> statements<00:24:53.240> so<00:24:53.399> they<00:24:53.559> just<00:24:53.679> make<00:24:53.840> a 00:24:54.070 --> 00:24:54.080 align:start position:0% value of statements so they just make a 00:24:54.080 --> 00:24:56.070 align:start position:0% value of statements so they just make a claim<00:24:54.440> about<00:24:54.640> an<00:24:54.799> entry<00:24:55.159> in<00:24:55.240> the<00:24:55.440> system<00:24:55.919> in 00:24:56.070 --> 00:24:56.080 align:start position:0% claim about an entry in the system in 00:24:56.080 --> 00:24:58.590 align:start position:0% claim about an entry in the system in this<00:24:56.279> specific<00:24:56.679> pod<00:24:57.640> so<00:24:57.760> you'll<00:24:57.960> see<00:24:58.159> that<00:24:58.440> it 00:24:58.590 --> 00:24:58.600 align:start position:0% this specific pod so you'll see that it 00:24:58.600 --> 00:25:02.190 align:start position:0% this specific pod so you'll see that it claims<00:24:58.919> that<00:24:59.120> my<00:24:59.360> age<00:24:59.840> is<00:25:00.320> 26<00:25:01.320> my<00:25:01.520> ID<00:25:01.919> is<00:25:02.039> the 00:25:02.190 --> 00:25:02.200 align:start position:0% claims that my age is 26 my ID is the 00:25:02.200 --> 00:25:05.110 align:start position:0% claims that my age is 26 my ID is the number<00:25:02.480> I<00:25:02.600> typed<00:25:03.120> and<00:25:03.240> my<00:25:03.399> zip<00:25:03.679> code<00:25:03.880> is<00:25:04.120> 121 00:25:05.110 --> 00:25:05.120 align:start position:0% number I typed and my zip code is 121 00:25:05.120 --> 00:25:07.710 align:start position:0% number I typed and my zip code is 121 and<00:25:05.279> on<00:25:05.480> top<00:25:05.640> of<00:25:05.799> that<00:25:05.960> we<00:25:06.080> have<00:25:06.480> another<00:25:07.480> value 00:25:07.710 --> 00:25:07.720 align:start position:0% and on top of that we have another value 00:25:07.720 --> 00:25:08.789 align:start position:0% and on top of that we have another value of<00:25:07.840> statement<00:25:08.159> that<00:25:08.279> has<00:25:08.399> been<00:25:08.520> added 00:25:08.789 --> 00:25:08.799 align:start position:0% of statement that has been added 00:25:08.799 --> 00:25:10.710 align:start position:0% of statement that has been added automatically<00:25:09.679> that<00:25:09.799> I<00:25:09.960> did<00:25:10.120> not<00:25:10.320> set<00:25:10.600> and 00:25:10.710 --> 00:25:10.720 align:start position:0% automatically that I did not set and 00:25:10.720 --> 00:25:12.310 align:start position:0% automatically that I did not set and that<00:25:10.960> in<00:25:11.120> fact<00:25:11.279> I<00:25:11.399> cannot<00:25:11.720> set<00:25:12.080> because<00:25:12.240> it 00:25:12.310 --> 00:25:12.320 align:start position:0% that in fact I cannot set because it 00:25:12.320 --> 00:25:14.470 align:start position:0% that in fact I cannot set because it starts<00:25:12.600> with<00:25:12.720> an<00:25:12.840> under<00:25:13.360> score<00:25:13.880> which<00:25:14.000> is<00:25:14.159> the 00:25:14.470 --> 00:25:14.480 align:start position:0% starts with an under score which is the 00:25:14.480 --> 00:25:18.149 align:start position:0% starts with an under score which is the public<00:25:14.960> key<00:25:15.600> that<00:25:15.799> signed<00:25:16.200> this<00:25:16.640> pod<00:25:17.640> um<00:25:18.000> it's 00:25:18.149 --> 00:25:18.159 align:start position:0% public key that signed this pod um it's 00:25:18.159 --> 00:25:20.230 align:start position:0% public key that signed this pod um it's the<00:25:18.279> same<00:25:18.600> here<00:25:19.080> so<00:25:19.240> you'll<00:25:19.440> notice<00:25:19.919> that<00:25:20.159> as 00:25:20.230 --> 00:25:20.240 align:start position:0% the same here so you'll notice that as 00:25:20.240 --> 00:25:22.110 align:start position:0% the same here so you'll notice that as an<00:25:20.399> example<00:25:20.679> for<00:25:20.840> this<00:25:21.080> pod<00:25:21.480> the<00:25:21.640> public<00:25:21.919> key 00:25:22.110 --> 00:25:22.120 align:start position:0% an example for this pod the public key 00:25:22.120 --> 00:25:24.029 align:start position:0% an example for this pod the public key which<00:25:22.240> is<00:25:22.360> an<00:25:22.520> important<00:25:22.960> value<00:25:23.200> in<00:25:23.279> order<00:25:23.520> to 00:25:24.029 --> 00:25:24.039 align:start position:0% which is an important value in order to 00:25:24.039 --> 00:25:26.190 align:start position:0% which is an important value in order to Anchor<00:25:24.960> that<00:25:25.120> piece<00:25:25.279> of<00:25:25.480> information<00:25:25.840> to 00:25:26.190 --> 00:25:26.200 align:start position:0% Anchor that piece of information to 00:25:26.200 --> 00:25:28.909 align:start position:0% Anchor that piece of information to reality<00:25:27.200> is<00:25:27.720> something<00:25:28.039> we<00:25:28.200> can<00:25:28.360> can<00:25:28.559> operate 00:25:28.909 --> 00:25:28.919 align:start position:0% reality is something we can can operate 00:25:28.919 --> 00:25:30.510 align:start position:0% reality is something we can can operate on<00:25:29.120> the<00:25:29.240> same<00:25:29.440> way<00:25:29.600> we<00:25:29.679> can<00:25:29.840> operate<00:25:30.120> on<00:25:30.240> other 00:25:30.510 --> 00:25:30.520 align:start position:0% on the same way we can operate on other 00:25:30.520 --> 00:25:32.389 align:start position:0% on the same way we can operate on other kinds<00:25:30.720> of<00:25:30.919> data<00:25:31.480> public<00:25:31.760> keys<00:25:31.960> are<00:25:32.080> not 00:25:32.389 --> 00:25:32.399 align:start position:0% kinds of data public keys are not 00:25:32.399 --> 00:25:34.990 align:start position:0% kinds of data public keys are not special<00:25:32.919> in<00:25:33.080> the<00:25:33.279> system<00:25:33.640> they're<00:25:33.919> just 00:25:34.990 --> 00:25:35.000 align:start position:0% special in the system they're just 00:25:35.000 --> 00:25:38.149 align:start position:0% special in the system they're just data<00:25:36.000> cool<00:25:36.600> okay<00:25:36.760> so<00:25:36.919> let's<00:25:37.080> make<00:25:37.200> another<00:25:37.559> pod 00:25:38.149 --> 00:25:38.159 align:start position:0% data cool okay so let's make another pod 00:25:38.159 --> 00:25:41.470 align:start position:0% data cool okay so let's make another pod and<00:25:38.440> this<00:25:38.600> aod<00:25:39.039> is<00:25:39.120> going<00:25:39.279> to<00:25:39.360> be<00:25:39.480> a<00:25:39.679> past<00:25:40.480> tub 00:25:41.470 --> 00:25:41.480 align:start position:0% and this aod is going to be a past tub 00:25:41.480 --> 00:25:44.510 align:start position:0% and this aod is going to be a past tub uh<00:25:41.799> so<00:25:42.600> this<00:25:42.760> past<00:25:43.080> Tu<00:25:43.720> it's<00:25:43.919> issued<00:25:44.399> by 00:25:44.510 --> 00:25:44.520 align:start position:0% uh so this past Tu it's issued by 00:25:44.520 --> 00:25:46.389 align:start position:0% uh so this past Tu it's issued by someone<00:25:44.799> else<00:25:45.399> ideally<00:25:45.799> I<00:25:45.880> would<00:25:46.000> be<00:25:46.120> able<00:25:46.279> to 00:25:46.389 --> 00:25:46.399 align:start position:0% someone else ideally I would be able to 00:25:46.399 --> 00:25:48.710 align:start position:0% someone else ideally I would be able to change<00:25:46.799> my<00:25:47.000> private<00:25:47.360> key<00:25:47.799> in<00:25:47.960> the<00:25:48.080> reple<00:25:48.600> I 00:25:48.710 --> 00:25:48.720 align:start position:0% change my private key in the reple I 00:25:48.720 --> 00:25:50.230 align:start position:0% change my private key in the reple I can't<00:25:49.000> and<00:25:49.120> also<00:25:49.320> if<00:25:49.399> I<00:25:49.520> exit<00:25:49.760> the<00:25:49.840> reple<00:25:50.159> it 00:25:50.230 --> 00:25:50.240 align:start position:0% can't and also if I exit the reple it 00:25:50.240 --> 00:25:51.630 align:start position:0% can't and also if I exit the reple it deletes<00:25:50.520> all<00:25:50.640> my<00:25:50.799> pods<00:25:51.120> so<00:25:51.240> we're<00:25:51.360> in<00:25:51.480> this 00:25:51.630 --> 00:25:51.640 align:start position:0% deletes all my pods so we're in this 00:25:51.640 --> 00:25:53.549 align:start position:0% deletes all my pods so we're in this very<00:25:51.799> annoying<00:25:52.159> system<00:25:52.640> where<00:25:53.039> the<00:25:53.200> past<00:25:53.440> up 00:25:53.549 --> 00:25:53.559 align:start position:0% very annoying system where the past up 00:25:53.559 --> 00:25:54.750 align:start position:0% very annoying system where the past up is<00:25:53.640> going<00:25:53.720> to<00:25:53.840> be<00:25:53.960> signed<00:25:54.279> by<00:25:54.399> the<00:25:54.559> same 00:25:54.750 --> 00:25:54.760 align:start position:0% is going to be signed by the same 00:25:54.760 --> 00:25:55.990 align:start position:0% is going to be signed by the same Authority<00:25:55.200> but<00:25:55.320> could<00:25:55.440> be<00:25:55.520> signed<00:25:55.799> by<00:25:55.880> a 00:25:55.990 --> 00:25:56.000 align:start position:0% Authority but could be signed by a 00:25:56.000 --> 00:25:57.510 align:start position:0% Authority but could be signed by a different<00:25:56.240> one<00:25:56.640> doesn't<00:25:56.919> have<00:25:57.039> to<00:25:57.159> be<00:25:57.240> signed 00:25:57.510 --> 00:25:57.520 align:start position:0% different one doesn't have to be signed 00:25:57.520 --> 00:25:58.990 align:start position:0% different one doesn't have to be signed by<00:25:57.600> the<00:25:57.679> same<00:25:57.799> Pro<00:25:58.120> key 00:25:58.990 --> 00:25:59.000 align:start position:0% by the same Pro key 00:25:59.000 --> 00:26:03.310 align:start position:0% by the same Pro key so<00:25:59.279> I<00:25:59.360> have<00:25:59.480> a<00:25:59.720> salary<00:26:00.720> um<00:26:01.120> let's<00:26:01.279> say<00:26:01.960> 120,000 00:26:03.310 --> 00:26:03.320 align:start position:0% so I have a salary um let's say 120,000 00:26:03.320 --> 00:26:07.470 align:start position:0% so I have a salary um let's say 120,000 units<00:26:04.320> um<00:26:04.640> this<00:26:04.799> B<00:26:05.080> stop<00:26:05.279> is<00:26:05.399> linked<00:26:05.799> to<00:26:06.799> an<00:26:07.000> ID 00:26:07.470 --> 00:26:07.480 align:start position:0% units um this B stop is linked to an ID 00:26:07.480 --> 00:26:10.470 align:start position:0% units um this B stop is linked to an ID of<00:26:07.640> someone<00:26:07.960> using<00:26:08.640> any<00:26:08.799> kind<00:26:08.960> of<00:26:09.080> ID<00:26:09.480> system 00:26:10.470 --> 00:26:10.480 align:start position:0% of someone using any kind of ID system 00:26:10.480 --> 00:26:12.669 align:start position:0% of someone using any kind of ID system and<00:26:10.640> that's<00:26:10.840> it<00:26:11.440> so<00:26:11.640> now<00:26:11.760> I<00:26:11.840> have<00:26:11.960> another<00:26:12.240> pod 00:26:12.669 --> 00:26:12.679 align:start position:0% and that's it so now I have another pod 00:26:12.679 --> 00:26:14.310 align:start position:0% and that's it so now I have another pod same<00:26:13.000> same<00:26:13.240> deal<00:26:13.480> we<00:26:13.600> have<00:26:13.679> some<00:26:13.880> value<00:26:14.080> of 00:26:14.310 --> 00:26:14.320 align:start position:0% same same deal we have some value of 00:26:14.320 --> 00:26:17.549 align:start position:0% same same deal we have some value of statements<00:26:15.320> um<00:26:15.520> same<00:26:15.799> there's<00:26:16.000> a<00:26:16.120> signer<00:26:16.880> okay 00:26:17.549 --> 00:26:17.559 align:start position:0% statements um same there's a signer okay 00:26:17.559 --> 00:26:19.470 align:start position:0% statements um same there's a signer okay so<00:26:17.720> now<00:26:17.880> what<00:26:18.000> I<00:26:18.080> want<00:26:18.159> to<00:26:18.320> do<00:26:18.840> if<00:26:18.960> we<00:26:19.159> go<00:26:19.320> back 00:26:19.470 --> 00:26:19.480 align:start position:0% so now what I want to do if we go back 00:26:19.480 --> 00:26:22.350 align:start position:0% so now what I want to do if we go back to<00:26:19.720> this<00:26:20.240> computational<00:26:21.039> graph<00:26:21.880> um<00:26:22.080> let<00:26:22.200> me 00:26:22.350 --> 00:26:22.360 align:start position:0% to this computational graph um let me 00:26:22.360 --> 00:26:23.750 align:start position:0% to this computational graph um let me bring<00:26:22.559> it<00:26:22.679> up 00:26:23.750 --> 00:26:23.760 align:start position:0% bring it up 00:26:23.760 --> 00:26:26.789 align:start position:0% bring it up here<00:26:24.760> I<00:26:24.919> have<00:26:25.159> two<00:26:25.399> pods<00:26:26.080> let's<00:26:26.240> say<00:26:26.440> pod<00:26:26.640> red 00:26:26.789 --> 00:26:26.799 align:start position:0% here I have two pods let's say pod red 00:26:26.799 --> 00:26:29.310 align:start position:0% here I have two pods let's say pod red and<00:26:26.960> P<00:26:27.640> pod<00:26:27.880> green<00:26:28.440> which<00:26:28.559> are<00:26:28.840> pods<00:26:29.120> they<00:26:29.240> have 00:26:29.310 --> 00:26:29.320 align:start position:0% and P pod green which are pods they have 00:26:29.320 --> 00:26:32.230 align:start position:0% and P pod green which are pods they have been<00:26:29.480> issued<00:26:29.880> by<00:26:30.080> different<00:26:31.000> like<00:26:31.240> people<00:26:32.039> one 00:26:32.230 --> 00:26:32.240 align:start position:0% been issued by different like people one 00:26:32.240 --> 00:26:35.269 align:start position:0% been issued by different like people one is<00:26:32.440> my<00:26:32.640> ID<00:26:33.039> card<00:26:33.480> maybe<00:26:33.720> it<00:26:33.840> was<00:26:34.039> imported<00:26:34.640> from 00:26:35.269 --> 00:26:35.279 align:start position:0% is my ID card maybe it was imported from 00:26:35.279 --> 00:26:37.470 align:start position:0% is my ID card maybe it was imported from whatever<00:26:36.000> horrible<00:26:36.559> format<00:26:36.960> the<00:26:37.080> government 00:26:37.470 --> 00:26:37.480 align:start position:0% whatever horrible format the government 00:26:37.480 --> 00:26:39.430 align:start position:0% whatever horrible format the government uses<00:26:37.919> to<00:26:38.039> make<00:26:38.279> ID<00:26:38.760> ID<00:26:39.039> cards<00:26:39.279> be 00:26:39.430 --> 00:26:39.440 align:start position:0% uses to make ID ID cards be 00:26:39.440 --> 00:26:41.029 align:start position:0% uses to make ID ID cards be cryptographically<00:26:40.159> verified<00:26:40.720> and<00:26:40.840> then<00:26:40.960> the 00:26:41.029 --> 00:26:41.039 align:start position:0% cryptographically verified and then the 00:26:41.039 --> 00:26:42.750 align:start position:0% cryptographically verified and then the other<00:26:41.200> one<00:26:41.360> is<00:26:41.440> a<00:26:41.600> past<00:26:41.919> up<00:26:42.200> and<00:26:42.360> imagine 00:26:42.750 --> 00:26:42.760 align:start position:0% other one is a past up and imagine 00:26:42.760 --> 00:26:45.350 align:start position:0% other one is a past up and imagine that's<00:26:42.960> been<00:26:43.200> imported<00:26:43.720> using<00:26:44.720> uh<00:26:44.840> the<00:26:44.960> ZK 00:26:45.350 --> 00:26:45.360 align:start position:0% that's been imported using uh the ZK 00:26:45.360 --> 00:26:47.149 align:start position:0% that's been imported using uh the ZK email<00:26:45.720> system<00:26:46.080> that<00:26:46.240> aush<00:26:46.640> is<00:26:46.720> going<00:26:46.840> to<00:26:47.000> tell 00:26:47.149 --> 00:26:47.159 align:start position:0% email system that aush is going to tell 00:26:47.159 --> 00:26:49.549 align:start position:0% email system that aush is going to tell us<00:26:47.320> about<00:26:47.600> later<00:26:48.159> where<00:26:48.320> it<00:26:48.559> parsed<00:26:49.320> my 00:26:49.549 --> 00:26:49.559 align:start position:0% us about later where it parsed my 00:26:49.559 --> 00:26:52.510 align:start position:0% us about later where it parsed my pasteup<00:26:50.080> email<00:26:51.039> from<00:26:51.559> let's<00:26:51.720> say<00:26:51.880> like<00:26:52.080> Gusto 00:26:52.510 --> 00:26:52.520 align:start position:0% pasteup email from let's say like Gusto 00:26:52.520 --> 00:26:54.430 align:start position:0% pasteup email from let's say like Gusto or<00:26:52.640> your<00:26:52.799> payroll<00:26:53.240> system<00:26:53.919> now<00:26:54.080> I<00:26:54.159> have<00:26:54.320> these 00:26:54.430 --> 00:26:54.440 align:start position:0% or your payroll system now I have these 00:26:54.440 --> 00:26:55.830 align:start position:0% or your payroll system now I have these two<00:26:54.600> pods<00:26:54.840> I<00:26:54.919> want<00:26:55.000> to<00:26:55.080> make<00:26:55.200> a<00:26:55.279> new<00:26:55.480> part<00:26:55.720> out 00:26:55.830 --> 00:26:55.840 align:start position:0% two pods I want to make a new part out 00:26:55.840 --> 00:26:58.389 align:start position:0% two pods I want to make a new part out of<00:26:55.960> it<00:26:56.679> and<00:26:56.799> what<00:26:56.960> this<00:26:57.080> new<00:26:57.320> pod<00:26:57.640> is<00:26:57.799> is<00:26:58.000> just 00:26:58.389 --> 00:26:58.399 align:start position:0% of it and what this new pod is is just 00:26:58.399 --> 00:27:02.110 align:start position:0% of it and what this new pod is is just says<00:26:59.440> um<00:27:00.440> I<00:27:00.520> want<00:27:00.640> to<00:27:00.760> do<00:27:00.919> a<00:27:01.039> draw<00:27:01.480> on<00:27:01.640> all<00:27:01.760> of<00:27:01.919> my 00:27:02.110 --> 00:27:02.120 align:start position:0% says um I want to do a draw on all of my 00:27:02.120 --> 00:27:06.950 align:start position:0% says um I want to do a draw on all of my data<00:27:02.559> which<00:27:02.679> say<00:27:03.039> like<00:27:03.360> the<00:27:03.640> ID<00:27:04.640> my<00:27:05.039> my<00:27:05.200> ID<00:27:06.120> has 00:27:06.950 --> 00:27:06.960 align:start position:0% data which say like the ID my my ID has 00:27:06.960 --> 00:27:10.350 align:start position:0% data which say like the ID my my ID has this<00:27:07.200> much<00:27:07.880> annual<00:27:08.559> salary<00:27:09.559> with<00:27:09.840> this<00:27:10.080> ZIP 00:27:10.350 --> 00:27:10.360 align:start position:0% this much annual salary with this ZIP 00:27:10.360 --> 00:27:13.190 align:start position:0% this much annual salary with this ZIP code<00:27:11.279> right<00:27:11.640> let's<00:27:11.880> try<00:27:12.039> to<00:27:12.200> do<00:27:12.399> that<00:27:12.960> so<00:27:13.120> what 00:27:13.190 --> 00:27:13.200 align:start position:0% code right let's try to do that so what 00:27:13.200 --> 00:27:14.590 align:start position:0% code right let's try to do that so what I<00:27:13.279> need<00:27:13.399> to<00:27:13.520> do<00:27:13.640> is<00:27:13.720> I<00:27:13.799> need<00:27:13.919> to<00:27:14.039> take<00:27:14.200> two<00:27:14.360> pods 00:27:14.590 --> 00:27:14.600 align:start position:0% I need to do is I need to take two pods 00:27:14.600 --> 00:27:16.070 align:start position:0% I need to do is I need to take two pods and<00:27:14.679> need<00:27:14.880> put<00:27:15.000> them<00:27:15.120> into<00:27:15.320> one<00:27:15.559> pod<00:27:15.760> and<00:27:15.919> also 00:27:16.070 --> 00:27:16.080 align:start position:0% and need put them into one pod and also 00:27:16.080 --> 00:27:18.310 align:start position:0% and need put them into one pod and also need<00:27:16.240> to<00:27:16.399> create<00:27:16.720> some<00:27:17.200> logical<00:27:17.720> statements 00:27:18.310 --> 00:27:18.320 align:start position:0% need to create some logical statements 00:27:18.320 --> 00:27:19.909 align:start position:0% need to create some logical statements that<00:27:18.679> kind<00:27:18.799> of<00:27:18.919> like<00:27:19.039> makes<00:27:19.320> everything<00:27:19.600> fit 00:27:19.909 --> 00:27:19.919 align:start position:0% that kind of like makes everything fit 00:27:19.919 --> 00:27:21.350 align:start position:0% that kind of like makes everything fit together<00:27:20.240> and<00:27:20.480> it<00:27:20.559> will<00:27:20.760> make<00:27:20.919> more<00:27:21.080> sense<00:27:21.240> as 00:27:21.350 --> 00:27:21.360 align:start position:0% together and it will make more sense as 00:27:21.360 --> 00:27:23.549 align:start position:0% together and it will make more sense as I<00:27:21.480> read<00:27:21.679> it<00:27:22.279> so<00:27:22.399> we're<00:27:22.520> going<00:27:22.640> to<00:27:22.720> create<00:27:22.919> a<00:27:23.039> new 00:27:23.549 --> 00:27:23.559 align:start position:0% I read it so we're going to create a new 00:27:23.559 --> 00:27:26.350 align:start position:0% I read it so we're going to create a new pod<00:27:24.559> um<00:27:25.039> actually<00:27:25.279> let's<00:27:25.440> do<00:27:25.679> like<00:27:25.840> an<00:27:26.000> an<00:27:26.159> even 00:27:26.350 --> 00:27:26.360 align:start position:0% pod um actually let's do like an an even 00:27:26.360 --> 00:27:28.470 align:start position:0% pod um actually let's do like an an even more<00:27:26.559> interesting<00:27:27.080> example<00:27:27.559> which<00:27:27.679> is<00:27:28.320> not 00:27:28.470 --> 00:27:28.480 align:start position:0% more interesting example which is not 00:27:28.480 --> 00:27:29.830 align:start position:0% more interesting example which is not only<00:27:28.720> do<00:27:28.840> I<00:27:28.919> want<00:27:29.039> to<00:27:29.159> show<00:27:29.399> that<00:27:29.520> I<00:27:29.600> have<00:27:29.679> a 00:27:29.830 --> 00:27:29.840 align:start position:0% only do I want to show that I have a 00:27:29.840 --> 00:27:31.310 align:start position:0% only do I want to show that I have a specific<00:27:30.200> salary<00:27:30.679> I<00:27:30.760> actually<00:27:30.919> don't<00:27:31.080> want<00:27:31.159> to 00:27:31.310 --> 00:27:31.320 align:start position:0% specific salary I actually don't want to 00:27:31.320 --> 00:27:32.590 align:start position:0% specific salary I actually don't want to reveal<00:27:31.679> the<00:27:31.760> amount<00:27:31.960> of<00:27:32.080> salary<00:27:32.360> I<00:27:32.440> just<00:27:32.520> want 00:27:32.590 --> 00:27:32.600 align:start position:0% reveal the amount of salary I just want 00:27:32.600 --> 00:27:34.950 align:start position:0% reveal the amount of salary I just want to<00:27:32.720> show<00:27:32.840> it's<00:27:33.000> over<00:27:33.159> a<00:27:33.279> certain<00:27:33.600> amount<00:27:34.279> right 00:27:34.950 --> 00:27:34.960 align:start position:0% to show it's over a certain amount right 00:27:34.960 --> 00:27:38.630 align:start position:0% to show it's over a certain amount right so<00:27:35.200> we'll<00:27:35.440> do<00:27:35.880> salary<00:27:36.880> over<00:27:37.840> amount<00:27:38.520> that's 00:27:38.630 --> 00:27:38.640 align:start position:0% so we'll do salary over amount that's 00:27:38.640 --> 00:27:41.430 align:start position:0% so we'll do salary over amount that's the<00:27:38.760> name<00:27:38.919> of<00:27:39.039> our<00:27:39.480> pod<00:27:40.480> so<00:27:40.760> first<00:27:41.159> here<00:27:41.320> what 00:27:41.430 --> 00:27:41.440 align:start position:0% the name of our pod so first here what 00:27:41.440 --> 00:27:43.190 align:start position:0% the name of our pod so first here what we'll<00:27:41.600> do<00:27:41.760> is<00:27:41.880> we're<00:27:42.039> going<00:27:42.200> to<00:27:42.480> query<00:27:42.840> for 00:27:43.190 --> 00:27:43.200 align:start position:0% we'll do is we're going to query for 00:27:43.200 --> 00:27:45.909 align:start position:0% we'll do is we're going to query for pods<00:27:44.039> within<00:27:44.440> this<00:27:44.679> pod<00:27:45.559> and<00:27:45.679> the<00:27:45.799> thing 00:27:45.909 --> 00:27:45.919 align:start position:0% pods within this pod and the thing 00:27:45.919 --> 00:27:47.389 align:start position:0% pods within this pod and the thing that's<00:27:46.120> important<00:27:46.399> to<00:27:46.519> know<00:27:46.799> about<00:27:47.159> what<00:27:47.279> I'm 00:27:47.389 --> 00:27:47.399 align:start position:0% that's important to know about what I'm 00:27:47.399 --> 00:27:49.310 align:start position:0% that's important to know about what I'm going<00:27:47.559> to<00:27:47.720> do<00:27:47.960> is<00:27:48.120> that<00:27:48.279> the<00:27:48.399> quer<00:27:48.679> is 00:27:49.310 --> 00:27:49.320 align:start position:0% going to do is that the quer is 00:27:49.320 --> 00:27:51.870 align:start position:0% going to do is that the quer is approvable<00:27:50.320> so<00:27:50.519> the<00:27:50.640> way<00:27:50.799> I<00:27:50.960> express<00:27:51.399> my<00:27:51.600> query 00:27:51.870 --> 00:27:51.880 align:start position:0% approvable so the way I express my query 00:27:51.880 --> 00:27:54.470 align:start position:0% approvable so the way I express my query using<00:27:52.320> this<00:27:52.720> query<00:27:53.080> language<00:27:53.880> gets<00:27:54.120> turned 00:27:54.470 --> 00:27:54.480 align:start position:0% using this query language gets turned 00:27:54.480 --> 00:27:56.149 align:start position:0% using this query language gets turned into<00:27:54.720> a<00:27:54.880> bunch<00:27:55.080> of<00:27:55.240> stuff<00:27:55.480> within<00:27:55.720> the<00:27:55.840> logic 00:27:56.149 --> 00:27:56.159 align:start position:0% into a bunch of stuff within the logic 00:27:56.159 --> 00:27:57.669 align:start position:0% into a bunch of stuff within the logic VM<00:27:56.559> that<00:27:56.640> shows<00:27:56.960> I've<00:27:57.120> done<00:27:57.279> this<00:27:57.440> query 00:27:57.669 --> 00:27:57.679 align:start position:0% VM that shows I've done this query 00:27:57.679 --> 00:27:58.669 align:start position:0% VM that shows I've done this query correctly 00:27:58.669 --> 00:27:58.679 align:start position:0% correctly 00:27:58.679 --> 00:28:01.190 align:start position:0% correctly which<00:27:58.799> is<00:27:59.480> but<00:27:59.640> also<00:27:59.960> that<00:28:00.200> it<00:28:00.399> Imports<00:28:01.080> a 00:28:01.190 --> 00:28:01.200 align:start position:0% which is but also that it Imports a 00:28:01.200 --> 00:28:02.789 align:start position:0% which is but also that it Imports a bunch<00:28:01.399> of<00:28:01.559> statements<00:28:01.960> from<00:28:02.159> previous<00:28:02.480> part 00:28:02.789 --> 00:28:02.799 align:start position:0% bunch of statements from previous part 00:28:02.799 --> 00:28:04.430 align:start position:0% bunch of statements from previous part such<00:28:03.000> that<00:28:03.080> a<00:28:03.240> verifier<00:28:03.799> down<00:28:03.960> the<00:28:04.080> line<00:28:04.320> can 00:28:04.430 --> 00:28:04.440 align:start position:0% such that a verifier down the line can 00:28:04.440 --> 00:28:06.789 align:start position:0% such that a verifier down the line can be<00:28:04.600> like<00:28:04.880> okay<00:28:05.080> they<00:28:05.200> truly<00:28:05.519> imported<00:28:06.360> a<00:28:06.480> real 00:28:06.789 --> 00:28:06.799 align:start position:0% be like okay they truly imported a real 00:28:06.799 --> 00:28:08.070 align:start position:0% be like okay they truly imported a real ID<00:28:07.200> not<00:28:07.360> something<00:28:07.640> that<00:28:07.760> they're<00:28:07.960> like 00:28:08.070 --> 00:28:08.080 align:start position:0% ID not something that they're like 00:28:08.080 --> 00:28:09.630 align:start position:0% ID not something that they're like little<00:28:08.399> brother<00:28:08.720> signed<00:28:09.039> or<00:28:09.159> something<00:28:09.440> like 00:28:09.630 --> 00:28:09.640 align:start position:0% little brother signed or something like 00:28:09.640 --> 00:28:11.830 align:start position:0% little brother signed or something like that<00:28:10.440> so<00:28:10.919> um<00:28:11.080> on<00:28:11.200> top<00:28:11.360> of<00:28:11.440> that<00:28:11.559> we're<00:28:11.679> going<00:28:11.760> to 00:28:11.830 --> 00:28:11.840 align:start position:0% that so um on top of that we're going to 00:28:11.840 --> 00:28:13.230 align:start position:0% that so um on top of that we're going to use<00:28:11.960> a<00:28:12.080> new<00:28:12.240> piece<00:28:12.399> of<00:28:12.559> syntax<00:28:12.960> which<00:28:13.080> is 00:28:13.230 --> 00:28:13.240 align:start position:0% use a new piece of syntax which is 00:28:13.240 --> 00:28:15.350 align:start position:0% use a new piece of syntax which is defined<00:28:13.840> because<00:28:14.240> as<00:28:14.360> a<00:28:14.519> quer<00:28:14.760> a<00:28:15.000> pod<00:28:15.240> I'm 00:28:15.350 --> 00:28:15.360 align:start position:0% defined because as a quer a pod I'm 00:28:15.360 --> 00:28:17.389 align:start position:0% defined because as a quer a pod I'm going<00:28:15.440> to<00:28:15.600> get<00:28:15.880> bindings<00:28:16.600> to<00:28:16.840> values<00:28:17.120> in<00:28:17.240> the 00:28:17.389 --> 00:28:17.399 align:start position:0% going to get bindings to values in the 00:28:17.399 --> 00:28:19.029 align:start position:0% going to get bindings to values in the Pod<00:28:17.600> and<00:28:17.679> I<00:28:17.720> want<00:28:17.840> to<00:28:17.960> reuse<00:28:18.360> them<00:28:18.559> so<00:28:18.720> I<00:28:18.799> will 00:28:19.029 --> 00:28:19.039 align:start position:0% Pod and I want to reuse them so I will 00:28:19.039 --> 00:28:21.269 align:start position:0% Pod and I want to reuse them so I will bind<00:28:19.360> them<00:28:19.559> to<00:28:19.840> variables<00:28:20.480> because<00:28:21.000> you<00:28:21.200> you 00:28:21.269 --> 00:28:21.279 align:start position:0% bind them to variables because you you 00:28:21.279 --> 00:28:22.630 align:start position:0% bind them to variables because you you might<00:28:21.399> have<00:28:21.519> noticed<00:28:21.840> in<00:28:21.960> lists<00:28:22.279> there<00:28:22.360> are<00:28:22.440> no 00:28:22.630 --> 00:28:22.640 align:start position:0% might have noticed in lists there are no 00:28:22.640 --> 00:28:24.470 align:start position:0% might have noticed in lists there are no real<00:28:22.960> variables<00:28:23.519> by<00:28:23.679> default<00:28:24.080> you<00:28:24.240> just 00:28:24.470 --> 00:28:24.480 align:start position:0% real variables by default you just 00:28:24.480 --> 00:28:26.669 align:start position:0% real variables by default you just compute<00:28:25.200> so<00:28:25.440> here<00:28:25.840> we'll<00:28:26.000> need<00:28:26.200> some<00:28:26.480> some 00:28:26.669 --> 00:28:26.679 align:start position:0% compute so here we'll need some some 00:28:26.679 --> 00:28:27.990 align:start position:0% compute so here we'll need some some variable<00:28:27.120> like<00:28:27.320> stuff<00:28:27.600> otherwise<00:28:27.840> it's<00:28:27.919> going 00:28:27.990 --> 00:28:28.000 align:start position:0% variable like stuff otherwise it's going 00:28:28.000 --> 00:28:30.230 align:start position:0% variable like stuff otherwise it's going to<00:28:28.200> get<00:28:28.320> really<00:28:28.720> gnarly<00:28:29.720> so<00:28:29.880> first<00:28:30.080> we're 00:28:30.230 --> 00:28:30.240 align:start position:0% to get really gnarly so first we're 00:28:30.240 --> 00:28:32.950 align:start position:0% to get really gnarly so first we're going<00:28:30.399> to<00:28:30.799> query<00:28:31.120> for<00:28:31.399> things<00:28:31.720> in<00:28:31.880> my<00:28:32.120> ID<00:28:32.519> card 00:28:32.950 --> 00:28:32.960 align:start position:0% going to query for things in my ID card 00:28:32.960 --> 00:28:37.950 align:start position:0% going to query for things in my ID card pod<00:28:33.960> so<00:28:34.120> we'll<00:28:34.399> say<00:28:34.919> okay<00:28:35.120> so<00:28:35.640> ID<00:28:35.960> card<00:28:36.279> ID<00:28:37.200> H 00:28:37.950 --> 00:28:37.960 align:start position:0% pod so we'll say okay so ID card ID H 00:28:37.960 --> 00:28:39.669 align:start position:0% pod so we'll say okay so ID card ID H zip<00:28:38.279> code<00:28:38.799> these<00:28:38.919> are<00:28:39.039> the<00:28:39.159> names<00:28:39.399> of<00:28:39.519> the 00:28:39.669 --> 00:28:39.679 align:start position:0% zip code these are the names of the 00:28:39.679 --> 00:28:41.669 align:start position:0% zip code these are the names of the variables<00:28:40.159> I<00:28:40.279> want<00:28:40.399> to<00:28:40.600> bind<00:28:41.039> the<00:28:41.159> outcome<00:28:41.559> of 00:28:41.669 --> 00:28:41.679 align:start position:0% variables I want to bind the outcome of 00:28:41.679 --> 00:28:43.710 align:start position:0% variables I want to bind the outcome of my<00:28:41.840> PO<00:28:42.080> query<00:28:42.360> to<00:28:43.000> and<00:28:43.080> we'll<00:28:43.279> use<00:28:43.519> this 00:28:43.710 --> 00:28:43.720 align:start position:0% my PO query to and we'll use this 00:28:43.720 --> 00:28:45.710 align:start position:0% my PO query to and we'll use this statement<00:28:44.159> called<00:28:44.360> pot<00:28:44.600> question<00:28:44.880> mark<00:28:45.640> and 00:28:45.710 --> 00:28:45.720 align:start position:0% statement called pot question mark and 00:28:45.720 --> 00:28:48.350 align:start position:0% statement called pot question mark and so<00:28:46.039> what<00:28:46.200> follows<00:28:46.679> pot<00:28:46.919> question<00:28:47.159> mark<00:28:47.559> is<00:28:47.799> a 00:28:48.350 --> 00:28:48.360 align:start position:0% so what follows pot question mark is a 00:28:48.360 --> 00:28:51.310 align:start position:0% so what follows pot question mark is a it's<00:28:48.480> a<00:28:48.640> query<00:28:49.360> language<00:28:50.360> so<00:28:50.919> what<00:28:51.039> we'll<00:28:51.200> do 00:28:51.310 --> 00:28:51.320 align:start position:0% it's a query language so what we'll do 00:28:51.320 --> 00:28:52.590 align:start position:0% it's a query language so what we'll do here<00:28:51.440> with<00:28:51.559> the<00:28:51.679> query<00:28:51.880> language<00:28:52.240> is<00:28:52.399> we're 00:28:52.590 --> 00:28:52.600 align:start position:0% here with the query language is we're 00:28:52.600 --> 00:28:54.590 align:start position:0% here with the query language is we're going<00:28:52.679> to<00:28:52.840> be<00:28:53.640> very<00:28:53.919> open<00:28:54.240> we're<00:28:54.399> just<00:28:54.519> going 00:28:54.590 --> 00:28:54.600 align:start position:0% going to be very open we're just going 00:28:54.600 --> 00:28:57.149 align:start position:0% going to be very open we're just going to<00:28:54.679> say<00:28:54.880> hey<00:28:55.000> I<00:28:55.080> want<00:28:55.159> a<00:28:55.320> pod<00:28:55.519> that<00:28:55.679> as<00:28:55.799> an<00:28:56.159> ID 00:28:57.149 --> 00:28:57.159 align:start position:0% to say hey I want a pod that as an ID 00:28:57.159 --> 00:28:58.549 align:start position:0% to say hey I want a pod that as an ID that<00:28:57.360> as<00:28:57.480> an<00:28:57.640> age 00:28:58.549 --> 00:28:58.559 align:start position:0% that as an age 00:28:58.559 --> 00:29:00.430 align:start position:0% that as an age that<00:28:58.679> is<00:28:58.840> a<00:28:58.960> zip 00:29:00.430 --> 00:29:00.440 align:start position:0% that is a zip 00:29:00.440 --> 00:29:03.470 align:start position:0% that is a zip code<00:29:01.440> and<00:29:01.760> whose<00:29:02.039> signer<00:29:02.760> is<00:29:02.919> equal<00:29:03.159> to<00:29:03.279> a 00:29:03.470 --> 00:29:03.480 align:start position:0% code and whose signer is equal to a 00:29:03.480 --> 00:29:05.149 align:start position:0% code and whose signer is equal to a specific 00:29:05.149 --> 00:29:05.159 align:start position:0% specific 00:29:05.159 --> 00:29:07.750 align:start position:0% specific value<00:29:06.159> okay<00:29:06.760> so<00:29:06.960> what<00:29:07.080> I'm<00:29:07.200> doing<00:29:07.480> here<00:29:07.600> is 00:29:07.750 --> 00:29:07.760 align:start position:0% value okay so what I'm doing here is 00:29:07.760 --> 00:29:09.470 align:start position:0% value okay so what I'm doing here is what<00:29:07.880> this<00:29:08.000> query<00:29:08.360> does<00:29:08.559> is<00:29:08.880> it<00:29:09.000> asks<00:29:09.240> for<00:29:09.360> a 00:29:09.470 --> 00:29:09.480 align:start position:0% what this query does is it asks for a 00:29:09.480 --> 00:29:11.430 align:start position:0% what this query does is it asks for a pod<00:29:09.760> with<00:29:09.919> these<00:29:10.159> three<00:29:10.720> things<00:29:11.039> and<00:29:11.159> also<00:29:11.320> it 00:29:11.430 --> 00:29:11.440 align:start position:0% pod with these three things and also it 00:29:11.440 --> 00:29:13.830 align:start position:0% pod with these three things and also it adds<00:29:11.640> a<00:29:11.720> constraint<00:29:12.120> for<00:29:12.240> the<00:29:12.640> signer<00:29:13.640> this 00:29:13.830 --> 00:29:13.840 align:start position:0% adds a constraint for the signer this 00:29:13.840 --> 00:29:15.590 align:start position:0% adds a constraint for the signer this constraint<00:29:14.320> currently<00:29:14.679> it's<00:29:14.760> a<00:29:14.960> PL<00:29:15.320> text 00:29:15.590 --> 00:29:15.600 align:start position:0% constraint currently it's a PL text 00:29:15.600 --> 00:29:17.470 align:start position:0% constraint currently it's a PL text constraint<00:29:16.399> so<00:29:16.559> what<00:29:16.640> this<00:29:16.799> means<00:29:17.120> it's<00:29:17.279> not 00:29:17.470 --> 00:29:17.480 align:start position:0% constraint so what this means it's not 00:29:17.480 --> 00:29:18.990 align:start position:0% constraint so what this means it's not actually<00:29:17.760> verified<00:29:18.320> I'll<00:29:18.519> have<00:29:18.640> to<00:29:18.799> do 00:29:18.990 --> 00:29:19.000 align:start position:0% actually verified I'll have to do 00:29:19.000 --> 00:29:21.029 align:start position:0% actually verified I'll have to do something<00:29:19.320> with<00:29:19.480> the<00:29:19.679> signer<00:29:20.000> later<00:29:20.760> such 00:29:21.029 --> 00:29:21.039 align:start position:0% something with the signer later such 00:29:21.039 --> 00:29:23.070 align:start position:0% something with the signer later such that<00:29:21.360> like<00:29:21.960> this<00:29:22.360> this<00:29:22.519> query<00:29:22.799> cannot 00:29:23.070 --> 00:29:23.080 align:start position:0% that like this this query cannot 00:29:23.080 --> 00:29:25.070 align:start position:0% that like this this query cannot actually<00:29:23.320> be<00:29:23.440> cheated<00:29:23.960> later<00:29:24.480> so<00:29:24.760> we'll<00:29:24.919> we'll 00:29:25.070 --> 00:29:25.080 align:start position:0% actually be cheated later so we'll we'll 00:29:25.080 --> 00:29:28.350 align:start position:0% actually be cheated later so we'll we'll get<00:29:25.159> a<00:29:25.279> binder<00:29:25.640> to<00:29:25.799> this<00:29:26.000> as<00:29:26.159> well<00:29:26.960> ID<00:29:27.440> signer 00:29:28.350 --> 00:29:28.360 align:start position:0% get a binder to this as well ID signer 00:29:28.360 --> 00:29:29.710 align:start position:0% get a binder to this as well ID signer let's<00:29:28.559> do<00:29:28.720> it<00:29:28.880> this 00:29:29.710 --> 00:29:29.720 align:start position:0% let's do it this 00:29:29.720 --> 00:29:31.909 align:start position:0% let's do it this way 00:29:31.909 --> 00:29:31.919 align:start position:0% way 00:29:31.919 --> 00:29:34.549 align:start position:0% way okay<00:29:32.919> um<00:29:33.279> one<00:29:33.399> thing<00:29:33.559> you<00:29:33.640> might<00:29:33.799> notice<00:29:34.120> is<00:29:34.360> I 00:29:34.549 --> 00:29:34.559 align:start position:0% okay um one thing you might notice is I 00:29:34.559 --> 00:29:38.110 align:start position:0% okay um one thing you might notice is I cannot<00:29:35.279> explicitly<00:29:36.279> pass<00:29:36.840> pods<00:29:37.360> into<00:29:37.760> other 00:29:38.110 --> 00:29:38.120 align:start position:0% cannot explicitly pass pods into other 00:29:38.120 --> 00:29:40.389 align:start position:0% cannot explicitly pass pods into other pods<00:29:38.480> I<00:29:38.600> can<00:29:38.720> only<00:29:38.960> query<00:29:39.240> for<00:29:39.480> pods<00:29:40.159> the 00:29:40.389 --> 00:29:40.399 align:start position:0% pods I can only query for pods the 00:29:40.399 --> 00:29:42.310 align:start position:0% pods I can only query for pods the reason<00:29:41.039> we've<00:29:41.240> made<00:29:41.440> this<00:29:41.600> decision<00:29:41.919> to<00:29:42.080> only 00:29:42.310 --> 00:29:42.320 align:start position:0% reason we've made this decision to only 00:29:42.320 --> 00:29:44.389 align:start position:0% reason we've made this decision to only allowing<00:29:42.679> for<00:29:42.880> pods<00:29:43.120> to<00:29:43.240> be<00:29:43.360> queried<00:29:44.200> is 00:29:44.389 --> 00:29:44.399 align:start position:0% allowing for pods to be queried is 00:29:44.399 --> 00:29:46.950 align:start position:0% allowing for pods to be queried is because<00:29:44.720> if<00:29:45.080> you<00:29:45.240> query<00:29:45.519> for<00:29:45.679> a<00:29:45.840> pod<00:29:46.440> the<00:29:46.600> query 00:29:46.950 --> 00:29:46.960 align:start position:0% because if you query for a pod the query 00:29:46.960 --> 00:29:48.630 align:start position:0% because if you query for a pod the query should<00:29:47.200> include<00:29:47.760> everything<00:29:48.320> that's 00:29:48.630 --> 00:29:48.640 align:start position:0% should include everything that's 00:29:48.640 --> 00:29:51.549 align:start position:0% should include everything that's necessary<00:29:49.279> for<00:29:49.519> this<00:29:49.799> pod<00:29:50.240> to<00:29:50.440> be<00:29:51.200> then<00:29:51.440> like 00:29:51.549 --> 00:29:51.559 align:start position:0% necessary for this pod to be then like 00:29:51.559 --> 00:29:54.190 align:start position:0% necessary for this pod to be then like used<00:29:51.799> as<00:29:51.919> a<00:29:52.080> legitimate<00:29:52.679> entry<00:29:53.240> so<00:29:53.480> if<00:29:53.559> a<00:29:53.720> query 00:29:54.190 --> 00:29:54.200 align:start position:0% used as a legitimate entry so if a query 00:29:54.200 --> 00:29:56.029 align:start position:0% used as a legitimate entry so if a query were<00:29:54.320> to<00:29:54.559> return<00:29:54.799> multiple<00:29:55.200> pods<00:29:55.720> they<00:29:55.840> should 00:29:56.029 --> 00:29:56.039 align:start position:0% were to return multiple pods they should 00:29:56.039 --> 00:29:56.750 align:start position:0% were to return multiple pods they should be 00:29:56.750 --> 00:29:56.760 align:start position:0% be 00:29:56.760 --> 00:29:58.509 align:start position:0% be equivalent<00:29:57.760> because<00:29:58.080> if<00:29:58.200> they're<00:29:58.360> not 00:29:58.509 --> 00:29:58.519 align:start position:0% equivalent because if they're not 00:29:58.519 --> 00:29:59.789 align:start position:0% equivalent because if they're not equivalent<00:29:58.960> from<00:29:59.120> the<00:29:59.240> perspective<00:29:59.559> of<00:29:59.679> the 00:29:59.789 --> 00:29:59.799 align:start position:0% equivalent from the perspective of the 00:29:59.799 --> 00:30:01.389 align:start position:0% equivalent from the perspective of the verifier<00:30:00.399> that<00:30:00.559> that<00:30:00.679> means<00:30:00.840> your<00:30:00.960> query<00:30:01.240> is 00:30:01.389 --> 00:30:01.399 align:start position:0% verifier that that means your query is 00:30:01.399 --> 00:30:04.389 align:start position:0% verifier that that means your query is not<00:30:02.039> like<00:30:02.279> tight<00:30:02.679> enough<00:30:03.679> uh<00:30:03.960> this<00:30:04.080> is<00:30:04.200> an 00:30:04.389 --> 00:30:04.399 align:start position:0% not like tight enough uh this is an 00:30:04.399 --> 00:30:06.509 align:start position:0% not like tight enough uh this is an aspirational<00:30:05.000> goal<00:30:05.720> maybe<00:30:06.080> we'll<00:30:06.279> have<00:30:06.399> to 00:30:06.509 --> 00:30:06.519 align:start position:0% aspirational goal maybe we'll have to 00:30:06.519 --> 00:30:08.549 align:start position:0% aspirational goal maybe we'll have to change<00:30:06.880> that<00:30:07.679> uh<00:30:07.799> but<00:30:07.919> for<00:30:08.039> now<00:30:08.200> this<00:30:08.320> is<00:30:08.399> how 00:30:08.549 --> 00:30:08.559 align:start position:0% change that uh but for now this is how 00:30:08.559 --> 00:30:10.950 align:start position:0% change that uh but for now this is how it<00:30:08.640> works<00:30:09.080> so<00:30:09.200> we'll<00:30:09.360> do<00:30:09.519> another<00:30:09.799> defined<00:30:10.640> um 00:30:10.950 --> 00:30:10.960 align:start position:0% it works so we'll do another defined um 00:30:10.960 --> 00:30:12.230 align:start position:0% it works so we'll do another defined um where<00:30:11.080> we're<00:30:11.240> going<00:30:11.360> to<00:30:11.480> get<00:30:11.640> binding<00:30:11.919> store 00:30:12.230 --> 00:30:12.240 align:start position:0% where we're going to get binding store 00:30:12.240 --> 00:30:15.470 align:start position:0% where we're going to get binding store pay<00:30:12.519> stubs<00:30:13.279> so<00:30:13.480> we'll<00:30:13.720> have<00:30:14.000> salary<00:30:14.720> salary 00:30:15.470 --> 00:30:15.480 align:start position:0% pay stubs so we'll have salary salary 00:30:15.480 --> 00:30:17.750 align:start position:0% pay stubs so we'll have salary salary and<00:30:15.679> then<00:30:15.919> past<00:30:16.240> up 00:30:17.750 --> 00:30:17.760 align:start position:0% and then past up 00:30:17.760 --> 00:30:21.750 align:start position:0% and then past up ID<00:30:18.760> same<00:30:19.080> deal<00:30:19.679> here 00:30:21.750 --> 00:30:21.760 align:start position:0% ID same deal here 00:30:21.760 --> 00:30:28.830 align:start position:0% ID same deal here salary<00:30:22.799> ID<00:30:23.799> and<00:30:23.919> then<00:30:24.320> I<00:30:24.600> also<00:30:24.880> need 00:30:28.830 --> 00:30:28.840 align:start position:0% 00:30:28.840 --> 00:30:30.669 align:start position:0% also<00:30:29.159> if<00:30:29.320> anything<00:30:29.720> doesn't<00:30:30.039> make<00:30:30.240> sense<00:30:30.480> feel 00:30:30.669 --> 00:30:30.679 align:start position:0% also if anything doesn't make sense feel 00:30:30.679 --> 00:30:32.070 align:start position:0% also if anything doesn't make sense feel free<00:30:30.880> to<00:30:31.000> interrupt<00:30:31.440> me<00:30:31.600> and<00:30:31.760> ask<00:30:31.880> me 00:30:32.070 --> 00:30:32.080 align:start position:0% free to interrupt me and ask me 00:30:32.080 --> 00:30:33.630 align:start position:0% free to interrupt me and ask me questions<00:30:32.480> because<00:30:32.640> it's<00:30:32.799> only<00:30:33.080> going<00:30:33.200> to<00:30:33.399> get 00:30:33.630 --> 00:30:33.640 align:start position:0% questions because it's only going to get 00:30:33.640 --> 00:30:37.950 align:start position:0% questions because it's only going to get crazier<00:30:34.240> from<00:30:34.880> here<00:30:35.880> uh<00:30:36.600> cool<00:30:37.240> okay<00:30:37.440> so<00:30:37.640> now<00:30:37.799> I 00:30:37.950 --> 00:30:37.960 align:start position:0% crazier from here uh cool okay so now I 00:30:37.960 --> 00:30:40.470 align:start position:0% crazier from here uh cool okay so now I have<00:30:38.240> all<00:30:38.399> of<00:30:38.559> these<00:30:38.720> little<00:30:39.039> variables<00:30:39.720> right 00:30:40.470 --> 00:30:40.480 align:start position:0% have all of these little variables right 00:30:40.480 --> 00:30:42.590 align:start position:0% have all of these little variables right if<00:30:40.600> the<00:30:40.720> query<00:30:41.000> succeed<00:30:41.440> that<00:30:41.600> is<00:30:42.320> what<00:30:42.440> am<00:30:42.519> I 00:30:42.590 --> 00:30:42.600 align:start position:0% if the query succeed that is what am I 00:30:42.600 --> 00:30:43.990 align:start position:0% if the query succeed that is what am I going<00:30:42.760> to<00:30:42.880> do<00:30:43.039> with<00:30:43.200> these<00:30:43.399> things<00:30:43.679> well<00:30:43.840> the 00:30:43.990 --> 00:30:44.000 align:start position:0% going to do with these things well the 00:30:44.000 --> 00:30:46.950 align:start position:0% going to do with these things well the first<00:30:44.240> thing<00:30:44.640> is<00:30:45.200> um<00:30:46.200> I<00:30:46.279> want<00:30:46.519> things<00:30:46.679> to<00:30:46.799> be 00:30:46.950 --> 00:30:46.960 align:start position:0% first thing is um I want things to be 00:30:46.960 --> 00:30:48.990 align:start position:0% first thing is um I want things to be revealed<00:30:47.360> in<00:30:47.519> this<00:30:47.720> part<00:30:48.159> right<00:30:48.640> what<00:30:48.760> I'll 00:30:48.990 --> 00:30:49.000 align:start position:0% revealed in this part right what I'll 00:30:49.000 --> 00:30:50.669 align:start position:0% revealed in this part right what I'll asample<00:30:49.440> what<00:30:49.519> I<00:30:49.640> revealed<00:30:50.000> is<00:30:50.080> I<00:30:50.240> reveal<00:30:50.559> my 00:30:50.669 --> 00:30:50.679 align:start position:0% asample what I revealed is I reveal my 00:30:50.679 --> 00:30:53.590 align:start position:0% asample what I revealed is I reveal my ZIP<00:30:50.919> code<00:30:51.480> so<00:30:51.640> I'll<00:30:51.799> say<00:30:52.720> zip<00:30:53.039> code<00:30:53.320> remember 00:30:53.590 --> 00:30:53.600 align:start position:0% ZIP code so I'll say zip code remember 00:30:53.600 --> 00:30:56.549 align:start position:0% ZIP code so I'll say zip code remember the<00:30:53.760> syntax<00:30:54.200> is<00:30:54.640> key<00:30:55.039> value<00:30:55.559> key<00:30:55.880> value<00:30:56.279> key 00:30:56.549 --> 00:30:56.559 align:start position:0% the syntax is key value key value key 00:30:56.559 --> 00:30:58.950 align:start position:0% the syntax is key value key value key value<00:30:57.000> so<00:30:57.159> I<00:30:57.320> say<00:30:57.679> there<00:30:58.000> will<00:30:58.120> be<00:30:58.279> a<00:30:58.679> a<00:30:58.799> key 00:30:58.950 --> 00:30:58.960 align:start position:0% value so I say there will be a a key 00:30:58.960 --> 00:31:00.909 align:start position:0% value so I say there will be a a key called<00:30:59.200> zip<00:30:59.440> code<00:30:59.960> and<00:31:00.159> the<00:31:00.279> value<00:31:00.559> will<00:31:00.720> be 00:31:00.909 --> 00:31:00.919 align:start position:0% called zip code and the value will be 00:31:00.919 --> 00:31:04.190 align:start position:0% called zip code and the value will be zip<00:31:01.200> code<00:31:01.760> which<00:31:01.919> I<00:31:02.120> got<00:31:02.840> from<00:31:03.559> this<00:31:03.760> spot<00:31:04.039> I'm 00:31:04.190 --> 00:31:04.200 align:start position:0% zip code which I got from this spot I'm 00:31:04.200 --> 00:31:05.590 align:start position:0% zip code which I got from this spot I'm querying 00:31:05.590 --> 00:31:05.600 align:start position:0% querying 00:31:05.600 --> 00:31:08.110 align:start position:0% querying here<00:31:06.600> um<00:31:07.320> and<00:31:07.399> then<00:31:07.600> that's<00:31:07.760> the<00:31:07.840> only<00:31:08.000> thing 00:31:08.110 --> 00:31:08.120 align:start position:0% here um and then that's the only thing 00:31:08.120 --> 00:31:09.230 align:start position:0% here um and then that's the only thing I'm<00:31:08.200> going<00:31:08.320> to<00:31:08.440> reveal<00:31:08.679> in<00:31:08.799> the<00:31:08.880> clear 00:31:09.230 --> 00:31:09.240 align:start position:0% I'm going to reveal in the clear 00:31:09.240 --> 00:31:11.430 align:start position:0% I'm going to reveal in the clear everything<00:31:09.519> else<00:31:09.679> I'm<00:31:09.799> going<00:31:09.919> to<00:31:10.080> reveal<00:31:10.600> are 00:31:11.430 --> 00:31:11.440 align:start position:0% everything else I'm going to reveal are 00:31:11.440 --> 00:31:13.070 align:start position:0% everything else I'm going to reveal are specific<00:31:11.919> constraints<00:31:12.519> that<00:31:12.639> are<00:31:12.760> applied 00:31:13.070 --> 00:31:13.080 align:start position:0% specific constraints that are applied 00:31:13.080 --> 00:31:14.389 align:start position:0% specific constraints that are applied between<00:31:13.360> these<00:31:13.559> B<00:31:13.799> so<00:31:13.960> the<00:31:14.039> first<00:31:14.200> thing<00:31:14.320> I'm 00:31:14.389 --> 00:31:14.399 align:start position:0% between these B so the first thing I'm 00:31:14.399 --> 00:31:16.789 align:start position:0% between these B so the first thing I'm going<00:31:14.480> to<00:31:14.559> constr<00:31:14.919> is<00:31:15.039> I'm<00:31:15.120> going<00:31:15.200> to<00:31:15.440> say<00:31:16.440> ID 00:31:16.789 --> 00:31:16.799 align:start position:0% going to constr is I'm going to say ID 00:31:16.799 --> 00:31:17.629 align:start position:0% going to constr is I'm going to say ID card 00:31:17.629 --> 00:31:17.639 align:start position:0% card 00:31:17.639 --> 00:31:21.350 align:start position:0% card ID<00:31:18.720> equals<00:31:19.720> BB<00:31:20.200> ID<00:31:20.679> right<00:31:20.840> because<00:31:21.039> otherwise 00:31:21.350 --> 00:31:21.360 align:start position:0% ID equals BB ID right because otherwise 00:31:21.360 --> 00:31:22.430 align:start position:0% ID equals BB ID right because otherwise that<00:31:21.440> means<00:31:21.600> I'm<00:31:21.720> using<00:31:22.039> either<00:31:22.240> someone 00:31:22.430 --> 00:31:22.440 align:start position:0% that means I'm using either someone 00:31:22.440 --> 00:31:26.190 align:start position:0% that means I'm using either someone else's<00:31:22.720> PB<00:31:23.159> or<00:31:23.279> someone<00:31:23.480> else's<00:31:23.880> ID<00:31:24.279> card<00:31:25.279> um 00:31:26.190 --> 00:31:26.200 align:start position:0% else's PB or someone else's ID card um 00:31:26.200 --> 00:31:27.549 align:start position:0% else's PB or someone else's ID card um then<00:31:26.399> I'm<00:31:26.559> going<00:31:26.679> to<00:31:26.760> make<00:31:26.880> a<00:31:27.000> claim<00:31:27.320> that<00:31:27.440> my 00:31:27.549 --> 00:31:27.559 align:start position:0% then I'm going to make a claim that my 00:31:27.559 --> 00:31:31.470 align:start position:0% then I'm going to make a claim that my salary<00:31:28.360> is<00:31:28.519> over<00:31:29.080> 100,000 00:31:31.470 --> 00:31:31.480 align:start position:0% salary is over 100,000 00:31:31.480 --> 00:31:33.990 align:start position:0% salary is over 100,000 units<00:31:32.480> um<00:31:32.880> another<00:31:33.120> thing<00:31:33.279> I'll<00:31:33.440> do<00:31:33.600> is<00:31:33.760> I'm 00:31:33.990 --> 00:31:34.000 align:start position:0% units um another thing I'll do is I'm 00:31:34.000 --> 00:31:36.870 align:start position:0% units um another thing I'll do is I'm going<00:31:34.080> to<00:31:34.279> claim<00:31:34.720> that<00:31:35.120> the<00:31:35.679> ID<00:31:36.360> so<00:31:36.600> okay<00:31:36.760> what 00:31:36.870 --> 00:31:36.880 align:start position:0% going to claim that the ID so okay what 00:31:36.880 --> 00:31:38.470 align:start position:0% going to claim that the ID so okay what I<00:31:36.960> want<00:31:37.039> to<00:31:37.159> do<00:31:37.360> here<00:31:37.480> is<00:31:37.600> I<00:31:37.679> want<00:31:37.799> to<00:31:38.000> reveal<00:31:38.399> I 00:31:38.470 --> 00:31:38.480 align:start position:0% I want to do here is I want to reveal I 00:31:38.480 --> 00:31:39.830 align:start position:0% I want to do here is I want to reveal I want<00:31:38.559> to<00:31:38.679> show<00:31:39.000> that<00:31:39.120> the<00:31:39.240> pods<00:31:39.559> I've<00:31:39.720> been 00:31:39.830 --> 00:31:39.840 align:start position:0% want to show that the pods I've been 00:31:39.840 --> 00:31:41.590 align:start position:0% want to show that the pods I've been using<00:31:40.279> are<00:31:40.480> using<00:31:40.799> are<00:31:40.919> from<00:31:41.080> a<00:31:41.240> specific 00:31:41.590 --> 00:31:41.600 align:start position:0% using are using are from a specific 00:31:41.600 --> 00:31:43.870 align:start position:0% using are using are from a specific signer<00:31:42.480> not<00:31:42.679> from<00:31:42.919> like<00:31:43.080> my<00:31:43.240> little<00:31:43.519> brother 00:31:43.870 --> 00:31:43.880 align:start position:0% signer not from like my little brother 00:31:43.880 --> 00:31:45.230 align:start position:0% signer not from like my little brother or<00:31:44.039> something<00:31:44.559> there<00:31:44.639> are<00:31:44.760> two<00:31:44.919> ways<00:31:45.039> for<00:31:45.159> me 00:31:45.230 --> 00:31:45.240 align:start position:0% or something there are two ways for me 00:31:45.240 --> 00:31:47.269 align:start position:0% or something there are two ways for me to<00:31:45.399> do<00:31:45.559> this<00:31:46.080> one<00:31:46.279> way<00:31:46.399> is<00:31:46.480> I<00:31:46.679> reveal<00:31:47.080> both 00:31:47.269 --> 00:31:47.279 align:start position:0% to do this one way is I reveal both 00:31:47.279 --> 00:31:49.149 align:start position:0% to do this one way is I reveal both signers<00:31:48.200> another<00:31:48.440> way<00:31:48.559> to<00:31:48.639> do<00:31:48.799> this<00:31:48.880> is<00:31:49.000> I 00:31:49.149 --> 00:31:49.159 align:start position:0% signers another way to do this is I 00:31:49.159 --> 00:31:50.590 align:start position:0% signers another way to do this is I reveal<00:31:49.480> one<00:31:49.639> signer<00:31:49.960> and<00:31:50.080> I<00:31:50.159> show<00:31:50.360> that<00:31:50.480> it's 00:31:50.590 --> 00:31:50.600 align:start position:0% reveal one signer and I show that it's 00:31:50.600 --> 00:31:52.230 align:start position:0% reveal one signer and I show that it's equal<00:31:50.840> to<00:31:50.960> the<00:31:51.039> other<00:31:51.240> signer<00:31:51.880> which<00:31:52.039> is 00:31:52.230 --> 00:31:52.240 align:start position:0% equal to the other signer which is 00:31:52.240 --> 00:31:53.870 align:start position:0% equal to the other signer which is equivalent<00:31:52.960> right<00:31:53.159> so<00:31:53.320> we'll<00:31:53.480> we'll<00:31:53.639> do<00:31:53.760> the 00:31:53.870 --> 00:31:53.880 align:start position:0% equivalent right so we'll we'll do the 00:31:53.880 --> 00:31:55.590 align:start position:0% equivalent right so we'll we'll do the second<00:31:54.120> way<00:31:54.279> because<00:31:54.399> it's<00:31:54.559> more<00:31:54.720> fun<00:31:55.279> so<00:31:55.399> we's 00:31:55.590 --> 00:31:55.600 align:start position:0% second way because it's more fun so we's 00:31:55.600 --> 00:31:58.470 align:start position:0% second way because it's more fun so we's say<00:31:55.799> ID<00:31:56.519> signer<00:31:57.519> equal 00:31:58.470 --> 00:31:58.480 align:start position:0% say ID signer equal 00:31:58.480 --> 00:31:59.629 align:start position:0% say ID signer equal Bop 00:31:59.629 --> 00:31:59.639 align:start position:0% Bop 00:31:59.639 --> 00:32:03.230 align:start position:0% Bop signer<00:32:00.639> and<00:32:00.760> on<00:32:00.919> top<00:32:01.039> of<00:32:01.200> that<00:32:01.360> we<00:32:01.480> will<00:32:02.240> reveal 00:32:03.230 --> 00:32:03.240 align:start position:0% signer and on top of that we will reveal 00:32:03.240 --> 00:32:08.710 align:start position:0% signer and on top of that we will reveal um<00:32:03.559> the<00:32:03.720> signer<00:32:04.639> which<00:32:04.799> is<00:32:05.240> the 00:32:08.710 --> 00:32:08.720 align:start position:0% 00:32:08.720 --> 00:32:12.350 align:start position:0% signer<00:32:09.760> okay<00:32:10.760> so<00:32:11.279> are<00:32:11.440> we<00:32:11.600> using<00:32:12.000> everything 00:32:12.350 --> 00:32:12.360 align:start position:0% signer okay so are we using everything 00:32:12.360 --> 00:32:15.950 align:start position:0% signer okay so are we using everything we<00:32:12.519> got<00:32:12.880> here<00:32:13.159> so<00:32:13.360> we're<00:32:13.600> using<00:32:14.600> ID<00:32:14.960> card<00:32:15.200> ID<00:32:15.799> oh 00:32:15.950 --> 00:32:15.960 align:start position:0% we got here so we're using ID card ID oh 00:32:15.960 --> 00:32:18.549 align:start position:0% we got here so we're using ID card ID oh and<00:32:16.159> H<00:32:16.480> what<00:32:16.559> should<00:32:16.720> we<00:32:16.799> do<00:32:16.919> with 00:32:18.549 --> 00:32:18.559 align:start position:0% and H what should we do with 00:32:18.559 --> 00:32:22.149 align:start position:0% and H what should we do with h<00:32:19.559> over<00:32:19.880> 18<00:32:20.880> okay<00:32:21.240> let's<00:32:21.440> do 00:32:22.149 --> 00:32:22.159 align:start position:0% h over 18 okay let's do 00:32:22.159 --> 00:32:25.430 align:start position:0% h over 18 okay let's do that<00:32:23.159> so<00:32:23.639> I'm<00:32:23.760> going<00:32:23.840> to<00:32:24.080> REM<00:32:24.600> remove<00:32:25.000> this 00:32:25.430 --> 00:32:25.440 align:start position:0% that so I'm going to REM remove this 00:32:25.440 --> 00:32:26.870 align:start position:0% that so I'm going to REM remove this this<00:32:25.600> closing<00:32:26.039> thing<00:32:26.240> otherwise<00:32:26.639> it's<00:32:26.799> going 00:32:26.870 --> 00:32:26.880 align:start position:0% this closing thing otherwise it's going 00:32:26.880 --> 00:32:28.789 align:start position:0% this closing thing otherwise it's going to<00:32:27.080> just<00:32:27.559> create<00:32:27.960> the 00:32:28.789 --> 00:32:28.799 align:start position:0% to just create the 00:32:28.799 --> 00:32:35.310 align:start position:0% to just create the Pod<00:32:29.799> so<00:32:30.679> age<00:32:31.240> is<00:32:31.399> over<00:32:31.679> 18<00:32:33.039> quum<00:32:34.039> okay<00:32:34.760> so<00:32:35.200> now 00:32:35.310 --> 00:32:35.320 align:start position:0% Pod so age is over 18 quum okay so now 00:32:35.320 --> 00:32:38.110 align:start position:0% Pod so age is over 18 quum okay so now we'll<00:32:35.519> press<00:32:35.799> enter<00:32:36.799> and<00:32:37.279> if<00:32:37.399> the<00:32:37.559> demo<00:32:37.840> God<00:32:38.039> is 00:32:38.110 --> 00:32:38.120 align:start position:0% we'll press enter and if the demo God is 00:32:38.120 --> 00:32:41.149 align:start position:0% we'll press enter and if the demo God is on<00:32:38.279> my<00:32:38.480> side<00:32:39.080> this<00:32:39.240> will<00:32:39.840> succeed<00:32:40.840> oh<00:32:41.000> it's 00:32:41.149 --> 00:32:41.159 align:start position:0% on my side this will succeed oh it's 00:32:41.159 --> 00:32:43.269 align:start position:0% on my side this will succeed oh it's working<00:32:41.720> all<00:32:41.840> right<00:32:42.200> so<00:32:42.360> we<00:32:42.480> just<00:32:42.600> made<00:32:42.720> a<00:32:42.799> zero 00:32:43.269 --> 00:32:43.279 align:start position:0% working all right so we just made a zero 00:32:43.279 --> 00:32:44.789 align:start position:0% working all right so we just made a zero proof<00:32:43.480> and<00:32:43.559> we<00:32:43.679> created<00:32:43.919> a<00:32:44.039> new<00:32:44.240> pod<00:32:44.600> what's 00:32:44.789 --> 00:32:44.799 align:start position:0% proof and we created a new pod what's 00:32:44.799 --> 00:32:46.669 align:start position:0% proof and we created a new pod what's inside<00:32:45.039> our<00:32:45.200> new<00:32:45.399> pod<00:32:45.919> well<00:32:46.240> we<00:32:46.360> have<00:32:46.440> a<00:32:46.519> bunch 00:32:46.669 --> 00:32:46.679 align:start position:0% inside our new pod well we have a bunch 00:32:46.679 --> 00:32:47.710 align:start position:0% inside our new pod well we have a bunch of<00:32:46.840> logical 00:32:47.710 --> 00:32:47.720 align:start position:0% of logical 00:32:47.720 --> 00:32:50.149 align:start position:0% of logical statements<00:32:48.720> uh<00:32:48.840> let's<00:32:49.080> read<00:32:49.320> this<00:32:49.600> together 00:32:50.149 --> 00:32:50.159 align:start position:0% statements uh let's read this together 00:32:50.159 --> 00:32:51.710 align:start position:0% statements uh let's read this together because<00:32:50.440> there's<00:32:50.600> a<00:32:50.760> lot<00:32:50.960> going<00:32:51.159> on<00:32:51.440> so<00:32:51.600> the 00:32:51.710 --> 00:32:51.720 align:start position:0% because there's a lot going on so the 00:32:51.720 --> 00:32:53.509 align:start position:0% because there's a lot going on so the first<00:32:52.000> thing<00:32:52.159> you'll 00:32:53.509 --> 00:32:53.519 align:start position:0% first thing you'll 00:32:53.519 --> 00:32:56.590 align:start position:0% first thing you'll notice<00:32:54.519> is<00:32:54.799> that<00:32:55.120> some<00:32:55.440> entries<00:32:55.880> now<00:32:56.039> are 00:32:56.590 --> 00:32:56.600 align:start position:0% notice is that some entries now are 00:32:56.600 --> 00:32:58.950 align:start position:0% notice is that some entries now are prefixed<00:32:57.600> or<00:32:57.840> or<00:32:57.919> entries<00:32:58.200> used<00:32:58.480> to<00:32:58.639> not<00:32:58.760> be 00:32:58.950 --> 00:32:58.960 align:start position:0% prefixed or or entries used to not be 00:32:58.960 --> 00:33:01.389 align:start position:0% prefixed or or entries used to not be prefixed<00:32:59.960> entries<00:33:00.320> that<00:33:00.440> are<00:33:00.639> prefixed<00:33:01.200> are 00:33:01.389 --> 00:33:01.399 align:start position:0% prefixed entries that are prefixed are 00:33:01.399 --> 00:33:03.629 align:start position:0% prefixed entries that are prefixed are entries<00:33:01.760> that<00:33:01.960> provably<00:33:02.519> come<00:33:02.760> from<00:33:02.960> other 00:33:03.629 --> 00:33:03.639 align:start position:0% entries that provably come from other 00:33:03.639 --> 00:33:07.110 align:start position:0% entries that provably come from other pods<00:33:04.639> um<00:33:05.120> the<00:33:05.559> the<00:33:05.799> the<00:33:05.919> origin<00:33:06.799> doesn't 00:33:07.110 --> 00:33:07.120 align:start position:0% pods um the the the origin doesn't 00:33:07.120 --> 00:33:08.830 align:start position:0% pods um the the the origin doesn't really<00:33:07.360> matter<00:33:07.679> like<00:33:07.840> what's<00:33:08.039> written<00:33:08.440> be 00:33:08.830 --> 00:33:08.840 align:start position:0% really matter like what's written be 00:33:08.840 --> 00:33:10.350 align:start position:0% really matter like what's written be behind<00:33:09.039> the<00:33:09.159> column<00:33:09.440> doesn't<00:33:09.679> really<00:33:09.880> matter 00:33:10.350 --> 00:33:10.360 align:start position:0% behind the column doesn't really matter 00:33:10.360 --> 00:33:11.509 align:start position:0% behind the column doesn't really matter the<00:33:10.440> only<00:33:10.600> thing<00:33:10.720> that<00:33:10.840> matters<00:33:11.120> is<00:33:11.240> if<00:33:11.360> it's 00:33:11.509 --> 00:33:11.519 align:start position:0% the only thing that matters is if it's 00:33:11.519 --> 00:33:13.350 align:start position:0% the only thing that matters is if it's written<00:33:11.799> in<00:33:12.000> two<00:33:12.279> places<00:33:12.679> you<00:33:12.840> know<00:33:13.000> that<00:33:13.200> this 00:33:13.350 --> 00:33:13.360 align:start position:0% written in two places you know that this 00:33:13.360 --> 00:33:15.190 align:start position:0% written in two places you know that this entry<00:33:14.000> both<00:33:14.200> of<00:33:14.320> these<00:33:14.440> entry<00:33:14.760> came<00:33:14.960> from<00:33:15.120> the 00:33:15.190 --> 00:33:15.200 align:start position:0% entry both of these entry came from the 00:33:15.200 --> 00:33:17.070 align:start position:0% entry both of these entry came from the same<00:33:15.399> pod<00:33:16.000> the<00:33:16.159> reason<00:33:16.480> why<00:33:16.600> it's<00:33:16.799> really 00:33:17.070 --> 00:33:17.080 align:start position:0% same pod the reason why it's really 00:33:17.080 --> 00:33:18.870 align:start position:0% same pod the reason why it's really important<00:33:17.559> to<00:33:17.799> have<00:33:18.080> traces<00:33:18.559> of<00:33:18.720> where 00:33:18.870 --> 00:33:18.880 align:start position:0% important to have traces of where 00:33:18.880 --> 00:33:21.269 align:start position:0% important to have traces of where entries<00:33:19.279> come<00:33:19.480> from<00:33:20.039> is<00:33:20.240> because<00:33:20.480> you<00:33:20.639> cannot 00:33:21.269 --> 00:33:21.279 align:start position:0% entries come from is because you cannot 00:33:21.279 --> 00:33:23.070 align:start position:0% entries come from is because you cannot the<00:33:21.440> point<00:33:21.600> of<00:33:21.760> a<00:33:21.960> pod<00:33:22.200> the<00:33:22.279> reason<00:33:22.559> why<00:33:22.679> a<00:33:22.840> pod 00:33:23.070 --> 00:33:23.080 align:start position:0% the point of a pod the reason why a pod 00:33:23.080 --> 00:33:24.710 align:start position:0% the point of a pod the reason why a pod is<00:33:23.159> a<00:33:23.320> list<00:33:23.519> of<00:33:23.720> key<00:33:23.919> value<00:33:24.240> and<00:33:24.360> not<00:33:24.480> just<00:33:24.600> a 00:33:24.710 --> 00:33:24.720 align:start position:0% is a list of key value and not just a 00:33:24.720 --> 00:33:26.310 align:start position:0% is a list of key value and not just a single<00:33:25.000> key<00:33:25.200> and<00:33:25.240> a<00:33:25.360> single<00:33:25.639> value<00:33:25.880> is<00:33:26.039> because 00:33:26.310 --> 00:33:26.320 align:start position:0% single key and a single value is because 00:33:26.320 --> 00:33:28.669 align:start position:0% single key and a single value is because there<00:33:26.559> exist<00:33:26.880> in<00:33:27.000> the<00:33:27.120> world<00:33:27.840> values<00:33:28.159> that<00:33:28.320> go 00:33:28.669 --> 00:33:28.679 align:start position:0% there exist in the world values that go 00:33:28.679 --> 00:33:30.669 align:start position:0% there exist in the world values that go together<00:33:29.440> as<00:33:29.519> an<00:33:29.679> example<00:33:30.000> I<00:33:30.120> can't<00:33:30.320> take<00:33:30.519> my 00:33:30.669 --> 00:33:30.679 align:start position:0% together as an example I can't take my 00:33:30.679 --> 00:33:32.230 align:start position:0% together as an example I can't take my age<00:33:30.960> and<00:33:31.120> combine<00:33:31.440> it<00:33:31.600> with<00:33:31.720> your<00:33:31.919> name<00:33:32.120> and 00:33:32.230 --> 00:33:32.240 align:start position:0% age and combine it with your name and 00:33:32.240 --> 00:33:33.870 align:start position:0% age and combine it with your name and make<00:33:32.399> a<00:33:32.519> new<00:33:32.720> person<00:33:33.039> out<00:33:33.200> of<00:33:33.320> that<00:33:33.639> these 00:33:33.870 --> 00:33:33.880 align:start position:0% make a new person out of that these 00:33:33.880 --> 00:33:36.110 align:start position:0% make a new person out of that these entries<00:33:34.320> need<00:33:34.440> to<00:33:34.799> remain<00:33:35.039> logically<00:33:35.559> groups 00:33:36.110 --> 00:33:36.120 align:start position:0% entries need to remain logically groups 00:33:36.120 --> 00:33:38.830 align:start position:0% entries need to remain logically groups so<00:33:36.279> that's<00:33:36.480> why<00:33:36.600> we<00:33:36.760> have<00:33:37.320> this<00:33:38.320> so<00:33:38.480> let's<00:33:38.639> read 00:33:38.830 --> 00:33:38.840 align:start position:0% so that's why we have this so let's read 00:33:38.840 --> 00:33:42.830 align:start position:0% so that's why we have this so let's read it<00:33:39.120> together<00:33:39.919> um<00:33:40.559> maybe<00:33:41.559> we<00:33:41.679> we'll<00:33:41.880> do<00:33:42.120> the<00:33:42.440> the 00:33:42.830 --> 00:33:42.840 align:start position:0% it together um maybe we we'll do the the 00:33:42.840 --> 00:33:44.629 align:start position:0% it together um maybe we we'll do the the the<00:33:43.200> the<00:33:43.279> easy<00:33:43.639> stuff<00:33:43.919> first<00:33:44.120> so<00:33:44.320> first<00:33:44.519> we 00:33:44.629 --> 00:33:44.639 align:start position:0% the the easy stuff first so first we 00:33:44.639 --> 00:33:47.509 align:start position:0% the the easy stuff first so first we introduced<00:33:45.080> a<00:33:45.440> constant<00:33:46.440> constants<00:33:46.840> don't<00:33:47.080> ex 00:33:47.509 --> 00:33:47.519 align:start position:0% introduced a constant constants don't ex 00:33:47.519 --> 00:33:49.110 align:start position:0% introduced a constant constants don't ex exist<00:33:47.720> in<00:33:47.840> the<00:33:47.960> system<00:33:48.240> so<00:33:48.360> we<00:33:48.519> just<00:33:48.639> said 00:33:49.110 --> 00:33:49.120 align:start position:0% exist in the system so we just said 00:33:49.120 --> 00:33:51.509 align:start position:0% exist in the system so we just said 100,000<00:33:49.880> equals<00:33:50.440> 100,000<00:33:51.039> or<00:33:51.159> at<00:33:51.279> least<00:33:51.399> the 00:33:51.509 --> 00:33:51.519 align:start position:0% 100,000 equals 100,000 or at least the 00:33:51.519 --> 00:33:54.350 align:start position:0% 100,000 equals 100,000 or at least the entry<00:33:52.039> named<00:33:52.480> 100,000<00:33:52.960> as<00:33:53.080> a<00:33:53.240> string<00:33:53.679> equals 00:33:54.350 --> 00:33:54.360 align:start position:0% entry named 100,000 as a string equals 00:33:54.360 --> 00:33:56.870 align:start position:0% entry named 100,000 as a string equals 100,000<00:33:55.360> uh<00:33:55.480> We've<00:33:55.720> reveal<00:33:56.120> we<00:33:56.240> have<00:33:56.440> this 00:33:56.870 --> 00:33:56.880 align:start position:0% 100,000 uh We've reveal we have this 00:33:56.880 --> 00:33:59.350 align:start position:0% 100,000 uh We've reveal we have this entry<00:33:57.200> called<00:33:57.399> zip<00:33:57.559> code<00:33:57.799> code<00:33:58.200> 121<00:33:59.200> and 00:33:59.350 --> 00:33:59.360 align:start position:0% entry called zip code code 121 and 00:33:59.360 --> 00:34:01.110 align:start position:0% entry called zip code code 121 and notice<00:33:59.679> that<00:33:59.840> if<00:33:59.919> you<00:34:00.000> were<00:34:00.360> just<00:34:00.480> to<00:34:00.639> see<00:34:00.880> this 00:34:01.110 --> 00:34:01.120 align:start position:0% notice that if you were just to see this 00:34:01.120 --> 00:34:02.590 align:start position:0% notice that if you were just to see this that<00:34:01.240> doesn't<00:34:01.480> mean<00:34:01.720> that<00:34:01.880> my<00:34:02.080> zip<00:34:02.279> code<00:34:02.480> is 00:34:02.590 --> 00:34:02.600 align:start position:0% that doesn't mean that my zip code is 00:34:02.600 --> 00:34:03.990 align:start position:0% that doesn't mean that my zip code is that<00:34:02.799> zip<00:34:03.039> code<00:34:03.399> that<00:34:03.519> just<00:34:03.679> mean<00:34:03.880> that 00:34:03.990 --> 00:34:04.000 align:start position:0% that zip code that just mean that 00:34:04.000 --> 00:34:05.350 align:start position:0% that zip code that just mean that there's<00:34:04.159> an<00:34:04.279> entrical<00:34:04.840> zip<00:34:05.039> code<00:34:05.200> in<00:34:05.279> the 00:34:05.350 --> 00:34:05.360 align:start position:0% there's an entrical zip code in the 00:34:05.360 --> 00:34:07.230 align:start position:0% there's an entrical zip code in the current<00:34:05.679> pod<00:34:05.919> that<00:34:06.039> has<00:34:06.159> a<00:34:06.279> specific<00:34:06.639> value 00:34:07.230 --> 00:34:07.240 align:start position:0% current pod that has a specific value 00:34:07.240 --> 00:34:09.190 align:start position:0% current pod that has a specific value there's<00:34:07.440> another<00:34:07.840> constant<00:34:08.399> which<00:34:08.560> says<00:34:08.760> 18 00:34:09.190 --> 00:34:09.200 align:start position:0% there's another constant which says 18 00:34:09.200 --> 00:34:11.629 align:start position:0% there's another constant which says 18 is<00:34:09.480> is<00:34:09.679> 18<00:34:10.679> and<00:34:10.839> finally<00:34:11.200> there's<00:34:11.399> another 00:34:11.629 --> 00:34:11.639 align:start position:0% is is 18 and finally there's another 00:34:11.639 --> 00:34:13.829 align:start position:0% is is 18 and finally there's another entry<00:34:11.919> in<00:34:12.000> the<00:34:12.079> current<00:34:12.359> pod<00:34:12.639> that<00:34:12.760> says<00:34:13.000> serer 00:34:13.829 --> 00:34:13.839 align:start position:0% entry in the current pod that says serer 00:34:13.839 --> 00:34:16.190 align:start position:0% entry in the current pod that says serer equals<00:34:14.200> this<00:34:14.399> public<00:34:14.679> key<00:34:15.359> so<00:34:15.520> if<00:34:15.639> you<00:34:15.720> were<00:34:15.919> to 00:34:16.190 --> 00:34:16.200 align:start position:0% equals this public key so if you were to 00:34:16.200 --> 00:34:19.030 align:start position:0% equals this public key so if you were to just<00:34:16.399> see<00:34:16.919> these<00:34:17.440> these<00:34:17.639> four<00:34:17.960> blue<00:34:18.320> values 00:34:19.030 --> 00:34:19.040 align:start position:0% just see these these four blue values 00:34:19.040 --> 00:34:20.790 align:start position:0% just see these these four blue values that<00:34:19.159> wouldn't<00:34:19.520> really<00:34:19.800> prove<00:34:20.159> anything<00:34:20.639> that 00:34:20.790 --> 00:34:20.800 align:start position:0% that wouldn't really prove anything that 00:34:20.800 --> 00:34:22.149 align:start position:0% that wouldn't really prove anything that just<00:34:20.919> says<00:34:21.119> I<00:34:21.200> just<00:34:21.320> made<00:34:21.440> a<00:34:21.560> pod<00:34:21.800> with<00:34:21.919> a<00:34:22.000> bunch 00:34:22.149 --> 00:34:22.159 align:start position:0% just says I just made a pod with a bunch 00:34:22.159 --> 00:34:23.950 align:start position:0% just says I just made a pod with a bunch of<00:34:22.240> entries<00:34:22.560> in<00:34:22.720> them<00:34:23.040> what<00:34:23.159> matters<00:34:23.560> now<00:34:23.800> is 00:34:23.950 --> 00:34:23.960 align:start position:0% of entries in them what matters now is 00:34:23.960 --> 00:34:25.510 align:start position:0% of entries in them what matters now is the<00:34:24.159> relationship<00:34:24.760> between<00:34:25.040> these<00:34:25.200> entries 00:34:25.510 --> 00:34:25.520 align:start position:0% the relationship between these entries 00:34:25.520 --> 00:34:28.149 align:start position:0% the relationship between these entries and<00:34:25.720> previous<00:34:26.079> entries<00:34:26.919> through<00:34:27.240> logical 00:34:28.149 --> 00:34:28.159 align:start position:0% and previous entries through logical 00:34:28.159 --> 00:34:30.270 align:start position:0% and previous entries through logical statements<00:34:29.159> so<00:34:29.399> let's<00:34:29.599> read<00:34:29.800> them<00:34:29.960> from<00:34:30.119> the 00:34:30.270 --> 00:34:30.280 align:start position:0% statements so let's read them from the 00:34:30.280 --> 00:34:33.230 align:start position:0% statements so let's read them from the top<00:34:30.639> so<00:34:30.800> the<00:34:30.960> top<00:34:31.200> says<00:34:31.800> there's<00:34:32.000> a<00:34:32.240> pod<00:34:32.919> whose 00:34:33.230 --> 00:34:33.240 align:start position:0% top so the top says there's a pod whose 00:34:33.240 --> 00:34:35.629 align:start position:0% top so the top says there's a pod whose origin<00:34:33.679> ends<00:34:33.919> with<00:34:34.079> 973<00:34:35.079> and<00:34:35.200> in<00:34:35.320> that<00:34:35.480> pod 00:34:35.629 --> 00:34:35.639 align:start position:0% origin ends with 973 and in that pod 00:34:35.639 --> 00:34:36.990 align:start position:0% origin ends with 973 and in that pod there<00:34:35.720> was<00:34:35.839> an<00:34:36.000> entry<00:34:36.280> called<00:34:36.480> age<00:34:36.720> and<00:34:36.839> it's 00:34:36.990 --> 00:34:37.000 align:start position:0% there was an entry called age and it's 00:34:37.000 --> 00:34:37.790 align:start position:0% there was an entry called age and it's over 00:34:37.790 --> 00:34:37.800 align:start position:0% over 00:34:37.800 --> 00:34:40.430 align:start position:0% over 18<00:34:38.800> there<00:34:38.919> are<00:34:39.040> two<00:34:39.280> pods<00:34:39.800> one<00:34:39.960> that<00:34:40.079> end<00:34:40.320> with 00:34:40.430 --> 00:34:40.440 align:start position:0% 18 there are two pods one that end with 00:34:40.440 --> 00:34:42.589 align:start position:0% 18 there are two pods one that end with 973<00:34:41.119> the<00:34:41.200> other<00:34:41.359> one<00:34:41.480> that<00:34:41.599> ends<00:34:41.800> with<00:34:41.919> 226 00:34:42.589 --> 00:34:42.599 align:start position:0% 973 the other one that ends with 226 00:34:42.599 --> 00:34:44.349 align:start position:0% 973 the other one that ends with 226 where<00:34:42.839> both<00:34:43.000> of<00:34:43.119> their<00:34:43.280> under<00:34:43.560> SC<00:34:43.879> scanners 00:34:44.349 --> 00:34:44.359 align:start position:0% where both of their under SC scanners 00:34:44.359 --> 00:34:47.149 align:start position:0% where both of their under SC scanners were<00:34:44.560> the<00:34:44.879> same<00:34:45.879> the<00:34:46.040> Pod<00:34:46.200> that<00:34:46.320> ends<00:34:46.520> with<00:34:46.639> 226 00:34:47.149 --> 00:34:47.159 align:start position:0% were the same the Pod that ends with 226 00:34:47.159 --> 00:34:49.669 align:start position:0% were the same the Pod that ends with 226 had<00:34:47.280> a<00:34:47.440> salary<00:34:47.760> entry<00:34:48.079> which<00:34:48.200> is<00:34:48.320> over<00:34:48.679> 100,000 00:34:49.669 --> 00:34:49.679 align:start position:0% had a salary entry which is over 100,000 00:34:49.679 --> 00:34:52.710 align:start position:0% had a salary entry which is over 100,000 and<00:34:50.079> both<00:34:50.399> pods<00:34:50.800> have<00:34:50.960> the<00:34:51.079> same<00:34:51.280> ID<00:34:52.040> finally 00:34:52.710 --> 00:34:52.720 align:start position:0% and both pods have the same ID finally 00:34:52.720 --> 00:34:54.430 align:start position:0% and both pods have the same ID finally the<00:34:52.919> ZIP<00:34:53.159> code<00:34:53.359> entry<00:34:53.639> in<00:34:53.679> the<00:34:53.800> current<00:34:54.079> pod<00:34:54.320> is 00:34:54.430 --> 00:34:54.440 align:start position:0% the ZIP code entry in the current pod is 00:34:54.440 --> 00:34:56.230 align:start position:0% the ZIP code entry in the current pod is the<00:34:54.520> same<00:34:54.679> as<00:34:54.800> the<00:34:54.919> ZIP<00:34:55.119> code<00:34:55.280> entry<00:34:55.520> in<00:34:55.599> the<00:34:55.679> 73 00:34:56.230 --> 00:34:56.240 align:start position:0% the same as the ZIP code entry in the 73 00:34:56.240 --> 00:34:58.230 align:start position:0% the same as the ZIP code entry in the 73 pod<00:34:56.720> and<00:34:56.839> the<00:34:56.960> signer<00:34:57.320> in<00:34:57.400> the<00:34:57.680> current<00:34:57.920> pod<00:34:58.119> is 00:34:58.230 --> 00:34:58.240 align:start position:0% pod and the signer in the current pod is 00:34:58.240 --> 00:35:01.030 align:start position:0% pod and the signer in the current pod is the<00:34:58.359> same<00:34:58.599> as<00:34:58.720> the<00:34:58.880> underscore<00:34:59.320> c73<00:35:00.320> pod<00:35:00.839> so 00:35:01.030 --> 00:35:01.040 align:start position:0% the same as the underscore c73 pod so 00:35:01.040 --> 00:35:03.150 align:start position:0% the same as the underscore c73 pod so this<00:35:01.320> EXA<00:35:01.760> basically<00:35:02.160> as<00:35:02.280> a 00:35:03.150 --> 00:35:03.160 align:start position:0% this EXA basically as a 00:35:03.160 --> 00:35:05.790 align:start position:0% this EXA basically as a claim<00:35:04.160> kind<00:35:04.280> of<00:35:04.440> like<00:35:04.560> shows<00:35:04.920> logically<00:35:05.680> what 00:35:05.790 --> 00:35:05.800 align:start position:0% claim kind of like shows logically what 00:35:05.800 --> 00:35:07.950 align:start position:0% claim kind of like shows logically what we've<00:35:05.960> been<00:35:06.079> trying<00:35:06.280> to<00:35:06.400> show<00:35:06.640> so<00:35:06.839> far<00:35:07.720> okay<00:35:07.839> so 00:35:07.950 --> 00:35:07.960 align:start position:0% we've been trying to show so far okay so 00:35:07.960 --> 00:35:10.470 align:start position:0% we've been trying to show so far okay so I'll<00:35:08.160> stop<00:35:08.480> here<00:35:08.800> because<00:35:09.200> we<00:35:09.359> just<00:35:09.520> did<00:35:09.680> a<00:35:09.800> lot 00:35:10.470 --> 00:35:10.480 align:start position:0% I'll stop here because we just did a lot 00:35:10.480 --> 00:35:12.190 align:start position:0% I'll stop here because we just did a lot um<00:35:10.880> if<00:35:11.000> there<00:35:11.119> are<00:35:11.320> questions<00:35:11.760> we<00:35:11.839> can<00:35:12.000> go 00:35:12.190 --> 00:35:12.200 align:start position:0% um if there are questions we can go 00:35:12.200 --> 00:35:14.230 align:start position:0% um if there are questions we can go through<00:35:12.400> this<00:35:12.599> like<00:35:12.760> many<00:35:13.000> times<00:35:13.280> so<00:35:14.000> let<00:35:14.119> me 00:35:14.230 --> 00:35:14.240 align:start position:0% through this like many times so let me 00:35:14.240 --> 00:35:18.109 align:start position:0% through this like many times so let me know<00:35:14.359> if<00:35:14.480> there<00:35:14.599> are<00:35:14.760> questions<00:35:15.119> here<00:35:15.480> so 00:35:18.109 --> 00:35:18.119 align:start position:0% 00:35:18.119 --> 00:35:23.069 align:start position:0% far<00:35:19.119> yes<00:35:20.079> can<00:35:21.079> uh<00:35:21.960> can<00:35:22.160> one<00:35:22.359> volunteer<00:35:22.760> bring<00:35:22.960> a 00:35:23.069 --> 00:35:23.079 align:start position:0% far yes can uh can one volunteer bring a 00:35:23.079 --> 00:35:29.990 align:start position:0% far yes can uh can one volunteer bring a mic<00:35:23.320> oh<00:35:23.480> thanks<00:35:23.680> Arturo 00:35:29.990 --> 00:35:30.000 align:start position:0% 00:35:30.000 --> 00:35:31.030 align:start position:0% thank 00:35:31.030 --> 00:35:31.040 align:start position:0% thank 00:35:31.040 --> 00:35:33.990 align:start position:0% thank you<00:35:32.040> thanks<00:35:32.280> for<00:35:32.440> the<00:35:32.680> introduction<00:35:33.680> if<00:35:33.839> we 00:35:33.990 --> 00:35:34.000 align:start position:0% you thanks for the introduction if we 00:35:34.000 --> 00:35:36.230 align:start position:0% you thanks for the introduction if we assume<00:35:34.440> that<00:35:34.640> this<00:35:34.760> is<00:35:34.920> the<00:35:35.240> technical 00:35:36.230 --> 00:35:36.240 align:start position:0% assume that this is the technical 00:35:36.240 --> 00:35:39.510 align:start position:0% assume that this is the technical capability<00:35:37.240> what<00:35:37.359> would<00:35:37.560> be<00:35:37.680> an<00:35:37.880> application 00:35:39.510 --> 00:35:39.520 align:start position:0% capability what would be an application 00:35:39.520 --> 00:35:43.270 align:start position:0% capability what would be an application M<00:35:40.520> um 00:35:43.270 --> 00:35:43.280 align:start position:0% 00:35:43.280 --> 00:35:46.589 align:start position:0% so<00:35:44.280> the<00:35:44.440> current<00:35:44.760> technical<00:35:45.599> capabilities 00:35:46.589 --> 00:35:46.599 align:start position:0% so the current technical capabilities 00:35:46.599 --> 00:35:48.790 align:start position:0% so the current technical capabilities which<00:35:47.079> have<00:35:47.240> to<00:35:47.400> do<00:35:47.599> with<00:35:47.760> importing<00:35:48.320> data<00:35:48.599> are 00:35:48.790 --> 00:35:48.800 align:start position:0% which have to do with importing data are 00:35:48.800 --> 00:35:50.190 align:start position:0% which have to do with importing data are pretty<00:35:49.079> limited<00:35:49.640> because<00:35:49.800> we're<00:35:50.040> just 00:35:50.190 --> 00:35:50.200 align:start position:0% pretty limited because we're just 00:35:50.200 --> 00:35:52.470 align:start position:0% pretty limited because we're just signing<00:35:50.640> pods<00:35:50.960> ourselves<00:35:51.599> right<00:35:52.119> so<00:35:52.319> what 00:35:52.470 --> 00:35:52.480 align:start position:0% signing pods ourselves right so what 00:35:52.480 --> 00:35:55.309 align:start position:0% signing pods ourselves right so what this<00:35:52.599> means<00:35:52.920> is<00:35:53.599> this<00:35:53.720> is<00:35:53.960> only<00:35:54.359> useful 00:35:55.309 --> 00:35:55.319 align:start position:0% this means is this is only useful 00:35:55.319 --> 00:35:57.990 align:start position:0% this means is this is only useful currently<00:35:56.160> if<00:35:56.839> just<00:35:57.079> like<00:35:57.240> the<00:35:57.400> pod<00:35:57.760> one 00:35:57.990 --> 00:35:58.000 align:start position:0% currently if just like the pod one 00:35:58.000 --> 00:36:00.030 align:start position:0% currently if just like the pod one systems<00:35:58.640> people<00:35:58.920> that<00:35:59.040> are<00:35:59.280> use<00:35:59.599> issuing 00:36:00.030 --> 00:36:00.040 align:start position:0% systems people that are use issuing 00:36:00.040 --> 00:36:02.670 align:start position:0% systems people that are use issuing useful<00:36:00.480> data<00:36:01.240> like<00:36:01.440> the<00:36:01.560> swamp<00:36:02.200> that<00:36:02.319> issues 00:36:02.670 --> 00:36:02.680 align:start position:0% useful data like the swamp that issues 00:36:02.680 --> 00:36:04.870 align:start position:0% useful data like the swamp that issues your<00:36:02.839> frogs<00:36:03.680> issues<00:36:04.040> you<00:36:04.200> Frog<00:36:04.520> as<00:36:04.680> these 00:36:04.870 --> 00:36:04.880 align:start position:0% your frogs issues you Frog as these 00:36:04.880 --> 00:36:08.430 align:start position:0% your frogs issues you Frog as these schnore<00:36:05.319> 16<00:36:05.760> pods<00:36:06.400> right<00:36:07.079> so<00:36:07.720> if<00:36:07.839> you<00:36:08.000> could<00:36:08.200> do 00:36:08.430 --> 00:36:08.440 align:start position:0% schnore 16 pods right so if you could do 00:36:08.440 --> 00:36:09.990 align:start position:0% schnore 16 pods right so if you could do that<00:36:08.839> then<00:36:09.079> the<00:36:09.200> way<00:36:09.319> to<00:36:09.480> think<00:36:09.640> about<00:36:09.839> the 00:36:09.990 --> 00:36:10.000 align:start position:0% that then the way to think about the 00:36:10.000 --> 00:36:12.190 align:start position:0% that then the way to think about the system<00:36:10.280> is<00:36:10.440> it's<00:36:10.560> a<00:36:10.720> way<00:36:10.880> to<00:36:11.079> operate<00:36:11.400> on<00:36:11.640> data 00:36:12.190 --> 00:36:12.200 align:start position:0% system is it's a way to operate on data 00:36:12.200 --> 00:36:13.309 align:start position:0% system is it's a way to operate on data and<00:36:12.319> then<00:36:12.480> make<00:36:12.640> further<00:36:12.960> and<00:36:13.040> further 00:36:13.309 --> 00:36:13.319 align:start position:0% and then make further and further 00:36:13.319 --> 00:36:14.790 align:start position:0% and then make further and further refinement<00:36:13.800> of<00:36:13.920> data<00:36:14.079> and<00:36:14.240> combination<00:36:14.640> of 00:36:14.790 --> 00:36:14.800 align:start position:0% refinement of data and combination of 00:36:14.800 --> 00:36:17.109 align:start position:0% refinement of data and combination of data<00:36:15.200> in<00:36:15.359> such<00:36:15.520> a<00:36:15.640> way<00:36:15.800> that<00:36:15.960> the<00:36:16.119> data 00:36:17.109 --> 00:36:17.119 align:start position:0% data in such a way that the data 00:36:17.119 --> 00:36:19.790 align:start position:0% data in such a way that the data Integrity<00:36:17.720> is<00:36:17.880> maintained<00:36:18.880> so<00:36:19.440> there's<00:36:19.640> a 00:36:19.790 --> 00:36:19.800 align:start position:0% Integrity is maintained so there's a 00:36:19.800 --> 00:36:22.270 align:start position:0% Integrity is maintained so there's a couple<00:36:20.040> of<00:36:20.160> things<00:36:20.359> you<00:36:20.480> can<00:36:20.640> do<00:36:21.119> one<00:36:21.359> is<00:36:22.000> um 00:36:22.270 --> 00:36:22.280 align:start position:0% couple of things you can do one is um 00:36:22.280 --> 00:36:24.790 align:start position:0% couple of things you can do one is um I'll<00:36:22.480> take<00:36:22.680> the<00:36:22.880> national<00:36:23.359> ID<00:36:24.079> kind<00:36:24.240> of<00:36:24.440> lens 00:36:24.790 --> 00:36:24.800 align:start position:0% I'll take the national ID kind of lens 00:36:24.800 --> 00:36:26.270 align:start position:0% I'll take the national ID kind of lens even<00:36:24.960> if<00:36:25.079> it's<00:36:25.200> not<00:36:25.359> my<00:36:25.520> favorite<00:36:25.839> one<00:36:26.079> because 00:36:26.270 --> 00:36:26.280 align:start position:0% even if it's not my favorite one because 00:36:26.280 --> 00:36:28.510 align:start position:0% even if it's not my favorite one because it<00:36:26.400> speaks<00:36:26.720> the<00:36:26.839> most<00:36:27.000> to<00:36:27.200> people<00:36:27.839> which<00:36:28.000> is 00:36:28.510 --> 00:36:28.520 align:start position:0% it speaks the most to people which is 00:36:28.520 --> 00:36:31.710 align:start position:0% it speaks the most to people which is that<00:36:29.520> if<00:36:29.640> you<00:36:29.920> expect<00:36:30.480> a<00:36:30.680> data<00:36:30.960> issuer<00:36:31.480> to<00:36:31.640> be 00:36:31.710 --> 00:36:31.720 align:start position:0% that if you expect a data issuer to be 00:36:31.720 --> 00:36:33.710 align:start position:0% that if you expect a data issuer to be able<00:36:31.920> to<00:36:32.079> answer<00:36:32.520> any<00:36:32.800> kind<00:36:33.000> of<00:36:33.280> question<00:36:33.599> that 00:36:33.710 --> 00:36:33.720 align:start position:0% able to answer any kind of question that 00:36:33.720 --> 00:36:35.030 align:start position:0% able to answer any kind of question that someone<00:36:33.960> would<00:36:34.160> want<00:36:34.280> to<00:36:34.440> ask<00:36:34.680> about<00:36:34.880> that 00:36:35.030 --> 00:36:35.040 align:start position:0% someone would want to ask about that 00:36:35.040 --> 00:36:36.270 align:start position:0% someone would want to ask about that data<00:36:35.319> it's<00:36:35.520> really<00:36:35.680> annoying<00:36:36.000> for<00:36:36.160> them 00:36:36.270 --> 00:36:36.280 align:start position:0% data it's really annoying for them 00:36:36.280 --> 00:36:38.069 align:start position:0% data it's really annoying for them because<00:36:36.440> they<00:36:36.560> have<00:36:36.640> to<00:36:36.720> do<00:36:36.839> a<00:36:36.920> lot<00:36:37.040> of<00:36:37.200> work 00:36:38.069 --> 00:36:38.079 align:start position:0% because they have to do a lot of work 00:36:38.079 --> 00:36:39.630 align:start position:0% because they have to do a lot of work ideally<00:36:38.520> what<00:36:38.640> you<00:36:38.760> want<00:36:39.000> them<00:36:39.160> is<00:36:39.280> to<00:36:39.440> want 00:36:39.630 --> 00:36:39.640 align:start position:0% ideally what you want them is to want 00:36:39.640 --> 00:36:41.349 align:start position:0% ideally what you want them is to want them<00:36:39.800> to<00:36:40.040> issue<00:36:40.319> some<00:36:40.520> data<00:36:40.760> and<00:36:40.880> be<00:36:41.000> like<00:36:41.200> now 00:36:41.349 --> 00:36:41.359 align:start position:0% them to issue some data and be like now 00:36:41.359 --> 00:36:43.390 align:start position:0% them to issue some data and be like now it's<00:36:41.560> your<00:36:41.880> problem<00:36:42.240> to<00:36:42.440> operate<00:36:42.760> on<00:36:43.240> that 00:36:43.390 --> 00:36:43.400 align:start position:0% it's your problem to operate on that 00:36:43.400 --> 00:36:46.670 align:start position:0% it's your problem to operate on that data<00:36:43.800> but<00:36:43.960> at<00:36:44.119> least<00:36:44.520> you<00:36:44.680> cannot<00:36:45.640> make<00:36:46.280> like 00:36:46.670 --> 00:36:46.680 align:start position:0% data but at least you cannot make like 00:36:46.680 --> 00:36:49.550 align:start position:0% data but at least you cannot make like false<00:36:47.200> data<00:36:47.880> pretending<00:36:48.240> to<00:36:48.359> be<00:36:48.520> me<00:36:48.960> so<00:36:49.119> as<00:36:49.200> an 00:36:49.550 --> 00:36:49.560 align:start position:0% false data pretending to be me so as an 00:36:49.560 --> 00:36:52.470 align:start position:0% false data pretending to be me so as an example<00:36:50.560> um<00:36:51.000> if<00:36:51.359> so<00:36:51.599> I<00:36:51.680> come<00:36:51.800> from<00:36:51.960> Belgium<00:36:52.359> if 00:36:52.470 --> 00:36:52.480 align:start position:0% example um if so I come from Belgium if 00:36:52.480 --> 00:36:53.990 align:start position:0% example um if so I come from Belgium if the<00:36:52.599> government<00:36:52.960> of<00:36:53.119> Belgium<00:36:53.720> they're 00:36:53.990 --> 00:36:54.000 align:start position:0% the government of Belgium they're 00:36:54.000 --> 00:36:56.550 align:start position:0% the government of Belgium they're Europeans<00:36:54.520> so<00:36:54.680> they're<00:36:54.839> further<00:36:55.240> thinking<00:36:56.200> um 00:36:56.550 --> 00:36:56.560 align:start position:0% Europeans so they're further thinking um 00:36:56.560 --> 00:36:58.710 align:start position:0% Europeans so they're further thinking um they<00:36:56.839> start<00:36:57.119> issuing<00:36:57.640> passport<00:36:58.040> or<00:36:58.359> national 00:36:58.710 --> 00:36:58.720 align:start position:0% they start issuing passport or national 00:36:58.720 --> 00:37:01.829 align:start position:0% they start issuing passport or national ID<00:36:59.040> card<00:36:59.400> using<00:36:59.680> the<00:36:59.839> schnore<00:37:00.200> 16<00:37:00.560> pod<00:37:01.400> um<00:37:01.640> now 00:37:01.829 --> 00:37:01.839 align:start position:0% ID card using the schnore 16 pod um now 00:37:01.839 --> 00:37:03.910 align:start position:0% ID card using the schnore 16 pod um now I<00:37:01.960> can<00:37:02.280> do<00:37:02.520> things<00:37:02.839> like<00:37:03.240> go<00:37:03.440> somewhere<00:37:03.760> and 00:37:03.910 --> 00:37:03.920 align:start position:0% I can do things like go somewhere and 00:37:03.920 --> 00:37:05.349 align:start position:0% I can do things like go somewhere and prove<00:37:04.119> that<00:37:04.240> my<00:37:04.359> age<00:37:04.560> is<00:37:04.680> a<00:37:04.839> specific<00:37:05.119> amount 00:37:05.349 --> 00:37:05.359 align:start position:0% prove that my age is a specific amount 00:37:05.359 --> 00:37:07.030 align:start position:0% prove that my age is a specific amount or<00:37:05.520> I<00:37:05.599> can<00:37:05.760> claim<00:37:06.000> a<00:37:06.119> government<00:37:06.480> benefit 00:37:07.030 --> 00:37:07.040 align:start position:0% or I can claim a government benefit 00:37:07.040 --> 00:37:08.870 align:start position:0% or I can claim a government benefit anonymously<00:37:08.040> without<00:37:08.240> being<00:37:08.400> able<00:37:08.560> to<00:37:08.640> claim 00:37:08.870 --> 00:37:08.880 align:start position:0% anonymously without being able to claim 00:37:08.880 --> 00:37:10.430 align:start position:0% anonymously without being able to claim it<00:37:08.960> multiple<00:37:09.359> time<00:37:09.599> or<00:37:09.720> I<00:37:09.800> can<00:37:09.920> use<00:37:10.119> that<00:37:10.280> to 00:37:10.430 --> 00:37:10.440 align:start position:0% it multiple time or I can use that to 00:37:10.440 --> 00:37:12.430 align:start position:0% it multiple time or I can use that to sign<00:37:10.880> digital<00:37:11.319> documents<00:37:11.760> or<00:37:11.920> I<00:37:12.000> can<00:37:12.200> kind<00:37:12.319> of 00:37:12.430 --> 00:37:12.440 align:start position:0% sign digital documents or I can kind of 00:37:12.440 --> 00:37:13.950 align:start position:0% sign digital documents or I can kind of like<00:37:12.599> anything<00:37:12.839> that<00:37:13.000> involves<00:37:13.319> my<00:37:13.480> identity 00:37:13.950 --> 00:37:13.960 align:start position:0% like anything that involves my identity 00:37:13.960 --> 00:37:15.710 align:start position:0% like anything that involves my identity is<00:37:14.119> just<00:37:14.280> logical<00:37:14.760> statements<00:37:15.240> apply<00:37:15.520> to<00:37:15.599> my 00:37:15.710 --> 00:37:15.720 align:start position:0% is just logical statements apply to my 00:37:15.720 --> 00:37:17.630 align:start position:0% is just logical statements apply to my identity<00:37:16.319> as<00:37:16.480> example<00:37:16.760> signing<00:37:17.040> a<00:37:17.240> document 00:37:17.630 --> 00:37:17.640 align:start position:0% identity as example signing a document 00:37:17.640 --> 00:37:19.790 align:start position:0% identity as example signing a document is<00:37:17.760> a<00:37:17.960> pod<00:37:18.240> that<00:37:18.359> says<00:37:18.880> the<00:37:19.040> hash<00:37:19.280> of<00:37:19.480> that 00:37:19.790 --> 00:37:19.800 align:start position:0% is a pod that says the hash of that 00:37:19.800 --> 00:37:22.710 align:start position:0% is a pod that says the hash of that document<00:37:20.800> as<00:37:20.960> an<00:37:21.119> entry<00:37:21.800> and<00:37:21.880> then<00:37:22.079> there<00:37:22.160> is 00:37:22.710 --> 00:37:22.720 align:start position:0% document as an entry and then there is 00:37:22.720 --> 00:37:24.910 align:start position:0% document as an entry and then there is my<00:37:23.079> I<00:37:23.160> don't<00:37:23.319> know<00:37:23.880> ID<00:37:24.240> number<00:37:24.560> or<00:37:24.680> something 00:37:24.910 --> 00:37:24.920 align:start position:0% my I don't know ID number or something 00:37:24.920 --> 00:37:26.790 align:start position:0% my I don't know ID number or something else<00:37:25.200> there<00:37:25.560> provably<00:37:26.000> coming<00:37:26.240> from<00:37:26.359> an<00:37:26.520> ID 00:37:26.790 --> 00:37:26.800 align:start position:0% else there provably coming from an ID 00:37:26.800 --> 00:37:29.270 align:start position:0% else there provably coming from an ID card<00:37:27.040> sign<00:37:27.319> but<00:37:27.520> the<00:37:27.599> Belgian<00:37:28.160> government<00:37:29.160> and 00:37:29.270 --> 00:37:29.280 align:start position:0% card sign but the Belgian government and 00:37:29.280 --> 00:37:31.550 align:start position:0% card sign but the Belgian government and the<00:37:29.480> required<00:37:29.960> infrastructure<00:37:30.920> would<00:37:31.200> be 00:37:31.550 --> 00:37:31.560 align:start position:0% the required infrastructure would be 00:37:31.560 --> 00:37:34.710 align:start position:0% the required infrastructure would be that<00:37:32.000> the<00:37:32.200> government<00:37:32.920> and<00:37:33.119> your<00:37:33.720> employer 00:37:34.710 --> 00:37:34.720 align:start position:0% that the government and your employer 00:37:34.720 --> 00:37:38.510 align:start position:0% that the government and your employer both<00:37:35.000> have<00:37:35.599> public<00:37:35.960> Keys<00:37:36.800> yes<00:37:37.119> so<00:37:37.720> so<00:37:37.920> they<00:37:38.079> do 00:37:38.510 --> 00:37:38.520 align:start position:0% both have public Keys yes so so they do 00:37:38.520 --> 00:37:39.870 align:start position:0% both have public Keys yes so so they do the<00:37:38.640> the<00:37:38.720> government<00:37:39.079> has<00:37:39.240> public<00:37:39.440> Keys<00:37:39.680> your 00:37:39.870 --> 00:37:39.880 align:start position:0% the the government has public Keys your 00:37:39.880 --> 00:37:41.910 align:start position:0% the the government has public Keys your passport<00:37:40.480> is<00:37:40.640> signed<00:37:41.119> your<00:37:41.319> ID<00:37:41.599> card<00:37:41.800> is 00:37:41.910 --> 00:37:41.920 align:start position:0% passport is signed your ID card is 00:37:41.920 --> 00:37:43.470 align:start position:0% passport is signed your ID card is signed<00:37:42.359> so<00:37:42.480> what<00:37:42.599> I'm<00:37:42.680> saying<00:37:42.880> is<00:37:43.040> the<00:37:43.160> current 00:37:43.470 --> 00:37:43.480 align:start position:0% signed so what I'm saying is the current 00:37:43.480 --> 00:37:45.349 align:start position:0% signed so what I'm saying is the current the<00:37:43.599> current<00:37:43.839> system<00:37:44.119> really<00:37:44.319> sucks<00:37:45.119> right 00:37:45.349 --> 00:37:45.359 align:start position:0% the current system really sucks right 00:37:45.359 --> 00:37:46.829 align:start position:0% the current system really sucks right because<00:37:45.680> you<00:37:45.880> you<00:37:46.000> need<00:37:46.240> people<00:37:46.440> to<00:37:46.599> issue 00:37:46.829 --> 00:37:46.839 align:start position:0% because you you need people to issue 00:37:46.839 --> 00:37:48.589 align:start position:0% because you you need people to issue their<00:37:46.960> own<00:37:47.160> pods<00:37:47.760> where<00:37:47.920> we're<00:37:48.079> trying<00:37:48.280> to<00:37:48.440> get 00:37:48.589 --> 00:37:48.599 align:start position:0% their own pods where we're trying to get 00:37:48.599 --> 00:37:50.589 align:start position:0% their own pods where we're trying to get to<00:37:49.119> and<00:37:49.680> I<00:37:49.760> thought<00:37:49.920> we<00:37:50.040> would<00:37:50.160> get<00:37:50.280> to<00:37:50.440> there 00:37:50.589 --> 00:37:50.599 align:start position:0% to and I thought we would get to there 00:37:50.599 --> 00:37:52.109 align:start position:0% to and I thought we would get to there for<00:37:50.760> this<00:37:50.920> demo<00:37:51.200> but<00:37:51.280> we<00:37:51.480> did<00:37:51.640> not<00:37:51.920> it's<00:37:52.040> going 00:37:52.109 --> 00:37:52.119 align:start position:0% for this demo but we did not it's going 00:37:52.119 --> 00:37:54.430 align:start position:0% for this demo but we did not it's going to<00:37:52.240> take<00:37:52.359> us<00:37:52.520> one<00:37:52.640> more<00:37:52.839> week<00:37:53.200> is<00:37:53.960> the<00:37:54.119> first 00:37:54.430 --> 00:37:54.440 align:start position:0% to take us one more week is the first 00:37:54.440 --> 00:37:56.190 align:start position:0% to take us one more week is the first demo<00:37:54.680> of<00:37:54.800> an<00:37:55.000> introduction<00:37:55.599> Gadget<00:37:56.000> where<00:37:56.119> you 00:37:56.190 --> 00:37:56.200 align:start position:0% demo of an introduction Gadget where you 00:37:56.200 --> 00:37:57.950 align:start position:0% demo of an introduction Gadget where you can<00:37:56.359> take<00:37:56.599> existing<00:37:57.000> cryptography<00:37:57.680> data<00:37:57.880> that 00:37:57.950 --> 00:37:57.960 align:start position:0% can take existing cryptography data that 00:37:57.960 --> 00:37:59.550 align:start position:0% can take existing cryptography data that is<00:37:58.040> in<00:37:58.119> a<00:37:58.280> totally<00:37:58.599> different<00:37:58.880> format<00:37:59.359> and 00:37:59.550 --> 00:37:59.560 align:start position:0% is in a totally different format and 00:37:59.560 --> 00:38:01.589 align:start position:0% is in a totally different format and import<00:37:59.960> it<00:38:00.119> as<00:38:00.240> a<00:38:00.440> pod<00:38:01.119> and<00:38:01.240> then<00:38:01.359> you<00:38:01.440> can 00:38:01.589 --> 00:38:01.599 align:start position:0% import it as a pod and then you can 00:38:01.599 --> 00:38:03.270 align:start position:0% import it as a pod and then you can operate<00:38:01.880> on<00:38:02.000> it<00:38:02.200> so<00:38:02.560> what<00:38:02.680> we<00:38:02.760> were<00:38:02.920> trying<00:38:03.119> to 00:38:03.270 --> 00:38:03.280 align:start position:0% operate on it so what we were trying to 00:38:03.280 --> 00:38:04.790 align:start position:0% operate on it so what we were trying to do<00:38:03.560> but<00:38:03.680> we<00:38:03.800> didn't<00:38:04.000> get<00:38:04.119> enough<00:38:04.319> sleep<00:38:04.680> this 00:38:04.790 --> 00:38:04.800 align:start position:0% do but we didn't get enough sleep this 00:38:04.800 --> 00:38:07.470 align:start position:0% do but we didn't get enough sleep this week<00:38:05.319> is<00:38:05.520> to<00:38:05.720> import<00:38:06.200> frogs<00:38:06.839> which<00:38:06.960> are<00:38:07.160> not 00:38:07.470 --> 00:38:07.480 align:start position:0% week is to import frogs which are not 00:38:07.480 --> 00:38:09.190 align:start position:0% week is to import frogs which are not nor<00:38:07.800> 16<00:38:08.200> pods<00:38:08.520> they're<00:38:08.720> different<00:38:08.960> kind<00:38:09.119> of 00:38:09.190 --> 00:38:09.200 align:start position:0% nor 16 pods they're different kind of 00:38:09.200 --> 00:38:10.349 align:start position:0% nor 16 pods they're different kind of cryptographic<00:38:09.720> data<00:38:09.920> and<00:38:10.040> then<00:38:10.160> do 00:38:10.349 --> 00:38:10.359 align:start position:0% cryptographic data and then do 00:38:10.359 --> 00:38:12.589 align:start position:0% cryptographic data and then do operations<00:38:10.720> on<00:38:10.880> our<00:38:11.040> frogs<00:38:11.760> right<00:38:12.119> so<00:38:12.280> as<00:38:12.400> an 00:38:12.589 --> 00:38:12.599 align:start position:0% operations on our frogs right so as an 00:38:12.599 --> 00:38:15.510 align:start position:0% operations on our frogs right so as an example<00:38:13.599> the<00:38:13.720> NFC<00:38:14.200> card<00:38:14.440> in<00:38:14.560> your<00:38:14.760> passport<00:38:15.359> is 00:38:15.510 --> 00:38:15.520 align:start position:0% example the NFC card in your passport is 00:38:15.520 --> 00:38:16.750 align:start position:0% example the NFC card in your passport is signed<00:38:15.880> by<00:38:16.000> the<00:38:16.160> public<00:38:16.400> key<00:38:16.560> of<00:38:16.640> your 00:38:16.750 --> 00:38:16.760 align:start position:0% signed by the public key of your 00:38:16.760 --> 00:38:18.990 align:start position:0% signed by the public key of your government<00:38:17.560> but<00:38:17.680> it's<00:38:17.920> using<00:38:18.280> some<00:38:18.599> garbage 00:38:18.990 --> 00:38:19.000 align:start position:0% government but it's using some garbage 00:38:19.000 --> 00:38:20.589 align:start position:0% government but it's using some garbage signature<00:38:19.520> scheme<00:38:19.880> it's<00:38:20.000> like<00:38:20.119> a<00:38:20.280> totally 00:38:20.589 --> 00:38:20.599 align:start position:0% signature scheme it's like a totally 00:38:20.599 --> 00:38:22.230 align:start position:0% signature scheme it's like a totally different<00:38:20.920> system<00:38:21.599> so<00:38:21.800> there<00:38:21.880> are<00:38:22.040> people 00:38:22.230 --> 00:38:22.240 align:start position:0% different system so there are people 00:38:22.240 --> 00:38:23.910 align:start position:0% different system so there are people today<00:38:22.520> that<00:38:22.640> build<00:38:22.920> bespoke<00:38:23.400> systems<00:38:23.760> to 00:38:23.910 --> 00:38:23.920 align:start position:0% today that build bespoke systems to 00:38:23.920 --> 00:38:25.670 align:start position:0% today that build bespoke systems to operate<00:38:24.200> on<00:38:24.400> passports<00:38:25.240> what<00:38:25.359> I<00:38:25.440> would<00:38:25.599> like 00:38:25.670 --> 00:38:25.680 align:start position:0% operate on passports what I would like 00:38:25.680 --> 00:38:27.069 align:start position:0% operate on passports what I would like to<00:38:25.760> do<00:38:25.880> is<00:38:26.000> be<00:38:26.079> able<00:38:26.200> to<00:38:26.319> import<00:38:26.599> a<00:38:26.720> passport<00:38:27.040> as 00:38:27.069 --> 00:38:27.079 align:start position:0% to do is be able to import a passport as 00:38:27.079 --> 00:38:28.710 align:start position:0% to do is be able to import a passport as a<00:38:27.200> part<00:38:27.680> and<00:38:27.800> everything<00:38:28.040> else<00:38:28.200> that<00:38:28.319> consumes 00:38:28.710 --> 00:38:28.720 align:start position:0% a part and everything else that consumes 00:38:28.720 --> 00:38:30.829 align:start position:0% a part and everything else that consumes part<00:38:28.960> two<00:38:29.480> and<00:38:29.760> does<00:38:29.960> operation<00:38:30.400> part<00:38:30.560> two<00:38:30.680> can 00:38:30.829 --> 00:38:30.839 align:start position:0% part two and does operation part two can 00:38:30.839 --> 00:38:33.470 align:start position:0% part two and does operation part two can use<00:38:31.000> it<00:38:31.480> so<00:38:31.640> on<00:38:31.760> the<00:38:31.960> verification<00:38:32.720> side<00:38:33.280> you 00:38:33.470 --> 00:38:33.480 align:start position:0% use it so on the verification side you 00:38:33.480 --> 00:38:35.790 align:start position:0% use it so on the verification side you do<00:38:33.760> need<00:38:34.200> the<00:38:34.400> person<00:38:34.720> or<00:38:34.880> the<00:38:35.079> company<00:38:35.520> or<00:38:35.640> the 00:38:35.790 --> 00:38:35.800 align:start position:0% do need the person or the company or the 00:38:35.800 --> 00:38:38.109 align:start position:0% do need the person or the company or the program<00:38:36.119> that<00:38:36.240> is<00:38:36.440> verifying<00:38:36.960> this<00:38:37.160> data<00:38:37.440> to 00:38:38.109 --> 00:38:38.119 align:start position:0% program that is verifying this data to 00:38:38.119 --> 00:38:40.270 align:start position:0% program that is verifying this data to accept<00:38:38.440> the<00:38:38.560> truth<00:38:38.839> of<00:38:39.000> that<00:38:39.200> data<00:38:39.760> so<00:38:39.920> in<00:38:40.040> some 00:38:40.270 --> 00:38:40.280 align:start position:0% accept the truth of that data so in some 00:38:40.280 --> 00:38:42.550 align:start position:0% accept the truth of that data so in some ways<00:38:40.960> you<00:38:41.119> don't<00:38:41.359> need<00:38:41.640> infrastructure<00:38:42.400> at 00:38:42.550 --> 00:38:42.560 align:start position:0% ways you don't need infrastructure at 00:38:42.560 --> 00:38:44.349 align:start position:0% ways you don't need infrastructure at the<00:38:42.720> attestation<00:38:43.319> side<00:38:43.839> because<00:38:44.040> we'll<00:38:44.240> just 00:38:44.349 --> 00:38:44.359 align:start position:0% the attestation side because we'll just 00:38:44.359 --> 00:38:45.950 align:start position:0% the attestation side because we'll just be<00:38:44.480> able<00:38:44.680> to<00:38:44.800> import<00:38:45.160> it<00:38:45.480> but<00:38:45.560> we<00:38:45.680> do<00:38:45.800> need 00:38:45.950 --> 00:38:45.960 align:start position:0% be able to import it but we do need 00:38:45.960 --> 00:38:47.870 align:start position:0% be able to import it but we do need infrastructure<00:38:46.440> at<00:38:46.560> the<00:38:46.680> verification<00:38:47.359> side 00:38:47.870 --> 00:38:47.880 align:start position:0% infrastructure at the verification side 00:38:47.880 --> 00:38:49.309 align:start position:0% infrastructure at the verification side so<00:38:48.160> I<00:38:48.240> think<00:38:48.440> the<00:38:48.560> way<00:38:48.680> we<00:38:48.800> should<00:38:48.960> start<00:38:49.200> with 00:38:49.309 --> 00:38:49.319 align:start position:0% so I think the way we should start with 00:38:49.319 --> 00:38:52.030 align:start position:0% so I think the way we should start with this<00:38:49.520> system<00:38:50.440> is<00:38:50.640> we<00:38:50.720> should<00:38:51.480> bring<00:38:51.640> it<00:38:51.760> to 00:38:52.030 --> 00:38:52.040 align:start position:0% this system is we should bring it to 00:38:52.040 --> 00:38:55.150 align:start position:0% this system is we should bring it to companies<00:38:52.839> not<00:38:53.079> governments<00:38:53.880> that<00:38:54.119> need<00:38:54.319> to 00:38:55.150 --> 00:38:55.160 align:start position:0% companies not governments that need to 00:38:55.160 --> 00:38:57.670 align:start position:0% companies not governments that need to like<00:38:55.720> essentially<00:38:56.720> compute<00:38:57.079> stuff<00:38:57.280> on<00:38:57.440> on<00:38:57.520> top 00:38:57.670 --> 00:38:57.680 align:start position:0% like essentially compute stuff on on top 00:38:57.680 --> 00:38:59.630 align:start position:0% like essentially compute stuff on on top of<00:38:57.800> official<00:38:58.200> data<00:38:58.920> and<00:38:59.040> instead<00:38:59.319> of<00:38:59.440> them 00:38:59.630 --> 00:38:59.640 align:start position:0% of official data and instead of them 00:38:59.640 --> 00:39:01.750 align:start position:0% of official data and instead of them having<00:38:59.839> to<00:38:59.960> pay<00:39:00.160> like<00:39:00.240> $3<00:39:00.880> per<00:39:01.079> verification 00:39:01.750 --> 00:39:01.760 align:start position:0% having to pay like $3 per verification 00:39:01.760 --> 00:39:03.430 align:start position:0% having to pay like $3 per verification for<00:39:01.960> something<00:39:02.280> like<00:39:02.480> Persona<00:39:03.160> where<00:39:03.319> they 00:39:03.430 --> 00:39:03.440 align:start position:0% for something like Persona where they 00:39:03.440 --> 00:39:05.109 align:start position:0% for something like Persona where they have<00:39:03.560> to<00:39:03.760> like<00:39:03.920> get<00:39:04.200> the<00:39:04.359> video<00:39:04.680> of<00:39:04.800> you<00:39:05.000> and 00:39:05.109 --> 00:39:05.119 align:start position:0% have to like get the video of you and 00:39:05.119 --> 00:39:06.790 align:start position:0% have to like get the video of you and your<00:39:05.240> passport<00:39:05.680> being<00:39:05.839> watched<00:39:06.160> by<00:39:06.280> someone 00:39:06.790 --> 00:39:06.800 align:start position:0% your passport being watched by someone 00:39:06.800 --> 00:39:09.109 align:start position:0% your passport being watched by someone they<00:39:06.960> can<00:39:07.079> just<00:39:07.240> accept<00:39:07.480> the<00:39:07.640> part<00:39:07.839> too<00:39:08.400> right 00:39:09.109 --> 00:39:09.119 align:start position:0% they can just accept the part too right 00:39:09.119 --> 00:39:10.109 align:start position:0% they can just accept the part too right so<00:39:09.319> of<00:39:09.440> course<00:39:09.599> they<00:39:09.680> would<00:39:09.839> have<00:39:09.920> to<00:39:10.000> make 00:39:10.109 --> 00:39:10.119 align:start position:0% so of course they would have to make 00:39:10.119 --> 00:39:11.349 align:start position:0% so of course they would have to make sure<00:39:10.240> that<00:39:10.359> all<00:39:10.520> this<00:39:10.640> stuff<00:39:10.800> is<00:39:10.880> audited 00:39:11.349 --> 00:39:11.359 align:start position:0% sure that all this stuff is audited 00:39:11.359 --> 00:39:12.910 align:start position:0% sure that all this stuff is audited works<00:39:11.599> correctly<00:39:12.040> but<00:39:12.200> I<00:39:12.280> think<00:39:12.480> the<00:39:12.640> way<00:39:12.800> to 00:39:12.910 --> 00:39:12.920 align:start position:0% works correctly but I think the way to 00:39:12.920 --> 00:39:14.309 align:start position:0% works correctly but I think the way to bring<00:39:13.119> this<00:39:13.240> to<00:39:13.400> Market<00:39:13.680> sorry<00:39:13.920> we're<00:39:14.079> going 00:39:14.309 --> 00:39:14.319 align:start position:0% bring this to Market sorry we're going 00:39:14.319 --> 00:39:16.150 align:start position:0% bring this to Market sorry we're going way<00:39:14.440> out<00:39:14.599> of<00:39:14.720> bound<00:39:14.960> of<00:39:15.040> this<00:39:15.200> Workshop<00:39:15.640> now<00:39:16.040> is 00:39:16.150 --> 00:39:16.160 align:start position:0% way out of bound of this Workshop now is 00:39:16.160 --> 00:39:19.109 align:start position:0% way out of bound of this Workshop now is to<00:39:16.359> go<00:39:16.599> to<00:39:17.119> to<00:39:17.599> people<00:39:17.960> that<00:39:18.119> need<00:39:18.640> data<00:39:18.920> from 00:39:19.109 --> 00:39:19.119 align:start position:0% to go to to people that need data from 00:39:19.119 --> 00:39:20.990 align:start position:0% to go to to people that need data from other<00:39:19.319> sources<00:39:19.880> that<00:39:20.000> needs<00:39:20.160> to<00:39:20.280> be<00:39:20.480> processed 00:39:20.990 --> 00:39:21.000 align:start position:0% other sources that needs to be processed 00:39:21.000 --> 00:39:22.630 align:start position:0% other sources that needs to be processed in<00:39:21.119> a<00:39:21.240> way<00:39:21.480> where<00:39:21.680> it's<00:39:21.920> cheaper<00:39:22.200> for<00:39:22.359> them<00:39:22.480> to 00:39:22.630 --> 00:39:22.640 align:start position:0% in a way where it's cheaper for them to 00:39:22.640 --> 00:39:23.430 align:start position:0% in a way where it's cheaper for them to do 00:39:23.430 --> 00:39:23.440 align:start position:0% do 00:39:23.440 --> 00:39:28.349 align:start position:0% do so<00:39:24.440> and<00:39:25.040> last<00:39:25.359> question<00:39:26.000> building<00:39:26.359> on<00:39:26.599> that 00:39:28.349 --> 00:39:28.359 align:start position:0% so and last question building on that 00:39:28.359 --> 00:39:31.430 align:start position:0% so and last question building on that the<00:39:28.560> verifier<00:39:29.280> what<00:39:29.400> does<00:39:29.960> what<00:39:30.079> do<00:39:30.280> they<00:39:30.440> need 00:39:31.430 --> 00:39:31.440 align:start position:0% the verifier what does what do they need 00:39:31.440 --> 00:39:33.309 align:start position:0% the verifier what does what do they need the<00:39:31.560> verifier<00:39:32.280> yes<00:39:32.520> they<00:39:32.640> just<00:39:32.720> need<00:39:32.880> a<00:39:32.960> lower 00:39:33.309 --> 00:39:33.319 align:start position:0% the verifier yes they just need a lower 00:39:33.319 --> 00:39:35.430 align:start position:0% the verifier yes they just need a lower program<00:39:34.119> and<00:39:34.200> then<00:39:34.400> what<00:39:34.560> they<00:39:34.760> they<00:39:34.960> get<00:39:35.280> and 00:39:35.430 --> 00:39:35.440 align:start position:0% program and then what they they get and 00:39:35.440 --> 00:39:38.069 align:start position:0% program and then what they they get and they<00:39:35.599> need<00:39:35.800> the<00:39:36.119> public<00:39:36.560> keys<00:39:37.560> they<00:39:37.720> need 00:39:38.069 --> 00:39:38.079 align:start position:0% they need the public keys they need 00:39:38.079 --> 00:39:41.430 align:start position:0% they need the public keys they need anything<00:39:38.800> that's<00:39:39.200> part<00:39:39.720> of<00:39:40.119> the<00:39:40.599> axiomatic 00:39:41.430 --> 00:39:41.440 align:start position:0% anything that's part of the axiomatic 00:39:41.440 --> 00:39:43.950 align:start position:0% anything that's part of the axiomatic pod<00:39:41.800> to<00:39:42.040> tie<00:39:42.280> them<00:39:42.440> to<00:39:42.720> reality<00:39:43.440> so<00:39:43.680> it<00:39:43.800> might 00:39:43.950 --> 00:39:43.960 align:start position:0% pod to tie them to reality so it might 00:39:43.960 --> 00:39:46.109 align:start position:0% pod to tie them to reality so it might be<00:39:44.160> public<00:39:44.480> Keys<00:39:44.800> it<00:39:44.920> might<00:39:45.079> be<00:39:45.240> certificate 00:39:46.109 --> 00:39:46.119 align:start position:0% be public Keys it might be certificate 00:39:46.119 --> 00:39:48.030 align:start position:0% be public Keys it might be certificate Authority<00:39:46.839> it's<00:39:47.040> it's<00:39:47.359> it<00:39:47.440> will<00:39:47.640> depend<00:39:47.920> on 00:39:48.030 --> 00:39:48.040 align:start position:0% Authority it's it's it will depend on 00:39:48.040 --> 00:39:50.510 align:start position:0% Authority it's it's it will depend on each<00:39:48.240> use<00:39:48.599> case<00:39:49.079> and<00:39:49.280> the<00:39:49.480> resulting<00:39:50.079> Port<00:39:50.400> but 00:39:50.510 --> 00:39:50.520 align:start position:0% each use case and the resulting Port but 00:39:50.520 --> 00:39:52.150 align:start position:0% each use case and the resulting Port but not<00:39:50.680> the<00:39:50.839> input<00:39:51.200> ports<00:39:51.640> no<00:39:51.800> they<00:39:51.880> don't<00:39:52.040> need 00:39:52.150 --> 00:39:52.160 align:start position:0% not the input ports no they don't need 00:39:52.160 --> 00:39:53.190 align:start position:0% not the input ports no they don't need the<00:39:52.240> input<00:39:52.520> Parts<00:39:52.760> they<00:39:52.839> don't<00:39:52.960> need<00:39:53.079> the 00:39:53.190 --> 00:39:53.200 align:start position:0% the input Parts they don't need the 00:39:53.200 --> 00:39:56.309 align:start position:0% the input Parts they don't need the computational<00:39:53.960> graphs<00:39:54.960> yeah<00:39:55.920> thank<00:39:56.079> you 00:39:56.309 --> 00:39:56.319 align:start position:0% computational graphs yeah thank you 00:39:56.319 --> 00:40:00.309 align:start position:0% computational graphs yeah thank you thank<00:39:56.440> you<00:39:56.520> for<00:39:56.640> your<00:39:56.800> questions 00:40:00.309 --> 00:40:00.319 align:start position:0% 00:40:00.319 --> 00:40:04.829 align:start position:0% there's<00:40:00.520> a<00:40:00.640> question<00:40:00.920> the<00:40:01.040> front 00:40:04.829 --> 00:40:04.839 align:start position:0% 00:40:04.839 --> 00:40:08.309 align:start position:0% aruro<00:40:05.839> thanks<00:40:06.640> um<00:40:07.119> so<00:40:07.359> this<00:40:07.560> language<00:40:07.960> is<00:40:08.200> kind 00:40:08.309 --> 00:40:08.319 align:start position:0% aruro thanks um so this language is kind 00:40:08.319 --> 00:40:10.550 align:start position:0% aruro thanks um so this language is kind of<00:40:08.520> like<00:40:08.800> a<00:40:09.200> relational<00:40:09.839> algebra<00:40:10.319> the<00:40:10.440> way 00:40:10.550 --> 00:40:10.560 align:start position:0% of like a relational algebra the way 00:40:10.560 --> 00:40:12.790 align:start position:0% of like a relational algebra the way that<00:40:10.680> it's<00:40:11.079> yes<00:40:11.280> it's<00:40:11.400> like<00:40:11.640> prologue<00:40:12.480> yeah 00:40:12.790 --> 00:40:12.800 align:start position:0% that it's yes it's like prologue yeah 00:40:12.800 --> 00:40:15.910 align:start position:0% that it's yes it's like prologue yeah and<00:40:12.960> so<00:40:13.839> um<00:40:14.200> when<00:40:14.319> we're<00:40:14.480> saying<00:40:14.839> that<00:40:15.200> we<00:40:15.400> have 00:40:15.910 --> 00:40:15.920 align:start position:0% and so um when we're saying that we have 00:40:15.920 --> 00:40:18.790 align:start position:0% and so um when we're saying that we have the<00:40:16.160> programs<00:40:16.680> now<00:40:17.560> are<00:40:17.839> approvable<00:40:18.520> in<00:40:18.640> the 00:40:18.790 --> 00:40:18.800 align:start position:0% the programs now are approvable in the 00:40:18.800 --> 00:40:22.150 align:start position:0% the programs now are approvable in the sense<00:40:19.040> that<00:40:19.240> if<00:40:19.560> you<00:40:20.560> listed<00:40:21.119> the<00:40:21.599> queries<00:40:22.000> and 00:40:22.150 --> 00:40:22.160 align:start position:0% sense that if you listed the queries and 00:40:22.160 --> 00:40:25.710 align:start position:0% sense that if you listed the queries and maybe<00:40:22.400> the<00:40:22.839> lines<00:40:23.839> of<00:40:24.560> evaluation<00:40:25.319> you<00:40:25.480> could 00:40:25.710 --> 00:40:25.720 align:start position:0% maybe the lines of evaluation you could 00:40:25.720 --> 00:40:28.069 align:start position:0% maybe the lines of evaluation you could use<00:40:26.000> some<00:40:26.400> rules<00:40:26.680> of<00:40:26.839> inference<00:40:27.400> to<00:40:27.599> say<00:40:27.839> that 00:40:28.069 --> 00:40:28.079 align:start position:0% use some rules of inference to say that 00:40:28.079 --> 00:40:30.069 align:start position:0% use some rules of inference to say that these<00:40:28.520> are<00:40:28.839> this<00:40:29.079> computation<00:40:29.599> is<00:40:29.760> done<00:40:29.960> by 00:40:30.069 --> 00:40:30.079 align:start position:0% these are this computation is done by 00:40:30.079 --> 00:40:33.309 align:start position:0% these are this computation is done by rules<00:40:30.319> of<00:40:30.480> inference<00:40:31.000> and<00:40:31.160> not<00:40:31.400> by<00:40:32.319> evaluation 00:40:33.309 --> 00:40:33.319 align:start position:0% rules of inference and not by evaluation 00:40:33.319 --> 00:40:35.630 align:start position:0% rules of inference and not by evaluation and<00:40:33.520> then<00:40:33.960> when<00:40:34.119> we<00:40:34.240> talk<00:40:34.480> about<00:40:34.720> the<00:40:34.960> zero<00:40:35.480> the 00:40:35.630 --> 00:40:35.640 align:start position:0% and then when we talk about the zero the 00:40:35.640 --> 00:40:38.109 align:start position:0% and then when we talk about the zero the zero<00:40:35.960> knowledge<00:40:36.440> proof<00:40:37.200> you're<00:40:37.520> going<00:40:37.760> to 00:40:38.109 --> 00:40:38.119 align:start position:0% zero knowledge proof you're going to 00:40:38.119 --> 00:40:40.950 align:start position:0% zero knowledge proof you're going to write<00:40:38.319> a<00:40:38.520> verifier<00:40:39.079> of<00:40:39.240> that<00:40:39.640> algebra<00:40:40.200> and 00:40:40.950 --> 00:40:40.960 align:start position:0% write a verifier of that algebra and 00:40:40.960 --> 00:40:44.270 align:start position:0% write a verifier of that algebra and snark<00:40:41.520> the<00:40:41.839> verifier<00:40:42.440> of<00:40:42.599> this<00:40:42.760> algebra<00:40:43.480> yeah 00:40:44.270 --> 00:40:44.280 align:start position:0% snark the verifier of this algebra yeah 00:40:44.280 --> 00:40:45.430 align:start position:0% snark the verifier of this algebra yeah I<00:40:44.359> just<00:40:44.480> wanted<00:40:44.640> to<00:40:44.720> make<00:40:44.800> sure<00:40:44.960> I<00:40:45.280> understand 00:40:45.430 --> 00:40:45.440 align:start position:0% I just wanted to make sure I understand 00:40:45.440 --> 00:40:46.950 align:start position:0% I just wanted to make sure I understand the<00:40:45.599> two<00:40:45.920> steps<00:40:46.200> of<00:40:46.400> like<00:40:46.640> because<00:40:46.760> there's 00:40:46.950 --> 00:40:46.960 align:start position:0% the two steps of like because there's 00:40:46.960 --> 00:40:49.430 align:start position:0% the two steps of like because there's two<00:40:47.200> proofs<00:40:47.560> going<00:40:47.720> on<00:40:48.000> one<00:40:48.400> two<00:40:48.520> proofs<00:40:48.960> yeah 00:40:49.430 --> 00:40:49.440 align:start position:0% two proofs going on one two proofs yeah 00:40:49.440 --> 00:40:50.790 align:start position:0% two proofs going on one two proofs yeah it's<00:40:49.599> kind<00:40:49.720> of<00:40:49.800> like<00:40:49.960> this<00:40:50.119> pi<00:40:50.359> squared 00:40:50.790 --> 00:40:50.800 align:start position:0% it's kind of like this pi squared 00:40:50.800 --> 00:40:52.470 align:start position:0% it's kind of like this pi squared project<00:40:51.079> that<00:40:51.200> I<00:40:51.319> heard<00:40:51.520> about<00:40:51.680> earlier<00:40:52.200> this 00:40:52.470 --> 00:40:52.480 align:start position:0% project that I heard about earlier this 00:40:52.480 --> 00:40:54.430 align:start position:0% project that I heard about earlier this week<00:40:52.880> a<00:40:53.000> little<00:40:53.200> bit<00:40:53.720> Yeah<00:40:53.920> they<00:40:54.000> used<00:40:54.160> the<00:40:54.319> K 00:40:54.430 --> 00:40:54.440 align:start position:0% week a little bit Yeah they used the K 00:40:54.440 --> 00:40:56.230 align:start position:0% week a little bit Yeah they used the K framework<00:40:55.119> yeah<00:40:55.280> but<00:40:55.359> in<00:40:55.440> the<00:40:55.560> similar<00:40:55.960> way 00:40:56.230 --> 00:40:56.240 align:start position:0% framework yeah but in the similar way 00:40:56.240 --> 00:40:58.150 align:start position:0% framework yeah but in the similar way like<00:40:56.400> they<00:40:56.520> have<00:40:56.640> this<00:40:56.760> front<00:40:57.000> l<00:40:57.640> that's 00:40:58.150 --> 00:40:58.160 align:start position:0% like they have this front l that's 00:40:58.160 --> 00:41:00.030 align:start position:0% like they have this front l that's provable<00:40:58.640> in<00:40:58.760> some<00:40:58.960> other<00:40:59.200> sense<00:40:59.480> of<00:40:59.599> the<00:40:59.760> word 00:41:00.030 --> 00:41:00.040 align:start position:0% provable in some other sense of the word 00:41:00.040 --> 00:41:02.030 align:start position:0% provable in some other sense of the word that<00:41:00.760> yeah<00:41:01.160> correct<00:41:01.520> and<00:41:01.599> then<00:41:01.680> I<00:41:01.760> have<00:41:01.880> a 00:41:02.030 --> 00:41:02.040 align:start position:0% that yeah correct and then I have a 00:41:02.040 --> 00:41:04.390 align:start position:0% that yeah correct and then I have a question<00:41:02.720> so<00:41:02.920> lisp<00:41:03.280> is<00:41:03.440> cool<00:41:03.760> because<00:41:04.040> it's 00:41:04.390 --> 00:41:04.400 align:start position:0% question so lisp is cool because it's 00:41:04.400 --> 00:41:08.349 align:start position:0% question so lisp is cool because it's also<00:41:04.800> like<00:41:05.040> homo<00:41:05.480> ionic<00:41:06.040> so<00:41:06.480> lisp<00:41:06.960> is<00:41:07.640> data 00:41:08.349 --> 00:41:08.359 align:start position:0% also like homo ionic so lisp is data 00:41:08.359 --> 00:41:10.630 align:start position:0% also like homo ionic so lisp is data code<00:41:08.680> is<00:41:08.880> data<00:41:09.440> and<00:41:09.599> we're<00:41:09.920> just<00:41:10.280> giving 00:41:10.630 --> 00:41:10.640 align:start position:0% code is data and we're just giving 00:41:10.640 --> 00:41:12.109 align:start position:0% code is data and we're just giving examples<00:41:11.119> that's<00:41:11.359> pretty<00:41:11.599> similar<00:41:11.880> to<00:41:12.000> the 00:41:12.109 --> 00:41:12.119 align:start position:0% examples that's pretty similar to the 00:41:12.119 --> 00:41:13.470 align:start position:0% examples that's pretty similar to the normal<00:41:12.440> data<00:41:12.680> that<00:41:12.760> we're<00:41:12.880> used<00:41:13.079> to<00:41:13.280> looking 00:41:13.470 --> 00:41:13.480 align:start position:0% normal data that we're used to looking 00:41:13.480 --> 00:41:15.710 align:start position:0% normal data that we're used to looking at<00:41:14.040> is<00:41:14.160> there<00:41:14.280> a<00:41:14.440> way<00:41:14.640> that<00:41:14.800> you<00:41:14.920> can<00:41:15.160> leverage 00:41:15.710 --> 00:41:15.720 align:start position:0% at is there a way that you can leverage 00:41:15.720 --> 00:41:19.670 align:start position:0% at is there a way that you can leverage this<00:41:16.599> fact<00:41:16.880> that<00:41:17.119> code<00:41:17.440> is<00:41:17.640> also<00:41:18.119> data<00:41:18.680> in<00:41:19.520> in 00:41:19.670 --> 00:41:19.680 align:start position:0% this fact that code is also data in in 00:41:19.680 --> 00:41:21.390 align:start position:0% this fact that code is also data in in this<00:41:19.839> framework<00:41:20.280> or<00:41:20.440> that's<00:41:20.680> I<00:41:20.760> mean<00:41:21.000> probably 00:41:21.390 --> 00:41:21.400 align:start position:0% this framework or that's I mean probably 00:41:21.400 --> 00:41:23.589 align:start position:0% this framework or that's I mean probably far<00:41:21.599> out<00:41:21.880> future<00:41:22.359> but<00:41:23.040> yeah<00:41:23.200> so<00:41:23.319> this<00:41:23.400> is<00:41:23.480> a 00:41:23.589 --> 00:41:23.599 align:start position:0% far out future but yeah so this is a 00:41:23.599 --> 00:41:25.150 align:start position:0% far out future but yeah so this is a great<00:41:23.880> question<00:41:24.280> and<00:41:24.400> you<00:41:24.480> will<00:41:24.680> need<00:41:24.839> to<00:41:24.960> do 00:41:25.150 --> 00:41:25.160 align:start position:0% great question and you will need to do 00:41:25.160 --> 00:41:26.829 align:start position:0% great question and you will need to do this<00:41:25.359> when<00:41:25.480> you<00:41:25.599> start<00:41:25.880> doing<00:41:26.400> first<00:41:26.680> and 00:41:26.829 --> 00:41:26.839 align:start position:0% this when you start doing first and 00:41:26.839 --> 00:41:29.550 align:start position:0% this when you start doing first and second<00:41:27.040> order<00:41:27.560> logic<00:41:28.400> cuz<00:41:28.560> you<00:41:28.680> know<00:41:29.240> this 00:41:29.550 --> 00:41:29.560 align:start position:0% second order logic cuz you know this 00:41:29.560 --> 00:41:31.109 align:start position:0% second order logic cuz you know this this<00:41:29.800> logic<00:41:30.119> that<00:41:30.200> we<00:41:30.319> have<00:41:30.480> right<00:41:30.640> now<00:41:30.800> is<00:41:30.880> a 00:41:31.109 --> 00:41:31.119 align:start position:0% this logic that we have right now is a 00:41:31.119 --> 00:41:34.349 align:start position:0% this logic that we have right now is a bastard<00:41:31.760> propositional<00:41:32.680> logic<00:41:33.680> uh<00:41:34.040> it<00:41:34.160> has 00:41:34.349 --> 00:41:34.359 align:start position:0% bastard propositional logic uh it has 00:41:34.359 --> 00:41:36.069 align:start position:0% bastard propositional logic uh it has numbers<00:41:34.720> usually<00:41:35.000> propositional<00:41:35.560> L<00:41:35.880> doesn't 00:41:36.069 --> 00:41:36.079 align:start position:0% numbers usually propositional L doesn't 00:41:36.079 --> 00:41:37.510 align:start position:0% numbers usually propositional L doesn't have<00:41:36.240> numbers<00:41:36.599> it<00:41:36.720> just<00:41:36.839> has<00:41:37.040> statements 00:41:37.510 --> 00:41:37.520 align:start position:0% have numbers it just has statements 00:41:37.520 --> 00:41:39.230 align:start position:0% have numbers it just has statements about<00:41:37.760> stuff<00:41:37.960> like<00:41:38.119> it<00:41:38.240> is<00:41:38.400> raining<00:41:38.839> or<00:41:39.000> it<00:41:39.079> is 00:41:39.230 --> 00:41:39.240 align:start position:0% about stuff like it is raining or it is 00:41:39.240 --> 00:41:41.589 align:start position:0% about stuff like it is raining or it is not<00:41:39.440> raining<00:41:39.920> here<00:41:40.079> we<00:41:40.200> have<00:41:40.440> numbers<00:41:41.440> if<00:41:41.520> you 00:41:41.589 --> 00:41:41.599 align:start position:0% not raining here we have numbers if you 00:41:41.599 --> 00:41:43.589 align:start position:0% not raining here we have numbers if you don't<00:41:41.800> have<00:41:41.960> numbers<00:41:42.480> for<00:41:42.680> the<00:41:42.839> ultra<00:41:43.280> nerds 00:41:43.589 --> 00:41:43.599 align:start position:0% don't have numbers for the ultra nerds 00:41:43.599 --> 00:41:44.950 align:start position:0% don't have numbers for the ultra nerds here<00:41:43.800> you<00:41:43.920> would<00:41:44.079> have<00:41:44.200> to<00:41:44.319> do<00:41:44.440> it<00:41:44.560> in<00:41:44.640> a<00:41:44.800> way 00:41:44.950 --> 00:41:44.960 align:start position:0% here you would have to do it in a way 00:41:44.960 --> 00:41:47.030 align:start position:0% here you would have to do it in a way where<00:41:45.119> you<00:41:45.319> define<00:41:45.920> the<00:41:46.119> zero<00:41:46.520> number<00:41:46.920> and 00:41:47.030 --> 00:41:47.040 align:start position:0% where you define the zero number and 00:41:47.040 --> 00:41:49.349 align:start position:0% where you define the zero number and then<00:41:47.160> you<00:41:47.280> define<00:41:47.839> successor<00:41:48.720> and<00:41:48.800> so<00:41:49.040> three 00:41:49.349 --> 00:41:49.359 align:start position:0% then you define successor and so three 00:41:49.359 --> 00:41:51.069 align:start position:0% then you define successor and so three is<00:41:49.560> successor<00:41:50.000> of<00:41:50.160> successor<00:41:50.560> of<00:41:50.720> successor 00:41:51.069 --> 00:41:51.079 align:start position:0% is successor of successor of successor 00:41:51.079 --> 00:41:52.470 align:start position:0% is successor of successor of successor of<00:41:51.200> zero<00:41:51.480> but<00:41:51.599> then<00:41:51.720> you<00:41:51.800> see<00:41:51.920> how<00:41:52.079> narly<00:41:52.400> it 00:41:52.470 --> 00:41:52.480 align:start position:0% of zero but then you see how narly it 00:41:52.480 --> 00:41:54.349 align:start position:0% of zero but then you see how narly it gets<00:41:52.680> very<00:41:52.839> quickly<00:41:53.319> so<00:41:53.440> we<00:41:53.599> added<00:41:53.839> numbers<00:41:54.160> to 00:41:54.349 --> 00:41:54.359 align:start position:0% gets very quickly so we added numbers to 00:41:54.359 --> 00:41:56.630 align:start position:0% gets very quickly so we added numbers to propositional<00:41:55.040> logic<00:41:56.040> if<00:41:56.160> you<00:41:56.240> want<00:41:56.359> to<00:41:56.480> do 00:41:56.630 --> 00:41:56.640 align:start position:0% propositional logic if you want to do 00:41:56.640 --> 00:41:58.069 align:start position:0% propositional logic if you want to do first<00:41:56.880> order<00:41:57.240> logic<00:41:57.560> you're<00:41:57.720> going<00:41:57.800> to<00:41:57.920> need 00:41:58.069 --> 00:41:58.079 align:start position:0% first order logic you're going to need 00:41:58.079 --> 00:42:00.349 align:start position:0% first order logic you're going to need to<00:41:58.160> be<00:41:58.280> able<00:41:58.480> to<00:41:58.680> manipulate<00:41:59.359> statements<00:42:00.119> via 00:42:00.349 --> 00:42:00.359 align:start position:0% to be able to manipulate statements via 00:42:00.359 --> 00:42:01.550 align:start position:0% to be able to manipulate statements via other<00:42:00.599> statements<00:42:01.040> like<00:42:01.200> groups<00:42:01.440> of 00:42:01.550 --> 00:42:01.560 align:start position:0% other statements like groups of 00:42:01.560 --> 00:42:03.349 align:start position:0% other statements like groups of statements<00:42:01.920> via<00:42:02.119> other<00:42:02.319> statements<00:42:02.760> and<00:42:02.880> so 00:42:03.349 --> 00:42:03.359 align:start position:0% statements via other statements and so 00:42:03.359 --> 00:42:06.349 align:start position:0% statements via other statements and so the<00:42:04.040> the<00:42:04.760> the<00:42:04.880> semantic<00:42:05.359> of<00:42:05.520> lisp<00:42:05.839> will<00:42:06.040> help 00:42:06.349 --> 00:42:06.359 align:start position:0% the the the semantic of lisp will help 00:42:06.359 --> 00:42:08.430 align:start position:0% the the the semantic of lisp will help here<00:42:06.640> quite<00:42:06.839> a<00:42:06.960> bit<00:42:07.520> like<00:42:07.720> I<00:42:07.839> I<00:42:07.920> could<00:42:08.119> imagine 00:42:08.430 --> 00:42:08.440 align:start position:0% here quite a bit like I I could imagine 00:42:08.440 --> 00:42:10.870 align:start position:0% here quite a bit like I I could imagine how<00:42:08.560> this<00:42:08.680> would<00:42:08.839> be<00:42:08.960> useful<00:42:09.640> but<00:42:10.079> we<00:42:10.680> that's 00:42:10.870 --> 00:42:10.880 align:start position:0% how this would be useful but we that's 00:42:10.880 --> 00:42:12.950 align:start position:0% how this would be useful but we that's where<00:42:11.040> we<00:42:11.160> stopped<00:42:11.839> yeah<00:42:12.000> so<00:42:12.160> the<00:42:12.319> lisp<00:42:12.680> is<00:42:12.920> I 00:42:12.950 --> 00:42:12.960 align:start position:0% where we stopped yeah so the lisp is I 00:42:12.960 --> 00:42:14.750 align:start position:0% where we stopped yeah so the lisp is I mean<00:42:13.160> it's<00:42:13.920> you<00:42:14.079> said<00:42:14.280> it's<00:42:14.480> just<00:42:14.599> a 00:42:14.750 --> 00:42:14.760 align:start position:0% mean it's you said it's just a 00:42:14.760 --> 00:42:16.990 align:start position:0% mean it's you said it's just a convenience<00:42:15.240> for<00:42:15.800> defining<00:42:16.240> a<00:42:16.400> language<00:42:16.800> but 00:42:16.990 --> 00:42:17.000 align:start position:0% convenience for defining a language but 00:42:17.000 --> 00:42:19.230 align:start position:0% convenience for defining a language but actually<00:42:17.560> you<00:42:17.760> might<00:42:18.280> keep<00:42:18.480> it<00:42:18.760> because<00:42:19.000> it's 00:42:19.230 --> 00:42:19.240 align:start position:0% actually you might keep it because it's 00:42:19.240 --> 00:42:21.710 align:start position:0% actually you might keep it because it's useful<00:42:19.920> yeah<00:42:20.079> it's<00:42:20.319> possible<00:42:20.960> yes<00:42:21.359> the<00:42:21.440> reason 00:42:21.710 --> 00:42:21.720 align:start position:0% useful yeah it's possible yes the reason 00:42:21.720 --> 00:42:23.150 align:start position:0% useful yeah it's possible yes the reason why<00:42:21.800> I<00:42:21.880> say<00:42:22.040> that<00:42:22.160> is<00:42:22.319> because<00:42:22.720> because<00:42:22.960> people 00:42:23.150 --> 00:42:23.160 align:start position:0% why I say that is because because people 00:42:23.160 --> 00:42:26.230 align:start position:0% why I say that is because because people get<00:42:23.319> spooked<00:42:23.760> out<00:42:24.480> by<00:42:24.640> the<00:42:24.760> lisp<00:42:25.760> like<00:42:25.960> oh<00:42:26.119> this 00:42:26.230 --> 00:42:26.240 align:start position:0% get spooked out by the lisp like oh this 00:42:26.240 --> 00:42:28.030 align:start position:0% get spooked out by the lisp like oh this is<00:42:26.440> amazing<00:42:26.920> but<00:42:27.200> I<00:42:27.280> will<00:42:27.440> never<00:42:27.640> use<00:42:27.800> it 00:42:28.030 --> 00:42:28.040 align:start position:0% is amazing but I will never use it 00:42:28.040 --> 00:42:29.510 align:start position:0% is amazing but I will never use it because<00:42:28.240> it's<00:42:28.359> a<00:42:28.480> lisp<00:42:28.839> you<00:42:28.920> know<00:42:29.240> if<00:42:29.359> there 00:42:29.510 --> 00:42:29.520 align:start position:0% because it's a lisp you know if there 00:42:29.520 --> 00:42:31.510 align:start position:0% because it's a lisp you know if there was<00:42:29.640> a<00:42:29.839> space<00:42:30.160> elevator<00:42:30.880> that<00:42:31.040> required<00:42:31.440> you 00:42:31.510 --> 00:42:31.520 align:start position:0% was a space elevator that required you 00:42:31.520 --> 00:42:32.990 align:start position:0% was a space elevator that required you to<00:42:31.640> write<00:42:31.800> some<00:42:31.960> lisp<00:42:32.240> to<00:42:32.359> go<00:42:32.440> on<00:42:32.559> a<00:42:32.680> bunch<00:42:32.839> of 00:42:32.990 --> 00:42:33.000 align:start position:0% to write some lisp to go on a bunch of 00:42:33.000 --> 00:42:35.030 align:start position:0% to write some lisp to go on a bunch of people<00:42:33.200> would<00:42:33.400> not<00:42:34.160> they<00:42:34.359> be<00:42:34.520> like<00:42:34.680> it's<00:42:34.800> just 00:42:35.030 --> 00:42:35.040 align:start position:0% people would not they be like it's just 00:42:35.040 --> 00:42:37.150 align:start position:0% people would not they be like it's just too<00:42:35.280> hard<00:42:35.520> that's<00:42:35.640> a<00:42:35.760> good<00:42:35.880> way<00:42:35.960> of<00:42:36.079> putting 00:42:37.150 --> 00:42:37.160 align:start position:0% too hard that's a good way of putting 00:42:37.160 --> 00:42:41.270 align:start position:0% too hard that's a good way of putting it<00:42:38.280> thanks<00:42:39.280> cool<00:42:40.040> uh<00:42:40.200> if<00:42:40.359> anyone<00:42:40.680> keeps<00:42:41.160> like 00:42:41.270 --> 00:42:41.280 align:start position:0% it thanks cool uh if anyone keeps like 00:42:41.280 --> 00:42:42.860 align:start position:0% it thanks cool uh if anyone keeps like if<00:42:41.400> you<00:42:41.640> oh<00:42:41.960> more<00:42:42.160> questions<00:42:42.559> let's 00:42:42.860 --> 00:42:42.870 align:start position:0% if you oh more questions let's 00:42:42.870 --> 00:42:44.109 align:start position:0% if you oh more questions let's [Music] 00:42:44.109 --> 00:42:44.119 align:start position:0% [Music] 00:42:44.119 --> 00:42:46.870 align:start position:0% [Music] go<00:42:45.119> thanks<00:42:45.319> for<00:42:45.480> the<00:42:45.680> introduction<00:42:46.599> uh<00:42:46.720> more 00:42:46.870 --> 00:42:46.880 align:start position:0% go thanks for the introduction uh more 00:42:46.880 --> 00:42:50.390 align:start position:0% go thanks for the introduction uh more on<00:42:47.079> the<00:42:47.319> verification<00:42:48.520> side<00:42:49.520> um<00:42:49.839> the<00:42:50.000> premise 00:42:50.390 --> 00:42:50.400 align:start position:0% on the verification side um the premise 00:42:50.400 --> 00:42:53.950 align:start position:0% on the verification side um the premise of<00:42:50.599> that<00:42:50.839> is<00:42:51.599> you<00:42:51.920> trust<00:42:52.720> this<00:42:52.920> blob<00:42:53.280> of<00:42:53.480> data 00:42:53.950 --> 00:42:53.960 align:start position:0% of that is you trust this blob of data 00:42:53.960 --> 00:42:56.430 align:start position:0% of that is you trust this blob of data in<00:42:54.079> the<00:42:54.280> pot<00:42:54.760> that<00:42:54.880> is<00:42:55.160> issued<00:42:55.680> by<00:42:55.960> someone 00:42:56.430 --> 00:42:56.440 align:start position:0% in the pot that is issued by someone 00:42:56.440 --> 00:42:57.670 align:start position:0% in the pot that is issued by someone right<00:42:56.599> to<00:42:56.720> be<00:42:56.839> authentic 00:42:57.670 --> 00:42:57.680 align:start position:0% right to be authentic 00:42:57.680 --> 00:43:00.430 align:start position:0% right to be authentic yeah<00:42:57.800> so<00:42:58.040> here<00:42:58.240> you<00:42:58.400> do<00:42:58.559> not<00:42:58.800> trust<00:42:59.200> these<00:42:59.520> guys 00:43:00.430 --> 00:43:00.440 align:start position:0% yeah so here you do not trust these guys 00:43:00.440 --> 00:43:04.390 align:start position:0% yeah so here you do not trust these guys you<00:43:00.680> only<00:43:01.119> trust<00:43:02.119> um<00:43:02.760> these<00:43:03.400> original<00:43:04.040> pods 00:43:04.390 --> 00:43:04.400 align:start position:0% you only trust um these original pods 00:43:04.400 --> 00:43:06.510 align:start position:0% you only trust um these original pods that<00:43:04.480> were<00:43:04.720> created<00:43:05.440> here<00:43:05.800> yes<00:43:06.040> based<00:43:06.240> on<00:43:06.359> the 00:43:06.510 --> 00:43:06.520 align:start position:0% that were created here yes based on the 00:43:06.520 --> 00:43:08.670 align:start position:0% that were created here yes based on the public<00:43:06.760> keys<00:43:07.200> right<00:43:07.599> or<00:43:07.839> anything<00:43:08.119> else<00:43:08.599> it 00:43:08.670 --> 00:43:08.680 align:start position:0% public keys right or anything else it 00:43:08.680 --> 00:43:10.109 align:start position:0% public keys right or anything else it could<00:43:08.800> have<00:43:08.920> been<00:43:09.079> imported<00:43:09.440> from<00:43:09.599> an<00:43:09.720> email 00:43:10.109 --> 00:43:10.119 align:start position:0% could have been imported from an email 00:43:10.119 --> 00:43:11.870 align:start position:0% could have been imported from an email and<00:43:10.280> it<00:43:10.400> would<00:43:10.520> be<00:43:10.680> based<00:43:10.920> on<00:43:11.079> who<00:43:11.280> sent<00:43:11.720> the 00:43:11.870 --> 00:43:11.880 align:start position:0% and it would be based on who sent the 00:43:11.880 --> 00:43:14.309 align:start position:0% and it would be based on who sent the email<00:43:12.480> it<00:43:12.599> could<00:43:12.760> come<00:43:13.079> like<00:43:13.480> it's<00:43:14.000> it<00:43:14.119> doesn't 00:43:14.309 --> 00:43:14.319 align:start position:0% email it could come like it's it doesn't 00:43:14.319 --> 00:43:15.950 align:start position:0% email it could come like it's it doesn't matter<00:43:14.599> it's<00:43:14.720> based<00:43:14.920> on<00:43:15.160> some<00:43:15.680> way<00:43:15.800> of 00:43:15.950 --> 00:43:15.960 align:start position:0% matter it's based on some way of 00:43:15.960 --> 00:43:17.950 align:start position:0% matter it's based on some way of representing<00:43:16.559> Authority<00:43:17.359> so<00:43:17.640> in<00:43:17.760> the 00:43:17.950 --> 00:43:17.960 align:start position:0% representing Authority so in the 00:43:17.960 --> 00:43:20.390 align:start position:0% representing Authority so in the verification<00:43:18.640> side<00:43:18.960> then<00:43:19.200> does<00:43:19.359> it<00:43:19.880> mean<00:43:20.200> that 00:43:20.390 --> 00:43:20.400 align:start position:0% verification side then does it mean that 00:43:20.400 --> 00:43:22.990 align:start position:0% verification side then does it mean that it<00:43:20.760> it<00:43:21.079> it<00:43:21.400> it<00:43:21.520> needs<00:43:21.800> some<00:43:21.920> sort<00:43:22.119> of<00:43:22.200> a<00:43:22.440> trusted 00:43:22.990 --> 00:43:23.000 align:start position:0% it it it it needs some sort of a trusted 00:43:23.000 --> 00:43:25.670 align:start position:0% it it it it needs some sort of a trusted Source<00:43:23.520> registry<00:43:24.240> that<00:43:24.800> says<00:43:25.200> that<00:43:25.400> you<00:43:25.480> know 00:43:25.670 --> 00:43:25.680 align:start position:0% Source registry that says that you know 00:43:25.680 --> 00:43:28.870 align:start position:0% Source registry that says that you know this<00:43:25.960> identifier<00:43:26.839> of<00:43:27.559> this<00:43:27.880> signer<00:43:28.680> is 00:43:28.870 --> 00:43:28.880 align:start position:0% this identifier of this signer is 00:43:28.880 --> 00:43:31.109 align:start position:0% this identifier of this signer is trustworthy<00:43:29.839> correct<00:43:30.319> but<00:43:30.480> it<00:43:30.599> can<00:43:30.720> be<00:43:30.839> built 00:43:31.109 --> 00:43:31.119 align:start position:0% trustworthy correct but it can be built 00:43:31.119 --> 00:43:32.870 align:start position:0% trustworthy correct but it can be built on<00:43:31.359> top<00:43:31.520> so<00:43:31.680> you<00:43:31.760> see<00:43:31.960> how<00:43:32.079> you<00:43:32.160> have<00:43:32.319> this<00:43:32.520> pod 00:43:32.870 --> 00:43:32.880 align:start position:0% on top so you see how you have this pod 00:43:32.880 --> 00:43:35.950 align:start position:0% on top so you see how you have this pod here<00:43:33.200> right<00:43:33.880> so<00:43:34.720> if<00:43:34.800> you<00:43:35.079> trust<00:43:35.359> the<00:43:35.520> system 00:43:35.950 --> 00:43:35.960 align:start position:0% here right so if you trust the system 00:43:35.960 --> 00:43:38.349 align:start position:0% here right so if you trust the system what<00:43:36.079> you<00:43:36.200> trust<00:43:36.599> is<00:43:37.240> these<00:43:37.559> statements<00:43:38.200> have 00:43:38.349 --> 00:43:38.359 align:start position:0% what you trust is these statements have 00:43:38.359 --> 00:43:40.309 align:start position:0% what you trust is these statements have been<00:43:38.520> done<00:43:38.760> in<00:43:38.880> a<00:43:39.000> way<00:43:39.119> that<00:43:39.240> is<00:43:39.440> sound<00:43:40.040> from<00:43:40.200> a 00:43:40.309 --> 00:43:40.319 align:start position:0% been done in a way that is sound from a 00:43:40.319 --> 00:43:42.510 align:start position:0% been done in a way that is sound from a logical<00:43:40.920> perspective<00:43:41.920> now<00:43:42.119> the<00:43:42.280> way<00:43:42.440> you 00:43:42.510 --> 00:43:42.520 align:start position:0% logical perspective now the way you 00:43:42.520 --> 00:43:44.030 align:start position:0% logical perspective now the way you would<00:43:42.720> actually<00:43:43.079> trust<00:43:43.319> this<00:43:43.480> pod<00:43:43.760> is<00:43:43.920> you 00:43:44.030 --> 00:43:44.040 align:start position:0% would actually trust this pod is you 00:43:44.040 --> 00:43:46.950 align:start position:0% would actually trust this pod is you have<00:43:44.160> to<00:43:44.319> check<00:43:45.040> this<00:43:45.599> number<00:43:46.559> right<00:43:46.720> which<00:43:46.839> is 00:43:46.950 --> 00:43:46.960 align:start position:0% have to check this number right which is 00:43:46.960 --> 00:43:49.349 align:start position:0% have to check this number right which is the<00:43:47.119> public<00:43:47.440> key<00:43:47.720> of<00:43:47.920> both<00:43:48.119> of<00:43:48.240> the<00:43:48.359> pods<00:43:48.839> we<00:43:49.160> we 00:43:49.349 --> 00:43:49.359 align:start position:0% the public key of both of the pods we we 00:43:49.359 --> 00:43:51.270 align:start position:0% the public key of both of the pods we we constructed<00:43:49.800> that<00:43:49.960> logical<00:43:50.359> statement<00:43:51.160> so 00:43:51.270 --> 00:43:51.280 align:start position:0% constructed that logical statement so 00:43:51.280 --> 00:43:52.549 align:start position:0% constructed that logical statement so the<00:43:51.400> way<00:43:51.520> I'm<00:43:51.640> thinking<00:43:51.880> about<00:43:52.040> the<00:43:52.160> system<00:43:52.440> is 00:43:52.549 --> 00:43:52.559 align:start position:0% the way I'm thinking about the system is 00:43:52.559 --> 00:43:55.190 align:start position:0% the way I'm thinking about the system is I<00:43:52.640> want<00:43:52.800> to<00:43:53.000> layer<00:43:53.480> in<00:43:54.040> Trust<00:43:54.520> on<00:43:54.760> top<00:43:54.920> of<00:43:55.040> the 00:43:55.190 --> 00:43:55.200 align:start position:0% I want to layer in Trust on top of the 00:43:55.200 --> 00:43:56.750 align:start position:0% I want to layer in Trust on top of the logic<00:43:55.559> I<00:43:55.640> don't<00:43:55.760> want<00:43:55.839> to<00:43:56.000> Big<00:43:56.280> trust<00:43:56.559> in<00:43:56.680> the 00:43:56.750 --> 00:43:56.760 align:start position:0% logic I don't want to Big trust in the 00:43:56.760 --> 00:43:59.069 align:start position:0% logic I don't want to Big trust in the logic<00:43:57.400> because<00:43:57.559> I<00:43:57.640> want<00:43:57.720> to<00:43:58.079> manipulate 00:43:59.069 --> 00:43:59.079 align:start position:0% logic because I want to manipulate 00:43:59.079 --> 00:44:00.790 align:start position:0% logic because I want to manipulate things<00:43:59.359> that<00:43:59.440> are<00:43:59.760> like<00:44:00.079> that<00:44:00.160> are<00:44:00.359> linked<00:44:00.640> to 00:44:00.790 --> 00:44:00.800 align:start position:0% things that are like that are linked to 00:44:00.800 --> 00:44:02.230 align:start position:0% things that are like that are linked to trust<00:44:01.240> just<00:44:01.359> like<00:44:01.520> I'm<00:44:01.640> manipulating 00:44:02.230 --> 00:44:02.240 align:start position:0% trust just like I'm manipulating 00:44:02.240 --> 00:44:03.870 align:start position:0% trust just like I'm manipulating anything<00:44:02.520> else<00:44:03.040> but<00:44:03.160> you're<00:44:03.400> right<00:44:03.599> that<00:44:03.720> for 00:44:03.870 --> 00:44:03.880 align:start position:0% anything else but you're right that for 00:44:03.880 --> 00:44:05.230 align:start position:0% anything else but you're right that for this<00:44:04.000> to<00:44:04.160> actually<00:44:04.359> be<00:44:04.520> useful<00:44:04.960> we<00:44:05.119> would 00:44:05.230 --> 00:44:05.240 align:start position:0% this to actually be useful we would 00:44:05.240 --> 00:44:07.150 align:start position:0% this to actually be useful we would layer<00:44:05.520> it<00:44:05.680> and<00:44:05.920> something<00:44:06.200> else<00:44:06.359> on<00:44:06.559> top<00:44:07.000> So 00:44:07.150 --> 00:44:07.160 align:start position:0% layer it and something else on top So 00:44:07.160 --> 00:44:08.790 align:start position:0% layer it and something else on top So eventually<00:44:07.559> it<00:44:07.640> would<00:44:07.800> need<00:44:08.000> some<00:44:08.160> sort<00:44:08.359> of 00:44:08.790 --> 00:44:08.800 align:start position:0% eventually it would need some sort of 00:44:08.800 --> 00:44:10.990 align:start position:0% eventually it would need some sort of something<00:44:09.119> like<00:44:09.240> a<00:44:09.520> CA<00:44:10.119> certificate<00:44:10.800> like 00:44:10.990 --> 00:44:11.000 align:start position:0% something like a CA certificate like 00:44:11.000 --> 00:44:13.230 align:start position:0% something like a CA certificate like Authority<00:44:11.559> that<00:44:11.720> kind<00:44:11.839> of<00:44:12.760> I<00:44:12.839> think<00:44:13.160> there 00:44:13.230 --> 00:44:13.240 align:start position:0% Authority that kind of I think there 00:44:13.240 --> 00:44:14.950 align:start position:0% Authority that kind of I think there could<00:44:13.359> be<00:44:13.480> many<00:44:13.760> different<00:44:14.079> competing<00:44:14.599> ways 00:44:14.950 --> 00:44:14.960 align:start position:0% could be many different competing ways 00:44:14.960 --> 00:44:16.510 align:start position:0% could be many different competing ways even<00:44:15.160> of<00:44:15.280> doing<00:44:15.520> that<00:44:15.760> some<00:44:15.880> people<00:44:16.079> might<00:44:16.240> use 00:44:16.510 --> 00:44:16.520 align:start position:0% even of doing that some people might use 00:44:16.520 --> 00:44:18.230 align:start position:0% even of doing that some people might use CA<00:44:17.000> some<00:44:17.160> people<00:44:17.319> might<00:44:17.480> use<00:44:17.599> a<00:44:17.720> blockchain<00:44:18.119> as 00:44:18.230 --> 00:44:18.240 align:start position:0% CA some people might use a blockchain as 00:44:18.240 --> 00:44:19.790 align:start position:0% CA some people might use a blockchain as a<00:44:18.319> way<00:44:18.440> to<00:44:18.559> register<00:44:18.960> schemas<00:44:19.440> but<00:44:19.559> we<00:44:19.640> don't 00:44:19.790 --> 00:44:19.800 align:start position:0% a way to register schemas but we don't 00:44:19.800 --> 00:44:22.150 align:start position:0% a way to register schemas but we don't want<00:44:19.880> to<00:44:20.079> bundle<00:44:20.559> this<00:44:20.839> with<00:44:21.119> a<00:44:21.319> specific<00:44:22.040> kind 00:44:22.150 --> 00:44:22.160 align:start position:0% want to bundle this with a specific kind 00:44:22.160 --> 00:44:23.430 align:start position:0% want to bundle this with a specific kind of<00:44:22.280> registy<00:44:22.800> because<00:44:22.960> we<00:44:23.079> think<00:44:23.200> it's<00:44:23.280> a 00:44:23.430 --> 00:44:23.440 align:start position:0% of registy because we think it's a 00:44:23.440 --> 00:44:24.829 align:start position:0% of registy because we think it's a mistake<00:44:23.760> that<00:44:23.880> is<00:44:24.000> being<00:44:24.160> made<00:44:24.359> by<00:44:24.480> a<00:44:24.559> bunch<00:44:24.720> of 00:44:24.829 --> 00:44:24.839 align:start position:0% mistake that is being made by a bunch of 00:44:24.839 --> 00:44:25.910 align:start position:0% mistake that is being made by a bunch of projects<00:44:25.200> out<00:44:25.400> there<00:44:25.559> where<00:44:25.720> they're 00:44:25.910 --> 00:44:25.920 align:start position:0% projects out there where they're 00:44:25.920 --> 00:44:28.030 align:start position:0% projects out there where they're building<00:44:26.240> this<00:44:26.400> monolith<00:44:27.240> of<00:44:27.400> like<00:44:27.760> the<00:44:27.880> way 00:44:28.030 --> 00:44:28.040 align:start position:0% building this monolith of like the way 00:44:28.040 --> 00:44:29.910 align:start position:0% building this monolith of like the way we<00:44:28.200> import<00:44:28.559> data<00:44:29.000> example<00:44:29.280> from<00:44:29.440> passport<00:44:29.839> the 00:44:29.910 --> 00:44:29.920 align:start position:0% we import data example from passport the 00:44:29.920 --> 00:44:31.549 align:start position:0% we import data example from passport the way<00:44:30.040> we<00:44:30.160> verify<00:44:30.559> public<00:44:30.839> key<00:44:31.079> using<00:44:31.359> this 00:44:31.549 --> 00:44:31.559 align:start position:0% way we verify public key using this 00:44:31.559 --> 00:44:32.990 align:start position:0% way we verify public key using this specific<00:44:31.880> blockchain<00:44:32.319> the<00:44:32.400> way<00:44:32.520> we<00:44:32.680> operate 00:44:32.990 --> 00:44:33.000 align:start position:0% specific blockchain the way we operate 00:44:33.000 --> 00:44:34.750 align:start position:0% specific blockchain the way we operate using<00:44:33.280> these<00:44:33.440> specific<00:44:33.760> circuits<00:44:34.400> we<00:44:34.520> want<00:44:34.640> to 00:44:34.750 --> 00:44:34.760 align:start position:0% using these specific circuits we want to 00:44:34.760 --> 00:44:36.309 align:start position:0% using these specific circuits we want to unbundle<00:44:35.359> everything<00:44:35.800> whether<00:44:36.000> it's<00:44:36.200> where 00:44:36.309 --> 00:44:36.319 align:start position:0% unbundle everything whether it's where 00:44:36.319 --> 00:44:38.230 align:start position:0% unbundle everything whether it's where the<00:44:36.520> data<00:44:36.760> come<00:44:37.000> from<00:44:37.520> how<00:44:37.640> the<00:44:37.800> competition 00:44:38.230 --> 00:44:38.240 align:start position:0% the data come from how the competition 00:44:38.240 --> 00:44:40.950 align:start position:0% the data come from how the competition got<00:44:38.440> done<00:44:39.079> and<00:44:39.599> where<00:44:40.119> which<00:44:40.319> which<00:44:40.480> registry 00:44:40.950 --> 00:44:40.960 align:start position:0% got done and where which which registry 00:44:40.960 --> 00:44:43.109 align:start position:0% got done and where which which registry of<00:44:41.079> truth<00:44:41.440> of<00:44:41.599> trust<00:44:41.880> is<00:44:42.000> being<00:44:42.200> used<00:44:42.680> yeah<00:44:43.000> all 00:44:43.109 --> 00:44:43.119 align:start position:0% of truth of trust is being used yeah all 00:44:43.119 --> 00:44:45.950 align:start position:0% of truth of trust is being used yeah all right<00:44:43.280> thank<00:44:43.440> you<00:44:43.559> very<00:44:43.720> much<00:44:44.000> you're 00:44:45.950 --> 00:44:45.960 align:start position:0% right thank you very much you're 00:44:45.960 --> 00:44:50.790 align:start position:0% right thank you very much you're welcome<00:44:46.960> cool<00:44:47.520> so<00:44:48.280> um<00:44:48.720> how<00:44:48.880> much<00:44:49.040> time<00:44:49.200> do<00:44:49.319> I 00:44:50.790 --> 00:44:50.800 align:start position:0% welcome cool so um how much time do I 00:44:50.800 --> 00:44:54.990 align:start position:0% welcome cool so um how much time do I have<00:44:51.800> 10<00:44:52.040> minutes<00:44:53.040> dang<00:44:53.640> okay 00:44:54.990 --> 00:44:55.000 align:start position:0% have 10 minutes dang okay 00:44:55.000 --> 00:44:57.670 align:start position:0% have 10 minutes dang okay um<00:44:56.000> what<00:44:56.119> would<00:44:56.280> be<00:44:56.440> more<00:44:56.599> interesting<00:44:57.319> making 00:44:57.670 --> 00:44:57.680 align:start position:0% um what would be more interesting making 00:44:57.680 --> 00:45:00.030 align:start position:0% um what would be more interesting making more<00:44:58.079> pods<00:44:58.720> looking<00:44:59.000> in<00:44:59.119> the<00:44:59.280> code<00:44:59.559> base<00:44:59.880> to 00:45:00.030 --> 00:45:00.040 align:start position:0% more pods looking in the code base to 00:45:00.040 --> 00:45:02.390 align:start position:0% more pods looking in the code base to show<00:45:00.440> how<00:45:00.760> a<00:45:00.960> specific<00:45:01.400> logical<00:45:01.880> operation 00:45:02.390 --> 00:45:02.400 align:start position:0% show how a specific logical operation 00:45:02.400 --> 00:45:06.349 align:start position:0% show how a specific logical operation Works<00:45:03.079> something<00:45:03.440> else<00:45:04.280> beatboxing<00:45:05.359> um 00:45:06.349 --> 00:45:06.359 align:start position:0% Works something else beatboxing um 00:45:06.359 --> 00:45:09.309 align:start position:0% Works something else beatboxing um anyone<00:45:06.640> has<00:45:06.760> an 00:45:09.309 --> 00:45:09.319 align:start position:0% 00:45:09.319 --> 00:45:12.190 align:start position:0% opinion<00:45:10.319> code<00:45:10.559> base<00:45:11.160> cool<00:45:11.599> let's<00:45:11.800> look<00:45:11.920> at<00:45:12.079> the 00:45:12.190 --> 00:45:12.200 align:start position:0% opinion code base cool let's look at the 00:45:12.200 --> 00:45:15.309 align:start position:0% opinion code base cool let's look at the code 00:45:15.309 --> 00:45:15.319 align:start position:0% 00:45:15.319 --> 00:45:17.630 align:start position:0% base<00:45:16.319> I<00:45:16.440> can't<00:45:16.640> do<00:45:16.800> two<00:45:16.960> things<00:45:17.160> at<00:45:17.280> the<00:45:17.400> same 00:45:17.630 --> 00:45:17.640 align:start position:0% base I can't do two things at the same 00:45:17.640 --> 00:45:20.510 align:start position:0% base I can't do two things at the same time<00:45:17.960> I<00:45:18.040> am<00:45:18.160> a<00:45:18.319> single<00:45:18.720> threaded<00:45:19.440> processor<00:45:20.440> I 00:45:20.510 --> 00:45:20.520 align:start position:0% time I am a single threaded processor I 00:45:20.520 --> 00:45:22.910 align:start position:0% time I am a single threaded processor I would<00:45:20.680> have<00:45:20.800> to<00:45:21.000> stop<00:45:21.200> everything<00:45:21.480> to 00:45:22.910 --> 00:45:22.920 align:start position:0% would have to stop everything to 00:45:22.920 --> 00:45:30.549 align:start position:0% would have to stop everything to beatbox<00:45:24.240> um<00:45:25.240> Okay<00:45:25.760> so 00:45:30.549 --> 00:45:30.559 align:start position:0% 00:45:30.559 --> 00:45:34.790 align:start position:0% cool<00:45:31.440> so<00:45:32.400> this<00:45:32.920> is<00:45:33.520> a<00:45:33.720> file<00:45:34.079> that<00:45:34.200> we<00:45:34.400> have<00:45:34.640> that 00:45:34.790 --> 00:45:34.800 align:start position:0% cool so this is a file that we have that 00:45:34.800 --> 00:45:36.870 align:start position:0% cool so this is a file that we have that list<00:45:35.359> all<00:45:35.559> of<00:45:35.720> the<00:45:36.040> operations<00:45:36.720> that 00:45:36.870 --> 00:45:36.880 align:start position:0% list all of the operations that 00:45:36.880 --> 00:45:38.670 align:start position:0% list all of the operations that currently<00:45:37.280> exist<00:45:37.520> in<00:45:37.599> the<00:45:37.760> system<00:45:38.359> it's<00:45:38.559> just 00:45:38.670 --> 00:45:38.680 align:start position:0% currently exist in the system it's just 00:45:38.680 --> 00:45:43.430 align:start position:0% currently exist in the system it's just an<00:45:38.839> enom<00:45:39.160> in<00:45:39.800> Rust<00:45:40.800> um<00:45:41.720> one<00:45:42.119> specific<00:45:43.000> entry 00:45:43.430 --> 00:45:43.440 align:start position:0% an enom in Rust um one specific entry 00:45:43.440 --> 00:45:46.150 align:start position:0% an enom in Rust um one specific entry here<00:45:43.599> is<00:45:44.200> greater<00:45:44.760> from<00:45:45.040> entries<00:45:45.800> so<00:45:46.000> what 00:45:46.150 --> 00:45:46.160 align:start position:0% here is greater from entries so what 00:45:46.160 --> 00:45:48.190 align:start position:0% here is greater from entries so what this<00:45:46.319> operation<00:45:46.839> does<00:45:47.240> is<00:45:47.359> it<00:45:47.559> takes<00:45:47.920> two 00:45:48.190 --> 00:45:48.200 align:start position:0% this operation does is it takes two 00:45:48.200 --> 00:45:51.109 align:start position:0% this operation does is it takes two statements<00:45:49.160> you<00:45:49.280> see<00:45:49.559> S<00:45:49.760> and<00:45:50.000> S<00:45:50.760> what<00:45:50.960> the 00:45:51.109 --> 00:45:51.119 align:start position:0% statements you see S and S what the 00:45:51.119 --> 00:45:52.790 align:start position:0% statements you see S and S what the statements<00:45:51.559> need<00:45:51.720> to<00:45:51.839> be<00:45:51.960> is<00:45:52.119> they<00:45:52.240> need<00:45:52.359> to<00:45:52.480> be 00:45:52.790 --> 00:45:52.800 align:start position:0% statements need to be is they need to be 00:45:52.800 --> 00:45:55.230 align:start position:0% statements need to be is they need to be value<00:45:53.160> of<00:45:53.480> statements<00:45:54.319> so<00:45:54.599> statements<00:45:55.079> that 00:45:55.230 --> 00:45:55.240 align:start position:0% value of statements so statements that 00:45:55.240 --> 00:45:57.630 align:start position:0% value of statements so statements that point<00:45:55.440> to<00:45:55.599> the<00:45:55.720> value<00:45:55.920> of<00:45:56.000> an<00:45:56.160> entry<00:45:57.359> and<00:45:57.480> then 00:45:57.630 --> 00:45:57.640 align:start position:0% point to the value of an entry and then 00:45:57.640 --> 00:45:59.349 align:start position:0% point to the value of an entry and then if<00:45:57.839> the<00:45:58.000> entry<00:45:58.359> is<00:45:58.520> Behind<00:45:58.800> These<00:45:58.960> two<00:45:59.119> value 00:45:59.349 --> 00:45:59.359 align:start position:0% if the entry is Behind These two value 00:45:59.359 --> 00:46:01.109 align:start position:0% if the entry is Behind These two value of<00:45:59.520> statements<00:46:00.160> if<00:46:00.280> the<00:46:00.400> first<00:46:00.599> one<00:46:00.760> is<00:46:00.880> bigger 00:46:01.109 --> 00:46:01.119 align:start position:0% of statements if the first one is bigger 00:46:01.119 --> 00:46:03.109 align:start position:0% of statements if the first one is bigger than<00:46:01.240> the<00:46:01.400> second<00:46:01.640> one<00:46:02.240> it<00:46:02.359> will<00:46:02.599> add<00:46:02.800> a<00:46:02.920> new 00:46:03.109 --> 00:46:03.119 align:start position:0% than the second one it will add a new 00:46:03.119 --> 00:46:04.710 align:start position:0% than the second one it will add a new statement<00:46:03.640> which<00:46:03.760> is<00:46:04.119> something<00:46:04.480> like 00:46:04.710 --> 00:46:04.720 align:start position:0% statement which is something like 00:46:04.720 --> 00:46:07.829 align:start position:0% statement which is something like greater<00:46:05.200> than<00:46:05.520> we<00:46:05.640> we<00:46:05.720> can<00:46:05.880> check<00:46:06.119> later 00:46:07.829 --> 00:46:07.839 align:start position:0% greater than we we can check later 00:46:07.839 --> 00:46:11.190 align:start position:0% greater than we we can check later so<00:46:08.880> um<00:46:09.880> let's<00:46:10.079> see<00:46:10.400> how<00:46:10.599> that<00:46:10.800> actually 00:46:11.190 --> 00:46:11.200 align:start position:0% so um let's see how that actually 00:46:11.200 --> 00:46:14.030 align:start position:0% so um let's see how that actually happens 00:46:14.030 --> 00:46:14.040 align:start position:0% 00:46:14.040 --> 00:46:18.109 align:start position:0% so<00:46:15.040> let's<00:46:15.599> command<00:46:15.960> f<00:46:16.160> for<00:46:16.520> this<00:46:17.520> so<00:46:17.800> okay<00:46:18.040> I 00:46:18.109 --> 00:46:18.119 align:start position:0% so let's command f for this so okay I 00:46:18.119 --> 00:46:19.589 align:start position:0% so let's command f for this so okay I will<00:46:18.280> not<00:46:18.400> show<00:46:18.599> you<00:46:18.800> guys<00:46:18.920> the<00:46:19.040> front<00:46:19.280> end<00:46:19.520> I 00:46:19.589 --> 00:46:19.599 align:start position:0% will not show you guys the front end I 00:46:19.599 --> 00:46:21.069 align:start position:0% will not show you guys the front end I will<00:46:19.720> not<00:46:19.839> show<00:46:19.960> you<00:46:20.079> how<00:46:20.200> in<00:46:20.319> the<00:46:20.440> Lis<00:46:20.960> this 00:46:21.069 --> 00:46:21.079 align:start position:0% will not show you how in the Lis this 00:46:21.079 --> 00:46:22.589 align:start position:0% will not show you how in the Lis this gets<00:46:21.240> turned<00:46:21.480> into<00:46:21.640> the<00:46:21.800> specific<00:46:22.160> command 00:46:22.589 --> 00:46:22.599 align:start position:0% gets turned into the specific command 00:46:22.599 --> 00:46:23.990 align:start position:0% gets turned into the specific command but<00:46:22.680> now<00:46:22.800> you<00:46:22.920> have<00:46:23.040> to<00:46:23.319> kind<00:46:23.440> of<00:46:23.559> like<00:46:23.720> believe 00:46:23.990 --> 00:46:24.000 align:start position:0% but now you have to kind of like believe 00:46:24.000 --> 00:46:25.630 align:start position:0% but now you have to kind of like believe me<00:46:24.240> that<00:46:24.440> this<00:46:24.599> command<00:46:24.960> is<00:46:25.079> called<00:46:25.319> at<00:46:25.440> some 00:46:25.630 --> 00:46:25.640 align:start position:0% me that this command is called at some 00:46:25.640 --> 00:46:27.589 align:start position:0% me that this command is called at some point<00:46:25.960> pointing<00:46:26.240> to<00:46:26.359> the<00:46:26.480> right<00:46:26.640> statement 00:46:27.589 --> 00:46:27.599 align:start position:0% point pointing to the right statement 00:46:27.599 --> 00:46:30.150 align:start position:0% point pointing to the right statement so<00:46:27.920> first 00:46:30.150 --> 00:46:30.160 align:start position:0% so first 00:46:30.160 --> 00:46:32.950 align:start position:0% so first um<00:46:31.160> one<00:46:31.400> thing<00:46:31.680> I'll<00:46:31.839> show<00:46:32.040> you<00:46:32.200> is<00:46:32.400> how<00:46:32.520> to 00:46:32.950 --> 00:46:32.960 align:start position:0% um one thing I'll show you is how to 00:46:32.960 --> 00:46:37.349 align:start position:0% um one thing I'll show you is how to evaluate<00:46:33.960> this<00:46:34.599> statement<00:46:35.599> in<00:46:36.400> plain<00:46:36.760> text<00:46:37.119> so 00:46:37.349 --> 00:46:37.359 align:start position:0% evaluate this statement in plain text so 00:46:37.359 --> 00:46:40.430 align:start position:0% evaluate this statement in plain text so not<00:46:37.520> using<00:46:38.040> cryptography<00:46:39.040> so<00:46:39.240> if<00:46:39.400> we<00:46:39.559> see<00:46:39.920> here 00:46:40.430 --> 00:46:40.440 align:start position:0% not using cryptography so if we see here 00:46:40.440 --> 00:46:43.630 align:start position:0% not using cryptography so if we see here when<00:46:40.599> I<00:46:40.720> have<00:46:40.839> the<00:46:41.000> greater<00:46:41.319> from<00:46:41.880> entries<00:46:42.880> I 00:46:43.630 --> 00:46:43.640 align:start position:0% when I have the greater from entries I 00:46:43.640 --> 00:46:46.710 align:start position:0% when I have the greater from entries I destructure<00:46:44.640> um<00:46:44.920> two<00:46:45.240> value<00:46:45.520> of<00:46:45.720> statements 00:46:46.710 --> 00:46:46.720 align:start position:0% destructure um two value of statements 00:46:46.720 --> 00:46:49.069 align:start position:0% destructure um two value of statements and<00:46:46.880> then<00:46:47.240> the<00:46:47.440> actual<00:46:47.760> entries<00:46:48.240> between<00:46:48.559> them 00:46:49.069 --> 00:46:49.079 align:start position:0% and then the actual entries between them 00:46:49.079 --> 00:46:52.069 align:start position:0% and then the actual entries between them and<00:46:49.200> then<00:46:49.319> I<00:46:49.440> turn<00:46:49.720> these<00:46:49.920> entries<00:46:50.319> into<00:46:51.079> u64 00:46:52.069 --> 00:46:52.079 align:start position:0% and then I turn these entries into u64 00:46:52.079 --> 00:46:53.670 align:start position:0% and then I turn these entries into u64 and<00:46:52.240> if<00:46:52.400> the<00:46:52.520> first<00:46:52.720> one<00:46:52.920> is<00:46:53.079> indeed<00:46:53.400> bigger 00:46:53.670 --> 00:46:53.680 align:start position:0% and if the first one is indeed bigger 00:46:53.680 --> 00:46:55.150 align:start position:0% and if the first one is indeed bigger than<00:46:53.839> the<00:46:53.960> second<00:46:54.240> one<00:46:54.520> I<00:46:54.640> create<00:46:54.880> a<00:46:55.000> new 00:46:55.150 --> 00:46:55.160 align:start position:0% than the second one I create a new 00:46:55.160 --> 00:46:57.190 align:start position:0% than the second one I create a new statement<00:46:55.640> which<00:46:55.800> is<00:46:56.079> greater<00:46:56.480> than<00:46:57.040> the 00:46:57.190 --> 00:46:57.200 align:start position:0% statement which is greater than the 00:46:57.200 --> 00:46:58.950 align:start position:0% statement which is greater than the first<00:46:57.440> key<00:46:57.640> the<00:46:57.760> second 00:46:58.950 --> 00:46:58.960 align:start position:0% first key the second 00:46:58.960 --> 00:47:01.309 align:start position:0% first key the second key<00:46:59.960> so<00:47:00.160> till<00:47:00.359> then<00:47:00.520> this<00:47:00.640> should<00:47:00.800> make<00:47:01.000> sense 00:47:01.309 --> 00:47:01.319 align:start position:0% key so till then this should make sense 00:47:01.319 --> 00:47:02.670 align:start position:0% key so till then this should make sense right<00:47:01.520> like<00:47:01.720> we're<00:47:01.920> just<00:47:02.079> showing<00:47:02.359> how<00:47:02.520> this 00:47:02.670 --> 00:47:02.680 align:start position:0% right like we're just showing how this 00:47:02.680 --> 00:47:05.230 align:start position:0% right like we're just showing how this happens<00:47:02.960> in<00:47:03.119> plain<00:47:03.400> text<00:47:04.119> okay 00:47:05.230 --> 00:47:05.240 align:start position:0% happens in plain text okay 00:47:05.240 --> 00:47:09.069 align:start position:0% happens in plain text okay so<00:47:06.240> now<00:47:06.640> how<00:47:06.800> does<00:47:07.079> this<00:47:07.520> happens<00:47:08.359> uh<00:47:08.640> in<00:47:08.880> a 00:47:09.069 --> 00:47:09.079 align:start position:0% so now how does this happens uh in a 00:47:09.079 --> 00:47:13.150 align:start position:0% so now how does this happens uh in a circuit<00:47:10.040> so<00:47:10.440> what<00:47:10.559> we'll<00:47:10.800> do<00:47:11.079> here<00:47:11.520> is<00:47:12.280> first 00:47:13.150 --> 00:47:13.160 align:start position:0% circuit so what we'll do here is first 00:47:13.160 --> 00:47:15.510 align:start position:0% circuit so what we'll do here is first um<00:47:13.319> in<00:47:13.440> a<00:47:13.640> circuit<00:47:14.599> every<00:47:14.839> single<00:47:15.200> one<00:47:15.359> of 00:47:15.510 --> 00:47:15.520 align:start position:0% um in a circuit every single one of 00:47:15.520 --> 00:47:17.270 align:start position:0% um in a circuit every single one of these<00:47:15.720> statements<00:47:16.280> need<00:47:16.440> to<00:47:16.559> be<00:47:16.680> turned<00:47:16.960> into 00:47:17.270 --> 00:47:17.280 align:start position:0% these statements need to be turned into 00:47:17.280 --> 00:47:20.349 align:start position:0% these statements need to be turned into op<00:47:17.559> codes<00:47:18.160> and<00:47:18.319> these<00:47:18.520> op<00:47:18.800> codes<00:47:19.240> are<00:47:19.839> field 00:47:20.349 --> 00:47:20.359 align:start position:0% op codes and these op codes are field 00:47:20.359 --> 00:47:22.510 align:start position:0% op codes and these op codes are field element<00:47:21.160> into<00:47:21.520> the<00:47:21.640> field<00:47:21.920> we're<00:47:22.079> using<00:47:22.400> which 00:47:22.510 --> 00:47:22.520 align:start position:0% element into the field we're using which 00:47:22.520 --> 00:47:24.870 align:start position:0% element into the field we're using which is<00:47:22.640> the<00:47:22.760> goldilock<00:47:23.319> field<00:47:24.240> so<00:47:24.480> the<00:47:24.599> greater 00:47:24.870 --> 00:47:24.880 align:start position:0% is the goldilock field so the greater 00:47:24.880 --> 00:47:27.309 align:start position:0% is the goldilock field so the greater from<00:47:25.119> entries<00:47:25.480> gets<00:47:25.640> thrown<00:47:25.960> into<00:47:26.920> this<00:47:27.079> up 00:47:27.309 --> 00:47:27.319 align:start position:0% from entries gets thrown into this up 00:47:27.319 --> 00:47:30.589 align:start position:0% from entries gets thrown into this up codes<00:47:27.640> up<00:47:27.880> code<00:47:28.119> number<00:47:28.880> five<00:47:29.880> um<00:47:30.359> and<00:47:30.440> then 00:47:30.589 --> 00:47:30.599 align:start position:0% codes up code number five um and then 00:47:30.599 --> 00:47:32.069 align:start position:0% codes up code number five um and then another<00:47:30.839> thing<00:47:30.960> I<00:47:31.079> will<00:47:31.200> do<00:47:31.359> is<00:47:31.440> it<00:47:31.520> will<00:47:31.760> take 00:47:32.069 --> 00:47:32.079 align:start position:0% another thing I will do is it will take 00:47:32.079 --> 00:47:34.230 align:start position:0% another thing I will do is it will take the<00:47:32.319> operant<00:47:32.839> of<00:47:33.040> this<00:47:33.200> statement<00:47:33.880> here<00:47:34.040> it's 00:47:34.230 --> 00:47:34.240 align:start position:0% the operant of this statement here it's 00:47:34.240 --> 00:47:36.390 align:start position:0% the operant of this statement here it's S1<00:47:34.559> and<00:47:34.680> S2<00:47:34.960> and<00:47:35.040> turn<00:47:35.200> them<00:47:35.359> into<00:47:35.520> a<00:47:35.720> vector<00:47:36.200> of 00:47:36.390 --> 00:47:36.400 align:start position:0% S1 and S2 and turn them into a vector of 00:47:36.400 --> 00:47:37.750 align:start position:0% S1 and S2 and turn them into a vector of oper<00:47:36.880> that<00:47:36.960> will<00:47:37.079> be<00:47:37.200> injected<00:47:37.559> in<00:47:37.640> the 00:47:37.750 --> 00:47:37.760 align:start position:0% oper that will be injected in the 00:47:37.760 --> 00:47:39.870 align:start position:0% oper that will be injected in the circuit<00:47:38.119> as<00:47:38.240> well<00:47:38.960> I<00:47:39.040> think<00:47:39.160> there's<00:47:39.440> one<00:47:39.680> last 00:47:39.870 --> 00:47:39.880 align:start position:0% circuit as well I think there's one last 00:47:39.880 --> 00:47:42.549 align:start position:0% circuit as well I think there's one last thing<00:47:40.040> that<00:47:40.520> oh<00:47:40.720> this<00:47:40.839> is<00:47:41.040> just<00:47:41.640> a<00:47:41.800> way<00:47:41.920> to<00:47:42.119> sort 00:47:42.549 --> 00:47:42.559 align:start position:0% thing that oh this is just a way to sort 00:47:42.559 --> 00:47:43.790 align:start position:0% thing that oh this is just a way to sort these<00:47:42.760> statements<00:47:43.240> because<00:47:43.400> they<00:47:43.520> need<00:47:43.640> to<00:47:43.720> be 00:47:43.790 --> 00:47:43.800 align:start position:0% these statements because they need to be 00:47:43.800 --> 00:47:46.230 align:start position:0% these statements because they need to be sorted<00:47:44.119> in<00:47:44.200> a<00:47:44.359> specific<00:47:44.760> way<00:47:45.240> okay<00:47:45.520> so<00:47:45.680> in<00:47:45.800> our 00:47:46.230 --> 00:47:46.240 align:start position:0% sorted in a specific way okay so in our 00:47:46.240 --> 00:47:48.790 align:start position:0% sorted in a specific way okay so in our circuit<00:47:47.240> here's<00:47:47.520> what<00:47:47.640> we<00:47:47.800> do<00:47:48.280> so<00:47:48.440> let's<00:47:48.599> go<00:47:48.680> to 00:47:48.790 --> 00:47:48.800 align:start position:0% circuit here's what we do so let's go to 00:47:48.800 --> 00:47:52.630 align:start position:0% circuit here's what we do so let's go to the<00:47:48.960> top<00:47:49.119> of<00:47:49.200> our<00:47:49.760> circuit<00:47:51.119> um<00:47:52.119> what<00:47:52.319> the<00:47:52.520> the 00:47:52.630 --> 00:47:52.640 align:start position:0% the top of our circuit um what the the 00:47:52.640 --> 00:47:54.309 align:start position:0% the top of our circuit um what the the top<00:47:52.839> of<00:47:52.920> the<00:47:53.040> circuit<00:47:53.400> does<00:47:53.599> it<00:47:53.760> says<00:47:54.119> there's 00:47:54.309 --> 00:47:54.319 align:start position:0% top of the circuit does it says there's 00:47:54.319 --> 00:47:56.510 align:start position:0% top of the circuit does it says there's a<00:47:54.480> current<00:47:54.839> Builder<00:47:55.559> the<00:47:55.680> Builder<00:47:56.040> is<00:47:56.240> just<00:47:56.359> an 00:47:56.510 --> 00:47:56.520 align:start position:0% a current Builder the Builder is just an 00:47:56.520 --> 00:47:57.990 align:start position:0% a current Builder the Builder is just an object<00:47:57.000> that<00:47:57.119> you<00:47:57.240> have<00:47:57.440> in<00:47:57.559> the<00:47:57.680> proving 00:47:57.990 --> 00:47:58.000 align:start position:0% object that you have in the proving 00:47:58.000 --> 00:47:59.390 align:start position:0% object that you have in the proving system<00:47:58.280> we<00:47:58.400> use<00:47:58.640> to<00:47:58.720> be<00:47:58.839> able<00:47:58.960> to<00:47:59.079> add<00:47:59.280> new 00:47:59.390 --> 00:47:59.400 align:start position:0% system we use to be able to add new 00:47:59.400 --> 00:48:01.870 align:start position:0% system we use to be able to add new constraint<00:48:00.319> and<00:48:00.480> there<00:48:00.640> is<00:48:01.200> um<00:48:01.359> a<00:48:01.520> bunch<00:48:01.680> of 00:48:01.870 --> 00:48:01.880 align:start position:0% constraint and there is um a bunch of 00:48:01.880 --> 00:48:06.069 align:start position:0% constraint and there is um a bunch of statements<00:48:02.839> right<00:48:03.480> and<00:48:03.640> and<00:48:03.760> they<00:48:04.359> targets 00:48:06.069 --> 00:48:06.079 align:start position:0% statements right and and they targets 00:48:06.079 --> 00:48:09.349 align:start position:0% statements right and and they targets so<00:48:07.079> this<00:48:07.440> mumbo<00:48:07.839> jumbo<00:48:08.359> here<00:48:08.720> is<00:48:08.839> a<00:48:09.000> way<00:48:09.160> to<00:48:09.280> be 00:48:09.349 --> 00:48:09.359 align:start position:0% so this mumbo jumbo here is a way to be 00:48:09.359 --> 00:48:11.390 align:start position:0% so this mumbo jumbo here is a way to be able<00:48:09.559> to<00:48:09.760> select<00:48:10.359> from<00:48:10.520> the<00:48:10.680> list<00:48:10.880> of<00:48:11.000> entries 00:48:11.390 --> 00:48:11.400 align:start position:0% able to select from the list of entries 00:48:11.400 --> 00:48:13.390 align:start position:0% able to select from the list of entries we<00:48:11.599> have<00:48:12.160> the<00:48:12.280> entry<00:48:12.640> that<00:48:12.800> corresponds<00:48:13.280> to 00:48:13.390 --> 00:48:13.400 align:start position:0% we have the entry that corresponds to 00:48:13.400 --> 00:48:15.630 align:start position:0% we have the entry that corresponds to the<00:48:13.559> statement<00:48:14.559> um<00:48:14.760> we<00:48:14.880> need<00:48:15.000> to<00:48:15.119> do<00:48:15.240> some<00:48:15.480> like 00:48:15.630 --> 00:48:15.640 align:start position:0% the statement um we need to do some like 00:48:15.640 --> 00:48:19.790 align:start position:0% the statement um we need to do some like Matrix<00:48:16.440> kind<00:48:16.599> of<00:48:16.800> like<00:48:17.040> indexing<00:48:17.880> thing<00:48:18.880> so 00:48:19.790 --> 00:48:19.800 align:start position:0% Matrix kind of like indexing thing so 00:48:19.800 --> 00:48:23.309 align:start position:0% Matrix kind of like indexing thing so what<00:48:19.920> we'll<00:48:20.160> do<00:48:20.559> here<00:48:21.240> is 00:48:23.309 --> 00:48:23.319 align:start position:0% what we'll do here is 00:48:23.319 --> 00:48:26.270 align:start position:0% what we'll do here is uh<00:48:24.319> we<00:48:24.480> have<00:48:24.680> this<00:48:24.880> op<00:48:25.319> is<00:48:25.480> valid<00:48:25.800> AR<00:48:25.960> right<00:48:26.119> so 00:48:26.270 --> 00:48:26.280 align:start position:0% uh we have this op is valid AR right so 00:48:26.280 --> 00:48:28.069 align:start position:0% uh we have this op is valid AR right so the<00:48:26.400> code<00:48:26.599> is<00:48:26.839> still<00:48:27.000> not<00:48:27.200> great<00:48:27.559> Ahad<00:48:27.920> will 00:48:28.069 --> 00:48:28.079 align:start position:0% the code is still not great Ahad will 00:48:28.079 --> 00:48:29.750 align:start position:0% the code is still not great Ahad will tell<00:48:28.240> you<00:48:28.520> how<00:48:28.680> we<00:48:28.800> got<00:48:29.040> there<00:48:29.319> but<00:48:29.440> we'll<00:48:29.640> make 00:48:29.750 --> 00:48:29.760 align:start position:0% tell you how we got there but we'll make 00:48:29.760 --> 00:48:31.790 align:start position:0% tell you how we got there but we'll make it<00:48:29.920> better<00:48:30.520> but<00:48:30.800> what<00:48:30.920> you<00:48:31.079> have<00:48:31.200> to<00:48:31.400> think<00:48:31.640> to 00:48:31.790 --> 00:48:31.800 align:start position:0% it better but what you have to think to 00:48:31.800 --> 00:48:33.990 align:start position:0% it better but what you have to think to do<00:48:32.040> here<00:48:32.240> is<00:48:32.559> you<00:48:32.680> have<00:48:32.800> to<00:48:33.000> index<00:48:33.760> you<00:48:33.839> can 00:48:33.990 --> 00:48:34.000 align:start position:0% do here is you have to index you can 00:48:34.000 --> 00:48:35.910 align:start position:0% do here is you have to index you can imagine<00:48:34.359> so<00:48:34.800> the<00:48:34.920> circuit<00:48:35.319> model<00:48:35.559> is<00:48:35.680> not<00:48:35.800> the 00:48:35.910 --> 00:48:35.920 align:start position:0% imagine so the circuit model is not the 00:48:35.920 --> 00:48:37.510 align:start position:0% imagine so the circuit model is not the computational<00:48:36.440> model<00:48:36.680> you<00:48:36.800> have<00:48:36.880> to<00:48:37.040> execute 00:48:37.510 --> 00:48:37.520 align:start position:0% computational model you have to execute 00:48:37.520 --> 00:48:38.750 align:start position:0% computational model you have to execute everything<00:48:37.880> all<00:48:38.000> the<00:48:38.160> time<00:48:38.440> and<00:48:38.520> then<00:48:38.640> what 00:48:38.750 --> 00:48:38.760 align:start position:0% everything all the time and then what 00:48:38.760 --> 00:48:40.309 align:start position:0% everything all the time and then what you<00:48:38.839> do<00:48:38.960> is<00:48:39.040> you<00:48:39.119> have<00:48:39.280> selectors<00:48:39.880> that<00:48:40.040> turned 00:48:40.309 --> 00:48:40.319 align:start position:0% you do is you have selectors that turned 00:48:40.319 --> 00:48:42.430 align:start position:0% you do is you have selectors that turned on<00:48:40.599> for<00:48:40.800> what<00:48:40.880> you<00:48:41.040> actually<00:48:41.240> need<00:48:41.400> to<00:48:41.559> check 00:48:42.430 --> 00:48:42.440 align:start position:0% on for what you actually need to check 00:48:42.440 --> 00:48:44.549 align:start position:0% on for what you actually need to check so<00:48:42.640> what<00:48:42.800> we<00:48:42.920> do<00:48:43.040> in<00:48:43.160> this<00:48:43.440> massive<00:48:43.800> array<00:48:44.200> op 00:48:44.549 --> 00:48:44.559 align:start position:0% so what we do in this massive array op 00:48:44.559 --> 00:48:47.270 align:start position:0% so what we do in this massive array op is<00:48:44.760> valid<00:48:45.440> is<00:48:45.599> we<00:48:45.800> basically<00:48:46.720> check<00:48:47.119> the 00:48:47.270 --> 00:48:47.280 align:start position:0% is valid is we basically check the 00:48:47.280 --> 00:48:49.549 align:start position:0% is valid is we basically check the validity<00:48:47.800> of<00:48:48.119> every<00:48:48.400> single<00:48:48.839> operation<00:48:49.400> that 00:48:49.549 --> 00:48:49.559 align:start position:0% validity of every single operation that 00:48:49.559 --> 00:48:50.950 align:start position:0% validity of every single operation that could<00:48:49.760> happen<00:48:50.000> on<00:48:50.240> the<00:48:50.400> statements<00:48:50.760> that<00:48:50.880> are 00:48:50.950 --> 00:48:50.960 align:start position:0% could happen on the statements that are 00:48:50.960 --> 00:48:52.470 align:start position:0% could happen on the statements that are currently<00:48:51.280> being<00:48:51.520> selected<00:48:52.040> and<00:48:52.160> when<00:48:52.280> you 00:48:52.470 --> 00:48:52.480 align:start position:0% currently being selected and when you 00:48:52.480 --> 00:48:54.190 align:start position:0% currently being selected and when you turn<00:48:52.720> on<00:48:52.920> the<00:48:53.079> selector<00:48:53.599> for<00:48:53.799> the<00:48:53.920> actual 00:48:54.190 --> 00:48:54.200 align:start position:0% turn on the selector for the actual 00:48:54.200 --> 00:48:55.349 align:start position:0% turn on the selector for the actual operation<00:48:54.520> that<00:48:54.640> we're<00:48:54.799> doing<00:48:55.079> the<00:48:55.200> other 00:48:55.349 --> 00:48:55.359 align:start position:0% operation that we're doing the other 00:48:55.359 --> 00:48:57.870 align:start position:0% operation that we're doing the other ones<00:48:55.520> we<00:48:55.599> don't<00:48:55.760> care<00:48:55.920> about<00:48:56.160> them<00:48:56.839> so<00:48:57.559> the<00:48:57.680> way 00:48:57.870 --> 00:48:57.880 align:start position:0% ones we don't care about them so the way 00:48:57.880 --> 00:49:01.069 align:start position:0% ones we don't care about them so the way this<00:48:58.079> works<00:48:58.480> is<00:48:59.079> the<00:48:59.520> selector<00:49:00.520> for<00:49:00.880> this 00:49:01.069 --> 00:49:01.079 align:start position:0% this works is the selector for this 00:49:01.079 --> 00:49:03.190 align:start position:0% this works is the selector for this array<00:49:01.480> is<00:49:01.640> going<00:49:01.799> to<00:49:01.920> be<00:49:02.079> the<00:49:02.280> op<00:49:02.640> code<00:49:02.960> so 00:49:03.190 --> 00:49:03.200 align:start position:0% array is going to be the op code so 00:49:03.200 --> 00:49:04.950 align:start position:0% array is going to be the op code so remember<00:49:03.559> the<00:49:03.680> op<00:49:04.000> code<00:49:04.200> of<00:49:04.359> Greater<00:49:04.760> from 00:49:04.950 --> 00:49:04.960 align:start position:0% remember the op code of Greater from 00:49:04.960 --> 00:49:08.829 align:start position:0% remember the op code of Greater from entries<00:49:05.280> is<00:49:05.440> up<00:49:05.680> code<00:49:05.880> number<00:49:06.160> four<00:49:07.119> so 00:49:08.829 --> 00:49:08.839 align:start position:0% entries is up code number four so 00:49:08.839 --> 00:49:13.510 align:start position:0% entries is up code number four so uh<00:49:09.839> one0<00:49:10.640> 1<00:49:11.200> two<00:49:12.200> 3<00:49:12.559> 4<00:49:12.960> yeah<00:49:13.079> it's<00:49:13.200> currently 00:49:13.510 --> 00:49:13.520 align:start position:0% uh one0 1 two 3 4 yeah it's currently 00:49:13.520 --> 00:49:15.549 align:start position:0% uh one0 1 two 3 4 yeah it's currently the<00:49:13.599> fourth<00:49:13.920> one<00:49:14.400> so<00:49:14.839> when<00:49:15.040> greater<00:49:15.319> form 00:49:15.549 --> 00:49:15.559 align:start position:0% the fourth one so when greater form 00:49:15.559 --> 00:49:17.230 align:start position:0% the fourth one so when greater form entries<00:49:15.839> is<00:49:15.960> turned<00:49:16.240> on<00:49:16.640> what<00:49:16.839> actually<00:49:17.040> gets 00:49:17.230 --> 00:49:17.240 align:start position:0% entries is turned on what actually gets 00:49:17.240 --> 00:49:21.069 align:start position:0% entries is turned on what actually gets checked<00:49:17.559> is<00:49:17.680> an<00:49:17.839> end<00:49:18.200> statement<00:49:19.240> on<00:49:20.240> whether 00:49:21.069 --> 00:49:21.079 align:start position:0% checked is an end statement on whether 00:49:21.079 --> 00:49:23.390 align:start position:0% checked is an end statement on whether statement<00:49:22.040> the<00:49:22.319> the<00:49:22.400> first<00:49:22.640> statement<00:49:23.040> is<00:49:23.280> is 00:49:23.390 --> 00:49:23.400 align:start position:0% statement the the first statement is is 00:49:23.400 --> 00:49:25.069 align:start position:0% statement the the first statement is is indeed<00:49:23.680> a<00:49:23.839> value<00:49:24.079> of<00:49:24.240> statement<00:49:24.760> in<00:49:24.880> the 00:49:25.069 --> 00:49:25.079 align:start position:0% indeed a value of statement in the 00:49:25.079 --> 00:49:26.430 align:start position:0% indeed a value of statement in the second<00:49:25.359> statement<00:49:25.720> is<00:49:25.839> indeed<00:49:26.040> a<00:49:26.160> value<00:49:26.319> of 00:49:26.430 --> 00:49:26.440 align:start position:0% second statement is indeed a value of 00:49:26.440 --> 00:49:27.270 align:start position:0% second statement is indeed a value of statement 00:49:27.270 --> 00:49:27.280 align:start position:0% statement 00:49:27.280 --> 00:49:28.910 align:start position:0% statement so<00:49:27.440> if<00:49:27.559> you<00:49:27.760> read<00:49:28.079> this<00:49:28.319> this<00:49:28.559> doesn't 00:49:28.910 --> 00:49:28.920 align:start position:0% so if you read this this doesn't 00:49:28.920 --> 00:49:30.789 align:start position:0% so if you read this this doesn't actually<00:49:29.200> do<00:49:29.400> the<00:49:29.559> greater<00:49:29.880> from<00:49:30.119> entries 00:49:30.789 --> 00:49:30.799 align:start position:0% actually do the greater from entries 00:49:30.799 --> 00:49:32.109 align:start position:0% actually do the greater from entries right<00:49:31.040> what<00:49:31.119> it<00:49:31.280> does<00:49:31.440> is<00:49:31.520> it<00:49:31.680> just<00:49:31.799> checks 00:49:32.109 --> 00:49:32.119 align:start position:0% right what it does is it just checks 00:49:32.119 --> 00:49:34.190 align:start position:0% right what it does is it just checks that<00:49:32.240> you're<00:49:32.559> doing<00:49:32.960> the<00:49:33.119> greater<00:49:33.480> than<00:49:33.799> on 00:49:34.190 --> 00:49:34.200 align:start position:0% that you're doing the greater than on 00:49:34.200 --> 00:49:35.950 align:start position:0% that you're doing the greater than on actual<00:49:34.480> entries<00:49:35.200> not<00:49:35.400> whether<00:49:35.599> the<00:49:35.680> first<00:49:35.839> one 00:49:35.950 --> 00:49:35.960 align:start position:0% actual entries not whether the first one 00:49:35.960 --> 00:49:37.870 align:start position:0% actual entries not whether the first one is<00:49:36.040> greater<00:49:36.280> than<00:49:36.400> the<00:49:36.480> second<00:49:36.720> one<00:49:37.280> so<00:49:37.640> for 00:49:37.870 --> 00:49:37.880 align:start position:0% is greater than the second one so for 00:49:37.880 --> 00:49:39.589 align:start position:0% is greater than the second one so for reasons<00:49:38.359> obscure<00:49:38.839> that<00:49:38.920> it<00:49:39.240> discovered<00:49:39.480> this 00:49:39.589 --> 00:49:39.599 align:start position:0% reasons obscure that it discovered this 00:49:39.599 --> 00:49:40.910 align:start position:0% reasons obscure that it discovered this morning<00:49:39.799> and<00:49:39.880> we'll<00:49:40.040> have<00:49:40.119> to<00:49:40.240> ask<00:49:40.440> aad<00:49:40.839> why 00:49:40.910 --> 00:49:40.920 align:start position:0% morning and we'll have to ask aad why 00:49:40.920 --> 00:49:42.309 align:start position:0% morning and we'll have to ask aad why it's<00:49:41.040> done<00:49:41.280> this<00:49:41.400> way<00:49:41.640> the<00:49:41.839> way<00:49:42.040> the<00:49:42.160> place 00:49:42.309 --> 00:49:42.319 align:start position:0% it's done this way the way the place 00:49:42.319 --> 00:49:44.270 align:start position:0% it's done this way the way the place where<00:49:42.480> we<00:49:42.680> actually<00:49:42.880> do<00:49:43.119> this<00:49:43.280> checked<00:49:43.680> is 00:49:44.270 --> 00:49:44.280 align:start position:0% where we actually do this checked is 00:49:44.280 --> 00:49:47.309 align:start position:0% where we actually do this checked is here<00:49:45.280> so<00:49:45.480> we<00:49:45.640> have<00:49:46.119> the<00:49:46.280> greater<00:49:46.599> than<00:49:46.799> up<00:49:47.079> code 00:49:47.309 --> 00:49:47.319 align:start position:0% here so we have the greater than up code 00:49:47.319 --> 00:49:49.910 align:start position:0% here so we have the greater than up code Target<00:49:48.040> and<00:49:48.160> we<00:49:48.280> say<00:49:48.599> hey<00:49:49.040> if<00:49:49.200> the<00:49:49.319> current<00:49:49.640> up 00:49:49.910 --> 00:49:49.920 align:start position:0% Target and we say hey if the current up 00:49:49.920 --> 00:49:52.589 align:start position:0% Target and we say hey if the current up code<00:49:50.160> is<00:49:50.359> indeed<00:49:50.799> the<00:49:50.920> greater<00:49:51.240> than<00:49:52.040> from<00:49:52.480> the 00:49:52.589 --> 00:49:52.599 align:start position:0% code is indeed the greater than from the 00:49:52.599 --> 00:49:54.150 align:start position:0% code is indeed the greater than from the greater<00:49:52.839> from<00:49:52.960> entries<00:49:53.319> up<00:49:53.520> code<00:49:53.720> we<00:49:53.839> do<00:49:54.000> an 00:49:54.150 --> 00:49:54.160 align:start position:0% greater from entries up code we do an 00:49:54.160 --> 00:49:57.630 align:start position:0% greater from entries up code we do an assertion<00:49:55.040> that<00:49:55.200> says<00:49:55.960> uh<00:49:56.119> it<00:49:56.280> it<00:49:57.040> that<00:49:57.440> that 00:49:57.630 --> 00:49:57.640 align:start position:0% assertion that says uh it it that that 00:49:57.640 --> 00:49:59.270 align:start position:0% assertion that says uh it it that that something<00:49:57.960> is<00:49:58.160> less<00:49:58.440> than<00:49:58.760> and<00:49:58.880> here<00:49:59.079> the 00:49:59.270 --> 00:49:59.280 align:start position:0% something is less than and here the 00:49:59.280 --> 00:50:00.910 align:start position:0% something is less than and here the statement<00:49:59.640> two<00:49:59.880> is<00:50:00.040> less<00:50:00.200> than<00:50:00.319> the<00:50:00.440> statement 00:50:00.910 --> 00:50:00.920 align:start position:0% statement two is less than the statement 00:50:00.920 --> 00:50:03.549 align:start position:0% statement two is less than the statement one<00:50:01.599> so<00:50:02.119> you'll<00:50:02.359> see<00:50:02.720> this<00:50:02.839> is<00:50:03.000> still<00:50:03.119> a<00:50:03.280> messy 00:50:03.549 --> 00:50:03.559 align:start position:0% one so you'll see this is still a messy 00:50:03.559 --> 00:50:05.470 align:start position:0% one so you'll see this is still a messy code<00:50:03.799> base<00:50:04.319> but<00:50:04.520> at<00:50:04.680> the<00:50:04.720> end<00:50:04.839> of<00:50:04.960> the<00:50:05.079> day 00:50:05.470 --> 00:50:05.480 align:start position:0% code base but at the end of the day 00:50:05.480 --> 00:50:07.230 align:start position:0% code base but at the end of the day everything<00:50:06.119> you<00:50:06.240> know<00:50:06.599> the<00:50:06.720> operation<00:50:07.119> that 00:50:07.230 --> 00:50:07.240 align:start position:0% everything you know the operation that 00:50:07.240 --> 00:50:08.710 align:start position:0% everything you know the operation that gots<00:50:07.440> executed<00:50:07.880> at<00:50:08.000> the<00:50:08.040> end<00:50:08.160> of<00:50:08.400> just<00:50:08.520> gets 00:50:08.710 --> 00:50:08.720 align:start position:0% gots executed at the end of just gets 00:50:08.720 --> 00:50:10.829 align:start position:0% gots executed at the end of just gets converted<00:50:09.440> into<00:50:09.920> some<00:50:10.240> some<00:50:10.400> circuit 00:50:10.829 --> 00:50:10.839 align:start position:0% converted into some some circuit 00:50:10.839 --> 00:50:13.190 align:start position:0% converted into some some circuit operation<00:50:11.599> and<00:50:11.720> so<00:50:12.400> you<00:50:12.680> also<00:50:12.799> notice<00:50:13.119> that 00:50:13.190 --> 00:50:13.200 align:start position:0% operation and so you also notice that 00:50:13.200 --> 00:50:15.230 align:start position:0% operation and so you also notice that it's<00:50:13.359> actually<00:50:13.640> pretty<00:50:14.000> easy<00:50:14.559> to<00:50:14.760> add<00:50:15.000> new 00:50:15.230 --> 00:50:15.240 align:start position:0% it's actually pretty easy to add new 00:50:15.240 --> 00:50:17.230 align:start position:0% it's actually pretty easy to add new operations<00:50:16.000> right<00:50:16.200> like<00:50:16.400> here<00:50:16.760> we<00:50:16.960> just<00:50:17.119> had 00:50:17.230 --> 00:50:17.240 align:start position:0% operations right like here we just had 00:50:17.240 --> 00:50:19.069 align:start position:0% operations right like here we just had to<00:50:17.440> add<00:50:17.640> like<00:50:17.920> eight<00:50:18.079> or<00:50:18.240> nine<00:50:18.440> lines<00:50:18.680> of<00:50:18.799> code 00:50:19.069 --> 00:50:19.079 align:start position:0% to add like eight or nine lines of code 00:50:19.079 --> 00:50:21.589 align:start position:0% to add like eight or nine lines of code to<00:50:19.240> add<00:50:19.599> to<00:50:19.760> to<00:50:19.920> add<00:50:20.040> an<00:50:20.319> operation<00:50:21.319> um<00:50:21.520> of 00:50:21.589 --> 00:50:21.599 align:start position:0% to add to to add an operation um of 00:50:21.599 --> 00:50:22.589 align:start position:0% to add to to add an operation um of course<00:50:21.760> there<00:50:21.839> are<00:50:21.960> difficulties<00:50:22.440> when<00:50:22.520> you 00:50:22.589 --> 00:50:22.599 align:start position:0% course there are difficulties when you 00:50:22.599 --> 00:50:24.109 align:start position:0% course there are difficulties when you start<00:50:22.799> having<00:50:23.040> complex<00:50:23.400> data<00:50:23.640> types<00:50:23.960> like 00:50:24.109 --> 00:50:24.119 align:start position:0% start having complex data types like 00:50:24.119 --> 00:50:26.430 align:start position:0% start having complex data types like arrays<00:50:24.559> Etc<00:50:25.119> but<00:50:25.480> a<00:50:25.599> lot<00:50:25.720> of<00:50:25.839> the<00:50:26.200> difficulty 00:50:26.430 --> 00:50:26.440 align:start position:0% arrays Etc but a lot of the difficulty 00:50:26.440 --> 00:50:28.870 align:start position:0% arrays Etc but a lot of the difficulty in<00:50:26.839> system<00:50:27.160> is<00:50:27.319> to<00:50:27.920> write<00:50:28.359> everything<00:50:28.680> else 00:50:28.870 --> 00:50:28.880 align:start position:0% in system is to write everything else 00:50:28.880 --> 00:50:30.710 align:start position:0% in system is to write everything else that<00:50:29.040> happens<00:50:29.359> on<00:50:29.599> top<00:50:29.799> of<00:50:29.960> these<00:50:30.119> logical<00:50:30.520> up 00:50:30.710 --> 00:50:30.720 align:start position:0% that happens on top of these logical up 00:50:30.720 --> 00:50:32.109 align:start position:0% that happens on top of these logical up codes<00:50:30.960> so<00:50:31.040> that<00:50:31.160> you<00:50:31.280> can<00:50:31.400> manipulate<00:50:31.920> them 00:50:32.109 --> 00:50:32.119 align:start position:0% codes so that you can manipulate them 00:50:32.119 --> 00:50:34.589 align:start position:0% codes so that you can manipulate them easily<00:50:32.680> because<00:50:33.599> one<00:50:33.880> one<00:50:34.040> thing<00:50:34.200> we<00:50:34.319> did<00:50:34.480> is 00:50:34.589 --> 00:50:34.599 align:start position:0% easily because one one thing we did is 00:50:34.599 --> 00:50:36.349 align:start position:0% easily because one one thing we did is we<00:50:34.760> had<00:50:34.960> this<00:50:35.200> massive<00:50:35.599> we<00:50:35.680> have<00:50:35.839> this<00:50:36.000> massive 00:50:36.349 --> 00:50:36.359 align:start position:0% we had this massive we have this massive 00:50:36.359 --> 00:50:38.510 align:start position:0% we had this massive we have this massive test<00:50:37.079> that<00:50:37.319> checks<00:50:37.720> this<00:50:37.880> kind<00:50:38.000> of<00:50:38.160> like<00:50:38.319> web 00:50:38.510 --> 00:50:38.520 align:start position:0% test that checks this kind of like web 00:50:38.520 --> 00:50:41.109 align:start position:0% test that checks this kind of like web of<00:50:38.760> trust<00:50:39.160> like<00:50:39.680> computation<00:50:40.680> um<00:50:40.880> and<00:50:41.000> when 00:50:41.109 --> 00:50:41.119 align:start position:0% of trust like computation um and when 00:50:41.119 --> 00:50:42.710 align:start position:0% of trust like computation um and when you<00:50:41.280> write<00:50:41.559> these<00:50:41.720> up<00:50:41.960> codes<00:50:42.200> yourself<00:50:42.559> it 00:50:42.710 --> 00:50:42.720 align:start position:0% you write these up codes yourself it 00:50:42.720 --> 00:50:43.910 align:start position:0% you write these up codes yourself it just<00:50:42.839> takes<00:50:43.079> hours<00:50:43.440> and<00:50:43.559> most<00:50:43.680> of<00:50:43.760> the<00:50:43.839> time 00:50:43.910 --> 00:50:43.920 align:start position:0% just takes hours and most of the time 00:50:43.920 --> 00:50:46.349 align:start position:0% just takes hours and most of the time you<00:50:44.040> get<00:50:44.119> it<00:50:44.280> wrong<00:50:44.799> so<00:50:45.200> like<00:50:45.359> a<00:50:45.480> lot<00:50:45.599> of<00:50:45.839> the 00:50:46.349 --> 00:50:46.359 align:start position:0% you get it wrong so like a lot of the 00:50:46.359 --> 00:50:49.510 align:start position:0% you get it wrong so like a lot of the the<00:50:46.880> a<00:50:46.960> lot<00:50:47.079> of<00:50:47.200> the<00:50:47.400> smart<00:50:47.880> stuff<00:50:48.760> here<00:50:49.359> that 00:50:49.510 --> 00:50:49.520 align:start position:0% the a lot of the smart stuff here that 00:50:49.520 --> 00:50:51.069 align:start position:0% the a lot of the smart stuff here that makes<00:50:49.760> this<00:50:49.960> easy<00:50:50.160> to<00:50:50.319> use<00:50:50.680> comes<00:50:50.839> from<00:50:50.960> The 00:50:51.069 --> 00:50:51.079 align:start position:0% makes this easy to use comes from The 00:50:51.079 --> 00:50:52.870 align:start position:0% makes this easy to use comes from The Logical<00:50:51.520> programming<00:50:51.960> language<00:50:52.599> right<00:50:52.760> and 00:50:52.870 --> 00:50:52.880 align:start position:0% Logical programming language right and 00:50:52.880 --> 00:50:54.190 align:start position:0% Logical programming language right and then<00:50:53.000> the<00:50:53.119> layer<00:50:53.359> on<00:50:53.559> top<00:50:53.799> of<00:50:53.880> course<00:50:54.000> you<00:50:54.079> have 00:50:54.190 --> 00:50:54.200 align:start position:0% then the layer on top of course you have 00:50:54.200 --> 00:50:55.990 align:start position:0% then the layer on top of course you have to<00:50:54.280> write<00:50:54.440> the<00:50:54.559> circuits<00:50:54.920> correctly<00:50:55.680> um<00:50:55.839> some 00:50:55.990 --> 00:50:56.000 align:start position:0% to write the circuits correctly um some 00:50:56.000 --> 00:50:57.309 align:start position:0% to write the circuits correctly um some of<00:50:56.119> the<00:50:56.200> circuits<00:50:56.640> here<00:50:56.760> is<00:50:56.920> like<00:50:57.079> pretty 00:50:57.309 --> 00:50:57.319 align:start position:0% of the circuits here is like pretty 00:50:57.319 --> 00:50:59.589 align:start position:0% of the circuits here is like pretty tricky<00:50:57.799> like<00:50:58.000> if<00:50:58.079> you<00:50:58.200> want<00:50:58.319> to<00:50:58.720> show<00:50:59.079> that 00:50:59.589 --> 00:50:59.599 align:start position:0% tricky like if you want to show that 00:50:59.599 --> 00:51:01.470 align:start position:0% tricky like if you want to show that that<00:50:59.720> an<00:50:59.880> entry<00:51:00.160> is<00:51:00.240> contained<00:51:00.520> in<00:51:00.640> an<00:51:00.799> array 00:51:01.470 --> 00:51:01.480 align:start position:0% that an entry is contained in an array 00:51:01.480 --> 00:51:03.470 align:start position:0% that an entry is contained in an array you<00:51:01.599> can<00:51:02.160> you<00:51:02.240> should<00:51:02.400> do<00:51:02.599> this<00:51:02.720> using<00:51:03.200> like<00:51:03.319> a 00:51:03.470 --> 00:51:03.480 align:start position:0% you can you should do this using like a 00:51:03.480 --> 00:51:05.030 align:start position:0% you can you should do this using like a Merkle<00:51:03.920> proof<00:51:04.119> as<00:51:04.200> an<00:51:04.319> example<00:51:04.680> to<00:51:04.799> make<00:51:04.920> this 00:51:05.030 --> 00:51:05.040 align:start position:0% Merkle proof as an example to make this 00:51:05.040 --> 00:51:06.430 align:start position:0% Merkle proof as an example to make this more<00:51:05.200> efficient<00:51:05.559> so<00:51:05.799> so<00:51:05.920> there's<00:51:06.079> a<00:51:06.200> lot<00:51:06.319> of 00:51:06.430 --> 00:51:06.440 align:start position:0% more efficient so so there's a lot of 00:51:06.440 --> 00:51:07.710 align:start position:0% more efficient so so there's a lot of work<00:51:06.720> here<00:51:06.960> both<00:51:07.119> at<00:51:07.240> the<00:51:07.319> programming 00:51:07.710 --> 00:51:07.720 align:start position:0% work here both at the programming 00:51:07.720 --> 00:51:09.270 align:start position:0% work here both at the programming language<00:51:08.040> at<00:51:08.160> the<00:51:08.319> Lo<00:51:08.559> logic<00:51:08.839> level<00:51:09.079> at<00:51:09.200> the 00:51:09.270 --> 00:51:09.280 align:start position:0% language at the Lo logic level at the 00:51:09.280 --> 00:51:12.190 align:start position:0% language at the Lo logic level at the circuit<00:51:09.599> level<00:51:10.559> um<00:51:11.240> so<00:51:11.400> I'll<00:51:11.559> stop<00:51:11.839> here<00:51:11.960> for 00:51:12.190 --> 00:51:12.200 align:start position:0% circuit level um so I'll stop here for 00:51:12.200 --> 00:51:14.270 align:start position:0% circuit level um so I'll stop here for questions<00:51:12.599> or<00:51:12.720> for<00:51:13.160> future<00:51:13.559> prompts<00:51:14.079> I<00:51:14.119> think 00:51:14.270 --> 00:51:14.280 align:start position:0% questions or for future prompts I think 00:51:14.280 --> 00:51:16.030 align:start position:0% questions or for future prompts I think we<00:51:14.400> have<00:51:14.640> five<00:51:14.839> more<00:51:15.040> minutes<00:51:15.520> before<00:51:15.760> I<00:51:15.880> pass 00:51:16.030 --> 00:51:16.040 align:start position:0% we have five more minutes before I pass 00:51:16.040 --> 00:51:22.589 align:start position:0% we have five more minutes before I pass it<00:51:16.200> off<00:51:16.799> and<00:51:17.160> we<00:51:17.240> can<00:51:17.400> also<00:51:17.559> do<00:51:17.720> maybe<00:51:17.920> a<00:51:18.000> light 00:51:22.589 --> 00:51:22.599 align:start position:0% 00:51:22.599 --> 00:51:29.789 align:start position:0% Q&A<00:51:23.599> cool<00:51:24.480> okay 00:51:29.789 --> 00:51:29.799 align:start position:0% 00:51:29.799 --> 00:51:31.470 align:start position:0% done 00:51:31.470 --> 00:51:31.480 align:start position:0% done 00:51:31.480 --> 00:51:33.870 align:start position:0% done here<00:51:32.480> yeah<00:51:32.640> this<00:51:32.760> is<00:51:32.839> a<00:51:33.000> good<00:51:33.240> question<00:51:33.760> I 00:51:33.870 --> 00:51:33.880 align:start position:0% here yeah this is a good question I 00:51:33.880 --> 00:51:38.349 align:start position:0% here yeah this is a good question I think<00:51:34.640> so<00:51:35.280> as<00:51:35.599> I've<00:51:35.880> been<00:51:36.839> working<00:51:37.240> on<00:51:37.599> so<00:51:37.920> my 00:51:38.349 --> 00:51:38.359 align:start position:0% think so as I've been working on so my 00:51:38.359 --> 00:51:40.750 align:start position:0% think so as I've been working on so my my<00:51:38.520> role<00:51:38.880> here<00:51:39.040> was<00:51:39.200> to<00:51:39.359> work<00:51:39.599> on<00:51:39.839> the<00:51:40.200> PEX 00:51:40.750 --> 00:51:40.760 align:start position:0% my role here was to work on the PEX 00:51:40.760 --> 00:51:43.990 align:start position:0% my role here was to work on the PEX language<00:51:41.799> um<00:51:42.799> and<00:51:42.960> what<00:51:43.079> I've<00:51:43.480> discovered<00:51:43.799> is 00:51:43.990 --> 00:51:44.000 align:start position:0% language um and what I've discovered is 00:51:44.000 --> 00:51:45.349 align:start position:0% language um and what I've discovered is like<00:51:44.319> every<00:51:44.480> time<00:51:44.640> I<00:51:44.720> want<00:51:44.799> to<00:51:44.920> make<00:51:45.119> more 00:51:45.349 --> 00:51:45.359 align:start position:0% like every time I want to make more 00:51:45.359 --> 00:51:46.829 align:start position:0% like every time I want to make more complicated<00:51:45.920> program<00:51:46.280> I<00:51:46.359> have<00:51:46.440> to<00:51:46.559> make<00:51:46.680> the 00:51:46.829 --> 00:51:46.839 align:start position:0% complicated program I have to make the 00:51:46.839 --> 00:51:49.150 align:start position:0% complicated program I have to make the program<00:51:47.559> language<00:51:47.960> smarter<00:51:48.559> which<00:51:48.640> is<00:51:48.839> not<00:51:49.000> a 00:51:49.150 --> 00:51:49.160 align:start position:0% program language smarter which is not a 00:51:49.160 --> 00:51:50.630 align:start position:0% program language smarter which is not a good<00:51:49.319> sign<00:51:49.640> so<00:51:49.799> that<00:51:49.920> means<00:51:50.160> we're<00:51:50.359> probably 00:51:50.630 --> 00:51:50.640 align:start position:0% good sign so that means we're probably 00:51:50.640 --> 00:51:53.789 align:start position:0% good sign so that means we're probably doing<00:51:50.839> it<00:51:50.960> in<00:51:51.040> a<00:51:51.280> wrong<00:51:51.559> way<00:51:52.160> so<00:51:52.960> um<00:51:53.559> one 00:51:53.789 --> 00:51:53.799 align:start position:0% doing it in a wrong way so um one 00:51:53.799 --> 00:51:56.750 align:start position:0% doing it in a wrong way so um one inspiration<00:51:54.400> we<00:51:54.599> have<00:51:54.920> which<00:51:55.799> is<00:51:55.960> still<00:51:56.240> a<00:51:56.640> bit 00:51:56.750 --> 00:51:56.760 align:start position:0% inspiration we have which is still a bit 00:51:56.760 --> 00:51:57.990 align:start position:0% inspiration we have which is still a bit out<00:51:56.880> of<00:51:57.040> touch<00:51:57.280> with<00:51:57.440> what<00:51:57.559> we're<00:51:57.720> trying<00:51:57.880> to 00:51:57.990 --> 00:51:58.000 align:start position:0% out of touch with what we're trying to 00:51:58.000 --> 00:52:00.030 align:start position:0% out of touch with what we're trying to do<00:51:58.160> is<00:51:58.359> interactive<00:51:58.799> theor<00:51:59.119> imprs<00:51:59.680> so<00:51:59.880> like 00:52:00.030 --> 00:52:00.040 align:start position:0% do is interactive theor imprs so like 00:52:00.040 --> 00:52:02.109 align:start position:0% do is interactive theor imprs so like IRAs<00:52:00.760> Etc<00:52:01.280> but<00:52:01.359> these<00:52:01.480> are<00:52:01.799> heavily 00:52:02.109 --> 00:52:02.119 align:start position:0% IRAs Etc but these are heavily 00:52:02.119 --> 00:52:03.990 align:start position:0% IRAs Etc but these are heavily human<00:52:02.480> assisted<00:52:03.280> and<00:52:03.400> also<00:52:03.599> they're<00:52:03.799> like 00:52:03.990 --> 00:52:04.000 align:start position:0% human assisted and also they're like 00:52:04.000 --> 00:52:06.150 align:start position:0% human assisted and also they're like very<00:52:04.200> complex<00:52:04.640> Beast<00:52:05.000> so<00:52:05.240> I<00:52:05.359> would<00:52:05.640> rather<00:52:05.920> not 00:52:06.150 --> 00:52:06.160 align:start position:0% very complex Beast so I would rather not 00:52:06.160 --> 00:52:07.390 align:start position:0% very complex Beast so I would rather not have<00:52:06.280> to<00:52:06.400> write<00:52:06.640> an<00:52:06.760> interactive<00:52:07.160> theor 00:52:07.390 --> 00:52:07.400 align:start position:0% have to write an interactive theor 00:52:07.400 --> 00:52:09.910 align:start position:0% have to write an interactive theor improver<00:52:07.799> in<00:52:07.880> order<00:52:08.079> to<00:52:08.240> make<00:52:08.400> this<00:52:08.520> useful<00:52:09.400> so 00:52:09.910 --> 00:52:09.920 align:start position:0% improver in order to make this useful so 00:52:09.920 --> 00:52:12.150 align:start position:0% improver in order to make this useful so um<00:52:10.640> yeah<00:52:10.960> I've<00:52:11.119> been<00:52:11.280> trying<00:52:11.520> to<00:52:11.640> find<00:52:11.920> in<00:52:12.040> the 00:52:12.150 --> 00:52:12.160 align:start position:0% um yeah I've been trying to find in the 00:52:12.160 --> 00:52:14.829 align:start position:0% um yeah I've been trying to find in the literature<00:52:12.720> outside<00:52:13.319> people<00:52:13.680> that<00:52:13.799> have<00:52:13.960> been 00:52:14.829 --> 00:52:14.839 align:start position:0% literature outside people that have been 00:52:14.839 --> 00:52:18.349 align:start position:0% literature outside people that have been writing<00:52:15.880> programs<00:52:16.880> in<00:52:17.040> an<00:52:17.240> imperative<00:52:17.839> way<00:52:18.119> or 00:52:18.349 --> 00:52:18.359 align:start position:0% writing programs in an imperative way or 00:52:18.359 --> 00:52:19.910 align:start position:0% writing programs in an imperative way or or<00:52:18.480> in<00:52:18.599> something<00:52:18.880> that's<00:52:19.119> not<00:52:19.680> like<00:52:19.799> a 00:52:19.910 --> 00:52:19.920 align:start position:0% or in something that's not like a 00:52:19.920 --> 00:52:21.069 align:start position:0% or in something that's not like a theorem<00:52:20.240> prover<00:52:20.520> in<00:52:20.599> a<00:52:20.720> way<00:52:20.839> where<00:52:20.920> you<00:52:21.000> can 00:52:21.069 --> 00:52:21.079 align:start position:0% theorem prover in a way where you can 00:52:21.079 --> 00:52:22.789 align:start position:0% theorem prover in a way where you can turn<00:52:21.280> that<00:52:21.400> into<00:52:21.559> logical<00:52:21.960> operations<00:52:22.680> and 00:52:22.789 --> 00:52:22.799 align:start position:0% turn that into logical operations and 00:52:22.799 --> 00:52:23.950 align:start position:0% turn that into logical operations and there<00:52:22.880> is<00:52:23.040> some<00:52:23.200> cool<00:52:23.400> stuff<00:52:23.599> out<00:52:23.799> there 00:52:23.950 --> 00:52:23.960 align:start position:0% there is some cool stuff out there 00:52:23.960 --> 00:52:25.190 align:start position:0% there is some cool stuff out there there's<00:52:24.160> this<00:52:24.280> programming<00:52:24.640> language<00:52:24.960> called 00:52:25.190 --> 00:52:25.200 align:start position:0% there's this programming language called 00:52:25.200 --> 00:52:26.630 align:start position:0% there's this programming language called agda<00:52:25.880> that<00:52:26.000> you<00:52:26.040> can<00:52:26.160> use<00:52:26.280> to<00:52:26.400> make<00:52:26.520> make 00:52:26.630 --> 00:52:26.640 align:start position:0% agda that you can use to make make 00:52:26.640 --> 00:52:28.789 align:start position:0% agda that you can use to make make proofs<00:52:26.920> about<00:52:27.079> its<00:52:27.200> own<00:52:27.480> correctness<00:52:28.480> um<00:52:28.680> and 00:52:28.789 --> 00:52:28.799 align:start position:0% proofs about its own correctness um and 00:52:28.799 --> 00:52:31.069 align:start position:0% proofs about its own correctness um and it's<00:52:29.000> like<00:52:29.200> not<00:52:29.440> that<00:52:29.680> bad<00:52:29.920> to<00:52:30.079> use<00:52:30.280> it<00:52:30.559> so<00:52:30.960> yeah 00:52:31.069 --> 00:52:31.079 align:start position:0% it's like not that bad to use it so yeah 00:52:31.079 --> 00:52:32.349 align:start position:0% it's like not that bad to use it so yeah there's<00:52:31.280> still<00:52:31.440> a<00:52:31.520> lot<00:52:31.640> of<00:52:31.760> work<00:52:31.920> to<00:52:32.040> do<00:52:32.240> there 00:52:32.349 --> 00:52:32.359 align:start position:0% there's still a lot of work to do there 00:52:32.359 --> 00:52:34.950 align:start position:0% there's still a lot of work to do there on<00:52:32.559> like<00:52:32.680> the<00:52:32.839> right<00:52:33.040> way<00:52:33.160> to<00:52:33.359> express<00:52:33.760> this 00:52:34.950 --> 00:52:34.960 align:start position:0% on like the right way to express this 00:52:34.960 --> 00:52:37.470 align:start position:0% on like the right way to express this one<00:52:35.960> challenge<00:52:36.400> that<00:52:36.559> we<00:52:36.799> have<00:52:37.079> that<00:52:37.200> we<00:52:37.280> set 00:52:37.470 --> 00:52:37.480 align:start position:0% one challenge that we have that we set 00:52:37.480 --> 00:52:39.030 align:start position:0% one challenge that we have that we set ourselves<00:52:37.880> to<00:52:38.079> be<00:52:38.200> able<00:52:38.359> to<00:52:38.520> achieve<00:52:38.799> with<00:52:38.920> the 00:52:39.030 --> 00:52:39.040 align:start position:0% ourselves to be able to achieve with the 00:52:39.040 --> 00:52:40.510 align:start position:0% ourselves to be able to achieve with the language<00:52:39.480> to<00:52:39.680> then<00:52:39.839> decide<00:52:40.119> if<00:52:40.240> it's<00:52:40.359> the 00:52:40.510 --> 00:52:40.520 align:start position:0% language to then decide if it's the 00:52:40.520 --> 00:52:41.990 align:start position:0% language to then decide if it's the right<00:52:40.680> way<00:52:40.799> to<00:52:40.880> do<00:52:41.000> it<00:52:41.119> or<00:52:41.240> not<00:52:41.480> is<00:52:41.599> to<00:52:41.720> be<00:52:41.839> able 00:52:41.990 --> 00:52:42.000 align:start position:0% right way to do it or not is to be able 00:52:42.000 --> 00:52:45.109 align:start position:0% right way to do it or not is to be able to<00:52:42.160> construct<00:52:42.680> pods<00:52:43.119> that<00:52:43.480> might<00:52:44.359> uh<00:52:44.480> recurse 00:52:45.109 --> 00:52:45.119 align:start position:0% to construct pods that might uh recurse 00:52:45.119 --> 00:52:46.870 align:start position:0% to construct pods that might uh recurse like<00:52:45.280> an<00:52:45.440> infinite<00:52:45.799> amount<00:52:45.960> of<00:52:46.160> time<00:52:46.680> so 00:52:46.870 --> 00:52:46.880 align:start position:0% like an infinite amount of time so 00:52:46.880 --> 00:52:48.190 align:start position:0% like an infinite amount of time so imagine<00:52:47.200> a<00:52:47.359> kind<00:52:47.480> of<00:52:47.599> pod<00:52:47.760> I<00:52:47.839> would<00:52:47.960> like<00:52:48.079> to 00:52:48.190 --> 00:52:48.200 align:start position:0% imagine a kind of pod I would like to 00:52:48.200 --> 00:52:50.230 align:start position:0% imagine a kind of pod I would like to construct<00:52:48.720> which<00:52:48.839> is<00:52:49.079> a<00:52:49.280> pod<00:52:49.599> that<00:52:49.720> shows<00:52:50.000> me 00:52:50.230 --> 00:52:50.240 align:start position:0% construct which is a pod that shows me 00:52:50.240 --> 00:52:52.670 align:start position:0% construct which is a pod that shows me how<00:52:50.599> far<00:52:50.839> away<00:52:51.160> I<00:52:51.280> am<00:52:51.480> from<00:52:51.680> someone<00:52:52.400> so<00:52:52.599> what 00:52:52.670 --> 00:52:52.680 align:start position:0% how far away I am from someone so what 00:52:52.680 --> 00:52:54.430 align:start position:0% how far away I am from someone so what this<00:52:52.839> would<00:52:52.960> mean<00:52:53.200> is<00:52:53.760> let's<00:52:53.920> say<00:52:54.040> it's<00:52:54.200> from 00:52:54.430 --> 00:52:54.440 align:start position:0% this would mean is let's say it's from 00:52:54.440 --> 00:52:56.470 align:start position:0% this would mean is let's say it's from how<00:52:54.599> far<00:52:54.760> away<00:52:54.960> is<00:52:55.119> from<00:52:55.280> Alex<00:52:55.799> so<00:52:55.960> Alex<00:52:56.280> is 00:52:56.470 --> 00:52:56.480 align:start position:0% how far away is from Alex so Alex is 00:52:56.480 --> 00:52:58.270 align:start position:0% how far away is from Alex so Alex is isues<00:52:56.720> a<00:52:56.839> part<00:52:57.000> to<00:52:57.119> all<00:52:57.200> of<00:52:57.319> his<00:52:57.520> friends<00:52:58.040> where 00:52:58.270 --> 00:52:58.280 align:start position:0% isues a part to all of his friends where 00:52:58.280 --> 00:53:01.390 align:start position:0% isues a part to all of his friends where he<00:52:58.640> has<00:52:59.640> a<00:52:59.760> bunch<00:52:59.920> of<00:53:00.000> logical<00:53:00.880> statments<00:53:01.319> that 00:53:01.390 --> 00:53:01.400 align:start position:0% he has a bunch of logical statments that 00:53:01.400 --> 00:53:03.069 align:start position:0% he has a bunch of logical statments that says<00:53:01.559> he<00:53:01.720> attested<00:53:02.040> to<00:53:02.160> someone's<00:53:02.480> public<00:53:02.720> key 00:53:03.069 --> 00:53:03.079 align:start position:0% says he attested to someone's public key 00:53:03.079 --> 00:53:04.470 align:start position:0% says he attested to someone's public key and<00:53:03.160> then<00:53:03.359> these<00:53:03.520> people<00:53:03.799> can<00:53:03.960> attest<00:53:04.240> to 00:53:04.470 --> 00:53:04.480 align:start position:0% and then these people can attest to 00:53:04.480 --> 00:53:05.750 align:start position:0% and then these people can attest to someone<00:53:04.720> else<00:53:04.960> like<00:53:05.119> me<00:53:05.319> because<00:53:05.520> I<00:53:05.599> don't 00:53:05.750 --> 00:53:05.760 align:start position:0% someone else like me because I don't 00:53:05.760 --> 00:53:07.549 align:start position:0% someone else like me because I don't actually<00:53:05.960> know<00:53:06.119> Alex<00:53:06.440> directly<00:53:07.119> and<00:53:07.319> I<00:53:07.440> would 00:53:07.549 --> 00:53:07.559 align:start position:0% actually know Alex directly and I would 00:53:07.559 --> 00:53:09.190 align:start position:0% actually know Alex directly and I would like<00:53:07.720> the<00:53:07.960> Pod<00:53:08.240> there<00:53:08.359> to<00:53:08.480> have<00:53:08.599> a<00:53:08.720> number<00:53:09.079> that 00:53:09.190 --> 00:53:09.200 align:start position:0% like the Pod there to have a number that 00:53:09.200 --> 00:53:11.950 align:start position:0% like the Pod there to have a number that says<00:53:09.520> I<00:53:09.599> am<00:53:09.880> two<00:53:10.200> degrees<00:53:10.920> away<00:53:11.160> from<00:53:11.359> Alex<00:53:11.839> and 00:53:11.950 --> 00:53:11.960 align:start position:0% says I am two degrees away from Alex and 00:53:11.960 --> 00:53:12.990 align:start position:0% says I am two degrees away from Alex and I<00:53:12.040> want<00:53:12.160> to<00:53:12.240> be<00:53:12.319> able<00:53:12.480> to<00:53:12.640> like<00:53:12.760> do<00:53:12.839> it<00:53:12.920> for 00:53:12.990 --> 00:53:13.000 align:start position:0% I want to be able to like do it for 00:53:13.000 --> 00:53:14.870 align:start position:0% I want to be able to like do it for someone<00:53:13.240> else<00:53:13.400> and<00:53:13.520> be<00:53:13.599> 3<00:53:13.799> degrees<00:53:14.040> for<00:53:14.200> Alex 00:53:14.870 --> 00:53:14.880 align:start position:0% someone else and be 3 degrees for Alex 00:53:14.880 --> 00:53:16.349 align:start position:0% someone else and be 3 degrees for Alex so<00:53:15.040> there's<00:53:15.200> a<00:53:15.359> trivial<00:53:15.720> way<00:53:15.839> to<00:53:16.000> do<00:53:16.160> this 00:53:16.349 --> 00:53:16.359 align:start position:0% so there's a trivial way to do this 00:53:16.359 --> 00:53:18.030 align:start position:0% so there's a trivial way to do this where<00:53:16.559> the<00:53:16.799> size<00:53:17.040> of<00:53:17.160> the<00:53:17.319> pods<00:53:17.640> in<00:53:17.720> terms<00:53:17.920> of 00:53:18.030 --> 00:53:18.040 align:start position:0% where the size of the pods in terms of 00:53:18.040 --> 00:53:19.510 align:start position:0% where the size of the pods in terms of how<00:53:18.160> many<00:53:18.319> logical<00:53:18.720> statements<00:53:19.119> it<00:53:19.240> has 00:53:19.510 --> 00:53:19.520 align:start position:0% how many logical statements it has 00:53:19.520 --> 00:53:21.349 align:start position:0% how many logical statements it has increases<00:53:20.040> linearly<00:53:20.760> with<00:53:20.880> the<00:53:21.040> distance 00:53:21.349 --> 00:53:21.359 align:start position:0% increases linearly with the distance 00:53:21.359 --> 00:53:23.390 align:start position:0% increases linearly with the distance from<00:53:21.559> Alex<00:53:22.280> we<00:53:22.400> would<00:53:22.599> like<00:53:22.720> to<00:53:22.839> do<00:53:23.040> this<00:53:23.160> in<00:53:23.240> a 00:53:23.390 --> 00:53:23.400 align:start position:0% from Alex we would like to do this in a 00:53:23.400 --> 00:53:24.829 align:start position:0% from Alex we would like to do this in a way<00:53:23.599> where<00:53:23.799> the<00:53:23.920> number<00:53:24.160> of<00:53:24.240> statements<00:53:24.680> does 00:53:24.829 --> 00:53:24.839 align:start position:0% way where the number of statements does 00:53:24.839 --> 00:53:26.870 align:start position:0% way where the number of statements does not<00:53:25.000> increase<00:53:25.359> linearly<00:53:26.040> by<00:53:26.200> having<00:53:26.680> more 00:53:26.870 --> 00:53:26.880 align:start position:0% not increase linearly by having more 00:53:26.880 --> 00:53:28.870 align:start position:0% not increase linearly by having more powerful<00:53:27.319> logic<00:53:27.680> where<00:53:27.839> we<00:53:27.920> can<00:53:28.200> count<00:53:28.559> using 00:53:28.870 --> 00:53:28.880 align:start position:0% powerful logic where we can count using 00:53:28.880 --> 00:53:30.309 align:start position:0% powerful logic where we can count using probably<00:53:29.119> first<00:53:29.359> order<00:53:29.680> logic<00:53:29.960> or<00:53:30.079> something 00:53:30.309 --> 00:53:30.319 align:start position:0% probably first order logic or something 00:53:30.319 --> 00:53:32.910 align:start position:0% probably first order logic or something else<00:53:30.559> like<00:53:30.760> that<00:53:31.240> and<00:53:31.400> also<00:53:31.760> where<00:53:32.240> the<00:53:32.480> script 00:53:32.910 --> 00:53:32.920 align:start position:0% else like that and also where the script 00:53:32.920 --> 00:53:34.710 align:start position:0% else like that and also where the script the<00:53:33.079> PEC<00:53:33.319> script<00:53:33.640> that<00:53:33.760> we<00:53:33.920> write<00:53:34.119> for<00:53:34.280> this<00:53:34.559> is 00:53:34.710 --> 00:53:34.720 align:start position:0% the PEC script that we write for this is 00:53:34.720 --> 00:53:37.430 align:start position:0% the PEC script that we write for this is the<00:53:34.880> same<00:53:35.119> for<00:53:35.440> every<00:53:36.359> degree<00:53:36.720> of<00:53:36.880> separation 00:53:37.430 --> 00:53:37.440 align:start position:0% the same for every degree of separation 00:53:37.440 --> 00:53:38.430 align:start position:0% the same for every degree of separation because<00:53:37.599> currently<00:53:37.960> the<00:53:38.040> way<00:53:38.160> you<00:53:38.200> would<00:53:38.359> do 00:53:38.430 --> 00:53:38.440 align:start position:0% because currently the way you would do 00:53:38.440 --> 00:53:39.510 align:start position:0% because currently the way you would do it<00:53:38.559> with<00:53:38.640> the<00:53:38.720> current<00:53:39.000> PEX<00:53:39.240> you<00:53:39.319> would<00:53:39.400> have 00:53:39.510 --> 00:53:39.520 align:start position:0% it with the current PEX you would have 00:53:39.520 --> 00:53:40.789 align:start position:0% it with the current PEX you would have to<00:53:39.680> write<00:53:39.920> different<00:53:40.200> scripts<00:53:40.520> for<00:53:40.640> each 00:53:40.789 --> 00:53:40.799 align:start position:0% to write different scripts for each 00:53:40.799 --> 00:53:42.670 align:start position:0% to write different scripts for each degree<00:53:41.040> of<00:53:41.160> separation<00:53:41.880> so<00:53:42.040> if<00:53:42.119> we<00:53:42.240> can<00:53:42.480> do 00:53:42.670 --> 00:53:42.680 align:start position:0% degree of separation so if we can do 00:53:42.680 --> 00:53:44.870 align:start position:0% degree of separation so if we can do that<00:53:43.280> in<00:53:43.359> a<00:53:43.480> way<00:53:43.599> where<00:53:43.720> it's<00:53:43.960> constant<00:53:44.559> size 00:53:44.870 --> 00:53:44.880 align:start position:0% that in a way where it's constant size 00:53:44.880 --> 00:53:47.470 align:start position:0% that in a way where it's constant size script<00:53:45.240> and<00:53:45.440> constant<00:53:45.880> side<00:53:46.480> logic<00:53:47.280> uh<00:53:47.400> we 00:53:47.470 --> 00:53:47.480 align:start position:0% script and constant side logic uh we 00:53:47.480 --> 00:53:49.470 align:start position:0% script and constant side logic uh we would<00:53:47.640> be<00:53:47.799> pretty<00:53:48.160> happy<00:53:48.760> if<00:53:48.880> we<00:53:49.040> cannot<00:53:49.319> do 00:53:49.470 --> 00:53:49.480 align:start position:0% would be pretty happy if we cannot do 00:53:49.480 --> 00:53:55.270 align:start position:0% would be pretty happy if we cannot do that<00:53:49.640> then<00:53:49.760> we'll<00:53:49.920> have<00:53:50.000> to<00:53:50.119> revisit<00:53:50.480> our 00:53:55.270 --> 00:53:55.280 align:start position:0% 00:53:55.280 --> 00:53:57.829 align:start position:0% approach<00:53:56.280> cool<00:53:56.440> cool<00:53:56.599> and<00:53:56.760> I<00:53:57.000> I'll<00:53:57.520> I<00:53:57.720> I'll 00:53:57.829 --> 00:53:57.839 align:start position:0% approach cool cool and I I'll I I'll 00:53:57.839 --> 00:53:59.750 align:start position:0% approach cool cool and I I'll I I'll close<00:53:58.079> it<00:53:58.319> here<00:53:58.960> um<00:53:59.160> now<00:53:59.319> we're<00:53:59.440> going<00:53:59.559> to<00:53:59.640> have 00:53:59.750 --> 00:53:59.760 align:start position:0% close it here um now we're going to have 00:53:59.760 --> 00:54:03.230 align:start position:0% close it here um now we're going to have a<00:53:59.920> talk<00:54:00.359> so<00:54:00.599> everybody<00:54:00.960> wake<00:54:01.240> up<00:54:01.880> uh<00:54:02.880> different 00:54:03.230 --> 00:54:03.240 align:start position:0% a talk so everybody wake up uh different 00:54:03.240 --> 00:54:04.630 align:start position:0% a talk so everybody wake up uh different person<00:54:03.599> different<00:54:03.880> style<00:54:04.319> we're<00:54:04.400> gonna<00:54:04.559> have 00:54:04.630 --> 00:54:04.640 align:start position:0% person different style we're gonna have 00:54:04.640 --> 00:54:06.470 align:start position:0% person different style we're gonna have a<00:54:04.760> talk<00:54:04.920> from<00:54:05.119> Arno<00:54:05.520> and<00:54:05.680> Ahmad<00:54:06.200> about<00:54:06.400> the 00:54:06.470 --> 00:54:06.480 align:start position:0% a talk from Arno and Ahmad about the 00:54:06.480 --> 00:54:07.950 align:start position:0% a talk from Arno and Ahmad about the circuits<00:54:06.839> and<00:54:06.920> how<00:54:07.000> they<00:54:07.119> were<00:54:07.240> put<00:54:07.480> together 00:54:07.950 --> 00:54:07.960 align:start position:0% circuits and how they were put together 00:54:07.960 --> 00:54:10.109 align:start position:0% circuits and how they were put together so<00:54:08.119> here<00:54:08.240> I<00:54:08.319> showed<00:54:08.559> you<00:54:08.720> guys<00:54:08.880> the<00:54:09.119> easy<00:54:09.520> part 00:54:10.109 --> 00:54:10.119 align:start position:0% so here I showed you guys the easy part 00:54:10.119 --> 00:54:12.030 align:start position:0% so here I showed you guys the easy part which<00:54:10.280> was<00:54:10.720> ex<00:54:11.119> putting<00:54:11.359> the<00:54:11.520> operations 00:54:12.030 --> 00:54:12.040 align:start position:0% which was ex putting the operations 00:54:12.040 --> 00:54:13.510 align:start position:0% which was ex putting the operations together<00:54:12.280> the<00:54:12.520> really<00:54:12.760> hard<00:54:13.000> part<00:54:13.160> of<00:54:13.319> this 00:54:13.510 --> 00:54:13.520 align:start position:0% together the really hard part of this 00:54:13.520 --> 00:54:15.190 align:start position:0% together the really hard part of this was<00:54:13.799> making<00:54:14.119> this<00:54:14.319> system<00:54:14.680> like<00:54:14.839> basically 00:54:15.190 --> 00:54:15.200 align:start position:0% was making this system like basically 00:54:15.200 --> 00:54:17.190 align:start position:0% was making this system like basically infinitely<00:54:15.799> recursive<00:54:16.799> where<00:54:16.920> you<00:54:17.040> can 00:54:17.190 --> 00:54:17.200 align:start position:0% infinitely recursive where you can 00:54:17.200 --> 00:54:19.390 align:start position:0% infinitely recursive where you can ingest<00:54:17.599> multiple<00:54:18.079> pods<00:54:18.440> some<00:54:18.599> snor<00:54:19.000> pods<00:54:19.240> some 00:54:19.390 --> 00:54:19.400 align:start position:0% ingest multiple pods some snor pods some 00:54:19.400 --> 00:54:20.710 align:start position:0% ingest multiple pods some snor pods some frony<00:54:19.839> pods<00:54:20.040> in<00:54:20.119> a<00:54:20.200> way<00:54:20.400> you<00:54:20.480> can<00:54:20.599> keep 00:54:20.710 --> 00:54:20.720 align:start position:0% frony pods in a way you can keep 00:54:20.720 --> 00:54:22.549 align:start position:0% frony pods in a way you can keep recursing<00:54:21.160> and<00:54:21.280> that<00:54:21.400> was<00:54:21.920> pretty<00:54:22.160> tricky<00:54:22.480> to 00:54:22.549 --> 00:54:22.559 align:start position:0% recursing and that was pretty tricky to 00:54:22.559 --> 00:54:24.750 align:start position:0% recursing and that was pretty tricky to do<00:54:22.760> correctly<00:54:23.559> so<00:54:23.880> that<00:54:24.000> will<00:54:24.119> be<00:54:24.359> the<00:54:24.680> the 00:54:24.750 --> 00:54:24.760 align:start position:0% do correctly so that will be the the 00:54:24.760 --> 00:54:26.069 align:start position:0% do correctly so that will be the the next<00:54:24.960> speakers<00:54:25.480> you<00:54:25.599> guys<00:54:25.680> want<00:54:25.799> to<00:54:25.880> come<00:54:26.000> on 00:54:26.069 --> 00:54:26.079 align:start position:0% next speakers you guys want to come on 00:54:26.079 --> 00:54:27.349 align:start position:0% next speakers you guys want to come on stage 00:54:27.349 --> 00:54:27.359 align:start position:0% stage 00:54:27.359 --> 00:54:28.770 align:start position:0% stage thank 00:54:28.770 --> 00:54:28.780 align:start position:0% thank 00:54:28.780 --> 00:54:36.710 align:start position:0% thank [Applause] 00:54:36.710 --> 00:54:36.720 align:start position:0% 00:54:36.720 --> 00:54:39.309 align:start position:0% you<00:54:37.720> and<00:54:38.000> while<00:54:38.160> we<00:54:38.359> prepare<00:54:38.720> if<00:54:38.880> anyone<00:54:39.160> has 00:54:39.309 --> 00:54:39.319 align:start position:0% you and while we prepare if anyone has 00:54:39.319 --> 00:54:41.109 align:start position:0% you and while we prepare if anyone has more<00:54:39.520> questions<00:54:40.000> I<00:54:40.079> can<00:54:40.240> answer<00:54:40.520> them<00:54:40.960> I'll 00:54:41.109 --> 00:54:41.119 align:start position:0% more questions I can answer them I'll 00:54:41.119 --> 00:54:47.309 align:start position:0% more questions I can answer them I'll just<00:54:41.240> take<00:54:41.400> the 00:54:47.309 --> 00:54:47.319 align:start position:0% 00:54:47.319 --> 00:54:53.670 align:start position:0% mic<00:54:48.319> hey<00:54:48.920> yesly<00:54:49.920> uh<00:54:50.799> so<00:54:51.280> some<00:54:52.040> uh<00:54:52.559> talk<00:54:52.880> about<00:54:53.440> K 00:54:53.670 --> 00:54:53.680 align:start position:0% mic hey yesly uh so some uh talk about K 00:54:53.680 --> 00:54:56.510 align:start position:0% mic hey yesly uh so some uh talk about K and<00:54:54.040> the<00:54:54.200> matching<00:54:54.480> logic<00:54:54.760> over<00:54:54.960> there<00:54:55.799> so 00:54:56.510 --> 00:54:56.520 align:start position:0% and the matching logic over there so 00:54:56.520 --> 00:55:00.230 align:start position:0% and the matching logic over there so hard<00:54:56.760> would<00:54:56.960> be<00:54:57.160> to<00:54:57.960> plug<00:54:58.520> the<00:54:58.839> result<00:54:59.400> of<00:54:59.680> the 00:55:00.230 --> 00:55:00.240 align:start position:0% hard would be to plug the result of the 00:55:00.240 --> 00:55:02.710 align:start position:0% hard would be to plug the result of the K<00:55:00.880> execution<00:55:01.400> so<00:55:01.680> the<00:55:01.799> magic<00:55:02.160> logic<00:55:02.480> over 00:55:02.710 --> 00:55:02.720 align:start position:0% K execution so the magic logic over 00:55:02.720 --> 00:55:06.549 align:start position:0% K execution so the magic logic over there<00:55:03.160> into<00:55:03.920> pods<00:55:04.920> um<00:55:05.280> yeah<00:55:05.480> I<00:55:05.599> think<00:55:06.040> so<00:55:06.440> we 00:55:06.549 --> 00:55:06.559 align:start position:0% there into pods um yeah I think so we 00:55:06.559 --> 00:55:08.510 align:start position:0% there into pods um yeah I think so we spent<00:55:06.799> a<00:55:06.880> bunch<00:55:07.040> of<00:55:07.160> time<00:55:07.280> looking<00:55:07.480> at<00:55:07.680> K<00:55:08.359> uh 00:55:08.510 --> 00:55:08.520 align:start position:0% spent a bunch of time looking at K uh 00:55:08.520 --> 00:55:10.309 align:start position:0% spent a bunch of time looking at K uh even<00:55:08.760> writing<00:55:09.200> some<00:55:09.480> like<00:55:09.640> little<00:55:10.119> K 00:55:10.309 --> 00:55:10.319 align:start position:0% even writing some like little K 00:55:10.319 --> 00:55:12.109 align:start position:0% even writing some like little K definitions<00:55:10.799> ourselves<00:55:11.280> for<00:55:11.480> like<00:55:11.599> toy 00:55:12.109 --> 00:55:12.119 align:start position:0% definitions ourselves for like toy 00:55:12.119 --> 00:55:14.589 align:start position:0% definitions ourselves for like toy languages<00:55:13.119> um<00:55:13.400> I<00:55:13.520> think<00:55:14.040> the<00:55:14.240> way<00:55:14.400> we're 00:55:14.589 --> 00:55:14.599 align:start position:0% languages um I think the way we're 00:55:14.599 --> 00:55:17.109 align:start position:0% languages um I think the way we're thinking<00:55:14.880> about<00:55:15.200> this<00:55:15.559> is<00:55:16.359> we<00:55:16.599> really<00:55:16.799> want<00:55:16.960> to 00:55:17.109 --> 00:55:17.119 align:start position:0% thinking about this is we really want to 00:55:17.119 --> 00:55:19.349 align:start position:0% thinking about this is we really want to figure<00:55:17.440> out<00:55:17.720> like<00:55:18.000> what's<00:55:18.359> the<00:55:18.880> right<00:55:19.079> tool 00:55:19.349 --> 00:55:19.359 align:start position:0% figure out like what's the right tool 00:55:19.359 --> 00:55:21.109 align:start position:0% figure out like what's the right tool for<00:55:19.559> the<00:55:19.799> job<00:55:20.400> you<00:55:20.520> know<00:55:20.680> because<00:55:20.880> we<00:55:20.960> were 00:55:21.109 --> 00:55:21.119 align:start position:0% for the job you know because we were 00:55:21.119 --> 00:55:22.349 align:start position:0% for the job you know because we were thinking<00:55:21.319> about<00:55:21.520> like<00:55:21.640> oh<00:55:21.760> should<00:55:21.920> we<00:55:22.119> just 00:55:22.349 --> 00:55:22.359 align:start position:0% thinking about like oh should we just 00:55:22.359 --> 00:55:25.029 align:start position:0% thinking about like oh should we just like<00:55:22.839> write<00:55:23.520> a<00:55:23.640> Z<00:55:24.000> proof<00:55:24.240> for<00:55:24.440> like<00:55:24.640> the 00:55:25.029 --> 00:55:25.039 align:start position:0% like write a Z proof for like the 00:55:25.039 --> 00:55:26.549 align:start position:0% like write a Z proof for like the the<00:55:25.319> improver<00:55:25.680> or<00:55:25.799> something<00:55:26.000> like<00:55:26.119> that<00:55:26.400> and 00:55:26.549 --> 00:55:26.559 align:start position:0% the improver or something like that and 00:55:26.559 --> 00:55:28.029 align:start position:0% the improver or something like that and there's<00:55:26.760> been<00:55:26.880> a<00:55:26.960> bunch<00:55:27.160> of<00:55:27.280> work<00:55:27.640> there<00:55:27.880> from 00:55:28.029 --> 00:55:28.039 align:start position:0% there's been a bunch of work there from 00:55:28.039 --> 00:55:29.789 align:start position:0% there's been a bunch of work there from like<00:55:28.160> students<00:55:28.440> of<00:55:28.599> Dan<00:55:28.799> Bonet<00:55:29.119> as<00:55:29.200> an<00:55:29.359> example 00:55:29.789 --> 00:55:29.799 align:start position:0% like students of Dan Bonet as an example 00:55:29.799 --> 00:55:31.150 align:start position:0% like students of Dan Bonet as an example but<00:55:29.960> these<00:55:30.119> proofs<00:55:30.359> are<00:55:30.599> incredibly 00:55:31.150 --> 00:55:31.160 align:start position:0% but these proofs are incredibly 00:55:31.160 --> 00:55:32.710 align:start position:0% but these proofs are incredibly expensive<00:55:31.880> and<00:55:32.039> really<00:55:32.160> hard<00:55:32.319> to<00:55:32.440> put 00:55:32.710 --> 00:55:32.720 align:start position:0% expensive and really hard to put 00:55:32.720 --> 00:55:35.190 align:start position:0% expensive and really hard to put together<00:55:33.559> I<00:55:33.680> don't<00:55:33.960> know<00:55:34.400> what<00:55:34.520> are<00:55:34.760> numbers 00:55:35.190 --> 00:55:35.200 align:start position:0% together I don't know what are numbers 00:55:35.200 --> 00:55:36.510 align:start position:0% together I don't know what are numbers yet<00:55:35.359> for<00:55:35.599> something<00:55:35.839> like<00:55:36.039> K<00:55:36.200> I<00:55:36.240> don't<00:55:36.359> know<00:55:36.440> if 00:55:36.510 --> 00:55:36.520 align:start position:0% yet for something like K I don't know if 00:55:36.520 --> 00:55:37.990 align:start position:0% yet for something like K I don't know if you<00:55:36.599> guys<00:55:36.720> are<00:55:36.839> writing<00:55:37.200> proofs<00:55:37.480> yourself<00:55:37.839> or 00:55:37.990 --> 00:55:38.000 align:start position:0% you guys are writing proofs yourself or 00:55:38.000 --> 00:55:39.309 align:start position:0% you guys are writing proofs yourself or using<00:55:38.200> something<00:55:38.440> like<00:55:38.520> a<00:55:38.640> zkm<00:55:39.079> but<00:55:39.200> it's 00:55:39.309 --> 00:55:39.319 align:start position:0% using something like a zkm but it's 00:55:39.319 --> 00:55:42.670 align:start position:0% using something like a zkm but it's probably<00:55:39.640> very<00:55:40.400> expensive<00:55:41.400> um<00:55:42.039> like<00:55:42.319> the<00:55:42.440> pods 00:55:42.670 --> 00:55:42.680 align:start position:0% probably very expensive um like the pods 00:55:42.680 --> 00:55:44.029 align:start position:0% probably very expensive um like the pods we<00:55:42.839> put<00:55:43.039> together<00:55:43.280> here<00:55:43.440> they<00:55:43.599> take<00:55:43.760> like<00:55:43.880> two 00:55:44.029 --> 00:55:44.039 align:start position:0% we put together here they take like two 00:55:44.039 --> 00:55:45.670 align:start position:0% we put together here they take like two seconds<00:55:44.359> on<00:55:44.480> a<00:55:44.720> on<00:55:44.799> a<00:55:44.960> laptop<00:55:45.359> so<00:55:45.520> that's 00:55:45.670 --> 00:55:45.680 align:start position:0% seconds on a on a laptop so that's 00:55:45.680 --> 00:55:47.430 align:start position:0% seconds on a on a laptop so that's pretty<00:55:45.920> neat<00:55:46.520> but<00:55:46.640> in<00:55:46.760> some<00:55:46.960> ways<00:55:47.200> what<00:55:47.319> I 00:55:47.430 --> 00:55:47.440 align:start position:0% pretty neat but in some ways what I 00:55:47.440 --> 00:55:49.829 align:start position:0% pretty neat but in some ways what I would<00:55:47.599> like<00:55:47.760> is<00:55:47.880> it<00:55:48.039> would<00:55:48.200> like<00:55:48.960> I<00:55:49.599> one<00:55:49.720> thing 00:55:49.829 --> 00:55:49.839 align:start position:0% would like is it would like I one thing 00:55:49.839 --> 00:55:51.029 align:start position:0% would like is it would like I one thing that<00:55:49.960> would<00:55:50.079> be<00:55:50.200> really<00:55:50.400> cool<00:55:50.599> is<00:55:50.680> to<00:55:50.799> be<00:55:50.880> able 00:55:51.029 --> 00:55:51.039 align:start position:0% that would be really cool is to be able 00:55:51.039 --> 00:55:53.549 align:start position:0% that would be really cool is to be able to<00:55:51.240> dynamically<00:55:51.880> size<00:55:52.760> the<00:55:52.960> complexity<00:55:53.440> of 00:55:53.549 --> 00:55:53.559 align:start position:0% to dynamically size the complexity of 00:55:53.559 --> 00:55:54.710 align:start position:0% to dynamically size the complexity of the<00:55:53.680> logic<00:55:54.000> based<00:55:54.200> on<00:55:54.280> the<00:55:54.359> claims<00:55:54.599> you're 00:55:54.710 --> 00:55:54.720 align:start position:0% the logic based on the claims you're 00:55:54.720 --> 00:55:56.390 align:start position:0% the logic based on the claims you're trying<00:55:54.920> to<00:55:55.079> make<00:55:55.240> and<00:55:55.400> use<00:55:55.640> less<00:55:55.839> powerful 00:55:56.390 --> 00:55:56.400 align:start position:0% trying to make and use less powerful 00:55:56.400 --> 00:55:57.950 align:start position:0% trying to make and use less powerful kinds<00:55:56.599> of<00:55:56.720> logic<00:55:57.039> that<00:55:57.119> are<00:55:57.319> faster<00:55:57.599> to<00:55:57.720> prove 00:55:57.950 --> 00:55:57.960 align:start position:0% kinds of logic that are faster to prove 00:55:57.960 --> 00:55:59.630 align:start position:0% kinds of logic that are faster to prove or<00:55:58.119> more<00:55:58.280> powerful<00:55:58.680> kinds<00:55:58.880> of<00:55:59.039> logic<00:55:59.400> that<00:55:59.520> are 00:55:59.630 --> 00:55:59.640 align:start position:0% or more powerful kinds of logic that are 00:55:59.640 --> 00:56:01.270 align:start position:0% or more powerful kinds of logic that are more<00:55:59.839> expensive<00:56:00.200> to<00:56:00.319> prove<00:56:00.839> that<00:56:00.920> would<00:56:01.039> be<00:56:01.160> a 00:56:01.270 --> 00:56:01.280 align:start position:0% more expensive to prove that would be a 00:56:01.280 --> 00:56:02.950 align:start position:0% more expensive to prove that would be a really<00:56:01.480> cool<00:56:01.760> system<00:56:02.319> whereas<00:56:02.599> an<00:56:02.680> example 00:56:02.950 --> 00:56:02.960 align:start position:0% really cool system whereas an example 00:56:02.960 --> 00:56:05.029 align:start position:0% really cool system whereas an example you<00:56:03.039> could<00:56:03.200> tap<00:56:03.400> into<00:56:03.760> K<00:56:04.400> if<00:56:04.480> you<00:56:04.559> want<00:56:04.680> to<00:56:04.799> make 00:56:05.029 --> 00:56:05.039 align:start position:0% you could tap into K if you want to make 00:56:05.039 --> 00:56:06.589 align:start position:0% you could tap into K if you want to make like<00:56:05.319> really<00:56:05.599> complex<00:56:05.960> proves<00:56:06.280> and<00:56:06.440> very 00:56:06.589 --> 00:56:06.599 align:start position:0% like really complex proves and very 00:56:06.599 --> 00:56:07.789 align:start position:0% like really complex proves and very powerful<00:56:06.920> proves<00:56:07.240> but<00:56:07.319> if<00:56:07.400> you<00:56:07.520> just<00:56:07.599> want<00:56:07.720> to 00:56:07.789 --> 00:56:07.799 align:start position:0% powerful proves but if you just want to 00:56:07.799 --> 00:56:09.750 align:start position:0% powerful proves but if you just want to show<00:56:08.039> your<00:56:08.160> age<00:56:08.319> is<00:56:08.440> over<00:56:08.640> 18<00:56:09.319> you<00:56:09.400> can<00:56:09.559> just 00:56:09.750 --> 00:56:09.760 align:start position:0% show your age is over 18 you can just 00:56:09.760 --> 00:56:11.630 align:start position:0% show your age is over 18 you can just like<00:56:09.960> make<00:56:10.160> that<00:56:10.359> pod<00:56:10.640> yourself<00:56:11.039> in<00:56:11.200> like<00:56:11.359> 30 00:56:11.630 --> 00:56:11.640 align:start position:0% like make that pod yourself in like 30 00:56:11.640 --> 00:56:13.670 align:start position:0% like make that pod yourself in like 30 millisecond<00:56:12.160> on<00:56:12.319> a<00:56:12.559> on<00:56:12.640> a<00:56:13.039> phone<00:56:13.280> or<00:56:13.400> something 00:56:13.670 --> 00:56:13.680 align:start position:0% millisecond on a on a phone or something 00:56:13.680 --> 00:56:15.109 align:start position:0% millisecond on a on a phone or something like<00:56:13.839> that<00:56:14.280> but<00:56:14.520> I<00:56:14.559> would<00:56:14.680> be<00:56:14.760> interested<00:56:15.000> to 00:56:15.109 --> 00:56:15.119 align:start position:0% like that but I would be interested to 00:56:15.119 --> 00:56:16.549 align:start position:0% like that but I would be interested to look<00:56:15.240> more<00:56:15.359> into<00:56:15.520> it<00:56:15.760> are<00:56:15.839> you<00:56:15.960> working<00:56:16.200> at<00:56:16.359> pi 00:56:16.549 --> 00:56:16.559 align:start position:0% look more into it are you working at pi 00:56:16.559 --> 00:56:18.549 align:start position:0% look more into it are you working at pi squared<00:56:17.280> awesome<00:56:17.599> yes<00:56:17.839> okay<00:56:18.000> cool<00:56:18.280> yeah<00:56:18.400> so 00:56:18.549 --> 00:56:18.559 align:start position:0% squared awesome yes okay cool yeah so 00:56:18.559 --> 00:56:19.870 align:start position:0% squared awesome yes okay cool yeah so you're<00:56:18.760> the<00:56:18.880> guys<00:56:19.079> that<00:56:19.200> like<00:56:19.319> prove<00:56:19.559> the<00:56:19.680> K 00:56:19.870 --> 00:56:19.880 align:start position:0% you're the guys that like prove the K 00:56:19.880 --> 00:56:21.349 align:start position:0% you're the guys that like prove the K framework<00:56:20.280> execution<00:56:20.799> right<00:56:21.039> yeah<00:56:21.160> yeah<00:56:21.280> we 00:56:21.349 --> 00:56:21.359 align:start position:0% framework execution right yeah yeah we 00:56:21.359 --> 00:56:26.390 align:start position:0% framework execution right yeah yeah we can<00:56:21.480> chat<00:56:21.720> about<00:56:21.960> this<00:56:22.520> all<00:56:22.640> right<00:56:23.520> thank<00:56:23.680> you 00:56:26.390 --> 00:56:26.400 align:start position:0% can chat about this all right thank you 00:56:26.400 --> 00:56:29.549 align:start position:0% can chat about this all right thank you oh 00:56:29.549 --> 00:56:29.559 align:start position:0% 00:56:29.559 --> 00:56:33.069 align:start position:0% yeah<00:56:30.559> all<00:56:30.760> right<00:56:31.520> welcome<00:56:31.839> to<00:56:32.119> the<00:56:32.559> to<00:56:32.799> our 00:56:33.069 --> 00:56:33.079 align:start position:0% yeah all right welcome to the to our 00:56:33.079 --> 00:56:36.309 align:start position:0% yeah all right welcome to the to our lightning<00:56:33.480> talk<00:56:33.720> on<00:56:34.400> pod<00:56:34.760> two<00:56:35.760> uh<00:56:35.880> show<00:56:36.119> of 00:56:36.309 --> 00:56:36.319 align:start position:0% lightning talk on pod two uh show of 00:56:36.319 --> 00:56:38.549 align:start position:0% lightning talk on pod two uh show of hands<00:56:36.880> who<00:56:37.119> here<00:56:37.319> is<00:56:37.599> not<00:56:37.880> yet<00:56:38.000> sure<00:56:38.280> what<00:56:38.400> a 00:56:38.549 --> 00:56:38.559 align:start position:0% hands who here is not yet sure what a 00:56:38.559 --> 00:56:39.710 align:start position:0% hands who here is not yet sure what a pod 00:56:39.710 --> 00:56:39.720 align:start position:0% pod 00:56:39.720 --> 00:56:41.829 align:start position:0% pod is<00:56:40.720> who<00:56:40.880> here<00:56:41.039> is<00:56:41.160> too<00:56:41.319> afraid<00:56:41.559> to<00:56:41.640> put<00:56:41.760> their 00:56:41.829 --> 00:56:41.839 align:start position:0% is who here is too afraid to put their 00:56:41.839 --> 00:56:42.630 align:start position:0% is who here is too afraid to put their hand 00:56:42.630 --> 00:56:42.640 align:start position:0% hand 00:56:42.640 --> 00:56:45.670 align:start position:0% hand up<00:56:43.640> okay<00:56:43.760> at<00:56:43.839> least<00:56:44.039> one<00:56:44.240> person<00:56:45.119> um<00:56:45.280> so<00:56:45.440> pods 00:56:45.670 --> 00:56:45.680 align:start position:0% up okay at least one person um so pods 00:56:45.680 --> 00:56:47.309 align:start position:0% up okay at least one person um so pods in<00:56:45.760> a<00:56:45.880> nutshell<00:56:46.440> you<00:56:46.599> basically<00:56:46.920> have<00:56:47.000> a<00:56:47.119> key 00:56:47.309 --> 00:56:47.319 align:start position:0% in a nutshell you basically have a key 00:56:47.319 --> 00:56:48.670 align:start position:0% in a nutshell you basically have a key Value<00:56:47.559> Store<00:56:47.839> of<00:56:47.960> some<00:56:48.119> sort<00:56:48.319> you 00:56:48.670 --> 00:56:48.680 align:start position:0% Value Store of some sort you 00:56:48.680 --> 00:56:51.750 align:start position:0% Value Store of some sort you cryptographically<00:56:49.680> um<00:56:49.960> you<00:56:50.079> know<00:56:51.000> sign<00:56:51.319> it<00:56:51.640> in 00:56:51.750 --> 00:56:51.760 align:start position:0% cryptographically um you know sign it in 00:56:51.760 --> 00:56:54.109 align:start position:0% cryptographically um you know sign it in some<00:56:52.000> manner<00:56:52.920> um<00:56:53.119> I'll<00:56:53.559> I'll<00:56:53.720> say<00:56:53.880> a<00:56:53.960> little 00:56:54.109 --> 00:56:54.119 align:start position:0% some manner um I'll I'll say a little 00:56:54.119 --> 00:56:55.829 align:start position:0% some manner um I'll I'll say a little bit<00:56:54.280> about<00:56:54.480> that<00:56:54.599> in<00:56:54.720> a<00:56:54.880> moment<00:56:55.480> um<00:56:55.599> we'll<00:56:55.720> be 00:56:55.829 --> 00:56:55.839 align:start position:0% bit about that in a moment um we'll be 00:56:55.839 --> 00:56:57.829 align:start position:0% bit about that in a moment um we'll be talking<00:56:56.039> about<00:56:56.319> the<00:56:56.440> next<00:56:56.640> generation<00:56:57.119> of<00:56:57.440> pod 00:56:57.829 --> 00:56:57.839 align:start position:0% talking about the next generation of pod 00:56:57.839 --> 00:57:02.029 align:start position:0% talking about the next generation of pod that<00:56:58.000> was<00:56:58.400> uh<00:56:59.000> already<00:56:59.280> alluded<00:56:59.640> to<00:57:00.000> by<00:57:01.039> Justin 00:57:02.029 --> 00:57:02.039 align:start position:0% that was uh already alluded to by Justin 00:57:02.039 --> 00:57:03.829 align:start position:0% that was uh already alluded to by Justin and<00:57:02.160> the<00:57:02.280> summary<00:57:02.880> of<00:57:03.079> pod<00:57:03.319> two<00:57:03.520> is<00:57:03.640> that<00:57:03.720> it 00:57:03.829 --> 00:57:03.839 align:start position:0% and the summary of pod two is that it 00:57:03.839 --> 00:57:05.589 align:start position:0% and the summary of pod two is that it allows<00:57:04.119> for<00:57:04.280> easier<00:57:04.559> composability<00:57:04.920> than<00:57:05.359> pod 00:57:05.589 --> 00:57:05.599 align:start position:0% allows for easier composability than pod 00:57:05.599 --> 00:57:07.309 align:start position:0% allows for easier composability than pod one<00:57:05.960> that's<00:57:06.160> essentially<00:57:06.599> it<00:57:07.039> all<00:57:07.200> the 00:57:07.309 --> 00:57:07.319 align:start position:0% one that's essentially it all the 00:57:07.319 --> 00:57:09.589 align:start position:0% one that's essentially it all the advantages<00:57:07.720> of<00:57:07.880> pod<00:57:08.079> one<00:57:08.640> are<00:57:08.920> there<00:57:09.160> in<00:57:09.359> pod 00:57:09.589 --> 00:57:09.599 align:start position:0% advantages of pod one are there in pod 00:57:09.599 --> 00:57:12.069 align:start position:0% advantages of pod one are there in pod two<00:57:10.200> it's<00:57:10.400> just<00:57:10.520> a<00:57:10.680> matter<00:57:11.000> of<00:57:11.359> having<00:57:11.839> being 00:57:12.069 --> 00:57:12.079 align:start position:0% two it's just a matter of having being 00:57:12.079 --> 00:57:15.309 align:start position:0% two it's just a matter of having being able<00:57:12.359> to<00:57:13.200> compose<00:57:13.799> pods<00:57:14.280> which<00:57:14.440> we<00:57:14.799> cannot<00:57:15.119> do 00:57:15.309 --> 00:57:15.319 align:start position:0% able to compose pods which we cannot do 00:57:15.319 --> 00:57:17.789 align:start position:0% able to compose pods which we cannot do with<00:57:15.480> pod<00:57:15.760> one<00:57:16.480> in<00:57:16.680> quite<00:57:16.880> the<00:57:17.000> same 00:57:17.789 --> 00:57:17.799 align:start position:0% with pod one in quite the same 00:57:17.799 --> 00:57:21.950 align:start position:0% with pod one in quite the same way<00:57:18.799> so<00:57:19.119> just<00:57:19.400> a<00:57:19.680> QR<00:57:20.039> code<00:57:20.480> with<00:57:21.319> uh<00:57:21.480> link<00:57:21.760> to 00:57:21.950 --> 00:57:21.960 align:start position:0% way so just a QR code with uh link to 00:57:21.960 --> 00:57:24.349 align:start position:0% way so just a QR code with uh link to our<00:57:22.359> repo<00:57:22.960> you<00:57:23.039> can<00:57:23.200> find<00:57:23.400> all<00:57:23.559> the<00:57:23.680> code<00:57:24.000> here 00:57:24.349 --> 00:57:24.359 align:start position:0% our repo you can find all the code here 00:57:24.359 --> 00:57:25.950 align:start position:0% our repo you can find all the code here uh<00:57:24.480> Justin's<00:57:24.880> already<00:57:25.160> provided<00:57:25.559> this<00:57:25.720> link 00:57:25.950 --> 00:57:25.960 align:start position:0% uh Justin's already provided this link 00:57:25.960 --> 00:57:27.589 align:start position:0% uh Justin's already provided this link but<00:57:26.319> here<00:57:26.440> it<00:57:26.520> is<00:57:26.640> in<00:57:26.720> the<00:57:26.799> form<00:57:26.920> of<00:57:27.000> a<00:57:27.119> QR<00:57:27.400> code 00:57:27.589 --> 00:57:27.599 align:start position:0% but here it is in the form of a QR code 00:57:27.599 --> 00:57:31.829 align:start position:0% but here it is in the form of a QR code if<00:57:27.680> you<00:57:27.799> like<00:57:27.920> to<00:57:28.839> scan<00:57:29.200> QR<00:57:29.480> codes<00:57:29.920> instead<00:57:30.920> um 00:57:31.829 --> 00:57:31.839 align:start position:0% if you like to scan QR codes instead um 00:57:31.839 --> 00:57:34.910 align:start position:0% if you like to scan QR codes instead um so<00:57:32.520> we<00:57:32.720> actually<00:57:32.920> have<00:57:33.079> an<00:57:33.240> ongoing<00:57:33.839> Port<00:57:34.640> of 00:57:34.910 --> 00:57:34.920 align:start position:0% so we actually have an ongoing Port of 00:57:34.920 --> 00:57:37.430 align:start position:0% so we actually have an ongoing Port of pod<00:57:35.160> one<00:57:35.400> to<00:57:35.720> rust<00:57:36.240> and<00:57:36.359> that's<00:57:36.520> in<00:57:36.640> the<00:57:36.880> parket 00:57:37.430 --> 00:57:37.440 align:start position:0% pod one to rust and that's in the parket 00:57:37.440 --> 00:57:39.990 align:start position:0% pod one to rust and that's in the parket Pod<00:57:37.880> subdirectory<00:57:38.880> and<00:57:38.960> then<00:57:39.119> pod<00:57:39.359> two<00:57:39.559> has 00:57:39.990 --> 00:57:40.000 align:start position:0% Pod subdirectory and then pod two has 00:57:40.000 --> 00:57:44.549 align:start position:0% Pod subdirectory and then pod two has the<00:57:41.000> our<00:57:41.200> current<00:57:42.079> efforts<00:57:43.079> uh<00:57:43.680> in<00:57:44.079> developing 00:57:44.549 --> 00:57:44.559 align:start position:0% the our current efforts uh in developing 00:57:44.559 --> 00:57:48.829 align:start position:0% the our current efforts uh in developing pod<00:57:45.280> 2<00:57:46.280> so<00:57:46.559> pod<00:57:46.799> one<00:57:47.280> so<00:57:47.559> far<00:57:48.119> as<00:57:48.200> I<00:57:48.359> mentioned 00:57:48.829 --> 00:57:48.839 align:start position:0% pod 2 so pod one so far as I mentioned 00:57:48.839 --> 00:57:50.710 align:start position:0% pod 2 so pod one so far as I mentioned you<00:57:49.000> basically<00:57:49.319> have<00:57:49.400> a<00:57:49.520> key<00:57:49.760> Value<00:57:50.160> Store<00:57:50.559> you 00:57:50.710 --> 00:57:50.720 align:start position:0% you basically have a key Value Store you 00:57:50.720 --> 00:57:53.349 align:start position:0% you basically have a key Value Store you meriz<00:57:51.319> it<00:57:51.760> this<00:57:51.880> isn't<00:57:52.119> an<00:57:52.280> entirely<00:57:52.680> new<00:57:52.920> idea 00:57:53.349 --> 00:57:53.359 align:start position:0% meriz it this isn't an entirely new idea 00:57:53.359 --> 00:57:55.190 align:start position:0% meriz it this isn't an entirely new idea but<00:57:53.480> it<00:57:53.599> is<00:57:53.720> a<00:57:53.920> solid<00:57:54.280> one<00:57:54.680> there's<00:57:54.880> a<00:57:55.000> nice 00:57:55.190 --> 00:57:55.200 align:start position:0% but it is a solid one there's a nice 00:57:55.200 --> 00:57:58.150 align:start position:0% but it is a solid one there's a nice blog<00:57:55.480> post<00:57:55.720> by<00:57:55.839> Joe<00:57:56.520> geps<00:57:57.000> and<00:57:57.520> merizing<00:57:58.079> the 00:57:58.150 --> 00:57:58.160 align:start position:0% blog post by Joe geps and merizing the 00:57:58.160 --> 00:58:00.549 align:start position:0% blog post by Joe geps and merizing the key<00:57:58.319> value<00:57:58.520> store<00:57:58.760> for<00:57:58.880> Fun<00:57:59.079> and<00:57:59.280> Profit<00:58:00.079> worth 00:58:00.549 --> 00:58:00.559 align:start position:0% key value store for Fun and Profit worth 00:58:00.559 --> 00:58:03.589 align:start position:0% key value store for Fun and Profit worth reading<00:58:01.559> um<00:58:02.559> and<00:58:02.760> we<00:58:02.920> construct<00:58:03.319> things<00:58:03.480> in 00:58:03.589 --> 00:58:03.599 align:start position:0% reading um and we construct things in 00:58:03.599 --> 00:58:05.109 align:start position:0% reading um and we construct things in such<00:58:03.760> a<00:58:03.839> way<00:58:04.000> that<00:58:04.079> it's<00:58:04.240> easy<00:58:04.440> to<00:58:04.559> make<00:58:04.720> ZK 00:58:05.109 --> 00:58:05.119 align:start position:0% such a way that it's easy to make ZK 00:58:05.119 --> 00:58:07.470 align:start position:0% such a way that it's easy to make ZK proofs<00:58:05.440> about<00:58:05.640> these<00:58:05.799> things<00:58:06.160> yeah<00:58:06.920> so<00:58:07.039> we<00:58:07.160> use 00:58:07.470 --> 00:58:07.480 align:start position:0% proofs about these things yeah so we use 00:58:07.480 --> 00:58:09.430 align:start position:0% proofs about these things yeah so we use the<00:58:07.799> you<00:58:07.920> know<00:58:08.359> appropriate<00:58:08.960> signature 00:58:09.430 --> 00:58:09.440 align:start position:0% the you know appropriate signature 00:58:09.440 --> 00:58:12.710 align:start position:0% the you know appropriate signature scheme<00:58:10.119> and<00:58:10.280> so<00:58:10.440> on<00:58:10.960> so<00:58:11.240> we<00:58:11.319> can<00:58:11.480> use<00:58:11.920> grth<00:58:12.359> 16 00:58:12.710 --> 00:58:12.720 align:start position:0% scheme and so on so we can use grth 16 00:58:12.720 --> 00:58:13.829 align:start position:0% scheme and so on so we can use grth 16 for 00:58:13.829 --> 00:58:13.839 align:start position:0% for 00:58:13.839 --> 00:58:16.390 align:start position:0% for proofs<00:58:14.839> um<00:58:15.000> and<00:58:15.079> the<00:58:15.200> ZK<00:58:15.559> workflow<00:58:15.960> for<00:58:16.119> pod 00:58:16.390 --> 00:58:16.400 align:start position:0% proofs um and the ZK workflow for pod 00:58:16.400 --> 00:58:18.950 align:start position:0% proofs um and the ZK workflow for pod one<00:58:16.880> is<00:58:17.520> essentially<00:58:17.920> you<00:58:18.119> take<00:58:18.280> your<00:58:18.480> pods 00:58:18.950 --> 00:58:18.960 align:start position:0% one is essentially you take your pods 00:58:18.960 --> 00:58:20.510 align:start position:0% one is essentially you take your pods you<00:58:19.079> have<00:58:19.240> some<00:58:19.400> kind<00:58:19.520> of<00:58:19.640> configuration 00:58:20.510 --> 00:58:20.520 align:start position:0% you have some kind of configuration 00:58:20.520 --> 00:58:22.069 align:start position:0% you have some kind of configuration proof<00:58:20.839> configuration<00:58:21.440> that<00:58:21.559> says<00:58:21.880> what<00:58:22.000> you 00:58:22.069 --> 00:58:22.079 align:start position:0% proof configuration that says what you 00:58:22.079 --> 00:58:24.109 align:start position:0% proof configuration that says what you want<00:58:22.200> to<00:58:22.359> prove<00:58:23.319> and<00:58:23.440> you<00:58:23.559> plug<00:58:23.760> that<00:58:23.880> into 00:58:24.109 --> 00:58:24.119 align:start position:0% want to prove and you plug that into 00:58:24.119 --> 00:58:26.549 align:start position:0% want to prove and you plug that into some<00:58:24.319> procedure<00:58:24.720> called<00:58:24.920> GPC<00:58:25.400> prove<00:58:26.319> what<00:58:26.440> you 00:58:26.549 --> 00:58:26.559 align:start position:0% some procedure called GPC prove what you 00:58:26.559 --> 00:58:28.349 align:start position:0% some procedure called GPC prove what you get<00:58:26.680> out<00:58:26.799> of<00:58:26.920> that<00:58:27.079> is<00:58:27.160> a<00:58:27.280> Gro<00:58:27.599> 16<00:58:27.920> proof 00:58:28.349 --> 00:58:28.359 align:start position:0% get out of that is a Gro 16 proof 00:58:28.359 --> 00:58:30.349 align:start position:0% get out of that is a Gro 16 proof together<00:58:28.559> with<00:58:28.720> some<00:58:29.039> revealed<00:58:29.480> claims<00:58:30.000> and 00:58:30.349 --> 00:58:30.359 align:start position:0% together with some revealed claims and 00:58:30.359 --> 00:58:32.829 align:start position:0% together with some revealed claims and this<00:58:30.440> is<00:58:30.920> the<00:58:31.079> rough<00:58:31.359> workflow<00:58:32.359> now<00:58:32.559> let's<00:58:32.720> say 00:58:32.829 --> 00:58:32.839 align:start position:0% this is the rough workflow now let's say 00:58:32.839 --> 00:58:34.910 align:start position:0% this is the rough workflow now let's say you<00:58:32.960> wanted<00:58:33.240> to<00:58:33.640> take<00:58:33.839> the<00:58:33.960> output<00:58:34.359> of<00:58:34.559> this 00:58:34.910 --> 00:58:34.920 align:start position:0% you wanted to take the output of this 00:58:34.920 --> 00:58:37.029 align:start position:0% you wanted to take the output of this and<00:58:35.079> generate<00:58:35.440> a<00:58:35.559> brand<00:58:35.839> new<00:58:36.039> proof<00:58:36.799> so 00:58:37.029 --> 00:58:37.039 align:start position:0% and generate a brand new proof so 00:58:37.039 --> 00:58:38.950 align:start position:0% and generate a brand new proof so something<00:58:37.480> like<00:58:38.200> you<00:58:38.319> know<00:58:38.480> taking<00:58:38.720> a<00:58:38.799> bunch 00:58:38.950 --> 00:58:38.960 align:start position:0% something like you know taking a bunch 00:58:38.960 --> 00:58:40.710 align:start position:0% something like you know taking a bunch of<00:58:39.079> PODS<00:58:39.760> taking<00:58:40.000> a<00:58:40.079> bunch<00:58:40.240> of<00:58:40.359> proofs 00:58:40.710 --> 00:58:40.720 align:start position:0% of PODS taking a bunch of proofs 00:58:40.720 --> 00:58:42.829 align:start position:0% of PODS taking a bunch of proofs revealed<00:58:41.119> claims<00:58:41.960> putting<00:58:42.200> it<00:58:42.280> in<00:58:42.400> a<00:58:42.520> box<00:58:42.720> and 00:58:42.829 --> 00:58:42.839 align:start position:0% revealed claims putting it in a box and 00:58:42.839 --> 00:58:45.390 align:start position:0% revealed claims putting it in a box and then<00:58:42.960> spitting<00:58:43.280> out<00:58:43.400> a<00:58:43.520> brand<00:58:43.720> new<00:58:44.200> proof<00:58:45.200> um 00:58:45.390 --> 00:58:45.400 align:start position:0% then spitting out a brand new proof um 00:58:45.400 --> 00:58:47.390 align:start position:0% then spitting out a brand new proof um but<00:58:45.520> how<00:58:45.640> do<00:58:45.720> we<00:58:45.880> do<00:58:46.119> this<00:58:46.680> um<00:58:47.039> it's<00:58:47.200> not 00:58:47.390 --> 00:58:47.400 align:start position:0% but how do we do this um it's not 00:58:47.400 --> 00:58:49.270 align:start position:0% but how do we do this um it's not entirely<00:58:47.799> clear<00:58:48.079> how<00:58:48.200> to<00:58:48.359> do<00:58:48.559> this<00:58:48.960> with<00:58:49.079> our 00:58:49.270 --> 00:58:49.280 align:start position:0% entirely clear how to do this with our 00:58:49.280 --> 00:58:52.710 align:start position:0% entirely clear how to do this with our current<00:58:49.599> setup<00:58:50.400> uh<00:58:50.520> using<00:58:50.839> circom<00:58:51.520> and<00:58:52.160> grth 00:58:52.710 --> 00:58:52.720 align:start position:0% current setup uh using circom and grth 00:58:52.720 --> 00:58:56.069 align:start position:0% current setup uh using circom and grth 16<00:58:53.720> now<00:58:54.160> why<00:58:54.319> would<00:58:54.480> we<00:58:54.640> not<00:58:54.960> proceed<00:58:55.760> with 00:58:56.069 --> 00:58:56.079 align:start position:0% 16 now why would we not proceed with 00:58:56.079 --> 00:58:59.270 align:start position:0% 16 now why would we not proceed with Groth<00:58:56.400> 16<00:58:56.760> why<00:58:56.839> is<00:58:57.000> Groth<00:58:57.400> 16<00:58:58.079> not 00:58:59.270 --> 00:58:59.280 align:start position:0% Groth 16 why is Groth 16 not 00:58:59.280 --> 00:59:02.710 align:start position:0% Groth 16 why is Groth 16 not suitable<00:59:00.280> for<00:59:00.559> this<00:59:00.920> application<00:59:01.920> R<00:59:02.200> now<00:59:02.520> so 00:59:02.710 --> 00:59:02.720 align:start position:0% suitable for this application R now so 00:59:02.720 --> 00:59:04.549 align:start position:0% suitable for this application R now so very<00:59:02.920> quickly<00:59:03.520> uh<00:59:03.680> the<00:59:03.799> main<00:59:04.000> idea<00:59:04.280> here<00:59:04.400> is 00:59:04.549 --> 00:59:04.559 align:start position:0% very quickly uh the main idea here is 00:59:04.559 --> 00:59:06.510 align:start position:0% very quickly uh the main idea here is like<00:59:04.880> we<00:59:04.960> can<00:59:05.119> do<00:59:05.280> recursion<00:59:05.920> over<00:59:06.119> the<00:59:06.280> grth 00:59:06.510 --> 00:59:06.520 align:start position:0% like we can do recursion over the grth 00:59:06.520 --> 00:59:08.549 align:start position:0% like we can do recursion over the grth 16<00:59:06.880> it's<00:59:06.960> just<00:59:07.160> like<00:59:07.359> it's<00:59:07.680> too<00:59:07.880> expensive<00:59:08.359> for 00:59:08.549 --> 00:59:08.559 align:start position:0% 16 it's just like it's too expensive for 00:59:08.559 --> 00:59:10.750 align:start position:0% 16 it's just like it's too expensive for like<00:59:08.680> most<00:59:08.839> of<00:59:09.000> like<00:59:09.160> the<00:59:09.319> real<00:59:09.640> world<00:59:10.160> uh 00:59:10.750 --> 00:59:10.760 align:start position:0% like most of like the real world uh 00:59:10.760 --> 00:59:13.710 align:start position:0% like most of like the real world uh applications<00:59:11.760> uh<00:59:12.160> the<00:59:12.240> main<00:59:12.400> idea<00:59:12.599> is<00:59:12.720> that 00:59:13.710 --> 00:59:13.720 align:start position:0% applications uh the main idea is that 00:59:13.720 --> 00:59:15.549 align:start position:0% applications uh the main idea is that this<00:59:13.880> Brute<00:59:14.200> Force<00:59:14.440> recursion<00:59:14.960> will<00:59:15.119> be<00:59:15.319> like 00:59:15.549 --> 00:59:15.559 align:start position:0% this Brute Force recursion will be like 00:59:15.559 --> 00:59:18.789 align:start position:0% this Brute Force recursion will be like uh<00:59:15.760> we<00:59:15.960> Define<00:59:16.240> a<00:59:16.640> circuit<00:59:17.640> that<00:59:17.960> verifies<00:59:18.640> uh 00:59:18.789 --> 00:59:18.799 align:start position:0% uh we Define a circuit that verifies uh 00:59:18.799 --> 00:59:21.910 align:start position:0% uh we Define a circuit that verifies uh like<00:59:18.920> a<00:59:19.000> full<00:59:19.280> proof<00:59:20.079> of<00:59:20.240> the<00:59:20.359> same<00:59:20.599> system<00:59:21.559> so 00:59:21.910 --> 00:59:21.920 align:start position:0% like a full proof of the same system so 00:59:21.920 --> 00:59:23.910 align:start position:0% like a full proof of the same system so in<00:59:22.119> in<00:59:22.480> 16<00:59:22.720> will<00:59:22.839> be<00:59:22.960> like<00:59:23.079> having<00:59:23.240> a<00:59:23.359> A1c 00:59:23.910 --> 00:59:23.920 align:start position:0% in in 16 will be like having a A1c 00:59:23.920 --> 00:59:25.670 align:start position:0% in in 16 will be like having a A1c circuit<00:59:24.280> that<00:59:24.440> verifies<00:59:24.920> like<00:59:25.079> the<00:59:25.200> logic<00:59:25.520> of 00:59:25.670 --> 00:59:25.680 align:start position:0% circuit that verifies like the logic of 00:59:25.680 --> 00:59:28.430 align:start position:0% circuit that verifies like the logic of the<00:59:26.240> ping<00:59:26.559> checks<00:59:26.880> and<00:59:27.079> and<00:59:27.200> so<00:59:27.359> on<00:59:27.680> of<00:59:27.839> a<00:59:28.160> 6 00:59:28.430 --> 00:59:28.440 align:start position:0% the ping checks and and so on of a 6 00:59:28.440 --> 00:59:31.309 align:start position:0% the ping checks and and so on of a 6 proof<00:59:29.240> which<00:59:29.480> requires<00:59:29.880> some<00:59:30.119> like<00:59:30.559> uh<00:59:30.880> in<00:59:31.200> in 00:59:31.309 --> 00:59:31.319 align:start position:0% proof which requires some like uh in in 00:59:31.319 --> 00:59:32.750 align:start position:0% proof which requires some like uh in in the<00:59:31.440> worst<00:59:31.640> case<00:59:31.839> like<00:59:31.960> some<00:59:32.160> non-native 00:59:32.750 --> 00:59:32.760 align:start position:0% the worst case like some non-native 00:59:32.760 --> 00:59:34.109 align:start position:0% the worst case like some non-native arithmetic<00:59:33.200> of<00:59:33.280> the<00:59:33.359> elliptic<00:59:33.640> Cur<00:59:33.880> which<00:59:34.000> is 00:59:34.109 --> 00:59:34.119 align:start position:0% arithmetic of the elliptic Cur which is 00:59:34.119 --> 00:59:36.270 align:start position:0% arithmetic of the elliptic Cur which is very<00:59:34.319> expensive<00:59:34.680> in<00:59:34.839> circuit<00:59:35.640> and<00:59:35.799> in<00:59:36.000> some 00:59:36.270 --> 00:59:36.280 align:start position:0% very expensive in circuit and in some 00:59:36.280 --> 00:59:38.910 align:start position:0% very expensive in circuit and in some cases<00:59:36.720> where<00:59:36.960> we<00:59:37.079> can<00:59:37.359> use<00:59:37.599> some<00:59:37.880> c<00:59:38.200> c<00:59:38.599> curve 00:59:38.910 --> 00:59:38.920 align:start position:0% cases where we can use some c c curve 00:59:38.920 --> 00:59:42.789 align:start position:0% cases where we can use some c c curve Cycles<00:59:39.920> uh<00:59:40.359> we<00:59:40.520> can<00:59:40.720> get<00:59:40.920> this<00:59:41.079> a<00:59:41.200> bit<00:59:41.400> down<00:59:41.920> but 00:59:42.789 --> 00:59:42.799 align:start position:0% Cycles uh we can get this a bit down but 00:59:42.799 --> 00:59:45.470 align:start position:0% Cycles uh we can get this a bit down but uh<00:59:43.319> nowadays<00:59:43.760> we<00:59:43.880> have<00:59:44.079> like<00:59:44.359> some<00:59:44.760> like<00:59:45.119> uh 00:59:45.470 --> 00:59:45.480 align:start position:0% uh nowadays we have like some like uh 00:59:45.480 --> 00:59:47.710 align:start position:0% uh nowadays we have like some like uh more<00:59:45.799> efficient<00:59:46.440> uh<00:59:46.599> options<00:59:47.200> uh<00:59:47.319> such<00:59:47.520> as 00:59:47.710 --> 00:59:47.720 align:start position:0% more efficient uh options uh such as 00:59:47.720 --> 00:59:51.029 align:start position:0% more efficient uh options uh such as like<00:59:47.920> the<00:59:48.319> Stark<00:59:49.000> Side<00:59:49.240> of<00:59:49.400> Things<00:59:49.920> uh<00:59:50.359> we<00:59:50.839> um 00:59:51.029 --> 00:59:51.039 align:start position:0% like the Stark Side of Things uh we um 00:59:51.039 --> 00:59:53.990 align:start position:0% like the Stark Side of Things uh we um using<00:59:51.359> also<00:59:52.359> some<00:59:52.520> of<00:59:52.680> those<00:59:52.920> like<00:59:53.240> uh<00:59:53.640> small 00:59:53.990 --> 00:59:54.000 align:start position:0% using also some of those like uh small 00:59:54.000 --> 00:59:56.789 align:start position:0% using also some of those like uh small Prime<00:59:54.240> field<00:59:55.200> uh<00:59:55.400> systems<00:59:56.039> like<00:59:56.160> Goldilocks 00:59:56.789 --> 00:59:56.799 align:start position:0% Prime field uh systems like Goldilocks 00:59:56.799 --> 00:59:59.230 align:start position:0% Prime field uh systems like Goldilocks in<00:59:56.960> the<00:59:57.240> case<00:59:57.400> of<00:59:57.520> PL<00:59:57.839> 2<00:59:58.000> or<00:59:58.200> Marine<00:59:58.640> primes<00:59:59.039> in 00:59:59.230 --> 00:59:59.240 align:start position:0% in the case of PL 2 or Marine primes in 00:59:59.240 --> 01:00:01.750 align:start position:0% in the case of PL 2 or Marine primes in in<00:59:59.359> PL<00:59:59.720> 3<01:00:00.359> uh<01:00:00.559> we<01:00:00.680> can<01:00:01.119> we<01:00:01.200> can<01:00:01.319> achieve<01:00:01.599> this 01:00:01.750 --> 01:00:01.760 align:start position:0% in PL 3 uh we can we can achieve this 01:00:01.760 --> 01:00:03.390 align:start position:0% in PL 3 uh we can we can achieve this like<01:00:01.960> kind<01:00:02.079> of<01:00:02.240> recursion<01:00:02.960> which<01:00:03.240> like 01:00:03.390 --> 01:00:03.400 align:start position:0% like kind of recursion which like 01:00:03.400 --> 01:00:05.990 align:start position:0% like kind of recursion which like instead<01:00:03.680> of<01:00:03.760> taking<01:00:04.119> like<01:00:04.960> uh<01:00:05.480> millions<01:00:05.880> of 01:00:05.990 --> 01:00:06.000 align:start position:0% instead of taking like uh millions of 01:00:06.000 --> 01:00:09.069 align:start position:0% instead of taking like uh millions of constraints<01:00:06.680> it<01:00:06.799> takes<01:00:07.119> like<01:00:08.000> hundreds<01:00:08.760> of<01:00:08.960> of 01:00:09.069 --> 01:00:09.079 align:start position:0% constraints it takes like hundreds of of 01:00:09.079 --> 01:00:10.630 align:start position:0% constraints it takes like hundreds of of gates<01:00:09.480> and<01:00:09.640> and<01:00:09.760> then<01:00:09.839> it's<01:00:10.000> like<01:00:10.280> uh<01:00:10.520> it 01:00:10.630 --> 01:00:10.640 align:start position:0% gates and and then it's like uh it 01:00:10.640 --> 01:00:13.150 align:start position:0% gates and and then it's like uh it translates<01:00:11.240> like<01:00:12.000> smaller<01:00:12.520> proving<01:00:12.880> times 01:00:13.150 --> 01:00:13.160 align:start position:0% translates like smaller proving times 01:00:13.160 --> 01:00:14.309 align:start position:0% translates like smaller proving times like<01:00:13.400> few 01:00:14.309 --> 01:00:14.319 align:start position:0% like few 01:00:14.319 --> 01:00:18.430 align:start position:0% like few seconds<01:00:15.319> so<01:00:16.319> um<01:00:16.839> so<01:00:17.119> far<01:00:17.400> as<01:00:17.520> I<01:00:17.680> mentioned<01:00:18.160> a 01:00:18.430 --> 01:00:18.440 align:start position:0% seconds so um so far as I mentioned a 01:00:18.440 --> 01:00:20.230 align:start position:0% seconds so um so far as I mentioned a pod<01:00:19.160> well<01:00:19.400> actually<01:00:19.599> I<01:00:19.680> didn't<01:00:19.880> exactly 01:00:20.230 --> 01:00:20.240 align:start position:0% pod well actually I didn't exactly 01:00:20.240 --> 01:00:21.549 align:start position:0% pod well actually I didn't exactly mention<01:00:20.480> it<01:00:20.680> but<01:00:20.839> essentially<01:00:21.200> a<01:00:21.359> pod 01:00:21.549 --> 01:00:21.559 align:start position:0% mention it but essentially a pod 01:00:21.559 --> 01:00:24.230 align:start position:0% mention it but essentially a pod consists<01:00:21.920> of<01:00:22.000> a<01:00:22.119> claim<01:00:22.319> and<01:00:22.440> a<01:00:22.599> proof<01:00:23.400> here 01:00:24.230 --> 01:00:24.240 align:start position:0% consists of a claim and a proof here 01:00:24.240 --> 01:00:27.910 align:start position:0% consists of a claim and a proof here yeah 01:00:27.910 --> 01:00:27.920 align:start position:0% 01:00:27.920 --> 01:00:29.710 align:start position:0% would<01:00:28.119> not<01:00:28.280> sync<01:00:28.599> up<01:00:28.760> on<01:00:28.960> this<01:00:29.079> one<01:00:29.400> so<01:00:29.599> one 01:00:29.710 --> 01:00:29.720 align:start position:0% would not sync up on this one so one 01:00:29.720 --> 01:00:31.870 align:start position:0% would not sync up on this one so one thing<01:00:29.839> i'<01:00:30.000> say<01:00:30.160> is<01:00:30.440> this<01:00:30.559> is<01:00:30.839> POD<01:00:31.119> one<01:00:31.640> which<01:00:31.760> is 01:00:31.870 --> 01:00:31.880 align:start position:0% thing i' say is this is POD one which is 01:00:31.880 --> 01:00:33.470 align:start position:0% thing i' say is this is POD one which is a<01:00:32.000> system<01:00:32.240> that's<01:00:32.400> currently<01:00:32.680> used<01:00:32.920> for<01:00:33.079> frogs 01:00:33.470 --> 01:00:33.480 align:start position:0% a system that's currently used for frogs 01:00:33.480 --> 01:00:35.549 align:start position:0% a system that's currently used for frogs Etc<01:00:33.960> which<01:00:34.079> has<01:00:34.280> limitations<01:00:35.079> and<01:00:35.160> so<01:00:35.280> Ahad 01:00:35.549 --> 01:00:35.559 align:start position:0% Etc which has limitations and so Ahad 01:00:35.559 --> 01:00:37.109 align:start position:0% Etc which has limitations and so Ahad and<01:00:35.640> AR<01:00:35.799> are<01:00:35.880> going<01:00:35.960> to<01:00:36.240> talk<01:00:36.440> both<01:00:36.640> about<01:00:36.920> pod 01:00:37.109 --> 01:00:37.119 align:start position:0% and AR are going to talk both about pod 01:00:37.119 --> 01:00:38.870 align:start position:0% and AR are going to talk both about pod one<01:00:37.280> and<01:00:37.440> pod<01:00:37.680> two<01:00:38.200> what<01:00:38.319> I<01:00:38.400> showed<01:00:38.640> you<01:00:38.760> guys 01:00:38.870 --> 01:00:38.880 align:start position:0% one and pod two what I showed you guys 01:00:38.880 --> 01:00:41.990 align:start position:0% one and pod two what I showed you guys is<01:00:39.079> POD<01:00:39.359> two<01:00:39.839> just<01:00:39.960> so<01:00:40.160> it's<01:00:40.319> super<01:00:40.559> clear<01:00:41.440> um 01:00:41.990 --> 01:00:42.000 align:start position:0% is POD two just so it's super clear um 01:00:42.000 --> 01:00:43.750 align:start position:0% is POD two just so it's super clear um sorry<01:00:42.240> for<01:00:42.359> that<01:00:42.480> Interruption<01:00:43.119> exactly<01:00:43.559> no 01:00:43.750 --> 01:00:43.760 align:start position:0% sorry for that Interruption exactly no 01:00:43.760 --> 01:00:46.069 align:start position:0% sorry for that Interruption exactly no worries<01:00:44.760> so<01:00:44.960> essentially<01:00:45.400> we<01:00:45.520> have<01:00:45.640> a<01:00:45.799> claim 01:00:46.069 --> 01:00:46.079 align:start position:0% worries so essentially we have a claim 01:00:46.079 --> 01:00:48.510 align:start position:0% worries so essentially we have a claim and<01:00:46.200> a<01:00:46.359> proof<01:00:46.880> with<01:00:47.079> pod<01:00:47.319> one<01:00:47.640> you<01:00:47.839> essentially 01:00:48.510 --> 01:00:48.520 align:start position:0% and a proof with pod one you essentially 01:00:48.520 --> 01:00:50.789 align:start position:0% and a proof with pod one you essentially claim<01:00:49.000> I<01:00:49.119> have<01:00:49.319> this<01:00:49.480> key<01:00:49.680> Value<01:00:49.960> Store<01:00:50.520> some 01:00:50.789 --> 01:00:50.799 align:start position:0% claim I have this key Value Store some 01:00:50.799 --> 01:00:53.990 align:start position:0% claim I have this key Value Store some party<01:00:51.240> with<01:00:51.440> this<01:00:51.640> public<01:00:52.280> given<01:00:52.599> public<01:00:53.000> key 01:00:53.990 --> 01:00:54.000 align:start position:0% party with this public given public key 01:00:54.000 --> 01:00:56.029 align:start position:0% party with this public given public key um<01:00:54.240> attests<01:00:54.599> to<01:00:54.760> the<01:00:54.880> validity<01:00:55.319> of<01:00:55.480> this 01:00:56.029 --> 01:00:56.039 align:start position:0% um attests to the validity of this 01:00:56.039 --> 01:00:58.589 align:start position:0% um attests to the validity of this collection<01:00:56.440> of<01:00:57.280> keys<01:00:57.520> and<01:00:57.680> values<01:00:58.119> key<01:00:58.359> value 01:00:58.589 --> 01:00:58.599 align:start position:0% collection of keys and values key value 01:00:58.599 --> 01:01:00.549 align:start position:0% collection of keys and values key value Pairs<01:00:58.920> and<01:00:59.079> then<01:00:59.240> proof<01:00:59.440> is<01:00:59.599> just<01:00:59.680> a 01:01:00.549 --> 01:01:00.559 align:start position:0% Pairs and then proof is just a 01:01:00.559 --> 01:01:02.549 align:start position:0% Pairs and then proof is just a signature<01:01:01.559> but<01:01:01.680> then<01:01:01.799> when<01:01:01.920> we<01:01:02.039> plug<01:01:02.240> it<01:01:02.359> into 01:01:02.549 --> 01:01:02.559 align:start position:0% signature but then when we plug it into 01:01:02.559 --> 01:01:04.510 align:start position:0% signature but then when we plug it into that<01:01:02.760> box<01:01:03.000> to<01:01:03.119> get<01:01:03.200> a<01:01:03.319> ZK<01:01:03.720> proof<01:01:04.240> we<01:01:04.359> get 01:01:04.510 --> 01:01:04.520 align:start position:0% that box to get a ZK proof we get 01:01:04.520 --> 01:01:06.349 align:start position:0% that box to get a ZK proof we get something<01:01:04.760> of<01:01:04.880> a<01:01:05.039> completely<01:01:05.400> different<01:01:05.720> form 01:01:06.349 --> 01:01:06.359 align:start position:0% something of a completely different form 01:01:06.359 --> 01:01:08.349 align:start position:0% something of a completely different form um<01:01:06.480> our<01:01:06.640> claim<01:01:06.960> is<01:01:07.079> that<01:01:07.200> we<01:01:07.319> have<01:01:07.440> a<01:01:07.599> proof 01:01:08.349 --> 01:01:08.359 align:start position:0% um our claim is that we have a proof 01:01:08.359 --> 01:01:10.750 align:start position:0% um our claim is that we have a proof config<01:01:09.359> and<01:01:09.720> it<01:01:09.839> is<01:01:10.000> consistent<01:01:10.440> with<01:01:10.559> some 01:01:10.750 --> 01:01:10.760 align:start position:0% config and it is consistent with some 01:01:10.760 --> 01:01:12.510 align:start position:0% config and it is consistent with some set<01:01:10.920> of<01:01:11.079> revealed<01:01:11.520> claims<01:01:12.119> like<01:01:12.240> maybe<01:01:12.400> you 01:01:12.510 --> 01:01:12.520 align:start position:0% set of revealed claims like maybe you 01:01:12.520 --> 01:01:14.390 align:start position:0% set of revealed claims like maybe you reveal<01:01:12.839> your<01:01:13.000> date<01:01:13.160> of<01:01:13.319> birth<01:01:13.640> or<01:01:13.799> something 01:01:14.390 --> 01:01:14.400 align:start position:0% reveal your date of birth or something 01:01:14.400 --> 01:01:16.589 align:start position:0% reveal your date of birth or something out<01:01:14.640> from<01:01:14.760> an<01:01:14.920> ID<01:01:15.359> pod<01:01:16.079> and<01:01:16.160> then<01:01:16.280> the<01:01:16.400> proof 01:01:16.589 --> 01:01:16.599 align:start position:0% out from an ID pod and then the proof 01:01:16.599 --> 01:01:18.390 align:start position:0% out from an ID pod and then the proof would<01:01:16.720> just<01:01:16.839> be<01:01:16.920> some<01:01:17.079> grth<01:01:17.400> 16<01:01:17.799> proof<01:01:18.240> like 01:01:18.390 --> 01:01:18.400 align:start position:0% would just be some grth 16 proof like 01:01:18.400 --> 01:01:19.990 align:start position:0% would just be some grth 16 proof like plus<01:01:18.559> or<01:01:18.680> minus<01:01:18.920> some<01:01:19.039> extra<01:01:19.359> bits<01:01:19.559> to<01:01:19.680> say 01:01:19.990 --> 01:01:20.000 align:start position:0% plus or minus some extra bits to say 01:01:20.000 --> 01:01:21.789 align:start position:0% plus or minus some extra bits to say exactly<01:01:20.400> what<01:01:20.559> circuit<01:01:20.880> we're<01:01:21.079> dealing<01:01:21.440> with 01:01:21.789 --> 01:01:21.799 align:start position:0% exactly what circuit we're dealing with 01:01:21.799 --> 01:01:25.630 align:start position:0% exactly what circuit we're dealing with like<01:01:22.359> you<01:01:22.480> know<01:01:23.640> artifacts<01:01:24.640> um<01:01:25.000> and<01:01:25.359> so<01:01:25.520> you 01:01:25.630 --> 01:01:25.640 align:start position:0% like you know artifacts um and so you 01:01:25.640 --> 01:01:27.390 align:start position:0% like you know artifacts um and so you can<01:01:25.760> see<01:01:25.960> see<01:01:26.079> it's<01:01:26.160> sort<01:01:26.359> of<01:01:26.640> heterogeneous 01:01:27.390 --> 01:01:27.400 align:start position:0% can see see it's sort of heterogeneous 01:01:27.400 --> 01:01:30.109 align:start position:0% can see see it's sort of heterogeneous here<01:01:27.599> as<01:01:27.760> far<01:01:27.960> as<01:01:28.520> the<01:01:28.640> form<01:01:29.200> of<01:01:29.559> claim<01:01:29.880> or 01:01:30.109 --> 01:01:30.119 align:start position:0% here as far as the form of claim or 01:01:30.119 --> 01:01:32.630 align:start position:0% here as far as the form of claim or proof<01:01:30.599> and<01:01:30.839> our<01:01:31.480> our<01:01:31.760> approach<01:01:32.160> now<01:01:32.359> is<01:01:32.480> to 01:01:32.630 --> 01:01:32.640 align:start position:0% proof and our our approach now is to 01:01:32.640 --> 01:01:34.789 align:start position:0% proof and our our approach now is to kind<01:01:32.760> of<01:01:32.960> unify<01:01:33.480> these<01:01:34.079> in<01:01:34.240> such<01:01:34.400> a<01:01:34.520> way<01:01:34.680> that 01:01:34.789 --> 01:01:34.799 align:start position:0% kind of unify these in such a way that 01:01:34.799 --> 01:01:36.870 align:start position:0% kind of unify these in such a way that the<01:01:34.920> claims<01:01:35.720> should<01:01:35.920> be<01:01:36.039> of<01:01:36.200> roughly<01:01:36.520> the<01:01:36.640> same 01:01:36.870 --> 01:01:36.880 align:start position:0% the claims should be of roughly the same 01:01:36.880 --> 01:01:40.150 align:start position:0% the claims should be of roughly the same data<01:01:37.559> type<01:01:38.559> and<01:01:38.760> that's<01:01:39.000> where<01:01:39.200> pod<01:01:39.480> two<01:01:39.920> comes 01:01:40.150 --> 01:01:40.160 align:start position:0% data type and that's where pod two comes 01:01:40.160 --> 01:01:42.309 align:start position:0% data type and that's where pod two comes in<01:01:40.520> and<01:01:40.640> in<01:01:40.720> a<01:01:40.880> nutshell<01:01:41.440> we<01:01:41.760> again<01:01:42.079> have<01:01:42.200> a 01:01:42.309 --> 01:01:42.319 align:start position:0% in and in a nutshell we again have a 01:01:42.319 --> 01:01:44.990 align:start position:0% in and in a nutshell we again have a claim<01:01:42.559> and<01:01:42.680> a<01:01:42.799> proof<01:01:43.559> the<01:01:43.720> claim<01:01:44.079> is<01:01:44.280> basically 01:01:44.990 --> 01:01:45.000 align:start position:0% claim and a proof the claim is basically 01:01:45.000 --> 01:01:46.990 align:start position:0% claim and a proof the claim is basically we<01:01:45.160> have<01:01:45.280> a<01:01:45.400> bunch<01:01:45.559> of<01:01:45.720> statements<01:01:46.599> named 01:01:46.990 --> 01:01:47.000 align:start position:0% we have a bunch of statements named 01:01:47.000 --> 01:01:49.549 align:start position:0% we have a bunch of statements named statements<01:01:47.599> so<01:01:47.799> we<01:01:47.920> have<01:01:48.000> a<01:01:48.240> map<01:01:48.960> taking<01:01:49.280> some 01:01:49.549 --> 01:01:49.559 align:start position:0% statements so we have a map taking some 01:01:49.559 --> 01:01:51.109 align:start position:0% statements so we have a map taking some key<01:01:50.039> you<01:01:50.160> can<01:01:50.319> just<01:01:50.480> assume<01:01:50.760> it's<01:01:50.880> some 01:01:51.109 --> 01:01:51.119 align:start position:0% key you can just assume it's some 01:01:51.119 --> 01:01:52.589 align:start position:0% key you can just assume it's some identifier<01:01:51.720> it<01:01:51.839> doesn't<01:01:52.039> really<01:01:52.240> matter<01:01:52.480> what 01:01:52.589 --> 01:01:52.599 align:start position:0% identifier it doesn't really matter what 01:01:52.599 --> 01:01:56.109 align:start position:0% identifier it doesn't really matter what form<01:01:52.839> it<01:01:53.000> is<01:01:53.720> to<01:01:54.079> a<01:01:54.240> statement<01:01:55.000> and<01:01:55.119> our<01:01:55.359> proof 01:01:56.109 --> 01:01:56.119 align:start position:0% form it is to a statement and our proof 01:01:56.119 --> 01:01:58.990 align:start position:0% form it is to a statement and our proof is<01:01:56.279> either<01:01:56.480> going<01:01:56.559> to<01:01:56.680> be<01:01:57.079> a<01:01:57.559> a<01:01:57.839> signature<01:01:58.839> of 01:01:58.990 --> 01:01:59.000 align:start position:0% is either going to be a a signature of 01:01:59.000 --> 01:02:00.829 align:start position:0% is either going to be a a signature of some<01:01:59.200> sort<01:01:59.520> kind<01:01:59.640> of<01:01:59.799> like<01:01:59.920> with<01:02:00.119> pod<01:02:00.359> one<01:02:00.720> in 01:02:00.829 --> 01:02:00.839 align:start position:0% some sort kind of like with pod one in 01:02:00.839 --> 01:02:02.670 align:start position:0% some sort kind of like with pod one in our<01:02:01.000> case<01:02:01.160> we<01:02:01.279> use<01:02:01.440> a<01:02:01.599> schnor<01:02:02.079> type<01:02:02.279> signature 01:02:02.670 --> 01:02:02.680 align:start position:0% our case we use a schnor type signature 01:02:02.680 --> 01:02:04.430 align:start position:0% our case we use a schnor type signature scheme<01:02:03.039> but<01:02:03.400> we're<01:02:03.599> kind<01:02:03.680> of<01:02:03.880> branching<01:02:04.240> out 01:02:04.430 --> 01:02:04.440 align:start position:0% scheme but we're kind of branching out 01:02:04.440 --> 01:02:07.069 align:start position:0% scheme but we're kind of branching out from<01:02:04.640> that<01:02:05.559> and<01:02:05.839> or<01:02:06.000> it<01:02:06.119> could<01:02:06.240> be<01:02:06.319> a<01:02:06.440> ZK<01:02:06.799> proof 01:02:07.069 --> 01:02:07.079 align:start position:0% from that and or it could be a ZK proof 01:02:07.079 --> 01:02:08.990 align:start position:0% from that and or it could be a ZK proof in<01:02:07.160> the<01:02:07.240> form<01:02:07.440> of<01:02:07.559> a<01:02:07.640> planky<01:02:08.000> 2<01:02:08.240> proof<01:02:08.520> so<01:02:08.680> we've 01:02:08.990 --> 01:02:09.000 align:start position:0% in the form of a planky 2 proof so we've 01:02:09.000 --> 01:02:13.510 align:start position:0% in the form of a planky 2 proof so we've shifted<01:02:09.440> from<01:02:09.720> grth<01:02:10.079> 16<01:02:10.400> to<01:02:10.799> planky<01:02:11.440> 2<01:02:12.440> and<01:02:12.640> now 01:02:13.510 --> 01:02:13.520 align:start position:0% shifted from grth 16 to planky 2 and now 01:02:13.520 --> 01:02:15.630 align:start position:0% shifted from grth 16 to planky 2 and now what<01:02:13.640> is<01:02:13.760> a<01:02:14.079> statement<01:02:15.079> well<01:02:15.240> to<01:02:15.359> get<01:02:15.440> into 01:02:15.630 --> 01:02:15.640 align:start position:0% what is a statement well to get into 01:02:15.640 --> 01:02:17.309 align:start position:0% what is a statement well to get into what<01:02:15.760> a<01:02:15.880> statement<01:02:16.240> is<01:02:16.359> I<01:02:16.440> need<01:02:16.599> to<01:02:16.720> tell<01:02:16.920> you 01:02:17.309 --> 01:02:17.319 align:start position:0% what a statement is I need to tell you 01:02:17.319 --> 01:02:20.190 align:start position:0% what a statement is I need to tell you exactly<01:02:17.680> how<01:02:17.839> things<01:02:17.960> are<01:02:18.160> laid<01:02:18.480> out<01:02:19.480> um<01:02:20.079> but 01:02:20.190 --> 01:02:20.200 align:start position:0% exactly how things are laid out um but 01:02:20.200 --> 01:02:21.710 align:start position:0% exactly how things are laid out um but let's<01:02:20.359> just<01:02:20.520> start<01:02:20.760> with<01:02:21.079> statements<01:02:21.640> a 01:02:21.710 --> 01:02:21.720 align:start position:0% let's just start with statements a 01:02:21.720 --> 01:02:22.990 align:start position:0% let's just start with statements a statement<01:02:22.039> could<01:02:22.200> either<01:02:22.400> say<01:02:22.599> nothing<01:02:22.839> at 01:02:22.990 --> 01:02:23.000 align:start position:0% statement could either say nothing at 01:02:23.000 --> 01:02:25.470 align:start position:0% statement could either say nothing at all<01:02:23.400> or<01:02:23.599> as<01:02:23.799> Justin<01:02:24.359> said<01:02:24.640> you<01:02:24.760> could<01:02:24.960> say<01:02:25.279> hey 01:02:25.470 --> 01:02:25.480 align:start position:0% all or as Justin said you could say hey 01:02:25.480 --> 01:02:28.109 align:start position:0% all or as Justin said you could say hey the<01:02:25.599> state<01:02:26.200> is<01:02:26.359> I<01:02:26.480> have<01:02:26.599> a<01:02:26.760> value<01:02:27.599> this<01:02:27.680> is<01:02:27.839> its 01:02:28.109 --> 01:02:28.119 align:start position:0% the state is I have a value this is its 01:02:28.119 --> 01:02:31.750 align:start position:0% the state is I have a value this is its name<01:02:28.680> it<01:02:29.000> comes<01:02:29.240> from<01:02:29.480> this<01:02:30.079> place<01:02:31.079> um<01:02:31.480> and<01:02:31.640> in 01:02:31.750 --> 01:02:31.760 align:start position:0% name it comes from this place um and in 01:02:31.760 --> 01:02:33.510 align:start position:0% name it comes from this place um and in this<01:02:32.039> case<01:02:32.240> we<01:02:32.319> have<01:02:32.440> a<01:02:32.520> notion<01:02:32.760> of<01:02:32.960> origin<01:02:33.359> and 01:02:33.510 --> 01:02:33.520 align:start position:0% this case we have a notion of origin and 01:02:33.520 --> 01:02:35.549 align:start position:0% this case we have a notion of origin and anchored<01:02:34.000> key<01:02:34.599> um<01:02:34.720> I<01:02:34.799> won't<01:02:35.039> really<01:02:35.200> say<01:02:35.400> too 01:02:35.549 --> 01:02:35.559 align:start position:0% anchored key um I won't really say too 01:02:35.559 --> 01:02:37.910 align:start position:0% anchored key um I won't really say too much<01:02:35.760> about<01:02:36.039> that<01:02:36.520> but<01:02:36.720> the<01:02:36.920> rough<01:02:37.200> idea<01:02:37.520> is<01:02:37.760> we 01:02:37.910 --> 01:02:37.920 align:start position:0% much about that but the rough idea is we 01:02:37.920 --> 01:02:39.190 align:start position:0% much about that but the rough idea is we we're<01:02:38.039> going<01:02:38.160> to<01:02:38.279> have<01:02:38.559> processes<01:02:39.000> for 01:02:39.190 --> 01:02:39.200 align:start position:0% we're going to have processes for 01:02:39.200 --> 01:02:40.910 align:start position:0% we're going to have processes for constructing<01:02:39.680> new<01:02:39.920> pods<01:02:40.400> and<01:02:40.520> we<01:02:40.680> kind<01:02:40.799> of 01:02:40.910 --> 01:02:40.920 align:start position:0% constructing new pods and we kind of 01:02:40.920 --> 01:02:42.430 align:start position:0% constructing new pods and we kind of want<01:02:41.039> to<01:02:41.200> say<01:02:41.440> how<01:02:41.640> these<01:02:41.880> new<01:02:42.039> pods<01:02:42.240> were 01:02:42.430 --> 01:02:42.440 align:start position:0% want to say how these new pods were 01:02:42.440 --> 01:02:44.910 align:start position:0% want to say how these new pods were constructed<01:02:43.400> in<01:02:43.520> the<01:02:43.760> process<01:02:44.520> and<01:02:44.720> keep 01:02:44.910 --> 01:02:44.920 align:start position:0% constructed in the process and keep 01:02:44.920 --> 01:02:49.190 align:start position:0% constructed in the process and keep track<01:02:45.119> of<01:02:45.240> their<01:02:45.880> Origins<01:02:47.160> um<01:02:48.160> and<01:02:48.640> um<01:02:49.039> yeah<01:02:49.160> I 01:02:49.190 --> 01:02:49.200 align:start position:0% track of their Origins um and um yeah I 01:02:49.200 --> 01:02:50.829 align:start position:0% track of their Origins um and um yeah I mean<01:02:49.319> we<01:02:49.440> have<01:02:49.599> other<01:02:50.039> such<01:02:50.240> statements<01:02:50.640> like 01:02:50.829 --> 01:02:50.839 align:start position:0% mean we have other such statements like 01:02:50.839 --> 01:02:52.150 align:start position:0% mean we have other such statements like equality 01:02:52.150 --> 01:02:52.160 align:start position:0% equality 01:02:52.160 --> 01:02:54.269 align:start position:0% equality non-equality<01:02:53.160> inequalities<01:02:53.720> are<01:02:53.920> also<01:02:54.119> in 01:02:54.269 --> 01:02:54.279 align:start position:0% non-equality inequalities are also in 01:02:54.279 --> 01:02:56.029 align:start position:0% non-equality inequalities are also in there<01:02:54.440> but<01:02:54.599> I<01:02:54.720> just<01:02:54.960> omitted<01:02:55.319> them<01:02:55.520> here<01:02:55.920> but 01:02:56.029 --> 01:02:56.039 align:start position:0% there but I just omitted them here but 01:02:56.039 --> 01:02:57.789 align:start position:0% there but I just omitted them here but then<01:02:56.160> we<01:02:56.279> have<01:02:56.400> things<01:02:56.599> like<01:02:56.720> sum<01:02:57.039> of<01:02:57.599> which 01:02:57.789 --> 01:02:57.799 align:start position:0% then we have things like sum of which 01:02:57.799 --> 01:03:00.269 align:start position:0% then we have things like sum of which Justin<01:02:58.200> already<01:02:58.480> talked<01:02:58.799> about<01:02:59.520> and<01:02:59.680> to<01:03:00.039> to 01:03:00.269 --> 01:03:00.279 align:start position:0% Justin already talked about and to to 01:03:00.279 --> 01:03:02.470 align:start position:0% Justin already talked about and to to actually<01:03:00.799> construct<01:03:01.279> statements<01:03:01.920> you<01:03:02.079> apply 01:03:02.470 --> 01:03:02.480 align:start position:0% actually construct statements you apply 01:03:02.480 --> 01:03:04.829 align:start position:0% actually construct statements you apply operations<01:03:03.119> so<01:03:03.319> again<01:03:03.440> we<01:03:03.559> have<01:03:03.720> like<01:03:03.880> no<01:03:04.160> Ops 01:03:04.829 --> 01:03:04.839 align:start position:0% operations so again we have like no Ops 01:03:04.839 --> 01:03:06.549 align:start position:0% operations so again we have like no Ops uh<01:03:04.960> constructing<01:03:05.440> new<01:03:05.640> entries<01:03:06.039> copying 01:03:06.549 --> 01:03:06.559 align:start position:0% uh constructing new entries copying 01:03:06.559 --> 01:03:09.589 align:start position:0% uh constructing new entries copying statements<01:03:07.559> and<01:03:07.720> so<01:03:08.079> on<01:03:09.079> and<01:03:09.200> the<01:03:09.319> idea<01:03:09.520> is 01:03:09.589 --> 01:03:09.599 align:start position:0% statements and so on and the idea is 01:03:09.599 --> 01:03:10.750 align:start position:0% statements and so on and the idea is we're<01:03:09.720> going<01:03:09.799> to<01:03:09.880> have<01:03:10.039> these<01:03:10.200> boxes<01:03:10.640> where 01:03:10.750 --> 01:03:10.760 align:start position:0% we're going to have these boxes where 01:03:10.760 --> 01:03:12.670 align:start position:0% we're going to have these boxes where you<01:03:10.880> can<01:03:11.079> actually<01:03:11.359> take<01:03:11.640> pods<01:03:12.079> and<01:03:12.440> all<01:03:12.559> you 01:03:12.670 --> 01:03:12.680 align:start position:0% you can actually take pods and all you 01:03:12.680 --> 01:03:14.349 align:start position:0% you can actually take pods and all you could<01:03:12.799> do<01:03:13.039> you<01:03:13.119> could<01:03:13.400> just<01:03:13.640> copy<01:03:13.920> statements 01:03:14.349 --> 01:03:14.359 align:start position:0% could do you could just copy statements 01:03:14.359 --> 01:03:17.549 align:start position:0% could do you could just copy statements from<01:03:14.559> these<01:03:14.760> pods<01:03:15.480> um<01:03:15.799> and<01:03:16.799> verify<01:03:17.279> that<01:03:17.440> the 01:03:17.549 --> 01:03:17.559 align:start position:0% from these pods um and verify that the 01:03:17.559 --> 01:03:20.150 align:start position:0% from these pods um and verify that the copying<01:03:17.920> was<01:03:18.079> done<01:03:18.359> properly<01:03:18.880> in 01:03:20.150 --> 01:03:20.160 align:start position:0% copying was done properly in 01:03:20.160 --> 01:03:24.470 align:start position:0% copying was done properly in ZK<01:03:21.160> now<01:03:22.119> uh<01:03:22.920> as<01:03:23.039> I<01:03:23.160> said<01:03:23.400> earlier<01:03:23.920> we<01:03:24.079> kind<01:03:24.240> of 01:03:24.470 --> 01:03:24.480 align:start position:0% ZK now uh as I said earlier we kind of 01:03:24.480 --> 01:03:27.029 align:start position:0% ZK now uh as I said earlier we kind of had<01:03:25.000> like<01:03:25.240> we<01:03:25.400> had<01:03:25.799> pod<01:03:26.039> and<01:03:26.200> GPC<01:03:26.760> they're<01:03:26.920> kind 01:03:27.029 --> 01:03:27.039 align:start position:0% had like we had pod and GPC they're kind 01:03:27.039 --> 01:03:29.710 align:start position:0% had like we had pod and GPC they're kind of<01:03:27.200> like<01:03:27.400> two<01:03:27.680> completely<01:03:28.160> different<01:03:28.720> animals 01:03:29.710 --> 01:03:29.720 align:start position:0% of like two completely different animals 01:03:29.720 --> 01:03:32.990 align:start position:0% of like two completely different animals here<01:03:29.960> we<01:03:30.200> have<01:03:30.880> a<01:03:31.200> pod<01:03:32.200> and<01:03:32.279> we<01:03:32.400> have<01:03:32.559> PODS<01:03:32.799> of 01:03:32.990 --> 01:03:33.000 align:start position:0% here we have a pod and we have PODS of 01:03:33.000 --> 01:03:35.750 align:start position:0% here we have a pod and we have PODS of different<01:03:33.599> types<01:03:34.599> now<01:03:34.799> claims<01:03:35.200> will<01:03:35.440> always 01:03:35.750 --> 01:03:35.760 align:start position:0% different types now claims will always 01:03:35.760 --> 01:03:38.589 align:start position:0% different types now claims will always be<01:03:36.480> maps<01:03:36.880> from<01:03:37.079> keys<01:03:37.480> to 01:03:38.589 --> 01:03:38.599 align:start position:0% be maps from keys to 01:03:38.599 --> 01:03:41.349 align:start position:0% be maps from keys to statements<01:03:39.599> um<01:03:39.880> but<01:03:40.079> proofs<01:03:40.640> could<01:03:40.839> differ<01:03:41.200> in 01:03:41.349 --> 01:03:41.359 align:start position:0% statements um but proofs could differ in 01:03:41.359 --> 01:03:43.670 align:start position:0% statements um but proofs could differ in their<01:03:41.480> formats<01:03:42.279> so<01:03:42.480> we<01:03:42.640> Define<01:03:42.880> a<01:03:43.000> schnor<01:03:43.440> pod 01:03:43.670 --> 01:03:43.680 align:start position:0% their formats so we Define a schnor pod 01:03:43.680 --> 01:03:46.549 align:start position:0% their formats so we Define a schnor pod to<01:03:44.160> be<01:03:44.799> a<01:03:45.000> pod<01:03:45.240> whose<01:03:45.480> claims<01:03:45.760> are<01:03:45.920> of<01:03:46.039> the<01:03:46.119> form 01:03:46.549 --> 01:03:46.559 align:start position:0% to be a pod whose claims are of the form 01:03:46.559 --> 01:03:50.630 align:start position:0% to be a pod whose claims are of the form value<01:03:46.920> of<01:03:47.559> key<01:03:47.920> is<01:03:48.640> value<01:03:49.640> yeah<01:03:50.000> so<01:03:50.240> all<01:03:50.440> all<01:03:50.520> of 01:03:50.630 --> 01:03:50.640 align:start position:0% value of key is value yeah so all all of 01:03:50.640 --> 01:03:52.750 align:start position:0% value of key is value yeah so all all of its<01:03:50.760> statements<01:03:51.119> will<01:03:51.279> have<01:03:51.480> that<01:03:51.680> form<01:03:52.680> and 01:03:52.750 --> 01:03:52.760 align:start position:0% its statements will have that form and 01:03:52.760 --> 01:03:54.549 align:start position:0% its statements will have that form and the<01:03:52.880> proof<01:03:53.079> will<01:03:53.279> always<01:03:53.480> be<01:03:53.599> a<01:03:53.680> schnore 01:03:54.549 --> 01:03:54.559 align:start position:0% the proof will always be a schnore 01:03:54.559 --> 01:03:56.870 align:start position:0% the proof will always be a schnore signature<01:03:56.039> now<01:03:56.160> we<01:03:56.279> have<01:03:56.400> the<01:03:56.480> notion<01:03:56.680> of<01:03:56.799> an 01:03:56.870 --> 01:03:56.880 align:start position:0% signature now we have the notion of an 01:03:56.880 --> 01:03:58.829 align:start position:0% signature now we have the notion of an oracle<01:03:57.279> pod<01:03:57.559> which<01:03:57.680> can<01:03:57.839> take<01:03:58.039> claims<01:03:58.359> of<01:03:58.559> any 01:03:58.829 --> 01:03:58.839 align:start position:0% oracle pod which can take claims of any 01:03:58.839 --> 01:04:01.069 align:start position:0% oracle pod which can take claims of any form<01:03:59.559> so<01:03:59.839> here<01:04:00.079> we're<01:04:00.319> assuming<01:04:00.680> there's<01:04:00.880> some 01:04:01.069 --> 01:04:01.079 align:start position:0% form so here we're assuming there's some 01:04:01.079 --> 01:04:02.910 align:start position:0% form so here we're assuming there's some trusted<01:04:01.480> party<01:04:01.760> or<01:04:01.920> some<01:04:02.119> trusted<01:04:02.480> machine<01:04:02.799> in 01:04:02.910 --> 01:04:02.920 align:start position:0% trusted party or some trusted machine in 01:04:02.920 --> 01:04:04.750 align:start position:0% trusted party or some trusted machine in the<01:04:03.079> cloud<01:04:03.440> perhaps<01:04:04.079> we<01:04:04.200> have<01:04:04.319> a<01:04:04.440> fully 01:04:04.750 --> 01:04:04.760 align:start position:0% the cloud perhaps we have a fully 01:04:04.760 --> 01:04:07.789 align:start position:0% the cloud perhaps we have a fully homomorphically<01:04:05.520> encrypted<01:04:06.480> setup<01:04:06.880> going<01:04:07.119> on 01:04:07.789 --> 01:04:07.799 align:start position:0% homomorphically encrypted setup going on 01:04:07.799 --> 01:04:09.190 align:start position:0% homomorphically encrypted setup going on where<01:04:07.920> we<01:04:08.039> could<01:04:08.200> just<01:04:08.440> pass<01:04:08.640> all<01:04:08.839> this<01:04:09.000> data 01:04:09.190 --> 01:04:09.200 align:start position:0% where we could just pass all this data 01:04:09.200 --> 01:04:10.710 align:start position:0% where we could just pass all this data to<01:04:09.400> some<01:04:09.599> server<01:04:09.960> and<01:04:10.079> it's<01:04:10.200> going<01:04:10.319> to<01:04:10.440> run 01:04:10.710 --> 01:04:10.720 align:start position:0% to some server and it's going to run 01:04:10.720 --> 01:04:13.710 align:start position:0% to some server and it's going to run those<01:04:10.920> non<01:04:11.240> ZK<01:04:11.760> programs<01:04:12.720> and<01:04:13.319> you<01:04:13.440> know<01:04:13.599> it's 01:04:13.710 --> 01:04:13.720 align:start position:0% those non ZK programs and you know it's 01:04:13.720 --> 01:04:15.069 align:start position:0% those non ZK programs and you know it's going<01:04:13.799> to<01:04:13.920> take<01:04:14.079> a<01:04:14.160> bunch<01:04:14.359> of<01:04:14.520> PODS<01:04:14.880> and<01:04:14.960> it's 01:04:15.069 --> 01:04:15.079 align:start position:0% going to take a bunch of PODS and it's 01:04:15.079 --> 01:04:16.390 align:start position:0% going to take a bunch of PODS and it's going<01:04:15.200> to<01:04:15.279> check<01:04:15.520> that<01:04:15.640> you<01:04:15.760> know<01:04:16.000> this<01:04:16.160> entry 01:04:16.390 --> 01:04:16.400 align:start position:0% going to check that you know this entry 01:04:16.400 --> 01:04:17.829 align:start position:0% going to check that you know this entry in<01:04:16.559> that<01:04:16.720> pod<01:04:16.920> is<01:04:17.039> greater<01:04:17.279> than<01:04:17.440> that<01:04:17.559> entry 01:04:17.829 --> 01:04:17.839 align:start position:0% in that pod is greater than that entry 01:04:17.839 --> 01:04:19.470 align:start position:0% in that pod is greater than that entry in<01:04:18.000> that<01:04:18.160> pod<01:04:18.799> and<01:04:18.880> then<01:04:19.000> it's<01:04:19.079> going<01:04:19.200> to<01:04:19.279> spit 01:04:19.470 --> 01:04:19.480 align:start position:0% in that pod and then it's going to spit 01:04:19.480 --> 01:04:21.230 align:start position:0% in that pod and then it's going to spit out<01:04:19.559> a<01:04:19.760> brand<01:04:19.960> new<01:04:20.119> pod<01:04:20.359> attesting<01:04:20.760> to<01:04:20.960> all<01:04:21.079> of 01:04:21.230 --> 01:04:21.240 align:start position:0% out a brand new pod attesting to all of 01:04:21.240 --> 01:04:23.430 align:start position:0% out a brand new pod attesting to all of that<01:04:21.480> so<01:04:21.599> we<01:04:21.720> call<01:04:21.920> that<01:04:22.039> an<01:04:22.160> oracle<01:04:22.559> pod<01:04:23.319> and 01:04:23.430 --> 01:04:23.440 align:start position:0% that so we call that an oracle pod and 01:04:23.440 --> 01:04:25.269 align:start position:0% that so we call that an oracle pod and it<01:04:23.520> is<01:04:23.680> pretty<01:04:23.880> much<01:04:24.000> a<01:04:24.160> snor<01:04:24.640> pod<01:04:24.839> with<01:04:24.960> a 01:04:25.269 --> 01:04:25.279 align:start position:0% it is pretty much a snor pod with a 01:04:25.279 --> 01:04:28.230 align:start position:0% it is pretty much a snor pod with a god-given<01:04:25.760> an<01:04:25.880> oracle<01:04:26.240> signature<01:04:27.240> basically 01:04:28.230 --> 01:04:28.240 align:start position:0% god-given an oracle signature basically 01:04:28.240 --> 01:04:29.950 align:start position:0% god-given an oracle signature basically and<01:04:28.799> why<01:04:28.880> would<01:04:29.039> we<01:04:29.200> have<01:04:29.359> this<01:04:29.520> well<01:04:29.680> besides 01:04:29.950 --> 01:04:29.960 align:start position:0% and why would we have this well besides 01:04:29.960 --> 01:04:32.430 align:start position:0% and why would we have this well besides you<01:04:30.119> know<01:04:31.039> being<01:04:31.359> optimistic<01:04:31.880> about<01:04:32.119> fully 01:04:32.430 --> 01:04:32.440 align:start position:0% you know being optimistic about fully 01:04:32.440 --> 01:04:34.750 align:start position:0% you know being optimistic about fully homomorphic<01:04:33.119> encryption<01:04:34.119> and<01:04:34.319> perhaps<01:04:34.599> even 01:04:34.750 --> 01:04:34.760 align:start position:0% homomorphic encryption and perhaps even 01:04:34.760 --> 01:04:37.150 align:start position:0% homomorphic encryption and perhaps even multi-party<01:04:35.480> computation<01:04:36.480> um<01:04:36.599> it<01:04:36.720> gives<01:04:36.880> us<01:04:37.000> a 01:04:37.150 --> 01:04:37.160 align:start position:0% multi-party computation um it gives us a 01:04:37.160 --> 01:04:39.109 align:start position:0% multi-party computation um it gives us a model<01:04:37.520> of<01:04:37.760> what<01:04:37.880> the<01:04:38.079> ZK<01:04:38.480> circuit<01:04:38.760> is<01:04:38.880> going<01:04:38.960> to 01:04:39.109 --> 01:04:39.119 align:start position:0% model of what the ZK circuit is going to 01:04:39.119 --> 01:04:41.349 align:start position:0% model of what the ZK circuit is going to do<01:04:39.559> just<01:04:39.760> outside<01:04:40.160> of<01:04:40.319> ZK<01:04:40.920> and<01:04:41.000> that's<01:04:41.119> what<01:04:41.240> a 01:04:41.349 --> 01:04:41.359 align:start position:0% do just outside of ZK and that's what a 01:04:41.359 --> 01:04:44.029 align:start position:0% do just outside of ZK and that's what a planky<01:04:41.839> pod<01:04:42.640> is<01:04:42.920> it's<01:04:43.119> basically<01:04:43.480> an<01:04:43.599> oracle 01:04:44.029 --> 01:04:44.039 align:start position:0% planky pod is it's basically an oracle 01:04:44.039 --> 01:04:45.710 align:start position:0% planky pod is it's basically an oracle pod<01:04:44.319> but<01:04:44.440> done<01:04:44.720> in<01:04:44.880> the<01:04:45.039> circuit<01:04:45.480> and<01:04:45.599> the 01:04:45.710 --> 01:04:45.720 align:start position:0% pod but done in the circuit and the 01:04:45.720 --> 01:04:49.870 align:start position:0% pod but done in the circuit and the proof<01:04:46.039> is<01:04:46.160> not<01:04:46.319> a<01:04:46.480> signature<01:04:47.279> but<01:04:47.400> a<01:04:47.520> plony<01:04:47.839> 2 01:04:49.870 --> 01:04:49.880 align:start position:0% proof is not a signature but a plony 2 01:04:49.880 --> 01:04:53.269 align:start position:0% proof is not a signature but a plony 2 proof<01:04:50.880> and<01:04:51.680> I<01:04:51.760> mean<01:04:51.960> as<01:04:52.119> I<01:04:52.279> said<01:04:52.680> you<01:04:52.880> basically 01:04:53.269 --> 01:04:53.279 align:start position:0% proof and I mean as I said you basically 01:04:53.279 --> 01:04:55.910 align:start position:0% proof and I mean as I said you basically want<01:04:53.400> to<01:04:53.680> take<01:04:54.200> some<01:04:54.520> data<01:04:55.119> and<01:04:55.279> construct<01:04:55.799> a 01:04:55.910 --> 01:04:55.920 align:start position:0% want to take some data and construct a 01:04:55.920 --> 01:04:58.150 align:start position:0% want to take some data and construct a pod<01:04:56.119> out<01:04:56.240> of<01:04:56.319> it<01:04:56.480> some<01:04:56.760> dat<01:04:57.079> yeah<01:04:57.359> one<01:04:57.559> minute 01:04:58.150 --> 01:04:58.160 align:start position:0% pod out of it some dat yeah one minute 01:04:58.160 --> 01:05:00.870 align:start position:0% pod out of it some dat yeah one minute no<01:04:58.440> two<01:04:58.640> minutes<01:04:59.400> okay<01:04:59.599> great<01:05:00.480> uh<01:05:00.559> we<01:05:00.720> have 01:05:00.870 --> 01:05:00.880 align:start position:0% no two minutes okay great uh we have 01:05:00.880 --> 01:05:02.870 align:start position:0% no two minutes okay great uh we have gadgets<01:05:01.640> constructing<01:05:02.200> pods<01:05:02.440> you<01:05:02.559> use 01:05:02.870 --> 01:05:02.880 align:start position:0% gadgets constructing pods you use 01:05:02.880 --> 01:05:05.109 align:start position:0% gadgets constructing pods you use gadgets<01:05:03.559> that's<01:05:03.760> our<01:05:03.960> terminology<01:05:04.960> that's 01:05:05.109 --> 01:05:05.119 align:start position:0% gadgets that's our terminology that's 01:05:05.119 --> 01:05:06.910 align:start position:0% gadgets that's our terminology that's essentially<01:05:05.520> what<01:05:05.599> the<01:05:05.760> slide<01:05:06.119> says<01:05:06.440> so<01:05:06.799> you 01:05:06.910 --> 01:05:06.920 align:start position:0% essentially what the slide says so you 01:05:06.920 --> 01:05:08.710 align:start position:0% essentially what the slide says so you can<01:05:07.359> construct<01:05:07.720> a<01:05:07.799> schnor<01:05:08.240> pod<01:05:08.440> using<01:05:08.640> a 01:05:08.710 --> 01:05:08.720 align:start position:0% can construct a schnor pod using a 01:05:08.720 --> 01:05:10.349 align:start position:0% can construct a schnor pod using a schnor<01:05:09.119> gadget<01:05:09.720> which<01:05:09.839> basically<01:05:10.119> means 01:05:10.349 --> 01:05:10.359 align:start position:0% schnor gadget which basically means 01:05:10.359 --> 01:05:11.549 align:start position:0% schnor gadget which basically means taking<01:05:10.559> this<01:05:10.680> key<01:05:10.880> Value<01:05:11.119> Store<01:05:11.359> at<01:05:11.480> the 01:05:11.549 --> 01:05:11.559 align:start position:0% taking this key Value Store at the 01:05:11.559 --> 01:05:13.910 align:start position:0% taking this key Value Store at the secret<01:05:11.880> key<01:05:12.160> and<01:05:12.359> Bam<01:05:12.559> schnor<01:05:13.039> pod<01:05:13.720> and 01:05:13.910 --> 01:05:13.920 align:start position:0% secret key and Bam schnor pod and 01:05:13.920 --> 01:05:17.190 align:start position:0% secret key and Bam schnor pod and similar<01:05:14.240> deal<01:05:14.599> with<01:05:14.880> the<01:05:15.359> planky<01:05:16.359> gadget<01:05:17.039> I'll 01:05:17.190 --> 01:05:17.200 align:start position:0% similar deal with the planky gadget I'll 01:05:17.200 --> 01:05:21.349 align:start position:0% similar deal with the planky gadget I'll sort<01:05:17.359> of<01:05:17.680> rush<01:05:18.079> over<01:05:18.359> to<01:05:18.559> the<01:05:18.680> ZK<01:05:19.160> circuit<01:05:20.359> um 01:05:21.349 --> 01:05:21.359 align:start position:0% sort of rush over to the ZK circuit um 01:05:21.359 --> 01:05:23.750 align:start position:0% sort of rush over to the ZK circuit um because<01:05:21.920> we<01:05:22.039> don't<01:05:22.240> really<01:05:22.440> have<01:05:22.599> much<01:05:22.880> time 01:05:23.750 --> 01:05:23.760 align:start position:0% because we don't really have much time 01:05:23.760 --> 01:05:26.870 align:start position:0% because we don't really have much time but<01:05:23.960> long<01:05:24.200> story<01:05:24.480> short<01:05:24.839> we<01:05:25.000> have<01:05:25.160> a<01:05:25.279> recur<01:05:25.880> Ive 01:05:26.870 --> 01:05:26.880 align:start position:0% but long story short we have a recur Ive 01:05:26.880 --> 01:05:29.349 align:start position:0% but long story short we have a recur Ive circuit<01:05:27.440> in<01:05:27.599> plony<01:05:27.960> 2<01:05:28.680> where<01:05:28.799> we<01:05:28.960> plug<01:05:29.160> in<01:05:29.279> a 01:05:29.349 --> 01:05:29.359 align:start position:0% circuit in plony 2 where we plug in a 01:05:29.359 --> 01:05:31.109 align:start position:0% circuit in plony 2 where we plug in a bunch<01:05:29.520> of<01:05:29.599> schnor<01:05:30.000> or<01:05:30.119> Oracle<01:05:30.520> pods<01:05:30.960> together 01:05:31.109 --> 01:05:31.119 align:start position:0% bunch of schnor or Oracle pods together 01:05:31.119 --> 01:05:35.670 align:start position:0% bunch of schnor or Oracle pods together with<01:05:31.240> plony<01:05:31.720> pods<01:05:32.720> we<01:05:32.880> verify<01:05:33.839> signatures<01:05:34.839> or 01:05:35.670 --> 01:05:35.680 align:start position:0% with plony pods we verify signatures or 01:05:35.680 --> 01:05:39.190 align:start position:0% with plony pods we verify signatures or plony<01:05:36.200> pod<01:05:36.680> uh<01:05:36.960> yeah<01:05:37.119> proofs<01:05:37.599> plony<01:05:38.200> proofs 01:05:39.190 --> 01:05:39.200 align:start position:0% plony pod uh yeah proofs plony proofs 01:05:39.200 --> 01:05:40.670 align:start position:0% plony pod uh yeah proofs plony proofs and<01:05:39.319> then<01:05:39.480> in<01:05:39.599> the<01:05:39.720> circuit<01:05:40.119> we<01:05:40.359> you<01:05:40.480> know 01:05:40.670 --> 01:05:40.680 align:start position:0% and then in the circuit we you know 01:05:40.680 --> 01:05:42.829 align:start position:0% and then in the circuit we you know check<01:05:41.160> a<01:05:41.279> bunch<01:05:41.440> of<01:05:41.680> stuff<01:05:42.160> so<01:05:42.359> we<01:05:42.520> also<01:05:42.720> have 01:05:42.829 --> 01:05:42.839 align:start position:0% check a bunch of stuff so we also have 01:05:42.839 --> 01:05:45.670 align:start position:0% check a bunch of stuff so we also have to<01:05:42.960> keep<01:05:43.160> track<01:05:43.400> of<01:05:43.640> where<01:05:44.359> these<01:05:44.599> pods<01:05:45.400> um 01:05:45.670 --> 01:05:45.680 align:start position:0% to keep track of where these pods um 01:05:45.680 --> 01:05:47.309 align:start position:0% to keep track of where these pods um come<01:05:45.920> from<01:05:46.200> where<01:05:46.359> their<01:05:46.520> values<01:05:46.920> come<01:05:47.079> from 01:05:47.309 --> 01:05:47.319 align:start position:0% come from where their values come from 01:05:47.319 --> 01:05:48.710 align:start position:0% come from where their values come from and<01:05:47.480> so<01:05:47.640> on<01:05:47.920> all<01:05:48.160> this<01:05:48.279> stuff<01:05:48.440> has<01:05:48.559> to<01:05:48.640> be 01:05:48.710 --> 01:05:48.720 align:start position:0% and so on all this stuff has to be 01:05:48.720 --> 01:05:50.109 align:start position:0% and so on all this stuff has to be checked<01:05:48.960> in<01:05:49.079> the<01:05:49.160> circuit<01:05:49.520> the<01:05:49.720> operations 01:05:50.109 --> 01:05:50.119 align:start position:0% checked in the circuit the operations 01:05:50.119 --> 01:05:52.390 align:start position:0% checked in the circuit the operations have<01:05:50.240> to<01:05:50.359> be<01:05:50.480> applied<01:05:50.799> yada<01:05:51.039> yada<01:05:51.279> yada<01:05:51.960> plony 01:05:52.390 --> 01:05:52.400 align:start position:0% have to be applied yada yada yada plony 01:05:52.400 --> 01:05:55.470 align:start position:0% have to be applied yada yada yada plony pod<01:05:52.559> comes<01:05:53.119> out<01:05:54.119> future<01:05:54.480> directions<01:05:55.240> uh<01:05:55.359> this 01:05:55.470 --> 01:05:55.480 align:start position:0% pod comes out future directions uh this 01:05:55.480 --> 01:05:57.670 align:start position:0% pod comes out future directions uh this is<01:05:56.039> the<01:05:56.119> workflow<01:05:56.520> needs<01:05:56.680> to<01:05:56.799> be<01:05:56.960> streamlined 01:05:57.670 --> 01:05:57.680 align:start position:0% is the workflow needs to be streamlined 01:05:57.680 --> 01:05:59.190 align:start position:0% is the workflow needs to be streamlined the<01:05:57.799> cryptography<01:05:58.359> is<01:05:58.480> not<01:05:58.640> that<01:05:58.920> strong<01:05:59.119> at 01:05:59.190 --> 01:05:59.200 align:start position:0% the cryptography is not that strong at 01:05:59.200 --> 01:06:01.789 align:start position:0% the cryptography is not that strong at the<01:05:59.400> moment<01:06:00.400> um<01:06:00.799> we<01:06:00.960> kind<01:06:01.039> of<01:06:01.160> want<01:06:01.319> non-native 01:06:01.789 --> 01:06:01.799 align:start position:0% the moment um we kind of want non-native 01:06:01.799 --> 01:06:03.950 align:start position:0% the moment um we kind of want non-native arithmetic<01:06:02.319> non-native<01:06:02.799> schemes<01:06:03.400> so<01:06:03.760> we<01:06:03.839> want 01:06:03.950 --> 01:06:03.960 align:start position:0% arithmetic non-native schemes so we want 01:06:03.960 --> 01:06:06.630 align:start position:0% arithmetic non-native schemes so we want to<01:06:04.079> use<01:06:04.279> our<01:06:04.480> pod<01:06:04.760> ones<01:06:05.240> so<01:06:05.520> you<01:06:05.640> know<01:06:05.760> BN<01:06:06.000> 254 01:06:06.630 --> 01:06:06.640 align:start position:0% to use our pod ones so you know BN 254 01:06:06.640 --> 01:06:10.670 align:start position:0% to use our pod ones so you know BN 254 based<01:06:07.119> crypto<01:06:08.119> in<01:06:08.319> this<01:06:08.799> 64-bit<01:06:09.799> field<01:06:10.520> which 01:06:10.670 --> 01:06:10.680 align:start position:0% based crypto in this 64-bit field which 01:06:10.680 --> 01:06:13.309 align:start position:0% based crypto in this 64-bit field which is<01:06:11.400> bit<01:06:11.920> difficult<01:06:12.480> and<01:06:12.680> that<01:06:12.799> is<01:06:13.000> essentially 01:06:13.309 --> 01:06:13.319 align:start position:0% is bit difficult and that is essentially 01:06:13.319 --> 01:06:14.510 align:start position:0% is bit difficult and that is essentially what<01:06:13.440> leads<01:06:13.680> to<01:06:14.000> the<01:06:14.119> backwards 01:06:14.510 --> 01:06:14.520 align:start position:0% what leads to the backwards 01:06:14.520 --> 01:06:15.710 align:start position:0% what leads to the backwards compatibility<01:06:15.079> that<01:06:15.200> we're<01:06:15.319> kind<01:06:15.400> of<01:06:15.520> hoping 01:06:15.710 --> 01:06:15.720 align:start position:0% compatibility that we're kind of hoping 01:06:15.720 --> 01:06:18.390 align:start position:0% compatibility that we're kind of hoping to<01:06:15.960> get<01:06:16.160> out<01:06:16.279> of<01:06:16.480> this<01:06:17.279> yeah<01:06:17.920> U<01:06:18.039> by<01:06:18.160> the<01:06:18.240> way 01:06:18.390 --> 01:06:18.400 align:start position:0% to get out of this yeah U by the way 01:06:18.400 --> 01:06:20.150 align:start position:0% to get out of this yeah U by the way these<01:06:18.520> slides<01:06:18.760> are<01:06:18.880> on<01:06:19.039> my<01:06:19.279> GitHub<01:06:19.720> I<01:06:19.799> can<01:06:19.920> link 01:06:20.150 --> 01:06:20.160 align:start position:0% these slides are on my GitHub I can link 01:06:20.160 --> 01:06:21.510 align:start position:0% these slides are on my GitHub I can link to<01:06:20.319> them<01:06:20.480> if<01:06:20.599> anybody<01:06:20.920> wants<01:06:21.079> to<01:06:21.200> have<01:06:21.279> a<01:06:21.400> look 01:06:21.510 --> 01:06:21.520 align:start position:0% to them if anybody wants to have a look 01:06:21.520 --> 01:06:22.750 align:start position:0% to them if anybody wants to have a look at<01:06:21.599> them<01:06:21.760> later<01:06:22.000> on<01:06:22.240> so<01:06:22.359> you<01:06:22.440> don't<01:06:22.559> have<01:06:22.640> to 01:06:22.750 --> 01:06:22.760 align:start position:0% at them later on so you don't have to 01:06:22.760 --> 01:06:23.910 align:start position:0% at them later on so you don't have to take<01:06:22.880> pictures<01:06:23.319> thank<01:06:23.440> you<01:06:23.559> very<01:06:23.680> much<01:06:23.799> for 01:06:23.910 --> 01:06:23.920 align:start position:0% take pictures thank you very much for 01:06:23.920 --> 01:06:25.390 align:start position:0% take pictures thank you very much for your<01:06:24.079> attention 01:06:25.390 --> 01:06:25.400 align:start position:0% your attention 01:06:25.400 --> 01:06:29.390 align:start position:0% your attention [Applause] 01:06:29.390 --> 01:06:29.400 align:start position:0% [Applause] 01:06:29.400 --> 01:06:31.269 align:start position:0% [Applause] being<01:06:29.559> an<01:06:29.720> MC<01:06:30.240> for<01:06:30.400> a<01:06:30.520> bit<01:06:30.760> we<01:06:30.880> have<01:06:31.039> a<01:06:31.119> little 01:06:31.269 --> 01:06:31.279 align:start position:0% being an MC for a bit we have a little 01:06:31.279 --> 01:06:32.829 align:start position:0% being an MC for a bit we have a little bit<01:06:31.400> of<01:06:31.559> time<01:06:31.720> for<01:06:31.920> questions<01:06:32.240> for<01:06:32.480> Arnold 01:06:32.829 --> 01:06:32.839 align:start position:0% bit of time for questions for Arnold 01:06:32.839 --> 01:06:36.150 align:start position:0% bit of time for questions for Arnold andad<01:06:33.400> so<01:06:34.160> oh<01:06:34.359> yeah<01:06:34.559> we<01:06:34.680> have<01:06:34.799> a<01:06:35.160> hands<01:06:35.400> raiser 01:06:36.150 --> 01:06:36.160 align:start position:0% andad so oh yeah we have a hands raiser 01:06:36.160 --> 01:06:39.390 align:start position:0% andad so oh yeah we have a hands raiser arur<01:06:36.599> do<01:06:36.640> you<01:06:36.720> have<01:06:36.799> a 01:06:39.390 --> 01:06:39.400 align:start position:0% 01:06:39.400 --> 01:06:42.109 align:start position:0% mic<01:06:40.400> so<01:06:40.960> um<01:06:41.160> do<01:06:41.279> you<01:06:41.359> think<01:06:41.520> of<01:06:41.640> roughly<01:06:42.000> the 01:06:42.109 --> 01:06:42.119 align:start position:0% mic so um do you think of roughly the 01:06:42.119 --> 01:06:44.430 align:start position:0% mic so um do you think of roughly the schnor<01:06:42.640> Pod<01:06:42.799> is<01:06:42.920> like<01:06:43.039> a<01:06:43.440> self-attestation 01:06:44.430 --> 01:06:44.440 align:start position:0% schnor Pod is like a self-attestation 01:06:44.440 --> 01:06:46.029 align:start position:0% schnor Pod is like a self-attestation the<01:06:44.520> Oracle<01:06:44.960> pod<01:06:45.200> is<01:06:45.480> anything<01:06:45.839> that<01:06:45.960> you 01:06:46.029 --> 01:06:46.039 align:start position:0% the Oracle pod is anything that you 01:06:46.039 --> 01:06:47.630 align:start position:0% the Oracle pod is anything that you would<01:06:46.200> use<01:06:46.559> via<01:06:46.760> an<01:06:46.920> introduction<01:06:47.400> Gadget 01:06:47.630 --> 01:06:47.640 align:start position:0% would use via an introduction Gadget 01:06:47.640 --> 01:06:49.349 align:start position:0% would use via an introduction Gadget will<01:06:47.799> come<01:06:47.920> in<01:06:48.039> as<01:06:48.119> an<01:06:48.240> oracle<01:06:48.599> pod<01:06:49.160> whether 01:06:49.349 --> 01:06:49.359 align:start position:0% will come in as an oracle pod whether 01:06:49.359 --> 01:06:51.910 align:start position:0% will come in as an oracle pod whether it's<01:06:49.680> originally<01:06:50.279> like<01:06:50.599> a<01:06:50.720> proof<01:06:51.000> from<01:06:51.079> a<01:06:51.200> zvm 01:06:51.910 --> 01:06:51.920 align:start position:0% it's originally like a proof from a zvm 01:06:51.920 --> 01:06:54.230 align:start position:0% it's originally like a proof from a zvm or<01:06:52.079> something<01:06:52.400> signed<01:06:52.799> or<01:06:53.039> whatever<01:06:53.880> is<01:06:54.039> that 01:06:54.230 --> 01:06:54.240 align:start position:0% or something signed or whatever is that 01:06:54.240 --> 01:06:56.269 align:start position:0% or something signed or whatever is that just<01:06:55.000> how<01:06:55.240> things<01:06:55.599> will<01:06:55.680> sort<01:06:55.839> of<01:06:55.960> always<01:06:56.119> be 01:06:56.269 --> 01:06:56.279 align:start position:0% just how things will sort of always be 01:06:56.279 --> 01:06:58.109 align:start position:0% just how things will sort of always be introduced<01:06:57.279> and<01:06:57.359> then<01:06:57.480> the<01:06:57.559> plugy<01:06:57.920> pod's 01:06:58.109 --> 01:06:58.119 align:start position:0% introduced and then the plugy pod's 01:06:58.119 --> 01:07:00.470 align:start position:0% introduced and then the plugy pod's always<01:06:58.319> within<01:06:58.520> the<01:06:58.799> system<01:06:59.799> um<01:06:59.960> kind<01:07:00.119> of<01:07:00.279> sort 01:07:00.470 --> 01:07:00.480 align:start position:0% always within the system um kind of sort 01:07:00.480 --> 01:07:02.390 align:start position:0% always within the system um kind of sort of<01:07:00.799> actually<01:07:01.160> I<01:07:01.240> would<01:07:01.480> view<01:07:01.720> it<01:07:02.000> slightly 01:07:02.390 --> 01:07:02.400 align:start position:0% of actually I would view it slightly 01:07:02.400 --> 01:07:05.109 align:start position:0% of actually I would view it slightly differently<01:07:03.039> the<01:07:03.160> introduction<01:07:04.039> Gadget<01:07:05.039> at 01:07:05.109 --> 01:07:05.119 align:start position:0% differently the introduction Gadget at 01:07:05.119 --> 01:07:07.029 align:start position:0% differently the introduction Gadget at least<01:07:05.319> the<01:07:05.440> way<01:07:05.599> I<01:07:05.720> viewed<01:07:06.000> it<01:07:06.240> was<01:07:06.400> more<01:07:06.599> to<01:07:06.839> go 01:07:07.029 --> 01:07:07.039 align:start position:0% least the way I viewed it was more to go 01:07:07.039 --> 01:07:10.510 align:start position:0% least the way I viewed it was more to go from<01:07:07.319> our<01:07:07.559> legac<01:07:08.119> Legacy<01:07:08.559> pod<01:07:08.799> ones<01:07:09.640> to<01:07:10.000> schnor 01:07:10.510 --> 01:07:10.520 align:start position:0% from our legac Legacy pod ones to schnor 01:07:10.520 --> 01:07:12.309 align:start position:0% from our legac Legacy pod ones to schnor pods<01:07:10.920> actually<01:07:11.359> so<01:07:11.559> schnor<01:07:11.880> pods<01:07:12.039> are<01:07:12.160> pretty 01:07:12.309 --> 01:07:12.319 align:start position:0% pods actually so schnor pods are pretty 01:07:12.319 --> 01:07:13.870 align:start position:0% pods actually so schnor pods are pretty much<01:07:12.520> exactly<01:07:12.839> the<01:07:12.960> same<01:07:13.119> as<01:07:13.279> the<01:07:13.400> pods<01:07:13.720> you 01:07:13.870 --> 01:07:13.880 align:start position:0% much exactly the same as the pods you 01:07:13.880 --> 01:07:15.349 align:start position:0% much exactly the same as the pods you you<01:07:13.960> know<01:07:14.079> the<01:07:14.160> Frog<01:07:14.440> pods<01:07:14.720> the<01:07:14.799> ticket<01:07:15.079> pods 01:07:15.349 --> 01:07:15.359 align:start position:0% you know the Frog pods the ticket pods 01:07:15.359 --> 01:07:19.589 align:start position:0% you know the Frog pods the ticket pods Etc<01:07:15.960> that<01:07:16.079> we've<01:07:16.319> had<01:07:16.520> so<01:07:16.960> far<01:07:18.039> um<01:07:19.039> what<01:07:19.240> that 01:07:19.589 --> 01:07:19.599 align:start position:0% Etc that we've had so far um what that 01:07:19.599 --> 01:07:21.109 align:start position:0% Etc that we've had so far um what that no<01:07:19.839> they<01:07:19.960> wouldn't<01:07:20.200> be<01:07:20.279> schnor<01:07:20.680> pods<01:07:20.880> but<01:07:21.000> they 01:07:21.109 --> 01:07:21.119 align:start position:0% no they wouldn't be schnor pods but they 01:07:21.119 --> 01:07:22.430 align:start position:0% no they wouldn't be schnor pods but they could<01:07:21.279> be<01:07:21.480> they<01:07:21.599> could<01:07:21.720> have<01:07:21.839> been<01:07:21.960> schnor 01:07:22.430 --> 01:07:22.440 align:start position:0% could be they could have been schnor 01:07:22.440 --> 01:07:24.029 align:start position:0% could be they could have been schnor pods<01:07:23.039> it's<01:07:23.200> just<01:07:23.319> that<01:07:23.440> we<01:07:23.559> had<01:07:23.680> a<01:07:23.799> different 01:07:24.029 --> 01:07:24.039 align:start position:0% pods it's just that we had a different 01:07:24.039 --> 01:07:26.109 align:start position:0% pods it's just that we had a different cryptographic<01:07:24.640> scheme<01:07:25.520> but<01:07:25.640> if<01:07:25.720> you<01:07:25.839> take 01:07:26.109 --> 01:07:26.119 align:start position:0% cryptographic scheme but if you take 01:07:26.119 --> 01:07:27.470 align:start position:0% cryptographic scheme but if you take those<01:07:26.400> you<01:07:26.480> would<01:07:26.640> use<01:07:26.839> the<01:07:26.960> introduction 01:07:27.470 --> 01:07:27.480 align:start position:0% those you would use the introduction 01:07:27.480 --> 01:07:30.269 align:start position:0% those you would use the introduction Gadget<01:07:27.839> to<01:07:28.319> get<01:07:28.480> a<01:07:28.599> schnor<01:07:29.119> pod<01:07:29.640> to<01:07:29.799> then<01:07:29.960> use 01:07:30.269 --> 01:07:30.279 align:start position:0% Gadget to get a schnor pod to then use 01:07:30.279 --> 01:07:31.870 align:start position:0% Gadget to get a schnor pod to then use here<01:07:30.760> well<01:07:30.839> you<01:07:30.920> wouldn't<01:07:31.160> get<01:07:31.240> a<01:07:31.319> schnor<01:07:31.720> pod 01:07:31.870 --> 01:07:31.880 align:start position:0% here well you wouldn't get a schnor pod 01:07:31.880 --> 01:07:33.230 align:start position:0% here well you wouldn't get a schnor pod cuz<01:07:32.000> it<01:07:32.079> wouldn't<01:07:32.279> be<01:07:32.359> schnor<01:07:32.799> signed<01:07:33.160> it 01:07:33.230 --> 01:07:33.240 align:start position:0% cuz it wouldn't be schnor signed it 01:07:33.240 --> 01:07:36.390 align:start position:0% cuz it wouldn't be schnor signed it would<01:07:33.400> be<01:07:33.520> a<01:07:33.720> ZK<01:07:34.079> proof<01:07:34.279> on<01:07:34.400> it<01:07:34.960> yeah<01:07:35.960> well<01:07:36.319> I'm 01:07:36.390 --> 01:07:36.400 align:start position:0% would be a ZK proof on it yeah well I'm 01:07:36.400 --> 01:07:37.950 align:start position:0% would be a ZK proof on it yeah well I'm saying<01:07:36.760> okay<01:07:36.920> so<01:07:37.079> you<01:07:37.200> would<01:07:37.480> essentially<01:07:37.839> get 01:07:37.950 --> 01:07:37.960 align:start position:0% saying okay so you would essentially get 01:07:37.960 --> 01:07:39.870 align:start position:0% saying okay so you would essentially get a<01:07:38.039> snorepod<01:07:38.480> but<01:07:38.559> you<01:07:38.680> do<01:07:38.799> that<01:07:38.880> in<01:07:39.039> ZK<01:07:39.599> so<01:07:39.720> that 01:07:39.870 --> 01:07:39.880 align:start position:0% a snorepod but you do that in ZK so that 01:07:39.880 --> 01:07:41.750 align:start position:0% a snorepod but you do that in ZK so that you<01:07:40.160> you<01:07:40.279> don't<01:07:40.480> have<01:07:40.599> to<01:07:40.799> actually<01:07:41.200> attest 01:07:41.750 --> 01:07:41.760 align:start position:0% you you don't have to actually attest 01:07:41.760 --> 01:07:43.230 align:start position:0% you you don't have to actually attest well<01:07:41.839> I<01:07:41.920> guess<01:07:42.000> we<01:07:42.119> could<01:07:42.279> call<01:07:42.480> them 01:07:43.230 --> 01:07:43.240 align:start position:0% well I guess we could call them 01:07:43.240 --> 01:07:45.430 align:start position:0% well I guess we could call them differently<01:07:44.240> yeah<01:07:44.520> so<01:07:44.760> there<01:07:45.000> there<01:07:45.079> are<01:07:45.240> many 01:07:45.430 --> 01:07:45.440 align:start position:0% differently yeah so there there are many 01:07:45.440 --> 01:07:47.990 align:start position:0% differently yeah so there there are many ways<01:07:45.599> to<01:07:45.720> do<01:07:45.920> it<01:07:46.119> I<01:07:46.279> guess<01:07:46.640> I<01:07:46.880> think<01:07:47.880> the 01:07:47.990 --> 01:07:48.000 align:start position:0% ways to do it I guess I think the 01:07:48.000 --> 01:07:49.589 align:start position:0% ways to do it I guess I think the comment<01:07:48.240> you<01:07:48.359> made<01:07:48.680> which<01:07:49.079> you're<01:07:49.279> right 01:07:49.589 --> 01:07:49.599 align:start position:0% comment you made which you're right 01:07:49.599 --> 01:07:50.990 align:start position:0% comment you made which you're right about<01:07:49.960> which<01:07:50.079> is<01:07:50.200> like<01:07:50.440> things<01:07:50.640> inside<01:07:50.880> the 01:07:50.990 --> 01:07:51.000 align:start position:0% about which is like things inside the 01:07:51.000 --> 01:07:52.670 align:start position:0% about which is like things inside the system<01:07:51.240> would<01:07:51.359> be<01:07:51.480> prony<01:07:51.880> pods<01:07:52.359> it's<01:07:52.520> true 01:07:52.670 --> 01:07:52.680 align:start position:0% system would be prony pods it's true 01:07:52.680 --> 01:07:54.069 align:start position:0% system would be prony pods it's true that<01:07:52.799> strong<01:07:53.119> pods<01:07:53.279> are<01:07:53.359> going<01:07:53.440> to<01:07:53.520> be<01:07:53.640> self 01:07:54.069 --> 01:07:54.079 align:start position:0% that strong pods are going to be self 01:07:54.079 --> 01:07:57.390 align:start position:0% that strong pods are going to be self basically<01:07:54.400> self<01:07:54.599> attestations<01:07:55.799> and<01:07:55.960> then 01:07:57.390 --> 01:07:57.400 align:start position:0% basically self attestations and then 01:07:57.400 --> 01:07:59.750 align:start position:0% basically self attestations and then um<01:07:58.400> foreign<01:07:58.799> cryptographic<01:07:59.319> data<01:07:59.559> being 01:07:59.750 --> 01:07:59.760 align:start position:0% um foreign cryptographic data being 01:07:59.760 --> 01:08:01.549 align:start position:0% um foreign cryptographic data being imported<01:08:00.440> one<01:08:00.640> way<01:08:00.799> we<01:08:00.880> could<01:08:01.039> do<01:08:01.160> it<01:08:01.359> which<01:08:01.440> is 01:08:01.549 --> 01:08:01.559 align:start position:0% imported one way we could do it which is 01:08:01.559 --> 01:08:03.109 align:start position:0% imported one way we could do it which is not<01:08:01.720> necessarily<01:08:02.039> the<01:08:02.160> right<01:08:02.400> way<01:08:02.640> I<01:08:02.720> mean<01:08:02.960> the 01:08:03.109 --> 01:08:03.119 align:start position:0% not necessarily the right way I mean the 01:08:03.119 --> 01:08:05.230 align:start position:0% not necessarily the right way I mean the way<01:08:03.520> I'mma<01:08:03.839> describe<01:08:04.119> it<01:08:04.200> works<01:08:04.440> as<01:08:04.599> well<01:08:04.960> is 01:08:05.230 --> 01:08:05.240 align:start position:0% way I'mma describe it works as well is 01:08:05.240 --> 01:08:07.390 align:start position:0% way I'mma describe it works as well is we<01:08:05.359> would<01:08:05.520> make<01:08:05.680> a<01:08:05.799> new<01:08:06.119> Gadget<01:08:06.520> type<01:08:06.920> for<01:08:07.160> each 01:08:07.390 --> 01:08:07.400 align:start position:0% we would make a new Gadget type for each 01:08:07.400 --> 01:08:09.269 align:start position:0% we would make a new Gadget type for each new<01:08:07.640> kinds<01:08:07.880> of<01:08:08.079> data<01:08:08.480> that<01:08:08.599> you<01:08:08.720> would<01:08:08.880> import 01:08:09.269 --> 01:08:09.279 align:start position:0% new kinds of data that you would import 01:08:09.279 --> 01:08:10.269 align:start position:0% new kinds of data that you would import basically<01:08:09.640> so<01:08:09.720> you<01:08:09.799> would<01:08:09.920> have<01:08:10.039> like<01:08:10.160> an 01:08:10.269 --> 01:08:10.279 align:start position:0% basically so you would have like an 01:08:10.279 --> 01:08:12.670 align:start position:0% basically so you would have like an email<01:08:10.599> pod<01:08:11.039> you<01:08:11.160> for<01:08:11.400> to<01:08:11.559> import<01:08:11.880> stuff<01:08:12.119> from<01:08:12.480> a 01:08:12.670 --> 01:08:12.680 align:start position:0% email pod you for to import stuff from a 01:08:12.680 --> 01:08:14.670 align:start position:0% email pod you for to import stuff from a Us's<01:08:13.039> ZK<01:08:13.400> email<01:08:13.799> we<01:08:13.880> would<01:08:14.000> have<01:08:14.119> a<01:08:14.279> passport 01:08:14.670 --> 01:08:14.680 align:start position:0% Us's ZK email we would have a passport 01:08:14.680 --> 01:08:16.470 align:start position:0% Us's ZK email we would have a passport pod<01:08:15.000> for<01:08:15.200> like<01:08:15.359> a<01:08:15.480> specific<01:08:15.799> kinds<01:08:15.960> of<01:08:16.120> pass 01:08:16.470 --> 01:08:16.480 align:start position:0% pod for like a specific kinds of pass 01:08:16.480 --> 01:08:17.630 align:start position:0% pod for like a specific kinds of pass okay<01:08:16.560> that's<01:08:16.679> what<01:08:16.759> I<01:08:16.839> was<01:08:17.159> sort<01:08:17.279> of<01:08:17.359> wondering 01:08:17.630 --> 01:08:17.640 align:start position:0% okay that's what I was sort of wondering 01:08:17.640 --> 01:08:18.789 align:start position:0% okay that's what I was sort of wondering is<01:08:17.759> if<01:08:17.839> you<01:08:17.920> were<01:08:18.040> going<01:08:18.120> to<01:08:18.199> try<01:08:18.319> to<01:08:18.480> import 01:08:18.789 --> 01:08:18.799 align:start position:0% is if you were going to try to import 01:08:18.799 --> 01:08:20.149 align:start position:0% is if you were going to try to import them<01:08:18.920> under<01:08:19.120> the<01:08:19.199> same<01:08:19.480> pod<01:08:19.679> type<01:08:19.880> or<01:08:20.040> just 01:08:20.149 --> 01:08:20.159 align:start position:0% them under the same pod type or just 01:08:20.159 --> 01:08:22.269 align:start position:0% them under the same pod type or just introduce<01:08:20.520> a<01:08:20.679> new<01:08:21.359> specific<01:08:21.719> pod<01:08:21.960> type<01:08:22.120> for 01:08:22.269 --> 01:08:22.279 align:start position:0% introduce a new specific pod type for 01:08:22.279 --> 01:08:24.709 align:start position:0% introduce a new specific pod type for each<01:08:22.839> yeah<01:08:23.000> and<01:08:23.120> so<01:08:23.520> the<01:08:23.719> the<01:08:23.880> cost<01:08:24.080> of<01:08:24.640> of 01:08:24.709 --> 01:08:24.719 align:start position:0% each yeah and so the the cost of of 01:08:24.719 --> 01:08:26.269 align:start position:0% each yeah and so the the cost of of having<01:08:24.920> a<01:08:25.040> new<01:08:25.199> pod<01:08:25.600> type<01:08:25.759> is<01:08:25.839> you<01:08:25.920> need<01:08:26.080> the 01:08:26.269 --> 01:08:26.279 align:start position:0% having a new pod type is you need the 01:08:26.279 --> 01:08:27.950 align:start position:0% having a new pod type is you need the verifier<01:08:26.719> for<01:08:26.880> that<01:08:27.040> pod<01:08:27.279> type<01:08:27.480> to<01:08:27.600> be<01:08:27.719> part<01:08:27.839> of 01:08:27.950 --> 01:08:27.960 align:start position:0% verifier for that pod type to be part of 01:08:27.960 --> 01:08:30.550 align:start position:0% verifier for that pod type to be part of the<01:08:28.159> spine<01:08:28.520> pod<01:08:29.000> right<01:08:29.159> the<01:08:29.279> plunky<01:08:29.640> Pod<01:08:30.279> so 01:08:30.550 --> 01:08:30.560 align:start position:0% the spine pod right the plunky Pod so 01:08:30.560 --> 01:08:32.950 align:start position:0% the spine pod right the plunky Pod so one<01:08:30.719> tricky<01:08:31.040> thing<01:08:31.279> is<01:08:32.120> if<01:08:32.400> ideally<01:08:32.759> you<01:08:32.839> would 01:08:32.950 --> 01:08:32.960 align:start position:0% one tricky thing is if ideally you would 01:08:32.960 --> 01:08:34.229 align:start position:0% one tricky thing is if ideally you would get<01:08:33.080> to<01:08:33.159> a<01:08:33.279> stage<01:08:33.520> where<01:08:33.679> you<01:08:33.759> don't<01:08:33.920> need<01:08:34.080> to 01:08:34.229 --> 01:08:34.239 align:start position:0% get to a stage where you don't need to 01:08:34.239 --> 01:08:35.950 align:start position:0% get to a stage where you don't need to embed<01:08:34.520> the<01:08:34.679> verification<01:08:35.319> key<01:08:35.560> for<01:08:35.719> all<01:08:35.839> of 01:08:35.950 --> 01:08:35.960 align:start position:0% embed the verification key for all of 01:08:35.960 --> 01:08:37.470 align:start position:0% embed the verification key for all of these<01:08:36.159> gadgets<01:08:36.520> into<01:08:36.719> the<01:08:36.839> spine<01:08:37.120> pod<01:08:37.319> and<01:08:37.400> you 01:08:37.470 --> 01:08:37.480 align:start position:0% these gadgets into the spine pod and you 01:08:37.480 --> 01:08:39.149 align:start position:0% these gadgets into the spine pod and you would<01:08:37.600> be<01:08:37.679> able<01:08:37.920> to<01:08:38.120> like<01:08:38.319> dynamically<01:08:38.839> load 01:08:39.149 --> 01:08:39.159 align:start position:0% would be able to like dynamically load 01:08:39.159 --> 01:08:40.829 align:start position:0% would be able to like dynamically load them<01:08:39.480> by<01:08:39.679> witnessing<01:08:40.159> them<01:08:40.359> and<01:08:40.480> having<01:08:40.719> like 01:08:40.829 --> 01:08:40.839 align:start position:0% them by witnessing them and having like 01:08:40.839 --> 01:08:42.309 align:start position:0% them by witnessing them and having like some<01:08:40.960> form<01:08:41.239> like<01:08:41.480> certificate<01:08:41.880> Authority 01:08:42.309 --> 01:08:42.319 align:start position:0% some form like certificate Authority 01:08:42.319 --> 01:08:43.910 align:start position:0% some form like certificate Authority system<01:08:42.640> or<01:08:42.759> something<01:08:43.000> like<01:08:43.159> that<01:08:43.359> but<01:08:43.719> very 01:08:43.910 --> 01:08:43.920 align:start position:0% system or something like that but very 01:08:43.920 --> 01:08:45.309 align:start position:0% system or something like that but very much<01:08:44.279> work<01:08:44.480> in 01:08:45.309 --> 01:08:45.319 align:start position:0% much work in 01:08:45.319 --> 01:08:47.669 align:start position:0% much work in progress<01:08:46.319> thank<01:08:46.480> you<01:08:46.920> I<01:08:47.000> mean<01:08:47.159> I<01:08:47.239> think<01:08:47.359> we<01:08:47.520> do 01:08:47.669 --> 01:08:47.679 align:start position:0% progress thank you I mean I think we do 01:08:47.679 --> 01:08:49.229 align:start position:0% progress thank you I mean I think we do kind<01:08:47.799> of<01:08:47.920> need<01:08:48.080> a<01:08:48.239> new<01:08:48.480> type<01:08:48.960> it<01:08:49.080> would 01:08:49.229 --> 01:08:49.239 align:start position:0% kind of need a new type it would 01:08:49.239 --> 01:08:50.709 align:start position:0% kind of need a new type it would essentially<01:08:49.679> look<01:08:49.880> like<01:08:49.960> a<01:08:50.040> schnor<01:08:50.480> pod<01:08:50.600> but 01:08:50.709 --> 01:08:50.719 align:start position:0% essentially look like a schnor pod but 01:08:50.719 --> 01:08:53.829 align:start position:0% essentially look like a schnor pod but with<01:08:50.799> a<01:08:50.920> ZK<01:08:51.279> proof<01:08:51.799> instead<01:08:52.799> so<01:08:53.319> we'<01:08:53.520> put<01:08:53.679> some 01:08:53.829 --> 01:08:53.839 align:start position:0% with a ZK proof instead so we' put some 01:08:53.839 --> 01:08:55.149 align:start position:0% with a ZK proof instead so we' put some constraints<01:08:54.239> on<01:08:54.359> the<01:08:54.480> types<01:08:54.679> of<01:08:54.839> statements 01:08:55.149 --> 01:08:55.159 align:start position:0% constraints on the types of statements 01:08:55.159 --> 01:08:56.669 align:start position:0% constraints on the types of statements you<01:08:55.719> happen 01:08:56.669 --> 01:08:56.679 align:start position:0% you happen 01:08:56.679 --> 01:08:59.229 align:start position:0% you happen there<01:08:57.679> it<01:08:57.759> seems<01:08:57.960> like<01:08:58.080> we're<01:08:58.359> super<01:08:58.799> out<01:08:58.960> of 01:08:59.229 --> 01:08:59.239 align:start position:0% there it seems like we're super out of 01:08:59.239 --> 01:09:01.669 align:start position:0% there it seems like we're super out of time<01:08:59.679> so<01:09:00.239> uh<01:09:00.319> our<01:09:00.480> next<01:09:00.679> speaker<01:09:01.040> is<01:09:01.359> aush 01:09:01.669 --> 01:09:01.679 align:start position:0% time so uh our next speaker is aush 01:09:01.679 --> 01:09:03.390 align:start position:0% time so uh our next speaker is aush Gupta<01:09:02.040> aush<01:09:02.319> Gupta<01:09:02.560> is<01:09:02.600> gonna<01:09:02.799> talk<01:09:02.920> about<01:09:03.080> ZK 01:09:03.390 --> 01:09:03.400 align:start position:0% Gupta aush Gupta is gonna talk about ZK 01:09:03.400 --> 01:09:06.070 align:start position:0% Gupta aush Gupta is gonna talk about ZK email<01:09:03.920> so<01:09:04.440> um<01:09:04.920> ZK<01:09:05.239> email<01:09:05.480> is<01:09:05.560> a<01:09:05.719> way<01:09:05.839> to 01:09:06.070 --> 01:09:06.080 align:start position:0% email so um ZK email is a way to 01:09:06.080 --> 01:09:08.309 align:start position:0% email so um ZK email is a way to introduce<01:09:07.080> uh<01:09:07.199> cryptographic<01:09:07.799> data<01:09:08.080> from 01:09:08.309 --> 01:09:08.319 align:start position:0% introduce uh cryptographic data from 01:09:08.319 --> 01:09:12.149 align:start position:0% introduce uh cryptographic data from email<01:09:08.759> systems<01:09:09.759> um<01:09:10.120> and<01:09:11.040> it's<01:09:11.319> uh<01:09:11.759> very<01:09:11.960> much 01:09:12.149 --> 01:09:12.159 align:start position:0% email systems um and it's uh very much 01:09:12.159 --> 01:09:13.630 align:start position:0% email systems um and it's uh very much philosophically<01:09:12.799> fits<01:09:13.120> within<01:09:13.359> what<01:09:13.480> we've 01:09:13.630 --> 01:09:13.640 align:start position:0% philosophically fits within what we've 01:09:13.640 --> 01:09:15.309 align:start position:0% philosophically fits within what we've been<01:09:13.759> talking<01:09:14.040> about<01:09:14.359> over<01:09:14.520> the<01:09:14.679> last<01:09:14.880> hour 01:09:15.309 --> 01:09:15.319 align:start position:0% been talking about over the last hour 01:09:15.319 --> 01:09:16.669 align:start position:0% been talking about over the last hour which<01:09:15.440> is<01:09:15.600> making<01:09:15.839> use<01:09:16.040> of<01:09:16.159> cryptographic 01:09:16.669 --> 01:09:16.679 align:start position:0% which is making use of cryptographic 01:09:16.679 --> 01:09:31.470 align:start position:0% which is making use of cryptographic data<01:09:16.880> and<01:09:17.000> Computing<01:09:17.400> on<01:09:17.560> top<01:09:17.679> of<01:09:17.799> it 01:09:31.470 --> 01:09:31.480 align:start position:0% 01:09:31.480 --> 01:09:33.990 align:start position:0% cool<01:09:32.080> um<01:09:32.679> maybe<01:09:33.120> just<01:09:33.359> so<01:09:33.480> I<01:09:33.560> can<01:09:33.640> get<01:09:33.719> a<01:09:33.799> sense 01:09:33.990 --> 01:09:34.000 align:start position:0% cool um maybe just so I can get a sense 01:09:34.000 --> 01:09:35.870 align:start position:0% cool um maybe just so I can get a sense of<01:09:34.120> where<01:09:34.279> people<01:09:34.640> at<01:09:35.199> um<01:09:35.319> and<01:09:35.440> how<01:09:35.560> much<01:09:35.799> I 01:09:35.870 --> 01:09:35.880 align:start position:0% of where people at um and how much I 01:09:35.880 --> 01:09:37.390 align:start position:0% of where people at um and how much I should<01:09:36.040> spend<01:09:36.319> on<01:09:36.719> background<01:09:37.120> maybe<01:09:37.279> like 01:09:37.390 --> 01:09:37.400 align:start position:0% should spend on background maybe like 01:09:37.400 --> 01:09:38.430 align:start position:0% should spend on background maybe like raise<01:09:37.560> your<01:09:37.640> hand<01:09:37.799> if<01:09:37.839> you've<01:09:38.000> heard<01:09:38.120> of<01:09:38.199> ZK 01:09:38.430 --> 01:09:38.440 align:start position:0% raise your hand if you've heard of ZK 01:09:38.440 --> 01:09:40.470 align:start position:0% raise your hand if you've heard of ZK email<01:09:38.679> or<01:09:38.759> seen<01:09:38.920> any<01:09:39.040> of<01:09:39.159> our<01:09:39.279> talks<01:09:39.560> this<01:09:39.719> week 01:09:40.470 --> 01:09:40.480 align:start position:0% email or seen any of our talks this week 01:09:40.480 --> 01:09:42.149 align:start position:0% email or seen any of our talks this week um<01:09:41.040> Okay<01:09:41.199> cool<01:09:41.440> so<01:09:41.560> in<01:09:41.679> that<01:09:41.799> case<01:09:41.920> I'll<01:09:42.080> kind 01:09:42.149 --> 01:09:42.159 align:start position:0% um Okay cool so in that case I'll kind 01:09:42.159 --> 01:09:43.789 align:start position:0% um Okay cool so in that case I'll kind of<01:09:42.279> skim<01:09:42.560> over<01:09:42.719> the<01:09:42.839> basics<01:09:43.199> and<01:09:43.319> I'll<01:09:43.520> focus 01:09:43.789 --> 01:09:43.799 align:start position:0% of skim over the basics and I'll focus 01:09:43.799 --> 01:09:45.669 align:start position:0% of skim over the basics and I'll focus more<01:09:44.000> on<01:09:44.199> the<01:09:44.480> like<01:09:44.960> interesting<01:09:45.319> new<01:09:45.480> stuff 01:09:45.669 --> 01:09:45.679 align:start position:0% more on the like interesting new stuff 01:09:45.679 --> 01:09:46.990 align:start position:0% more on the like interesting new stuff that<01:09:45.759> I<01:09:45.839> didn't<01:09:46.040> cover<01:09:46.239> in<01:09:46.359> all<01:09:46.440> of<01:09:46.560> our<01:09:46.759> other 01:09:46.990 --> 01:09:47.000 align:start position:0% that I didn't cover in all of our other 01:09:47.000 --> 01:09:49.749 align:start position:0% that I didn't cover in all of our other talks<01:09:47.960> um<01:09:48.279> so<01:09:48.880> we'll<01:09:49.159> quickly<01:09:49.440> go<01:09:49.520> through<01:09:49.640> the 01:09:49.749 --> 01:09:49.759 align:start position:0% talks um so we'll quickly go through the 01:09:49.759 --> 01:09:51.030 align:start position:0% talks um so we'll quickly go through the basics<01:09:50.080> and<01:09:50.199> I'll<01:09:50.319> talk<01:09:50.480> about<01:09:50.679> some<01:09:50.799> of<01:09:50.920> the 01:09:51.030 --> 01:09:51.040 align:start position:0% basics and I'll talk about some of the 01:09:51.040 --> 01:09:52.309 align:start position:0% basics and I'll talk about some of the interesting<01:09:51.480> infrastructure<01:09:52.080> that<01:09:52.159> is 01:09:52.309 --> 01:09:52.319 align:start position:0% interesting infrastructure that is 01:09:52.319 --> 01:09:54.269 align:start position:0% interesting infrastructure that is relevant<01:09:53.040> not<01:09:53.199> just<01:09:53.319> for<01:09:53.480> email<01:09:53.799> proofs<01:09:54.120> but 01:09:54.269 --> 01:09:54.279 align:start position:0% relevant not just for email proofs but 01:09:54.279 --> 01:09:56.669 align:start position:0% relevant not just for email proofs but generally<01:09:54.640> for<01:09:54.840> provent<01:09:55.600> proofs<01:09:56.239> um<01:09:56.360> and<01:09:56.480> one 01:09:56.669 --> 01:09:56.679 align:start position:0% generally for provent proofs um and one 01:09:56.679 --> 01:09:58.470 align:start position:0% generally for provent proofs um and one vision<01:09:56.920> of<01:09:57.159> how<01:09:57.760> doing<01:09:58.040> this<01:09:58.159> sort<01:09:58.320> of 01:09:58.470 --> 01:09:58.480 align:start position:0% vision of how doing this sort of 01:09:58.480 --> 01:09:59.750 align:start position:0% vision of how doing this sort of programmable<01:09:58.920> cryptography<01:09:59.440> might<01:09:59.560> look 01:09:59.750 --> 01:09:59.760 align:start position:0% programmable cryptography might look 01:09:59.760 --> 01:10:02.270 align:start position:0% programmable cryptography might look like<01:10:00.000> and<01:10:00.159> then<01:10:00.600> hopefully<01:10:01.080> expanding<01:10:02.080> uh<01:10:02.199> the 01:10:02.270 --> 01:10:02.280 align:start position:0% like and then hopefully expanding uh the 01:10:02.280 --> 01:10:03.669 align:start position:0% like and then hopefully expanding uh the sense<01:10:02.480> of<01:10:02.600> what<01:10:02.679> you<01:10:02.760> can<01:10:02.880> do<01:10:03.080> with<01:10:03.239> like<01:10:03.400> weird 01:10:03.669 --> 01:10:03.679 align:start position:0% sense of what you can do with like weird 01:10:03.679 --> 01:10:05.270 align:start position:0% sense of what you can do with like weird applications<01:10:04.320> that<01:10:04.679> you<01:10:04.800> know<01:10:04.920> are<01:10:05.040> kind<01:10:05.159> of 01:10:05.270 --> 01:10:05.280 align:start position:0% applications that you know are kind of 01:10:05.280 --> 01:10:07.510 align:start position:0% applications that you know are kind of half<01:10:05.440> zkl<01:10:06.000> and<01:10:06.159> half<01:10:06.400> other<01:10:06.640> Primitives<01:10:07.360> um 01:10:07.510 --> 01:10:07.520 align:start position:0% half zkl and half other Primitives um 01:10:07.520 --> 01:10:09.470 align:start position:0% half zkl and half other Primitives um that<01:10:07.679> might<01:10:08.159> you<01:10:08.280> know<01:10:08.679> lend<01:10:08.960> itself<01:10:09.199> well<01:10:09.320> to 01:10:09.470 --> 01:10:09.480 align:start position:0% that might you know lend itself well to 01:10:09.480 --> 01:10:11.030 align:start position:0% that might you know lend itself well to the<01:10:09.560> idea<01:10:09.800> of<01:10:09.960> oh<01:10:10.120> like<01:10:10.239> what<01:10:10.360> if<01:10:10.440> you<01:10:10.880> like 01:10:11.030 --> 01:10:11.040 align:start position:0% the idea of oh like what if you like 01:10:11.040 --> 01:10:12.229 align:start position:0% the idea of oh like what if you like compose<01:10:11.400> these<01:10:11.560> proofs<01:10:11.800> can<01:10:11.920> you<01:10:12.000> get<01:10:12.080> more 01:10:12.229 --> 01:10:12.239 align:start position:0% compose these proofs can you get more 01:10:12.239 --> 01:10:13.270 align:start position:0% compose these proofs can you get more interesting 01:10:13.270 --> 01:10:13.280 align:start position:0% interesting 01:10:13.280 --> 01:10:15.910 align:start position:0% interesting things<01:10:14.280> okay<01:10:14.480> so<01:10:15.000> the<01:10:15.159> first<01:10:15.400> thing<01:10:15.600> I<01:10:15.679> want<01:10:15.760> to 01:10:15.910 --> 01:10:15.920 align:start position:0% things okay so the first thing I want to 01:10:15.920 --> 01:10:20.430 align:start position:0% things okay so the first thing I want to talk<01:10:16.080> about<01:10:16.320> is<01:10:16.840> how<01:10:17.159> I<01:10:17.440> see<01:10:18.440> um<01:10:19.239> adoption<01:10:20.239> of 01:10:20.430 --> 01:10:20.440 align:start position:0% talk about is how I see um adoption of 01:10:20.440 --> 01:10:21.669 align:start position:0% talk about is how I see um adoption of say<01:10:20.600> cryp<01:10:20.880> graphic<01:10:21.080> technology<01:10:21.480> in<01:10:21.560> the 01:10:21.669 --> 01:10:21.679 align:start position:0% say cryp graphic technology in the 01:10:21.679 --> 01:10:22.950 align:start position:0% say cryp graphic technology in the context<01:10:21.960> of<01:10:22.080> all<01:10:22.159> the<01:10:22.239> other<01:10:22.400> cryptographic 01:10:22.950 --> 01:10:22.960 align:start position:0% context of all the other cryptographic 01:10:22.960 --> 01:10:25.510 align:start position:0% context of all the other cryptographic technology<01:10:23.800> if<01:10:23.880> we<01:10:24.040> look<01:10:24.239> at<01:10:24.880> um<01:10:25.320> cryog 01:10:25.510 --> 01:10:25.520 align:start position:0% technology if we look at um cryog 01:10:25.520 --> 01:10:27.189 align:start position:0% technology if we look at um cryog graphic<01:10:25.679> infra<01:10:25.960> over<01:10:26.080> the<01:10:26.280> last<01:10:26.679> you<01:10:26.800> know<01:10:27.040> 10 01:10:27.189 --> 01:10:27.199 align:start position:0% graphic infra over the last you know 10 01:10:27.199 --> 01:10:29.830 align:start position:0% graphic infra over the last you know 10 to<01:10:27.320> 20<01:10:27.600> years<01:10:28.040> we<01:10:28.199> see<01:10:28.520> that<01:10:29.040> there's<01:10:29.600> a 01:10:29.830 --> 01:10:29.840 align:start position:0% to 20 years we see that there's a 01:10:29.840 --> 01:10:31.590 align:start position:0% to 20 years we see that there's a practice<01:10:30.199> of<01:10:30.360> making<01:10:30.679> things<01:10:31.000> more<01:10:31.199> user 01:10:31.590 --> 01:10:31.600 align:start position:0% practice of making things more user 01:10:31.600 --> 01:10:35.709 align:start position:0% practice of making things more user inuitive<01:10:32.600> but<01:10:32.880> not<01:10:33.120> a<01:10:33.400> practice<01:10:34.080> of<01:10:34.640> say<01:10:34.960> like 01:10:35.709 --> 01:10:35.719 align:start position:0% inuitive but not a practice of say like 01:10:35.719 --> 01:10:37.229 align:start position:0% inuitive but not a practice of say like uh<01:10:35.880> private<01:10:36.159> key<01:10:36.360> ownership<01:10:36.760> so<01:10:36.880> for<01:10:37.000> instance 01:10:37.229 --> 01:10:37.239 align:start position:0% uh private key ownership so for instance 01:10:37.239 --> 01:10:39.310 align:start position:0% uh private key ownership so for instance with<01:10:37.360> VPN<01:10:38.040> it<01:10:38.120> was<01:10:38.320> very<01:10:38.560> hard<01:10:38.760> to<01:10:38.880> set<01:10:39.040> them<01:10:39.159> up 01:10:39.310 --> 01:10:39.320 align:start position:0% with VPN it was very hard to set them up 01:10:39.320 --> 01:10:40.990 align:start position:0% with VPN it was very hard to set them up at<01:10:39.480> first<01:10:40.040> and<01:10:40.159> then<01:10:40.360> now<01:10:40.520> it's<01:10:40.719> much<01:10:40.840> more 01:10:40.990 --> 01:10:41.000 align:start position:0% at first and then now it's much more 01:10:41.000 --> 01:10:42.630 align:start position:0% at first and then now it's much more turn<01:10:41.320> key<01:10:41.480> in<01:10:41.640> that<01:10:41.880> adoption<01:10:42.199> curve<01:10:42.440> maybe 01:10:42.630 --> 01:10:42.640 align:start position:0% turn key in that adoption curve maybe 01:10:42.640 --> 01:10:45.030 align:start position:0% turn key in that adoption curve maybe took<01:10:42.800> like<01:10:42.880> 10<01:10:43.159> 15<01:10:43.440> years<01:10:44.280> um<01:10:44.560> end<01:10:44.760> to<01:10:44.840> end 01:10:45.030 --> 01:10:45.040 align:start position:0% took like 10 15 years um end to end 01:10:45.040 --> 01:10:46.870 align:start position:0% took like 10 15 years um end to end encrypted<01:10:45.440> chat<01:10:46.080> um<01:10:46.320> initially<01:10:46.600> you<01:10:46.719> had<01:10:46.800> to 01:10:46.870 --> 01:10:46.880 align:start position:0% encrypted chat um initially you had to 01:10:46.880 --> 01:10:49.110 align:start position:0% encrypted chat um initially you had to roll<01:10:47.080> your<01:10:47.159> own<01:10:47.360> pgp<01:10:48.199> now<01:10:48.360> you<01:10:48.480> can<01:10:48.600> use<01:10:48.800> endend 01:10:49.110 --> 01:10:49.120 align:start position:0% roll your own pgp now you can use endend 01:10:49.120 --> 01:10:51.350 align:start position:0% roll your own pgp now you can use endend encrypted<01:10:49.719> Messengers<01:10:50.719> um<01:10:50.920> previously<01:10:51.280> you 01:10:51.350 --> 01:10:51.360 align:start position:0% encrypted Messengers um previously you 01:10:51.360 --> 01:10:52.550 align:start position:0% encrypted Messengers um previously you had<01:10:51.440> to<01:10:51.520> roll<01:10:51.679> your<01:10:51.760> own<01:10:51.920> tour<01:10:52.239> you<01:10:52.320> have<01:10:52.440> to 01:10:52.550 --> 01:10:52.560 align:start position:0% had to roll your own tour you have to 01:10:52.560 --> 01:10:53.790 align:start position:0% had to roll your own tour you have to find<01:10:52.760> your<01:10:52.840> own<01:10:52.960> exit<01:10:53.199> nodes<01:10:53.520> now<01:10:53.640> you<01:10:53.719> can 01:10:53.790 --> 01:10:53.800 align:start position:0% find your own exit nodes now you can 01:10:53.800 --> 01:10:55.790 align:start position:0% find your own exit nodes now you can just<01:10:53.920> use<01:10:54.080> Brave<01:10:54.320> incognito<01:10:54.840> mode 01:10:55.790 --> 01:10:55.800 align:start position:0% just use Brave incognito mode 01:10:55.800 --> 01:10:58.470 align:start position:0% just use Brave incognito mode um<01:10:56.320> to<01:10:56.719> have<01:10:56.880> TLS<01:10:57.360> interpret<01:10:57.640> TLS<01:10:57.960> or<01:10:58.080> have<01:10:58.199> TLS 01:10:58.470 --> 01:10:58.480 align:start position:0% um to have TLS interpret TLS or have TLS 01:10:58.480 --> 01:10:59.510 align:start position:0% um to have TLS interpret TLS or have TLS in<01:10:58.560> your<01:10:58.640> website<01:10:58.920> you<01:10:59.000> had<01:10:59.080> to<01:10:59.159> do<01:10:59.320> very 01:10:59.510 --> 01:10:59.520 align:start position:0% in your website you had to do very 01:10:59.520 --> 01:11:01.910 align:start position:0% in your website you had to do very bespoke<01:11:00.120> certificate<01:11:00.640> stuff<01:11:01.000> now<01:11:01.400> it's<01:11:01.560> all 01:11:01.910 --> 01:11:01.920 align:start position:0% bespoke certificate stuff now it's all 01:11:01.920 --> 01:11:04.110 align:start position:0% bespoke certificate stuff now it's all Happening<01:11:02.239> by<01:11:02.440> default<01:11:03.440> um<01:11:03.560> and<01:11:03.679> similarly 01:11:04.110 --> 01:11:04.120 align:start position:0% Happening by default um and similarly 01:11:04.120 --> 01:11:05.550 align:start position:0% Happening by default um and similarly you<01:11:04.199> can<01:11:04.400> you<01:11:04.520> can<01:11:04.640> make<01:11:04.760> a<01:11:04.880> similar<01:11:05.199> argument 01:11:05.550 --> 01:11:05.560 align:start position:0% you can you can make a similar argument 01:11:05.560 --> 01:11:08.590 align:start position:0% you can you can make a similar argument for<01:11:05.800> say<01:11:06.120> like<01:11:07.080> uh<01:11:07.679> blockchains<01:11:08.120> or<01:11:08.239> web<01:11:08.440> three 01:11:08.590 --> 01:11:08.600 align:start position:0% for say like uh blockchains or web three 01:11:08.600 --> 01:11:11.790 align:start position:0% for say like uh blockchains or web three data<01:11:08.800> or<01:11:08.880> even<01:11:09.159> cryptography<01:11:09.719> in<01:11:09.920> general<01:11:10.920> and 01:11:11.790 --> 01:11:11.800 align:start position:0% data or even cryptography in general and 01:11:11.800 --> 01:11:13.430 align:start position:0% data or even cryptography in general and um<01:11:12.080> one<01:11:12.199> of<01:11:12.320> the<01:11:12.440> main<01:11:12.719> takeaways<01:11:13.199> here<01:11:13.320> is 01:11:13.430 --> 01:11:13.440 align:start position:0% um one of the main takeaways here is 01:11:13.440 --> 01:11:14.830 align:start position:0% um one of the main takeaways here is that<01:11:13.600> like<01:11:13.719> there<01:11:13.800> should<01:11:13.960> be<01:11:14.080> an<01:11:14.239> easy<01:11:14.520> way<01:11:14.679> to 01:11:14.830 --> 01:11:14.840 align:start position:0% that like there should be an easy way to 01:11:14.840 --> 01:11:17.030 align:start position:0% that like there should be an easy way to do<01:11:15.000> these<01:11:15.159> kinds<01:11:15.360> of<01:11:15.520> proofs<01:11:16.480> um<01:11:16.760> where<01:11:16.880> you 01:11:17.030 --> 01:11:17.040 align:start position:0% do these kinds of proofs um where you 01:11:17.040 --> 01:11:18.470 align:start position:0% do these kinds of proofs um where you don't<01:11:17.239> have<01:11:17.360> to<01:11:17.520> punch<01:11:17.800> private<01:11:18.080> data<01:11:18.280> to<01:11:18.400> a 01:11:18.470 --> 01:11:18.480 align:start position:0% don't have to punch private data to a 01:11:18.480 --> 01:11:20.030 align:start position:0% don't have to punch private data to a server<01:11:18.800> because<01:11:19.000> in<01:11:19.120> all<01:11:19.360> the<01:11:19.520> cry<01:11:19.840> all<01:11:19.960> the 01:11:20.030 --> 01:11:20.040 align:start position:0% server because in all the cry all the 01:11:20.040 --> 01:11:21.270 align:start position:0% server because in all the cry all the technology<01:11:20.400> we've<01:11:20.560> seen<01:11:20.719> in<01:11:20.800> the<01:11:20.960> past<01:11:21.159> where 01:11:21.270 --> 01:11:21.280 align:start position:0% technology we've seen in the past where 01:11:21.280 --> 01:11:23.510 align:start position:0% technology we've seen in the past where cryptographic<01:11:22.239> technology<01:11:22.760> is<01:11:23.040> like<01:11:23.400> the 01:11:23.510 --> 01:11:23.520 align:start position:0% cryptographic technology is like the 01:11:23.520 --> 01:11:24.870 align:start position:0% cryptographic technology is like the purpose<01:11:23.800> of<01:11:23.880> the<01:11:24.000> thing<01:11:24.159> or<01:11:24.280> the<01:11:24.400> end<01:11:24.600> game 01:11:24.870 --> 01:11:24.880 align:start position:0% purpose of the thing or the end game 01:11:24.880 --> 01:11:26.950 align:start position:0% purpose of the thing or the end game like<01:11:24.960> you<01:11:25.360> never<01:11:25.640> want<01:11:26.040> to<01:11:26.239> manage<01:11:26.640> private 01:11:26.950 --> 01:11:26.960 align:start position:0% like you never want to manage private 01:11:26.960 --> 01:11:29.310 align:start position:0% like you never want to manage private data<01:11:27.199> for<01:11:27.360> users<01:11:27.760> it's<01:11:27.960> always<01:11:28.239> on<01:11:28.360> the<01:11:28.480> client 01:11:29.310 --> 01:11:29.320 align:start position:0% data for users it's always on the client 01:11:29.320 --> 01:11:31.870 align:start position:0% data for users it's always on the client side<01:11:30.320> um<01:11:30.800> and<01:11:30.960> I<01:11:31.080> think<01:11:31.360> you<01:11:31.440> know<01:11:31.640> folks 01:11:31.870 --> 01:11:31.880 align:start position:0% side um and I think you know folks 01:11:31.880 --> 01:11:33.110 align:start position:0% side um and I think you know folks alluded<01:11:32.199> to<01:11:32.320> this<01:11:32.400> in<01:11:32.560> many<01:11:32.719> of<01:11:32.800> the<01:11:32.880> earlier 01:11:33.110 --> 01:11:33.120 align:start position:0% alluded to this in many of the earlier 01:11:33.120 --> 01:11:34.709 align:start position:0% alluded to this in many of the earlier talk<01:11:33.600> lots<01:11:33.760> of<01:11:33.800> digital<01:11:34.040> signatures<01:11:34.440> you<01:11:34.560> can 01:11:34.709 --> 01:11:34.719 align:start position:0% talk lots of digital signatures you can 01:11:34.719 --> 01:11:36.470 align:start position:0% talk lots of digital signatures you can take<01:11:35.400> um<01:11:35.480> you<01:11:35.560> can<01:11:35.679> take<01:11:35.840> pass<01:11:36.120> Keys<01:11:36.320> you<01:11:36.400> can 01:11:36.470 --> 01:11:36.480 align:start position:0% take um you can take pass Keys you can 01:11:36.480 --> 01:11:39.110 align:start position:0% take um you can take pass Keys you can use<01:11:36.640> this<01:11:36.719> to<01:11:36.880> do<01:11:37.320> transactions<01:11:37.920> very<01:11:38.120> easily 01:11:39.110 --> 01:11:39.120 align:start position:0% use this to do transactions very easily 01:11:39.120 --> 01:11:40.310 align:start position:0% use this to do transactions very easily um<01:11:39.239> you<01:11:39.360> can<01:11:39.480> take<01:11:39.679> passports<01:11:40.080> you<01:11:40.159> can<01:11:40.239> do 01:11:40.310 --> 01:11:40.320 align:start position:0% um you can take passports you can do 01:11:40.320 --> 01:11:41.669 align:start position:0% um you can take passports you can do this<01:11:40.400> to<01:11:40.480> proove<01:11:40.719> citizenship<01:11:41.360> you<01:11:41.440> can<01:11:41.560> take 01:11:41.669 --> 01:11:41.679 align:start position:0% this to proove citizenship you can take 01:11:41.679 --> 01:11:43.030 align:start position:0% this to proove citizenship you can take app<01:11:41.840> a<01:11:41.960> test<01:11:42.159> you<01:11:42.239> can<01:11:42.320> use<01:11:42.440> this<01:11:42.560> to<01:11:42.679> approve 01:11:43.030 --> 01:11:43.040 align:start position:0% app a test you can use this to approve 01:11:43.040 --> 01:11:45.750 align:start position:0% app a test you can use this to approve execution<01:11:43.440> of<01:11:43.600> some<01:11:43.760> app<01:11:43.920> on<01:11:44.040> your<01:11:44.320> phone<01:11:45.320> um 01:11:45.750 --> 01:11:45.760 align:start position:0% execution of some app on your phone um 01:11:45.760 --> 01:11:48.390 align:start position:0% execution of some app on your phone um and<01:11:45.920> of<01:11:46.080> course<01:11:46.480> emails<01:11:47.360> um<01:11:47.880> and<01:11:48.120> the<01:11:48.239> really 01:11:48.390 --> 01:11:48.400 align:start position:0% and of course emails um and the really 01:11:48.400 --> 01:11:51.390 align:start position:0% and of course emails um and the really interesting<01:11:48.760> thing<01:11:48.960> here<01:11:49.199> is<01:11:49.480> that<01:11:50.360> uh<01:11:51.280> as 01:11:51.390 --> 01:11:51.400 align:start position:0% interesting thing here is that uh as 01:11:51.400 --> 01:11:52.950 align:start position:0% interesting thing here is that uh as long<01:11:51.560> as<01:11:51.679> you<01:11:51.760> have<01:11:51.880> a<01:11:51.960> digital<01:11:52.239> signature<01:11:52.840> you 01:11:52.950 --> 01:11:52.960 align:start position:0% long as you have a digital signature you 01:11:52.960 --> 01:11:54.669 align:start position:0% long as you have a digital signature you can<01:11:53.280> put<01:11:53.440> a<01:11:53.560> ZK<01:11:53.800> proof<01:11:54.040> on<01:11:54.159> top<01:11:54.320> of<01:11:54.440> that<01:11:54.560> and 01:11:54.669 --> 01:11:54.679 align:start position:0% can put a ZK proof on top of that and 01:11:54.679 --> 01:11:56.709 align:start position:0% can put a ZK proof on top of that and then<01:11:54.800> verify<01:11:55.400> that<01:11:55.480> offchain<01:11:55.880> data<01:11:56.159> onchain 01:11:56.709 --> 01:11:56.719 align:start position:0% then verify that offchain data onchain 01:11:56.719 --> 01:11:59.270 align:start position:0% then verify that offchain data onchain and<01:11:56.840> so<01:11:57.280> the<01:11:57.400> hope<01:11:57.639> is<01:11:57.840> that 01:11:59.270 --> 01:11:59.280 align:start position:0% and so the hope is that 01:11:59.280 --> 01:12:01.950 align:start position:0% and so the hope is that um<01:12:00.280> more<01:12:00.560> seeing<01:12:00.880> more<01:12:01.040> of<01:12:01.239> these<01:12:01.440> and<01:12:01.639> driving 01:12:01.950 --> 01:12:01.960 align:start position:0% um more seeing more of these and driving 01:12:01.960 --> 01:12:03.750 align:start position:0% um more seeing more of these and driving more<01:12:02.040> of<01:12:02.159> this<01:12:02.280> adoption<01:12:02.760> can<01:12:03.320> make<01:12:03.520> this<01:12:03.639> kind 01:12:03.750 --> 01:12:03.760 align:start position:0% more of this adoption can make this kind 01:12:03.760 --> 01:12:04.790 align:start position:0% more of this adoption can make this kind of<01:12:03.920> concept<01:12:04.199> of<01:12:04.320> cryptographic 01:12:04.790 --> 01:12:04.800 align:start position:0% of concept of cryptographic 01:12:04.800 --> 01:12:07.830 align:start position:0% of concept of cryptographic interoperability<01:12:05.800> more<01:12:06.040> tangible<01:12:07.000> um<01:12:07.480> and<01:12:07.600> so 01:12:07.830 --> 01:12:07.840 align:start position:0% interoperability more tangible um and so 01:12:07.840 --> 01:12:08.910 align:start position:0% interoperability more tangible um and so I<01:12:07.920> guess<01:12:08.040> most<01:12:08.199> folks<01:12:08.400> already<01:12:08.560> know<01:12:08.719> this<01:12:08.800> but 01:12:08.910 --> 01:12:08.920 align:start position:0% I guess most folks already know this but 01:12:08.920 --> 01:12:10.550 align:start position:0% I guess most folks already know this but email<01:12:09.159> are<01:12:09.280> sonicor<01:12:09.760> the<01:12:09.800> Deon<01:12:10.080> protocol<01:12:10.440> we 01:12:10.550 --> 01:12:10.560 align:start position:0% email are sonicor the Deon protocol we 01:12:10.560 --> 01:12:12.070 align:start position:0% email are sonicor the Deon protocol we stuff<01:12:10.800> this<01:12:10.880> into<01:12:11.000> a<01:12:11.120> ZK<01:12:11.440> proof<01:12:11.719> and<01:12:11.800> we<01:12:11.920> add 01:12:12.070 --> 01:12:12.080 align:start position:0% stuff this into a ZK proof and we add 01:12:12.080 --> 01:12:14.149 align:start position:0% stuff this into a ZK proof and we add selective<01:12:12.400> privacy<01:12:12.760> on<01:12:12.920> top<01:12:13.600> this<01:12:13.760> means<01:12:14.040> we 01:12:14.149 --> 01:12:14.159 align:start position:0% selective privacy on top this means we 01:12:14.159 --> 01:12:15.870 align:start position:0% selective privacy on top this means we can<01:12:14.320> keep<01:12:14.880> whatever<01:12:15.159> data<01:12:15.360> we<01:12:15.480> want<01:12:15.639> in<01:12:15.760> the 01:12:15.870 --> 01:12:15.880 align:start position:0% can keep whatever data we want in the 01:12:15.880 --> 01:12:18.229 align:start position:0% can keep whatever data we want in the email<01:12:16.400> private<01:12:17.040> we<01:12:17.159> can<01:12:17.480> directly<01:12:17.840> verify<01:12:18.159> the 01:12:18.229 --> 01:12:18.239 align:start position:0% email private we can directly verify the 01:12:18.239 --> 01:12:19.870 align:start position:0% email private we can directly verify the web<01:12:18.400> to<01:12:18.560> mail<01:12:18.760> server<01:12:19.199> and<01:12:19.320> we<01:12:19.400> can<01:12:19.520> verify 01:12:19.870 --> 01:12:19.880 align:start position:0% web to mail server and we can verify 01:12:19.880 --> 01:12:22.310 align:start position:0% web to mail server and we can verify them<01:12:20.000> on<01:12:20.560> chain<01:12:21.560> um<01:12:21.800> there's<01:12:21.960> a<01:12:22.040> bunch<01:12:22.199> of 01:12:22.310 --> 01:12:22.320 align:start position:0% them on chain um there's a bunch of 01:12:22.320 --> 01:12:23.270 align:start position:0% them on chain um there's a bunch of interesting<01:12:22.600> Primitives<01:12:23.040> that<01:12:23.120> we're 01:12:23.270 --> 01:12:23.280 align:start position:0% interesting Primitives that we're 01:12:23.280 --> 01:12:25.669 align:start position:0% interesting Primitives that we're thinking<01:12:23.639> about<01:12:24.639> um 01:12:25.669 --> 01:12:25.679 align:start position:0% thinking about um 01:12:25.679 --> 01:12:27.149 align:start position:0% thinking about um the<01:12:26.000> the<01:12:26.280> the<01:12:26.440> nice<01:12:26.639> thing<01:12:26.800> here<01:12:26.920> is<01:12:27.040> that 01:12:27.149 --> 01:12:27.159 align:start position:0% the the the nice thing here is that 01:12:27.159 --> 01:12:28.189 align:start position:0% the the the nice thing here is that we've<01:12:27.320> tried<01:12:27.480> to<01:12:27.600> abstract<01:12:27.920> these<01:12:28.040> all<01:12:28.120> the 01:12:28.189 --> 01:12:28.199 align:start position:0% we've tried to abstract these all the 01:12:28.199 --> 01:12:29.590 align:start position:0% we've tried to abstract these all the way<01:12:28.360> so<01:12:28.520> we<01:12:28.639> have<01:12:28.840> libraries<01:12:29.199> for<01:12:29.360> all<01:12:29.440> of 01:12:29.590 --> 01:12:29.600 align:start position:0% way so we have libraries for all of 01:12:29.600 --> 01:12:30.950 align:start position:0% way so we have libraries for all of these<01:12:29.760> things<01:12:30.080> in<01:12:30.239> all<01:12:30.400> the<01:12:30.480> different<01:12:30.679> ZK 01:12:30.950 --> 01:12:30.960 align:start position:0% these things in all the different ZK 01:12:30.960 --> 01:12:32.070 align:start position:0% these things in all the different ZK proving<01:12:31.199> languages<01:12:31.520> and<01:12:31.639> we're<01:12:31.760> constantly 01:12:32.070 --> 01:12:32.080 align:start position:0% proving languages and we're constantly 01:12:32.080 --> 01:12:34.270 align:start position:0% proving languages and we're constantly iterating<01:12:32.480> on<01:12:32.719> these<01:12:33.320> but<01:12:33.440> the<01:12:33.520> hope<01:12:33.760> is<01:12:33.920> that 01:12:34.270 --> 01:12:34.280 align:start position:0% iterating on these but the hope is that 01:12:34.280 --> 01:12:35.910 align:start position:0% iterating on these but the hope is that users<01:12:34.760> actually<01:12:35.040> creating<01:12:35.480> these<01:12:35.600> kinds<01:12:35.800> of 01:12:35.910 --> 01:12:35.920 align:start position:0% users actually creating these kinds of 01:12:35.920 --> 01:12:37.310 align:start position:0% users actually creating these kinds of proof<01:12:36.159> should<01:12:36.280> not<01:12:36.440> have<01:12:36.520> to<01:12:36.679> think<01:12:36.880> about<01:12:37.199> the 01:12:37.310 --> 01:12:37.320 align:start position:0% proof should not have to think about the 01:12:37.320 --> 01:12:38.750 align:start position:0% proof should not have to think about the details<01:12:37.719> of<01:12:37.880> which<01:12:38.040> of<01:12:38.159> these<01:12:38.360> Primitives 01:12:38.750 --> 01:12:38.760 align:start position:0% details of which of these Primitives 01:12:38.760 --> 01:12:41.990 align:start position:0% details of which of these Primitives they're<01:12:39.239> using<01:12:40.239> um<01:12:40.800> and<01:12:41.159> you<01:12:41.280> know<01:12:41.560> one<01:12:41.719> simple 01:12:41.990 --> 01:12:42.000 align:start position:0% they're using um and you know one simple 01:12:42.000 --> 01:12:43.189 align:start position:0% they're using um and you know one simple idea<01:12:42.239> of<01:12:42.320> something<01:12:42.520> you<01:12:42.600> could<01:12:42.719> do<01:12:42.840> is<01:12:43.000> very 01:12:43.189 --> 01:12:43.199 align:start position:0% idea of something you could do is very 01:12:43.199 --> 01:12:45.709 align:start position:0% idea of something you could do is very simple<01:12:43.560> email<01:12:43.880> redaction<01:12:44.280> or<01:12:44.719> whistleblowing 01:12:45.709 --> 01:12:45.719 align:start position:0% simple email redaction or whistleblowing 01:12:45.719 --> 01:12:46.950 align:start position:0% simple email redaction or whistleblowing um<01:12:45.880> where<01:12:46.000> you<01:12:46.080> know<01:12:46.239> you<01:12:46.360> you<01:12:46.480> take<01:12:46.600> an<01:12:46.679> email 01:12:46.950 --> 01:12:46.960 align:start position:0% um where you know you you take an email 01:12:46.960 --> 01:12:47.990 align:start position:0% um where you know you you take an email you<01:12:47.080> highlight<01:12:47.360> what<01:12:47.440> you<01:12:47.520> want<01:12:47.600> to<01:12:47.719> hide<01:12:47.920> and 01:12:47.990 --> 01:12:48.000 align:start position:0% you highlight what you want to hide and 01:12:48.000 --> 01:12:49.950 align:start position:0% you highlight what you want to hide and you<01:12:48.120> reveal<01:12:48.480> everything<01:12:48.760> else<01:12:49.679> um<01:12:49.760> but<01:12:49.880> you 01:12:49.950 --> 01:12:49.960 align:start position:0% you reveal everything else um but you 01:12:49.960 --> 01:12:51.470 align:start position:0% you reveal everything else um but you can<01:12:50.040> do<01:12:50.199> much<01:12:50.360> more<01:12:50.560> complicated<01:12:51.040> things<01:12:51.320> one 01:12:51.470 --> 01:12:51.480 align:start position:0% can do much more complicated things one 01:12:51.480 --> 01:12:53.870 align:start position:0% can do much more complicated things one cool<01:12:51.679> thing<01:12:51.800> that<01:12:51.920> zkp<01:12:52.560> recently<01:12:52.920> built<01:12:53.520> is<01:12:53.639> a 01:12:53.870 --> 01:12:53.880 align:start position:0% cool thing that zkp recently built is a 01:12:53.880 --> 01:12:55.910 align:start position:0% cool thing that zkp recently built is a domain<01:12:54.600> Marketplace<01:12:55.239> on<01:12:55.320> top<01:12:55.440> of<01:12:55.520> ethereum 01:12:55.910 --> 01:12:55.920 align:start position:0% domain Marketplace on top of ethereum 01:12:55.920 --> 01:12:57.430 align:start position:0% domain Marketplace on top of ethereum where<01:12:56.040> you<01:12:56.120> can<01:12:56.360> prove<01:12:56.840> you<01:12:57.000> transfer<01:12:57.360> a 01:12:57.430 --> 01:12:57.440 align:start position:0% where you can prove you transfer a 01:12:57.440 --> 01:12:58.629 align:start position:0% where you can prove you transfer a domain<01:12:57.679> on<01:12:57.800> name<01:12:58.000> cheap<01:12:58.280> you<01:12:58.400> get<01:12:58.520> a 01:12:58.629 --> 01:12:58.639 align:start position:0% domain on name cheap you get a 01:12:58.639 --> 01:13:00.629 align:start position:0% domain on name cheap you get a confirmation<01:12:59.159> email<01:12:59.840> and<01:12:59.920> you<01:13:00.080> use<01:13:00.320> that<01:13:00.480> for 01:13:00.629 --> 01:13:00.639 align:start position:0% confirmation email and you use that for 01:13:00.639 --> 01:13:02.870 align:start position:0% confirmation email and you use that for the<01:13:00.760> seller<01:13:01.080> to<01:13:01.239> unlock<01:13:01.639> the<01:13:01.800> escro<01:13:02.400> money 01:13:02.870 --> 01:13:02.880 align:start position:0% the seller to unlock the escro money 01:13:02.880 --> 01:13:05.070 align:start position:0% the seller to unlock the escro money that<01:13:03.040> the<01:13:03.199> buyer<01:13:03.520> locked<01:13:03.840> on<01:13:04.000> chain<01:13:04.880> um<01:13:05.000> and 01:13:05.070 --> 01:13:05.080 align:start position:0% that the buyer locked on chain um and 01:13:05.080 --> 01:13:06.070 align:start position:0% that the buyer locked on chain um and this<01:13:05.159> is<01:13:05.280> quite<01:13:05.400> interesting<01:13:05.800> because<01:13:05.960> this 01:13:06.070 --> 01:13:06.080 align:start position:0% this is quite interesting because this 01:13:06.080 --> 01:13:07.669 align:start position:0% this is quite interesting because this means<01:13:06.360> that<01:13:06.480> you<01:13:06.639> can<01:13:07.120> as<01:13:07.239> long<01:13:07.360> as<01:13:07.440> you<01:13:07.560> have<01:13:07.600> a 01:13:07.669 --> 01:13:07.679 align:start position:0% means that you can as long as you have a 01:13:07.679 --> 01:13:09.070 align:start position:0% means that you can as long as you have a signature<01:13:08.080> you<01:13:08.159> can<01:13:08.280> build<01:13:08.520> markets<01:13:08.840> on<01:13:08.960> top 01:13:09.070 --> 01:13:09.080 align:start position:0% signature you can build markets on top 01:13:09.080 --> 01:13:10.430 align:start position:0% signature you can build markets on top of<01:13:09.199> it<01:13:09.280> you<01:13:09.360> can<01:13:09.440> build<01:13:09.600> interoperability<01:13:10.280> on 01:13:10.430 --> 01:13:10.440 align:start position:0% of it you can build interoperability on 01:13:10.440 --> 01:13:12.229 align:start position:0% of it you can build interoperability on top<01:13:10.560> of<01:13:10.679> it<01:13:11.320> um<01:13:11.440> but<01:13:11.560> how<01:13:11.679> do<01:13:11.800> we<01:13:11.960> have<01:13:12.080> a 01:13:12.229 --> 01:13:12.239 align:start position:0% top of it um but how do we have a 01:13:12.239 --> 01:13:16.310 align:start position:0% top of it um but how do we have a million<01:13:12.600> zkp<01:13:13.440> tops<01:13:14.440> um<01:13:15.400> and<01:13:15.480> so<01:13:15.600> the<01:13:15.719> idea<01:13:16.040> is 01:13:16.310 --> 01:13:16.320 align:start position:0% million zkp tops um and so the idea is 01:13:16.320 --> 01:13:17.390 align:start position:0% million zkp tops um and so the idea is you<01:13:16.440> need<01:13:16.560> to<01:13:16.639> be<01:13:16.719> able<01:13:16.880> to<01:13:16.960> make<01:13:17.120> these<01:13:17.239> new 01:13:17.390 --> 01:13:17.400 align:start position:0% you need to be able to make these new 01:13:17.400 --> 01:13:18.750 align:start position:0% you need to be able to make these new kinds<01:13:17.560> of<01:13:17.679> proofs<01:13:18.040> very<01:13:18.239> very<01:13:18.440> fast<01:13:18.600> and 01:13:18.750 --> 01:13:18.760 align:start position:0% kinds of proofs very very fast and 01:13:18.760 --> 01:13:20.470 align:start position:0% kinds of proofs very very fast and integrate<01:13:19.080> them<01:13:19.280> very<01:13:19.480> very<01:13:19.719> fast<01:13:20.000> and<01:13:20.360> part 01:13:20.470 --> 01:13:20.480 align:start position:0% integrate them very very fast and part 01:13:20.480 --> 01:13:22.709 align:start position:0% integrate them very very fast and part of<01:13:20.639> this<01:13:20.840> is<01:13:21.120> the<01:13:21.239> pods<01:13:21.560> Vision<01:13:22.199> it's<01:13:22.440> you<01:13:22.520> know 01:13:22.709 --> 01:13:22.719 align:start position:0% of this is the pods Vision it's you know 01:13:22.719 --> 01:13:24.149 align:start position:0% of this is the pods Vision it's you know very<01:13:22.880> easy<01:13:23.120> to<01:13:23.280> to<01:13:23.400> select<01:13:23.639> which<01:13:23.800> proofs<01:13:24.040> you 01:13:24.149 --> 01:13:24.159 align:start position:0% very easy to to select which proofs you 01:13:24.159 --> 01:13:25.830 align:start position:0% very easy to to select which proofs you want<01:13:24.480> and<01:13:24.600> part<01:13:24.719> of<01:13:24.840> it<01:13:24.920> is<01:13:25.159> actually<01:13:25.400> defining 01:13:25.830 --> 01:13:25.840 align:start position:0% want and part of it is actually defining 01:13:25.840 --> 01:13:27.270 align:start position:0% want and part of it is actually defining these<01:13:25.960> kinds<01:13:26.120> of<01:13:26.239> proofs<01:13:26.480> in<01:13:26.600> a<01:13:26.719> very<01:13:26.880> bespoke 01:13:27.270 --> 01:13:27.280 align:start position:0% these kinds of proofs in a very bespoke 01:13:27.280 --> 01:13:29.990 align:start position:0% these kinds of proofs in a very bespoke way<01:13:27.400> for<01:13:27.560> each<01:13:27.760> proof<01:13:28.120> system<01:13:29.120> and 01:13:29.990 --> 01:13:30.000 align:start position:0% way for each proof system and 01:13:30.000 --> 01:13:32.229 align:start position:0% way for each proof system and so<01:13:31.000> one<01:13:31.120> of<01:13:31.239> one<01:13:31.360> of<01:13:31.440> the<01:13:31.520> Visions<01:13:31.840> we<01:13:32.000> have<01:13:32.159> is 01:13:32.229 --> 01:13:32.239 align:start position:0% so one of one of the Visions we have is 01:13:32.239 --> 01:13:34.030 align:start position:0% so one of one of the Visions we have is that<01:13:32.360> it<01:13:32.440> should<01:13:32.639> be<01:13:32.840> very<01:13:33.199> easy<01:13:33.560> for<01:13:33.760> an<01:13:33.880> app 01:13:34.030 --> 01:13:34.040 align:start position:0% that it should be very easy for an app 01:13:34.040 --> 01:13:35.189 align:start position:0% that it should be very easy for an app developer<01:13:34.360> to<01:13:34.440> not<01:13:34.600> have<01:13:34.719> to<01:13:34.840> think<01:13:34.960> about 01:13:35.189 --> 01:13:35.199 align:start position:0% developer to not have to think about 01:13:35.199 --> 01:13:36.629 align:start position:0% developer to not have to think about these<01:13:35.400> details<01:13:35.800> of<01:13:36.000> what<01:13:36.120> is<01:13:36.239> the<01:13:36.320> back<01:13:36.440> end<01:13:36.600> of 01:13:36.629 --> 01:13:36.639 align:start position:0% these details of what is the back end of 01:13:36.639 --> 01:13:37.629 align:start position:0% these details of what is the back end of the<01:13:36.719> cryptographic<01:13:37.159> infrastructure<01:13:37.520> they're 01:13:37.629 --> 01:13:37.639 align:start position:0% the cryptographic infrastructure they're 01:13:37.639 --> 01:13:39.590 align:start position:0% the cryptographic infrastructure they're using<01:13:37.920> they<01:13:38.040> just<01:13:38.199> say<01:13:38.480> I<01:13:38.560> want<01:13:38.719> it<01:13:38.840> to<01:13:39.040> happen 01:13:39.590 --> 01:13:39.600 align:start position:0% using they just say I want it to happen 01:13:39.600 --> 01:13:41.110 align:start position:0% using they just say I want it to happen on<01:13:39.719> the<01:13:39.840> client<01:13:40.199> side<01:13:40.360> or<01:13:40.440> on<01:13:40.520> the<01:13:40.600> server<01:13:40.920> side 01:13:41.110 --> 01:13:41.120 align:start position:0% on the client side or on the server side 01:13:41.120 --> 01:13:43.629 align:start position:0% on the client side or on the server side and<01:13:41.199> it<01:13:41.280> should<01:13:41.480> just<01:13:41.800> happen<01:13:42.800> um<01:13:43.280> and<01:13:43.400> so<01:13:43.520> you 01:13:43.629 --> 01:13:43.639 align:start position:0% and it should just happen um and so you 01:13:43.639 --> 01:13:45.149 align:start position:0% and it should just happen um and so you know<01:13:43.800> we<01:13:44.040> we<01:13:44.199> we've<01:13:44.360> investigated<01:13:44.800> all<01:13:44.920> these 01:13:45.149 --> 01:13:45.159 align:start position:0% know we we we've investigated all these 01:13:45.159 --> 01:13:46.430 align:start position:0% know we we we've investigated all these invested<01:13:45.679> we've<01:13:45.920> you<01:13:46.000> know<01:13:46.159> created 01:13:46.430 --> 01:13:46.440 align:start position:0% invested we've you know created 01:13:46.440 --> 01:13:49.070 align:start position:0% invested we've you know created primitive<01:13:46.800> in<01:13:46.920> many<01:13:47.080> of<01:13:47.159> these<01:13:47.320> languages<01:13:48.000> but 01:13:49.070 --> 01:13:49.080 align:start position:0% primitive in many of these languages but 01:13:49.080 --> 01:13:51.470 align:start position:0% primitive in many of these languages but um<01:13:50.080> the<01:13:50.159> point<01:13:50.440> is<01:13:50.639> that<01:13:50.800> we<01:13:50.960> we<01:13:51.080> decided<01:13:51.360> to 01:13:51.470 --> 01:13:51.480 align:start position:0% um the point is that we we decided to 01:13:51.480 --> 01:13:54.070 align:start position:0% um the point is that we we decided to abstract<01:13:51.840> this<01:13:51.960> away<01:13:52.199> so<01:13:52.400> that<01:13:52.920> you<01:13:53.760> you<01:13:53.960> you 01:13:54.070 --> 01:13:54.080 align:start position:0% abstract this away so that you you you 01:13:54.080 --> 01:13:55.390 align:start position:0% abstract this away so that you you you kind<01:13:54.199> of<01:13:54.320> had<01:13:54.400> the<01:13:54.480> proof<01:13:54.679> system<01:13:54.880> to<01:13:55.080> decided 01:13:55.390 --> 01:13:55.400 align:start position:0% kind of had the proof system to decided 01:13:55.400 --> 01:13:57.510 align:start position:0% kind of had the proof system to decided for<01:13:55.600> you<01:13:56.239> and<01:13:56.320> so<01:13:56.440> the<01:13:56.560> idea<01:13:56.800> is<01:13:56.920> you<01:13:57.040> can<01:13:57.280> say 01:13:57.510 --> 01:13:57.520 align:start position:0% for you and so the idea is you can say 01:13:57.520 --> 01:13:59.270 align:start position:0% for you and so the idea is you can say look<01:13:57.719> I<01:13:57.800> want<01:13:58.040> this<01:13:58.199> specific<01:13:58.480> ZK<01:13:58.760> email<01:13:59.040> proof 01:13:59.270 --> 01:13:59.280 align:start position:0% look I want this specific ZK email proof 01:13:59.280 --> 01:14:00.870 align:start position:0% look I want this specific ZK email proof maybe<01:13:59.639> the<01:13:59.880> the<01:14:00.040> proof<01:14:00.239> that<01:14:00.320> you<01:14:00.440> got<01:14:00.639> say 01:14:00.870 --> 01:14:00.880 align:start position:0% maybe the the proof that you got say 01:14:00.880 --> 01:14:02.790 align:start position:0% maybe the the proof that you got say rejected<01:14:01.239> from<01:14:01.360> Devcon<01:14:02.320> and<01:14:02.440> then<01:14:02.600> I'm<01:14:02.719> going 01:14:02.790 --> 01:14:02.800 align:start position:0% rejected from Devcon and then I'm going 01:14:02.800 --> 01:14:04.950 align:start position:0% rejected from Devcon and then I'm going to<01:14:02.920> specify<01:14:03.520> whether<01:14:03.719> I'm<01:14:03.880> local<01:14:04.159> or<01:14:04.360> not<01:14:04.880> and 01:14:04.950 --> 01:14:04.960 align:start position:0% to specify whether I'm local or not and 01:14:04.960 --> 01:14:06.390 align:start position:0% to specify whether I'm local or not and I<01:14:05.040> can<01:14:05.199> put<01:14:05.360> other<01:14:05.560> parameters<01:14:06.040> here<01:14:06.199> if<01:14:06.280> I 01:14:06.390 --> 01:14:06.400 align:start position:0% I can put other parameters here if I 01:14:06.400 --> 01:14:07.910 align:start position:0% I can put other parameters here if I want<01:14:06.520> to<01:14:06.600> be<01:14:06.760> more<01:14:06.920> selective<01:14:07.360> like<01:14:07.520> oh<01:14:07.639> I<01:14:07.760> want 01:14:07.910 --> 01:14:07.920 align:start position:0% want to be more selective like oh I want 01:14:07.920 --> 01:14:09.470 align:start position:0% want to be more selective like oh I want this<01:14:08.040> to<01:14:08.199> be<01:14:08.600> you<01:14:08.679> know<01:14:08.880> I<01:14:08.960> want<01:14:09.120> the<01:14:09.280> Pod 01:14:09.470 --> 01:14:09.480 align:start position:0% this to be you know I want the Pod 01:14:09.480 --> 01:14:10.430 align:start position:0% this to be you know I want the Pod version<01:14:09.719> of<01:14:09.880> this<01:14:10.000> I<01:14:10.080> want<01:14:10.199> it<01:14:10.280> to<01:14:10.360> be 01:14:10.430 --> 01:14:10.440 align:start position:0% version of this I want it to be 01:14:10.440 --> 01:14:12.709 align:start position:0% version of this I want it to be composable<01:14:10.840> with<01:14:10.920> rust<01:14:11.320> whatever<01:14:11.560> it<01:14:11.679> is<01:14:12.239> and 01:14:12.709 --> 01:14:12.719 align:start position:0% composable with rust whatever it is and 01:14:12.719 --> 01:14:13.870 align:start position:0% composable with rust whatever it is and create<01:14:13.000> prover<01:14:13.320> will<01:14:13.440> automatically 01:14:13.870 --> 01:14:13.880 align:start position:0% create prover will automatically 01:14:13.880 --> 01:14:15.350 align:start position:0% create prover will automatically determine<01:14:14.199> the<01:14:14.320> best<01:14:14.440> prover<01:14:14.760> for<01:14:14.880> your<01:14:15.040> use 01:14:15.350 --> 01:14:15.360 align:start position:0% determine the best prover for your use 01:14:15.360 --> 01:14:17.030 align:start position:0% determine the best prover for your use case<01:14:15.960> and<01:14:16.120> when<01:14:16.239> you<01:14:16.360> actually<01:14:16.560> want<01:14:16.679> to<01:14:16.840> use 01:14:17.030 --> 01:14:17.040 align:start position:0% case and when you actually want to use 01:14:17.040 --> 01:14:20.790 align:start position:0% case and when you actually want to use it<01:14:17.440> you<01:14:17.560> can<01:14:18.560> uh<01:14:18.760> just<01:14:19.679> uh<01:14:19.880> call<01:14:20.440> exactly<01:14:20.719> what 01:14:20.790 --> 01:14:20.800 align:start position:0% it you can uh just uh call exactly what 01:14:20.800 --> 01:14:22.070 align:start position:0% it you can uh just uh call exactly what you<01:14:20.880> want<01:14:20.960> to<01:14:21.040> do<01:14:21.159> generate<01:14:21.520> proof<01:14:21.760> verify 01:14:22.070 --> 01:14:22.080 align:start position:0% you want to do generate proof verify 01:14:22.080 --> 01:14:23.310 align:start position:0% you want to do generate proof verify onchain<01:14:22.440> whatever<01:14:22.679> and<01:14:22.800> it'll<01:14:23.000> just<01:14:23.120> happen 01:14:23.310 --> 01:14:23.320 align:start position:0% onchain whatever and it'll just happen 01:14:23.320 --> 01:14:25.990 align:start position:0% onchain whatever and it'll just happen in<01:14:23.440> the<01:14:23.560> background<01:14:23.920> for<01:14:24.199> you<01:14:24.920> um<01:14:25.159> um<01:14:25.440> and<01:14:25.880> the 01:14:25.990 --> 01:14:26.000 align:start position:0% in the background for you um um and the 01:14:26.000 --> 01:14:27.790 align:start position:0% in the background for you um um and the hope<01:14:26.239> is<01:14:26.440> that<01:14:26.880> again<01:14:27.080> by<01:14:27.239> extracting 01:14:27.790 --> 01:14:27.800 align:start position:0% hope is that again by extracting 01:14:27.800 --> 01:14:29.390 align:start position:0% hope is that again by extracting extracting<01:14:28.199> this<01:14:28.600> abstracting<01:14:29.040> this<01:14:29.159> away 01:14:29.390 --> 01:14:29.400 align:start position:0% extracting this abstracting this away 01:14:29.400 --> 01:14:31.510 align:start position:0% extracting this abstracting this away from<01:14:29.679> actual<01:14:30.040> developers<01:14:31.040> um<01:14:31.120> you<01:14:31.239> don't<01:14:31.400> have 01:14:31.510 --> 01:14:31.520 align:start position:0% from actual developers um you don't have 01:14:31.520 --> 01:14:34.149 align:start position:0% from actual developers um you don't have to<01:14:31.600> think<01:14:31.760> about<01:14:31.880> the<01:14:32.040> ZK<01:14:32.320> as<01:14:32.440> deeply<01:14:33.159> anymore 01:14:34.149 --> 01:14:34.159 align:start position:0% to think about the ZK as deeply anymore 01:14:34.159 --> 01:14:35.270 align:start position:0% to think about the ZK as deeply anymore but<01:14:34.239> how<01:14:34.360> do<01:14:34.440> you<01:14:34.560> actually<01:14:34.760> create<01:14:35.120> these 01:14:35.270 --> 01:14:35.280 align:start position:0% but how do you actually create these 01:14:35.280 --> 01:14:37.629 align:start position:0% but how do you actually create these proofs<01:14:35.600> like<01:14:35.679> that<01:14:35.840> Devcon<01:14:36.199> rejection<01:14:36.639> proof 01:14:37.629 --> 01:14:37.639 align:start position:0% proofs like that Devcon rejection proof 01:14:37.639 --> 01:14:39.070 align:start position:0% proofs like that Devcon rejection proof um<01:14:37.880> The<01:14:38.000> Hope<01:14:38.199> is<01:14:38.320> that<01:14:38.440> you<01:14:38.520> can<01:14:38.679> make<01:14:38.880> this 01:14:39.070 --> 01:14:39.080 align:start position:0% um The Hope is that you can make this 01:14:39.080 --> 01:14:40.750 align:start position:0% um The Hope is that you can make this really<01:14:39.320> easy<01:14:39.560> to<01:14:39.760> make<01:14:40.199> so<01:14:40.360> we've<01:14:40.520> done<01:14:40.679> a 01:14:40.750 --> 01:14:40.760 align:start position:0% really easy to make so we've done a 01:14:40.760 --> 01:14:42.310 align:start position:0% really easy to make so we've done a bunch<01:14:40.920> of<01:14:41.080> iteration<01:14:41.560> with<01:14:41.719> folks<01:14:41.960> building 01:14:42.310 --> 01:14:42.320 align:start position:0% bunch of iteration with folks building 01:14:42.320 --> 01:14:44.590 align:start position:0% bunch of iteration with folks building different<01:14:42.560> kinds<01:14:42.719> of<01:14:42.840> patterns<01:14:43.840> um<01:14:44.320> and<01:14:44.440> we've 01:14:44.590 --> 01:14:44.600 align:start position:0% different kinds of patterns um and we've 01:14:44.600 --> 01:14:45.790 align:start position:0% different kinds of patterns um and we've kind<01:14:44.679> of<01:14:44.760> settled<01:14:45.040> on<01:14:45.120> this<01:14:45.239> flow<01:14:45.520> that<01:14:45.600> seems 01:14:45.790 --> 01:14:45.800 align:start position:0% kind of settled on this flow that seems 01:14:45.800 --> 01:14:47.270 align:start position:0% kind of settled on this flow that seems to<01:14:45.880> be<01:14:46.000> intuitive<01:14:46.360> for<01:14:46.520> most<01:14:46.719> people<01:14:47.040> which<01:14:47.120> is 01:14:47.270 --> 01:14:47.280 align:start position:0% to be intuitive for most people which is 01:14:47.280 --> 01:14:49.030 align:start position:0% to be intuitive for most people which is basically<01:14:47.920> you<01:14:48.120> name<01:14:48.320> your<01:14:48.480> pattern<01:14:48.840> you 01:14:49.030 --> 01:14:49.040 align:start position:0% basically you name your pattern you 01:14:49.040 --> 01:14:50.830 align:start position:0% basically you name your pattern you upload<01:14:49.360> an<01:14:49.520> example<01:14:49.920> email<01:14:50.560> and<01:14:50.639> then<01:14:50.719> we 01:14:50.830 --> 01:14:50.840 align:start position:0% upload an example email and then we 01:14:50.840 --> 01:14:52.390 align:start position:0% upload an example email and then we autofill<01:14:51.280> a<01:14:51.360> bunch<01:14:51.520> of<01:14:51.679> information<01:14:52.199> from 01:14:52.390 --> 01:14:52.400 align:start position:0% autofill a bunch of information from 01:14:52.400 --> 01:14:54.310 align:start position:0% autofill a bunch of information from your<01:14:52.600> example<01:14:52.960> email<01:14:53.280> so<01:14:53.400> we<01:14:53.560> say<01:14:53.920> you<01:14:54.040> know 01:14:54.310 --> 01:14:54.320 align:start position:0% your example email so we say you know 01:14:54.320 --> 01:14:56.229 align:start position:0% your example email so we say you know who<01:14:54.440> is<01:14:54.520> the<01:14:54.639> sender<01:14:55.159> what<01:14:55.239> is<01:14:55.320> a<01:14:55.480> selector 01:14:56.229 --> 01:14:56.239 align:start position:0% who is the sender what is a selector 01:14:56.239 --> 01:14:57.229 align:start position:0% who is the sender what is a selector what<01:14:56.320> are<01:14:56.480> all<01:14:56.560> the<01:14:56.679> different<01:14:56.880> lengths<01:14:57.159> and 01:14:57.229 --> 01:14:57.239 align:start position:0% what are all the different lengths and 01:14:57.239 --> 01:14:59.070 align:start position:0% what are all the different lengths and we<01:14:57.320> will<01:14:57.440> autofill<01:14:57.920> this<01:14:58.080> information<01:14:58.520> for 01:14:59.070 --> 01:14:59.080 align:start position:0% we will autofill this information for 01:14:59.080 --> 01:15:01.669 align:start position:0% we will autofill this information for you<01:15:00.080> and<01:15:00.239> then<01:15:00.880> um<01:15:01.040> one<01:15:01.199> of<01:15:01.320> the<01:15:01.400> things<01:15:01.560> we 01:15:01.669 --> 01:15:01.679 align:start position:0% you and then um one of the things we 01:15:01.679 --> 01:15:02.990 align:start position:0% you and then um one of the things we Noti<01:15:01.960> is<01:15:02.040> that<01:15:02.159> when<01:15:02.239> you<01:15:02.400> actually<01:15:02.600> want<01:15:02.760> to 01:15:02.990 --> 01:15:03.000 align:start position:0% Noti is that when you actually want to 01:15:03.000 --> 01:15:04.310 align:start position:0% Noti is that when you actually want to parse<01:15:03.199> the<01:15:03.280> email<01:15:03.600> you<01:15:03.760> have<01:15:03.840> to<01:15:04.000> basically 01:15:04.310 --> 01:15:04.320 align:start position:0% parse the email you have to basically 01:15:04.320 --> 01:15:06.510 align:start position:0% parse the email you have to basically Define<01:15:04.639> this<01:15:04.760> like<01:15:04.920> Rex<01:15:05.320> to<01:15:05.480> do<01:15:05.679> that<01:15:06.239> um<01:15:06.440> this 01:15:06.510 --> 01:15:06.520 align:start position:0% Define this like Rex to do that um this 01:15:06.520 --> 01:15:08.030 align:start position:0% Define this like Rex to do that um this is<01:15:06.560> a<01:15:06.679> great<01:15:06.880> gor<01:15:07.239> post<01:15:07.440> where<01:15:07.560> he<01:15:07.679> talks<01:15:07.880> about 01:15:08.030 --> 01:15:08.040 align:start position:0% is a great gor post where he talks about 01:15:08.040 --> 01:15:09.750 align:start position:0% is a great gor post where he talks about how<01:15:08.159> Rex<01:15:08.520> is<01:15:08.679> kind<01:15:08.800> of<01:15:08.880> like<01:15:09.000> a<01:15:09.159> very<01:15:09.400> early 01:15:09.750 --> 01:15:09.760 align:start position:0% how Rex is kind of like a very early 01:15:09.760 --> 01:15:11.950 align:start position:0% how Rex is kind of like a very early vision<01:15:10.000> of<01:15:10.159> neural<01:15:10.480> networks<01:15:10.840> it<01:15:11.000> was<01:15:11.159> like<01:15:11.480> uh 01:15:11.950 --> 01:15:11.960 align:start position:0% vision of neural networks it was like uh 01:15:11.960 --> 01:15:12.950 align:start position:0% vision of neural networks it was like uh the<01:15:12.040> folks<01:15:12.239> who<01:15:12.320> were<01:15:12.400> inventing<01:15:12.679> this<01:15:12.800> stuff 01:15:12.950 --> 01:15:12.960 align:start position:0% the folks who were inventing this stuff 01:15:12.960 --> 01:15:14.270 align:start position:0% the folks who were inventing this stuff were<01:15:13.080> like<01:15:13.239> oh<01:15:13.360> like<01:15:13.520> rexes<01:15:13.920> are<01:15:14.080> really 01:15:14.270 --> 01:15:14.280 align:start position:0% were like oh like rexes are really 01:15:14.280 --> 01:15:15.510 align:start position:0% were like oh like rexes are really powerful<01:15:14.719> and<01:15:14.800> so<01:15:15.000> that's<01:15:15.239> part<01:15:15.360> of<01:15:15.440> the 01:15:15.510 --> 01:15:15.520 align:start position:0% powerful and so that's part of the 01:15:15.520 --> 01:15:16.669 align:start position:0% powerful and so that's part of the reason<01:15:15.719> that<01:15:15.800> we<01:15:15.920> rely<01:15:16.159> on<01:15:16.239> them<01:15:16.360> for<01:15:16.440> a<01:15:16.520> lot<01:15:16.600> of 01:15:16.669 --> 01:15:16.679 align:start position:0% reason that we rely on them for a lot of 01:15:16.679 --> 01:15:19.470 align:start position:0% reason that we rely on them for a lot of the<01:15:16.760> pars<01:15:17.000> saying<01:15:17.920> um<01:15:18.280> and<01:15:19.000> in<01:15:19.080> a<01:15:19.199> kind<01:15:19.280> of<01:15:19.360> a 01:15:19.470 --> 01:15:19.480 align:start position:0% the pars saying um and in a kind of a 01:15:19.480 --> 01:15:21.270 align:start position:0% the pars saying um and in a kind of a different<01:15:19.760> way<01:15:19.960> we<01:15:20.120> basically<01:15:20.679> like<01:15:21.199> we 01:15:21.270 --> 01:15:21.280 align:start position:0% different way we basically like we 01:15:21.280 --> 01:15:22.550 align:start position:0% different way we basically like we notice<01:15:21.600> one<01:15:21.719> of<01:15:21.800> the<01:15:21.920> problems<01:15:22.239> is<01:15:22.360> that 01:15:22.550 --> 01:15:22.560 align:start position:0% notice one of the problems is that 01:15:22.560 --> 01:15:24.189 align:start position:0% notice one of the problems is that people<01:15:22.920> often<01:15:23.280> like<01:15:23.639> don't<01:15:23.920> Define 01:15:24.189 --> 01:15:24.199 align:start position:0% people often like don't Define 01:15:24.199 --> 01:15:26.870 align:start position:0% people often like don't Define deterministic<01:15:24.719> re<01:15:25.080> is<01:15:25.320> very<01:15:25.520> well<01:15:26.360> uh<01:15:26.560> like 01:15:26.870 --> 01:15:26.880 align:start position:0% deterministic re is very well uh like 01:15:26.880 --> 01:15:28.470 align:start position:0% deterministic re is very well uh like many<01:15:27.120> folks<01:15:27.719> like<01:15:27.960> because<01:15:28.159> there's<01:15:28.320> some 01:15:28.470 --> 01:15:28.480 align:start position:0% many folks like because there's some 01:15:28.480 --> 01:15:29.550 align:start position:0% many folks like because there's some constraints<01:15:28.840> like<01:15:28.960> oh<01:15:29.080> you<01:15:29.199> can't<01:15:29.360> use 01:15:29.550 --> 01:15:29.560 align:start position:0% constraints like oh you can't use 01:15:29.560 --> 01:15:31.629 align:start position:0% constraints like oh you can't use lookarounds<01:15:30.120> you<01:15:30.239> can't<01:15:30.440> like<01:15:30.600> go<01:15:30.800> back<01:15:31.520> or 01:15:31.629 --> 01:15:31.639 align:start position:0% lookarounds you can't like go back or 01:15:31.639 --> 01:15:33.550 align:start position:0% lookarounds you can't like go back or else<01:15:31.800> you<01:15:31.920> break<01:15:32.159> some<01:15:32.320> of<01:15:32.639> like<01:15:33.280> things 01:15:33.550 --> 01:15:33.560 align:start position:0% else you break some of like things 01:15:33.560 --> 01:15:35.990 align:start position:0% else you break some of like things become<01:15:33.719> a<01:15:33.800> lot<01:15:33.920> more<01:15:34.159> expensive<01:15:35.159> um<01:15:35.520> we<01:15:35.679> like 01:15:35.990 --> 01:15:36.000 align:start position:0% become a lot more expensive um we like 01:15:36.000 --> 01:15:37.229 align:start position:0% become a lot more expensive um we like basically<01:15:36.239> train<01:15:36.480> this<01:15:36.600> AI<01:15:36.840> on<01:15:36.920> all<01:15:37.040> of<01:15:37.120> our 01:15:37.229 --> 01:15:37.239 align:start position:0% basically train this AI on all of our 01:15:37.239 --> 01:15:38.790 align:start position:0% basically train this AI on all of our patterns<01:15:37.679> and<01:15:37.800> now<01:15:37.920> the<01:15:38.040> idea<01:15:38.400> that<01:15:38.600> it'll 01:15:38.790 --> 01:15:38.800 align:start position:0% patterns and now the idea that it'll 01:15:38.800 --> 01:15:40.510 align:start position:0% patterns and now the idea that it'll automatically<01:15:39.199> you<01:15:39.360> say<01:15:39.560> oh<01:15:39.760> I<01:15:39.840> want<01:15:40.040> to 01:15:40.510 --> 01:15:40.520 align:start position:0% automatically you say oh I want to 01:15:40.520 --> 01:15:42.110 align:start position:0% automatically you say oh I want to extract<01:15:40.840> the<01:15:40.960> username<01:15:41.360> out<01:15:41.480> of<01:15:41.600> this<01:15:41.760> body 01:15:42.110 --> 01:15:42.120 align:start position:0% extract the username out of this body 01:15:42.120 --> 01:15:43.430 align:start position:0% extract the username out of this body and<01:15:42.360> it'll<01:15:42.560> should<01:15:42.760> automatically<01:15:43.159> generate 01:15:43.430 --> 01:15:43.440 align:start position:0% and it'll should automatically generate 01:15:43.440 --> 01:15:44.470 align:start position:0% and it'll should automatically generate something<01:15:43.639> that<01:15:43.719> will<01:15:43.840> extract<01:15:44.080> the<01:15:44.159> username 01:15:44.470 --> 01:15:44.480 align:start position:0% something that will extract the username 01:15:44.480 --> 01:15:47.149 align:start position:0% something that will extract the username out<01:15:44.560> of<01:15:44.719> that<01:15:44.840> body<01:15:45.679> um<01:15:46.639> so<01:15:46.719> the<01:15:46.800> hope<01:15:46.960> is<01:15:47.080> the 01:15:47.149 --> 01:15:47.159 align:start position:0% out of that body um so the hope is the 01:15:47.159 --> 01:15:48.310 align:start position:0% out of that body um so the hope is the flow<01:15:47.320> of<01:15:47.440> making<01:15:47.600> these<01:15:47.719> proofs<01:15:47.920> is<01:15:48.080> like<01:15:48.199> much 01:15:48.310 --> 01:15:48.320 align:start position:0% flow of making these proofs is like much 01:15:48.320 --> 01:15:50.390 align:start position:0% flow of making these proofs is like much more<01:15:48.520> intuitive<01:15:49.520> and<01:15:49.679> you<01:15:49.840> get<01:15:50.040> kind<01:15:50.120> of<01:15:50.239> a 01:15:50.390 --> 01:15:50.400 align:start position:0% more intuitive and you get kind of a 01:15:50.400 --> 01:15:51.390 align:start position:0% more intuitive and you get kind of a pattern<01:15:50.639> that<01:15:50.760> looks<01:15:50.920> like<01:15:51.040> this<01:15:51.159> it's<01:15:51.320> like 01:15:51.390 --> 01:15:51.400 align:start position:0% pattern that looks like this it's like 01:15:51.400 --> 01:15:52.830 align:start position:0% pattern that looks like this it's like maybe<01:15:51.600> 20<01:15:51.840> 25<01:15:52.159> lines<01:15:52.360> you<01:15:52.440> don't<01:15:52.560> have<01:15:52.639> to<01:15:52.719> read 01:15:52.830 --> 01:15:52.840 align:start position:0% maybe 20 25 lines you don't have to read 01:15:52.840 --> 01:15:54.390 align:start position:0% maybe 20 25 lines you don't have to read it<01:15:53.000> obviously<01:15:53.440> but<01:15:53.560> it's<01:15:53.920> basically<01:15:54.280> like 01:15:54.390 --> 01:15:54.400 align:start position:0% it obviously but it's basically like 01:15:54.400 --> 01:15:55.750 align:start position:0% it obviously but it's basically like some<01:15:54.520> reject<01:15:55.080> of<01:15:55.239> where<01:15:55.320> you're<01:15:55.480> actually 01:15:55.750 --> 01:15:55.760 align:start position:0% some reject of where you're actually 01:15:55.760 --> 01:15:57.830 align:start position:0% some reject of where you're actually parsing<01:15:56.639> um<01:15:56.800> the<01:15:56.920> domains<01:15:57.440> and<01:15:57.679> the 01:15:57.830 --> 01:15:57.840 align:start position:0% parsing um the domains and the 01:15:57.840 --> 01:15:59.470 align:start position:0% parsing um the domains and the parameters<01:15:58.239> of<01:15:58.360> the<01:15:58.440> email<01:15:58.760> itself<01:15:59.280> and<01:15:59.400> this 01:15:59.470 --> 01:15:59.480 align:start position:0% parameters of the email itself and this 01:15:59.480 --> 01:16:00.430 align:start position:0% parameters of the email itself and this will<01:15:59.600> just<01:15:59.719> get<01:15:59.840> applied<01:16:00.120> to<01:16:00.239> all<01:16:00.320> the 01:16:00.430 --> 01:16:00.440 align:start position:0% will just get applied to all the 01:16:00.440 --> 01:16:03.229 align:start position:0% will just get applied to all the relevant<01:16:01.199> emails<01:16:02.199> um<01:16:02.679> and<01:16:02.800> then<01:16:02.960> the<01:16:03.040> cool 01:16:03.229 --> 01:16:03.239 align:start position:0% relevant emails um and then the cool 01:16:03.239 --> 01:16:05.629 align:start position:0% relevant emails um and then the cool thing<01:16:03.520> is<01:16:04.120> imagine<01:16:04.560> you<01:16:04.719> want<01:16:04.920> to<01:16:05.120> like<01:16:05.280> reuse 01:16:05.629 --> 01:16:05.639 align:start position:0% thing is imagine you want to like reuse 01:16:05.639 --> 01:16:06.870 align:start position:0% thing is imagine you want to like reuse some<01:16:05.840> proof<01:16:06.080> that<01:16:06.159> somebody<01:16:06.400> else<01:16:06.520> is<01:16:06.639> using 01:16:06.870 --> 01:16:06.880 align:start position:0% some proof that somebody else is using 01:16:06.880 --> 01:16:08.390 align:start position:0% some proof that somebody else is using you<01:16:07.000> see<01:16:07.199> oh<01:16:07.360> I<01:16:07.440> want<01:16:07.520> to<01:16:07.639> reuse<01:16:07.920> name<01:16:08.080> chep's 01:16:08.390 --> 01:16:08.400 align:start position:0% you see oh I want to reuse name chep's 01:16:08.400 --> 01:16:10.030 align:start position:0% you see oh I want to reuse name chep's domain<01:16:08.719> proof<01:16:09.239> and<01:16:09.360> instead<01:16:09.600> of<01:16:09.679> building<01:16:09.960> a 01:16:10.030 --> 01:16:10.040 align:start position:0% domain proof and instead of building a 01:16:10.040 --> 01:16:11.550 align:start position:0% domain proof and instead of building a Marketplace<01:16:10.480> on<01:16:10.600> top<01:16:10.719> of<01:16:10.840> that<01:16:11.239> I<01:16:11.320> want<01:16:11.440> to 01:16:11.550 --> 01:16:11.560 align:start position:0% Marketplace on top of that I want to 01:16:11.560 --> 01:16:13.070 align:start position:0% Marketplace on top of that I want to unlock<01:16:11.920> another<01:16:12.159> domain<01:16:12.480> the<01:16:12.560> other<01:16:12.760> way<01:16:12.920> or 01:16:13.070 --> 01:16:13.080 align:start position:0% unlock another domain the other way or 01:16:13.080 --> 01:16:14.470 align:start position:0% unlock another domain the other way or something<01:16:13.480> you<01:16:13.560> want<01:16:13.679> to<01:16:13.800> build<01:16:14.040> some<01:16:14.239> other 01:16:14.470 --> 01:16:14.480 align:start position:0% something you want to build some other 01:16:14.480 --> 01:16:16.189 align:start position:0% something you want to build some other composable<01:16:14.960> thing<01:16:15.120> on<01:16:15.280> top<01:16:15.440> of<01:16:15.560> it<01:16:16.000> then<01:16:16.080> you 01:16:16.189 --> 01:16:16.199 align:start position:0% composable thing on top of it then you 01:16:16.199 --> 01:16:17.790 align:start position:0% composable thing on top of it then you want<01:16:16.360> the<01:16:16.520> ability<01:16:16.920> to<01:16:17.080> look<01:16:17.239> at<01:16:17.480> existing 01:16:17.790 --> 01:16:17.800 align:start position:0% want the ability to look at existing 01:16:17.800 --> 01:16:19.709 align:start position:0% want the ability to look at existing proofs<01:16:18.040> that<01:16:18.239> everybody<01:16:18.560> is<01:16:18.960> using<01:16:19.239> making<01:16:19.520> on 01:16:19.709 --> 01:16:19.719 align:start position:0% proofs that everybody is using making on 01:16:19.719 --> 01:16:21.830 align:start position:0% proofs that everybody is using making on chain<01:16:20.360> verify<01:16:20.760> them<01:16:20.960> reuse<01:16:21.320> them<01:16:21.560> and<01:16:21.639> so<01:16:21.760> we 01:16:21.830 --> 01:16:21.840 align:start position:0% chain verify them reuse them and so we 01:16:21.840 --> 01:16:22.990 align:start position:0% chain verify them reuse them and so we have<01:16:22.000> this<01:16:22.120> nice<01:16:22.320> little<01:16:22.480> registry<01:16:22.880> where 01:16:22.990 --> 01:16:23.000 align:start position:0% have this nice little registry where 01:16:23.000 --> 01:16:24.270 align:start position:0% have this nice little registry where people<01:16:23.199> can<01:16:23.360> look<01:16:23.480> at<01:16:23.600> all<01:16:23.719> the<01:16:23.880> existing 01:16:24.270 --> 01:16:24.280 align:start position:0% people can look at all the existing 01:16:24.280 --> 01:16:25.430 align:start position:0% people can look at all the existing proofs 01:16:25.430 --> 01:16:25.440 align:start position:0% proofs 01:16:25.440 --> 01:16:27.430 align:start position:0% proofs um<01:16:25.960> and<01:16:26.199> the<01:16:26.320> really<01:16:26.520> cool<01:16:26.719> thing<01:16:26.920> is<01:16:27.239> there's 01:16:27.430 --> 01:16:27.440 align:start position:0% um and the really cool thing is there's 01:16:27.440 --> 01:16:29.590 align:start position:0% um and the really cool thing is there's sort<01:16:27.600> of<01:16:27.800> this<01:16:28.000> like<01:16:28.440> versel<01:16:28.960> like<01:16:29.199> Vision 01:16:29.590 --> 01:16:29.600 align:start position:0% sort of this like versel like Vision 01:16:29.600 --> 01:16:30.990 align:start position:0% sort of this like versel like Vision where<01:16:29.760> you<01:16:29.920> want<01:16:30.080> to<01:16:30.199> be<01:16:30.320> able<01:16:30.520> to<01:16:30.639> deploy 01:16:30.990 --> 01:16:31.000 align:start position:0% where you want to be able to deploy 01:16:31.000 --> 01:16:32.229 align:start position:0% where you want to be able to deploy things<01:16:31.239> very<01:16:31.400> easily<01:16:31.760> so<01:16:31.880> once<01:16:32.040> you've 01:16:32.229 --> 01:16:32.239 align:start position:0% things very easily so once you've 01:16:32.239 --> 01:16:34.030 align:start position:0% things very easily so once you've defined<01:16:32.600> this<01:16:32.800> pattern<01:16:33.400> we<01:16:33.560> automatically 01:16:34.030 --> 01:16:34.040 align:start position:0% defined this pattern we automatically 01:16:34.040 --> 01:16:35.750 align:start position:0% defined this pattern we automatically deploy<01:16:34.360> this<01:16:34.480> little<01:16:34.600> front<01:16:34.800> end<01:16:35.040> for<01:16:35.280> you 01:16:35.750 --> 01:16:35.760 align:start position:0% deploy this little front end for you 01:16:35.760 --> 01:16:36.830 align:start position:0% deploy this little front end for you where<01:16:35.880> we<01:16:36.000> say<01:16:36.199> look<01:16:36.320> we're<01:16:36.440> automatically 01:16:36.830 --> 01:16:36.840 align:start position:0% where we say look we're automatically 01:16:36.840 --> 01:16:37.790 align:start position:0% where we say look we're automatically going<01:16:36.960> to<01:16:37.040> create<01:16:37.239> this<01:16:37.360> thing<01:16:37.520> where<01:16:37.639> you<01:16:37.679> can 01:16:37.790 --> 01:16:37.800 align:start position:0% going to create this thing where you can 01:16:37.800 --> 01:16:39.430 align:start position:0% going to create this thing where you can sign<01:16:37.960> in<01:16:38.120> with<01:16:38.239> your<01:16:38.360> Google<01:16:38.679> account<01:16:39.239> we'll 01:16:39.430 --> 01:16:39.440 align:start position:0% sign in with your Google account we'll 01:16:39.440 --> 01:16:41.189 align:start position:0% sign in with your Google account we'll filter<01:16:39.920> which<01:16:40.120> emails<01:16:40.520> should<01:16:40.679> be<01:16:40.800> in<01:16:41.000> fact 01:16:41.189 --> 01:16:41.199 align:start position:0% filter which emails should be in fact 01:16:41.199 --> 01:16:42.310 align:start position:0% filter which emails should be in fact parse<01:16:41.520> if<01:16:41.600> you<01:16:41.679> look<01:16:41.760> at<01:16:41.880> the<01:16:41.960> bottom<01:16:42.199> we 01:16:42.310 --> 01:16:42.320 align:start position:0% parse if you look at the bottom we 01:16:42.320 --> 01:16:43.950 align:start position:0% parse if you look at the bottom we filtered<01:16:42.639> their<01:16:42.760> inbox<01:16:43.080> to<01:16:43.239> say<01:16:43.679> these<01:16:43.840> are 01:16:43.950 --> 01:16:43.960 align:start position:0% filtered their inbox to say these are 01:16:43.960 --> 01:16:45.470 align:start position:0% filtered their inbox to say these are the<01:16:44.120> correct<01:16:44.400> emails<01:16:44.760> that<01:16:44.880> will<01:16:45.000> parse<01:16:45.280> for 01:16:45.470 --> 01:16:45.480 align:start position:0% the correct emails that will parse for 01:16:45.480 --> 01:16:47.189 align:start position:0% the correct emails that will parse for this<01:16:45.679> kind<01:16:45.800> of<01:16:46.000> proof<01:16:46.600> and<01:16:46.679> the<01:16:46.800> user<01:16:47.040> can 01:16:47.189 --> 01:16:47.199 align:start position:0% this kind of proof and the user can 01:16:47.199 --> 01:16:50.950 align:start position:0% this kind of proof and the user can automatically<01:16:47.920> verify<01:16:48.480> them<01:16:49.480> and<01:16:49.600> so<01:16:50.600> and<01:16:50.840> you 01:16:50.950 --> 01:16:50.960 align:start position:0% automatically verify them and so and you 01:16:50.960 --> 01:16:52.629 align:start position:0% automatically verify them and so and you know<01:16:51.120> another<01:16:51.480> interesting<01:16:51.960> analogy<01:16:52.400> that<01:16:52.560> I 01:16:52.629 --> 01:16:52.639 align:start position:0% know another interesting analogy that I 01:16:52.639 --> 01:16:54.229 align:start position:0% know another interesting analogy that I think<01:16:52.920> we<01:16:53.040> see<01:16:53.280> in<01:16:53.480> like<01:16:53.600> normal<01:16:53.880> development 01:16:54.229 --> 01:16:54.239 align:start position:0% think we see in like normal development 01:16:54.239 --> 01:16:56.189 align:start position:0% think we see in like normal development space<01:16:54.480> we<01:16:54.600> haven't<01:16:54.719> yet<01:16:55.040> see<01:16:55.199> in<01:16:55.360> in<01:16:55.520> ZK<01:16:55.920> space 01:16:56.189 --> 01:16:56.199 align:start position:0% space we haven't yet see in in ZK space 01:16:56.199 --> 01:16:57.550 align:start position:0% space we haven't yet see in in ZK space is<01:16:56.400> like<01:16:56.719> how<01:16:56.840> do<01:16:56.920> you<01:16:57.040> actually<01:16:57.199> do<01:16:57.320> this<01:16:57.440> kind 01:16:57.550 --> 01:16:57.560 align:start position:0% is like how do you actually do this kind 01:16:57.560 --> 01:17:00.550 align:start position:0% is like how do you actually do this kind of<01:16:57.679> version<01:16:58.040> history<01:16:58.520> because<01:16:59.239> these<01:17:00.120> emails 01:17:00.550 --> 01:17:00.560 align:start position:0% of version history because these emails 01:17:00.560 --> 01:17:02.149 align:start position:0% of version history because these emails change<01:17:00.800> formats<01:17:01.159> all<01:17:01.280> the<01:17:01.440> time<01:17:01.679> or<01:17:01.880> people 01:17:02.149 --> 01:17:02.159 align:start position:0% change formats all the time or people 01:17:02.159 --> 01:17:04.149 align:start position:0% change formats all the time or people want<01:17:02.320> to<01:17:02.480> maybe<01:17:02.800> like<01:17:03.199> Fork<01:17:03.679> the<01:17:03.800> pattern<01:17:04.040> for 01:17:04.149 --> 01:17:04.159 align:start position:0% want to maybe like Fork the pattern for 01:17:04.159 --> 01:17:05.629 align:start position:0% want to maybe like Fork the pattern for Devcon<01:17:04.520> rejection<01:17:04.880> to<01:17:05.000> ship<01:17:05.199> Devcon 01:17:05.629 --> 01:17:05.639 align:start position:0% Devcon rejection to ship Devcon 01:17:05.639 --> 01:17:07.310 align:start position:0% Devcon rejection to ship Devcon acceptance<01:17:06.040> or<01:17:06.199> something<01:17:06.800> and<01:17:06.880> so<01:17:07.000> you<01:17:07.120> want 01:17:07.310 --> 01:17:07.320 align:start position:0% acceptance or something and so you want 01:17:07.320 --> 01:17:08.990 align:start position:0% acceptance or something and so you want like<01:17:07.440> a<01:17:07.600> very<01:17:07.920> like<01:17:08.080> natively<01:17:08.480> integrated 01:17:08.990 --> 01:17:09.000 align:start position:0% like a very like natively integrated 01:17:09.000 --> 01:17:10.629 align:start position:0% like a very like natively integrated GitHub<01:17:09.360> like<01:17:09.520> capability<01:17:09.960> to<01:17:10.080> say<01:17:10.239> oh<01:17:10.400> I<01:17:10.480> like 01:17:10.629 --> 01:17:10.639 align:start position:0% GitHub like capability to say oh I like 01:17:10.639 --> 01:17:11.750 align:start position:0% GitHub like capability to say oh I like this<01:17:10.800> pattern<01:17:11.080> but<01:17:11.159> I<01:17:11.199> want<01:17:11.280> to<01:17:11.360> tweak<01:17:11.600> it<01:17:11.679> a 01:17:11.750 --> 01:17:11.760 align:start position:0% this pattern but I want to tweak it a 01:17:11.760 --> 01:17:12.950 align:start position:0% this pattern but I want to tweak it a bit<01:17:11.880> or<01:17:12.000> I<01:17:12.040> want<01:17:12.159> to<01:17:12.239> use<01:17:12.360> an<01:17:12.480> older<01:17:12.679> version 01:17:12.950 --> 01:17:12.960 align:start position:0% bit or I want to use an older version 01:17:12.960 --> 01:17:14.910 align:start position:0% bit or I want to use an older version for<01:17:13.080> this<01:17:13.199> older<01:17:13.400> email<01:17:13.719> or<01:17:13.880> whatever<01:17:14.719> um<01:17:14.800> and 01:17:14.910 --> 01:17:14.920 align:start position:0% for this older email or whatever um and 01:17:14.920 --> 01:17:16.709 align:start position:0% for this older email or whatever um and so<01:17:15.040> building<01:17:15.400> these<01:17:15.560> kinds<01:17:15.760> of<01:17:16.320> version 01:17:16.709 --> 01:17:16.719 align:start position:0% so building these kinds of version 01:17:16.719 --> 01:17:18.550 align:start position:0% so building these kinds of version Primitives<01:17:17.199> I<01:17:17.280> think<01:17:17.400> is<01:17:17.600> very 01:17:18.550 --> 01:17:18.560 align:start position:0% Primitives I think is very 01:17:18.560 --> 01:17:20.790 align:start position:0% Primitives I think is very powerful<01:17:19.560> um<01:17:20.000> folks<01:17:20.199> have<01:17:20.320> built<01:17:20.520> a<01:17:20.600> lot<01:17:20.679> of 01:17:20.790 --> 01:17:20.800 align:start position:0% powerful um folks have built a lot of 01:17:20.800 --> 01:17:22.950 align:start position:0% powerful um folks have built a lot of cool<01:17:21.040> stuff<01:17:21.600> um<01:17:22.000> someone<01:17:22.320> built<01:17:22.480> a<01:17:22.560> Dropbox 01:17:22.950 --> 01:17:22.960 align:start position:0% cool stuff um someone built a Dropbox 01:17:22.960 --> 01:17:24.510 align:start position:0% cool stuff um someone built a Dropbox verification<01:17:23.719> someone<01:17:24.000> built<01:17:24.239> proof<01:17:24.400> of 01:17:24.510 --> 01:17:24.520 align:start position:0% verification someone built proof of 01:17:24.520 --> 01:17:26.750 align:start position:0% verification someone built proof of flight<01:17:24.920> ticket<01:17:25.320> from<01:17:25.760> one<01:17:26.239> uh<01:17:26.360> and<01:17:26.440> you<01:17:26.560> only 01:17:26.750 --> 01:17:26.760 align:start position:0% flight ticket from one uh and you only 01:17:26.760 --> 01:17:29.030 align:start position:0% flight ticket from one uh and you only reveal<01:17:27.080> F<01:17:27.360> and<01:17:27.520> two<01:17:28.360> um<01:17:28.480> someone<01:17:28.719> built<01:17:28.920> your 01:17:29.030 --> 01:17:29.040 align:start position:0% reveal F and two um someone built your 01:17:29.040 --> 01:17:30.550 align:start position:0% reveal F and two um someone built your part<01:17:29.159> of<01:17:29.199> a<01:17:29.320> slack<01:17:29.600> workspace<01:17:30.320> now<01:17:30.400> you<01:17:30.480> can 01:17:30.550 --> 01:17:30.560 align:start position:0% part of a slack workspace now you can 01:17:30.560 --> 01:17:31.470 align:start position:0% part of a slack workspace now you can start<01:17:30.719> to<01:17:30.800> see<01:17:30.920> how<01:17:31.000> this<01:17:31.120> composability 01:17:31.470 --> 01:17:31.480 align:start position:0% start to see how this composability 01:17:31.480 --> 01:17:33.709 align:start position:0% start to see how this composability really<01:17:31.920> matters<01:17:32.400> like<01:17:32.480> I<01:17:32.560> can<01:17:32.719> prove<01:17:33.120> now<01:17:33.600> that 01:17:33.709 --> 01:17:33.719 align:start position:0% really matters like I can prove now that 01:17:33.719 --> 01:17:35.390 align:start position:0% really matters like I can prove now that I'm<01:17:33.920> part<01:17:34.080> of<01:17:34.159> the<01:17:34.239> company<01:17:34.600> slck<01:17:34.840> workspace 01:17:35.390 --> 01:17:35.400 align:start position:0% I'm part of the company slck workspace 01:17:35.400 --> 01:17:37.270 align:start position:0% I'm part of the company slck workspace and<01:17:35.480> I<01:17:35.600> took<01:17:35.719> a<01:17:35.840> flight<01:17:36.080> to<01:17:36.360> Bangkok<01:17:37.080> and<01:17:37.199> now 01:17:37.270 --> 01:17:37.280 align:start position:0% and I took a flight to Bangkok and now 01:17:37.280 --> 01:17:38.149 align:start position:0% and I took a flight to Bangkok and now I'm<01:17:37.400> going<01:17:37.480> to<01:17:37.560> get<01:17:37.719> automatically 01:17:38.149 --> 01:17:38.159 align:start position:0% I'm going to get automatically 01:17:38.159 --> 01:17:40.709 align:start position:0% I'm going to get automatically reimbursed<01:17:38.639> on<01:17:38.760> chain<01:17:39.719> um<01:17:39.920> and<01:17:40.040> so<01:17:40.480> as<01:17:40.600> you 01:17:40.709 --> 01:17:40.719 align:start position:0% reimbursed on chain um and so as you 01:17:40.719 --> 01:17:42.390 align:start position:0% reimbursed on chain um and so as you start<01:17:41.159> composing<01:17:41.560> these<01:17:41.800> together<01:17:42.040> you<01:17:42.199> get 01:17:42.390 --> 01:17:42.400 align:start position:0% start composing these together you get 01:17:42.400 --> 01:17:44.830 align:start position:0% start composing these together you get very<01:17:42.639> interesting<01:17:43.040> powerful<01:17:43.639> Primitives<01:17:44.639> um 01:17:44.830 --> 01:17:44.840 align:start position:0% very interesting powerful Primitives um 01:17:44.840 --> 01:17:46.149 align:start position:0% very interesting powerful Primitives um you<01:17:44.920> can<01:17:45.080> prove<01:17:45.239> you<01:17:45.360> exported<01:17:45.679> your<01:17:45.760> LinkedIn 01:17:46.149 --> 01:17:46.159 align:start position:0% you can prove you exported your LinkedIn 01:17:46.159 --> 01:17:48.430 align:start position:0% you can prove you exported your LinkedIn data<01:17:46.400> and<01:17:46.480> then<01:17:46.560> you<01:17:46.639> sell<01:17:46.840> that<01:17:46.960> to<01:17:47.040> open<01:17:47.440> AI 01:17:48.430 --> 01:17:48.440 align:start position:0% data and then you sell that to open AI 01:17:48.440 --> 01:17:49.950 align:start position:0% data and then you sell that to open AI um<01:17:48.880> you<01:17:49.000> can<01:17:49.120> prove<01:17:49.280> you<01:17:49.400> exported<01:17:49.719> your<01:17:49.800> open 01:17:49.950 --> 01:17:49.960 align:start position:0% um you can prove you exported your open 01:17:49.960 --> 01:17:51.950 align:start position:0% um you can prove you exported your open AI<01:17:50.239> data<01:17:50.480> and<01:17:50.560> then<01:17:50.679> sell<01:17:50.880> that<01:17:50.960> to 01:17:51.950 --> 01:17:51.960 align:start position:0% AI data and then sell that to 01:17:51.960 --> 01:17:53.950 align:start position:0% AI data and then sell that to anthropic<01:17:52.960> um<01:17:53.120> you<01:17:53.199> can<01:17:53.320> prove<01:17:53.520> you<01:17:53.639> completed 01:17:53.950 --> 01:17:53.960 align:start position:0% anthropic um you can prove you completed 01:17:53.960 --> 01:17:55.430 align:start position:0% anthropic um you can prove you completed some<01:17:54.120> issue<01:17:54.400> on<01:17:54.560> GitHub<01:17:54.920> and<01:17:55.000> automatically 01:17:55.430 --> 01:17:55.440 align:start position:0% some issue on GitHub and automatically 01:17:55.440 --> 01:17:57.350 align:start position:0% some issue on GitHub and automatically get<01:17:55.600> paid<01:17:56.480> um<01:17:56.560> you<01:17:56.639> can<01:17:56.760> prove<01:17:56.960> you<01:17:57.040> ordered 01:17:57.350 --> 01:17:57.360 align:start position:0% get paid um you can prove you ordered 01:17:57.360 --> 01:18:00.149 align:start position:0% get paid um you can prove you ordered padti<01:17:57.719> in<01:17:58.040> Thailand<01:17:59.040> um<01:17:59.560> you<01:17:59.840> basically<01:18:00.080> have 01:18:00.149 --> 01:18:00.159 align:start position:0% padti in Thailand um you basically have 01:18:00.159 --> 01:18:01.350 align:start position:0% padti in Thailand um you basically have a<01:18:00.239> grabber<01:18:00.520> seat<01:18:00.679> that<01:18:00.760> shows<01:18:00.920> your<01:18:01.080> location 01:18:01.350 --> 01:18:01.360 align:start position:0% a grabber seat that shows your location 01:18:01.360 --> 01:18:03.550 align:start position:0% a grabber seat that shows your location is<01:18:01.520> Thailand<01:18:01.840> and<01:18:02.000> Pad<01:18:02.159> Tai<01:18:02.320> was<01:18:02.400> in<01:18:02.480> the<01:18:02.560> order 01:18:03.550 --> 01:18:03.560 align:start position:0% is Thailand and Pad Tai was in the order 01:18:03.560 --> 01:18:04.870 align:start position:0% is Thailand and Pad Tai was in the order um<01:18:03.719> and<01:18:03.840> of<01:18:03.960> course<01:18:04.120> that<01:18:04.280> you<01:18:04.480> maybe<01:18:04.719> got 01:18:04.870 --> 01:18:04.880 align:start position:0% um and of course that you maybe got 01:18:04.880 --> 01:18:06.590 align:start position:0% um and of course that you maybe got rejected<01:18:05.199> or<01:18:05.320> accepted<01:18:05.679> to 01:18:06.590 --> 01:18:06.600 align:start position:0% rejected or accepted to 01:18:06.600 --> 01:18:08.709 align:start position:0% rejected or accepted to Devcon<01:18:07.600> um<01:18:07.840> and<01:18:07.920> now<01:18:08.040> you<01:18:08.120> can<01:18:08.239> see<01:18:08.480> how<01:18:08.600> this 01:18:08.709 --> 01:18:08.719 align:start position:0% Devcon um and now you can see how this 01:18:08.719 --> 01:18:10.110 align:start position:0% Devcon um and now you can see how this SDK<01:18:09.080> makes<01:18:09.199> a<01:18:09.320> lot<01:18:09.440> more<01:18:09.560> sense<01:18:09.880> you<01:18:10.000> just 01:18:10.110 --> 01:18:10.120 align:start position:0% SDK makes a lot more sense you just 01:18:10.120 --> 01:18:11.510 align:start position:0% SDK makes a lot more sense you just choose<01:18:10.360> the<01:18:10.440> one<01:18:10.560> you<01:18:10.639> want<01:18:10.719> to<01:18:10.880> import<01:18:11.239> and<01:18:11.440> we 01:18:11.510 --> 01:18:11.520 align:start position:0% choose the one you want to import and we 01:18:11.520 --> 01:18:13.430 align:start position:0% choose the one you want to import and we can<01:18:11.639> automatically<01:18:12.159> fetch<01:18:12.440> that<01:18:12.560> from<01:18:12.719> the 01:18:13.430 --> 01:18:13.440 align:start position:0% can automatically fetch that from the 01:18:13.440 --> 01:18:17.030 align:start position:0% can automatically fetch that from the registry<01:18:14.600> um<01:18:15.600> yeah<01:18:15.760> so<01:18:15.920> this<01:18:16.080> is<01:18:16.360> this<01:18:16.480> is<01:18:16.719> live 01:18:17.030 --> 01:18:17.040 align:start position:0% registry um yeah so this is this is live 01:18:17.040 --> 01:18:20.189 align:start position:0% registry um yeah so this is this is live folks<01:18:17.280> can<01:18:17.400> try<01:18:17.560> it<01:18:17.679> out<01:18:18.440> um<01:18:19.440> another<01:18:20.000> I<01:18:20.080> think 01:18:20.189 --> 01:18:20.199 align:start position:0% folks can try it out um another I think 01:18:20.199 --> 01:18:21.470 align:start position:0% folks can try it out um another I think underrated<01:18:20.600> piece<01:18:20.760> of<01:18:20.840> infrastructure<01:18:21.320> is 01:18:21.470 --> 01:18:21.480 align:start position:0% underrated piece of infrastructure is 01:18:21.480 --> 01:18:23.390 align:start position:0% underrated piece of infrastructure is like<01:18:21.639> archiving<01:18:22.120> these<01:18:22.320> public<01:18:22.639> keys<01:18:23.199> this<01:18:23.320> is 01:18:23.390 --> 01:18:23.400 align:start position:0% like archiving these public keys this is 01:18:23.400 --> 01:18:24.510 align:start position:0% like archiving these public keys this is the<01:18:23.520> case<01:18:23.679> for<01:18:23.800> Deacon<01:18:24.120> but<01:18:24.199> this<01:18:24.320> also<01:18:24.440> going 01:18:24.510 --> 01:18:24.520 align:start position:0% the case for Deacon but this also going 01:18:24.520 --> 01:18:25.830 align:start position:0% the case for Deacon but this also going to<01:18:24.560> be<01:18:24.800> Cas<01:18:24.960> for<01:18:25.080> all<01:18:25.159> the<01:18:25.239> other<01:18:25.400> public<01:18:25.639> keys 01:18:25.830 --> 01:18:25.840 align:start position:0% to be Cas for all the other public keys 01:18:25.840 --> 01:18:27.390 align:start position:0% to be Cas for all the other public keys on<01:18:25.920> the<01:18:26.000> internet<01:18:26.480> the<01:18:26.600> country<01:18:26.920> public<01:18:27.199> keys 01:18:27.390 --> 01:18:27.400 align:start position:0% on the internet the country public keys 01:18:27.400 --> 01:18:31.149 align:start position:0% on the internet the country public keys for<01:18:27.679> passports<01:18:28.840> the<01:18:29.840> uh<01:18:30.199> ID<01:18:30.520> public<01:18:30.800> keys<01:18:31.000> for 01:18:31.149 --> 01:18:31.159 align:start position:0% for passports the uh ID public keys for 01:18:31.159 --> 01:18:33.189 align:start position:0% for passports the uh ID public keys for ID<01:18:31.440> cards<01:18:32.000> there's<01:18:32.320> not<01:18:32.520> really<01:18:32.760> a<01:18:32.920> clear 01:18:33.189 --> 01:18:33.199 align:start position:0% ID cards there's not really a clear 01:18:33.199 --> 01:18:35.189 align:start position:0% ID cards there's not really a clear Archive<01:18:33.560> of<01:18:33.679> these<01:18:33.840> keys<01:18:34.159> anywhere<01:18:34.960> and<01:18:35.040> so 01:18:35.189 --> 01:18:35.199 align:start position:0% Archive of these keys anywhere and so 01:18:35.199 --> 01:18:36.590 align:start position:0% Archive of these keys anywhere and so our<01:18:35.320> Hope<01:18:35.520> was<01:18:35.679> that<01:18:35.800> we<01:18:35.880> should<01:18:36.080> make<01:18:36.199> it<01:18:36.360> easy 01:18:36.590 --> 01:18:36.600 align:start position:0% our Hope was that we should make it easy 01:18:36.600 --> 01:18:38.990 align:start position:0% our Hope was that we should make it easy for<01:18:36.800> folks<01:18:37.040> to<01:18:37.320> see<01:18:37.560> these<01:18:37.719> old<01:18:37.920> public<01:18:38.239> keys 01:18:38.990 --> 01:18:39.000 align:start position:0% for folks to see these old public keys 01:18:39.000 --> 01:18:40.430 align:start position:0% for folks to see these old public keys and<01:18:39.120> then<01:18:39.360> access<01:18:39.639> them<01:18:39.760> where<01:18:39.880> they<01:18:40.000> want<01:18:40.199> to 01:18:40.430 --> 01:18:40.440 align:start position:0% and then access them where they want to 01:18:40.440 --> 01:18:42.350 align:start position:0% and then access them where they want to and<01:18:40.560> like<01:18:40.679> why<01:18:40.800> is<01:18:40.920> this<01:18:41.080> relevant<01:18:41.960> um<01:18:42.159> so 01:18:42.350 --> 01:18:42.360 align:start position:0% and like why is this relevant um so 01:18:42.360 --> 01:18:43.310 align:start position:0% and like why is this relevant um so here's<01:18:42.560> one<01:18:42.679> example<01:18:42.960> like<01:18:43.080> this<01:18:43.159> is<01:18:43.239> like 01:18:43.310 --> 01:18:43.320 align:start position:0% here's one example like this is like 01:18:43.320 --> 01:18:45.830 align:start position:0% here's one example like this is like Hillary<01:18:43.560> Clinton's<01:18:43.960> email<01:18:44.560> inbox<01:18:45.560> um<01:18:45.679> from 01:18:45.830 --> 01:18:45.840 align:start position:0% Hillary Clinton's email inbox um from 01:18:45.840 --> 01:18:47.870 align:start position:0% Hillary Clinton's email inbox um from 2016<01:18:46.400> we<01:18:46.520> ran<01:18:46.880> like<01:18:47.000> Deon<01:18:47.320> verification<01:18:47.719> over 01:18:47.870 --> 01:18:47.880 align:start position:0% 2016 we ran like Deon verification over 01:18:47.880 --> 01:18:48.910 align:start position:0% 2016 we ran like Deon verification over all<01:18:48.000> of<01:18:48.080> it<01:18:48.199> and<01:18:48.280> these<01:18:48.400> red<01:18:48.520> ones<01:18:48.719> are<01:18:48.840> the 01:18:48.910 --> 01:18:48.920 align:start position:0% all of it and these red ones are the 01:18:48.920 --> 01:18:50.149 align:start position:0% all of it and these red ones are the ones<01:18:49.040> that<01:18:49.120> no<01:18:49.239> longer<01:18:49.480> verify<01:18:49.840> because<01:18:49.920> we<01:18:50.040> no 01:18:50.149 --> 01:18:50.159 align:start position:0% ones that no longer verify because we no 01:18:50.159 --> 01:18:52.270 align:start position:0% ones that no longer verify because we no longer<01:18:50.360> have<01:18:50.520> those<01:18:50.679> deom<01:18:51.080> keys<01:18:51.960> um<01:18:52.080> and<01:18:52.159> this 01:18:52.270 --> 01:18:52.280 align:start position:0% longer have those deom keys um and this 01:18:52.280 --> 01:18:53.470 align:start position:0% longer have those deom keys um and this problem<01:18:52.480> is<01:18:52.560> going<01:18:52.639> to<01:18:52.760> happen<01:18:53.000> more<01:18:53.120> and<01:18:53.280> more 01:18:53.470 --> 01:18:53.480 align:start position:0% problem is going to happen more and more 01:18:53.480 --> 01:18:54.350 align:start position:0% problem is going to happen more and more like<01:18:53.600> as<01:18:53.719> we<01:18:53.840> build<01:18:54.000> the<01:18:54.080> signature 01:18:54.350 --> 01:18:54.360 align:start position:0% like as we build the signature 01:18:54.360 --> 01:18:55.629 align:start position:0% like as we build the signature verification<01:18:54.800> per<01:18:55.040> is<01:18:55.120> we<01:18:55.239> need<01:18:55.320> a<01:18:55.480> place 01:18:55.629 --> 01:18:55.639 align:start position:0% verification per is we need a place 01:18:55.639 --> 01:18:59.110 align:start position:0% verification per is we need a place where<01:18:55.760> we<01:18:55.840> can<01:18:55.920> settle<01:18:56.239> these<01:18:56.440> public<01:18:57.040> Keys<01:18:58.120> um 01:18:59.110 --> 01:18:59.120 align:start position:0% where we can settle these public Keys um 01:18:59.120 --> 01:19:00.750 align:start position:0% where we can settle these public Keys um and<01:18:59.280> for<01:18:59.520> for<01:18:59.679> deim<01:19:00.040> it's<01:19:00.159> very<01:19:00.280> easy<01:19:00.520> you<01:19:00.600> just 01:19:00.750 --> 01:19:00.760 align:start position:0% and for for deim it's very easy you just 01:19:00.760 --> 01:19:03.590 align:start position:0% and for for deim it's very easy you just hit<01:19:00.960> this<01:19:01.239> DNS<01:19:01.960> registry<01:19:02.960> um<01:19:03.120> and<01:19:03.239> you<01:19:03.320> can 01:19:03.590 --> 01:19:03.600 align:start position:0% hit this DNS registry um and you can 01:19:03.600 --> 01:19:05.189 align:start position:0% hit this DNS registry um and you can kind<01:19:03.719> of<01:19:03.800> search<01:19:04.040> on<01:19:04.159> this<01:19:04.280> archive<01:19:04.960> and<01:19:05.080> the 01:19:05.189 --> 01:19:05.199 align:start position:0% kind of search on this archive and the 01:19:05.199 --> 01:19:06.709 align:start position:0% kind of search on this archive and the hope<01:19:05.400> is<01:19:05.560> that<01:19:05.840> you<01:19:05.920> know<01:19:06.120> right<01:19:06.280> now<01:19:06.440> this<01:19:06.520> is 01:19:06.709 --> 01:19:06.719 align:start position:0% hope is that you know right now this is 01:19:06.719 --> 01:19:08.550 align:start position:0% hope is that you know right now this is one<01:19:06.920> server<01:19:07.280> that's<01:19:07.600> doing<01:19:07.880> this<01:19:08.040> archiving 01:19:08.550 --> 01:19:08.560 align:start position:0% one server that's doing this archiving 01:19:08.560 --> 01:19:09.590 align:start position:0% one server that's doing this archiving but<01:19:08.639> you<01:19:08.719> can<01:19:08.880> imagine<01:19:09.120> you<01:19:09.239> can<01:19:09.360> build<01:19:09.520> a 01:19:09.590 --> 01:19:09.600 align:start position:0% but you can imagine you can build a 01:19:09.600 --> 01:19:10.870 align:start position:0% but you can imagine you can build a whole<01:19:09.760> consensus<01:19:10.120> layer<01:19:10.320> on<01:19:10.440> top<01:19:10.560> of<01:19:10.639> this<01:19:10.760> you 01:19:10.870 --> 01:19:10.880 align:start position:0% whole consensus layer on top of this you 01:19:10.880 --> 01:19:12.590 align:start position:0% whole consensus layer on top of this you could<01:19:11.000> have<01:19:11.120> a<01:19:11.239> bunch<01:19:11.400> of<01:19:11.639> own<01:19:12.159> independent 01:19:12.590 --> 01:19:12.600 align:start position:0% could have a bunch of own independent 01:19:12.600 --> 01:19:14.030 align:start position:0% could have a bunch of own independent archiving<01:19:13.040> nodes<01:19:13.520> and<01:19:13.600> when<01:19:13.679> you<01:19:13.800> want<01:19:13.880> to 01:19:14.030 --> 01:19:14.040 align:start position:0% archiving nodes and when you want to 01:19:14.040 --> 01:19:15.870 align:start position:0% archiving nodes and when you want to fetch<01:19:14.239> a<01:19:14.400> value<01:19:14.800> you<01:19:15.080> say<01:19:15.320> do<01:19:15.440> a<01:19:15.520> threshold 01:19:15.870 --> 01:19:15.880 align:start position:0% fetch a value you say do a threshold 01:19:15.880 --> 01:19:17.550 align:start position:0% fetch a value you say do a threshold signature<01:19:16.199> over<01:19:16.440> all<01:19:16.639> those<01:19:16.840> archiving<01:19:17.280> nodes 01:19:17.550 --> 01:19:17.560 align:start position:0% signature over all those archiving nodes 01:19:17.560 --> 01:19:19.229 align:start position:0% signature over all those archiving nodes and<01:19:17.639> you<01:19:17.760> say<01:19:17.960> look<01:19:18.360> yep<01:19:18.600> like<01:19:18.760> 10<01:19:18.920> out<01:19:19.000> of<01:19:19.120> 10 01:19:19.229 --> 01:19:19.239 align:start position:0% and you say look yep like 10 out of 10 01:19:19.239 --> 01:19:20.430 align:start position:0% and you say look yep like 10 out of 10 of<01:19:19.320> the<01:19:19.400> archiving<01:19:19.760> noes<01:19:19.960> said<01:19:20.080> that<01:19:20.199> this<01:19:20.280> was 01:19:20.430 --> 01:19:20.440 align:start position:0% of the archiving noes said that this was 01:19:20.440 --> 01:19:21.950 align:start position:0% of the archiving noes said that this was in<01:19:20.560> fact<01:19:20.679> the<01:19:20.800> public<01:19:21.040> key<01:19:21.199> on<01:19:21.360> that<01:19:21.520> day 01:19:21.950 --> 01:19:21.960 align:start position:0% in fact the public key on that day 01:19:21.960 --> 01:19:23.390 align:start position:0% in fact the public key on that day sounds<01:19:22.239> good<01:19:22.360> to<01:19:22.480> me<01:19:22.679> and<01:19:22.920> and<01:19:23.000> you<01:19:23.120> can<01:19:23.280> kind 01:19:23.390 --> 01:19:23.400 align:start position:0% sounds good to me and and you can kind 01:19:23.400 --> 01:19:25.229 align:start position:0% sounds good to me and and you can kind of<01:19:23.560> almost<01:19:23.840> build<01:19:24.320> a<01:19:24.400> content<01:19:24.719> sens<01:19:24.960> Network 01:19:25.229 --> 01:19:25.239 align:start position:0% of almost build a content sens Network 01:19:25.239 --> 01:19:27.950 align:start position:0% of almost build a content sens Network that<01:19:25.320> is<01:19:25.480> just<01:19:25.719> archiving<01:19:26.360> Keys<01:19:27.360> um<01:19:27.840> and 01:19:27.950 --> 01:19:27.960 align:start position:0% that is just archiving Keys um and 01:19:27.960 --> 01:19:29.189 align:start position:0% that is just archiving Keys um and there's<01:19:28.120> one<01:19:28.280> cool<01:19:28.520> trick<01:19:28.760> specifically<01:19:29.080> with 01:19:29.189 --> 01:19:29.199 align:start position:0% there's one cool trick specifically with 01:19:29.199 --> 01:19:30.629 align:start position:0% there's one cool trick specifically with RSA<01:19:29.520> where<01:19:29.600> you<01:19:29.679> can<01:19:29.760> recover<01:19:30.080> lost<01:19:30.360> public 01:19:30.629 --> 01:19:30.639 align:start position:0% RSA where you can recover lost public 01:19:30.639 --> 01:19:32.310 align:start position:0% RSA where you can recover lost public keys<01:19:30.880> so<01:19:31.000> we<01:19:31.080> were<01:19:31.199> able<01:19:31.360> to<01:19:31.520> like<01:19:31.880> get<01:19:32.080> public 01:19:32.310 --> 01:19:32.320 align:start position:0% keys so we were able to like get public 01:19:32.320 --> 01:19:33.629 align:start position:0% keys so we were able to like get public keys<01:19:32.520> from<01:19:32.679> 10<01:19:32.840> years<01:19:32.960> ago<01:19:33.120> that<01:19:33.239> no<01:19:33.360> longer 01:19:33.629 --> 01:19:33.639 align:start position:0% keys from 10 years ago that no longer 01:19:33.639 --> 01:19:35.510 align:start position:0% keys from 10 years ago that no longer exist<01:19:33.920> and<01:19:34.040> you<01:19:34.120> do<01:19:34.280> this<01:19:34.400> like<01:19:34.520> cool<01:19:34.719> RSA<01:19:35.080> gcg 01:19:35.510 --> 01:19:35.520 align:start position:0% exist and you do this like cool RSA gcg 01:19:35.520 --> 01:19:36.910 align:start position:0% exist and you do this like cool RSA gcg trick<01:19:35.880> that<01:19:35.960> I<01:19:36.080> don't<01:19:36.159> have<01:19:36.280> time<01:19:36.400> to<01:19:36.480> get<01:19:36.600> into 01:19:36.910 --> 01:19:36.920 align:start position:0% trick that I don't have time to get into 01:19:36.920 --> 01:19:38.390 align:start position:0% trick that I don't have time to get into but<01:19:37.040> you<01:19:37.120> can<01:19:37.360> look<01:19:37.520> at<01:19:37.639> this<01:19:37.760> if<01:19:37.840> you<01:19:37.960> want<01:19:38.320> um 01:19:38.390 --> 01:19:38.400 align:start position:0% but you can look at this if you want um 01:19:38.400 --> 01:19:41.510 align:start position:0% but you can look at this if you want um it's<01:19:38.560> pretty<01:19:38.920> nifty<01:19:39.920> um<01:19:40.920> and<01:19:41.000> then<01:19:41.120> users<01:19:41.400> have 01:19:41.510 --> 01:19:41.520 align:start position:0% it's pretty nifty um and then users have 01:19:41.520 --> 01:19:43.350 align:start position:0% it's pretty nifty um and then users have to<01:19:41.639> contribute<01:19:42.320> how<01:19:42.480> they<01:19:42.679> actually<01:19:43.080> like 01:19:43.350 --> 01:19:43.360 align:start position:0% to contribute how they actually like 01:19:43.360 --> 01:19:44.669 align:start position:0% to contribute how they actually like access<01:19:43.639> these<01:19:43.840> keys<01:19:44.040> so<01:19:44.159> for<01:19:44.239> emails<01:19:44.520> you<01:19:44.600> have 01:19:44.669 --> 01:19:44.679 align:start position:0% access these keys so for emails you have 01:19:44.679 --> 01:19:46.750 align:start position:0% access these keys so for emails you have to<01:19:44.800> contribute<01:19:45.440> the<01:19:45.560> URL<01:19:46.159> for<01:19:46.360> passports 01:19:46.750 --> 01:19:46.760 align:start position:0% to contribute the URL for passports 01:19:46.760 --> 01:19:48.510 align:start position:0% to contribute the URL for passports you'd<01:19:46.880> have<01:19:47.000> to<01:19:47.120> contribute<01:19:47.679> the<01:19:47.920> the<01:19:48.080> country 01:19:48.510 --> 01:19:48.520 align:start position:0% you'd have to contribute the the country 01:19:48.520 --> 01:19:52.470 align:start position:0% you'd have to contribute the the country kind<01:19:48.679> of<01:19:49.239> URL<01:19:50.239> um<01:19:50.679> and<01:19:50.800> so<01:19:51.719> it's<01:19:51.880> always<01:19:52.320> there 01:19:52.470 --> 01:19:52.480 align:start position:0% kind of URL um and so it's always there 01:19:52.480 --> 01:19:53.590 align:start position:0% kind of URL um and so it's always there has<01:19:52.560> to<01:19:52.639> be<01:19:52.760> some<01:19:52.920> kind<01:19:53.040> of<01:19:53.120> mechanism<01:19:53.480> to 01:19:53.590 --> 01:19:53.600 align:start position:0% has to be some kind of mechanism to 01:19:53.600 --> 01:19:55.189 align:start position:0% has to be some kind of mechanism to contribute<01:19:53.960> to<01:19:54.080> this<01:19:54.239> kind<01:19:54.320> of<01:19:54.440> AR 01:19:55.189 --> 01:19:55.199 align:start position:0% contribute to this kind of AR 01:19:55.199 --> 01:19:58.350 align:start position:0% contribute to this kind of AR Network<01:19:56.199> um<01:19:56.719> cool<01:19:57.199> and<01:19:57.360> then<01:19:57.880> maybe<01:19:58.199> to 01:19:58.350 --> 01:19:58.360 align:start position:0% Network um cool and then maybe to 01:19:58.360 --> 01:19:59.510 align:start position:0% Network um cool and then maybe to inspire<01:19:58.639> a<01:19:58.719> little<01:19:58.880> more<01:19:59.040> I'll<01:19:59.159> just<01:19:59.280> kind<01:19:59.400> of 01:19:59.510 --> 01:19:59.520 align:start position:0% inspire a little more I'll just kind of 01:19:59.520 --> 01:20:02.830 align:start position:0% inspire a little more I'll just kind of Rapid<01:19:59.840> Fire<01:20:00.040> some<01:20:00.520> applications<01:20:01.679> um<01:20:02.679> one 01:20:02.830 --> 01:20:02.840 align:start position:0% Rapid Fire some applications um one 01:20:02.840 --> 01:20:03.870 align:start position:0% Rapid Fire some applications um one thing<01:20:02.960> folks<01:20:03.159> have<01:20:03.280> really<01:20:03.440> wanted<01:20:03.679> is<01:20:03.800> the 01:20:03.870 --> 01:20:03.880 align:start position:0% thing folks have really wanted is the 01:20:03.880 --> 01:20:05.950 align:start position:0% thing folks have really wanted is the ability<01:20:04.159> to<01:20:04.280> use<01:20:04.440> Google<01:20:04.679> signin<01:20:05.120> directly<01:20:05.800> so 01:20:05.950 --> 01:20:05.960 align:start position:0% ability to use Google signin directly so 01:20:05.960 --> 01:20:07.070 align:start position:0% ability to use Google signin directly so we<01:20:06.080> kind<01:20:06.159> of<01:20:06.239> built<01:20:06.400> a<01:20:06.520> school<01:20:06.719> primitive 01:20:07.070 --> 01:20:07.080 align:start position:0% we kind of built a school primitive 01:20:07.080 --> 01:20:08.149 align:start position:0% we kind of built a school primitive where<01:20:07.159> you<01:20:07.239> can<01:20:07.360> enter<01:20:07.560> a<01:20:07.639> command<01:20:07.960> and<01:20:08.040> then 01:20:08.149 --> 01:20:08.159 align:start position:0% where you can enter a command and then 01:20:08.159 --> 01:20:09.669 align:start position:0% where you can enter a command and then sign<01:20:08.320> in<01:20:08.440> with<01:20:08.560> Google<01:20:08.840> and<01:20:09.120> the<01:20:09.239> sign<01:20:09.440> in<01:20:09.560> with 01:20:09.669 --> 01:20:09.679 align:start position:0% sign in with Google and the sign in with 01:20:09.679 --> 01:20:10.990 align:start position:0% sign in with Google and the sign in with Google<01:20:09.880> will<01:20:10.040> sign<01:20:10.320> that<01:20:10.440> command<01:20:10.800> and<01:20:10.880> then 01:20:10.990 --> 01:20:11.000 align:start position:0% Google will sign that command and then 01:20:11.000 --> 01:20:14.550 align:start position:0% Google will sign that command and then prove<01:20:11.159> it<01:20:11.239> on<01:20:11.480> chain<01:20:12.480> um<01:20:12.840> you<01:20:12.960> can<01:20:13.239> do<01:20:14.239> uh<01:20:14.440> kind 01:20:14.550 --> 01:20:14.560 align:start position:0% prove it on chain um you can do uh kind 01:20:14.560 --> 01:20:16.270 align:start position:0% prove it on chain um you can do uh kind of<01:20:14.920> credible<01:20:15.280> whistleblowing<01:20:15.840> or<01:20:15.960> domain 01:20:16.270 --> 01:20:16.280 align:start position:0% of credible whistleblowing or domain 01:20:16.280 --> 01:20:17.629 align:start position:0% of credible whistleblowing or domain proof<01:20:16.600> so<01:20:16.800> for<01:20:16.960> instance<01:20:17.159> you<01:20:17.239> can<01:20:17.360> prove<01:20:17.560> you 01:20:17.629 --> 01:20:17.639 align:start position:0% proof so for instance you can prove you 01:20:17.639 --> 01:20:19.990 align:start position:0% proof so for instance you can prove you work<01:20:17.800> at<01:20:17.880> a<01:20:18.000> company<01:20:18.840> and<01:20:19.040> then<01:20:19.719> uh<01:20:19.880> the 01:20:19.990 --> 01:20:20.000 align:start position:0% work at a company and then uh the 01:20:20.000 --> 01:20:21.270 align:start position:0% work at a company and then uh the question<01:20:20.199> is<01:20:20.320> how<01:20:20.400> do<01:20:20.480> you<01:20:20.560> do<01:20:20.719> moderation<01:20:21.120> on 01:20:21.270 --> 01:20:21.280 align:start position:0% question is how do you do moderation on 01:20:21.280 --> 01:20:23.110 align:start position:0% question is how do you do moderation on Anonymous<01:20:21.719> message<01:20:21.960> boards<01:20:22.760> um<01:20:22.840> so<01:20:23.000> for 01:20:23.110 --> 01:20:23.120 align:start position:0% Anonymous message boards um so for 01:20:23.120 --> 01:20:24.110 align:start position:0% Anonymous message boards um so for instance<01:20:23.360> maybe<01:20:23.520> you<01:20:23.600> want<01:20:23.719> to<01:20:23.840> prove<01:20:24.040> you 01:20:24.110 --> 01:20:24.120 align:start position:0% instance maybe you want to prove you 01:20:24.120 --> 01:20:25.310 align:start position:0% instance maybe you want to prove you worked<01:20:24.320> at<01:20:24.440> Boeing 01:20:25.310 --> 01:20:25.320 align:start position:0% worked at Boeing 01:20:25.320 --> 01:20:26.270 align:start position:0% worked at Boeing but<01:20:25.400> you<01:20:25.480> don't<01:20:25.560> want<01:20:25.639> to<01:20:25.679> Ral<01:20:25.920> who<01:20:26.040> you<01:20:26.120> are 01:20:26.270 --> 01:20:26.280 align:start position:0% but you don't want to Ral who you are 01:20:26.280 --> 01:20:27.350 align:start position:0% but you don't want to Ral who you are but<01:20:26.360> you<01:20:26.440> want<01:20:26.520> to<01:20:26.600> say<01:20:26.760> look<01:20:26.880> I<01:20:26.960> forgot<01:20:27.159> to<01:20:27.239> put 01:20:27.350 --> 01:20:27.360 align:start position:0% but you want to say look I forgot to put 01:20:27.360 --> 01:20:28.790 align:start position:0% but you want to say look I forgot to put screws<01:20:27.639> on<01:20:27.760> that<01:20:27.920> plane<01:20:28.120> maybe<01:20:28.320> don't<01:20:28.440> fly<01:20:28.639> in 01:20:28.790 --> 01:20:28.800 align:start position:0% screws on that plane maybe don't fly in 01:20:28.800 --> 01:20:31.430 align:start position:0% screws on that plane maybe don't fly in that<01:20:28.960> one<01:20:29.840> um<01:20:30.520> well<01:20:30.880> you<01:20:30.960> know<01:20:31.120> the<01:20:31.199> best<01:20:31.360> way 01:20:31.430 --> 01:20:31.440 align:start position:0% that one um well you know the best way 01:20:31.440 --> 01:20:33.870 align:start position:0% that one um well you know the best way to<01:20:31.600> do<01:20:31.800> this<01:20:32.120> is<01:20:32.679> you<01:20:32.800> prove<01:20:33.000> your<01:20:33.280> an<01:20:33.400> employee 01:20:33.870 --> 01:20:33.880 align:start position:0% to do this is you prove your an employee 01:20:33.880 --> 01:20:36.110 align:start position:0% to do this is you prove your an employee there<01:20:34.360> and<01:20:34.560> then<01:20:35.120> we<01:20:35.320> do<01:20:35.520> moderation<01:20:36.000> with 01:20:36.110 --> 01:20:36.120 align:start position:0% there and then we do moderation with 01:20:36.120 --> 01:20:38.110 align:start position:0% there and then we do moderation with tees<01:20:36.920> um<01:20:37.040> with<01:20:37.159> this<01:20:37.280> kind<01:20:37.400> of<01:20:37.480> teleport<01:20:37.840> style 01:20:38.110 --> 01:20:38.120 align:start position:0% tees um with this kind of teleport style 01:20:38.120 --> 01:20:41.149 align:start position:0% tees um with this kind of teleport style thing<01:20:38.320> which<01:20:38.440> is<01:20:38.639> which<01:20:38.760> is<01:20:38.920> quite<01:20:39.239> cool<01:20:40.239> um 01:20:41.149 --> 01:20:41.159 align:start position:0% thing which is which is quite cool um 01:20:41.159 --> 01:20:43.830 align:start position:0% thing which is which is quite cool um you<01:20:41.280> can<01:20:41.400> have<01:20:41.480> email<01:20:41.719> trigger<01:20:42.400> transactions 01:20:43.830 --> 01:20:43.840 align:start position:0% you can have email trigger transactions 01:20:43.840 --> 01:20:45.709 align:start position:0% you can have email trigger transactions um<01:20:44.840> it<01:20:44.960> kind<01:20:45.040> of<01:20:45.159> looks<01:20:45.320> like<01:20:45.400> you'll<01:20:45.560> get<01:20:45.639> an 01:20:45.709 --> 01:20:45.719 align:start position:0% um it kind of looks like you'll get an 01:20:45.719 --> 01:20:46.830 align:start position:0% um it kind of looks like you'll get an email<01:20:45.920> like<01:20:46.040> this<01:20:46.120> or<01:20:46.199> you'll<01:20:46.360> do<01:20:46.440> a<01:20:46.520> sign<01:20:46.679> in 01:20:46.830 --> 01:20:46.840 align:start position:0% email like this or you'll do a sign in 01:20:46.840 --> 01:20:48.030 align:start position:0% email like this or you'll do a sign in and<01:20:46.920> you<01:20:47.000> can<01:20:47.120> approve<01:20:47.360> a<01:20:47.480> transaction<01:20:47.880> on 01:20:48.030 --> 01:20:48.040 align:start position:0% and you can approve a transaction on 01:20:48.040 --> 01:20:50.070 align:start position:0% and you can approve a transaction on chain<01:20:49.040> um<01:20:49.159> it's<01:20:49.320> very<01:20:49.440> easy<01:20:49.639> to<01:20:49.719> build<01:20:49.920> this 01:20:50.070 --> 01:20:50.080 align:start position:0% chain um it's very easy to build this 01:20:50.080 --> 01:20:52.990 align:start position:0% chain um it's very easy to build this kind<01:20:50.199> of<01:20:50.400> thing<01:20:51.000> and<01:20:51.440> uh<01:20:51.920> yeah<01:20:52.239> I'm<01:20:52.400> excited<01:20:52.760> to 01:20:52.990 --> 01:20:53.000 align:start position:0% kind of thing and uh yeah I'm excited to 01:20:53.000 --> 01:20:55.810 align:start position:0% kind of thing and uh yeah I'm excited to to<01:20:53.120> jam<01:20:53.360> more<01:20:53.480> and<01:20:53.560> I'll<01:20:53.679> take<01:20:53.800> any<01:20:54.000> questions 01:20:55.810 --> 01:20:55.820 align:start position:0% to jam more and I'll take any questions 01:20:55.820 --> 01:21:04.030 align:start position:0% to jam more and I'll take any questions [Applause] 01:21:04.030 --> 01:21:04.040 align:start position:0% 01:21:04.040 --> 01:21:06.830 align:start position:0% it's 01:21:06.830 --> 01:21:06.840 align:start position:0% 01:21:06.840 --> 01:21:14.950 align:start position:0% fine<01:21:07.840> um<01:21:08.040> any 01:21:14.950 --> 01:21:14.960 align:start position:0% 01:21:14.960 --> 01:21:19.669 align:start position:0% question<01:21:15.960> okay<01:21:16.120> I<01:21:16.239> have<01:21:16.440> questions<01:21:17.000> yeah<01:21:17.440> uh 01:21:19.669 --> 01:21:19.679 align:start position:0% question okay I have questions yeah uh 01:21:19.679 --> 01:21:21.950 align:start position:0% question okay I have questions yeah uh so<01:21:20.679> so<01:21:20.960> you<01:21:21.239> you<01:21:21.320> were<01:21:21.480> talking<01:21:21.679> about<01:21:21.880> the 01:21:21.950 --> 01:21:21.960 align:start position:0% so so you you were talking about the 01:21:21.960 --> 01:21:23.550 align:start position:0% so so you you were talking about the idea<01:21:22.199> of<01:21:22.320> having<01:21:22.600> kind<01:21:22.719> of<01:21:22.840> like<01:21:22.960> a<01:21:23.040> consensus 01:21:23.550 --> 01:21:23.560 align:start position:0% idea of having kind of like a consensus 01:21:23.560 --> 01:21:26.669 align:start position:0% idea of having kind of like a consensus Network<01:21:23.880> to<01:21:24.000> save<01:21:24.280> public<01:21:24.679> key<01:21:25.280> um<01:21:26.239> from<01:21:26.440> your 01:21:26.669 --> 01:21:26.679 align:start position:0% Network to save public key um from your 01:21:26.679 --> 01:21:28.750 align:start position:0% Network to save public key um from your perspective<01:21:27.159> like<01:21:27.320> what's<01:21:27.600> the<01:21:27.800> actual<01:21:28.520> like 01:21:28.750 --> 01:21:28.760 align:start position:0% perspective like what's the actual like 01:21:28.760 --> 01:21:30.350 align:start position:0% perspective like what's the actual like what<01:21:28.920> what<01:21:29.040> do<01:21:29.159> you<01:21:29.320> think<01:21:29.560> personally<01:21:29.960> is<01:21:30.120> the 01:21:30.350 --> 01:21:30.360 align:start position:0% what what do you think personally is the 01:21:30.360 --> 01:21:31.990 align:start position:0% what what do you think personally is the like<01:21:30.480> the<01:21:30.600> scalable<01:21:31.080> way<01:21:31.199> to<01:21:31.360> just<01:21:31.560> like 01:21:31.990 --> 01:21:32.000 align:start position:0% like the scalable way to just like 01:21:32.000 --> 01:21:34.470 align:start position:0% like the scalable way to just like Google<01:21:32.280> search<01:21:33.239> Style<01:21:33.679> just<01:21:33.880> like<01:21:34.040> save<01:21:34.360> the 01:21:34.470 --> 01:21:34.480 align:start position:0% Google search Style just like save the 01:21:34.480 --> 01:21:36.709 align:start position:0% Google search Style just like save the whole<01:21:34.679> internet<01:21:35.639> like<01:21:35.840> public<01:21:36.199> key<01:21:36.440> from<01:21:36.600> a 01:21:36.709 --> 01:21:36.719 align:start position:0% whole internet like public key from a 01:21:36.719 --> 01:21:38.870 align:start position:0% whole internet like public key from a public<01:21:36.960> key<01:21:37.199> perspective<01:21:38.159> whether<01:21:38.360> it's<01:21:38.600> like 01:21:38.870 --> 01:21:38.880 align:start position:0% public key perspective whether it's like 01:21:38.880 --> 01:21:41.189 align:start position:0% public key perspective whether it's like htps<01:21:39.440> certificates<01:21:40.320> domain<01:21:40.719> name<01:21:40.960> public 01:21:41.189 --> 01:21:41.199 align:start position:0% htps certificates domain name public 01:21:41.199 --> 01:21:42.709 align:start position:0% htps certificates domain name public Keys<01:21:41.520> Etc<01:21:41.960> just<01:21:42.120> everything<01:21:42.360> that's<01:21:42.520> being 01:21:42.709 --> 01:21:42.719 align:start position:0% Keys Etc just everything that's being 01:21:42.719 --> 01:21:44.510 align:start position:0% Keys Etc just everything that's being used<01:21:43.480> yeah<01:21:43.600> it<01:21:43.679> would<01:21:43.800> be<01:21:43.960> really<01:21:44.120> nice<01:21:44.320> if<01:21:44.400> you 01:21:44.510 --> 01:21:44.520 align:start position:0% used yeah it would be really nice if you 01:21:44.520 --> 01:21:46.430 align:start position:0% used yeah it would be really nice if you had<01:21:44.719> signatur<01:21:45.199> so<01:21:45.400> like<01:21:45.600> if<01:21:45.800> these<01:21:46.000> countries 01:21:46.430 --> 01:21:46.440 align:start position:0% had signatur so like if these countries 01:21:46.440 --> 01:21:49.310 align:start position:0% had signatur so like if these countries added<01:21:46.760> sxg<01:21:47.239> or<01:21:47.440> RFC<01:21:47.800> 9421<01:21:48.560> to<01:21:48.679> their<01:21:48.880> web<01:21:49.040> pages 01:21:49.310 --> 01:21:49.320 align:start position:0% added sxg or RFC 9421 to their web pages 01:21:49.320 --> 01:21:50.550 align:start position:0% added sxg or RFC 9421 to their web pages you<01:21:49.400> would<01:21:49.560> have<01:21:49.719> direct<01:21:49.960> signatures<01:21:50.360> that 01:21:50.550 --> 01:21:50.560 align:start position:0% you would have direct signatures that 01:21:50.560 --> 01:21:51.870 align:start position:0% you would have direct signatures that then<01:21:50.639> you<01:21:50.760> could<01:21:51.159> save<01:21:51.400> and<01:21:51.480> you<01:21:51.560> don't<01:21:51.679> need<01:21:51.800> a 01:21:51.870 --> 01:21:51.880 align:start position:0% then you could save and you don't need a 01:21:51.880 --> 01:21:53.030 align:start position:0% then you could save and you don't need a Network<01:21:52.159> anymore<01:21:52.360> you<01:21:52.480> need<01:21:52.600> one<01:21:52.719> person<01:21:52.920> to 01:21:53.030 --> 01:21:53.040 align:start position:0% Network anymore you need one person to 01:21:53.040 --> 01:21:53.950 align:start position:0% Network anymore you need one person to save<01:21:53.159> the<01:21:53.239> signature<01:21:53.560> and<01:21:53.679> that's<01:21:53.800> good 01:21:53.950 --> 01:21:53.960 align:start position:0% save the signature and that's good 01:21:53.960 --> 01:21:56.750 align:start position:0% save the signature and that's good enough<01:21:55.000> um<01:21:55.520> unfortunately<01:21:56.199> like<01:21:56.480> many<01:21:56.639> of 01:21:56.750 --> 01:21:56.760 align:start position:0% enough um unfortunately like many of 01:21:56.760 --> 01:21:58.030 align:start position:0% enough um unfortunately like many of these<01:21:56.880> keys<01:21:57.120> are<01:21:57.239> distributed<01:21:57.679> across 01:21:58.030 --> 01:21:58.040 align:start position:0% these keys are distributed across 01:21:58.040 --> 01:21:59.470 align:start position:0% these keys are distributed across various<01:21:58.280> internet<01:21:58.560> infrastructure<01:21:59.199> like 01:21:59.470 --> 01:21:59.480 align:start position:0% various internet infrastructure like 01:21:59.480 --> 01:22:00.590 align:start position:0% various internet infrastructure like certificate<01:21:59.920> authorities<01:22:00.280> that<01:22:00.360> aren't 01:22:00.590 --> 01:22:00.600 align:start position:0% certificate authorities that aren't 01:22:00.600 --> 01:22:02.229 align:start position:0% certificate authorities that aren't really<01:22:00.760> on<01:22:00.880> the<01:22:01.000> Internet<01:22:01.239> or<01:22:01.360> on<01:22:01.440> a<01:22:01.560> website 01:22:02.229 --> 01:22:02.239 align:start position:0% really on the Internet or on a website 01:22:02.239 --> 01:22:04.470 align:start position:0% really on the Internet or on a website or<01:22:02.600> on<01:22:02.840> like<01:22:03.000> DNS<01:22:03.520> without<01:22:03.719> DNS<01:22:04.080> sex<01:22:04.360> they 01:22:04.470 --> 01:22:04.480 align:start position:0% or on like DNS without DNS sex they 01:22:04.480 --> 01:22:06.750 align:start position:0% or on like DNS without DNS sex they don't<01:22:04.600> have<01:22:04.719> signatures<01:22:05.560> and<01:22:05.639> so<01:22:05.840> the<01:22:06.040> classic 01:22:06.750 --> 01:22:06.760 align:start position:0% don't have signatures and so the classic 01:22:06.760 --> 01:22:08.110 align:start position:0% don't have signatures and so the classic method<01:22:07.000> of<01:22:07.159> like<01:22:07.360> yeah<01:22:07.480> ideally<01:22:07.760> we<01:22:07.880> just<01:22:08.000> use 01:22:08.110 --> 01:22:08.120 align:start position:0% method of like yeah ideally we just use 01:22:08.120 --> 01:22:09.629 align:start position:0% method of like yeah ideally we just use a<01:22:08.239> Wayback<01:22:08.520> machine<01:22:08.760> toiz<01:22:09.120> archiving<01:22:09.520> but 01:22:09.629 --> 01:22:09.639 align:start position:0% a Wayback machine toiz archiving but 01:22:09.639 --> 01:22:12.189 align:start position:0% a Wayback machine toiz archiving but much<01:22:09.760> of<01:22:09.880> the<01:22:10.000> stuff<01:22:10.199> is<01:22:10.360> not<01:22:10.679> on<01:22:10.920> like<01:22:11.040> a<01:22:11.520> hdps 01:22:12.189 --> 01:22:12.199 align:start position:0% much of the stuff is not on like a hdps 01:22:12.199 --> 01:22:14.110 align:start position:0% much of the stuff is not on like a hdps web<01:22:12.440> page<01:22:13.159> it's<01:22:13.280> on<01:22:13.400> some<01:22:13.520> other<01:22:13.719> public<01:22:13.960> key 01:22:14.110 --> 01:22:14.120 align:start position:0% web page it's on some other public key 01:22:14.120 --> 01:22:15.550 align:start position:0% web page it's on some other public key infrastructure<01:22:14.600> that's<01:22:14.760> not<01:22:15.000> directly<01:22:15.320> tied 01:22:15.550 --> 01:22:15.560 align:start position:0% infrastructure that's not directly tied 01:22:15.560 --> 01:22:17.390 align:start position:0% infrastructure that's not directly tied to<01:22:15.679> the<01:22:15.760> internet<01:22:16.000> in<01:22:16.120> some<01:22:16.280> easy<01:22:16.560> way<01:22:16.800> and<01:22:16.920> so 01:22:17.390 --> 01:22:17.400 align:start position:0% to the internet in some easy way and so 01:22:17.400 --> 01:22:18.629 align:start position:0% to the internet in some easy way and so that's<01:22:17.600> why<01:22:17.719> I<01:22:17.800> think<01:22:17.960> we<01:22:18.080> want<01:22:18.280> this<01:22:18.440> like 01:22:18.629 --> 01:22:18.639 align:start position:0% that's why I think we want this like 01:22:18.639 --> 01:22:20.750 align:start position:0% that's why I think we want this like other<01:22:18.920> Paradigm<01:22:19.280> of<01:22:19.440> archiving<01:22:20.239> um<01:22:20.560> but<01:22:20.639> yeah 01:22:20.750 --> 01:22:20.760 align:start position:0% other Paradigm of archiving um but yeah 01:22:20.760 --> 01:22:22.229 align:start position:0% other Paradigm of archiving um but yeah I<01:22:20.840> wish<01:22:21.000> way<01:22:21.159> back<01:22:21.280> machine<01:22:21.560> just<01:22:21.719> added<01:22:22.080> the 01:22:22.229 --> 01:22:22.239 align:start position:0% I wish way back machine just added the 01:22:22.239 --> 01:22:38.950 align:start position:0% I wish way back machine just added the ability<01:22:22.520> to<01:22:22.679> do<01:22:23.040> this<01:22:24.040> um 01:22:38.950 --> 01:22:38.960 align:start position:0% 01:22:38.960 --> 01:22:41.070 align:start position:0% yeah<01:22:39.960> yeah<01:22:40.080> it's<01:22:40.199> a<01:22:40.320> good<01:22:40.520> question<01:22:40.840> like<01:22:40.960> we 01:22:41.070 --> 01:22:41.080 align:start position:0% yeah yeah it's a good question like we 01:22:41.080 --> 01:22:42.790 align:start position:0% yeah yeah it's a good question like we are<01:22:41.639> like<01:22:41.960> how<01:22:42.080> do<01:22:42.159> we<01:22:42.280> think<01:22:42.400> about<01:22:42.520> the<01:22:42.639> risk 01:22:42.790 --> 01:22:42.800 align:start position:0% are like how do we think about the risk 01:22:42.800 --> 01:22:44.950 align:start position:0% are like how do we think about the risk of<01:22:42.920> bootstrapping<01:22:43.520> this<01:22:43.679> on<01:22:43.920> top<01:22:44.080> of<01:22:44.280> the<01:22:44.400> deom 01:22:44.950 --> 01:22:44.960 align:start position:0% of bootstrapping this on top of the deom 01:22:44.960 --> 01:22:46.470 align:start position:0% of bootstrapping this on top of the deom standard<01:22:45.360> which<01:22:45.520> may<01:22:45.679> not<01:22:45.920> have<01:22:46.120> been 01:22:46.470 --> 01:22:46.480 align:start position:0% standard which may not have been 01:22:46.480 --> 01:22:48.709 align:start position:0% standard which may not have been engineered<01:22:47.000> to<01:22:47.159> do<01:22:47.480> like<01:22:48.120> all<01:22:48.280> the<01:22:48.400> security 01:22:48.709 --> 01:22:48.719 align:start position:0% engineered to do like all the security 01:22:48.719 --> 01:22:50.830 align:start position:0% engineered to do like all the security things<01:22:48.880> we<01:22:49.000> want<01:22:49.120> it<01:22:49.199> to<01:22:49.360> do<01:22:50.199> um<01:22:50.320> and<01:22:50.440> maybe<01:22:50.679> one 01:22:50.830 --> 01:22:50.840 align:start position:0% things we want it to do um and maybe one 01:22:50.840 --> 01:22:52.030 align:start position:0% things we want it to do um and maybe one thing<01:22:50.960> I<01:22:51.040> would<01:22:51.199> say<01:22:51.320> is<01:22:51.440> that<01:22:51.639> this<01:22:51.719> is<01:22:51.880> sort 01:22:52.030 --> 01:22:52.040 align:start position:0% thing I would say is that this is sort 01:22:52.040 --> 01:22:54.629 align:start position:0% thing I would say is that this is sort of<01:22:52.280> like<01:22:52.679> an<01:22:52.880> intermediate<01:22:53.480> transition<01:22:54.520> like 01:22:54.629 --> 01:22:54.639 align:start position:0% of like an intermediate transition like 01:22:54.639 --> 01:22:56.030 align:start position:0% of like an intermediate transition like it's<01:22:54.800> kind<01:22:54.920> of<01:22:55.120> if<01:22:55.199> we<01:22:55.320> want<01:22:55.480> to<01:22:55.600> get<01:22:55.679> signed 01:22:56.030 --> 01:22:56.040 align:start position:0% it's kind of if we want to get signed 01:22:56.040 --> 01:22:57.830 align:start position:0% it's kind of if we want to get signed data<01:22:56.280> everywhere<01:22:56.600> and<01:22:56.719> if<01:22:56.800> we<01:22:56.960> want<01:22:57.080> to<01:22:57.320> get 01:22:57.830 --> 01:22:57.840 align:start position:0% data everywhere and if we want to get 01:22:57.840 --> 01:23:00.229 align:start position:0% data everywhere and if we want to get really<01:22:58.360> like<01:22:58.840> all<01:22:59.040> those<01:22:59.440> private<01:22:59.719> keys<01:22:59.960> to<01:23:00.080> be 01:23:00.229 --> 01:23:00.239 align:start position:0% really like all those private keys to be 01:23:00.239 --> 01:23:02.629 align:start position:0% really like all those private keys to be in<01:23:00.360> like<01:23:00.480> super<01:23:00.800> security<01:23:01.239> EES<01:23:01.639> or<01:23:01.800> whatever 01:23:02.629 --> 01:23:02.639 align:start position:0% in like super security EES or whatever 01:23:02.639 --> 01:23:03.950 align:start position:0% in like super security EES or whatever uh<01:23:02.760> down<01:23:02.920> the<01:23:03.040> line<01:23:03.239> we<01:23:03.360> have<01:23:03.440> to<01:23:03.600> prove<01:23:03.800> to 01:23:03.950 --> 01:23:03.960 align:start position:0% uh down the line we have to prove to 01:23:03.960 --> 01:23:05.350 align:start position:0% uh down the line we have to prove to people<01:23:04.199> hey<01:23:04.360> you<01:23:04.440> can<01:23:04.560> do<01:23:04.760> interesting<01:23:05.120> stuff 01:23:05.350 --> 01:23:05.360 align:start position:0% people hey you can do interesting stuff 01:23:05.360 --> 01:23:07.229 align:start position:0% people hey you can do interesting stuff today<01:23:06.159> and<01:23:06.320> I<01:23:06.400> think<01:23:06.600> that<01:23:06.719> a<01:23:06.840> lot<01:23:06.960> of<01:23:07.080> that 01:23:07.229 --> 01:23:07.239 align:start position:0% today and I think that a lot of that 01:23:07.239 --> 01:23:08.870 align:start position:0% today and I think that a lot of that comes<01:23:07.480> from<01:23:07.719> like<01:23:07.960> look<01:23:08.239> like<01:23:08.520> you<01:23:08.639> can<01:23:08.760> do 01:23:08.870 --> 01:23:08.880 align:start position:0% comes from like look like you can do 01:23:08.880 --> 01:23:10.149 align:start position:0% comes from like look like you can do these<01:23:09.040> interesting<01:23:09.320> composable<01:23:09.760> proofs<01:23:10.040> oh 01:23:10.149 --> 01:23:10.159 align:start position:0% these interesting composable proofs oh 01:23:10.159 --> 01:23:11.830 align:start position:0% these interesting composable proofs oh you<01:23:10.239> can<01:23:10.360> do<01:23:10.560> account<01:23:10.800> recovery<01:23:11.520> and<01:23:11.679> like 01:23:11.830 --> 01:23:11.840 align:start position:0% you can do account recovery and like 01:23:11.840 --> 01:23:13.430 align:start position:0% you can do account recovery and like yeah<01:23:11.960> the<01:23:12.120> security<01:23:12.600> is<01:23:12.800> like<01:23:13.120> the<01:23:13.199> same 01:23:13.430 --> 01:23:13.440 align:start position:0% yeah the security is like the same 01:23:13.440 --> 01:23:14.870 align:start position:0% yeah the security is like the same security<01:23:13.800> as<01:23:13.960> the<01:23:14.080> ability<01:23:14.360> for<01:23:14.480> you<01:23:14.560> to<01:23:14.679> send 01:23:14.870 --> 01:23:14.880 align:start position:0% security as the ability for you to send 01:23:14.880 --> 01:23:16.830 align:start position:0% security as the ability for you to send from<01:23:15.040> another<01:23:15.280> Gmail<01:23:15.679> account<01:23:16.480> um<01:23:16.639> like<01:23:16.719> you 01:23:16.830 --> 01:23:16.840 align:start position:0% from another Gmail account um like you 01:23:16.840 --> 01:23:18.070 align:start position:0% from another Gmail account um like you know<01:23:17.199> if<01:23:17.280> you<01:23:17.360> can<01:23:17.480> do<01:23:17.600> that<01:23:17.679> you<01:23:17.760> can<01:23:17.880> break 01:23:18.070 --> 01:23:18.080 align:start position:0% know if you can do that you can break 01:23:18.080 --> 01:23:19.629 align:start position:0% know if you can do that you can break the<01:23:18.159> system<01:23:18.560> but<01:23:18.679> the<01:23:18.760> hope<01:23:18.960> is<01:23:19.120> that<01:23:19.320> like 01:23:19.629 --> 01:23:19.639 align:start position:0% the system but the hope is that like 01:23:19.639 --> 01:23:21.030 align:start position:0% the system but the hope is that like Gmail<01:23:19.960> Outlook<01:23:20.239> Etc<01:23:20.520> have<01:23:20.600> engineered<01:23:20.920> their 01:23:21.030 --> 01:23:21.040 align:start position:0% Gmail Outlook Etc have engineered their 01:23:21.040 --> 01:23:22.310 align:start position:0% Gmail Outlook Etc have engineered their systems<01:23:21.280> to<01:23:21.400> be<01:23:21.600> good<01:23:21.760> enough<01:23:22.040> that<01:23:22.159> this 01:23:22.310 --> 01:23:22.320 align:start position:0% systems to be good enough that this 01:23:22.320 --> 01:23:24.149 align:start position:0% systems to be good enough that this works<01:23:22.560> at<01:23:22.639> a<01:23:22.760> small<01:23:23.040> enough<01:23:23.280> scale<01:23:23.960> and<01:23:24.080> then 01:23:24.149 --> 01:23:24.159 align:start position:0% works at a small enough scale and then 01:23:24.159 --> 01:23:25.950 align:start position:0% works at a small enough scale and then hope<01:23:24.719> you<01:23:24.800> can<01:23:25.239> eventually<01:23:25.600> get<01:23:25.719> proof 01:23:25.950 --> 01:23:25.960 align:start position:0% hope you can eventually get proof 01:23:25.960 --> 01:23:27.350 align:start position:0% hope you can eventually get proof there's<01:23:26.120> more<01:23:26.239> robust<01:23:26.560> signatures<01:23:27.159> people 01:23:27.350 --> 01:23:27.360 align:start position:0% there's more robust signatures people 01:23:27.360 --> 01:23:28.870 align:start position:0% there's more robust signatures people add<01:23:27.520> DNS<01:23:27.840> SE<01:23:28.040> because<01:23:28.159> they<01:23:28.520> oh<01:23:28.600> this<01:23:28.679> is<01:23:28.760> a 01:23:28.870 --> 01:23:28.880 align:start position:0% add DNS SE because they oh this is a 01:23:28.880 --> 01:23:30.790 align:start position:0% add DNS SE because they oh this is a real<01:23:29.080> thing<01:23:29.280> people<01:23:29.520> want<01:23:29.679> and<01:23:29.800> are<01:23:30.000> using<01:23:30.639> so 01:23:30.790 --> 01:23:30.800 align:start position:0% real thing people want and are using so 01:23:30.800 --> 01:23:32.590 align:start position:0% real thing people want and are using so I<01:23:30.880> would<01:23:31.000> even<01:23:31.199> say<01:23:31.440> this<01:23:31.560> is<01:23:31.840> like<01:23:32.480> a 01:23:32.590 --> 01:23:32.600 align:start position:0% I would even say this is like a 01:23:32.600 --> 01:23:34.390 align:start position:0% I would even say this is like a transition<01:23:33.080> period<01:23:33.400> of<01:23:33.639> how<01:23:33.920> oh<01:23:34.040> we<01:23:34.120> need<01:23:34.239> to 01:23:34.390 --> 01:23:34.400 align:start position:0% transition period of how oh we need to 01:23:34.400 --> 01:23:36.110 align:start position:0% transition period of how oh we need to connect<01:23:34.960> these<01:23:35.120> kind<01:23:35.239> of<01:23:35.320> Worlds<01:23:35.560> of<01:23:35.760> data 01:23:36.110 --> 01:23:36.120 align:start position:0% connect these kind of Worlds of data 01:23:36.120 --> 01:23:38.990 align:start position:0% connect these kind of Worlds of data before<01:23:36.679> all<01:23:36.880> the<01:23:37.040> data<01:23:37.280> is<01:23:37.400> signed<01:23:37.679> and 01:23:38.990 --> 01:23:39.000 align:start position:0% before all the data is signed and 01:23:39.000 --> 01:23:42.149 align:start position:0% before all the data is signed and verifiable<01:23:40.000> hello<01:23:40.760> um<01:23:41.199> so<01:23:41.520> here<01:23:41.840> I'm<01:23:42.080> I'm 01:23:42.149 --> 01:23:42.159 align:start position:0% verifiable hello um so here I'm I'm 01:23:42.159 --> 01:23:44.870 align:start position:0% verifiable hello um so here I'm I'm going<01:23:42.280> to<01:23:42.480> talk<01:23:42.639> about<01:23:43.159> uh<01:23:43.320> cyber<01:23:43.679> frogs<01:23:44.520> um<01:23:44.760> if 01:23:44.870 --> 01:23:44.880 align:start position:0% going to talk about uh cyber frogs um if 01:23:44.880 --> 01:23:46.470 align:start position:0% going to talk about uh cyber frogs um if you've<01:23:45.400> uh<01:23:45.520> played<01:23:45.760> around<01:23:45.960> with<01:23:46.040> the<01:23:46.159> frog 01:23:46.470 --> 01:23:46.480 align:start position:0% you've uh played around with the frog 01:23:46.480 --> 01:23:48.110 align:start position:0% you've uh played around with the frog game<01:23:46.760> by<01:23:47.000> registration<01:23:47.600> you<01:23:47.719> might<01:23:47.840> have<01:23:47.920> seen 01:23:48.110 --> 01:23:48.120 align:start position:0% game by registration you might have seen 01:23:48.120 --> 01:23:50.510 align:start position:0% game by registration you might have seen one<01:23:48.239> of<01:23:48.360> these<01:23:48.679> things<01:23:49.639> uh<01:23:49.840> this<01:23:49.920> is<01:23:50.040> a<01:23:50.199> little 01:23:50.510 --> 01:23:50.520 align:start position:0% one of these things uh this is a little 01:23:50.520 --> 01:23:52.990 align:start position:0% one of these things uh this is a little box<01:23:51.440> um<01:23:51.639> a<01:23:51.760> little<01:23:52.239> uh<01:23:52.360> sort<01:23:52.520> of<01:23:52.679> custom 01:23:52.990 --> 01:23:53.000 align:start position:0% box um a little uh sort of custom 01:23:53.000 --> 01:23:57.870 align:start position:0% box um a little uh sort of custom circuit<01:23:53.320> board<01:23:53.840> a<01:23:54.520> uh<01:23:55.120> PCD<01:23:55.760> PCB<01:23:56.760> if<01:23:56.840> you<01:23:57.000> will 01:23:57.870 --> 01:23:57.880 align:start position:0% circuit board a uh PCD PCB if you will 01:23:57.880 --> 01:24:00.189 align:start position:0% circuit board a uh PCD PCB if you will um<01:23:58.400> that<01:23:58.760> like<01:23:59.159> it<01:23:59.320> has<01:23:59.480> the<01:23:59.639> ability<01:23:59.960> to 01:24:00.189 --> 01:24:00.199 align:start position:0% um that like it has the ability to 01:24:00.199 --> 01:24:04.629 align:start position:0% um that like it has the ability to generate<01:24:00.960> um<01:24:01.199> pod<01:24:01.639> v1s<01:24:02.639> uh<01:24:02.800> entirely<01:24:03.239> on<01:24:03.880> uh<01:24:04.120> a 01:24:04.629 --> 01:24:04.639 align:start position:0% generate um pod v1s uh entirely on uh a 01:24:04.639 --> 01:24:07.550 align:start position:0% generate um pod v1s uh entirely on uh a kind<01:24:04.760> of<01:24:05.000> like<01:24:05.440> pod<01:24:06.199> pipeline<01:24:06.840> that's<01:24:07.080> built 01:24:07.550 --> 01:24:07.560 align:start position:0% kind of like pod pipeline that's built 01:24:07.560 --> 01:24:11.750 align:start position:0% kind of like pod pipeline that's built using<01:24:08.560> uh<01:24:08.920> to<01:24:09.080> run<01:24:09.320> on<01:24:09.560> this<01:24:09.800> very<01:24:10.040> small<01:24:10.760> cheap 01:24:11.750 --> 01:24:11.760 align:start position:0% using uh to run on this very small cheap 01:24:11.760 --> 01:24:16.270 align:start position:0% using uh to run on this very small cheap uh<01:24:12.400> like<01:24:13.120> uh<01:24:13.480> risk<01:24:13.840> 5<01:24:14.280> processor<01:24:15.080> so<01:24:15.440> first<01:24:16.080> and 01:24:16.270 --> 01:24:16.280 align:start position:0% uh like uh risk 5 processor so first and 01:24:16.280 --> 01:24:17.470 align:start position:0% uh like uh risk 5 processor so first and and<01:24:16.400> I<01:24:16.480> think<01:24:16.600> that<01:24:16.760> there's<01:24:16.960> a<01:24:17.120> couple<01:24:17.320> of 01:24:17.470 --> 01:24:17.480 align:start position:0% and I think that there's a couple of 01:24:17.480 --> 01:24:18.750 align:start position:0% and I think that there's a couple of lessons<01:24:17.880> here<01:24:18.080> that<01:24:18.199> I<01:24:18.360> think<01:24:18.480> are<01:24:18.560> going<01:24:18.679> to 01:24:18.750 --> 01:24:18.760 align:start position:0% lessons here that I think are going to 01:24:18.760 --> 01:24:20.750 align:start position:0% lessons here that I think are going to be<01:24:18.920> interesting<01:24:19.280> to<01:24:19.480> people<01:24:19.760> interested<01:24:20.280> in 01:24:20.750 --> 01:24:20.760 align:start position:0% be interesting to people interested in 01:24:20.760 --> 01:24:23.390 align:start position:0% be interesting to people interested in sort<01:24:20.920> of<01:24:21.120> General<01:24:21.600> software<01:24:22.600> uh<01:24:22.880> programmable 01:24:23.390 --> 01:24:23.400 align:start position:0% sort of General software uh programmable 01:24:23.400 --> 01:24:25.790 align:start position:0% sort of General software uh programmable cryptography<01:24:24.199> uh 01:24:25.790 --> 01:24:25.800 align:start position:0% cryptography uh 01:24:25.800 --> 01:24:29.350 align:start position:0% cryptography uh that<01:24:25.920> I<01:24:26.040> think<01:24:26.719> parallels<01:24:27.719> um<01:24:28.520> like<01:24:29.159> like 01:24:29.350 --> 01:24:29.360 align:start position:0% that I think parallels um like like 01:24:29.360 --> 01:24:31.310 align:start position:0% that I think parallels um like like Hardware<01:24:29.760> I<01:24:29.840> think<01:24:30.080> parallels<01:24:30.920> uh<01:24:31.159> like 01:24:31.310 --> 01:24:31.320 align:start position:0% Hardware I think parallels uh like 01:24:31.320 --> 01:24:33.390 align:start position:0% Hardware I think parallels uh like programmable<01:24:31.960> cryptography<01:24:32.960> uh<01:24:33.199> in 01:24:33.390 --> 01:24:33.400 align:start position:0% programmable cryptography uh in 01:24:33.400 --> 01:24:36.790 align:start position:0% programmable cryptography uh in particular<01:24:33.800> ways<01:24:34.280> so<01:24:34.800> uh<01:24:35.480> going<01:24:35.800> back<01:24:36.280> to<01:24:36.520> some 01:24:36.790 --> 01:24:36.800 align:start position:0% particular ways so uh going back to some 01:24:36.800 --> 01:24:41.070 align:start position:0% particular ways so uh going back to some history<01:24:37.199> stuff<01:24:38.000> uh<01:24:38.120> this<01:24:38.239> is<01:24:38.400> ANC<01:24:39.320> oh<01:24:39.760> it's<01:24:40.760> uh 01:24:41.070 --> 01:24:41.080 align:start position:0% history stuff uh this is ANC oh it's uh 01:24:41.080 --> 01:24:44.149 align:start position:0% history stuff uh this is ANC oh it's uh wait<01:24:41.480> okay<01:24:41.800> this<01:24:41.920> is<01:24:42.080> aniac<01:24:42.600> it's<01:24:42.840> from<01:24:43.400> 1945 01:24:44.149 --> 01:24:44.159 align:start position:0% wait okay this is aniac it's from 1945 01:24:44.159 --> 01:24:46.109 align:start position:0% wait okay this is aniac it's from 1945 one<01:24:44.280> of<01:24:44.400> the<01:24:44.480> first<01:24:44.840> computers<01:24:45.320> it<01:24:45.400> was<01:24:45.480> $7.5 01:24:46.109 --> 01:24:46.119 align:start position:0% one of the first computers it was $7.5 01:24:46.119 --> 01:24:49.990 align:start position:0% one of the first computers it was $7.5 million<01:24:46.760> and<01:24:46.880> it<01:24:47.000> ran<01:24:47.239> at<01:24:48.000> 0.05<01:24:49.000> megahertz<01:24:49.880> a 01:24:49.990 --> 01:24:50.000 align:start position:0% million and it ran at 0.05 megahertz a 01:24:50.000 --> 01:24:51.470 align:start position:0% million and it ran at 0.05 megahertz a few<01:24:50.199> years<01:24:50.400> later<01:24:50.679> there<01:24:50.800> was<01:24:50.960> the<01:24:51.080> Apollo 01:24:51.470 --> 01:24:51.480 align:start position:0% few years later there was the Apollo 01:24:51.480 --> 01:24:54.910 align:start position:0% few years later there was the Apollo guidance<01:24:51.800> computer<01:24:52.159> $4.4<01:24:52.840> million<01:24:53.480> 2<01:24:53.719> MHz 01:24:54.910 --> 01:24:54.920 align:start position:0% guidance computer $4.4 million 2 MHz 01:24:54.920 --> 01:24:57.990 align:start position:0% guidance computer $4.4 million 2 MHz uh<01:24:55.159> and<01:24:55.520> in<01:24:55.679> 1984<01:24:56.400> we<01:24:56.560> had<01:24:56.880> the<01:24:57.320> Macintosh 01:24:57.990 --> 01:24:58.000 align:start position:0% uh and in 1984 we had the Macintosh 01:24:58.000 --> 01:24:58.830 align:start position:0% uh and in 1984 we had the Macintosh about 01:24:58.830 --> 01:24:58.840 align:start position:0% about 01:24:58.840 --> 01:25:02.750 align:start position:0% about $7,000<01:24:59.840> uh<01:24:59.960> 8<01:25:00.280> MHz<01:25:00.800> this<01:25:00.920> is<01:25:01.159> mors<01:25:01.560> law<01:25:01.840> roughly 01:25:02.750 --> 01:25:02.760 align:start position:0% $7,000 uh 8 MHz this is mors law roughly 01:25:02.760 --> 01:25:05.350 align:start position:0% $7,000 uh 8 MHz this is mors law roughly um<01:25:03.600> so<01:25:03.960> this<01:25:04.080> is<01:25:04.199> the<01:25:04.320> cyberfrog<01:25:05.000> it<01:25:05.119> costs 01:25:05.350 --> 01:25:05.360 align:start position:0% um so this is the cyberfrog it costs 01:25:05.360 --> 01:25:08.470 align:start position:0% um so this is the cyberfrog it costs about<01:25:05.560> $5<01:25:06.440> totally<01:25:06.920> custom<01:25:07.760> like<01:25:07.960> ordered<01:25:08.280> and 01:25:08.470 --> 01:25:08.480 align:start position:0% about $5 totally custom like ordered and 01:25:08.480 --> 01:25:10.790 align:start position:0% about $5 totally custom like ordered and designed<01:25:08.840> and<01:25:09.080> fabricated<01:25:09.679> and<01:25:10.239> with 01:25:10.790 --> 01:25:10.800 align:start position:0% designed and fabricated and with 01:25:10.800 --> 01:25:12.870 align:start position:0% designed and fabricated and with essentially<01:25:11.400> this<01:25:11.639> cost<01:25:12.040> over<01:25:12.360> the<01:25:12.520> course<01:25:12.719> of 01:25:12.870 --> 01:25:12.880 align:start position:0% essentially this cost over the course of 01:25:12.880 --> 01:25:15.830 align:start position:0% essentially this cost over the course of about<01:25:13.040> a<01:25:13.199> week<01:25:13.719> it<01:25:13.800> runs<01:25:14.080> at<01:25:14.560> 160<01:25:14.880> megahertz<01:25:15.679> so 01:25:15.830 --> 01:25:15.840 align:start position:0% about a week it runs at 160 megahertz so 01:25:15.840 --> 01:25:18.550 align:start position:0% about a week it runs at 160 megahertz so you<01:25:15.920> can<01:25:16.080> see<01:25:16.600> uh<01:25:16.920> and<01:25:17.000> it<01:25:17.119> has<01:25:17.239> a<01:25:17.400> risk<01:25:17.679> five<01:25:18.280> uh 01:25:18.550 --> 01:25:18.560 align:start position:0% you can see uh and it has a risk five uh 01:25:18.560 --> 01:25:22.310 align:start position:0% you can see uh and it has a risk five uh core<01:25:19.080> and<01:25:19.239> that<01:25:19.560> specific<01:25:19.960> core<01:25:20.560> is<01:25:20.760> about 01:25:22.310 --> 01:25:22.320 align:start position:0% core and that specific core is about 01:25:22.320 --> 01:25:25.109 align:start position:0% core and that specific core is about $160<01:25:23.320> um<01:25:23.480> and<01:25:23.600> that<01:25:23.679> sort<01:25:23.840> of<01:25:23.920> shows<01:25:24.440> the<01:25:24.600> scale 01:25:25.109 --> 01:25:25.119 align:start position:0% $160 um and that sort of shows the scale 01:25:25.119 --> 01:25:28.629 align:start position:0% $160 um and that sort of shows the scale of<01:25:25.840> like<01:25:26.840> how<01:25:27.280> Moors<01:25:27.679> law<01:25:28.000> has<01:25:28.159> essentially 01:25:28.629 --> 01:25:28.639 align:start position:0% of like how Moors law has essentially 01:25:28.639 --> 01:25:31.109 align:start position:0% of like how Moors law has essentially made<01:25:29.400> like<01:25:29.679> computers<01:25:30.159> super<01:25:30.400> cheap<01:25:30.840> super 01:25:31.109 --> 01:25:31.119 align:start position:0% made like computers super cheap super 01:25:31.119 --> 01:25:34.470 align:start position:0% made like computers super cheap super small<01:25:31.960> um<01:25:32.840> and<01:25:33.000> I<01:25:33.080> think<01:25:33.840> this<01:25:33.920> is<01:25:34.119> kind<01:25:34.239> of 01:25:34.470 --> 01:25:34.480 align:start position:0% small um and I think this is kind of 01:25:34.480 --> 01:25:36.430 align:start position:0% small um and I think this is kind of like<01:25:34.800> a<01:25:35.119> a<01:25:35.280> diagram<01:25:35.719> I<01:25:35.800> think<01:25:35.960> that<01:25:36.040> shows<01:25:36.320> some 01:25:36.430 --> 01:25:36.440 align:start position:0% like a a diagram I think that shows some 01:25:36.440 --> 01:25:38.870 align:start position:0% like a a diagram I think that shows some of<01:25:36.520> the<01:25:36.639> parallels<01:25:37.239> between<01:25:38.119> like<01:25:38.600> in<01:25:38.679> the 01:25:38.870 --> 01:25:38.880 align:start position:0% of the parallels between like in the 01:25:38.880 --> 01:25:40.910 align:start position:0% of the parallels between like in the past<01:25:39.119> we<01:25:39.280> had<01:25:39.440> these<01:25:39.639> big<01:25:39.840> room<01:25:40.159> siiz 01:25:40.910 --> 01:25:40.920 align:start position:0% past we had these big room siiz 01:25:40.920 --> 01:25:43.030 align:start position:0% past we had these big room siiz supercomputers<01:25:41.920> uh<01:25:42.119> that<01:25:42.400> sort<01:25:42.560> of<01:25:42.679> do<01:25:42.920> the 01:25:43.030 --> 01:25:43.040 align:start position:0% supercomputers uh that sort of do the 01:25:43.040 --> 01:25:44.990 align:start position:0% supercomputers uh that sort of do the equivalent<01:25:43.520> of<01:25:43.920> sort<01:25:44.119> of<01:25:44.239> the<01:25:44.440> very<01:25:44.679> small 01:25:44.990 --> 01:25:45.000 align:start position:0% equivalent of sort of the very small 01:25:45.000 --> 01:25:46.510 align:start position:0% equivalent of sort of the very small amount<01:25:45.199> of<01:25:45.360> compute<01:25:45.880> that<01:25:45.960> you<01:25:46.040> can<01:25:46.239> get<01:25:46.360> for 01:25:46.510 --> 01:25:46.520 align:start position:0% amount of compute that you can get for 01:25:46.520 --> 01:25:48.910 align:start position:0% amount of compute that you can get for literal<01:25:46.960> pennies<01:25:47.400> now<01:25:48.080> um<01:25:48.280> and<01:25:48.480> if<01:25:48.600> you<01:25:48.760> sort 01:25:48.910 --> 01:25:48.920 align:start position:0% literal pennies now um and if you sort 01:25:48.920 --> 01:25:51.189 align:start position:0% literal pennies now um and if you sort of<01:25:49.080> go<01:25:49.360> horizontally<01:25:50.119> and<01:25:50.320> like<01:25:50.520> preserve<01:25:51.040> the 01:25:51.189 --> 01:25:51.199 align:start position:0% of go horizontally and like preserve the 01:25:51.199 --> 01:25:54.070 align:start position:0% of go horizontally and like preserve the scale<01:25:51.719> the<01:25:52.199> size<01:25:52.440> and<01:25:52.719> cost<01:25:53.560> uh<01:25:53.639> you<01:25:53.760> end<01:25:53.920> up 01:25:54.070 --> 01:25:54.080 align:start position:0% scale the size and cost uh you end up 01:25:54.080 --> 01:25:55.750 align:start position:0% scale the size and cost uh you end up with<01:25:54.400> essentially<01:25:54.760> the<01:25:54.920> like<01:25:55.080> latest<01:25:55.440> AI 01:25:55.750 --> 01:25:55.760 align:start position:0% with essentially the like latest AI 01:25:55.760 --> 01:25:57.790 align:start position:0% with essentially the like latest AI supercomputers<01:25:56.480> on<01:25:56.639> the<01:25:56.800> right<01:25:57.119> is<01:25:57.639> the 01:25:57.790 --> 01:25:57.800 align:start position:0% supercomputers on the right is the 01:25:57.800 --> 01:26:00.390 align:start position:0% supercomputers on the right is the latest<01:25:58.199> Nvidia<01:25:58.679> dgx<01:25:59.360> like<01:25:59.560> super<01:25:59.920> cluster 01:26:00.390 --> 01:26:00.400 align:start position:0% latest Nvidia dgx like super cluster 01:26:00.400 --> 01:26:02.270 align:start position:0% latest Nvidia dgx like super cluster thing<01:26:00.880> which<01:26:01.000> is<01:26:01.159> sort<01:26:01.320> of<01:26:01.440> the<01:26:01.560> equivalent<01:26:02.000> of 01:26:02.270 --> 01:26:02.280 align:start position:0% thing which is sort of the equivalent of 01:26:02.280 --> 01:26:04.790 align:start position:0% thing which is sort of the equivalent of a<01:26:02.360> few<01:26:02.600> trillion<01:26:03.040> Hertz<01:26:03.840> uh<01:26:03.960> versus<01:26:04.320> 5,000 01:26:04.790 --> 01:26:04.800 align:start position:0% a few trillion Hertz uh versus 5,000 01:26:04.800 --> 01:26:07.830 align:start position:0% a few trillion Hertz uh versus 5,000 Hertz<01:26:05.719> um<01:26:06.560> on<01:26:06.679> the<01:26:06.840> bottom<01:26:07.199> you<01:26:07.320> can<01:26:07.440> sort<01:26:07.600> of 01:26:07.830 --> 01:26:07.840 align:start position:0% Hertz um on the bottom you can sort of 01:26:07.840 --> 01:26:09.830 align:start position:0% Hertz um on the bottom you can sort of have<01:26:08.480> uh<01:26:08.600> you<01:26:08.719> can<01:26:08.840> see<01:26:09.000> this<01:26:09.159> Arrow<01:26:09.520> it's<01:26:09.719> kind 01:26:09.830 --> 01:26:09.840 align:start position:0% have uh you can see this Arrow it's kind 01:26:09.840 --> 01:26:12.950 align:start position:0% have uh you can see this Arrow it's kind of<01:26:10.560> meant<01:26:10.760> to<01:26:11.000> represent<01:26:11.679> essentially<01:26:12.600> uh 01:26:12.950 --> 01:26:12.960 align:start position:0% of meant to represent essentially uh 01:26:12.960 --> 01:26:15.149 align:start position:0% of meant to represent essentially uh like<01:26:13.199> conservation<01:26:14.080> of<01:26:14.480> sort<01:26:14.679> of<01:26:14.840> compute 01:26:15.149 --> 01:26:15.159 align:start position:0% like conservation of sort of compute 01:26:15.159 --> 01:26:18.629 align:start position:0% like conservation of sort of compute quantity<01:26:16.000> so<01:26:16.639> uh<01:26:17.040> this<01:26:17.480> like<01:26:17.920> one<01:26:18.280> dollar 01:26:18.629 --> 01:26:18.639 align:start position:0% quantity so uh this like one dollar 01:26:18.639 --> 01:26:20.590 align:start position:0% quantity so uh this like one dollar processor<01:26:19.199> has<01:26:19.880> actually<01:26:20.159> orders<01:26:20.440> of 01:26:20.590 --> 01:26:20.600 align:start position:0% processor has actually orders of 01:26:20.600 --> 01:26:22.430 align:start position:0% processor has actually orders of magnitude<01:26:21.040> more<01:26:21.320> compute<01:26:21.719> capability<01:26:22.280> than 01:26:22.430 --> 01:26:22.440 align:start position:0% magnitude more compute capability than 01:26:22.440 --> 01:26:24.830 align:start position:0% magnitude more compute capability than that<01:26:22.719> like<01:26:23.440> original<01:26:23.800> ENC 01:26:24.830 --> 01:26:24.840 align:start position:0% that like original ENC 01:26:24.840 --> 01:26:27.270 align:start position:0% that like original ENC um<01:26:25.520> uh<01:26:25.760> but<01:26:25.920> you<01:26:26.040> can<01:26:26.239> also<01:26:26.520> end<01:26:26.679> up<01:26:26.920> creating 01:26:27.270 --> 01:26:27.280 align:start position:0% um uh but you can also end up creating 01:26:27.280 --> 01:26:30.510 align:start position:0% um uh but you can also end up creating an<01:26:27.440> even<01:26:27.719> slower<01:26:28.280> computer<01:26:29.280> uh<01:26:29.760> on<01:26:30.040> top<01:26:30.239> of 01:26:30.510 --> 01:26:30.520 align:start position:0% an even slower computer uh on top of 01:26:30.520 --> 01:26:34.590 align:start position:0% an even slower computer uh on top of that<01:26:31.119> like<01:26:31.880> trillion<01:26:32.880> like<01:26:33.239> terascale<01:26:34.239> like 01:26:34.590 --> 01:26:34.600 align:start position:0% that like trillion like terascale like 01:26:34.600 --> 01:26:36.270 align:start position:0% that like trillion like terascale like supercomputer<01:26:35.320> and<01:26:35.440> that's<01:26:35.840> sort<01:26:36.040> of<01:26:36.159> the 01:26:36.270 --> 01:26:36.280 align:start position:0% supercomputer and that's sort of the 01:26:36.280 --> 01:26:38.270 align:start position:0% supercomputer and that's sort of the overhead<01:26:36.719> of<01:26:36.800> a<01:26:36.880> lot<01:26:37.040> of<01:26:37.199> these<01:26:37.600> like<01:26:38.119> uh 01:26:38.270 --> 01:26:38.280 align:start position:0% overhead of a lot of these like uh 01:26:38.280 --> 01:26:40.270 align:start position:0% overhead of a lot of these like uh programmable<01:26:38.800> cryptography<01:26:39.440> systems<01:26:40.040> if 01:26:40.270 --> 01:26:40.280 align:start position:0% programmable cryptography systems if 01:26:40.280 --> 01:26:42.510 align:start position:0% programmable cryptography systems if you've<01:26:40.719> uh<01:26:40.840> played<01:26:41.119> the<01:26:41.239> Frog<01:26:41.639> Zone<01:26:42.080> thing 01:26:42.510 --> 01:26:42.520 align:start position:0% you've uh played the Frog Zone thing 01:26:42.520 --> 01:26:46.109 align:start position:0% you've uh played the Frog Zone thing also<01:26:43.679> um<01:26:44.679> that's<01:26:44.840> sort<01:26:45.000> of<01:26:45.119> an<01:26:45.280> example<01:26:45.639> of<01:26:45.960> the 01:26:46.109 --> 01:26:46.119 align:start position:0% also um that's sort of an example of the 01:26:46.119 --> 01:26:47.870 align:start position:0% also um that's sort of an example of the sort<01:26:46.239> of<01:26:46.320> tremendous<01:26:46.800> overhead<01:26:47.520> that<01:26:47.639> some<01:26:47.760> of 01:26:47.870 --> 01:26:47.880 align:start position:0% sort of tremendous overhead that some of 01:26:47.880 --> 01:26:50.430 align:start position:0% sort of tremendous overhead that some of these<01:26:48.000> Frontier<01:26:48.440> techniques<01:26:49.040> uh<01:26:49.239> involve<01:26:50.159> um 01:26:50.430 --> 01:26:50.440 align:start position:0% these Frontier techniques uh involve um 01:26:50.440 --> 01:26:52.629 align:start position:0% these Frontier techniques uh involve um so<01:26:50.800> going<01:26:51.040> back<01:26:51.199> to<01:26:51.320> the<01:26:51.440> FR<01:26:51.800> cyber<01:26:52.080> frogs<01:26:52.560> I 01:26:52.629 --> 01:26:52.639 align:start position:0% so going back to the FR cyber frogs I 01:26:52.639 --> 01:26:55.070 align:start position:0% so going back to the FR cyber frogs I think<01:26:53.360> there's<01:26:53.600> another<01:26:54.000> as<01:26:54.239> aspect<01:26:54.679> besides 01:26:55.070 --> 01:26:55.080 align:start position:0% think there's another as aspect besides 01:26:55.080 --> 01:26:57.790 align:start position:0% think there's another as aspect besides the<01:26:55.199> sort<01:26:55.360> of<01:26:55.679> computational<01:26:56.480> capability<01:26:57.360> oh 01:26:57.790 --> 01:26:57.800 align:start position:0% the sort of computational capability oh 01:26:57.800 --> 01:26:59.790 align:start position:0% the sort of computational capability oh and<01:26:58.159> I<01:26:58.320> I<01:26:58.400> think<01:26:59.080> uh<01:26:59.400> what's<01:26:59.560> sort<01:26:59.679> of 01:26:59.790 --> 01:26:59.800 align:start position:0% and I I think uh what's sort of 01:26:59.800 --> 01:27:01.830 align:start position:0% and I I think uh what's sort of interesting<01:27:00.360> is<01:27:00.880> basically<01:27:01.320> working<01:27:01.679> with 01:27:01.830 --> 01:27:01.840 align:start position:0% interesting is basically working with 01:27:01.840 --> 01:27:03.669 align:start position:0% interesting is basically working with this<01:27:01.960> sort<01:27:02.119> of<01:27:02.320> very<01:27:02.600> cheap<01:27:03.080> like<01:27:03.280> dollar 01:27:03.669 --> 01:27:03.679 align:start position:0% this sort of very cheap like dollar 01:27:03.679 --> 01:27:05.950 align:start position:0% this sort of very cheap like dollar scale<01:27:04.320> infrastructure<01:27:05.320> uh<01:27:05.440> you're<01:27:05.639> sort<01:27:05.840> of 01:27:05.950 --> 01:27:05.960 align:start position:0% scale infrastructure uh you're sort of 01:27:05.960 --> 01:27:07.750 align:start position:0% scale infrastructure uh you're sort of playing<01:27:06.320> with<01:27:06.480> a<01:27:06.719> restricted<01:27:07.320> Computing 01:27:07.750 --> 01:27:07.760 align:start position:0% playing with a restricted Computing 01:27:07.760 --> 01:27:10.830 align:start position:0% playing with a restricted Computing environment<01:27:08.639> the<01:27:08.800> way<01:27:09.199> that<01:27:09.560> like<01:27:10.520> uh<01:27:10.679> you 01:27:10.830 --> 01:27:10.840 align:start position:0% environment the way that like uh you 01:27:10.840 --> 01:27:13.109 align:start position:0% environment the way that like uh you sort<01:27:11.000> of<01:27:11.199> are<01:27:12.040> when<01:27:12.199> you're<01:27:12.440> working<01:27:12.920> with 01:27:13.109 --> 01:27:13.119 align:start position:0% sort of are when you're working with 01:27:13.119 --> 01:27:14.629 align:start position:0% sort of are when you're working with sort<01:27:13.320> of<01:27:13.520> programmable<01:27:14.080> cryptography 01:27:14.629 --> 01:27:14.639 align:start position:0% sort of programmable cryptography 01:27:14.639 --> 01:27:16.310 align:start position:0% sort of programmable cryptography environments<01:27:15.119> you're<01:27:15.400> like<01:27:15.520> they're<01:27:15.800> both 01:27:16.310 --> 01:27:16.320 align:start position:0% environments you're like they're both 01:27:16.320 --> 01:27:17.709 align:start position:0% environments you're like they're both sort<01:27:16.480> of<01:27:16.679> situations<01:27:17.239> where<01:27:17.360> you're<01:27:17.480> sort<01:27:17.639> of 01:27:17.709 --> 01:27:17.719 align:start position:0% sort of situations where you're sort of 01:27:17.719 --> 01:27:19.790 align:start position:0% sort of situations where you're sort of artificially<01:27:18.320> working<01:27:18.760> with<01:27:19.280> relatively 01:27:19.790 --> 01:27:19.800 align:start position:0% artificially working with relatively 01:27:19.800 --> 01:27:22.590 align:start position:0% artificially working with relatively cheap<01:27:20.360> or<01:27:20.600> relatively<01:27:21.119> slow<01:27:21.600> computers<01:27:22.320> so<01:27:22.480> I 01:27:22.590 --> 01:27:22.600 align:start position:0% cheap or relatively slow computers so I 01:27:22.600 --> 01:27:24.790 align:start position:0% cheap or relatively slow computers so I think<01:27:22.800> that's<01:27:23.360> uh<01:27:23.520> the<01:27:23.639> first<01:27:23.880> half<01:27:24.280> of<01:27:24.679> the 01:27:24.790 --> 01:27:24.800 align:start position:0% think that's uh the first half of the 01:27:24.800 --> 01:27:28.109 align:start position:0% think that's uh the first half of the first<01:27:25.119> parallel<01:27:25.600> I<01:27:25.719> think<01:27:26.480> of<01:27:26.719> why<01:27:27.239> um<01:27:27.800> sort<01:27:28.000> of 01:27:28.109 --> 01:27:28.119 align:start position:0% first parallel I think of why um sort of 01:27:28.119 --> 01:27:29.830 align:start position:0% first parallel I think of why um sort of playing<01:27:28.320> with<01:27:28.480> Hardware<01:27:28.800> is<01:27:28.920> interesting<01:27:29.719> uh 01:27:29.830 --> 01:27:29.840 align:start position:0% playing with Hardware is interesting uh 01:27:29.840 --> 01:27:32.430 align:start position:0% playing with Hardware is interesting uh the<01:27:29.960> second<01:27:30.239> one<01:27:30.880> is<01:27:31.199> that<01:27:31.639> like<01:27:31.880> they're<01:27:32.159> both 01:27:32.430 --> 01:27:32.440 align:start position:0% the second one is that like they're both 01:27:32.440 --> 01:27:34.149 align:start position:0% the second one is that like they're both called<01:27:32.719> circuits<01:27:33.360> like<01:27:33.600> when<01:27:33.719> you're<01:27:33.880> working 01:27:34.149 --> 01:27:34.159 align:start position:0% called circuits like when you're working 01:27:34.159 --> 01:27:36.629 align:start position:0% called circuits like when you're working with<01:27:34.320> ZK<01:27:34.679> snarks<01:27:35.639> uh<01:27:35.880> and<01:27:36.159> also<01:27:36.360> when<01:27:36.480> you're 01:27:36.629 --> 01:27:36.639 align:start position:0% with ZK snarks uh and also when you're 01:27:36.639 --> 01:27:38.350 align:start position:0% with ZK snarks uh and also when you're working<01:27:36.960> with<01:27:37.199> like<01:27:37.480> electronic<01:27:37.960> circuits 01:27:38.350 --> 01:27:38.360 align:start position:0% working with like electronic circuits 01:27:38.360 --> 01:27:40.470 align:start position:0% working with like electronic circuits they're<01:27:38.560> both<01:27:38.840> naturally<01:27:39.320> circuits<01:27:40.239> uh<01:27:40.360> on 01:27:40.470 --> 01:27:40.480 align:start position:0% they're both naturally circuits uh on 01:27:40.480 --> 01:27:43.109 align:start position:0% they're both naturally circuits uh on the<01:27:40.639> left<01:27:41.040> I<01:27:41.239> have<01:27:41.840> um<01:27:42.639> uh<01:27:42.800> this<01:27:42.880> is<01:27:43.000> a 01:27:43.109 --> 01:27:43.119 align:start position:0% the left I have um uh this is a 01:27:43.119 --> 01:27:45.070 align:start position:0% the left I have um uh this is a screenshot<01:27:43.600> from<01:27:43.719> ZK<01:27:44.080> reppel<01:27:44.480> which<01:27:44.600> is<01:27:44.719> a 01:27:45.070 --> 01:27:45.080 align:start position:0% screenshot from ZK reppel which is a 01:27:45.080 --> 01:27:47.430 align:start position:0% screenshot from ZK reppel which is a little<01:27:45.400> circom<01:27:46.239> like<01:27:46.400> developer<01:27:46.840> environment 01:27:47.430 --> 01:27:47.440 align:start position:0% little circom like developer environment 01:27:47.440 --> 01:27:49.830 align:start position:0% little circom like developer environment that<01:27:47.800> runs<01:27:48.159> in<01:27:48.239> the<01:27:48.520> browser<01:27:49.320> uh<01:27:49.400> that<01:27:49.520> I<01:27:49.600> built 01:27:49.830 --> 01:27:49.840 align:start position:0% that runs in the browser uh that I built 01:27:49.840 --> 01:27:52.950 align:start position:0% that runs in the browser uh that I built a<01:27:49.920> few<01:27:50.080> years<01:27:50.280> ago<01:27:51.080> um<01:27:51.639> and<01:27:51.960> on<01:27:52.080> the<01:27:52.280> right<01:27:52.600> is<01:27:52.840> a 01:27:52.950 --> 01:27:52.960 align:start position:0% a few years ago um and on the right is a 01:27:52.960 --> 01:27:55.830 align:start position:0% a few years ago um and on the right is a screenshot<01:27:53.440> from<01:27:53.600> eased<01:27:54.280> a<01:27:54.880> uh<01:27:55.000> which<01:27:55.119> is<01:27:55.280> a 01:27:55.830 --> 01:27:55.840 align:start position:0% screenshot from eased a uh which is a 01:27:55.840 --> 01:27:58.709 align:start position:0% screenshot from eased a uh which is a also<01:27:56.080> a<01:27:56.280> web-based<01:27:57.119> uh<01:27:57.320> very<01:27:57.560> easy<01:27:57.880> to<01:27:58.520> get 01:27:58.709 --> 01:27:58.719 align:start position:0% also a web-based uh very easy to get 01:27:58.719 --> 01:28:01.669 align:start position:0% also a web-based uh very easy to get started<01:27:59.199> with<01:27:59.760> uh<01:28:00.280> like<01:28:00.880> a<01:28:01.080> system<01:28:01.440> for 01:28:01.669 --> 01:28:01.679 align:start position:0% started with uh like a system for 01:28:01.679 --> 01:28:04.189 align:start position:0% started with uh like a system for Designing<01:28:02.159> circuit<01:28:02.480> boards<01:28:03.080> including<01:28:03.960> uh 01:28:04.189 --> 01:28:04.199 align:start position:0% Designing circuit boards including uh 01:28:04.199 --> 01:28:07.629 align:start position:0% Designing circuit boards including uh like<01:28:04.639> the<01:28:05.280> uh<01:28:05.960> uh<01:28:06.119> cyberfrog<01:28:06.840> which<01:28:07.080> this<01:28:07.199> is<01:28:07.480> a 01:28:07.629 --> 01:28:07.639 align:start position:0% like the uh uh cyberfrog which this is a 01:28:07.639 --> 01:28:11.070 align:start position:0% like the uh uh cyberfrog which this is a sort<01:28:07.800> of<01:28:08.560> uh<01:28:08.800> screenshot<01:28:09.239> of<01:28:09.360> part<01:28:09.520> of<01:28:09.639> it<01:28:10.119> um 01:28:11.070 --> 01:28:11.080 align:start position:0% sort of uh screenshot of part of it um 01:28:11.080 --> 01:28:12.669 align:start position:0% sort of uh screenshot of part of it um you<01:28:11.199> can<01:28:11.320> see<01:28:11.520> that<01:28:11.639> they're<01:28:12.119> both<01:28:12.360> about<01:28:12.560> like 01:28:12.669 --> 01:28:12.679 align:start position:0% you can see that they're both about like 01:28:12.679 --> 01:28:14.070 align:start position:0% you can see that they're both about like sort<01:28:12.840> of<01:28:12.920> declaring<01:28:13.320> signals<01:28:13.719> one<01:28:13.840> is<01:28:13.960> a 01:28:14.070 --> 01:28:14.080 align:start position:0% sort of declaring signals one is a 01:28:14.080 --> 01:28:15.390 align:start position:0% sort of declaring signals one is a graphical<01:28:14.440> interface<01:28:14.840> the<01:28:14.960> other<01:28:15.080> one's<01:28:15.280> sort 01:28:15.390 --> 01:28:15.400 align:start position:0% graphical interface the other one's sort 01:28:15.400 --> 01:28:17.550 align:start position:0% graphical interface the other one's sort of<01:28:15.520> more<01:28:15.719> code-like<01:28:16.119> but<01:28:16.719> ultimately<01:28:17.199> it<01:28:17.320> gets 01:28:17.550 --> 01:28:17.560 align:start position:0% of more code-like but ultimately it gets 01:28:17.560 --> 01:28:21.830 align:start position:0% of more code-like but ultimately it gets compiled<01:28:18.159> down<01:28:18.960> into<01:28:20.199> uh<01:28:21.199> something<01:28:21.520> that<01:28:21.719> in 01:28:21.830 --> 01:28:21.840 align:start position:0% compiled down into uh something that in 01:28:21.840 --> 01:28:23.550 align:start position:0% compiled down into uh something that in the<01:28:22.000> electrical<01:28:22.480> world<01:28:22.800> is<01:28:22.960> called<01:28:23.159> a<01:28:23.280> net 01:28:23.550 --> 01:28:23.560 align:start position:0% the electrical world is called a net 01:28:23.560 --> 01:28:27.550 align:start position:0% the electrical world is called a net list<01:28:24.400> um<01:28:24.960> it's<01:28:25.960> pretty<01:28:26.199> much<01:28:26.480> equivalent<01:28:27.119> to 01:28:27.550 --> 01:28:27.560 align:start position:0% list um it's pretty much equivalent to 01:28:27.560 --> 01:28:30.550 align:start position:0% list um it's pretty much equivalent to the<01:28:27.719> sort<01:28:27.880> of<01:28:28.000> R1<01:28:28.880> uh<01:28:29.000> CS<01:28:29.440> sort<01:28:29.600> of<01:28:30.320> uh 01:28:30.550 --> 01:28:30.560 align:start position:0% the sort of R1 uh CS sort of uh 01:28:30.560 --> 01:28:33.990 align:start position:0% the sort of R1 uh CS sort of uh representation<01:28:31.360> that<01:28:31.639> like<01:28:32.520> uh<01:28:33.520> is<01:28:33.679> sort<01:28:33.880> of 01:28:33.990 --> 01:28:34.000 align:start position:0% representation that like uh is sort of 01:28:34.000 --> 01:28:37.030 align:start position:0% representation that like uh is sort of the<01:28:34.360> intermediate<01:28:35.360> uh<01:28:35.679> like<01:28:35.880> part<01:28:36.040> of<01:28:36.199> circom 01:28:37.030 --> 01:28:37.040 align:start position:0% the intermediate uh like part of circom 01:28:37.040 --> 01:28:39.990 align:start position:0% the intermediate uh like part of circom that<01:28:37.199> eventually<01:28:38.000> uh<01:28:38.119> turns<01:28:38.600> into<01:28:39.600> like<01:28:39.840> sort 01:28:39.990 --> 01:28:40.000 align:start position:0% that eventually uh turns into like sort 01:28:40.000 --> 01:28:44.070 align:start position:0% that eventually uh turns into like sort of<01:28:40.159> plon<01:28:40.440> or<01:28:40.560> grth<01:28:40.920> 16<01:28:41.280> or<01:28:41.800> whatever<01:28:42.639> um 01:28:44.070 --> 01:28:44.080 align:start position:0% of plon or grth 16 or whatever um 01:28:44.080 --> 01:28:48.830 align:start position:0% of plon or grth 16 or whatever um so<01:28:45.080> you<01:28:45.280> have<01:28:45.520> this<01:28:46.239> um<01:28:47.199> and<01:28:47.320> then<01:28:48.199> at<01:28:48.320> the<01:28:48.440> end 01:28:48.830 --> 01:28:48.840 align:start position:0% so you have this um and then at the end 01:28:48.840 --> 01:28:51.350 align:start position:0% so you have this um and then at the end it<01:28:49.000> gets<01:28:49.239> compiled<01:28:49.800> into<01:28:50.679> a<01:28:50.840> sort<01:28:51.000> of<01:28:51.159> like 01:28:51.350 --> 01:28:51.360 align:start position:0% it gets compiled into a sort of like 01:28:51.360 --> 01:28:55.830 align:start position:0% it gets compiled into a sort of like physical<01:28:52.280> uh<01:28:52.840> representation<01:28:53.840> uh<01:28:54.480> like<01:28:55.159> uh<01:28:55.400> by 01:28:55.830 --> 01:28:55.840 align:start position:0% physical uh representation uh like uh by 01:28:55.840 --> 01:28:57.910 align:start position:0% physical uh representation uh like uh by some<01:28:56.000> sort<01:28:56.159> of<01:28:56.280> compiler<01:28:57.280> on<01:28:57.400> the<01:28:57.520> left<01:28:57.760> is 01:28:57.910 --> 01:28:57.920 align:start position:0% some sort of compiler on the left is 01:28:57.920 --> 01:28:59.229 align:start position:0% some sort of compiler on the left is sort<01:28:58.040> of<01:28:58.159> a<01:28:58.280> little<01:28:58.560> application<01:28:59.080> that 01:28:59.229 --> 01:28:59.239 align:start position:0% sort of a little application that 01:28:59.239 --> 01:29:01.870 align:start position:0% sort of a little application that generates<01:29:00.080> uh<01:29:00.400> that<01:29:00.520> takes<01:29:00.800> that<01:29:00.920> sort<01:29:01.080> of<01:29:01.480> R1 01:29:01.870 --> 01:29:01.880 align:start position:0% generates uh that takes that sort of R1 01:29:01.880 --> 01:29:03.590 align:start position:0% generates uh that takes that sort of R1 CS<01:29:02.159> stuff<01:29:02.400> turns<01:29:02.639> it<01:29:02.760> into<01:29:03.080> like<01:29:03.199> a<01:29:03.360> little 01:29:03.590 --> 01:29:03.600 align:start position:0% CS stuff turns it into like a little 01:29:03.600 --> 01:29:06.669 align:start position:0% CS stuff turns it into like a little plun<01:29:04.000> prover<01:29:05.000> uh<01:29:05.480> and<01:29:05.639> then<01:29:05.800> on<01:29:05.960> the<01:29:06.119> right<01:29:06.400> you 01:29:06.669 --> 01:29:06.679 align:start position:0% plun prover uh and then on the right you 01:29:06.679 --> 01:29:10.149 align:start position:0% plun prover uh and then on the right you have<01:29:07.440> uh<01:29:07.560> the<01:29:07.679> sort<01:29:07.840> of<01:29:07.960> laid<01:29:08.199> out<01:29:08.719> PCB<01:29:09.719> um<01:29:09.880> for 01:29:10.149 --> 01:29:10.159 align:start position:0% have uh the sort of laid out PCB um for 01:29:10.159 --> 01:29:11.790 align:start position:0% have uh the sort of laid out PCB um for the<01:29:10.280> Frog<01:29:10.639> this<01:29:10.719> is<01:29:11.000> sort<01:29:11.159> of<01:29:11.320> the<01:29:11.440> tail 01:29:11.790 --> 01:29:11.800 align:start position:0% the Frog this is sort of the tail 01:29:11.800 --> 01:29:13.550 align:start position:0% the Frog this is sort of the tail section 01:29:13.550 --> 01:29:13.560 align:start position:0% section 01:29:13.560 --> 01:29:18.990 align:start position:0% section um<01:29:14.560> and<01:29:15.000> so<01:29:15.600> like<01:29:16.560> I<01:29:16.679> think<01:29:17.280> basically<01:29:18.280> there's 01:29:18.990 --> 01:29:19.000 align:start position:0% um and so like I think basically there's 01:29:19.000 --> 01:29:21.629 align:start position:0% um and so like I think basically there's two<01:29:19.280> things<01:29:19.560> that<01:29:19.719> I<01:29:19.800> think<01:29:19.920> are<01:29:20.639> interesting 01:29:21.629 --> 01:29:21.639 align:start position:0% two things that I think are interesting 01:29:21.639 --> 01:29:23.430 align:start position:0% two things that I think are interesting like<01:29:21.840> one<01:29:22.040> is<01:29:22.199> sort<01:29:22.400> of<01:29:22.840> working<01:29:23.159> in<01:29:23.280> these 01:29:23.430 --> 01:29:23.440 align:start position:0% like one is sort of working in these 01:29:23.440 --> 01:29:24.870 align:start position:0% like one is sort of working in these constrainted<01:29:23.800> envir<01:29:24.199> environments<01:29:24.600> are<01:29:24.760> kind 01:29:24.870 --> 01:29:24.880 align:start position:0% constrainted envir environments are kind 01:29:24.880 --> 01:29:27.990 align:start position:0% constrainted envir environments are kind of<01:29:25.000> similar<01:29:25.960> uh<01:29:26.440> and<01:29:26.600> and<01:29:26.800> kind<01:29:26.880> of<01:29:27.040> fun<01:29:27.639> uh<01:29:27.840> and 01:29:27.990 --> 01:29:28.000 align:start position:0% of similar uh and and kind of fun uh and 01:29:28.000 --> 01:29:30.229 align:start position:0% of similar uh and and kind of fun uh and the<01:29:28.159> second<01:29:28.560> is<01:29:29.040> sort<01:29:29.239> of<01:29:29.400> structurally<01:29:30.080> when 01:29:30.229 --> 01:29:30.239 align:start position:0% the second is sort of structurally when 01:29:30.239 --> 01:29:32.510 align:start position:0% the second is sort of structurally when you're<01:29:30.440> working<01:29:30.800> with<01:29:31.000> Hardware<01:29:32.000> uh<01:29:32.320> you're 01:29:32.510 --> 01:29:32.520 align:start position:0% you're working with Hardware uh you're 01:29:32.520 --> 01:29:33.830 align:start position:0% you're working with Hardware uh you're building<01:29:32.880> circuits<01:29:33.280> and<01:29:33.400> a<01:29:33.480> lot<01:29:33.600> of<01:29:33.679> these 01:29:33.830 --> 01:29:33.840 align:start position:0% building circuits and a lot of these 01:29:33.840 --> 01:29:36.070 align:start position:0% building circuits and a lot of these circuits<01:29:34.199> are<01:29:35.119> develop<01:29:35.480> a<01:29:35.600> lot<01:29:35.679> of<01:29:35.800> similar 01:29:36.070 --> 01:29:36.080 align:start position:0% circuits are develop a lot of similar 01:29:36.080 --> 01:29:37.790 align:start position:0% circuits are develop a lot of similar mental<01:29:36.400> models<01:29:36.719> around<01:29:37.040> abstraction<01:29:37.639> and 01:29:37.790 --> 01:29:37.800 align:start position:0% mental models around abstraction and 01:29:37.800 --> 01:29:41.270 align:start position:0% mental models around abstraction and connecting<01:29:38.600> things<01:29:38.960> together<01:29:39.880> uh<01:29:40.480> that<01:29:41.040> uh 01:29:41.270 --> 01:29:41.280 align:start position:0% connecting things together uh that uh 01:29:41.280 --> 01:29:43.750 align:start position:0% connecting things together uh that uh also<01:29:41.600> apply<01:29:42.480> uh<01:29:42.679> and<01:29:42.880> actually<01:29:43.280> it's<01:29:43.440> just 01:29:43.750 --> 01:29:43.760 align:start position:0% also apply uh and actually it's just 01:29:43.760 --> 01:29:46.390 align:start position:0% also apply uh and actually it's just like<01:29:44.760> nowadays<01:29:45.199> with<01:29:45.400> how<01:29:45.600> cheap<01:29:45.960> it<01:29:46.080> is<01:29:46.239> to 01:29:46.390 --> 01:29:46.400 align:start position:0% like nowadays with how cheap it is to 01:29:46.400 --> 01:29:48.510 align:start position:0% like nowadays with how cheap it is to manufacture<01:29:46.960> stuff<01:29:47.159> in<01:29:47.320> China<01:29:47.920> like<01:29:48.239> I<01:29:48.320> think 01:29:48.510 --> 01:29:48.520 align:start position:0% manufacture stuff in China like I think 01:29:48.520 --> 01:29:50.550 align:start position:0% manufacture stuff in China like I think if<01:29:48.639> you<01:29:48.800> have<01:29:48.960> the<01:29:49.119> skills<01:29:49.480> to<01:29:49.760> like<01:29:50.199> build 01:29:50.550 --> 01:29:50.560 align:start position:0% if you have the skills to like build 01:29:50.560 --> 01:29:54.149 align:start position:0% if you have the skills to like build circuits<01:29:51.199> with<01:29:51.719> uh<01:29:52.119> like<01:29:52.320> software<01:29:53.040> and<01:29:53.880> uh 01:29:54.149 --> 01:29:54.159 align:start position:0% circuits with uh like software and uh 01:29:54.159 --> 01:29:55.870 align:start position:0% circuits with uh like software and uh like<01:29:54.280> ZK<01:29:54.600> snarks<01:29:54.920> you<01:29:55.000> can<01:29:55.159> also<01:29:55.480> pretty<01:29:55.679> much 01:29:55.870 --> 01:29:55.880 align:start position:0% like ZK snarks you can also pretty much 01:29:55.880 --> 01:29:57.310 align:start position:0% like ZK snarks you can also pretty much apply<01:29:56.159> a<01:29:56.239> lot<01:29:56.360> of<01:29:56.480> those<01:29:56.639> same<01:29:56.840> skills<01:29:57.159> to 01:29:57.310 --> 01:29:57.320 align:start position:0% apply a lot of those same skills to 01:29:57.320 --> 01:29:59.109 align:start position:0% apply a lot of those same skills to building<01:29:57.960> sort<01:29:58.119> of<01:29:58.280> physical<01:29:58.639> things<01:29:59.000> that 01:29:59.109 --> 01:29:59.119 align:start position:0% building sort of physical things that 01:29:59.119 --> 01:30:02.229 align:start position:0% building sort of physical things that are<01:29:59.239> shaped<01:29:59.560> like<01:29:59.679> frogs<01:30:00.480> so 01:30:02.229 --> 01:30:02.239 align:start position:0% are shaped like frogs so 01:30:02.239 --> 01:30:06.070 align:start position:0% are shaped like frogs so yeah<01:30:03.239> um<01:30:03.679> happy<01:30:03.880> to<01:30:04.000> answer<01:30:04.239> any<01:30:04.440> questions 01:30:06.070 --> 01:30:06.080 align:start position:0% yeah um happy to answer any questions 01:30:06.080 --> 01:30:11.979 align:start position:0% yeah um happy to answer any questions [Applause]