WEBVTT Kind: captions Language: en 00:00:01.570 --> 00:00:17.870 align:start position:0% [Music] 00:00:17.870 --> 00:00:17.880 align:start position:0% 00:00:17.880 --> 00:00:22.029 align:start position:0% okay<00:00:18.119> great<00:00:18.439> so<00:00:18.840> the<00:00:19.359> uh<00:00:19.520> far<00:00:19.880> future<00:00:20.560> of<00:00:20.920> uh 00:00:22.029 --> 00:00:22.039 align:start position:0% okay great so the uh far future of uh 00:00:22.039 --> 00:00:26.310 align:start position:0% okay great so the uh far future of uh cryptography<00:00:23.039> um 00:00:26.310 --> 00:00:26.320 align:start position:0% 00:00:26.320 --> 00:00:30.310 align:start position:0% sorry<00:00:27.320> next<00:00:27.519> slide<00:00:28.000> okay<00:00:28.599> great<00:00:28.920> so<00:00:29.640> I<00:00:29.759> think 00:00:30.310 --> 00:00:30.320 align:start position:0% sorry next slide okay great so I think 00:00:30.320 --> 00:00:32.350 align:start position:0% sorry next slide okay great so I think first<00:00:30.960> know<00:00:31.080> we'll<00:00:31.279> talk<00:00:31.480> we'll<00:00:31.720> talk<00:00:31.960> about 00:00:32.350 --> 00:00:32.360 align:start position:0% first know we'll talk we'll talk about 00:00:32.360 --> 00:00:36.190 align:start position:0% first know we'll talk we'll talk about the<00:00:32.960> uh<00:00:33.440> very<00:00:33.879> recent<00:00:34.879> past<00:00:35.480> and<00:00:35.879> I<00:00:36.000> think 00:00:36.190 --> 00:00:36.200 align:start position:0% the uh very recent past and I think 00:00:36.200 --> 00:00:38.150 align:start position:0% the uh very recent past and I think still<00:00:36.440> ongoing<00:00:36.879> present<00:00:37.239> of<00:00:37.399> cryptography 00:00:38.150 --> 00:00:38.160 align:start position:0% still ongoing present of cryptography 00:00:38.160 --> 00:00:40.869 align:start position:0% still ongoing present of cryptography right<00:00:38.320> I<00:00:38.480> think<00:00:39.480> the<00:00:39.640> biggest<00:00:40.039> change<00:00:40.719> that 00:00:40.869 --> 00:00:40.879 align:start position:0% right I think the biggest change that 00:00:40.879 --> 00:00:44.190 align:start position:0% right I think the biggest change that we've<00:00:41.079> seen<00:00:41.559> over<00:00:41.920> the<00:00:42.600> last<00:00:43.000> few<00:00:43.280> years<00:00:43.760> is 00:00:44.190 --> 00:00:44.200 align:start position:0% we've seen over the last few years is 00:00:44.200 --> 00:00:46.590 align:start position:0% we've seen over the last few years is basically<00:00:45.120> the<00:00:45.280> way<00:00:45.440> that<00:00:45.600> sarks<00:00:46.160> have<00:00:46.320> really 00:00:46.590 --> 00:00:46.600 align:start position:0% basically the way that sarks have really 00:00:46.600 --> 00:00:49.270 align:start position:0% basically the way that sarks have really taken<00:00:46.879> over<00:00:47.160> everything<00:00:47.760> right<00:00:48.520> and<00:00:49.039> one<00:00:49.160> of 00:00:49.270 --> 00:00:49.280 align:start position:0% taken over everything right and one of 00:00:49.280 --> 00:00:50.830 align:start position:0% taken over everything right and one of the<00:00:49.399> analogies<00:00:49.840> that<00:00:49.960> I've<00:00:50.079> used<00:00:50.399> is<00:00:50.600> I've 00:00:50.830 --> 00:00:50.840 align:start position:0% the analogies that I've used is I've 00:00:50.840 --> 00:00:52.670 align:start position:0% the analogies that I've used is I've thought<00:00:51.000> of<00:00:51.120> SARS<00:00:51.640> as<00:00:51.760> being<00:00:52.000> similar<00:00:52.359> to<00:00:52.520> a 00:00:52.670 --> 00:00:52.680 align:start position:0% thought of SARS as being similar to a 00:00:52.680 --> 00:00:55.029 align:start position:0% thought of SARS as being similar to a Transformer<00:00:53.399> right<00:00:53.520> so<00:00:53.719> this<00:00:53.840> is<00:00:54.719> know<00:00:54.920> the 00:00:55.029 --> 00:00:55.039 align:start position:0% Transformer right so this is know the 00:00:55.039 --> 00:00:57.950 align:start position:0% Transformer right so this is know the GPT<00:00:55.559> architecture<00:00:56.359> that's<00:00:56.840> now<00:00:57.120> famous<00:00:57.520> from 00:00:57.950 --> 00:00:57.960 align:start position:0% GPT architecture that's now famous from 00:00:57.960 --> 00:01:00.470 align:start position:0% GPT architecture that's now famous from AI<00:00:58.399> land<00:00:59.199> and 00:01:00.470 --> 00:01:00.480 align:start position:0% AI land and 00:01:00.480 --> 00:01:02.670 align:start position:0% AI land and the<00:01:00.640> analogy<00:01:01.160> here<00:01:01.320> is<00:01:01.559> basically<00:01:02.160> that<00:01:02.559> if 00:01:02.670 --> 00:01:02.680 align:start position:0% the analogy here is basically that if 00:01:02.680 --> 00:01:05.070 align:start position:0% the analogy here is basically that if you<00:01:02.840> think<00:01:03.079> about<00:01:03.320> what<00:01:03.519> GPT<00:01:04.400> did<00:01:04.760> right<00:01:04.920> it 00:01:05.070 --> 00:01:05.080 align:start position:0% you think about what GPT did right it 00:01:05.080 --> 00:01:07.429 align:start position:0% you think about what GPT did right it basically<00:01:06.000> took<00:01:06.640> a<00:01:06.840> whole<00:01:07.040> bunch<00:01:07.280> of 00:01:07.429 --> 00:01:07.439 align:start position:0% basically took a whole bunch of 00:01:07.439 --> 00:01:09.310 align:start position:0% basically took a whole bunch of different<00:01:07.720> use<00:01:08.080> cases<00:01:08.479> for<00:01:08.680> which<00:01:08.920> thousands 00:01:09.310 --> 00:01:09.320 align:start position:0% different use cases for which thousands 00:01:09.320 --> 00:01:11.270 align:start position:0% different use cases for which thousands of<00:01:09.479> people<00:01:09.759> have<00:01:09.920> been<00:01:10.080> putting<00:01:10.360> in<00:01:10.720> years<00:01:11.040> of 00:01:11.270 --> 00:01:11.280 align:start position:0% of people have been putting in years of 00:01:11.280 --> 00:01:14.070 align:start position:0% of people have been putting in years of hard<00:01:11.560> work<00:01:11.960> years<00:01:12.240> of<00:01:12.920> application<00:01:13.600> specific 00:01:14.070 --> 00:01:14.080 align:start position:0% hard work years of application specific 00:01:14.080 --> 00:01:16.310 align:start position:0% hard work years of application specific algorithms<00:01:14.799> application<00:01:15.479> specific<00:01:15.960> data 00:01:16.310 --> 00:01:16.320 align:start position:0% algorithms application specific data 00:01:16.320 --> 00:01:18.749 align:start position:0% algorithms application specific data Gathering<00:01:16.840> application<00:01:17.439> specific<00:01:17.880> expertise 00:01:18.749 --> 00:01:18.759 align:start position:0% Gathering application specific expertise 00:01:18.759 --> 00:01:21.109 align:start position:0% Gathering application specific expertise and<00:01:18.840> it<00:01:19.040> just<00:01:19.240> like<00:01:19.400> swept<00:01:19.960> all<00:01:20.119> of<00:01:20.360> that<00:01:20.560> away 00:01:21.109 --> 00:01:21.119 align:start position:0% and it just like swept all of that away 00:01:21.119 --> 00:01:22.950 align:start position:0% and it just like swept all of that away with<00:01:21.400> just<00:01:21.520> a<00:01:21.720> really<00:01:22.000> dumb<00:01:22.320> system<00:01:22.640> where<00:01:22.759> you 00:01:22.950 --> 00:01:22.960 align:start position:0% with just a really dumb system where you 00:01:22.960 --> 00:01:25.350 align:start position:0% with just a really dumb system where you just<00:01:23.240> like<00:01:23.880> put<00:01:24.360> like<00:01:24.520> take<00:01:25.000> half<00:01:25.200> the 00:01:25.350 --> 00:01:25.360 align:start position:0% just like put like take half the 00:01:25.360 --> 00:01:27.310 align:start position:0% just like put like take half the internet<00:01:25.840> like<00:01:26.000> throw<00:01:26.200> it<00:01:26.360> into<00:01:26.560> a<00:01:26.720> funnel<00:01:27.159> and 00:01:27.310 --> 00:01:27.320 align:start position:0% internet like throw it into a funnel and 00:01:27.320 --> 00:01:29.550 align:start position:0% internet like throw it into a funnel and then<00:01:27.799> like<00:01:27.960> run<00:01:28.159> the<00:01:28.320> G<00:01:28.520> run<00:01:28.680> a<00:01:28.799> bunch<00:01:28.960> of<00:01:29.119> gpus 00:01:29.550 --> 00:01:29.560 align:start position:0% then like run the G run a bunch of gpus 00:01:29.560 --> 00:01:31.350 align:start position:0% then like run the G run a bunch of gpus for<00:01:29.680> a<00:01:29.759> while<00:01:30.320> and<00:01:30.439> it<00:01:30.600> just<00:01:30.799> manages<00:01:31.200> to 00:01:31.350 --> 00:01:31.360 align:start position:0% for a while and it just manages to 00:01:31.360 --> 00:01:33.109 align:start position:0% for a while and it just manages to magically<00:01:31.759> outperform<00:01:32.439> all<00:01:32.560> of<00:01:32.720> them<00:01:32.880> as<00:01:33.000> a 00:01:33.109 --> 00:01:33.119 align:start position:0% magically outperform all of them as a 00:01:33.119 --> 00:01:35.910 align:start position:0% magically outperform all of them as a general<00:01:33.479> purpose<00:01:33.880> architecture<00:01:34.640> right<00:01:35.439> and 00:01:35.910 --> 00:01:35.920 align:start position:0% general purpose architecture right and 00:01:35.920 --> 00:01:39.030 align:start position:0% general purpose architecture right and snarks<00:01:36.520> you<00:01:37.079> have<00:01:37.280> done<00:01:37.960> basically<00:01:38.520> exactly 00:01:39.030 --> 00:01:39.040 align:start position:0% snarks you have done basically exactly 00:01:39.040 --> 00:01:41.069 align:start position:0% snarks you have done basically exactly that<00:01:39.240> same<00:01:39.479> thing<00:01:39.759> for<00:01:40.079> cryptography<00:01:40.840> right 00:01:41.069 --> 00:01:41.079 align:start position:0% that same thing for cryptography right 00:01:41.079 --> 00:01:42.630 align:start position:0% that same thing for cryptography right so<00:01:41.880> we've 00:01:42.630 --> 00:01:42.640 align:start position:0% so we've 00:01:42.640 --> 00:01:46.190 align:start position:0% so we've seen<00:01:43.640> ring<00:01:44.159> signatures<00:01:45.159> we've<00:01:45.320> seen<00:01:45.600> range 00:01:46.190 --> 00:01:46.200 align:start position:0% seen ring signatures we've seen range 00:01:46.200 --> 00:01:48.950 align:start position:0% seen ring signatures we've seen range proofs<00:01:47.040> um<00:01:47.159> you<00:01:47.280> know<00:01:47.439> we've<00:01:47.600> seen<00:01:48.360> all<00:01:48.680> kinds 00:01:48.950 --> 00:01:48.960 align:start position:0% proofs um you know we've seen all kinds 00:01:48.960 --> 00:01:50.870 align:start position:0% proofs um you know we've seen all kinds of<00:01:49.159> different<00:01:49.439> use<00:01:49.759> cases<00:01:50.240> just<00:01:50.439> basically 00:01:50.870 --> 00:01:50.880 align:start position:0% of different use cases just basically 00:01:50.880 --> 00:01:54.030 align:start position:0% of different use cases just basically swept<00:01:51.360> away<00:01:51.799> and<00:01:52.399> subsumed<00:01:53.200> under<00:01:53.600> this 00:01:54.030 --> 00:01:54.040 align:start position:0% swept away and subsumed under this 00:01:54.040 --> 00:01:56.910 align:start position:0% swept away and subsumed under this umbrella<00:01:54.680> of<00:01:55.280> I<00:01:55.399> am<00:01:55.640> just<00:01:55.840> making<00:01:56.200> a<00:01:56.439> proof 00:01:56.910 --> 00:01:56.920 align:start position:0% umbrella of I am just making a proof 00:01:56.920 --> 00:01:59.590 align:start position:0% umbrella of I am just making a proof about<00:01:57.680> a<00:01:57.920> computation<00:01:58.600> about<00:01:58.880> private<00:01:59.200> data 00:01:59.590 --> 00:01:59.600 align:start position:0% about a computation about private data 00:01:59.600 --> 00:02:01.950 align:start position:0% about a computation about private data that<00:01:59.719> is<00:01:59.920> is<00:02:00.119> expressed<00:02:00.799> as<00:02:01.399> some<00:02:01.640> kind<00:02:01.799> of 00:02:01.950 --> 00:02:01.960 align:start position:0% that is is expressed as some kind of 00:02:01.960 --> 00:02:03.950 align:start position:0% that is is expressed as some kind of standard<00:02:02.479> um<00:02:02.680> arithmetic<00:02:03.320> circuit<00:02:03.680> in<00:02:03.799> a 00:02:03.950 --> 00:02:03.960 align:start position:0% standard um arithmetic circuit in a 00:02:03.960 --> 00:02:07.350 align:start position:0% standard um arithmetic circuit in a standardized<00:02:04.640> language<00:02:05.640> and<00:02:06.399> that<00:02:06.640> you<00:02:06.759> can 00:02:07.350 --> 00:02:07.360 align:start position:0% standardized language and that you can 00:02:07.360 --> 00:02:09.229 align:start position:0% standardized language and that you can you<00:02:07.479> can<00:02:07.640> make<00:02:07.799> a<00:02:07.960> fair<00:02:08.160> a<00:02:08.239> fairly<00:02:08.560> short<00:02:08.879> proof 00:02:09.229 --> 00:02:09.239 align:start position:0% you can make a fair a fairly short proof 00:02:09.239 --> 00:02:10.710 align:start position:0% you can make a fair a fairly short proof that<00:02:09.399> just<00:02:09.599> proves<00:02:09.959> whatever<00:02:10.280> claim<00:02:10.520> you<00:02:10.640> want 00:02:10.710 --> 00:02:10.720 align:start position:0% that just proves whatever claim you want 00:02:10.720 --> 00:02:13.070 align:start position:0% that just proves whatever claim you want to<00:02:10.840> prove<00:02:11.120> about<00:02:11.440> private<00:02:11.959> information<00:02:12.959> that 00:02:13.070 --> 00:02:13.080 align:start position:0% to prove about private information that 00:02:13.080 --> 00:02:15.670 align:start position:0% to prove about private information that you<00:02:13.400> have<00:02:13.680> in<00:02:13.920> zero<00:02:14.239> knowledge<00:02:15.000> and<00:02:15.239> oh<00:02:15.480> at<00:02:15.599> the 00:02:15.670 --> 00:02:15.680 align:start position:0% you have in zero knowledge and oh at the 00:02:15.680 --> 00:02:17.750 align:start position:0% you have in zero knowledge and oh at the same<00:02:16.000> time<00:02:16.160> it<00:02:16.319> also<00:02:16.560> solves<00:02:16.920> scalability 00:02:17.750 --> 00:02:17.760 align:start position:0% same time it also solves scalability 00:02:17.760 --> 00:02:19.910 align:start position:0% same time it also solves scalability right<00:02:18.280> so<00:02:18.440> it's<00:02:18.599> this<00:02:18.879> extremely<00:02:19.480> powerful 00:02:19.910 --> 00:02:19.920 align:start position:0% right so it's this extremely powerful 00:02:19.920 --> 00:02:22.070 align:start position:0% right so it's this extremely powerful general<00:02:20.280> purpose<00:02:20.640> technology<00:02:21.400> and<00:02:21.959> the 00:02:22.070 --> 00:02:22.080 align:start position:0% general purpose technology and the 00:02:22.080 --> 00:02:24.309 align:start position:0% general purpose technology and the ethereum<00:02:22.560> road<00:02:22.800> map<00:02:23.120> has<00:02:23.400> already<00:02:23.879> changed 00:02:24.309 --> 00:02:24.319 align:start position:0% ethereum road map has already changed 00:02:24.319 --> 00:02:27.190 align:start position:0% ethereum road map has already changed completely<00:02:24.920> as<00:02:25.040> a<00:02:25.239> result<00:02:25.840> right<00:02:26.080> so<00:02:26.879> if<00:02:27.000> you 00:02:27.190 --> 00:02:27.200 align:start position:0% completely as a result right so if you 00:02:27.200 --> 00:02:29.309 align:start position:0% completely as a result right so if you look<00:02:27.400> at<00:02:27.640> the<00:02:28.080> plans<00:02:28.400> that<00:02:28.519> ethereum<00:02:29.040> has<00:02:29.200> for 00:02:29.309 --> 00:02:29.319 align:start position:0% look at the plans that ethereum has for 00:02:29.319 --> 00:02:32.270 align:start position:0% look at the plans that ethereum has for the<00:02:29.400> next<00:02:29.599> few<00:02:30.120> years<00:02:31.120> all<00:02:31.280> of<00:02:31.400> the<00:02:31.519> far<00:02:31.800> future 00:02:32.270 --> 00:02:32.280 align:start position:0% the next few years all of the far future 00:02:32.280 --> 00:02:34.869 align:start position:0% the next few years all of the far future stuff<00:02:32.599> really<00:02:33.120> uh<00:02:33.519> depends<00:02:34.040> on<00:02:34.239> sonars 00:02:34.869 --> 00:02:34.879 align:start position:0% stuff really uh depends on sonars 00:02:34.879 --> 00:02:37.589 align:start position:0% stuff really uh depends on sonars existing<00:02:35.519> the<00:02:35.920> uh<00:02:36.319> road<00:02:36.599> map<00:02:36.800> for<00:02:37.120> replacing 00:02:37.589 --> 00:02:37.599 align:start position:0% existing the uh road map for replacing 00:02:37.599 --> 00:02:39.670 align:start position:0% existing the uh road map for replacing veral<00:02:38.000> trees<00:02:38.360> with<00:02:38.560> something<00:02:38.879> Quantum<00:02:39.319> safe 00:02:39.670 --> 00:02:39.680 align:start position:0% veral trees with something Quantum safe 00:02:39.680 --> 00:02:43.390 align:start position:0% veral trees with something Quantum safe depends<00:02:39.959> on<00:02:40.239> Starks<00:02:41.239> the<00:02:41.760> uh<00:02:42.400> road<00:02:42.720> map<00:02:43.000> for 00:02:43.390 --> 00:02:43.400 align:start position:0% depends on Starks the uh road map for 00:02:43.400 --> 00:02:46.309 align:start position:0% depends on Starks the uh road map for long-term<00:02:44.000> full<00:02:44.440> light<00:02:44.720> clients<00:02:45.519> depends<00:02:45.959> on 00:02:46.309 --> 00:02:46.319 align:start position:0% long-term full light clients depends on 00:02:46.319 --> 00:02:50.149 align:start position:0% long-term full light clients depends on Starks<00:02:47.319> the<00:02:48.000> uh<00:02:48.480> and<00:02:48.720> rollups<00:02:49.560> started<00:02:49.920> off 00:02:50.149 --> 00:02:50.159 align:start position:0% Starks the uh and rollups started off 00:02:50.159 --> 00:02:52.309 align:start position:0% Starks the uh and rollups started off being<00:02:50.480> optimistic<00:02:51.040> rollups<00:02:51.519> and<00:02:51.680> now<00:02:51.840> there's 00:02:52.309 --> 00:02:52.319 align:start position:0% being optimistic rollups and now there's 00:02:52.319 --> 00:02:55.710 align:start position:0% being optimistic rollups and now there's ZK<00:02:52.760> rollups<00:02:53.239> and<00:02:53.519> they<00:02:53.959> demand<00:02:54.319> on<00:02:54.519> Starks<00:02:55.519> or 00:02:55.710 --> 00:02:55.720 align:start position:0% ZK rollups and they demand on Starks or 00:02:55.720 --> 00:02:58.790 align:start position:0% ZK rollups and they demand on Starks or depend<00:02:56.040> on<00:02:56.200> Starks<00:02:57.080> they're<00:02:57.440> um<00:02:57.560> also<00:02:58.000> plasma 00:02:58.790 --> 00:02:58.800 align:start position:0% depend on Starks they're um also plasma 00:02:58.800 --> 00:03:01.949 align:start position:0% depend on Starks they're um also plasma before<00:02:59.400> sonar<00:03:00.159> it<00:03:00.319> was<00:03:00.640> a<00:03:01.159> a<00:03:01.319> very<00:03:01.599> limited 00:03:01.949 --> 00:03:01.959 align:start position:0% before sonar it was a a very limited 00:03:01.959 --> 00:03:03.910 align:start position:0% before sonar it was a a very limited architecture<00:03:02.599> that<00:03:03.120> that<00:03:03.239> could<00:03:03.400> only<00:03:03.599> do<00:03:03.799> a 00:03:03.910 --> 00:03:03.920 align:start position:0% architecture that that could only do a 00:03:03.920 --> 00:03:06.390 align:start position:0% architecture that that could only do a little<00:03:04.159> bit<00:03:04.720> after<00:03:04.959> snarks<00:03:05.480> it<00:03:05.680> just<00:03:05.879> be<00:03:06.200> it 00:03:06.390 --> 00:03:06.400 align:start position:0% little bit after snarks it just be it 00:03:06.400 --> 00:03:07.949 align:start position:0% little bit after snarks it just be it actually<00:03:06.760> has<00:03:06.959> become<00:03:07.319> something<00:03:07.640> quite<00:03:07.840> a 00:03:07.949 --> 00:03:07.959 align:start position:0% actually has become something quite a 00:03:07.959 --> 00:03:11.309 align:start position:0% actually has become something quite a bit<00:03:08.080> more<00:03:08.280> powerful<00:03:09.400> so<00:03:10.400> snarks<00:03:10.879> have<00:03:11.080> really 00:03:11.309 --> 00:03:11.319 align:start position:0% bit more powerful so snarks have really 00:03:11.319 --> 00:03:13.750 align:start position:0% bit more powerful so snarks have really overturned<00:03:12.000> everything<00:03:12.640> and<00:03:13.239> in<00:03:13.360> a<00:03:13.480> lot<00:03:13.599> of 00:03:13.750 --> 00:03:13.760 align:start position:0% overturned everything and in a lot of 00:03:13.760 --> 00:03:15.589 align:start position:0% overturned everything and in a lot of ways<00:03:14.040> they've<00:03:14.360> also<00:03:14.680> simplified<00:03:15.239> a<00:03:15.319> lot<00:03:15.440> of 00:03:15.589 --> 00:03:15.599 align:start position:0% ways they've also simplified a lot of 00:03:15.599 --> 00:03:18.270 align:start position:0% ways they've also simplified a lot of things<00:03:16.040> right<00:03:16.400> like<00:03:17.400> if<00:03:17.519> you<00:03:17.680> remember<00:03:18.040> trying 00:03:18.270 --> 00:03:18.280 align:start position:0% things right like if you remember trying 00:03:18.280 --> 00:03:21.229 align:start position:0% things right like if you remember trying to<00:03:18.480> design<00:03:18.959> protocols<00:03:19.560> in<00:03:19.680> the<00:03:19.840> prear<00:03:20.640> era 00:03:21.229 --> 00:03:21.239 align:start position:0% to design protocols in the prear era 00:03:21.239 --> 00:03:22.990 align:start position:0% to design protocols in the prear era like<00:03:21.360> you<00:03:21.599> really<00:03:21.840> need<00:03:22.400> specialized 00:03:22.990 --> 00:03:23.000 align:start position:0% like you really need specialized 00:03:23.000 --> 00:03:24.550 align:start position:0% like you really need specialized cryptographers<00:03:23.799> putting<00:03:24.040> in<00:03:24.159> a<00:03:24.280> lot<00:03:24.400> of 00:03:24.550 --> 00:03:24.560 align:start position:0% cryptographers putting in a lot of 00:03:24.560 --> 00:03:27.110 align:start position:0% cryptographers putting in a lot of specialized<00:03:25.239> cryptographic<00:03:26.120> work<00:03:26.640> to<00:03:26.840> make 00:03:27.110 --> 00:03:27.120 align:start position:0% specialized cryptographic work to make 00:03:27.120 --> 00:03:29.990 align:start position:0% specialized cryptographic work to make specific<00:03:27.560> applications<00:03:28.239> work<00:03:28.599> whether<00:03:28.879> it's 00:03:29.990 --> 00:03:30.000 align:start position:0% specific applications work whether it's 00:03:30.000 --> 00:03:32.110 align:start position:0% specific applications work whether it's proofs<00:03:30.400> or<00:03:30.560> it's<00:03:30.799> ring<00:03:31.080> signatures<00:03:31.760> or<00:03:31.879> it's 00:03:32.110 --> 00:03:32.120 align:start position:0% proofs or it's ring signatures or it's 00:03:32.120 --> 00:03:34.630 align:start position:0% proofs or it's ring signatures or it's linkable<00:03:32.599> ring<00:03:32.879> signatures<00:03:33.879> or<00:03:34.040> it's<00:03:34.239> chami 00:03:34.630 --> 00:03:34.640 align:start position:0% linkable ring signatures or it's chami 00:03:34.640 --> 00:03:36.070 align:start position:0% linkable ring signatures or it's chami and<00:03:34.799> blinding<00:03:35.400> every<00:03:35.599> one<00:03:35.720> of<00:03:35.879> these 00:03:36.070 --> 00:03:36.080 align:start position:0% and blinding every one of these 00:03:36.080 --> 00:03:38.470 align:start position:0% and blinding every one of these Primitives<00:03:36.599> would<00:03:36.840> require<00:03:37.519> a<00:03:37.720> cryptographic 00:03:38.470 --> 00:03:38.480 align:start position:0% Primitives would require a cryptographic 00:03:38.480 --> 00:03:40.309 align:start position:0% Primitives would require a cryptographic professional<00:03:38.920> to<00:03:39.080> do<00:03:39.200> a<00:03:39.319> whole<00:03:39.480> bunch<00:03:39.680> of<00:03:39.840> work 00:03:40.309 --> 00:03:40.319 align:start position:0% professional to do a whole bunch of work 00:03:40.319 --> 00:03:42.190 align:start position:0% professional to do a whole bunch of work and<00:03:40.519> even<00:03:40.840> still<00:03:41.200> you'd<00:03:41.400> only<00:03:41.640> make<00:03:41.840> something 00:03:42.190 --> 00:03:42.200 align:start position:0% and even still you'd only make something 00:03:42.200 --> 00:03:44.070 align:start position:0% and even still you'd only make something that<00:03:42.319> works<00:03:42.560> for<00:03:42.760> a<00:03:42.879> few<00:03:43.159> particular<00:03:43.680> sets<00:03:43.879> of 00:03:44.070 --> 00:03:44.080 align:start position:0% that works for a few particular sets of 00:03:44.080 --> 00:03:47.110 align:start position:0% that works for a few particular sets of applications<00:03:45.239> snarks<00:03:46.239> indiv<00:03:46.720> non- 00:03:47.110 --> 00:03:47.120 align:start position:0% applications snarks indiv non- 00:03:47.120 --> 00:03:48.910 align:start position:0% applications snarks indiv non- cryptographers<00:03:47.920> can<00:03:48.120> just<00:03:48.319> go<00:03:48.480> in<00:03:48.640> and<00:03:48.799> they 00:03:48.910 --> 00:03:48.920 align:start position:0% cryptographers can just go in and they 00:03:48.920 --> 00:03:51.229 align:start position:0% cryptographers can just go in and they can<00:03:49.080> do<00:03:49.280> their<00:03:49.480> thing<00:03:49.720> put<00:03:49.879> in<00:03:50.040> their<00:03:50.239> code<00:03:50.920> and 00:03:51.229 --> 00:03:51.239 align:start position:0% can do their thing put in their code and 00:03:51.239 --> 00:03:54.990 align:start position:0% can do their thing put in their code and it<00:03:51.480> just<00:03:51.680> works<00:03:52.319> next<00:03:52.959> slide<00:03:53.959> so<00:03:54.640> let's<00:03:54.840> talk 00:03:54.990 --> 00:03:55.000 align:start position:0% it just works next slide so let's talk 00:03:55.000 --> 00:03:56.470 align:start position:0% it just works next slide so let's talk about<00:03:55.200> what<00:03:55.319> happens<00:03:55.720> what<00:03:55.879> happens<00:03:56.200> Beyond 00:03:56.470 --> 00:03:56.480 align:start position:0% about what happens what happens Beyond 00:03:56.480 --> 00:04:00.110 align:start position:0% about what happens what happens Beyond snarks<00:03:57.239> so<00:03:58.040> in<00:03:58.439> one<00:03:58.560> of<00:03:58.760> my<00:03:59.159> recent<00:03:59.439> posts 00:04:00.110 --> 00:04:00.120 align:start position:0% snarks so in one of my recent posts 00:04:00.120 --> 00:04:01.710 align:start position:0% snarks so in one of my recent posts talking<00:04:00.439> about<00:04:00.640> the<00:04:00.760> future<00:04:01.040> of<00:04:01.159> the<00:04:01.239> ethereum 00:04:01.710 --> 00:04:01.720 align:start position:0% talking about the future of the ethereum 00:04:01.720 --> 00:04:04.949 align:start position:0% talking about the future of the ethereum protocol<00:04:02.120> and<00:04:02.280> made<00:04:02.519> this<00:04:03.280> analogy<00:04:03.840> to<00:04:04.239> these 00:04:04.949 --> 00:04:04.959 align:start position:0% protocol and made this analogy to these 00:04:04.959 --> 00:04:07.750 align:start position:0% protocol and made this analogy to these Egyptian<00:04:05.480> god<00:04:05.760> cards<00:04:06.079> from<00:04:06.280> yui<00:04:06.879> right<00:04:07.079> these 00:04:07.750 --> 00:04:07.760 align:start position:0% Egyptian god cards from yui right these 00:04:07.760 --> 00:04:10.069 align:start position:0% Egyptian god cards from yui right these like<00:04:08.000> extremely<00:04:08.640> powerful<00:04:09.239> monsters<00:04:09.840> that 00:04:10.069 --> 00:04:10.079 align:start position:0% like extremely powerful monsters that 00:04:10.079 --> 00:04:13.789 align:start position:0% like extremely powerful monsters that just<00:04:10.959> have<00:04:11.239> these<00:04:11.840> incredible<00:04:12.840> Powers<00:04:13.480> right 00:04:13.789 --> 00:04:13.799 align:start position:0% just have these incredible Powers right 00:04:13.799 --> 00:04:16.629 align:start position:0% just have these incredible Powers right and<00:04:14.200> uh<00:04:14.400> you<00:04:14.519> know<00:04:14.720> in<00:04:14.920> Yu-Gi-Oh<00:04:15.439> Legend<00:04:16.120> these 00:04:16.629 --> 00:04:16.639 align:start position:0% and uh you know in Yu-Gi-Oh Legend these 00:04:16.639 --> 00:04:19.310 align:start position:0% and uh you know in Yu-Gi-Oh Legend these cards<00:04:17.000> are<00:04:17.519> so<00:04:17.799> powerful<00:04:18.440> that<00:04:18.600> it's 00:04:19.310 --> 00:04:19.320 align:start position:0% cards are so powerful that it's 00:04:19.320 --> 00:04:21.870 align:start position:0% cards are so powerful that it's physically<00:04:19.840> dangerous<00:04:20.359> to<00:04:20.600> actually<00:04:21.519> attempt 00:04:21.870 --> 00:04:21.880 align:start position:0% physically dangerous to actually attempt 00:04:21.880 --> 00:04:23.590 align:start position:0% physically dangerous to actually attempt to<00:04:22.040> create<00:04:22.320> one<00:04:22.479> of<00:04:22.639> them<00:04:22.919> and<00:04:23.199> you're<00:04:23.360> not 00:04:23.590 --> 00:04:23.600 align:start position:0% to create one of them and you're not 00:04:23.600 --> 00:04:25.430 align:start position:0% to create one of them and you're not actually<00:04:23.960> allowed<00:04:24.240> to<00:04:24.360> use<00:04:24.560> them<00:04:24.720> in<00:04:24.840> duels 00:04:25.430 --> 00:04:25.440 align:start position:0% actually allowed to use them in duels 00:04:25.440 --> 00:04:28.070 align:start position:0% actually allowed to use them in duels right<00:04:25.800> and<00:04:26.240> uh<00:04:26.960> like<00:04:27.120> these<00:04:27.280> three<00:04:27.479> protocols 00:04:28.070 --> 00:04:28.080 align:start position:0% right and uh like these three protocols 00:04:28.080 --> 00:04:30.590 align:start position:0% right and uh like these three protocols I<00:04:28.199> think<00:04:28.479> are<00:04:29.120> exactly<00:04:29.720> that<00:04:29.919> powerful<00:04:30.360> in<00:04:30.479> the 00:04:30.590 --> 00:04:30.600 align:start position:0% I think are exactly that powerful in the 00:04:30.600 --> 00:04:33.310 align:start position:0% I think are exactly that powerful in the same<00:04:30.840> way<00:04:31.199> right<00:04:31.400> so<00:04:32.080> we<00:04:32.199> talked<00:04:32.440> about<00:04:32.639> sarcs 00:04:33.310 --> 00:04:33.320 align:start position:0% same way right so we talked about sarcs 00:04:33.320 --> 00:04:35.270 align:start position:0% same way right so we talked about sarcs but<00:04:33.680> let's<00:04:33.880> talk<00:04:34.080> about<00:04:34.320> the<00:04:34.479> other<00:04:34.720> two<00:04:34.960> items 00:04:35.270 --> 00:04:35.280 align:start position:0% but let's talk about the other two items 00:04:35.280 --> 00:04:36.749 align:start position:0% but let's talk about the other two items in<00:04:35.400> the<00:04:35.600> series<00:04:36.039> right<00:04:36.160> so<00:04:36.360> the<00:04:36.440> one<00:04:36.560> in<00:04:36.639> the 00:04:36.749 --> 00:04:36.759 align:start position:0% in the series right so the one in the 00:04:36.759 --> 00:04:39.310 align:start position:0% in the series right so the one in the middle<00:04:37.240> is<00:04:37.600> uh<00:04:38.400> fully<00:04:38.759> homomorphic 00:04:39.310 --> 00:04:39.320 align:start position:0% middle is uh fully homomorphic 00:04:39.320 --> 00:04:41.590 align:start position:0% middle is uh fully homomorphic encryption<00:04:40.160> fully<00:04:40.479> homomorphic<00:04:41.000> encryption 00:04:41.590 --> 00:04:41.600 align:start position:0% encryption fully homomorphic encryption 00:04:41.600 --> 00:04:45.350 align:start position:0% encryption fully homomorphic encryption lets<00:04:41.919> you<00:04:42.680> do<00:04:43.160> any<00:04:43.520> computation<00:04:44.440> on<00:04:44.759> encrypted 00:04:45.350 --> 00:04:45.360 align:start position:0% lets you do any computation on encrypted 00:04:45.360 --> 00:04:47.590 align:start position:0% lets you do any computation on encrypted data<00:04:46.240> without<00:04:46.600> being<00:04:46.840> able<00:04:47.039> to<00:04:47.240> learn 00:04:47.590 --> 00:04:47.600 align:start position:0% data without being able to learn 00:04:47.600 --> 00:04:50.150 align:start position:0% data without being able to learn anything<00:04:48.000> about<00:04:48.280> that<00:04:48.479> data<00:04:49.280> this<00:04:49.440> is 00:04:50.150 --> 00:04:50.160 align:start position:0% anything about that data this is 00:04:50.160 --> 00:04:52.350 align:start position:0% anything about that data this is extremely<00:04:50.759> powerful<00:04:51.280> this<00:04:51.680> basically<00:04:52.080> lets 00:04:52.350 --> 00:04:52.360 align:start position:0% extremely powerful this basically lets 00:04:52.360 --> 00:04:54.590 align:start position:0% extremely powerful this basically lets you<00:04:52.639> take<00:04:53.080> a<00:04:53.320> very<00:04:53.680> wide<00:04:54.039> class<00:04:54.360> of 00:04:54.590 --> 00:04:54.600 align:start position:0% you take a very wide class of 00:04:54.600 --> 00:04:57.029 align:start position:0% you take a very wide class of applications<00:04:55.600> and<00:04:55.800> just<00:04:56.080> Express<00:04:56.520> them<00:04:56.800> very 00:04:57.029 --> 00:04:57.039 align:start position:0% applications and just Express them very 00:04:57.039 --> 00:05:00.189 align:start position:0% applications and just Express them very easily<00:04:57.479> as<00:04:57.600> an<00:04:57.759> FHA<00:04:58.320> problem<00:04:59.240> I<00:04:59.400> have<00:04:59.840> private 00:05:00.189 --> 00:05:00.199 align:start position:0% easily as an FHA problem I have private 00:05:00.199 --> 00:05:04.670 align:start position:0% easily as an FHA problem I have private data<00:05:00.960> and<00:05:01.360> I<00:05:01.560> want<00:05:02.039> you<00:05:02.400> to<00:05:03.120> do<00:05:03.440> an<00:05:03.600> algor<00:05:04.479> run 00:05:04.670 --> 00:05:04.680 align:start position:0% data and I want you to do an algor run 00:05:04.680 --> 00:05:06.550 align:start position:0% data and I want you to do an algor run some<00:05:05.000> algorithm<00:05:05.520> on<00:05:05.639> the<00:05:05.800> private<00:05:06.120> data<00:05:06.360> and 00:05:06.550 --> 00:05:06.560 align:start position:0% some algorithm on the private data and 00:05:06.560 --> 00:05:09.189 align:start position:0% some algorithm on the private data and give<00:05:06.680> me<00:05:06.880> the<00:05:07.080> results<00:05:07.960> without<00:05:08.680> um<00:05:08.919> actually 00:05:09.189 --> 00:05:09.199 align:start position:0% give me the results without um actually 00:05:09.199 --> 00:05:11.830 align:start position:0% give me the results without um actually learning<00:05:09.639> my<00:05:09.840> private<00:05:10.160> data<00:05:10.880> that's<00:05:11.039> an<00:05:11.199> FHA 00:05:11.830 --> 00:05:11.840 align:start position:0% learning my private data that's an FHA 00:05:11.840 --> 00:05:14.670 align:start position:0% learning my private data that's an FHA problem<00:05:12.479> um<00:05:12.639> I<00:05:12.759> want<00:05:13.360> to<00:05:13.600> be<00:05:13.720> able<00:05:13.919> to<00:05:14.120> train<00:05:14.440> on 00:05:14.670 --> 00:05:14.680 align:start position:0% problem um I want to be able to train on 00:05:14.680 --> 00:05:17.150 align:start position:0% problem um I want to be able to train on people's<00:05:15.320> data<00:05:15.680> without<00:05:15.840> learning<00:05:16.240> the<00:05:16.400> data 00:05:17.150 --> 00:05:17.160 align:start position:0% people's data without learning the data 00:05:17.160 --> 00:05:19.830 align:start position:0% people's data without learning the data that's<00:05:17.680> also<00:05:17.880> an<00:05:18.039> FH<00:05:18.600> problem<00:05:19.160> you<00:05:19.319> do<00:05:19.520> need<00:05:19.720> a 00:05:19.830 --> 00:05:19.840 align:start position:0% that's also an FH problem you do need a 00:05:19.840 --> 00:05:21.590 align:start position:0% that's also an FH problem you do need a little<00:05:20.000> bit<00:05:20.120> of<00:05:20.319> cleverness<00:05:20.880> to<00:05:21.039> make<00:05:21.240> sure 00:05:21.590 --> 00:05:21.600 align:start position:0% little bit of cleverness to make sure 00:05:21.600 --> 00:05:23.469 align:start position:0% little bit of cleverness to make sure that<00:05:22.199> like<00:05:22.360> the<00:05:22.520> thing<00:05:22.800> that<00:05:22.919> the<00:05:23.080> model 00:05:23.469 --> 00:05:23.479 align:start position:0% that like the thing that the model 00:05:23.479 --> 00:05:25.870 align:start position:0% that like the thing that the model actually<00:05:23.840> learns<00:05:24.280> about<00:05:24.520> you<00:05:24.800> doesn't<00:05:25.400> uh 00:05:25.870 --> 00:05:25.880 align:start position:0% actually learns about you doesn't uh 00:05:25.880 --> 00:05:27.629 align:start position:0% actually learns about you doesn't uh actually<00:05:26.240> itself<00:05:26.639> reveal<00:05:27.039> your<00:05:27.199> data<00:05:27.479> and 00:05:27.629 --> 00:05:27.639 align:start position:0% actually itself reveal your data and 00:05:27.639 --> 00:05:29.390 align:start position:0% actually itself reveal your data and like<00:05:27.840> that's<00:05:27.960> a<00:05:28.120> differential<00:05:28.680> privacy<00:05:29.120> thing 00:05:29.390 --> 00:05:29.400 align:start position:0% like that's a differential privacy thing 00:05:29.400 --> 00:05:31.670 align:start position:0% like that's a differential privacy thing right<00:05:29.759> but<00:05:30.199> the<00:05:30.360> bulk<00:05:30.639> of<00:05:30.759> the<00:05:30.919> hardness<00:05:31.440> like 00:05:31.670 --> 00:05:31.680 align:start position:0% right but the bulk of the hardness like 00:05:31.680 --> 00:05:33.749 align:start position:0% right but the bulk of the hardness like actually<00:05:31.960> is<00:05:32.280> just<00:05:32.479> captured<00:05:32.919> by<00:05:33.039> the<00:05:33.199> FH 00:05:33.749 --> 00:05:33.759 align:start position:0% actually is just captured by the FH 00:05:33.759 --> 00:05:37.510 align:start position:0% actually is just captured by the FH piece<00:05:34.759> if<00:05:35.199> uh<00:05:35.560> you<00:05:35.800> want<00:05:36.160> many<00:05:36.520> kinds<00:05:36.840> of<00:05:37.240> uh 00:05:37.510 --> 00:05:37.520 align:start position:0% piece if uh you want many kinds of uh 00:05:37.520 --> 00:05:39.590 align:start position:0% piece if uh you want many kinds of uh like<00:05:37.800> privacy<00:05:38.280> pres<00:05:38.639> uh<00:05:39.080> preserving 00:05:39.590 --> 00:05:39.600 align:start position:0% like privacy pres uh preserving 00:05:39.600 --> 00:05:42.110 align:start position:0% like privacy pres uh preserving architectures<00:05:40.319> privacy<00:05:40.680> preserving<00:05:41.160> Dows<00:05:41.919> as 00:05:42.110 --> 00:05:42.120 align:start position:0% architectures privacy preserving Dows as 00:05:42.120 --> 00:05:43.710 align:start position:0% architectures privacy preserving Dows as long<00:05:42.360> as<00:05:42.520> you're<00:05:42.720> willing<00:05:43.000> to<00:05:43.280> accept<00:05:43.560> a 00:05:43.710 --> 00:05:43.720 align:start position:0% long as you're willing to accept a 00:05:43.720 --> 00:05:45.990 align:start position:0% long as you're willing to accept a certain<00:05:44.120> certain<00:05:44.360> trust<00:05:44.840> assumptions<00:05:45.840> it 00:05:45.990 --> 00:05:46.000 align:start position:0% certain certain trust assumptions it 00:05:46.000 --> 00:05:49.830 align:start position:0% certain certain trust assumptions it becomes<00:05:46.319> an<00:05:46.440> FH<00:05:46.960> problem<00:05:47.479> f<00:05:48.039> is<00:05:48.560> like<00:05:48.840> actually 00:05:49.830 --> 00:05:49.840 align:start position:0% becomes an FH problem f is like actually 00:05:49.840 --> 00:05:51.950 align:start position:0% becomes an FH problem f is like actually an<00:05:50.160> incredibly<00:05:50.680> powerful<00:05:51.120> technology 00:05:51.950 --> 00:05:51.960 align:start position:0% an incredibly powerful technology 00:05:51.960 --> 00:05:53.710 align:start position:0% an incredibly powerful technology another<00:05:52.280> thing<00:05:52.479> that<00:05:52.600> it<00:05:52.720> gives<00:05:52.919> you<00:05:53.199> actually 00:05:53.710 --> 00:05:53.720 align:start position:0% another thing that it gives you actually 00:05:53.720 --> 00:05:56.309 align:start position:0% another thing that it gives you actually is<00:05:54.120> uh<00:05:54.639> uh<00:05:55.240> it<00:05:55.360> gives<00:05:55.560> you<00:05:56.000> private 00:05:56.309 --> 00:05:56.319 align:start position:0% is uh uh it gives you private 00:05:56.319 --> 00:05:58.230 align:start position:0% is uh uh it gives you private information<00:05:56.800> retrieval<00:05:57.360> so<00:05:57.560> the<00:05:57.720> ability<00:05:58.080> to 00:05:58.230 --> 00:05:58.240 align:start position:0% information retrieval so the ability to 00:05:58.240 --> 00:06:00.189 align:start position:0% information retrieval so the ability to make<00:05:58.440> queries<00:05:58.880> against<00:05:59.120> a<00:05:59.240> database<00:05:59.960> without 00:06:00.189 --> 00:06:00.199 align:start position:0% make queries against a database without 00:06:00.199 --> 00:06:01.909 align:start position:0% make queries against a database without the<00:06:00.360> database<00:06:00.840> learning<00:06:01.280> what<00:06:01.360> you're<00:06:01.600> asking 00:06:01.909 --> 00:06:01.919 align:start position:0% the database learning what you're asking 00:06:01.919 --> 00:06:05.950 align:start position:0% the database learning what you're asking for<00:06:02.840> and<00:06:03.199> one<00:06:03.520> use<00:06:03.800> case<00:06:03.960> of<00:06:04.240> this<00:06:04.560> is<00:06:05.440> privacy 00:06:05.950 --> 00:06:05.960 align:start position:0% for and one use case of this is privacy 00:06:05.960 --> 00:06:07.469 align:start position:0% for and one use case of this is privacy preserving<00:06:06.479> light<00:06:06.720> clients<00:06:07.199> right<00:06:07.280> so<00:06:07.400> you 00:06:07.469 --> 00:06:07.479 align:start position:0% preserving light clients right so you 00:06:07.479 --> 00:06:09.230 align:start position:0% preserving light clients right so you can<00:06:07.599> have<00:06:07.720> an<00:06:07.840> ethereum<00:06:08.240> light<00:06:08.440> clients<00:06:09.120> and 00:06:09.230 --> 00:06:09.240 align:start position:0% can have an ethereum light clients and 00:06:09.240 --> 00:06:11.309 align:start position:0% can have an ethereum light clients and your<00:06:09.440> light<00:06:09.680> clients<00:06:10.080> can<00:06:10.280> go<00:06:10.479> and<00:06:10.759> like<00:06:10.960> ask 00:06:11.309 --> 00:06:11.319 align:start position:0% your light clients can go and like ask 00:06:11.319 --> 00:06:13.830 align:start position:0% your light clients can go and like ask for<00:06:12.319> like<00:06:12.440> some<00:06:12.720> piece<00:06:12.919> of<00:06:13.120> data<00:06:13.520> about 00:06:13.830 --> 00:06:13.840 align:start position:0% for like some piece of data about 00:06:13.840 --> 00:06:16.469 align:start position:0% for like some piece of data about history<00:06:14.639> without<00:06:15.400> the<00:06:15.800> server<00:06:16.240> actually 00:06:16.469 --> 00:06:16.479 align:start position:0% history without the server actually 00:06:16.479 --> 00:06:19.469 align:start position:0% history without the server actually learning<00:06:16.919> what<00:06:17.039> you're<00:06:17.240> asking<00:06:17.560> for<00:06:18.240> so<00:06:19.240> very 00:06:19.469 --> 00:06:19.479 align:start position:0% learning what you're asking for so very 00:06:19.479 --> 00:06:21.749 align:start position:0% learning what you're asking for so very powerful<00:06:20.000> stuff<00:06:20.599> but<00:06:20.800> you<00:06:20.919> know<00:06:21.280> we<00:06:21.440> also<00:06:21.680> have 00:06:21.749 --> 00:06:21.759 align:start position:0% powerful stuff but you know we also have 00:06:21.759 --> 00:06:23.830 align:start position:0% powerful stuff but you know we also have to<00:06:21.919> get<00:06:22.039> to<00:06:22.240> the<00:06:22.440> third<00:06:23.039> Egyptian<00:06:23.599> god 00:06:23.830 --> 00:06:23.840 align:start position:0% to get to the third Egyptian god 00:06:23.840 --> 00:06:26.350 align:start position:0% to get to the third Egyptian god protocol<00:06:24.319> which<00:06:24.440> is<00:06:24.680> alisation<00:06:25.560> right<00:06:26.199> you 00:06:26.350 --> 00:06:26.360 align:start position:0% protocol which is alisation right you 00:06:26.360 --> 00:06:29.110 align:start position:0% protocol which is alisation right you can<00:06:26.680> encrypt<00:06:27.280> a<00:06:27.520> program<00:06:28.280> in<00:06:28.479> such<00:06:28.680> a<00:06:28.840> way<00:06:29.000> that 00:06:29.110 --> 00:06:29.120 align:start position:0% can encrypt a program in such a way that 00:06:29.120 --> 00:06:32.309 align:start position:0% can encrypt a program in such a way that the<00:06:29.240> encrypt<00:06:30.000> program<00:06:30.680> has<00:06:30.919> the<00:06:31.120> exact<00:06:31.639> same 00:06:32.309 --> 00:06:32.319 align:start position:0% the encrypt program has the exact same 00:06:32.319 --> 00:06:34.670 align:start position:0% the encrypt program has the exact same functionality<00:06:33.319> but<00:06:33.759> if<00:06:33.840> you<00:06:34.000> have<00:06:34.160> a<00:06:34.319> copy<00:06:34.560> of 00:06:34.670 --> 00:06:34.680 align:start position:0% functionality but if you have a copy of 00:06:34.680 --> 00:06:36.909 align:start position:0% functionality but if you have a copy of the<00:06:34.800> encrypted<00:06:35.360> program<00:06:35.960> you<00:06:36.080> can<00:06:36.360> learn 00:06:36.909 --> 00:06:36.919 align:start position:0% the encrypted program you can learn 00:06:36.919 --> 00:06:39.110 align:start position:0% the encrypted program you can learn nothing<00:06:37.400> about<00:06:37.720> the<00:06:37.840> internals<00:06:38.319> of<00:06:38.479> it<00:06:38.919> like 00:06:39.110 --> 00:06:39.120 align:start position:0% nothing about the internals of it like 00:06:39.120 --> 00:06:40.870 align:start position:0% nothing about the internals of it like basically<00:06:39.800> yeah<00:06:40.039> except<00:06:40.400> for<00:06:40.639> what<00:06:40.759> the 00:06:40.870 --> 00:06:40.880 align:start position:0% basically yeah except for what the 00:06:40.880 --> 00:06:43.430 align:start position:0% basically yeah except for what the inputs<00:06:41.160> and<00:06:41.280> outputs<00:06:41.639> are<00:06:42.039> now<00:06:42.840> technically 00:06:43.430 --> 00:06:43.440 align:start position:0% inputs and outputs are now technically 00:06:43.440 --> 00:06:46.550 align:start position:0% inputs and outputs are now technically like<00:06:43.639> that<00:06:43.880> exact<00:06:44.400> definition<00:06:45.240> is<00:06:45.840> uh<00:06:46.280> like 00:06:46.550 --> 00:06:46.560 align:start position:0% like that exact definition is uh like 00:06:46.560 --> 00:06:49.309 align:start position:0% like that exact definition is uh like not<00:06:46.840> exactly<00:06:47.319> achievable<00:06:48.039> but<00:06:48.479> like<00:06:48.639> in<00:06:48.880> real 00:06:49.309 --> 00:06:49.319 align:start position:0% not exactly achievable but like in real 00:06:49.319 --> 00:06:51.230 align:start position:0% not exactly achievable but like in real like<00:06:49.440> for<00:06:49.720> any<00:06:49.960> realistic<00:06:50.479> use<00:06:50.759> case<00:06:50.960> it's 00:06:51.230 --> 00:06:51.240 align:start position:0% like for any realistic use case it's 00:06:51.240 --> 00:06:52.990 align:start position:0% like for any realistic use case it's like<00:06:51.400> basically<00:06:51.880> close<00:06:52.199> enough<00:06:52.400> to<00:06:52.599> that 00:06:52.990 --> 00:06:53.000 align:start position:0% like basically close enough to that 00:06:53.000 --> 00:06:57.990 align:start position:0% like basically close enough to that right<00:06:53.479> and<00:06:53.720> so<00:06:54.919> alisation<00:06:55.919> lets<00:06:56.280> you<00:06:56.800> uh<00:06:57.560> be 00:06:57.990 --> 00:06:58.000 align:start position:0% right and so alisation lets you uh be 00:06:58.000 --> 00:07:01.070 align:start position:0% right and so alisation lets you uh be actually<00:06:58.360> do<00:06:58.759> everything<00:06:59.280> that<00:06:59.759> FHA<00:07:00.360> does<00:07:00.919> but 00:07:01.070 --> 00:07:01.080 align:start position:0% actually do everything that FHA does but 00:07:01.080 --> 00:07:02.990 align:start position:0% actually do everything that FHA does but it<00:07:01.240> lets<00:07:01.440> you<00:07:01.639> kick<00:07:01.840> out<00:07:02.240> like<00:07:02.400> even<00:07:02.599> more<00:07:02.800> of 00:07:02.990 --> 00:07:03.000 align:start position:0% it lets you kick out like even more of 00:07:03.000 --> 00:07:05.510 align:start position:0% it lets you kick out like even more of the<00:07:03.800> of<00:07:03.919> the<00:07:04.039> trust<00:07:04.400> assumptions<00:07:05.080> almost<00:07:05.400> all 00:07:05.510 --> 00:07:05.520 align:start position:0% the of the trust assumptions almost all 00:07:05.520 --> 00:07:07.550 align:start position:0% the of the trust assumptions almost all of<00:07:05.680> them<00:07:06.160> you<00:07:06.280> can<00:07:06.440> do<00:07:06.720> Dows<00:07:07.160> that<00:07:07.319> have 00:07:07.550 --> 00:07:07.560 align:start position:0% of them you can do Dows that have 00:07:07.560 --> 00:07:09.749 align:start position:0% of them you can do Dows that have secrets<00:07:08.360> you<00:07:08.520> can<00:07:08.800> you<00:07:08.879> can<00:07:09.080> actually<00:07:09.440> use 00:07:09.749 --> 00:07:09.759 align:start position:0% secrets you can you can actually use 00:07:09.759 --> 00:07:12.469 align:start position:0% secrets you can you can actually use offis<00:07:10.120> cation<00:07:10.479> to<00:07:10.759> implement<00:07:11.759> basically<00:07:12.240> any 00:07:12.469 --> 00:07:12.479 align:start position:0% offis cation to implement basically any 00:07:12.479 --> 00:07:14.430 align:start position:0% offis cation to implement basically any other<00:07:12.759> cryptographic<00:07:13.400> protocol<00:07:14.000> you<00:07:14.080> can<00:07:14.240> use 00:07:14.430 --> 00:07:14.440 align:start position:0% other cryptographic protocol you can use 00:07:14.440 --> 00:07:17.430 align:start position:0% other cryptographic protocol you can use offis<00:07:14.800> cation<00:07:15.120> to<00:07:15.560> implement<00:07:15.919> encrypted<00:07:16.440> mols 00:07:17.430 --> 00:07:17.440 align:start position:0% offis cation to implement encrypted mols 00:07:17.440 --> 00:07:20.270 align:start position:0% offis cation to implement encrypted mols you<00:07:17.560> can<00:07:17.800> use<00:07:18.280> offis<00:07:18.720> cation<00:07:19.080> to<00:07:19.280> implement<00:07:20.080> a 00:07:20.270 --> 00:07:20.280 align:start position:0% you can use offis cation to implement a 00:07:20.280 --> 00:07:23.550 align:start position:0% you can use offis cation to implement a ZK<00:07:20.639> SAR<00:07:21.120> scheme<00:07:21.599> where<00:07:21.919> verifying<00:07:22.560> the<00:07:22.720> SAR 00:07:23.550 --> 00:07:23.560 align:start position:0% ZK SAR scheme where verifying the SAR 00:07:23.560 --> 00:07:26.589 align:start position:0% ZK SAR scheme where verifying the SAR only<00:07:23.800> requires<00:07:24.280> verifying<00:07:24.800> a<00:07:25.280> signature<00:07:26.280> um 00:07:26.589 --> 00:07:26.599 align:start position:0% only requires verifying a signature um 00:07:26.599 --> 00:07:30.510 align:start position:0% only requires verifying a signature um it's<00:07:27.080> it<00:07:27.280> can<00:07:27.720> uh<00:07:28.160> let<00:07:28.520> you<00:07:29.599> Implement<00:07:30.319> like 00:07:30.510 --> 00:07:30.520 align:start position:0% it's it can uh let you Implement like 00:07:30.520 --> 00:07:34.430 align:start position:0% it's it can uh let you Implement like any<00:07:30.800> kind<00:07:31.000> of<00:07:31.440> uh<00:07:31.919> FH<00:07:32.919> MPC<00:07:33.479> two<00:07:33.759> party<00:07:34.080> uh<00:07:34.199> two- 00:07:34.430 --> 00:07:34.440 align:start position:0% any kind of uh FH MPC two party uh two- 00:07:34.440 --> 00:07:38.510 align:start position:0% any kind of uh FH MPC two party uh two- party<00:07:34.919> computation<00:07:35.919> it<00:07:36.479> uh<00:07:37.080> like<00:07:37.520> basically 00:07:38.510 --> 00:07:38.520 align:start position:0% party computation it uh like basically 00:07:38.520 --> 00:07:41.230 align:start position:0% party computation it uh like basically is<00:07:38.680> a<00:07:38.879> superet<00:07:39.400> of<00:07:39.639> like<00:07:40.560> almost<00:07:40.919> everything 00:07:41.230 --> 00:07:41.240 align:start position:0% is a superet of like almost everything 00:07:41.240 --> 00:07:44.629 align:start position:0% is a superet of like almost everything else<00:07:41.720> cryptographic<00:07:42.879> so<00:07:43.879> in<00:07:43.960> order<00:07:44.199> to<00:07:44.360> try<00:07:44.479> to 00:07:44.629 --> 00:07:44.639 align:start position:0% else cryptographic so in order to try to 00:07:44.639 --> 00:07:46.189 align:start position:0% else cryptographic so in order to try to make<00:07:44.800> this<00:07:44.919> a<00:07:45.000> little<00:07:45.159> bit<00:07:45.319> more<00:07:45.560> concrete 00:07:46.189 --> 00:07:46.199 align:start position:0% make this a little bit more concrete 00:07:46.199 --> 00:07:48.110 align:start position:0% make this a little bit more concrete let's<00:07:46.440> look<00:07:46.599> at<00:07:46.759> voting<00:07:47.080> as<00:07:47.199> an<00:07:47.360> example<00:07:47.879> right 00:07:48.110 --> 00:07:48.120 align:start position:0% let's look at voting as an example right 00:07:48.120 --> 00:07:51.230 align:start position:0% let's look at voting as an example right so<00:07:48.919> I<00:07:49.039> think<00:07:49.199> of<00:07:49.400> voting<00:07:49.840> as<00:07:49.960> an<00:07:50.240> example 00:07:51.230 --> 00:07:51.240 align:start position:0% so I think of voting as an example 00:07:51.240 --> 00:07:53.909 align:start position:0% so I think of voting as an example because<00:07:52.080> I<00:07:52.120> mean<00:07:52.400> obviously<00:07:52.919> voting<00:07:53.440> is 00:07:53.909 --> 00:07:53.919 align:start position:0% because I mean obviously voting is 00:07:53.919 --> 00:07:57.430 align:start position:0% because I mean obviously voting is important<00:07:54.319> in<00:07:54.520> itself<00:07:55.440> but<00:07:55.720> also<00:07:56.440> voting<00:07:57.159> um 00:07:57.430 --> 00:07:57.440 align:start position:0% important in itself but also voting um 00:07:57.440 --> 00:08:01.230 align:start position:0% important in itself but also voting um to<00:07:57.680> me<00:07:58.120> is<00:07:58.840> like<00:07:58.960> a<00:07:59.120> stand<00:07:59.720> in<00:08:00.120> for<00:08:00.479> basically 00:08:01.230 --> 00:08:01.240 align:start position:0% to me is like a stand in for basically 00:08:01.240 --> 00:08:04.309 align:start position:0% to me is like a stand in for basically any<00:08:01.639> kind<00:08:01.879> of<00:08:02.360> onchain<00:08:03.120> mechanism<00:08:03.879> that<00:08:04.199> that 00:08:04.309 --> 00:08:04.319 align:start position:0% any kind of onchain mechanism that that 00:08:04.319 --> 00:08:07.909 align:start position:0% any kind of onchain mechanism that that is<00:08:04.520> not<00:08:04.759> purely<00:08:05.120> financialized<00:08:05.960> right<00:08:06.919> so 00:08:07.909 --> 00:08:07.919 align:start position:0% is not purely financialized right so 00:08:07.919 --> 00:08:10.270 align:start position:0% is not purely financialized right so yeah<00:08:08.520> I<00:08:08.599> wrote<00:08:09.159> this<00:08:09.240> is<00:08:09.440> like<00:08:09.639> one<00:08:09.759> of<00:08:09.919> my<00:08:10.039> own 00:08:10.270 --> 00:08:10.280 align:start position:0% yeah I wrote this is like one of my own 00:08:10.280 --> 00:08:12.510 align:start position:0% yeah I wrote this is like one of my own fra<00:08:10.639> uh<00:08:10.800> Frameworks<00:08:11.479> right<00:08:11.680> so<00:08:12.080> I<00:08:12.159> wrote<00:08:12.360> an 00:08:12.510 --> 00:08:12.520 align:start position:0% fra uh Frameworks right so I wrote an 00:08:12.520 --> 00:08:14.629 align:start position:0% fra uh Frameworks right so I wrote an article<00:08:12.919> about<00:08:13.240> this<00:08:13.520> um<00:08:13.680> I<00:08:13.800> think<00:08:14.080> this<00:08:14.280> was 00:08:14.629 --> 00:08:14.639 align:start position:0% article about this um I think this was 00:08:14.639 --> 00:08:16.589 align:start position:0% article about this um I think this was uh<00:08:15.000> the<00:08:15.120> one<00:08:15.360> on<00:08:15.759> Nathan<00:08:16.039> Schneider's 00:08:16.589 --> 00:08:16.599 align:start position:0% uh the one on Nathan Schneider's 00:08:16.599 --> 00:08:18.749 align:start position:0% uh the one on Nathan Schneider's cryptoeconomics<00:08:17.440> or<00:08:17.759> coordination<00:08:18.400> good<00:08:18.560> and 00:08:18.749 --> 00:08:18.759 align:start position:0% cryptoeconomics or coordination good and 00:08:18.759 --> 00:08:21.189 align:start position:0% cryptoeconomics or coordination good and bad<00:08:19.280> but<00:08:19.400> the<00:08:19.560> B<00:08:20.000> what<00:08:20.080> I<00:08:20.240> call<00:08:20.440> financialized 00:08:21.189 --> 00:08:21.199 align:start position:0% bad but the B what I call financialized 00:08:21.199 --> 00:08:24.589 align:start position:0% bad but the B what I call financialized is<00:08:21.479> basically<00:08:22.479> mechanisms<00:08:23.280> where<00:08:23.960> you<00:08:24.240> don't 00:08:24.589 --> 00:08:24.599 align:start position:0% is basically mechanisms where you don't 00:08:24.599 --> 00:08:27.189 align:start position:0% is basically mechanisms where you don't mind<00:08:25.120> people<00:08:25.560> arbitrarily<00:08:26.280> colluding<00:08:27.000> and 00:08:27.189 --> 00:08:27.199 align:start position:0% mind people arbitrarily colluding and 00:08:27.199 --> 00:08:28.710 align:start position:0% mind people arbitrarily colluding and one<00:08:27.400> example<00:08:27.800> of<00:08:27.960> this<00:08:28.120> is<00:08:28.319> like<00:08:28.440> if<00:08:28.520> you 00:08:28.710 --> 00:08:28.720 align:start position:0% one example of this is like if you 00:08:28.720 --> 00:08:32.269 align:start position:0% one example of this is like if you compare<00:08:29.080> money<00:08:29.680> to<00:08:30.080> let's<00:08:30.319> say<00:08:31.039> like<00:08:32.039> like 00:08:32.269 --> 00:08:32.279 align:start position:0% compare money to let's say like like 00:08:32.279 --> 00:08:34.190 align:start position:0% compare money to let's say like like likes<00:08:32.719> on<00:08:32.959> Reddit<00:08:33.399> right<00:08:33.680> if<00:08:33.760> you<00:08:33.880> think<00:08:34.039> of 00:08:34.190 --> 00:08:34.200 align:start position:0% likes on Reddit right if you think of 00:08:34.200 --> 00:08:36.310 align:start position:0% likes on Reddit right if you think of money<00:08:34.880> I<00:08:35.080> give<00:08:35.240> you<00:08:35.360> a<00:08:35.519> dollar<00:08:35.800> in<00:08:35.919> exchange 00:08:36.310 --> 00:08:36.320 align:start position:0% money I give you a dollar in exchange 00:08:36.320 --> 00:08:38.149 align:start position:0% money I give you a dollar in exchange for<00:08:36.479> you<00:08:36.640> giving<00:08:36.880> me<00:08:37.039> a<00:08:37.159> dollar<00:08:37.680> is<00:08:37.839> not<00:08:37.959> a 00:08:38.149 --> 00:08:38.159 align:start position:0% for you giving me a dollar is not a 00:08:38.159 --> 00:08:40.029 align:start position:0% for you giving me a dollar is not a problem<00:08:38.440> it's<00:08:38.640> working<00:08:38.959> as<00:08:39.159> intended<00:08:39.839> on 00:08:40.029 --> 00:08:40.039 align:start position:0% problem it's working as intended on 00:08:40.039 --> 00:08:42.709 align:start position:0% problem it's working as intended on Reddit<00:08:40.320> or<00:08:40.479> on<00:08:40.599> Twitter<00:08:41.320> I<00:08:41.719> upload<00:08:42.159> your<00:08:42.399> post 00:08:42.709 --> 00:08:42.719 align:start position:0% Reddit or on Twitter I upload your post 00:08:42.719 --> 00:08:44.630 align:start position:0% Reddit or on Twitter I upload your post and<00:08:43.000> in<00:08:43.159> exchange<00:08:43.519> for<00:08:43.719> you<00:08:43.880> uploading<00:08:44.440> my 00:08:44.630 --> 00:08:44.640 align:start position:0% and in exchange for you uploading my 00:08:44.640 --> 00:08:47.030 align:start position:0% and in exchange for you uploading my post<00:08:45.240> especially<00:08:45.760> if<00:08:45.880> it<00:08:46.120> got<00:08:46.360> optimized<00:08:46.839> to 00:08:47.030 --> 00:08:47.040 align:start position:0% post especially if it got optimized to 00:08:47.040 --> 00:08:48.829 align:start position:0% post especially if it got optimized to Infinity<00:08:47.680> would<00:08:47.839> just<00:08:48.000> completely<00:08:48.399> break<00:08:48.680> the 00:08:48.829 --> 00:08:48.839 align:start position:0% Infinity would just completely break the 00:08:48.839 --> 00:08:51.230 align:start position:0% Infinity would just completely break the system<00:08:49.360> right<00:08:50.000> and<00:08:50.120> so<00:08:50.480> if<00:08:50.560> you<00:08:50.760> want<00:08:51.040> to 00:08:51.230 --> 00:08:51.240 align:start position:0% system right and so if you want to 00:08:51.240 --> 00:08:52.790 align:start position:0% system right and so if you want to support<00:08:51.600> any<00:08:51.800> kind<00:08:51.920> of<00:08:52.080> mechanism<00:08:52.560> that<00:08:52.640> is 00:08:52.790 --> 00:08:52.800 align:start position:0% support any kind of mechanism that is 00:08:52.800 --> 00:08:54.949 align:start position:0% support any kind of mechanism that is not<00:08:52.959> financialized<00:08:53.880> then<00:08:54.360> like<00:08:54.560> that<00:08:54.680> means 00:08:54.949 --> 00:08:54.959 align:start position:0% not financialized then like that means 00:08:54.959 --> 00:08:57.230 align:start position:0% not financialized then like that means that<00:08:55.120> you<00:08:55.320> have<00:08:55.480> to<00:08:55.680> be<00:08:55.839> able<00:08:56.080> to<00:08:56.320> prevent<00:08:57.080> uh 00:08:57.230 --> 00:08:57.240 align:start position:0% that you have to be able to prevent uh 00:08:57.240 --> 00:08:59.829 align:start position:0% that you have to be able to prevent uh collusion<00:08:57.760> in<00:08:57.920> some<00:08:58.160> way<00:08:58.440> at<00:08:58.600> least<00:08:58.920> make<00:08:59.079> it 00:08:59.829 --> 00:08:59.839 align:start position:0% collusion in some way at least make it 00:08:59.839 --> 00:09:02.230 align:start position:0% collusion in some way at least make it difficults<00:09:00.120> to<00:09:00.279> trust<00:09:01.040> and<00:09:01.360> that<00:09:01.560> requires<00:09:02.120> as 00:09:02.230 --> 00:09:02.240 align:start position:0% difficults to trust and that requires as 00:09:02.240 --> 00:09:04.829 align:start position:0% difficults to trust and that requires as it<00:09:02.360> turns<00:09:02.640> out<00:09:03.000> exactly<00:09:03.440> the<00:09:03.600> same<00:09:03.880> type<00:09:04.160> of 00:09:04.829 --> 00:09:04.839 align:start position:0% it turns out exactly the same type of 00:09:04.839 --> 00:09:07.430 align:start position:0% it turns out exactly the same type of properties<00:09:05.320> that<00:09:05.440> voting<00:09:05.800> requires<00:09:06.640> so<00:09:07.200> let's 00:09:07.430 --> 00:09:07.440 align:start position:0% properties that voting requires so let's 00:09:07.440 --> 00:09:09.670 align:start position:0% properties that voting requires so let's look<00:09:07.600> at<00:09:07.720> voting<00:09:08.040> as<00:09:08.160> an<00:09:08.360> example<00:09:09.079> so<00:09:09.360> base 00:09:09.670 --> 00:09:09.680 align:start position:0% look at voting as an example so base 00:09:09.680 --> 00:09:11.670 align:start position:0% look at voting as an example so base case<00:09:10.279> put<00:09:10.399> it<00:09:10.519> on<00:09:10.640> the<00:09:10.800> blockchain<00:09:11.399> so<00:09:11.560> what 00:09:11.670 --> 00:09:11.680 align:start position:0% case put it on the blockchain so what 00:09:11.680 --> 00:09:12.990 align:start position:0% case put it on the blockchain so what does<00:09:11.839> putting<00:09:12.120> it<00:09:12.240> on<00:09:12.320> the<00:09:12.440> blockchain<00:09:12.880> give 00:09:12.990 --> 00:09:13.000 align:start position:0% does putting it on the blockchain give 00:09:13.000 --> 00:09:14.829 align:start position:0% does putting it on the blockchain give you<00:09:13.200> right<00:09:13.320> it<00:09:13.480> gives<00:09:13.720> you<00:09:14.320> public 00:09:14.829 --> 00:09:14.839 align:start position:0% you right it gives you public 00:09:14.839 --> 00:09:17.230 align:start position:0% you right it gives you public verifiability<00:09:15.839> so<00:09:16.160> anyone<00:09:16.560> can<00:09:16.800> check<00:09:17.079> that 00:09:17.230 --> 00:09:17.240 align:start position:0% verifiability so anyone can check that 00:09:17.240 --> 00:09:19.350 align:start position:0% verifiability so anyone can check that the<00:09:17.399> result<00:09:17.720> was<00:09:17.880> computed<00:09:18.279> correctly<00:09:19.120> and<00:09:19.240> it 00:09:19.350 --> 00:09:19.360 align:start position:0% the result was computed correctly and it 00:09:19.360 --> 00:09:21.030 align:start position:0% the result was computed correctly and it gives<00:09:19.519> you<00:09:19.680> censorship<00:09:20.240> resistance<00:09:20.959> if 00:09:21.030 --> 00:09:21.040 align:start position:0% gives you censorship resistance if 00:09:21.040 --> 00:09:22.790 align:start position:0% gives you censorship resistance if you're<00:09:21.240> an<00:09:21.360> eligible<00:09:21.800> voter<00:09:22.120> no<00:09:22.200> one<00:09:22.360> can<00:09:22.560> stop 00:09:22.790 --> 00:09:22.800 align:start position:0% you're an eligible voter no one can stop 00:09:22.800 --> 00:09:25.269 align:start position:0% you're an eligible voter no one can stop you<00:09:22.959> from<00:09:23.120> voting<00:09:23.920> so<00:09:24.480> it's<00:09:24.640> a<00:09:24.760> good<00:09:24.959> starting 00:09:25.269 --> 00:09:25.279 align:start position:0% you from voting so it's a good starting 00:09:25.279 --> 00:09:27.150 align:start position:0% you from voting so it's a good starting point<00:09:25.800> Dows<00:09:26.160> have<00:09:26.320> been<00:09:26.480> doing<00:09:26.720> this<00:09:26.839> for<00:09:27.000> a 00:09:27.150 --> 00:09:27.160 align:start position:0% point Dows have been doing this for a 00:09:27.160 --> 00:09:31.110 align:start position:0% point Dows have been doing this for a very<00:09:27.399> long<00:09:27.720> time<00:09:28.320> very<00:09:28.600> basic<00:09:29.480> now<00:09:30.440> of<00:09:30.600> course 00:09:31.110 --> 00:09:31.120 align:start position:0% very long time very basic now of course 00:09:31.120 --> 00:09:32.829 align:start position:0% very long time very basic now of course voting<00:09:31.399> on<00:09:31.519> The<00:09:31.680> blockchain<00:09:32.200> has<00:09:32.399> a<00:09:32.519> lot<00:09:32.640> of 00:09:32.829 --> 00:09:32.839 align:start position:0% voting on The blockchain has a lot of 00:09:32.839 --> 00:09:34.430 align:start position:0% voting on The blockchain has a lot of problems<00:09:33.240> so<00:09:33.480> let's<00:09:33.680> talk<00:09:33.880> about<00:09:34.120> adding 00:09:34.430 --> 00:09:34.440 align:start position:0% problems so let's talk about adding 00:09:34.440 --> 00:09:38.870 align:start position:0% problems so let's talk about adding cryptography<00:09:35.000> on<00:09:35.200> top<00:09:36.079> let's<00:09:36.399> add<00:09:36.880> ZK<00:09:37.880> ARS 00:09:38.870 --> 00:09:38.880 align:start position:0% cryptography on top let's add ZK ARS 00:09:38.880 --> 00:09:40.949 align:start position:0% cryptography on top let's add ZK ARS keep<00:09:39.079> the<00:09:39.240> previous<00:09:39.680> properties<00:09:40.560> but<00:09:40.720> you 00:09:40.949 --> 00:09:40.959 align:start position:0% keep the previous properties but you 00:09:40.959 --> 00:09:42.790 align:start position:0% keep the previous properties but you also<00:09:41.399> add<00:09:41.839> and<00:09:41.959> you<00:09:42.120> keep<00:09:42.399> public 00:09:42.790 --> 00:09:42.800 align:start position:0% also add and you keep public 00:09:42.800 --> 00:09:46.110 align:start position:0% also add and you keep public verifiability<00:09:43.800> but<00:09:43.959> you<00:09:44.200> and<00:09:44.640> uh<00:09:45.640> you<00:09:45.839> also 00:09:46.110 --> 00:09:46.120 align:start position:0% verifiability but you and uh you also 00:09:46.120 --> 00:09:48.230 align:start position:0% verifiability but you and uh you also have<00:09:46.320> censorship<00:09:46.920> or<00:09:47.120> resistance<00:09:47.720> okay<00:09:48.079> sorry 00:09:48.230 --> 00:09:48.240 align:start position:0% have censorship or resistance okay sorry 00:09:48.240 --> 00:09:50.470 align:start position:0% have censorship or resistance okay sorry I<00:09:48.320> wrote<00:09:48.560> this<00:09:49.200> incorrectly<00:09:49.920> um<00:09:50.200> the<00:09:50.320> thing 00:09:50.470 --> 00:09:50.480 align:start position:0% I wrote this incorrectly um the thing 00:09:50.480 --> 00:09:52.590 align:start position:0% I wrote this incorrectly um the thing that<00:09:50.600> you<00:09:50.720> add<00:09:50.920> is<00:09:51.079> privacy<00:09:51.600> right<00:09:52.000> basically 00:09:52.590 --> 00:09:52.600 align:start position:0% that you add is privacy right basically 00:09:52.600 --> 00:09:56.350 align:start position:0% that you add is privacy right basically if<00:09:52.680> you<00:09:52.920> vote<00:09:53.600> then<00:09:54.440> no<00:09:54.560> one<00:09:54.920> will<00:09:55.640> uh<00:09:55.920> be<00:09:56.120> able 00:09:56.350 --> 00:09:56.360 align:start position:0% if you vote then no one will uh be able 00:09:56.360 --> 00:09:58.829 align:start position:0% if you vote then no one will uh be able to<00:09:56.560> tell<00:09:57.279> who<00:09:57.560> like<00:09:57.800> which<00:09:58.079> person<00:09:58.440> made<00:09:58.680> a 00:09:58.829 --> 00:09:58.839 align:start position:0% to tell who like which person made a 00:09:58.839 --> 00:10:00.710 align:start position:0% to tell who like which person made a particular<00:09:59.440> vote<00:09:59.880> you'll<00:10:00.120> still<00:10:00.320> be<00:10:00.440> able<00:10:00.600> to 00:10:00.710 --> 00:10:00.720 align:start position:0% particular vote you'll still be able to 00:10:00.720 --> 00:10:02.829 align:start position:0% particular vote you'll still be able to see<00:10:00.920> the<00:10:01.040> contest<00:10:01.440> of<00:10:01.560> the<00:10:01.720> votes<00:10:02.399> but<00:10:02.720> you 00:10:02.829 --> 00:10:02.839 align:start position:0% see the contest of the votes but you 00:10:02.839 --> 00:10:04.470 align:start position:0% see the contest of the votes but you will<00:10:03.040> not<00:10:03.200> be<00:10:03.360> able<00:10:03.560> to<00:10:03.720> see<00:10:04.040> like<00:10:04.200> who 00:10:04.470 --> 00:10:04.480 align:start position:0% will not be able to see like who 00:10:04.480 --> 00:10:07.110 align:start position:0% will not be able to see like who actually<00:10:04.839> made<00:10:05.200> a<00:10:05.680> particular<00:10:06.279> vote<00:10:06.640> right 00:10:07.110 --> 00:10:07.120 align:start position:0% actually made a particular vote right 00:10:07.120 --> 00:10:08.949 align:start position:0% actually made a particular vote right and<00:10:07.279> this<00:10:07.560> already<00:10:07.880> is<00:10:08.000> a<00:10:08.200> very<00:10:08.440> significant 00:10:08.949 --> 00:10:08.959 align:start position:0% and this already is a very significant 00:10:08.959 --> 00:10:11.710 align:start position:0% and this already is a very significant privacy<00:10:09.399> gain<00:10:10.000> it<00:10:10.160> already<00:10:10.519> makes<00:10:10.959> uh<00:10:11.320> many 00:10:11.710 --> 00:10:11.720 align:start position:0% privacy gain it already makes uh many 00:10:11.720 --> 00:10:13.990 align:start position:0% privacy gain it already makes uh many types<00:10:12.000> of<00:10:12.240> collusion<00:10:12.880> much<00:10:13.320> uh<00:10:13.560> much<00:10:13.800> much 00:10:13.990 --> 00:10:14.000 align:start position:0% types of collusion much uh much much 00:10:14.000 --> 00:10:16.190 align:start position:0% types of collusion much uh much much harder<00:10:14.800> and<00:10:15.200> like<00:10:15.320> it's<00:10:15.519> already<00:10:15.760> a<00:10:15.959> really 00:10:16.190 --> 00:10:16.200 align:start position:0% harder and like it's already a really 00:10:16.200 --> 00:10:18.710 align:start position:0% harder and like it's already a really significant<00:10:16.720> Improvement<00:10:17.360> right<00:10:18.079> but<00:10:18.519> it's 00:10:18.710 --> 00:10:18.720 align:start position:0% significant Improvement right but it's 00:10:18.720 --> 00:10:20.030 align:start position:0% significant Improvement right but it's still<00:10:18.920> not<00:10:19.160> enough<00:10:19.480> right<00:10:19.600> and<00:10:19.680> the<00:10:19.800> reason 00:10:20.030 --> 00:10:20.040 align:start position:0% still not enough right and the reason 00:10:20.040 --> 00:10:22.389 align:start position:0% still not enough right and the reason it's<00:10:20.200> still<00:10:20.440> not<00:10:20.680> enough<00:10:21.120> is<00:10:21.399> basically<00:10:22.000> that 00:10:22.389 --> 00:10:22.399 align:start position:0% it's still not enough is basically that 00:10:22.399 --> 00:10:24.470 align:start position:0% it's still not enough is basically that if<00:10:22.480> you<00:10:22.720> really<00:10:22.959> wanted<00:10:23.360> to<00:10:23.440> sell<00:10:23.720> your<00:10:23.880> vote 00:10:24.470 --> 00:10:24.480 align:start position:0% if you really wanted to sell your vote 00:10:24.480 --> 00:10:26.389 align:start position:0% if you really wanted to sell your vote then<00:10:24.640> if<00:10:24.720> you<00:10:24.839> made<00:10:25.000> a<00:10:25.120> CK<00:10:25.440> snark<00:10:26.079> you<00:10:26.240> could 00:10:26.389 --> 00:10:26.399 align:start position:0% then if you made a CK snark you could 00:10:26.399 --> 00:10:27.910 align:start position:0% then if you made a CK snark you could still<00:10:26.720> prove<00:10:26.959> to<00:10:27.120> someone<00:10:27.399> else<00:10:27.640> that<00:10:27.760> you 00:10:27.910 --> 00:10:27.920 align:start position:0% still prove to someone else that you 00:10:27.920 --> 00:10:29.750 align:start position:0% still prove to someone else that you voted<00:10:28.560> for<00:10:28.839> some<00:10:29.079> particular<00:10:29.320> particular 00:10:29.750 --> 00:10:29.760 align:start position:0% voted for some particular particular 00:10:29.760 --> 00:10:32.110 align:start position:0% voted for some particular particular candidate<00:10:30.320> very<00:10:30.519> easily<00:10:31.320> so<00:10:31.640> let's<00:10:31.839> add<00:10:32.000> the 00:10:32.110 --> 00:10:32.120 align:start position:0% candidate very easily so let's add the 00:10:32.120 --> 00:10:34.750 align:start position:0% candidate very easily so let's add the Macy<00:10:32.480> mechanism<00:10:33.279> the<00:10:33.440> Macy<00:10:33.760> mechanism<00:10:34.560> does 00:10:34.750 --> 00:10:34.760 align:start position:0% Macy mechanism the Macy mechanism does 00:10:34.760 --> 00:10:37.190 align:start position:0% Macy mechanism the Macy mechanism does not<00:10:34.959> rely<00:10:35.279> on<00:10:35.480> any<00:10:35.639> new<00:10:36.040> cryptography<00:10:37.040> it 00:10:37.190 --> 00:10:37.200 align:start position:0% not rely on any new cryptography it 00:10:37.200 --> 00:10:39.069 align:start position:0% not rely on any new cryptography it keeps<00:10:37.480> the<00:10:37.639> previous<00:10:38.120> properties<00:10:38.760> but<00:10:38.880> it 00:10:39.069 --> 00:10:39.079 align:start position:0% keeps the previous properties but it 00:10:39.079 --> 00:10:41.350 align:start position:0% keeps the previous properties but it also<00:10:39.360> adds<00:10:39.639> coercion<00:10:40.120> resistance<00:10:40.720> right<00:10:40.880> and 00:10:41.350 --> 00:10:41.360 align:start position:0% also adds coercion resistance right and 00:10:41.360 --> 00:10:43.389 align:start position:0% also adds coercion resistance right and assuming<00:10:41.760> that<00:10:41.920> the<00:10:42.040> server<00:10:42.360> is<00:10:42.560> honest<00:10:43.200> so 00:10:43.389 --> 00:10:43.399 align:start position:0% assuming that the server is honest so 00:10:43.399 --> 00:10:45.269 align:start position:0% assuming that the server is honest so assuming<00:10:43.760> that<00:10:43.880> the<00:10:44.000> server<00:10:44.320> is<00:10:44.480> honest<00:10:45.040> you 00:10:45.269 --> 00:10:45.279 align:start position:0% assuming that the server is honest you 00:10:45.279 --> 00:10:47.350 align:start position:0% assuming that the server is honest you add<00:10:45.440> this<00:10:45.600> new<00:10:45.839> property<00:10:46.279> which<00:10:46.399> is<00:10:46.680> that<00:10:47.120> you 00:10:47.350 --> 00:10:47.360 align:start position:0% add this new property which is that you 00:10:47.360 --> 00:10:49.910 align:start position:0% add this new property which is that you cannot<00:10:47.880> prove<00:10:48.200> who<00:10:48.360> you<00:10:48.519> voted<00:10:48.880> for<00:10:49.519> even<00:10:49.800> if 00:10:49.910 --> 00:10:49.920 align:start position:0% cannot prove who you voted for even if 00:10:49.920 --> 00:10:51.750 align:start position:0% cannot prove who you voted for even if you<00:10:50.120> wanted<00:10:50.399> to<00:10:50.560> make<00:10:50.839> that<00:10:50.959> kind<00:10:51.079> of<00:10:51.240> proof 00:10:51.750 --> 00:10:51.760 align:start position:0% you wanted to make that kind of proof 00:10:51.760 --> 00:10:54.949 align:start position:0% you wanted to make that kind of proof and<00:10:51.959> this<00:10:52.160> adds<00:10:52.560> like<00:10:53.120> a<00:10:53.440> very<00:10:53.760> large<00:10:54.079> friction 00:10:54.949 --> 00:10:54.959 align:start position:0% and this adds like a very large friction 00:10:54.959 --> 00:10:57.230 align:start position:0% and this adds like a very large friction against<00:10:55.760> actually<00:10:56.160> trying<00:10:56.440> to<00:10:56.600> implement<00:10:57.079> any 00:10:57.230 --> 00:10:57.240 align:start position:0% against actually trying to implement any 00:10:57.240 --> 00:10:58.829 align:start position:0% against actually trying to implement any of<00:10:57.399> this<00:10:57.560> kind<00:10:57.720> of<00:10:57.839> bribing<00:10:58.440> because 00:10:58.829 --> 00:10:58.839 align:start position:0% of this kind of bribing because 00:10:58.839 --> 00:11:00.350 align:start position:0% of this kind of bribing because basically 00:11:00.350 --> 00:11:00.360 align:start position:0% basically 00:11:00.360 --> 00:11:02.750 align:start position:0% basically either<00:11:01.240> they<00:11:01.440> have<00:11:01.519> to<00:11:01.720> do<00:11:02.000> some<00:11:02.240> kind<00:11:02.399> of<00:11:02.600> like 00:11:02.750 --> 00:11:02.760 align:start position:0% either they have to do some kind of like 00:11:02.760 --> 00:11:04.870 align:start position:0% either they have to do some kind of like side<00:11:03.000> Channel<00:11:03.399> attack<00:11:03.800> against<00:11:04.160> you<00:11:04.440> directly 00:11:04.870 --> 00:11:04.880 align:start position:0% side Channel attack against you directly 00:11:04.880 --> 00:11:08.430 align:start position:0% side Channel attack against you directly as<00:11:05.000> a<00:11:05.160> voter<00:11:05.920> or<00:11:06.519> they<00:11:06.760> actually<00:11:07.120> have<00:11:07.279> to<00:11:07.519> like 00:11:08.430 --> 00:11:08.440 align:start position:0% as a voter or they actually have to like 00:11:08.440 --> 00:11:12.750 align:start position:0% as a voter or they actually have to like attack<00:11:08.839> the<00:11:09.360> server<00:11:10.279> now<00:11:10.920> let's<00:11:11.320> add<00:11:11.639> FH<00:11:12.399> right 00:11:12.750 --> 00:11:12.760 align:start position:0% attack the server now let's add FH right 00:11:12.760 --> 00:11:14.790 align:start position:0% attack the server now let's add FH right so<00:11:12.959> with<00:11:13.120> FH<00:11:13.839> you<00:11:14.000> keep<00:11:14.200> the<00:11:14.360> previous 00:11:14.790 --> 00:11:14.800 align:start position:0% so with FH you keep the previous 00:11:14.800 --> 00:11:18.030 align:start position:0% so with FH you keep the previous properties<00:11:15.800> but<00:11:16.399> you<00:11:16.680> if<00:11:16.760> you<00:11:16.959> add<00:11:17.279> FHA 00:11:18.030 --> 00:11:18.040 align:start position:0% properties but you if you add FHA 00:11:18.040 --> 00:11:20.069 align:start position:0% properties but you if you add FHA together<00:11:18.360> with<00:11:18.560> threshold<00:11:19.040> decryption<00:11:19.920> you 00:11:20.069 --> 00:11:20.079 align:start position:0% together with threshold decryption you 00:11:20.079 --> 00:11:21.590 align:start position:0% together with threshold decryption you can<00:11:20.279> make<00:11:20.519> the<00:11:20.680> coercion<00:11:21.120> resistance 00:11:21.590 --> 00:11:21.600 align:start position:0% can make the coercion resistance 00:11:21.600 --> 00:11:24.069 align:start position:0% can make the coercion resistance guarantee<00:11:22.440> only<00:11:22.800> depend<00:11:23.200> on<00:11:23.399> an<00:11:23.560> mfn 00:11:24.069 --> 00:11:24.079 align:start position:0% guarantee only depend on an mfn 00:11:24.079 --> 00:11:25.990 align:start position:0% guarantee only depend on an mfn assumption<00:11:24.560> so<00:11:24.720> instead<00:11:24.959> of<00:11:25.120> relying<00:11:25.480> on<00:11:25.680> one 00:11:25.990 --> 00:11:26.000 align:start position:0% assumption so instead of relying on one 00:11:26.000 --> 00:11:29.350 align:start position:0% assumption so instead of relying on one operator<00:11:26.959> you<00:11:27.079> can<00:11:27.360> rely<00:11:27.800> on<00:11:28.440> potentially 00:11:29.350 --> 00:11:29.360 align:start position:0% operator you can rely on potentially 00:11:29.360 --> 00:11:31.310 align:start position:0% operator you can rely on potentially like<00:11:29.560> say<00:11:29.880> seven<00:11:30.240> operators<00:11:30.800> out<00:11:30.959> of<00:11:31.120> which 00:11:31.310 --> 00:11:31.320 align:start position:0% like say seven operators out of which 00:11:31.320 --> 00:11:34.470 align:start position:0% like say seven operators out of which like<00:11:31.519> four<00:11:31.800> need<00:11:31.959> to<00:11:32.120> be<00:11:32.600> honest<00:11:33.160> right<00:11:33.680> now 00:11:34.470 --> 00:11:34.480 align:start position:0% like four need to be honest right now 00:11:34.480 --> 00:11:36.470 align:start position:0% like four need to be honest right now there<00:11:34.680> are<00:11:35.320> voting<00:11:35.680> protocols<00:11:36.160> that<00:11:36.279> have 00:11:36.470 --> 00:11:36.480 align:start position:0% there are voting protocols that have 00:11:36.480 --> 00:11:39.430 align:start position:0% there are voting protocols that have existed<00:11:36.920> since<00:11:37.200> like<00:11:37.600> 2002<00:11:38.600> that<00:11:38.760> have<00:11:38.959> given 00:11:39.430 --> 00:11:39.440 align:start position:0% existed since like 2002 that have given 00:11:39.440 --> 00:11:41.590 align:start position:0% existed since like 2002 that have given all<00:11:39.560> of<00:11:39.839> these<00:11:40.240> uh<00:11:40.639> properties<00:11:41.120> depending<00:11:41.440> on 00:11:41.590 --> 00:11:41.600 align:start position:0% all of these uh properties depending on 00:11:41.600 --> 00:11:43.670 align:start position:0% all of these uh properties depending on an<00:11:41.720> mfn<00:11:42.240> assumption<00:11:42.720> with<00:11:42.880> simpler 00:11:43.670 --> 00:11:43.680 align:start position:0% an mfn assumption with simpler 00:11:43.680 --> 00:11:47.550 align:start position:0% an mfn assumption with simpler technology<00:11:44.680> but<00:11:45.519> those<00:11:46.000> protocols<00:11:46.959> they<00:11:47.160> gave 00:11:47.550 --> 00:11:47.560 align:start position:0% technology but those protocols they gave 00:11:47.560 --> 00:11:49.790 align:start position:0% technology but those protocols they gave all<00:11:47.760> of<00:11:47.920> the<00:11:48.120> prop<00:11:48.639> all<00:11:48.800> of<00:11:49.040> these<00:11:49.360> properties 00:11:49.790 --> 00:11:49.800 align:start position:0% all of the prop all of these properties 00:11:49.800 --> 00:11:51.590 align:start position:0% all of the prop all of these properties under<00:11:50.079> that<00:11:50.279> assumption<00:11:51.079> this<00:11:51.240> kind<00:11:51.399> of 00:11:51.590 --> 00:11:51.600 align:start position:0% under that assumption this kind of 00:11:51.600 --> 00:11:54.150 align:start position:0% under that assumption this kind of design<00:11:52.079> actually<00:11:52.480> gives<00:11:52.959> uh<00:11:53.560> um<00:11:53.800> every 00:11:54.150 --> 00:11:54.160 align:start position:0% design actually gives uh um every 00:11:54.160 --> 00:11:55.990 align:start position:0% design actually gives uh um every property<00:11:54.560> except<00:11:54.800> for<00:11:55.000> corrsion<00:11:55.440> resistance 00:11:55.990 --> 00:11:56.000 align:start position:0% property except for corrsion resistance 00:11:56.000 --> 00:11:58.829 align:start position:0% property except for corrsion resistance an<00:11:56.160> even<00:11:56.480> stronger<00:11:56.920> guarantee<00:11:57.920> and<00:11:58.480> if<00:11:58.600> you<00:11:58.720> do 00:11:58.829 --> 00:11:58.839 align:start position:0% an even stronger guarantee and if you do 00:11:58.839 --> 00:12:00.990 align:start position:0% an even stronger guarantee and if you do it<00:11:58.959> with<00:11:59.240> general<00:11:59.480> purpose<00:11:59.800> cryptography<00:12:00.800> it 00:12:00.990 --> 00:12:01.000 align:start position:0% it with general purpose cryptography it 00:12:01.000 --> 00:12:03.110 align:start position:0% it with general purpose cryptography it generalizes<00:12:01.839> much<00:12:02.000> more<00:12:02.240> naturally<00:12:02.760> to<00:12:02.920> any 00:12:03.110 --> 00:12:03.120 align:start position:0% generalizes much more naturally to any 00:12:03.120 --> 00:12:05.590 align:start position:0% generalizes much more naturally to any voting<00:12:03.480> system<00:12:04.079> you're<00:12:04.279> not<00:12:04.480> if<00:12:04.600> you<00:12:05.040> H<00:12:05.320> have<00:12:05.440> a 00:12:05.590 --> 00:12:05.600 align:start position:0% voting system you're not if you H have a 00:12:05.600 --> 00:12:07.389 align:start position:0% voting system you're not if you H have a system<00:12:06.000> that's<00:12:06.200> designed<00:12:06.560> for<00:12:06.680> doing<00:12:07.040> Simple 00:12:07.389 --> 00:12:07.399 align:start position:0% system that's designed for doing Simple 00:12:07.399 --> 00:12:09.870 align:start position:0% system that's designed for doing Simple vote<00:12:07.639> counting<00:12:08.560> you<00:12:08.760> can<00:12:09.120> switch<00:12:09.399> it<00:12:09.560> over<00:12:09.760> to 00:12:09.870 --> 00:12:09.880 align:start position:0% vote counting you can switch it over to 00:12:09.880 --> 00:12:12.110 align:start position:0% vote counting you can switch it over to doing<00:12:10.120> quadratic<00:12:10.639> voting<00:12:10.959> quadratic<00:12:11.399> funding 00:12:12.110 --> 00:12:12.120 align:start position:0% doing quadratic voting quadratic funding 00:12:12.120 --> 00:12:14.030 align:start position:0% doing quadratic voting quadratic funding with<00:12:12.320> like<00:12:12.480> a<00:12:12.600> few<00:12:12.800> lines<00:12:13.000> of<00:12:13.160> code<00:12:13.720> you<00:12:13.839> can 00:12:14.030 --> 00:12:14.040 align:start position:0% with like a few lines of code you can 00:12:14.040 --> 00:12:16.350 align:start position:0% with like a few lines of code you can switch<00:12:14.320> it<00:12:14.480> over<00:12:14.639> to<00:12:14.800> doing<00:12:15.079> pairwise<00:12:15.959> bounded 00:12:16.350 --> 00:12:16.360 align:start position:0% switch it over to doing pairwise bounded 00:12:16.360 --> 00:12:18.829 align:start position:0% switch it over to doing pairwise bounded quadratic<00:12:16.839> voting<00:12:17.480> a<00:12:17.560> few<00:12:17.760> lines<00:12:18.000> of<00:12:18.160> code<00:12:18.720> you 00:12:18.829 --> 00:12:18.839 align:start position:0% quadratic voting a few lines of code you 00:12:18.839 --> 00:12:20.310 align:start position:0% quadratic voting a few lines of code you can<00:12:19.000> switch<00:12:19.240> it<00:12:19.360> over<00:12:19.519> to<00:12:19.680> doing<00:12:19.920> cluster 00:12:20.310 --> 00:12:20.320 align:start position:0% can switch it over to doing cluster 00:12:20.320 --> 00:12:22.150 align:start position:0% can switch it over to doing cluster matching<00:12:20.720> a<00:12:20.800> few<00:12:21.000> lines<00:12:21.199> of<00:12:21.360> code<00:12:21.880> you<00:12:22.000> can 00:12:22.150 --> 00:12:22.160 align:start position:0% matching a few lines of code you can 00:12:22.160 --> 00:12:24.590 align:start position:0% matching a few lines of code you can switch<00:12:22.440> it<00:12:22.600> over<00:12:22.839> to<00:12:23.040> doing<00:12:23.560> the<00:12:24.120> community 00:12:24.590 --> 00:12:24.600 align:start position:0% switch it over to doing the community 00:12:24.600 --> 00:12:26.629 align:start position:0% switch it over to doing the community notes<00:12:25.000> bridging<00:12:25.480> Matrix<00:12:25.959> factorization 00:12:26.629 --> 00:12:26.639 align:start position:0% notes bridging Matrix factorization 00:12:26.639 --> 00:12:29.189 align:start position:0% notes bridging Matrix factorization algorithm<00:12:27.600> with<00:12:27.800> only<00:12:28.079> the<00:12:28.240> lines<00:12:28.480> of<00:12:28.680> code 00:12:29.189 --> 00:12:29.199 align:start position:0% algorithm with only the lines of code 00:12:29.199 --> 00:12:30.629 align:start position:0% algorithm with only the lines of code that<00:12:29.320> you<00:12:29.399> need<00:12:29.560> to<00:12:29.800> actually<00:12:30.079> Implement<00:12:30.519> that 00:12:30.629 --> 00:12:30.639 align:start position:0% that you need to actually Implement that 00:12:30.639 --> 00:12:32.710 align:start position:0% that you need to actually Implement that Matrix<00:12:31.079> factorization<00:12:31.760> algorithm<00:12:32.480> and<00:12:32.639> if 00:12:32.710 --> 00:12:32.720 align:start position:0% Matrix factorization algorithm and if 00:12:32.720 --> 00:12:34.230 align:start position:0% Matrix factorization algorithm and if you<00:12:32.800> want<00:12:32.880> to<00:12:33.000> do<00:12:33.120> it<00:12:33.279> efficiently<00:12:33.760> it's<00:12:33.920> a<00:12:34.040> bit 00:12:34.230 --> 00:12:34.240 align:start position:0% you want to do it efficiently it's a bit 00:12:34.240 --> 00:12:36.310 align:start position:0% you want to do it efficiently it's a bit hard<00:12:34.560> but<00:12:34.920> the<00:12:35.079> algorithm<00:12:35.639> itself<00:12:36.040> like 00:12:36.310 --> 00:12:36.320 align:start position:0% hard but the algorithm itself like 00:12:36.320 --> 00:12:39.189 align:start position:0% hard but the algorithm itself like basically<00:12:36.720> about<00:12:36.920> 20<00:12:37.320> lines<00:12:37.519> of<00:12:37.680> code<00:12:38.120> right 00:12:39.189 --> 00:12:39.199 align:start position:0% basically about 20 lines of code right 00:12:39.199 --> 00:12:43.590 align:start position:0% basically about 20 lines of code right so<00:12:40.199> FHA<00:12:41.160> basically<00:12:42.079> together<00:12:42.360> with<00:12:42.560> SARS<00:12:43.360> you 00:12:43.590 --> 00:12:43.600 align:start position:0% so FHA basically together with SARS you 00:12:43.600 --> 00:12:45.269 align:start position:0% so FHA basically together with SARS you actually<00:12:43.880> create<00:12:44.160> this<00:12:44.360> like<00:12:44.519> very<00:12:44.760> general 00:12:45.269 --> 00:12:45.279 align:start position:0% actually create this like very general 00:12:45.279 --> 00:12:47.629 align:start position:0% actually create this like very general purpose<00:12:45.760> uh<00:12:45.959> design<00:12:46.800> and<00:12:46.920> you<00:12:47.120> keep<00:12:47.360> all<00:12:47.480> of 00:12:47.629 --> 00:12:47.639 align:start position:0% purpose uh design and you keep all of 00:12:47.639 --> 00:12:49.389 align:start position:0% purpose uh design and you keep all of your<00:12:48.160> all<00:12:48.279> of<00:12:48.480> these<00:12:48.760> properties<00:12:49.160> that<00:12:49.279> you 00:12:49.389 --> 00:12:49.399 align:start position:0% your all of these properties that you 00:12:49.399 --> 00:12:51.790 align:start position:0% your all of these properties that you want<00:12:49.680> out<00:12:49.800> of<00:12:49.920> a<00:12:50.000> voting<00:12:50.360> system<00:12:50.760> except<00:12:51.320> cion 00:12:51.790 --> 00:12:51.800 align:start position:0% want out of a voting system except cion 00:12:51.800 --> 00:12:53.829 align:start position:0% want out of a voting system except cion resistance<00:12:52.320> depends<00:12:52.639> on<00:12:52.760> an<00:12:52.920> MN<00:12:53.360> assumption 00:12:53.829 --> 00:12:53.839 align:start position:0% resistance depends on an MN assumption 00:12:53.839 --> 00:12:56.189 align:start position:0% resistance depends on an MN assumption which<00:12:54.000> is<00:12:54.240> like<00:12:54.880> not<00:12:55.120> ideal<00:12:55.560> right<00:12:55.760> because<00:12:56.040> M 00:12:56.189 --> 00:12:56.199 align:start position:0% which is like not ideal right because M 00:12:56.199 --> 00:12:58.870 align:start position:0% which is like not ideal right because M out<00:12:56.360> of<00:12:56.480> n<00:12:57.000> can<00:12:57.199> still<00:12:57.600> collude<00:12:58.279> silently<00:12:58.760> and 00:12:58.870 --> 00:12:58.880 align:start position:0% out of n can still collude silently and 00:12:58.880 --> 00:13:00.829 align:start position:0% out of n can still collude silently and they<00:12:58.959> can<00:12:59.240> collude<00:12:59.560> silently<00:13:00.079> they<00:13:00.160> can<00:13:00.440> like 00:13:00.829 --> 00:13:00.839 align:start position:0% they can collude silently they can like 00:13:00.839 --> 00:13:03.069 align:start position:0% they can collude silently they can like pass<00:13:01.120> all<00:13:01.240> of<00:13:01.360> the<00:13:01.560> information<00:13:02.120> over<00:13:02.360> to<00:13:02.639> the 00:13:03.069 --> 00:13:03.079 align:start position:0% pass all of the information over to the 00:13:03.079 --> 00:13:06.230 align:start position:0% pass all of the information over to the NSA<00:13:04.079> and<00:13:04.639> like<00:13:04.800> no<00:13:04.920> one<00:13:05.079> would<00:13:05.240> be<00:13:05.360> able<00:13:05.600> to 00:13:06.230 --> 00:13:06.240 align:start position:0% NSA and like no one would be able to 00:13:06.240 --> 00:13:08.230 align:start position:0% NSA and like no one would be able to actually<00:13:06.639> tell<00:13:06.920> that<00:13:07.079> any<00:13:07.320> collusion<00:13:07.760> is 00:13:08.230 --> 00:13:08.240 align:start position:0% actually tell that any collusion is 00:13:08.240 --> 00:13:12.629 align:start position:0% actually tell that any collusion is happening<00:13:09.240> so<00:13:10.160> now<00:13:10.519> let's<00:13:10.800> add<00:13:11.240> aisc<00:13:12.240> so<00:13:12.399> with 00:13:12.629 --> 00:13:12.639 align:start position:0% happening so now let's add aisc so with 00:13:12.639 --> 00:13:14.790 align:start position:0% happening so now let's add aisc so with aisc<00:13:13.639> you<00:13:13.760> can<00:13:14.000> keep<00:13:14.240> the<00:13:14.399> previous 00:13:14.790 --> 00:13:14.800 align:start position:0% aisc you can keep the previous 00:13:14.800 --> 00:13:17.150 align:start position:0% aisc you can keep the previous properties<00:13:15.560> but<00:13:15.680> you<00:13:15.839> can<00:13:16.079> make<00:13:16.360> you<00:13:16.480> can<00:13:16.959> make 00:13:17.150 --> 00:13:17.160 align:start position:0% properties but you can make you can make 00:13:17.160 --> 00:13:19.990 align:start position:0% properties but you can make you can make it<00:13:17.360> so<00:13:17.639> that<00:13:18.199> extracting<00:13:18.880> or<00:13:19.120> proving<00:13:19.720> any 00:13:19.990 --> 00:13:20.000 align:start position:0% it so that extracting or proving any 00:13:20.000 --> 00:13:21.829 align:start position:0% it so that extracting or proving any information<00:13:20.560> at<00:13:20.680> all<00:13:21.000> about<00:13:21.279> individual 00:13:21.829 --> 00:13:21.839 align:start position:0% information at all about individual 00:13:21.839 --> 00:13:24.829 align:start position:0% information at all about individual votes<00:13:22.279> requires<00:13:23.160> blockchain<00:13:23.600> consensus<00:13:24.600> and 00:13:24.829 --> 00:13:24.839 align:start position:0% votes requires blockchain consensus and 00:13:24.839 --> 00:13:26.590 align:start position:0% votes requires blockchain consensus and you<00:13:24.920> can<00:13:25.120> even<00:13:25.360> make<00:13:25.480> it<00:13:25.680> require<00:13:26.160> some<00:13:26.399> amount 00:13:26.590 --> 00:13:26.600 align:start position:0% you can even make it require some amount 00:13:26.600 --> 00:13:28.550 align:start position:0% you can even make it require some amount of<00:13:26.720> proof<00:13:26.920> of<00:13:27.120> work<00:13:27.480> per<00:13:27.720> bit<00:13:27.880> of<00:13:28.040> entropy<00:13:28.480> that 00:13:28.550 --> 00:13:28.560 align:start position:0% of proof of work per bit of entropy that 00:13:28.560 --> 00:13:29.670 align:start position:0% of proof of work per bit of entropy that you<00:13:28.760> extract 00:13:29.670 --> 00:13:29.680 align:start position:0% you extract 00:13:29.680 --> 00:13:31.430 align:start position:0% you extract so<00:13:29.880> how<00:13:30.000> do<00:13:30.079> you<00:13:30.240> do<00:13:30.399> this 00:13:31.430 --> 00:13:31.440 align:start position:0% so how do you do this 00:13:31.440 --> 00:13:35.150 align:start position:0% so how do you do this basically<00:13:32.440> when<00:13:32.720> a<00:13:32.839> user<00:13:33.240> votes<00:13:34.199> instead<00:13:34.600> of 00:13:35.150 --> 00:13:35.160 align:start position:0% basically when a user votes instead of 00:13:35.160 --> 00:13:39.870 align:start position:0% basically when a user votes instead of sending<00:13:35.680> their<00:13:35.959> vote<00:13:36.680> to<00:13:37.680> a<00:13:38.480> a<00:13:38.639> threshold<00:13:39.199> key 00:13:39.870 --> 00:13:39.880 align:start position:0% sending their vote to a a threshold key 00:13:39.880 --> 00:13:40.670 align:start position:0% sending their vote to a a threshold key um 00:13:40.670 --> 00:13:40.680 align:start position:0% um 00:13:40.680 --> 00:13:43.829 align:start position:0% um or<00:13:41.680> like<00:13:41.839> FHA<00:13:42.320> encrypting<00:13:42.800> it<00:13:43.120> to<00:13:43.240> a<00:13:43.360> threshold 00:13:43.829 --> 00:13:43.839 align:start position:0% or like FHA encrypting it to a threshold 00:13:43.839 --> 00:13:47.629 align:start position:0% or like FHA encrypting it to a threshold key<00:13:44.519> they<00:13:45.079> FH<00:13:45.519> encrypted<00:13:46.120> to<00:13:46.279> a<00:13:46.519> key<00:13:47.199> that<00:13:47.320> is 00:13:47.629 --> 00:13:47.639 align:start position:0% key they FH encrypted to a key that is 00:13:47.639 --> 00:13:51.389 align:start position:0% key they FH encrypted to a key that is inside<00:13:48.160> of<00:13:48.399> an<00:13:48.560> offis<00:13:48.959> gated<00:13:49.399> program<00:13:50.399> and<00:13:50.920> uh 00:13:51.389 --> 00:13:51.399 align:start position:0% inside of an offis gated program and uh 00:13:51.399 --> 00:13:53.350 align:start position:0% inside of an offis gated program and uh the<00:13:51.560> so<00:13:51.759> this<00:13:51.920> is<00:13:52.040> a<00:13:52.160> trusted<00:13:52.639> setup<00:13:53.000> but<00:13:53.240> but 00:13:53.350 --> 00:13:53.360 align:start position:0% the so this is a trusted setup but but 00:13:53.360 --> 00:13:54.990 align:start position:0% the so this is a trusted setup but but there<00:13:53.480> are<00:13:53.680> ways<00:13:53.880> to<00:13:54.000> make<00:13:54.160> the<00:13:54.279> trust<00:13:54.680> setup 00:13:54.990 --> 00:13:55.000 align:start position:0% there are ways to make the trust setup 00:13:55.000 --> 00:13:56.990 align:start position:0% there are ways to make the trust setup be<00:13:55.160> one<00:13:55.320> of<00:13:55.560> one<00:13:55.720> of<00:13:55.880> N<00:13:56.399> and<00:13:56.519> you<00:13:56.600> can<00:13:56.759> make<00:13:56.920> the 00:13:56.990 --> 00:13:57.000 align:start position:0% be one of one of N and you can make the 00:13:57.000 --> 00:14:00.550 align:start position:0% be one of one of N and you can make the N<00:13:57.199> be<00:13:57.399> like<00:13:57.560> extremely<00:13:58.040> large<00:13:58.480> right<00:13:59.160> so<00:13:59.600> FHA 00:14:00.550 --> 00:14:00.560 align:start position:0% N be like extremely large right so FHA 00:14:00.560 --> 00:14:02.350 align:start position:0% N be like extremely large right so FHA encrypted<00:14:01.079> into<00:14:01.320> this<00:14:01.680> key<00:14:01.920> that's<00:14:02.120> held 00:14:02.350 --> 00:14:02.360 align:start position:0% encrypted into this key that's held 00:14:02.360 --> 00:14:04.230 align:start position:0% encrypted into this key that's held inside<00:14:02.600> of<00:14:02.680> a<00:14:02.880> program<00:14:03.639> and<00:14:03.759> then<00:14:03.959> that 00:14:04.230 --> 00:14:04.240 align:start position:0% inside of a program and then that 00:14:04.240 --> 00:14:07.470 align:start position:0% inside of a program and then that program<00:14:05.040> only<00:14:05.519> gives<00:14:06.160> the<00:14:06.440> total<00:14:06.920> output<00:14:07.360> of 00:14:07.470 --> 00:14:07.480 align:start position:0% program only gives the total output of 00:14:07.480 --> 00:14:09.829 align:start position:0% program only gives the total output of all<00:14:07.600> of<00:14:07.720> the<00:14:07.880> votes<00:14:08.639> and<00:14:08.920> in<00:14:09.040> order<00:14:09.320> to<00:14:09.600> give 00:14:09.829 --> 00:14:09.839 align:start position:0% all of the votes and in order to give 00:14:09.839 --> 00:14:12.269 align:start position:0% all of the votes and in order to give the<00:14:10.360> the<00:14:10.480> total<00:14:10.800> output<00:14:11.279> at<00:14:11.440> all<00:14:11.920> and<00:14:12.040> even 00:14:12.269 --> 00:14:12.279 align:start position:0% the the total output at all and even 00:14:12.279 --> 00:14:13.590 align:start position:0% the the total output at all and even there<00:14:12.680> it's<00:14:12.759> not<00:14:12.920> going<00:14:13.000> to<00:14:13.160> give<00:14:13.279> the<00:14:13.399> full 00:14:13.590 --> 00:14:13.600 align:start position:0% there it's not going to give the full 00:14:13.600 --> 00:14:14.870 align:start position:0% there it's not going to give the full number<00:14:13.880> it's<00:14:14.000> just<00:14:14.120> going<00:14:14.240> to<00:14:14.399> give<00:14:14.600> like<00:14:14.759> the 00:14:14.870 --> 00:14:14.880 align:start position:0% number it's just going to give like the 00:14:14.880 --> 00:14:18.470 align:start position:0% number it's just going to give like the one<00:14:15.160> bit<00:14:15.440> basically<00:14:15.839> who<00:14:16.040> won<00:14:16.560> right<00:14:17.279> and<00:14:17.720> or 00:14:18.470 --> 00:14:18.480 align:start position:0% one bit basically who won right and or 00:14:18.480 --> 00:14:20.189 align:start position:0% one bit basically who won right and or potentially<00:14:18.959> a<00:14:19.079> few<00:14:19.240> more<00:14:19.480> bits<00:14:19.759> if<00:14:19.839> it's<00:14:20.040> like 00:14:20.189 --> 00:14:20.199 align:start position:0% potentially a few more bits if it's like 00:14:20.199 --> 00:14:22.310 align:start position:0% potentially a few more bits if it's like quadratic<00:14:20.639> funding<00:14:21.160> right<00:14:21.720> and<00:14:21.839> the<00:14:21.959> way<00:14:22.120> that 00:14:22.310 --> 00:14:22.320 align:start position:0% quadratic funding right and the way that 00:14:22.320 --> 00:14:24.949 align:start position:0% quadratic funding right and the way that this<00:14:22.759> program<00:14:23.480> works<00:14:23.880> is<00:14:24.240> it<00:14:24.399> Tellies<00:14:24.800> the 00:14:24.949 --> 00:14:24.959 align:start position:0% this program works is it Tellies the 00:14:24.959 --> 00:14:28.150 align:start position:0% this program works is it Tellies the votes<00:14:25.600> and<00:14:25.720> it<00:14:25.920> also<00:14:26.320> checks<00:14:27.279> that<00:14:27.680> there<00:14:27.800> is<00:14:27.920> a 00:14:28.150 --> 00:14:28.160 align:start position:0% votes and it also checks that there is a 00:14:28.160 --> 00:14:29.910 align:start position:0% votes and it also checks that there is a proof<00:14:28.440> that<00:14:28.560> the<00:14:28.680> block<00:14:29.320> consent<00:14:29.680> has 00:14:29.910 --> 00:14:29.920 align:start position:0% proof that the block consent has 00:14:29.920 --> 00:14:32.030 align:start position:0% proof that the block consent has finalized<00:14:30.440> it<00:14:30.880> and<00:14:31.040> on<00:14:31.240> top<00:14:31.399> of<00:14:31.519> that<00:14:31.639> it<00:14:31.800> also 00:14:32.030 --> 00:14:32.040 align:start position:0% finalized it and on top of that it also 00:14:32.040 --> 00:14:33.710 align:start position:0% finalized it and on top of that it also can<00:14:32.199> check<00:14:32.440> for<00:14:32.720> like<00:14:32.880> some<00:14:33.040> little<00:14:33.320> amount<00:14:33.560> of 00:14:33.710 --> 00:14:33.720 align:start position:0% can check for like some little amount of 00:14:33.720 --> 00:14:35.389 align:start position:0% can check for like some little amount of proof<00:14:33.920> of<00:14:34.040> work<00:14:34.399> right<00:14:34.560> so<00:14:34.680> you<00:14:34.839> could<00:14:35.000> do<00:14:35.160> it 00:14:35.389 --> 00:14:35.399 align:start position:0% proof of work right so you could do it 00:14:35.399 --> 00:14:37.949 align:start position:0% proof of work right so you could do it like<00:14:36.040> say<00:14:36.360> like<00:14:36.440> $500<00:14:37.320> worth<00:14:37.480> of<00:14:37.600> proof<00:14:37.800> of 00:14:37.949 --> 00:14:37.959 align:start position:0% like say like $500 worth of proof of 00:14:37.959 --> 00:14:40.470 align:start position:0% like say like $500 worth of proof of work<00:14:38.440> or<00:14:38.600> you<00:14:38.720> could<00:14:38.959> imagine<00:14:39.560> like<00:14:39.959> ethereum 00:14:40.470 --> 00:14:40.480 align:start position:0% work or you could imagine like ethereum 00:14:40.480 --> 00:14:42.670 align:start position:0% work or you could imagine like ethereum eventually<00:14:41.000> adding<00:14:41.360> like<00:14:41.560> maybe<00:14:41.920> like 00:14:42.670 --> 00:14:42.680 align:start position:0% eventually adding like maybe like 00:14:42.680 --> 00:14:45.150 align:start position:0% eventually adding like maybe like $10,000<00:14:43.680> proof<00:14:43.880> of<00:14:44.000> work<00:14:44.199> on<00:14:44.360> every<00:14:44.600> finalized 00:14:45.150 --> 00:14:45.160 align:start position:0% $10,000 proof of work on every finalized 00:14:45.160 --> 00:14:47.749 align:start position:0% $10,000 proof of work on every finalized blocker<00:14:45.639> like<00:14:45.800> some<00:14:46.079> simple<00:14:46.880> uh<00:14:47.440> simple 00:14:47.749 --> 00:14:47.759 align:start position:0% blocker like some simple uh simple 00:14:47.759 --> 00:14:50.829 align:start position:0% blocker like some simple uh simple amounts<00:14:48.240> right<00:14:48.839> and<00:14:48.959> so<00:14:49.240> then<00:14:49.880> even<00:14:50.279> if<00:14:50.680> the 00:14:50.829 --> 00:14:50.839 align:start position:0% amounts right and so then even if the 00:14:50.839 --> 00:14:51.990 align:start position:0% amounts right and so then even if the blockchain 00:14:51.990 --> 00:14:52.000 align:start position:0% blockchain 00:14:52.000 --> 00:14:55.389 align:start position:0% blockchain consensus<00:14:53.079> colluded<00:14:54.079> um<00:14:54.680> even<00:14:54.959> if<00:14:55.199> like 00:14:55.389 --> 00:14:55.399 align:start position:0% consensus colluded um even if like 00:14:55.399 --> 00:14:57.189 align:start position:0% consensus colluded um even if like everyone<00:14:55.800> colluded<00:14:56.519> they<00:14:56.639> would<00:14:56.839> only<00:14:57.079> be 00:14:57.189 --> 00:14:57.199 align:start position:0% everyone colluded they would only be 00:14:57.199 --> 00:14:59.910 align:start position:0% everyone colluded they would only be able<00:14:57.360> to<00:14:57.600> extract<00:14:58.279> a<00:14:58.480> very<00:14:58.680> small<00:14:59.160> number<00:14:59.519> of 00:14:59.910 --> 00:14:59.920 align:start position:0% able to extract a very small number of 00:14:59.920 --> 00:15:01.990 align:start position:0% able to extract a very small number of bit<00:15:00.279> of<00:15:00.399> bits<00:15:00.600> of<00:15:00.759> entropy<00:15:01.240> from<00:15:01.440> the<00:15:01.560> system 00:15:01.990 --> 00:15:02.000 align:start position:0% bit of bits of entropy from the system 00:15:02.000 --> 00:15:04.710 align:start position:0% bit of bits of entropy from the system right<00:15:02.120> and<00:15:02.279> so<00:15:02.920> actually<00:15:03.519> deter<00:15:03.959> and<00:15:04.079> then<00:15:04.600> you 00:15:04.710 --> 00:15:04.720 align:start position:0% right and so actually deter and then you 00:15:04.720 --> 00:15:06.269 align:start position:0% right and so actually deter and then you can<00:15:04.880> also<00:15:05.120> make<00:15:05.320> the<00:15:05.480> program<00:15:05.880> add<00:15:06.040> a<00:15:06.120> little 00:15:06.269 --> 00:15:06.279 align:start position:0% can also make the program add a little 00:15:06.279 --> 00:15:08.990 align:start position:0% can also make the program add a little bit<00:15:06.399> of<00:15:06.519> gy<00:15:06.839> and<00:15:07.079> no<00:15:07.399> noise<00:15:07.959> and<00:15:08.079> so<00:15:08.360> extracting 00:15:08.990 --> 00:15:09.000 align:start position:0% bit of gy and no noise and so extracting 00:15:09.000 --> 00:15:10.790 align:start position:0% bit of gy and no noise and so extracting any<00:15:09.240> information<00:15:09.759> about<00:15:10.000> how<00:15:10.160> an<00:15:10.320> individual 00:15:10.790 --> 00:15:10.800 align:start position:0% any information about how an individual 00:15:10.800 --> 00:15:12.990 align:start position:0% any information about how an individual voter<00:15:11.160> voted<00:15:11.480> will<00:15:11.680> basically<00:15:12.160> just<00:15:12.360> become 00:15:12.990 --> 00:15:13.000 align:start position:0% voter voted will basically just become 00:15:13.000 --> 00:15:16.310 align:start position:0% voter voted will basically just become extremely<00:15:13.519> hard<00:15:14.279> so<00:15:15.199> this<00:15:15.320> is<00:15:15.600> like<00:15:16.040> very 00:15:16.310 --> 00:15:16.320 align:start position:0% extremely hard so this is like very 00:15:16.320 --> 00:15:19.870 align:start position:0% extremely hard so this is like very close<00:15:16.560> to<00:15:16.759> Ideal<00:15:17.279> right<00:15:17.560> so<00:15:18.519> but<00:15:18.680> there's<00:15:18.959> more 00:15:19.870 --> 00:15:19.880 align:start position:0% close to Ideal right so but there's more 00:15:19.880 --> 00:15:22.189 align:start position:0% close to Ideal right so but there's more so<00:15:20.000> we'll<00:15:20.199> talk<00:15:20.360> about<00:15:20.560> onot<00:15:21.000> signatures<00:15:21.759> onot 00:15:22.189 --> 00:15:22.199 align:start position:0% so we'll talk about onot signatures onot 00:15:22.199 --> 00:15:25.150 align:start position:0% so we'll talk about onot signatures onot signatures<00:15:22.800> are<00:15:23.279> A<00:15:23.720> Primitive<00:15:24.320> where<00:15:24.839> you<00:15:24.959> can 00:15:25.150 --> 00:15:25.160 align:start position:0% signatures are A Primitive where you can 00:15:25.160 --> 00:15:27.590 align:start position:0% signatures are A Primitive where you can make<00:15:25.480> you<00:15:25.600> can<00:15:25.759> have<00:15:25.880> a<00:15:26.120> key<00:15:26.800> where<00:15:27.079> that<00:15:27.279> key 00:15:27.590 --> 00:15:27.600 align:start position:0% make you can have a key where that key 00:15:27.600 --> 00:15:29.629 align:start position:0% make you can have a key where that key can<00:15:27.880> only<00:15:28.160> be<00:15:28.360> used<00:15:28.680> in<00:15:29.120> to<00:15:29.240> make<00:15:29.360> one 00:15:29.629 --> 00:15:29.639 align:start position:0% can only be used in to make one 00:15:29.639 --> 00:15:33.389 align:start position:0% can only be used in to make one signature<00:15:30.639> one<00:15:31.120> signatures<00:15:32.040> require<00:15:32.680> users 00:15:33.389 --> 00:15:33.399 align:start position:0% signature one signatures require users 00:15:33.399 --> 00:15:35.749 align:start position:0% signature one signatures require users to<00:15:33.600> have<00:15:33.839> quantum<00:15:34.279> computers<00:15:35.160> so<00:15:35.399> this<00:15:35.480> is<00:15:35.600> a 00:15:35.749 --> 00:15:35.759 align:start position:0% to have quantum computers so this is a 00:15:35.759 --> 00:15:37.910 align:start position:0% to have quantum computers so this is a milestone<00:15:36.240> that<00:15:36.319> will<00:15:36.519> come<00:15:36.800> at<00:15:37.319> quite<00:15:37.480> a<00:15:37.600> bit 00:15:37.910 --> 00:15:37.920 align:start position:0% milestone that will come at quite a bit 00:15:37.920 --> 00:15:39.629 align:start position:0% milestone that will come at quite a bit after<00:15:38.480> the<00:15:38.639> bad<00:15:38.839> guys<00:15:39.079> have<00:15:39.279> quantum 00:15:39.629 --> 00:15:39.639 align:start position:0% after the bad guys have quantum 00:15:39.639 --> 00:15:41.509 align:start position:0% after the bad guys have quantum computers<00:15:40.199> right<00:15:40.560> when<00:15:40.720> quantum<00:15:41.079> computers 00:15:41.509 --> 00:15:41.519 align:start position:0% computers right when quantum computers 00:15:41.519 --> 00:15:42.710 align:start position:0% computers right when quantum computers come<00:15:41.759> they're<00:15:41.920> going<00:15:42.000> to<00:15:42.120> be<00:15:42.279> like<00:15:42.480> hundred 00:15:42.710 --> 00:15:42.720 align:start position:0% come they're going to be like hundred 00:15:42.720 --> 00:15:45.030 align:start position:0% come they're going to be like hundred million<00:15:43.079> dollar<00:15:43.399> things<00:15:44.000> you<00:15:44.120> know<00:15:44.399> the<00:15:44.839> the 00:15:45.030 --> 00:15:45.040 align:start position:0% million dollar things you know the the 00:15:45.040 --> 00:15:47.269 align:start position:0% million dollar things you know the the bad<00:15:45.279> guys<00:15:45.480> or<00:15:45.680> at<00:15:45.800> least<00:15:46.480> the<00:15:46.639> people<00:15:46.920> that<00:15:47.079> we 00:15:47.269 --> 00:15:47.279 align:start position:0% bad guys or at least the people that we 00:15:47.279 --> 00:15:49.110 align:start position:0% bad guys or at least the people that we consider<00:15:47.680> threats<00:15:48.040> will<00:15:48.279> have<00:15:48.480> them<00:15:48.720> first 00:15:49.110 --> 00:15:49.120 align:start position:0% consider threats will have them first 00:15:49.120 --> 00:15:50.990 align:start position:0% consider threats will have them first right<00:15:49.560> and<00:15:49.680> so<00:15:49.959> you'll<00:15:50.199> have<00:15:50.319> to<00:15:50.480> wait<00:15:50.720> quite<00:15:50.880> a 00:15:50.990 --> 00:15:51.000 align:start position:0% right and so you'll have to wait quite a 00:15:51.000 --> 00:15:53.350 align:start position:0% right and so you'll have to wait quite a bit<00:15:51.120> of<00:15:51.319> time<00:15:51.639> after<00:15:52.079> that<00:15:52.600> until<00:15:53.000> regular 00:15:53.350 --> 00:15:53.360 align:start position:0% bit of time after that until regular 00:15:53.360 --> 00:15:55.309 align:start position:0% bit of time after that until regular users<00:15:53.759> can<00:15:53.920> also<00:15:54.160> have<00:15:54.319> quantum<00:15:54.759> computers 00:15:55.309 --> 00:15:55.319 align:start position:0% users can also have quantum computers 00:15:55.319 --> 00:15:57.550 align:start position:0% users can also have quantum computers right<00:15:56.000> but<00:15:56.199> you<00:15:56.319> do<00:15:56.519> is<00:15:56.839> what<00:15:57.000> what<00:15:57.079> this<00:15:57.240> ISS 00:15:57.550 --> 00:15:57.560 align:start position:0% right but you do is what what this ISS 00:15:57.560 --> 00:15:59.430 align:start position:0% right but you do is what what this ISS is<00:15:57.839> basically<00:15:58.440> yeah<00:15:58.680> you<00:15:58.759> know<00:15:59.079> you<00:15:59.160> can<00:15:59.319> have 00:15:59.430 --> 00:15:59.440 align:start position:0% is basically yeah you know you can have 00:15:59.440 --> 00:16:02.509 align:start position:0% is basically yeah you know you can have a<00:15:59.639> public<00:16:00.000> key<00:16:00.639> and<00:16:01.000> it's<00:16:01.120> a<00:16:01.279> mechanism<00:16:02.279> by 00:16:02.509 --> 00:16:02.519 align:start position:0% a public key and it's a mechanism by 00:16:02.519 --> 00:16:05.590 align:start position:0% a public key and it's a mechanism by which<00:16:03.120> it's<00:16:03.240> a<00:16:03.480> public<00:16:03.839> key<00:16:04.240> such<00:16:04.600> that<00:16:05.360> the 00:16:05.590 --> 00:16:05.600 align:start position:0% which it's a public key such that the 00:16:05.600 --> 00:16:08.670 align:start position:0% which it's a public key such that the you<00:16:05.920> for<00:16:06.319> any<00:16:06.680> given<00:16:07.360> uh<00:16:07.519> Nots<00:16:08.120> you're<00:16:08.360> only 00:16:08.670 --> 00:16:08.680 align:start position:0% you for any given uh Nots you're only 00:16:08.680 --> 00:16:12.069 align:start position:0% you for any given uh Nots you're only allow<00:16:09.519> it's<00:16:09.680> only<00:16:10.079> possible<00:16:11.040> for<00:16:11.440> the<00:16:11.759> owner 00:16:12.069 --> 00:16:12.079 align:start position:0% allow it's only possible for the owner 00:16:12.079 --> 00:16:14.949 align:start position:0% allow it's only possible for the owner of<00:16:12.199> the<00:16:12.360> private<00:16:12.759> key<00:16:13.199> to<00:16:13.440> sign<00:16:14.000> exactly<00:16:14.600> one 00:16:14.949 --> 00:16:14.959 align:start position:0% of the private key to sign exactly one 00:16:14.959 --> 00:16:17.110 align:start position:0% of the private key to sign exactly one message<00:16:15.399> with<00:16:15.560> that<00:16:15.720> Nots<00:16:16.519> and<00:16:16.800> this<00:16:16.920> all 00:16:17.110 --> 00:16:17.120 align:start position:0% message with that Nots and this all 00:16:17.120 --> 00:16:18.749 align:start position:0% message with that Nots and this all depends<00:16:17.440> on<00:16:17.600> the<00:16:17.720> quantum<00:16:18.120> no<00:16:18.360> cloning 00:16:18.749 --> 00:16:18.759 align:start position:0% depends on the quantum no cloning 00:16:18.759 --> 00:16:20.509 align:start position:0% depends on the quantum no cloning theorem<00:16:19.199> right<00:16:19.519> if<00:16:19.639> you<00:16:19.759> have<00:16:19.880> a<00:16:20.000> Quantum 00:16:20.509 --> 00:16:20.519 align:start position:0% theorem right if you have a Quantum 00:16:20.519 --> 00:16:23.590 align:start position:0% theorem right if you have a Quantum State<00:16:21.399> then<00:16:22.040> you<00:16:22.240> cannot<00:16:22.720> actually<00:16:23.240> copy<00:16:23.480> the 00:16:23.590 --> 00:16:23.600 align:start position:0% State then you cannot actually copy the 00:16:23.600 --> 00:16:25.069 align:start position:0% State then you cannot actually copy the quantum<00:16:24.000> State<00:16:24.240> there's<00:16:24.560> mathematical 00:16:25.069 --> 00:16:25.079 align:start position:0% quantum State there's mathematical 00:16:25.079 --> 00:16:27.790 align:start position:0% quantum State there's mathematical proofs<00:16:25.360> that<00:16:25.519> this<00:16:25.639> is<00:16:25.959> impossible<00:16:26.959> and<00:16:27.399> the 00:16:27.790 --> 00:16:27.800 align:start position:0% proofs that this is impossible and the 00:16:27.800 --> 00:16:30.430 align:start position:0% proofs that this is impossible and the signature<00:16:28.319> scheme<00:16:29.040> depends<00:16:29.560> on<00:16:29.800> solving<00:16:30.199> a 00:16:30.430 --> 00:16:30.440 align:start position:0% signature scheme depends on solving a 00:16:30.440 --> 00:16:32.550 align:start position:0% signature scheme depends on solving a problem<00:16:30.839> which<00:16:31.040> is<00:16:31.600> um<00:16:31.800> infeasible<00:16:32.399> with 00:16:32.550 --> 00:16:32.560 align:start position:0% problem which is um infeasible with 00:16:32.560 --> 00:16:34.189 align:start position:0% problem which is um infeasible with classical<00:16:33.040> computers<00:16:33.480> but<00:16:33.639> doable<00:16:34.040> with 00:16:34.189 --> 00:16:34.199 align:start position:0% classical computers but doable with 00:16:34.199 --> 00:16:35.829 align:start position:0% classical computers but doable with quantum<00:16:34.560> computers<00:16:35.319> and<00:16:35.440> so<00:16:35.639> you're 00:16:35.829 --> 00:16:35.839 align:start position:0% quantum computers and so you're 00:16:35.839 --> 00:16:38.829 align:start position:0% quantum computers and so you're basically<00:16:36.800> like<00:16:37.160> proving<00:16:37.720> that<00:16:37.839> you<00:16:38.160> have<00:16:38.680> and 00:16:38.829 --> 00:16:38.839 align:start position:0% basically like proving that you have and 00:16:38.839 --> 00:16:40.230 align:start position:0% basically like proving that you have and that<00:16:38.959> you're<00:16:39.199> spending<00:16:39.680> one<00:16:39.839> of<00:16:40.000> these 00:16:40.230 --> 00:16:40.240 align:start position:0% that you're spending one of these 00:16:40.240 --> 00:16:43.309 align:start position:0% that you're spending one of these unclonable<00:16:40.920> Quantum<00:16:41.319> States<00:16:42.160> so<00:16:42.920> this<00:16:43.079> could 00:16:43.309 --> 00:16:43.319 align:start position:0% unclonable Quantum States so this could 00:16:43.319 --> 00:16:45.069 align:start position:0% unclonable Quantum States so this could actually<00:16:43.560> be<00:16:43.720> used<00:16:43.959> to<00:16:44.120> make<00:16:44.319> Quantum<00:16:44.680> money 00:16:45.069 --> 00:16:45.079 align:start position:0% actually be used to make Quantum money 00:16:45.079 --> 00:16:46.870 align:start position:0% actually be used to make Quantum money without<00:16:45.240> a<00:16:45.399> blockchain<00:16:46.199> now<00:16:46.399> it<00:16:46.560> doesn't 00:16:46.870 --> 00:16:46.880 align:start position:0% without a blockchain now it doesn't 00:16:46.880 --> 00:16:48.269 align:start position:0% without a blockchain now it doesn't remove<00:16:47.240> the<00:16:47.319> need<00:16:47.519> for<00:16:47.720> blockchains 00:16:48.269 --> 00:16:48.279 align:start position:0% remove the need for blockchains 00:16:48.279 --> 00:16:50.189 align:start position:0% remove the need for blockchains completely<00:16:49.000> it<00:16:49.199> still<00:16:49.480> doesn't<00:16:49.839> solve 00:16:50.189 --> 00:16:50.199 align:start position:0% completely it still doesn't solve 00:16:50.199 --> 00:16:52.710 align:start position:0% completely it still doesn't solve sensorship<00:16:50.800> resistance<00:16:51.279> on<00:16:51.440> its<00:16:51.560> own<00:16:52.199> but 00:16:52.710 --> 00:16:52.720 align:start position:0% sensorship resistance on its own but 00:16:52.720 --> 00:16:54.550 align:start position:0% sensorship resistance on its own but this<00:16:52.920> is<00:16:53.079> the<00:16:53.240> thing<00:16:53.440> that<00:16:53.639> like<00:16:54.120> I'm<00:16:54.319> not<00:16:54.480> I 00:16:54.550 --> 00:16:54.560 align:start position:0% this is the thing that like I'm not I 00:16:54.560 --> 00:16:56.590 align:start position:0% this is the thing that like I'm not I don't<00:16:54.759> want<00:16:55.000> to<00:16:55.279> call<00:16:55.600> an<00:16:55.800> Egyptian<00:16:56.319> god 00:16:56.590 --> 00:16:56.600 align:start position:0% don't want to call an Egyptian god 00:16:56.600 --> 00:16:58.990 align:start position:0% don't want to call an Egyptian god protocol<00:16:57.160> because<00:16:57.720> like<00:16:57.880> this<00:16:57.959> is<00:16:58.160> not<00:16:58.440> just 00:16:58.990 --> 00:16:59.000 align:start position:0% protocol because like this is not just 00:16:59.000 --> 00:17:01.030 align:start position:0% protocol because like this is not just the<00:16:59.160> land<00:16:59.440> of<00:16:59.880> computer<00:17:00.279> science<00:17:00.680> this<00:17:00.800> is 00:17:01.030 --> 00:17:01.040 align:start position:0% the land of computer science this is 00:17:01.040 --> 00:17:03.110 align:start position:0% the land of computer science this is like<00:17:01.199> in<00:17:01.279> the<00:17:01.440> land<00:17:01.639> of<00:17:01.839> physics<00:17:02.360> right<00:17:02.800> and<00:17:02.920> so 00:17:03.110 --> 00:17:03.120 align:start position:0% like in the land of physics right and so 00:17:03.120 --> 00:17:05.350 align:start position:0% like in the land of physics right and so it's<00:17:03.360> like<00:17:03.959> it's<00:17:04.160> some<00:17:04.360> kind<00:17:04.520> of<00:17:04.720> tier<00:17:05.120> that's 00:17:05.350 --> 00:17:05.360 align:start position:0% it's like it's some kind of tier that's 00:17:05.360 --> 00:17:06.829 align:start position:0% it's like it's some kind of tier that's like<00:17:05.520> even<00:17:05.760> more<00:17:05.959> powerful<00:17:06.400> than<00:17:06.559> these 00:17:06.829 --> 00:17:06.839 align:start position:0% like even more powerful than these 00:17:06.839 --> 00:17:10.429 align:start position:0% like even more powerful than these things<00:17:08.240> so<00:17:09.240> when<00:17:09.439> will<00:17:09.640> we<00:17:09.799> get<00:17:10.000> all<00:17:10.120> of<00:17:10.240> this 00:17:10.429 --> 00:17:10.439 align:start position:0% things so when will we get all of this 00:17:10.439 --> 00:17:12.990 align:start position:0% things so when will we get all of this technology<00:17:11.079> right<00:17:11.280> so<00:17:11.720> zekus<00:17:12.160> SARS<00:17:12.799> we're 00:17:12.990 --> 00:17:13.000 align:start position:0% technology right so zekus SARS we're 00:17:13.000 --> 00:17:14.789 align:start position:0% technology right so zekus SARS we're seeing<00:17:13.280> an<00:17:13.439> increasingly<00:17:14.120> high<00:17:14.360> level<00:17:14.600> of 00:17:14.789 --> 00:17:14.799 align:start position:0% seeing an increasingly high level of 00:17:14.799 --> 00:17:17.590 align:start position:0% seeing an increasingly high level of maturity<00:17:15.559> I<00:17:15.600> mean<00:17:15.880> I<00:17:16.079> personally<00:17:16.919> look<00:17:17.400> would 00:17:17.590 --> 00:17:17.600 align:start position:0% maturity I mean I personally look would 00:17:17.600 --> 00:17:19.350 align:start position:0% maturity I mean I personally look would declare<00:17:18.039> Victory<00:17:18.520> once<00:17:18.679> we're<00:17:18.919> able<00:17:19.120> to 00:17:19.350 --> 00:17:19.360 align:start position:0% declare Victory once we're able to 00:17:19.360 --> 00:17:21.870 align:start position:0% declare Victory once we're able to actually<00:17:19.799> have<00:17:20.360> ZK<00:17:20.799> EVMS<00:17:21.280> that<00:17:21.360> are<00:17:21.520> proving 00:17:21.870 --> 00:17:21.880 align:start position:0% actually have ZK EVMS that are proving 00:17:21.880 --> 00:17:24.150 align:start position:0% actually have ZK EVMS that are proving blocks<00:17:22.360> within<00:17:22.600> one<00:17:22.880> swad<00:17:23.559> currently<00:17:23.919> we're 00:17:24.150 --> 00:17:24.160 align:start position:0% blocks within one swad currently we're 00:17:24.160 --> 00:17:25.549 align:start position:0% blocks within one swad currently we're probably<00:17:24.400> still<00:17:24.679> like<00:17:24.839> a<00:17:24.959> couple<00:17:25.160> of<00:17:25.280> orders 00:17:25.549 --> 00:17:25.559 align:start position:0% probably still like a couple of orders 00:17:25.559 --> 00:17:27.470 align:start position:0% probably still like a couple of orders of<00:17:25.720> magnitude<00:17:26.199> away<00:17:26.400> from<00:17:26.640> this<00:17:27.160> but<00:17:27.280> there's 00:17:27.470 --> 00:17:27.480 align:start position:0% of magnitude away from this but there's 00:17:27.480 --> 00:17:29.190 align:start position:0% of magnitude away from this but there's a<00:17:27.640> huge<00:17:27.839> amount<00:17:28.039> of<00:17:28.240> progress<00:17:28.600> there's<00:17:28.919> a<00:17:29.039> huge 00:17:29.190 --> 00:17:29.200 align:start position:0% a huge amount of progress there's a huge 00:17:29.200 --> 00:17:30.909 align:start position:0% a huge amount of progress there's a huge amount<00:17:29.400> of<00:17:29.520> work<00:17:29.760> in<00:17:29.880> binary<00:17:30.240> field<00:17:30.559> proving 00:17:30.909 --> 00:17:30.919 align:start position:0% amount of work in binary field proving 00:17:30.919 --> 00:17:35.110 align:start position:0% amount of work in binary field proving systems<00:17:31.679> like<00:17:31.840> basically<00:17:32.280> the<00:17:32.400> race<00:17:32.640> is<00:17:32.960> on<00:17:34.120> um 00:17:35.110 --> 00:17:35.120 align:start position:0% systems like basically the race is on um 00:17:35.120 --> 00:17:37.710 align:start position:0% systems like basically the race is on um FHA<00:17:36.000> we're<00:17:36.240> starting<00:17:36.600> to<00:17:36.880> see<00:17:37.280> viable 00:17:37.710 --> 00:17:37.720 align:start position:0% FHA we're starting to see viable 00:17:37.720 --> 00:17:40.430 align:start position:0% FHA we're starting to see viable applications<00:17:38.720> so<00:17:39.160> if<00:17:39.320> anyone<00:17:39.640> here<00:17:39.840> was<00:17:40.120> at<00:17:40.280> at 00:17:40.430 --> 00:17:40.440 align:start position:0% applications so if anyone here was at at 00:17:40.440 --> 00:17:42.150 align:start position:0% applications so if anyone here was at at H<00:17:40.720> City<00:17:41.000> you<00:17:41.160> probably<00:17:41.400> got<00:17:41.559> one<00:17:41.679> of<00:17:41.880> those 00:17:42.150 --> 00:17:42.160 align:start position:0% H City you probably got one of those 00:17:42.160 --> 00:17:44.029 align:start position:0% H City you probably got one of those like<00:17:42.320> Square<00:17:42.679> wristband<00:17:43.240> things<00:17:43.799> and<00:17:43.919> there 00:17:44.029 --> 00:17:44.039 align:start position:0% like Square wristband things and there 00:17:44.039 --> 00:17:45.909 align:start position:0% like Square wristband things and there was<00:17:44.160> an<00:17:44.360> application<00:17:44.919> called<00:17:45.160> cursive<00:17:45.720> where 00:17:45.909 --> 00:17:45.919 align:start position:0% was an application called cursive where 00:17:45.919 --> 00:17:47.990 align:start position:0% was an application called cursive where basically<00:17:46.919> you<00:17:47.080> could<00:17:47.320> provide<00:17:47.559> a<00:17:47.720> list<00:17:47.880> of 00:17:47.990 --> 00:17:48.000 align:start position:0% basically you could provide a list of 00:17:48.000 --> 00:17:49.350 align:start position:0% basically you could provide a list of what<00:17:48.120> your<00:17:48.320> interests<00:17:48.720> are<00:17:48.960> someone<00:17:49.200> else 00:17:49.350 --> 00:17:49.360 align:start position:0% what your interests are someone else 00:17:49.360 --> 00:17:50.590 align:start position:0% what your interests are someone else could<00:17:49.559> provide<00:17:50.000> a<00:17:50.080> list<00:17:50.240> of<00:17:50.360> what<00:17:50.480> their 00:17:50.590 --> 00:17:50.600 align:start position:0% could provide a list of what their 00:17:50.600 --> 00:17:52.950 align:start position:0% could provide a list of what their interests<00:17:50.960> are<00:17:51.400> and<00:17:51.720> actually<00:17:52.000> used<00:17:52.360> FHA<00:17:52.799> to 00:17:52.950 --> 00:17:52.960 align:start position:0% interests are and actually used FHA to 00:17:52.960 --> 00:17:54.870 align:start position:0% interests are and actually used FHA to compute<00:17:53.280> the<00:17:53.520> intersection<00:17:54.520> so<00:17:54.679> we're 00:17:54.870 --> 00:17:54.880 align:start position:0% compute the intersection so we're 00:17:54.880 --> 00:17:56.950 align:start position:0% compute the intersection so we're starting<00:17:55.240> to<00:17:55.480> like<00:17:55.600> see<00:17:55.919> toy<00:17:56.280> applications 00:17:56.950 --> 00:17:56.960 align:start position:0% starting to like see toy applications 00:17:56.960 --> 00:17:59.750 align:start position:0% starting to like see toy applications that<00:17:57.120> like<00:17:57.280> right<00:17:57.559> consumers<00:17:58.440> can<00:17:59.200> use<00:17:59.520> on 00:17:59.750 --> 00:17:59.760 align:start position:0% that like right consumers can use on 00:17:59.760 --> 00:18:03.070 align:start position:0% that like right consumers can use on local<00:18:00.159> devices<00:18:01.159> the<00:18:01.280> FHA<00:18:02.000> has<00:18:02.360> roughly<00:18:02.919> a 00:18:03.070 --> 00:18:03.080 align:start position:0% local devices the FHA has roughly a 00:18:03.080 --> 00:18:06.070 align:start position:0% local devices the FHA has roughly a million<00:18:03.559> Factor<00:18:03.960> overhead<00:18:04.840> and<00:18:05.039> so<00:18:05.640> you<00:18:05.799> can 00:18:06.070 --> 00:18:06.080 align:start position:0% million Factor overhead and so you can 00:18:06.080 --> 00:18:08.990 align:start position:0% million Factor overhead and so you can run<00:18:06.480> business<00:18:07.039> logic<00:18:07.600> inside<00:18:07.919> of<00:18:08.080> it<00:18:08.640> but<00:18:08.840> you 00:18:08.990 --> 00:18:09.000 align:start position:0% run business logic inside of it but you 00:18:09.000 --> 00:18:10.950 align:start position:0% run business logic inside of it but you can<00:18:09.559> realistically<00:18:10.240> you<00:18:10.360> cannot<00:18:10.679> run 00:18:10.950 --> 00:18:10.960 align:start position:0% can realistically you cannot run 00:18:10.960 --> 00:18:12.909 align:start position:0% can realistically you cannot run cryptography<00:18:11.600> inside<00:18:11.840> of<00:18:11.960> it<00:18:12.200> right<00:18:12.520> so<00:18:12.720> it's 00:18:12.909 --> 00:18:12.919 align:start position:0% cryptography inside of it right so it's 00:18:12.919 --> 00:18:15.549 align:start position:0% cryptography inside of it right so it's like<00:18:13.080> at<00:18:13.280> that<00:18:13.480> interesting<00:18:14.400> level<00:18:15.000> where 00:18:15.549 --> 00:18:15.559 align:start position:0% like at that interesting level where 00:18:15.559 --> 00:18:17.789 align:start position:0% like at that interesting level where it's<00:18:15.799> like<00:18:16.000> you<00:18:16.200> good<00:18:16.360> for<00:18:16.600> some<00:18:16.880> things<00:18:17.400> not 00:18:17.789 --> 00:18:17.799 align:start position:0% it's like you good for some things not 00:18:17.799 --> 00:18:19.430 align:start position:0% it's like you good for some things not it's<00:18:17.960> still<00:18:18.200> not<00:18:18.400> good<00:18:18.520> for<00:18:18.679> a<00:18:18.799> lot<00:18:18.919> of<00:18:19.120> things 00:18:19.430 --> 00:18:19.440 align:start position:0% it's still not good for a lot of things 00:18:19.440 --> 00:18:21.789 align:start position:0% it's still not good for a lot of things it's<00:18:19.760> uh<00:18:19.919> you<00:18:20.039> know<00:18:20.200> in<00:18:20.320> that<00:18:20.480> middle<00:18:20.799> Zone 00:18:21.789 --> 00:18:21.799 align:start position:0% it's uh you know in that middle Zone 00:18:21.799 --> 00:18:24.310 align:start position:0% it's uh you know in that middle Zone alisation<00:18:22.799> the<00:18:23.000> big<00:18:23.200> news<00:18:23.559> over<00:18:23.760> the<00:18:23.919> last<00:18:24.120> few 00:18:24.310 --> 00:18:24.320 align:start position:0% alisation the big news over the last few 00:18:24.320 --> 00:18:25.549 align:start position:0% alisation the big news over the last few years<00:18:24.600> is<00:18:24.720> that<00:18:24.840> we're<00:18:24.960> starting<00:18:25.200> to<00:18:25.320> see 00:18:25.549 --> 00:18:25.559 align:start position:0% years is that we're starting to see 00:18:25.559 --> 00:18:28.350 align:start position:0% years is that we're starting to see viable<00:18:25.960> protocols<00:18:26.520> in<00:18:26.919> 2020<00:18:27.919> there<00:18:28.039> was<00:18:28.200> the 00:18:28.350 --> 00:18:28.360 align:start position:0% viable protocols in 2020 there was the 00:18:28.360 --> 00:18:30.310 align:start position:0% viable protocols in 2020 there was the first<00:18:28.799> protocol<00:18:29.240> that<00:18:29.360> was<00:18:29.559> dependent<00:18:30.039> on 00:18:30.310 --> 00:18:30.320 align:start position:0% first protocol that was dependent on 00:18:30.320 --> 00:18:33.710 align:start position:0% first protocol that was dependent on only<00:18:30.640> standard<00:18:31.480> assumptions<00:18:32.480> and<00:18:33.280> this 00:18:33.710 --> 00:18:33.720 align:start position:0% only standard assumptions and this 00:18:33.720 --> 00:18:35.270 align:start position:0% only standard assumptions and this protocol<00:18:34.200> someone<00:18:34.559> actually<00:18:34.799> tried<00:18:35.080> to 00:18:35.270 --> 00:18:35.280 align:start position:0% protocol someone actually tried to 00:18:35.280 --> 00:18:37.230 align:start position:0% protocol someone actually tried to implement<00:18:35.720> it<00:18:36.200> and<00:18:36.360> they<00:18:36.720> discovered<00:18:37.039> that<00:18:37.120> it 00:18:37.230 --> 00:18:37.240 align:start position:0% implement it and they discovered that it 00:18:37.240 --> 00:18:39.230 align:start position:0% implement it and they discovered that it would<00:18:37.400> take<00:18:37.640> 10<00:18:37.880> to<00:18:38.000> the<00:18:38.159> power<00:18:38.360> of<00:18:38.520> 27<00:18:39.039> years 00:18:39.230 --> 00:18:39.240 align:start position:0% would take 10 to the power of 27 years 00:18:39.240 --> 00:18:42.789 align:start position:0% would take 10 to the power of 27 years to<00:18:39.520> run<00:18:40.520> a<00:18:40.640> year<00:18:40.880> later<00:18:41.520> someone<00:18:41.919> created<00:18:42.400> a 00:18:42.789 --> 00:18:42.799 align:start position:0% to run a year later someone created a 00:18:42.799 --> 00:18:44.630 align:start position:0% to run a year later someone created a slightly<00:18:43.280> improved<00:18:43.720> protocol<00:18:44.280> and<00:18:44.400> someone 00:18:44.630 --> 00:18:44.640 align:start position:0% slightly improved protocol and someone 00:18:44.640 --> 00:18:46.110 align:start position:0% slightly improved protocol and someone else<00:18:44.880> started<00:18:45.120> to<00:18:45.280> implement<00:18:45.640> it<00:18:45.799> and<00:18:45.919> they're 00:18:46.110 --> 00:18:46.120 align:start position:0% else started to implement it and they're 00:18:46.120 --> 00:18:47.510 align:start position:0% else started to implement it and they're estimating<00:18:46.640> that<00:18:46.720> it's<00:18:46.880> going<00:18:46.960> to<00:18:47.120> take<00:18:47.320> one 00:18:47.510 --> 00:18:47.520 align:start position:0% estimating that it's going to take one 00:18:47.520 --> 00:18:51.190 align:start position:0% estimating that it's going to take one year<00:18:47.679> to<00:18:48.039> run<00:18:49.039> now<00:18:49.520> there's<00:18:49.799> also<00:18:50.679> a<00:18:50.840> separate 00:18:51.190 --> 00:18:51.200 align:start position:0% year to run now there's also a separate 00:18:51.200 --> 00:18:53.230 align:start position:0% year to run now there's also a separate line<00:18:51.360> of<00:18:51.559> work<00:18:52.120> that's<00:18:52.360> trying<00:18:52.640> to<00:18:52.840> make<00:18:53.000> off 00:18:53.230 --> 00:18:53.240 align:start position:0% line of work that's trying to make off 00:18:53.240 --> 00:18:55.789 align:start position:0% line of work that's trying to make off escas<00:18:53.720> protocols<00:18:54.240> based<00:18:54.520> on<00:18:55.080> slightly<00:18:55.520> more 00:18:55.789 --> 00:18:55.799 align:start position:0% escas protocols based on slightly more 00:18:55.799 --> 00:18:57.590 align:start position:0% escas protocols based on slightly more exotic<00:18:56.240> assumptions<00:18:57.039> and<00:18:57.120> it's<00:18:57.360> like 00:18:57.590 --> 00:18:57.600 align:start position:0% exotic assumptions and it's like 00:18:57.600 --> 00:18:59.590 align:start position:0% exotic assumptions and it's like actually<00:18:57.919> more<00:18:58.200> debatable<00:18:58.880> in<00:18:59.000> the<00:18:59.120> long<00:18:59.360> run 00:18:59.590 --> 00:18:59.600 align:start position:0% actually more debatable in the long run 00:18:59.600 --> 00:19:01.070 align:start position:0% actually more debatable in the long run whether<00:18:59.840> this<00:18:59.960> is<00:19:00.080> more<00:19:00.240> or<00:19:00.440> less<00:19:00.640> secure 00:19:01.070 --> 00:19:01.080 align:start position:0% whether this is more or less secure 00:19:01.080 --> 00:19:02.909 align:start position:0% whether this is more or less secure right<00:19:01.240> because<00:19:01.480> it's<00:19:01.720> like<00:19:02.280> on<00:19:02.440> the<00:19:02.520> one<00:19:02.720> hand 00:19:02.909 --> 00:19:02.919 align:start position:0% right because it's like on the one hand 00:19:02.919 --> 00:19:04.630 align:start position:0% right because it's like on the one hand you<00:19:03.039> have<00:19:03.240> more<00:19:03.520> exotic<00:19:03.919> lattice<00:19:04.280> based 00:19:04.630 --> 00:19:04.640 align:start position:0% you have more exotic lattice based 00:19:04.640 --> 00:19:06.230 align:start position:0% you have more exotic lattice based assumptions<00:19:05.200> that<00:19:05.280> are<00:19:05.480> like<00:19:05.640> based<00:19:05.880> on 00:19:06.230 --> 00:19:06.240 align:start position:0% assumptions that are like based on 00:19:06.240 --> 00:19:08.149 align:start position:0% assumptions that are like based on multi-linear<00:19:06.960> map<00:19:07.200> constructions<00:19:07.840> and<00:19:08.039> like 00:19:08.149 --> 00:19:08.159 align:start position:0% multi-linear map constructions and like 00:19:08.159 --> 00:19:09.830 align:start position:0% multi-linear map constructions and like zero<00:19:08.480> testing<00:19:08.799> and<00:19:08.960> like<00:19:09.159> that<00:19:09.280> whole<00:19:09.440> line<00:19:09.640> of 00:19:09.830 --> 00:19:09.840 align:start position:0% zero testing and like that whole line of 00:19:09.840 --> 00:19:11.630 align:start position:0% zero testing and like that whole line of stuff<00:19:10.280> but<00:19:10.520> on<00:19:10.640> the<00:19:10.760> other<00:19:11.000> side<00:19:11.200> you<00:19:11.400> have 00:19:11.630 --> 00:19:11.640 align:start position:0% stuff but on the other side you have 00:19:11.640 --> 00:19:14.070 align:start position:0% stuff but on the other side you have like<00:19:12.080> Normie<00:19:12.640> assumptions<00:19:13.120> about<00:19:13.360> luses<00:19:14.039> I 00:19:14.070 --> 00:19:14.080 align:start position:0% like Normie assumptions about luses I 00:19:14.080 --> 00:19:15.549 align:start position:0% like Normie assumptions about luses I mean<00:19:14.280> you<00:19:14.360> know<00:19:14.520> go<00:19:14.840> go<00:19:14.960> out<00:19:15.080> and<00:19:15.240> like<00:19:15.360> ask 00:19:15.549 --> 00:19:15.559 align:start position:0% mean you know go go out and like ask 00:19:15.559 --> 00:19:17.029 align:start position:0% mean you know go go out and like ask anori<00:19:16.039> what<00:19:16.200> they<00:19:16.320> what<00:19:16.400> they<00:19:16.520> assume<00:19:16.760> in<00:19:16.880> belt 00:19:17.029 --> 00:19:17.039 align:start position:0% anori what they what they assume in belt 00:19:17.039 --> 00:19:19.230 align:start position:0% anori what they what they assume in belt lce<00:19:17.360> is<00:19:17.600> right<00:19:17.760> that<00:19:17.880> kind<00:19:18.039> of<00:19:18.240> stuff<00:19:18.919> um<00:19:19.080> and 00:19:19.230 --> 00:19:19.240 align:start position:0% lce is right that kind of stuff um and 00:19:19.240 --> 00:19:20.630 align:start position:0% lce is right that kind of stuff um and but<00:19:19.480> at<00:19:19.600> the<00:19:19.720> same<00:19:19.919> time<00:19:20.080> you<00:19:20.240> have<00:19:20.320> to<00:19:20.480> like 00:19:20.630 --> 00:19:20.640 align:start position:0% but at the same time you have to like 00:19:20.640 --> 00:19:22.950 align:start position:0% but at the same time you have to like assume<00:19:21.080> and<00:19:21.400> that<00:19:21.960> and<00:19:22.240> elliptic<00:19:22.600> Cur 00:19:22.950 --> 00:19:22.960 align:start position:0% assume and that and elliptic Cur 00:19:22.960 --> 00:19:24.710 align:start position:0% assume and that and elliptic Cur pairings<00:19:23.559> and<00:19:23.880> like<00:19:24.000> one<00:19:24.120> or<00:19:24.240> two<00:19:24.480> other 00:19:24.710 --> 00:19:24.720 align:start position:0% pairings and like one or two other 00:19:24.720 --> 00:19:27.510 align:start position:0% pairings and like one or two other things<00:19:25.080> right<00:19:25.520> and<00:19:25.679> so<00:19:26.120> but<00:19:26.760> that<00:19:27.000> stuff<00:19:27.400> you 00:19:27.510 --> 00:19:27.520 align:start position:0% things right and so but that stuff you 00:19:27.520 --> 00:19:29.350 align:start position:0% things right and so but that stuff you know<00:19:27.720> if<00:19:27.799> you<00:19:27.919> want<00:19:28.039> to<00:19:28.280> in<00:19:28.799> office<00:19:29.080> get<00:19:29.200> a 00:19:29.350 --> 00:19:29.360 align:start position:0% know if you want to in office get a 00:19:29.360 --> 00:19:31.070 align:start position:0% know if you want to in office get a program<00:19:29.640> it<00:19:29.760> takes<00:19:30.039> like<00:19:30.159> a<00:19:30.280> couple<00:19:30.480> of<00:19:30.640> weeks 00:19:31.070 --> 00:19:31.080 align:start position:0% program it takes like a couple of weeks 00:19:31.080 --> 00:19:32.789 align:start position:0% program it takes like a couple of weeks right<00:19:31.559> and<00:19:31.640> then<00:19:31.799> one<00:19:32.039> shot<00:19:32.240> signature<00:19:32.600> is 00:19:32.789 --> 00:19:32.799 align:start position:0% right and then one shot signature is 00:19:32.799 --> 00:19:35.270 align:start position:0% right and then one shot signature is obviously<00:19:33.240> no<00:19:33.480> idea<00:19:33.919> definitely<00:19:34.320> a<00:19:34.520> long<00:19:34.760> time 00:19:35.270 --> 00:19:35.280 align:start position:0% obviously no idea definitely a long time 00:19:35.280 --> 00:19:37.070 align:start position:0% obviously no idea definitely a long time and<00:19:35.400> we'll<00:19:35.520> see<00:19:35.760> quantum<00:19:36.200> computers<00:19:36.720> break 00:19:37.070 --> 00:19:37.080 align:start position:0% and we'll see quantum computers break 00:19:37.080 --> 00:19:39.950 align:start position:0% and we'll see quantum computers break half<00:19:37.240> of<00:19:37.440> existing<00:19:37.919> cryptography<00:19:38.960> including 00:19:39.950 --> 00:19:39.960 align:start position:0% half of existing cryptography including 00:19:39.960 --> 00:19:41.950 align:start position:0% half of existing cryptography including anything<00:19:40.280> lip<00:19:40.520> to<00:19:40.720> curve<00:19:40.960> based<00:19:41.400> long<00:19:41.640> before 00:19:41.950 --> 00:19:41.960 align:start position:0% anything lip to curve based long before 00:19:41.960 --> 00:19:44.390 align:start position:0% anything lip to curve based long before this<00:19:42.159> actually<00:19:42.480> becomes<00:19:42.880> possible<00:19:43.480> so 00:19:44.390 --> 00:19:44.400 align:start position:0% this actually becomes possible so 00:19:44.400 --> 00:19:46.430 align:start position:0% this actually becomes possible so basically<00:19:44.880> I<00:19:44.960> think<00:19:45.120> the<00:19:45.240> takeaway<00:19:45.679> is<00:19:45.960> that 00:19:46.430 --> 00:19:46.440 align:start position:0% basically I think the takeaway is that 00:19:46.440 --> 00:19:48.750 align:start position:0% basically I think the takeaway is that all<00:19:46.720> this<00:19:46.919> stuff<00:19:47.200> that<00:19:47.360> was<00:19:47.600> like<00:19:48.080> extreme 00:19:48.750 --> 00:19:48.760 align:start position:0% all this stuff that was like extreme 00:19:48.760 --> 00:19:51.549 align:start position:0% all this stuff that was like extreme science<00:19:49.200> fiction<00:19:50.080> a<00:19:50.240> decade<00:19:50.600> ago<00:19:51.159> is<00:19:51.360> like 00:19:51.549 --> 00:19:51.559 align:start position:0% science fiction a decade ago is like 00:19:51.559 --> 00:19:53.789 align:start position:0% science fiction a decade ago is like slowly<00:19:52.080> coming<00:19:52.320> into<00:19:52.679> view<00:19:53.120> right<00:19:53.559> every 00:19:53.789 --> 00:19:53.799 align:start position:0% slowly coming into view right every 00:19:53.799 --> 00:19:55.950 align:start position:0% slowly coming into view right every single<00:19:54.159> piece<00:19:54.440> is<00:19:54.679> like<00:19:54.960> with<00:19:55.240> every<00:19:55.520> single 00:19:55.950 --> 00:19:55.960 align:start position:0% single piece is like with every single 00:19:55.960 --> 00:19:58.270 align:start position:0% single piece is like with every single passing<00:19:56.400> year<00:19:56.960> is<00:19:57.200> becoming<00:19:57.720> slightly<00:19:58.120> more 00:19:58.270 --> 00:19:58.280 align:start position:0% passing year is becoming slightly more 00:19:58.280 --> 00:20:00.270 align:start position:0% passing year is becoming slightly more and<00:19:58.400> more<00:19:58.799> clear<00:19:59.440> and<00:19:59.640> I<00:19:59.760> think<00:19:59.919> we<00:20:00.039> can 00:20:00.270 --> 00:20:00.280 align:start position:0% and more clear and I think we can 00:20:00.280 --> 00:20:02.230 align:start position:0% and more clear and I think we can actually<00:20:00.600> really<00:20:01.159> start<00:20:01.440> getting<00:20:01.880> excited 00:20:02.230 --> 00:20:02.240 align:start position:0% actually really start getting excited 00:20:02.240 --> 00:20:03.549 align:start position:0% actually really start getting excited about<00:20:02.480> these<00:20:02.640> things<00:20:02.919> right<00:20:03.039> and<00:20:03.120> we<00:20:03.320> get 00:20:03.549 --> 00:20:03.559 align:start position:0% about these things right and we get 00:20:03.559 --> 00:20:06.230 align:start position:0% about these things right and we get excited<00:20:03.919> about<00:20:04.159> a<00:20:04.280> world<00:20:04.679> where<00:20:05.440> cryptography 00:20:06.230 --> 00:20:06.240 align:start position:0% excited about a world where cryptography 00:20:06.240 --> 00:20:09.110 align:start position:0% excited about a world where cryptography actually<00:20:06.760> can<00:20:07.440> get<00:20:07.559> to<00:20:07.760> the<00:20:07.960> point<00:20:08.360> of<00:20:08.760> in<00:20:08.880> a 00:20:09.110 --> 00:20:09.120 align:start position:0% actually can get to the point of in a 00:20:09.120 --> 00:20:11.590 align:start position:0% actually can get to the point of in a general<00:20:09.600> purpose<00:20:10.120> way<00:20:10.760> actually<00:20:11.120> being<00:20:11.360> able 00:20:11.590 --> 00:20:11.600 align:start position:0% general purpose way actually being able 00:20:11.600 --> 00:20:14.190 align:start position:0% general purpose way actually being able to<00:20:11.919> replicate<00:20:12.919> the<00:20:13.320> or<00:20:13.600> replace<00:20:14.039> the 00:20:14.190 --> 00:20:14.200 align:start position:0% to replicate the or replace the 00:20:14.200 --> 00:20:16.789 align:start position:0% to replicate the or replace the functionality<00:20:14.880> of<00:20:15.000> any<00:20:15.200> trusted<00:20:15.679> third<00:20:15.960> party 00:20:16.789 --> 00:20:16.799 align:start position:0% functionality of any trusted third party 00:20:16.799 --> 00:20:18.470 align:start position:0% functionality of any trusted third party and<00:20:17.200> uh<00:20:17.480> I<00:20:17.559> think<00:20:17.760> that<00:20:17.919> future<00:20:18.159> will<00:20:18.320> be 00:20:18.470 --> 00:20:18.480 align:start position:0% and uh I think that future will be 00:20:18.480 --> 00:20:25.270 align:start position:0% and uh I think that future will be amazing<00:20:19.080> thank 00:20:25.270 --> 00:20:25.280 align:start position:0% 00:20:25.280 --> 00:20:28.270 align:start position:0% you<00:20:26.280> thank<00:20:26.400> you<00:20:26.559> vitalic<00:20:27.520> um<00:20:27.720> so<00:20:27.880> we<00:20:28.000> will<00:20:28.120> do 00:20:28.270 --> 00:20:28.280 align:start position:0% you thank you vitalic um so we will do 00:20:28.280 --> 00:20:31.149 align:start position:0% you thank you vitalic um so we will do three<00:20:28.880> of<00:20:29.000> Q&A<00:20:29.799> uh<00:20:29.919> we<00:20:30.080> have<00:20:30.360> the<00:20:30.559> QR<00:20:30.840> code<00:20:31.039> here 00:20:31.149 --> 00:20:31.159 align:start position:0% three of Q&A uh we have the QR code here 00:20:31.159 --> 00:20:33.590 align:start position:0% three of Q&A uh we have the QR code here you<00:20:31.280> can<00:20:31.480> scan<00:20:32.039> to<00:20:32.559> both<00:20:32.880> add<00:20:33.159> questions<00:20:33.440> and 00:20:33.590 --> 00:20:33.600 align:start position:0% you can scan to both add questions and 00:20:33.600 --> 00:20:36.110 align:start position:0% you can scan to both add questions and up<00:20:33.799> vote<00:20:34.159> questions<00:20:35.159> um<00:20:35.600> there<00:20:35.679> are<00:20:35.799> only<00:20:35.960> two 00:20:36.110 --> 00:20:36.120 align:start position:0% up vote questions um there are only two 00:20:36.120 --> 00:20:37.789 align:start position:0% up vote questions um there are only two questions<00:20:36.400> so<00:20:36.640> far<00:20:36.799> and<00:20:36.960> one<00:20:37.240> with<00:20:37.559> I<00:20:37.679> I'll 00:20:37.789 --> 00:20:37.799 align:start position:0% questions so far and one with I I'll 00:20:37.799 --> 00:20:39.310 align:start position:0% questions so far and one with I I'll start<00:20:38.039> with<00:20:38.159> the<00:20:38.240> fun<00:20:38.440> one<00:20:38.679> which<00:20:38.760> is<00:20:38.919> vitalic 00:20:39.310 --> 00:20:39.320 align:start position:0% start with the fun one which is vitalic 00:20:39.320 --> 00:20:40.830 align:start position:0% start with the fun one which is vitalic if<00:20:39.400> you<00:20:39.520> played<00:20:39.720> the<00:20:39.840> frog<00:20:40.159> game<00:20:40.360> and<00:20:40.480> if<00:20:40.640> yes 00:20:40.830 --> 00:20:40.840 align:start position:0% if you played the frog game and if yes 00:20:40.840 --> 00:20:42.149 align:start position:0% if you played the frog game and if yes how<00:20:40.960> many<00:20:41.080> frogs<00:20:41.400> have<00:20:41.520> you<00:20:41.640> collected 00:20:42.149 --> 00:20:42.159 align:start position:0% how many frogs have you collected 00:20:42.159 --> 00:20:43.950 align:start position:0% how many frogs have you collected unfortunately<00:20:42.799> not<00:20:43.080> this<00:20:43.280> time<00:20:43.559> I've<00:20:43.720> had 00:20:43.950 --> 00:20:43.960 align:start position:0% unfortunately not this time I've had 00:20:43.960 --> 00:20:46.070 align:start position:0% unfortunately not this time I've had like<00:20:44.320> zero<00:20:44.840> time<00:20:45.039> to<00:20:45.200> do<00:20:45.400> anything<00:20:45.760> other<00:20:45.919> than 00:20:46.070 --> 00:20:46.080 align:start position:0% like zero time to do anything other than 00:20:46.080 --> 00:20:48.310 align:start position:0% like zero time to do anything other than jumping<00:20:46.400> around<00:20:46.640> Devon<00:20:47.200> stuff<00:20:47.720> but<00:20:47.919> but<00:20:48.120> but 00:20:48.310 --> 00:20:48.320 align:start position:0% jumping around Devon stuff but but but 00:20:48.320 --> 00:20:50.630 align:start position:0% jumping around Devon stuff but but but here<00:20:48.480> it's<00:20:48.640> been<00:20:49.039> fun<00:20:50.039> um<00:20:50.320> okay<00:20:50.480> what 00:20:50.630 --> 00:20:50.640 align:start position:0% here it's been fun um okay what 00:20:50.640 --> 00:20:53.110 align:start position:0% here it's been fun um okay what advantages<00:20:51.159> will<00:20:51.360> the<00:20:51.520> snark<00:20:51.880> ification<00:20:52.720> of 00:20:53.110 --> 00:20:53.120 align:start position:0% advantages will the snark ification of 00:20:53.120 --> 00:20:57.630 align:start position:0% advantages will the snark ification of uh<00:20:53.880> the<00:20:54.000> beacon<00:20:54.360> chain<00:20:55.120> um<00:20:55.440> have<00:20:56.080> I<00:20:56.520> mean<00:20:57.520> I 00:20:57.630 --> 00:20:57.640 align:start position:0% uh the beacon chain um have I mean I 00:20:57.640 --> 00:20:59.630 align:start position:0% uh the beacon chain um have I mean I think<00:20:58.039> uh<00:20:58.200> the<00:20:58.360> big<00:20:58.760> the<00:20:58.880> big<00:20:59.080> one<00:20:59.400> is 00:20:59.630 --> 00:20:59.640 align:start position:0% think uh the big the big one is 00:20:59.640 --> 00:21:01.470 align:start position:0% think uh the big the big one is basically<00:21:00.120> that<00:21:00.280> you<00:21:00.360> will<00:21:00.679> have<00:21:01.120> light 00:21:01.470 --> 00:21:01.480 align:start position:0% basically that you will have light 00:21:01.480 --> 00:21:03.190 align:start position:0% basically that you will have light clients<00:21:01.919> that<00:21:02.039> will<00:21:02.200> be<00:21:02.320> able<00:21:02.520> to<00:21:02.799> fully 00:21:03.190 --> 00:21:03.200 align:start position:0% clients that will be able to fully 00:21:03.200 --> 00:21:05.590 align:start position:0% clients that will be able to fully verify<00:21:03.720> the<00:21:03.840> ethereum<00:21:04.360> protocol<00:21:05.200> right<00:21:05.360> so 00:21:05.590 --> 00:21:05.600 align:start position:0% verify the ethereum protocol right so 00:21:05.600 --> 00:21:07.350 align:start position:0% verify the ethereum protocol right so like<00:21:05.799> on<00:21:05.919> your<00:21:06.080> phone<00:21:06.440> on<00:21:06.640> your<00:21:06.919> watch 00:21:07.350 --> 00:21:07.360 align:start position:0% like on your phone on your watch 00:21:07.360 --> 00:21:09.230 align:start position:0% like on your phone on your watch anywhere<00:21:08.120> anywhere<00:21:08.480> that<00:21:08.600> you<00:21:08.720> wants<00:21:08.919> to<00:21:09.080> do 00:21:09.230 --> 00:21:09.240 align:start position:0% anywhere anywhere that you wants to do 00:21:09.240 --> 00:21:10.990 align:start position:0% anywhere anywhere that you wants to do things<00:21:09.440> with<00:21:09.600> ethereum<00:21:10.240> you'll<00:21:10.440> be<00:21:10.600> able<00:21:10.760> to 00:21:10.990 --> 00:21:11.000 align:start position:0% things with ethereum you'll be able to 00:21:11.000 --> 00:21:13.549 align:start position:0% things with ethereum you'll be able to like<00:21:11.240> actually<00:21:12.039> fully<00:21:12.440> verify<00:21:12.960> the<00:21:13.080> rules<00:21:13.400> of 00:21:13.549 --> 00:21:13.559 align:start position:0% like actually fully verify the rules of 00:21:13.559 --> 00:21:16.630 align:start position:0% like actually fully verify the rules of the<00:21:13.679> chain<00:21:14.440> and<00:21:15.200> uh<00:21:15.679> like<00:21:15.799> you'll<00:21:15.960> be<00:21:16.240> part<00:21:16.480> of 00:21:16.630 --> 00:21:16.640 align:start position:0% the chain and uh like you'll be part of 00:21:16.640 --> 00:21:19.230 align:start position:0% the chain and uh like you'll be part of the<00:21:16.799> mechanism<00:21:17.400> that<00:21:17.559> ensures<00:21:18.159> that<00:21:18.760> the<00:21:19.120> the 00:21:19.230 --> 00:21:19.240 align:start position:0% the mechanism that ensures that the the 00:21:19.240 --> 00:21:21.830 align:start position:0% the mechanism that ensures that the the chain<00:21:19.559> and<00:21:19.799> like<00:21:20.000> even<00:21:20.360> 51%<00:21:21.120> of<00:21:21.240> the<00:21:21.679> of<00:21:21.760> the 00:21:21.830 --> 00:21:21.840 align:start position:0% chain and like even 51% of the of the 00:21:21.840 --> 00:21:24.310 align:start position:0% chain and like even 51% of the of the sakers<00:21:22.240> are<00:21:22.400> not<00:21:22.679> changing<00:21:23.039> the<00:21:23.159> rules<00:21:23.480> on<00:21:23.679> you 00:21:24.310 --> 00:21:24.320 align:start position:0% sakers are not changing the rules on you 00:21:24.320 --> 00:21:28.350 align:start position:0% sakers are not changing the rules on you and<00:21:24.799> uh<00:21:25.640> that's<00:21:26.159> uh<00:21:26.840> so<00:21:27.840> and<00:21:28.000> this<00:21:28.120> will<00:21:28.240> all 00:21:28.350 --> 00:21:28.360 align:start position:0% and uh that's uh so and this will all 00:21:28.360 --> 00:21:30.070 align:start position:0% and uh that's uh so and this will all just<00:21:28.760> like<00:21:28.960> happen<00:21:29.320> passively<00:21:29.760> and 00:21:30.070 --> 00:21:30.080 align:start position:0% just like happen passively and 00:21:30.080 --> 00:21:32.350 align:start position:0% just like happen passively and automatically<00:21:31.080> um<00:21:31.440> to<00:21:31.679> invite<00:21:31.919> me<00:21:32.039> to<00:21:32.200> a 00:21:32.350 --> 00:21:32.360 align:start position:0% automatically um to invite me to a 00:21:32.360 --> 00:21:34.710 align:start position:0% automatically um to invite me to a conference<00:21:32.799> to<00:21:32.960> speak<00:21:33.240> out<00:21:33.440> how<00:21:33.600> does<00:21:33.880> one<00:21:34.520> go 00:21:34.710 --> 00:21:34.720 align:start position:0% conference to speak out how does one go 00:21:34.720 --> 00:21:37.310 align:start position:0% conference to speak out how does one go I'm<00:21:34.840> not<00:21:35.159> not<00:21:35.480> answering<00:21:36.480> um<00:21:36.840> One<00:21:37.120> Shot 00:21:37.310 --> 00:21:37.320 align:start position:0% I'm not not answering um One Shot 00:21:37.320 --> 00:21:38.750 align:start position:0% I'm not not answering um One Shot signature<00:21:37.720> on<00:21:37.799> the<00:21:37.919> book<00:21:38.200> possible<00:21:38.600> not 00:21:38.750 --> 00:21:38.760 align:start position:0% signature on the book possible not 00:21:38.760 --> 00:21:40.310 align:start position:0% signature on the book possible not answering<00:21:39.400> can<00:21:39.520> we<00:21:39.679> call<00:21:39.880> beam<00:21:40.080> chain 00:21:40.310 --> 00:21:40.320 align:start position:0% answering can we call beam chain 00:21:40.320 --> 00:21:43.190 align:start position:0% answering can we call beam chain ethereum<00:21:40.799> 3.0<00:21:41.520> I<00:21:41.640> think<00:21:41.960> no<00:21:42.720> and<00:21:42.840> I<00:21:42.960> think<00:21:43.120> this 00:21:43.190 --> 00:21:43.200 align:start position:0% ethereum 3.0 I think no and I think this 00:21:43.200 --> 00:21:44.950 align:start position:0% ethereum 3.0 I think no and I think this is<00:21:43.400> like<00:21:43.520> an<00:21:43.679> important<00:21:44.000> misconception<00:21:44.760> right 00:21:44.950 --> 00:21:44.960 align:start position:0% is like an important misconception right 00:21:44.960 --> 00:21:46.870 align:start position:0% is like an important misconception right because<00:21:45.200> I<00:21:45.320> think<00:21:45.600> like<00:21:46.080> a<00:21:46.200> lot<00:21:46.360> of<00:21:46.520> people 00:21:46.870 --> 00:21:46.880 align:start position:0% because I think like a lot of people 00:21:46.880 --> 00:21:48.630 align:start position:0% because I think like a lot of people like<00:21:47.039> got<00:21:47.240> this<00:21:47.440> weird<00:21:47.760> Twitter<00:21:48.159> impression 00:21:48.630 --> 00:21:48.640 align:start position:0% like got this weird Twitter impression 00:21:48.640 --> 00:21:51.430 align:start position:0% like got this weird Twitter impression that<00:21:48.880> like<00:21:49.120> oh<00:21:49.720> you<00:21:49.880> know<00:21:50.120> in<00:21:50.559> the<00:21:50.720> be<00:21:51.080> the<00:21:51.159> beam 00:21:51.430 --> 00:21:51.440 align:start position:0% that like oh you know in the be the beam 00:21:51.440 --> 00:21:54.750 align:start position:0% that like oh you know in the be the beam chain<00:21:51.840> it<00:21:51.960> will<00:21:52.120> only<00:21:52.440> happen<00:21:52.760> in<00:21:53.400> 2029<00:21:54.400> and<00:21:54.520> it 00:21:54.750 --> 00:21:54.760 align:start position:0% chain it will only happen in 2029 and it 00:21:54.760 --> 00:21:56.909 align:start position:0% chain it will only happen in 2029 and it only<00:21:55.159> happen<00:21:55.600> gives<00:21:55.799> you<00:21:56.000> these<00:21:56.240> nice<00:21:56.520> Ivory 00:21:56.909 --> 00:21:56.919 align:start position:0% only happen gives you these nice Ivory 00:21:56.919 --> 00:21:58.830 align:start position:0% only happen gives you these nice Ivory Tower<00:21:57.279> Properties<00:21:57.720> about<00:21:57.919> the<00:21:58.039> consent<00:21:58.640> layer 00:21:58.830 --> 00:21:58.840 align:start position:0% Tower Properties about the consent layer 00:21:58.840 --> 00:22:00.269 align:start position:0% Tower Properties about the consent layer and<00:21:58.960> so<00:21:59.080> it<00:21:59.200> doesn't<00:21:59.440> even<00:21:59.600> mean<00:21:59.799> anything<00:22:00.080> for 00:22:00.269 --> 00:22:00.279 align:start position:0% and so it doesn't even mean anything for 00:22:00.279 --> 00:22:02.310 align:start position:0% and so it doesn't even mean anything for users<00:22:00.679> and<00:22:00.880> like<00:22:01.039> this<00:22:01.159> is<00:22:01.320> ethereum<00:22:01.720> 3.0 00:22:02.310 --> 00:22:02.320 align:start position:0% users and like this is ethereum 3.0 00:22:02.320 --> 00:22:04.149 align:start position:0% users and like this is ethereum 3.0 right<00:22:02.880> and<00:22:03.000> the<00:22:03.159> reality<00:22:03.520> is<00:22:03.760> like<00:22:03.919> very 00:22:04.149 --> 00:22:04.159 align:start position:0% right and the reality is like very 00:22:04.159 --> 00:22:05.789 align:start position:0% right and the reality is like very different<00:22:04.440> from<00:22:04.640> that<00:22:04.840> right<00:22:04.960> the<00:22:05.080> beam<00:22:05.320> chain 00:22:05.789 --> 00:22:05.799 align:start position:0% different from that right the beam chain 00:22:05.799 --> 00:22:08.510 align:start position:0% different from that right the beam chain is<00:22:06.559> only<00:22:06.960> covering<00:22:07.400> the<00:22:07.559> ethereum<00:22:08.039> consensus 00:22:08.510 --> 00:22:08.520 align:start position:0% is only covering the ethereum consensus 00:22:08.520 --> 00:22:11.269 align:start position:0% is only covering the ethereum consensus layer<00:22:09.159> which<00:22:09.320> is<00:22:09.559> only<00:22:10.000> like<00:22:10.480> maybe<00:22:10.799> one<00:22:11.039> third 00:22:11.269 --> 00:22:11.279 align:start position:0% layer which is only like maybe one third 00:22:11.279 --> 00:22:13.070 align:start position:0% layer which is only like maybe one third or<00:22:11.400> one<00:22:11.600> quarter<00:22:11.919> of<00:22:12.039> the<00:22:12.159> ethereum<00:22:12.679> stack 00:22:13.070 --> 00:22:13.080 align:start position:0% or one quarter of the ethereum stack 00:22:13.080 --> 00:22:15.110 align:start position:0% or one quarter of the ethereum stack right<00:22:13.520> the<00:22:13.720> execution<00:22:14.240> layer<00:22:14.640> that<00:22:14.760> so<00:22:15.000> the 00:22:15.110 --> 00:22:15.120 align:start position:0% right the execution layer that so the 00:22:15.120 --> 00:22:17.789 align:start position:0% right the execution layer that so the evm<00:22:15.960> has<00:22:16.120> its<00:22:16.320> own<00:22:16.559> road<00:22:16.880> map<00:22:17.279> and<00:22:17.360> then<00:22:17.520> layer 00:22:17.789 --> 00:22:17.799 align:start position:0% evm has its own road map and then layer 00:22:17.799 --> 00:22:19.710 align:start position:0% evm has its own road map and then layer twos<00:22:18.159> and<00:22:18.320> Layer<00:22:18.520> Two<00:22:18.720> interoperability<00:22:19.559> has 00:22:19.710 --> 00:22:19.720 align:start position:0% twos and Layer Two interoperability has 00:22:19.720 --> 00:22:24.070 align:start position:0% twos and Layer Two interoperability has its<00:22:19.840> own<00:22:20.080> road<00:22:20.400> map<00:22:21.400> and<00:22:21.880> uh<00:22:22.559> even<00:22:23.039> on<00:22:23.520> the 00:22:24.070 --> 00:22:24.080 align:start position:0% its own road map and uh even on the 00:22:24.080 --> 00:22:26.230 align:start position:0% its own road map and uh even on the consensus<00:22:24.720> side<00:22:25.200> all<00:22:25.360> of<00:22:25.520> the<00:22:25.720> key<00:22:25.960> things 00:22:26.230 --> 00:22:26.240 align:start position:0% consensus side all of the key things 00:22:26.240 --> 00:22:27.990 align:start position:0% consensus side all of the key things that<00:22:26.360> are<00:22:26.559> actually<00:22:26.880> meaningful<00:22:27.360> for<00:22:27.559> users 00:22:27.990 --> 00:22:28.000 align:start position:0% that are actually meaningful for users 00:22:28.000 --> 00:22:29.990 align:start position:0% that are actually meaningful for users so<00:22:28.200> ESP<00:22:28.520> especially<00:22:28.840> getting<00:22:29.080> dank<00:22:29.320> charting 00:22:29.990 --> 00:22:30.000 align:start position:0% so ESP especially getting dank charting 00:22:30.000 --> 00:22:33.350 align:start position:0% so ESP especially getting dank charting um<00:22:30.240> up<00:22:31.080> I<00:22:31.200> think<00:22:31.400> can<00:22:31.720> happen<00:22:32.400> a<00:22:32.600> lot<00:22:32.840> sooner 00:22:33.350 --> 00:22:33.360 align:start position:0% um up I think can happen a lot sooner 00:22:33.360 --> 00:22:35.230 align:start position:0% um up I think can happen a lot sooner than<00:22:33.799> uh 00:22:35.230 --> 00:22:35.240 align:start position:0% than uh 00:22:35.240 --> 00:22:39.310 align:start position:0% than uh 2029<00:22:36.240> thank<00:22:36.679> you<00:22:37.679> um<00:22:37.919> okay<00:22:38.080> more<00:22:38.360> questions 00:22:39.310 --> 00:22:39.320 align:start position:0% 2029 thank you um okay more questions 00:22:39.320 --> 00:22:41.149 align:start position:0% 2029 thank you um okay more questions what<00:22:39.440> do<00:22:39.600> I<00:22:39.720> think<00:22:39.919> about<00:22:40.120> tees<00:22:40.799> I<00:22:40.840> mean<00:22:41.039> I 00:22:41.149 --> 00:22:41.159 align:start position:0% what do I think about tees I mean I 00:22:41.159 --> 00:22:44.230 align:start position:0% what do I think about tees I mean I think<00:22:41.360> they're<00:22:42.320> definitely<00:22:43.279> interesting<00:22:43.840> for 00:22:44.230 --> 00:22:44.240 align:start position:0% think they're definitely interesting for 00:22:44.240 --> 00:22:45.909 align:start position:0% think they're definitely interesting for some<00:22:44.600> uses<00:22:45.080> though<00:22:45.240> I<00:22:45.320> think<00:22:45.480> it's<00:22:45.679> always 00:22:45.909 --> 00:22:45.919 align:start position:0% some uses though I think it's always 00:22:45.919 --> 00:22:47.830 align:start position:0% some uses though I think it's always important<00:22:46.240> to<00:22:46.440> remember<00:22:46.880> that<00:22:47.080> like<00:22:47.640> they 00:22:47.830 --> 00:22:47.840 align:start position:0% important to remember that like they 00:22:47.840 --> 00:22:50.029 align:start position:0% important to remember that like they depend<00:22:48.360> on<00:22:48.640> a<00:22:48.760> lot<00:22:48.919> of<00:22:49.080> trust<00:22:49.440> in<00:22:49.640> specific 00:22:50.029 --> 00:22:50.039 align:start position:0% depend on a lot of trust in specific 00:22:50.039 --> 00:22:51.630 align:start position:0% depend on a lot of trust in specific manufacturers<00:22:50.760> and<00:22:50.919> they<00:22:51.039> get<00:22:51.200> frequently 00:22:51.630 --> 00:22:51.640 align:start position:0% manufacturers and they get frequently 00:22:51.640 --> 00:22:54.070 align:start position:0% manufacturers and they get frequently broken<00:22:52.120> right<00:22:52.240> and<00:22:52.400> so<00:22:53.039> you<00:22:53.200> want<00:22:53.480> to<00:22:53.679> use<00:22:53.919> them 00:22:54.070 --> 00:22:54.080 align:start position:0% broken right and so you want to use them 00:22:54.080 --> 00:22:55.470 align:start position:0% broken right and so you want to use them for<00:22:54.279> like<00:22:54.520> applications<00:22:55.120> where<00:22:55.279> they're 00:22:55.470 --> 00:22:55.480 align:start position:0% for like applications where they're 00:22:55.480 --> 00:22:56.990 align:start position:0% for like applications where they're either<00:22:55.760> just<00:22:56.000> additive<00:22:56.440> in<00:22:56.520> terms<00:22:56.760> of 00:22:56.990 --> 00:22:57.000 align:start position:0% either just additive in terms of 00:22:57.000 --> 00:22:59.390 align:start position:0% either just additive in terms of security<00:22:57.600> or<00:22:57.880> where<00:22:58.559> the<00:22:58.799> cost<00:22:59.039> of<00:22:59.200> them 00:22:59.390 --> 00:22:59.400 align:start position:0% security or where the cost of them 00:22:59.400 --> 00:23:01.190 align:start position:0% security or where the cost of them breaking<00:22:59.880> is<00:23:00.080> like<00:23:00.279> not<00:23:00.480> too<00:23:00.720> high<00:23:01.000> but<00:23:01.120> you 00:23:01.190 --> 00:23:01.200 align:start position:0% breaking is like not too high but you 00:23:01.200 --> 00:23:03.029 align:start position:0% breaking is like not too high but you don't<00:23:01.440> actually<00:23:01.640> want<00:23:01.760> to<00:23:01.919> use<00:23:02.159> them<00:23:02.279> to<00:23:02.559> like 00:23:03.029 --> 00:23:03.039 align:start position:0% don't actually want to use them to like 00:23:03.039 --> 00:23:05.190 align:start position:0% don't actually want to use them to like literally<00:23:03.480> replace<00:23:03.840> cryptography<00:23:04.799> so<00:23:05.080> you 00:23:05.190 --> 00:23:05.200 align:start position:0% literally replace cryptography so you 00:23:05.200 --> 00:23:08.549 align:start position:0% literally replace cryptography so you know<00:23:05.320> use<00:23:05.520> them<00:23:05.960> responsibly<00:23:07.080> um<00:23:08.080> what<00:23:08.200> can<00:23:08.360> on 00:23:08.549 --> 00:23:08.559 align:start position:0% know use them responsibly um what can on 00:23:08.559 --> 00:23:10.390 align:start position:0% know use them responsibly um what can on shot<00:23:08.720> signatures<00:23:09.279> plus<00:23:09.480> sisc<00:23:10.159> plus 00:23:10.390 --> 00:23:10.400 align:start position:0% shot signatures plus sisc plus 00:23:10.400 --> 00:23:13.710 align:start position:0% shot signatures plus sisc plus blockchain<00:23:11.400> not<00:23:11.720> do<00:23:12.720> it<00:23:12.919> cannot<00:23:13.360> give<00:23:13.480> you 00:23:13.710 --> 00:23:13.720 align:start position:0% blockchain not do it cannot give you 00:23:13.720 --> 00:23:16.029 align:start position:0% blockchain not do it cannot give you true<00:23:14.120> love<00:23:15.120> thank 00:23:16.029 --> 00:23:16.039 align:start position:0% true love thank 00:23:16.039 --> 00:23:22.350 align:start position:0% true love thank you<00:23:17.039> thank<00:23:17.159> you 00:23:22.350 --> 00:23:22.360 align:start position:0% 00:23:22.360 --> 00:23:26.070 align:start position:0% vtic<00:23:23.360> so<00:23:24.159> what<00:23:24.400> our<00:23:24.600> next<00:23:24.840> speaker<00:23:25.799> um<00:23:25.960> is 00:23:26.070 --> 00:23:26.080 align:start position:0% vtic so what our next speaker um is 00:23:26.080 --> 00:23:28.110 align:start position:0% vtic so what our next speaker um is going<00:23:26.279> to<00:23:26.960> prepare<00:23:27.520> the<00:23:27.679> connection<00:23:28.000> with 00:23:28.110 --> 00:23:28.120 align:start position:0% going to prepare the connection with 00:23:28.120 --> 00:23:31.070 align:start position:0% going to prepare the connection with their<00:23:28.640> top<00:23:29.480> um<00:23:29.840> I've<00:23:30.039> been<00:23:30.159> sent<00:23:30.440> to<00:23:30.600> entertain 00:23:31.070 --> 00:23:31.080 align:start position:0% their top um I've been sent to entertain 00:23:31.080 --> 00:23:33.029 align:start position:0% their top um I've been sent to entertain you<00:23:31.520> guys 00:23:33.029 --> 00:23:33.039 align:start position:0% you guys 00:23:33.039 --> 00:23:35.230 align:start position:0% you guys so<00:23:34.039> uh<00:23:34.120> one<00:23:34.279> thing<00:23:34.400> I<00:23:34.480> found<00:23:34.679> interesting<00:23:35.080> with 00:23:35.230 --> 00:23:35.240 align:start position:0% so uh one thing I found interesting with 00:23:35.240 --> 00:23:36.870 align:start position:0% so uh one thing I found interesting with vitalic<00:23:35.760> presentation<00:23:36.159> is<00:23:36.360> when<00:23:36.520> you<00:23:36.640> start 00:23:36.870 --> 00:23:36.880 align:start position:0% vitalic presentation is when you start 00:23:36.880 --> 00:23:38.990 align:start position:0% vitalic presentation is when you start listing<00:23:37.400> down<00:23:38.080> these<00:23:38.440> cryptographic 00:23:38.990 --> 00:23:39.000 align:start position:0% listing down these cryptographic 00:23:39.000 --> 00:23:41.310 align:start position:0% listing down these cryptographic protocols<00:23:39.400> one<00:23:39.600> by<00:23:39.799> one<00:23:40.559> um<00:23:40.880> you<00:23:40.960> don't<00:23:41.159> need 00:23:41.310 --> 00:23:41.320 align:start position:0% protocols one by one um you don't need 00:23:41.320 --> 00:23:43.549 align:start position:0% protocols one by one um you don't need to<00:23:41.440> like<00:23:41.600> scre<00:23:42.000> your<00:23:42.159> eyes<00:23:42.520> that<00:23:42.760> hard<00:23:43.039> to<00:23:43.440> kind 00:23:43.549 --> 00:23:43.559 align:start position:0% to like scre your eyes that hard to kind 00:23:43.559 --> 00:23:45.870 align:start position:0% to like scre your eyes that hard to kind of<00:23:43.720> like<00:23:43.880> see<00:23:44.679> some<00:23:44.840> form<00:23:45.039> of<00:23:45.279> mathematical 00:23:45.870 --> 00:23:45.880 align:start position:0% of like see some form of mathematical 00:23:45.880 --> 00:23:48.230 align:start position:0% of like see some form of mathematical computer<00:23:46.279> emerge<00:23:47.200> right<00:23:47.440> like<00:23:47.640> each<00:23:47.840> of<00:23:48.000> these 00:23:48.230 --> 00:23:48.240 align:start position:0% computer emerge right like each of these 00:23:48.240 --> 00:23:50.470 align:start position:0% computer emerge right like each of these Primitives<00:23:48.919> are<00:23:49.400> synergistic<00:23:50.200> with<00:23:50.320> each 00:23:50.470 --> 00:23:50.480 align:start position:0% Primitives are synergistic with each 00:23:50.480 --> 00:23:53.350 align:start position:0% Primitives are synergistic with each other<00:23:51.200> um<00:23:51.559> as<00:23:51.679> an<00:23:51.840> example<00:23:52.159> one<00:23:52.400> primitive<00:23:53.000> V 00:23:53.350 --> 00:23:53.360 align:start position:0% other um as an example one primitive V 00:23:53.360 --> 00:23:56.070 align:start position:0% other um as an example one primitive V did<00:23:53.480> not<00:23:53.640> talk<00:23:53.799> about<00:23:54.000> is<00:23:54.120> Oram<00:23:54.640> oblivious<00:23:55.080> RAM 00:23:56.070 --> 00:23:56.080 align:start position:0% did not talk about is Oram oblivious RAM 00:23:56.080 --> 00:23:57.230 align:start position:0% did not talk about is Oram oblivious RAM and<00:23:56.240> one<00:23:56.360> thing<00:23:56.480> that's<00:23:56.679> interesting<00:23:57.080> with 00:23:57.230 --> 00:23:57.240 align:start position:0% and one thing that's interesting with 00:23:57.240 --> 00:23:59.549 align:start position:0% and one thing that's interesting with that<00:23:57.400> is<00:23:57.840> the<00:23:57.960> same<00:23:58.200> way<00:23:58.720> in<00:23:59.039> traditional 00:23:59.549 --> 00:23:59.559 align:start position:0% that is the same way in traditional 00:23:59.559 --> 00:24:01.789 align:start position:0% that is the same way in traditional computers<00:24:00.240> we<00:24:00.440> could<00:24:00.760> put<00:24:01.000> all<00:24:01.159> of<00:24:01.279> our<00:24:01.440> state 00:24:01.789 --> 00:24:01.799 align:start position:0% computers we could put all of our state 00:24:01.799 --> 00:24:03.630 align:start position:0% computers we could put all of our state in<00:24:01.919> CPU<00:24:02.360> registers<00:24:02.840> but<00:24:03.000> we<00:24:03.120> don't<00:24:03.440> because 00:24:03.630 --> 00:24:03.640 align:start position:0% in CPU registers but we don't because 00:24:03.640 --> 00:24:05.710 align:start position:0% in CPU registers but we don't because they're<00:24:03.880> hella<00:24:04.279> expensive<00:24:05.000> and<00:24:05.120> we<00:24:05.240> have<00:24:05.440> like 00:24:05.710 --> 00:24:05.720 align:start position:0% they're hella expensive and we have like 00:24:05.720 --> 00:24:07.230 align:start position:0% they're hella expensive and we have like you<00:24:05.799> know<00:24:05.960> multiple<00:24:06.320> layers<00:24:06.600> of<00:24:06.720> storage<00:24:07.080> we 00:24:07.230 --> 00:24:07.240 align:start position:0% you know multiple layers of storage we 00:24:07.240 --> 00:24:10.350 align:start position:0% you know multiple layers of storage we have<00:24:07.559> CPU<00:24:08.000> registers<00:24:08.640> Ram<00:24:09.600> uh<00:24:09.720> blog<00:24:10.000> storage 00:24:10.350 --> 00:24:10.360 align:start position:0% have CPU registers Ram uh blog storage 00:24:10.360 --> 00:24:12.310 align:start position:0% have CPU registers Ram uh blog storage network<00:24:10.720> storage<00:24:11.080> Etc<00:24:11.720> it's<00:24:11.919> probably<00:24:12.159> going 00:24:12.310 --> 00:24:12.320 align:start position:0% network storage Etc it's probably going 00:24:12.320 --> 00:24:14.470 align:start position:0% network storage Etc it's probably going to<00:24:12.440> be<00:24:12.600> the<00:24:12.760> case<00:24:13.039> that<00:24:13.360> with<00:24:13.679> cryptography<00:24:14.400> we 00:24:14.470 --> 00:24:14.480 align:start position:0% to be the case that with cryptography we 00:24:14.480 --> 00:24:16.710 align:start position:0% to be the case that with cryptography we will<00:24:14.600> have<00:24:14.720> to<00:24:14.799> do<00:24:14.960> the<00:24:15.120> same<00:24:15.480> so<00:24:16.320> while<00:24:16.559> some 00:24:16.710 --> 00:24:16.720 align:start position:0% will have to do the same so while some 00:24:16.720 --> 00:24:18.390 align:start position:0% will have to do the same so while some of<00:24:16.880> these<00:24:17.039> protocols<00:24:17.559> can<00:24:17.720> technically<00:24:18.120> do 00:24:18.390 --> 00:24:18.400 align:start position:0% of these protocols can technically do 00:24:18.400 --> 00:24:19.870 align:start position:0% of these protocols can technically do everything<00:24:18.840> we'll<00:24:19.080> probably<00:24:19.360> compose<00:24:19.720> them 00:24:19.870 --> 00:24:19.880 align:start position:0% everything we'll probably compose them 00:24:19.880 --> 00:24:21.510 align:start position:0% everything we'll probably compose them with<00:24:20.039> each<00:24:20.159> other<00:24:20.440> in<00:24:20.559> order<00:24:20.760> to<00:24:20.960> like<00:24:21.200> reap 00:24:21.510 --> 00:24:21.520 align:start position:0% with each other in order to like reap 00:24:21.520 --> 00:24:23.710 align:start position:0% with each other in order to like reap the<00:24:21.640> best<00:24:21.799> performance<00:24:22.240> possible<00:24:23.039> and<00:24:23.159> so<00:24:23.559> who 00:24:23.710 --> 00:24:23.720 align:start position:0% the best performance possible and so who 00:24:23.720 --> 00:24:25.470 align:start position:0% the best performance possible and so who knows<00:24:23.960> maybe<00:24:24.159> in<00:24:24.200> a<00:24:24.360> decade<00:24:24.640> we<00:24:24.760> will<00:24:25.000> have 00:24:25.470 --> 00:24:25.480 align:start position:0% knows maybe in a decade we will have 00:24:25.480 --> 00:24:27.350 align:start position:0% knows maybe in a decade we will have cryptography<00:24:26.159> computer<00:24:26.520> Engineers<00:24:27.120> whose 00:24:27.350 --> 00:24:27.360 align:start position:0% cryptography computer Engineers whose 00:24:27.360 --> 00:24:29.029 align:start position:0% cryptography computer Engineers whose entire<00:24:27.760> job<00:24:27.960> is<00:24:28.039> to<00:24:28.159> build<00:24:28.399> computers<00:24:28.760> out<00:24:28.880> of 00:24:29.029 --> 00:24:29.039 align:start position:0% entire job is to build computers out of 00:24:29.039 --> 00:24:31.870 align:start position:0% entire job is to build computers out of polinomial<00:24:29.799> and<00:24:29.919> not<00:24:30.159> out<00:24:30.320> of<00:24:30.799> silicon<00:24:31.720> uh 00:24:31.870 --> 00:24:31.880 align:start position:0% polinomial and not out of silicon uh 00:24:31.880 --> 00:24:34.310 align:start position:0% polinomial and not out of silicon uh which<00:24:32.080> and<00:24:32.200> they<00:24:32.320> will<00:24:33.320> I<00:24:33.679> one<00:24:33.840> thing<00:24:34.000> I<00:24:34.080> was 00:24:34.310 --> 00:24:34.320 align:start position:0% which and they will I one thing I was 00:24:34.320 --> 00:24:35.389 align:start position:0% which and they will I one thing I was thinking<00:24:34.600> about<00:24:34.760> yesterday<00:24:35.080> night<00:24:35.240> when<00:24:35.320> I 00:24:35.389 --> 00:24:35.399 align:start position:0% thinking about yesterday night when I 00:24:35.399 --> 00:24:36.950 align:start position:0% thinking about yesterday night when I couldn't<00:24:35.600> sleep<00:24:35.880> is<00:24:36.200> who's<00:24:36.440> going<00:24:36.600> to<00:24:36.679> be<00:24:36.799> the 00:24:36.950 --> 00:24:36.960 align:start position:0% couldn't sleep is who's going to be the 00:24:36.960 --> 00:24:40.230 align:start position:0% couldn't sleep is who's going to be the tsmc<00:24:37.640> of<00:24:37.799> cryptography<00:24:38.679> you<00:24:38.880> know<00:24:39.880> kind<00:24:40.039> of 00:24:40.230 --> 00:24:40.240 align:start position:0% tsmc of cryptography you know kind of 00:24:40.240 --> 00:24:43.269 align:start position:0% tsmc of cryptography you know kind of like<00:24:40.720> a<00:24:41.159> polinomial<00:24:41.840> Constructor<00:24:42.320> For<00:24:42.600> Hire 00:24:43.269 --> 00:24:43.279 align:start position:0% like a polinomial Constructor For Hire 00:24:43.279 --> 00:24:44.630 align:start position:0% like a polinomial Constructor For Hire that<00:24:43.480> put<00:24:43.799> together<00:24:44.080> the<00:24:44.360> biggest 00:24:44.630 --> 00:24:44.640 align:start position:0% that put together the biggest 00:24:44.640 --> 00:24:47.710 align:start position:0% that put together the biggest cryptography<00:24:45.399> computers<00:24:46.399> um<00:24:47.200> I<00:24:47.279> will<00:24:47.440> also 00:24:47.710 --> 00:24:47.720 align:start position:0% cryptography computers um I will also 00:24:47.720 --> 00:24:51.110 align:start position:0% cryptography computers um I will also check<00:24:48.039> with<00:24:48.960> a<00:24:49.320> if<00:24:49.399> we're<00:24:49.600> ready<00:24:50.360> we're<00:24:50.600> ready 00:24:51.110 --> 00:24:51.120 align:start position:0% check with a if we're ready we're ready 00:24:51.120 --> 00:24:52.630 align:start position:0% check with a if we're ready we're ready okay<00:24:51.279> cool<00:24:51.559> so<00:24:51.720> I<00:24:51.799> will<00:24:51.919> introduce<00:24:52.360> our<00:24:52.480> next 00:24:52.630 --> 00:24:52.640 align:start position:0% okay cool so I will introduce our next 00:24:52.640 --> 00:24:56.310 align:start position:0% okay cool so I will introduce our next speaker<00:24:52.880> to<00:24:53.000> the<00:24:53.240> stage<00:24:54.240> um<00:24:55.240> so<00:24:55.440> Albert<00:24:55.799> KN<00:24:56.200> has 00:24:56.310 --> 00:24:56.320 align:start position:0% speaker to the stage um so Albert KN has 00:24:56.320 --> 00:24:58.430 align:start position:0% speaker to the stage um so Albert KN has been<00:24:56.559> many<00:24:56.760> things<00:24:57.000> to<00:24:57.159> many<00:24:57.360> people<00:24:57.799> at<00:24:57.960> both 00:24:58.430 --> 00:24:58.440 align:start position:0% been many things to many people at both 00:24:58.440 --> 00:25:00.549 align:start position:0% been many things to many people at both eorum<00:24:58.799> foundation<00:24:59.080> in<00:24:59.240> zerx<00:24:59.640> park<00:25:00.159> but<00:25:00.320> above 00:25:00.549 --> 00:25:00.559 align:start position:0% eorum foundation in zerx park but above 00:25:00.559 --> 00:25:02.549 align:start position:0% eorum foundation in zerx park but above all<00:25:00.720> he's<00:25:00.880> someone<00:25:01.159> who<00:25:01.320> pushes<00:25:02.000> us<00:25:02.200> all<00:25:02.399> to 00:25:02.549 --> 00:25:02.559 align:start position:0% all he's someone who pushes us all to 00:25:02.559 --> 00:25:04.389 align:start position:0% all he's someone who pushes us all to think<00:25:02.720> in<00:25:02.880> more<00:25:03.200> Direction<00:25:03.880> and<00:25:04.000> I<00:25:04.080> think<00:25:04.240> he's 00:25:04.389 --> 00:25:04.399 align:start position:0% think in more Direction and I think he's 00:25:04.399 --> 00:25:06.190 align:start position:0% think in more Direction and I think he's going<00:25:04.559> to<00:25:04.679> do<00:25:04.880> that<00:25:05.240> yet<00:25:05.480> once<00:25:05.760> again<00:25:06.000> with 00:25:06.190 --> 00:25:06.200 align:start position:0% going to do that yet once again with 00:25:06.200 --> 00:25:07.830 align:start position:0% going to do that yet once again with this<00:25:06.399> talk<00:25:06.960> titled<00:25:07.360> the<00:25:07.440> future<00:25:07.679> of 00:25:07.830 --> 00:25:07.840 align:start position:0% this talk titled the future of 00:25:07.840 --> 00:25:11.070 align:start position:0% this talk titled the future of cryptography<00:25:08.679> the<00:25:08.840> real<00:25:09.679> surreal<00:25:10.559> and<00:25:10.720> super 00:25:11.070 --> 00:25:11.080 align:start position:0% cryptography the real surreal and super 00:25:11.080 --> 00:25:14.340 align:start position:0% cryptography the real surreal and super real<00:25:11.640> thank<00:25:11.799> you 00:25:14.340 --> 00:25:14.350 align:start position:0% 00:25:14.350 --> 00:25:23.870 align:start position:0% [Music] 00:25:23.870 --> 00:25:23.880 align:start position:0% 00:25:23.880 --> 00:25:28.909 align:start position:0% Albert<00:25:24.880> like<00:25:25.120> I<00:25:25.440> said<00:25:25.880> we<00:25:26.000> have<00:25:26.120> to<00:25:26.279> do<00:25:26.600> this 00:25:28.909 --> 00:25:28.919 align:start position:0% Albert like I said we have to do this 00:25:28.919 --> 00:25:33.029 align:start position:0% Albert like I said we have to do this there<00:25:29.039> we 00:25:33.029 --> 00:25:33.039 align:start position:0% 00:25:33.039 --> 00:25:36.630 align:start position:0% go<00:25:34.039> all<00:25:34.360> right<00:25:35.360> hi<00:25:35.559> everyone<00:25:36.360> thank<00:25:36.480> you 00:25:36.630 --> 00:25:36.640 align:start position:0% go all right hi everyone thank you 00:25:36.640 --> 00:25:39.830 align:start position:0% go all right hi everyone thank you Justin<00:25:37.200> for<00:25:37.520> a<00:25:37.919> very<00:25:38.120> fitting<00:25:38.480> intro<00:25:39.320> today 00:25:39.830 --> 00:25:39.840 align:start position:0% Justin for a very fitting intro today 00:25:39.840 --> 00:25:41.510 align:start position:0% Justin for a very fitting intro today above<00:25:40.120> all<00:25:40.399> I<00:25:40.520> want<00:25:40.679> to<00:25:40.840> share<00:25:41.240> some 00:25:41.510 --> 00:25:41.520 align:start position:0% above all I want to share some 00:25:41.520 --> 00:25:43.269 align:start position:0% above all I want to share some interesting<00:25:42.080> ways<00:25:42.480> I<00:25:42.640> think<00:25:43.000> about<00:25:43.200> the 00:25:43.269 --> 00:25:43.279 align:start position:0% interesting ways I think about the 00:25:43.279 --> 00:25:44.389 align:start position:0% interesting ways I think about the future<00:25:43.559> of 00:25:44.389 --> 00:25:44.399 align:start position:0% future of 00:25:44.399 --> 00:25:47.750 align:start position:0% future of cryptography<00:25:45.480> some<00:25:46.480> many<00:25:46.919> perhaps<00:25:47.279> are<00:25:47.480> ways 00:25:47.750 --> 00:25:47.760 align:start position:0% cryptography some many perhaps are ways 00:25:47.760 --> 00:25:50.070 align:start position:0% cryptography some many perhaps are ways people<00:25:48.000> have<00:25:48.200> not<00:25:48.720> considered<00:25:49.720> um<00:25:49.840> this<00:25:49.960> is 00:25:50.070 --> 00:25:50.080 align:start position:0% people have not considered um this is 00:25:50.080 --> 00:25:51.669 align:start position:0% people have not considered um this is going<00:25:50.240> to<00:25:50.399> go<00:25:50.600> to<00:25:50.799> some<00:25:50.960> interesting<00:25:51.399> places 00:25:51.669 --> 00:25:51.679 align:start position:0% going to go to some interesting places 00:25:51.679 --> 00:25:54.510 align:start position:0% going to go to some interesting places as<00:25:51.840> the<00:25:52.000> title<00:25:52.440> hints<00:25:52.960> at<00:25:53.679> but<00:25:53.880> before<00:25:54.080> I<00:25:54.279> dive 00:25:54.510 --> 00:25:54.520 align:start position:0% as the title hints at but before I dive 00:25:54.520 --> 00:25:56.590 align:start position:0% as the title hints at but before I dive in<00:25:54.760> I<00:25:54.840> want<00:25:54.919> to<00:25:55.159> emphasize<00:25:55.799> that<00:25:56.000> while<00:25:56.200> I<00:25:56.320> want 00:25:56.590 --> 00:25:56.600 align:start position:0% in I want to emphasize that while I want 00:25:56.600 --> 00:25:58.430 align:start position:0% in I want to emphasize that while I want folks<00:25:56.919> to<00:25:57.159> consider<00:25:57.559> more<00:25:57.799> directions<00:25:58.360> the 00:25:58.430 --> 00:25:58.440 align:start position:0% folks to consider more directions the 00:25:58.440 --> 00:26:00.269 align:start position:0% folks to consider more directions the point<00:25:58.640> is<00:25:58.880> not<00:25:59.080> to<00:25:59.440> replace<00:26:00.000> how<00:26:00.120> you 00:26:00.269 --> 00:26:00.279 align:start position:0% point is not to replace how you 00:26:00.279 --> 00:26:02.070 align:start position:0% point is not to replace how you currently<00:26:00.640> think<00:26:00.840> about<00:26:01.120> things<00:26:01.679> this<00:26:01.799> is<00:26:01.919> not 00:26:02.070 --> 00:26:02.080 align:start position:0% currently think about things this is not 00:26:02.080 --> 00:26:04.230 align:start position:0% currently think about things this is not new<00:26:02.320> thinking<00:26:02.559> in<00:26:02.640> a<00:26:02.799> totalizing<00:26:03.440> sense<00:26:04.080> it's 00:26:04.230 --> 00:26:04.240 align:start position:0% new thinking in a totalizing sense it's 00:26:04.240 --> 00:26:06.470 align:start position:0% new thinking in a totalizing sense it's not<00:26:04.440> declaring<00:26:05.039> it's<00:26:05.159> not<00:26:05.320> even<00:26:05.760> predicting 00:26:06.470 --> 00:26:06.480 align:start position:0% not declaring it's not even predicting 00:26:06.480 --> 00:26:08.350 align:start position:0% not declaring it's not even predicting at<00:26:06.600> least<00:26:06.760> not<00:26:06.919> in<00:26:07.039> the<00:26:07.200> sense<00:26:07.480> that<00:26:08.000> people 00:26:08.350 --> 00:26:08.360 align:start position:0% at least not in the sense that people 00:26:08.360 --> 00:26:10.310 align:start position:0% at least not in the sense that people usually<00:26:08.760> interpret<00:26:09.240> the<00:26:09.440> concept<00:26:09.840> of<00:26:10.000> talking 00:26:10.310 --> 00:26:10.320 align:start position:0% usually interpret the concept of talking 00:26:10.320 --> 00:26:13.070 align:start position:0% usually interpret the concept of talking about<00:26:10.600> the<00:26:10.760> future<00:26:11.600> this<00:26:11.720> is<00:26:11.880> just<00:26:12.080> thinking 00:26:13.070 --> 00:26:13.080 align:start position:0% about the future this is just thinking 00:26:13.080 --> 00:26:14.510 align:start position:0% about the future this is just thinking creating<00:26:13.440> awareness<00:26:13.799> for<00:26:13.960> what<00:26:14.120> may<00:26:14.320> be 00:26:14.510 --> 00:26:14.520 align:start position:0% creating awareness for what may be 00:26:14.520 --> 00:26:16.389 align:start position:0% creating awareness for what may be possible<00:26:14.840> and<00:26:14.960> may<00:26:15.120> be<00:26:15.320> true<00:26:16.000> because 00:26:16.389 --> 00:26:16.399 align:start position:0% possible and may be true because 00:26:16.399 --> 00:26:17.750 align:start position:0% possible and may be true because sometimes<00:26:16.640> that<00:26:16.760> awareness<00:26:17.159> is<00:26:17.320> what<00:26:17.480> makes 00:26:17.750 --> 00:26:17.760 align:start position:0% sometimes that awareness is what makes 00:26:17.760 --> 00:26:21.070 align:start position:0% sometimes that awareness is what makes something<00:26:18.600> unexpectedly<00:26:19.799> possible<00:26:20.799> we<00:26:20.919> don't 00:26:21.070 --> 00:26:21.080 align:start position:0% something unexpectedly possible we don't 00:26:21.080 --> 00:26:22.389 align:start position:0% something unexpectedly possible we don't have<00:26:21.240> much<00:26:21.440> time<00:26:21.720> so<00:26:21.840> I'm<00:26:21.919> going<00:26:22.000> to<00:26:22.080> talk<00:26:22.240> as 00:26:22.389 --> 00:26:22.399 align:start position:0% have much time so I'm going to talk as 00:26:22.399 --> 00:26:25.110 align:start position:0% have much time so I'm going to talk as fast<00:26:22.559> as<00:26:22.720> possible<00:26:23.440> uh<00:26:23.600> just<00:26:23.799> kidding<00:26:24.600> but 00:26:25.110 --> 00:26:25.120 align:start position:0% fast as possible uh just kidding but 00:26:25.120 --> 00:26:28.549 align:start position:0% fast as possible uh just kidding but seriously<00:26:25.520> buckle<00:26:25.880> up 00:26:28.549 --> 00:26:28.559 align:start position:0% seriously buckle up 00:26:28.559 --> 00:26:30.389 align:start position:0% seriously buckle up so<00:26:28.760> part<00:26:29.000> one<00:26:29.520> the 00:26:30.389 --> 00:26:30.399 align:start position:0% so part one the 00:26:30.399 --> 00:26:33.110 align:start position:0% so part one the real<00:26:31.399> let's<00:26:31.559> start<00:26:31.760> with<00:26:31.880> some<00:26:32.080> easy<00:26:32.600> stuff 00:26:33.110 --> 00:26:33.120 align:start position:0% real let's start with some easy stuff 00:26:33.120 --> 00:26:34.950 align:start position:0% real let's start with some easy stuff things<00:26:33.480> many<00:26:33.720> of<00:26:33.880> you<00:26:34.240> know<00:26:34.520> if<00:26:34.640> you've<00:26:34.799> been 00:26:34.950 --> 00:26:34.960 align:start position:0% things many of you know if you've been 00:26:34.960 --> 00:26:37.029 align:start position:0% things many of you know if you've been exploring<00:26:35.360> modern<00:26:35.720> cryptography<00:26:36.720> here<00:26:36.840> are 00:26:37.029 --> 00:26:37.039 align:start position:0% exploring modern cryptography here are 00:26:37.039 --> 00:26:39.710 align:start position:0% exploring modern cryptography here are some<00:26:37.399> uh<00:26:37.720> slogans<00:26:38.520> if<00:26:38.640> you<00:26:38.799> will<00:26:39.200> come<00:26:39.399> for<00:26:39.600> the 00:26:39.710 --> 00:26:39.720 align:start position:0% some uh slogans if you will come for the 00:26:39.720 --> 00:26:42.630 align:start position:0% some uh slogans if you will come for the encryption<00:26:40.399> stay<00:26:40.640> for<00:26:40.799> the<00:26:41.200> signatures<00:26:42.200> or 00:26:42.630 --> 00:26:42.640 align:start position:0% encryption stay for the signatures or 00:26:42.640 --> 00:26:44.830 align:start position:0% encryption stay for the signatures or come<00:26:42.799> for<00:26:43.000> the<00:26:43.279> security<00:26:44.279> stay<00:26:44.440> for<00:26:44.600> the 00:26:44.830 --> 00:26:44.840 align:start position:0% come for the security stay for the 00:26:44.840 --> 00:26:47.549 align:start position:0% come for the security stay for the interoperability<00:26:45.840> like<00:26:46.000> today<00:26:46.480> https<00:26:47.320> is<00:26:47.440> a 00:26:47.549 --> 00:26:47.559 align:start position:0% interoperability like today https is a 00:26:47.559 --> 00:26:51.269 align:start position:0% interoperability like today https is a statement<00:26:47.919> of<00:26:48.120> security<00:26:48.880> but<00:26:49.039> maybe<00:26:49.559> zps<00:26:50.559> or 00:26:51.269 --> 00:26:51.279 align:start position:0% statement of security but maybe zps or 00:26:51.279 --> 00:26:53.669 align:start position:0% statement of security but maybe zps or pctp<00:26:52.039> programmable<00:26:52.679> cryptography<00:26:53.240> transfer 00:26:53.669 --> 00:26:53.679 align:start position:0% pctp programmable cryptography transfer 00:26:53.679 --> 00:26:57.230 align:start position:0% pctp programmable cryptography transfer protocol<00:26:54.399> will<00:26:54.559> be<00:26:54.720> a<00:26:54.919> statement<00:26:55.480> of 00:26:57.230 --> 00:26:57.240 align:start position:0% protocol will be a statement of 00:26:57.240 --> 00:26:59.669 align:start position:0% protocol will be a statement of possibility<00:26:58.240> how<00:26:58.360> about<00:26:58.559> this<00:26:59.200> come<00:26:59.399> for<00:26:59.559> the 00:26:59.669 --> 00:26:59.679 align:start position:0% possibility how about this come for the 00:26:59.679 --> 00:27:01.710 align:start position:0% possibility how about this come for the nuk<00:27:00.080> proof<00:27:00.399> paint<00:27:00.880> stay<00:27:01.159> for<00:27:01.320> the 00:27:01.710 --> 00:27:01.720 align:start position:0% nuk proof paint stay for the 00:27:01.720 --> 00:27:03.630 align:start position:0% nuk proof paint stay for the superconductor<00:27:02.720> we've<00:27:02.919> known<00:27:03.080> for<00:27:03.240> a<00:27:03.399> long 00:27:03.630 --> 00:27:03.640 align:start position:0% superconductor we've known for a long 00:27:03.640 --> 00:27:05.909 align:start position:0% superconductor we've known for a long time<00:27:03.880> that<00:27:04.039> cryptography<00:27:04.840> is<00:27:05.159> digital<00:27:05.520> nuke 00:27:05.909 --> 00:27:05.919 align:start position:0% time that cryptography is digital nuke 00:27:05.919 --> 00:27:08.789 align:start position:0% time that cryptography is digital nuke proof<00:27:06.279> paint<00:27:07.200> but<00:27:07.440> it's<00:27:07.679> the<00:27:07.880> superconductor 00:27:08.789 --> 00:27:08.799 align:start position:0% proof paint but it's the superconductor 00:27:08.799 --> 00:27:10.830 align:start position:0% proof paint but it's the superconductor aspect<00:27:09.440> that<00:27:09.600> we<00:27:09.720> are<00:27:09.919> only<00:27:10.200> beginning<00:27:10.640> to 00:27:10.830 --> 00:27:10.840 align:start position:0% aspect that we are only beginning to 00:27:10.840 --> 00:27:13.269 align:start position:0% aspect that we are only beginning to realize<00:27:11.440> and 00:27:13.269 --> 00:27:13.279 align:start position:0% realize and 00:27:13.279 --> 00:27:14.950 align:start position:0% realize and understand<00:27:14.279> now<00:27:14.360> I<00:27:14.399> want<00:27:14.520> to<00:27:14.559> go<00:27:14.640> in<00:27:14.720> a<00:27:14.799> bit<00:27:14.919> of 00:27:14.950 --> 00:27:14.960 align:start position:0% understand now I want to go in a bit of 00:27:14.960 --> 00:27:16.389 align:start position:0% understand now I want to go in a bit of a<00:27:15.080> different<00:27:15.279> direction<00:27:15.760> here's<00:27:15.919> a<00:27:16.080> quote 00:27:16.389 --> 00:27:16.399 align:start position:0% a different direction here's a quote 00:27:16.399 --> 00:27:18.269 align:start position:0% a different direction here's a quote from<00:27:16.559> Steve<00:27:16.919> Jobs<00:27:17.480> recorded<00:27:17.840> in<00:27:17.960> the<00:27:18.080> book 00:27:18.269 --> 00:27:18.279 align:start position:0% from Steve Jobs recorded in the book 00:27:18.279 --> 00:27:20.190 align:start position:0% from Steve Jobs recorded in the book Valley<00:27:18.600> of<00:27:18.720> Genius<00:27:19.320> an<00:27:19.480> oral<00:27:19.799> history<00:27:20.080> of 00:27:20.190 --> 00:27:20.200 align:start position:0% Valley of Genius an oral history of 00:27:20.200 --> 00:27:22.669 align:start position:0% Valley of Genius an oral history of Silicon<00:27:20.520> Valley<00:27:20.799> that<00:27:20.880> I'd<00:27:21.080> highly 00:27:22.669 --> 00:27:22.679 align:start position:0% Silicon Valley that I'd highly 00:27:22.679 --> 00:27:26.070 align:start position:0% Silicon Valley that I'd highly recommend<00:27:23.679> one<00:27:23.799> of<00:27:24.039> many<00:27:24.399> things<00:27:25.279> that<00:27:25.600> stands 00:27:26.070 --> 00:27:26.080 align:start position:0% recommend one of many things that stands 00:27:26.080 --> 00:27:28.669 align:start position:0% recommend one of many things that stands out<00:27:26.440> from<00:27:26.679> this<00:27:26.840> quote<00:27:27.279> is<00:27:27.520> this<00:27:27.760> phrase 00:27:28.669 --> 00:27:28.679 align:start position:0% out from this quote is this phrase 00:27:28.679 --> 00:27:31.510 align:start position:0% out from this quote is this phrase medium<00:27:29.440> of 00:27:31.510 --> 00:27:31.520 align:start position:0% medium of 00:27:31.520 --> 00:27:35.710 align:start position:0% medium of expression<00:27:32.679> today<00:27:33.679> what<00:27:33.880> is<00:27:34.159> the<00:27:34.440> thing<00:27:34.840> that 00:27:35.710 --> 00:27:35.720 align:start position:0% expression today what is the thing that 00:27:35.720 --> 00:27:37.710 align:start position:0% expression today what is the thing that this<00:27:35.960> thing<00:27:36.200> we<00:27:36.360> call<00:27:36.640> computer<00:27:37.039> technology 00:27:37.710 --> 00:27:37.720 align:start position:0% this thing we call computer technology 00:27:37.720 --> 00:27:40.350 align:start position:0% this thing we call computer technology what<00:27:37.840> is<00:27:37.960> it<00:27:38.080> a<00:27:38.200> medium<00:27:38.559> of<00:27:38.799> expression<00:27:39.399> for 00:27:40.350 --> 00:27:40.360 align:start position:0% what is it a medium of expression for 00:27:40.360 --> 00:27:41.870 align:start position:0% what is it a medium of expression for consider<00:27:40.799> all<00:27:41.000> that's<00:27:41.200> been<00:27:41.360> built<00:27:41.600> around 00:27:41.870 --> 00:27:41.880 align:start position:0% consider all that's been built around 00:27:41.880 --> 00:27:43.990 align:start position:0% consider all that's been built around computer<00:27:42.279> technology<00:27:43.279> especially<00:27:43.799> the 00:27:43.990 --> 00:27:44.000 align:start position:0% computer technology especially the 00:27:44.000 --> 00:27:46.149 align:start position:0% computer technology especially the companies<00:27:44.600> the<00:27:44.720> organizations<00:27:45.480> the<00:27:45.720> products 00:27:46.149 --> 00:27:46.159 align:start position:0% companies the organizations the products 00:27:46.159 --> 00:27:48.669 align:start position:0% companies the organizations the products the<00:27:46.799> institutions<00:27:47.799> what<00:27:47.919> are<00:27:48.080> they 00:27:48.669 --> 00:27:48.679 align:start position:0% the institutions what are they 00:27:48.679 --> 00:27:50.870 align:start position:0% the institutions what are they expressing<00:27:49.679> or<00:27:50.120> this<00:27:50.200> is<00:27:50.320> a<00:27:50.399> bit<00:27:50.559> more<00:27:50.679> of<00:27:50.799> a 00:27:50.870 --> 00:27:50.880 align:start position:0% expressing or this is a bit more of a 00:27:50.880 --> 00:27:54.110 align:start position:0% expressing or this is a bit more of a leading<00:27:51.320> question<00:27:51.880> what<00:27:52.159> have<00:27:52.440> they<00:27:53.120> become 00:27:54.110 --> 00:27:54.120 align:start position:0% leading question what have they become 00:27:54.120 --> 00:27:56.230 align:start position:0% leading question what have they become everyone<00:27:54.600> senses<00:27:55.279> something<00:27:55.679> has<00:27:55.840> gone<00:27:56.000> a<00:27:56.120> bit 00:27:56.230 --> 00:27:56.240 align:start position:0% everyone senses something has gone a bit 00:27:56.240 --> 00:27:58.430 align:start position:0% everyone senses something has gone a bit ay<00:27:56.840> with<00:27:57.000> our<00:27:57.200> relationship<00:27:57.919> with<00:27:58.279> the 00:27:58.430 --> 00:27:58.440 align:start position:0% ay with our relationship with the 00:27:58.440 --> 00:28:00.750 align:start position:0% ay with our relationship with the digital<00:27:59.320> a<00:27:59.519> relationship<00:28:00.120> that's<00:28:00.360> largely 00:28:00.750 --> 00:28:00.760 align:start position:0% digital a relationship that's largely 00:28:00.760 --> 00:28:02.430 align:start position:0% digital a relationship that's largely mediated<00:28:01.320> by<00:28:01.480> what<00:28:01.640> we<00:28:01.760> broadly<00:28:02.159> call 00:28:02.430 --> 00:28:02.440 align:start position:0% mediated by what we broadly call 00:28:02.440 --> 00:28:04.389 align:start position:0% mediated by what we broadly call computer 00:28:04.389 --> 00:28:04.399 align:start position:0% computer 00:28:04.399 --> 00:28:06.710 align:start position:0% computer technology<00:28:05.399> and<00:28:05.559> so<00:28:06.159> I<00:28:06.240> want<00:28:06.320> to<00:28:06.399> take<00:28:06.519> this 00:28:06.710 --> 00:28:06.720 align:start position:0% technology and so I want to take this 00:28:06.720 --> 00:28:08.590 align:start position:0% technology and so I want to take this immune<00:28:07.120> system<00:28:07.480> lens<00:28:07.919> when<00:28:08.039> we<00:28:08.200> think<00:28:08.399> of<00:28:08.519> the 00:28:08.590 --> 00:28:08.600 align:start position:0% immune system lens when we think of the 00:28:08.600 --> 00:28:10.549 align:start position:0% immune system lens when we think of the word<00:28:08.840> immune<00:28:09.200> system<00:28:09.559> we<00:28:09.720> naturally<00:28:10.120> think<00:28:10.440> of 00:28:10.549 --> 00:28:10.559 align:start position:0% word immune system we naturally think of 00:28:10.559 --> 00:28:12.549 align:start position:0% word immune system we naturally think of our<00:28:10.880> physical<00:28:11.320> immune<00:28:11.720> systems<00:28:12.399> this 00:28:12.549 --> 00:28:12.559 align:start position:0% our physical immune systems this 00:28:12.559 --> 00:28:14.870 align:start position:0% our physical immune systems this predates<00:28:13.000> literally<00:28:13.440> Humanity<00:28:13.880> itself<00:28:14.760> but 00:28:14.870 --> 00:28:14.880 align:start position:0% predates literally Humanity itself but 00:28:14.880 --> 00:28:16.549 align:start position:0% predates literally Humanity itself but for<00:28:15.039> much<00:28:15.200> of<00:28:15.399> human<00:28:15.720> history<00:28:16.039> there's<00:28:16.320> also 00:28:16.549 --> 00:28:16.559 align:start position:0% for much of human history there's also 00:28:16.559 --> 00:28:18.149 align:start position:0% for much of human history there's also been<00:28:16.799> this<00:28:16.960> implicit<00:28:17.440> notion<00:28:17.880> of<00:28:18.000> an 00:28:18.149 --> 00:28:18.159 align:start position:0% been this implicit notion of an 00:28:18.159 --> 00:28:19.950 align:start position:0% been this implicit notion of an intellectual<00:28:18.720> immune<00:28:19.080> system<00:28:19.679> you<00:28:19.760> could 00:28:19.950 --> 00:28:19.960 align:start position:0% intellectual immune system you could 00:28:19.960 --> 00:28:21.269 align:start position:0% intellectual immune system you could also<00:28:20.200> consider<00:28:20.559> calling<00:28:20.880> this<00:28:21.080> a 00:28:21.269 --> 00:28:21.279 align:start position:0% also consider calling this a 00:28:21.279 --> 00:28:23.630 align:start position:0% also consider calling this a philosophical<00:28:22.159> immune<00:28:22.480> system<00:28:23.279> think<00:28:23.440> about 00:28:23.630 --> 00:28:23.640 align:start position:0% philosophical immune system think about 00:28:23.640 --> 00:28:25.149 align:start position:0% philosophical immune system think about how<00:28:23.720> you<00:28:23.919> respond<00:28:24.360> intellectually<00:28:25.000> to 00:28:25.149 --> 00:28:25.159 align:start position:0% how you respond intellectually to 00:28:25.159 --> 00:28:27.310 align:start position:0% how you respond intellectually to various<00:28:25.600> things<00:28:26.159> how<00:28:26.320> that's<00:28:26.600> changed 00:28:27.310 --> 00:28:27.320 align:start position:0% various things how that's changed 00:28:27.320 --> 00:28:29.470 align:start position:0% various things how that's changed developed<00:28:27.799> over<00:28:28.240> time<00:28:29.080> sometimes<00:28:29.240> it 00:28:29.470 --> 00:28:29.480 align:start position:0% developed over time sometimes it 00:28:29.480 --> 00:28:31.230 align:start position:0% developed over time sometimes it strengthens<00:28:30.480> sometimes<00:28:30.679> it's<00:28:30.919> probably 00:28:31.230 --> 00:28:31.240 align:start position:0% strengthens sometimes it's probably 00:28:31.240 --> 00:28:32.750 align:start position:0% strengthens sometimes it's probably weakened<00:28:31.799> kind<00:28:31.919> of<00:28:32.080> like<00:28:32.200> your<00:28:32.399> physical 00:28:32.750 --> 00:28:32.760 align:start position:0% weakened kind of like your physical 00:28:32.760 --> 00:28:33.590 align:start position:0% weakened kind of like your physical immune 00:28:33.590 --> 00:28:33.600 align:start position:0% immune 00:28:33.600 --> 00:28:36.310 align:start position:0% immune system<00:28:34.600> what<00:28:34.720> about<00:28:34.880> the<00:28:35.000> digital<00:28:36.000> right<00:28:36.200> now 00:28:36.310 --> 00:28:36.320 align:start position:0% system what about the digital right now 00:28:36.320 --> 00:28:38.750 align:start position:0% system what about the digital right now we<00:28:36.440> think<00:28:36.679> of<00:28:36.880> digital<00:28:37.360> stuff<00:28:38.120> in<00:28:38.240> terms<00:28:38.519> of 00:28:38.750 --> 00:28:38.760 align:start position:0% we think of digital stuff in terms of 00:28:38.760 --> 00:28:41.190 align:start position:0% we think of digital stuff in terms of security<00:28:39.399> and<00:28:39.679> protection<00:28:40.679> but<00:28:40.799> as<00:28:40.960> our 00:28:41.190 --> 00:28:41.200 align:start position:0% security and protection but as our 00:28:41.200 --> 00:28:42.830 align:start position:0% security and protection but as our digitally<00:28:41.919> anchored<00:28:42.320> and<00:28:42.399> oriented 00:28:42.830 --> 00:28:42.840 align:start position:0% digitally anchored and oriented 00:28:42.840 --> 00:28:44.630 align:start position:0% digitally anchored and oriented experiences<00:28:43.320> become<00:28:43.640> increasingly 00:28:44.630 --> 00:28:44.640 align:start position:0% experiences become increasingly 00:28:44.640 --> 00:28:47.029 align:start position:0% experiences become increasingly intertwined<00:28:45.320> with<00:28:45.440> our<00:28:45.679> lives<00:28:46.559> perhaps<00:28:46.880> the 00:28:47.029 --> 00:28:47.039 align:start position:0% intertwined with our lives perhaps the 00:28:47.039 --> 00:28:48.870 align:start position:0% intertwined with our lives perhaps the notion<00:28:47.320> of<00:28:47.480> an<00:28:47.640> almost<00:28:48.000> organic<00:28:48.519> digital 00:28:48.870 --> 00:28:48.880 align:start position:0% notion of an almost organic digital 00:28:48.880 --> 00:28:51.710 align:start position:0% notion of an almost organic digital immune<00:28:49.200> system<00:28:49.720> is<00:28:49.840> a<00:28:49.960> way<00:28:50.080> to<00:28:50.240> think<00:28:50.440> about<00:28:50.720> it 00:28:51.710 --> 00:28:51.720 align:start position:0% immune system is a way to think about it 00:28:51.720 --> 00:28:54.029 align:start position:0% immune system is a way to think about it notably<00:28:52.640> a<00:28:52.840> digital<00:28:53.240> immune<00:28:53.600> system 00:28:54.029 --> 00:28:54.039 align:start position:0% notably a digital immune system 00:28:54.039 --> 00:28:55.830 align:start position:0% notably a digital immune system conceptually<00:28:54.760> wouldn't<00:28:55.039> even<00:28:55.279> have<00:28:55.519> been 00:28:55.830 --> 00:28:55.840 align:start position:0% conceptually wouldn't even have been 00:28:55.840 --> 00:28:59.430 align:start position:0% conceptually wouldn't even have been cogent<00:28:56.799> 100<00:28:57.039> years<00:28:57.240> ago<00:28:57.559> probably<00:28:58.240> less<00:28:59.240> it's 00:28:59.430 --> 00:28:59.440 align:start position:0% cogent 100 years ago probably less it's 00:28:59.440 --> 00:29:01.909 align:start position:0% cogent 100 years ago probably less it's simply<00:28:59.799> much<00:29:00.000> newer<00:29:00.480> almost<00:29:00.799> primordial<00:29:01.760> so 00:29:01.909 --> 00:29:01.919 align:start position:0% simply much newer almost primordial so 00:29:01.919 --> 00:29:03.350 align:start position:0% simply much newer almost primordial so we<00:29:02.039> need<00:29:02.159> to<00:29:02.320> remember<00:29:02.640> it's<00:29:02.880> going<00:29:03.159> through 00:29:03.350 --> 00:29:03.360 align:start position:0% we need to remember it's going through 00:29:03.360 --> 00:29:05.070 align:start position:0% we need to remember it's going through things<00:29:03.559> that<00:29:03.679> are<00:29:03.840> more<00:29:04.120> associated<00:29:04.760> with<00:29:04.880> the 00:29:05.070 --> 00:29:05.080 align:start position:0% things that are more associated with the 00:29:05.080 --> 00:29:06.789 align:start position:0% things that are more associated with the very<00:29:05.320> early<00:29:05.679> stages<00:29:06.080> of<00:29:06.200> a<00:29:06.320> system<00:29:06.600> or 00:29:06.789 --> 00:29:06.799 align:start position:0% very early stages of a system or 00:29:06.799 --> 00:29:07.909 align:start position:0% very early stages of a system or ecosystem 00:29:07.909 --> 00:29:07.919 align:start position:0% ecosystem 00:29:07.919 --> 00:29:10.509 align:start position:0% ecosystem developing<00:29:08.919> for<00:29:09.120> instance<00:29:09.960> one<00:29:10.200> might<00:29:10.360> say 00:29:10.509 --> 00:29:10.519 align:start position:0% developing for instance one might say 00:29:10.519 --> 00:29:11.669 align:start position:0% developing for instance one might say that<00:29:10.640> the<00:29:10.760> interaction<00:29:11.279> between<00:29:11.519> the 00:29:11.669 --> 00:29:11.679 align:start position:0% that the interaction between the 00:29:11.679 --> 00:29:14.190 align:start position:0% that the interaction between the physical<00:29:12.000> and<00:29:12.120> the<00:29:12.279> digital<00:29:12.880> currently<00:29:13.279> leans 00:29:14.190 --> 00:29:14.200 align:start position:0% physical and the digital currently leans 00:29:14.200 --> 00:29:16.149 align:start position:0% physical and the digital currently leans parasitic<00:29:15.200> this<00:29:15.320> is<00:29:15.519> partly<00:29:15.840> because<00:29:16.039> we 00:29:16.149 --> 00:29:16.159 align:start position:0% parasitic this is partly because we 00:29:16.159 --> 00:29:17.789 align:start position:0% parasitic this is partly because we haven't<00:29:16.440> realized<00:29:16.880> the<00:29:16.960> full<00:29:17.240> potential<00:29:17.640> of 00:29:17.789 --> 00:29:17.799 align:start position:0% haven't realized the full potential of 00:29:17.799 --> 00:29:19.470 align:start position:0% haven't realized the full potential of digital<00:29:18.120> Technologies<00:29:18.720> and<00:29:18.919> and<00:29:19.039> I<00:29:19.159> guess<00:29:19.320> the 00:29:19.470 --> 00:29:19.480 align:start position:0% digital Technologies and and I guess the 00:29:19.480 --> 00:29:21.549 align:start position:0% digital Technologies and and I guess the digital<00:29:19.840> realm<00:29:20.399> to<00:29:20.519> be<00:29:20.679> more<00:29:20.880> symbiotic<00:29:21.440> with 00:29:21.549 --> 00:29:21.559 align:start position:0% digital realm to be more symbiotic with 00:29:21.559 --> 00:29:24.070 align:start position:0% digital realm to be more symbiotic with our<00:29:21.720> overall<00:29:22.360> existence<00:29:23.360> but<00:29:23.559> I<00:29:23.679> think<00:29:23.880> this 00:29:24.070 --> 00:29:24.080 align:start position:0% our overall existence but I think this 00:29:24.080 --> 00:29:26.310 align:start position:0% our overall existence but I think this can<00:29:24.320> and<00:29:24.519> inevitably<00:29:25.360> inevitably<00:29:26.000> will 00:29:26.310 --> 00:29:26.320 align:start position:0% can and inevitably inevitably will 00:29:26.320 --> 00:29:28.350 align:start position:0% can and inevitably inevitably will happen<00:29:27.000> especially<00:29:27.360> as<00:29:27.480> our<00:29:27.600> intellect<00:29:28.080> ual 00:29:28.350 --> 00:29:28.360 align:start position:0% happen especially as our intellect ual 00:29:28.360 --> 00:29:30.870 align:start position:0% happen especially as our intellect ual immune<00:29:28.640> systems<00:29:29.360> co-develop<00:29:29.880> or<00:29:30.039> co-evolve 00:29:30.870 --> 00:29:30.880 align:start position:0% immune systems co-develop or co-evolve 00:29:30.880 --> 00:29:33.110 align:start position:0% immune systems co-develop or co-evolve with<00:29:31.000> our<00:29:31.159> digital<00:29:31.519> immune<00:29:31.799> systems<00:29:32.640> remember 00:29:33.110 --> 00:29:33.120 align:start position:0% with our digital immune systems remember 00:29:33.120 --> 00:29:34.669 align:start position:0% with our digital immune systems remember one<00:29:33.240> of<00:29:33.360> the<00:29:33.480> most<00:29:33.679> underrated<00:29:34.240> things<00:29:34.440> about 00:29:34.669 --> 00:29:34.679 align:start position:0% one of the most underrated things about 00:29:34.679 --> 00:29:37.149 align:start position:0% one of the most underrated things about evolution<00:29:35.360> is<00:29:35.519> that<00:29:35.760> symbiotic<00:29:36.360> coexistence 00:29:37.149 --> 00:29:37.159 align:start position:0% evolution is that symbiotic coexistence 00:29:37.159 --> 00:29:38.470 align:start position:0% evolution is that symbiotic coexistence is<00:29:37.320> literally<00:29:37.640> a<00:29:37.799> more<00:29:38.080> effective 00:29:38.470 --> 00:29:38.480 align:start position:0% is literally a more effective 00:29:38.480 --> 00:29:41.110 align:start position:0% is literally a more effective equilibrium<00:29:39.399> than<00:29:39.679> Total<00:29:40.080> Takeover<00:29:40.880> this<00:29:40.960> is 00:29:41.110 --> 00:29:41.120 align:start position:0% equilibrium than Total Takeover this is 00:29:41.120 --> 00:29:43.110 align:start position:0% equilibrium than Total Takeover this is true<00:29:41.559> even<00:29:41.760> when<00:29:41.919> the<00:29:42.120> specific<00:29:42.519> organisms 00:29:43.110 --> 00:29:43.120 align:start position:0% true even when the specific organisms 00:29:43.120 --> 00:29:45.070 align:start position:0% true even when the specific organisms fundamentally<00:29:43.720> remain<00:29:43.880> in<00:29:44.120> competition<00:29:44.919> such 00:29:45.070 --> 00:29:45.080 align:start position:0% fundamentally remain in competition such 00:29:45.080 --> 00:29:46.990 align:start position:0% fundamentally remain in competition such as<00:29:45.240> predator<00:29:45.640> and<00:29:45.840> prey<00:29:46.399> if<00:29:46.480> the<00:29:46.600> Predators 00:29:46.990 --> 00:29:47.000 align:start position:0% as predator and prey if the Predators 00:29:47.000 --> 00:29:48.310 align:start position:0% as predator and prey if the Predators start<00:29:47.200> doing<00:29:47.399> too<00:29:47.559> well<00:29:47.760> they<00:29:47.880> crowd<00:29:48.200> each 00:29:48.310 --> 00:29:48.320 align:start position:0% start doing too well they crowd each 00:29:48.320 --> 00:29:52.310 align:start position:0% start doing too well they crowd each other<00:29:48.559> out<00:29:49.559> same<00:29:49.919> goes<00:29:50.360> for<00:29:50.559> the<00:29:51.120> prey<00:29:52.120> now<00:29:52.240> you 00:29:52.310 --> 00:29:52.320 align:start position:0% other out same goes for the prey now you 00:29:52.320 --> 00:29:53.909 align:start position:0% other out same goes for the prey now you might<00:29:52.440> think<00:29:52.679> okay<00:29:52.840> cool<00:29:53.320> digital<00:29:53.640> immune 00:29:53.909 --> 00:29:53.919 align:start position:0% might think okay cool digital immune 00:29:53.919 --> 00:29:56.110 align:start position:0% might think okay cool digital immune system<00:29:54.360> cryptography<00:29:55.360> that<00:29:55.480> makes<00:29:55.720> sense<00:29:56.000> the 00:29:56.110 --> 00:29:56.120 align:start position:0% system cryptography that makes sense the 00:29:56.120 --> 00:29:58.509 align:start position:0% system cryptography that makes sense the connection<00:29:56.519> is<00:29:57.200> relevant<00:29:58.039> but<00:29:58.120> that's<00:29:58.279> not 00:29:58.509 --> 00:29:58.519 align:start position:0% connection is relevant but that's not 00:29:58.519 --> 00:30:00.350 align:start position:0% connection is relevant but that's not exactly<00:29:59.120> where<00:29:59.480> I'm 00:30:00.350 --> 00:30:00.360 align:start position:0% exactly where I'm 00:30:00.360 --> 00:30:03.470 align:start position:0% exactly where I'm going<00:30:01.360> what<00:30:01.480> I<00:30:01.559> want<00:30:01.679> to<00:30:01.840> consider<00:30:02.279> next<00:30:02.679> is 00:30:03.470 --> 00:30:03.480 align:start position:0% going what I want to consider next is 00:30:03.480 --> 00:30:05.669 align:start position:0% going what I want to consider next is literacy<00:30:04.480> consider<00:30:04.919> this<00:30:05.039> word<00:30:05.279> and<00:30:05.440> why<00:30:05.559> it 00:30:05.669 --> 00:30:05.679 align:start position:0% literacy consider this word and why it 00:30:05.679 --> 00:30:09.110 align:start position:0% literacy consider this word and why it even<00:30:06.399> exists<00:30:07.399> it<00:30:07.519> used<00:30:07.720> to<00:30:07.880> be<00:30:08.080> notable<00:30:08.840> when 00:30:09.110 --> 00:30:09.120 align:start position:0% even exists it used to be notable when 00:30:09.120 --> 00:30:12.350 align:start position:0% even exists it used to be notable when someone<00:30:09.760> was<00:30:10.039> literate<00:30:10.640> as<00:30:10.760> in<00:30:11.159> could<00:30:11.640> read<00:30:12.120> or 00:30:12.350 --> 00:30:12.360 align:start position:0% someone was literate as in could read or 00:30:12.360 --> 00:30:15.269 align:start position:0% someone was literate as in could read or write<00:30:13.000> for<00:30:13.200> most<00:30:13.360> of<00:30:13.519> History<00:30:13.840> it<00:30:14.000> was<00:30:14.240> rare<00:30:14.679> or 00:30:15.269 --> 00:30:15.279 align:start position:0% write for most of History it was rare or 00:30:15.279 --> 00:30:17.110 align:start position:0% write for most of History it was rare or definitely<00:30:15.600> not<00:30:15.840> universally<00:30:16.480> expected<00:30:16.919> for 00:30:17.110 --> 00:30:17.120 align:start position:0% definitely not universally expected for 00:30:17.120 --> 00:30:19.149 align:start position:0% definitely not universally expected for people<00:30:17.399> to<00:30:17.600> be<00:30:17.840> literate<00:30:18.760> that's<00:30:18.919> why<00:30:19.039> the 00:30:19.149 --> 00:30:19.159 align:start position:0% people to be literate that's why the 00:30:19.159 --> 00:30:21.789 align:start position:0% people to be literate that's why the word<00:30:19.480> exists<00:30:20.200> to<00:30:20.440> point<00:30:20.640> out<00:30:20.799> an<00:30:21.039> unexpected 00:30:21.789 --> 00:30:21.799 align:start position:0% word exists to point out an unexpected 00:30:21.799 --> 00:30:24.509 align:start position:0% word exists to point out an unexpected thing<00:30:22.799> of<00:30:22.960> course<00:30:23.519> today<00:30:23.840> it's<00:30:24.000> notable<00:30:24.399> when 00:30:24.509 --> 00:30:24.519 align:start position:0% thing of course today it's notable when 00:30:24.519 --> 00:30:26.990 align:start position:0% thing of course today it's notable when someone<00:30:24.799> is<00:30:25.559> illiterate<00:30:26.559> it's<00:30:26.679> not<00:30:26.840> just 00:30:26.990 --> 00:30:27.000 align:start position:0% someone is illiterate it's not just 00:30:27.000 --> 00:30:28.750 align:start position:0% someone is illiterate it's not just notable<00:30:27.399> it<00:30:27.519> kind<00:30:27.600> of<00:30:27.679> feels<00:30:28.200> wrong<00:30:28.600> like 00:30:28.750 --> 00:30:28.760 align:start position:0% notable it kind of feels wrong like 00:30:28.760 --> 00:30:31.310 align:start position:0% notable it kind of feels wrong like Society<00:30:29.200> has<00:30:29.399> failed<00:30:29.840> that<00:30:30.039> person<00:30:30.960> keep<00:30:31.159> this 00:30:31.310 --> 00:30:31.320 align:start position:0% Society has failed that person keep this 00:30:31.320 --> 00:30:34.430 align:start position:0% Society has failed that person keep this in<00:30:31.480> mind<00:30:32.399> going<00:30:32.679> from<00:30:33.000> default<00:30:33.480> illiterate<00:30:34.159> to 00:30:34.430 --> 00:30:34.440 align:start position:0% in mind going from default illiterate to 00:30:34.440 --> 00:30:37.110 align:start position:0% in mind going from default illiterate to default<00:30:34.880> literate<00:30:35.679> happens<00:30:36.159> all<00:30:36.320> the<00:30:36.519> time 00:30:37.110 --> 00:30:37.120 align:start position:0% default literate happens all the time 00:30:37.120 --> 00:30:39.389 align:start position:0% default literate happens all the time often<00:30:37.440> slowly<00:30:38.039> then 00:30:39.389 --> 00:30:39.399 align:start position:0% often slowly then 00:30:39.399 --> 00:30:41.750 align:start position:0% often slowly then quickly<00:30:40.399> one<00:30:40.559> of<00:30:40.679> the<00:30:40.919> most<00:30:41.279> well-known 00:30:41.750 --> 00:30:41.760 align:start position:0% quickly one of the most well-known 00:30:41.760 --> 00:30:43.710 align:start position:0% quickly one of the most well-known company<00:30:42.080> slogans<00:30:42.399> of<00:30:42.519> my<00:30:42.799> childhood<00:30:43.399> was<00:30:43.559> from 00:30:43.710 --> 00:30:43.720 align:start position:0% company slogans of my childhood was from 00:30:43.720 --> 00:30:45.909 align:start position:0% company slogans of my childhood was from Bill<00:30:43.960> Gates<00:30:44.200> and<00:30:44.360> Microsoft<00:30:45.320> as<00:30:45.399> you<00:30:45.519> can<00:30:45.640> see 00:30:45.909 --> 00:30:45.919 align:start position:0% Bill Gates and Microsoft as you can see 00:30:45.919 --> 00:30:48.029 align:start position:0% Bill Gates and Microsoft as you can see the<00:30:46.039> slogan<00:30:46.399> was<00:30:46.640> a<00:30:46.799> computer<00:30:47.200> on<00:30:47.399> every<00:30:47.720> desk 00:30:48.029 --> 00:30:48.039 align:start position:0% the slogan was a computer on every desk 00:30:48.039 --> 00:30:50.470 align:start position:0% the slogan was a computer on every desk and<00:30:48.159> in<00:30:48.320> every<00:30:48.559> home<00:30:49.399> 30<00:30:49.720> plus<00:30:49.919> years<00:30:50.080> ago<00:30:50.360> this 00:30:50.470 --> 00:30:50.480 align:start position:0% and in every home 30 plus years ago this 00:30:50.480 --> 00:30:52.470 align:start position:0% and in every home 30 plus years ago this sounded<00:30:50.880> incredibly<00:30:51.600> ambitious<00:30:52.200> it<00:30:52.279> was 00:30:52.470 --> 00:30:52.480 align:start position:0% sounded incredibly ambitious it was 00:30:52.480 --> 00:30:54.990 align:start position:0% sounded incredibly ambitious it was almost<00:30:52.799> awe<00:30:53.440> inspiring<00:30:54.440> as<00:30:54.519> it<00:30:54.640> turned<00:30:54.840> out 00:30:54.990 --> 00:30:55.000 align:start position:0% almost awe inspiring as it turned out 00:30:55.000 --> 00:30:56.990 align:start position:0% almost awe inspiring as it turned out this<00:30:55.080> was<00:30:55.320> nowhere<00:30:55.639> near<00:30:55.840> ambitious<00:30:56.320> enough 00:30:56.990 --> 00:30:57.000 align:start position:0% this was nowhere near ambitious enough 00:30:57.000 --> 00:30:58.870 align:start position:0% this was nowhere near ambitious enough should<00:30:57.159> have<00:30:57.240> been<00:30:57.360> a<00:30:57.440> computer<00:30:58.159> pocket 00:30:58.870 --> 00:30:58.880 align:start position:0% should have been a computer pocket 00:30:58.880 --> 00:31:00.549 align:start position:0% should have been a computer pocket computer<00:30:59.240> with<00:30:59.320> you<00:30:59.440> at<00:30:59.559> all<00:30:59.760> times<00:31:00.399> a 00:31:00.549 --> 00:31:00.559 align:start position:0% computer with you at all times a 00:31:00.559 --> 00:31:02.190 align:start position:0% computer with you at all times a computer<00:31:00.919> the<00:31:01.080> first<00:31:01.360> thing<00:31:01.720> when<00:31:01.880> you<00:31:02.000> wake 00:31:02.190 --> 00:31:02.200 align:start position:0% computer the first thing when you wake 00:31:02.200 --> 00:31:05.029 align:start position:0% computer the first thing when you wake up<00:31:02.919> the<00:31:03.120> last<00:31:03.399> before<00:31:03.600> you<00:31:03.720> sleep<00:31:04.600> a<00:31:04.720> computer 00:31:05.029 --> 00:31:05.039 align:start position:0% up the last before you sleep a computer 00:31:05.039 --> 00:31:06.470 align:start position:0% up the last before you sleep a computer while<00:31:05.159> you're<00:31:05.279> on<00:31:05.399> the<00:31:05.519> toilet<00:31:06.240> when<00:31:06.360> you're 00:31:06.470 --> 00:31:06.480 align:start position:0% while you're on the toilet when you're 00:31:06.480 --> 00:31:09.029 align:start position:0% while you're on the toilet when you're in<00:31:06.559> a<00:31:06.679> meeting<00:31:07.320> or<00:31:07.519> attending<00:31:07.880> a<00:31:08.080> talk<00:31:08.840> a 00:31:09.029 --> 00:31:09.039 align:start position:0% in a meeting or attending a talk a 00:31:09.039 --> 00:31:12.789 align:start position:0% in a meeting or attending a talk a computer<00:31:09.559> every<00:31:10.240> we<00:31:10.519> at<00:31:10.639> all 00:31:12.789 --> 00:31:12.799 align:start position:0% computer every we at all 00:31:12.799 --> 00:31:16.070 align:start position:0% computer every we at all times<00:31:13.799> computer<00:31:14.240> literacy<00:31:15.159> as<00:31:15.320> in<00:31:15.559> being<00:31:15.840> able 00:31:16.070 --> 00:31:16.080 align:start position:0% times computer literacy as in being able 00:31:16.080 --> 00:31:18.230 align:start position:0% times computer literacy as in being able to<00:31:16.240> make<00:31:16.399> use<00:31:16.559> of<00:31:16.639> a<00:31:16.799> computer<00:31:17.200> for<00:31:17.399> your<00:31:17.600> needs 00:31:18.230 --> 00:31:18.240 align:start position:0% to make use of a computer for your needs 00:31:18.240 --> 00:31:21.190 align:start position:0% to make use of a computer for your needs was<00:31:18.519> rare<00:31:18.960> until<00:31:19.320> very<00:31:19.760> recently<00:31:20.760> when<00:31:20.960> I<00:31:21.080> was 00:31:21.190 --> 00:31:21.200 align:start position:0% was rare until very recently when I was 00:31:21.200 --> 00:31:23.149 align:start position:0% was rare until very recently when I was a<00:31:21.399> kid<00:31:22.080> aptitude<00:31:22.440> with<00:31:22.600> computers<00:31:22.960> was 00:31:23.149 --> 00:31:23.159 align:start position:0% a kid aptitude with computers was 00:31:23.159 --> 00:31:25.590 align:start position:0% a kid aptitude with computers was actually<00:31:23.399> low<00:31:23.840> viewed<00:31:24.159> as<00:31:24.320> low<00:31:24.720> status 00:31:25.590 --> 00:31:25.600 align:start position:0% actually low viewed as low status 00:31:25.600 --> 00:31:27.110 align:start position:0% actually low viewed as low status phrases<00:31:26.080> like<00:31:26.360> computers<00:31:26.720> are<00:31:26.880> for 00:31:27.110 --> 00:31:27.120 align:start position:0% phrases like computers are for 00:31:27.120 --> 00:31:30.070 align:start position:0% phrases like computers are for secretaries<00:31:27.960> were<00:31:28.200> common<00:31:29.080> today<00:31:29.720> everyone 00:31:30.070 --> 00:31:30.080 align:start position:0% secretaries were common today everyone 00:31:30.080 --> 00:31:32.269 align:start position:0% secretaries were common today everyone below<00:31:30.320> a<00:31:30.440> certain<00:31:30.679> age<00:31:30.840> is<00:31:31.000> computer<00:31:31.399> literate 00:31:32.269 --> 00:31:32.279 align:start position:0% below a certain age is computer literate 00:31:32.279 --> 00:31:33.269 align:start position:0% below a certain age is computer literate but<00:31:32.440> not<00:31:32.559> in<00:31:32.639> the<00:31:32.760> way<00:31:32.880> that<00:31:32.960> you<00:31:33.039> might<00:31:33.159> have 00:31:33.269 --> 00:31:33.279 align:start position:0% but not in the way that you might have 00:31:33.279 --> 00:31:35.669 align:start position:0% but not in the way that you might have naively<00:31:33.760> expected<00:31:34.159> 25<00:31:34.600> years<00:31:34.840> ago<00:31:35.360> and<00:31:35.480> it's 00:31:35.669 --> 00:31:35.679 align:start position:0% naively expected 25 years ago and it's 00:31:35.679 --> 00:31:37.389 align:start position:0% naively expected 25 years ago and it's definitely<00:31:36.039> not<00:31:36.200> that<00:31:36.360> everyone<00:31:36.799> now<00:31:37.039> knows 00:31:37.389 --> 00:31:37.399 align:start position:0% definitely not that everyone now knows 00:31:37.399 --> 00:31:39.750 align:start position:0% definitely not that everyone now knows how<00:31:37.639> computers<00:31:38.240> work<00:31:39.120> it's<00:31:39.240> that<00:31:39.480> every 00:31:39.750 --> 00:31:39.760 align:start position:0% how computers work it's that every 00:31:39.760 --> 00:31:41.470 align:start position:0% how computers work it's that every computers<00:31:40.159> became<00:31:40.399> a<00:31:40.519> thing<00:31:40.799> everyone<00:31:41.159> knew 00:31:41.470 --> 00:31:41.480 align:start position:0% computers became a thing everyone knew 00:31:41.480 --> 00:31:43.509 align:start position:0% computers became a thing everyone knew how<00:31:41.679> to<00:31:41.880> use<00:31:42.519> thanks<00:31:42.720> in<00:31:42.880> large<00:31:43.120> part<00:31:43.240> to<00:31:43.360> the 00:31:43.509 --> 00:31:43.519 align:start position:0% how to use thanks in large part to the 00:31:43.519 --> 00:31:45.430 align:start position:0% how to use thanks in large part to the iPhone<00:31:43.960> and<00:31:44.080> the<00:31:44.159> subsequent<00:31:44.639> smartphone 00:31:45.430 --> 00:31:45.440 align:start position:0% iPhone and the subsequent smartphone 00:31:45.440 --> 00:31:47.950 align:start position:0% iPhone and the subsequent smartphone Revolution<00:31:46.440> again<00:31:47.000> default<00:31:47.399> illiterate 00:31:47.950 --> 00:31:47.960 align:start position:0% Revolution again default illiterate 00:31:47.960 --> 00:31:50.070 align:start position:0% Revolution again default illiterate becomes<00:31:48.360> default<00:31:48.760> literate<00:31:49.480> but<00:31:49.720> how<00:31:49.919> it 00:31:50.070 --> 00:31:50.080 align:start position:0% becomes default literate but how it 00:31:50.080 --> 00:31:52.549 align:start position:0% becomes default literate but how it happens<00:31:50.440> is<00:31:50.639> often<00:31:50.960> hard<00:31:51.200> to<00:31:51.399> predict<00:31:52.360> even 00:31:52.549 --> 00:31:52.559 align:start position:0% happens is often hard to predict even 00:31:52.559 --> 00:31:54.669 align:start position:0% happens is often hard to predict even when<00:31:52.720> the<00:31:52.919> iPhone<00:31:53.399> came<00:31:53.639> out<00:31:54.200> many<00:31:54.440> thought<00:31:54.600> it 00:31:54.669 --> 00:31:54.679 align:start position:0% when the iPhone came out many thought it 00:31:54.679 --> 00:31:56.509 align:start position:0% when the iPhone came out many thought it was<00:31:54.799> going<00:31:54.880> to<00:31:54.960> be<00:31:55.039> a<00:31:55.120> total 00:31:56.509 --> 00:31:56.519 align:start position:0% was going to be a total 00:31:56.519 --> 00:31:59.230 align:start position:0% was going to be a total flop<00:31:57.519> consider<00:31:58.120> also<00:31:58.360> how<00:31:58.480> the<00:31:58.679> concept<00:31:59.080> of 00:31:59.230 --> 00:31:59.240 align:start position:0% flop consider also how the concept of 00:31:59.240 --> 00:32:01.230 align:start position:0% flop consider also how the concept of photographic<00:31:59.840> evidence<00:32:00.320> has<00:32:00.480> only<00:32:00.799> existed 00:32:01.230 --> 00:32:01.240 align:start position:0% photographic evidence has only existed 00:32:01.240 --> 00:32:03.350 align:start position:0% photographic evidence has only existed for<00:32:01.440> like<00:32:01.559> a<00:32:01.799> hundred<00:32:02.159> years<00:32:02.799> imagine<00:32:03.120> telling 00:32:03.350 --> 00:32:03.360 align:start position:0% for like a hundred years imagine telling 00:32:03.360 --> 00:32:04.870 align:start position:0% for like a hundred years imagine telling someone<00:32:03.600> in<00:32:03.760> 1850<00:32:04.440> that<00:32:04.519> there's<00:32:04.679> a 00:32:04.870 --> 00:32:04.880 align:start position:0% someone in 1850 that there's a 00:32:04.880 --> 00:32:07.389 align:start position:0% someone in 1850 that there's a photograph<00:32:05.360> or<00:32:05.559> video<00:32:05.919> or<00:32:06.159> audio<00:32:06.519> recording 00:32:07.389 --> 00:32:07.399 align:start position:0% photograph or video or audio recording 00:32:07.399 --> 00:32:09.389 align:start position:0% photograph or video or audio recording to<00:32:07.720> prove<00:32:08.000> or<00:32:08.240> disprove<00:32:08.760> their<00:32:08.919> version<00:32:09.200> of 00:32:09.389 --> 00:32:09.399 align:start position:0% to prove or disprove their version of 00:32:09.399 --> 00:32:11.509 align:start position:0% to prove or disprove their version of events<00:32:10.279> today<00:32:10.600> that<00:32:10.760> idea<00:32:11.000> is<00:32:11.120> entirely 00:32:11.509 --> 00:32:11.519 align:start position:0% events today that idea is entirely 00:32:11.519 --> 00:32:13.110 align:start position:0% events today that idea is entirely second<00:32:11.960> nature<00:32:12.320> most<00:32:12.480> of<00:32:12.600> us<00:32:12.760> have<00:32:12.919> never 00:32:13.110 --> 00:32:13.120 align:start position:0% second nature most of us have never 00:32:13.120 --> 00:32:15.029 align:start position:0% second nature most of us have never known<00:32:13.360> a<00:32:13.480> world<00:32:13.679> without<00:32:14.000> it<00:32:14.799> of<00:32:14.880> course 00:32:15.029 --> 00:32:15.039 align:start position:0% known a world without it of course 00:32:15.039 --> 00:32:17.190 align:start position:0% known a world without it of course there's<00:32:15.200> a<00:32:15.360> storm<00:32:15.760> brewing<00:32:16.240> brewing<00:32:16.960> with 00:32:17.190 --> 00:32:17.200 align:start position:0% there's a storm brewing brewing with 00:32:17.200 --> 00:32:19.070 align:start position:0% there's a storm brewing brewing with progress<00:32:17.559> on<00:32:17.760> what<00:32:17.880> we<00:32:18.039> call<00:32:18.279> AI<00:32:18.840> because<00:32:19.000> we 00:32:19.070 --> 00:32:19.080 align:start position:0% progress on what we call AI because we 00:32:19.080 --> 00:32:20.870 align:start position:0% progress on what we call AI because we don't<00:32:19.240> know<00:32:19.360> what<00:32:19.480> else<00:32:19.639> to<00:32:19.799> call<00:32:20.000> it<00:32:20.760> the 00:32:20.870 --> 00:32:20.880 align:start position:0% don't know what else to call it the 00:32:20.880 --> 00:32:22.990 align:start position:0% don't know what else to call it the current<00:32:21.279> concept<00:32:21.559> of<00:32:21.679> photographic<00:32:22.360> evidence 00:32:22.990 --> 00:32:23.000 align:start position:0% current concept of photographic evidence 00:32:23.000 --> 00:32:25.029 align:start position:0% current concept of photographic evidence definitely<00:32:23.519> won't<00:32:23.799> last<00:32:24.000> another<00:32:24.360> 100<00:32:24.639> years 00:32:25.029 --> 00:32:25.039 align:start position:0% definitely won't last another 100 years 00:32:25.039 --> 00:32:27.950 align:start position:0% definitely won't last another 100 years might<00:32:25.200> not<00:32:25.360> even<00:32:25.639> last<00:32:26.000> 10<00:32:27.000> if<00:32:27.120> you<00:32:27.320> naively 00:32:27.950 --> 00:32:27.960 align:start position:0% might not even last 10 if you naively 00:32:27.960 --> 00:32:29.190 align:start position:0% might not even last 10 if you naively extrapolate<00:32:28.559> you<00:32:28.679> might<00:32:28.840> think<00:32:28.960> we're<00:32:29.120> going 00:32:29.190 --> 00:32:29.200 align:start position:0% extrapolate you might think we're going 00:32:29.200 --> 00:32:31.669 align:start position:0% extrapolate you might think we're going to<00:32:29.360> revert<00:32:29.720> to<00:32:29.880> the<00:32:30.000> world<00:32:30.360> of<00:32:30.639> trust<00:32:30.919> me<00:32:31.120> bro 00:32:31.669 --> 00:32:31.679 align:start position:0% to revert to the world of trust me bro 00:32:31.679 --> 00:32:33.549 align:start position:0% to revert to the world of trust me bro just<00:32:31.840> like<00:32:32.080> all<00:32:32.320> of<00:32:32.639> history<00:32:33.159> before<00:32:33.440> the 00:32:33.549 --> 00:32:33.559 align:start position:0% just like all of history before the 00:32:33.559 --> 00:32:35.590 align:start position:0% just like all of history before the photographic<00:32:34.159> evidence 00:32:35.590 --> 00:32:35.600 align:start position:0% photographic evidence 00:32:35.600 --> 00:32:38.269 align:start position:0% photographic evidence era<00:32:36.600> but<00:32:36.720> naive<00:32:37.080> extrapolation<00:32:37.639> almost<00:32:37.919> never 00:32:38.269 --> 00:32:38.279 align:start position:0% era but naive extrapolation almost never 00:32:38.279 --> 00:32:40.629 align:start position:0% era but naive extrapolation almost never actually<00:32:38.600> plays<00:32:38.880> out<00:32:39.639> a<00:32:39.760> couple<00:32:40.039> Generations 00:32:40.629 --> 00:32:40.639 align:start position:0% actually plays out a couple Generations 00:32:40.639 --> 00:32:42.909 align:start position:0% actually plays out a couple Generations from<00:32:40.880> now<00:32:41.799> cryptographically<00:32:42.559> grounded 00:32:42.909 --> 00:32:42.919 align:start position:0% from now cryptographically grounded 00:32:42.919 --> 00:32:44.710 align:start position:0% from now cryptographically grounded evidence<00:32:43.279> will<00:32:43.440> be<00:32:43.600> second<00:32:44.039> nature<00:32:44.279> to<00:32:44.440> people 00:32:44.710 --> 00:32:44.720 align:start position:0% evidence will be second nature to people 00:32:44.720 --> 00:32:46.430 align:start position:0% evidence will be second nature to people the<00:32:44.840> same<00:32:45.039> way<00:32:45.240> iPhones<00:32:45.679> made<00:32:45.960> computers 00:32:46.430 --> 00:32:46.440 align:start position:0% the same way iPhones made computers 00:32:46.440 --> 00:32:49.149 align:start position:0% the same way iPhones made computers second<00:32:46.799> nature<00:32:47.120> to<00:32:47.320> kids<00:32:47.639> today<00:32:48.639> the<00:32:48.760> same<00:32:48.960> way 00:32:49.149 --> 00:32:49.159 align:start position:0% second nature to kids today the same way 00:32:49.159 --> 00:32:50.909 align:start position:0% second nature to kids today the same way photographic<00:32:49.799> evidence<00:32:50.200> has<00:32:50.360> been<00:32:50.559> second 00:32:50.909 --> 00:32:50.919 align:start position:0% photographic evidence has been second 00:32:50.919 --> 00:32:51.990 align:start position:0% photographic evidence has been second nature<00:32:51.240> for 00:32:51.990 --> 00:32:52.000 align:start position:0% nature for 00:32:52.000 --> 00:32:54.110 align:start position:0% nature for decades<00:32:53.000> but<00:32:53.279> it's<00:32:53.399> not<00:32:53.559> even<00:32:53.760> really<00:32:53.960> the 00:32:54.110 --> 00:32:54.120 align:start position:0% decades but it's not even really the 00:32:54.120 --> 00:32:56.549 align:start position:0% decades but it's not even really the cryptographic<00:32:55.039> evidence<00:32:55.639> era<00:32:56.000> we<00:32:56.159> kind<00:32:56.320> of 00:32:56.549 --> 00:32:56.559 align:start position:0% cryptographic evidence era we kind of 00:32:56.559 --> 00:32:59.029 align:start position:0% cryptographic evidence era we kind of have<00:32:56.760> that<00:32:57.000> already<00:32:57.440> to<00:32:57.559> some<00:32:57.840> some<00:32:58.039> extent 00:32:59.029 --> 00:32:59.039 align:start position:0% have that already to some some extent 00:32:59.039 --> 00:33:01.230 align:start position:0% have that already to some some extent it's<00:32:59.200> the<00:32:59.320> cryptographic<00:32:59.919> literacy<00:33:00.440> era 00:33:01.230 --> 00:33:01.240 align:start position:0% it's the cryptographic literacy era 00:33:01.240 --> 00:33:03.549 align:start position:0% it's the cryptographic literacy era remember<00:33:01.720> literacy<00:33:02.320> doesn't<00:33:02.600> mean<00:33:02.960> Mastery 00:33:03.549 --> 00:33:03.559 align:start position:0% remember literacy doesn't mean Mastery 00:33:03.559 --> 00:33:05.310 align:start position:0% remember literacy doesn't mean Mastery and<00:33:03.799> widespread<00:33:04.320> cryptographic<00:33:04.880> literacy 00:33:05.310 --> 00:33:05.320 align:start position:0% and widespread cryptographic literacy 00:33:05.320 --> 00:33:06.830 align:start position:0% and widespread cryptographic literacy doesn't<00:33:05.559> mean<00:33:05.840> widespread<00:33:06.480> understanding<00:33:06.720> of 00:33:06.830 --> 00:33:06.840 align:start position:0% doesn't mean widespread understanding of 00:33:06.840 --> 00:33:09.310 align:start position:0% doesn't mean widespread understanding of how<00:33:07.000> cryptography<00:33:07.919> Works<00:33:08.760> similar<00:33:09.080> to<00:33:09.159> how<00:33:09.240> I 00:33:09.310 --> 00:33:09.320 align:start position:0% how cryptography Works similar to how I 00:33:09.320 --> 00:33:11.110 align:start position:0% how cryptography Works similar to how I noted<00:33:09.559> earlier<00:33:09.840> that<00:33:10.000> widespread<00:33:10.440> computer<00:33:10.799> L 00:33:11.110 --> 00:33:11.120 align:start position:0% noted earlier that widespread computer L 00:33:11.120 --> 00:33:12.870 align:start position:0% noted earlier that widespread computer L literacy<00:33:11.559> doesn't<00:33:11.799> mean<00:33:12.120> everyone<00:33:12.440> knows<00:33:12.720> how 00:33:12.870 --> 00:33:12.880 align:start position:0% literacy doesn't mean everyone knows how 00:33:12.880 --> 00:33:14.590 align:start position:0% literacy doesn't mean everyone knows how a<00:33:13.039> computer 00:33:14.590 --> 00:33:14.600 align:start position:0% a computer 00:33:14.600 --> 00:33:17.389 align:start position:0% a computer works<00:33:15.600> still<00:33:16.480> what's<00:33:16.840> really<00:33:17.120> going<00:33:17.240> to 00:33:17.389 --> 00:33:17.399 align:start position:0% works still what's really going to 00:33:17.399 --> 00:33:18.750 align:start position:0% works still what's really going to happen<00:33:17.600> is<00:33:17.760> not<00:33:18.120> actually<00:33:18.399> going<00:33:18.519> to<00:33:18.639> be 00:33:18.750 --> 00:33:18.760 align:start position:0% happen is not actually going to be 00:33:18.760 --> 00:33:21.070 align:start position:0% happen is not actually going to be thought<00:33:18.919> of<00:33:19.039> as<00:33:19.159> cryptographic<00:33:20.080> literacy 00:33:21.070 --> 00:33:21.080 align:start position:0% thought of as cryptographic literacy 00:33:21.080 --> 00:33:23.269 align:start position:0% thought of as cryptographic literacy what<00:33:21.240> will<00:33:21.440> it<00:33:21.600> be<00:33:21.799> thought<00:33:22.000> of 00:33:23.269 --> 00:33:23.279 align:start position:0% what will it be thought of 00:33:23.279 --> 00:33:26.310 align:start position:0% what will it be thought of as<00:33:24.279> I<00:33:24.440> consider<00:33:24.919> this<00:33:25.279> one<00:33:25.399> of<00:33:25.600> italic<00:33:26.120> most 00:33:26.310 --> 00:33:26.320 align:start position:0% as I consider this one of italic most 00:33:26.320 --> 00:33:27.870 align:start position:0% as I consider this one of italic most underrated<00:33:26.799> blog<00:33:27.039> posts<00:33:27.320> should<00:33:27.480> be<00:33:27.559> pretty 00:33:27.870 --> 00:33:27.880 align:start position:0% underrated blog posts should be pretty 00:33:27.880 --> 00:33:30.710 align:start position:0% underrated blog posts should be pretty easy<00:33:28.080> to<00:33:28.159> look<00:33:28.320> it<00:33:28.480> up<00:33:29.000> given<00:33:29.240> the<00:33:29.720> title 00:33:30.710 --> 00:33:30.720 align:start position:0% easy to look it up given the title 00:33:30.720 --> 00:33:33.149 align:start position:0% easy to look it up given the title within<00:33:30.960> the<00:33:31.120> post<00:33:31.760> balic<00:33:32.159> defined<00:33:32.480> legitimacy 00:33:33.149 --> 00:33:33.159 align:start position:0% within the post balic defined legitimacy 00:33:33.159 --> 00:33:36.029 align:start position:0% within the post balic defined legitimacy as<00:33:33.519> a<00:33:33.799> pattern<00:33:34.200> of<00:33:34.399> higher<00:33:34.720> order<00:33:35.200> acceptance 00:33:36.029 --> 00:33:36.039 align:start position:0% as a pattern of higher order acceptance 00:33:36.039 --> 00:33:38.310 align:start position:0% as a pattern of higher order acceptance Loosely<00:33:36.480> speaking<00:33:37.120> people<00:33:37.600> expecting<00:33:38.039> other 00:33:38.310 --> 00:33:38.320 align:start position:0% Loosely speaking people expecting other 00:33:38.320 --> 00:33:40.269 align:start position:0% Loosely speaking people expecting other people<00:33:38.679> to<00:33:38.960> expect<00:33:39.480> the<00:33:39.639> same<00:33:39.840> things<00:33:40.120> and 00:33:40.269 --> 00:33:40.279 align:start position:0% people to expect the same things and 00:33:40.279 --> 00:33:43.310 align:start position:0% people to expect the same things and therefore<00:33:40.559> we<00:33:40.679> can<00:33:40.919> all<00:33:41.240> expect 00:33:43.310 --> 00:33:43.320 align:start position:0% therefore we can all expect 00:33:43.320 --> 00:33:45.870 align:start position:0% therefore we can all expect something<00:33:44.320> recall<00:33:44.679> that<00:33:44.960> smartphones<00:33:45.720> are 00:33:45.870 --> 00:33:45.880 align:start position:0% something recall that smartphones are 00:33:45.880 --> 00:33:48.070 align:start position:0% something recall that smartphones are what<00:33:46.039> unlocked<00:33:46.559> computer<00:33:46.960> literacy<00:33:47.799> they<00:33:47.919> are 00:33:48.070 --> 00:33:48.080 align:start position:0% what unlocked computer literacy they are 00:33:48.080 --> 00:33:49.350 align:start position:0% what unlocked computer literacy they are the<00:33:48.200> form<00:33:48.399> and<00:33:48.559> mechanism<00:33:49.000> through<00:33:49.200> which 00:33:49.350 --> 00:33:49.360 align:start position:0% the form and mechanism through which 00:33:49.360 --> 00:33:51.950 align:start position:0% the form and mechanism through which computer<00:33:49.760> literacy<00:33:50.240> became<00:33:50.480> near<00:33:50.960> Universal 00:33:51.950 --> 00:33:51.960 align:start position:0% computer literacy became near Universal 00:33:51.960 --> 00:33:54.269 align:start position:0% computer literacy became near Universal for<00:33:52.120> cryptographic<00:33:52.720> literacy<00:33:53.360> or<00:33:53.559> legitimacy 00:33:54.269 --> 00:33:54.279 align:start position:0% for cryptographic literacy or legitimacy 00:33:54.279 --> 00:33:56.549 align:start position:0% for cryptographic literacy or legitimacy literacy<00:33:55.279> the<00:33:55.480> form<00:33:55.760> and<00:33:55.960> mechanism<00:33:56.440> is 00:33:56.549 --> 00:33:56.559 align:start position:0% literacy the form and mechanism is 00:33:56.559 --> 00:33:58.110 align:start position:0% literacy the form and mechanism is something<00:33:56.840> we<00:33:56.960> don't<00:33:57.159> know<00:33:57.360> yet<00:33:57.799> what<00:33:57.919> is<00:33:58.000> it 00:33:58.110 --> 00:33:58.120 align:start position:0% something we don't know yet what is it 00:33:58.120 --> 00:33:59.669 align:start position:0% something we don't know yet what is it that<00:33:58.279> makes<00:33:58.600> things<00:33:58.840> more<00:33:59.080> high<00:33:59.279> order 00:33:59.669 --> 00:33:59.679 align:start position:0% that makes things more high order 00:33:59.679 --> 00:34:02.110 align:start position:0% that makes things more high order accepted<00:34:00.279> in<00:34:00.440> this<00:34:00.639> broader<00:34:01.080> sense<00:34:01.840> product 00:34:02.110 --> 00:34:02.120 align:start position:0% accepted in this broader sense product 00:34:02.120 --> 00:34:03.669 align:start position:0% accepted in this broader sense product and<00:34:02.279> Technology<00:34:02.679> Innovations<00:34:03.120> will<00:34:03.279> unlock 00:34:03.669 --> 00:34:03.679 align:start position:0% and Technology Innovations will unlock 00:34:03.679 --> 00:34:05.350 align:start position:0% and Technology Innovations will unlock this<00:34:03.799> future<00:34:04.159> and<00:34:04.320> I<00:34:04.399> bet<00:34:04.639> some<00:34:04.840> of<00:34:05.039> them<00:34:05.240> will 00:34:05.350 --> 00:34:05.360 align:start position:0% this future and I bet some of them will 00:34:05.360 --> 00:34:07.350 align:start position:0% this future and I bet some of them will feel<00:34:05.639> just<00:34:05.880> as<00:34:06.000> surprising<00:34:06.760> as<00:34:06.880> the<00:34:07.039> iPhone 00:34:07.350 --> 00:34:07.360 align:start position:0% feel just as surprising as the iPhone 00:34:07.360 --> 00:34:09.550 align:start position:0% feel just as surprising as the iPhone would<00:34:07.519> have<00:34:07.639> felt<00:34:08.079> just<00:34:08.280> 30<00:34:08.639> years<00:34:08.879> ago<00:34:09.359> to 00:34:09.550 --> 00:34:09.560 align:start position:0% would have felt just 30 years ago to 00:34:09.560 --> 00:34:11.550 align:start position:0% would have felt just 30 years ago to someone<00:34:09.800> still<00:34:10.000> being<00:34:10.240> AED<00:34:10.679> by<00:34:10.919> Bill<00:34:11.119> Gates's 00:34:11.550 --> 00:34:11.560 align:start position:0% someone still being AED by Bill Gates's 00:34:11.560 --> 00:34:13.510 align:start position:0% someone still being AED by Bill Gates's computer<00:34:11.879> on<00:34:12.040> every<00:34:12.280> desk 00:34:13.510 --> 00:34:13.520 align:start position:0% computer on every desk 00:34:13.520 --> 00:34:16.230 align:start position:0% computer on every desk Vision<00:34:14.520> also<00:34:14.839> remember<00:34:15.599> the<00:34:15.760> value<00:34:16.000> of<00:34:16.119> the 00:34:16.230 --> 00:34:16.240 align:start position:0% Vision also remember the value of the 00:34:16.240 --> 00:34:18.109 align:start position:0% Vision also remember the value of the wheel<00:34:16.919> it<00:34:17.040> was<00:34:17.200> unlocked<00:34:17.599> by<00:34:17.679> the<00:34:17.800> invention 00:34:18.109 --> 00:34:18.119 align:start position:0% wheel it was unlocked by the invention 00:34:18.119 --> 00:34:20.430 align:start position:0% wheel it was unlocked by the invention of<00:34:18.280> the<00:34:18.480> axle<00:34:19.320> people<00:34:19.560> weren't<00:34:19.919> idiots<00:34:20.280> they 00:34:20.430 --> 00:34:20.440 align:start position:0% of the axle people weren't idiots they 00:34:20.440 --> 00:34:21.950 align:start position:0% of the axle people weren't idiots they long<00:34:20.599> noticed<00:34:20.960> that<00:34:21.079> round<00:34:21.359> things<00:34:21.560> can<00:34:21.760> move 00:34:21.950 --> 00:34:21.960 align:start position:0% long noticed that round things can move 00:34:21.960 --> 00:34:24.349 align:start position:0% long noticed that round things can move more<00:34:22.159> easily<00:34:22.960> but<00:34:23.240> that's<00:34:23.560> not<00:34:23.800> what<00:34:23.919> it<00:34:24.079> takes 00:34:24.349 --> 00:34:24.359 align:start position:0% more easily but that's not what it takes 00:34:24.359 --> 00:34:26.510 align:start position:0% more easily but that's not what it takes to<00:34:24.560> make<00:34:24.760> use<00:34:25.040> of<00:34:25.200> the<00:34:25.359> wheel<00:34:25.960> we<00:34:26.159> don't<00:34:26.359> know 00:34:26.510 --> 00:34:26.520 align:start position:0% to make use of the wheel we don't know 00:34:26.520 --> 00:34:28.109 align:start position:0% to make use of the wheel we don't know what<00:34:26.639> the<00:34:26.760> axles<00:34:27.079> are<00:34:27.240> to<00:34:27.359> Crypt<00:34:27.720> phography 00:34:28.109 --> 00:34:28.119 align:start position:0% what the axles are to Crypt phography 00:34:28.119 --> 00:34:29.149 align:start position:0% what the axles are to Crypt phography Wheels 00:34:29.149 --> 00:34:29.159 align:start position:0% Wheels 00:34:29.159 --> 00:34:31.430 align:start position:0% Wheels yet<00:34:30.159> one<00:34:30.359> consequence<00:34:30.800> of<00:34:30.919> all<00:34:31.079> this<00:34:31.200> is<00:34:31.320> that 00:34:31.430 --> 00:34:31.440 align:start position:0% yet one consequence of all this is that 00:34:31.440 --> 00:34:32.829 align:start position:0% yet one consequence of all this is that something<00:34:31.679> that<00:34:31.760> feels<00:34:32.040> like<00:34:32.159> cryptographic 00:34:32.829 --> 00:34:32.839 align:start position:0% something that feels like cryptographic 00:34:32.839 --> 00:34:34.869 align:start position:0% something that feels like cryptographic writing<00:34:33.159> will<00:34:33.399> exist<00:34:34.119> I'm<00:34:34.240> sure<00:34:34.520> it<00:34:34.639> won't 00:34:34.869 --> 00:34:34.879 align:start position:0% writing will exist I'm sure it won't 00:34:34.879 --> 00:34:36.550 align:start position:0% writing will exist I'm sure it won't feel<00:34:35.159> literally<00:34:35.679> like<00:34:35.879> writing<00:34:36.240> combined 00:34:36.550 --> 00:34:36.560 align:start position:0% feel literally like writing combined 00:34:36.560 --> 00:34:38.270 align:start position:0% feel literally like writing combined with<00:34:36.720> cryptographic<00:34:37.280> signatures<00:34:37.800> in<00:34:37.960> fact<00:34:38.119> we 00:34:38.270 --> 00:34:38.280 align:start position:0% with cryptographic signatures in fact we 00:34:38.280 --> 00:34:40.149 align:start position:0% with cryptographic signatures in fact we already<00:34:38.720> have<00:34:39.000> that<00:34:39.520> but<00:34:39.679> what's<00:34:39.879> important 00:34:40.149 --> 00:34:40.159 align:start position:0% already have that but what's important 00:34:40.159 --> 00:34:41.589 align:start position:0% already have that but what's important is<00:34:40.280> it'll<00:34:40.560> have<00:34:40.679> the<00:34:40.839> property<00:34:41.200> of<00:34:41.320> being 00:34:41.589 --> 00:34:41.599 align:start position:0% is it'll have the property of being 00:34:41.599 --> 00:34:43.109 align:start position:0% is it'll have the property of being inherently<00:34:42.119> higher<00:34:42.399> legitimacy<00:34:42.919> than 00:34:43.109 --> 00:34:43.119 align:start position:0% inherently higher legitimacy than 00:34:43.119 --> 00:34:45.430 align:start position:0% inherently higher legitimacy than conventional<00:34:43.720> digital<00:34:44.079> writing<00:34:44.960> we<00:34:45.040> will<00:34:45.240> not 00:34:45.430 --> 00:34:45.440 align:start position:0% conventional digital writing we will not 00:34:45.440 --> 00:34:46.990 align:start position:0% conventional digital writing we will not think<00:34:45.599> of<00:34:45.760> all<00:34:45.960> things<00:34:46.159> written<00:34:46.440> digitally<00:34:46.879> as 00:34:46.990 --> 00:34:47.000 align:start position:0% think of all things written digitally as 00:34:47.000 --> 00:34:48.470 align:start position:0% think of all things written digitally as being<00:34:47.200> more<00:34:47.320> or<00:34:47.520> less<00:34:47.760> the<00:34:47.879> same<00:34:48.280> this<00:34:48.399> is 00:34:48.470 --> 00:34:48.480 align:start position:0% being more or less the same this is 00:34:48.480 --> 00:34:49.710 align:start position:0% being more or less the same this is already<00:34:48.679> true<00:34:48.839> to<00:34:48.960> a<00:34:49.119> limited<00:34:49.480> extent 00:34:49.710 --> 00:34:49.720 align:start position:0% already true to a limited extent 00:34:49.720 --> 00:34:50.990 align:start position:0% already true to a limited extent depending<00:34:50.000> on<00:34:50.119> the<00:34:50.280> context<00:34:50.760> but<00:34:50.839> the 00:34:50.990 --> 00:34:51.000 align:start position:0% depending on the context but the 00:34:51.000 --> 00:34:52.230 align:start position:0% depending on the context but the distinction<00:34:51.359> will<00:34:51.520> be<00:34:51.800> much<00:34:52.000> more 00:34:52.230 --> 00:34:52.240 align:start position:0% distinction will be much more 00:34:52.240 --> 00:34:53.550 align:start position:0% distinction will be much more substantial<00:34:53.040> and<00:34:53.159> there<00:34:53.240> will<00:34:53.320> be<00:34:53.440> a 00:34:53.550 --> 00:34:53.560 align:start position:0% substantial and there will be a 00:34:53.560 --> 00:34:55.869 align:start position:0% substantial and there will be a reflexive<00:34:54.000> feedback<00:34:54.440> loop<00:34:55.079> that<00:34:55.240> causes<00:34:55.679> even 00:34:55.869 --> 00:34:55.879 align:start position:0% reflexive feedback loop that causes even 00:34:55.879 --> 00:34:57.470 align:start position:0% reflexive feedback loop that causes even more<00:34:56.079> widespread<00:34:56.560> legitimacy<00:34:57.079> literacy 00:34:57.470 --> 00:34:57.480 align:start position:0% more widespread legitimacy literacy 00:34:57.480 --> 00:34:59.430 align:start position:0% more widespread legitimacy literacy through<00:34:57.680> throughout<00:34:58.000> Society<00:34:58.920> all<00:34:59.079> of<00:34:59.280> this 00:34:59.430 --> 00:34:59.440 align:start position:0% through throughout Society all of this 00:34:59.440 --> 00:35:01.589 align:start position:0% through throughout Society all of this will<00:34:59.680> contribute<00:35:00.359> to<00:35:00.599> another<00:35:00.880> shift<00:35:01.160> in<00:35:01.320> how 00:35:01.589 --> 00:35:01.599 align:start position:0% will contribute to another shift in how 00:35:01.599 --> 00:35:03.470 align:start position:0% will contribute to another shift in how people<00:35:01.839> feel<00:35:02.320> about<00:35:02.560> cryptography<00:35:03.200> even<00:35:03.359> if 00:35:03.470 --> 00:35:03.480 align:start position:0% people feel about cryptography even if 00:35:03.480 --> 00:35:04.870 align:start position:0% people feel about cryptography even if they<00:35:03.599> don't<00:35:03.800> know<00:35:04.040> that's<00:35:04.200> the<00:35:04.359> thing<00:35:04.560> that 00:35:04.870 --> 00:35:04.880 align:start position:0% they don't know that's the thing that 00:35:04.880 --> 00:35:06.950 align:start position:0% they don't know that's the thing that they<00:35:05.000> are<00:35:05.119> feeling<00:35:05.480> something 00:35:06.950 --> 00:35:06.960 align:start position:0% they are feeling something 00:35:06.960 --> 00:35:09.109 align:start position:0% they are feeling something about<00:35:07.960> so<00:35:08.119> everything<00:35:08.400> so<00:35:08.599> far<00:35:08.760> I've<00:35:08.920> put 00:35:09.109 --> 00:35:09.119 align:start position:0% about so everything so far I've put 00:35:09.119 --> 00:35:11.550 align:start position:0% about so everything so far I've put under<00:35:09.720> the<00:35:09.960> real<00:35:10.800> now<00:35:10.960> I<00:35:11.040> want<00:35:11.160> to<00:35:11.240> start<00:35:11.400> to 00:35:11.550 --> 00:35:11.560 align:start position:0% under the real now I want to start to 00:35:11.560 --> 00:35:14.470 align:start position:0% under the real now I want to start to segue<00:35:12.040> towards<00:35:12.440> the<00:35:12.599> super<00:35:12.960> real<00:35:13.800> to<00:35:13.920> do<00:35:14.119> that 00:35:14.470 --> 00:35:14.480 align:start position:0% segue towards the super real to do that 00:35:14.480 --> 00:35:16.790 align:start position:0% segue towards the super real to do that first<00:35:14.839> I<00:35:14.920> want<00:35:15.040> to<00:35:15.280> revisit<00:35:15.800> some<00:35:16.079> miracles<00:35:16.560> of 00:35:16.790 --> 00:35:16.800 align:start position:0% first I want to revisit some miracles of 00:35:16.800 --> 00:35:19.630 align:start position:0% first I want to revisit some miracles of science<00:35:17.280> here<00:35:17.440> I'll<00:35:17.720> Loosely<00:35:18.240> Define<00:35:18.680> Miracle 00:35:19.630 --> 00:35:19.640 align:start position:0% science here I'll Loosely Define Miracle 00:35:19.640 --> 00:35:21.230 align:start position:0% science here I'll Loosely Define Miracle as<00:35:19.839> something<00:35:20.200> where<00:35:20.359> if<00:35:20.440> you<00:35:20.560> didn't<00:35:20.839> know 00:35:21.230 --> 00:35:21.240 align:start position:0% as something where if you didn't know 00:35:21.240 --> 00:35:23.190 align:start position:0% as something where if you didn't know something<00:35:21.640> existed<00:35:21.960> or<00:35:22.119> was<00:35:22.359> possible<00:35:23.119> it 00:35:23.190 --> 00:35:23.200 align:start position:0% something existed or was possible it 00:35:23.200 --> 00:35:24.990 align:start position:0% something existed or was possible it would<00:35:23.359> be<00:35:23.640> very<00:35:23.960> surprising<00:35:24.599> that<00:35:24.760> such<00:35:24.880> a 00:35:24.990 --> 00:35:25.000 align:start position:0% would be very surprising that such a 00:35:25.000 --> 00:35:26.230 align:start position:0% would be very surprising that such a thing<00:35:25.240> exists<00:35:25.680> just<00:35:25.800> as<00:35:25.920> it<00:35:26.000> would<00:35:26.160> be 00:35:26.230 --> 00:35:26.240 align:start position:0% thing exists just as it would be 00:35:26.240 --> 00:35:28.670 align:start position:0% thing exists just as it would be surprising<00:35:26.680> if<00:35:26.920> magic<00:35:27.280> exists 00:35:28.670 --> 00:35:28.680 align:start position:0% surprising if magic exists 00:35:28.680 --> 00:35:30.829 align:start position:0% surprising if magic exists my<00:35:28.839> first<00:35:29.079> example<00:35:29.400> is<00:35:29.599> fire<00:35:30.320> the<00:35:30.480> existence 00:35:30.829 --> 00:35:30.839 align:start position:0% my first example is fire the existence 00:35:30.839 --> 00:35:32.589 align:start position:0% my first example is fire the existence isn't<00:35:31.079> a<00:35:31.200> surprise<00:35:31.680> since<00:35:31.839> it<00:35:32.000> spontaneously 00:35:32.589 --> 00:35:32.599 align:start position:0% isn't a surprise since it spontaneously 00:35:32.599 --> 00:35:34.430 align:start position:0% isn't a surprise since it spontaneously occurs<00:35:32.880> in<00:35:33.040> nature<00:35:33.680> but<00:35:33.839> the<00:35:33.960> ability<00:35:34.280> to 00:35:34.430 --> 00:35:34.440 align:start position:0% occurs in nature but the ability to 00:35:34.440 --> 00:35:36.230 align:start position:0% occurs in nature but the ability to control<00:35:34.920> fire<00:35:35.359> was<00:35:35.599> a<00:35:35.760> significant 00:35:36.230 --> 00:35:36.240 align:start position:0% control fire was a significant 00:35:36.240 --> 00:35:39.069 align:start position:0% control fire was a significant development<00:35:36.839> to<00:35:37.000> say<00:35:37.160> the<00:35:37.680> least<00:35:38.680> next<00:35:38.839> is 00:35:39.069 --> 00:35:39.079 align:start position:0% development to say the least next is 00:35:39.079 --> 00:35:41.190 align:start position:0% development to say the least next is electricity<00:35:40.079> this<00:35:40.200> one<00:35:40.359> is<00:35:40.480> a<00:35:40.599> bit<00:35:40.720> surprising 00:35:41.190 --> 00:35:41.200 align:start position:0% electricity this one is a bit surprising 00:35:41.200 --> 00:35:43.670 align:start position:0% electricity this one is a bit surprising I<00:35:41.320> guess<00:35:41.480> people<00:35:41.839> had<00:35:42.040> seen<00:35:42.480> lightning<00:35:43.400> but 00:35:43.670 --> 00:35:43.680 align:start position:0% I guess people had seen lightning but 00:35:43.680 --> 00:35:45.109 align:start position:0% I guess people had seen lightning but what<00:35:43.839> reason<00:35:44.119> was<00:35:44.280> there<00:35:44.400> to<00:35:44.599> believe<00:35:44.920> that 00:35:45.109 --> 00:35:45.119 align:start position:0% what reason was there to believe that 00:35:45.119 --> 00:35:46.829 align:start position:0% what reason was there to believe that this<00:35:45.240> thing<00:35:45.440> could<00:35:45.640> be<00:35:46.160> harness<00:35:46.680> that<00:35:46.760> it 00:35:46.829 --> 00:35:46.839 align:start position:0% this thing could be harness that it 00:35:46.839 --> 00:35:48.349 align:start position:0% this thing could be harness that it would<00:35:46.960> turn<00:35:47.079> out<00:35:47.160> to<00:35:47.280> be<00:35:47.480> magic<00:35:47.839> juice<00:35:48.240> that 00:35:48.349 --> 00:35:48.359 align:start position:0% would turn out to be magic juice that 00:35:48.359 --> 00:35:49.990 align:start position:0% would turn out to be magic juice that moves<00:35:48.720> infinitely<00:35:49.200> fast<00:35:49.440> and<00:35:49.640> basically 00:35:49.990 --> 00:35:50.000 align:start position:0% moves infinitely fast and basically 00:35:50.000 --> 00:35:51.990 align:start position:0% moves infinitely fast and basically gives<00:35:50.200> us<00:35:50.680> permanent<00:35:51.079> light<00:35:51.400> communication 00:35:51.990 --> 00:35:52.000 align:start position:0% gives us permanent light communication 00:35:52.000 --> 00:35:54.069 align:start position:0% gives us permanent light communication across<00:35:52.440> vast<00:35:52.720> distances<00:35:53.480> or<00:35:53.599> to<00:35:53.720> be<00:35:53.800> able<00:35:53.960> to 00:35:54.069 --> 00:35:54.079 align:start position:0% across vast distances or to be able to 00:35:54.079 --> 00:35:55.790 align:start position:0% across vast distances or to be able to construct<00:35:54.599> things<00:35:54.880> like 00:35:55.790 --> 00:35:55.800 align:start position:0% construct things like 00:35:55.800 --> 00:35:58.030 align:start position:0% construct things like computers<00:35:56.800> then<00:35:56.920> there's<00:35:57.119> nuclear<00:35:57.720> power 00:35:58.030 --> 00:35:58.040 align:start position:0% computers then there's nuclear power 00:35:58.040 --> 00:36:00.390 align:start position:0% computers then there's nuclear power which<00:35:58.240> was<00:35:58.680> I<00:35:58.760> think<00:35:59.000> truly<00:35:59.359> a<00:35:59.560> surprise<00:36:00.280> like 00:36:00.390 --> 00:36:00.400 align:start position:0% which was I think truly a surprise like 00:36:00.400 --> 00:36:02.430 align:start position:0% which was I think truly a surprise like wait<00:36:00.560> a<00:36:00.680> second<00:36:01.040> effectively<00:36:01.599> infinite<00:36:02.040> power 00:36:02.430 --> 00:36:02.440 align:start position:0% wait a second effectively infinite power 00:36:02.440 --> 00:36:05.550 align:start position:0% wait a second effectively infinite power is<00:36:02.720> everywhere<00:36:03.640> mass<00:36:03.920> is<00:36:04.079> literally 00:36:05.550 --> 00:36:05.560 align:start position:0% is everywhere mass is literally 00:36:05.560 --> 00:36:07.790 align:start position:0% is everywhere mass is literally energy<00:36:06.560> but<00:36:06.680> there's<00:36:06.839> one<00:36:07.000> more<00:36:07.200> source<00:36:07.599> of 00:36:07.790 --> 00:36:07.800 align:start position:0% energy but there's one more source of 00:36:07.800 --> 00:36:09.470 align:start position:0% energy but there's one more source of quote<00:36:08.040> unquote<00:36:08.440> power<00:36:08.640> that<00:36:08.760> gets<00:36:08.960> overlooked 00:36:09.470 --> 00:36:09.480 align:start position:0% quote unquote power that gets overlooked 00:36:09.480 --> 00:36:10.829 align:start position:0% quote unquote power that gets overlooked because<00:36:09.640> it's<00:36:09.760> a<00:36:09.920> fundamentally<00:36:10.520> different 00:36:10.829 --> 00:36:10.839 align:start position:0% because it's a fundamentally different 00:36:10.839 --> 00:36:13.150 align:start position:0% because it's a fundamentally different type<00:36:11.040> of<00:36:11.280> power<00:36:12.000> each<00:36:12.160> of<00:36:12.319> the<00:36:12.520> first<00:36:12.839> three 00:36:13.150 --> 00:36:13.160 align:start position:0% type of power each of the first three 00:36:13.160 --> 00:36:15.150 align:start position:0% type of power each of the first three Miracle<00:36:13.720> power<00:36:13.960> sources<00:36:14.400> can<00:36:14.520> be<00:36:14.640> viewed<00:36:14.920> as 00:36:15.150 --> 00:36:15.160 align:start position:0% Miracle power sources can be viewed as 00:36:15.160 --> 00:36:17.550 align:start position:0% Miracle power sources can be viewed as asymmetric<00:36:15.839> offense<00:36:16.599> it's<00:36:16.760> a<00:36:16.920> lot<00:36:17.119> easier<00:36:17.400> to 00:36:17.550 --> 00:36:17.560 align:start position:0% asymmetric offense it's a lot easier to 00:36:17.560 --> 00:36:19.030 align:start position:0% asymmetric offense it's a lot easier to burn<00:36:17.880> something<00:36:18.160> to<00:36:18.319> make<00:36:18.520> than<00:36:18.640> to<00:36:18.760> make<00:36:18.880> it 00:36:19.030 --> 00:36:19.040 align:start position:0% burn something to make than to make it 00:36:19.040 --> 00:36:21.150 align:start position:0% burn something to make than to make it fireproof<00:36:19.920> and<00:36:20.040> we<00:36:20.160> know<00:36:20.400> how<00:36:20.680> powerful<00:36:21.000> a 00:36:21.150 --> 00:36:21.160 align:start position:0% fireproof and we know how powerful a 00:36:21.160 --> 00:36:23.910 align:start position:0% fireproof and we know how powerful a nuclear<00:36:21.640> weapon<00:36:22.040> can<00:36:22.240> be<00:36:23.119> but<00:36:23.319> as<00:36:23.440> I<00:36:23.560> noted 00:36:23.910 --> 00:36:23.920 align:start position:0% nuclear weapon can be but as I noted 00:36:23.920 --> 00:36:25.710 align:start position:0% nuclear weapon can be but as I noted earlier<00:36:24.319> cryptography<00:36:24.920> is<00:36:25.040> digital<00:36:25.359> nuke 00:36:25.710 --> 00:36:25.720 align:start position:0% earlier cryptography is digital nuke 00:36:25.720 --> 00:36:27.910 align:start position:0% earlier cryptography is digital nuke proof<00:36:26.040> paint<00:36:26.640> cryptography<00:36:27.200> is<00:36:27.280> an<00:36:27.599> almost 00:36:27.910 --> 00:36:27.920 align:start position:0% proof paint cryptography is an almost 00:36:27.920 --> 00:36:29.670 align:start position:0% proof paint cryptography is an almost infinitely<00:36:28.520> powerful<00:36:29.000> defensive<00:36:29.480> or 00:36:29.670 --> 00:36:29.680 align:start position:0% infinitely powerful defensive or 00:36:29.680 --> 00:36:31.470 align:start position:0% infinitely powerful defensive or protective<00:36:30.160> technology<00:36:31.000> and<00:36:31.119> the<00:36:31.240> fact<00:36:31.359> that 00:36:31.470 --> 00:36:31.480 align:start position:0% protective technology and the fact that 00:36:31.480 --> 00:36:33.030 align:start position:0% protective technology and the fact that it's<00:36:31.599> the<00:36:31.720> digital<00:36:32.040> superconductor<00:36:32.720> is<00:36:32.920> like 00:36:33.030 --> 00:36:33.040 align:start position:0% it's the digital superconductor is like 00:36:33.040 --> 00:36:35.750 align:start position:0% it's the digital superconductor is like the<00:36:33.200> icing<00:36:33.520> on<00:36:33.720> the<00:36:34.079> cake<00:36:35.079> so<00:36:35.200> I<00:36:35.280> do<00:36:35.440> think<00:36:35.640> it's 00:36:35.750 --> 00:36:35.760 align:start position:0% the icing on the cake so I do think it's 00:36:35.760 --> 00:36:37.349 align:start position:0% the icing on the cake so I do think it's reasonable<00:36:36.160> to<00:36:36.280> consider<00:36:36.599> cryptography<00:36:37.200> a 00:36:37.349 --> 00:36:37.359 align:start position:0% reasonable to consider cryptography a 00:36:37.359 --> 00:36:40.150 align:start position:0% reasonable to consider cryptography a miracle<00:36:37.839> of<00:36:38.280> Science<00:36:39.280> and<00:36:39.560> one<00:36:39.760> reason<00:36:40.000> is 00:36:40.150 --> 00:36:40.160 align:start position:0% miracle of Science and one reason is 00:36:40.160 --> 00:36:41.589 align:start position:0% miracle of Science and one reason is because<00:36:40.400> cryptography<00:36:40.960> is<00:36:41.040> a<00:36:41.240> physical 00:36:41.589 --> 00:36:41.599 align:start position:0% because cryptography is a physical 00:36:41.599 --> 00:36:45.349 align:start position:0% because cryptography is a physical realization<00:36:42.280> of<00:36:42.440> the<00:36:42.680> potential<00:36:43.560> of 00:36:45.349 --> 00:36:45.359 align:start position:0% realization of the potential of 00:36:45.359 --> 00:36:47.750 align:start position:0% realization of the potential of mathematics<00:36:46.359> now<00:36:46.560> let's<00:36:46.839> consider<00:36:47.280> the<00:36:47.440> four 00:36:47.750 --> 00:36:47.760 align:start position:0% mathematics now let's consider the four 00:36:47.760 --> 00:36:49.230 align:start position:0% mathematics now let's consider the four fundamental<00:36:48.319> forces<00:36:48.640> of<00:36:48.800> the<00:36:48.880> physical 00:36:49.230 --> 00:36:49.240 align:start position:0% fundamental forces of the physical 00:36:49.240 --> 00:36:51.630 align:start position:0% fundamental forces of the physical Universe<00:36:50.119> we've<00:36:50.319> got<00:36:50.560> gravity<00:36:51.119> a<00:36:51.240> force<00:36:51.520> that 00:36:51.630 --> 00:36:51.640 align:start position:0% Universe we've got gravity a force that 00:36:51.640 --> 00:36:52.990 align:start position:0% Universe we've got gravity a force that was<00:36:51.760> definitely<00:36:52.040> apparent<00:36:52.319> to<00:36:52.480> humans<00:36:52.760> since 00:36:52.990 --> 00:36:53.000 align:start position:0% was definitely apparent to humans since 00:36:53.000 --> 00:36:54.829 align:start position:0% was definitely apparent to humans since well<00:36:53.200> before<00:36:53.440> we<00:36:53.560> were<00:36:53.760> humans<00:36:54.520> then<00:36:54.680> there's 00:36:54.829 --> 00:36:54.839 align:start position:0% well before we were humans then there's 00:36:54.839 --> 00:36:57.270 align:start position:0% well before we were humans then there's the<00:36:55.000> electromagnetic<00:36:55.839> force<00:36:56.359> which<00:36:56.599> was<00:36:57.160> the 00:36:57.270 --> 00:36:57.280 align:start position:0% the electromagnetic force which was the 00:36:57.280 --> 00:36:58.790 align:start position:0% the electromagnetic force which was the fact<00:36:57.680> that<00:36:57.800> was<00:36:57.880> a<00:36:57.960> force<00:36:58.240> was<00:36:58.359> not<00:36:58.560> actually 00:36:58.790 --> 00:36:58.800 align:start position:0% fact that was a force was not actually 00:36:58.800 --> 00:37:01.390 align:start position:0% fact that was a force was not actually really<00:36:59.000> clear<00:36:59.280> until<00:36:59.480> about<00:36:59.839> 200<00:37:00.160> years<00:37:00.400> ago 00:37:01.390 --> 00:37:01.400 align:start position:0% really clear until about 200 years ago 00:37:01.400 --> 00:37:03.309 align:start position:0% really clear until about 200 years ago then<00:37:01.520> we've<00:37:01.720> got<00:37:01.839> these<00:37:02.000> two<00:37:02.359> crazy<00:37:02.960> forces 00:37:03.309 --> 00:37:03.319 align:start position:0% then we've got these two crazy forces 00:37:03.319 --> 00:37:05.190 align:start position:0% then we've got these two crazy forces that<00:37:03.480> operate<00:37:03.760> at<00:37:03.960> Atomic<00:37:04.359> scales<00:37:04.839> the<00:37:04.960> weak 00:37:05.190 --> 00:37:05.200 align:start position:0% that operate at Atomic scales the weak 00:37:05.200 --> 00:37:07.470 align:start position:0% that operate at Atomic scales the weak force<00:37:05.480> and<00:37:05.680> the<00:37:05.920> strong<00:37:06.079> force<00:37:06.800> we<00:37:07.000> actually 00:37:07.470 --> 00:37:07.480 align:start position:0% force and the strong force we actually 00:37:07.480 --> 00:37:08.829 align:start position:0% force and the strong force we actually didn't<00:37:07.720> even<00:37:07.920> realize<00:37:08.200> they<00:37:08.359> existed<00:37:08.640> until 00:37:08.829 --> 00:37:08.839 align:start position:0% didn't even realize they existed until 00:37:08.839 --> 00:37:10.950 align:start position:0% didn't even realize they existed until the<00:37:08.960> 20th<00:37:09.319> century<00:37:09.920> and<00:37:10.040> we<00:37:10.119> didn't<00:37:10.440> confirm 00:37:10.950 --> 00:37:10.960 align:start position:0% the 20th century and we didn't confirm 00:37:10.960 --> 00:37:14.190 align:start position:0% the 20th century and we didn't confirm how<00:37:11.079> the<00:37:11.240> weak<00:37:11.480> Force<00:37:11.800> functions<00:37:12.280> until<00:37:12.640> like 00:37:14.190 --> 00:37:14.200 align:start position:0% how the weak Force functions until like 00:37:14.200 --> 00:37:17.710 align:start position:0% how the weak Force functions until like 1960<00:37:15.200> so<00:37:15.359> are<00:37:15.480> we<00:37:15.599> sure<00:37:15.880> that<00:37:16.000> we've<00:37:16.240> got<00:37:16.440> them 00:37:17.710 --> 00:37:17.720 align:start position:0% 1960 so are we sure that we've got them 00:37:17.720 --> 00:37:20.309 align:start position:0% 1960 so are we sure that we've got them all<00:37:18.720> there's<00:37:18.960> even<00:37:19.160> like<00:37:19.280> a<00:37:19.480> digital<00:37:20.000> strong 00:37:20.309 --> 00:37:20.319 align:start position:0% all there's even like a digital strong 00:37:20.319 --> 00:37:22.510 align:start position:0% all there's even like a digital strong force<00:37:21.079> strong<00:37:21.240> nuclear<00:37:21.640> force<00:37:21.920> parallel<00:37:22.359> here 00:37:22.510 --> 00:37:22.520 align:start position:0% force strong nuclear force parallel here 00:37:22.520 --> 00:37:24.030 align:start position:0% force strong nuclear force parallel here you<00:37:22.640> know<00:37:22.800> cryptography<00:37:23.359> holds<00:37:23.640> things 00:37:24.030 --> 00:37:24.040 align:start position:0% you know cryptography holds things 00:37:24.040 --> 00:37:25.950 align:start position:0% you know cryptography holds things together<00:37:24.640> at<00:37:24.720> a<00:37:24.880> level<00:37:25.119> that<00:37:25.319> overcomes<00:37:25.839> the 00:37:25.950 --> 00:37:25.960 align:start position:0% together at a level that overcomes the 00:37:25.960 --> 00:37:28.030 align:start position:0% together at a level that overcomes the inherent<00:37:26.440> collapse<00:37:26.880> of<00:37:27.000> Digital<00:37:27.280> Data 00:37:28.030 --> 00:37:28.040 align:start position:0% inherent collapse of Digital Data 00:37:28.040 --> 00:37:29.470 align:start position:0% inherent collapse of Digital Data kind<00:37:28.160> of<00:37:28.319> like<00:37:28.400> the<00:37:28.640> strong<00:37:28.800> force<00:37:29.079> overcomes 00:37:29.470 --> 00:37:29.480 align:start position:0% kind of like the strong force overcomes 00:37:29.480 --> 00:37:31.230 align:start position:0% kind of like the strong force overcomes the<00:37:29.640> repulsion<00:37:30.160> that<00:37:30.359> positively<00:37:30.760> charge 00:37:31.230 --> 00:37:31.240 align:start position:0% the repulsion that positively charge 00:37:31.240 --> 00:37:33.230 align:start position:0% the repulsion that positively charge protons<00:37:31.880> otherwise<00:37:32.280> would<00:37:32.480> experience<00:37:33.040> when 00:37:33.230 --> 00:37:33.240 align:start position:0% protons otherwise would experience when 00:37:33.240 --> 00:37:35.670 align:start position:0% protons otherwise would experience when packed<00:37:33.599> together<00:37:34.079> in<00:37:34.240> an<00:37:34.400> atomic<00:37:34.800> nucleus<00:37:35.480> so 00:37:35.670 --> 00:37:35.680 align:start position:0% packed together in an atomic nucleus so 00:37:35.680 --> 00:37:37.069 align:start position:0% packed together in an atomic nucleus so that's<00:37:35.800> why<00:37:35.960> I<00:37:36.079> wonder<00:37:36.319> if<00:37:36.440> it<00:37:36.560> might<00:37:36.720> be<00:37:36.839> apt 00:37:37.069 --> 00:37:37.079 align:start position:0% that's why I wonder if it might be apt 00:37:37.079 --> 00:37:38.829 align:start position:0% that's why I wonder if it might be apt to<00:37:37.200> think<00:37:37.319> of<00:37:37.480> cryptography<00:37:38.160> as<00:37:38.280> like<00:37:38.400> a<00:37:38.560> fifth 00:37:38.829 --> 00:37:38.839 align:start position:0% to think of cryptography as like a fifth 00:37:38.839 --> 00:37:40.670 align:start position:0% to think of cryptography as like a fifth fundamental<00:37:39.280> force<00:37:39.520> of<00:37:39.680> the<00:37:39.800> universe 00:37:40.670 --> 00:37:40.680 align:start position:0% fundamental force of the universe 00:37:40.680 --> 00:37:41.910 align:start position:0% fundamental force of the universe especially<00:37:41.040> a<00:37:41.160> universe<00:37:41.599> that<00:37:41.760> is 00:37:41.910 --> 00:37:41.920 align:start position:0% especially a universe that is 00:37:41.920 --> 00:37:43.710 align:start position:0% especially a universe that is increasingly<00:37:42.560> becoming<00:37:42.839> a<00:37:43.040> combination<00:37:43.560> of 00:37:43.710 --> 00:37:43.720 align:start position:0% increasingly becoming a combination of 00:37:43.720 --> 00:37:45.550 align:start position:0% increasingly becoming a combination of the<00:37:43.839> physical<00:37:44.359> and<00:37:44.560> the 00:37:45.550 --> 00:37:45.560 align:start position:0% the physical and the 00:37:45.560 --> 00:37:48.309 align:start position:0% the physical and the digital<00:37:46.560> and<00:37:46.640> so<00:37:46.800> that<00:37:46.920> takes<00:37:47.119> us<00:37:47.240> to<00:37:47.440> part<00:37:47.680> two 00:37:48.309 --> 00:37:48.319 align:start position:0% digital and so that takes us to part two 00:37:48.319 --> 00:37:50.550 align:start position:0% digital and so that takes us to part two the<00:37:48.440> super<00:37:48.839> real<00:37:49.560> and<00:37:49.800> I<00:37:50.040> I<00:37:50.160> like<00:37:50.359> this 00:37:50.550 --> 00:37:50.560 align:start position:0% the super real and I I like this 00:37:50.560 --> 00:37:52.510 align:start position:0% the super real and I I like this particular<00:37:51.000> definition<00:37:51.680> of<00:37:51.760> the<00:37:51.880> word<00:37:52.200> marked 00:37:52.510 --> 00:37:52.520 align:start position:0% particular definition of the word marked 00:37:52.520 --> 00:37:54.630 align:start position:0% particular definition of the word marked by<00:37:52.760> extraordinary 00:37:54.630 --> 00:37:54.640 align:start position:0% by extraordinary 00:37:54.640 --> 00:37:56.990 align:start position:0% by extraordinary vividness<00:37:55.640> so<00:37:55.800> if<00:37:55.960> cryptography<00:37:56.520> is<00:37:56.599> a<00:37:56.760> force 00:37:56.990 --> 00:37:57.000 align:start position:0% vividness so if cryptography is a force 00:37:57.000 --> 00:37:57.950 align:start position:0% vividness so if cryptography is a force of<00:37:57.160> nature 00:37:57.950 --> 00:37:57.960 align:start position:0% of nature 00:37:57.960 --> 00:37:59.670 align:start position:0% of nature then<00:37:58.280> actually<00:37:58.680> utilize<00:37:59.240> that<00:37:59.400> Force 00:37:59.670 --> 00:37:59.680 align:start position:0% then actually utilize that Force 00:37:59.680 --> 00:38:01.750 align:start position:0% then actually utilize that Force requires<00:38:00.160> implementation<00:38:01.119> our<00:38:01.280> day-to-day 00:38:01.750 --> 00:38:01.760 align:start position:0% requires implementation our day-to-day 00:38:01.760 --> 00:38:03.550 align:start position:0% requires implementation our day-to-day us<00:38:02.160> usage<00:38:02.440> of<00:38:02.560> electricity<00:38:03.000> isn't<00:38:03.240> just<00:38:03.359> some 00:38:03.550 --> 00:38:03.560 align:start position:0% us usage of electricity isn't just some 00:38:03.560 --> 00:38:04.950 align:start position:0% us usage of electricity isn't just some like<00:38:03.839> General<00:38:04.319> usage<00:38:04.720> of<00:38:04.839> the 00:38:04.950 --> 00:38:04.960 align:start position:0% like General usage of the 00:38:04.960 --> 00:38:06.950 align:start position:0% like General usage of the electromagnetic<00:38:05.839> force<00:38:06.400> you<00:38:06.480> know<00:38:06.640> there's 00:38:06.950 --> 00:38:06.960 align:start position:0% electromagnetic force you know there's 00:38:06.960 --> 00:38:09.550 align:start position:0% electromagnetic force you know there's voltage<00:38:07.640> there's<00:38:08.440> how<00:38:08.839> what<00:38:09.160> decisions 00:38:09.550 --> 00:38:09.560 align:start position:0% voltage there's how what decisions 00:38:09.560 --> 00:38:11.270 align:start position:0% voltage there's how what decisions around<00:38:09.880> batteries<00:38:10.359> alternating<00:38:10.920> versus 00:38:11.270 --> 00:38:11.280 align:start position:0% around batteries alternating versus 00:38:11.280 --> 00:38:12.990 align:start position:0% around batteries alternating versus direct<00:38:11.560> current<00:38:11.920> and<00:38:12.040> so<00:38:12.280> much<00:38:12.480> more<00:38:12.880> there 00:38:12.990 --> 00:38:13.000 align:start position:0% direct current and so much more there 00:38:13.000 --> 00:38:14.990 align:start position:0% direct current and so much more there are<00:38:13.160> a<00:38:13.280> lot<00:38:13.480> of<00:38:13.720> specific<00:38:14.160> things<00:38:14.680> so<00:38:14.800> when<00:38:14.920> I 00:38:14.990 --> 00:38:15.000 align:start position:0% are a lot of specific things so when I 00:38:15.000 --> 00:38:17.150 align:start position:0% are a lot of specific things so when I say<00:38:15.200> Cryptor<00:38:15.960> here<00:38:16.160> what<00:38:16.280> I'm<00:38:16.440> gesturing<00:38:16.960> at 00:38:17.150 --> 00:38:17.160 align:start position:0% say Cryptor here what I'm gesturing at 00:38:17.160 --> 00:38:19.430 align:start position:0% say Cryptor here what I'm gesturing at is<00:38:17.319> the<00:38:17.520> specific<00:38:17.960> form<00:38:18.680> that<00:38:18.880> of<00:38:19.000> things<00:38:19.240> that 00:38:19.430 --> 00:38:19.440 align:start position:0% is the specific form that of things that 00:38:19.440 --> 00:38:23.510 align:start position:0% is the specific form that of things that actually<00:38:19.760> harnesses<00:38:20.400> the<00:38:20.680> cryptographic 00:38:23.510 --> 00:38:23.520 align:start position:0% actually harnesses the cryptographic 00:38:23.520 --> 00:38:26.109 align:start position:0% actually harnesses the cryptographic force<00:38:24.520> this<00:38:24.640> is<00:38:24.839> one<00:38:25.079> reason<00:38:25.520> I<00:38:25.720> kind<00:38:25.839> of<00:38:26.000> like 00:38:26.109 --> 00:38:26.119 align:start position:0% force this is one reason I kind of like 00:38:26.119 --> 00:38:28.150 align:start position:0% force this is one reason I kind of like to<00:38:26.200> think<00:38:26.319> of<00:38:26.480> cryptography<00:38:27.079> as<00:38:27.160> a<00:38:27.480> digal<00:38:27.800> duel 00:38:28.150 --> 00:38:28.160 align:start position:0% to think of cryptography as a digal duel 00:38:28.160 --> 00:38:30.309 align:start position:0% to think of cryptography as a digal duel to<00:38:28.359> physical<00:38:28.720> reality<00:38:29.280> electricity<00:38:30.160> the 00:38:30.309 --> 00:38:30.319 align:start position:0% to physical reality electricity the 00:38:30.319 --> 00:38:31.750 align:start position:0% to physical reality electricity the transition<00:38:30.800> we're<00:38:31.000> undergoing<00:38:31.520> can<00:38:31.599> be 00:38:31.750 --> 00:38:31.760 align:start position:0% transition we're undergoing can be 00:38:31.760 --> 00:38:33.190 align:start position:0% transition we're undergoing can be likened<00:38:32.040> to<00:38:32.200> the<00:38:32.319> transition<00:38:32.760> from<00:38:32.880> a<00:38:33.000> world 00:38:33.190 --> 00:38:33.200 align:start position:0% likened to the transition from a world 00:38:33.200 --> 00:38:34.990 align:start position:0% likened to the transition from a world that<00:38:33.319> only<00:38:33.480> knew<00:38:33.800> fire<00:38:34.280> to<00:38:34.440> a<00:38:34.560> world<00:38:34.800> where 00:38:34.990 --> 00:38:35.000 align:start position:0% that only knew fire to a world where 00:38:35.000 --> 00:38:37.109 align:start position:0% that only knew fire to a world where electricity<00:38:35.560> is<00:38:35.800> everywhere<00:38:36.800> back<00:38:36.960> when 00:38:37.109 --> 00:38:37.119 align:start position:0% electricity is everywhere back when 00:38:37.119 --> 00:38:38.750 align:start position:0% electricity is everywhere back when people<00:38:37.319> only<00:38:37.480> knew<00:38:37.800> fire<00:38:38.160> if<00:38:38.280> someone<00:38:38.560> told 00:38:38.750 --> 00:38:38.760 align:start position:0% people only knew fire if someone told 00:38:38.760 --> 00:38:40.270 align:start position:0% people only knew fire if someone told you<00:38:38.880> about<00:38:39.119> electricity<00:38:39.880> that<00:38:40.000> we<00:38:40.119> could 00:38:40.270 --> 00:38:40.280 align:start position:0% you about electricity that we could 00:38:40.280 --> 00:38:42.270 align:start position:0% you about electricity that we could somehow<00:38:40.599> harness<00:38:41.079> lightning<00:38:41.920> you<00:38:42.079> might 00:38:42.270 --> 00:38:42.280 align:start position:0% somehow harness lightning you might 00:38:42.280 --> 00:38:44.870 align:start position:0% somehow harness lightning you might imagine<00:38:42.760> better<00:38:43.040> lights<00:38:43.839> better<00:38:44.160> heat 00:38:44.870 --> 00:38:44.880 align:start position:0% imagine better lights better heat 00:38:44.880 --> 00:38:46.510 align:start position:0% imagine better lights better heat perhaps<00:38:45.240> better<00:38:45.520> cooking<00:38:46.000> ironically 00:38:46.510 --> 00:38:46.520 align:start position:0% perhaps better cooking ironically 00:38:46.520 --> 00:38:47.990 align:start position:0% perhaps better cooking ironically because<00:38:46.720> I<00:38:46.880> fire<00:38:47.079> is<00:38:47.240> actually<00:38:47.480> better<00:38:47.800> than 00:38:47.990 --> 00:38:48.000 align:start position:0% because I fire is actually better than 00:38:48.000 --> 00:38:49.589 align:start position:0% because I fire is actually better than cooking<00:38:48.640> for<00:38:48.880> cooking<00:38:49.160> in<00:38:49.240> a<00:38:49.359> lot<00:38:49.480> of 00:38:49.589 --> 00:38:49.599 align:start position:0% cooking for cooking in a lot of 00:38:49.599 --> 00:38:51.790 align:start position:0% cooking for cooking in a lot of situations<00:38:50.599> you<00:38:50.720> can<00:38:50.880> imagine<00:38:51.160> lighting<00:38:51.520> up<00:38:51.640> a 00:38:51.790 --> 00:38:51.800 align:start position:0% situations you can imagine lighting up a 00:38:51.800 --> 00:38:54.309 align:start position:0% situations you can imagine lighting up a city<00:38:52.079> and<00:38:52.280> heating<00:38:52.680> a<00:38:52.920> city<00:38:53.599> but<00:38:53.760> you<00:38:53.880> wouldn't 00:38:54.309 --> 00:38:54.319 align:start position:0% city and heating a city but you wouldn't 00:38:54.319 --> 00:38:57.150 align:start position:0% city and heating a city but you wouldn't really<00:38:54.640> imagine<00:38:55.400> powering<00:38:56.000> a<00:38:56.280> city<00:38:57.040> you 00:38:57.150 --> 00:38:57.160 align:start position:0% really imagine powering a city you 00:38:57.160 --> 00:39:00.270 align:start position:0% really imagine powering a city you wouldn't<00:38:57.800> imagine<00:38:58.319> computers<00:38:59.280> the<00:38:59.520> Internet 00:39:00.270 --> 00:39:00.280 align:start position:0% wouldn't imagine computers the Internet 00:39:00.280 --> 00:39:01.589 align:start position:0% wouldn't imagine computers the Internet or<00:39:00.440> that<00:39:00.599> electricity<00:39:01.160> actually<00:39:01.359> kind<00:39:01.480> of 00:39:01.589 --> 00:39:01.599 align:start position:0% or that electricity actually kind of 00:39:01.599 --> 00:39:03.750 align:start position:0% or that electricity actually kind of runs<00:39:01.920> even<00:39:02.119> through<00:39:02.280> our<00:39:02.599> brains<00:39:03.599> you 00:39:03.750 --> 00:39:03.760 align:start position:0% runs even through our brains you 00:39:03.760 --> 00:39:05.230 align:start position:0% runs even through our brains you wouldn't<00:39:04.400> you<00:39:04.599> definitely<00:39:04.960> would<00:39:05.079> not 00:39:05.230 --> 00:39:05.240 align:start position:0% wouldn't you definitely would not 00:39:05.240 --> 00:39:07.069 align:start position:0% wouldn't you definitely would not imagine<00:39:05.720> artificial<00:39:06.240> intelligence<00:39:06.800> and<00:39:06.920> you 00:39:07.069 --> 00:39:07.079 align:start position:0% imagine artificial intelligence and you 00:39:07.079 --> 00:39:09.510 align:start position:0% imagine artificial intelligence and you definitely<00:39:07.480> wouldn't<00:39:07.839> imagine 00:39:09.510 --> 00:39:09.520 align:start position:0% definitely wouldn't imagine 00:39:09.520 --> 00:39:11.990 align:start position:0% definitely wouldn't imagine cryptography<00:39:10.520> so<00:39:10.640> in<00:39:10.760> the<00:39:10.880> future<00:39:11.599> digital 00:39:11.990 --> 00:39:12.000 align:start position:0% cryptography so in the future digital 00:39:12.000 --> 00:39:14.030 align:start position:0% cryptography so in the future digital stuff<00:39:12.400> such<00:39:12.560> as<00:39:12.720> data<00:39:13.040> computation 00:39:14.030 --> 00:39:14.040 align:start position:0% stuff such as data computation 00:39:14.040 --> 00:39:16.589 align:start position:0% stuff such as data computation information<00:39:14.520> transmission<00:39:15.520> that<00:39:15.680> makes<00:39:16.200> use 00:39:16.589 --> 00:39:16.599 align:start position:0% information transmission that makes use 00:39:16.599 --> 00:39:18.030 align:start position:0% information transmission that makes use of<00:39:17.000> programmable<00:39:17.480> and<00:39:17.599> other<00:39:17.720> future 00:39:18.030 --> 00:39:18.040 align:start position:0% of programmable and other future 00:39:18.040 --> 00:39:20.270 align:start position:0% of programmable and other future cryptography<00:39:18.920> will<00:39:19.119> feel<00:39:19.400> like<00:39:19.599> electrically 00:39:20.270 --> 00:39:20.280 align:start position:0% cryptography will feel like electrically 00:39:20.280 --> 00:39:22.230 align:start position:0% cryptography will feel like electrically powered<00:39:20.839> objects<00:39:21.240> in<00:39:21.480> comparison<00:39:21.839> to<00:39:22.000> what<00:39:22.119> we 00:39:22.230 --> 00:39:22.240 align:start position:0% powered objects in comparison to what we 00:39:22.240 --> 00:39:24.270 align:start position:0% powered objects in comparison to what we have<00:39:22.400> across<00:39:22.680> the<00:39:22.839> web<00:39:23.040> today<00:39:23.800> Computing<00:39:24.160> that 00:39:24.270 --> 00:39:24.280 align:start position:0% have across the web today Computing that 00:39:24.280 --> 00:39:26.430 align:start position:0% have across the web today Computing that is<00:39:24.400> cryptographically<00:39:25.240> charged<00:39:25.880> or<00:39:26.040> maybe 00:39:26.430 --> 00:39:26.440 align:start position:0% is cryptographically charged or maybe 00:39:26.440 --> 00:39:29.190 align:start position:0% is cryptographically charged or maybe Enchanted<00:39:27.480> is<00:39:27.720> far<00:39:28.040> from<00:39:28.240> what<00:39:28.400> we<00:39:28.640> currently 00:39:29.190 --> 00:39:29.200 align:start position:0% Enchanted is far from what we currently 00:39:29.200 --> 00:39:32.309 align:start position:0% Enchanted is far from what we currently think<00:39:29.480> of<00:39:29.920> as<00:39:30.319> Computing<00:39:31.319> same<00:39:31.560> with<00:39:31.800> data 00:39:32.309 --> 00:39:32.319 align:start position:0% think of as Computing same with data 00:39:32.319 --> 00:39:35.069 align:start position:0% think of as Computing same with data that<00:39:32.440> is<00:39:32.599> cryptographically<00:39:33.520> Enchanted<00:39:34.520> and 00:39:35.069 --> 00:39:35.079 align:start position:0% that is cryptographically Enchanted and 00:39:35.079 --> 00:39:37.630 align:start position:0% that is cryptographically Enchanted and Beyond<00:39:36.079> now<00:39:36.400> why<00:39:36.599> is<00:39:36.920> this<00:39:37.240> even<00:39:37.440> more 00:39:37.630 --> 00:39:37.640 align:start position:0% Beyond now why is this even more 00:39:37.640 --> 00:39:39.670 align:start position:0% Beyond now why is this even more important<00:39:38.000> than<00:39:38.119> it<00:39:38.240> might<00:39:38.400> seem<00:39:38.640> at<00:39:38.760> first 00:39:39.670 --> 00:39:39.680 align:start position:0% important than it might seem at first 00:39:39.680 --> 00:39:42.349 align:start position:0% important than it might seem at first blush<00:39:40.680> because<00:39:41.240> the<00:39:41.400> tech<00:39:41.640> industry<00:39:42.079> as<00:39:42.160> of 00:39:42.349 --> 00:39:42.359 align:start position:0% blush because the tech industry as of 00:39:42.359 --> 00:39:44.390 align:start position:0% blush because the tech industry as of now<00:39:42.560> has<00:39:42.760> philosophically<00:39:43.440> flattened<00:39:44.240> in 00:39:44.390 --> 00:39:44.400 align:start position:0% now has philosophically flattened in 00:39:44.400 --> 00:39:46.190 align:start position:0% now has philosophically flattened in fact<00:39:44.560> we<00:39:44.640> can<00:39:44.760> see<00:39:45.119> remnants<00:39:45.720> of<00:39:45.839> the<00:39:45.960> higher 00:39:46.190 --> 00:39:46.200 align:start position:0% fact we can see remnants of the higher 00:39:46.200 --> 00:39:48.150 align:start position:0% fact we can see remnants of the higher dimensional<00:39:46.680> space<00:39:46.960> it<00:39:47.160> it<00:39:47.280> fell<00:39:47.520> from<00:39:47.960> if<00:39:48.040> you 00:39:48.150 --> 00:39:48.160 align:start position:0% dimensional space it it fell from if you 00:39:48.160 --> 00:39:50.109 align:start position:0% dimensional space it it fell from if you look<00:39:48.240> at<00:39:48.359> any<00:39:48.520> Tech<00:39:48.760> startups<00:39:49.319> pitch<00:39:49.960> they 00:39:50.109 --> 00:39:50.119 align:start position:0% look at any Tech startups pitch they 00:39:50.119 --> 00:39:51.750 align:start position:0% look at any Tech startups pitch they pretty<00:39:50.319> much<00:39:50.520> all<00:39:50.680> still<00:39:50.920> contain<00:39:51.240> a<00:39:51.400> mission 00:39:51.750 --> 00:39:51.760 align:start position:0% pretty much all still contain a mission 00:39:51.760 --> 00:39:53.309 align:start position:0% pretty much all still contain a mission and<00:39:51.839> the<00:39:51.960> mission<00:39:52.200> is<00:39:52.359> never<00:39:52.599> build<00:39:52.920> the<00:39:53.079> most 00:39:53.309 --> 00:39:53.319 align:start position:0% and the mission is never build the most 00:39:53.319 --> 00:39:55.230 align:start position:0% and the mission is never build the most valuable<00:39:53.839> company<00:39:54.560> now<00:39:54.680> if<00:39:54.760> you've<00:39:54.920> ever<00:39:55.040> seen 00:39:55.230 --> 00:39:55.240 align:start position:0% valuable company now if you've ever seen 00:39:55.240 --> 00:39:56.750 align:start position:0% valuable company now if you've ever seen a<00:39:55.359> hedge<00:39:55.640> fund<00:39:55.960> like<00:39:56.079> a<00:39:56.160> new<00:39:56.319> hedge<00:39:56.520> funds 00:39:56.750 --> 00:39:56.760 align:start position:0% a hedge fund like a new hedge funds 00:39:56.760 --> 00:39:58.390 align:start position:0% a hedge fund like a new hedge funds pitch<00:39:57.040> deck<00:39:57.480> they<00:39:57.640> never<00:39:57.880> have<00:39:58.000> a<00:39:58.079> mission 00:39:58.390 --> 00:39:58.400 align:start position:0% pitch deck they never have a mission 00:39:58.400 --> 00:39:59.750 align:start position:0% pitch deck they never have a mission it's<00:39:58.560> all<00:39:58.760> business<00:39:59.119> it's<00:39:59.280> how<00:39:59.400> they're<00:39:59.560> going 00:39:59.750 --> 00:39:59.760 align:start position:0% it's all business it's how they're going 00:39:59.760 --> 00:40:01.910 align:start position:0% it's all business it's how they're going to<00:39:59.880> make<00:40:00.079> the<00:40:00.440> most<00:40:00.680> money<00:40:01.319> the<00:40:01.480> whole<00:40:01.680> tech 00:40:01.910 --> 00:40:01.920 align:start position:0% to make the most money the whole tech 00:40:01.920 --> 00:40:03.390 align:start position:0% to make the most money the whole tech company<00:40:02.240> Mission<00:40:02.599> thing<00:40:02.760> at<00:40:02.920> this<00:40:03.040> point<00:40:03.200> is 00:40:03.390 --> 00:40:03.400 align:start position:0% company Mission thing at this point is 00:40:03.400 --> 00:40:04.990 align:start position:0% company Mission thing at this point is kind<00:40:03.480> of<00:40:03.599> a<00:40:03.720> Remnant<00:40:04.119> from<00:40:04.280> a<00:40:04.400> philosophically 00:40:04.990 --> 00:40:05.000 align:start position:0% kind of a Remnant from a philosophically 00:40:05.000 --> 00:40:07.790 align:start position:0% kind of a Remnant from a philosophically higher<00:40:05.359> dimensional<00:40:05.839> era<00:40:06.400> of<00:40:06.599> Silicon 00:40:07.790 --> 00:40:07.800 align:start position:0% higher dimensional era of Silicon 00:40:07.800 --> 00:40:09.870 align:start position:0% higher dimensional era of Silicon Valley<00:40:08.800> and<00:40:08.920> at<00:40:09.040> the<00:40:09.119> same<00:40:09.319> time<00:40:09.480> and<00:40:09.640> not 00:40:09.870 --> 00:40:09.880 align:start position:0% Valley and at the same time and not 00:40:09.880 --> 00:40:11.990 align:start position:0% Valley and at the same time and not coincidentally<00:40:10.800> while<00:40:11.000> computer<00:40:11.400> technology 00:40:11.990 --> 00:40:12.000 align:start position:0% coincidentally while computer technology 00:40:12.000 --> 00:40:13.630 align:start position:0% coincidentally while computer technology has<00:40:12.119> improved<00:40:12.480> dramatically<00:40:13.280> it<00:40:13.440> is 00:40:13.630 --> 00:40:13.640 align:start position:0% has improved dramatically it is 00:40:13.640 --> 00:40:15.349 align:start position:0% has improved dramatically it is regressed<00:40:14.319> from<00:40:14.480> the<00:40:14.599> standpoint<00:40:14.960> of<00:40:15.079> how<00:40:15.240> it 00:40:15.349 --> 00:40:15.359 align:start position:0% regressed from the standpoint of how it 00:40:15.359 --> 00:40:17.230 align:start position:0% regressed from the standpoint of how it feels<00:40:16.240> counterintuitive 00:40:17.230 --> 00:40:17.240 align:start position:0% feels counterintuitive 00:40:17.240 --> 00:40:19.069 align:start position:0% feels counterintuitive counterintuitively<00:40:18.079> using<00:40:18.359> computers<00:40:18.800> going 00:40:19.069 --> 00:40:19.079 align:start position:0% counterintuitively using computers going 00:40:19.079 --> 00:40:21.069 align:start position:0% counterintuitively using computers going back<00:40:19.200> to<00:40:19.359> like<00:40:19.520> Doom<00:40:19.839> or<00:40:20.079> civilization<00:40:20.640> 1<00:40:20.920> or 00:40:21.069 --> 00:40:21.079 align:start position:0% back to like Doom or civilization 1 or 00:40:21.079 --> 00:40:24.150 align:start position:0% back to like Doom or civilization 1 or the<00:40:21.200> well<00:40:21.599> or<00:40:21.839> IRC<00:40:22.480> or<00:40:22.640> aim<00:40:23.400> or<00:40:23.599> text-based 00:40:24.150 --> 00:40:24.160 align:start position:0% the well or IRC or aim or text-based 00:40:24.160 --> 00:40:26.430 align:start position:0% the well or IRC or aim or text-based multi-user<00:40:24.680> dungeons<00:40:25.640> in<00:40:25.800> many<00:40:26.000> ways<00:40:26.200> felt 00:40:26.430 --> 00:40:26.440 align:start position:0% multi-user dungeons in many ways felt 00:40:26.440 --> 00:40:28.470 align:start position:0% multi-user dungeons in many ways felt more<00:40:26.680> expansive<00:40:27.440> enriching<00:40:28.079> not<00:40:28.240> that<00:40:28.359> things 00:40:28.470 --> 00:40:28.480 align:start position:0% more expansive enriching not that things 00:40:28.480 --> 00:40:30.069 align:start position:0% more expansive enriching not that things were<00:40:28.680> anywhere<00:40:29.000> near<00:40:29.319> perfect<00:40:29.720> back<00:40:29.880> then 00:40:30.069 --> 00:40:30.079 align:start position:0% were anywhere near perfect back then 00:40:30.079 --> 00:40:31.870 align:start position:0% were anywhere near perfect back then don't<00:40:30.280> get<00:40:30.359> me<00:40:30.599> wrong<00:40:31.119> but<00:40:31.240> there<00:40:31.359> was<00:40:31.520> a<00:40:31.640> hard 00:40:31.870 --> 00:40:31.880 align:start position:0% don't get me wrong but there was a hard 00:40:31.880 --> 00:40:34.109 align:start position:0% don't get me wrong but there was a hard to<00:40:32.079> quantify<00:40:32.640> feeling<00:40:32.920> of<00:40:33.119> moeness<00:40:34.000> that 00:40:34.109 --> 00:40:34.119 align:start position:0% to quantify feeling of moeness that 00:40:34.119 --> 00:40:35.910 align:start position:0% to quantify feeling of moeness that feels<00:40:34.480> so<00:40:34.839> different<00:40:35.280> than<00:40:35.440> how<00:40:35.560> the<00:40:35.720> web 00:40:35.910 --> 00:40:35.920 align:start position:0% feels so different than how the web 00:40:35.920 --> 00:40:38.270 align:start position:0% feels so different than how the web feels<00:40:36.280> now<00:40:36.800> it's<00:40:37.160> fascinating<00:40:38.000> how 00:40:38.270 --> 00:40:38.280 align:start position:0% feels now it's fascinating how 00:40:38.280 --> 00:40:40.270 align:start position:0% feels now it's fascinating how differently<00:40:38.760> and<00:40:38.920> in<00:40:39.079> so<00:40:39.280> many<00:40:39.640> in<00:40:39.760> some<00:40:39.960> ways 00:40:40.270 --> 00:40:40.280 align:start position:0% differently and in so many in some ways 00:40:40.280 --> 00:40:42.470 align:start position:0% differently and in so many in some ways better<00:40:40.920> I<00:40:41.000> felt<00:40:41.240> using<00:40:41.480> a<00:40:41.599> dialup<00:40:42.000> modem<00:40:42.319> with 00:40:42.470 --> 00:40:42.480 align:start position:0% better I felt using a dialup modem with 00:40:42.480 --> 00:40:44.589 align:start position:0% better I felt using a dialup modem with terrible<00:40:42.800> bandwidth<00:40:43.200> and<00:40:43.359> latency<00:40:44.119> than<00:40:44.280> I<00:40:44.400> do 00:40:44.589 --> 00:40:44.599 align:start position:0% terrible bandwidth and latency than I do 00:40:44.599 --> 00:40:48.109 align:start position:0% terrible bandwidth and latency than I do now<00:40:44.800> on<00:40:44.960> my<00:40:45.160> 5G<00:40:45.720> pocket<00:40:46.119> superc<00:40:47.000> computer<00:40:48.000> now 00:40:48.109 --> 00:40:48.119 align:start position:0% now on my 5G pocket superc computer now 00:40:48.119 --> 00:40:50.109 align:start position:0% now on my 5G pocket superc computer now a<00:40:48.280> common<00:40:48.560> response<00:40:48.839> to<00:40:49.040> this<00:40:49.440> is<00:40:49.640> technology 00:40:50.109 --> 00:40:50.119 align:start position:0% a common response to this is technology 00:40:50.119 --> 00:40:52.589 align:start position:0% a common response to this is technology is<00:40:50.359> bad<00:40:50.560> and<00:40:50.680> we<00:40:50.800> need<00:40:51.000> less<00:40:51.280> of<00:40:51.480> it<00:40:52.240> I'm<00:40:52.400> open 00:40:52.589 --> 00:40:52.599 align:start position:0% is bad and we need less of it I'm open 00:40:52.599 --> 00:40:53.950 align:start position:0% is bad and we need less of it I'm open to<00:40:52.760> that<00:40:52.960> perspective<00:40:53.400> but<00:40:53.520> I<00:40:53.599> don't<00:40:53.760> think<00:40:53.880> it 00:40:53.950 --> 00:40:53.960 align:start position:0% to that perspective but I don't think it 00:40:53.960 --> 00:40:55.990 align:start position:0% to that perspective but I don't think it should<00:40:54.119> be<00:40:54.240> a<00:40:54.359> totalizing<00:40:54.960> one<00:40:55.400> we've<00:40:55.599> got<00:40:55.680> to 00:40:55.990 --> 00:40:56.000 align:start position:0% should be a totalizing one we've got to 00:40:56.000 --> 00:40:57.870 align:start position:0% should be a totalizing one we've got to also<00:40:56.319> explore<00:40:56.680> how<00:40:56.800> the<00:40:56.960> digital<00:40:57.480> can<00:40:57.720> return 00:40:57.870 --> 00:40:57.880 align:start position:0% also explore how the digital can return 00:40:57.880 --> 00:40:59.790 align:start position:0% also explore how the digital can return to<00:40:58.000> being<00:40:58.200> an<00:40:58.359> expansive<00:40:58.960> and<00:40:59.119> enriching 00:40:59.790 --> 00:40:59.800 align:start position:0% to being an expansive and enriching 00:40:59.800 --> 00:41:01.710 align:start position:0% to being an expansive and enriching experience<00:41:00.680> we've<00:41:00.880> gone<00:41:01.119> from<00:41:01.240> it<00:41:01.400> being 00:41:01.710 --> 00:41:01.720 align:start position:0% experience we've gone from it being 00:41:01.720 --> 00:41:04.630 align:start position:0% experience we've gone from it being symbiotic<00:41:02.480> to<00:41:02.720> parasitic<00:41:03.680> how<00:41:03.800> do<00:41:03.920> we<00:41:04.119> go<00:41:04.359> back 00:41:04.630 --> 00:41:04.640 align:start position:0% symbiotic to parasitic how do we go back 00:41:04.640 --> 00:41:06.870 align:start position:0% symbiotic to parasitic how do we go back to<00:41:04.760> being<00:41:05.040> symbiotic<00:41:06.040> that's<00:41:06.200> the<00:41:06.359> real<00:41:06.640> game 00:41:06.870 --> 00:41:06.880 align:start position:0% to being symbiotic that's the real game 00:41:06.880 --> 00:41:08.630 align:start position:0% to being symbiotic that's the real game and<00:41:07.000> the<00:41:07.079> future<00:41:07.319> of<00:41:07.480> cryptography<00:41:08.240> plays<00:41:08.440> a 00:41:08.630 --> 00:41:08.640 align:start position:0% and the future of cryptography plays a 00:41:08.640 --> 00:41:11.030 align:start position:0% and the future of cryptography plays a vital<00:41:09.480> necessary<00:41:10.160> though<00:41:10.319> certainly<00:41:10.720> not 00:41:11.030 --> 00:41:11.040 align:start position:0% vital necessary though certainly not 00:41:11.040 --> 00:41:13.510 align:start position:0% vital necessary though certainly not sufficient<00:41:11.920> role<00:41:12.359> in<00:41:12.599> this<00:41:13.000> and<00:41:13.119> it's<00:41:13.359> why 00:41:13.510 --> 00:41:13.520 align:start position:0% sufficient role in this and it's why 00:41:13.520 --> 00:41:14.870 align:start position:0% sufficient role in this and it's why looking<00:41:13.720> at<00:41:13.839> cryptography<00:41:14.400> strictly<00:41:14.760> through 00:41:14.870 --> 00:41:14.880 align:start position:0% looking at cryptography strictly through 00:41:14.880 --> 00:41:17.030 align:start position:0% looking at cryptography strictly through the<00:41:15.000> lens<00:41:15.280> of<00:41:15.440> what<00:41:15.560> it<00:41:15.680> can<00:41:15.880> technically<00:41:16.400> do 00:41:17.030 --> 00:41:17.040 align:start position:0% the lens of what it can technically do 00:41:17.040 --> 00:41:18.150 align:start position:0% the lens of what it can technically do is 00:41:18.150 --> 00:41:18.160 align:start position:0% is 00:41:18.160 --> 00:41:20.550 align:start position:0% is incomplete<00:41:19.160> instead<00:41:19.760> or<00:41:19.920> in<00:41:20.079> addition<00:41:20.480> I 00:41:20.550 --> 00:41:20.560 align:start position:0% incomplete instead or in addition I 00:41:20.560 --> 00:41:22.990 align:start position:0% incomplete instead or in addition I think<00:41:20.680> we<00:41:20.800> need<00:41:20.960> lenses<00:41:21.480> such<00:41:21.640> as<00:41:21.880> this<00:41:22.760> no<00:41:22.839> one 00:41:22.990 --> 00:41:23.000 align:start position:0% think we need lenses such as this no one 00:41:23.000 --> 00:41:24.829 align:start position:0% think we need lenses such as this no one today<00:41:23.280> thinks<00:41:23.480> of<00:41:23.640> cryptography<00:41:24.200> in<00:41:24.319> terms<00:41:24.520> of 00:41:24.829 --> 00:41:24.839 align:start position:0% today thinks of cryptography in terms of 00:41:24.839 --> 00:41:26.990 align:start position:0% today thinks of cryptography in terms of nourishment<00:41:25.839> um<00:41:25.960> it<00:41:26.040> might<00:41:26.200> sound<00:41:26.480> crazy<00:41:26.839> but 00:41:26.990 --> 00:41:27.000 align:start position:0% nourishment um it might sound crazy but 00:41:27.000 --> 00:41:29.109 align:start position:0% nourishment um it might sound crazy but I<00:41:27.079> think<00:41:27.440> we<00:41:27.560> not<00:41:27.680> only<00:41:27.960> can<00:41:28.160> but<00:41:28.359> perhaps<00:41:28.800> must 00:41:29.109 --> 00:41:29.119 align:start position:0% I think we not only can but perhaps must 00:41:29.119 --> 00:41:31.230 align:start position:0% I think we not only can but perhaps must think<00:41:29.280> of<00:41:29.400> it<00:41:29.640> in<00:41:29.839> these<00:41:30.040> terms<00:41:30.680> because<00:41:30.960> only 00:41:31.230 --> 00:41:31.240 align:start position:0% think of it in these terms because only 00:41:31.240 --> 00:41:32.829 align:start position:0% think of it in these terms because only then<00:41:31.400> can<00:41:31.560> we<00:41:31.720> potentially<00:41:32.400> discover<00:41:32.640> or 00:41:32.829 --> 00:41:32.839 align:start position:0% then can we potentially discover or 00:41:32.839 --> 00:41:34.910 align:start position:0% then can we potentially discover or realize<00:41:33.240> that<00:41:33.359> it's<00:41:33.680> actually<00:41:33.920> a<00:41:34.119> valid<00:41:34.520> way 00:41:34.910 --> 00:41:34.920 align:start position:0% realize that it's actually a valid way 00:41:34.920 --> 00:41:36.670 align:start position:0% realize that it's actually a valid way to<00:41:35.079> think<00:41:35.359> about<00:41:35.560> it<00:41:35.839> we<00:41:35.960> might<00:41:36.119> even<00:41:36.319> find<00:41:36.480> out 00:41:36.670 --> 00:41:36.680 align:start position:0% to think about it we might even find out 00:41:36.680 --> 00:41:38.950 align:start position:0% to think about it we might even find out eventually<00:41:37.040> it's<00:41:37.240> the<00:41:37.400> only<00:41:37.839> natural<00:41:38.319> way<00:41:38.760> to 00:41:38.950 --> 00:41:38.960 align:start position:0% eventually it's the only natural way to 00:41:38.960 --> 00:41:40.710 align:start position:0% eventually it's the only natural way to think<00:41:39.160> about<00:41:39.359> it<00:41:39.720> and<00:41:39.960> as<00:41:40.040> for<00:41:40.240> enrichment 00:41:40.710 --> 00:41:40.720 align:start position:0% think about it and as for enrichment 00:41:40.720 --> 00:41:42.390 align:start position:0% think about it and as for enrichment this<00:41:40.839> is<00:41:40.920> a<00:41:41.040> cryptocurrency<00:41:41.720> conference<00:41:42.160> so<00:41:42.319> I 00:41:42.390 --> 00:41:42.400 align:start position:0% this is a cryptocurrency conference so I 00:41:42.400 --> 00:41:44.349 align:start position:0% this is a cryptocurrency conference so I want<00:41:42.480> to<00:41:42.640> emphasize<00:41:43.040> I'm<00:41:43.280> saying<00:41:43.520> enrich<00:41:44.240> you 00:41:44.349 --> 00:41:44.359 align:start position:0% want to emphasize I'm saying enrich you 00:41:44.359 --> 00:41:46.030 align:start position:0% want to emphasize I'm saying enrich you know<00:41:44.520> kind<00:41:44.599> of<00:41:44.760> like<00:41:44.880> the<00:41:45.079> soil<00:41:45.480> got<00:41:45.640> enriched 00:41:46.030 --> 00:41:46.040 align:start position:0% know kind of like the soil got enriched 00:41:46.040 --> 00:41:47.430 align:start position:0% know kind of like the soil got enriched and<00:41:46.160> we<00:41:46.240> were<00:41:46.359> able<00:41:46.520> to<00:41:46.640> support<00:41:47.000> much<00:41:47.200> more 00:41:47.430 --> 00:41:47.440 align:start position:0% and we were able to support much more 00:41:47.440 --> 00:41:50.510 align:start position:0% and we were able to support much more people<00:41:47.680> on<00:41:47.839> Earth<00:41:48.480> not<00:41:48.720> the<00:41:48.960> uh<00:41:49.079> the<00:41:49.200> other<00:41:49.520> one 00:41:50.510 --> 00:41:50.520 align:start position:0% people on Earth not the uh the other one 00:41:50.520 --> 00:41:53.069 align:start position:0% people on Earth not the uh the other one um<00:41:51.000> one<00:41:51.280> last<00:41:51.480> lens<00:41:51.760> from<00:41:51.880> the<00:41:52.040> super<00:41:52.319> real<00:41:52.680> is 00:41:53.069 --> 00:41:53.079 align:start position:0% um one last lens from the super real is 00:41:53.079 --> 00:41:55.190 align:start position:0% um one last lens from the super real is how<00:41:53.240> can<00:41:53.440> cryptography<00:41:54.040> help<00:41:54.240> us<00:41:54.480> reenchant 00:41:55.190 --> 00:41:55.200 align:start position:0% how can cryptography help us reenchant 00:41:55.200 --> 00:41:57.230 align:start position:0% how can cryptography help us reenchant the<00:41:55.359> digital<00:41:56.240> it's<00:41:56.400> not<00:41:56.560> just<00:41:56.760> now<00:41:56.920> we<00:41:57.000> can<00:41:57.079> do 00:41:57.230 --> 00:41:57.240 align:start position:0% the digital it's not just now we can do 00:41:57.240 --> 00:41:58.910 align:start position:0% the digital it's not just now we can do do<00:41:57.400> programming<00:41:57.839> on<00:41:58.040> cryptography<00:41:58.599> even<00:41:58.720> if 00:41:58.910 --> 00:41:58.920 align:start position:0% do programming on cryptography even if 00:41:58.920 --> 00:42:01.190 align:start position:0% do programming on cryptography even if that<00:41:59.079> is<00:41:59.319> very<00:41:59.560> cool<00:42:00.200> it's<00:42:00.359> that<00:42:00.520> cryptography 00:42:01.190 --> 00:42:01.200 align:start position:0% that is very cool it's that cryptography 00:42:01.200 --> 00:42:03.150 align:start position:0% that is very cool it's that cryptography itself<00:42:01.520> is<00:42:01.680> fundamentally<00:42:02.200> a<00:42:02.319> bridge<00:42:02.680> between 00:42:03.150 --> 00:42:03.160 align:start position:0% itself is fundamentally a bridge between 00:42:03.160 --> 00:42:05.030 align:start position:0% itself is fundamentally a bridge between math<00:42:03.359> and<00:42:03.560> physics<00:42:04.240> between<00:42:04.480> the<00:42:04.599> digital<00:42:04.920> and 00:42:05.030 --> 00:42:05.040 align:start position:0% math and physics between the digital and 00:42:05.040 --> 00:42:06.910 align:start position:0% math and physics between the digital and the<00:42:05.240> physical<00:42:06.040> and<00:42:06.200> perhaps<00:42:06.520> between 00:42:06.910 --> 00:42:06.920 align:start position:0% the physical and perhaps between 00:42:06.920 --> 00:42:10.109 align:start position:0% the physical and perhaps between computation<00:42:07.839> and<00:42:08.040> lived 00:42:10.109 --> 00:42:10.119 align:start position:0% computation and lived 00:42:10.119 --> 00:42:12.910 align:start position:0% computation and lived experience<00:42:11.119> so<00:42:11.400> finally<00:42:12.040> I<00:42:12.119> want<00:42:12.200> to<00:42:12.400> spend<00:42:12.800> a 00:42:12.910 --> 00:42:12.920 align:start position:0% experience so finally I want to spend a 00:42:12.920 --> 00:42:14.790 align:start position:0% experience so finally I want to spend a quick<00:42:13.160> few<00:42:13.400> minutes<00:42:14.000> on<00:42:14.240> what<00:42:14.359> I'm<00:42:14.480> going<00:42:14.599> to 00:42:14.790 --> 00:42:14.800 align:start position:0% quick few minutes on what I'm going to 00:42:14.800 --> 00:42:16.870 align:start position:0% quick few minutes on what I'm going to call<00:42:15.200> The<00:42:15.359> Surreal<00:42:16.200> I've<00:42:16.359> got<00:42:16.440> a<00:42:16.560> quote<00:42:16.760> here 00:42:16.870 --> 00:42:16.880 align:start position:0% call The Surreal I've got a quote here 00:42:16.880 --> 00:42:19.750 align:start position:0% call The Surreal I've got a quote here from<00:42:17.040> Italo<00:42:17.599> calino<00:42:18.599> um<00:42:18.920> that<00:42:19.079> closes<00:42:19.440> with<00:42:19.640> if 00:42:19.750 --> 00:42:19.760 align:start position:0% from Italo calino um that closes with if 00:42:19.760 --> 00:42:22.309 align:start position:0% from Italo calino um that closes with if a<00:42:19.920> new<00:42:20.119> world<00:42:20.400> were<00:42:20.800> discovered<00:42:21.200> now<00:42:21.880> would<00:42:22.079> we 00:42:22.309 --> 00:42:22.319 align:start position:0% a new world were discovered now would we 00:42:22.319 --> 00:42:25.069 align:start position:0% a new world were discovered now would we be<00:42:22.599> able<00:42:23.200> to<00:42:23.400> see<00:42:23.640> it<00:42:24.280> and<00:42:24.440> the<00:42:24.599> definition<00:42:24.960> of 00:42:25.069 --> 00:42:25.079 align:start position:0% be able to see it and the definition of 00:42:25.079 --> 00:42:30.190 align:start position:0% be able to see it and the definition of surreal<00:42:26.000> a<00:42:26.240> definition<00:42:26.599> at<00:42:26.680> least<00:42:26.920> is<00:42:27.400> Beyond 00:42:30.190 --> 00:42:30.200 align:start position:0% 00:42:30.200 --> 00:42:32.630 align:start position:0% reality<00:42:31.200> so<00:42:31.359> I<00:42:31.440> want<00:42:31.559> to<00:42:31.680> start<00:42:31.920> somewhere 00:42:32.630 --> 00:42:32.640 align:start position:0% reality so I want to start somewhere 00:42:32.640 --> 00:42:34.870 align:start position:0% reality so I want to start somewhere again<00:42:33.000> probably<00:42:33.280> a<00:42:33.359> bit<00:42:33.680> unexpected<00:42:34.680> what's 00:42:34.870 --> 00:42:34.880 align:start position:0% again probably a bit unexpected what's 00:42:34.880 --> 00:42:36.670 align:start position:0% again probably a bit unexpected what's the<00:42:35.040> greatest<00:42:35.440> invention<00:42:35.880> in<00:42:35.960> the<00:42:36.119> history<00:42:36.400> of 00:42:36.670 --> 00:42:36.680 align:start position:0% the greatest invention in the history of 00:42:36.680 --> 00:42:39.510 align:start position:0% the greatest invention in the history of mathematics<00:42:37.680> in<00:42:37.800> my<00:42:37.960> opinion<00:42:38.240> it's<00:42:38.359> the<00:42:38.599> polom 00:42:39.510 --> 00:42:39.520 align:start position:0% mathematics in my opinion it's the polom 00:42:39.520 --> 00:42:41.109 align:start position:0% mathematics in my opinion it's the polom the<00:42:39.640> ancient<00:42:39.960> Greeks<00:42:40.319> Romans<00:42:40.680> Chinese<00:42:41.040> they 00:42:41.109 --> 00:42:41.119 align:start position:0% the ancient Greeks Romans Chinese they 00:42:41.119 --> 00:42:42.870 align:start position:0% the ancient Greeks Romans Chinese they were<00:42:41.280> all<00:42:41.440> excellent<00:42:41.800> in<00:42:42.000> math<00:42:42.480> but<00:42:42.599> they<00:42:42.680> were 00:42:42.870 --> 00:42:42.880 align:start position:0% were all excellent in math but they were 00:42:42.880 --> 00:42:44.710 align:start position:0% were all excellent in math but they were held<00:42:43.240> back<00:42:43.480> by<00:42:43.640> not<00:42:43.839> having<00:42:44.200> something<00:42:44.520> like 00:42:44.710 --> 00:42:44.720 align:start position:0% held back by not having something like 00:42:44.720 --> 00:42:45.950 align:start position:0% held back by not having something like polinomial 00:42:45.950 --> 00:42:45.960 align:start position:0% polinomial 00:42:45.960 --> 00:42:47.430 align:start position:0% polinomial representation<00:42:46.960> but<00:42:47.119> here's<00:42:47.319> the 00:42:47.430 --> 00:42:47.440 align:start position:0% representation but here's the 00:42:47.440 --> 00:42:49.069 align:start position:0% representation but here's the interesting<00:42:47.800> thing<00:42:47.960> about<00:42:48.200> pols<00:42:48.800> even<00:42:48.960> though 00:42:49.069 --> 00:42:49.079 align:start position:0% interesting thing about pols even though 00:42:49.079 --> 00:42:50.829 align:start position:0% interesting thing about pols even though they<00:42:49.160> were<00:42:49.400> invented<00:42:50.040> close<00:42:50.280> to<00:42:50.440> a<00:42:50.559> thousand 00:42:50.829 --> 00:42:50.839 align:start position:0% they were invented close to a thousand 00:42:50.839 --> 00:42:52.510 align:start position:0% they were invented close to a thousand years<00:42:51.079> ago<00:42:51.960> and<00:42:52.040> even<00:42:52.200> though<00:42:52.319> they<00:42:52.400> were 00:42:52.510 --> 00:42:52.520 align:start position:0% years ago and even though they were 00:42:52.520 --> 00:42:53.710 align:start position:0% years ago and even though they were instrumental<00:42:52.960> to<00:42:53.119> things<00:42:53.280> even<00:42:53.480> like<00:42:53.599> the 00:42:53.710 --> 00:42:53.720 align:start position:0% instrumental to things even like the 00:42:53.720 --> 00:42:56.150 align:start position:0% instrumental to things even like the invention<00:42:54.000> of<00:42:54.200> calculus<00:42:55.000> we<00:42:55.160> didn't<00:42:55.680> really 00:42:56.150 --> 00:42:56.160 align:start position:0% invention of calculus we didn't really 00:42:56.160 --> 00:42:58.230 align:start position:0% invention of calculus we didn't really understand<00:42:56.359> how<00:42:56.640> awesome<00:42:57.319> were<00:42:57.520> until<00:42:57.760> around 00:42:58.230 --> 00:42:58.240 align:start position:0% understand how awesome were until around 00:42:58.240 --> 00:43:01.390 align:start position:0% understand how awesome were until around 200<00:42:58.520> years<00:42:59.119> ago<00:43:00.119> what<00:43:00.240> happened<00:43:00.599> then<00:43:01.160> we<00:43:01.280> got 00:43:01.390 --> 00:43:01.400 align:start position:0% 200 years ago what happened then we got 00:43:01.400 --> 00:43:03.190 align:start position:0% 200 years ago what happened then we got the<00:43:01.520> first<00:43:01.800> rigorous<00:43:02.359> proofs<00:43:02.680> of<00:43:02.760> a<00:43:02.880> theorem 00:43:03.190 --> 00:43:03.200 align:start position:0% the first rigorous proofs of a theorem 00:43:03.200 --> 00:43:05.270 align:start position:0% the first rigorous proofs of a theorem about<00:43:03.440> pols<00:43:04.040> that's<00:43:04.240> so<00:43:04.440> important<00:43:04.839> we<00:43:05.000> call 00:43:05.270 --> 00:43:05.280 align:start position:0% about pols that's so important we call 00:43:05.280 --> 00:43:07.549 align:start position:0% about pols that's so important we call it<00:43:05.440> the<00:43:05.599> fundamental<00:43:06.280> theorem<00:43:06.680> of 00:43:07.549 --> 00:43:07.559 align:start position:0% it the fundamental theorem of 00:43:07.559 --> 00:43:09.630 align:start position:0% it the fundamental theorem of algebra<00:43:08.559> the<00:43:08.680> thing<00:43:08.880> about<00:43:09.079> the<00:43:09.200> fundamental 00:43:09.630 --> 00:43:09.640 align:start position:0% algebra the thing about the fundamental 00:43:09.640 --> 00:43:11.670 align:start position:0% algebra the thing about the fundamental theorem<00:43:09.920> of<00:43:10.000> algebra<00:43:10.520> is<00:43:11.000> it<00:43:11.119> doesn't<00:43:11.400> even 00:43:11.670 --> 00:43:11.680 align:start position:0% theorem of algebra is it doesn't even 00:43:11.680 --> 00:43:13.990 align:start position:0% theorem of algebra is it doesn't even work<00:43:11.920> if<00:43:12.040> you<00:43:12.200> only<00:43:12.480> have<00:43:12.680> real<00:43:13.000> numbers<00:43:13.800> it 00:43:13.990 --> 00:43:14.000 align:start position:0% work if you only have real numbers it 00:43:14.000 --> 00:43:16.430 align:start position:0% work if you only have real numbers it only<00:43:14.280> works<00:43:14.599> when<00:43:14.720> you<00:43:14.920> have<00:43:15.280> complex<00:43:15.800> numbers 00:43:16.430 --> 00:43:16.440 align:start position:0% only works when you have complex numbers 00:43:16.440 --> 00:43:18.390 align:start position:0% only works when you have complex numbers and<00:43:16.520> it<00:43:16.640> turns<00:43:16.839> out<00:43:17.079> pols<00:43:17.760> are<00:43:17.960> just<00:43:18.079> one<00:43:18.200> of 00:43:18.390 --> 00:43:18.400 align:start position:0% and it turns out pols are just one of 00:43:18.400 --> 00:43:20.630 align:start position:0% and it turns out pols are just one of many<00:43:18.640> things<00:43:18.880> that<00:43:19.040> make<00:43:19.480> way<00:43:19.839> way<00:43:20.119> way<00:43:20.280> more 00:43:20.630 --> 00:43:20.640 align:start position:0% many things that make way way way more 00:43:20.640 --> 00:43:23.630 align:start position:0% many things that make way way way more sense<00:43:20.960> with<00:43:21.319> complex<00:43:22.200> numbers<00:43:23.200> that's<00:43:23.359> why<00:43:23.520> I 00:43:23.630 --> 00:43:23.640 align:start position:0% sense with complex numbers that's why I 00:43:23.640 --> 00:43:25.670 align:start position:0% sense with complex numbers that's why I say<00:43:23.839> the<00:43:24.079> most<00:43:24.400> unbelievable<00:43:25.079> realization<00:43:25.559> in 00:43:25.670 --> 00:43:25.680 align:start position:0% say the most unbelievable realization in 00:43:25.680 --> 00:43:27.270 align:start position:0% say the most unbelievable realization in the<00:43:25.760> history<00:43:26.000> of<00:43:26.160> mathematics<00:43:26.599> and<00:43:26.720> arguably 00:43:27.270 --> 00:43:27.280 align:start position:0% the history of mathematics and arguably 00:43:27.280 --> 00:43:29.150 align:start position:0% the history of mathematics and arguably the<00:43:27.400> world<00:43:27.920> is<00:43:28.040> that<00:43:28.280> reality<00:43:28.760> itself 00:43:29.150 --> 00:43:29.160 align:start position:0% the world is that reality itself 00:43:29.160 --> 00:43:31.549 align:start position:0% the world is that reality itself consists<00:43:29.520> of<00:43:29.680> more<00:43:29.920> than<00:43:30.200> just<00:43:30.559> real<00:43:30.839> numbers 00:43:31.549 --> 00:43:31.559 align:start position:0% consists of more than just real numbers 00:43:31.559 --> 00:43:33.470 align:start position:0% consists of more than just real numbers that<00:43:31.720> the<00:43:31.839> real<00:43:32.040> numbers<00:43:32.359> were<00:43:32.680> nowhere<00:43:33.119> near 00:43:33.470 --> 00:43:33.480 align:start position:0% that the real numbers were nowhere near 00:43:33.480 --> 00:43:35.390 align:start position:0% that the real numbers were nowhere near all<00:43:33.680> that<00:43:33.800> was<00:43:33.920> required<00:43:34.280> to<00:43:34.440> Simply<00:43:34.839> describe 00:43:35.390 --> 00:43:35.400 align:start position:0% all that was required to Simply describe 00:43:35.400 --> 00:43:37.910 align:start position:0% all that was required to Simply describe and<00:43:35.559> reason<00:43:35.960> about<00:43:36.400> reality<00:43:37.040> accurately 00:43:37.910 --> 00:43:37.920 align:start position:0% and reason about reality accurately 00:43:37.920 --> 00:43:39.470 align:start position:0% and reason about reality accurately complex<00:43:38.280> numbers<00:43:38.520> show<00:43:38.720> up<00:43:38.880> everywhere<00:43:39.280> from 00:43:39.470 --> 00:43:39.480 align:start position:0% complex numbers show up everywhere from 00:43:39.480 --> 00:43:41.790 align:start position:0% complex numbers show up everywhere from Electronics<00:43:40.280> to<00:43:40.440> fluid<00:43:40.760> dynamics<00:43:41.280> to<00:43:41.400> quantum 00:43:41.790 --> 00:43:41.800 align:start position:0% Electronics to fluid dynamics to quantum 00:43:41.800 --> 00:43:45.190 align:start position:0% Electronics to fluid dynamics to quantum mechanics<00:43:42.359> and<00:43:43.040> more<00:43:44.040> what's<00:43:44.240> more<00:43:44.480> the<00:43:44.599> reals 00:43:45.190 --> 00:43:45.200 align:start position:0% mechanics and more what's more the reals 00:43:45.200 --> 00:43:47.510 align:start position:0% mechanics and more what's more the reals themselves<00:43:45.599> became<00:43:45.920> more<00:43:46.280> spectacular<00:43:47.280> once 00:43:47.510 --> 00:43:47.520 align:start position:0% themselves became more spectacular once 00:43:47.520 --> 00:43:49.910 align:start position:0% themselves became more spectacular once we<00:43:47.800> completed<00:43:48.480> or<00:43:48.760> algebraically<00:43:49.400> closed<00:43:49.760> for 00:43:49.910 --> 00:43:49.920 align:start position:0% we completed or algebraically closed for 00:43:49.920 --> 00:43:51.349 align:start position:0% we completed or algebraically closed for those<00:43:50.079> are<00:43:50.440> who<00:43:50.559> are<00:43:50.680> familiar<00:43:51.000> with<00:43:51.200> that 00:43:51.349 --> 00:43:51.359 align:start position:0% those are who are familiar with that 00:43:51.359 --> 00:43:53.710 align:start position:0% those are who are familiar with that notation<00:43:52.200> once<00:43:52.400> we<00:43:52.599> completed<00:43:53.079> the<00:43:53.200> reals<00:43:53.559> to 00:43:53.710 --> 00:43:53.720 align:start position:0% notation once we completed the reals to 00:43:53.720 --> 00:43:56.190 align:start position:0% notation once we completed the reals to form<00:43:53.960> the<00:43:54.200> complex<00:43:54.680> numbers<00:43:55.480> e<00:43:55.800> goes<00:43:56.000> from 00:43:56.190 --> 00:43:56.200 align:start position:0% form the complex numbers e goes from 00:43:56.200 --> 00:43:57.910 align:start position:0% form the complex numbers e goes from being<00:43:56.640> the<00:43:56.760> number<00:43:57.200> that's<00:43:57.359> defined<00:43:57.680> as<00:43:57.800> like 00:43:57.910 --> 00:43:57.920 align:start position:0% being the number that's defined as like 00:43:57.920 --> 00:43:59.430 align:start position:0% being the number that's defined as like the<00:43:58.040> derivative<00:43:58.440> of<00:43:58.559> e<00:43:58.680> to<00:43:58.800> the<00:43:58.880> x<00:43:59.040> is<00:43:59.160> still<00:43:59.280> e 00:43:59.430 --> 00:43:59.440 align:start position:0% the derivative of e to the x is still e 00:43:59.440 --> 00:44:01.390 align:start position:0% the derivative of e to the x is still e to<00:43:59.559> the<00:43:59.680> X<00:44:00.000> to<00:44:00.160> being<00:44:00.319> a<00:44:00.440> fundamental<00:44:00.920> basis<00:44:01.200> of 00:44:01.390 --> 00:44:01.400 align:start position:0% to the X to being a fundamental basis of 00:44:01.400 --> 00:44:03.829 align:start position:0% to the X to being a fundamental basis of rotation<00:44:01.880> in<00:44:01.960> the<00:44:02.160> complex<00:44:02.599> plane<00:44:03.359> Pi<00:44:03.640> goes 00:44:03.829 --> 00:44:03.839 align:start position:0% rotation in the complex plane Pi goes 00:44:03.839 --> 00:44:05.710 align:start position:0% rotation in the complex plane Pi goes from<00:44:03.960> circles<00:44:04.319> being<00:44:04.559> cool<00:44:05.119> to<00:44:05.280> being<00:44:05.559> far 00:44:05.710 --> 00:44:05.720 align:start position:0% from circles being cool to being far 00:44:05.720 --> 00:44:07.549 align:start position:0% from circles being cool to being far more<00:44:05.960> significant<00:44:06.599> in<00:44:06.800> part<00:44:07.079> because<00:44:07.280> the<00:44:07.400> set 00:44:07.549 --> 00:44:07.559 align:start position:0% more significant in part because the set 00:44:07.559 --> 00:44:09.510 align:start position:0% more significant in part because the set of<00:44:07.640> points<00:44:07.920> equidistant<00:44:08.480> from<00:44:08.640> the<00:44:08.760> origin 00:44:09.510 --> 00:44:09.520 align:start position:0% of points equidistant from the origin 00:44:09.520 --> 00:44:11.030 align:start position:0% of points equidistant from the origin becomes<00:44:09.920> far<00:44:10.160> more<00:44:10.400> interesting<00:44:10.800> in<00:44:10.880> a 00:44:11.030 --> 00:44:11.040 align:start position:0% becomes far more interesting in a 00:44:11.040 --> 00:44:13.069 align:start position:0% becomes far more interesting in a two-dimensional<00:44:11.760> complex<00:44:12.200> plane<00:44:12.680> than<00:44:12.800> on<00:44:12.920> a 00:44:13.069 --> 00:44:13.079 align:start position:0% two-dimensional complex plane than on a 00:44:13.079 --> 00:44:14.430 align:start position:0% two-dimensional complex plane than on a one-dimensional<00:44:13.720> number<00:44:14.000> line<00:44:14.200> where<00:44:14.319> you 00:44:14.430 --> 00:44:14.440 align:start position:0% one-dimensional number line where you 00:44:14.440 --> 00:44:17.349 align:start position:0% one-dimensional number line where you just<00:44:14.559> have<00:44:14.760> X<00:44:15.079> and<00:44:15.240> negative<00:44:16.040> X<00:44:17.040> and<00:44:17.160> that's 00:44:17.349 --> 00:44:17.359 align:start position:0% just have X and negative X and that's 00:44:17.359 --> 00:44:19.069 align:start position:0% just have X and negative X and that's barely<00:44:17.640> scratching<00:44:18.359> the<00:44:18.520> surface<00:44:18.839> of 00:44:19.069 --> 00:44:19.079 align:start position:0% barely scratching the surface of 00:44:19.079 --> 00:44:21.710 align:start position:0% barely scratching the surface of examples<00:44:19.960> so<00:44:20.200> consider<00:44:20.640> this<00:44:21.200> if<00:44:21.319> the<00:44:21.480> real 00:44:21.710 --> 00:44:21.720 align:start position:0% examples so consider this if the real 00:44:21.720 --> 00:44:23.109 align:start position:0% examples so consider this if the real numbers<00:44:22.000> aren't<00:44:22.319> the<00:44:22.440> full<00:44:22.640> picture<00:44:22.880> of 00:44:23.109 --> 00:44:23.119 align:start position:0% numbers aren't the full picture of 00:44:23.119 --> 00:44:25.309 align:start position:0% numbers aren't the full picture of reality<00:44:23.960> should<00:44:24.160> we<00:44:24.359> expect<00:44:24.680> anything<00:44:25.000> else 00:44:25.309 --> 00:44:25.319 align:start position:0% reality should we expect anything else 00:44:25.319 --> 00:44:28.750 align:start position:0% reality should we expect anything else to<00:44:25.559> be<00:44:26.520> does<00:44:26.680> the<00:44:27.119> digital<00:44:28.119> the<00:44:28.240> internet<00:44:28.640> the 00:44:28.750 --> 00:44:28.760 align:start position:0% to be does the digital the internet the 00:44:28.760 --> 00:44:30.630 align:start position:0% to be does the digital the internet the web<00:44:29.000> and<00:44:29.119> perhaps<00:44:29.440> more<00:44:29.760> not<00:44:30.040> really<00:44:30.359> make 00:44:30.630 --> 00:44:30.640 align:start position:0% web and perhaps more not really make 00:44:30.640 --> 00:44:32.510 align:start position:0% web and perhaps more not really make sense<00:44:30.960> until<00:44:31.280> we<00:44:31.520> complete<00:44:31.880> it<00:44:32.040> with<00:44:32.160> a<00:44:32.280> unit 00:44:32.510 --> 00:44:32.520 align:start position:0% sense until we complete it with a unit 00:44:32.520 --> 00:44:35.109 align:start position:0% sense until we complete it with a unit of<00:44:32.640> cryptography<00:44:33.640> as<00:44:33.760> the<00:44:33.880> reals<00:44:34.319> were<00:44:34.880> to 00:44:35.109 --> 00:44:35.119 align:start position:0% of cryptography as the reals were to 00:44:35.119 --> 00:44:36.309 align:start position:0% of cryptography as the reals were to form<00:44:35.319> the 00:44:36.309 --> 00:44:36.319 align:start position:0% form the 00:44:36.319 --> 00:44:38.710 align:start position:0% form the complex<00:44:37.319> if<00:44:37.520> physical<00:44:37.880> reality<00:44:38.200> is<00:44:38.280> built<00:44:38.520> on 00:44:38.710 --> 00:44:38.720 align:start position:0% complex if physical reality is built on 00:44:38.720 --> 00:44:41.069 align:start position:0% complex if physical reality is built on physics<00:44:39.160> can<00:44:39.280> we<00:44:39.640> enrich<00:44:40.079> a<00:44:40.280> complex<00:44:40.760> super 00:44:41.069 --> 00:44:41.079 align:start position:0% physics can we enrich a complex super 00:44:41.079 --> 00:44:42.750 align:start position:0% physics can we enrich a complex super Reality<00:44:41.480> by<00:44:41.599> bringing<00:44:41.960> elements<00:44:42.520> of<00:44:42.640> the 00:44:42.750 --> 00:44:42.760 align:start position:0% Reality by bringing elements of the 00:44:42.760 --> 00:44:44.829 align:start position:0% Reality by bringing elements of the physical<00:44:43.359> into<00:44:43.559> the<00:44:43.680> digital<00:44:44.040> realm<00:44:44.559> just<00:44:44.680> as 00:44:44.829 --> 00:44:44.839 align:start position:0% physical into the digital realm just as 00:44:44.839 --> 00:44:46.150 align:start position:0% physical into the digital realm just as we've<00:44:45.040> clearly<00:44:45.319> brought<00:44:45.599> elements<00:44:45.920> of<00:44:46.040> the 00:44:46.150 --> 00:44:46.160 align:start position:0% we've clearly brought elements of the 00:44:46.160 --> 00:44:48.390 align:start position:0% we've clearly brought elements of the digital<00:44:46.640> into<00:44:46.839> our<00:44:47.040> physical<00:44:47.480> existence<00:44:48.240> and 00:44:48.390 --> 00:44:48.400 align:start position:0% digital into our physical existence and 00:44:48.400 --> 00:44:50.950 align:start position:0% digital into our physical existence and can<00:44:48.559> this<00:44:48.720> be<00:44:48.920> a<00:44:49.119> symbiotic<00:44:49.800> relationship<00:44:50.800> it 00:44:50.950 --> 00:44:50.960 align:start position:0% can this be a symbiotic relationship it 00:44:50.960 --> 00:44:52.910 align:start position:0% can this be a symbiotic relationship it almost<00:44:51.280> can't<00:44:51.559> not<00:44:51.720> be<00:44:51.880> to<00:44:52.200> actually<00:44:52.559> feel 00:44:52.910 --> 00:44:52.920 align:start position:0% almost can't not be to actually feel 00:44:52.920 --> 00:44:55.470 align:start position:0% almost can't not be to actually feel like<00:44:53.079> super<00:44:53.680> reality<00:44:54.680> is<00:44:54.800> there<00:44:54.920> a<00:44:55.079> complex 00:44:55.470 --> 00:44:55.480 align:start position:0% like super reality is there a complex 00:44:55.480 --> 00:44:57.549 align:start position:0% like super reality is there a complex big<00:44:55.720> BL<00:44:56.000> bang<00:44:56.520> will<00:44:56.680> it<00:44:56.760> look<00:44:56.880> like<00:44:57.079> a<00:44:57.160> Genesis 00:44:57.549 --> 00:44:57.559 align:start position:0% big BL bang will it look like a Genesis 00:44:57.559 --> 00:44:59.510 align:start position:0% big BL bang will it look like a Genesis block<00:44:57.800> or<00:44:57.920> something<00:44:58.200> else<00:44:58.800> is<00:44:58.960> cryptography 00:44:59.510 --> 00:44:59.520 align:start position:0% block or something else is cryptography 00:44:59.520 --> 00:45:02.030 align:start position:0% block or something else is cryptography where<00:44:59.720> silicon<00:45:00.240> based<00:45:00.680> life<00:45:00.960> really<00:45:01.200> comes 00:45:02.030 --> 00:45:02.040 align:start position:0% where silicon based life really comes 00:45:02.040 --> 00:45:04.750 align:start position:0% where silicon based life really comes from<00:45:03.040> and<00:45:03.160> what's<00:45:03.359> more<00:45:03.599> real<00:45:04.240> places<00:45:04.520> in<00:45:04.640> the 00:45:04.750 --> 00:45:04.760 align:start position:0% from and what's more real places in the 00:45:04.760 --> 00:45:06.230 align:start position:0% from and what's more real places in the physical<00:45:05.079> Universe<00:45:05.440> we<00:45:05.559> can<00:45:05.680> literally<00:45:06.040> never 00:45:06.230 --> 00:45:06.240 align:start position:0% physical Universe we can literally never 00:45:06.240 --> 00:45:07.910 align:start position:0% physical Universe we can literally never reach<00:45:06.559> like<00:45:06.680> we<00:45:06.800> get<00:45:07.040> light<00:45:07.240> from<00:45:07.480> places<00:45:07.800> that 00:45:07.910 --> 00:45:07.920 align:start position:0% reach like we get light from places that 00:45:07.920 --> 00:45:09.430 align:start position:0% reach like we get light from places that are<00:45:08.079> so<00:45:08.280> far<00:45:08.520> that<00:45:08.640> if<00:45:08.720> we<00:45:08.839> traveled<00:45:09.200> at<00:45:09.319> the 00:45:09.430 --> 00:45:09.440 align:start position:0% are so far that if we traveled at the 00:45:09.440 --> 00:45:11.109 align:start position:0% are so far that if we traveled at the speed<00:45:09.640> of<00:45:09.760> light<00:45:09.960> towards<00:45:10.400> them<00:45:10.839> because<00:45:11.040> the 00:45:11.109 --> 00:45:11.119 align:start position:0% speed of light towards them because the 00:45:11.119 --> 00:45:12.710 align:start position:0% speed of light towards them because the universe<00:45:11.480> is<00:45:11.640> expanding<00:45:12.079> we<00:45:12.160> will<00:45:12.359> literally 00:45:12.710 --> 00:45:12.720 align:start position:0% universe is expanding we will literally 00:45:12.720 --> 00:45:15.349 align:start position:0% universe is expanding we will literally never<00:45:13.160> get<00:45:13.400> there<00:45:14.000> what's<00:45:14.200> more<00:45:14.400> real<00:45:15.079> those 00:45:15.349 --> 00:45:15.359 align:start position:0% never get there what's more real those 00:45:15.359 --> 00:45:17.589 align:start position:0% never get there what's more real those places<00:45:15.680> are<00:45:15.960> places<00:45:16.240> in<00:45:16.480> this<00:45:16.920> perhaps<00:45:17.280> more 00:45:17.589 --> 00:45:17.599 align:start position:0% places are places in this perhaps more 00:45:17.599 --> 00:45:19.430 align:start position:0% places are places in this perhaps more vast<00:45:17.960> complex<00:45:18.359> reality<00:45:18.720> that<00:45:18.880> we<00:45:19.079> actually 00:45:19.430 --> 00:45:19.440 align:start position:0% vast complex reality that we actually 00:45:19.440 --> 00:45:21.990 align:start position:0% vast complex reality that we actually can<00:45:19.880> visit<00:45:20.880> and<00:45:21.000> so<00:45:21.119> the<00:45:21.240> last<00:45:21.400> thing<00:45:21.520> I'll<00:45:21.720> say 00:45:21.990 --> 00:45:22.000 align:start position:0% can visit and so the last thing I'll say 00:45:22.000 --> 00:45:23.950 align:start position:0% can visit and so the last thing I'll say is<00:45:22.440> in<00:45:22.599> science<00:45:22.920> fiction<00:45:23.240> you<00:45:23.319> know<00:45:23.480> we<00:45:23.680> see 00:45:23.950 --> 00:45:23.960 align:start position:0% is in science fiction you know we see 00:45:23.960 --> 00:45:26.510 align:start position:0% is in science fiction you know we see this<00:45:24.119> phrase<00:45:24.400> outer<00:45:24.720> World<00:45:25.319> sometimes<00:45:26.280> will 00:45:26.510 --> 00:45:26.520 align:start position:0% this phrase outer World sometimes will 00:45:26.520 --> 00:45:28.750 align:start position:0% this phrase outer World sometimes will we<00:45:26.680> one<00:45:27.079> think<00:45:27.200> of<00:45:27.280> outer<00:45:27.599> realities<00:45:28.559> and<00:45:28.640> I 00:45:28.750 --> 00:45:28.760 align:start position:0% we one think of outer realities and I 00:45:28.760 --> 00:45:30.190 align:start position:0% we one think of outer realities and I wonder<00:45:29.040> when<00:45:29.160> we<00:45:29.359> hear<00:45:29.559> a<00:45:29.720> voice<00:45:29.920> from<00:45:30.079> an 00:45:30.190 --> 00:45:30.200 align:start position:0% wonder when we hear a voice from an 00:45:30.200 --> 00:45:32.589 align:start position:0% wonder when we hear a voice from an outer<00:45:30.520> reality<00:45:31.040> what<00:45:31.400> we<00:45:31.760> will<00:45:31.960> look<00:45:32.160> like<00:45:32.400> by 00:45:32.589 --> 00:45:32.599 align:start position:0% outer reality what we will look like by 00:45:32.599 --> 00:45:34.549 align:start position:0% outer reality what we will look like by then<00:45:33.200> and<00:45:33.359> who<00:45:33.559> will<00:45:33.720> be 00:45:34.549 --> 00:45:34.559 align:start position:0% then and who will be 00:45:34.559 --> 00:45:37.150 align:start position:0% then and who will be listening<00:45:35.559> and<00:45:35.680> so<00:45:36.400> I'll<00:45:36.559> leave<00:45:36.760> you<00:45:37.000> with 00:45:37.150 --> 00:45:37.160 align:start position:0% listening and so I'll leave you with 00:45:37.160 --> 00:45:39.349 align:start position:0% listening and so I'll leave you with this<00:45:37.319> final<00:45:37.599> note<00:45:38.280> as<00:45:38.440> we<00:45:38.680> uh<00:45:38.760> take<00:45:38.920> a<00:45:39.000> few<00:45:39.200> for 00:45:39.349 --> 00:45:39.359 align:start position:0% this final note as we uh take a few for 00:45:39.359 --> 00:45:42.910 align:start position:0% this final note as we uh take a few for Q&A<00:45:40.160> thanks<00:45:40.319> a<00:45:40.440> lot<00:45:40.559> for 00:45:42.910 --> 00:45:42.920 align:start position:0% 00:45:42.920 --> 00:45:46.309 align:start position:0% coming<00:45:43.920> thank<00:45:44.079> you 00:45:46.309 --> 00:45:46.319 align:start position:0% 00:45:46.319 --> 00:45:49.630 align:start position:0% Albert<00:45:47.319> so<00:45:47.920> to<00:45:48.079> start<00:45:48.280> the<00:45:48.440> Q&A<00:45:48.839> session<00:45:49.520> the 00:45:49.630 --> 00:45:49.640 align:start position:0% Albert so to start the Q&A session the 00:45:49.640 --> 00:45:51.349 align:start position:0% Albert so to start the Q&A session the first<00:45:49.880> question<00:45:50.160> is<00:45:50.440> how<00:45:50.559> does<00:45:50.800> cryptography 00:45:51.349 --> 00:45:51.359 align:start position:0% first question is how does cryptography 00:45:51.359 --> 00:45:52.990 align:start position:0% first question is how does cryptography as<00:45:51.480> a<00:45:51.599> fifth<00:45:51.880> Force<00:45:52.280> interface<00:45:52.800> with<00:45:52.920> the 00:45:52.990 --> 00:45:53.000 align:start position:0% as a fifth Force interface with the 00:45:53.000 --> 00:45:54.950 align:start position:0% as a fifth Force interface with the firmy<00:45:53.400> Paradox<00:45:53.920> are<00:45:54.040> all<00:45:54.280> the<00:45:54.400> aliens 00:45:54.950 --> 00:45:54.960 align:start position:0% firmy Paradox are all the aliens 00:45:54.960 --> 00:45:57.069 align:start position:0% firmy Paradox are all the aliens encrypted<00:45:55.960> yeah<00:45:56.079> I<00:45:56.200> love<00:45:56.400> this<00:45:56.559> question 00:45:57.069 --> 00:45:57.079 align:start position:0% encrypted yeah I love this question 00:45:57.079 --> 00:45:58.190 align:start position:0% encrypted yeah I love this question actually<00:45:57.400> because<00:45:57.640> I've<00:45:57.800> always<00:45:57.960> thought<00:45:58.119> the 00:45:58.190 --> 00:45:58.200 align:start position:0% actually because I've always thought the 00:45:58.200 --> 00:46:00.309 align:start position:0% actually because I've always thought the firming<00:45:58.599> Paradox<00:45:59.160> was<00:45:59.400> a<00:45:59.480> little<00:45:59.680> bit<00:45:59.880> simpler 00:46:00.309 --> 00:46:00.319 align:start position:0% firming Paradox was a little bit simpler 00:46:00.319 --> 00:46:01.790 align:start position:0% firming Paradox was a little bit simpler than<00:46:00.440> people<00:46:00.680> make<00:46:00.839> it<00:46:00.960> out<00:46:01.160> to<00:46:01.280> be<00:46:01.599> because 00:46:01.790 --> 00:46:01.800 align:start position:0% than people make it out to be because 00:46:01.800 --> 00:46:03.470 align:start position:0% than people make it out to be because the<00:46:01.920> key<00:46:02.079> is<00:46:02.280> why<00:46:02.400> aren't<00:46:02.599> we<00:46:02.760> observing 00:46:03.470 --> 00:46:03.480 align:start position:0% the key is why aren't we observing 00:46:03.480 --> 00:46:06.190 align:start position:0% the key is why aren't we observing things<00:46:04.359> and<00:46:05.040> given<00:46:05.280> that<00:46:05.400> for<00:46:05.559> example<00:46:05.880> we<00:46:06.000> can 00:46:06.190 --> 00:46:06.200 align:start position:0% things and given that for example we can 00:46:06.200 --> 00:46:08.990 align:start position:0% things and given that for example we can observe<00:46:06.720> an<00:46:06.920> ant<00:46:07.280> farm<00:46:08.160> without<00:46:08.559> it<00:46:08.760> having 00:46:08.990 --> 00:46:09.000 align:start position:0% observe an ant farm without it having 00:46:09.000 --> 00:46:10.430 align:start position:0% observe an ant farm without it having any<00:46:09.160> sense<00:46:09.359> that<00:46:09.480> we're<00:46:09.640> observing<00:46:10.079> them 00:46:10.430 --> 00:46:10.440 align:start position:0% any sense that we're observing them 00:46:10.440 --> 00:46:12.190 align:start position:0% any sense that we're observing them there's<00:46:10.559> a<00:46:10.720> pretty<00:46:11.079> big<00:46:11.400> assumption<00:46:11.880> that<00:46:12.040> it 00:46:12.190 --> 00:46:12.200 align:start position:0% there's a pretty big assumption that it 00:46:12.200 --> 00:46:14.069 align:start position:0% there's a pretty big assumption that it should<00:46:12.440> be<00:46:12.760> like<00:46:13.000> that<00:46:13.160> easy<00:46:13.400> to<00:46:13.640> observe 00:46:14.069 --> 00:46:14.079 align:start position:0% should be like that easy to observe 00:46:14.079 --> 00:46:15.630 align:start position:0% should be like that easy to observe stuff<00:46:14.319> out<00:46:14.520> there<00:46:14.839> so<00:46:14.960> that's<00:46:15.119> not<00:46:15.319> exactly 00:46:15.630 --> 00:46:15.640 align:start position:0% stuff out there so that's not exactly 00:46:15.640 --> 00:46:17.470 align:start position:0% stuff out there so that's not exactly what<00:46:15.800> this<00:46:16.119> question<00:46:16.640> is<00:46:16.800> saying<00:46:17.160> but<00:46:17.280> I<00:46:17.359> just 00:46:17.470 --> 00:46:17.480 align:start position:0% what this question is saying but I just 00:46:17.480 --> 00:46:18.910 align:start position:0% what this question is saying but I just kind<00:46:17.559> of<00:46:17.680> wanted<00:46:17.880> to<00:46:18.000> point<00:46:18.200> that<00:46:18.319> out<00:46:18.559> like 00:46:18.910 --> 00:46:18.920 align:start position:0% kind of wanted to point that out like 00:46:18.920 --> 00:46:20.430 align:start position:0% kind of wanted to point that out like what<00:46:19.040> if<00:46:19.160> you<00:46:19.280> could 00:46:20.430 --> 00:46:20.440 align:start position:0% what if you could 00:46:20.440 --> 00:46:22.470 align:start position:0% what if you could cryptographically<00:46:21.440> be<00:46:21.680> like<00:46:21.960> encrypt<00:46:22.359> your 00:46:22.470 --> 00:46:22.480 align:start position:0% cryptographically be like encrypt your 00:46:22.480 --> 00:46:24.270 align:start position:0% cryptographically be like encrypt your mind<00:46:22.680> onto<00:46:23.000> like<00:46:23.160> neutrinos<00:46:23.760> and<00:46:23.880> then<00:46:23.960> flow 00:46:24.270 --> 00:46:24.280 align:start position:0% mind onto like neutrinos and then flow 00:46:24.280 --> 00:46:25.510 align:start position:0% mind onto like neutrinos and then flow through<00:46:24.480> everything<00:46:25.040> maybe<00:46:25.280> that's 00:46:25.510 --> 00:46:25.520 align:start position:0% through everything maybe that's 00:46:25.520 --> 00:46:26.630 align:start position:0% through everything maybe that's happening<00:46:25.920> right<00:46:26.040> now<00:46:26.200> and<00:46:26.280> maybe<00:46:26.480> that's 00:46:26.630 --> 00:46:26.640 align:start position:0% happening right now and maybe that's 00:46:26.640 --> 00:46:28.950 align:start position:0% happening right now and maybe that's where<00:46:27.000> things<00:46:27.240> will<00:46:27.520> go<00:46:28.079> so<00:46:28.319> even<00:46:28.520> just<00:46:28.680> at 00:46:28.950 --> 00:46:28.960 align:start position:0% where things will go so even just at 00:46:28.960 --> 00:46:30.470 align:start position:0% where things will go so even just at that<00:46:29.160> level<00:46:29.400> like<00:46:29.520> cryptography<00:46:30.119> has<00:46:30.240> helped 00:46:30.470 --> 00:46:30.480 align:start position:0% that level like cryptography has helped 00:46:30.480 --> 00:46:31.829 align:start position:0% that level like cryptography has helped me<00:46:30.599> with<00:46:30.720> my<00:46:30.880> thinking<00:46:31.160> around<00:46:31.400> the<00:46:31.480> fmy 00:46:31.829 --> 00:46:31.839 align:start position:0% me with my thinking around the fmy 00:46:31.839 --> 00:46:33.670 align:start position:0% me with my thinking around the fmy Paradox<00:46:32.520> not<00:46:32.680> saying<00:46:32.920> that's<00:46:33.079> the<00:46:33.240> answer<00:46:33.520> but 00:46:33.670 --> 00:46:33.680 align:start position:0% Paradox not saying that's the answer but 00:46:33.680 --> 00:46:35.230 align:start position:0% Paradox not saying that's the answer but I<00:46:33.760> think<00:46:33.920> it's<00:46:34.319> people<00:46:34.520> kind<00:46:34.640> of<00:46:34.720> skip<00:46:35.000> over 00:46:35.230 --> 00:46:35.240 align:start position:0% I think it's people kind of skip over 00:46:35.240 --> 00:46:36.589 align:start position:0% I think it's people kind of skip over the<00:46:35.359> whole<00:46:35.559> like<00:46:35.800> oh<00:46:35.920> of<00:46:36.040> course<00:46:36.200> we'd<00:46:36.359> be<00:46:36.480> able 00:46:36.589 --> 00:46:36.599 align:start position:0% the whole like oh of course we'd be able 00:46:36.599 --> 00:46:38.750 align:start position:0% the whole like oh of course we'd be able to<00:46:36.720> see<00:46:36.880> it<00:46:37.079> even<00:46:37.319> though<00:46:37.960> it's<00:46:38.200> actually<00:46:38.520> it's 00:46:38.750 --> 00:46:38.760 align:start position:0% to see it even though it's actually it's 00:46:38.760 --> 00:46:41.069 align:start position:0% to see it even though it's actually it's like<00:46:38.920> literally<00:46:39.240> trivial<00:46:39.599> for<00:46:39.720> us<00:46:39.880> to<00:46:40.079> observe 00:46:41.069 --> 00:46:41.079 align:start position:0% like literally trivial for us to observe 00:46:41.079 --> 00:46:42.790 align:start position:0% like literally trivial for us to observe life<00:46:41.400> that<00:46:41.520> is<00:46:41.800> probably<00:46:42.160> closer<00:46:42.440> to<00:46:42.599> what<00:46:42.680> we 00:46:42.790 --> 00:46:42.800 align:start position:0% life that is probably closer to what we 00:46:42.800 --> 00:46:45.030 align:start position:0% life that is probably closer to what we are<00:46:43.119> than<00:46:43.319> you<00:46:43.400> know<00:46:43.559> maybe<00:46:43.800> more<00:46:44.040> powerful 00:46:45.030 --> 00:46:45.040 align:start position:0% are than you know maybe more powerful 00:46:45.040 --> 00:46:48.190 align:start position:0% are than you know maybe more powerful intelligences<00:46:45.720> are<00:46:45.920> to<00:46:46.119> us<00:46:47.079> thank<00:46:47.240> you<00:46:47.359> Albert 00:46:48.190 --> 00:46:48.200 align:start position:0% intelligences are to us thank you Albert 00:46:48.200 --> 00:46:49.589 align:start position:0% intelligences are to us thank you Albert um<00:46:48.359> reminder<00:46:48.760> that<00:46:48.880> you<00:46:48.960> can<00:46:49.040> scan<00:46:49.280> the<00:46:49.400> Cure 00:46:49.589 --> 00:46:49.599 align:start position:0% um reminder that you can scan the Cure 00:46:49.599 --> 00:46:50.870 align:start position:0% um reminder that you can scan the Cure code<00:46:49.800> to<00:46:49.880> ask<00:46:50.079> questions<00:46:50.319> we<00:46:50.440> still<00:46:50.559> have<00:46:50.680> two 00:46:50.870 --> 00:46:50.880 align:start position:0% code to ask questions we still have two 00:46:50.880 --> 00:46:52.190 align:start position:0% code to ask questions we still have two minutes<00:46:51.079> of<00:46:51.240> questions<00:46:51.520> so<00:46:51.720> many<00:46:51.920> things<00:46:52.079> you 00:46:52.190 --> 00:46:52.200 align:start position:0% minutes of questions so many things you 00:46:52.200 --> 00:46:54.470 align:start position:0% minutes of questions so many things you can<00:46:52.319> ask<00:46:52.640> Albert<00:46:53.640> um<00:46:53.880> there's<00:46:54.079> one<00:46:54.200> question 00:46:54.470 --> 00:46:54.480 align:start position:0% can ask Albert um there's one question 00:46:54.480 --> 00:46:56.190 align:start position:0% can ask Albert um there's one question one<00:46:54.800> vot<00:46:55.040> which<00:46:55.119> is<00:46:55.240> what's<00:46:55.400> your<00:46:55.599> suggestion 00:46:56.190 --> 00:46:56.200 align:start position:0% one vot which is what's your suggestion 00:46:56.200 --> 00:46:59.390 align:start position:0% one vot which is what's your suggestion for<00:46:56.400> individual<00:46:56.960> to<00:46:57.040> contribute<00:46:57.400> to<00:46:58.079> this<00:46:59.079> um 00:46:59.390 --> 00:46:59.400 align:start position:0% for individual to contribute to this um 00:46:59.400 --> 00:47:00.950 align:start position:0% for individual to contribute to this um so<00:46:59.640> this<00:46:59.760> can<00:46:59.920> mean<00:47:00.079> a<00:47:00.240> lot<00:47:00.359> of<00:47:00.520> things<00:47:00.839> right 00:47:00.950 --> 00:47:00.960 align:start position:0% so this can mean a lot of things right 00:47:00.960 --> 00:47:02.549 align:start position:0% so this can mean a lot of things right it<00:47:01.040> can<00:47:01.200> mean<00:47:01.640> you<00:47:01.760> know<00:47:01.920> a<00:47:02.040> lot<00:47:02.119> of<00:47:02.240> the<00:47:02.400> stuff 00:47:02.549 --> 00:47:02.559 align:start position:0% it can mean you know a lot of the stuff 00:47:02.559 --> 00:47:03.750 align:start position:0% it can mean you know a lot of the stuff that<00:47:02.680> people<00:47:02.839> are<00:47:02.960> showing<00:47:03.280> here<00:47:03.440> or<00:47:03.559> it<00:47:03.640> can 00:47:03.750 --> 00:47:03.760 align:start position:0% that people are showing here or it can 00:47:03.760 --> 00:47:05.630 align:start position:0% that people are showing here or it can mean<00:47:03.920> the<00:47:04.040> thing<00:47:04.200> that<00:47:04.359> I<00:47:04.480> just<00:47:04.640> talked<00:47:05.079> about 00:47:05.630 --> 00:47:05.640 align:start position:0% mean the thing that I just talked about 00:47:05.640 --> 00:47:07.230 align:start position:0% mean the thing that I just talked about but<00:47:05.880> I<00:47:06.000> will<00:47:06.240> actually<00:47:06.440> focus<00:47:06.720> on<00:47:06.839> what<00:47:06.960> I<00:47:07.119> just 00:47:07.230 --> 00:47:07.240 align:start position:0% but I will actually focus on what I just 00:47:07.240 --> 00:47:10.790 align:start position:0% but I will actually focus on what I just talked<00:47:07.520> about<00:47:08.000> I<00:47:08.520> I<00:47:08.680> think<00:47:09.680> as<00:47:10.079> simplistic<00:47:10.680> as 00:47:10.790 --> 00:47:10.800 align:start position:0% talked about I I think as simplistic as 00:47:10.800 --> 00:47:14.150 align:start position:0% talked about I I think as simplistic as it<00:47:11.359> sounds<00:47:12.359> my<00:47:12.559> goal<00:47:12.880> here<00:47:13.160> is<00:47:13.480> for<00:47:13.680> people<00:47:13.960> to 00:47:14.150 --> 00:47:14.160 align:start position:0% it sounds my goal here is for people to 00:47:14.160 --> 00:47:16.069 align:start position:0% it sounds my goal here is for people to recognize<00:47:14.920> that<00:47:15.240> sometimes<00:47:15.480> just<00:47:15.640> taking<00:47:15.920> a 00:47:16.069 --> 00:47:16.079 align:start position:0% recognize that sometimes just taking a 00:47:16.079 --> 00:47:18.349 align:start position:0% recognize that sometimes just taking a moment<00:47:16.359> to<00:47:16.599> think<00:47:16.800> about<00:47:17.200> things<00:47:18.000> can<00:47:18.160> be 00:47:18.349 --> 00:47:18.359 align:start position:0% moment to think about things can be 00:47:18.359 --> 00:47:20.510 align:start position:0% moment to think about things can be surprisingly<00:47:19.000> valuable<00:47:19.440> that<00:47:19.559> sounds<00:47:20.040> really 00:47:20.510 --> 00:47:20.520 align:start position:0% surprisingly valuable that sounds really 00:47:20.520 --> 00:47:22.430 align:start position:0% surprisingly valuable that sounds really obvious<00:47:21.040> and<00:47:21.200> yet<00:47:21.359> like<00:47:21.640> how<00:47:21.839> much<00:47:22.079> time<00:47:22.280> is 00:47:22.430 --> 00:47:22.440 align:start position:0% obvious and yet like how much time is 00:47:22.440 --> 00:47:25.030 align:start position:0% obvious and yet like how much time is spent<00:47:23.160> trying<00:47:23.720> to<00:47:24.040> just<00:47:24.200> take<00:47:24.359> a<00:47:24.480> moment<00:47:24.800> and 00:47:25.030 --> 00:47:25.040 align:start position:0% spent trying to just take a moment and 00:47:25.040 --> 00:47:27.470 align:start position:0% spent trying to just take a moment and think<00:47:25.839> and<00:47:26.359> the<00:47:26.520> talk<00:47:26.920> here<00:47:27.079> the<00:47:27.160> goal<00:47:27.359> of 00:47:27.470 --> 00:47:27.480 align:start position:0% think and the talk here the goal of 00:47:27.480 --> 00:47:29.670 align:start position:0% think and the talk here the goal of nothing<00:47:27.680> else<00:47:27.880> was<00:47:28.040> to<00:47:28.520> give<00:47:28.720> an<00:47:28.960> example<00:47:29.400> of 00:47:29.670 --> 00:47:29.680 align:start position:0% nothing else was to give an example of 00:47:29.680 --> 00:47:32.230 align:start position:0% nothing else was to give an example of how<00:47:29.800> many<00:47:30.040> directions<00:47:30.480> that<00:47:30.680> can<00:47:30.880> go<00:47:31.119> in<00:47:31.880> and 00:47:32.230 --> 00:47:32.240 align:start position:0% how many directions that can go in and 00:47:32.240 --> 00:47:33.270 align:start position:0% how many directions that can go in and and<00:47:32.359> not<00:47:32.520> in<00:47:32.599> a<00:47:32.720> way<00:47:32.839> where<00:47:32.920> I'm<00:47:33.040> like<00:47:33.200> I'm 00:47:33.270 --> 00:47:33.280 align:start position:0% and not in a way where I'm like I'm 00:47:33.280 --> 00:47:34.870 align:start position:0% and not in a way where I'm like I'm trying<00:47:33.440> to<00:47:33.640> convince<00:47:34.000> you<00:47:34.160> of<00:47:34.319> something<00:47:34.640> or 00:47:34.870 --> 00:47:34.880 align:start position:0% trying to convince you of something or 00:47:34.880 --> 00:47:36.910 align:start position:0% trying to convince you of something or or<00:47:35.240> sell<00:47:35.640> something<00:47:35.920> or<00:47:36.119> anything<00:47:36.400> else<00:47:36.680> like 00:47:36.910 --> 00:47:36.920 align:start position:0% or sell something or anything else like 00:47:36.920 --> 00:47:38.790 align:start position:0% or sell something or anything else like that<00:47:37.440> so<00:47:37.640> I<00:47:37.720> think<00:47:37.880> you<00:47:38.079> may<00:47:38.280> be<00:47:38.400> able<00:47:38.599> to 00:47:38.790 --> 00:47:38.800 align:start position:0% that so I think you may be able to 00:47:38.800 --> 00:47:41.870 align:start position:0% that so I think you may be able to contribute<00:47:39.440> more<00:47:39.640> than<00:47:39.800> you<00:47:40.079> expect<00:47:40.960> by<00:47:41.640> just 00:47:41.870 --> 00:47:41.880 align:start position:0% contribute more than you expect by just 00:47:41.880 --> 00:47:43.829 align:start position:0% contribute more than you expect by just taking<00:47:42.119> a<00:47:42.240> moment<00:47:42.520> to<00:47:42.720> think<00:47:43.040> about<00:47:43.520> what<00:47:43.680> you 00:47:43.829 --> 00:47:43.839 align:start position:0% taking a moment to think about what you 00:47:43.839 --> 00:47:45.750 align:start position:0% taking a moment to think about what you know<00:47:44.119> and<00:47:44.319> what<00:47:44.520> and<00:47:44.640> your<00:47:44.960> perspective<00:47:45.640> and 00:47:45.750 --> 00:47:45.760 align:start position:0% know and what and your perspective and 00:47:45.760 --> 00:47:47.710 align:start position:0% know and what and your perspective and see<00:47:46.000> how<00:47:46.200> that<00:47:46.400> might<00:47:46.680> intermingle<00:47:47.280> with 00:47:47.710 --> 00:47:47.720 align:start position:0% see how that might intermingle with 00:47:47.720 --> 00:47:49.430 align:start position:0% see how that might intermingle with stuff<00:47:48.160> as<00:47:48.280> for<00:47:48.520> other<00:47:48.720> ways<00:47:49.079> I<00:47:49.160> think<00:47:49.280> there's 00:47:49.430 --> 00:47:49.440 align:start position:0% stuff as for other ways I think there's 00:47:49.440 --> 00:47:50.750 align:start position:0% stuff as for other ways I think there's a<00:47:49.520> lot<00:47:49.640> of<00:47:49.800> great<00:47:49.960> opportunities<00:47:50.440> to<00:47:50.559> ask 00:47:50.750 --> 00:47:50.760 align:start position:0% a lot of great opportunities to ask 00:47:50.760 --> 00:47:52.910 align:start position:0% a lot of great opportunities to ask folks<00:47:51.119> about<00:47:51.359> that<00:47:51.559> overall<00:47:52.200> so<00:47:52.520> we'll<00:47:52.680> go<00:47:52.800> to 00:47:52.910 --> 00:47:52.920 align:start position:0% folks about that overall so we'll go to 00:47:52.920 --> 00:47:56.510 align:start position:0% folks about that overall so we'll go to the<00:47:53.040> next<00:47:53.240> one<00:47:53.880> thank<00:47:54.040> you<00:47:55.079> um<00:47:56.079> anyone<00:47:56.400> you 00:47:56.510 --> 00:47:56.520 align:start position:0% the next one thank you um anyone you 00:47:56.520 --> 00:47:58.390 align:start position:0% the next one thank you um anyone you care<00:47:56.680> more<00:47:56.839> more<00:47:57.000> about<00:47:57.440> what<00:47:57.559> you<00:47:57.640> want<00:47:57.760> to 00:47:58.390 --> 00:47:58.400 align:start position:0% care more more about what you want to 00:47:58.400 --> 00:48:02.270 align:start position:0% care more more about what you want to answer<00:47:59.599> um<00:48:00.599> sure<00:48:01.040> I'll<00:48:01.280> go<00:48:01.520> with<00:48:01.920> how<00:48:02.040> do<00:48:02.160> you 00:48:02.270 --> 00:48:02.280 align:start position:0% answer um sure I'll go with how do you 00:48:02.280 --> 00:48:03.710 align:start position:0% answer um sure I'll go with how do you see<00:48:02.520> cryptography<00:48:03.079> contributing<00:48:03.480> to<00:48:03.599> an 00:48:03.710 --> 00:48:03.720 align:start position:0% see cryptography contributing to an 00:48:03.720 --> 00:48:05.470 align:start position:0% see cryptography contributing to an Internet<00:48:04.040> that<00:48:04.160> is<00:48:04.280> joyful<00:48:04.800> symbiotic<00:48:05.280> and 00:48:05.470 --> 00:48:05.480 align:start position:0% Internet that is joyful symbiotic and 00:48:05.480 --> 00:48:07.670 align:start position:0% Internet that is joyful symbiotic and expansive<00:48:06.000> to<00:48:06.200> use<00:48:07.040> um<00:48:07.160> I<00:48:07.200> don't<00:48:07.359> have<00:48:07.480> much 00:48:07.670 --> 00:48:07.680 align:start position:0% expansive to use um I don't have much 00:48:07.680 --> 00:48:10.349 align:start position:0% expansive to use um I don't have much time<00:48:07.839> but<00:48:07.960> the<00:48:08.160> quick<00:48:08.480> answer<00:48:08.960> here<00:48:09.280> is<00:48:10.119> uh<00:48:10.240> the 00:48:10.349 --> 00:48:10.359 align:start position:0% time but the quick answer here is uh the 00:48:10.359 --> 00:48:11.870 align:start position:0% time but the quick answer here is uh the physical<00:48:10.680> world<00:48:10.920> has<00:48:11.000> a<00:48:11.119> lot<00:48:11.240> of<00:48:11.480> properties 00:48:11.870 --> 00:48:11.880 align:start position:0% physical world has a lot of properties 00:48:11.880 --> 00:48:13.910 align:start position:0% physical world has a lot of properties we<00:48:12.040> take<00:48:12.200> for<00:48:12.400> granted<00:48:13.000> and<00:48:13.200> if<00:48:13.400> nothing<00:48:13.680> else 00:48:13.910 --> 00:48:13.920 align:start position:0% we take for granted and if nothing else 00:48:13.920 --> 00:48:16.190 align:start position:0% we take for granted and if nothing else we're<00:48:14.200> evolved<00:48:15.000> to<00:48:15.240> like<00:48:15.359> Orient<00:48:15.760> around<00:48:16.000> that 00:48:16.190 --> 00:48:16.200 align:start position:0% we're evolved to like Orient around that 00:48:16.200 --> 00:48:17.349 align:start position:0% we're evolved to like Orient around that even<00:48:16.359> the<00:48:16.520> fact<00:48:16.680> that<00:48:16.880> like<00:48:17.000> non-f 00:48:17.349 --> 00:48:17.359 align:start position:0% even the fact that like non-f 00:48:17.359 --> 00:48:19.309 align:start position:0% even the fact that like non-f fungibility<00:48:18.040> is<00:48:18.200> like<00:48:18.440> default<00:48:18.880> on<00:48:19.119> in<00:48:19.200> the 00:48:19.309 --> 00:48:19.319 align:start position:0% fungibility is like default on in the 00:48:19.319 --> 00:48:20.790 align:start position:0% fungibility is like default on in the physical<00:48:19.680> world<00:48:20.160> and<00:48:20.280> we<00:48:20.359> need<00:48:20.559> like 00:48:20.790 --> 00:48:20.800 align:start position:0% physical world and we need like 00:48:20.800 --> 00:48:22.589 align:start position:0% physical world and we need like sophisticated<00:48:21.480> constructions<00:48:22.200> to<00:48:22.359> make 00:48:22.589 --> 00:48:22.599 align:start position:0% sophisticated constructions to make 00:48:22.599 --> 00:48:24.390 align:start position:0% sophisticated constructions to make things<00:48:22.880> like<00:48:23.200> essentially<00:48:23.640> fungible<00:48:24.280> like 00:48:24.390 --> 00:48:24.400 align:start position:0% things like essentially fungible like 00:48:24.400 --> 00:48:27.030 align:start position:0% things like essentially fungible like words<00:48:24.680> are<00:48:24.920> fungible<00:48:25.480> in<00:48:25.599> a<00:48:25.800> sense<00:48:26.400> to<00:48:26.800> apples 00:48:27.030 --> 00:48:27.040 align:start position:0% words are fungible in a sense to apples 00:48:27.040 --> 00:48:28.309 align:start position:0% words are fungible in a sense to apples are<00:48:27.160> more<00:48:27.280> or<00:48:27.440> less<00:48:27.599> fungible<00:48:28.079> that's<00:48:28.160> only 00:48:28.309 --> 00:48:28.319 align:start position:0% are more or less fungible that's only 00:48:28.319 --> 00:48:29.190 align:start position:0% are more or less fungible that's only because<00:48:28.440> we've<00:48:28.599> gotten<00:48:28.760> good<00:48:28.880> at<00:48:29.000> putting 00:48:29.190 --> 00:48:29.200 align:start position:0% because we've gotten good at putting 00:48:29.200 --> 00:48:31.030 align:start position:0% because we've gotten good at putting them<00:48:29.280> all<00:48:29.400> in<00:48:29.480> a<00:48:29.680> market<00:48:30.079> and<00:48:30.240> so<00:48:30.400> on<00:48:30.880> the 00:48:31.030 --> 00:48:31.040 align:start position:0% them all in a market and so on the 00:48:31.040 --> 00:48:32.510 align:start position:0% them all in a market and so on the digital<00:48:31.359> world<00:48:31.599> has<00:48:31.760> like<00:48:31.880> these<00:48:32.079> inversion 00:48:32.510 --> 00:48:32.520 align:start position:0% digital world has like these inversion 00:48:32.520 --> 00:48:34.549 align:start position:0% digital world has like these inversion of<00:48:32.640> a<00:48:32.760> lot<00:48:32.880> of<00:48:33.079> properties<00:48:33.839> so<00:48:34.000> if<00:48:34.240> nothing 00:48:34.549 --> 00:48:34.559 align:start position:0% of a lot of properties so if nothing 00:48:34.559 --> 00:48:36.950 align:start position:0% of a lot of properties so if nothing else<00:48:35.000> I<00:48:35.079> think<00:48:35.680> cryptography<00:48:36.680> uh<00:48:36.800> is 00:48:36.950 --> 00:48:36.960 align:start position:0% else I think cryptography uh is 00:48:36.960 --> 00:48:38.710 align:start position:0% else I think cryptography uh is underrated<00:48:37.599> its<00:48:37.760> potential<00:48:38.079> to<00:48:38.240> enrich 00:48:38.710 --> 00:48:38.720 align:start position:0% underrated its potential to enrich 00:48:38.720 --> 00:48:41.309 align:start position:0% underrated its potential to enrich because<00:48:39.040> it's<00:48:39.200> a<00:48:39.480> way<00:48:39.720> for<00:48:39.960> us<00:48:40.160> to<00:48:40.800> imbue<00:48:41.200> the 00:48:41.309 --> 00:48:41.319 align:start position:0% because it's a way for us to imbue the 00:48:41.319 --> 00:48:42.870 align:start position:0% because it's a way for us to imbue the digital<00:48:41.680> world<00:48:41.960> with<00:48:42.160> physical<00:48:42.480> world 00:48:42.870 --> 00:48:42.880 align:start position:0% digital world with physical world 00:48:42.880 --> 00:48:44.670 align:start position:0% digital world with physical world properties<00:48:43.640> and<00:48:43.760> that's<00:48:44.079> a<00:48:44.200> lens<00:48:44.440> that<00:48:44.599> I 00:48:44.670 --> 00:48:44.680 align:start position:0% properties and that's a lens that I 00:48:44.680 --> 00:48:46.270 align:start position:0% properties and that's a lens that I think<00:48:44.839> we<00:48:45.000> haven't<00:48:45.359> really<00:48:45.640> explored<00:48:46.079> much 00:48:46.270 --> 00:48:46.280 align:start position:0% think we haven't really explored much 00:48:46.280 --> 00:48:47.430 align:start position:0% think we haven't really explored much yet<00:48:46.440> yeah<00:48:46.559> there's<00:48:46.720> the<00:48:46.800> fungibility 00:48:47.430 --> 00:48:47.440 align:start position:0% yet yeah there's the fungibility 00:48:47.440 --> 00:48:49.230 align:start position:0% yet yeah there's the fungibility scarcity<00:48:48.040> stuff<00:48:48.440> but<00:48:48.559> I<00:48:48.640> think<00:48:48.800> there's<00:48:48.960> a<00:48:49.079> lot 00:48:49.230 --> 00:48:49.240 align:start position:0% scarcity stuff but I think there's a lot 00:48:49.240 --> 00:48:51.069 align:start position:0% scarcity stuff but I think there's a lot more<00:48:49.400> to<00:48:49.599> go<00:48:49.760> in<00:48:49.920> that<00:48:50.119> direction<00:48:50.839> thank<00:48:50.960> you 00:48:51.069 --> 00:48:51.079 align:start position:0% more to go in that direction thank you 00:48:51.079 --> 00:48:52.789 align:start position:0% more to go in that direction thank you Albert<00:48:51.599> thank<00:48:51.760> you<00:48:52.200> another<00:48:52.480> round<00:48:52.640> of 00:48:52.789 --> 00:48:52.799 align:start position:0% Albert thank you another round of 00:48:52.799 --> 00:48:59.349 align:start position:0% Albert thank you another round of applause<00:48:53.079> for<00:48:53.200> Albert<00:48:53.559> please<00:48:53.839> thank<00:48:54.000> you 00:48:59.349 --> 00:48:59.359 align:start position:0% 00:48:59.359 --> 00:49:00.910 align:start position:0% all<00:48:59.520> right<00:48:59.680> so<00:48:59.799> we<00:48:59.920> have<00:49:00.000> a<00:49:00.160> special<00:49:00.480> treat 00:49:00.910 --> 00:49:00.920 align:start position:0% all right so we have a special treat 00:49:00.920 --> 00:49:03.190 align:start position:0% all right so we have a special treat next<00:49:01.280> our<00:49:01.480> next<00:49:01.680> speaker<00:49:02.000> is<00:49:02.200> Barry<00:49:02.559> White<00:49:02.920> Hat 00:49:03.190 --> 00:49:03.200 align:start position:0% next our next speaker is Barry White Hat 00:49:03.200 --> 00:49:06.510 align:start position:0% next our next speaker is Barry White Hat a<00:49:03.760> self-proclaimed<00:49:04.760> Street<00:49:05.319> cryptographer<00:49:06.319> a 00:49:06.510 --> 00:49:06.520 align:start position:0% a self-proclaimed Street cryptographer a 00:49:06.520 --> 00:49:08.470 align:start position:0% a self-proclaimed Street cryptographer a longtime<00:49:07.040> collaborator<00:49:07.640> with<00:49:07.799> the<00:49:07.920> EF<00:49:08.319> and 00:49:08.470 --> 00:49:08.480 align:start position:0% longtime collaborator with the EF and 00:49:08.480 --> 00:49:11.430 align:start position:0% longtime collaborator with the EF and zerox<00:49:08.920> Spark<00:49:09.720> Barry<00:49:10.079> will<00:49:10.440> wideboard<00:49:11.000> out<00:49:11.200> his 00:49:11.430 --> 00:49:11.440 align:start position:0% zerox Spark Barry will wideboard out his 00:49:11.440 --> 00:49:13.910 align:start position:0% zerox Spark Barry will wideboard out his thoughts<00:49:11.760> on<00:49:11.920> how<00:49:12.079> to<00:49:12.280> build<00:49:12.599> with<00:49:13.160> IO<00:49:13.720> and 00:49:13.910 --> 00:49:13.920 align:start position:0% thoughts on how to build with IO and 00:49:13.920 --> 00:49:16.150 align:start position:0% thoughts on how to build with IO and more<00:49:14.799> um<00:49:15.000> I<00:49:15.119> always<00:49:15.319> a<00:49:15.440> treat<00:49:15.680> to<00:49:15.799> hear<00:49:16.040> what 00:49:16.150 --> 00:49:16.160 align:start position:0% more um I always a treat to hear what 00:49:16.160 --> 00:49:18.030 align:start position:0% more um I always a treat to hear what he's<00:49:16.359> cooking<00:49:16.680> up<00:49:17.200> please<00:49:17.559> welcome<00:49:17.839> to<00:49:17.920> the 00:49:18.030 --> 00:49:18.040 align:start position:0% he's cooking up please welcome to the 00:49:18.040 --> 00:49:20.560 align:start position:0% he's cooking up please welcome to the stage<00:49:18.280> Barry<00:49:18.559> White<00:49:18.799> hat<00:49:19.000> thank 00:49:20.560 --> 00:49:20.570 align:start position:0% stage Barry White hat thank 00:49:20.570 --> 00:49:25.470 align:start position:0% stage Barry White hat thank [Applause] 00:49:25.470 --> 00:49:25.480 align:start position:0% 00:49:25.480 --> 00:49:28.910 align:start position:0% you<00:49:26.480> okay<00:49:26.760> folks<00:49:27.359> uh<00:49:27.480> can<00:49:27.559> you<00:49:27.680> hear 00:49:28.910 --> 00:49:28.920 align:start position:0% you okay folks uh can you hear 00:49:28.920 --> 00:49:31.549 align:start position:0% you okay folks uh can you hear me<00:49:29.920> okay<00:49:30.760> okay<00:49:30.880> we're<00:49:31.000> going<00:49:31.119> to<00:49:31.240> do<00:49:31.359> some 00:49:31.549 --> 00:49:31.559 align:start position:0% me okay okay we're going to do some 00:49:31.559 --> 00:49:34.829 align:start position:0% me okay okay we're going to do some whiteboarding<00:49:32.280> stuff<00:49:33.280> um<00:49:33.960> so<00:49:34.200> like<00:49:34.400> basically 00:49:34.829 --> 00:49:34.839 align:start position:0% whiteboarding stuff um so like basically 00:49:34.839 --> 00:49:37.430 align:start position:0% whiteboarding stuff um so like basically the<00:49:35.040> plan<00:49:35.280> for<00:49:35.480> today<00:49:35.960> is<00:49:36.119> to<00:49:36.599> like<00:49:36.839> architect 00:49:37.430 --> 00:49:37.440 align:start position:0% the plan for today is to like architect 00:49:37.440 --> 00:49:39.069 align:start position:0% the plan for today is to like architect some<00:49:37.640> simple<00:49:38.000> things<00:49:38.240> using 00:49:39.069 --> 00:49:39.079 align:start position:0% some simple things using 00:49:39.079 --> 00:49:42.710 align:start position:0% some simple things using IO<00:49:40.079> um<00:49:40.400> can<00:49:40.480> I<00:49:40.599> turn<00:49:40.799> this<00:49:41.000> around<00:49:41.680> so<00:49:41.920> like<00:49:42.440> do 00:49:42.710 --> 00:49:42.720 align:start position:0% IO um can I turn this around so like do 00:49:42.720 --> 00:49:43.829 align:start position:0% IO um can I turn this around so like do people<00:49:42.960> have<00:49:43.119> things<00:49:43.280> that<00:49:43.440> they<00:49:43.520> would<00:49:43.680> want 00:49:43.829 --> 00:49:43.839 align:start position:0% people have things that they would want 00:49:43.839 --> 00:49:45.990 align:start position:0% people have things that they would want to<00:49:44.040> architect<00:49:44.640> so<00:49:44.920> like<00:49:45.400> a<00:49:45.520> couple<00:49:45.720> of<00:49:45.839> things 00:49:45.990 --> 00:49:46.000 align:start position:0% to architect so like a couple of things 00:49:46.000 --> 00:49:47.549 align:start position:0% to architect so like a couple of things I<00:49:46.079> was<00:49:46.200> thinking<00:49:46.440> about<00:49:46.640> doing<00:49:46.920> is<00:49:47.160> like<00:49:47.400> how 00:49:47.549 --> 00:49:47.559 align:start position:0% I was thinking about doing is like how 00:49:47.559 --> 00:49:50.230 align:start position:0% I was thinking about doing is like how to<00:49:47.720> do<00:49:47.920> is<00:49:48.240> how<00:49:48.359> to<00:49:49.160> how<00:49:49.280> to<00:49:49.599> oh<00:49:49.799> p<00:49:50.000> goes<00:49:50.119> the 00:49:50.230 --> 00:49:50.240 align:start position:0% to do is how to how to oh p goes the 00:49:50.240 --> 00:49:53.030 align:start position:0% to do is how to how to oh p goes the other<00:49:50.440> way<00:49:51.240> how<00:49:51.400> to<00:49:51.640> use<00:49:52.280> uh<00:49:52.400> zero<00:49:52.720> knowledge 00:49:53.030 --> 00:49:53.040 align:start position:0% other way how to use uh zero knowledge 00:49:53.040 --> 00:49:56.309 align:start position:0% other way how to use uh zero knowledge how<00:49:53.160> to<00:49:53.280> use<00:49:53.520> IO<00:49:54.359> to<00:49:55.359> uh<00:49:55.799> to<00:49:55.960> make<00:49:56.119> zero 00:49:56.309 --> 00:49:56.319 align:start position:0% how to use IO to uh to make zero 00:49:56.319 --> 00:49:57.430 align:start position:0% how to use IO to uh to make zero knowledge<00:49:56.680> group<00:49:56.880> that<00:49:56.960> are<00:49:57.079> just<00:49:57.200> like<00:49:57.319> a 00:49:57.430 --> 00:49:57.440 align:start position:0% knowledge group that are just like a 00:49:57.440 --> 00:49:59.349 align:start position:0% knowledge group that are just like a single<00:49:57.799> signature<00:49:58.240> to<00:49:58.400> verify<00:49:59.040> so<00:49:59.160> you<00:49:59.240> have 00:49:59.349 --> 00:49:59.359 align:start position:0% single signature to verify so you have 00:49:59.359 --> 00:50:01.230 align:start position:0% single signature to verify so you have this<00:49:59.520> iio<00:49:59.799> box<00:50:00.119> it<00:50:00.280> it<00:50:00.400> does<00:50:00.640> some<00:50:00.920> stuff<00:50:01.160> and 00:50:01.230 --> 00:50:01.240 align:start position:0% this iio box it it does some stuff and 00:50:01.240 --> 00:50:02.750 align:start position:0% this iio box it it does some stuff and it's<00:50:01.400> bits<00:50:01.599> out<00:50:01.720> of<00:50:01.839> signature<00:50:02.319> and<00:50:02.480> like<00:50:02.599> once 00:50:02.750 --> 00:50:02.760 align:start position:0% it's bits out of signature and like once 00:50:02.760 --> 00:50:04.430 align:start position:0% it's bits out of signature and like once you<00:50:02.880> check<00:50:03.040> the<00:50:03.160> signatures<00:50:03.640> it's<00:50:03.839> enough 00:50:04.430 --> 00:50:04.440 align:start position:0% you check the signatures it's enough 00:50:04.440 --> 00:50:06.589 align:start position:0% you check the signatures it's enough it's<00:50:04.680> enough<00:50:04.880> to<00:50:05.160> say<00:50:05.559> to<00:50:05.839> to<00:50:06.079> to<00:50:06.240> know<00:50:06.440> that 00:50:06.589 --> 00:50:06.599 align:start position:0% it's enough to say to to to know that 00:50:06.599 --> 00:50:08.430 align:start position:0% it's enough to say to to to know that that<00:50:06.760> computation<00:50:07.200> was<00:50:07.319> done<00:50:07.520> correctly<00:50:08.280> so 00:50:08.430 --> 00:50:08.440 align:start position:0% that computation was done correctly so 00:50:08.440 --> 00:50:10.470 align:start position:0% that computation was done correctly so that's<00:50:08.599> one<00:50:08.720> thing<00:50:08.880> that<00:50:09.000> we<00:50:09.119> could<00:50:09.280> do<00:50:10.280> other 00:50:10.470 --> 00:50:10.480 align:start position:0% that's one thing that we could do other 00:50:10.480 --> 00:50:14.990 align:start position:0% that's one thing that we could do other things<00:50:10.680> we<00:50:10.799> could<00:50:10.960> do<00:50:11.119> is<00:50:11.280> like<00:50:11.559> uh<00:50:12.119> uh<00:50:12.319> trusted 00:50:14.990 --> 00:50:15.000 align:start position:0% 00:50:15.000 --> 00:50:18.069 align:start position:0% setup<00:50:16.200> uh<00:50:17.200> other<00:50:17.440> things<00:50:17.599> we<00:50:17.680> could<00:50:17.799> do<00:50:17.880> is<00:50:18.000> we 00:50:18.069 --> 00:50:18.079 align:start position:0% setup uh other things we could do is we 00:50:18.079 --> 00:50:19.750 align:start position:0% setup uh other things we could do is we could<00:50:18.160> do<00:50:18.319> like<00:50:18.440> a<00:50:18.599> Bitcoin<00:50:19.119> Bridge<00:50:19.480> which<00:50:19.559> is 00:50:19.750 --> 00:50:19.760 align:start position:0% could do like a Bitcoin Bridge which is 00:50:19.760 --> 00:50:21.109 align:start position:0% could do like a Bitcoin Bridge which is kind 00:50:21.109 --> 00:50:21.119 align:start position:0% kind 00:50:21.119 --> 00:50:23.950 align:start position:0% kind of<00:50:22.119> more<00:50:22.359> blockchain 00:50:23.950 --> 00:50:23.960 align:start position:0% of more blockchain 00:50:23.960 --> 00:50:27.309 align:start position:0% of more blockchain e<00:50:24.960> uh<00:50:25.799> anything<00:50:26.079> else<00:50:26.280> people<00:50:26.440> want<00:50:26.880> do<00:50:27.200> this 00:50:27.309 --> 00:50:27.319 align:start position:0% e uh anything else people want do this 00:50:27.319 --> 00:50:28.670 align:start position:0% e uh anything else people want do this is<00:50:27.440> supposed<00:50:27.640> to<00:50:27.760> be<00:50:27.920> like<00:50:28.040> interactive<00:50:28.559> so 00:50:28.670 --> 00:50:28.680 align:start position:0% is supposed to be like interactive so 00:50:28.680 --> 00:50:30.109 align:start position:0% is supposed to be like interactive so feel<00:50:28.880> free<00:50:29.040> to<00:50:29.240> like<00:50:29.319> shout<00:50:29.640> stuff<00:50:29.799> out<00:50:29.960> and 00:50:30.109 --> 00:50:30.119 align:start position:0% feel free to like shout stuff out and 00:50:30.119 --> 00:50:32.150 align:start position:0% feel free to like shout stuff out and interrupt<00:50:30.520> me<00:50:30.880> like<00:50:31.440> I<00:50:31.640> I<00:50:31.680> want<00:50:31.799> to<00:50:31.920> have<00:50:32.000> more 00:50:32.150 --> 00:50:32.160 align:start position:0% interrupt me like I I want to have more 00:50:32.160 --> 00:50:34.230 align:start position:0% interrupt me like I I want to have more of<00:50:32.319> like<00:50:32.400> a<00:50:32.559> conversation<00:50:33.119> here<00:50:33.440> than<00:50:33.760> like<00:50:33.960> a 00:50:34.230 --> 00:50:34.240 align:start position:0% of like a conversation here than like a 00:50:34.240 --> 00:50:36.030 align:start position:0% of like a conversation here than like a a<00:50:34.359> presentation<00:50:35.280> your<00:50:35.440> thoughts<00:50:35.680> and<00:50:35.799> send 00:50:36.030 --> 00:50:36.040 align:start position:0% a presentation your thoughts and send 00:50:36.040 --> 00:50:38.750 align:start position:0% a presentation your thoughts and send them<00:50:36.200> as<00:50:36.359> nutr<00:50:36.960> across<00:50:37.240> the<00:50:37.359> Galaxy<00:50:38.119> oh<00:50:38.359> no 00:50:38.750 --> 00:50:38.760 align:start position:0% them as nutr across the Galaxy oh no 00:50:38.760 --> 00:50:40.549 align:start position:0% them as nutr across the Galaxy oh no that's<00:50:38.960> too<00:50:39.200> much<00:50:39.799> can<00:50:39.920> I<00:50:40.040> encrypt<00:50:40.400> my 00:50:40.549 --> 00:50:40.559 align:start position:0% that's too much can I encrypt my 00:50:40.559 --> 00:50:41.950 align:start position:0% that's too much can I encrypt my thoughts<00:50:40.760> and<00:50:40.880> send<00:50:41.079> them<00:50:41.240> as<00:50:41.359> neutrinos 00:50:41.950 --> 00:50:41.960 align:start position:0% thoughts and send them as neutrinos 00:50:41.960 --> 00:50:48.109 align:start position:0% thoughts and send them as neutrinos across<00:50:42.200> the<00:50:42.839> Galaxy<00:50:43.839> uh<00:50:44.079> not 00:50:48.109 --> 00:50:48.119 align:start position:0% 00:50:48.119 --> 00:50:52.030 align:start position:0% today<00:50:49.119> anything<00:50:49.480> else<00:50:50.440> okay<00:50:50.760> well<00:50:51.760> if<00:50:51.880> there's 00:50:52.030 --> 00:50:52.040 align:start position:0% today anything else okay well if there's 00:50:52.040 --> 00:50:54.789 align:start position:0% today anything else okay well if there's nothing<00:50:52.400> like<00:50:52.599> just<00:50:52.799> shout<00:50:53.079> at<00:50:53.240> me<00:50:53.599> later<00:50:54.599> I'll 00:50:54.789 --> 00:50:54.799 align:start position:0% nothing like just shout at me later I'll 00:50:54.799 --> 00:50:56.750 align:start position:0% nothing like just shout at me later I'll ask<00:50:54.960> you<00:50:55.119> again<00:50:55.280> in<00:50:55.359> a<00:50:55.520> while<00:50:56.200> so<00:50:56.480> let<00:50:56.640> let<00:50:56.680> me 00:50:56.750 --> 00:50:56.760 align:start position:0% ask you again in a while so let let me 00:50:56.760 --> 00:50:58.150 align:start position:0% ask you again in a while so let let me turn<00:50:57.160> this 00:50:58.150 --> 00:50:58.160 align:start position:0% turn this 00:50:58.160 --> 00:51:00.950 align:start position:0% turn this around<00:50:59.160> oh<00:50:59.400> yeah<00:50:59.559> it's 00:51:00.950 --> 00:51:00.960 align:start position:0% around oh yeah it's 00:51:00.960 --> 00:51:04.069 align:start position:0% around oh yeah it's okay<00:51:01.960> okay<00:51:02.119> so<00:51:02.400> basically<00:51:02.920> the<00:51:03.079> toolbox<00:51:03.559> of<00:51:03.720> IO 00:51:04.069 --> 00:51:04.079 align:start position:0% okay okay so basically the toolbox of IO 00:51:04.079 --> 00:51:06.030 align:start position:0% okay okay so basically the toolbox of IO is<00:51:04.200> that<00:51:04.319> we<00:51:04.440> have<00:51:04.720> like<00:51:04.839> some<00:51:05.119> program<00:51:05.920> that 00:51:06.030 --> 00:51:06.040 align:start position:0% is that we have like some program that 00:51:06.040 --> 00:51:07.950 align:start position:0% is that we have like some program that we<00:51:06.280> express<00:51:06.720> as<00:51:06.960> like 00:51:07.950 --> 00:51:07.960 align:start position:0% we express as like 00:51:07.960 --> 00:51:12.030 align:start position:0% we express as like Gates<00:51:08.960> and<00:51:09.119> we<00:51:09.240> have<00:51:09.359> some<00:51:09.599> ins<00:51:10.200> and<00:51:10.319> some<00:51:11.040> outs 00:51:12.030 --> 00:51:12.040 align:start position:0% Gates and we have some ins and some outs 00:51:12.040 --> 00:51:14.470 align:start position:0% Gates and we have some ins and some outs and<00:51:12.160> then<00:51:12.280> we<00:51:12.400> do<00:51:12.680> like<00:51:12.880> the<00:51:13.119> io 00:51:14.470 --> 00:51:14.480 align:start position:0% and then we do like the io 00:51:14.480 --> 00:51:17.549 align:start position:0% and then we do like the io thing<00:51:15.480> we<00:51:15.599> do<00:51:15.799> this<00:51:16.040> IO<00:51:16.520> kind<00:51:16.680> of<00:51:16.960> like<00:51:17.200> almost 00:51:17.549 --> 00:51:17.559 align:start position:0% thing we do this IO kind of like almost 00:51:17.559 --> 00:51:19.789 align:start position:0% thing we do this IO kind of like almost like<00:51:17.760> encryption<00:51:18.319> step<00:51:19.040> and<00:51:19.160> on<00:51:19.319> the<00:51:19.480> other 00:51:19.789 --> 00:51:19.799 align:start position:0% like encryption step and on the other 00:51:19.799 --> 00:51:22.150 align:start position:0% like encryption step and on the other side<00:51:20.040> we<00:51:20.200> get<00:51:20.480> like<00:51:20.799> a<00:51:20.920> whole<00:51:21.160> bunch<00:51:21.480> of<00:51:22.040> a 00:51:22.150 --> 00:51:22.160 align:start position:0% side we get like a whole bunch of a 00:51:22.160 --> 00:51:25.109 align:start position:0% side we get like a whole bunch of a whole<00:51:22.400> bunch<00:51:22.680> more<00:51:23.119> Gates<00:51:24.119> or<00:51:24.319> more<00:51:24.839> more 00:51:25.109 --> 00:51:25.119 align:start position:0% whole bunch more Gates or more more 00:51:25.119 --> 00:51:26.990 align:start position:0% whole bunch more Gates or more more information<00:51:25.920> and<00:51:26.040> it<00:51:26.160> still<00:51:26.359> has<00:51:26.640> ins<00:51:26.839> and 00:51:26.990 --> 00:51:27.000 align:start position:0% information and it still has ins and 00:51:27.000 --> 00:51:30.030 align:start position:0% information and it still has ins and outs<00:51:27.839> but<00:51:28.280> the<00:51:29.200> like<00:51:29.359> what's<00:51:29.599> happening<00:51:29.920> in 00:51:30.030 --> 00:51:30.040 align:start position:0% outs but the like what's happening in 00:51:30.040 --> 00:51:32.349 align:start position:0% outs but the like what's happening in the<00:51:30.160> middle<00:51:31.000> is<00:51:31.400> impossible<00:51:31.920> for<00:51:32.040> us<00:51:32.200> to 00:51:32.349 --> 00:51:32.359 align:start position:0% the middle is impossible for us to 00:51:32.359 --> 00:51:35.589 align:start position:0% the middle is impossible for us to figure<00:51:32.640> out<00:51:33.559> so<00:51:34.119> this<00:51:34.880> you<00:51:35.000> can<00:51:35.160> think<00:51:35.319> of<00:51:35.480> this 00:51:35.589 --> 00:51:35.599 align:start position:0% figure out so this you can think of this 00:51:35.599 --> 00:51:37.710 align:start position:0% figure out so this you can think of this as<00:51:35.760> like<00:51:35.880> an<00:51:36.040> encryption<00:51:36.599> step<00:51:37.079> that<00:51:37.280> takes<00:51:37.480> a 00:51:37.710 --> 00:51:37.720 align:start position:0% as like an encryption step that takes a 00:51:37.720 --> 00:51:40.510 align:start position:0% as like an encryption step that takes a program<00:51:38.440> it<00:51:38.599> encrypts<00:51:39.079> the<00:51:39.319> program<00:51:40.160> such 00:51:40.510 --> 00:51:40.520 align:start position:0% program it encrypts the program such 00:51:40.520 --> 00:51:41.950 align:start position:0% program it encrypts the program such that<00:51:41.160> the 00:51:41.950 --> 00:51:41.960 align:start position:0% that the 00:51:41.960 --> 00:51:45.549 align:start position:0% that the output<00:51:42.960> is<00:51:43.240> like<00:51:43.640> unknowable<00:51:44.480> it's<00:51:45.160> like<00:51:45.359> all 00:51:45.549 --> 00:51:45.559 align:start position:0% output is like unknowable it's like all 00:51:45.559 --> 00:51:47.750 align:start position:0% output is like unknowable it's like all you<00:51:45.720> can<00:51:46.319> all<00:51:46.480> you<00:51:46.599> can<00:51:46.760> do<00:51:46.920> is<00:51:47.119> like<00:51:47.280> put<00:51:47.480> stuff 00:51:47.750 --> 00:51:47.760 align:start position:0% you can all you can do is like put stuff 00:51:47.760 --> 00:51:48.990 align:start position:0% you can all you can do is like put stuff in<00:51:48.040> and<00:51:48.200> get<00:51:48.359> the 00:51:48.990 --> 00:51:49.000 align:start position:0% in and get the 00:51:49.000 --> 00:51:51.789 align:start position:0% in and get the outs<00:51:50.000> and<00:51:50.119> you<00:51:50.280> can<00:51:50.559> like<00:51:51.000> see<00:51:51.400> stuff<00:51:51.640> that's 00:51:51.789 --> 00:51:51.799 align:start position:0% outs and you can like see stuff that's 00:51:51.799 --> 00:51:53.750 align:start position:0% outs and you can like see stuff that's going<00:51:52.040> in<00:51:52.160> and<00:51:52.359> coming<00:51:52.599> out<00:51:53.160> but<00:51:53.280> you<00:51:53.480> can't 00:51:53.750 --> 00:51:53.760 align:start position:0% going in and coming out but you can't 00:51:53.760 --> 00:51:55.910 align:start position:0% going in and coming out but you can't figure<00:51:54.040> out<00:51:54.400> like<00:51:54.960> what<00:51:55.160> the<00:51:55.400> original 00:51:55.910 --> 00:51:55.920 align:start position:0% figure out like what the original 00:51:55.920 --> 00:51:57.910 align:start position:0% figure out like what the original program<00:51:56.280> is 00:51:57.910 --> 00:51:57.920 align:start position:0% program is 00:51:57.920 --> 00:52:00.430 align:start position:0% program is uh<00:51:58.040> so<00:51:58.280> one<00:51:58.559> example<00:51:59.200> of<00:51:59.520> this<00:51:59.960> okay<00:52:00.079> so<00:52:00.240> let's 00:52:00.430 --> 00:52:00.440 align:start position:0% uh so one example of this okay so let's 00:52:00.440 --> 00:52:02.510 align:start position:0% uh so one example of this okay so let's take<00:52:00.640> like<00:52:00.760> a<00:52:00.960> really<00:52:01.200> simple<00:52:01.599> example<00:52:02.359> and 00:52:02.510 --> 00:52:02.520 align:start position:0% take like a really simple example and 00:52:02.520 --> 00:52:04.309 align:start position:0% take like a really simple example and let's<00:52:02.720> say<00:52:02.960> that<00:52:03.079> our<00:52:03.400> gate<00:52:03.720> here<00:52:03.920> is<00:52:04.119> just 00:52:04.309 --> 00:52:04.319 align:start position:0% let's say that our gate here is just 00:52:04.319 --> 00:52:05.430 align:start position:0% let's say that our gate here is just like 00:52:05.430 --> 00:52:05.440 align:start position:0% like 00:52:05.440 --> 00:52:08.030 align:start position:0% like a<00:52:06.440> uh<00:52:06.760> and 00:52:08.030 --> 00:52:08.040 align:start position:0% a uh and 00:52:08.040 --> 00:52:10.309 align:start position:0% a uh and gate<00:52:09.040> yeah<00:52:09.200> so<00:52:09.359> we<00:52:09.440> have<00:52:09.559> a<00:52:09.720> really<00:52:09.960> simple 00:52:10.309 --> 00:52:10.319 align:start position:0% gate yeah so we have a really simple 00:52:10.319 --> 00:52:12.430 align:start position:0% gate yeah so we have a really simple program<00:52:10.880> as<00:52:10.960> an<00:52:11.119> and<00:52:11.400> gate<00:52:11.920> and<00:52:12.040> we<00:52:12.160> put<00:52:12.319> it 00:52:12.430 --> 00:52:12.440 align:start position:0% program as an and gate and we put it 00:52:12.440 --> 00:52:17.190 align:start position:0% program as an and gate and we put it into<00:52:12.680> our<00:52:12.960> IO<00:52:13.280> encryption 00:52:17.190 --> 00:52:17.200 align:start position:0% 00:52:17.200 --> 00:52:20.390 align:start position:0% box<00:52:18.200> IO<00:52:19.119> and<00:52:19.240> then<00:52:19.359> we<00:52:19.480> get<00:52:19.720> out<00:52:20.040> this<00:52:20.240> like 00:52:20.390 --> 00:52:20.400 align:start position:0% box IO and then we get out this like 00:52:20.400 --> 00:52:23.589 align:start position:0% box IO and then we get out this like more<00:52:20.720> complicated 00:52:23.589 --> 00:52:23.599 align:start position:0% 00:52:23.599 --> 00:52:26.069 align:start position:0% representation<00:52:24.599> right<00:52:25.160> so<00:52:25.359> this<00:52:25.440> is<00:52:25.799> this<00:52:25.880> is 00:52:26.069 --> 00:52:26.079 align:start position:0% representation right so this is this is 00:52:26.079 --> 00:52:28.309 align:start position:0% representation right so this is this is also<00:52:26.559> just<00:52:26.720> like<00:52:26.799> a<00:52:26.960> list<00:52:27.240> of<00:52:27.520> like<00:52:27.760> operations 00:52:28.309 --> 00:52:28.319 align:start position:0% also just like a list of like operations 00:52:28.319 --> 00:52:30.950 align:start position:0% also just like a list of like operations like<00:52:28.520> M<00:52:28.839> maybe<00:52:29.040> it's<00:52:29.200> Matrix<00:52:29.960> multiplications 00:52:30.950 --> 00:52:30.960 align:start position:0% like M maybe it's Matrix multiplications 00:52:30.960 --> 00:52:33.349 align:start position:0% like M maybe it's Matrix multiplications that's<00:52:31.240> what<00:52:31.760> uh<00:52:31.920> schemes 00:52:33.349 --> 00:52:33.359 align:start position:0% that's what uh schemes 00:52:33.359 --> 00:52:37.870 align:start position:0% that's what uh schemes ADP<00:52:34.359> uh<00:52:34.880> and<00:52:35.720> Matrix<00:52:36.319> branching<00:52:36.920> programs<00:52:37.680> you 00:52:37.870 --> 00:52:37.880 align:start position:0% ADP uh and Matrix branching programs you 00:52:37.880 --> 00:52:40.150 align:start position:0% ADP uh and Matrix branching programs you tend<00:52:38.119> to<00:52:38.319> use<00:52:39.079> but<00:52:39.359> maybe<00:52:39.599> it's<00:52:39.760> just<00:52:39.960> like 00:52:40.150 --> 00:52:40.160 align:start position:0% tend to use but maybe it's just like 00:52:40.160 --> 00:52:42.109 align:start position:0% tend to use but maybe it's just like other<00:52:40.440> binary<00:52:40.839> Gates<00:52:41.119> that's<00:52:41.520> the<00:52:41.799> local 00:52:42.109 --> 00:52:42.119 align:start position:0% other binary Gates that's the local 00:52:42.119 --> 00:52:45.630 align:start position:0% other binary Gates that's the local mixing<00:52:42.520> schemes<00:52:42.880> tend<00:52:43.040> to<00:52:43.200> use<00:52:43.799> those<00:52:44.799> so<00:52:45.480> we 00:52:45.630 --> 00:52:45.640 align:start position:0% mixing schemes tend to use those so we 00:52:45.640 --> 00:52:47.510 align:start position:0% mixing schemes tend to use those so we get<00:52:45.839> this<00:52:46.079> encrypted<00:52:46.599> format<00:52:46.960> of<00:52:47.079> our<00:52:47.240> program 00:52:47.510 --> 00:52:47.520 align:start position:0% get this encrypted format of our program 00:52:47.520 --> 00:52:49.470 align:start position:0% get this encrypted format of our program but<00:52:47.640> we<00:52:47.760> have<00:52:47.880> like<00:52:48.040> blackbox<00:52:48.720> access<00:52:49.000> to<00:52:49.200> it 00:52:49.470 --> 00:52:49.480 align:start position:0% but we have like blackbox access to it 00:52:49.480 --> 00:52:51.190 align:start position:0% but we have like blackbox access to it right<00:52:49.880> so<00:52:50.040> we<00:52:50.119> can<00:52:50.280> put<00:52:50.520> inputs<00:52:50.839> and<00:52:50.960> we<00:52:51.040> can 00:52:51.190 --> 00:52:51.200 align:start position:0% right so we can put inputs and we can 00:52:51.200 --> 00:52:53.430 align:start position:0% right so we can put inputs and we can get<00:52:51.359> outputs<00:52:52.160> so<00:52:52.400> like<00:52:52.599> this<00:52:52.760> one<00:52:53.160> this<00:52:53.240> one 00:52:53.430 --> 00:52:53.440 align:start position:0% get outputs so like this one this one 00:52:53.440 --> 00:52:55.270 align:start position:0% get outputs so like this one this one takes<00:52:53.680> just<00:52:53.839> two<00:52:54.079> inputs<00:52:54.680> but<00:52:54.799> there's<00:52:55.000> like<00:52:55.119> a 00:52:55.270 --> 00:52:55.280 align:start position:0% takes just two inputs but there's like a 00:52:55.280 --> 00:52:57.030 align:start position:0% takes just two inputs but there's like a whole<00:52:55.440> bunch<00:52:55.680> more<00:52:55.920> gates<00:52:56.240> here 00:52:57.030 --> 00:52:57.040 align:start position:0% whole bunch more gates here 00:52:57.040 --> 00:52:59.109 align:start position:0% whole bunch more gates here the<00:52:57.160> gates<00:52:57.359> are<00:52:57.559> really 00:52:59.109 --> 00:52:59.119 align:start position:0% the gates are really 00:52:59.119 --> 00:53:01.510 align:start position:0% the gates are really complicated<00:53:00.119> so<00:53:00.280> we<00:53:00.400> don't<00:53:00.640> know<00:53:00.960> what's 00:53:01.510 --> 00:53:01.520 align:start position:0% complicated so we don't know what's 00:53:01.520 --> 00:53:03.309 align:start position:0% complicated so we don't know what's happening<00:53:02.000> inside<00:53:02.319> our<00:53:02.520> circuit<00:53:03.000> but<00:53:03.119> we<00:53:03.200> are 00:53:03.309 --> 00:53:03.319 align:start position:0% happening inside our circuit but we are 00:53:03.319 --> 00:53:05.510 align:start position:0% happening inside our circuit but we are able<00:53:03.480> to<00:53:03.599> do<00:53:03.720> like<00:53:03.880> blackbox<00:53:04.359> access<00:53:05.079> so<00:53:05.240> I<00:53:05.319> can 00:53:05.510 --> 00:53:05.520 align:start position:0% able to do like blackbox access so I can 00:53:05.520 --> 00:53:07.750 align:start position:0% able to do like blackbox access so I can just<00:53:05.720> put<00:53:06.040> like<00:53:06.799> I<00:53:06.880> can<00:53:07.079> just<00:53:07.359> because<00:53:07.599> there's 00:53:07.750 --> 00:53:07.760 align:start position:0% just put like I can just because there's 00:53:07.760 --> 00:53:09.270 align:start position:0% just put like I can just because there's only<00:53:07.920> two<00:53:08.119> inputs<00:53:08.440> I<00:53:08.520> can<00:53:08.640> just<00:53:08.839> go<00:53:09.079> just 00:53:09.270 --> 00:53:09.280 align:start position:0% only two inputs I can just go just 00:53:09.280 --> 00:53:10.789 align:start position:0% only two inputs I can just go just calculate<00:53:09.599> the<00:53:09.680> whole<00:53:09.799> truth<00:53:10.119> table<00:53:10.480> right 00:53:10.789 --> 00:53:10.799 align:start position:0% calculate the whole truth table right 00:53:10.799 --> 00:53:11.950 align:start position:0% calculate the whole truth table right because<00:53:10.960> I<00:53:11.040> have<00:53:11.119> the<00:53:11.240> encrypted<00:53:11.640> program<00:53:11.880> I 00:53:11.950 --> 00:53:11.960 align:start position:0% because I have the encrypted program I 00:53:11.960 --> 00:53:14.510 align:start position:0% because I have the encrypted program I can<00:53:12.079> just<00:53:12.160> put<00:53:12.319> in<00:53:12.480> 0<00:53:13.079> and<00:53:13.200> I<00:53:13.359> get<00:53:13.520> out<00:53:14.319> uh<00:53:14.440> I 00:53:14.510 --> 00:53:14.520 align:start position:0% can just put in 0 and I get out uh I 00:53:14.520 --> 00:53:16.470 align:start position:0% can just put in 0 and I get out uh I don't<00:53:14.640> know<00:53:15.119> what<00:53:15.880> I<00:53:16.000> don't<00:53:16.119> know<00:53:16.240> what<00:53:16.359> the 00:53:16.470 --> 00:53:16.480 align:start position:0% don't know what I don't know what the 00:53:16.480 --> 00:53:19.109 align:start position:0% don't know what I don't know what the truth<00:53:16.760> table<00:53:17.000> of<00:53:17.079> andate<00:53:17.599> is<00:53:18.520> well<00:53:18.720> let<00:53:18.839> me<00:53:18.960> try 00:53:19.109 --> 00:53:19.119 align:start position:0% truth table of andate is well let me try 00:53:19.119 --> 00:53:22.030 align:start position:0% truth table of andate is well let me try and<00:53:19.319> guess<00:53:20.200> so<00:53:20.680> 0 00:53:22.030 --> 00:53:22.040 align:start position:0% and guess so 0 00:53:22.040 --> 00:53:28.910 align:start position:0% and guess so 0 0<00:53:23.040> 1<00:53:23.920> 1<00:53:24.240> 0<00:53:24.920> 0<00:53:25.920> uh<00:53:26.040> 0<00:53:26.599> 1<00:53:27.040> 0<00:53:27.680> one<00:53:27.960> one<00:53:28.200> one<00:53:28.559> okay 00:53:28.910 --> 00:53:28.920 align:start position:0% 0 1 1 0 0 uh 0 1 0 one one one okay 00:53:28.920 --> 00:53:31.990 align:start position:0% 0 1 1 0 0 uh 0 1 0 one one one okay that's<00:53:29.119> it<00:53:29.359> source<00:53:29.599> of<00:53:29.839> Truth<00:53:30.839> this<00:53:30.960> is<00:53:31.319> and 00:53:31.990 --> 00:53:32.000 align:start position:0% that's it source of Truth this is and 00:53:32.000 --> 00:53:37.950 align:start position:0% that's it source of Truth this is and gate<00:53:33.000> okay<00:53:33.359> so<00:53:33.520> we<00:53:33.640> can<00:53:33.880> just<00:53:34.200> like<00:53:35.040> these<00:53:35.160> are 00:53:37.950 --> 00:53:37.960 align:start position:0% 00:53:37.960 --> 00:53:41.430 align:start position:0% ins<00:53:38.960> out<00:53:39.720> okay<00:53:40.160> so<00:53:40.520> we<00:53:40.680> can<00:53:40.880> we<00:53:41.000> can<00:53:41.119> just<00:53:41.280> put 00:53:41.430 --> 00:53:41.440 align:start position:0% ins out okay so we can we can just put 00:53:41.440 --> 00:53:47.109 align:start position:0% ins out okay so we can we can just put that<00:53:41.599> in<00:53:41.799> and<00:53:42.000> and<00:53:42.520> like<00:53:43.520> that's<00:53:43.720> XR<00:53:44.200> oh 00:53:47.109 --> 00:53:47.119 align:start position:0% 00:53:47.119 --> 00:53:52.710 align:start position:0% huh<00:53:49.440> we<00:53:49.640> good<00:53:50.640> yeah 00:53:52.710 --> 00:53:52.720 align:start position:0% huh we good yeah 00:53:52.720 --> 00:53:55.069 align:start position:0% huh we good yeah okay<00:53:53.720> okay<00:53:53.839> so<00:53:54.079> we<00:53:54.240> can<00:53:54.480> we<00:53:54.599> can<00:53:54.720> just<00:53:54.880> go 00:53:55.069 --> 00:53:55.079 align:start position:0% okay okay so we can we can just go 00:53:55.079 --> 00:53:57.390 align:start position:0% okay okay so we can we can just go through<00:53:55.280> and<00:53:55.480> like<00:53:55.760> do<00:53:55.960> the<00:53:56.119> whole<00:53:56.920> uh<00:53:57.079> State 00:53:57.390 --> 00:53:57.400 align:start position:0% through and like do the whole uh State 00:53:57.400 --> 00:53:58.990 align:start position:0% through and like do the whole uh State space<00:53:57.640> enumeration<00:53:58.400> and<00:53:58.480> we<00:53:58.599> can<00:53:58.720> find<00:53:58.880> out 00:53:58.990 --> 00:53:59.000 align:start position:0% space enumeration and we can find out 00:53:59.000 --> 00:54:00.789 align:start position:0% space enumeration and we can find out the<00:53:59.079> truth<00:53:59.319> table<00:53:59.559> but<00:53:59.640> we<00:53:59.760> don't<00:54:00.000> know<00:54:00.640> if 00:54:00.789 --> 00:54:00.799 align:start position:0% the truth table but we don't know if 00:54:00.799 --> 00:54:02.230 align:start position:0% the truth table but we don't know if this<00:54:00.960> is<00:54:01.160> actually<00:54:01.359> an<00:54:01.480> anate<00:54:01.839> or<00:54:01.920> if<00:54:02.000> it's<00:54:02.119> a 00:54:02.230 --> 00:54:02.240 align:start position:0% this is actually an anate or if it's a 00:54:02.240 --> 00:54:05.309 align:start position:0% this is actually an anate or if it's a more<00:54:02.440> complicated<00:54:02.960> circuit<00:54:03.880> but<00:54:04.200> like<00:54:05.200> what 00:54:05.309 --> 00:54:05.319 align:start position:0% more complicated circuit but like what 00:54:05.319 --> 00:54:06.950 align:start position:0% more complicated circuit but like what I'm<00:54:05.520> getting<00:54:05.799> at<00:54:06.040> here<00:54:06.240> is<00:54:06.400> that<00:54:06.640> like<00:54:06.760> you're 00:54:06.950 --> 00:54:06.960 align:start position:0% I'm getting at here is that like you're 00:54:06.960 --> 00:54:09.430 align:start position:0% I'm getting at here is that like you're able<00:54:07.240> to<00:54:07.960> you<00:54:08.119> have<00:54:08.280> blackbox<00:54:08.880> access<00:54:09.119> to<00:54:09.280> the 00:54:09.430 --> 00:54:09.440 align:start position:0% able to you have blackbox access to the 00:54:09.440 --> 00:54:12.390 align:start position:0% able to you have blackbox access to the thing<00:54:10.040> right<00:54:10.400> like<00:54:10.920> the<00:54:11.160> goal<00:54:11.559> here<00:54:11.960> is<00:54:12.079> to<00:54:12.200> try 00:54:12.390 --> 00:54:12.400 align:start position:0% thing right like the goal here is to try 00:54:12.400 --> 00:54:14.270 align:start position:0% thing right like the goal here is to try and<00:54:12.520> build<00:54:12.760> up<00:54:12.960> this<00:54:13.200> model<00:54:13.680> so<00:54:13.839> you're<00:54:14.079> able 00:54:14.270 --> 00:54:14.280 align:start position:0% and build up this model so you're able 00:54:14.280 --> 00:54:16.589 align:start position:0% and build up this model so you're able to<00:54:14.440> sit<00:54:14.640> down<00:54:14.839> and<00:54:14.960> be<00:54:15.119> like<00:54:15.440> I<00:54:15.559> can<00:54:15.960> I<00:54:16.040> can 00:54:16.589 --> 00:54:16.599 align:start position:0% to sit down and be like I can I can 00:54:16.599 --> 00:54:20.150 align:start position:0% to sit down and be like I can I can imagine<00:54:17.079> how<00:54:17.240> to<00:54:17.440> make<00:54:17.640> things<00:54:17.880> with<00:54:18.520> IO<00:54:19.520> okay 00:54:20.150 --> 00:54:20.160 align:start position:0% imagine how to make things with IO okay 00:54:20.160 --> 00:54:24.750 align:start position:0% imagine how to make things with IO okay cool<00:54:21.160> okay<00:54:21.440> so<00:54:22.000> let's<00:54:22.200> do<00:54:22.359> our<00:54:22.559> first<00:54:22.920> example 00:54:24.750 --> 00:54:24.760 align:start position:0% cool okay so let's do our first example 00:54:24.760 --> 00:54:27.270 align:start position:0% cool okay so let's do our first example then<00:54:25.760> of<00:54:25.920> our<00:54:26.119> Z 00:54:27.270 --> 00:54:27.280 align:start position:0% then of our Z 00:54:27.280 --> 00:54:30.109 align:start position:0% then of our Z KP<00:54:28.280> right<00:54:29.000> because<00:54:29.359> like<00:54:29.599> I<00:54:29.680> don't<00:54:29.839> know<00:54:30.000> if 00:54:30.109 --> 00:54:30.119 align:start position:0% KP right because like I don't know if 00:54:30.119 --> 00:54:33.710 align:start position:0% KP right because like I don't know if you've<00:54:30.359> seen<00:54:30.720> the<00:54:30.920> kind<00:54:31.040> of<00:54:31.280> like<00:54:31.440> tree<00:54:32.280> of<00:54:33.280> uh 00:54:33.710 --> 00:54:33.720 align:start position:0% you've seen the kind of like tree of uh 00:54:33.720 --> 00:54:36.349 align:start position:0% you've seen the kind of like tree of uh different<00:54:34.559> the<00:54:34.920> teag<00:54:35.240> tree<00:54:35.520> of<00:54:35.680> different 00:54:36.349 --> 00:54:36.359 align:start position:0% different the teag tree of different 00:54:36.359 --> 00:54:38.950 align:start position:0% different the teag tree of different cryptographic<00:54:37.359> Primitives<00:54:38.079> but<00:54:38.280> IO<00:54:38.640> is<00:54:38.839> kind 00:54:38.950 --> 00:54:38.960 align:start position:0% cryptographic Primitives but IO is kind 00:54:38.960 --> 00:54:40.950 align:start position:0% cryptographic Primitives but IO is kind of<00:54:39.200> the<00:54:39.400> the<00:54:39.520> one<00:54:39.720> at<00:54:39.839> the<00:54:40.000> very<00:54:40.240> top<00:54:40.760> because 00:54:40.950 --> 00:54:40.960 align:start position:0% of the the one at the very top because 00:54:40.960 --> 00:54:42.589 align:start position:0% of the the one at the very top because you<00:54:41.040> can<00:54:41.200> use<00:54:41.359> it<00:54:41.480> to<00:54:41.599> implement<00:54:41.960> all<00:54:42.079> of<00:54:42.200> the 00:54:42.589 --> 00:54:42.599 align:start position:0% you can use it to implement all of the 00:54:42.599 --> 00:54:44.870 align:start position:0% you can use it to implement all of the others<00:54:43.599> so<00:54:44.040> like<00:54:44.200> as<00:54:44.319> a<00:54:44.480> way<00:54:44.599> to<00:54:44.720> just 00:54:44.870 --> 00:54:44.880 align:start position:0% others so like as a way to just 00:54:44.880 --> 00:54:47.510 align:start position:0% others so like as a way to just introduce<00:54:45.200> the<00:54:45.319> concept<00:54:45.640> let's<00:54:45.760> do<00:54:45.920> zkps<00:54:46.920> okay 00:54:47.510 --> 00:54:47.520 align:start position:0% introduce the concept let's do zkps okay 00:54:47.520 --> 00:54:49.549 align:start position:0% introduce the concept let's do zkps okay so<00:54:47.720> let's<00:54:47.920> say<00:54:48.160> that<00:54:48.400> like<00:54:48.760> oh<00:54:49.000> yeah<00:54:49.319> let's 00:54:49.549 --> 00:54:49.559 align:start position:0% so let's say that like oh yeah let's 00:54:49.559 --> 00:54:51.190 align:start position:0% so let's say that like oh yeah let's introduce<00:54:50.000> this<00:54:50.119> other<00:54:50.520> model<00:54:50.799> of<00:54:50.960> how<00:54:51.040> to 00:54:51.190 --> 00:54:51.200 align:start position:0% introduce this other model of how to 00:54:51.200 --> 00:54:53.030 align:start position:0% introduce this other model of how to think<00:54:51.400> about<00:54:51.559> it 00:54:53.030 --> 00:54:53.040 align:start position:0% think about it 00:54:53.040 --> 00:54:55.990 align:start position:0% think about it so<00:54:54.040> so<00:54:54.200> we<00:54:54.359> have<00:54:54.520> our<00:54:54.880> setup<00:54:55.559> which<00:54:55.680> is<00:54:55.760> what<00:54:55.880> we 00:54:55.990 --> 00:54:56.000 align:start position:0% so so we have our setup which is what we 00:54:56.000 --> 00:54:58.230 align:start position:0% so so we have our setup which is what we just<00:54:56.119> talk<00:54:56.359> aled<00:54:56.599> about<00:54:57.359> and<00:54:57.520> now<00:54:57.720> let's<00:54:58.000> talk 00:54:58.230 --> 00:54:58.240 align:start position:0% just talk aled about and now let's talk 00:54:58.240 --> 00:55:02.390 align:start position:0% just talk aled about and now let's talk about<00:54:58.640> like<00:54:59.040> how<00:54:59.319> we<00:54:59.680> think<00:54:59.920> about<00:55:00.200> the<00:55:00.760> io<00:55:01.400> box 00:55:02.390 --> 00:55:02.400 align:start position:0% about like how we think about the io box 00:55:02.400 --> 00:55:04.510 align:start position:0% about like how we think about the io box so<00:55:02.599> we<00:55:02.720> have<00:55:02.920> this<00:55:03.119> IO 00:55:04.510 --> 00:55:04.520 align:start position:0% so we have this IO 00:55:04.520 --> 00:55:10.349 align:start position:0% so we have this IO box<00:55:05.760> okay<00:55:06.760> iio<00:55:07.119> box<00:55:07.440> does<00:55:07.799> some<00:55:08.480> things<00:55:09.480> right 00:55:10.349 --> 00:55:10.359 align:start position:0% box okay iio box does some things right 00:55:10.359 --> 00:55:12.230 align:start position:0% box okay iio box does some things right so<00:55:10.880> the<00:55:11.040> first<00:55:11.280> thing<00:55:11.480> that<00:55:11.599> it<00:55:11.720> will<00:55:11.920> do<00:55:12.160> that 00:55:12.230 --> 00:55:12.240 align:start position:0% so the first thing that it will do that 00:55:12.240 --> 00:55:15.150 align:start position:0% so the first thing that it will do that it<00:55:12.480> does<00:55:12.880> is<00:55:13.040> it<00:55:13.400> it<00:55:13.559> does<00:55:13.960> some<00:55:14.359> like<00:55:14.760> we<00:55:14.920> can 00:55:15.150 --> 00:55:15.160 align:start position:0% it does is it it does some like we can 00:55:15.160 --> 00:55:19.670 align:start position:0% it does is it it does some like we can Define<00:55:15.640> some<00:55:15.960> computation<00:55:16.520> we<00:55:16.640> want<00:55:16.760> it<00:55:16.880> to 00:55:19.670 --> 00:55:19.680 align:start position:0% 00:55:19.680 --> 00:55:23.270 align:start position:0% do<00:55:20.680> and<00:55:21.039> then<00:55:22.039> given<00:55:22.359> that<00:55:22.520> the<00:55:22.680> computation 00:55:23.270 --> 00:55:23.280 align:start position:0% do and then given that the computation 00:55:23.280 --> 00:55:25.829 align:start position:0% do and then given that the computation succeeds<00:55:24.079> we<00:55:24.240> get<00:55:24.400> the<00:55:24.520> io<00:55:24.880> box<00:55:25.160> to<00:55:25.440> produce<00:55:25.720> a 00:55:25.829 --> 00:55:25.839 align:start position:0% succeeds we get the io box to produce a 00:55:25.839 --> 00:55:27.549 align:start position:0% succeeds we get the io box to produce a signature 00:55:27.549 --> 00:55:27.559 align:start position:0% signature 00:55:27.559 --> 00:55:31.750 align:start position:0% signature so<00:55:27.760> this<00:55:27.880> is<00:55:28.039> kind<00:55:28.200> of<00:55:28.359> like<00:55:28.480> an<00:55:28.720> if<00:55:29.559> if 00:55:31.750 --> 00:55:31.760 align:start position:0% so this is kind of like an if if 00:55:31.760 --> 00:55:33.549 align:start position:0% so this is kind of like an if if computation<00:55:32.760> I<00:55:32.839> have<00:55:32.920> to<00:55:33.000> move<00:55:33.160> over<00:55:33.319> to<00:55:33.440> the 00:55:33.549 --> 00:55:33.559 align:start position:0% computation I have to move over to the 00:55:33.559 --> 00:55:36.029 align:start position:0% computation I have to move over to the other<00:55:33.760> side<00:55:34.599> then<00:55:34.880> produce<00:55:35.160> the<00:55:35.280> signature<00:55:35.839> so 00:55:36.029 --> 00:55:36.039 align:start position:0% other side then produce the signature so 00:55:36.039 --> 00:55:37.670 align:start position:0% other side then produce the signature so if<00:55:36.119> the<00:55:36.319> computation<00:55:36.799> succeeds<00:55:37.240> then<00:55:37.400> produce 00:55:37.670 --> 00:55:37.680 align:start position:0% if the computation succeeds then produce 00:55:37.680 --> 00:55:40.029 align:start position:0% if the computation succeeds then produce a<00:55:37.760> signature<00:55:38.640> so<00:55:39.000> like<00:55:39.160> this<00:55:39.359> iio<00:55:39.720> box<00:55:39.920> has 00:55:40.029 --> 00:55:40.039 align:start position:0% a signature so like this iio box has 00:55:40.039 --> 00:55:41.589 align:start position:0% a signature so like this iio box has been<00:55:40.200> encrypted<00:55:40.720> and<00:55:40.880> I<00:55:40.960> have<00:55:41.119> given<00:55:41.319> it<00:55:41.440> to 00:55:41.589 --> 00:55:41.599 align:start position:0% been encrypted and I have given it to 00:55:41.599 --> 00:55:44.109 align:start position:0% been encrypted and I have given it to you<00:55:42.079> right<00:55:42.280> so<00:55:42.400> you<00:55:42.480> have<00:55:42.640> this<00:55:42.839> box<00:55:43.760> on<00:55:43.920> your 00:55:44.109 --> 00:55:44.119 align:start position:0% you right so you have this box on your 00:55:44.119 --> 00:55:49.069 align:start position:0% you right so you have this box on your computer<00:55:44.680> you're<00:55:44.880> able<00:55:45.119> to<00:55:45.319> give<00:55:45.440> it<00:55:45.839> any 00:55:49.069 --> 00:55:49.079 align:start position:0% 00:55:49.079 --> 00:55:52.069 align:start position:0% inputs<00:55:50.079> and<00:55:50.200> the<00:55:50.359> output<00:55:50.680> you<00:55:50.920> get<00:55:51.799> is<00:55:51.920> a 00:55:52.069 --> 00:55:52.079 align:start position:0% inputs and the output you get is a 00:55:52.079 --> 00:55:55.190 align:start position:0% inputs and the output you get is a signature<00:55:52.559> of<00:55:53.039> something<00:55:54.039> okay<00:55:54.760> maybe<00:55:55.039> the 00:55:55.190 --> 00:55:55.200 align:start position:0% signature of something okay maybe the 00:55:55.200 --> 00:55:57.390 align:start position:0% signature of something okay maybe the signature<00:55:55.880> is<00:55:56.319> maybe<00:55:56.559> we<00:55:56.680> just<00:55:56.839> signed<00:55:57.119> the 00:55:57.390 --> 00:55:57.400 align:start position:0% signature is maybe we just signed the 00:55:57.400 --> 00:56:00.349 align:start position:0% signature is maybe we just signed the computation<00:55:58.480> right<00:55:59.480> so<00:55:59.760> basically<00:56:00.160> if<00:56:00.240> we 00:56:00.349 --> 00:56:00.359 align:start position:0% computation right so basically if we 00:56:00.359 --> 00:56:01.950 align:start position:0% computation right so basically if we want<00:56:00.440> to<00:56:00.559> make<00:56:00.640> a<00:56:00.760> zero<00:56:01.000> knowledge<00:56:01.240> proof<00:56:01.839> what 00:56:01.950 --> 00:56:01.960 align:start position:0% want to make a zero knowledge proof what 00:56:01.960 --> 00:56:04.109 align:start position:0% want to make a zero knowledge proof what we<00:56:02.079> need<00:56:02.200> to<00:56:02.359> do<00:56:02.559> is<00:56:02.680> we<00:56:02.799> need<00:56:02.960> to<00:56:03.599> have<00:56:03.799> other 00:56:04.109 --> 00:56:04.119 align:start position:0% we need to do is we need to have other 00:56:04.119 --> 00:56:07.430 align:start position:0% we need to do is we need to have other colors<00:56:05.119> we<00:56:05.240> need<00:56:05.400> to<00:56:05.559> take<00:56:05.760> this<00:56:06.440> computation 00:56:07.430 --> 00:56:07.440 align:start position:0% colors we need to take this computation 00:56:07.440 --> 00:56:09.789 align:start position:0% colors we need to take this computation we<00:56:07.559> just<00:56:07.720> set<00:56:08.000> that<00:56:08.119> to<00:56:08.319> be<00:56:08.680> whatever<00:56:09.160> the 00:56:09.789 --> 00:56:09.799 align:start position:0% we just set that to be whatever the 00:56:09.799 --> 00:56:12.589 align:start position:0% we just set that to be whatever the whatever<00:56:10.280> the<00:56:10.880> the<00:56:11.480> the<00:56:11.760> thing<00:56:12.079> we<00:56:12.280> want<00:56:12.400> to 00:56:12.589 --> 00:56:12.599 align:start position:0% whatever the the the thing we want to 00:56:12.599 --> 00:56:16.230 align:start position:0% whatever the the the thing we want to prove<00:56:13.039> is<00:56:14.039> right<00:56:14.799> for<00:56:15.039> example<00:56:15.920> if<00:56:16.000> you<00:56:16.160> want 00:56:16.230 --> 00:56:16.240 align:start position:0% prove is right for example if you want 00:56:16.240 --> 00:56:19.710 align:start position:0% prove is right for example if you want to<00:56:16.559> prove<00:56:17.520> that<00:56:17.720> you<00:56:18.119> have<00:56:18.960> like<00:56:19.280> 10 00:56:19.710 --> 00:56:19.720 align:start position:0% to prove that you have like 10 00:56:19.720 --> 00:56:21.950 align:start position:0% to prove that you have like 10 signatures<00:56:20.280> from<00:56:20.440> a<00:56:20.520> certain<00:56:20.799> public<00:56:21.119> key 00:56:21.950 --> 00:56:21.960 align:start position:0% signatures from a certain public key 00:56:21.960 --> 00:56:24.829 align:start position:0% signatures from a certain public key what<00:56:22.079> you<00:56:22.280> do<00:56:23.160> is<00:56:23.559> you<00:56:23.720> take<00:56:23.839> your<00:56:24.000> IO<00:56:24.319> box<00:56:24.720> you 00:56:24.829 --> 00:56:24.839 align:start position:0% what you do is you take your IO box you 00:56:24.839 --> 00:56:26.309 align:start position:0% what you do is you take your IO box you set<00:56:25.079> the<00:56:25.240> computation<00:56:25.720> to<00:56:25.839> be<00:56:25.960> the 00:56:26.309 --> 00:56:26.319 align:start position:0% set the computation to be the 00:56:26.319 --> 00:56:28.349 align:start position:0% set the computation to be the verification<00:56:26.880> of<00:56:27.039> 10<00:56:27.280> signatures<00:56:28.160> and<00:56:28.280> then 00:56:28.349 --> 00:56:28.359 align:start position:0% verification of 10 signatures and then 00:56:28.359 --> 00:56:30.309 align:start position:0% verification of 10 signatures and then you<00:56:28.480> have<00:56:28.640> this<00:56:28.839> Clause<00:56:29.160> that<00:56:29.359> like<00:56:29.599> well<00:56:29.880> if 00:56:30.309 --> 00:56:30.319 align:start position:0% you have this Clause that like well if 00:56:30.319 --> 00:56:32.710 align:start position:0% you have this Clause that like well if 10<00:56:30.599> signatures<00:56:31.039> are<00:56:31.280> here<00:56:31.920> produce<00:56:32.400> this 00:56:32.710 --> 00:56:32.720 align:start position:0% 10 signatures are here produce this 00:56:32.720 --> 00:56:35.549 align:start position:0% 10 signatures are here produce this other<00:56:33.000> signature<00:56:33.400> and<00:56:33.559> pass<00:56:33.720> it<00:56:33.839> out<00:56:34.760> so<00:56:35.359> one 00:56:35.549 --> 00:56:35.559 align:start position:0% other signature and pass it out so one 00:56:35.559 --> 00:56:37.789 align:start position:0% other signature and pass it out so one important<00:56:35.839> thing<00:56:35.960> to<00:56:36.160> remember<00:56:37.000> is<00:56:37.240> that<00:56:37.680> we 00:56:37.789 --> 00:56:37.799 align:start position:0% important thing to remember is that we 00:56:37.799 --> 00:56:40.510 align:start position:0% important thing to remember is that we have<00:56:37.960> a<00:56:38.160> secret<00:56:38.640> inside<00:56:39.000> the<00:56:39.160> io<00:56:39.480> box<00:56:40.000> yeah<00:56:40.319> so 00:56:40.510 --> 00:56:40.520 align:start position:0% have a secret inside the io box yeah so 00:56:40.520 --> 00:56:42.549 align:start position:0% have a secret inside the io box yeah so let's<00:56:40.680> do 00:56:42.549 --> 00:56:42.559 align:start position:0% let's do 00:56:42.559 --> 00:56:45.069 align:start position:0% let's do secrets<00:56:43.559> we<00:56:43.680> have<00:56:43.880> secrets<00:56:44.319> inside<00:56:44.559> our<00:56:44.720> IO 00:56:45.069 --> 00:56:45.079 align:start position:0% secrets we have secrets inside our IO 00:56:45.079 --> 00:56:48.029 align:start position:0% secrets we have secrets inside our IO box<00:56:46.079> and<00:56:46.359> inside<00:56:46.640> our<00:56:46.799> IO<00:56:47.119> box<00:56:47.319> what<00:56:47.440> are<00:56:47.839> our 00:56:48.029 --> 00:56:48.039 align:start position:0% box and inside our IO box what are our 00:56:48.039 --> 00:56:51.710 align:start position:0% box and inside our IO box what are our secret<00:56:48.640> our<00:56:48.839> secret<00:56:49.240> is<00:56:49.559> the<00:56:50.559> uh<00:56:51.200> the<00:56:51.599> the 00:56:51.710 --> 00:56:51.720 align:start position:0% secret our secret is the uh the the 00:56:51.720 --> 00:56:54.470 align:start position:0% secret our secret is the uh the the secret<00:56:52.160> key<00:56:52.400> of<00:56:52.559> this<00:56:52.799> signature<00:56:53.799> right<00:56:54.359> and 00:56:54.470 --> 00:56:54.480 align:start position:0% secret key of this signature right and 00:56:54.480 --> 00:56:58.390 align:start position:0% secret key of this signature right and we<00:56:54.599> have<00:56:55.000> this<00:56:56.000> uh<00:56:56.480> it's<00:56:56.640> not<00:56:57.119> secret<00:56:58.119> we<00:56:58.240> have 00:56:58.390 --> 00:56:58.400 align:start position:0% we have this uh it's not secret we have 00:56:58.400 --> 00:57:01.870 align:start position:0% we have this uh it's not secret we have the<00:56:58.599> public<00:56:59.280> key<00:57:00.280> so<00:57:00.680> at<00:57:00.799> the<00:57:01.200> at<00:57:01.280> the<00:57:01.440> setup 00:57:01.870 --> 00:57:01.880 align:start position:0% the public key so at the at the setup 00:57:01.880 --> 00:57:05.470 align:start position:0% the public key so at the at the setup phase<00:57:02.440> what<00:57:02.559> I<00:57:02.680> do<00:57:02.920> is<00:57:03.240> I<00:57:03.960> create<00:57:04.359> this<00:57:04.559> IO<00:57:04.880> box 00:57:05.470 --> 00:57:05.480 align:start position:0% phase what I do is I create this IO box 00:57:05.480 --> 00:57:06.950 align:start position:0% phase what I do is I create this IO box and<00:57:05.599> I<00:57:05.720> do<00:57:05.880> the<00:57:06.000> encryption<00:57:06.440> step<00:57:06.720> that<00:57:06.839> we 00:57:06.950 --> 00:57:06.960 align:start position:0% and I do the encryption step that we 00:57:06.960 --> 00:57:10.910 align:start position:0% and I do the encryption step that we talked<00:57:07.200> about<00:57:07.400> on<00:57:07.520> the<00:57:07.720> previous<00:57:08.880> slide<00:57:09.920> and 00:57:10.910 --> 00:57:10.920 align:start position:0% talked about on the previous slide and 00:57:10.920 --> 00:57:12.950 align:start position:0% talked about on the previous slide and and<00:57:11.119> now<00:57:11.680> what<00:57:11.839> I 00:57:12.950 --> 00:57:12.960 align:start position:0% and now what I 00:57:12.960 --> 00:57:15.670 align:start position:0% and now what I do<00:57:13.960> is<00:57:14.200> I<00:57:14.440> I<00:57:14.599> publish<00:57:14.960> the<00:57:15.079> public<00:57:15.359> key<00:57:15.480> and<00:57:15.559> I 00:57:15.670 --> 00:57:15.680 align:start position:0% do is I I publish the public key and I 00:57:15.680 --> 00:57:17.910 align:start position:0% do is I I publish the public key and I say<00:57:15.920> hey<00:57:16.200> look<00:57:16.880> if<00:57:17.000> you<00:57:17.160> ever<00:57:17.400> get<00:57:17.599> something 00:57:17.910 --> 00:57:17.920 align:start position:0% say hey look if you ever get something 00:57:17.920 --> 00:57:20.029 align:start position:0% say hey look if you ever get something that's<00:57:18.079> signed<00:57:18.359> by<00:57:18.480> this<00:57:18.680> public<00:57:19.000> key<00:57:19.760> you 00:57:20.029 --> 00:57:20.039 align:start position:0% that's signed by this public key you 00:57:20.039 --> 00:57:23.710 align:start position:0% that's signed by this public key you know<00:57:20.960> that<00:57:21.079> it<00:57:21.280> has<00:57:21.520> passed<00:57:22.000> this<00:57:22.880> this<00:57:23.079> check 00:57:23.710 --> 00:57:23.720 align:start position:0% know that it has passed this this check 00:57:23.720 --> 00:57:25.150 align:start position:0% know that it has passed this this check right<00:57:24.000> cuz<00:57:24.160> the<00:57:24.319> only<00:57:24.559> way<00:57:24.720> that<00:57:24.839> you<00:57:24.960> can 00:57:25.150 --> 00:57:25.160 align:start position:0% right cuz the only way that you can 00:57:25.160 --> 00:57:27.670 align:start position:0% right cuz the only way that you can produce<00:57:25.520> this<00:57:25.680> signature<00:57:26.640> is<00:57:26.799> if<00:57:26.960> you<00:57:27.319> execute 00:57:27.670 --> 00:57:27.680 align:start position:0% produce this signature is if you execute 00:57:27.680 --> 00:57:29.549 align:start position:0% produce this signature is if you execute the<00:57:27.799> io 00:57:29.549 --> 00:57:29.559 align:start position:0% the io 00:57:29.559 --> 00:57:31.910 align:start position:0% the io box<00:57:30.559> okay<00:57:31.000> so<00:57:31.200> this<00:57:31.280> is<00:57:31.400> how<00:57:31.480> you<00:57:31.559> do<00:57:31.720> Zer 00:57:31.910 --> 00:57:31.920 align:start position:0% box okay so this is how you do Zer 00:57:31.920 --> 00:57:34.349 align:start position:0% box okay so this is how you do Zer knowledge<00:57:32.359> poost<00:57:33.359> do<00:57:33.480> we<00:57:33.599> have<00:57:33.720> any<00:57:33.880> questions 00:57:34.349 --> 00:57:34.359 align:start position:0% knowledge poost do we have any questions 00:57:34.359 --> 00:57:35.630 align:start position:0% knowledge poost do we have any questions so 00:57:35.630 --> 00:57:35.640 align:start position:0% so 00:57:35.640 --> 00:57:45.109 align:start position:0% so far<00:57:36.640> yes<00:57:36.839> there<00:57:36.960> we 00:57:45.109 --> 00:57:45.119 align:start position:0% 00:57:45.119 --> 00:57:48.430 align:start position:0% go<00:57:46.119> so<00:57:46.880> the<00:57:47.079> question<00:57:47.400> is<00:57:47.720> how<00:57:47.839> do<00:57:47.960> you<00:57:48.079> trust 00:57:48.430 --> 00:57:48.440 align:start position:0% go so the question is how do you trust 00:57:48.440 --> 00:57:50.870 align:start position:0% go so the question is how do you trust the<00:57:48.599> output<00:57:49.000> of<00:57:49.119> the<00:57:49.240> iio<00:57:49.599> box<00:57:50.319> if<00:57:50.440> you<00:57:50.640> don't 00:57:50.870 --> 00:57:50.880 align:start position:0% the output of the iio box if you don't 00:57:50.880 --> 00:57:53.549 align:start position:0% the output of the iio box if you don't know<00:57:51.119> the<00:57:51.680> computation<00:57:52.680> so<00:57:53.000> like<00:57:53.200> I'm<00:57:53.319> using 00:57:53.549 --> 00:57:53.559 align:start position:0% know the computation so like I'm using 00:57:53.559 --> 00:57:55.309 align:start position:0% know the computation so like I'm using the<00:57:53.680> computation<00:57:54.119> as<00:57:54.280> like<00:57:54.520> a<00:57:54.680> placeholder 00:57:55.309 --> 00:57:55.319 align:start position:0% the computation as like a placeholder 00:57:55.319 --> 00:57:57.390 align:start position:0% the computation as like a placeholder here<00:57:55.799> but<00:57:55.960> like<00:57:56.319> when<00:57:56.520> you<00:57:56.640> do<00:57:56.839> the<00:57:57.000> setup<00:57:57.319> you 00:57:57.390 --> 00:57:57.400 align:start position:0% here but like when you do the setup you 00:57:57.400 --> 00:57:58.870 align:start position:0% here but like when you do the setup you would<00:57:57.599> Define<00:57:57.920> the<00:57:58.079> computation<00:57:58.680> and<00:57:58.799> you 00:57:58.870 --> 00:57:58.880 align:start position:0% would Define the computation and you 00:57:58.880 --> 00:58:00.750 align:start position:0% would Define the computation and you would<00:57:59.039> sort<00:57:59.200> of<00:57:59.599> show<00:58:00.000> people<00:58:00.240> that<00:58:00.440> like<00:58:00.599> oh 00:58:00.750 --> 00:58:00.760 align:start position:0% would sort of show people that like oh 00:58:00.760 --> 00:58:03.069 align:start position:0% would sort of show people that like oh this<00:58:00.839> is<00:58:00.960> the<00:58:01.079> thing<00:58:01.240> that<00:58:01.359> I<00:58:01.480> set<00:58:01.680> up<00:58:02.680> so<00:58:02.920> like 00:58:03.069 --> 00:58:03.079 align:start position:0% this is the thing that I set up so like 00:58:03.079 --> 00:58:05.150 align:start position:0% this is the thing that I set up so like IO<00:58:03.640> inherently<00:58:04.240> has<00:58:04.400> this<00:58:04.599> kind<00:58:04.720> of<00:58:04.920> like 00:58:05.150 --> 00:58:05.160 align:start position:0% IO inherently has this kind of like 00:58:05.160 --> 00:58:07.630 align:start position:0% IO inherently has this kind of like setup<00:58:05.599> phase<00:58:06.359> which<00:58:06.480> you<00:58:06.599> can<00:58:06.839> think<00:58:07.039> of<00:58:07.359> as 00:58:07.630 --> 00:58:07.640 align:start position:0% setup phase which you can think of as 00:58:07.640 --> 00:58:09.789 align:start position:0% setup phase which you can think of as like<00:58:07.839> similar<00:58:08.160> to<00:58:08.319> the<00:58:08.440> zero<00:58:08.720> knowledge<00:58:09.039> proof 00:58:09.789 --> 00:58:09.799 align:start position:0% like similar to the zero knowledge proof 00:58:09.799 --> 00:58:12.630 align:start position:0% like similar to the zero knowledge proof uh<00:58:09.920> trusted<00:58:10.359> setup<00:58:11.280> where<00:58:11.520> you<00:58:11.760> set<00:58:12.000> up<00:58:12.319> the 00:58:12.630 --> 00:58:12.640 align:start position:0% uh trusted setup where you set up the 00:58:12.640 --> 00:58:14.990 align:start position:0% uh trusted setup where you set up the circuit<00:58:13.640> and<00:58:13.760> you<00:58:13.880> set<00:58:14.079> up<00:58:14.240> the<00:58:14.400> com<00:58:14.880> the 00:58:14.990 --> 00:58:15.000 align:start position:0% circuit and you set up the com the 00:58:15.000 --> 00:58:16.910 align:start position:0% circuit and you set up the com the program<00:58:15.400> that<00:58:15.480> you<00:58:15.559> want<00:58:15.680> to<00:58:15.839> prove<00:58:16.480> but<00:58:16.640> you 00:58:16.910 --> 00:58:16.920 align:start position:0% program that you want to prove but you 00:58:16.920 --> 00:58:18.710 align:start position:0% program that you want to prove but you also<00:58:17.280> need<00:58:17.440> to<00:58:17.640> set<00:58:17.839> up<00:58:18.079> the<00:58:18.240> kind<00:58:18.359> of<00:58:18.559> like 00:58:18.710 --> 00:58:18.720 align:start position:0% also need to set up the kind of like 00:58:18.720 --> 00:58:22.109 align:start position:0% also need to set up the kind of like private<00:58:19.079> key<00:58:20.200> right<00:58:21.200> you<00:58:21.319> set<00:58:21.520> up<00:58:21.680> the<00:58:21.799> private 00:58:22.109 --> 00:58:22.119 align:start position:0% private key right you set up the private 00:58:22.119 --> 00:58:23.710 align:start position:0% private key right you set up the private key<00:58:22.280> and<00:58:22.440> you<00:58:22.680> you<00:58:22.880> publish<00:58:23.200> the<00:58:23.319> public<00:58:23.559> key 00:58:23.710 --> 00:58:23.720 align:start position:0% key and you you publish the public key 00:58:23.720 --> 00:58:25.190 align:start position:0% key and you you publish the public key and<00:58:23.799> this<00:58:23.920> is<00:58:24.039> like<00:58:24.240> part<00:58:24.440> of<00:58:24.640> the<00:58:24.960> of<00:58:25.079> the 00:58:25.190 --> 00:58:25.200 align:start position:0% and this is like part of the of the 00:58:25.200 --> 00:58:28.230 align:start position:0% and this is like part of the of the setup<00:58:25.520> that<00:58:25.599> you<00:58:25.720> need<00:58:25.880> to<00:58:26.000> go<00:58:26.119> go 00:58:28.230 --> 00:58:28.240 align:start position:0% setup that you need to go go 00:58:28.240 --> 00:58:33.990 align:start position:0% setup that you need to go go through<00:58:29.240> good<00:58:30.079> anything 00:58:33.990 --> 00:58:34.000 align:start position:0% 00:58:34.000 --> 00:58:38.069 align:start position:0% else<00:58:35.000> okay<00:58:35.359> oh<00:58:35.599> Jordie<00:58:36.200> oh<00:58:36.680> no<00:58:37.280> okay<00:58:37.720> all<00:58:37.799> right 00:58:38.069 --> 00:58:38.079 align:start position:0% else okay oh Jordie oh no okay all right 00:58:38.079 --> 00:58:41.109 align:start position:0% else okay oh Jordie oh no okay all right later<00:58:38.559> Jordie<00:58:39.559> um<00:58:40.160> Okay<00:58:40.359> cool<00:58:40.599> so<00:58:40.799> this<00:58:40.920> is<00:58:41.039> how 00:58:41.109 --> 00:58:41.119 align:start position:0% later Jordie um Okay cool so this is how 00:58:41.119 --> 00:58:43.349 align:start position:0% later Jordie um Okay cool so this is how you<00:58:41.240> do<00:58:41.400> Zer<00:58:41.799> proofs<00:58:42.480> uh<00:58:42.599> so<00:58:42.880> like<00:58:43.000> a<00:58:43.160> quick 00:58:43.349 --> 00:58:43.359 align:start position:0% you do Zer proofs uh so like a quick 00:58:43.359 --> 00:58:44.870 align:start position:0% you do Zer proofs uh so like a quick aside<00:58:43.640> is<00:58:43.760> there<00:58:43.960> any<00:58:44.240> other<00:58:44.520> things<00:58:44.720> that 00:58:44.870 --> 00:58:44.880 align:start position:0% aside is there any other things that 00:58:44.880 --> 00:58:46.190 align:start position:0% aside is there any other things that people<00:58:45.079> are<00:58:45.240> interested<00:58:45.559> in<00:58:45.640> architecting<00:58:46.119> we 00:58:46.190 --> 00:58:46.200 align:start position:0% people are interested in architecting we 00:58:46.200 --> 00:58:47.710 align:start position:0% people are interested in architecting we have<00:58:46.319> 10<00:58:46.480> minutes<00:58:46.760> so<00:58:47.039> I<00:58:47.160> I<00:58:47.240> have<00:58:47.359> enough<00:58:47.559> stuff 00:58:47.710 --> 00:58:47.720 align:start position:0% have 10 minutes so I I have enough stuff 00:58:47.720 --> 00:58:48.789 align:start position:0% have 10 minutes so I I have enough stuff to<00:58:47.839> go<00:58:47.960> through<00:58:48.160> but<00:58:48.280> if<00:58:48.359> there's<00:58:48.559> something 00:58:48.789 --> 00:58:48.799 align:start position:0% to go through but if there's something 00:58:48.799 --> 00:58:50.789 align:start position:0% to go through but if there's something people<00:58:49.039> are<00:58:49.319> specifically<00:58:49.760> interested<00:58:50.200> in<00:58:50.680> we 00:58:50.789 --> 00:58:50.799 align:start position:0% people are specifically interested in we 00:58:50.799 --> 00:58:53.589 align:start position:0% people are specifically interested in we can<00:58:50.960> think<00:58:51.160> about 00:58:53.589 --> 00:58:53.599 align:start position:0% 00:58:53.599 --> 00:58:56.109 align:start position:0% them<00:58:54.599> okay<00:58:54.799> well<00:58:55.000> feel<00:58:55.160> free<00:58:55.359> to<00:58:55.480> interrupt<00:58:55.839> me 00:58:56.109 --> 00:58:56.119 align:start position:0% them okay well feel free to interrupt me 00:58:56.119 --> 00:59:00.029 align:start position:0% them okay well feel free to interrupt me if<00:58:56.280> something<00:58:56.520> comes<00:58:56.720> to 00:59:00.029 --> 00:59:00.039 align:start position:0% 00:59:00.039 --> 00:59:02.349 align:start position:0% oh<00:59:01.039> that<00:59:01.200> was<00:59:01.280> signing<00:59:01.559> things<00:59:01.880> okay<00:59:02.000> let's<00:59:02.200> do 00:59:02.349 --> 00:59:02.359 align:start position:0% oh that was signing things okay let's do 00:59:02.359 --> 00:59:05.589 align:start position:0% oh that was signing things okay let's do that<00:59:02.559> then<00:59:02.680> at<00:59:02.799> the<00:59:02.920> end<00:59:04.079> um<00:59:05.079> so<00:59:05.240> you<00:59:05.359> want<00:59:05.440> to 00:59:05.589 --> 00:59:05.599 align:start position:0% that then at the end um so you want to 00:59:05.599 --> 00:59:07.390 align:start position:0% that then at the end um so you want to have<00:59:05.839> oh<00:59:05.960> so<00:59:06.119> you<00:59:06.200> want<00:59:06.280> to<00:59:06.400> have<00:59:06.520> like<00:59:06.640> a<00:59:06.799> dow 00:59:07.390 --> 00:59:07.400 align:start position:0% have oh so you want to have like a dow 00:59:07.400 --> 00:59:09.990 align:start position:0% have oh so you want to have like a dow that<00:59:08.240> that<00:59:08.520> has<00:59:08.680> a<00:59:08.839> private<00:59:09.200> key<00:59:09.640> and<00:59:09.760> it<00:59:09.839> wants 00:59:09.990 --> 00:59:10.000 align:start position:0% that that has a private key and it wants 00:59:10.000 --> 00:59:11.910 align:start position:0% that that has a private key and it wants to<00:59:10.160> sign<00:59:10.440> things<00:59:11.119> but<00:59:11.280> like<00:59:11.440> what's<00:59:11.640> the<00:59:11.720> point 00:59:11.910 --> 00:59:11.920 align:start position:0% to sign things but like what's the point 00:59:11.920 --> 00:59:13.309 align:start position:0% to sign things but like what's the point of<00:59:12.079> doing<00:59:12.240> that<00:59:12.359> is<00:59:12.440> it<00:59:12.599> like<00:59:12.720> a<00:59:13.039> you<00:59:13.119> want<00:59:13.240> to 00:59:13.309 --> 00:59:13.319 align:start position:0% of doing that is it like a you want to 00:59:13.319 --> 00:59:20.549 align:start position:0% of doing that is it like a you want to have<00:59:13.440> an 00:59:20.549 --> 00:59:20.559 align:start position:0% 00:59:20.559 --> 00:59:23.750 align:start position:0% EA<00:59:21.559> EA<00:59:21.960> is<00:59:22.119> externally<00:59:22.520> owned<00:59:22.880> account<00:59:23.520> like<00:59:23.640> a 00:59:23.750 --> 00:59:23.760 align:start position:0% EA EA is externally owned account like a 00:59:23.760 --> 00:59:25.870 align:start position:0% EA EA is externally owned account like a private<00:59:24.079> key<00:59:24.240> for<00:59:24.319> a<00:59:24.440> dow<00:59:24.920> but<00:59:25.039> like<00:59:25.359> I<00:59:25.440> don't 00:59:25.870 --> 00:59:25.880 align:start position:0% private key for a dow but like I don't 00:59:25.880 --> 00:59:28.990 align:start position:0% private key for a dow but like I don't it<00:59:26.480> like<00:59:26.880> the<00:59:27.079> the<00:59:27.240> reason<00:59:27.599> I'm<00:59:28.119> I<00:59:28.319> I<00:59:28.480> don't<00:59:28.720> I'm 00:59:28.990 --> 00:59:29.000 align:start position:0% it like the the reason I'm I I don't I'm 00:59:29.000 --> 00:59:31.029 align:start position:0% it like the the reason I'm I I don't I'm concerned<00:59:29.400> about<00:59:29.599> doing<00:59:29.839> this<00:59:30.000> is<00:59:30.160> that<00:59:30.400> like 00:59:31.029 --> 00:59:31.039 align:start position:0% concerned about doing this is that like 00:59:31.039 --> 00:59:32.789 align:start position:0% concerned about doing this is that like well<00:59:31.520> you<00:59:31.640> can<00:59:31.839> just<00:59:32.000> have<00:59:32.160> the<00:59:32.280> dowo<00:59:32.599> be<00:59:32.720> a 00:59:32.789 --> 00:59:32.799 align:start position:0% well you can just have the dowo be a 00:59:32.799 --> 00:59:34.190 align:start position:0% well you can just have the dowo be a smart<00:59:33.079> contract<00:59:33.440> and<00:59:33.520> you<00:59:33.599> can<00:59:33.680> just<00:59:33.839> verify 00:59:34.190 --> 00:59:34.200 align:start position:0% smart contract and you can just verify 00:59:34.200 --> 00:59:35.789 align:start position:0% smart contract and you can just verify the<00:59:34.319> smart<00:59:34.559> contract<00:59:34.880> did<00:59:35.079> something<00:59:35.680> as 00:59:35.789 --> 00:59:35.799 align:start position:0% the smart contract did something as 00:59:35.799 --> 00:59:37.630 align:start position:0% the smart contract did something as opposed<00:59:36.119> to<00:59:36.359> like<00:59:36.559> verify<00:59:36.920> the<00:59:37.039> signature<00:59:37.480> of 00:59:37.630 --> 00:59:37.640 align:start position:0% opposed to like verify the signature of 00:59:37.640 --> 00:59:39.630 align:start position:0% opposed to like verify the signature of something<00:59:38.559> but<00:59:38.760> like<00:59:38.880> maybe<00:59:39.079> Jordy<00:59:39.440> means 00:59:39.630 --> 00:59:39.640 align:start position:0% something but like maybe Jordy means 00:59:39.640 --> 00:59:41.029 align:start position:0% something but like maybe Jordy means that<00:59:39.799> he<00:59:39.920> wants<00:59:40.119> to<00:59:40.280> be<00:59:40.400> able<00:59:40.559> to<00:59:40.680> have<00:59:40.839> stuff 00:59:41.029 --> 00:59:41.039 align:start position:0% that he wants to be able to have stuff 00:59:41.039 --> 00:59:49.990 align:start position:0% that he wants to be able to have stuff encrypted<00:59:41.480> for<00:59:41.599> the<00:59:41.720> Dow<00:59:42.079> that<00:59:42.200> the<00:59:42.440> D 00:59:49.990 --> 00:59:50.000 align:start position:0% 00:59:50.000 --> 00:59:56.950 align:start position:0% can<00:59:51.000> yeah 00:59:56.950 --> 00:59:56.960 align:start position:0% 00:59:56.960 --> 00:59:59.190 align:start position:0% uh<00:59:57.079> so<00:59:57.319> Jord<00:59:57.720> saying<00:59:58.039> that<00:59:58.240> he<00:59:58.400> has<00:59:58.640> he<00:59:58.920> has<00:59:59.039> an 00:59:59.190 --> 00:59:59.200 align:start position:0% uh so Jord saying that he has he has an 00:59:59.200 --> 01:00:01.510 align:start position:0% uh so Jord saying that he has he has an external<00:59:59.720> file<01:00:00.400> he<01:00:00.480> wants<01:00:00.680> it<01:00:00.760> to<01:00:00.839> be 01:00:01.510 --> 01:00:01.520 align:start position:0% external file he wants it to be 01:00:01.520 --> 01:00:04.109 align:start position:0% external file he wants it to be encrypted<01:00:02.520> uh<01:00:02.680> but<01:00:02.839> he<01:00:03.000> only<01:00:03.280> wants<01:00:03.599> you<01:00:03.799> to<01:00:04.000> be 01:00:04.109 --> 01:00:04.119 align:start position:0% encrypted uh but he only wants you to be 01:00:04.119 --> 01:00:05.630 align:start position:0% encrypted uh but he only wants you to be able<01:00:04.280> to<01:00:04.359> decrypt<01:00:04.720> the<01:00:04.839> file<01:00:05.079> if<01:00:05.200> you<01:00:05.319> send 01:00:05.630 --> 01:00:05.640 align:start position:0% able to decrypt the file if you send 01:00:05.640 --> 01:00:08.829 align:start position:0% able to decrypt the file if you send funds<01:00:06.000> to<01:00:06.160> the<01:00:06.839> Dow<01:00:07.839> right<01:00:08.079> yeah<01:00:08.160> and<01:00:08.359> and<01:00:08.520> this 01:00:08.829 --> 01:00:08.839 align:start position:0% funds to the Dow right yeah and and this 01:00:08.839 --> 01:00:10.710 align:start position:0% funds to the Dow right yeah and and this and<01:00:09.000> nobody<01:00:09.359> knows<01:00:09.839> I<01:00:09.920> mean<01:00:10.119> this<01:00:10.280> file<01:00:10.520> was 01:00:10.710 --> 01:00:10.720 align:start position:0% and nobody knows I mean this file was 01:00:10.720 --> 01:00:12.109 align:start position:0% and nobody knows I mean this file was encrypted<01:00:11.160> and<01:00:11.280> nobody<01:00:11.520> knows<01:00:11.720> the<01:00:11.839> key 01:00:12.109 --> 01:00:12.119 align:start position:0% encrypted and nobody knows the key 01:00:12.119 --> 01:00:14.029 align:start position:0% encrypted and nobody knows the key except<01:00:12.440> that<01:00:12.640> though<01:00:13.079> yeah<01:00:13.240> yeah<01:00:13.400> yeah<01:00:13.760> okay 01:00:14.029 --> 01:00:14.039 align:start position:0% except that though yeah yeah yeah okay 01:00:14.039 --> 01:00:16.109 align:start position:0% except that though yeah yeah yeah okay okay<01:00:14.359> okay<01:00:14.559> this<01:00:14.680> is<01:00:14.880> kind<01:00:15.000> of<01:00:15.200> like<01:00:15.760> is<01:00:15.920> this 01:00:16.109 --> 01:00:16.119 align:start position:0% okay okay this is kind of like is this 01:00:16.119 --> 01:00:17.630 align:start position:0% okay okay this is kind of like is this witness<01:00:16.440> encryption<01:00:16.839> I'm<01:00:16.960> not<01:00:17.079> sure<01:00:17.280> but<01:00:17.440> yeah 01:00:17.630 --> 01:00:17.640 align:start position:0% witness encryption I'm not sure but yeah 01:00:17.640 --> 01:00:20.349 align:start position:0% witness encryption I'm not sure but yeah okay<01:00:17.760> we<01:00:17.880> can<01:00:18.000> do<01:00:18.160> that<01:00:18.599> let's<01:00:19.079> uh<01:00:19.799> let<01:00:20.000> me<01:00:20.280> what 01:00:20.349 --> 01:00:20.359 align:start position:0% okay we can do that let's uh let me what 01:00:20.359 --> 01:00:23.470 align:start position:0% okay we can do that let's uh let me what was<01:00:20.480> the<01:00:20.599> other<01:00:20.760> things<01:00:20.920> I<01:00:21.000> had<01:00:21.119> written<01:00:21.359> down 01:00:23.470 --> 01:00:23.480 align:start position:0% was the other things I had written down 01:00:23.480 --> 01:00:27.390 align:start position:0% was the other things I had written down here<01:00:24.480> okay<01:00:24.640> trust<01:00:24.880> the<01:00:25.000> setup<01:00:25.720> okay<01:00:26.200> so<01:00:27.200> let's 01:00:27.390 --> 01:00:27.400 align:start position:0% here okay trust the setup okay so let's 01:00:27.400 --> 01:00:28.870 align:start position:0% here okay trust the setup okay so let's do<01:00:27.599> the<01:00:27.720> trust<01:00:28.039> setup<01:00:28.319> and<01:00:28.400> then<01:00:28.520> we'll<01:00:28.799> then 01:00:28.870 --> 01:00:28.880 align:start position:0% do the trust setup and then we'll then 01:00:28.880 --> 01:00:38.589 align:start position:0% do the trust setup and then we'll then we'll<01:00:29.039> talk<01:00:29.160> about<01:00:29.319> J<01:00:29.839> St 01:00:38.589 --> 01:00:38.599 align:start position:0% 01:00:38.599 --> 01:00:40.549 align:start position:0% okay 01:00:40.549 --> 01:00:40.559 align:start position:0% okay 01:00:40.559 --> 01:00:44.349 align:start position:0% okay okay 01:00:44.349 --> 01:00:44.359 align:start position:0% 01:00:44.359 --> 01:00:48.349 align:start position:0% so<01:00:45.359> okay<01:00:46.319> so<01:00:47.000> historically<01:00:47.839> like<01:00:48.000> we've<01:00:48.160> done 01:00:48.349 --> 01:00:48.359 align:start position:0% so okay so historically like we've done 01:00:48.359 --> 01:00:49.750 align:start position:0% so okay so historically like we've done trusted<01:00:48.799> setups<01:00:49.119> for<01:00:49.240> a<01:00:49.319> whole<01:00:49.480> bunch<01:00:49.640> of 01:00:49.750 --> 01:00:49.760 align:start position:0% trusted setups for a whole bunch of 01:00:49.760 --> 01:00:52.150 align:start position:0% trusted setups for a whole bunch of different<01:00:50.039> ZK<01:00:50.720> applications<01:00:51.720> and<01:00:51.920> this 01:00:52.150 --> 01:00:52.160 align:start position:0% different ZK applications and this 01:00:52.160 --> 01:00:54.670 align:start position:0% different ZK applications and this basically<01:00:52.599> means<01:00:53.000> that<01:00:53.200> we<01:00:53.599> like<01:00:54.200> gather 01:00:54.670 --> 01:00:54.680 align:start position:0% basically means that we like gather 01:00:54.680 --> 01:00:56.190 align:start position:0% basically means that we like gather Randomness<01:00:55.240> from<01:00:55.400> a<01:00:55.520> whole<01:00:55.680> bunch<01:00:56.039> of 01:00:56.190 --> 01:00:56.200 align:start position:0% Randomness from a whole bunch of 01:00:56.200 --> 01:00:58.190 align:start position:0% Randomness from a whole bunch of different<01:00:56.440> people<01:00:57.039> and<01:00:57.200> then<01:00:57.400> we<01:00:57.680> compute 01:00:58.190 --> 01:00:58.200 align:start position:0% different people and then we compute 01:00:58.200 --> 01:01:01.710 align:start position:0% different people and then we compute this<01:00:58.440> kind<01:00:58.599> of<01:00:59.039> like<01:01:00.039> uh<01:01:00.440> special<01:01:01.240> key<01:01:01.559> that 01:01:01.710 --> 01:01:01.720 align:start position:0% this kind of like uh special key that 01:01:01.720 --> 01:01:03.950 align:start position:0% this kind of like uh special key that has<01:01:01.880> certain<01:01:02.319> properties<01:01:03.319> and<01:01:03.520> basically 01:01:03.950 --> 01:01:03.960 align:start position:0% has certain properties and basically 01:01:03.960 --> 01:01:05.349 align:start position:0% has certain properties and basically what<01:01:04.079> I<01:01:04.160> want<01:01:04.280> to<01:01:04.400> talk<01:01:04.559> about<01:01:04.799> now<01:01:05.000> is<01:01:05.160> how<01:01:05.280> we 01:01:05.349 --> 01:01:05.359 align:start position:0% what I want to talk about now is how we 01:01:05.359 --> 01:01:07.829 align:start position:0% what I want to talk about now is how we can<01:01:05.480> use<01:01:05.680> IO<01:01:06.079> to<01:01:06.200> do<01:01:06.400> that<01:01:07.240> uh<01:01:07.359> in<01:01:07.440> a<01:01:07.559> way<01:01:07.720> that 01:01:07.829 --> 01:01:07.839 align:start position:0% can use IO to do that uh in a way that 01:01:07.839 --> 01:01:09.470 align:start position:0% can use IO to do that uh in a way that we<01:01:07.920> don't<01:01:08.119> need 01:01:09.470 --> 01:01:09.480 align:start position:0% we don't need 01:01:09.480 --> 01:01:12.990 align:start position:0% we don't need to<01:01:10.480> in<01:01:10.559> a<01:01:10.720> way<01:01:10.920> that's<01:01:11.319> that's<01:01:11.599> like<01:01:12.079> more 01:01:12.990 --> 01:01:13.000 align:start position:0% to in a way that's that's like more 01:01:13.000 --> 01:01:15.069 align:start position:0% to in a way that's that's like more programmable<01:01:14.000> that<01:01:14.119> we<01:01:14.240> can<01:01:14.440> have<01:01:14.640> this<01:01:14.839> like 01:01:15.069 --> 01:01:15.079 align:start position:0% programmable that we can have this like 01:01:15.079 --> 01:01:17.470 align:start position:0% programmable that we can have this like Universal<01:01:15.760> setup<01:01:16.559> that<01:01:16.720> we<01:01:16.839> can<01:01:17.119> gather 01:01:17.470 --> 01:01:17.480 align:start position:0% Universal setup that we can gather 01:01:17.480 --> 01:01:18.990 align:start position:0% Universal setup that we can gather Randomness<01:01:17.960> and<01:01:18.119> anyone<01:01:18.400> is<01:01:18.559> able<01:01:18.720> to<01:01:18.839> use 01:01:18.990 --> 01:01:19.000 align:start position:0% Randomness and anyone is able to use 01:01:19.000 --> 01:01:21.870 align:start position:0% Randomness and anyone is able to use that<01:01:19.160> Randomness<01:01:19.599> to<01:01:19.760> do<01:01:20.079> whatever<01:01:20.359> they<01:01:20.520> want 01:01:21.870 --> 01:01:21.880 align:start position:0% that Randomness to do whatever they want 01:01:21.880 --> 01:01:25.670 align:start position:0% that Randomness to do whatever they want with<01:01:22.880> so<01:01:23.240> here's<01:01:23.480> how<01:01:23.599> we<01:01:23.720> do<01:01:23.880> it<01:01:24.760> uh<01:01:25.160> so<01:01:25.480> again 01:01:25.670 --> 01:01:25.680 align:start position:0% with so here's how we do it uh so again 01:01:25.680 --> 01:01:30.029 align:start position:0% with so here's how we do it uh so again we<01:01:25.799> have<01:01:25.960> have<01:01:26.039> our<01:01:26.160> iio 01:01:30.029 --> 01:01:30.039 align:start position:0% 01:01:30.039 --> 01:01:35.270 align:start position:0% box<01:01:31.200> okay<01:01:32.200> and<01:01:32.359> our<01:01:32.559> IO<01:01:32.920> box<01:01:33.160> does<01:01:33.400> some 01:01:35.270 --> 01:01:35.280 align:start position:0% box okay and our IO box does some 01:01:35.280 --> 01:01:39.950 align:start position:0% box okay and our IO box does some compute<01:01:36.280> and<01:01:36.720> if<01:01:36.960> the<01:01:37.520> compute<01:01:38.760> succeeds<01:01:39.760> it 01:01:39.950 --> 01:01:39.960 align:start position:0% compute and if the compute succeeds it 01:01:39.960 --> 01:01:41.029 align:start position:0% compute and if the compute succeeds it produces<01:01:40.319> a 01:01:41.029 --> 01:01:41.039 align:start position:0% produces a 01:01:41.039 --> 01:01:43.950 align:start position:0% produces a signature<01:01:42.039> of<01:01:42.280> the 01:01:43.950 --> 01:01:43.960 align:start position:0% signature of the 01:01:43.960 --> 01:01:46.789 align:start position:0% signature of the compute<01:01:44.960> okay<01:01:45.760> but<01:01:45.920> in<01:01:46.039> this<01:01:46.240> case<01:01:46.440> it<01:01:46.559> will 01:01:46.789 --> 01:01:46.799 align:start position:0% compute okay but in this case it will 01:01:46.799 --> 01:01:51.390 align:start position:0% compute okay but in this case it will also<01:01:47.680> uh<01:01:47.839> encrypt 01:01:51.390 --> 01:01:51.400 align:start position:0% 01:01:51.400 --> 01:01:54.109 align:start position:0% something<01:01:52.400> encrypt<01:01:52.880> the<01:01:53.000> output<01:01:53.359> of<01:01:53.520> the 01:01:54.109 --> 01:01:54.119 align:start position:0% something encrypt the output of the 01:01:54.119 --> 01:01:56.710 align:start position:0% something encrypt the output of the compute<01:01:55.119> yeah 01:01:56.710 --> 01:01:56.720 align:start position:0% compute yeah 01:01:56.720 --> 01:01:59.269 align:start position:0% compute yeah and<01:01:57.079> it's<01:01:57.279> also<01:01:57.520> able<01:01:57.720> to<01:01:57.880> do<01:01:58.079> like<01:01:58.240> a 01:01:59.269 --> 01:01:59.279 align:start position:0% and it's also able to do like a 01:01:59.279 --> 01:02:01.829 align:start position:0% and it's also able to do like a decrypt<01:02:00.279> so<01:02:00.480> this<01:02:00.559> is<01:02:00.799> kind<01:02:00.920> of<01:02:01.200> like<01:02:01.520> similar 01:02:01.829 --> 01:02:01.839 align:start position:0% decrypt so this is kind of like similar 01:02:01.839 --> 01:02:04.430 align:start position:0% decrypt so this is kind of like similar to<01:02:02.039> what<01:02:02.160> Jordi<01:02:02.760> was<01:02:03.119> was<01:02:03.319> getting<01:02:03.640> at<01:02:04.160> so<01:02:04.319> it 01:02:04.430 --> 01:02:04.440 align:start position:0% to what Jordi was was getting at so it 01:02:04.440 --> 01:02:07.510 align:start position:0% to what Jordi was was getting at so it takes<01:02:04.599> the<01:02:05.200> input<01:02:06.200> it<01:02:06.359> decrypts 01:02:07.510 --> 01:02:07.520 align:start position:0% takes the input it decrypts 01:02:07.520 --> 01:02:12.789 align:start position:0% takes the input it decrypts it<01:02:08.520> uh<01:02:09.200> it<01:02:10.599> it<01:02:11.599> uh<01:02:11.920> oh<01:02:12.039> hold<01:02:12.160> on<01:02:12.279> I<01:02:12.359> want<01:02:12.480> to<01:02:12.599> put 01:02:12.789 --> 01:02:12.799 align:start position:0% it uh it it uh oh hold on I want to put 01:02:12.799 --> 01:02:15.750 align:start position:0% it uh it it uh oh hold on I want to put this<01:02:13.240> the<01:02:13.440> compute<01:02:13.960> at<01:02:14.119> the<01:02:14.480> end<01:02:15.480> I<01:02:15.559> want<01:02:15.640> to 01:02:15.750 --> 01:02:15.760 align:start position:0% this the compute at the end I want to 01:02:15.760 --> 01:02:17.190 align:start position:0% this the compute at the end I want to put<01:02:15.839> the<01:02:15.960> signature<01:02:16.319> at<01:02:16.440> the<01:02:16.520> end<01:02:16.799> so<01:02:16.960> it<01:02:17.079> gets 01:02:17.190 --> 01:02:17.200 align:start position:0% put the signature at the end so it gets 01:02:17.200 --> 01:02:19.910 align:start position:0% put the signature at the end so it gets an<01:02:17.359> input<01:02:18.200> it<01:02:18.359> decrypts<01:02:18.880> it<01:02:19.160> it<01:02:19.279> does<01:02:19.480> some 01:02:19.910 --> 01:02:19.920 align:start position:0% an input it decrypts it it does some 01:02:19.920 --> 01:02:21.910 align:start position:0% an input it decrypts it it does some compute<01:02:20.279> on<01:02:20.440> the 01:02:21.910 --> 01:02:21.920 align:start position:0% compute on the 01:02:21.920 --> 01:02:27.029 align:start position:0% compute on the thing<01:02:22.920> and<01:02:23.079> then<01:02:23.279> it<01:02:23.960> uh<01:02:24.200> encrypts<01:02:24.680> it 01:02:27.029 --> 01:02:27.039 align:start position:0% thing and then it uh encrypts it 01:02:27.039 --> 01:02:29.710 align:start position:0% thing and then it uh encrypts it and<01:02:27.200> it<01:02:27.359> signs 01:02:29.710 --> 01:02:29.720 align:start position:0% 01:02:29.720 --> 01:02:32.190 align:start position:0% it<01:02:30.720> and<01:02:30.920> that's<01:02:31.279> that's<01:02:31.440> all<01:02:31.559> that<01:02:31.680> it<01:02:31.839> does 01:02:32.190 --> 01:02:32.200 align:start position:0% it and that's that's all that it does 01:02:32.200 --> 01:02:33.870 align:start position:0% it and that's that's all that it does this<01:02:32.279> is<01:02:32.440> our<01:02:32.599> whole<01:02:32.799> compute<01:02:33.319> so<01:02:33.440> it<01:02:33.559> takes 01:02:33.870 --> 01:02:33.880 align:start position:0% this is our whole compute so it takes 01:02:33.880 --> 01:02:36.589 align:start position:0% this is our whole compute so it takes input<01:02:34.240> it<01:02:34.319> does<01:02:34.599> this<01:02:34.839> and<01:02:34.920> it<01:02:35.039> outputs<01:02:35.440> the 01:02:36.589 --> 01:02:36.599 align:start position:0% input it does this and it outputs the 01:02:36.599 --> 01:02:40.190 align:start position:0% input it does this and it outputs the signature<01:02:37.599> and<01:02:37.720> it<01:02:37.880> also<01:02:38.119> outputs<01:02:38.799> the<01:02:39.559> uh 01:02:40.190 --> 01:02:40.200 align:start position:0% signature and it also outputs the uh 01:02:40.200 --> 01:02:42.789 align:start position:0% signature and it also outputs the uh this 01:02:42.789 --> 01:02:42.799 align:start position:0% this 01:02:42.799 --> 01:02:45.029 align:start position:0% this out<01:02:43.799> also<01:02:44.079> up<01:02:44.279> puts 01:02:45.029 --> 01:02:45.039 align:start position:0% out also up puts 01:02:45.039 --> 01:02:48.029 align:start position:0% out also up puts out<01:02:46.039> okay<01:02:46.960> so<01:02:47.240> like<01:02:47.440> it's<01:02:47.599> important<01:02:47.880> to 01:02:48.029 --> 01:02:48.039 align:start position:0% out okay so like it's important to 01:02:48.039 --> 01:02:51.349 align:start position:0% out okay so like it's important to remember<01:02:48.359> that<01:02:48.520> like<01:02:48.640> the<01:02:48.799> io<01:02:49.200> box<01:02:50.079> is<01:02:50.680> created 01:02:51.349 --> 01:02:51.359 align:start position:0% remember that like the io box is created 01:02:51.359 --> 01:02:53.109 align:start position:0% remember that like the io box is created with<01:02:51.640> the<01:02:52.160> with<01:02:52.279> the<01:02:52.440> process<01:02:52.839> that<01:02:53.000> we 01:02:53.109 --> 01:02:53.119 align:start position:0% with the with the process that we 01:02:53.119 --> 01:02:54.789 align:start position:0% with the with the process that we described<01:02:53.520> at<01:02:53.640> the<01:02:53.760> very<01:02:54.000> start<01:02:54.520> where<01:02:54.640> we 01:02:54.789 --> 01:02:54.799 align:start position:0% described at the very start where we 01:02:54.799 --> 01:02:57.430 align:start position:0% described at the very start where we have<01:02:55.000> some<01:02:55.559> some<01:02:55.960> like<01:02:56.079> binary<01:02:56.440> circuit<01:02:57.160> you 01:02:57.430 --> 01:02:57.440 align:start position:0% have some some like binary circuit you 01:02:57.440 --> 01:02:58.829 align:start position:0% have some some like binary circuit you like<01:02:57.599> encrypt<01:02:57.960> the<01:02:58.039> binary<01:02:58.319> circuit<01:02:58.640> and<01:02:58.720> you 01:02:58.829 --> 01:02:58.839 align:start position:0% like encrypt the binary circuit and you 01:02:58.839 --> 01:03:00.150 align:start position:0% like encrypt the binary circuit and you have<01:02:59.000> this<01:02:59.119> like<01:02:59.279> encrypted<01:02:59.760> circuit<01:03:00.079> that 01:03:00.150 --> 01:03:00.160 align:start position:0% have this like encrypted circuit that 01:03:00.160 --> 01:03:01.349 align:start position:0% have this like encrypted circuit that you're<01:03:00.279> able<01:03:00.480> to<01:03:00.640> execute<01:03:01.000> but<01:03:01.079> you're<01:03:01.200> not 01:03:01.349 --> 01:03:01.359 align:start position:0% you're able to execute but you're not 01:03:01.359 --> 01:03:03.870 align:start position:0% you're able to execute but you're not able<01:03:01.520> to<01:03:01.839> like<01:03:02.680> understand<01:03:02.880> or<01:03:03.079> comprehend 01:03:03.870 --> 01:03:03.880 align:start position:0% able to like understand or comprehend 01:03:03.880 --> 01:03:05.630 align:start position:0% able to like understand or comprehend you're<01:03:04.039> able<01:03:04.240> to<01:03:04.359> do<01:03:04.520> like<01:03:04.680> blackbox<01:03:05.240> stuff<01:03:05.440> to 01:03:05.630 --> 01:03:05.640 align:start position:0% you're able to do like blackbox stuff to 01:03:05.640 --> 01:03:08.109 align:start position:0% you're able to do like blackbox stuff to it<01:03:06.039> but<01:03:06.200> you're<01:03:06.359> not<01:03:06.559> able<01:03:06.760> to<01:03:06.960> see<01:03:07.799> you're<01:03:07.960> not 01:03:08.109 --> 01:03:08.119 align:start position:0% it but you're not able to see you're not 01:03:08.119 --> 01:03:10.269 align:start position:0% it but you're not able to see you're not a<01:03:08.400> able<01:03:08.559> to<01:03:08.640> see<01:03:08.839> what's<01:03:09.000> going<01:03:09.160> on<01:03:09.319> inside<01:03:10.039> so 01:03:10.269 --> 01:03:10.279 align:start position:0% a able to see what's going on inside so 01:03:10.279 --> 01:03:14.309 align:start position:0% a able to see what's going on inside so this<01:03:10.400> is<01:03:10.599> like<01:03:10.880> the<01:03:11.200> the<01:03:11.480> the<01:03:11.799> core<01:03:12.319> API<01:03:13.279> of<01:03:13.520> IO 01:03:14.309 --> 01:03:14.319 align:start position:0% this is like the the the core API of IO 01:03:14.319 --> 01:03:16.549 align:start position:0% this is like the the the core API of IO and<01:03:14.480> this<01:03:14.559> is<01:03:14.720> the<01:03:14.960> thing<01:03:15.200> that<01:03:15.359> you<01:03:16.039> like<01:03:16.279> once 01:03:16.549 --> 01:03:16.559 align:start position:0% and this is the thing that you like once 01:03:16.559 --> 01:03:20.029 align:start position:0% and this is the thing that you like once we<01:03:16.880> combine<01:03:17.480> this<01:03:18.039> with<01:03:18.240> the<01:03:18.440> ability<01:03:18.920> to<01:03:19.200> take 01:03:20.029 --> 01:03:20.039 align:start position:0% we combine this with the ability to take 01:03:20.039 --> 01:03:22.589 align:start position:0% we combine this with the ability to take to<01:03:20.200> make<01:03:20.680> signatures<01:03:21.680> we<01:03:21.920> have<01:03:22.200> this<01:03:22.400> like 01:03:22.589 --> 01:03:22.599 align:start position:0% to make signatures we have this like 01:03:22.599 --> 01:03:24.230 align:start position:0% to make signatures we have this like authenticity<01:03:23.279> that<01:03:23.400> we're<01:03:23.559> able<01:03:23.760> to<01:03:23.880> use<01:03:24.079> the 01:03:24.230 --> 01:03:24.240 align:start position:0% authenticity that we're able to use the 01:03:24.240 --> 01:03:26.269 align:start position:0% authenticity that we're able to use the bootstrap<01:03:25.200> basically 01:03:26.269 --> 01:03:26.279 align:start position:0% bootstrap basically 01:03:26.279 --> 01:03:27.750 align:start position:0% bootstrap basically the 01:03:27.750 --> 01:03:27.760 align:start position:0% the 01:03:27.760 --> 01:03:30.150 align:start position:0% the whole<01:03:28.760> almost<01:03:29.200> everything<01:03:29.559> that<01:03:29.680> a<01:03:29.799> trusted 01:03:30.150 --> 01:03:30.160 align:start position:0% whole almost everything that a trusted 01:03:30.160 --> 01:03:32.670 align:start position:0% whole almost everything that a trusted party<01:03:30.440> can<01:03:30.599> do<01:03:31.119> so<01:03:31.359> like<01:03:31.960> one<01:03:32.160> way<01:03:32.319> to<01:03:32.480> think 01:03:32.670 --> 01:03:32.680 align:start position:0% party can do so like one way to think 01:03:32.680 --> 01:03:34.470 align:start position:0% party can do so like one way to think about<01:03:32.920> this<01:03:33.119> is<01:03:33.279> that<01:03:33.480> like<01:03:33.640> you<01:03:34.079> you<01:03:34.279> have 01:03:34.470 --> 01:03:34.480 align:start position:0% about this is that like you you have 01:03:34.480 --> 01:03:37.510 align:start position:0% about this is that like you you have like<01:03:34.680> trusted<01:03:35.319> party<01:03:36.319> like<01:03:36.559> IO<01:03:36.920> can<01:03:37.079> be<01:03:37.240> like<01:03:37.359> a 01:03:37.510 --> 01:03:37.520 align:start position:0% like trusted party like IO can be like a 01:03:37.520 --> 01:03:39.990 align:start position:0% like trusted party like IO can be like a really<01:03:37.760> trusted<01:03:38.160> trusted<01:03:38.880> third<01:03:39.160> party<01:03:39.839> right 01:03:39.990 --> 01:03:40.000 align:start position:0% really trusted trusted third party right 01:03:40.000 --> 01:03:41.630 align:start position:0% really trusted trusted third party right where<01:03:40.079> you<01:03:40.200> can<01:03:40.319> just<01:03:40.440> say<01:03:40.599> to<01:03:40.720> the<01:03:40.839> io<01:03:41.200> people 01:03:41.630 --> 01:03:41.640 align:start position:0% where you can just say to the io people 01:03:41.640 --> 01:03:43.630 align:start position:0% where you can just say to the io people the<01:03:41.799> iio<01:03:42.079> Box<01:03:42.359> hey<01:03:42.480> do<01:03:42.640> this<01:03:42.839> thing<01:03:43.160> and<01:03:43.319> sign 01:03:43.630 --> 01:03:43.640 align:start position:0% the iio Box hey do this thing and sign 01:03:43.640 --> 01:03:45.190 align:start position:0% the iio Box hey do this thing and sign this<01:03:43.799> thing<01:03:44.200> and<01:03:44.359> then<01:03:44.599> just<01:03:44.799> give<01:03:44.920> me<01:03:45.039> the 01:03:45.190 --> 01:03:45.200 align:start position:0% this thing and then just give me the 01:03:45.200 --> 01:03:47.269 align:start position:0% this thing and then just give me the signature<01:03:46.200> and<01:03:46.359> because<01:03:46.599> no<01:03:46.680> one<01:03:46.839> is<01:03:46.960> able<01:03:47.160> to 01:03:47.269 --> 01:03:47.279 align:start position:0% signature and because no one is able to 01:03:47.279 --> 01:03:48.990 align:start position:0% signature and because no one is able to see<01:03:47.559> inside<01:03:47.960> or<01:03:48.160> affect<01:03:48.480> what's<01:03:48.680> happening 01:03:48.990 --> 01:03:49.000 align:start position:0% see inside or affect what's happening 01:03:49.000 --> 01:03:51.069 align:start position:0% see inside or affect what's happening inside<01:03:49.799> this<01:03:50.000> becomes<01:03:50.279> a<01:03:50.440> really<01:03:50.680> powerful 01:03:51.069 --> 01:03:51.079 align:start position:0% inside this becomes a really powerful 01:03:51.079 --> 01:03:52.670 align:start position:0% inside this becomes a really powerful tool<01:03:51.319> that<01:03:51.440> we<01:03:51.520> can<01:03:51.640> use<01:03:51.799> to<01:03:51.960> build<01:03:52.279> like<01:03:52.520> all 01:03:52.670 --> 01:03:52.680 align:start position:0% tool that we can use to build like all 01:03:52.680 --> 01:03:54.589 align:start position:0% tool that we can use to build like all the<01:03:52.839> systems<01:03:53.160> that<01:03:53.279> we<01:03:53.400> ever<01:03:53.599> wanted<01:03:54.319> like 01:03:54.589 --> 01:03:54.599 align:start position:0% the systems that we ever wanted like 01:03:54.599 --> 01:03:56.549 align:start position:0% the systems that we ever wanted like imagine<01:03:55.079> that<01:03:55.359> if<01:03:55.440> you<01:03:55.839> could<01:03:56.000> really<01:03:56.200> trust 01:03:56.549 --> 01:03:56.559 align:start position:0% imagine that if you could really trust 01:03:56.559 --> 01:03:58.230 align:start position:0% imagine that if you could really trust Facebook<01:03:56.920> or<01:03:57.039> if<01:03:57.119> you<01:03:57.200> could<01:03:57.400> really<01:03:57.599> trust 01:03:58.230 --> 01:03:58.240 align:start position:0% Facebook or if you could really trust 01:03:58.240 --> 01:04:00.670 align:start position:0% Facebook or if you could really trust like<01:03:58.400> these<01:03:58.559> internet<01:03:59.400> services<01:04:00.400> that's<01:04:00.559> kind 01:04:00.670 --> 01:04:00.680 align:start position:0% like these internet services that's kind 01:04:00.680 --> 01:04:02.589 align:start position:0% like these internet services that's kind of<01:04:00.799> what<01:04:00.920> we're<01:04:01.039> getting<01:04:01.240> at<01:04:01.359> with<01:04:01.520> iio<01:04:02.440> okay 01:04:02.589 --> 01:04:02.599 align:start position:0% of what we're getting at with iio okay 01:04:02.599 --> 01:04:04.230 align:start position:0% of what we're getting at with iio okay so<01:04:02.799> how<01:04:02.920> do<01:04:03.039> we<01:04:03.160> do<01:04:03.400> the<01:04:03.680> how<01:04:03.799> do<01:04:03.880> we<01:04:03.960> do<01:04:04.079> the 01:04:04.230 --> 01:04:04.240 align:start position:0% so how do we do the how do we do the 01:04:04.240 --> 01:04:05.829 align:start position:0% so how do we do the how do we do the random<01:04:04.520> number<01:04:05.079> how<01:04:05.200> do<01:04:05.279> we<01:04:05.359> do<01:04:05.480> our<01:04:05.599> random 01:04:05.829 --> 01:04:05.839 align:start position:0% random number how do we do our random 01:04:05.839 --> 01:04:07.630 align:start position:0% random number how do we do our random number<01:04:06.039> generation<01:04:06.839> so<01:04:07.039> basically<01:04:07.400> what<01:04:07.520> we 01:04:07.630 --> 01:04:07.640 align:start position:0% number generation so basically what we 01:04:07.640 --> 01:04:10.269 align:start position:0% number generation so basically what we do<01:04:07.839> is<01:04:08.039> we<01:04:08.319> we<01:04:08.640> we<01:04:08.920> we<01:04:09.079> have<01:04:09.240> this<01:04:09.440> box<01:04:10.079> and<01:04:10.160> then 01:04:10.269 --> 01:04:10.279 align:start position:0% do is we we we we have this box and then 01:04:10.279 --> 01:04:12.789 align:start position:0% do is we we we we have this box and then we<01:04:10.440> say<01:04:10.680> to<01:04:10.839> people<01:04:11.079> that<01:04:11.279> like<01:04:11.559> okay<01:04:12.200> you<01:04:12.640> take 01:04:12.789 --> 01:04:12.799 align:start position:0% we say to people that like okay you take 01:04:12.799 --> 01:04:14.430 align:start position:0% we say to people that like okay you take a<01:04:12.960> random<01:04:13.240> number<01:04:13.520> and<01:04:13.680> encrypt<01:04:14.039> it<01:04:14.200> and<01:04:14.319> put 01:04:14.430 --> 01:04:14.440 align:start position:0% a random number and encrypt it and put 01:04:14.440 --> 01:04:18.029 align:start position:0% a random number and encrypt it and put it<01:04:14.559> into<01:04:14.760> the<01:04:15.400> box<01:04:16.400> and<01:04:16.799> then<01:04:17.279> Inside<01:04:17.559> the<01:04:17.760> Box 01:04:18.029 --> 01:04:18.039 align:start position:0% it into the box and then Inside the Box 01:04:18.039 --> 01:04:20.309 align:start position:0% it into the box and then Inside the Box the<01:04:18.200> Box<01:04:18.440> will<01:04:18.839> you<01:04:19.039> encrypt<01:04:19.400> it<01:04:19.760> uh<01:04:20.000> I<01:04:20.119> have<01:04:20.200> to 01:04:20.309 --> 01:04:20.319 align:start position:0% the Box will you encrypt it uh I have to 01:04:20.319 --> 01:04:23.750 align:start position:0% the Box will you encrypt it uh I have to put<01:04:20.440> the<01:04:20.559> secrets<01:04:21.319> here<01:04:22.319> so<01:04:22.640> we<01:04:22.760> have<01:04:22.920> a<01:04:23.319> public 01:04:23.750 --> 01:04:23.760 align:start position:0% put the secrets here so we have a public 01:04:23.760 --> 01:04:27.630 align:start position:0% put the secrets here so we have a public key<01:04:24.119> and<01:04:24.240> a<01:04:24.400> secret<01:04:24.799> key<01:04:25.839> these<01:04:25.960> are<01:04:26.640> secrets 01:04:27.630 --> 01:04:27.640 align:start position:0% key and a secret key these are secrets 01:04:27.640 --> 01:04:29.870 align:start position:0% key and a secret key these are secrets so<01:04:28.000> no<01:04:28.119> one<01:04:28.319> knows<01:04:28.720> the<01:04:29.039> oh<01:04:29.400> well<01:04:29.520> no<01:04:29.599> one<01:04:29.720> knows 01:04:29.870 --> 01:04:29.880 align:start position:0% so no one knows the oh well no one knows 01:04:29.880 --> 01:04:31.269 align:start position:0% so no one knows the oh well no one knows the<01:04:29.960> secret<01:04:30.279> key<01:04:30.480> but<01:04:30.680> everybody<01:04:30.960> knows<01:04:31.119> the 01:04:31.269 --> 01:04:31.279 align:start position:0% the secret key but everybody knows the 01:04:31.279 --> 01:04:33.190 align:start position:0% the secret key but everybody knows the public<01:04:31.520> key<01:04:32.319> so<01:04:32.480> basically<01:04:32.839> the<01:04:32.920> user 01:04:33.190 --> 01:04:33.200 align:start position:0% public key so basically the user 01:04:33.200 --> 01:04:34.829 align:start position:0% public key so basically the user encrypts<01:04:33.599> for<01:04:33.720> the<01:04:33.799> public<01:04:34.079> key<01:04:34.440> they<01:04:34.599> put<01:04:34.720> it 01:04:34.829 --> 01:04:34.839 align:start position:0% encrypts for the public key they put it 01:04:34.839 --> 01:04:36.870 align:start position:0% encrypts for the public key they put it into<01:04:35.000> the<01:04:35.119> iio<01:04:35.400> box<01:04:35.920> the<01:04:36.039> iio<01:04:36.319> Box<01:04:36.520> does<01:04:36.720> the 01:04:36.870 --> 01:04:36.880 align:start position:0% into the iio box the iio Box does the 01:04:36.880 --> 01:04:40.029 align:start position:0% into the iio box the iio Box does the compute<01:04:37.599> where<01:04:37.839> it<01:04:38.000> decrypts<01:04:38.480> it<01:04:38.960> it<01:04:39.200> it<01:04:39.680> it 01:04:40.029 --> 01:04:40.039 align:start position:0% compute where it decrypts it it it it 01:04:40.039 --> 01:04:42.190 align:start position:0% compute where it decrypts it it it it combines<01:04:40.480> it<01:04:40.720> with<01:04:40.960> the<01:04:41.599> with<01:04:41.839> with<01:04:41.960> the 01:04:42.190 --> 01:04:42.200 align:start position:0% combines it with the with with the 01:04:42.200 --> 01:04:44.230 align:start position:0% combines it with the with with the previous<01:04:42.680> Randomness<01:04:43.400> that<01:04:43.559> that<01:04:43.640> was<01:04:44.000> oh<01:04:44.160> we 01:04:44.230 --> 01:04:44.240 align:start position:0% previous Randomness that that was oh we 01:04:44.240 --> 01:04:47.109 align:start position:0% previous Randomness that that was oh we need<01:04:44.359> to<01:04:44.480> have<01:04:44.640> two<01:04:45.200> inputs<01:04:46.200> right<01:04:46.480> one<01:04:46.640> is<01:04:46.760> not 01:04:47.109 --> 01:04:47.119 align:start position:0% need to have two inputs right one is not 01:04:47.119 --> 01:04:50.910 align:start position:0% need to have two inputs right one is not enough<01:04:48.119> so<01:04:48.599> this<01:04:48.720> is<01:04:49.000> input<01:04:49.359> from<01:04:49.520> the<01:04:49.920> user 01:04:50.910 --> 01:04:50.920 align:start position:0% enough so this is input from the user 01:04:50.920 --> 01:04:54.230 align:start position:0% enough so this is input from the user and<01:04:51.119> this<01:04:51.240> is<01:04:51.720> input<01:04:52.720> from<01:04:52.880> the<01:04:53.000> current<01:04:53.319> state 01:04:54.230 --> 01:04:54.240 align:start position:0% and this is input from the current state 01:04:54.240 --> 01:04:56.750 align:start position:0% and this is input from the current state so<01:04:54.359> you<01:04:54.480> have<01:04:54.599> two<01:04:54.760> inputs<01:04:55.960> so<01:04:56.319> it<01:04:56.440> takes<01:04:56.640> the 01:04:56.750 --> 01:04:56.760 align:start position:0% so you have two inputs so it takes the 01:04:56.760 --> 01:04:58.150 align:start position:0% so you have two inputs so it takes the input<01:04:57.039> from<01:04:57.119> the<01:04:57.200> user<01:04:57.440> it<01:04:57.559> decrypts<01:04:57.960> it<01:04:58.079> it 01:04:58.150 --> 01:04:58.160 align:start position:0% input from the user it decrypts it it 01:04:58.160 --> 01:04:59.589 align:start position:0% input from the user it decrypts it it takes<01:04:58.359> the<01:04:58.720> input<01:04:59.000> from<01:04:59.119> the<01:04:59.240> state<01:04:59.480> it 01:04:59.589 --> 01:04:59.599 align:start position:0% takes the input from the state it 01:04:59.599 --> 01:05:02.029 align:start position:0% takes the input from the state it decrypts<01:05:00.000> it<01:05:00.440> it<01:05:00.640> joins<01:05:01.000> the<01:05:01.119> two<01:05:01.279> Randomness 01:05:02.029 --> 01:05:02.039 align:start position:0% decrypts it it joins the two Randomness 01:05:02.039 --> 01:05:04.069 align:start position:0% decrypts it it joins the two Randomness together<01:05:02.760> and<01:05:02.920> then<01:05:03.119> it<01:05:03.279> encrypts<01:05:03.680> the<01:05:03.760> output 01:05:04.069 --> 01:05:04.079 align:start position:0% together and then it encrypts the output 01:05:04.079 --> 01:05:06.990 align:start position:0% together and then it encrypts the output and<01:05:04.359> it<01:05:05.359> it<01:05:05.599> returns<01:05:05.839> that<01:05:05.960> and<01:05:06.119> assigns<01:05:06.480> that 01:05:06.990 --> 01:05:07.000 align:start position:0% and it it returns that and assigns that 01:05:07.000 --> 01:05:09.069 align:start position:0% and it it returns that and assigns that so<01:05:07.200> this<01:05:07.279> is<01:05:07.559> the<01:05:08.119> so<01:05:08.319> then<01:05:08.520> what<01:05:08.640> we<01:05:08.760> do<01:05:08.880> is<01:05:09.000> we 01:05:09.069 --> 01:05:09.079 align:start position:0% so this is the so then what we do is we 01:05:09.079 --> 01:05:11.349 align:start position:0% so this is the so then what we do is we make<01:05:09.200> it<01:05:09.359> like<01:05:09.440> a<01:05:09.599> chain<01:05:10.160> where<01:05:10.440> like<01:05:10.960> we<01:05:11.119> have 01:05:11.349 --> 01:05:11.359 align:start position:0% make it like a chain where like we have 01:05:11.359 --> 01:05:13.589 align:start position:0% make it like a chain where like we have like<01:05:11.520> this<01:05:11.760> iio<01:05:12.079> box<01:05:12.720> kind<01:05:12.839> of<01:05:13.000> pass<01:05:13.240> the<01:05:13.400> value 01:05:13.589 --> 01:05:13.599 align:start position:0% like this iio box kind of pass the value 01:05:13.599 --> 01:05:15.109 align:start position:0% like this iio box kind of pass the value to<01:05:13.760> the<01:05:13.880> next<01:05:14.079> one<01:05:14.319> which<01:05:14.480> pass<01:05:14.680> the<01:05:14.799> value<01:05:15.000> to 01:05:15.109 --> 01:05:15.119 align:start position:0% to the next one which pass the value to 01:05:15.119 --> 01:05:16.789 align:start position:0% to the next one which pass the value to the<01:05:15.240> next<01:05:15.440> one<01:05:16.039> and<01:05:16.160> like<01:05:16.319> what<01:05:16.400> we're<01:05:16.559> doing 01:05:16.789 --> 01:05:16.799 align:start position:0% the next one and like what we're doing 01:05:16.799 --> 01:05:18.269 align:start position:0% the next one and like what we're doing is<01:05:16.880> that<01:05:17.039> we're<01:05:17.240> just<01:05:17.400> stacking<01:05:17.799> Randomness 01:05:18.269 --> 01:05:18.279 align:start position:0% is that we're just stacking Randomness 01:05:18.279 --> 01:05:21.109 align:start position:0% is that we're just stacking Randomness up<01:05:18.440> on<01:05:18.599> top<01:05:18.760> of<01:05:18.920> it<01:05:19.279> of<01:05:19.440> itself<01:05:20.400> right<01:05:20.880> and<01:05:21.039> this 01:05:21.109 --> 01:05:21.119 align:start position:0% up on top of it of itself right and this 01:05:21.119 --> 01:05:23.029 align:start position:0% up on top of it of itself right and this is<01:05:21.279> kind<01:05:21.400> of<01:05:21.559> like<01:05:21.839> phase<01:05:22.200> one<01:05:22.400> of<01:05:22.520> our<01:05:22.680> trusta 01:05:23.029 --> 01:05:23.039 align:start position:0% is kind of like phase one of our trusta 01:05:23.039 --> 01:05:24.630 align:start position:0% is kind of like phase one of our trusta setup<01:05:23.359> where<01:05:23.480> we're<01:05:23.680> generating<01:05:24.200> this<01:05:24.359> random 01:05:24.630 --> 01:05:24.640 align:start position:0% setup where we're generating this random 01:05:24.640 --> 01:05:26.309 align:start position:0% setup where we're generating this random number<01:05:24.880> that<01:05:25.000> no<01:05:25.079> one<01:05:25.240> knows<01:05:25.920> and<01:05:26.039> like<01:05:26.200> the 01:05:26.309 --> 01:05:26.319 align:start position:0% number that no one knows and like the 01:05:26.319 --> 01:05:28.910 align:start position:0% number that no one knows and like the assumption<01:05:26.760> is<01:05:26.960> that<01:05:27.200> like<01:05:27.480> if<01:05:27.720> any<01:05:28.039> single 01:05:28.910 --> 01:05:28.920 align:start position:0% assumption is that like if any single 01:05:28.920 --> 01:05:30.670 align:start position:0% assumption is that like if any single parody<01:05:29.920> uh 01:05:30.670 --> 01:05:30.680 align:start position:0% parody uh 01:05:30.680 --> 01:05:33.549 align:start position:0% parody uh includes<01:05:31.680> uh<01:05:31.880> honestly<01:05:32.880> passes<01:05:33.160> a<01:05:33.319> random 01:05:33.549 --> 01:05:33.559 align:start position:0% includes uh honestly passes a random 01:05:33.559 --> 01:05:36.069 align:start position:0% includes uh honestly passes a random number<01:05:34.480> then<01:05:34.760> there's<01:05:34.960> no<01:05:35.119> way<01:05:35.240> for<01:05:35.400> anyone<01:05:35.680> to 01:05:36.069 --> 01:05:36.079 align:start position:0% number then there's no way for anyone to 01:05:36.079 --> 01:05:38.950 align:start position:0% number then there's no way for anyone to to<01:05:36.279> to<01:05:36.440> know<01:05:36.880> like<01:05:37.720> to<01:05:37.960> to<01:05:38.200> to<01:05:38.440> to<01:05:38.599> calculate 01:05:38.950 --> 01:05:38.960 align:start position:0% to to know like to to to to calculate 01:05:38.960 --> 01:05:40.349 align:start position:0% to to know like to to to to calculate the<01:05:39.079> random<01:05:39.319> number<01:05:39.640> right<01:05:39.799> because<01:05:39.960> in<01:05:40.079> order 01:05:40.349 --> 01:05:40.359 align:start position:0% the random number right because in order 01:05:40.359 --> 01:05:42.710 align:start position:0% the random number right because in order to<01:05:40.960> calculate<01:05:41.359> the<01:05:41.480> final<01:05:41.839> random<01:05:42.119> number<01:05:42.599> you 01:05:42.710 --> 01:05:42.720 align:start position:0% to calculate the final random number you 01:05:42.720 --> 01:05:44.910 align:start position:0% to calculate the final random number you need<01:05:42.920> to<01:05:43.680> have<01:05:43.920> all<01:05:44.039> of<01:05:44.200> the<01:05:44.359> intermediate 01:05:44.910 --> 01:05:44.920 align:start position:0% need to have all of the intermediate 01:05:44.920 --> 01:05:47.430 align:start position:0% need to have all of the intermediate random<01:05:45.680> numbers<01:05:46.680> okay<01:05:46.880> so<01:05:47.039> this<01:05:47.160> is<01:05:47.240> how<01:05:47.319> you 01:05:47.430 --> 01:05:47.440 align:start position:0% random numbers okay so this is how you 01:05:47.440 --> 01:05:49.069 align:start position:0% random numbers okay so this is how you generate<01:05:47.720> the<01:05:47.839> random<01:05:48.079> number<01:05:48.680> then<01:05:48.839> like<01:05:48.960> we 01:05:49.069 --> 01:05:49.079 align:start position:0% generate the random number then like we 01:05:49.079 --> 01:05:50.670 align:start position:0% generate the random number then like we have<01:05:49.160> to<01:05:49.240> make<01:05:49.400> another<01:05:49.720> box<01:05:49.960> to<01:05:50.200> actually<01:05:50.480> use 01:05:50.670 --> 01:05:50.680 align:start position:0% have to make another box to actually use 01:05:50.680 --> 01:05:52.470 align:start position:0% have to make another box to actually use a<01:05:50.880> random<01:05:51.160> number<01:05:51.480> cuz<01:05:51.640> like<01:05:51.799> with<01:05:51.920> the<01:05:52.359> with 01:05:52.470 --> 01:05:52.480 align:start position:0% a random number cuz like with the with 01:05:52.480 --> 01:05:53.910 align:start position:0% a random number cuz like with the with the<01:05:52.599> trust<01:05:52.920> setups<01:05:53.200> that<01:05:53.279> we've<01:05:53.480> historically 01:05:53.910 --> 01:05:53.920 align:start position:0% the trust setups that we've historically 01:05:53.920 --> 01:05:55.190 align:start position:0% the trust setups that we've historically done<01:05:54.119> they<01:05:54.200> need<01:05:54.319> to<01:05:54.440> have<01:05:54.520> a<01:05:54.760> special 01:05:55.190 --> 01:05:55.200 align:start position:0% done they need to have a special 01:05:55.200 --> 01:05:56.430 align:start position:0% done they need to have a special property 01:05:56.430 --> 01:05:56.440 align:start position:0% property 01:05:56.440 --> 01:05:58.150 align:start position:0% property uh<01:05:56.599> it's<01:05:56.760> not<01:05:56.960> enough<01:05:57.200> for<01:05:57.359> them<01:05:57.520> to<01:05:57.720> just<01:05:57.920> be 01:05:58.150 --> 01:05:58.160 align:start position:0% uh it's not enough for them to just be 01:05:58.160 --> 01:06:00.349 align:start position:0% uh it's not enough for them to just be like<01:05:58.640> random<01:05:59.000> or<01:05:59.160> whatever<01:05:59.720> they<01:05:59.880> need<01:06:00.000> to<01:06:00.200> be 01:06:00.349 --> 01:06:00.359 align:start position:0% like random or whatever they need to be 01:06:00.359 --> 01:06:01.150 align:start position:0% like random or whatever they need to be able 01:06:01.150 --> 01:06:01.160 align:start position:0% able 01:06:01.160 --> 01:06:03.750 align:start position:0% able to<01:06:02.160> they<01:06:02.279> need<01:06:02.440> to<01:06:02.839> have<01:06:03.039> this<01:06:03.359> like<01:06:03.520> for<01:06:03.640> the 01:06:03.750 --> 01:06:03.760 align:start position:0% to they need to have this like for the 01:06:03.760 --> 01:06:05.549 align:start position:0% to they need to have this like for the trust<01:06:04.200> for<01:06:04.359> the<01:06:04.480> powers<01:06:04.720> of<01:06:04.880> to<01:06:05.160> it<01:06:05.240> needs<01:06:05.400> to 01:06:05.549 --> 01:06:05.559 align:start position:0% trust for the powers of to it needs to 01:06:05.559 --> 01:06:08.870 align:start position:0% trust for the powers of to it needs to be<01:06:05.760> like<01:06:06.000> the<01:06:06.400> G<01:06:06.680> to<01:06:06.839> the<01:06:07.079> x<01:06:07.400> equals<01:06:07.760> g<01:06:08.000> to<01:06:08.240> or<01:06:08.359> gt 01:06:08.870 --> 01:06:08.880 align:start position:0% be like the G to the x equals g to or gt 01:06:08.880 --> 01:06:11.269 align:start position:0% be like the G to the x equals g to or gt to<01:06:09.119> the<01:06:09.799> to<01:06:09.960> the<01:06:10.119> x<01:06:10.279> or<01:06:10.440> something<01:06:10.640> like<01:06:10.799> that<01:06:11.240> I 01:06:11.269 --> 01:06:11.279 align:start position:0% to the to the x or something like that I 01:06:11.279 --> 01:06:13.069 align:start position:0% to the to the x or something like that I can't<01:06:11.440> remember<01:06:12.279> but<01:06:12.480> like<01:06:12.640> it<01:06:12.720> needs<01:06:12.880> to<01:06:13.000> have 01:06:13.069 --> 01:06:13.079 align:start position:0% can't remember but like it needs to have 01:06:13.079 --> 01:06:15.029 align:start position:0% can't remember but like it needs to have a<01:06:13.200> special<01:06:13.520> property<01:06:14.079> so<01:06:14.240> we<01:06:14.440> just<01:06:14.760> we<01:06:14.880> just 01:06:15.029 --> 01:06:15.039 align:start position:0% a special property so we just we just 01:06:15.039 --> 01:06:17.829 align:start position:0% a special property so we just we just make<01:06:15.240> another<01:06:15.520> IO<01:06:15.839> box<01:06:16.079> that<01:06:16.240> does 01:06:17.829 --> 01:06:17.839 align:start position:0% make another IO box that does 01:06:17.839 --> 01:06:20.710 align:start position:0% make another IO box that does that<01:06:18.839> so<01:06:19.000> the<01:06:19.160> io<01:06:19.440> box<01:06:19.720> has<01:06:19.839> the<01:06:20.000> same<01:06:20.279> kind<01:06:20.440> of 01:06:20.710 --> 01:06:20.720 align:start position:0% that so the io box has the same kind of 01:06:20.720 --> 01:06:26.269 align:start position:0% that so the io box has the same kind of like<01:06:21.760> uh<01:06:22.760> uh<01:06:22.960> public<01:06:23.279> key<01:06:23.480> and<01:06:23.599> secret<01:06:24.039> key 01:06:26.269 --> 01:06:26.279 align:start position:0% like uh uh public key and secret key 01:06:26.279 --> 01:06:28.829 align:start position:0% like uh uh public key and secret key so<01:06:26.440> we<01:06:26.520> have<01:06:26.640> the<01:06:26.720> same 01:06:28.829 --> 01:06:28.839 align:start position:0% so we have the same 01:06:28.839 --> 01:06:31.510 align:start position:0% so we have the same secrets<01:06:29.839> so<01:06:30.039> it's<01:06:30.200> kind<01:06:30.319> of<01:06:30.480> like<01:06:30.680> these<01:06:30.880> two 01:06:31.510 --> 01:06:31.520 align:start position:0% secrets so it's kind of like these two 01:06:31.520 --> 01:06:32.950 align:start position:0% secrets so it's kind of like these two these<01:06:31.640> are<01:06:31.839> two<01:06:32.079> different<01:06:32.359> trusted<01:06:32.720> parties 01:06:32.950 --> 01:06:32.960 align:start position:0% these are two different trusted parties 01:06:32.960 --> 01:06:34.349 align:start position:0% these are two different trusted parties and<01:06:33.039> they're<01:06:33.160> able<01:06:33.319> to<01:06:33.400> talk<01:06:33.640> to<01:06:33.799> each<01:06:33.920> other 01:06:34.349 --> 01:06:34.359 align:start position:0% and they're able to talk to each other 01:06:34.359 --> 01:06:36.150 align:start position:0% and they're able to talk to each other so<01:06:34.559> this<01:06:34.680> one<01:06:34.880> encrypts<01:06:35.400> some<01:06:35.640> values<01:06:35.960> for 01:06:36.150 --> 01:06:36.160 align:start position:0% so this one encrypts some values for 01:06:36.160 --> 01:06:37.390 align:start position:0% so this one encrypts some values for this<01:06:36.240> one<01:06:36.440> and<01:06:36.520> this<01:06:36.640> one<01:06:36.760> takes<01:06:37.000> those<01:06:37.160> values 01:06:37.390 --> 01:06:37.400 align:start position:0% this one and this one takes those values 01:06:37.400 --> 01:06:39.829 align:start position:0% this one and this one takes those values and<01:06:37.520> does<01:06:37.680> some<01:06:37.839> stuff<01:06:38.000> with<01:06:38.160> them<01:06:39.000> and<01:06:39.160> then 01:06:39.829 --> 01:06:39.839 align:start position:0% and does some stuff with them and then 01:06:39.839 --> 01:06:45.430 align:start position:0% and does some stuff with them and then we<01:06:39.960> can<01:06:40.160> have<01:06:40.359> like<01:06:40.520> our<01:06:40.760> arbitrary<01:06:41.599> compute 01:06:45.430 --> 01:06:45.440 align:start position:0% 01:06:45.440 --> 01:06:48.510 align:start position:0% here<01:06:46.440> and<01:06:46.640> we<01:06:46.760> do<01:06:46.920> our<01:06:47.119> compute<01:06:47.720> and<01:06:47.880> we<01:06:48.240> and<01:06:48.359> it 01:06:48.510 --> 01:06:48.520 align:start position:0% here and we do our compute and we and it 01:06:48.520 --> 01:06:51.150 align:start position:0% here and we do our compute and we and it and<01:06:48.640> it<01:06:48.720> outputs<01:06:49.200> the<01:06:49.400> actual<01:06:50.000> Tres 01:06:51.150 --> 01:06:51.160 align:start position:0% and it outputs the actual Tres 01:06:51.160 --> 01:07:01.309 align:start position:0% and it outputs the actual Tres up<01:06:52.240> okay<01:06:53.240> okay<01:06:53.640> how<01:06:53.760> is<01:06:54.000> this<01:06:54.480> any<01:06:54.720> questions 01:07:01.309 --> 01:07:01.319 align:start position:0% 01:07:01.319 --> 01:07:04.269 align:start position:0% yes<01:07:02.319> I<01:07:02.400> think<01:07:02.640> secret<01:07:03.079> key<01:07:03.319> is<01:07:03.640> included<01:07:04.079> in 01:07:04.269 --> 01:07:04.279 align:start position:0% yes I think secret key is included in 01:07:04.279 --> 01:07:07.150 align:start position:0% yes I think secret key is included in iob<01:07:04.680> box<01:07:05.000> but<01:07:05.200> is<01:07:05.279> it<01:07:05.599> make<01:07:06.119> able<01:07:06.520> that<01:07:07.000> no 01:07:07.150 --> 01:07:07.160 align:start position:0% iob box but is it make able that no 01:07:07.160 --> 01:07:09.990 align:start position:0% iob box but is it make able that no one's<01:07:07.440> know<01:07:07.760> that<01:07:08.000> secret<01:07:08.480> key<01:07:09.359> yeah<01:07:09.720> that's 01:07:09.990 --> 01:07:10.000 align:start position:0% one's know that secret key yeah that's 01:07:10.000 --> 01:07:12.589 align:start position:0% one's know that secret key yeah that's an<01:07:10.279> important<01:07:10.760> property<01:07:11.240> here<01:07:11.920> that<01:07:12.200> we<01:07:12.480> have 01:07:12.589 --> 01:07:12.599 align:start position:0% an important property here that we have 01:07:12.599 --> 01:07:14.230 align:start position:0% an important property here that we have to<01:07:12.760> make<01:07:12.880> sure<01:07:13.119> that<01:07:13.240> no<01:07:13.359> one<01:07:13.520> is<01:07:13.680> able<01:07:13.880> to<01:07:14.039> know 01:07:14.230 --> 01:07:14.240 align:start position:0% to make sure that no one is able to know 01:07:14.240 --> 01:07:16.109 align:start position:0% to make sure that no one is able to know the<01:07:14.400> secret<01:07:14.760> key<01:07:15.400> and<01:07:15.520> that's<01:07:15.720> one<01:07:15.839> of<01:07:15.960> the 01:07:16.109 --> 01:07:16.119 align:start position:0% the secret key and that's one of the 01:07:16.119 --> 01:07:18.190 align:start position:0% the secret key and that's one of the properties<01:07:16.480> that<01:07:16.599> we<01:07:16.760> get<01:07:17.000> from<01:07:17.359> the<01:07:17.720> like<01:07:18.039> the 01:07:18.190 --> 01:07:18.200 align:start position:0% properties that we get from the like the 01:07:18.200 --> 01:07:21.710 align:start position:0% properties that we get from the like the encryption<01:07:19.079> Step<01:07:19.480> At<01:07:19.599> the<01:07:19.720> very<01:07:20.200> start<01:07:21.200> yeah 01:07:21.710 --> 01:07:21.720 align:start position:0% encryption Step At the very start yeah 01:07:21.720 --> 01:07:23.750 align:start position:0% encryption Step At the very start yeah so<01:07:21.920> this<01:07:22.039> is<01:07:22.200> like<01:07:22.319> a<01:07:22.599> programmable 01:07:23.750 --> 01:07:23.760 align:start position:0% so this is like a programmable 01:07:23.760 --> 01:07:26.990 align:start position:0% so this is like a programmable encryption<01:07:24.760> ah<01:07:25.200> thank<01:07:25.359> you 01:07:26.990 --> 01:07:27.000 align:start position:0% encryption ah thank you 01:07:27.000 --> 01:07:29.430 align:start position:0% encryption ah thank you M 01:07:29.430 --> 01:07:29.440 align:start position:0% M 01:07:29.440 --> 01:07:33.510 align:start position:0% M yep<01:07:30.440> hello<01:07:30.960> so<01:07:31.319> if<01:07:31.440> you<01:07:31.559> are<01:07:32.440> uh<01:07:32.760> off<01:07:33.160> skating 01:07:33.510 --> 01:07:33.520 align:start position:0% yep hello so if you are uh off skating 01:07:33.520 --> 01:07:36.430 align:start position:0% yep hello so if you are uh off skating the<01:07:33.680> program<01:07:34.440> does<01:07:34.760> the<01:07:35.279> programmer<01:07:36.039> have<01:07:36.240> any 01:07:36.430 --> 01:07:36.440 align:start position:0% the program does the programmer have any 01:07:36.440 --> 01:07:38.349 align:start position:0% the program does the programmer have any advantage<01:07:36.880> by<01:07:37.039> knowing<01:07:37.319> the<01:07:37.440> actual<01:07:37.799> program 01:07:38.349 --> 01:07:38.359 align:start position:0% advantage by knowing the actual program 01:07:38.359 --> 01:07:40.829 align:start position:0% advantage by knowing the actual program and<01:07:38.520> if<01:07:38.680> so<01:07:39.039> like<01:07:39.480> how<01:07:39.680> can<01:07:39.960> other<01:07:40.319> people 01:07:40.829 --> 01:07:40.839 align:start position:0% and if so like how can other people 01:07:40.839 --> 01:07:43.109 align:start position:0% and if so like how can other people agree<01:07:41.200> that<01:07:41.559> the<01:07:41.760> program<01:07:42.119> is<01:07:42.279> corrective 01:07:43.109 --> 01:07:43.119 align:start position:0% agree that the program is corrective 01:07:43.119 --> 01:07:46.230 align:start position:0% agree that the program is corrective it's<01:07:43.319> sophiscated<01:07:44.200> yeah<01:07:45.200> okay<01:07:45.400> so<01:07:45.640> this<01:07:45.760> is<01:07:46.160> I 01:07:46.230 --> 01:07:46.240 align:start position:0% it's sophiscated yeah okay so this is I 01:07:46.240 --> 01:07:48.549 align:start position:0% it's sophiscated yeah okay so this is I saw<01:07:46.520> this<01:07:46.680> in<01:07:47.079> in<01:07:47.279> one<01:07:47.440> of<01:07:47.640> the<01:07:48.200> this<01:07:48.319> is<01:07:48.400> a 01:07:48.549 --> 01:07:48.559 align:start position:0% saw this in in one of the this is a 01:07:48.559 --> 01:07:50.950 align:start position:0% saw this in in one of the this is a question<01:07:48.960> earlier<01:07:49.960> uh<01:07:50.200> that<01:07:50.400> vitalic<01:07:50.760> didn't 01:07:50.950 --> 01:07:50.960 align:start position:0% question earlier uh that vitalic didn't 01:07:50.960 --> 01:07:52.710 align:start position:0% question earlier uh that vitalic didn't answer<01:07:51.279> but<01:07:51.440> yeah<01:07:51.640> I<01:07:51.839> I<01:07:51.960> think<01:07:52.200> this<01:07:52.279> is<01:07:52.400> a<01:07:52.520> good 01:07:52.710 --> 01:07:52.720 align:start position:0% answer but yeah I I think this is a good 01:07:52.720 --> 01:07:55.029 align:start position:0% answer but yeah I I think this is a good question<01:07:53.480> so<01:07:53.760> basically<01:07:54.319> like<01:07:54.520> in<01:07:54.680> general 01:07:55.029 --> 01:07:55.039 align:start position:0% question so basically like in general 01:07:55.039 --> 01:07:56.390 align:start position:0% question so basically like in general what<01:07:55.119> we<01:07:55.240> would<01:07:55.559> do<01:07:55.680> is<01:07:55.760> we<01:07:55.839> would<01:07:56.039> publish 01:07:56.390 --> 01:07:56.400 align:start position:0% what we would do is we would publish 01:07:56.400 --> 01:07:58.349 align:start position:0% what we would do is we would publish most<01:07:56.559> of<01:07:56.720> the<01:07:56.920> program<01:07:57.559> that<01:07:57.839> the<01:07:57.960> only<01:07:58.160> thing 01:07:58.349 --> 01:07:58.359 align:start position:0% most of the program that the only thing 01:07:58.359 --> 01:08:00.829 align:start position:0% most of the program that the only thing that<01:07:58.480> we<01:07:58.680> really<01:07:58.960> care<01:07:59.400> about<01:08:00.039> about<01:08:00.599> about 01:08:00.829 --> 01:08:00.839 align:start position:0% that we really care about about about 01:08:00.839 --> 01:08:02.589 align:start position:0% that we really care about about about hiding<01:08:01.240> is<01:08:01.559> is<01:08:01.760> is<01:08:01.920> what<01:08:02.079> this<01:08:02.240> person<01:08:02.440> was 01:08:02.589 --> 01:08:02.599 align:start position:0% hiding is is is what this person was 01:08:02.599 --> 01:08:04.549 align:start position:0% hiding is is is what this person was getting<01:08:02.839> at<01:08:03.240> that<01:08:03.480> all<01:08:03.640> we<01:08:03.760> care<01:08:04.079> about<01:08:04.279> hiding 01:08:04.549 --> 01:08:04.559 align:start position:0% getting at that all we care about hiding 01:08:04.559 --> 01:08:06.710 align:start position:0% getting at that all we care about hiding is<01:08:04.720> that<01:08:04.920> is<01:08:05.000> a<01:08:05.119> private<01:08:05.440> key<01:08:06.079> like<01:08:06.200> we're<01:08:06.520> okay 01:08:06.710 --> 01:08:06.720 align:start position:0% is that is a private key like we're okay 01:08:06.720 --> 01:08:08.710 align:start position:0% is that is a private key like we're okay with<01:08:06.880> someone<01:08:07.319> like<01:08:07.720> the<01:08:07.920> property<01:08:08.240> of<01:08:08.440> IO 01:08:08.710 --> 01:08:08.720 align:start position:0% with someone like the property of IO 01:08:08.720 --> 01:08:10.190 align:start position:0% with someone like the property of IO that<01:08:08.839> we<01:08:09.000> care<01:08:09.200> about<01:08:09.520> is<01:08:09.680> not<01:08:09.839> that<01:08:10.000> the 01:08:10.190 --> 01:08:10.200 align:start position:0% that we care about is not that the 01:08:10.200 --> 01:08:12.109 align:start position:0% that we care about is not that the program<01:08:10.520> is<01:08:10.680> like<01:08:10.960> indistinguishable<01:08:11.960> it's 01:08:12.109 --> 01:08:12.119 align:start position:0% program is like indistinguishable it's 01:08:12.119 --> 01:08:13.589 align:start position:0% program is like indistinguishable it's that<01:08:12.279> the<01:08:12.400> private<01:08:12.760> key<01:08:13.079> is 01:08:13.589 --> 01:08:13.599 align:start position:0% that the private key is 01:08:13.599 --> 01:08:16.430 align:start position:0% that the private key is indistinguishable<01:08:14.599> like<01:08:14.880> in<01:08:15.119> most<01:08:15.480> cases<01:08:16.239> we 01:08:16.430 --> 01:08:16.440 align:start position:0% indistinguishable like in most cases we 01:08:16.440 --> 01:08:18.430 align:start position:0% indistinguishable like in most cases we want<01:08:16.799> to<01:08:17.040> tell<01:08:17.239> you<01:08:17.719> everything<01:08:18.040> about<01:08:18.239> the 01:08:18.430 --> 01:08:18.440 align:start position:0% want to tell you everything about the 01:08:18.440 --> 01:08:20.390 align:start position:0% want to tell you everything about the program<01:08:19.080> we<01:08:19.199> want<01:08:19.359> to<01:08:19.520> explain<01:08:19.920> everything 01:08:20.390 --> 01:08:20.400 align:start position:0% program we want to explain everything 01:08:20.400 --> 01:08:26.669 align:start position:0% program we want to explain everything except<01:08:21.000> the<01:08:21.159> private<01:08:21.520> key 01:08:26.669 --> 01:08:26.679 align:start position:0% 01:08:26.679 --> 01:08:30.030 align:start position:0% cool<01:08:27.679> uh<01:08:27.960> so<01:08:28.799> questions<01:08:29.199> like<01:08:29.359> some<01:08:29.560> intuition 01:08:30.030 --> 01:08:30.040 align:start position:0% cool uh so questions like some intuition 01:08:30.040 --> 01:08:32.990 align:start position:0% cool uh so questions like some intuition for<01:08:30.440> the<01:08:30.839> the<01:08:31.120> blowup<01:08:32.000> so<01:08:32.359> if<01:08:32.480> you<01:08:32.719> let's<01:08:32.880> say 01:08:32.990 --> 01:08:33.000 align:start position:0% for the the blowup so if you let's say 01:08:33.000 --> 01:08:36.030 align:start position:0% for the the blowup so if you let's say you<01:08:33.080> implement<01:08:33.480> CPS<01:08:34.080> with<01:08:34.239> this<01:08:34.440> iio<01:08:34.839> box<01:08:35.839> uh 01:08:36.030 --> 01:08:36.040 align:start position:0% you implement CPS with this iio box uh 01:08:36.040 --> 01:08:37.990 align:start position:0% you implement CPS with this iio box uh and<01:08:36.159> then<01:08:36.319> if<01:08:36.440> you<01:08:36.520> have<01:08:36.640> a<01:08:36.719> more<01:08:36.960> complex<01:08:37.359> CP 01:08:37.990 --> 01:08:38.000 align:start position:0% and then if you have a more complex CP 01:08:38.000 --> 01:08:39.390 align:start position:0% and then if you have a more complex CP how<01:08:38.120> does<01:08:38.279> it<01:08:38.440> relate<01:08:38.719> to<01:08:38.880> sort<01:08:39.040> of<01:08:39.199> the 01:08:39.390 --> 01:08:39.400 align:start position:0% how does it relate to sort of the 01:08:39.400 --> 01:08:41.149 align:start position:0% how does it relate to sort of the exponential<01:08:39.960> blow<01:08:40.239> up<01:08:40.560> like<01:08:40.719> what<01:08:40.799> is<01:08:40.920> a<01:08:41.000> good 01:08:41.149 --> 01:08:41.159 align:start position:0% exponential blow up like what is a good 01:08:41.159 --> 01:08:44.590 align:start position:0% exponential blow up like what is a good intuition<01:08:41.719> for<01:08:42.440> how<01:08:43.120> how<01:08:43.719> much<01:08:43.960> SI<01:08:44.279> efficient 01:08:44.590 --> 01:08:44.600 align:start position:0% intuition for how how much SI efficient 01:08:44.600 --> 01:08:46.870 align:start position:0% intuition for how how much SI efficient it<01:08:44.759> become<01:08:45.120> as<01:08:45.440> of<01:08:45.600> the<01:08:45.920> logic<01:08:46.359> inside<01:08:46.719> this 01:08:46.870 --> 01:08:46.880 align:start position:0% it become as of the logic inside this 01:08:46.880 --> 01:08:47.910 align:start position:0% it become as of the logic inside this box 01:08:47.910 --> 01:08:47.920 align:start position:0% box 01:08:47.920 --> 01:08:50.590 align:start position:0% box changes<01:08:48.920> oh<01:08:49.199> so<01:08:49.799> it<01:08:49.960> seems<01:08:50.279> like<01:08:50.400> you're 01:08:50.590 --> 01:08:50.600 align:start position:0% changes oh so it seems like you're 01:08:50.600 --> 01:08:52.390 align:start position:0% changes oh so it seems like you're asking<01:08:50.960> two<01:08:51.239> questions<01:08:51.679> here<01:08:52.000> like<01:08:52.159> one<01:08:52.279> of 01:08:52.390 --> 01:08:52.400 align:start position:0% asking two questions here like one of 01:08:52.400 --> 01:08:54.309 align:start position:0% asking two questions here like one of them<01:08:52.560> is<01:08:52.719> like<01:08:52.880> what's<01:08:53.080> the<01:08:53.199> overhead<01:08:53.520> of<01:08:53.679> IO 01:08:54.309 --> 01:08:54.319 align:start position:0% them is like what's the overhead of IO 01:08:54.319 --> 01:08:57.149 align:start position:0% them is like what's the overhead of IO and<01:08:54.440> the<01:08:54.600> other<01:08:54.920> is<01:08:55.080> that<01:08:55.319> like<01:08:55.520> like<01:08:56.199> is<01:08:56.920> could 01:08:57.149 --> 01:08:57.159 align:start position:0% and the other is that like like is could 01:08:57.159 --> 01:08:59.390 align:start position:0% and the other is that like like is could IO<01:08:57.520> potentially<01:08:57.920> be<01:08:58.080> competitive<01:08:58.560> with<01:08:58.679> dkps 01:08:59.390 --> 01:08:59.400 align:start position:0% IO potentially be competitive with dkps 01:08:59.400 --> 01:09:02.229 align:start position:0% IO potentially be competitive with dkps in<01:08:59.480> terms<01:08:59.759> of<01:09:00.000> like<01:09:00.239> Pro<01:09:00.799> time<01:09:01.679> are<01:09:01.759> you<01:09:01.960> asking 01:09:02.229 --> 01:09:02.239 align:start position:0% in terms of like Pro time are you asking 01:09:02.239 --> 01:09:23.510 align:start position:0% in terms of like Pro time are you asking both<01:09:02.440> or<01:09:02.520> are<01:09:02.640> you<01:09:02.759> asking<01:09:03.000> one<01:09:03.120> of 01:09:23.510 --> 01:09:23.520 align:start position:0% 01:09:23.520 --> 01:09:27.590 align:start position:0% them<01:09:24.520> on<01:09:24.679> the<01:09:24.799> logic<01:09:25.080> inside<01:09:25.480> I 01:09:27.590 --> 01:09:27.600 align:start position:0% them on the logic inside I 01:09:27.600 --> 01:09:30.030 align:start position:0% them on the logic inside I box<01:09:28.600> huh<01:09:28.880> it's<01:09:29.080> basically<01:09:29.560> both<01:09:29.759> questions 01:09:30.030 --> 01:09:30.040 align:start position:0% box huh it's basically both questions 01:09:30.040 --> 01:09:31.910 align:start position:0% box huh it's basically both questions that<01:09:30.239> you<01:09:30.440> you<01:09:31.000> okay<01:09:31.279> okay<01:09:31.440> let<01:09:31.520> me<01:09:31.640> answer 01:09:31.910 --> 01:09:31.920 align:start position:0% that you you okay okay let me answer 01:09:31.920 --> 01:09:34.550 align:start position:0% that you you okay okay let me answer both<01:09:32.120> questions<01:09:32.480> then<01:09:33.319> uh<01:09:33.960> so<01:09:34.159> the<01:09:34.319> first 01:09:34.550 --> 01:09:34.560 align:start position:0% both questions then uh so the first 01:09:34.560 --> 01:09:35.950 align:start position:0% both questions then uh so the first question<01:09:34.880> is<01:09:35.040> that<01:09:35.159> it<01:09:35.319> depends<01:09:35.640> upon<01:09:35.839> the 01:09:35.950 --> 01:09:35.960 align:start position:0% question is that it depends upon the 01:09:35.960 --> 01:09:37.870 align:start position:0% question is that it depends upon the Assumption<01:09:36.679> like<01:09:36.839> different<01:09:37.120> IO<01:09:37.600> different 01:09:37.870 --> 01:09:37.880 align:start position:0% Assumption like different IO different 01:09:37.880 --> 01:09:40.910 align:start position:0% Assumption like different IO different IO<01:09:38.239> schemes<01:09:39.199> have<01:09:39.480> different<01:09:39.880> overhead<01:09:40.759> like 01:09:40.910 --> 01:09:40.920 align:start position:0% IO schemes have different overhead like 01:09:40.920 --> 01:09:42.630 align:start position:0% IO schemes have different overhead like some<01:09:41.080> of<01:09:41.199> the<01:09:41.400> more<01:09:41.719> like<01:09:42.000> extreme 01:09:42.630 --> 01:09:42.640 align:start position:0% some of the more like extreme 01:09:42.640 --> 01:09:45.990 align:start position:0% some of the more like extreme assumptions<01:09:43.279> are<01:09:43.600> actually<01:09:44.520> pretty<01:09:45.520> pretty 01:09:45.990 --> 01:09:46.000 align:start position:0% assumptions are actually pretty pretty 01:09:46.000 --> 01:09:48.749 align:start position:0% assumptions are actually pretty pretty efficient<01:09:46.920> in<01:09:47.080> terms<01:09:47.319> of<01:09:47.640> execution<01:09:48.640> the 01:09:48.749 --> 01:09:48.759 align:start position:0% efficient in terms of execution the 01:09:48.759 --> 01:09:50.430 align:start position:0% efficient in terms of execution the setup<01:09:49.159> is<01:09:49.359> the<01:09:49.520> main 01:09:50.430 --> 01:09:50.440 align:start position:0% setup is the main 01:09:50.440 --> 01:09:54.390 align:start position:0% setup is the main cost<01:09:51.560> um<01:09:52.560> but<01:09:52.679> it<01:09:52.960> remains<01:09:53.199> to<01:09:53.359> be<01:09:53.520> seen<01:09:54.239> it's 01:09:54.390 --> 01:09:54.400 align:start position:0% cost um but it remains to be seen it's 01:09:54.400 --> 01:09:56.550 align:start position:0% cost um but it remains to be seen it's still<01:09:54.600> very<01:09:54.760> early<01:09:55.040> so<01:09:55.199> I<01:09:55.400> can't<01:09:55.600> really<01:09:55.880> give 01:09:56.550 --> 01:09:56.560 align:start position:0% still very early so I can't really give 01:09:56.560 --> 01:10:00.070 align:start position:0% still very early so I can't really give specific<01:09:56.960> numbers<01:09:57.280> or<01:09:57.840> whatever<01:09:58.840> um<01:09:59.679> I'm<01:09:59.880> not 01:10:00.070 --> 01:10:00.080 align:start position:0% specific numbers or whatever um I'm not 01:10:00.080 --> 01:10:02.630 align:start position:0% specific numbers or whatever um I'm not sure<01:10:00.440> if<01:10:00.880> like<01:10:01.320> I<01:10:01.480> suppose<01:10:01.840> that<01:10:02.120> like<01:10:02.480> the 01:10:02.630 --> 01:10:02.640 align:start position:0% sure if like I suppose that like the 01:10:02.640 --> 01:10:04.350 align:start position:0% sure if like I suppose that like the thing<01:10:02.840> that<01:10:02.960> you're<01:10:03.280> gaining<01:10:03.719> from<01:10:03.920> the<01:10:04.040> io 01:10:04.350 --> 01:10:04.360 align:start position:0% thing that you're gaining from the io 01:10:04.360 --> 01:10:06.709 align:start position:0% thing that you're gaining from the io zkp<01:10:05.120> is<01:10:05.280> the<01:10:05.520> succinct<01:10:06.080> verifier<01:10:06.600> the 01:10:06.709 --> 01:10:06.719 align:start position:0% zkp is the succinct verifier the 01:10:06.719 --> 01:10:08.430 align:start position:0% zkp is the succinct verifier the verifier<01:10:07.159> is<01:10:07.480> really<01:10:07.800> easy<01:10:08.120> it's<01:10:08.280> just 01:10:08.430 --> 01:10:08.440 align:start position:0% verifier is really easy it's just 01:10:08.440 --> 01:10:11.030 align:start position:0% verifier is really easy it's just verifying<01:10:08.840> a<01:10:08.960> signature<01:10:09.960> so<01:10:10.159> it's<01:10:10.440> much<01:10:10.800> less 01:10:11.030 --> 01:10:11.040 align:start position:0% verifying a signature so it's much less 01:10:11.040 --> 01:10:12.990 align:start position:0% verifying a signature so it's much less overhead<01:10:11.640> than<01:10:11.920> traditional<01:10:12.320> Zer<01:10:12.560> knowledge 01:10:12.990 --> 01:10:13.000 align:start position:0% overhead than traditional Zer knowledge 01:10:13.000 --> 01:10:15.350 align:start position:0% overhead than traditional Zer knowledge proofs<01:10:14.000> uh<01:10:14.159> which<01:10:14.320> tend<01:10:14.560> to<01:10:14.679> be<01:10:14.880> like<01:10:15.000> a<01:10:15.120> couple 01:10:15.350 --> 01:10:15.360 align:start position:0% proofs uh which tend to be like a couple 01:10:15.360 --> 01:10:20.110 align:start position:0% proofs uh which tend to be like a couple of<01:10:15.840> pairings<01:10:16.840> uh<01:10:17.000> the<01:10:17.159> best<01:10:17.400> gr<01:10:17.760> 16<01:10:18.199> or<01:10:18.880> F<01:10:19.199> long 01:10:20.110 --> 01:10:20.120 align:start position:0% of pairings uh the best gr 16 or F long 01:10:20.120 --> 01:10:21.709 align:start position:0% of pairings uh the best gr 16 or F long is<01:10:20.280> like<01:10:20.400> a<01:10:20.560> pairing<01:10:20.960> and<01:10:21.239> like<01:10:21.360> some<01:10:21.520> other 01:10:21.709 --> 01:10:21.719 align:start position:0% is like a pairing and like some other 01:10:21.719 --> 01:10:24.590 align:start position:0% is like a pairing and like some other scal<01:10:22.080> mes<01:10:22.320> and<01:10:22.480> stuff<01:10:23.199> so<01:10:23.560> it's<01:10:23.760> better<01:10:24.480> uh 01:10:24.590 --> 01:10:24.600 align:start position:0% scal mes and stuff so it's better uh 01:10:24.600 --> 01:10:26.229 align:start position:0% scal mes and stuff so it's better uh it's<01:10:24.760> faster<01:10:25.080> ver<01:10:25.440> fire<01:10:25.600> but<01:10:25.679> the<01:10:25.760> appr<01:10:26.080> time 01:10:26.229 --> 01:10:26.239 align:start position:0% it's faster ver fire but the appr time 01:10:26.239 --> 01:10:28.870 align:start position:0% it's faster ver fire but the appr time is<01:10:26.400> likely<01:10:26.640> going<01:10:26.719> to<01:10:26.880> be<01:10:27.120> like<01:10:27.440> really<01:10:27.679> a<01:10:27.880> lot 01:10:28.870 --> 01:10:28.880 align:start position:0% is likely going to be like really a lot 01:10:28.880 --> 01:10:31.630 align:start position:0% is likely going to be like really a lot worse<01:10:29.560> at<01:10:29.719> least<01:10:29.920> in<01:10:30.040> the<01:10:30.159> short<01:10:30.360> term<01:10:31.360> uh<01:10:31.520> but 01:10:31.630 --> 01:10:31.640 align:start position:0% worse at least in the short term uh but 01:10:31.640 --> 01:10:33.910 align:start position:0% worse at least in the short term uh but it<01:10:31.800> depends<01:10:32.199> on<01:10:32.600> the<01:10:33.159> the<01:10:33.400> assumptions<01:10:33.800> that 01:10:33.910 --> 01:10:33.920 align:start position:0% it depends on the the assumptions that 01:10:33.920 --> 01:10:35.910 align:start position:0% it depends on the the assumptions that we<01:10:34.040> end<01:10:34.199> up<01:10:34.320> using<01:10:34.560> or<01:10:34.719> the<01:10:34.920> basis<01:10:35.360> that<01:10:35.480> we're 01:10:35.910 --> 01:10:35.920 align:start position:0% we end up using or the basis that we're 01:10:35.920 --> 01:10:37.790 align:start position:0% we end up using or the basis that we're end<01:10:36.040> up<01:10:36.159> building<01:10:36.440> things<01:10:36.600> on<01:10:37.000> so<01:10:37.440> not<01:10:37.600> really 01:10:37.790 --> 01:10:37.800 align:start position:0% end up building things on so not really 01:10:37.800 --> 01:10:39.430 align:start position:0% end up building things on so not really clear<01:10:38.080> yet<01:10:38.679> I<01:10:38.760> don't<01:10:38.920> think<01:10:39.080> that<01:10:39.199> Zer 01:10:39.430 --> 01:10:39.440 align:start position:0% clear yet I don't think that Zer 01:10:39.440 --> 01:10:40.470 align:start position:0% clear yet I don't think that Zer knowledge<01:10:39.640> proofs<01:10:39.880> need<01:10:39.960> to<01:10:40.080> worry<01:10:40.320> about 01:10:40.470 --> 01:10:40.480 align:start position:0% knowledge proofs need to worry about 01:10:40.480 --> 01:10:42.070 align:start position:0% knowledge proofs need to worry about anything<01:10:40.880> anytime<01:10:41.280> soon<01:10:41.640> I<01:10:41.719> think<01:10:41.880> that<01:10:42.000> they 01:10:42.070 --> 01:10:42.080 align:start position:0% anything anytime soon I think that they 01:10:42.080 --> 01:10:43.790 align:start position:0% anything anytime soon I think that they are<01:10:42.199> going<01:10:42.280> to<01:10:42.640> remain<01:10:43.120> like<01:10:43.280> this<01:10:43.360> is<01:10:43.440> more<01:10:43.600> an 01:10:43.790 --> 01:10:43.800 align:start position:0% are going to remain like this is more an 01:10:43.800 --> 01:10:45.350 align:start position:0% are going to remain like this is more an example<01:10:44.360> like<01:10:44.600> this<01:10:44.679> is<01:10:44.800> more<01:10:44.920> an<01:10:45.040> example<01:10:45.280> of 01:10:45.350 --> 01:10:45.360 align:start position:0% example like this is more an example of 01:10:45.360 --> 01:10:46.630 align:start position:0% example like this is more an example of what<01:10:45.440> you<01:10:45.520> can<01:10:45.640> do<01:10:45.840> I'm<01:10:45.960> not<01:10:46.080> saying<01:10:46.320> that<01:10:46.480> like 01:10:46.630 --> 01:10:46.640 align:start position:0% what you can do I'm not saying that like 01:10:46.640 --> 01:10:49.990 align:start position:0% what you can do I'm not saying that like oh<01:10:46.800> this<01:10:46.920> is<01:10:47.040> what<01:10:47.159> we<01:10:47.280> should<01:10:47.560> do<01:10:48.480> yeah<01:10:49.159> okay 01:10:49.990 --> 01:10:50.000 align:start position:0% oh this is what we should do yeah okay 01:10:50.000 --> 01:10:53.390 align:start position:0% oh this is what we should do yeah okay Barry<01:10:50.320> it's<01:10:50.480> Q&A<01:10:50.960> time<01:10:51.760> ah<01:10:52.360> okay<01:10:52.480> sorry<01:10:52.800> Jord 01:10:53.390 --> 01:10:53.400 align:start position:0% Barry it's Q&A time ah okay sorry Jord 01:10:53.400 --> 01:10:54.950 align:start position:0% Barry it's Q&A time ah okay sorry Jord no<01:10:53.560> it's<01:10:53.760> great<01:10:54.440> that<01:10:54.520> was<01:10:54.640> the<01:10:54.760> first 01:10:54.950 --> 01:10:54.960 align:start position:0% no it's great that was the first 01:10:54.960 --> 01:10:56.430 align:start position:0% no it's great that was the first question 01:10:56.430 --> 01:10:56.440 align:start position:0% question 01:10:56.440 --> 01:10:59.030 align:start position:0% question um<01:10:57.440> I'll<01:10:57.679> read<01:10:57.920> them<01:10:58.320> from<01:10:58.480> the<01:10:58.600> ones<01:10:58.800> with<01:10:58.920> the 01:10:59.030 --> 01:10:59.040 align:start position:0% um I'll read them from the ones with the 01:10:59.040 --> 01:11:00.510 align:start position:0% um I'll read them from the ones with the most<01:10:59.239> votes<01:10:59.520> but<01:10:59.640> feel<01:10:59.800> free<01:11:00.000> to<01:11:00.080> not<01:11:00.280> answer 01:11:00.510 --> 01:11:00.520 align:start position:0% most votes but feel free to not answer 01:11:00.520 --> 01:11:02.870 align:start position:0% most votes but feel free to not answer or<01:11:00.719> skip<01:11:00.960> to<01:11:01.080> the<01:11:01.199> next<01:11:01.400> one<01:11:01.840> okay<01:11:02.360> um<01:11:02.560> the<01:11:02.719> top 01:11:02.870 --> 01:11:02.880 align:start position:0% or skip to the next one okay um the top 01:11:02.880 --> 01:11:04.790 align:start position:0% or skip to the next one okay um the top one<01:11:03.000> is<01:11:03.159> can<01:11:03.280> you<01:11:03.400> explain<01:11:03.679> IO<01:11:03.960> as<01:11:04.320> explain<01:11:04.679> me 01:11:04.790 --> 01:11:04.800 align:start position:0% one is can you explain IO as explain me 01:11:04.800 --> 01:11:06.750 align:start position:0% one is can you explain IO as explain me like<01:11:04.960> I'm<01:11:05.199> five<01:11:05.640> and<01:11:05.800> why<01:11:05.960> do<01:11:06.080> we<01:11:06.199> need<01:11:06.400> to<01:11:06.520> use 01:11:06.750 --> 01:11:06.760 align:start position:0% like I'm five and why do we need to use 01:11:06.760 --> 01:11:10.310 align:start position:0% like I'm five and why do we need to use IO<01:11:07.040> instead<01:11:07.239> of<01:11:07.360> other<01:11:07.719> zkps<01:11:08.719> ah<01:11:09.280> ah<01:11:09.560> like<01:11:10.040> oh 01:11:10.310 --> 01:11:10.320 align:start position:0% IO instead of other zkps ah ah like oh 01:11:10.320 --> 01:11:11.910 align:start position:0% IO instead of other zkps ah ah like oh you<01:11:10.440> know<01:11:10.640> what<01:11:10.880> like<01:11:11.000> I<01:11:11.080> feel<01:11:11.440> like<01:11:11.600> we<01:11:11.719> got 01:11:11.910 --> 01:11:11.920 align:start position:0% you know what like I feel like we got 01:11:11.920 --> 01:11:13.510 align:start position:0% you know what like I feel like we got into<01:11:12.159> so<01:11:12.280> much<01:11:12.480> trouble<01:11:12.840> because<01:11:12.960> we<01:11:13.120> abused 01:11:13.510 --> 01:11:13.520 align:start position:0% into so much trouble because we abused 01:11:13.520 --> 01:11:15.990 align:start position:0% into so much trouble because we abused the<01:11:13.640> zero<01:11:13.960> knowledge<01:11:14.360> proof<01:11:14.920> not<01:11:15.320> or<01:11:15.480> name<01:11:15.760> for 01:11:15.990 --> 01:11:16.000 align:start position:0% the zero knowledge proof not or name for 01:11:16.000 --> 01:11:17.750 align:start position:0% the zero knowledge proof not or name for such<01:11:16.120> a<01:11:16.280> long<01:11:16.520> time<01:11:17.000> than<01:11:17.199> that<01:11:17.400> like<01:11:17.560> this 01:11:17.750 --> 01:11:17.760 align:start position:0% such a long time than that like this 01:11:17.760 --> 01:11:19.590 align:start position:0% such a long time than that like this question<01:11:18.120> just<01:11:18.520> it's<01:11:18.679> hard<01:11:18.880> for<01:11:19.000> me<01:11:19.120> to 01:11:19.590 --> 01:11:19.600 align:start position:0% question just it's hard for me to 01:11:19.600 --> 01:11:21.030 align:start position:0% question just it's hard for me to understand<01:11:19.880> what<01:11:20.080> this<01:11:20.239> means<01:11:20.520> by<01:11:20.679> like<01:11:20.800> other 01:11:21.030 --> 01:11:21.040 align:start position:0% understand what this means by like other 01:11:21.040 --> 01:11:22.950 align:start position:0% understand what this means by like other zerge<01:11:21.520> proofs<01:11:22.040> cuz<01:11:22.199> I<01:11:22.280> suppose<01:11:22.560> that<01:11:22.760> this 01:11:22.950 --> 01:11:22.960 align:start position:0% zerge proofs cuz I suppose that this 01:11:22.960 --> 01:11:24.950 align:start position:0% zerge proofs cuz I suppose that this person<01:11:23.199> is<01:11:23.360> thinking<01:11:23.679> that<01:11:23.880> like<01:11:24.360> oh<01:11:24.840> they 01:11:24.950 --> 01:11:24.960 align:start position:0% person is thinking that like oh they 01:11:24.960 --> 01:11:27.070 align:start position:0% person is thinking that like oh they just<01:11:25.400> this<01:11:25.520> blanket<01:11:25.880> term<01:11:26.080> for<01:11:26.280> all<01:11:26.520> like 01:11:27.070 --> 01:11:27.080 align:start position:0% just this blanket term for all like 01:11:27.080 --> 01:11:29.030 align:start position:0% just this blanket term for all like privacy<01:11:27.760> technology<01:11:28.320> and<01:11:28.480> that's<01:11:28.640> zerge 01:11:29.030 --> 01:11:29.040 align:start position:0% privacy technology and that's zerge 01:11:29.040 --> 01:11:32.270 align:start position:0% privacy technology and that's zerge proes<01:11:29.960> so<01:11:30.719> ah<01:11:30.960> so<01:11:31.320> I<01:11:31.400> think<01:11:31.640> that<01:11:31.800> the<01:11:32.040> key 01:11:32.270 --> 01:11:32.280 align:start position:0% proes so ah so I think that the key 01:11:32.280 --> 01:11:35.030 align:start position:0% proes so ah so I think that the key thing<01:11:33.040> that<01:11:33.480> iio<01:11:33.960> gives<01:11:34.199> is<01:11:34.320> a<01:11:34.480> non- 01:11:35.030 --> 01:11:35.040 align:start position:0% thing that iio gives is a non- 01:11:35.040 --> 01:11:36.910 align:start position:0% thing that iio gives is a non- interactivity<01:11:36.040> I<01:11:36.159> think<01:11:36.360> that<01:11:36.520> like<01:11:36.719> that's 01:11:36.910 --> 01:11:36.920 align:start position:0% interactivity I think that like that's 01:11:36.920 --> 01:11:38.990 align:start position:0% interactivity I think that like that's the<01:11:37.040> missing<01:11:37.440> piece<01:11:37.639> of<01:11:37.760> the<01:11:37.920> puzzle<01:11:38.440> but<01:11:38.560> zkps 01:11:38.990 --> 01:11:39.000 align:start position:0% the missing piece of the puzzle but zkps 01:11:39.000 --> 01:11:40.790 align:start position:0% the missing piece of the puzzle but zkps are<01:11:39.360> that<01:11:39.480> people<01:11:39.679> use<01:11:39.880> are<01:11:40.000> non-<01:11:40.199> interactive 01:11:40.790 --> 01:11:40.800 align:start position:0% are that people use are non- interactive 01:11:40.800 --> 01:11:42.189 align:start position:0% are that people use are non- interactive I<01:11:40.880> think<01:11:41.080> I<01:11:41.159> think<01:11:41.360> the<01:11:41.480> person<01:11:41.679> doesn't 01:11:42.189 --> 01:11:42.199 align:start position:0% I think I think the person doesn't 01:11:42.199 --> 01:11:44.790 align:start position:0% I think I think the person doesn't understand<01:11:42.440> that<01:11:42.800> yet<01:11:43.400> that<01:11:43.560> zkps<01:11:44.320> cannot<01:11:44.639> do 01:11:44.790 --> 01:11:44.800 align:start position:0% understand that yet that zkps cannot do 01:11:44.800 --> 01:11:47.070 align:start position:0% understand that yet that zkps cannot do everything<01:11:45.159> far<01:11:45.400> from<01:11:45.600> it<01:11:46.159> yeah<01:11:46.560> yeah<01:11:46.760> zero 01:11:47.070 --> 01:11:47.080 align:start position:0% everything far from it yeah yeah zero 01:11:47.080 --> 01:11:48.350 align:start position:0% everything far from it yeah yeah zero zero<01:11:47.320> knowledge<01:11:47.560> proofs<01:11:47.840> are<01:11:47.920> a<01:11:48.080> single 01:11:48.350 --> 01:11:48.360 align:start position:0% zero knowledge proofs are a single 01:11:48.360 --> 01:11:51.110 align:start position:0% zero knowledge proofs are a single player<01:11:48.639> technology<01:11:49.639> iio<01:11:50.000> is<01:11:50.080> a<01:11:50.199> multiplayer 01:11:51.110 --> 01:11:51.120 align:start position:0% player technology iio is a multiplayer 01:11:51.120 --> 01:11:53.550 align:start position:0% player technology iio is a multiplayer technology<01:11:52.120> this<01:11:52.239> is<01:11:52.440> what<01:11:52.639> we're<01:11:53.320> this<01:11:53.400> is 01:11:53.550 --> 01:11:53.560 align:start position:0% technology this is what we're this is 01:11:53.560 --> 01:11:55.870 align:start position:0% technology this is what we're this is what<01:11:53.679> seems<01:11:53.960> interesting<01:11:54.320> about<01:11:54.560> this 01:11:55.870 --> 01:11:55.880 align:start position:0% what seems interesting about this 01:11:55.880 --> 01:11:57.189 align:start position:0% what seems interesting about this we<01:11:56.000> can<01:11:56.120> take<01:11:56.320> the<01:11:56.400> other<01:11:56.600> one<01:11:56.800> which<01:11:56.920> is<01:11:57.080> how 01:11:57.189 --> 01:11:57.199 align:start position:0% we can take the other one which is how 01:11:57.199 --> 01:12:00.030 align:start position:0% we can take the other one which is how do<01:11:57.320> we<01:11:57.440> get<01:11:57.560> from<01:11:57.719> weeks<01:11:57.960> to<01:11:58.159> seconds<01:11:58.480> for<01:11:59.040> Io 01:12:00.030 --> 01:12:00.040 align:start position:0% do we get from weeks to seconds for Io 01:12:00.040 --> 01:12:02.790 align:start position:0% do we get from weeks to seconds for Io uh<01:12:01.040> I<01:12:01.159> suppose<01:12:01.520> we<01:12:01.639> just<01:12:01.800> have<01:12:01.920> to<01:12:02.239> like<01:12:02.440> try 01:12:02.790 --> 01:12:02.800 align:start position:0% uh I suppose we just have to like try 01:12:02.800 --> 01:12:04.709 align:start position:0% uh I suppose we just have to like try more<01:12:03.040> we<01:12:03.199> haven't<01:12:03.400> really<01:12:03.560> tried<01:12:03.840> at 01:12:04.709 --> 01:12:04.719 align:start position:0% more we haven't really tried at 01:12:04.719 --> 01:12:08.550 align:start position:0% more we haven't really tried at all<01:12:05.719> um<01:12:06.719> I<01:12:06.840> think<01:12:07.360> I<01:12:07.440> don't<01:12:07.600> know<01:12:07.880> like<01:12:08.120> I<01:12:08.239> mean 01:12:08.550 --> 01:12:08.560 align:start position:0% all um I think I don't know like I mean 01:12:08.560 --> 01:12:10.350 align:start position:0% all um I think I don't know like I mean well<01:12:08.880> come<01:12:08.960> on<01:12:09.199> I<01:12:09.280> know<01:12:09.600> like<01:12:09.800> we<01:12:09.920> just<01:12:10.080> need<01:12:10.199> to 01:12:10.350 --> 01:12:10.360 align:start position:0% well come on I know like we just need to 01:12:10.360 --> 01:12:12.189 align:start position:0% well come on I know like we just need to work<01:12:10.560> on 01:12:12.189 --> 01:12:12.199 align:start position:0% work on 01:12:12.199 --> 01:12:15.510 align:start position:0% work on it<01:12:13.199> you<01:12:13.360> heard<01:12:13.639> that<01:12:14.120> just<01:12:14.360> go<01:12:14.520> work<01:12:14.679> on 01:12:15.510 --> 01:12:15.520 align:start position:0% it you heard that just go work on 01:12:15.520 --> 01:12:18.110 align:start position:0% it you heard that just go work on it<01:12:16.520> the<01:12:16.639> next<01:12:16.800> one<01:12:16.920> is<01:12:17.080> what<01:12:17.280> are<01:12:17.639> exotic 01:12:18.110 --> 01:12:18.120 align:start position:0% it the next one is what are exotic 01:12:18.120 --> 01:12:20.629 align:start position:0% it the next one is what are exotic cryptographic<01:12:18.920> assumptions 01:12:20.629 --> 01:12:20.639 align:start position:0% cryptographic assumptions 01:12:20.639 --> 01:12:24.510 align:start position:0% cryptographic assumptions oh<01:12:21.639> I<01:12:21.760> think<01:12:21.960> they're<01:12:22.320> like<01:12:22.480> more<01:12:23.040> like<01:12:24.040> like 01:12:24.510 --> 01:12:24.520 align:start position:0% oh I think they're like more like like 01:12:24.520 --> 01:12:26.189 align:start position:0% oh I think they're like more like like do<01:12:24.679> they<01:12:24.800> want<01:12:25.199> examples<01:12:25.480> or<01:12:25.679> they<01:12:25.840> want<01:12:26.080> like 01:12:26.189 --> 01:12:26.199 align:start position:0% do they want examples or they want like 01:12:26.199 --> 01:12:27.910 align:start position:0% do they want examples or they want like the<01:12:26.360> vibe<01:12:26.800> I<01:12:26.960> I<01:12:27.120> just<01:12:27.360> think<01:12:27.560> they<01:12:27.679> want<01:12:27.800> to 01:12:27.910 --> 01:12:27.920 align:start position:0% the vibe I I just think they want to 01:12:27.920 --> 01:12:30.070 align:start position:0% the vibe I I just think they want to know<01:12:28.080> what<01:12:28.199> you<01:12:28.320> mean<01:12:28.560> by<01:12:28.719> that<01:12:29.520> ah<01:12:29.679> so<01:12:29.840> there's 01:12:30.070 --> 01:12:30.080 align:start position:0% know what you mean by that ah so there's 01:12:30.080 --> 01:12:31.990 align:start position:0% know what you mean by that ah so there's like<01:12:30.239> standard<01:12:30.679> assumptions<01:12:31.520> which<01:12:31.679> are 01:12:31.990 --> 01:12:32.000 align:start position:0% like standard assumptions which are 01:12:32.000 --> 01:12:34.110 align:start position:0% like standard assumptions which are assumptions<01:12:32.520> that<01:12:32.679> people<01:12:32.960> have<01:12:33.560> made<01:12:33.800> for<01:12:33.960> a 01:12:34.110 --> 01:12:34.120 align:start position:0% assumptions that people have made for a 01:12:34.120 --> 01:12:36.350 align:start position:0% assumptions that people have made for a long<01:12:34.400> time<01:12:35.080> all<01:12:35.440> like<01:12:35.560> all<01:12:35.800> cryptography<01:12:36.320> is 01:12:36.350 --> 01:12:36.360 align:start position:0% long time all like all cryptography is 01:12:36.360 --> 01:12:38.070 align:start position:0% long time all like all cryptography is based<01:12:36.560> upon<01:12:36.760> assumptions<01:12:37.639> because<01:12:37.920> like 01:12:38.070 --> 01:12:38.080 align:start position:0% based upon assumptions because like 01:12:38.080 --> 01:12:39.669 align:start position:0% based upon assumptions because like there's<01:12:38.280> this<01:12:38.480> open<01:12:38.760> problem<01:12:39.000> in<01:12:39.159> math<01:12:39.400> that<01:12:39.520> P 01:12:39.669 --> 01:12:39.679 align:start position:0% there's this open problem in math that P 01:12:39.679 --> 01:12:41.790 align:start position:0% there's this open problem in math that P is<01:12:39.800> not<01:12:39.920> equal<01:12:40.159> to<01:12:40.239> NP<01:12:40.920> and<01:12:41.320> that<01:12:41.440> basically 01:12:41.790 --> 01:12:41.800 align:start position:0% is not equal to NP and that basically 01:12:41.800 --> 01:12:43.149 align:start position:0% is not equal to NP and that basically means<01:12:42.040> that<01:12:42.239> like<01:12:42.360> some<01:12:42.520> things<01:12:42.639> are<01:12:42.800> hard<01:12:43.040> and 01:12:43.149 --> 01:12:43.159 align:start position:0% means that like some things are hard and 01:12:43.159 --> 01:12:44.709 align:start position:0% means that like some things are hard and some<01:12:43.320> things<01:12:43.440> are<01:12:43.639> easy<01:12:44.199> so<01:12:44.360> because<01:12:44.600> we're 01:12:44.709 --> 01:12:44.719 align:start position:0% some things are easy so because we're 01:12:44.719 --> 01:12:45.990 align:start position:0% some things are easy so because we're not<01:12:44.880> able<01:12:45.040> to<01:12:45.159> prove<01:12:45.360> that<01:12:45.520> some<01:12:45.719> stuff<01:12:45.880> is 01:12:45.990 --> 01:12:46.000 align:start position:0% not able to prove that some stuff is 01:12:46.000 --> 01:12:47.750 align:start position:0% not able to prove that some stuff is hard<01:12:46.280> and<01:12:46.440> some<01:12:46.639> stuff<01:12:46.840> is<01:12:47.000> easy<01:12:47.480> we're<01:12:47.639> not 01:12:47.750 --> 01:12:47.760 align:start position:0% hard and some stuff is easy we're not 01:12:47.760 --> 01:12:49.149 align:start position:0% hard and some stuff is easy we're not able<01:12:47.960> to<01:12:48.040> prove<01:12:48.239> that<01:12:48.360> any<01:12:48.600> particular<01:12:48.960> thing 01:12:49.149 --> 01:12:49.159 align:start position:0% able to prove that any particular thing 01:12:49.159 --> 01:12:50.709 align:start position:0% able to prove that any particular thing is<01:12:49.320> hard<01:12:49.880> and<01:12:50.000> because<01:12:50.199> we're<01:12:50.360> not<01:12:50.480> able<01:12:50.639> to 01:12:50.709 --> 01:12:50.719 align:start position:0% is hard and because we're not able to 01:12:50.719 --> 01:12:51.990 align:start position:0% is hard and because we're not able to prove<01:12:50.920> that<01:12:51.040> any<01:12:51.239> particular<01:12:51.560> thing<01:12:51.679> is<01:12:51.800> hard 01:12:51.990 --> 01:12:52.000 align:start position:0% prove that any particular thing is hard 01:12:52.000 --> 01:12:53.110 align:start position:0% prove that any particular thing is hard we<01:12:52.120> have<01:12:52.199> to<01:12:52.320> base<01:12:52.560> everything<01:12:52.800> we're<01:12:52.920> doing 01:12:53.110 --> 01:12:53.120 align:start position:0% we have to base everything we're doing 01:12:53.120 --> 01:12:54.709 align:start position:0% we have to base everything we're doing on<01:12:53.280> assumptions<01:12:53.719> we<01:12:53.880> assume<01:12:54.280> that<01:12:54.400> things<01:12:54.520> are 01:12:54.709 --> 01:12:54.719 align:start position:0% on assumptions we assume that things are 01:12:54.719 --> 01:12:56.390 align:start position:0% on assumptions we assume that things are hard<01:12:55.360> so<01:12:55.560> there's<01:12:55.800> different<01:12:56.040> things<01:12:56.239> that 01:12:56.390 --> 01:12:56.400 align:start position:0% hard so there's different things that 01:12:56.400 --> 01:12:58.270 align:start position:0% hard so there's different things that people<01:12:56.679> assume<01:12:57.320> there's<01:12:57.560> things<01:12:57.719> that<01:12:58.000> been 01:12:58.270 --> 01:12:58.280 align:start position:0% people assume there's things that been 01:12:58.280 --> 01:13:00.350 align:start position:0% people assume there's things that been people<01:12:58.520> being<01:12:58.920> assuming<01:12:59.239> for<01:12:59.360> a<01:12:59.520> long<01:12:59.760> time 01:13:00.350 --> 01:13:00.360 align:start position:0% people being assuming for a long time 01:13:00.360 --> 01:13:02.830 align:start position:0% people being assuming for a long time and<01:13:00.520> people<01:13:00.719> are<01:13:00.920> much<01:13:01.199> more<01:13:02.120> open<01:13:02.440> to<01:13:02.639> these 01:13:02.830 --> 01:13:02.840 align:start position:0% and people are much more open to these 01:13:02.840 --> 01:13:03.910 align:start position:0% and people are much more open to these assumptions<01:13:03.320> because<01:13:03.440> we've<01:13:03.600> been<01:13:03.719> making 01:13:03.910 --> 01:13:03.920 align:start position:0% assumptions because we've been making 01:13:03.920 --> 01:13:05.470 align:start position:0% assumptions because we've been making them<01:13:04.040> for<01:13:04.159> a<01:13:04.320> long<01:13:04.520> time<01:13:05.040> but<01:13:05.159> then<01:13:05.280> there's 01:13:05.470 --> 01:13:05.480 align:start position:0% them for a long time but then there's 01:13:05.480 --> 01:13:08.189 align:start position:0% them for a long time but then there's newer<01:13:05.840> assumptions<01:13:06.280> that<01:13:06.400> are<01:13:06.520> more<01:13:07.199> radical 01:13:08.189 --> 01:13:08.199 align:start position:0% newer assumptions that are more radical 01:13:08.199 --> 01:13:10.229 align:start position:0% newer assumptions that are more radical uh<01:13:08.560> that<01:13:08.880> that<01:13:09.199> that<01:13:09.440> and<01:13:09.600> those<01:13:09.920> are<01:13:10.040> what<01:13:10.159> I 01:13:10.229 --> 01:13:10.239 align:start position:0% uh that that that and those are what I 01:13:10.239 --> 01:13:11.709 align:start position:0% uh that that that and those are what I mean<01:13:10.400> by<01:13:10.520> exotic<01:13:10.840> assumptions<01:13:11.400> and<01:13:11.480> if<01:13:11.560> you're 01:13:11.709 --> 01:13:11.719 align:start position:0% mean by exotic assumptions and if you're 01:13:11.719 --> 01:13:13.430 align:start position:0% mean by exotic assumptions and if you're interested<01:13:12.040> in<01:13:12.199> that<01:13:12.639> uh<01:13:12.760> Brian<01:13:13.080> Lawrence 01:13:13.430 --> 01:13:13.440 align:start position:0% interested in that uh Brian Lawrence 01:13:13.440 --> 01:13:15.270 align:start position:0% interested in that uh Brian Lawrence will<01:13:13.639> give<01:13:13.760> a<01:13:13.920> talk<01:13:14.199> about<01:13:14.480> that<01:13:14.840> in<01:13:15.000> one<01:13:15.159> of 01:13:15.270 --> 01:13:15.280 align:start position:0% will give a talk about that in one of 01:13:15.280 --> 01:13:17.070 align:start position:0% will give a talk about that in one of the<01:13:15.440> workshop<01:13:15.920> the<01:13:16.080> iio<01:13:16.400> workshop<01:13:16.800> so<01:13:16.960> there 01:13:17.070 --> 01:13:17.080 align:start position:0% the workshop the iio workshop so there 01:13:17.080 --> 01:13:18.310 align:start position:0% the workshop the iio workshop so there will<01:13:17.199> be<01:13:17.280> a<01:13:17.400> talk<01:13:17.560> about<01:13:17.760> cryptographic 01:13:18.310 --> 01:13:18.320 align:start position:0% will be a talk about cryptographic 01:13:18.320 --> 01:13:20.070 align:start position:0% will be a talk about cryptographic assumptions<01:13:19.239> um<01:13:19.360> so<01:13:19.600> that's<01:13:19.760> it<01:13:19.920> we're 01:13:20.070 --> 01:13:20.080 align:start position:0% assumptions um so that's it we're 01:13:20.080 --> 01:13:21.870 align:start position:0% assumptions um so that's it we're running<01:13:20.320> out<01:13:20.440> of<01:13:20.639> time<01:13:20.880> thanks<01:13:21.159> everybody 01:13:21.870 --> 01:13:21.880 align:start position:0% running out of time thanks everybody 01:13:21.880 --> 01:13:28.229 align:start position:0% running out of time thanks everybody thanks<01:13:22.120> folks 01:13:28.229 --> 01:13:28.239 align:start position:0% 01:13:28.239 --> 01:13:29.709 align:start position:0% and<01:13:28.400> with<01:13:28.600> that<01:13:28.840> I<01:13:28.920> will<01:13:29.080> introduce<01:13:29.440> our<01:13:29.560> next 01:13:29.709 --> 01:13:29.719 align:start position:0% and with that I will introduce our next 01:13:29.719 --> 01:13:32.310 align:start position:0% and with that I will introduce our next speaker<01:13:29.960> to<01:13:30.120> the<01:13:30.239> stage<01:13:30.600> goep<01:13:31.480> um<01:13:31.600> goip<01:13:32.080> is<01:13:32.199> one 01:13:32.310 --> 01:13:32.320 align:start position:0% speaker to the stage goep um goip is one 01:13:32.320 --> 01:13:34.149 align:start position:0% speaker to the stage goep um goip is one of<01:13:32.400> the<01:13:32.520> co-founder<01:13:32.960> of<01:13:33.080> zor<01:13:33.440> spark<01:13:33.880> and<01:13:34.040> the 01:13:34.149 --> 01:13:34.159 align:start position:0% of the co-founder of zor spark and the 01:13:34.159 --> 01:13:35.629 align:start position:0% of the co-founder of zor spark and the creator<01:13:34.440> of<01:13:34.560> Dark<01:13:34.760> Forest<01:13:35.159> please<01:13:35.360> welcome 01:13:35.629 --> 01:13:35.639 align:start position:0% creator of Dark Forest please welcome 01:13:35.639 --> 01:13:40.610 align:start position:0% creator of Dark Forest please welcome him<01:13:35.760> to<01:13:35.880> the<01:13:36.000> stage<01:13:36.320> thank 01:13:40.610 --> 01:13:40.620 align:start position:0% 01:13:40.620 --> 01:13:43.149 align:start position:0% [Music] 01:13:43.149 --> 01:13:43.159 align:start position:0% [Music] 01:13:43.159 --> 01:13:45.510 align:start position:0% [Music] you<01:13:44.159> hey<01:13:44.320> everybody<01:13:44.719> thank<01:13:44.880> you<01:13:45.000> for<01:13:45.199> joining 01:13:45.510 --> 01:13:45.520 align:start position:0% you hey everybody thank you for joining 01:13:45.520 --> 01:13:47.070 align:start position:0% you hey everybody thank you for joining us<01:13:45.719> this<01:13:45.840> morning<01:13:46.120> for<01:13:46.320> the<01:13:46.480> programable 01:13:47.070 --> 01:13:47.080 align:start position:0% us this morning for the programable 01:13:47.080 --> 01:13:50.830 align:start position:0% us this morning for the programable cryptography<01:13:48.000> CLS<01:13:49.000> uh<01:13:49.719> the<01:13:49.880> title<01:13:50.199> of<01:13:50.360> my<01:13:50.560> talk 01:13:50.830 --> 01:13:50.840 align:start position:0% cryptography CLS uh the title of my talk 01:13:50.840 --> 01:13:53.310 align:start position:0% cryptography CLS uh the title of my talk today<01:13:51.360> is<01:13:51.880> contact<01:13:52.760> and<01:13:52.880> I'm<01:13:52.960> going<01:13:53.120> to<01:13:53.199> be 01:13:53.310 --> 01:13:53.320 align:start position:0% today is contact and I'm going to be 01:13:53.320 --> 01:13:54.590 align:start position:0% today is contact and I'm going to be explaining<01:13:53.760> a<01:13:53.840> little<01:13:54.000> bit<01:13:54.159> about<01:13:54.360> what<01:13:54.480> that 01:13:54.590 --> 01:13:54.600 align:start position:0% explaining a little bit about what that 01:13:54.600 --> 01:13:56.910 align:start position:0% explaining a little bit about what that means<01:13:54.800> short 01:13:56.910 --> 01:13:56.920 align:start position:0% means short 01:13:56.920 --> 01:13:58.590 align:start position:0% means short as<01:13:57.000> a<01:13:57.159> quick<01:13:57.320> introduction<01:13:57.960> I'm<01:13:58.120> gub<01:13:58.360> sheep 01:13:58.590 --> 01:13:58.600 align:start position:0% as a quick introduction I'm gub sheep 01:13:58.600 --> 01:13:59.790 align:start position:0% as a quick introduction I'm gub sheep I'm<01:13:58.679> one<01:13:58.800> of<01:13:58.880> the<01:13:58.960> co-founders<01:13:59.400> of<01:13:59.560> Dark 01:13:59.790 --> 01:13:59.800 align:start position:0% I'm one of the co-founders of Dark 01:13:59.800 --> 01:14:02.189 align:start position:0% I'm one of the co-founders of Dark Forest<01:14:00.760> uh<01:14:00.880> I<01:14:01.000> coined<01:14:01.360> the<01:14:01.440> term<01:14:01.719> programmable 01:14:02.189 --> 01:14:02.199 align:start position:0% Forest uh I coined the term programmable 01:14:02.199 --> 01:14:04.270 align:start position:0% Forest uh I coined the term programmable cryptography<01:14:02.719> about<01:14:02.840> two<01:14:03.080> years<01:14:03.280> ago<01:14:03.800> and 01:14:04.270 --> 01:14:04.280 align:start position:0% cryptography about two years ago and 01:14:04.280 --> 01:14:05.750 align:start position:0% cryptography about two years ago and ever<01:14:04.520> since<01:14:04.719> then<01:14:04.880> we've<01:14:05.040> been<01:14:05.280> exploring<01:14:05.679> a 01:14:05.750 --> 01:14:05.760 align:start position:0% ever since then we've been exploring a 01:14:05.760 --> 01:14:07.510 align:start position:0% ever since then we've been exploring a lot<01:14:05.840> of<01:14:05.960> its 01:14:07.510 --> 01:14:07.520 align:start position:0% lot of its 01:14:07.520 --> 01:14:09.950 align:start position:0% lot of its consequences<01:14:08.520> so<01:14:09.000> this<01:14:09.239> talk<01:14:09.480> is<01:14:09.600> going<01:14:09.760> to<01:14:09.840> be 01:14:09.950 --> 01:14:09.960 align:start position:0% consequences so this talk is going to be 01:14:09.960 --> 01:14:12.189 align:start position:0% consequences so this talk is going to be a<01:14:10.040> little<01:14:10.199> bit<01:14:10.360> more<01:14:10.719> of<01:14:10.920> a<01:14:11.440> mental<01:14:11.760> models<01:14:12.080> and 01:14:12.189 --> 01:14:12.199 align:start position:0% a little bit more of a mental models and 01:14:12.199 --> 01:14:14.149 align:start position:0% a little bit more of a mental models and Frameworks<01:14:12.679> talk<01:14:12.920> it's<01:14:13.040> not<01:14:13.199> going<01:14:13.320> to<01:14:13.440> be<01:14:13.840> a<01:14:14.040> a 01:14:14.149 --> 01:14:14.159 align:start position:0% Frameworks talk it's not going to be a a 01:14:14.159 --> 01:14:15.550 align:start position:0% Frameworks talk it's not going to be a a whiteboarding<01:14:14.679> session<01:14:15.000> or<01:14:15.120> a<01:14:15.239> session<01:14:15.440> where 01:14:15.550 --> 01:14:15.560 align:start position:0% whiteboarding session or a session where 01:14:15.560 --> 01:14:17.470 align:start position:0% whiteboarding session or a session where we<01:14:15.679> go<01:14:15.800> deep<01:14:16.000> into<01:14:16.159> the<01:14:16.280> cryptography<01:14:17.239> um<01:14:17.360> we 01:14:17.470 --> 01:14:17.480 align:start position:0% we go deep into the cryptography um we 01:14:17.480 --> 01:14:18.629 align:start position:0% we go deep into the cryptography um we are<01:14:17.600> going<01:14:17.719> to<01:14:17.840> hear<01:14:18.080> more<01:14:18.280> about<01:14:18.480> the 01:14:18.629 --> 01:14:18.639 align:start position:0% are going to hear more about the 01:14:18.639 --> 01:14:22.070 align:start position:0% are going to hear more about the technology<01:14:19.320> in<01:14:19.560> this<01:14:19.800> afternoon's<01:14:21.080> workshops 01:14:22.070 --> 01:14:22.080 align:start position:0% technology in this afternoon's workshops 01:14:22.080 --> 01:14:24.030 align:start position:0% technology in this afternoon's workshops uh<01:14:22.960> and<01:14:23.159> what<01:14:23.280> we're<01:14:23.400> going<01:14:23.520> to<01:14:23.600> do<01:14:23.719> in<01:14:23.880> this 01:14:24.030 --> 01:14:24.040 align:start position:0% uh and what we're going to do in this 01:14:24.040 --> 01:14:25.550 align:start position:0% uh and what we're going to do in this talk<01:14:24.280> is<01:14:24.719> you<01:14:24.840> know<01:14:25.080> we're<01:14:25.159> going<01:14:25.239> to<01:14:25.360> look<01:14:25.440> at 01:14:25.550 --> 01:14:25.560 align:start position:0% talk is you know we're going to look at 01:14:25.560 --> 01:14:28.590 align:start position:0% talk is you know we're going to look at some<01:14:25.800> history<01:14:26.159> and<01:14:26.320> some<01:14:26.440> worked<01:14:27.040> examples<01:14:28.040> of 01:14:28.590 --> 01:14:28.600 align:start position:0% some history and some worked examples of 01:14:28.600 --> 01:14:30.750 align:start position:0% some history and some worked examples of how<01:14:28.840> we've<01:14:29.080> come<01:14:29.239> to<01:14:29.440> build<01:14:29.800> up<01:14:30.159> even<01:14:30.360> the<01:14:30.480> ways 01:14:30.750 --> 01:14:30.760 align:start position:0% how we've come to build up even the ways 01:14:30.760 --> 01:14:32.030 align:start position:0% how we've come to build up even the ways that<01:14:30.880> we<01:14:31.040> think<01:14:31.239> about<01:14:31.480> programmable 01:14:32.030 --> 01:14:32.040 align:start position:0% that we think about programmable 01:14:32.040 --> 01:14:33.950 align:start position:0% that we think about programmable cryptography<01:14:32.960> um<01:14:33.199> at<01:14:33.320> the<01:14:33.400> end<01:14:33.600> we'll<01:14:33.800> also 01:14:33.950 --> 01:14:33.960 align:start position:0% cryptography um at the end we'll also 01:14:33.960 --> 01:14:36.070 align:start position:0% cryptography um at the end we'll also tag<01:14:34.199> on<01:14:34.320> some<01:14:34.520> highly<01:14:34.760> uncertain<01:14:35.199> speculation 01:14:36.070 --> 01:14:36.080 align:start position:0% tag on some highly uncertain speculation 01:14:36.080 --> 01:14:37.510 align:start position:0% tag on some highly uncertain speculation of<01:14:36.480> what<01:14:36.639> we<01:14:36.800> might<01:14:37.000> do<01:14:37.280> with<01:14:37.400> those 01:14:37.510 --> 01:14:37.520 align:start position:0% of what we might do with those 01:14:37.520 --> 01:14:38.950 align:start position:0% of what we might do with those Frameworks<01:14:37.920> in<01:14:38.000> the 01:14:38.950 --> 01:14:38.960 align:start position:0% Frameworks in the 01:14:38.960 --> 01:14:41.470 align:start position:0% Frameworks in the future<01:14:39.960> okay<01:14:40.080> so<01:14:40.239> the<01:14:40.400> title<01:14:40.679> of<01:14:40.840> this<01:14:41.040> talk<01:14:41.280> is 01:14:41.470 --> 01:14:41.480 align:start position:0% future okay so the title of this talk is 01:14:41.480 --> 01:14:44.990 align:start position:0% future okay so the title of this talk is inspired<01:14:42.320> by<01:14:42.880> a<01:14:43.480> Sci-Fi<01:14:44.040> series<01:14:44.639> this<01:14:44.719> is<01:14:44.840> the 01:14:44.990 --> 01:14:45.000 align:start position:0% inspired by a Sci-Fi series this is the 01:14:45.000 --> 01:14:46.990 align:start position:0% inspired by a Sci-Fi series this is the culture<01:14:45.360> series<01:14:45.679> by<01:14:45.840> Ian<01:14:46.120> Banks<01:14:46.679> raise<01:14:46.880> your 01:14:46.990 --> 01:14:47.000 align:start position:0% culture series by Ian Banks raise your 01:14:47.000 --> 01:14:49.229 align:start position:0% culture series by Ian Banks raise your hand<01:14:47.159> if<01:14:47.280> you've<01:14:47.679> read<01:14:47.880> or<01:14:48.080> heard<01:14:48.280> of<01:14:49.080> these 01:14:49.229 --> 01:14:49.239 align:start position:0% hand if you've read or heard of these 01:14:49.239 --> 01:14:50.470 align:start position:0% hand if you've read or heard of these books<01:14:49.480> oh<01:14:49.600> actually<01:14:49.760> it's<01:14:49.960> pretty<01:14:50.280> Prett 01:14:50.470 --> 01:14:50.480 align:start position:0% books oh actually it's pretty Prett 01:14:50.480 --> 01:14:52.189 align:start position:0% books oh actually it's pretty Prett pretty<01:14:50.679> decent<01:14:50.920> number<01:14:51.199> so<01:14:51.560> the<01:14:51.719> premise<01:14:52.040> of 01:14:52.189 --> 01:14:52.199 align:start position:0% pretty decent number so the premise of 01:14:52.199 --> 01:14:54.270 align:start position:0% pretty decent number so the premise of the<01:14:52.360> culture<01:14:52.800> series<01:14:53.360> is<01:14:53.440> that<01:14:53.719> explorers 01:14:54.270 --> 01:14:54.280 align:start position:0% the culture series is that explorers 01:14:54.280 --> 01:14:56.110 align:start position:0% the culture series is that explorers adventures<01:14:54.719> in<01:14:54.880> the<01:14:55.040> this<01:14:55.159> universe<01:14:55.679> where 01:14:56.110 --> 01:14:56.120 align:start position:0% adventures in the this universe where 01:14:56.120 --> 01:14:58.870 align:start position:0% adventures in the this universe where this<01:14:56.440> transhumanist<01:14:57.440> post<01:14:57.760> scarcity<01:14:58.360> Society 01:14:58.870 --> 01:14:58.880 align:start position:0% this transhumanist post scarcity Society 01:14:58.880 --> 01:15:01.350 align:start position:0% this transhumanist post scarcity Society exists<01:14:59.760> and<01:15:00.040> you<01:15:00.159> know<01:15:00.320> it's<01:15:00.480> sort<01:15:00.639> of<01:15:01.080> there's 01:15:01.350 --> 01:15:01.360 align:start position:0% exists and you know it's sort of there's 01:15:01.360 --> 01:15:05.510 align:start position:0% exists and you know it's sort of there's a<01:15:02.040> uh<01:15:02.320> G<01:15:02.679> galaxy-wide<01:15:03.679> culture<01:15:04.679> of<01:15:05.199> all<01:15:05.360> of 01:15:05.510 --> 01:15:05.520 align:start position:0% a uh G galaxy-wide culture of all of 01:15:05.520 --> 01:15:08.030 align:start position:0% a uh G galaxy-wide culture of all of these<01:15:05.760> humans<01:15:06.159> or<01:15:06.600> transhumans<01:15:07.600> that<01:15:07.760> are 01:15:08.030 --> 01:15:08.040 align:start position:0% these humans or transhumans that are 01:15:08.040 --> 01:15:11.270 align:start position:0% these humans or transhumans that are involved<01:15:08.440> in<01:15:08.600> this<01:15:09.000> Society<01:15:10.000> um<01:15:10.440> and<01:15:11.000> one<01:15:11.159> of 01:15:11.270 --> 01:15:11.280 align:start position:0% involved in this Society um and one of 01:15:11.280 --> 01:15:13.709 align:start position:0% involved in this Society um and one of the<01:15:11.480> most<01:15:11.880> interesting<01:15:12.679> sort<01:15:12.840> of<01:15:13.080> agencies 01:15:13.709 --> 01:15:13.719 align:start position:0% the most interesting sort of agencies 01:15:13.719 --> 01:15:16.750 align:start position:0% the most interesting sort of agencies that<01:15:14.080> exists<01:15:14.719> in<01:15:14.960> the<01:15:15.199> culture<01:15:15.760> civilization 01:15:16.750 --> 01:15:16.760 align:start position:0% that exists in the culture civilization 01:15:16.760 --> 01:15:18.629 align:start position:0% that exists in the culture civilization is<01:15:16.920> the<01:15:17.159> contact<01:15:17.719> Division<01:15:18.280> and<01:15:18.400> what<01:15:18.520> the 01:15:18.629 --> 01:15:18.639 align:start position:0% is the contact Division and what the 01:15:18.639 --> 01:15:20.390 align:start position:0% is the contact Division and what the contact<01:15:19.040> division<01:15:19.440> does<01:15:19.719> is<01:15:20.080> they're<01:15:20.320> the 01:15:20.390 --> 01:15:20.400 align:start position:0% contact division does is they're the 01:15:20.400 --> 01:15:21.270 align:start position:0% contact division does is they're the ones<01:15:20.560> who<01:15:20.679> are<01:15:20.800> essentially<01:15:21.120> at<01:15:21.199> the 01:15:21.270 --> 01:15:21.280 align:start position:0% ones who are essentially at the 01:15:21.280 --> 01:15:22.830 align:start position:0% ones who are essentially at the Frontiers<01:15:21.679> or<01:15:21.840> the<01:15:21.920> fringes<01:15:22.320> of<01:15:22.440> the 01:15:22.830 --> 01:15:22.840 align:start position:0% Frontiers or the fringes of the 01:15:22.840 --> 01:15:25.229 align:start position:0% Frontiers or the fringes of the civilization<01:15:23.840> uh<01:15:24.040> handling<01:15:24.560> all<01:15:24.760> kind<01:15:25.120> of 01:15:25.229 --> 01:15:25.239 align:start position:0% civilization uh handling all kind of 01:15:25.239 --> 01:15:27.110 align:start position:0% civilization uh handling all kind of interactions<01:15:25.800> with<01:15:26.120> any<01:15:26.480> other 01:15:27.110 --> 01:15:27.120 align:start position:0% interactions with any other 01:15:27.120 --> 01:15:28.990 align:start position:0% interactions with any other extraterrestrial<01:15:28.080> life<01:15:28.280> or<01:15:28.480> intelligences 01:15:28.990 --> 01:15:29.000 align:start position:0% extraterrestrial life or intelligences 01:15:29.000 --> 01:15:29.950 align:start position:0% extraterrestrial life or intelligences or<01:15:29.159> things<01:15:29.320> that<01:15:29.400> they're<01:15:29.520> finding<01:15:29.760> at<01:15:29.880> the 01:15:29.950 --> 01:15:29.960 align:start position:0% or things that they're finding at the 01:15:29.960 --> 01:15:31.510 align:start position:0% or things that they're finding at the fringes<01:15:30.800> and<01:15:30.920> one<01:15:31.040> thing<01:15:31.159> that<01:15:31.239> I<01:15:31.360> kind<01:15:31.440> of 01:15:31.510 --> 01:15:31.520 align:start position:0% fringes and one thing that I kind of 01:15:31.520 --> 01:15:33.189 align:start position:0% fringes and one thing that I kind of want<01:15:31.679> to<01:15:31.840> prompt<01:15:32.120> is<01:15:32.400> what<01:15:32.520> does<01:15:32.639> it<01:15:32.760> look<01:15:33.000> like 01:15:33.189 --> 01:15:33.199 align:start position:0% want to prompt is what does it look like 01:15:33.199 --> 01:15:35.830 align:start position:0% want to prompt is what does it look like for<01:15:33.440> ethereum<01:15:34.320> or<01:15:34.719> applied<01:15:35.159> cryptography<01:15:35.679> or 01:15:35.830 --> 01:15:35.840 align:start position:0% for ethereum or applied cryptography or 01:15:35.840 --> 01:15:37.390 align:start position:0% for ethereum or applied cryptography or programmable<01:15:36.360> cryptography<01:15:36.880> to<01:15:37.000> have<01:15:37.199> a 01:15:37.390 --> 01:15:37.400 align:start position:0% programmable cryptography to have a 01:15:37.400 --> 01:15:39.669 align:start position:0% programmable cryptography to have a contact<01:15:37.880> division<01:15:38.239> what<01:15:38.320> does<01:15:38.480> that<01:15:38.639> look 01:15:39.669 --> 01:15:39.679 align:start position:0% contact division what does that look 01:15:39.679 --> 01:15:42.750 align:start position:0% contact division what does that look like<01:15:40.679> okay<01:15:41.159> so<01:15:41.679> let's<01:15:41.920> first<01:15:42.199> take<01:15:42.320> a<01:15:42.480> step 01:15:42.750 --> 01:15:42.760 align:start position:0% like okay so let's first take a step 01:15:42.760 --> 01:15:44.390 align:start position:0% like okay so let's first take a step back<01:15:42.920> and<01:15:43.120> ask<01:15:43.600> what<01:15:43.719> are<01:15:43.800> we<01:15:43.920> trying<01:15:44.120> to<01:15:44.239> do 01:15:44.390 --> 01:15:44.400 align:start position:0% back and ask what are we trying to do 01:15:44.400 --> 01:15:46.629 align:start position:0% back and ask what are we trying to do here<01:15:44.560> with<01:15:44.719> programmable<01:15:45.280> cryptography<01:15:46.280> um 01:15:46.629 --> 01:15:46.639 align:start position:0% here with programmable cryptography um 01:15:46.639 --> 01:15:48.510 align:start position:0% here with programmable cryptography um the<01:15:46.920> the<01:15:47.159> various<01:15:47.520> organizations<01:15:48.400> the 01:15:48.510 --> 01:15:48.520 align:start position:0% the the various organizations the 01:15:48.520 --> 01:15:49.750 align:start position:0% the the various organizations the various<01:15:48.760> individual<01:15:49.199> contributors<01:15:49.639> the 01:15:49.750 --> 01:15:49.760 align:start position:0% various individual contributors the 01:15:49.760 --> 01:15:50.550 align:start position:0% various individual contributors the various<01:15:50.000> people<01:15:50.199> thinking<01:15:50.400> about 01:15:50.550 --> 01:15:50.560 align:start position:0% various people thinking about 01:15:50.560 --> 01:15:53.270 align:start position:0% various people thinking about programmable<01:15:51.400> cryptography<01:15:52.400> you<01:15:52.520> know<01:15:53.159> what 01:15:53.270 --> 01:15:53.280 align:start position:0% programmable cryptography you know what 01:15:53.280 --> 01:15:54.950 align:start position:0% programmable cryptography you know what is<01:15:53.600> what<01:15:53.679> is<01:15:53.800> sort<01:15:53.960> of<01:15:54.080> the<01:15:54.239> goal<01:15:54.480> here<01:15:54.600> with 01:15:54.950 --> 01:15:54.960 align:start position:0% is what is sort of the goal here with 01:15:54.960 --> 01:15:56.510 align:start position:0% is what is sort of the goal here with progammable<01:15:55.360> cryptography<01:15:56.040> we've<01:15:56.199> seen<01:15:56.400> a 01:15:56.510 --> 01:15:56.520 align:start position:0% progammable cryptography we've seen a 01:15:56.520 --> 01:15:58.070 align:start position:0% progammable cryptography we've seen a couple<01:15:56.760> of<01:15:56.920> instances<01:15:57.280> of<01:15:57.440> goals<01:15:57.719> maybe<01:15:57.920> it's 01:15:58.070 --> 01:15:58.080 align:start position:0% couple of instances of goals maybe it's 01:15:58.080 --> 01:16:00.110 align:start position:0% couple of instances of goals maybe it's realizing<01:15:58.760> the<01:15:58.920> the<01:15:59.040> real<01:15:59.360> or<01:15:59.480> the<01:15:59.600> super<01:15:59.880> real 01:16:00.110 --> 01:16:00.120 align:start position:0% realizing the the real or the super real 01:16:00.120 --> 01:16:04.030 align:start position:0% realizing the the real or the super real or<01:16:00.239> the<01:16:00.679> sural<01:16:01.960> um<01:16:02.960> one<01:16:03.360> framing<01:16:03.800> that<01:16:03.920> I 01:16:04.030 --> 01:16:04.040 align:start position:0% or the sural um one framing that I 01:16:04.040 --> 01:16:06.750 align:start position:0% or the sural um one framing that I really<01:16:04.280> liked<01:16:04.639> actually<01:16:04.880> from<01:16:05.120> Albert's<01:16:05.760> talk 01:16:06.750 --> 01:16:06.760 align:start position:0% really liked actually from Albert's talk 01:16:06.760 --> 01:16:08.390 align:start position:0% really liked actually from Albert's talk and<01:16:07.239> that<01:16:07.639> you<01:16:07.760> know<01:16:07.920> I've<01:16:08.040> been<01:16:08.199> thinking 01:16:08.390 --> 01:16:08.400 align:start position:0% and that you know I've been thinking 01:16:08.400 --> 01:16:09.830 align:start position:0% and that you know I've been thinking about<01:16:08.560> a<01:16:08.679> bit<01:16:08.840> myself<01:16:09.080> as<01:16:09.199> well<01:16:09.320> is<01:16:09.480> this<01:16:09.600> idea 01:16:09.830 --> 01:16:09.840 align:start position:0% about a bit myself as well is this idea 01:16:09.840 --> 01:16:12.310 align:start position:0% about a bit myself as well is this idea of<01:16:10.120> programmable<01:16:10.679> cryptography<01:16:11.440> as<01:16:11.760> a<01:16:11.960> fifth 01:16:12.310 --> 01:16:12.320 align:start position:0% of programmable cryptography as a fifth 01:16:12.320 --> 01:16:13.629 align:start position:0% of programmable cryptography as a fifth fundamental<01:16:12.840> force<01:16:13.120> and<01:16:13.239> as<01:16:13.320> we<01:16:13.440> saw<01:16:13.560> in 01:16:13.629 --> 01:16:13.639 align:start position:0% fundamental force and as we saw in 01:16:13.639 --> 01:16:16.470 align:start position:0% fundamental force and as we saw in Albert's<01:16:14.080> talk<01:16:14.840> um<01:16:15.440> cryptography<01:16:16.080> represents 01:16:16.470 --> 01:16:16.480 align:start position:0% Albert's talk um cryptography represents 01:16:16.480 --> 01:16:18.510 align:start position:0% Albert's talk um cryptography represents a<01:16:16.600> set<01:16:16.719> of<01:16:16.920> extraordinary<01:16:17.719> new<01:16:17.960> capabilities 01:16:18.510 --> 01:16:18.520 align:start position:0% a set of extraordinary new capabilities 01:16:18.520 --> 01:16:21.030 align:start position:0% a set of extraordinary new capabilities that<01:16:18.679> would<01:16:19.000> a<01:16:19.199> priori<01:16:19.600> seem<01:16:19.960> impossible<01:16:20.800> much 01:16:21.030 --> 01:16:21.040 align:start position:0% that would a priori seem impossible much 01:16:21.040 --> 01:16:22.750 align:start position:0% that would a priori seem impossible much like<01:16:21.199> how<01:16:21.400> something<01:16:21.719> like<01:16:22.120> nuclear 01:16:22.750 --> 01:16:22.760 align:start position:0% like how something like nuclear 01:16:22.760 --> 01:16:24.470 align:start position:0% like how something like nuclear technology<01:16:23.360> or<01:16:23.520> the<01:16:23.639> ability<01:16:23.960> to<01:16:24.080> harness 01:16:24.470 --> 01:16:24.480 align:start position:0% technology or the ability to harness 01:16:24.480 --> 01:16:26.229 align:start position:0% technology or the ability to harness electricity<01:16:25.159> might<01:16:25.280> have<01:16:25.400> seemed<01:16:25.760> impossible 01:16:26.229 --> 01:16:26.239 align:start position:0% electricity might have seemed impossible 01:16:26.239 --> 01:16:29.189 align:start position:0% electricity might have seemed impossible as<01:16:26.560> well<01:16:27.560> and<01:16:27.719> my<01:16:27.920> question<01:16:28.440> in<01:16:28.560> terms<01:16:28.800> of<01:16:29.080> what 01:16:29.189 --> 01:16:29.199 align:start position:0% as well and my question in terms of what 01:16:29.199 --> 01:16:30.870 align:start position:0% as well and my question in terms of what do<01:16:29.320> we<01:16:29.480> actually<01:16:29.960> what<01:16:30.040> are<01:16:30.159> we<01:16:30.280> doing<01:16:30.520> here<01:16:30.679> is 01:16:30.870 --> 01:16:30.880 align:start position:0% do we actually what are we doing here is 01:16:30.880 --> 01:16:32.470 align:start position:0% do we actually what are we doing here is we're<01:16:31.040> trying<01:16:31.239> to<01:16:31.320> figure<01:16:31.520> out<01:16:31.639> how<01:16:31.760> to<01:16:31.880> even 01:16:32.470 --> 01:16:32.480 align:start position:0% we're trying to figure out how to even 01:16:32.480 --> 01:16:34.070 align:start position:0% we're trying to figure out how to even grapple<01:16:32.960> or<01:16:33.120> come<01:16:33.280> to<01:16:33.440> terms<01:16:33.719> with<01:16:33.880> this<01:16:34.000> how 01:16:34.070 --> 01:16:34.080 align:start position:0% grapple or come to terms with this how 01:16:34.080 --> 01:16:35.430 align:start position:0% grapple or come to terms with this how do<01:16:34.159> we<01:16:34.239> even<01:16:34.440> think<01:16:34.600> about<01:16:34.840> this<01:16:35.159> what<01:16:35.280> does 01:16:35.430 --> 01:16:35.440 align:start position:0% do we even think about this what does 01:16:35.440 --> 01:16:36.790 align:start position:0% do we even think about this what does this<01:16:35.600> enable<01:16:36.040> what<01:16:36.120> are<01:16:36.239> the<01:16:36.360> right<01:16:36.480> mental 01:16:36.790 --> 01:16:36.800 align:start position:0% this enable what are the right mental 01:16:36.800 --> 01:16:38.590 align:start position:0% this enable what are the right mental models<01:16:37.120> for<01:16:37.280> this<01:16:37.440> technology<01:16:38.199> what<01:16:38.320> will<01:16:38.480> the 01:16:38.590 --> 01:16:38.600 align:start position:0% models for this technology what will the 01:16:38.600 --> 01:16:40.030 align:start position:0% models for this technology what will the different<01:16:38.920> path<01:16:39.159> dependencies<01:16:39.679> be<01:16:39.840> to 01:16:40.030 --> 01:16:40.040 align:start position:0% different path dependencies be to 01:16:40.040 --> 01:16:41.590 align:start position:0% different path dependencies be to realizing<01:16:40.600> this<01:16:41.000> what<01:16:41.120> are<01:16:41.239> the<01:16:41.360> right 01:16:41.590 --> 01:16:41.600 align:start position:0% realizing this what are the right 01:16:41.600 --> 01:16:43.270 align:start position:0% realizing this what are the right abstractions<01:16:42.320> for<01:16:42.480> the<01:16:42.639> technology<01:16:43.080> and<01:16:43.199> how 01:16:43.270 --> 01:16:43.280 align:start position:0% abstractions for the technology and how 01:16:43.280 --> 01:16:44.990 align:start position:0% abstractions for the technology and how do<01:16:43.360> you<01:16:43.440> design<01:16:43.719> the<01:16:43.920> interfaces<01:16:44.600> between 01:16:44.990 --> 01:16:45.000 align:start position:0% do you design the interfaces between 01:16:45.000 --> 01:16:48.229 align:start position:0% do you design the interfaces between each<01:16:45.239> level<01:16:45.480> of<01:16:45.600> the<01:16:45.719> stack<01:16:46.159> here<01:16:47.040> um<01:16:47.920> in<01:16:48.000> short 01:16:48.229 --> 01:16:48.239 align:start position:0% each level of the stack here um in short 01:16:48.239 --> 01:16:49.470 align:start position:0% each level of the stack here um in short you<01:16:48.360> know<01:16:48.480> we<01:16:48.560> have<01:16:48.679> to<01:16:48.920> we<01:16:49.040> have<01:16:49.120> to<01:16:49.199> Grapple 01:16:49.470 --> 01:16:49.480 align:start position:0% you know we have to we have to Grapple 01:16:49.480 --> 01:16:51.030 align:start position:0% you know we have to we have to Grapple with<01:16:49.600> the<01:16:49.679> same<01:16:49.920> problem<01:16:50.280> that<01:16:50.480> nuclear 01:16:51.030 --> 01:16:51.040 align:start position:0% with the same problem that nuclear 01:16:51.040 --> 01:16:53.149 align:start position:0% with the same problem that nuclear technologists<01:16:52.040> had<01:16:52.159> to<01:16:52.320> Grapple<01:16:52.679> with<01:16:53.040> you 01:16:53.149 --> 01:16:53.159 align:start position:0% technologists had to Grapple with you 01:16:53.159 --> 01:16:55.270 align:start position:0% technologists had to Grapple with you know<01:16:53.280> in<01:16:53.360> the<01:16:53.520> last<01:16:53.760> 100<01:16:54.040> years<01:16:54.600> are<01:16:54.960> we<01:16:55.080> first 01:16:55.270 --> 01:16:55.280 align:start position:0% know in the last 100 years are we first 01:16:55.280 --> 01:16:57.110 align:start position:0% know in the last 100 years are we first going<01:16:55.400> to<01:16:55.560> make<01:16:55.840> a<01:16:56.000> bomb<01:16:56.280> or<01:16:56.400> are<01:16:56.520> we<01:16:56.840> going<01:16:56.960> to 01:16:57.110 --> 01:16:57.120 align:start position:0% going to make a bomb or are we going to 01:16:57.120 --> 01:16:58.910 align:start position:0% going to make a bomb or are we going to make<01:16:57.360> infinite<01:16:57.760> energy<01:16:58.360> and<01:16:58.520> what<01:16:58.639> are<01:16:58.800> the 01:16:58.910 --> 01:16:58.920 align:start position:0% make infinite energy and what are the 01:16:58.920 --> 01:17:00.870 align:start position:0% make infinite energy and what are the sort<01:16:59.120> of<01:16:59.320> cross-<01:16:59.679> dependencies<01:17:00.600> both 01:17:00.870 --> 01:17:00.880 align:start position:0% sort of cross- dependencies both 01:17:00.880 --> 01:17:02.750 align:start position:0% sort of cross- dependencies both technologically<01:17:01.560> and<01:17:01.719> socially<01:17:02.440> that<01:17:02.520> are 01:17:02.750 --> 01:17:02.760 align:start position:0% technologically and socially that are 01:17:02.760 --> 01:17:04.830 align:start position:0% technologically and socially that are involved<01:17:03.159> in<01:17:03.280> figuring<01:17:03.600> that<01:17:03.760> question<01:17:04.040> out 01:17:04.830 --> 01:17:04.840 align:start position:0% involved in figuring that question out 01:17:04.840 --> 01:17:06.030 align:start position:0% involved in figuring that question out or<01:17:05.040> something<01:17:05.280> like<01:17:05.440> Computing<01:17:05.800> you<01:17:05.880> know 01:17:06.030 --> 01:17:06.040 align:start position:0% or something like Computing you know 01:17:06.040 --> 01:17:08.070 align:start position:0% or something like Computing you know it's<01:17:06.199> it's<01:17:06.400> very<01:17:06.600> non-obvious<01:17:07.560> in<01:17:07.639> the<01:17:07.800> days 01:17:08.070 --> 01:17:08.080 align:start position:0% it's it's very non-obvious in the days 01:17:08.080 --> 01:17:09.830 align:start position:0% it's it's very non-obvious in the days of<01:17:08.239> something<01:17:08.480> like<01:17:08.600> the<01:17:08.719> eniac<01:17:09.360> one<01:17:09.480> of<01:17:09.639> these 01:17:09.830 --> 01:17:09.840 align:start position:0% of something like the eniac one of these 01:17:09.840 --> 01:17:11.910 align:start position:0% of something like the eniac one of these giant<01:17:10.080> room<01:17:10.360> scale<01:17:10.639> computers<01:17:11.440> that<01:17:11.719> the 01:17:11.910 --> 01:17:11.920 align:start position:0% giant room scale computers that the 01:17:11.920 --> 01:17:14.950 align:start position:0% giant room scale computers that the descendant<01:17:12.440> of<01:17:12.679> this<01:17:13.239> 60<01:17:13.679> 70<01:17:13.960> 80<01:17:14.280> years<01:17:14.440> out<01:17:14.840> is 01:17:14.950 --> 01:17:14.960 align:start position:0% descendant of this 60 70 80 years out is 01:17:14.960 --> 01:17:16.870 align:start position:0% descendant of this 60 70 80 years out is going<01:17:15.120> to<01:17:15.239> be<01:17:15.360> something<01:17:15.719> like<01:17:16.320> you<01:17:16.440> know 01:17:16.870 --> 01:17:16.880 align:start position:0% going to be something like you know 01:17:16.880 --> 01:17:18.950 align:start position:0% going to be something like you know virtual<01:17:17.280> worlds<01:17:17.639> like<01:17:17.800> EV<01:17:18.040> on<01:17:18.320> line<01:17:18.679> where 01:17:18.950 --> 01:17:18.960 align:start position:0% virtual worlds like EV on line where 01:17:18.960 --> 01:17:20.790 align:start position:0% virtual worlds like EV on line where hundreds<01:17:19.280> of<01:17:19.480> thousands<01:17:19.840> of<01:17:20.000> people<01:17:20.520> are 01:17:20.790 --> 01:17:20.800 align:start position:0% hundreds of thousands of people are 01:17:20.800 --> 01:17:22.990 align:start position:0% hundreds of thousands of people are battling<01:17:21.199> in<01:17:21.360> a<01:17:21.560> virtual<01:17:22.000> space<01:17:22.440> reality<01:17:22.800> for 01:17:22.990 --> 01:17:23.000 align:start position:0% battling in a virtual space reality for 01:17:23.000 --> 01:17:25.590 align:start position:0% battling in a virtual space reality for control<01:17:23.320> of<01:17:23.480> virtual<01:17:23.920> space<01:17:24.320> planets<01:17:25.120> right 01:17:25.590 --> 01:17:25.600 align:start position:0% control of virtual space planets right 01:17:25.600 --> 01:17:27.550 align:start position:0% control of virtual space planets right how<01:17:25.719> do<01:17:25.840> you<01:17:26.040> even<01:17:26.320> begin<01:17:26.719> to<01:17:26.920> start<01:17:27.199> thinking 01:17:27.550 --> 01:17:27.560 align:start position:0% how do you even begin to start thinking 01:17:27.560 --> 01:17:30.270 align:start position:0% how do you even begin to start thinking about<01:17:28.480> what<01:17:28.960> might<01:17:29.440> take<01:17:29.639> you<01:17:29.760> from<01:17:29.920> the<01:17:30.040> leth 01:17:30.270 --> 01:17:30.280 align:start position:0% about what might take you from the leth 01:17:30.280 --> 01:17:31.790 align:start position:0% about what might take you from the leth hand<01:17:30.440> side<01:17:30.560> to<01:17:30.679> the<01:17:30.800> right<01:17:31.040> hand 01:17:31.790 --> 01:17:31.800 align:start position:0% hand side to the right hand 01:17:31.800 --> 01:17:34.189 align:start position:0% hand side to the right hand side<01:17:32.800> okay<01:17:33.080> so<01:17:33.480> there's<01:17:33.639> a<01:17:33.719> lot<01:17:33.840> of<01:17:33.960> stuff<01:17:34.120> that 01:17:34.189 --> 01:17:34.199 align:start position:0% side okay so there's a lot of stuff that 01:17:34.199 --> 01:17:35.669 align:start position:0% side okay so there's a lot of stuff that we<01:17:34.320> could<01:17:34.440> do<01:17:34.639> that<01:17:34.880> that<01:17:35.000> wouldn't<01:17:35.400> make 01:17:35.669 --> 01:17:35.679 align:start position:0% we could do that that wouldn't make 01:17:35.679 --> 01:17:38.110 align:start position:0% we could do that that wouldn't make sense<01:17:36.679> um<01:17:37.159> in<01:17:37.320> particular<01:17:37.639> it's<01:17:37.760> easy<01:17:37.960> to 01:17:38.110 --> 01:17:38.120 align:start position:0% sense um in particular it's easy to 01:17:38.120 --> 01:17:40.310 align:start position:0% sense um in particular it's easy to Rabbit<01:17:38.520> Hole<01:17:38.719> down<01:17:39.000> one<01:17:39.320> particular<01:17:39.960> kind<01:17:40.120> of 01:17:40.310 --> 01:17:40.320 align:start position:0% Rabbit Hole down one particular kind of 01:17:40.320 --> 01:17:42.870 align:start position:0% Rabbit Hole down one particular kind of programmable<01:17:40.880> cryptography<01:17:41.639> technology<01:17:42.639> uh 01:17:42.870 --> 01:17:42.880 align:start position:0% programmable cryptography technology uh 01:17:42.880 --> 01:17:44.910 align:start position:0% programmable cryptography technology uh or<01:17:43.040> to<01:17:43.239> Rabbit<01:17:43.600> Hole<01:17:43.840> down<01:17:44.400> like<01:17:44.600> one 01:17:44.910 --> 01:17:44.920 align:start position:0% or to Rabbit Hole down like one 01:17:44.920 --> 01:17:46.910 align:start position:0% or to Rabbit Hole down like one particular<01:17:45.280> sort<01:17:45.480> of<01:17:45.639> use<01:17:46.000> case<01:17:46.239> or<01:17:46.560> or 01:17:46.910 --> 01:17:46.920 align:start position:0% particular sort of use case or or 01:17:46.920 --> 01:17:49.189 align:start position:0% particular sort of use case or or product<01:17:47.239> or<01:17:47.400> something<01:17:47.719> like<01:17:47.920> that<01:17:48.840> but 01:17:49.189 --> 01:17:49.199 align:start position:0% product or something like that but 01:17:49.199 --> 01:17:50.910 align:start position:0% product or something like that but ultimately<01:17:49.639> it's<01:17:49.840> really<01:17:50.040> important<01:17:50.400> to<01:17:50.719> to 01:17:50.910 --> 01:17:50.920 align:start position:0% ultimately it's really important to to 01:17:50.920 --> 01:17:52.550 align:start position:0% ultimately it's really important to to keep<01:17:51.320> a<01:17:51.440> solid<01:17:51.760> head<01:17:51.880> on<01:17:52.000> your<01:17:52.120> shoulders<01:17:52.440> when 01:17:52.550 --> 01:17:52.560 align:start position:0% keep a solid head on your shoulders when 01:17:52.560 --> 01:17:54.350 align:start position:0% keep a solid head on your shoulders when you're<01:17:52.679> approaching<01:17:53.080> this<01:17:53.320> question<01:17:53.920> because 01:17:54.350 --> 01:17:54.360 align:start position:0% you're approaching this question because 01:17:54.360 --> 01:17:56.070 align:start position:0% you're approaching this question because this<01:17:54.480> is<01:17:54.600> a<01:17:54.880> decades<01:17:55.239> long<01:17:55.520> civilization 01:17:56.070 --> 01:17:56.080 align:start position:0% this is a decades long civilization 01:17:56.080 --> 01:17:59.430 align:start position:0% this is a decades long civilization scale<01:17:56.719> technology<01:17:57.719> and<01:17:58.560> we<01:17:58.719> need<01:17:58.880> to<01:17:59.120> approach 01:17:59.430 --> 01:17:59.440 align:start position:0% scale technology and we need to approach 01:17:59.440 --> 01:18:01.189 align:start position:0% scale technology and we need to approach it<01:17:59.639> and<01:17:59.840> and<01:18:00.000> take<01:18:00.159> it<01:18:00.320> seriously<01:18:00.800> as<01:18:00.920> such<01:18:01.080> we 01:18:01.189 --> 01:18:01.199 align:start position:0% it and and take it seriously as such we 01:18:01.199 --> 01:18:03.590 align:start position:0% it and and take it seriously as such we need<01:18:01.320> to<01:18:01.480> build<01:18:02.080> some<01:18:02.360> foundations<01:18:03.320> mental 01:18:03.590 --> 01:18:03.600 align:start position:0% need to build some foundations mental 01:18:03.600 --> 01:18:05.149 align:start position:0% need to build some foundations mental models<01:18:04.080> in<01:18:04.159> a<01:18:04.280> way<01:18:04.400> that<01:18:04.480> takes<01:18:04.719> seriously 01:18:05.149 --> 01:18:05.159 align:start position:0% models in a way that takes seriously 01:18:05.159 --> 01:18:08.590 align:start position:0% models in a way that takes seriously that<01:18:05.960> a<01:18:06.120> mental<01:18:06.520> model<01:18:07.159> needs<01:18:07.400> to<01:18:07.560> be<01:18:07.760> useful 01:18:08.590 --> 01:18:08.600 align:start position:0% that a mental model needs to be useful 01:18:08.600 --> 01:18:11.669 align:start position:0% that a mental model needs to be useful on<01:18:08.800> the<01:18:09.040> time<01:18:09.320> scale<01:18:09.719> of<01:18:10.000> potentially<01:18:10.679> decades 01:18:11.669 --> 01:18:11.679 align:start position:0% on the time scale of potentially decades 01:18:11.679 --> 01:18:12.709 align:start position:0% on the time scale of potentially decades that<01:18:11.760> doesn't<01:18:12.000> mean<01:18:12.159> we<01:18:12.239> need<01:18:12.360> to<01:18:12.480> get<01:18:12.600> those 01:18:12.709 --> 01:18:12.719 align:start position:0% that doesn't mean we need to get those 01:18:12.719 --> 01:18:16.110 align:start position:0% that doesn't mean we need to get those mental<01:18:13.000> models<01:18:13.600> exactly<01:18:14.159> correct<01:18:14.679> today<01:18:15.639> but 01:18:16.110 --> 01:18:16.120 align:start position:0% mental models exactly correct today but 01:18:16.120 --> 01:18:17.870 align:start position:0% mental models exactly correct today but how<01:18:16.280> we<01:18:16.440> think<01:18:16.679> about<01:18:17.000> this<01:18:17.320> should<01:18:17.560> be 01:18:17.870 --> 01:18:17.880 align:start position:0% how we think about this should be 01:18:17.880 --> 01:18:20.350 align:start position:0% how we think about this should be credibly<01:18:18.440> progressing<01:18:19.080> us<01:18:19.360> towards<01:18:19.760> the<01:18:19.920> goal 01:18:20.350 --> 01:18:20.360 align:start position:0% credibly progressing us towards the goal 01:18:20.360 --> 01:18:21.669 align:start position:0% credibly progressing us towards the goal of<01:18:20.719> understanding<01:18:20.920> how<01:18:21.000> to<01:18:21.159> think<01:18:21.320> about<01:18:21.520> this 01:18:21.669 --> 01:18:21.679 align:start position:0% of understanding how to think about this 01:18:21.679 --> 01:18:23.709 align:start position:0% of understanding how to think about this from<01:18:21.840> a<01:18:22.040> from<01:18:22.159> a<01:18:22.280> multi-decade<01:18:23.080> civilization 01:18:23.709 --> 01:18:23.719 align:start position:0% from a from a multi-decade civilization 01:18:23.719 --> 01:18:25.629 align:start position:0% from a from a multi-decade civilization scale<01:18:24.480> kind<01:18:24.600> of 01:18:25.629 --> 01:18:25.639 align:start position:0% scale kind of 01:18:25.639 --> 01:18:27.790 align:start position:0% scale kind of scope<01:18:26.639> now<01:18:26.840> the<01:18:27.000> other<01:18:27.239> thing<01:18:27.400> you<01:18:27.520> have<01:18:27.639> to 01:18:27.790 --> 01:18:27.800 align:start position:0% scope now the other thing you have to 01:18:27.800 --> 01:18:29.629 align:start position:0% scope now the other thing you have to avoid<01:18:28.120> while<01:18:28.360> doing<01:18:28.719> that<01:18:28.960> is<01:18:29.239> you<01:18:29.360> have<01:18:29.480> to 01:18:29.629 --> 01:18:29.639 align:start position:0% avoid while doing that is you have to 01:18:29.639 --> 01:18:31.310 align:start position:0% avoid while doing that is you have to avoid<01:18:29.880> getting<01:18:30.120> sucked<01:18:30.440> into<01:18:30.679> the<01:18:30.880> perfect 01:18:31.310 --> 01:18:31.320 align:start position:0% avoid getting sucked into the perfect 01:18:31.320 --> 01:18:32.950 align:start position:0% avoid getting sucked into the perfect system<01:18:31.679> trap<01:18:32.199> especially<01:18:32.520> in<01:18:32.560> a<01:18:32.679> way<01:18:32.800> that's 01:18:32.950 --> 01:18:32.960 align:start position:0% system trap especially in a way that's 01:18:32.960 --> 01:18:34.910 align:start position:0% system trap especially in a way that's not<01:18:33.159> grounded<01:18:33.520> in<01:18:33.760> reality<01:18:34.400> so<01:18:34.600> the<01:18:34.719> other 01:18:34.910 --> 01:18:34.920 align:start position:0% not grounded in reality so the other 01:18:34.920 --> 01:18:36.470 align:start position:0% not grounded in reality so the other thing<01:18:35.239> that<01:18:35.320> we<01:18:35.440> could<01:18:35.600> do<01:18:36.000> is<01:18:36.120> we<01:18:36.199> could<01:18:36.360> be 01:18:36.470 --> 01:18:36.480 align:start position:0% thing that we could do is we could be 01:18:36.480 --> 01:18:37.870 align:start position:0% thing that we could do is we could be like<01:18:36.600> all<01:18:36.719> right<01:18:36.840> programmable<01:18:37.360> cryptography 01:18:37.870 --> 01:18:37.880 align:start position:0% like all right programmable cryptography 01:18:37.880 --> 01:18:39.950 align:start position:0% like all right programmable cryptography allows<01:18:38.320> us<01:18:38.440> to<01:18:38.560> do<01:18:38.800> this<01:18:39.040> crazy<01:18:39.480> stuff<01:18:39.800> this 01:18:39.950 --> 01:18:39.960 align:start position:0% allows us to do this crazy stuff this 01:18:39.960 --> 01:18:41.310 align:start position:0% allows us to do this crazy stuff this crazy<01:18:40.199> stuff<01:18:40.360> with<01:18:40.480> tur<01:18:40.760> machines<01:18:41.080> with<01:18:41.199> these 01:18:41.310 --> 01:18:41.320 align:start position:0% crazy stuff with tur machines with these 01:18:41.320 --> 01:18:43.390 align:start position:0% crazy stuff with tur machines with these crazy<01:18:41.600> guarantees<01:18:42.400> let's<01:18:42.639> sort<01:18:42.800> of<01:18:42.920> sit<01:18:43.159> down 01:18:43.390 --> 01:18:43.400 align:start position:0% crazy guarantees let's sort of sit down 01:18:43.400 --> 01:18:45.390 align:start position:0% crazy guarantees let's sort of sit down and<01:18:43.600> and<01:18:43.800> theorize<01:18:44.360> for<01:18:44.560> that<01:18:44.760> theorize<01:18:45.199> about 01:18:45.390 --> 01:18:45.400 align:start position:0% and and theorize for that theorize about 01:18:45.400 --> 01:18:46.790 align:start position:0% and and theorize for that theorize about that<01:18:45.520> for<01:18:45.639> a<01:18:45.760> really<01:18:45.960> long<01:18:46.199> time<01:18:46.440> and<01:18:46.560> build 01:18:46.790 --> 01:18:46.800 align:start position:0% that for a really long time and build 01:18:46.800 --> 01:18:48.430 align:start position:0% that for a really long time and build some<01:18:46.920> sort<01:18:47.080> of<01:18:47.239> like<01:18:47.560> crazy<01:18:47.880> like<01:18:48.040> category 01:18:48.430 --> 01:18:48.440 align:start position:0% some sort of like crazy like category 01:18:48.440 --> 01:18:50.870 align:start position:0% some sort of like crazy like category Theory<01:18:48.840> type<01:18:49.120> Theory<01:18:49.920> like<01:18:50.360> you<01:18:50.440> know<01:18:50.600> correct 01:18:50.870 --> 01:18:50.880 align:start position:0% Theory type Theory like you know correct 01:18:50.880 --> 01:18:53.709 align:start position:0% Theory type Theory like you know correct by<01:18:51.040> construction<01:18:51.520> sort<01:18:51.679> of<01:18:51.880> thing<01:18:52.719> um<01:18:53.560> and 01:18:53.709 --> 01:18:53.719 align:start position:0% by construction sort of thing um and 01:18:53.719 --> 01:18:55.229 align:start position:0% by construction sort of thing um and then<01:18:54.120> you<01:18:54.199> know<01:18:54.360> that<01:18:54.480> that's<01:18:54.840> real<01:18:55.000> mouse 01:18:55.229 --> 01:18:55.239 align:start position:0% then you know that that's real mouse 01:18:55.239 --> 01:18:56.790 align:start position:0% then you know that that's real mouse trap<01:18:55.520> too<01:18:55.840> we<01:18:55.960> don't<01:18:56.040> want<01:18:56.120> to<01:18:56.239> go<01:18:56.360> down<01:18:56.639> that 01:18:56.790 --> 01:18:56.800 align:start position:0% trap too we don't want to go down that 01:18:56.800 --> 01:18:58.550 align:start position:0% trap too we don't want to go down that rabbit<01:18:57.080> hole<01:18:57.600> but<01:18:57.840> somehow<01:18:58.120> we<01:18:58.239> still<01:18:58.360> want<01:18:58.440> to 01:18:58.550 --> 01:18:58.560 align:start position:0% rabbit hole but somehow we still want to 01:18:58.560 --> 01:19:00.070 align:start position:0% rabbit hole but somehow we still want to be<01:18:58.719> making<01:18:59.040> progress<01:18:59.440> knowing<01:18:59.760> that<01:18:59.920> this 01:19:00.070 --> 01:19:00.080 align:start position:0% be making progress knowing that this 01:19:00.080 --> 01:19:03.110 align:start position:0% be making progress knowing that this thing<01:19:00.480> has<01:19:00.679> as<01:19:00.840> Grand<01:19:01.080> of<01:19:01.159> a<01:19:01.280> scope<01:19:01.520> as<01:19:01.600> it<01:19:02.120> does 01:19:03.110 --> 01:19:03.120 align:start position:0% thing has as Grand of a scope as it does 01:19:03.120 --> 01:19:06.070 align:start position:0% thing has as Grand of a scope as it does okay<01:19:03.320> so<01:19:03.760> I<01:19:03.840> want<01:19:03.960> to<01:19:04.159> talk<01:19:04.400> about<01:19:05.120> some<01:19:05.320> of<01:19:05.679> our 01:19:06.070 --> 01:19:06.080 align:start position:0% okay so I want to talk about some of our 01:19:06.080 --> 01:19:07.950 align:start position:0% okay so I want to talk about some of our thinking<01:19:06.719> on<01:19:06.880> how<01:19:07.040> we've<01:19:07.280> approached<01:19:07.760> this 01:19:07.950 --> 01:19:07.960 align:start position:0% thinking on how we've approached this 01:19:07.960 --> 01:19:10.790 align:start position:0% thinking on how we've approached this problem<01:19:08.239> over<01:19:08.440> the<01:19:08.600> last<01:19:08.880> five<01:19:09.159> years<01:19:10.159> so 01:19:10.790 --> 01:19:10.800 align:start position:0% problem over the last five years so 01:19:10.800 --> 01:19:12.350 align:start position:0% problem over the last five years so beginning<01:19:11.440> about<01:19:11.679> five<01:19:11.880> years<01:19:12.040> ago<01:19:12.239> we 01:19:12.350 --> 01:19:12.360 align:start position:0% beginning about five years ago we 01:19:12.360 --> 01:19:13.950 align:start position:0% beginning about five years ago we started<01:19:12.560> to<01:19:12.719> get<01:19:12.840> the<01:19:13.040> sense<01:19:13.320> that<01:19:13.480> there<01:19:13.679> was 01:19:13.950 --> 01:19:13.960 align:start position:0% started to get the sense that there was 01:19:13.960 --> 01:19:15.550 align:start position:0% started to get the sense that there was something<01:19:14.360> interesting<01:19:14.840> happening<01:19:15.360> in 01:19:15.550 --> 01:19:15.560 align:start position:0% something interesting happening in 01:19:15.560 --> 01:19:17.310 align:start position:0% something interesting happening in cryptography<01:19:16.120> we<01:19:16.239> didn't<01:19:16.480> have<01:19:16.760> the<01:19:16.920> words<01:19:17.159> to 01:19:17.310 --> 01:19:17.320 align:start position:0% cryptography we didn't have the words to 01:19:17.320 --> 01:19:18.510 align:start position:0% cryptography we didn't have the words to describe<01:19:17.639> it<01:19:17.760> we<01:19:17.840> didn't<01:19:18.040> have<01:19:18.239> the<01:19:18.400> the 01:19:18.510 --> 01:19:18.520 align:start position:0% describe it we didn't have the the 01:19:18.520 --> 01:19:20.430 align:start position:0% describe it we didn't have the the Frameworks<01:19:19.360> you<01:19:19.440> know<01:19:19.600> nowadays<01:19:20.040> people<01:19:20.239> talk 01:19:20.430 --> 01:19:20.440 align:start position:0% Frameworks you know nowadays people talk 01:19:20.440 --> 01:19:22.310 align:start position:0% Frameworks you know nowadays people talk about<01:19:20.639> the<01:19:20.719> idea<01:19:21.000> of<01:19:21.280> oh<01:19:21.400> you<01:19:21.480> know<01:19:21.600> ZK<01:19:21.920> enables 01:19:22.310 --> 01:19:22.320 align:start position:0% about the idea of oh you know ZK enables 01:19:22.320 --> 01:19:24.430 align:start position:0% about the idea of oh you know ZK enables data<01:19:22.920> interoperability<01:19:23.920> that<01:19:24.040> was<01:19:24.159> not<01:19:24.320> how 01:19:24.430 --> 01:19:24.440 align:start position:0% data interoperability that was not how 01:19:24.440 --> 01:19:26.590 align:start position:0% data interoperability that was not how we<01:19:24.520> were<01:19:24.840> thinking<01:19:25.040> about<01:19:25.199> ZK<01:19:25.560> at<01:19:25.639> all<01:19:26.400> when<01:19:26.520> I 01:19:26.590 --> 01:19:26.600 align:start position:0% we were thinking about ZK at all when I 01:19:26.600 --> 01:19:27.870 align:start position:0% we were thinking about ZK at all when I started<01:19:26.880> building<01:19:27.120> a<01:19:27.239> game<01:19:27.440> called<01:19:27.639> Dark 01:19:27.870 --> 01:19:27.880 align:start position:0% started building a game called Dark 01:19:27.880 --> 01:19:30.510 align:start position:0% started building a game called Dark Forest<01:19:28.520> in<01:19:28.679> 2019<01:19:29.679> the<01:19:29.800> way<01:19:29.960> that<01:19:30.080> I<01:19:30.199> was 01:19:30.510 --> 01:19:30.520 align:start position:0% Forest in 2019 the way that I was 01:19:30.520 --> 01:19:31.870 align:start position:0% Forest in 2019 the way that I was thinking<01:19:30.800> about<01:19:31.000> this<01:19:31.199> was<01:19:31.480> I<01:19:31.560> had<01:19:31.719> just 01:19:31.870 --> 01:19:31.880 align:start position:0% thinking about this was I had just 01:19:31.880 --> 01:19:33.910 align:start position:0% thinking about this was I had just learned<01:19:32.239> about<01:19:32.440> ZK<01:19:32.840> snarks<01:19:33.159> from<01:19:33.360> Jordy 01:19:33.910 --> 01:19:33.920 align:start position:0% learned about ZK snarks from Jordy 01:19:33.920 --> 01:19:36.669 align:start position:0% learned about ZK snarks from Jordy actually<01:19:34.840> and<01:19:35.520> I<01:19:35.639> had<01:19:35.760> this<01:19:35.920> idea<01:19:36.400> wow<01:19:36.600> you 01:19:36.669 --> 01:19:36.679 align:start position:0% actually and I had this idea wow you 01:19:36.679 --> 01:19:38.030 align:start position:0% actually and I had this idea wow you could<01:19:36.800> use<01:19:37.000> zero<01:19:37.239> knowledge<01:19:37.520> proofs<01:19:37.880> and 01:19:38.030 --> 01:19:38.040 align:start position:0% could use zero knowledge proofs and 01:19:38.040 --> 01:19:40.550 align:start position:0% could use zero knowledge proofs and blockchain<01:19:38.480> to<01:19:38.639> build<01:19:39.000> this<01:19:39.320> really<01:19:39.760> specific 01:19:40.550 --> 01:19:40.560 align:start position:0% blockchain to build this really specific 01:19:40.560 --> 01:19:42.750 align:start position:0% blockchain to build this really specific and<01:19:40.840> very<01:19:41.080> strange<01:19:41.600> game<01:19:41.920> so<01:19:42.080> dark<01:19:42.280> forest<01:19:42.639> was 01:19:42.750 --> 01:19:42.760 align:start position:0% and very strange game so dark forest was 01:19:42.760 --> 01:19:44.470 align:start position:0% and very strange game so dark forest was a<01:19:42.880> game<01:19:43.120> built<01:19:43.360> on<01:19:43.480> zero<01:19:43.719> knowledge<01:19:43.960> proofs<01:19:44.320> on 01:19:44.470 --> 01:19:44.480 align:start position:0% a game built on zero knowledge proofs on 01:19:44.480 --> 01:19:47.030 align:start position:0% a game built on zero knowledge proofs on blockchain<01:19:45.440> um<01:19:45.639> it<01:19:45.760> was<01:19:45.920> one<01:19:46.040> of<01:19:46.360> if<01:19:46.560> not<01:19:46.920> the 01:19:47.030 --> 01:19:47.040 align:start position:0% blockchain um it was one of if not the 01:19:47.040 --> 01:19:49.830 align:start position:0% blockchain um it was one of if not the first<01:19:47.320> non-<01:19:47.880> cryptocurrency<01:19:48.880> application<01:19:49.679> of 01:19:49.830 --> 01:19:49.840 align:start position:0% first non- cryptocurrency application of 01:19:49.840 --> 01:19:51.550 align:start position:0% first non- cryptocurrency application of zero<01:19:50.120> knowledge<01:19:50.400> proofs<01:19:50.960> and<01:19:51.080> it<01:19:51.159> just<01:19:51.280> seemed 01:19:51.550 --> 01:19:51.560 align:start position:0% zero knowledge proofs and it just seemed 01:19:51.560 --> 01:19:54.950 align:start position:0% zero knowledge proofs and it just seemed like<01:19:51.679> a<01:19:51.840> total<01:19:52.159> one-off<01:19:52.679> hack<01:19:52.960> at<01:19:53.080> the<01:19:53.280> time<01:19:54.199> so 01:19:54.950 --> 01:19:54.960 align:start position:0% like a total one-off hack at the time so 01:19:54.960 --> 01:19:57.070 align:start position:0% like a total one-off hack at the time so um<01:19:55.199> we<01:19:55.360> spent<01:19:55.639> this<01:19:55.840> time<01:19:56.159> we<01:19:56.320> spent<01:19:56.560> some<01:19:56.719> time 01:19:57.070 --> 01:19:57.080 align:start position:0% um we spent this time we spent some time 01:19:57.080 --> 01:19:59.950 align:start position:0% um we spent this time we spent some time building<01:19:58.080> uh<01:19:58.280> Dark<01:19:58.520> Forest<01:19:59.320> and<01:19:59.560> what<01:19:59.679> we<01:19:59.800> came 01:19:59.950 --> 01:19:59.960 align:start position:0% building uh Dark Forest and what we came 01:19:59.960 --> 01:20:01.310 align:start position:0% building uh Dark Forest and what we came to<01:20:00.159> realize<01:20:00.520> was<01:20:00.719> actually<01:20:00.880> there<01:20:00.960> was<01:20:01.080> a 01:20:01.310 --> 01:20:01.320 align:start position:0% to realize was actually there was a 01:20:01.320 --> 01:20:04.350 align:start position:0% to realize was actually there was a general<01:20:02.080> principle<01:20:02.520> going<01:20:02.840> on<01:20:03.360> which<01:20:03.520> is<01:20:03.719> that 01:20:04.350 --> 01:20:04.360 align:start position:0% general principle going on which is that 01:20:04.360 --> 01:20:05.910 align:start position:0% general principle going on which is that zero<01:20:04.679> knowledge<01:20:04.960> proofs<01:20:05.360> were<01:20:05.560> not<01:20:05.719> just 01:20:05.910 --> 01:20:05.920 align:start position:0% zero knowledge proofs were not just 01:20:05.920 --> 01:20:07.550 align:start position:0% zero knowledge proofs were not just enabling<01:20:06.360> this<01:20:06.520> one<01:20:06.840> specific<01:20:07.360> game 01:20:07.550 --> 01:20:07.560 align:start position:0% enabling this one specific game 01:20:07.560 --> 01:20:08.990 align:start position:0% enabling this one specific game construction<01:20:08.239> they<01:20:08.320> were<01:20:08.440> enabling<01:20:08.880> this 01:20:08.990 --> 01:20:09.000 align:start position:0% construction they were enabling this 01:20:09.000 --> 01:20:11.430 align:start position:0% construction they were enabling this idea<01:20:09.199> of<01:20:09.400> incomplete<01:20:10.120> information<01:20:10.760> games<01:20:11.199> or 01:20:11.430 --> 01:20:11.440 align:start position:0% idea of incomplete information games or 01:20:11.440 --> 01:20:12.870 align:start position:0% idea of incomplete information games or games<01:20:11.719> where<01:20:11.880> players<01:20:12.199> have<01:20:12.360> some<01:20:12.560> private 01:20:12.870 --> 01:20:12.880 align:start position:0% games where players have some private 01:20:12.880 --> 01:20:14.870 align:start position:0% games where players have some private State<01:20:13.520> on<01:20:13.679> a<01:20:13.880> blockchain<01:20:14.480> or<01:20:14.639> on<01:20:14.760> a 01:20:14.870 --> 01:20:14.880 align:start position:0% State on a blockchain or on a 01:20:14.880 --> 01:20:16.270 align:start position:0% State on a blockchain or on a decentralized<01:20:15.520> system<01:20:15.880> where<01:20:16.040> the<01:20:16.159> whole 01:20:16.270 --> 01:20:16.280 align:start position:0% decentralized system where the whole 01:20:16.280 --> 01:20:19.350 align:start position:0% decentralized system where the whole state<01:20:16.480> is<01:20:16.760> public<01:20:17.760> so<01:20:18.440> that<01:20:18.679> enabled<01:20:19.000> us<01:20:19.159> to 01:20:19.350 --> 01:20:19.360 align:start position:0% state is public so that enabled us to 01:20:19.360 --> 01:20:20.910 align:start position:0% state is public so that enabled us to you<01:20:19.440> know<01:20:19.639> that<01:20:19.840> that<01:20:20.000> came<01:20:20.199> through<01:20:20.600> building 01:20:20.910 --> 01:20:20.920 align:start position:0% you know that that came through building 01:20:20.920 --> 01:20:22.510 align:start position:0% you know that that came through building a<01:20:21.000> bunch<01:20:21.159> of<01:20:21.320> other<01:20:21.520> prototypes<01:20:22.080> of<01:20:22.280> of<01:20:22.360> some 01:20:22.510 --> 01:20:22.520 align:start position:0% a bunch of other prototypes of of some 01:20:22.520 --> 01:20:24.189 align:start position:0% a bunch of other prototypes of of some other<01:20:22.679> games<01:20:22.960> this<01:20:23.040> is<01:20:23.120> a<01:20:23.239> screenshot<01:20:23.800> from<01:20:24.120> a 01:20:24.189 --> 01:20:24.199 align:start position:0% other games this is a screenshot from a 01:20:24.199 --> 01:20:27.510 align:start position:0% other games this is a screenshot from a game<01:20:24.360> we<01:20:24.440> built<01:20:24.800> called<01:20:25.040> boat<01:20:25.320> fight<01:20:26.320> um<01:20:26.840> and 01:20:27.510 --> 01:20:27.520 align:start position:0% game we built called boat fight um and 01:20:27.520 --> 01:20:29.709 align:start position:0% game we built called boat fight um and unlocking<01:20:28.239> that<01:20:28.400> realization<01:20:29.159> allowed<01:20:29.440> us<01:20:29.600> to 01:20:29.709 --> 01:20:29.719 align:start position:0% unlocking that realization allowed us to 01:20:29.719 --> 01:20:31.470 align:start position:0% unlocking that realization allowed us to suddenly<01:20:30.159> see<01:20:30.480> what<01:20:30.600> was<01:20:30.760> going<01:20:30.960> on<01:20:31.120> with<01:20:31.280> dark 01:20:31.470 --> 01:20:31.480 align:start position:0% suddenly see what was going on with dark 01:20:31.480 --> 01:20:33.149 align:start position:0% suddenly see what was going on with dark forest<01:20:31.960> and<01:20:32.080> this<01:20:32.239> category<01:20:32.560> of<01:20:32.719> games<01:20:33.080> and 01:20:33.149 --> 01:20:33.159 align:start position:0% forest and this category of games and 01:20:33.159 --> 01:20:34.629 align:start position:0% forest and this category of games and suddenly<01:20:33.440> it<01:20:33.520> became<01:20:33.800> actually<01:20:34.000> a<01:20:34.120> lot<01:20:34.320> easier 01:20:34.629 --> 01:20:34.639 align:start position:0% suddenly it became actually a lot easier 01:20:34.639 --> 01:20:36.510 align:start position:0% suddenly it became actually a lot easier to<01:20:34.880> build<01:20:35.440> the<01:20:35.639> different<01:20:35.920> kinds<01:20:36.120> of<01:20:36.239> features 01:20:36.510 --> 01:20:36.520 align:start position:0% to build the different kinds of features 01:20:36.520 --> 01:20:38.030 align:start position:0% to build the different kinds of features and<01:20:36.679> even<01:20:36.960> figure<01:20:37.159> out<01:20:37.400> what<01:20:37.639> kinds<01:20:37.880> of 01:20:38.030 --> 01:20:38.040 align:start position:0% and even figure out what kinds of 01:20:38.040 --> 01:20:39.790 align:start position:0% and even figure out what kinds of features<01:20:38.400> we<01:20:38.480> could<01:20:38.600> add<01:20:38.760> into<01:20:38.960> Dark<01:20:39.159> Forest 01:20:39.790 --> 01:20:39.800 align:start position:0% features we could add into Dark Forest 01:20:39.800 --> 01:20:41.510 align:start position:0% features we could add into Dark Forest so<01:20:39.960> for<01:20:40.120> example<01:20:40.719> you<01:20:40.800> know<01:20:40.920> early<01:20:41.159> on<01:20:41.360> the 01:20:41.510 --> 01:20:41.520 align:start position:0% so for example you know early on the 01:20:41.520 --> 01:20:42.830 align:start position:0% so for example you know early on the into<01:20:41.719> the<01:20:41.800> game<01:20:41.960> we<01:20:42.080> introduced<01:20:42.480> this<01:20:42.560> idea<01:20:42.760> of 01:20:42.830 --> 01:20:42.840 align:start position:0% into the game we introduced this idea of 01:20:42.840 --> 01:20:45.390 align:start position:0% into the game we introduced this idea of procedural<01:20:43.679> generation<01:20:44.679> that<01:20:44.800> was<01:20:44.960> enabled 01:20:45.390 --> 01:20:45.400 align:start position:0% procedural generation that was enabled 01:20:45.400 --> 01:20:47.430 align:start position:0% procedural generation that was enabled by<01:20:45.520> this<01:20:45.719> mental<01:20:46.040> model<01:20:46.360> unlock<01:20:46.719> of<01:20:46.880> what<01:20:47.040> ZK 01:20:47.430 --> 01:20:47.440 align:start position:0% by this mental model unlock of what ZK 01:20:47.440 --> 01:20:49.189 align:start position:0% by this mental model unlock of what ZK was<01:20:47.600> fundamentally<01:20:48.199> doing 01:20:49.189 --> 01:20:49.199 align:start position:0% was fundamentally doing 01:20:49.199 --> 01:20:52.990 align:start position:0% was fundamentally doing here<01:20:50.199> okay<01:20:50.679> so<01:20:51.040> then<01:20:51.199> we<01:20:51.400> get<01:20:51.639> into<01:20:52.440> uh<01:20:52.560> so<01:20:52.800> dark 01:20:52.990 --> 01:20:53.000 align:start position:0% here okay so then we get into uh so dark 01:20:53.000 --> 01:20:55.350 align:start position:0% here okay so then we get into uh so dark force<01:20:53.280> was<01:20:53.400> out<01:20:53.560> 2020<01:20:54.400> this<01:20:54.920> idea<01:20:55.199> of 01:20:55.350 --> 01:20:55.360 align:start position:0% force was out 2020 this idea of 01:20:55.360 --> 01:20:57.750 align:start position:0% force was out 2020 this idea of incomplete<01:20:55.840> information<01:20:56.199> was<01:20:56.320> about<01:20:56.600> 2021<01:20:57.600> in 01:20:57.750 --> 01:20:57.760 align:start position:0% incomplete information was about 2021 in 01:20:57.760 --> 01:21:00.070 align:start position:0% incomplete information was about 2021 in 2022<01:20:58.280> we<01:20:58.360> started<01:20:58.639> experimenting<01:20:59.480> with<01:20:59.920> wait 01:21:00.070 --> 01:21:00.080 align:start position:0% 2022 we started experimenting with wait 01:21:00.080 --> 01:21:01.790 align:start position:0% 2022 we started experimenting with wait a<01:21:00.199> second<01:21:00.440> can<01:21:00.560> we<01:21:00.679> apply<01:21:00.960> this<01:21:01.159> principle 01:21:01.790 --> 01:21:01.800 align:start position:0% a second can we apply this principle 01:21:01.800 --> 01:21:04.189 align:start position:0% a second can we apply this principle across<01:21:02.159> a<01:21:02.320> bunch<01:21:02.760> of<01:21:03.199> other<01:21:03.480> kinds<01:21:03.679> of<01:21:03.800> domains 01:21:04.189 --> 01:21:04.199 align:start position:0% across a bunch of other kinds of domains 01:21:04.199 --> 01:21:05.790 align:start position:0% across a bunch of other kinds of domains not<01:21:04.400> just<01:21:04.560> games<01:21:05.080> so<01:21:05.239> you<01:21:05.320> know<01:21:05.440> we<01:21:05.520> built<01:21:05.719> a 01:21:05.790 --> 01:21:05.800 align:start position:0% not just games so you know we built a 01:21:05.800 --> 01:21:07.950 align:start position:0% not just games so you know we built a bunch<01:21:05.920> of<01:21:06.040> these<01:21:06.159> circuits<01:21:06.840> we<01:21:07.000> built<01:21:07.560> um 01:21:07.950 --> 01:21:07.960 align:start position:0% bunch of these circuits we built um 01:21:07.960 --> 01:21:09.430 align:start position:0% bunch of these circuits we built um thing<01:21:08.199> we<01:21:08.320> had<01:21:08.440> folks<01:21:08.719> in<01:21:08.800> the<01:21:08.920> Xerox<01:21:09.280> park 01:21:09.430 --> 01:21:09.440 align:start position:0% thing we had folks in the Xerox park 01:21:09.440 --> 01:21:11.310 align:start position:0% thing we had folks in the Xerox park community<01:21:09.840> ecosystem<01:21:10.320> building<01:21:10.679> things<01:21:10.920> like 01:21:11.310 --> 01:21:11.320 align:start position:0% community ecosystem building things like 01:21:11.320 --> 01:21:14.070 align:start position:0% community ecosystem building things like private<01:21:11.639> message<01:21:11.960> boards<01:21:12.920> um<01:21:13.239> ZK<01:21:13.600> reppel<01:21:13.960> over 01:21:14.070 --> 01:21:14.080 align:start position:0% private message boards um ZK reppel over 01:21:14.080 --> 01:21:15.470 align:start position:0% private message boards um ZK reppel over here<01:21:14.199> is<01:21:14.320> a<01:21:14.440> developer<01:21:14.840> tool<01:21:15.040> for<01:21:15.199> working 01:21:15.470 --> 01:21:15.480 align:start position:0% here is a developer tool for working 01:21:15.480 --> 01:21:16.990 align:start position:0% here is a developer tool for working with<01:21:15.639> zero<01:21:15.960> knowledge<01:21:16.239> proofs<01:21:16.760> there's 01:21:16.990 --> 01:21:17.000 align:start position:0% with zero knowledge proofs there's 01:21:17.000 --> 01:21:18.950 align:start position:0% with zero knowledge proofs there's stealth<01:21:17.360> drop<01:21:18.280> which<01:21:18.360> was<01:21:18.520> like<01:21:18.679> private 01:21:18.950 --> 01:21:18.960 align:start position:0% stealth drop which was like private 01:21:18.960 --> 01:21:20.669 align:start position:0% stealth drop which was like private airdrops<01:21:19.679> and<01:21:19.800> we<01:21:19.960> got<01:21:20.120> the<01:21:20.239> sense<01:21:20.440> that<01:21:20.600> what 01:21:20.669 --> 01:21:20.679 align:start position:0% airdrops and we got the sense that what 01:21:20.679 --> 01:21:22.270 align:start position:0% airdrops and we got the sense that what was<01:21:20.840> going<01:21:21.000> on<01:21:21.320> was<01:21:21.639> you<01:21:21.760> know<01:21:21.880> the<01:21:22.040> Common 01:21:22.270 --> 01:21:22.280 align:start position:0% was going on was you know the Common 01:21:22.280 --> 01:21:24.110 align:start position:0% was going on was you know the Common Thread<01:21:22.560> between<01:21:22.800> all<01:21:22.920> of<01:21:23.040> these<01:21:23.239> things<01:21:23.880> and 01:21:24.110 --> 01:21:24.120 align:start position:0% Thread between all of these things and 01:21:24.120 --> 01:21:26.790 align:start position:0% Thread between all of these things and between<01:21:24.679> the<01:21:24.800> game<01:21:25.080> thread<01:21:25.679> was<01:21:25.920> this<01:21:26.080> idea<01:21:26.280> of 01:21:26.790 --> 01:21:26.800 align:start position:0% between the game thread was this idea of 01:21:26.800 --> 01:21:29.430 align:start position:0% between the game thread was this idea of programmable<01:21:27.800> privacy<01:21:28.719> right<01:21:28.840> and<01:21:29.000> I<01:21:29.120> I<01:21:29.199> use 01:21:29.430 --> 01:21:29.440 align:start position:0% programmable privacy right and I I use 01:21:29.440 --> 01:21:30.910 align:start position:0% programmable privacy right and I I use privacy<01:21:29.760> in<01:21:29.840> quotes<01:21:30.120> here<01:21:30.239> because<01:21:30.440> I<01:21:30.600> I<01:21:30.760> sort 01:21:30.910 --> 01:21:30.920 align:start position:0% privacy in quotes here because I I sort 01:21:30.920 --> 01:21:32.550 align:start position:0% privacy in quotes here because I I sort of<01:21:31.280> am<01:21:31.440> referring<01:21:31.760> to<01:21:31.880> a<01:21:32.040> specific 01:21:32.550 --> 01:21:32.560 align:start position:0% of am referring to a specific 01:21:32.560 --> 01:21:33.950 align:start position:0% of am referring to a specific connotation<01:21:32.960> of<01:21:33.120> privacy<01:21:33.480> which<01:21:33.600> is<01:21:33.760> oh<01:21:33.880> I 01:21:33.950 --> 01:21:33.960 align:start position:0% connotation of privacy which is oh I 01:21:33.960 --> 01:21:35.470 align:start position:0% connotation of privacy which is oh I want<01:21:34.080> to<01:21:34.320> hide<01:21:34.560> something<01:21:34.800> I<01:21:34.880> want<01:21:35.000> to<01:21:35.120> have 01:21:35.470 --> 01:21:35.480 align:start position:0% want to hide something I want to have 01:21:35.480 --> 01:21:37.149 align:start position:0% want to hide something I want to have anonymity<01:21:36.080> or<01:21:36.159> pseudonymity<01:21:36.800> or<01:21:36.920> something 01:21:37.149 --> 01:21:37.159 align:start position:0% anonymity or pseudonymity or something 01:21:37.159 --> 01:21:40.270 align:start position:0% anonymity or pseudonymity or something like<01:21:37.639> that<01:21:38.639> and<01:21:39.159> we<01:21:39.320> kind<01:21:39.440> of<01:21:39.560> distilled<01:21:40.080> this 01:21:40.270 --> 01:21:40.280 align:start position:0% like that and we kind of distilled this 01:21:40.280 --> 01:21:43.390 align:start position:0% like that and we kind of distilled this down<01:21:40.760> into<01:21:41.000> this<01:21:41.199> idea<01:21:41.520> that<01:21:41.679> ZK<01:21:42.120> snarks<01:21:42.760> turn 01:21:43.390 --> 01:21:43.400 align:start position:0% down into this idea that ZK snarks turn 01:21:43.400 --> 01:21:45.030 align:start position:0% down into this idea that ZK snarks turn cryptography<01:21:44.040> problems<01:21:44.360> into<01:21:44.600> programming 01:21:45.030 --> 01:21:45.040 align:start position:0% cryptography problems into programming 01:21:45.040 --> 01:21:46.830 align:start position:0% cryptography problems into programming tasks<01:21:45.560> it<01:21:45.639> was<01:21:45.800> much<01:21:46.000> like<01:21:46.199> what<01:21:46.360> vitalic<01:21:46.760> was 01:21:46.830 --> 01:21:46.840 align:start position:0% tasks it was much like what vitalic was 01:21:46.840 --> 01:21:49.189 align:start position:0% tasks it was much like what vitalic was sort<01:21:46.960> of<01:21:47.080> saying<01:21:47.239> in<01:21:47.320> the<01:21:47.440> morning<01:21:48.120> where<01:21:49.040> uh 01:21:49.189 --> 01:21:49.199 align:start position:0% sort of saying in the morning where uh 01:21:49.199 --> 01:21:51.750 align:start position:0% sort of saying in the morning where uh we<01:21:49.360> don't<01:21:50.239> you<01:21:50.400> know<01:21:50.719> need<01:21:50.920> a<01:21:51.120> cryptographer 01:21:51.750 --> 01:21:51.760 align:start position:0% we don't you know need a cryptographer 01:21:51.760 --> 01:21:53.070 align:start position:0% we don't you know need a cryptographer to<01:21:51.880> invent<01:21:52.159> for<01:21:52.280> us<01:21:52.360> a<01:21:52.480> new<01:21:52.600> protocol<01:21:52.960> for 01:21:53.070 --> 01:21:53.080 align:start position:0% to invent for us a new protocol for 01:21:53.080 --> 01:21:54.750 align:start position:0% to invent for us a new protocol for every<01:21:53.320> feature<01:21:53.800> you<01:21:53.920> can<01:21:54.080> have<01:21:54.159> someone<01:21:54.600> WR 01:21:54.750 --> 01:21:54.760 align:start position:0% every feature you can have someone WR 01:21:54.760 --> 01:21:57.350 align:start position:0% every feature you can have someone WR code<01:21:54.920> and<01:21:55.080> compile<01:21:55.440> that<01:21:55.560> into 01:21:57.350 --> 01:21:57.360 align:start position:0% code and compile that into 01:21:57.360 --> 01:22:00.430 align:start position:0% code and compile that into cryptography<01:21:58.360> okay<01:21:58.480> so<01:21:58.719> from<01:21:59.000> there<01:21:59.400> once<01:21:59.719> we 01:22:00.430 --> 01:22:00.440 align:start position:0% cryptography okay so from there once we 01:22:00.440 --> 01:22:02.350 align:start position:0% cryptography okay so from there once we had<01:22:00.600> this<01:22:00.760> notion<01:22:01.000> of<01:22:01.159> programmable<01:22:01.639> cryptog 01:22:02.350 --> 01:22:02.360 align:start position:0% had this notion of programmable cryptog 01:22:02.360 --> 01:22:04.870 align:start position:0% had this notion of programmable cryptog programmable<01:22:03.199> privacy<01:22:03.679> we<01:22:03.760> were<01:22:03.960> like<01:22:04.440> well 01:22:04.870 --> 01:22:04.880 align:start position:0% programmable privacy we were like well 01:22:04.880 --> 01:22:06.229 align:start position:0% programmable privacy we were like well let's<01:22:05.080> step<01:22:05.280> on<01:22:05.400> the<01:22:05.560> gas<01:22:05.760> pedal<01:22:06.000> here<01:22:06.159> the 01:22:06.229 --> 01:22:06.239 align:start position:0% let's step on the gas pedal here the 01:22:06.239 --> 01:22:07.590 align:start position:0% let's step on the gas pedal here the point<01:22:06.440> is<01:22:06.560> now<01:22:06.719> a<01:22:06.800> bunch<01:22:06.960> of<01:22:07.080> people<01:22:07.280> can<01:22:07.400> make 01:22:07.590 --> 01:22:07.600 align:start position:0% point is now a bunch of people can make 01:22:07.600 --> 01:22:09.430 align:start position:0% point is now a bunch of people can make privacy<01:22:08.000> preserving<01:22:08.480> applications<01:22:09.280> and 01:22:09.430 --> 01:22:09.440 align:start position:0% privacy preserving applications and 01:22:09.440 --> 01:22:11.149 align:start position:0% privacy preserving applications and those<01:22:09.600> people<01:22:09.880> specifically<01:22:10.639> don't<01:22:10.920> have<01:22:11.040> to 01:22:11.149 --> 01:22:11.159 align:start position:0% those people specifically don't have to 01:22:11.159 --> 01:22:13.110 align:start position:0% those people specifically don't have to be<01:22:11.400> cryptographers<01:22:12.400> so<01:22:12.520> we<01:22:12.639> got<01:22:12.760> a<01:22:12.880> bunch<01:22:13.040> of 01:22:13.110 --> 01:22:13.120 align:start position:0% be cryptographers so we got a bunch of 01:22:13.120 --> 01:22:14.550 align:start position:0% be cryptographers so we got a bunch of people<01:22:13.440> together<01:22:13.760> started<01:22:14.040> bringing<01:22:14.320> folks 01:22:14.550 --> 01:22:14.560 align:start position:0% people together started bringing folks 01:22:14.560 --> 01:22:17.149 align:start position:0% people together started bringing folks into<01:22:14.800> this<01:22:14.960> ZK<01:22:15.360> ecosystem<01:22:16.360> and<01:22:16.600> we<01:22:16.760> produced 01:22:17.149 --> 01:22:17.159 align:start position:0% into this ZK ecosystem and we produced 01:22:17.159 --> 01:22:18.709 align:start position:0% into this ZK ecosystem and we produced things<01:22:17.400> like<01:22:17.560> the<01:22:17.719> first<01:22:18.120> zero<01:22:18.440> knowledge 01:22:18.709 --> 01:22:18.719 align:start position:0% things like the first zero knowledge 01:22:18.719 --> 01:22:20.470 align:start position:0% things like the first zero knowledge machine<01:22:18.960> learning<01:22:19.320> demonstrations<01:22:20.280> stuff 01:22:20.470 --> 01:22:20.480 align:start position:0% machine learning demonstrations stuff 01:22:20.480 --> 01:22:21.950 align:start position:0% machine learning demonstrations stuff like<01:22:20.679> handon<01:22:21.199> with<01:22:21.360> pseudonymous<01:22:21.840> or 01:22:21.950 --> 01:22:21.960 align:start position:0% like handon with pseudonymous or 01:22:21.960 --> 01:22:23.910 align:start position:0% like handon with pseudonymous or Anonymous<01:22:22.400> speech<01:22:23.080> ethos<01:22:23.600> which<01:22:23.719> was<01:22:23.840> the 01:22:23.910 --> 01:22:23.920 align:start position:0% Anonymous speech ethos which was the 01:22:23.920 --> 01:22:27.030 align:start position:0% Anonymous speech ethos which was the first<01:22:24.120> demonst<01:22:24.639> ation<01:22:25.000> of<01:22:25.320> recursive<01:22:25.840> zkps<01:22:26.800> in 01:22:27.030 --> 01:22:27.040 align:start position:0% first demonst ation of recursive zkps in 01:22:27.040 --> 01:22:30.030 align:start position:0% first demonst ation of recursive zkps in a<01:22:27.239> consumer<01:22:27.800> social<01:22:28.440> graph<01:22:28.800> kind<01:22:28.920> of<01:22:29.040> use<01:22:29.360> case 01:22:30.030 --> 01:22:30.040 align:start position:0% a consumer social graph kind of use case 01:22:30.040 --> 01:22:31.390 align:start position:0% a consumer social graph kind of use case um<01:22:30.239> things<01:22:30.480> which<01:22:30.600> would<01:22:30.760> allow<01:22:30.920> you<01:22:31.000> to<01:22:31.120> Port 01:22:31.390 --> 01:22:31.400 align:start position:0% um things which would allow you to Port 01:22:31.400 --> 01:22:32.990 align:start position:0% um things which would allow you to Port RSA<01:22:31.840> identities<01:22:32.239> into<01:22:32.480> zero<01:22:32.719> knowledge 01:22:32.990 --> 01:22:33.000 align:start position:0% RSA identities into zero knowledge 01:22:33.000 --> 01:22:35.189 align:start position:0% RSA identities into zero knowledge proofs<01:22:33.880> and<01:22:33.960> so<01:22:34.080> we<01:22:34.199> did<01:22:34.400> probably<01:22:34.760> like<01:22:35.120> you 01:22:35.189 --> 01:22:35.199 align:start position:0% proofs and so we did probably like you 01:22:35.199 --> 01:22:37.910 align:start position:0% proofs and so we did probably like you know<01:22:35.440> five<01:22:35.679> 10<01:22:36.000> 15<01:22:36.280> of<01:22:36.400> these<01:22:36.600> projects<01:22:37.480> and 01:22:37.910 --> 01:22:37.920 align:start position:0% know five 10 15 of these projects and 01:22:37.920 --> 01:22:39.990 align:start position:0% know five 10 15 of these projects and that's<01:22:38.320> what<01:22:38.920> got<01:22:39.120> us<01:22:39.280> to<01:22:39.440> arrive<01:22:39.719> at<01:22:39.840> this 01:22:39.990 --> 01:22:40.000 align:start position:0% that's what got us to arrive at this 01:22:40.000 --> 01:22:42.189 align:start position:0% that's what got us to arrive at this other<01:22:40.280> concept<01:22:40.679> called<01:22:40.880> proof<01:22:41.199> carrying<01:22:41.560> data 01:22:42.189 --> 01:22:42.199 align:start position:0% other concept called proof carrying data 01:22:42.199 --> 01:22:43.950 align:start position:0% other concept called proof carrying data the<01:22:42.320> idea<01:22:42.639> that<01:22:42.880> actually<01:22:43.400> the<01:22:43.560> thing<01:22:43.760> going 01:22:43.950 --> 01:22:43.960 align:start position:0% the idea that actually the thing going 01:22:43.960 --> 01:22:45.910 align:start position:0% the idea that actually the thing going on<01:22:44.159> here<01:22:44.280> with<01:22:44.400> zero<01:22:44.639> knowledge<01:22:44.920> proofs<01:22:45.639> is 01:22:45.910 --> 01:22:45.920 align:start position:0% on here with zero knowledge proofs is 01:22:45.920 --> 01:22:48.470 align:start position:0% on here with zero knowledge proofs is not<01:22:46.480> something<01:22:46.840> about<01:22:47.320> privacy<01:22:48.120> or 01:22:48.470 --> 01:22:48.480 align:start position:0% not something about privacy or 01:22:48.480 --> 01:22:50.310 align:start position:0% not something about privacy or scalability<01:22:49.239> like<01:22:49.440> yes<01:22:49.679> those<01:22:49.880> things<01:22:50.120> are 01:22:50.310 --> 01:22:50.320 align:start position:0% scalability like yes those things are 01:22:50.320 --> 01:22:51.550 align:start position:0% scalability like yes those things are very<01:22:50.520> relevant<01:22:50.880> particularly<01:22:51.320> in<01:22:51.400> the 01:22:51.550 --> 01:22:51.560 align:start position:0% very relevant particularly in the 01:22:51.560 --> 01:22:54.149 align:start position:0% very relevant particularly in the blockchain<01:22:52.080> context<01:22:52.960> but<01:22:53.400> after<01:22:53.639> building<01:22:54.000> 10 01:22:54.149 --> 01:22:54.159 align:start position:0% blockchain context but after building 10 01:22:54.159 --> 01:22:55.990 align:start position:0% blockchain context but after building 10 or<01:22:54.520> 15<01:22:54.719> of<01:22:54.840> these<01:22:54.960> apps<01:22:55.159> we<01:22:55.280> realized<01:22:55.639> that 01:22:55.990 --> 01:22:56.000 align:start position:0% or 15 of these apps we realized that 01:22:56.000 --> 01:22:57.350 align:start position:0% or 15 of these apps we realized that what<01:22:56.120> the<01:22:56.239> zero<01:22:56.520> knowledge<01:22:56.800> proofs<01:22:57.120> were 01:22:57.350 --> 01:22:57.360 align:start position:0% what the zero knowledge proofs were 01:22:57.360 --> 01:22:59.110 align:start position:0% what the zero knowledge proofs were fundamentally<01:22:58.040> doing<01:22:58.400> that<01:22:58.520> was<01:22:58.600> a<01:22:58.800> Common 01:22:59.110 --> 01:22:59.120 align:start position:0% fundamentally doing that was a Common 01:22:59.120 --> 01:23:00.750 align:start position:0% fundamentally doing that was a Common Thread<01:22:59.320> in<01:22:59.480> each<01:22:59.600> of<01:22:59.760> these<01:22:59.960> apps<01:23:00.520> was<01:23:00.679> they 01:23:00.750 --> 01:23:00.760 align:start position:0% Thread in each of these apps was they 01:23:00.760 --> 01:23:03.229 align:start position:0% Thread in each of these apps was they were<01:23:00.960> enabling<01:23:01.880> permissionless<01:23:02.880> data 01:23:03.229 --> 01:23:03.239 align:start position:0% were enabling permissionless data 01:23:03.239 --> 01:23:06.270 align:start position:0% were enabling permissionless data porting<01:23:03.920> from<01:23:04.159> Source<01:23:04.560> a<01:23:04.800> to<01:23:05.040> destination<01:23:05.719> B 01:23:06.270 --> 01:23:06.280 align:start position:0% porting from Source a to destination B 01:23:06.280 --> 01:23:07.950 align:start position:0% porting from Source a to destination B so<01:23:06.520> now<01:23:06.719> you<01:23:06.800> can<01:23:06.960> move<01:23:07.159> things<01:23:07.320> like<01:23:07.440> a<01:23:07.560> GitHub 01:23:07.950 --> 01:23:07.960 align:start position:0% so now you can move things like a GitHub 01:23:07.960 --> 01:23:09.950 align:start position:0% so now you can move things like a GitHub Identity<01:23:08.360> or<01:23:08.480> an<01:23:08.639> email<01:23:09.280> or<01:23:09.440> anything<01:23:09.760> like 01:23:09.950 --> 01:23:09.960 align:start position:0% Identity or an email or anything like 01:23:09.960 --> 01:23:13.950 align:start position:0% Identity or an email or anything like that<01:23:10.920> from<01:23:11.639> this<01:23:12.639> Destin<01:23:13.159> um<01:23:13.320> from<01:23:13.560> this 01:23:13.950 --> 01:23:13.960 align:start position:0% that from this Destin um from this 01:23:13.960 --> 01:23:16.629 align:start position:0% that from this Destin um from this origin<01:23:14.480> Source<01:23:15.400> o<01:23:15.560> over<01:23:15.760> to<01:23:15.920> this<01:23:16.120> destination 01:23:16.629 --> 01:23:16.639 align:start position:0% origin Source o over to this destination 01:23:16.639 --> 01:23:18.590 align:start position:0% origin Source o over to this destination without<01:23:16.880> needing<01:23:17.120> to<01:23:17.280> call<01:23:17.560> apis<01:23:18.040> or<01:23:18.199> things 01:23:18.590 --> 01:23:18.600 align:start position:0% without needing to call apis or things 01:23:18.600 --> 01:23:20.750 align:start position:0% without needing to call apis or things like<01:23:18.800> that<01:23:19.800> okay<01:23:19.920> so<01:23:20.040> that<01:23:20.159> gets<01:23:20.280> us<01:23:20.400> to<01:23:20.520> proof 01:23:20.750 --> 01:23:20.760 align:start position:0% like that okay so that gets us to proof 01:23:20.760 --> 01:23:23.030 align:start position:0% like that okay so that gets us to proof carrying<01:23:21.040> data<01:23:21.880> um<01:23:22.159> we<01:23:22.280> built<01:23:22.520> this<01:23:22.639> framework 01:23:23.030 --> 01:23:23.040 align:start position:0% carrying data um we built this framework 01:23:23.040 --> 01:23:24.950 align:start position:0% carrying data um we built this framework called<01:23:23.159> the<01:23:23.280> proof<01:23:23.560> carrying<01:23:23.840> data<01:23:24.560> software 01:23:24.950 --> 01:23:24.960 align:start position:0% called the proof carrying data software 01:23:24.960 --> 01:23:26.629 align:start position:0% called the proof carrying data software framework<01:23:25.440> so<01:23:25.600> this<01:23:25.679> is<01:23:25.800> a<01:23:25.880> mental<01:23:26.199> model<01:23:26.520> that 01:23:26.629 --> 01:23:26.639 align:start position:0% framework so this is a mental model that 01:23:26.639 --> 01:23:28.270 align:start position:0% framework so this is a mental model that then<01:23:26.800> got<01:23:27.040> actually<01:23:27.360> translated<01:23:27.880> into<01:23:28.080> a 01:23:28.270 --> 01:23:28.280 align:start position:0% then got actually translated into a 01:23:28.280 --> 01:23:30.229 align:start position:0% then got actually translated into a library<01:23:28.760> and<01:23:29.120> the<01:23:29.199> beginnings<01:23:29.560> of<01:23:29.679> a<01:23:29.840> software 01:23:30.229 --> 01:23:30.239 align:start position:0% library and the beginnings of a software 01:23:30.239 --> 01:23:31.910 align:start position:0% library and the beginnings of a software abstraction<01:23:31.080> and<01:23:31.159> then<01:23:31.280> we<01:23:31.400> started<01:23:31.639> building 01:23:31.910 --> 01:23:31.920 align:start position:0% abstraction and then we started building 01:23:31.920 --> 01:23:34.470 align:start position:0% abstraction and then we started building a<01:23:32.000> bunch<01:23:32.159> of<01:23:32.280> stuff<01:23:32.480> on<01:23:32.639> proof<01:23:32.920> carrying<01:23:33.480> data 01:23:34.470 --> 01:23:34.480 align:start position:0% a bunch of stuff on proof carrying data 01:23:34.480 --> 01:23:36.590 align:start position:0% a bunch of stuff on proof carrying data so<01:23:34.760> this<01:23:34.840> is<01:23:35.000> kind<01:23:35.120> of<01:23:35.320> the<01:23:35.880> the<01:23:36.040> the<01:23:36.159> Blind<01:23:36.440> Men 01:23:36.590 --> 01:23:36.600 align:start position:0% so this is kind of the the the Blind Men 01:23:36.600 --> 01:23:37.830 align:start position:0% so this is kind of the the the Blind Men and<01:23:36.679> the<01:23:36.760> elevant<01:23:37.120> sort<01:23:37.280> of<01:23:37.400> thing<01:23:37.600> we<01:23:37.679> were 01:23:37.830 --> 01:23:37.840 align:start position:0% and the elevant sort of thing we were 01:23:37.840 --> 01:23:39.070 align:start position:0% and the elevant sort of thing we were realizing<01:23:38.199> that<01:23:38.360> all<01:23:38.480> of<01:23:38.639> these<01:23:38.760> eight<01:23:38.920> things 01:23:39.070 --> 01:23:39.080 align:start position:0% realizing that all of these eight things 01:23:39.080 --> 01:23:40.950 align:start position:0% realizing that all of these eight things were<01:23:39.239> instances<01:23:39.639> of<01:23:39.800> this<01:23:39.920> common 01:23:40.950 --> 01:23:40.960 align:start position:0% were instances of this common 01:23:40.960 --> 01:23:43.510 align:start position:0% were instances of this common category<01:23:41.960> um<01:23:42.199> so<01:23:42.440> a<01:23:42.520> lot<01:23:42.639> of<01:23:42.760> our<01:23:42.880> proof<01:23:43.199> caring 01:23:43.510 --> 01:23:43.520 align:start position:0% category um so a lot of our proof caring 01:23:43.520 --> 01:23:46.550 align:start position:0% category um so a lot of our proof caring data<01:23:44.120> experiments<01:23:44.639> led<01:23:44.880> us<01:23:45.080> to<01:23:45.679> Zulu<01:23:46.440> which 01:23:46.550 --> 01:23:46.560 align:start position:0% data experiments led us to Zulu which 01:23:46.560 --> 01:23:48.830 align:start position:0% data experiments led us to Zulu which was<01:23:46.679> a<01:23:46.800> community<01:23:47.239> that<01:23:47.360> wanted<01:23:47.679> to<01:23:48.040> adopt 01:23:48.830 --> 01:23:48.840 align:start position:0% was a community that wanted to adopt 01:23:48.840 --> 01:23:50.709 align:start position:0% was a community that wanted to adopt decentralized<01:23:49.719> identities<01:23:50.159> cryptographic 01:23:50.709 --> 01:23:50.719 align:start position:0% decentralized identities cryptographic 01:23:50.719 --> 01:23:53.430 align:start position:0% decentralized identities cryptographic identities<01:23:51.440> work<01:23:51.639> with<01:23:51.800> cryptographic<01:23:52.440> data 01:23:53.430 --> 01:23:53.440 align:start position:0% identities work with cryptographic data 01:23:53.440 --> 01:23:55.590 align:start position:0% identities work with cryptographic data and<01:23:53.760> we<01:23:53.880> built<01:23:54.120> this<01:23:54.239> thing<01:23:54.520> called<01:23:54.719> zup<01:23:55.080> pass 01:23:55.590 --> 01:23:55.600 align:start position:0% and we built this thing called zup pass 01:23:55.600 --> 01:23:57.550 align:start position:0% and we built this thing called zup pass which<01:23:56.120> everyone<01:23:56.560> here<01:23:56.880> has<01:23:57.040> used<01:23:57.360> to 01:23:57.550 --> 01:23:57.560 align:start position:0% which everyone here has used to 01:23:57.560 --> 01:23:59.830 align:start position:0% which everyone here has used to basically<01:23:58.360> uh<01:23:58.480> claim<01:23:58.760> their<01:23:58.960> ticket<01:23:59.320> generate 01:23:59.830 --> 01:23:59.840 align:start position:0% basically uh claim their ticket generate 01:23:59.840 --> 01:24:02.030 align:start position:0% basically uh claim their ticket generate a<01:24:00.000> zero<01:24:00.320> knowledge<01:24:00.679> friendly<01:24:01.120> identity<01:24:01.920> um 01:24:02.030 --> 01:24:02.040 align:start position:0% a zero knowledge friendly identity um 01:24:02.040 --> 01:24:04.030 align:start position:0% a zero knowledge friendly identity um and<01:24:02.120> store<01:24:02.400> zero<01:24:02.679> knowledge<01:24:03.040> friendly<01:24:03.480> data 01:24:04.030 --> 01:24:04.040 align:start position:0% and store zero knowledge friendly data 01:24:04.040 --> 01:24:05.709 align:start position:0% and store zero knowledge friendly data and<01:24:04.159> we<01:24:04.280> built<01:24:04.480> a<01:24:04.600> bunch<01:24:04.760> of<01:24:04.920> apps<01:24:05.199> on<01:24:05.400> top<01:24:05.560> of 01:24:05.709 --> 01:24:05.719 align:start position:0% and we built a bunch of apps on top of 01:24:05.719 --> 01:24:07.950 align:start position:0% and we built a bunch of apps on top of this<01:24:05.960> concept<01:24:06.440> of<01:24:06.600> proof<01:24:06.960> carrying<01:24:07.239> data<01:24:07.760> with 01:24:07.950 --> 01:24:07.960 align:start position:0% this concept of proof carrying data with 01:24:07.960 --> 01:24:11.550 align:start position:0% this concept of proof carrying data with zup<01:24:08.360> pass<01:24:08.800> as<01:24:09.120> one<01:24:09.280> of<01:24:09.560> our<01:24:10.199> levers<01:24:11.199> so<01:24:11.320> we<01:24:11.440> have 01:24:11.550 --> 01:24:11.560 align:start position:0% zup pass as one of our levers so we have 01:24:11.560 --> 01:24:12.950 align:start position:0% zup pass as one of our levers so we have things<01:24:11.719> like<01:24:11.840> you<01:24:11.920> know<01:24:12.040> the<01:24:12.120> frog<01:24:12.480> game<01:24:12.840> you 01:24:12.950 --> 01:24:12.960 align:start position:0% things like you know the frog game you 01:24:12.960 --> 01:24:14.030 align:start position:0% things like you know the frog game you can<01:24:13.040> make<01:24:13.199> zero<01:24:13.440> knowledge<01:24:13.639> proofs<01:24:13.920> about 01:24:14.030 --> 01:24:14.040 align:start position:0% can make zero knowledge proofs about 01:24:14.040 --> 01:24:16.470 align:start position:0% can make zero knowledge proofs about your<01:24:14.199> frogs<01:24:14.800> we<01:24:14.920> had<01:24:15.040> zo<01:24:15.360> pole<01:24:16.000> which<01:24:16.120> was<01:24:16.280> a 01:24:16.470 --> 01:24:16.480 align:start position:0% your frogs we had zo pole which was a 01:24:16.480 --> 01:24:19.189 align:start position:0% your frogs we had zo pole which was a polling<01:24:17.000> app<01:24:17.400> for<01:24:17.639> the<01:24:17.760> Zulu<01:24:18.280> community<01:24:19.040> that 01:24:19.189 --> 01:24:19.199 align:start position:0% polling app for the Zulu community that 01:24:19.199 --> 01:24:20.510 align:start position:0% polling app for the Zulu community that also<01:24:19.440> expanded<01:24:19.840> to<01:24:19.960> a<01:24:20.040> couple<01:24:20.239> of<01:24:20.360> other 01:24:20.510 --> 01:24:20.520 align:start position:0% also expanded to a couple of other 01:24:20.520 --> 01:24:23.030 align:start position:0% also expanded to a couple of other communities<01:24:21.080> zuo<01:24:21.560> cast<01:24:22.080> or<01:24:22.280> zookat<01:24:22.920> which 01:24:23.030 --> 01:24:23.040 align:start position:0% communities zuo cast or zookat which 01:24:23.040 --> 01:24:25.390 align:start position:0% communities zuo cast or zookat which were<01:24:23.280> these<01:24:23.719> social<01:24:24.400> sort<01:24:24.560> of<01:24:24.719> private<01:24:25.080> social 01:24:25.390 --> 01:24:25.400 align:start position:0% were these social sort of private social 01:24:25.400 --> 01:24:27.550 align:start position:0% were these social sort of private social Message<01:24:25.719> Board<01:24:26.040> apps<01:24:26.320> for<01:24:26.520> these<01:24:26.719> communities 01:24:27.550 --> 01:24:27.560 align:start position:0% Message Board apps for these communities 01:24:27.560 --> 01:24:29.430 align:start position:0% Message Board apps for these communities um<01:24:27.679> just<01:24:27.800> these<01:24:28.000> various<01:24:28.320> different 01:24:29.430 --> 01:24:29.440 align:start position:0% um just these various different 01:24:29.440 --> 01:24:32.390 align:start position:0% um just these various different things<01:24:30.440> and<01:24:30.679> we<01:24:30.840> built<01:24:31.080> a<01:24:31.199> bunch<01:24:31.400> of<01:24:31.719> pcds 01:24:32.390 --> 01:24:32.400 align:start position:0% things and we built a bunch of pcds 01:24:32.400 --> 01:24:34.790 align:start position:0% things and we built a bunch of pcds proof<01:24:32.679> caring<01:24:33.000> data<01:24:33.600> uh<01:24:33.760> instances<01:24:34.600> and<01:24:34.679> we 01:24:34.790 --> 01:24:34.800 align:start position:0% proof caring data uh instances and we 01:24:34.800 --> 01:24:35.830 align:start position:0% proof caring data uh instances and we tried<01:24:35.000> to<01:24:35.080> build<01:24:35.239> a<01:24:35.320> bunch<01:24:35.480> of<01:24:35.560> stuff<01:24:35.719> with 01:24:35.830 --> 01:24:35.840 align:start position:0% tried to build a bunch of stuff with 01:24:35.840 --> 01:24:37.470 align:start position:0% tried to build a bunch of stuff with them<01:24:35.960> and<01:24:36.040> then<01:24:36.320> we<01:24:36.400> ran<01:24:36.600> into<01:24:36.800> more<01:24:37.000> limits 01:24:37.470 --> 01:24:37.480 align:start position:0% them and then we ran into more limits 01:24:37.480 --> 01:24:38.910 align:start position:0% them and then we ran into more limits and<01:24:37.560> then<01:24:37.719> we<01:24:37.880> started<01:24:38.159> to<01:24:38.280> factor<01:24:38.560> out<01:24:38.760> well 01:24:38.910 --> 01:24:38.920 align:start position:0% and then we started to factor out well 01:24:38.920 --> 01:24:41.550 align:start position:0% and then we started to factor out well what<01:24:39.080> are<01:24:39.239> the<01:24:39.480> common<01:24:39.880> threads<01:24:40.679> where<01:24:41.199> those 01:24:41.550 --> 01:24:41.560 align:start position:0% what are the common threads where those 01:24:41.560 --> 01:24:44.310 align:start position:0% what are the common threads where those limitations<01:24:42.560> are<01:24:42.800> holding<01:24:43.159> us<01:24:43.400> back<01:24:44.040> and<01:24:44.199> this 01:24:44.310 --> 01:24:44.320 align:start position:0% limitations are holding us back and this 01:24:44.320 --> 01:24:45.990 align:start position:0% limitations are holding us back and this is<01:24:44.480> what<01:24:44.760> really<01:24:44.960> led<01:24:45.159> us<01:24:45.280> to<01:24:45.440> programmable 01:24:45.990 --> 01:24:46.000 align:start position:0% is what really led us to programmable 01:24:46.000 --> 01:24:48.510 align:start position:0% is what really led us to programmable cryptography<01:24:46.679> so<01:24:47.040> for<01:24:47.239> example<01:24:47.960> with<01:24:48.159> proof 01:24:48.510 --> 01:24:48.520 align:start position:0% cryptography so for example with proof 01:24:48.520 --> 01:24:50.590 align:start position:0% cryptography so for example with proof carrying<01:24:48.760> data<01:24:48.960> and<01:24:49.080> with<01:24:49.239> ZK<01:24:49.600> snarks<01:24:50.480> we 01:24:50.590 --> 01:24:50.600 align:start position:0% carrying data and with ZK snarks we 01:24:50.600 --> 01:24:52.870 align:start position:0% carrying data and with ZK snarks we could<01:24:50.800> only<01:24:51.040> enable<01:24:51.520> individual<01:24:52.159> people<01:24:52.679> to 01:24:52.870 --> 01:24:52.880 align:start position:0% could only enable individual people to 01:24:52.880 --> 01:24:55.229 align:start position:0% could only enable individual people to make<01:24:53.199> proofs<01:24:53.600> about<01:24:53.840> operation<01:24:54.600> on<01:24:54.760> their<01:24:54.920> own 01:24:55.229 --> 01:24:55.239 align:start position:0% make proofs about operation on their own 01:24:55.239 --> 01:24:56.870 align:start position:0% make proofs about operation on their own data<01:24:55.800> but<01:24:55.880> there<01:24:55.960> are<01:24:56.119> a<01:24:56.199> bunch<01:24:56.400> of<01:24:56.560> places 01:24:56.870 --> 01:24:56.880 align:start position:0% data but there are a bunch of places 01:24:56.880 --> 01:24:58.750 align:start position:0% data but there are a bunch of places where<01:24:57.000> we<01:24:57.119> would<01:24:57.320> want<01:24:57.679> say<01:24:57.960> two<01:24:58.239> people<01:24:58.600> or 01:24:58.750 --> 01:24:58.760 align:start position:0% where we would want say two people or 01:24:58.760 --> 01:25:00.629 align:start position:0% where we would want say two people or multiple<01:24:59.199> people<01:24:59.600> to<01:24:59.719> be<01:24:59.840> able<01:25:00.000> to<01:25:00.159> jointly 01:25:00.629 --> 01:25:00.639 align:start position:0% multiple people to be able to jointly 01:25:00.639 --> 01:25:02.709 align:start position:0% multiple people to be able to jointly compute<01:25:01.119> across<01:25:01.719> data<01:25:02.040> that<01:25:02.239> I<01:25:02.400> have<01:25:02.520> in<01:25:02.600> my 01:25:02.709 --> 01:25:02.719 align:start position:0% compute across data that I have in my 01:25:02.719 --> 01:25:04.709 align:start position:0% compute across data that I have in my zup<01:25:03.000> pass<01:25:03.159> and<01:25:03.239> you<01:25:03.360> have<01:25:03.679> in<01:25:03.800> your<01:25:03.960> zup<01:25:04.320> pass 01:25:04.709 --> 01:25:04.719 align:start position:0% zup pass and you have in your zup pass 01:25:04.719 --> 01:25:05.910 align:start position:0% zup pass and you have in your zup pass and<01:25:04.800> that<01:25:04.920> led<01:25:05.080> us<01:25:05.159> to<01:25:05.280> realize<01:25:05.520> oh<01:25:05.679> there's<01:25:05.800> a 01:25:05.910 --> 01:25:05.920 align:start position:0% and that led us to realize oh there's a 01:25:05.920 --> 01:25:07.629 align:start position:0% and that led us to realize oh there's a very<01:25:06.119> natural<01:25:06.440> connection<01:25:07.119> with<01:25:07.239> these<01:25:07.440> other 01:25:07.629 --> 01:25:07.639 align:start position:0% very natural connection with these other 01:25:07.639 --> 01:25:09.910 align:start position:0% very natural connection with these other kinds<01:25:07.880> of<01:25:08.040> general<01:25:08.480> purpose<01:25:09.159> programmable 01:25:09.910 --> 01:25:09.920 align:start position:0% kinds of general purpose programmable 01:25:09.920 --> 01:25:11.870 align:start position:0% kinds of general purpose programmable cryptography<01:25:10.639> Primitives<01:25:11.199> like<01:25:11.360> multiparty 01:25:11.870 --> 01:25:11.880 align:start position:0% cryptography Primitives like multiparty 01:25:11.880 --> 01:25:14.310 align:start position:0% cryptography Primitives like multiparty computation<01:25:12.320> and<01:25:12.560> more<01:25:13.560> another<01:25:13.800> realization 01:25:14.310 --> 01:25:14.320 align:start position:0% computation and more another realization 01:25:14.320 --> 01:25:15.950 align:start position:0% computation and more another realization that<01:25:14.440> we<01:25:14.600> had<01:25:14.840> was<01:25:15.040> that<01:25:15.400> even<01:25:15.600> though<01:25:15.719> we<01:25:15.840> had 01:25:15.950 --> 01:25:15.960 align:start position:0% that we had was that even though we had 01:25:15.960 --> 01:25:17.950 align:start position:0% that we had was that even though we had this<01:25:16.199> abstract<01:25:16.760> concept<01:25:17.080> of<01:25:17.239> proof<01:25:17.560> carrying 01:25:17.950 --> 01:25:17.960 align:start position:0% this abstract concept of proof carrying 01:25:17.960 --> 01:25:21.470 align:start position:0% this abstract concept of proof carrying data<01:25:18.760> PCD<01:25:19.760> um<01:25:20.280> it<01:25:20.400> was<01:25:20.600> actually<01:25:20.840> in<01:25:21.040> practice 01:25:21.470 --> 01:25:21.480 align:start position:0% data PCD um it was actually in practice 01:25:21.480 --> 01:25:23.709 align:start position:0% data PCD um it was actually in practice really<01:25:21.800> hard<01:25:22.000> to<01:25:22.159> use<01:25:22.520> pcds<01:25:23.320> what<01:25:23.440> we'd<01:25:23.639> have 01:25:23.709 --> 01:25:23.719 align:start position:0% really hard to use pcds what we'd have 01:25:23.719 --> 01:25:25.189 align:start position:0% really hard to use pcds what we'd have to<01:25:23.800> do<01:25:23.880> is<01:25:23.960> we'd<01:25:24.159> have<01:25:24.400> to<01:25:24.520> write<01:25:24.719> one<01:25:24.880> more 01:25:25.189 --> 01:25:25.199 align:start position:0% to do is we'd have to write one more 01:25:25.199 --> 01:25:27.229 align:start position:0% to do is we'd have to write one more bespoke<01:25:25.639> circuit<01:25:26.040> for<01:25:26.360> every<01:25:26.679> kind<01:25:26.840> of 01:25:27.229 --> 01:25:27.239 align:start position:0% bespoke circuit for every kind of 01:25:27.239 --> 01:25:29.669 align:start position:0% bespoke circuit for every kind of cryptographic<01:25:27.880> operation<01:25:28.639> or<01:25:28.880> every<01:25:29.119> kind<01:25:29.320> of 01:25:29.669 --> 01:25:29.679 align:start position:0% cryptographic operation or every kind of 01:25:29.679 --> 01:25:31.270 align:start position:0% cryptographic operation or every kind of you<01:25:29.800> know<01:25:30.000> proof<01:25:30.320> carrying<01:25:30.679> transformation 01:25:31.270 --> 01:25:31.280 align:start position:0% you know proof carrying transformation 01:25:31.280 --> 01:25:32.990 align:start position:0% you know proof carrying transformation we<01:25:31.400> wanted<01:25:31.639> to<01:25:31.800> do<01:25:32.280> and<01:25:32.360> so<01:25:32.440> we<01:25:32.560> ended<01:25:32.760> up<01:25:32.880> with 01:25:32.990 --> 01:25:33.000 align:start position:0% we wanted to do and so we ended up with 01:25:33.000 --> 01:25:34.550 align:start position:0% we wanted to do and so we ended up with this<01:25:33.159> whole<01:25:33.520> repository<01:25:34.080> of<01:25:34.199> all<01:25:34.360> these 01:25:34.550 --> 01:25:34.560 align:start position:0% this whole repository of all these 01:25:34.560 --> 01:25:37.430 align:start position:0% this whole repository of all these different<01:25:34.880> circuits<01:25:35.280> and<01:25:35.440> PCD<01:25:35.920> types<01:25:36.800> um<01:25:37.280> and 01:25:37.430 --> 01:25:37.440 align:start position:0% different circuits and PCD types um and 01:25:37.440 --> 01:25:38.870 align:start position:0% different circuits and PCD types um and we<01:25:37.560> were<01:25:37.719> back<01:25:37.840> to<01:25:38.000> kind<01:25:38.080> of<01:25:38.199> square<01:25:38.480> one<01:25:38.639> on 01:25:38.870 --> 01:25:38.880 align:start position:0% we were back to kind of square one on 01:25:38.880 --> 01:25:40.709 align:start position:0% we were back to kind of square one on well<01:25:39.000> you<01:25:39.119> do<01:25:39.280> need<01:25:39.400> a<01:25:39.560> cryptography<01:25:40.320> aware 01:25:40.709 --> 01:25:40.719 align:start position:0% well you do need a cryptography aware 01:25:40.719 --> 01:25:42.750 align:start position:0% well you do need a cryptography aware developer<01:25:41.600> uh<01:25:41.679> in<01:25:41.760> order<01:25:41.960> to<01:25:42.159> even<01:25:42.360> be<01:25:42.480> able<01:25:42.639> to 01:25:42.750 --> 01:25:42.760 align:start position:0% developer uh in order to even be able to 01:25:42.760 --> 01:25:44.390 align:start position:0% developer uh in order to even be able to engage<01:25:43.040> in<01:25:43.159> this 01:25:44.390 --> 01:25:44.400 align:start position:0% engage in this 01:25:44.400 --> 01:25:47.470 align:start position:0% engage in this ecosystem<01:25:45.400> so<01:25:45.800> that<01:25:45.960> led<01:25:46.159> us<01:25:46.320> to<01:25:46.639> programmable 01:25:47.470 --> 01:25:47.480 align:start position:0% ecosystem so that led us to programmable 01:25:47.480 --> 01:25:50.310 align:start position:0% ecosystem so that led us to programmable cryptography<01:25:48.480> um<01:25:48.880> which<01:25:49.280> is<01:25:49.679> the<01:25:49.840> subject<01:25:50.159> of 01:25:50.310 --> 01:25:50.320 align:start position:0% cryptography um which is the subject of 01:25:50.320 --> 01:25:52.709 align:start position:0% cryptography um which is the subject of this<01:25:50.480> community-led<01:25:51.119> session<01:25:51.400> here<01:25:51.560> today<01:25:52.560> um 01:25:52.709 --> 01:25:52.719 align:start position:0% this community-led session here today um 01:25:52.719 --> 01:25:54.430 align:start position:0% this community-led session here today um and<01:25:52.840> concretely<01:25:53.280> what<01:25:53.360> it<01:25:53.440> means<01:25:53.719> to<01:25:53.880> say<01:25:54.320> it 01:25:54.430 --> 01:25:54.440 align:start position:0% and concretely what it means to say it 01:25:54.440 --> 01:25:55.990 align:start position:0% and concretely what it means to say it led<01:25:54.639> us<01:25:54.760> to<01:25:54.920> the<01:25:55.080> mental<01:25:55.520> model<01:25:55.840> of 01:25:55.990 --> 01:25:56.000 align:start position:0% led us to the mental model of 01:25:56.000 --> 01:25:57.950 align:start position:0% led us to the mental model of programmable<01:25:56.520> cryptography<01:25:57.080> or<01:25:57.560> this<01:25:57.800> this 01:25:57.950 --> 01:25:57.960 align:start position:0% programmable cryptography or this this 01:25:57.960 --> 01:25:59.390 align:start position:0% programmable cryptography or this this way<01:25:58.119> of<01:25:58.320> thinking<01:25:58.639> about<01:25:58.880> programmable 01:25:59.390 --> 01:25:59.400 align:start position:0% way of thinking about programmable 01:25:59.400 --> 01:26:01.790 align:start position:0% way of thinking about programmable cryptography<01:26:00.199> is<01:26:00.320> it<01:26:00.760> allowed<01:26:01.040> us<01:26:01.159> to<01:26:01.520> figure 01:26:01.790 --> 01:26:01.800 align:start position:0% cryptography is it allowed us to figure 01:26:01.800 --> 01:26:03.590 align:start position:0% cryptography is it allowed us to figure out<01:26:02.000> what<01:26:02.280> the<01:26:02.600> problem<01:26:02.920> was<01:26:03.159> and<01:26:03.280> what<01:26:03.400> the 01:26:03.590 --> 01:26:03.600 align:start position:0% out what the problem was and what the 01:26:03.600 --> 01:26:05.189 align:start position:0% out what the problem was and what the capabilities<01:26:04.199> would<01:26:04.360> be<01:26:04.719> un<01:26:05.040> what 01:26:05.189 --> 01:26:05.199 align:start position:0% capabilities would be un what 01:26:05.199 --> 01:26:06.629 align:start position:0% capabilities would be un what capabilities<01:26:05.679> would<01:26:05.800> be<01:26:05.920> unlocked<01:26:06.400> if<01:26:06.520> we 01:26:06.629 --> 01:26:06.639 align:start position:0% capabilities would be unlocked if we 01:26:06.639 --> 01:26:09.189 align:start position:0% capabilities would be unlocked if we solved<01:26:07.080> those<01:26:07.400> problems<01:26:08.400> so<01:26:08.760> you<01:26:08.880> know<01:26:09.000> me<01:26:09.080> and 01:26:09.189 --> 01:26:09.199 align:start position:0% solved those problems so you know me and 01:26:09.199 --> 01:26:10.790 align:start position:0% solved those problems so you know me and Andrew<01:26:09.480> we<01:26:09.560> took<01:26:09.679> a<01:26:09.800> look<01:26:10.000> at<01:26:10.360> all<01:26:10.480> the<01:26:10.600> stuff 01:26:10.790 --> 01:26:10.800 align:start position:0% Andrew we took a look at all the stuff 01:26:10.800 --> 01:26:12.310 align:start position:0% Andrew we took a look at all the stuff going<01:26:10.960> on<01:26:11.080> with<01:26:11.239> pcds<01:26:11.679> and<01:26:11.800> we<01:26:11.880> were<01:26:12.040> like<01:26:12.199> well 01:26:12.310 --> 01:26:12.320 align:start position:0% going on with pcds and we were like well 01:26:12.320 --> 01:26:13.910 align:start position:0% going on with pcds and we were like well this<01:26:12.400> needs<01:26:12.560> to<01:26:12.679> become<01:26:12.920> generalizable<01:26:13.840> and 01:26:13.910 --> 01:26:13.920 align:start position:0% this needs to become generalizable and 01:26:13.920 --> 01:26:15.629 align:start position:0% this needs to become generalizable and this<01:26:14.040> needs<01:26:14.239> to<01:26:14.360> become<01:26:14.639> much<01:26:14.800> more<01:26:15.000> flexible 01:26:15.629 --> 01:26:15.639 align:start position:0% this needs to become much more flexible 01:26:15.639 --> 01:26:18.990 align:start position:0% this needs to become much more flexible so<01:26:15.840> now<01:26:15.960> we<01:26:16.080> have<01:26:16.280> pod<01:26:16.840> and<01:26:17.040> pod<01:26:17.320> 2<01:26:18.280> as<01:26:18.360> a<01:26:18.520> result 01:26:18.990 --> 01:26:19.000 align:start position:0% so now we have pod and pod 2 as a result 01:26:19.000 --> 01:26:20.149 align:start position:0% so now we have pod and pod 2 as a result which<01:26:19.119> we'll<01:26:19.280> learn<01:26:19.440> about<01:26:19.639> more<01:26:19.840> today<01:26:20.080> in 01:26:20.149 --> 01:26:20.159 align:start position:0% which we'll learn about more today in 01:26:20.159 --> 01:26:24.510 align:start position:0% which we'll learn about more today in the<01:26:20.320> afternoon<01:26:20.840> sessions<01:26:22.040> um<01:26:23.040> we<01:26:23.280> have<01:26:23.880> uh<01:26:24.440> if 01:26:24.510 --> 01:26:24.520 align:start position:0% the afternoon sessions um we have uh if 01:26:24.520 --> 01:26:26.189 align:start position:0% the afternoon sessions um we have uh if you<01:26:24.600> can<01:26:24.719> go<01:26:24.800> to<01:26:24.960> you<01:26:25.040> can<01:26:25.119> go<01:26:25.199> to<01:26:25.360> p.org<01:26:25.880> to<01:26:26.080> see 01:26:26.189 --> 01:26:26.199 align:start position:0% you can go to you can go to p.org to see 01:26:26.199 --> 01:26:29.669 align:start position:0% you can go to you can go to p.org to see sort<01:26:26.360> of<01:26:26.440> the<01:26:26.560> latest<01:26:26.840> on<01:26:27.119> that<01:26:28.239> um<01:26:29.239> and<01:26:29.360> then 01:26:29.669 --> 01:26:29.679 align:start position:0% sort of the latest on that um and then 01:26:29.679 --> 01:26:31.189 align:start position:0% sort of the latest on that um and then we<01:26:29.800> started<01:26:30.360> carrying<01:26:30.679> out<01:26:30.920> other 01:26:31.189 --> 01:26:31.199 align:start position:0% we started carrying out other 01:26:31.199 --> 01:26:33.350 align:start position:0% we started carrying out other experiments<01:26:31.719> to<01:26:31.840> see<01:26:32.199> well<01:26:32.800> now<01:26:33.040> that<01:26:33.159> we've 01:26:33.350 --> 01:26:33.360 align:start position:0% experiments to see well now that we've 01:26:33.360 --> 01:26:34.629 align:start position:0% experiments to see well now that we've been<01:26:33.480> led<01:26:33.679> to<01:26:33.840> this<01:26:34.040> next<01:26:34.280> line<01:26:34.440> of 01:26:34.629 --> 01:26:34.639 align:start position:0% been led to this next line of 01:26:34.639 --> 01:26:36.629 align:start position:0% been led to this next line of Investigation<01:26:35.400> what<01:26:35.639> what<01:26:35.920> what<01:26:36.040> might<01:26:36.280> we<01:26:36.440> do 01:26:36.629 --> 01:26:36.639 align:start position:0% Investigation what what what might we do 01:26:36.639 --> 01:26:39.030 align:start position:0% Investigation what what what might we do if<01:26:36.760> we<01:26:36.920> take<01:26:37.280> fhe<01:26:37.840> or<01:26:38.040> obfuscation<01:26:38.639> or<01:26:38.840> these 01:26:39.030 --> 01:26:39.040 align:start position:0% if we take fhe or obfuscation or these 01:26:39.040 --> 01:26:40.669 align:start position:0% if we take fhe or obfuscation or these other<01:26:39.239> Technologies<01:26:39.719> to<01:26:39.840> their<01:26:40.000> logical 01:26:40.669 --> 01:26:40.679 align:start position:0% other Technologies to their logical 01:26:40.679 --> 01:26:44.709 align:start position:0% other Technologies to their logical conclusion<01:26:41.679> so<01:26:42.639> uh<01:26:43.360> this<01:26:43.800> Devcon<01:26:44.440> if<01:26:44.520> you've 01:26:44.709 --> 01:26:44.719 align:start position:0% conclusion so uh this Devcon if you've 01:26:44.719 --> 01:26:46.030 align:start position:0% conclusion so uh this Devcon if you've gone<01:26:44.880> down<01:26:45.000> to<01:26:45.080> the<01:26:45.159> Frog<01:26:45.440> Hub<01:26:45.639> you've<01:26:45.880> might 01:26:46.030 --> 01:26:46.040 align:start position:0% gone down to the Frog Hub you've might 01:26:46.040 --> 01:26:47.149 align:start position:0% gone down to the Frog Hub you've might you<01:26:46.119> might<01:26:46.239> have<01:26:46.400> seen<01:26:46.639> this<01:26:46.760> game<01:26:46.960> called 01:26:47.149 --> 01:26:47.159 align:start position:0% you might have seen this game called 01:26:47.159 --> 01:26:49.990 align:start position:0% you might have seen this game called frog<01:26:47.560> Zone<01:26:48.560> which<01:26:48.679> is<01:26:48.880> as<01:26:49.040> far<01:26:49.159> as<01:26:49.280> we're<01:26:49.440> aware 01:26:49.990 --> 01:26:50.000 align:start position:0% frog Zone which is as far as we're aware 01:26:50.000 --> 01:26:51.790 align:start position:0% frog Zone which is as far as we're aware the<01:26:50.199> first<01:26:50.560> game<01:26:51.040> where<01:26:51.199> the<01:26:51.360> back<01:26:51.480> end<01:26:51.719> is 01:26:51.790 --> 01:26:51.800 align:start position:0% the first game where the back end is 01:26:51.800 --> 01:26:53.510 align:start position:0% the first game where the back end is running<01:26:52.159> entirely<01:26:52.600> in<01:26:52.760> fully<01:26:53.000> homomorphic 01:26:53.510 --> 01:26:53.520 align:start position:0% running entirely in fully homomorphic 01:26:53.520 --> 01:26:55.709 align:start position:0% running entirely in fully homomorphic encryption<01:26:54.280> like<01:26:54.480> Justin<01:26:54.840> mentioned<01:26:55.520> we've 01:26:55.709 --> 01:26:55.719 align:start position:0% encryption like Justin mentioned we've 01:26:55.719 --> 01:26:57.510 align:start position:0% encryption like Justin mentioned we've basically<01:26:56.080> built<01:26:56.400> this<01:26:56.600> four<01:26:57.000> player<01:26:57.320> game 01:26:57.510 --> 01:26:57.520 align:start position:0% basically built this four player game 01:26:57.520 --> 01:26:59.950 align:start position:0% basically built this four player game where<01:26:57.639> you've<01:26:57.800> got<01:26:57.960> four<01:26:58.600> uh<01:26:58.719> four<01:26:59.040> frogs<01:26:59.679> on<01:26:59.800> a 01:26:59.950 --> 01:26:59.960 align:start position:0% where you've got four uh four frogs on a 01:26:59.960 --> 01:27:02.590 align:start position:0% where you've got four uh four frogs on a 32<01:27:00.360> by<01:27:00.480> 32<01:27:00.880> grid<01:27:01.400> the<01:27:01.520> frogs<01:27:01.800> can<01:27:01.920> move<01:27:02.199> up<01:27:02.400> down 01:27:02.590 --> 01:27:02.600 align:start position:0% 32 by 32 grid the frogs can move up down 01:27:02.600 --> 01:27:04.109 align:start position:0% 32 by 32 grid the frogs can move up down left<01:27:02.760> or<01:27:02.960> right<01:27:03.239> they<01:27:03.360> can<01:27:03.520> collect<01:27:03.840> items 01:27:04.109 --> 01:27:04.119 align:start position:0% left or right they can collect items 01:27:04.119 --> 01:27:06.270 align:start position:0% left or right they can collect items slay<01:27:04.440> monsters<01:27:04.880> Etc<01:27:05.520> and<01:27:05.679> all<01:27:05.800> of<01:27:05.960> that<01:27:06.080> is 01:27:06.270 --> 01:27:06.280 align:start position:0% slay monsters Etc and all of that is 01:27:06.280 --> 01:27:07.830 align:start position:0% slay monsters Etc and all of that is happening<01:27:06.719> inside<01:27:07.000> a<01:27:07.119> fully<01:27:07.360> homomorphic 01:27:07.830 --> 01:27:07.840 align:start position:0% happening inside a fully homomorphic 01:27:07.840 --> 01:27:10.750 align:start position:0% happening inside a fully homomorphic encryption<01:27:08.520> with<01:27:08.719> 1<01:27:09.040> billion<01:27:09.440> x<01:27:09.760> overhead<01:27:10.520> on 01:27:10.750 --> 01:27:10.760 align:start position:0% encryption with 1 billion x overhead on 01:27:10.760 --> 01:27:12.830 align:start position:0% encryption with 1 billion x overhead on top<01:27:11.080> of<01:27:11.400> what<01:27:11.520> it<01:27:11.639> would<01:27:11.800> take<01:27:12.000> to<01:27:12.199> run<01:27:12.600> this 01:27:12.830 --> 01:27:12.840 align:start position:0% top of what it would take to run this 01:27:12.840 --> 01:27:14.709 align:start position:0% top of what it would take to run this kind<01:27:13.000> of<01:27:13.080> a<01:27:13.239> game<01:27:13.600> normally<01:27:14.080> on<01:27:14.239> a<01:27:14.480> you<01:27:14.600> know 01:27:14.709 --> 01:27:14.719 align:start position:0% kind of a game normally on a you know 01:27:14.719 --> 01:27:16.830 align:start position:0% kind of a game normally on a you know plain<01:27:15.000> text<01:27:15.239> ordinary<01:27:15.679> computer<01:27:16.560> and<01:27:16.679> that's 01:27:16.830 --> 01:27:16.840 align:start position:0% plain text ordinary computer and that's 01:27:16.840 --> 01:27:17.950 align:start position:0% plain text ordinary computer and that's unlocked<01:27:17.239> some<01:27:17.400> really<01:27:17.560> interesting 01:27:17.950 --> 01:27:17.960 align:start position:0% unlocked some really interesting 01:27:17.960 --> 01:27:19.430 align:start position:0% unlocked some really interesting thoughts<01:27:18.199> and<01:27:18.320> it's<01:27:18.400> sort<01:27:18.560> of<01:27:18.960> that<01:27:19.080> is<01:27:19.199> one<01:27:19.320> of 01:27:19.430 --> 01:27:19.440 align:start position:0% thoughts and it's sort of that is one of 01:27:19.440 --> 01:27:20.790 align:start position:0% thoughts and it's sort of that is one of the<01:27:19.600> thing<01:27:19.960> the<01:27:20.040> things<01:27:20.239> that's<01:27:20.440> actually<01:27:20.600> led 01:27:20.790 --> 01:27:20.800 align:start position:0% the thing the things that's actually led 01:27:20.800 --> 01:27:22.790 align:start position:0% the thing the things that's actually led us<01:27:20.920> to<01:27:21.280> obfuscation<01:27:22.280> because<01:27:22.480> one<01:27:22.600> of<01:27:22.679> the 01:27:22.790 --> 01:27:22.800 align:start position:0% us to obfuscation because one of the 01:27:22.800 --> 01:27:24.390 align:start position:0% us to obfuscation because one of the huge<01:27:23.080> pain<01:27:23.360> points<01:27:23.600> of<01:27:23.719> building<01:27:24.199> something 01:27:24.390 --> 01:27:24.400 align:start position:0% huge pain points of building something 01:27:24.400 --> 01:27:26.149 align:start position:0% huge pain points of building something like<01:27:24.520> frog<01:27:24.840> Zone<01:27:25.320> if<01:27:25.400> you've<01:27:25.639> actually<01:27:25.880> tried 01:27:26.149 --> 01:27:26.159 align:start position:0% like frog Zone if you've actually tried 01:27:26.159 --> 01:27:27.950 align:start position:0% like frog Zone if you've actually tried the<01:27:26.239> game<01:27:26.480> downstairs<01:27:27.280> is<01:27:27.400> that<01:27:27.520> there<01:27:27.639> is<01:27:27.760> a 01:27:27.950 --> 01:27:27.960 align:start position:0% the game downstairs is that there is a 01:27:27.960 --> 01:27:29.629 align:start position:0% the game downstairs is that there is a ton<01:27:28.199> of<01:27:28.400> interactivity<01:27:29.080> there's<01:27:29.239> a<01:27:29.360> ton<01:27:29.520> of 01:27:29.629 --> 01:27:29.639 align:start position:0% ton of interactivity there's a ton of 01:27:29.639 --> 01:27:31.590 align:start position:0% ton of interactivity there's a ton of multi-party<01:27:30.239> computation<01:27:30.760> decryption<01:27:31.480> that 01:27:31.590 --> 01:27:31.600 align:start position:0% multi-party computation decryption that 01:27:31.600 --> 01:27:33.590 align:start position:0% multi-party computation decryption that needs<01:27:31.800> to<01:27:31.920> happen<01:27:32.400> the<01:27:32.600> Wi-Fi<01:27:33.040> keeps<01:27:33.280> going 01:27:33.590 --> 01:27:33.600 align:start position:0% needs to happen the Wi-Fi keeps going 01:27:33.600 --> 01:27:35.590 align:start position:0% needs to happen the Wi-Fi keeps going down<01:27:33.840> going<01:27:34.040> out<01:27:34.280> downstairs<01:27:34.960> our<01:27:35.239> Hardware 01:27:35.590 --> 01:27:35.600 align:start position:0% down going out downstairs our Hardware 01:27:35.600 --> 01:27:37.990 align:start position:0% down going out downstairs our Hardware switcher<01:27:36.119> thing<01:27:36.320> keeps<01:27:36.560> failing<01:27:37.360> and<01:27:37.520> so 01:27:37.990 --> 01:27:38.000 align:start position:0% switcher thing keeps failing and so 01:27:38.000 --> 01:27:39.590 align:start position:0% switcher thing keeps failing and so there's<01:27:38.320> no<01:27:38.560> way<01:27:38.760> that<01:27:38.880> you<01:27:39.000> can<01:27:39.199> take<01:27:39.400> this 01:27:39.590 --> 01:27:39.600 align:start position:0% there's no way that you can take this 01:27:39.600 --> 01:27:40.870 align:start position:0% there's no way that you can take this technology<01:27:40.080> and<01:27:40.239> scale<01:27:40.440> it<01:27:40.560> to<01:27:40.679> something 01:27:40.870 --> 01:27:40.880 align:start position:0% technology and scale it to something 01:27:40.880 --> 01:27:42.790 align:start position:0% technology and scale it to something like<01:27:41.000> a<01:27:41.119> billion<01:27:41.520> people<01:27:42.040> unless<01:27:42.320> you<01:27:42.520> bring 01:27:42.790 --> 01:27:42.800 align:start position:0% like a billion people unless you bring 01:27:42.800 --> 01:27:46.030 align:start position:0% like a billion people unless you bring in<01:27:43.000> a<01:27:43.159> non-<01:27:43.400> interactivity<01:27:44.159> technology<01:27:45.159> like 01:27:46.030 --> 01:27:46.040 align:start position:0% in a non- interactivity technology like 01:27:46.040 --> 01:27:48.590 align:start position:0% in a non- interactivity technology like obfuscation<01:27:47.040> so<01:27:47.600> each<01:27:47.760> of<01:27:47.960> these<01:27:48.159> things<01:27:48.440> has 01:27:48.590 --> 01:27:48.600 align:start position:0% obfuscation so each of these things has 01:27:48.600 --> 01:27:51.149 align:start position:0% obfuscation so each of these things has been<01:27:49.080> essentially<01:27:49.560> some<01:27:49.800> sequence<01:27:50.400> of 01:27:51.149 --> 01:27:51.159 align:start position:0% been essentially some sequence of 01:27:51.159 --> 01:27:53.109 align:start position:0% been essentially some sequence of figuring<01:27:51.520> out<01:27:51.880> what's<01:27:52.159> really<01:27:52.480> going<01:27:52.679> on<01:27:52.880> here 01:27:53.109 --> 01:27:53.119 align:start position:0% figuring out what's really going on here 01:27:53.119 --> 01:27:55.149 align:start position:0% figuring out what's really going on here trying<01:27:53.360> to<01:27:53.600> generalize<01:27:54.480> what<01:27:54.600> we<01:27:54.719> currently 01:27:55.149 --> 01:27:55.159 align:start position:0% trying to generalize what we currently 01:27:55.159 --> 01:27:57.030 align:start position:0% trying to generalize what we currently know<01:27:55.600> and<01:27:55.760> looking<01:27:56.040> for<01:27:56.280> what<01:27:56.360> is<01:27:56.480> the<01:27:56.639> general 01:27:57.030 --> 01:27:57.040 align:start position:0% know and looking for what is the general 01:27:57.040 --> 01:27:58.590 align:start position:0% know and looking for what is the general category<01:27:57.440> of<01:27:57.560> thing<01:27:57.760> that<01:27:57.920> this<01:27:58.080> is<01:27:58.400> and<01:27:58.480> how 01:27:58.590 --> 01:27:58.600 align:start position:0% category of thing that this is and how 01:27:58.600 --> 01:28:00.870 align:start position:0% category of thing that this is and how do<01:27:58.719> we<01:27:58.920> solve<01:27:59.239> that 01:28:00.870 --> 01:28:00.880 align:start position:0% do we solve that 01:28:00.880 --> 01:28:04.709 align:start position:0% do we solve that problem<01:28:01.880> um<01:28:02.400> each<01:28:02.560> of<01:28:02.760> these<01:28:03.159> steps<01:28:03.960> in<01:28:04.199> the 01:28:04.709 --> 01:28:04.719 align:start position:0% problem um each of these steps in the 01:28:04.719 --> 01:28:06.070 align:start position:0% problem um each of these steps in the understanding<01:28:05.000> tree<01:28:05.280> for<01:28:05.560> programmable 01:28:06.070 --> 01:28:06.080 align:start position:0% understanding tree for programmable 01:28:06.080 --> 01:28:09.070 align:start position:0% understanding tree for programmable cryptography<01:28:06.679> has<01:28:06.800> taken<01:28:07.080> about<01:28:07.280> a<01:28:07.480> year<01:28:08.480> and 01:28:09.070 --> 01:28:09.080 align:start position:0% cryptography has taken about a year and 01:28:09.080 --> 01:28:10.790 align:start position:0% cryptography has taken about a year and uh<01:28:09.199> each<01:28:09.360> of<01:28:09.480> them<01:28:09.639> has<01:28:09.760> been<01:28:09.880> a<01:28:10.159> concrete<01:28:10.600> step 01:28:10.790 --> 01:28:10.800 align:start position:0% uh each of them has been a concrete step 01:28:10.800 --> 01:28:12.830 align:start position:0% uh each of them has been a concrete step towards<01:28:11.040> a<01:28:11.199> grounded<01:28:11.719> conceptual<01:28:12.239> framework 01:28:12.830 --> 01:28:12.840 align:start position:0% towards a grounded conceptual framework 01:28:12.840 --> 01:28:14.109 align:start position:0% towards a grounded conceptual framework for<01:28:13.000> how<01:28:13.119> to<01:28:13.239> think<01:28:13.400> about<01:28:13.600> programmable 01:28:14.109 --> 01:28:14.119 align:start position:0% for how to think about programmable 01:28:14.119 --> 01:28:16.750 align:start position:0% for how to think about programmable cryptography<01:28:14.880> and<01:28:15.040> what<01:28:15.199> you<01:28:15.280> can<01:28:15.480> do<01:28:15.719> with<01:28:15.840> it 01:28:16.750 --> 01:28:16.760 align:start position:0% cryptography and what you can do with it 01:28:16.760 --> 01:28:18.550 align:start position:0% cryptography and what you can do with it so<01:28:17.400> again<01:28:17.719> like<01:28:17.840> I<01:28:17.960> said<01:28:18.159> in<01:28:18.239> the<01:28:18.320> beginning 01:28:18.550 --> 01:28:18.560 align:start position:0% so again like I said in the beginning 01:28:18.560 --> 01:28:20.470 align:start position:0% so again like I said in the beginning none<01:28:18.679> of<01:28:18.760> these<01:28:18.880> are<01:28:19.199> complete<01:28:19.960> Frameworks 01:28:20.470 --> 01:28:20.480 align:start position:0% none of these are complete Frameworks 01:28:20.480 --> 01:28:22.149 align:start position:0% none of these are complete Frameworks none<01:28:20.600> of<01:28:20.719> them<01:28:20.840> are<01:28:21.159> you<01:28:21.400> the<01:28:21.480> end<01:28:21.679> all<01:28:21.840> be<01:28:22.040> all 01:28:22.149 --> 01:28:22.159 align:start position:0% none of them are you the end all be all 01:28:22.159 --> 01:28:23.270 align:start position:0% none of them are you the end all be all of<01:28:22.280> how<01:28:22.360> to<01:28:22.440> think<01:28:22.600> about<01:28:22.760> programmable 01:28:23.270 --> 01:28:23.280 align:start position:0% of how to think about programmable 01:28:23.280 --> 01:28:25.189 align:start position:0% of how to think about programmable cryptography<01:28:24.159> but<01:28:24.280> each<01:28:24.440> of<01:28:24.560> them<01:28:24.719> does<01:28:24.920> build 01:28:25.189 --> 01:28:25.199 align:start position:0% cryptography but each of them does build 01:28:25.199 --> 01:28:26.669 align:start position:0% cryptography but each of them does build on<01:28:25.360> each<01:28:25.520> other<01:28:25.800> and<01:28:26.040> and<01:28:26.119> we're<01:28:26.280> starting<01:28:26.520> to 01:28:26.669 --> 01:28:26.679 align:start position:0% on each other and and we're starting to 01:28:26.679 --> 01:28:29.350 align:start position:0% on each other and and we're starting to get<01:28:26.800> hints<01:28:27.159> that<01:28:27.560> this<01:28:27.760> might<01:28:28.040> be<01:28:28.360> a<01:28:28.840> generally 01:28:29.350 --> 01:28:29.360 align:start position:0% get hints that this might be a generally 01:28:29.360 --> 01:28:30.750 align:start position:0% get hints that this might be a generally pretty<01:28:29.600> good<01:28:29.840> way<01:28:29.960> to<01:28:30.119> think<01:28:30.320> about<01:28:30.520> what<01:28:30.639> you 01:28:30.750 --> 01:28:30.760 align:start position:0% pretty good way to think about what you 01:28:30.760 --> 01:28:32.270 align:start position:0% pretty good way to think about what you can<01:28:30.880> do<01:28:31.000> with<01:28:31.159> this<01:28:31.320> technology<01:28:32.080> you<01:28:32.159> know 01:28:32.270 --> 01:28:32.280 align:start position:0% can do with this technology you know 01:28:32.280 --> 01:28:33.910 align:start position:0% can do with this technology you know first<01:28:32.440> starting<01:28:32.719> with<01:28:32.840> zkps<01:28:33.440> let<01:28:33.560> us<01:28:33.679> build 01:28:33.910 --> 01:28:33.920 align:start position:0% first starting with zkps let us build 01:28:33.920 --> 01:28:35.229 align:start position:0% first starting with zkps let us build incomplete<01:28:34.440> information<01:28:34.880> games<01:28:35.080> and 01:28:35.229 --> 01:28:35.239 align:start position:0% incomplete information games and 01:28:35.239 --> 01:28:37.229 align:start position:0% incomplete information games and decentralized<01:28:35.840> systems<01:28:36.560> then<01:28:36.719> generalizing 01:28:37.229 --> 01:28:37.239 align:start position:0% decentralized systems then generalizing 01:28:37.239 --> 01:28:39.229 align:start position:0% decentralized systems then generalizing that<01:28:37.360> to<01:28:37.480> saying<01:28:37.719> ZK<01:28:38.040> snarks<01:28:38.360> turn<01:28:38.679> privacy 01:28:39.229 --> 01:28:39.239 align:start position:0% that to saying ZK snarks turn privacy 01:28:39.239 --> 01:28:41.310 align:start position:0% that to saying ZK snarks turn privacy math<01:28:39.600> problems<01:28:39.880> into<01:28:40.119> coding<01:28:40.520> problems<01:28:41.159> then 01:28:41.310 --> 01:28:41.320 align:start position:0% math problems into coding problems then 01:28:41.320 --> 01:28:43.109 align:start position:0% math problems into coding problems then generalizing<01:28:41.960> that<01:28:42.080> into<01:28:42.320> ZK<01:28:42.639> snarks<01:28:42.960> are 01:28:43.109 --> 01:28:43.119 align:start position:0% generalizing that into ZK snarks are 01:28:43.119 --> 01:28:45.310 align:start position:0% generalizing that into ZK snarks are about<01:28:43.360> data<01:28:43.719> interoperability<01:28:44.719> and<01:28:44.960> as<01:28:45.119> vid 01:28:45.310 --> 01:28:45.320 align:start position:0% about data interoperability and as vid 01:28:45.320 --> 01:28:47.950 align:start position:0% about data interoperability and as vid Alik<01:28:45.600> said<01:28:46.119> actually<01:28:46.400> earlier<01:28:47.320> on<01:28:47.440> a<01:28:47.600> pan 01:28:47.950 --> 01:28:47.960 align:start position:0% Alik said actually earlier on a pan 01:28:47.960 --> 01:28:49.229 align:start position:0% Alik said actually earlier on a pan panel<01:28:48.239> earlier<01:28:48.520> this<01:28:48.639> week<01:28:48.880> rather<01:28:49.040> than 01:28:49.229 --> 01:28:49.239 align:start position:0% panel earlier this week rather than 01:28:49.239 --> 01:28:50.910 align:start position:0% panel earlier this week rather than calling<01:28:49.760> them<01:28:49.920> ZK<01:28:50.239> snarks<01:28:50.560> we<01:28:50.639> might<01:28:50.800> just 01:28:50.910 --> 01:28:50.920 align:start position:0% calling them ZK snarks we might just 01:28:50.920 --> 01:28:53.390 align:start position:0% calling them ZK snarks we might just call<01:28:51.119> all<01:28:51.239> of<01:28:51.360> these<01:28:51.520> things<01:28:52.159> proofs<01:28:53.159> and<01:28:53.239> then 01:28:53.390 --> 01:28:53.400 align:start position:0% call all of these things proofs and then 01:28:53.400 --> 01:28:55.310 align:start position:0% call all of these things proofs and then finally<01:28:53.760> we<01:28:54.159> we've<01:28:54.560> you<01:28:54.679> know<01:28:54.840> come<01:28:55.000> to<01:28:55.199> this 01:28:55.310 --> 01:28:55.320 align:start position:0% finally we we've you know come to this 01:28:55.320 --> 01:28:56.629 align:start position:0% finally we we've you know come to this sort<01:28:55.480> of<01:28:55.639> model<01:28:55.920> of<01:28:56.080> programmable 01:28:56.629 --> 01:28:56.639 align:start position:0% sort of model of programmable 01:28:56.639 --> 01:28:58.629 align:start position:0% sort of model of programmable cryptography<01:28:57.440> as<01:28:57.600> this<01:28:57.800> general<01:28:58.159> purpose<01:28:58.520> way 01:28:58.629 --> 01:28:58.639 align:start position:0% cryptography as this general purpose way 01:28:58.639 --> 01:29:00.990 align:start position:0% cryptography as this general purpose way to<01:28:58.760> think<01:28:58.880> about<01:28:59.199> computation<01:29:00.159> between<01:29:00.840> a 01:29:00.990 --> 01:29:01.000 align:start position:0% to think about computation between a 01:29:01.000 --> 01:29:02.750 align:start position:0% to think about computation between a network<01:29:01.320> of 01:29:02.750 --> 01:29:02.760 align:start position:0% network of 01:29:02.760 --> 01:29:06.030 align:start position:0% network of people<01:29:03.760> okay<01:29:03.920> so<01:29:04.440> in<01:29:04.679> essence<01:29:05.679> what<01:29:05.840> we've 01:29:06.030 --> 01:29:06.040 align:start position:0% people okay so in essence what we've 01:29:06.040 --> 01:29:07.550 align:start position:0% people okay so in essence what we've been<01:29:06.199> trying<01:29:06.440> to<01:29:06.560> do<01:29:06.760> over<01:29:06.920> the<01:29:07.080> past<01:29:07.239> several 01:29:07.550 --> 01:29:07.560 align:start position:0% been trying to do over the past several 01:29:07.560 --> 01:29:10.550 align:start position:0% been trying to do over the past several years<01:29:08.080> is<01:29:08.320> build<01:29:08.719> a<01:29:08.920> machine<01:29:09.360> to<01:29:09.639> produce<01:29:10.320> this 01:29:10.550 --> 01:29:10.560 align:start position:0% years is build a machine to produce this 01:29:10.560 --> 01:29:12.310 align:start position:0% years is build a machine to produce this kind<01:29:10.719> of<01:29:11.000> thinking<01:29:11.719> and<01:29:11.880> what<01:29:12.000> is<01:29:12.119> the 01:29:12.310 --> 01:29:12.320 align:start position:0% kind of thinking and what is the 01:29:12.320 --> 01:29:14.550 align:start position:0% kind of thinking and what is the mechanism<01:29:12.880> by<01:29:13.040> which<01:29:13.320> this<01:29:13.440> machine<01:29:13.840> operates 01:29:14.550 --> 01:29:14.560 align:start position:0% mechanism by which this machine operates 01:29:14.560 --> 01:29:17.189 align:start position:0% mechanism by which this machine operates that<01:29:14.719> mechanism<01:29:15.560> is<01:29:16.159> what<01:29:16.520> I<01:29:16.840> sometimes<01:29:17.040> think 01:29:17.189 --> 01:29:17.199 align:start position:0% that mechanism is what I sometimes think 01:29:17.199 --> 01:29:20.510 align:start position:0% that mechanism is what I sometimes think about<01:29:17.480> as<01:29:18.159> contact<01:29:18.639> with<01:29:18.880> reality<01:29:19.760> right<01:29:20.119> so 01:29:20.510 --> 01:29:20.520 align:start position:0% about as contact with reality right so 01:29:20.520 --> 01:29:21.870 align:start position:0% about as contact with reality right so rather<01:29:20.760> than<01:29:20.880> sitting<01:29:21.119> in<01:29:21.199> a<01:29:21.320> room<01:29:21.600> and<01:29:21.760> and 01:29:21.870 --> 01:29:21.880 align:start position:0% rather than sitting in a room and and 01:29:21.880 --> 01:29:23.350 align:start position:0% rather than sitting in a room and and theorizing<01:29:22.360> a<01:29:22.480> bunch<01:29:22.719> about<01:29:23.000> what<01:29:23.119> might<01:29:23.280> be 01:29:23.350 --> 01:29:23.360 align:start position:0% theorizing a bunch about what might be 01:29:23.360 --> 01:29:25.189 align:start position:0% theorizing a bunch about what might be an<01:29:23.480> interesting<01:29:24.400> system<01:29:24.719> or<01:29:24.880> what<01:29:25.000> might<01:29:25.119> be 01:29:25.189 --> 01:29:25.199 align:start position:0% an interesting system or what might be 01:29:25.199 --> 01:29:26.550 align:start position:0% an interesting system or what might be an<01:29:25.320> interesting<01:29:25.639> thing<01:29:25.760> to<01:29:25.880> put<01:29:26.040> it<01:29:26.400> put 01:29:26.550 --> 01:29:26.560 align:start position:0% an interesting thing to put it put 01:29:26.560 --> 01:29:28.550 align:start position:0% an interesting thing to put it put inside<01:29:26.760> of<01:29:26.840> a<01:29:26.920> snark<01:29:27.840> you<01:29:27.960> know<01:29:28.080> we'll<01:29:28.320> sit 01:29:28.550 --> 01:29:28.560 align:start position:0% inside of a snark you know we'll sit 01:29:28.560 --> 01:29:31.109 align:start position:0% inside of a snark you know we'll sit down<01:29:29.280> and<01:29:29.719> we'll<01:29:29.920> try<01:29:30.080> to<01:29:30.400> we<01:29:30.560> we'll<01:29:30.719> build<01:29:31.000> a 01:29:31.109 --> 01:29:31.119 align:start position:0% down and we'll try to we we'll build a 01:29:31.119 --> 01:29:32.790 align:start position:0% down and we'll try to we we'll build a lot<01:29:31.239> of<01:29:31.440> stuff<01:29:31.960> we'll<01:29:32.159> take<01:29:32.320> as<01:29:32.400> much<01:29:32.560> of<01:29:32.679> that 01:29:32.790 --> 01:29:32.800 align:start position:0% lot of stuff we'll take as much of that 01:29:32.800 --> 01:29:34.430 align:start position:0% lot of stuff we'll take as much of that stuff<01:29:33.000> as<01:29:33.080> we<01:29:33.199> can<01:29:33.360> we'll<01:29:33.560> deploy<01:29:33.880> it<01:29:34.040> whenever 01:29:34.430 --> 01:29:34.440 align:start position:0% stuff as we can we'll deploy it whenever 01:29:34.440 --> 01:29:36.070 align:start position:0% stuff as we can we'll deploy it whenever possible<01:29:34.760> in<01:29:34.920> as<01:29:35.080> real<01:29:35.360> of<01:29:35.480> a<01:29:35.600> setting<01:29:35.880> as 01:29:36.070 --> 01:29:36.080 align:start position:0% possible in as real of a setting as 01:29:36.080 --> 01:29:37.870 align:start position:0% possible in as real of a setting as possible<01:29:36.800> even<01:29:37.000> if<01:29:37.119> that's<01:29:37.320> just<01:29:37.440> to<01:29:37.639> a<01:29:37.719> few 01:29:37.870 --> 01:29:37.880 align:start position:0% possible even if that's just to a few 01:29:37.880 --> 01:29:40.189 align:start position:0% possible even if that's just to a few hundred<01:29:38.119> or<01:29:38.239> a<01:29:38.320> few<01:29:38.520> thousand<01:29:38.880> users<01:29:39.760> and<01:29:39.840> then 01:29:40.189 --> 01:29:40.199 align:start position:0% hundred or a few thousand users and then 01:29:40.199 --> 01:29:41.590 align:start position:0% hundred or a few thousand users and then we'll<01:29:40.480> constantly<01:29:40.880> go<01:29:41.000> through<01:29:41.159> this<01:29:41.360> process 01:29:41.590 --> 01:29:41.600 align:start position:0% we'll constantly go through this process 01:29:41.600 --> 01:29:43.270 align:start position:0% we'll constantly go through this process of<01:29:41.760> looking<01:29:42.080> back<01:29:42.320> auditing<01:29:42.719> pruning<01:29:43.119> and 01:29:43.270 --> 01:29:43.280 align:start position:0% of looking back auditing pruning and 01:29:43.280 --> 01:29:45.149 align:start position:0% of looking back auditing pruning and synthesizing<01:29:44.080> and<01:29:44.199> trying<01:29:44.360> to<01:29:44.480> figure<01:29:44.719> out 01:29:45.149 --> 01:29:45.159 align:start position:0% synthesizing and trying to figure out 01:29:45.159 --> 01:29:46.709 align:start position:0% synthesizing and trying to figure out what<01:29:45.320> is<01:29:45.440> the<01:29:45.600> general<01:29:46.000> principle<01:29:46.400> what's<01:29:46.560> the 01:29:46.709 --> 01:29:46.719 align:start position:0% what is the general principle what's the 01:29:46.719 --> 01:29:47.990 align:start position:0% what is the general principle what's the line<01:29:46.960> that<01:29:47.080> you<01:29:47.159> can<01:29:47.280> draw<01:29:47.520> between<01:29:47.760> all<01:29:47.880> of 01:29:47.990 --> 01:29:48.000 align:start position:0% line that you can draw between all of 01:29:48.000 --> 01:29:49.470 align:start position:0% line that you can draw between all of these 01:29:49.470 --> 01:29:49.480 align:start position:0% these 01:29:49.480 --> 01:29:51.910 align:start position:0% these points<01:29:50.480> here<01:29:50.600> are<01:29:50.800> some<01:29:51.000> forms<01:29:51.440> of<01:29:51.639> what 01:29:51.910 --> 01:29:51.920 align:start position:0% points here are some forms of what 01:29:51.920 --> 01:29:53.550 align:start position:0% points here are some forms of what contact<01:29:52.320> with<01:29:52.520> reality<01:29:52.920> might<01:29:53.119> actually<01:29:53.360> look 01:29:53.550 --> 01:29:53.560 align:start position:0% contact with reality might actually look 01:29:53.560 --> 01:29:55.510 align:start position:0% contact with reality might actually look like<01:29:54.040> one<01:29:54.239> is<01:29:54.400> building<01:29:54.760> a<01:29:54.880> first<01:29:55.159> endtoend 01:29:55.510 --> 01:29:55.520 align:start position:0% like one is building a first endtoend 01:29:55.520 --> 01:29:57.950 align:start position:0% like one is building a first endtoend prototype<01:29:56.320> of<01:29:56.440> some<01:29:56.719> technology<01:29:57.639> that<01:29:57.760> we've 01:29:57.950 --> 01:29:57.960 align:start position:0% prototype of some technology that we've 01:29:57.960 --> 01:29:59.430 align:start position:0% prototype of some technology that we've never<01:29:58.159> tried<01:29:58.440> before<01:29:58.760> so<01:29:58.960> something<01:29:59.280> like 01:29:59.430 --> 01:29:59.440 align:start position:0% never tried before so something like 01:29:59.440 --> 01:30:01.430 align:start position:0% never tried before so something like frog<01:29:59.840> Zone<01:30:00.320> again<01:30:00.520> let's<01:30:00.880> let's<01:30:01.040> just<01:30:01.199> try<01:30:01.320> to 01:30:01.430 --> 01:30:01.440 align:start position:0% frog Zone again let's let's just try to 01:30:01.440 --> 01:30:02.870 align:start position:0% frog Zone again let's let's just try to put<01:30:01.560> a<01:30:01.639> server<01:30:01.920> inside<01:30:02.159> a<01:30:02.239> fully<01:30:02.440> homomorphic 01:30:02.870 --> 01:30:02.880 align:start position:0% put a server inside a fully homomorphic 01:30:02.880 --> 01:30:04.310 align:start position:0% put a server inside a fully homomorphic encryption<01:30:03.320> even<01:30:03.480> if<01:30:03.560> it's<01:30:03.679> a<01:30:03.800> billion<01:30:04.119> times 01:30:04.310 --> 01:30:04.320 align:start position:0% encryption even if it's a billion times 01:30:04.320 --> 01:30:07.070 align:start position:0% encryption even if it's a billion times slower<01:30:04.840> and<01:30:04.960> we'll<01:30:05.119> figure<01:30:05.400> something<01:30:06.080> out 01:30:07.070 --> 01:30:07.080 align:start position:0% slower and we'll figure something out 01:30:07.080 --> 01:30:09.149 align:start position:0% slower and we'll figure something out another<01:30:07.320> one<01:30:07.520> is<01:30:07.679> trying<01:30:07.960> to<01:30:08.119> build<01:30:08.440> something 01:30:09.149 --> 01:30:09.159 align:start position:0% another one is trying to build something 01:30:09.159 --> 01:30:12.750 align:start position:0% another one is trying to build something that<01:30:10.080> folks<01:30:10.520> for<01:30:10.880> whatever<01:30:11.280> reasons<01:30:11.719> will<01:30:12.199> use 01:30:12.750 --> 01:30:12.760 align:start position:0% that folks for whatever reasons will use 01:30:12.760 --> 01:30:14.790 align:start position:0% that folks for whatever reasons will use or<01:30:12.960> need<01:30:13.199> or<01:30:13.360> ideally<01:30:13.800> love<01:30:14.280> even<01:30:14.480> if<01:30:14.560> it's<01:30:14.679> a 01:30:14.790 --> 01:30:14.800 align:start position:0% or need or ideally love even if it's a 01:30:14.800 --> 01:30:16.550 align:start position:0% or need or ideally love even if it's a small<01:30:15.040> group<01:30:15.239> of<01:30:15.360> just<01:30:15.480> a<01:30:15.600> couple<01:30:15.800> of<01:30:15.960> hundred 01:30:16.550 --> 01:30:16.560 align:start position:0% small group of just a couple of hundred 01:30:16.560 --> 01:30:19.350 align:start position:0% small group of just a couple of hundred people<01:30:17.560> um<01:30:18.080> another<01:30:18.360> one<01:30:18.719> is<01:30:18.960> teaching 01:30:19.350 --> 01:30:19.360 align:start position:0% people um another one is teaching 01:30:19.360 --> 01:30:21.189 align:start position:0% people um another one is teaching developers<01:30:19.800> and<01:30:20.040> providing<01:30:20.400> them<01:30:20.679> with 01:30:21.189 --> 01:30:21.199 align:start position:0% developers and providing them with 01:30:21.199 --> 01:30:23.709 align:start position:0% developers and providing them with different<01:30:21.520> tools<01:30:21.920> or<01:30:22.080> sdks<01:30:22.760> or<01:30:22.960> abstractions 01:30:23.709 --> 01:30:23.719 align:start position:0% different tools or sdks or abstractions 01:30:23.719 --> 01:30:25.550 align:start position:0% different tools or sdks or abstractions and<01:30:24.119> if<01:30:24.239> that<01:30:24.400> actually<01:30:24.600> enables<01:30:25.000> them<01:30:25.119> to<01:30:25.320> do 01:30:25.550 --> 01:30:25.560 align:start position:0% and if that actually enables them to do 01:30:25.560 --> 01:30:27.310 align:start position:0% and if that actually enables them to do something<01:30:26.320> that<01:30:26.480> they<01:30:26.600> couldn't<01:30:26.880> do<01:30:27.080> before 01:30:27.310 --> 01:30:27.320 align:start position:0% something that they couldn't do before 01:30:27.320 --> 01:30:28.510 align:start position:0% something that they couldn't do before or<01:30:27.800> understand<01:30:28.040> something<01:30:28.280> that<01:30:28.400> they 01:30:28.510 --> 01:30:28.520 align:start position:0% or understand something that they 01:30:28.520 --> 01:30:30.350 align:start position:0% or understand something that they couldn't<01:30:28.719> do<01:30:28.880> before<01:30:29.400> maybe<01:30:29.920> maybe<01:30:30.159> even 01:30:30.350 --> 01:30:30.360 align:start position:0% couldn't do before maybe maybe even 01:30:30.360 --> 01:30:32.070 align:start position:0% couldn't do before maybe maybe even build<01:30:30.639> something<01:30:31.159> that<01:30:31.280> we<01:30:31.400> could<01:30:31.560> not<01:30:31.800> even 01:30:32.070 --> 01:30:32.080 align:start position:0% build something that we could not even 01:30:32.080 --> 01:30:34.229 align:start position:0% build something that we could not even have<01:30:32.320> anticipated<01:30:33.080> if<01:30:33.159> we<01:30:33.280> can<01:30:33.400> do<01:30:33.719> that<01:30:34.080> then 01:30:34.229 --> 01:30:34.239 align:start position:0% have anticipated if we can do that then 01:30:34.239 --> 01:30:35.590 align:start position:0% have anticipated if we can do that then we<01:30:34.400> have<01:30:34.600> some<01:30:34.800> sense<01:30:35.080> that<01:30:35.239> oh<01:30:35.400> this 01:30:35.590 --> 01:30:35.600 align:start position:0% we have some sense that oh this 01:30:35.600 --> 01:30:37.430 align:start position:0% we have some sense that oh this abstraction<01:30:36.199> is<01:30:36.400> actually<01:30:36.679> something<01:30:37.040> that 01:30:37.430 --> 01:30:37.440 align:start position:0% abstraction is actually something that 01:30:37.440 --> 01:30:39.189 align:start position:0% abstraction is actually something that makes<01:30:37.760> sense<01:30:38.159> that<01:30:38.400> is<01:30:38.639> is<01:30:38.760> maybe<01:30:39.000> worth 01:30:39.189 --> 01:30:39.199 align:start position:0% makes sense that is is maybe worth 01:30:39.199 --> 01:30:42.310 align:start position:0% makes sense that is is maybe worth refining<01:30:39.600> and<01:30:39.719> building<01:30:40.040> on<01:30:40.239> top 01:30:42.310 --> 01:30:42.320 align:start position:0% refining and building on top 01:30:42.320 --> 01:30:46.189 align:start position:0% refining and building on top of<01:30:43.320> um<01:30:43.639> by<01:30:43.800> the<01:30:43.920> way<01:30:44.400> as<01:30:45.040> uh<01:30:45.239> sort<01:30:45.440> of<01:30:45.920> you<01:30:46.040> know 01:30:46.189 --> 01:30:46.199 align:start position:0% of um by the way as uh sort of you know 01:30:46.199 --> 01:30:47.590 align:start position:0% of um by the way as uh sort of you know in<01:30:46.360> reference<01:30:46.719> to<01:30:46.960> that<01:30:47.239> that<01:30:47.400> last 01:30:47.590 --> 01:30:47.600 align:start position:0% in reference to that that last 01:30:47.600 --> 01:30:49.390 align:start position:0% in reference to that that last particular<01:30:48.040> point<01:30:48.560> I<01:30:48.639> think<01:30:48.880> that<01:30:49.000> Folks<01:30:49.239> at 01:30:49.390 --> 01:30:49.400 align:start position:0% particular point I think that Folks at 01:30:49.400 --> 01:30:51.229 align:start position:0% particular point I think that Folks at Devcon<01:30:49.880> should<01:30:50.119> think<01:30:50.400> very<01:30:50.600> hard<01:30:50.840> about<01:30:51.080> the 01:30:51.229 --> 01:30:51.239 align:start position:0% Devcon should think very hard about the 01:30:51.239 --> 01:30:53.590 align:start position:0% Devcon should think very hard about the fact<01:30:51.800> that<01:30:52.199> every<01:30:52.480> Devcon<01:30:52.920> attendee<01:30:53.280> now<01:30:53.440> has 01:30:53.590 --> 01:30:53.600 align:start position:0% fact that every Devcon attendee now has 01:30:53.600 --> 01:30:55.830 align:start position:0% fact that every Devcon attendee now has access<01:30:54.080> to<01:30:54.159> a<01:30:54.280> ZK<01:30:54.600> friendly<01:30:54.960> EDSA<01:30:55.679> and 01:30:55.830 --> 01:30:55.840 align:start position:0% access to a ZK friendly EDSA and 01:30:55.840 --> 01:30:57.750 align:start position:0% access to a ZK friendly EDSA and semaphor<01:30:56.440> key<01:30:57.080> you<01:30:57.159> know<01:30:57.320> there's<01:30:57.600> there's 01:30:57.750 --> 01:30:57.760 align:start position:0% semaphor key you know there's there's 01:30:57.760 --> 01:30:58.830 align:start position:0% semaphor key you know there's there's essentially<01:30:58.080> you<01:30:58.159> can<01:30:58.280> think<01:30:58.400> of<01:30:58.600> what<01:30:58.719> will 01:30:58.830 --> 01:30:58.840 align:start position:0% essentially you can think of what will 01:30:58.840 --> 01:31:00.030 align:start position:0% essentially you can think of what will you<01:30:58.960> do<01:30:59.080> with<01:30:59.199> the<01:30:59.280> Merkel<01:30:59.600> route<01:30:59.800> of<01:30:59.920> all 01:31:00.030 --> 01:31:00.040 align:start position:0% you do with the Merkel route of all 01:31:00.040 --> 01:31:02.070 align:start position:0% you do with the Merkel route of all Devcon<01:31:00.440> attendees<01:31:01.159> in<01:31:01.320> addition<01:31:01.679> thanks<01:31:01.960> to 01:31:02.070 --> 01:31:02.080 align:start position:0% Devcon attendees in addition thanks to 01:31:02.080 --> 01:31:04.229 align:start position:0% Devcon attendees in addition thanks to the<01:31:02.199> Frog<01:31:02.560> QR<01:31:02.920> code<01:31:03.159> scanning<01:31:03.639> thing<01:31:04.080> that's 01:31:04.229 --> 01:31:04.239 align:start position:0% the Frog QR code scanning thing that's 01:31:04.239 --> 01:31:06.189 align:start position:0% the Frog QR code scanning thing that's been<01:31:04.440> going<01:31:04.600> on<01:31:05.040> there<01:31:05.159> are<01:31:05.400> hundreds<01:31:05.960> of 01:31:06.189 --> 01:31:06.199 align:start position:0% been going on there are hundreds of 01:31:06.199 --> 01:31:08.109 align:start position:0% been going on there are hundreds of thousands<01:31:06.520> of<01:31:06.679> self-issued<01:31:07.199> attestations 01:31:08.109 --> 01:31:08.119 align:start position:0% thousands of self-issued attestations 01:31:08.119 --> 01:31:10.510 align:start position:0% thousands of self-issued attestations now<01:31:08.320> between<01:31:08.639> attendees<01:31:09.400> that<01:31:09.520> form<01:31:09.719> a<01:31:09.960> dense 01:31:10.510 --> 01:31:10.520 align:start position:0% now between attendees that form a dense 01:31:10.520 --> 01:31:12.830 align:start position:0% now between attendees that form a dense social<01:31:10.960> graph<01:31:11.679> each<01:31:11.840> of<01:31:12.000> those<01:31:12.119> frog<01:31:12.480> requests 01:31:12.830 --> 01:31:12.840 align:start position:0% social graph each of those frog requests 01:31:12.840 --> 01:31:14.669 align:start position:0% social graph each of those frog requests is<01:31:13.000> essentially<01:31:13.560> your<01:31:13.880> P<01:31:14.119> your<01:31:14.280> key<01:31:14.480> pair 01:31:14.669 --> 01:31:14.679 align:start position:0% is essentially your P your key pair 01:31:14.679 --> 01:31:17.750 align:start position:0% is essentially your P your key pair signing<01:31:15.000> someone<01:31:15.239> else's<01:31:15.840> public 01:31:17.750 --> 01:31:17.760 align:start position:0% signing someone else's public 01:31:17.760 --> 01:31:20.709 align:start position:0% signing someone else's public key<01:31:18.760> okay<01:31:19.400> so<01:31:19.960> yeah<01:31:20.080> it's<01:31:20.199> important<01:31:20.440> to<01:31:20.560> make 01:31:20.709 --> 01:31:20.719 align:start position:0% key okay so yeah it's important to make 01:31:20.719 --> 01:31:22.750 align:start position:0% key okay so yeah it's important to make a<01:31:20.800> lot<01:31:20.920> of<01:31:21.119> stuff<01:31:21.800> equally<01:31:22.159> important<01:31:22.520> is<01:31:22.639> not 01:31:22.750 --> 01:31:22.760 align:start position:0% a lot of stuff equally important is not 01:31:22.760 --> 01:31:25.990 align:start position:0% a lot of stuff equally important is not to<01:31:22.960> get<01:31:23.159> distracted<01:31:24.040> so<01:31:24.600> if<01:31:24.840> something<01:31:25.800> that 01:31:25.990 --> 01:31:26.000 align:start position:0% to get distracted so if something that 01:31:26.000 --> 01:31:27.550 align:start position:0% to get distracted so if something that we're<01:31:26.199> building<01:31:26.560> doesn't<01:31:26.920> fundamentally 01:31:27.550 --> 01:31:27.560 align:start position:0% we're building doesn't fundamentally 01:31:27.560 --> 01:31:29.470 align:start position:0% we're building doesn't fundamentally make<01:31:27.840> sense<01:31:28.360> but<01:31:28.560> has<01:31:28.679> the<01:31:28.800> potential<01:31:29.159> to<01:31:29.400> you 01:31:29.470 --> 01:31:29.480 align:start position:0% make sense but has the potential to you 01:31:29.480 --> 01:31:30.950 align:start position:0% make sense but has the potential to you know<01:31:29.600> make<01:31:29.760> a<01:31:29.840> lot<01:31:29.960> of<01:31:30.040> money<01:31:30.280> or<01:31:30.400> score<01:31:30.760> really 01:31:30.950 --> 01:31:30.960 align:start position:0% know make a lot of money or score really 01:31:30.960 --> 01:31:34.149 align:start position:0% know make a lot of money or score really highly<01:31:31.199> on<01:31:31.400> some<01:31:32.000> notion<01:31:32.639> of<01:31:33.199> model<01:31:33.760> as<01:31:34.000> of 01:31:34.149 --> 01:31:34.159 align:start position:0% highly on some notion of model as of 01:31:34.159 --> 01:31:37.270 align:start position:0% highly on some notion of model as of metrics<01:31:34.679> like<01:31:34.840> users<01:31:35.679> um<01:31:36.000> knowing<01:31:36.719> when<01:31:37.080> that 01:31:37.270 --> 01:31:37.280 align:start position:0% metrics like users um knowing when that 01:31:37.280 --> 01:31:39.109 align:start position:0% metrics like users um knowing when that is<01:31:37.480> not<01:31:37.679> the<01:31:37.840> right<01:31:38.000> track<01:31:38.239> to<01:31:38.400> keep<01:31:38.719> going 01:31:39.109 --> 01:31:39.119 align:start position:0% is not the right track to keep going 01:31:39.119 --> 01:31:41.390 align:start position:0% is not the right track to keep going down<01:31:40.119> um<01:31:40.520> another<01:31:40.800> thing<01:31:40.960> that<01:31:41.080> we<01:31:41.199> think 01:31:41.390 --> 01:31:41.400 align:start position:0% down um another thing that we think 01:31:41.400 --> 01:31:43.790 align:start position:0% down um another thing that we think about<01:31:41.800> is<01:31:42.320> if<01:31:42.440> we're<01:31:42.719> really<01:31:43.080> here<01:31:43.520> with<01:31:43.639> the 01:31:43.790 --> 01:31:43.800 align:start position:0% about is if we're really here with the 01:31:43.800 --> 01:31:46.030 align:start position:0% about is if we're really here with the goal<01:31:44.000> of<01:31:44.199> testing<01:31:44.560> out<01:31:44.719> a<01:31:44.840> new<01:31:45.000> mental<01:31:45.320> model 01:31:46.030 --> 01:31:46.040 align:start position:0% goal of testing out a new mental model 01:31:46.040 --> 01:31:48.109 align:start position:0% goal of testing out a new mental model not<01:31:46.440> compromising<01:31:47.000> on<01:31:47.159> the<01:31:47.280> mental<01:31:47.600> model<01:31:47.960> and 01:31:48.109 --> 01:31:48.119 align:start position:0% not compromising on the mental model and 01:31:48.119 --> 01:31:49.550 align:start position:0% not compromising on the mental model and getting<01:31:48.400> that<01:31:48.600> goal<01:31:48.840> mixed<01:31:49.119> up<01:31:49.400> with 01:31:49.550 --> 01:31:49.560 align:start position:0% getting that goal mixed up with 01:31:49.560 --> 01:31:51.629 align:start position:0% getting that goal mixed up with something<01:31:50.040> like<01:31:50.320> adoption<01:31:51.080> it's<01:31:51.239> better<01:31:51.480> to 01:31:51.629 --> 01:31:51.639 align:start position:0% something like adoption it's better to 01:31:51.639 --> 01:31:53.910 align:start position:0% something like adoption it's better to have<01:31:51.800> a<01:31:51.960> test<01:31:52.320> with<01:31:52.679> a<01:31:52.840> thousand<01:31:53.239> people<01:31:53.520> that 01:31:53.910 --> 01:31:53.920 align:start position:0% have a test with a thousand people that 01:31:53.920 --> 01:31:55.270 align:start position:0% have a test with a thousand people that test<01:31:54.199> the<01:31:54.320> right<01:31:54.520> kind<01:31:54.679> of<01:31:54.800> framework<01:31:55.159> or 01:31:55.270 --> 01:31:55.280 align:start position:0% test the right kind of framework or 01:31:55.280 --> 01:31:57.510 align:start position:0% test the right kind of framework or mental<01:31:55.600> or<01:31:55.719> mental<01:31:56.040> model<01:31:56.560> than<01:31:56.719> to<01:31:56.880> scale<01:31:57.239> to 01:31:57.510 --> 01:31:57.520 align:start position:0% mental or mental model than to scale to 01:31:57.520 --> 01:32:00.750 align:start position:0% mental or mental model than to scale to you<01:31:57.639> know<01:31:58.000> 10,000<01:31:58.719> or<01:31:59.040> 100,000<01:31:59.639> in<01:31:59.719> a<01:31:59.920> way<01:32:00.239> that 01:32:00.750 --> 01:32:00.760 align:start position:0% you know 10,000 or 100,000 in a way that 01:32:00.760 --> 01:32:02.030 align:start position:0% you know 10,000 or 100,000 in a way that is<01:32:00.920> testing<01:32:01.239> a<01:32:01.360> different<01:32:01.600> thing<01:32:01.800> now<01:32:01.960> the 01:32:02.030 --> 01:32:02.040 align:start position:0% is testing a different thing now the 01:32:02.040 --> 01:32:03.270 align:start position:0% is testing a different thing now the ideal<01:32:02.280> thing<01:32:02.400> would<01:32:02.520> be<01:32:02.600> to<01:32:02.800> you<01:32:02.880> know<01:32:03.040> test 01:32:03.270 --> 01:32:03.280 align:start position:0% ideal thing would be to you know test 01:32:03.280 --> 01:32:04.510 align:start position:0% ideal thing would be to you know test with<01:32:03.400> a<01:32:03.520> 100,00<01:32:04.000> people<01:32:04.199> with<01:32:04.280> the<01:32:04.400> right 01:32:04.510 --> 01:32:04.520 align:start position:0% with a 100,00 people with the right 01:32:04.520 --> 01:32:06.189 align:start position:0% with a 100,00 people with the right mental<01:32:04.800> model<01:32:05.400> but<01:32:05.760> that's<01:32:05.920> what<01:32:06.040> we're 01:32:06.189 --> 01:32:06.199 align:start position:0% mental model but that's what we're 01:32:06.199 --> 01:32:08.709 align:start position:0% mental model but that's what we're working<01:32:06.440> towards<01:32:06.679> trying<01:32:06.840> to<01:32:06.960> scale<01:32:07.560> up<01:32:08.560> um 01:32:08.709 --> 01:32:08.719 align:start position:0% working towards trying to scale up um 01:32:08.719 --> 01:32:09.870 align:start position:0% working towards trying to scale up um and<01:32:08.840> yeah<01:32:09.000> the<01:32:09.080> last<01:32:09.239> one<01:32:09.360> is<01:32:09.440> being<01:32:09.600> willing 01:32:09.870 --> 01:32:09.880 align:start position:0% and yeah the last one is being willing 01:32:09.880 --> 01:32:11.709 align:start position:0% and yeah the last one is being willing to<01:32:10.040> constantly<01:32:10.400> reassess<01:32:10.880> resynthesize<01:32:11.520> and 01:32:11.709 --> 01:32:11.719 align:start position:0% to constantly reassess resynthesize and 01:32:11.719 --> 01:32:13.669 align:start position:0% to constantly reassess resynthesize and move<01:32:12.000> on<01:32:12.280> from<01:32:12.560> things<01:32:13.119> that<01:32:13.239> don't<01:32:13.480> make 01:32:13.669 --> 01:32:13.679 align:start position:0% move on from things that don't make 01:32:13.679 --> 01:32:14.950 align:start position:0% move on from things that don't make sense<01:32:13.880> or<01:32:14.000> aren't<01:32:14.239> working<01:32:14.480> so<01:32:14.639> we've<01:32:14.800> had 01:32:14.950 --> 01:32:14.960 align:start position:0% sense or aren't working so we've had 01:32:14.960 --> 01:32:16.550 align:start position:0% sense or aren't working so we've had plenty<01:32:15.159> of<01:32:15.280> false<01:32:15.560> starts<01:32:16.040> in<01:32:16.119> terms<01:32:16.360> of<01:32:16.480> how 01:32:16.550 --> 01:32:16.560 align:start position:0% plenty of false starts in terms of how 01:32:16.560 --> 01:32:18.030 align:start position:0% plenty of false starts in terms of how to<01:32:16.719> think<01:32:16.920> about<01:32:17.400> what<01:32:17.520> you<01:32:17.600> can<01:32:17.760> do<01:32:17.920> with 01:32:18.030 --> 01:32:18.040 align:start position:0% to think about what you can do with 01:32:18.040 --> 01:32:19.669 align:start position:0% to think about what you can do with programmable 01:32:19.669 --> 01:32:19.679 align:start position:0% programmable 01:32:19.679 --> 01:32:22.669 align:start position:0% programmable cryptography<01:32:20.679> okay<01:32:20.840> so<01:32:21.080> with<01:32:21.280> that<01:32:21.719> um<01:32:22.440> I<01:32:22.560> want 01:32:22.669 --> 01:32:22.679 align:start position:0% cryptography okay so with that um I want 01:32:22.679 --> 01:32:25.790 align:start position:0% cryptography okay so with that um I want to<01:32:22.920> talk<01:32:23.119> about<01:32:23.400> a<01:32:23.560> couple<01:32:24.280> of<01:32:24.760> new<01:32:25.520> mental 01:32:25.790 --> 01:32:25.800 align:start position:0% to talk about a couple of new mental 01:32:25.800 --> 01:32:27.950 align:start position:0% to talk about a couple of new mental models<01:32:26.080> or<01:32:26.199> Frameworks<01:32:26.880> that<01:32:27.159> have<01:32:27.679> uh<01:32:27.800> come 01:32:27.950 --> 01:32:27.960 align:start position:0% models or Frameworks that have uh come 01:32:27.960 --> 01:32:29.310 align:start position:0% models or Frameworks that have uh come up<01:32:28.159> even<01:32:28.360> just<01:32:28.560> through<01:32:28.760> discussions<01:32:29.159> over 01:32:29.310 --> 01:32:29.320 align:start position:0% up even just through discussions over 01:32:29.320 --> 01:32:31.709 align:start position:0% up even just through discussions over the<01:32:29.440> last<01:32:29.639> week<01:32:29.840> with<01:32:30.000> Folks<01:32:30.239> at<01:32:30.360> Devcon<01:32:31.360> um<01:32:31.520> so 01:32:31.709 --> 01:32:31.719 align:start position:0% the last week with Folks at Devcon um so 01:32:31.719 --> 01:32:33.149 align:start position:0% the last week with Folks at Devcon um so one<01:32:32.000> is<01:32:32.280> again<01:32:32.520> this<01:32:32.639> idea<01:32:32.920> that 01:32:33.149 --> 01:32:33.159 align:start position:0% one is again this idea that 01:32:33.159 --> 01:32:35.550 align:start position:0% one is again this idea that interactivity<01:32:33.960> really<01:32:34.280> kills<01:32:35.159> this<01:32:35.280> is 01:32:35.550 --> 01:32:35.560 align:start position:0% interactivity really kills this is 01:32:35.560 --> 01:32:37.070 align:start position:0% interactivity really kills this is another<01:32:35.800> one<01:32:35.920> of<01:32:36.040> those<01:32:36.199> motivations<01:32:36.679> for 01:32:37.070 --> 01:32:37.080 align:start position:0% another one of those motivations for 01:32:37.080 --> 01:32:38.870 align:start position:0% another one of those motivations for obfuscation<01:32:38.080> like<01:32:38.199> I<01:32:38.320> mentioned<01:32:38.600> we've<01:32:38.760> been 01:32:38.870 --> 01:32:38.880 align:start position:0% obfuscation like I mentioned we've been 01:32:38.880 --> 01:32:40.750 align:start position:0% obfuscation like I mentioned we've been running<01:32:39.239> this<01:32:39.360> frog<01:32:39.679> zone<01:32:40.040> game<01:32:40.440> in<01:32:40.639> the 01:32:40.750 --> 01:32:40.760 align:start position:0% running this frog zone game in the 01:32:40.760 --> 01:32:42.669 align:start position:0% running this frog zone game in the basement<01:32:41.080> of<01:32:41.199> Devcon<01:32:41.880> four<01:32:42.159> players<01:32:42.400> can<01:32:42.560> get 01:32:42.669 --> 01:32:42.679 align:start position:0% basement of Devcon four players can get 01:32:42.679 --> 01:32:44.990 align:start position:0% basement of Devcon four players can get around<01:32:42.960> and<01:32:43.239> you<01:32:43.360> know<01:32:43.560> it's<01:32:43.760> just<01:32:43.880> a<01:32:44.119> real 01:32:44.990 --> 01:32:45.000 align:start position:0% around and you know it's just a real 01:32:45.000 --> 01:32:47.109 align:start position:0% around and you know it's just a real difficult<01:32:45.360> problem<01:32:46.000> to<01:32:46.199> get<01:32:46.480> all<01:32:46.639> four<01:32:46.880> of<01:32:47.000> the 01:32:47.109 --> 01:32:47.119 align:start position:0% difficult problem to get all four of the 01:32:47.119 --> 01:32:49.669 align:start position:0% difficult problem to get all four of the clients<01:32:47.880> doing<01:32:48.360> the<01:32:48.560> decryption<01:32:49.119> multiparty 01:32:49.669 --> 01:32:49.679 align:start position:0% clients doing the decryption multiparty 01:32:49.679 --> 01:32:51.310 align:start position:0% clients doing the decryption multiparty computation<01:32:50.239> with<01:32:50.400> every<01:32:50.639> single<01:32:50.960> operation 01:32:51.310 --> 01:32:51.320 align:start position:0% computation with every single operation 01:32:51.320 --> 01:32:52.950 align:start position:0% computation with every single operation in<01:32:51.440> the<01:32:51.600> game<01:32:52.080> now<01:32:52.239> when<01:32:52.360> we<01:32:52.480> think<01:32:52.679> about 01:32:52.950 --> 01:32:52.960 align:start position:0% in the game now when we think about 01:32:52.960 --> 01:32:54.470 align:start position:0% in the game now when we think about something<01:32:53.239> like<01:32:53.400> interact<01:32:53.880> activity<01:32:54.199> versus 01:32:54.470 --> 01:32:54.480 align:start position:0% something like interact activity versus 01:32:54.480 --> 01:32:56.149 align:start position:0% something like interact activity versus non-<01:32:54.679> interactivity<01:32:55.639> that's<01:32:55.800> something<01:32:56.040> that 01:32:56.149 --> 01:32:56.159 align:start position:0% non- interactivity that's something that 01:32:56.159 --> 01:32:58.669 align:start position:0% non- interactivity that's something that doesn't<01:32:56.600> sound<01:32:56.960> as<01:32:57.159> sexy<01:32:57.600> as<01:32:57.800> like<01:32:58.320> now<01:32:58.480> I<01:32:58.560> can 01:32:58.669 --> 01:32:58.679 align:start position:0% doesn't sound as sexy as like now I can 01:32:58.679 --> 01:33:00.629 align:start position:0% doesn't sound as sexy as like now I can do<01:32:58.920> arbitrary<01:32:59.360> programs<01:32:59.679> on<01:32:59.840> encrypted<01:33:00.239> state 01:33:00.629 --> 01:33:00.639 align:start position:0% do arbitrary programs on encrypted state 01:33:00.639 --> 01:33:03.149 align:start position:0% do arbitrary programs on encrypted state but<01:33:00.760> it<01:33:00.880> just<01:33:01.000> turns<01:33:01.280> out<01:33:01.560> that<01:33:01.960> for<01:33:02.560> scaling 01:33:03.149 --> 01:33:03.159 align:start position:0% but it just turns out that for scaling 01:33:03.159 --> 01:33:05.270 align:start position:0% but it just turns out that for scaling these<01:33:03.400> systems<01:33:04.000> to<01:33:04.400> millions<01:33:04.800> or<01:33:04.920> potentially 01:33:05.270 --> 01:33:05.280 align:start position:0% these systems to millions or potentially 01:33:05.280 --> 01:33:08.350 align:start position:0% these systems to millions or potentially even<01:33:05.480> billions<01:33:05.840> of<01:33:06.080> people<01:33:07.080> um<01:33:07.480> you<01:33:07.679> need<01:33:08.040> some 01:33:08.350 --> 01:33:08.360 align:start position:0% even billions of people um you need some 01:33:08.360 --> 01:33:09.790 align:start position:0% even billions of people um you need some strategy<01:33:08.760> for<01:33:09.000> actually<01:33:09.239> dealing<01:33:09.520> with<01:33:09.639> the 01:33:09.790 --> 01:33:09.800 align:start position:0% strategy for actually dealing with the 01:33:09.800 --> 01:33:11.270 align:start position:0% strategy for actually dealing with the fact<01:33:09.960> that<01:33:10.119> only<01:33:10.320> the<01:33:10.440> people<01:33:10.679> involved<01:33:11.040> in<01:33:11.119> a 01:33:11.270 --> 01:33:11.280 align:start position:0% fact that only the people involved in a 01:33:11.280 --> 01:33:13.830 align:start position:0% fact that only the people involved in a computation<01:33:11.960> should<01:33:12.199> need<01:33:12.400> to<01:33:12.560> be<01:33:12.920> involved 01:33:13.830 --> 01:33:13.840 align:start position:0% computation should need to be involved 01:33:13.840 --> 01:33:16.070 align:start position:0% computation should need to be involved in<01:33:14.199> the<01:33:14.360> actual<01:33:14.639> process<01:33:14.880> of<01:33:15.000> running<01:33:15.239> the 01:33:16.070 --> 01:33:16.080 align:start position:0% in the actual process of running the 01:33:16.080 --> 01:33:17.950 align:start position:0% in the actual process of running the computation<01:33:17.080> and<01:33:17.440> an<01:33:17.560> interesting 01:33:17.950 --> 01:33:17.960 align:start position:0% computation and an interesting 01:33:17.960 --> 01:33:19.229 align:start position:0% computation and an interesting connection<01:33:18.280> that<01:33:18.440> actually<01:33:18.600> someone<01:33:18.840> made<01:33:19.080> at 01:33:19.229 --> 01:33:19.239 align:start position:0% connection that actually someone made at 01:33:19.239 --> 01:33:21.709 align:start position:0% connection that actually someone made at at<01:33:19.360> a<01:33:19.600> mpf<01:33:20.320> panel<01:33:20.560> yesterday<01:33:20.960> was<01:33:21.280> wait<01:33:21.480> maybe 01:33:21.709 --> 01:33:21.719 align:start position:0% at a mpf panel yesterday was wait maybe 01:33:21.719 --> 01:33:23.270 align:start position:0% at a mpf panel yesterday was wait maybe this<01:33:21.840> is<01:33:22.040> actually<01:33:22.480> one<01:33:22.600> of<01:33:22.679> the<01:33:22.840> reasons<01:33:23.119> why 01:33:23.270 --> 01:33:23.280 align:start position:0% this is actually one of the reasons why 01:33:23.280 --> 01:33:25.430 align:start position:0% this is actually one of the reasons why ZK<01:33:23.880> have<01:33:24.000> been<01:33:24.159> such<01:33:24.320> a<01:33:24.520> powerful<01:33:25.000> technology 01:33:25.430 --> 01:33:25.440 align:start position:0% ZK have been such a powerful technology 01:33:25.440 --> 01:33:27.189 align:start position:0% ZK have been such a powerful technology that's<01:33:25.600> been<01:33:25.760> so<01:33:26.000> accelerated<01:33:26.760> compared<01:33:27.080> to 01:33:27.189 --> 01:33:27.199 align:start position:0% that's been so accelerated compared to 01:33:27.199 --> 01:33:29.629 align:start position:0% that's been so accelerated compared to FHA<01:33:27.679> over<01:33:27.800> the<01:33:27.960> last<01:33:28.159> years<01:33:28.679> especially<01:33:29.040> with 01:33:29.629 --> 01:33:29.639 align:start position:0% FHA over the last years especially with 01:33:29.639 --> 01:33:31.430 align:start position:0% FHA over the last years especially with respect<01:33:29.920> to<01:33:30.080> blockchains<01:33:30.760> we've<01:33:31.040> actually 01:33:31.430 --> 01:33:31.440 align:start position:0% respect to blockchains we've actually 01:33:31.440 --> 01:33:32.950 align:start position:0% respect to blockchains we've actually had<01:33:31.760> general<01:33:32.119> purpose<01:33:32.400> zero<01:33:32.639> knowledge 01:33:32.950 --> 01:33:32.960 align:start position:0% had general purpose zero knowledge 01:33:32.960 --> 01:33:35.590 align:start position:0% had general purpose zero knowledge proofs<01:33:33.440> for<01:33:33.600> a<01:33:33.760> long<01:33:34.040> time<01:33:34.320> now<01:33:34.719> ZK<01:33:35.119> snarks<01:33:35.520> one 01:33:35.590 --> 01:33:35.600 align:start position:0% proofs for a long time now ZK snarks one 01:33:35.600 --> 01:33:36.870 align:start position:0% proofs for a long time now ZK snarks one of<01:33:35.679> the<01:33:35.800> additional<01:33:36.159> things<01:33:36.360> is<01:33:36.480> that<01:33:36.600> they're 01:33:36.870 --> 01:33:36.880 align:start position:0% of the additional things is that they're 01:33:36.880 --> 01:33:39.030 align:start position:0% of the additional things is that they're non-interactive<01:33:37.880> you<01:33:38.000> can<01:33:38.119> make<01:33:38.239> a<01:33:38.440> one-hot 01:33:39.030 --> 01:33:39.040 align:start position:0% non-interactive you can make a one-hot 01:33:39.040 --> 01:33:41.270 align:start position:0% non-interactive you can make a one-hot publicly<01:33:39.400> verifiable<01:33:40.119> proof<01:33:40.719> and<01:33:40.920> this<01:33:41.040> is<01:33:41.159> a 01:33:41.270 --> 01:33:41.280 align:start position:0% publicly verifiable proof and this is a 01:33:41.280 --> 01:33:43.109 align:start position:0% publicly verifiable proof and this is a thing<01:33:41.440> that's<01:33:41.679> actually<01:33:41.960> unlocked<01:33:42.600> a<01:33:42.800> ton<01:33:43.000> of 01:33:43.109 --> 01:33:43.119 align:start position:0% thing that's actually unlocked a ton of 01:33:43.119 --> 01:33:45.149 align:start position:0% thing that's actually unlocked a ton of use<01:33:43.440> cases<01:33:43.639> and<01:33:43.760> a<01:33:43.880> ton<01:33:44.040> of<01:33:44.199> actual<01:33:44.719> you<01:33:44.840> know 01:33:45.149 --> 01:33:45.159 align:start position:0% use cases and a ton of actual you know 01:33:45.159 --> 01:33:48.310 align:start position:0% use cases and a ton of actual you know in<01:33:45.360> the<01:33:45.520> real<01:33:45.800> world<01:33:46.400> developer 01:33:48.310 --> 01:33:48.320 align:start position:0% in the real world developer 01:33:48.320 --> 01:33:50.470 align:start position:0% in the real world developer activity<01:33:49.320> um<01:33:49.600> another<01:33:49.880> one<01:33:50.040> that<01:33:50.159> I<01:33:50.280> think 01:33:50.470 --> 01:33:50.480 align:start position:0% activity um another one that I think 01:33:50.480 --> 01:33:51.910 align:start position:0% activity um another one that I think about<01:33:51.040> um<01:33:51.159> and<01:33:51.239> I<01:33:51.320> know<01:33:51.440> I'm<01:33:51.520> running<01:33:51.719> out<01:33:51.800> of 01:33:51.910 --> 01:33:51.920 align:start position:0% about um and I know I'm running out of 01:33:51.920 --> 01:33:53.870 align:start position:0% about um and I know I'm running out of time<01:33:52.080> I<01:33:52.199> just<01:33:52.360> have<01:33:52.960> I<01:33:53.040> have<01:33:53.199> two<01:33:53.320> more<01:33:53.480> of 01:33:53.870 --> 01:33:53.880 align:start position:0% time I just have I have two more of 01:33:53.880 --> 01:33:56.070 align:start position:0% time I just have I have two more of these<01:33:54.360> um<01:33:54.760> what<01:33:55.000> is<01:33:55.119> this<01:33:55.280> idea<01:33:55.480> of<01:33:55.639> global 01:33:56.070 --> 01:33:56.080 align:start position:0% these um what is this idea of global 01:33:56.080 --> 01:33:58.750 align:start position:0% these um what is this idea of global private<01:33:56.560> state<01:33:57.400> so<01:33:57.719> we've<01:33:57.920> noticed<01:33:58.360> that<01:33:58.600> with 01:33:58.750 --> 01:33:58.760 align:start position:0% private state so we've noticed that with 01:33:58.760 --> 01:34:01.149 align:start position:0% private state so we've noticed that with things<01:33:59.040> like<01:33:59.199> fhe<01:33:59.639> or<01:33:59.760> MPC<01:34:00.560> you<01:34:00.679> can<01:34:00.880> build 01:34:01.149 --> 01:34:01.159 align:start position:0% things like fhe or MPC you can build 01:34:01.159 --> 01:34:03.189 align:start position:0% things like fhe or MPC you can build these<01:34:01.320> decentralized<01:34:02.040> applications<01:34:03.000> that 01:34:03.189 --> 01:34:03.199 align:start position:0% these decentralized applications that 01:34:03.199 --> 01:34:05.070 align:start position:0% these decentralized applications that have<01:34:03.480> state<01:34:04.199> you<01:34:04.320> know<01:34:04.480> imagine<01:34:04.800> like<01:34:04.920> a 01:34:05.070 --> 01:34:05.080 align:start position:0% have state you know imagine like a 01:34:05.080 --> 01:34:06.910 align:start position:0% have state you know imagine like a variable<01:34:05.520> or<01:34:05.639> a<01:34:05.760> location<01:34:06.159> of<01:34:06.320> a<01:34:06.440> monster<01:34:06.800> or 01:34:06.910 --> 01:34:06.920 align:start position:0% variable or a location of a monster or 01:34:06.920 --> 01:34:08.750 align:start position:0% variable or a location of a monster or something<01:34:07.400> where<01:34:07.600> none<01:34:07.800> of<01:34:07.960> the<01:34:08.119> participants 01:34:08.750 --> 01:34:08.760 align:start position:0% something where none of the participants 01:34:08.760 --> 01:34:10.669 align:start position:0% something where none of the participants in<01:34:08.880> the<01:34:09.040> application<01:34:09.560> actually<01:34:09.960> know<01:34:10.400> that 01:34:10.669 --> 01:34:10.679 align:start position:0% in the application actually know that 01:34:10.679 --> 01:34:12.830 align:start position:0% in the application actually know that state<01:34:11.280> but<01:34:11.360> the<01:34:11.480> state<01:34:11.679> is<01:34:11.760> being<01:34:12.000> computed<01:34:12.400> on 01:34:12.830 --> 01:34:12.840 align:start position:0% state but the state is being computed on 01:34:12.840 --> 01:34:15.390 align:start position:0% state but the state is being computed on correctly<01:34:13.840> so<01:34:14.159> in<01:34:14.280> frog<01:34:14.719> Zone<01:34:15.080> there's 01:34:15.390 --> 01:34:15.400 align:start position:0% correctly so in frog Zone there's 01:34:15.400 --> 01:34:18.550 align:start position:0% correctly so in frog Zone there's monsters<01:34:16.040> around<01:34:16.280> the<01:34:16.440> map<01:34:17.040> that<01:34:17.400> move<01:34:17.800> around 01:34:18.550 --> 01:34:18.560 align:start position:0% monsters around the map that move around 01:34:18.560 --> 01:34:21.629 align:start position:0% monsters around the map that move around but<01:34:18.840> nobody<01:34:19.560> knows<01:34:20.560> where<01:34:20.760> they're<01:34:20.960> moving<01:34:21.320> to 01:34:21.629 --> 01:34:21.639 align:start position:0% but nobody knows where they're moving to 01:34:21.639 --> 01:34:24.070 align:start position:0% but nobody knows where they're moving to or<01:34:21.960> from<01:34:22.679> the<01:34:22.840> servers<01:34:23.280> and<01:34:23.400> the<01:34:23.719> maches<01:34:23.920> are 01:34:24.070 --> 01:34:24.080 align:start position:0% or from the servers and the maches are 01:34:24.080 --> 01:34:25.070 align:start position:0% or from the servers and the maches are just<01:34:24.159> sort<01:34:24.280> of<01:34:24.400> executing<01:34:24.760> in<01:34:24.880> fully 01:34:25.070 --> 01:34:25.080 align:start position:0% just sort of executing in fully 01:34:25.080 --> 01:34:26.990 align:start position:0% just sort of executing in fully homomorphic<01:34:25.600> encryption<01:34:26.320> advancing<01:34:26.840> the 01:34:26.990 --> 01:34:27.000 align:start position:0% homomorphic encryption advancing the 01:34:27.000 --> 01:34:29.109 align:start position:0% homomorphic encryption advancing the state<01:34:27.280> of<01:34:27.400> the<01:34:27.520> game<01:34:27.800> one<01:34:28.000> step<01:34:28.239> at<01:34:28.320> a<01:34:28.480> time<01:34:29.000> and 01:34:29.109 --> 01:34:29.119 align:start position:0% state of the game one step at a time and 01:34:29.119 --> 01:34:30.830 align:start position:0% state of the game one step at a time and the<01:34:29.320> bat<01:34:29.600> is<01:34:29.719> just<01:34:29.840> sort<01:34:29.960> of<01:34:30.119> its<01:34:30.280> own<01:34:30.639> like 01:34:30.830 --> 01:34:30.840 align:start position:0% the bat is just sort of its own like 01:34:30.840 --> 01:34:33.310 align:start position:0% the bat is just sort of its own like autonomous<01:34:31.760> agent<01:34:32.600> that's<01:34:32.960> that's<01:34:33.159> just 01:34:33.310 --> 01:34:33.320 align:start position:0% autonomous agent that's that's just 01:34:33.320 --> 01:34:35.350 align:start position:0% autonomous agent that's that's just moving<01:34:33.719> around<01:34:34.600> you<01:34:34.719> know<01:34:34.840> so<01:34:35.000> one<01:34:35.159> question 01:34:35.350 --> 01:34:35.360 align:start position:0% moving around you know so one question 01:34:35.360 --> 01:34:37.590 align:start position:0% moving around you know so one question is<01:34:35.560> like<01:34:36.360> you<01:34:36.480> know<01:34:36.639> I<01:34:36.760> I<01:34:36.880> had<01:34:36.960> a<01:34:37.119> moment<01:34:37.480> when 01:34:37.590 --> 01:34:37.600 align:start position:0% is like you know I I had a moment when 01:34:37.600 --> 01:34:39.430 align:start position:0% is like you know I I had a moment when we<01:34:37.760> got<01:34:38.000> the<01:34:38.159> bat<01:34:38.480> moving<01:34:38.800> around<01:34:39.040> on<01:34:39.159> its<01:34:39.280> own 01:34:39.430 --> 01:34:39.440 align:start position:0% we got the bat moving around on its own 01:34:39.440 --> 01:34:40.709 align:start position:0% we got the bat moving around on its own working<01:34:39.760> where<01:34:39.840> I<01:34:39.920> was<01:34:40.040> like<01:34:40.280> wait<01:34:40.400> a<01:34:40.480> second 01:34:40.709 --> 01:34:40.719 align:start position:0% working where I was like wait a second 01:34:40.719 --> 01:34:42.629 align:start position:0% working where I was like wait a second like<01:34:40.880> what<01:34:40.960> is<01:34:41.080> the<01:34:41.280> subjective<01:34:41.920> experience 01:34:42.629 --> 01:34:42.639 align:start position:0% like what is the subjective experience 01:34:42.639 --> 01:34:45.470 align:start position:0% like what is the subjective experience of<01:34:42.840> this<01:34:43.080> bat<01:34:43.440> like<01:34:43.719> is<01:34:43.840> this<01:34:43.960> a<01:34:44.199> new<01:34:44.679> kind<01:34:45.119> of 01:34:45.470 --> 01:34:45.480 align:start position:0% of this bat like is this a new kind of 01:34:45.480 --> 01:34:47.790 align:start position:0% of this bat like is this a new kind of agent<01:34:46.320> it's<01:34:46.520> somehow<01:34:46.880> moving<01:34:47.239> around<01:34:47.600> in 01:34:47.790 --> 01:34:47.800 align:start position:0% agent it's somehow moving around in 01:34:47.800 --> 01:34:50.149 align:start position:0% agent it's somehow moving around in encryption<01:34:48.560> there's<01:34:48.800> literally<01:34:49.280> no<01:34:49.639> single 01:34:50.149 --> 01:34:50.159 align:start position:0% encryption there's literally no single 01:34:50.159 --> 01:34:53.350 align:start position:0% encryption there's literally no single computer<01:34:50.920> or<01:34:51.239> person<01:34:52.000> or<01:34:52.639> program<01:34:53.119> in<01:34:53.239> the 01:34:53.350 --> 01:34:53.360 align:start position:0% computer or person or program in the 01:34:53.360 --> 01:34:54.510 align:start position:0% computer or person or program in the world 01:34:54.510 --> 01:34:54.520 align:start position:0% world 01:34:54.520 --> 01:34:56.950 align:start position:0% world that<01:34:55.520> knows<01:34:55.840> where<01:34:56.000> the<01:34:56.159> bat<01:34:56.360> is<01:34:56.480> or<01:34:56.639> knows 01:34:56.950 --> 01:34:56.960 align:start position:0% that knows where the bat is or knows 01:34:56.960 --> 01:34:58.390 align:start position:0% that knows where the bat is or knows anything<01:34:57.320> about<01:34:57.520> what<01:34:57.639> it's<01:34:57.760> doing<01:34:58.000> and<01:34:58.159> yet 01:34:58.390 --> 01:34:58.400 align:start position:0% anything about what it's doing and yet 01:34:58.400 --> 01:34:59.990 align:start position:0% anything about what it's doing and yet it<01:34:58.520> somehow<01:34:58.880> has<01:34:59.080> this<01:34:59.239> like<01:34:59.440> independent 01:34:59.990 --> 01:35:00.000 align:start position:0% it somehow has this like independent 01:35:00.000 --> 01:35:01.669 align:start position:0% it somehow has this like independent objective<01:35:00.520> experience<01:35:01.159> where<01:35:01.239> it's<01:35:01.400> doing 01:35:01.669 --> 01:35:01.679 align:start position:0% objective experience where it's doing 01:35:01.679 --> 01:35:04.990 align:start position:0% objective experience where it's doing its<01:35:01.800> own<01:35:02.080> thing<01:35:03.080> um<01:35:03.920> it<01:35:04.159> raises<01:35:04.520> a<01:35:04.639> bunch<01:35:04.840> of 01:35:04.990 --> 01:35:05.000 align:start position:0% its own thing um it raises a bunch of 01:35:05.000 --> 01:35:06.990 align:start position:0% its own thing um it raises a bunch of interesting<01:35:05.520> questions<01:35:05.960> about<01:35:06.280> cryptography 01:35:06.990 --> 01:35:07.000 align:start position:0% interesting questions about cryptography 01:35:07.000 --> 01:35:09.070 align:start position:0% interesting questions about cryptography and<01:35:07.320> agency<01:35:08.000> right<01:35:08.239> like<01:35:08.560> one<01:35:08.719> thing<01:35:08.840> that<01:35:08.960> I 01:35:09.070 --> 01:35:09.080 align:start position:0% and agency right like one thing that I 01:35:09.080 --> 01:35:10.910 align:start position:0% and agency right like one thing that I think<01:35:09.239> about<01:35:09.440> also<01:35:09.800> here<01:35:10.000> is<01:35:10.360> you<01:35:10.480> know<01:35:10.760> a 01:35:10.910 --> 01:35:10.920 align:start position:0% think about also here is you know a 01:35:10.920 --> 01:35:12.709 align:start position:0% think about also here is you know a cryptographic<01:35:11.639> agent<01:35:12.119> has<01:35:12.239> a<01:35:12.400> different 01:35:12.709 --> 01:35:12.719 align:start position:0% cryptographic agent has a different 01:35:12.719 --> 01:35:15.070 align:start position:0% cryptographic agent has a different flavor<01:35:13.159> or<01:35:13.320> affordance<01:35:13.760> to<01:35:13.880> it<01:35:14.000> than<01:35:14.119> an<01:35:14.320> AI 01:35:15.070 --> 01:35:15.080 align:start position:0% flavor or affordance to it than an AI 01:35:15.080 --> 01:35:18.430 align:start position:0% flavor or affordance to it than an AI agent<01:35:16.560> um<01:35:17.560> a<01:35:17.760> thought<01:35:18.000> that<01:35:18.159> then<01:35:18.280> was 01:35:18.430 --> 01:35:18.440 align:start position:0% agent um a thought that then was 01:35:18.440 --> 01:35:20.229 align:start position:0% agent um a thought that then was prompted<01:35:19.040> from<01:35:19.280> that<01:35:19.520> from<01:35:19.679> some<01:35:19.840> other<01:35:20.000> folks 01:35:20.229 --> 01:35:20.239 align:start position:0% prompted from that from some other folks 01:35:20.239 --> 01:35:21.470 align:start position:0% prompted from that from some other folks who<01:35:20.320> looked<01:35:20.480> at<01:35:20.560> frog<01:35:20.840> Zone<01:35:21.040> was<01:35:21.159> like<01:35:21.320> well 01:35:21.470 --> 01:35:21.480 align:start position:0% who looked at frog Zone was like well 01:35:21.480 --> 01:35:22.950 align:start position:0% who looked at frog Zone was like well what's<01:35:21.760> actually<01:35:22.040> going<01:35:22.199> on<01:35:22.360> with<01:35:22.520> encryption 01:35:22.950 --> 01:35:22.960 align:start position:0% what's actually going on with encryption 01:35:22.960 --> 01:35:25.790 align:start position:0% what's actually going on with encryption we<01:35:23.119> think<01:35:23.920> of<01:35:24.440> encryption<01:35:25.040> as<01:35:25.119> a<01:35:25.320> technology 01:35:25.790 --> 01:35:25.800 align:start position:0% we think of encryption as a technology 01:35:25.800 --> 01:35:27.910 align:start position:0% we think of encryption as a technology for<01:35:26.119> hiding<01:35:26.600> messages<01:35:27.199> but<01:35:27.360> maybe<01:35:27.600> that's<01:35:27.760> not 01:35:27.910 --> 01:35:27.920 align:start position:0% for hiding messages but maybe that's not 01:35:27.920 --> 01:35:29.830 align:start position:0% for hiding messages but maybe that's not what's<01:35:28.199> actually<01:35:28.520> going<01:35:28.760> on<01:35:29.239> in<01:35:29.360> the<01:35:29.480> same<01:35:29.679> way 01:35:29.830 --> 01:35:29.840 align:start position:0% what's actually going on in the same way 01:35:29.840 --> 01:35:32.510 align:start position:0% what's actually going on in the same way that<01:35:30.040> zero<01:35:30.679> knowledge<01:35:31.679> in<01:35:31.800> many<01:35:32.040> context<01:35:32.400> is 01:35:32.510 --> 01:35:32.520 align:start position:0% that zero knowledge in many context is 01:35:32.520 --> 01:35:34.229 align:start position:0% that zero knowledge in many context is not<01:35:32.800> really<01:35:33.159> about<01:35:33.480> zero<01:35:33.760> knowledge<01:35:34.080> or 01:35:34.229 --> 01:35:34.239 align:start position:0% not really about zero knowledge or 01:35:34.239 --> 01:35:36.470 align:start position:0% not really about zero knowledge or hiding<01:35:34.880> it's<01:35:35.119> about<01:35:35.600> proving<01:35:36.000> and<01:35:36.119> it's<01:35:36.280> about 01:35:36.470 --> 01:35:36.480 align:start position:0% hiding it's about proving and it's about 01:35:36.480 --> 01:35:37.270 align:start position:0% hiding it's about proving and it's about data 01:35:37.270 --> 01:35:37.280 align:start position:0% data 01:35:37.280 --> 01:35:38.990 align:start position:0% data interoperability<01:35:38.280> so<01:35:38.480> maybe<01:35:38.719> the<01:35:38.840> thing 01:35:38.990 --> 01:35:39.000 align:start position:0% interoperability so maybe the thing 01:35:39.000 --> 01:35:40.910 align:start position:0% interoperability so maybe the thing going<01:35:39.159> on<01:35:39.280> with<01:35:39.440> encryption<01:35:40.000> here<01:35:40.280> is<01:35:40.760> you 01:35:40.910 --> 01:35:40.920 align:start position:0% going on with encryption here is you 01:35:40.920 --> 01:35:44.189 align:start position:0% going on with encryption here is you know<01:35:41.480> if<01:35:42.119> I<01:35:42.440> mind<01:35:42.800> uploaded<01:35:43.320> my<01:35:43.480> brain<01:35:44.000> in 01:35:44.189 --> 01:35:44.199 align:start position:0% know if I mind uploaded my brain in 01:35:44.199 --> 01:35:46.350 align:start position:0% know if I mind uploaded my brain in encryption<01:35:45.159> to<01:35:45.560> you<01:35:45.679> know<01:35:45.840> some<01:35:46.000> server 01:35:46.350 --> 01:35:46.360 align:start position:0% encryption to you know some server 01:35:46.360 --> 01:35:47.990 align:start position:0% encryption to you know some server somewhere<01:35:46.639> in<01:35:46.800> plain<01:35:47.199> or<01:35:47.320> sorry<01:35:47.719> not<01:35:47.840> in 01:35:47.990 --> 01:35:48.000 align:start position:0% somewhere in plain or sorry not in 01:35:48.000 --> 01:35:49.350 align:start position:0% somewhere in plain or sorry not in encryption<01:35:48.360> in<01:35:48.480> PL<01:35:48.679> text<01:35:48.880> to<01:35:48.960> some<01:35:49.080> server 01:35:49.350 --> 01:35:49.360 align:start position:0% encryption in PL text to some server 01:35:49.360 --> 01:35:51.070 align:start position:0% encryption in PL text to some server somewhere<01:35:49.960> the<01:35:50.119> operator<01:35:50.440> of<01:35:50.600> that<01:35:50.719> server 01:35:51.070 --> 01:35:51.080 align:start position:0% somewhere the operator of that server 01:35:51.080 --> 01:35:52.830 align:start position:0% somewhere the operator of that server would<01:35:51.239> be<01:35:51.360> able<01:35:51.560> to<01:35:51.760> do<01:35:52.000> surgery<01:35:52.480> on<01:35:52.679> my 01:35:52.830 --> 01:35:52.840 align:start position:0% would be able to do surgery on my 01:35:52.840 --> 01:35:54.830 align:start position:0% would be able to do surgery on my neurons<01:35:53.280> to<01:35:53.440> really<01:35:53.679> really<01:35:54.000> like<01:35:54.679> with 01:35:54.830 --> 01:35:54.840 align:start position:0% neurons to really really like with 01:35:54.840 --> 01:35:57.149 align:start position:0% neurons to really really like with my<01:35:55.000> subjective<01:35:55.560> experience<01:35:56.560> but<01:35:56.880> if<01:35:57.000> I 01:35:57.149 --> 01:35:57.159 align:start position:0% my subjective experience but if I 01:35:57.159 --> 01:35:59.310 align:start position:0% my subjective experience but if I uploaded<01:35:57.600> my<01:35:57.719> brain<01:35:58.040> in<01:35:58.320> encryption<01:35:58.960> or<01:35:59.119> in 01:35:59.310 --> 01:35:59.320 align:start position:0% uploaded my brain in encryption or in 01:35:59.320 --> 01:36:02.270 align:start position:0% uploaded my brain in encryption or in obfuscation<01:36:00.080> somewhere<01:36:00.719> the<01:36:00.920> only<01:36:01.360> way<01:36:01.960> for 01:36:02.270 --> 01:36:02.280 align:start position:0% obfuscation somewhere the only way for 01:36:02.280 --> 01:36:04.430 align:start position:0% obfuscation somewhere the only way for the<01:36:02.480> person<01:36:02.920> operating<01:36:03.600> that<01:36:03.880> program<01:36:04.280> to 01:36:04.430 --> 01:36:04.440 align:start position:0% the person operating that program to 01:36:04.440 --> 01:36:06.390 align:start position:0% the person operating that program to mess<01:36:04.679> with<01:36:04.880> me<01:36:05.199> specifically<01:36:05.960> would<01:36:06.119> be<01:36:06.239> for 01:36:06.390 --> 01:36:06.400 align:start position:0% mess with me specifically would be for 01:36:06.400 --> 01:36:07.709 align:start position:0% mess with me specifically would be for them<01:36:06.520> to<01:36:06.679> essentially<01:36:07.040> take<01:36:07.239> down<01:36:07.360> the<01:36:07.520> whole 01:36:07.709 --> 01:36:07.719 align:start position:0% them to essentially take down the whole 01:36:07.719 --> 01:36:09.830 align:start position:0% them to essentially take down the whole system<01:36:08.400> because<01:36:08.639> now<01:36:08.960> all<01:36:09.080> of<01:36:09.239> the<01:36:09.400> gates 01:36:09.830 --> 01:36:09.840 align:start position:0% system because now all of the gates 01:36:09.840 --> 01:36:11.830 align:start position:0% system because now all of the gates describing<01:36:10.320> my<01:36:10.480> brain<01:36:10.920> are<01:36:11.239> intimately 01:36:11.830 --> 01:36:11.840 align:start position:0% describing my brain are intimately 01:36:11.840 --> 01:36:13.149 align:start position:0% describing my brain are intimately connected<01:36:12.280> with<01:36:12.400> the<01:36:12.560> rest<01:36:12.719> of<01:36:12.840> the<01:36:12.960> off 01:36:13.149 --> 01:36:13.159 align:start position:0% connected with the rest of the off 01:36:13.159 --> 01:36:14.870 align:start position:0% connected with the rest of the off fiscated<01:36:13.560> program<01:36:14.040> you<01:36:14.119> can<01:36:14.320> either<01:36:14.520> turn<01:36:14.760> the 01:36:14.870 --> 01:36:14.880 align:start position:0% fiscated program you can either turn the 01:36:14.880 --> 01:36:17.629 align:start position:0% fiscated program you can either turn the crank<01:36:15.159> on<01:36:15.320> the<01:36:15.480> entire<01:36:16.040> program<01:36:16.360> at<01:36:16.520> once<01:36:17.080> or 01:36:17.629 --> 01:36:17.639 align:start position:0% crank on the entire program at once or 01:36:17.639 --> 01:36:20.189 align:start position:0% crank on the entire program at once or you<01:36:17.760> can<01:36:17.920> just<01:36:18.159> like<01:36:18.600> destroy<01:36:18.960> it<01:36:19.199> completely 01:36:20.189 --> 01:36:20.199 align:start position:0% you can just like destroy it completely 01:36:20.199 --> 01:36:22.270 align:start position:0% you can just like destroy it completely that<01:36:20.520> internal<01:36:21.080> logic<01:36:21.440> of<01:36:21.600> the<01:36:21.760> world<01:36:22.119> is 01:36:22.270 --> 01:36:22.280 align:start position:0% that internal logic of the world is 01:36:22.280 --> 01:36:24.189 align:start position:0% that internal logic of the world is somehow<01:36:22.679> preserved<01:36:23.639> because<01:36:23.840> of<01:36:23.960> the<01:36:24.080> fact 01:36:24.189 --> 01:36:24.199 align:start position:0% somehow preserved because of the fact 01:36:24.199 --> 01:36:25.950 align:start position:0% somehow preserved because of the fact that<01:36:24.320> it's<01:36:24.480> OB<01:36:24.679> fiscated<01:36:25.199> and<01:36:25.320> the<01:36:25.560> hiding 01:36:25.950 --> 01:36:25.960 align:start position:0% that it's OB fiscated and the hiding 01:36:25.960 --> 01:36:28.189 align:start position:0% that it's OB fiscated and the hiding thing<01:36:26.199> comes<01:36:26.400> out<01:36:26.639> as<01:36:26.760> an<01:36:27.040> accidental 01:36:28.189 --> 01:36:28.199 align:start position:0% thing comes out as an accidental 01:36:28.199 --> 01:36:30.470 align:start position:0% thing comes out as an accidental property<01:36:29.199> so<01:36:29.600> you<01:36:29.679> know<01:36:29.840> going<01:36:30.080> back<01:36:30.280> actually 01:36:30.470 --> 01:36:30.480 align:start position:0% property so you know going back actually 01:36:30.480 --> 01:36:31.709 align:start position:0% property so you know going back actually to<01:36:30.719> to<01:36:30.840> one<01:36:30.920> of<01:36:31.000> the<01:36:31.080> things<01:36:31.280> Albert<01:36:31.600> was 01:36:31.709 --> 01:36:31.719 align:start position:0% to to one of the things Albert was 01:36:31.719 --> 01:36:33.669 align:start position:0% to to one of the things Albert was referencing<01:36:32.239> as<01:36:32.400> well<01:36:32.840> there's<01:36:33.080> this<01:36:33.280> idea<01:36:33.520> of 01:36:33.669 --> 01:36:33.679 align:start position:0% referencing as well there's this idea of 01:36:33.679 --> 01:36:36.070 align:start position:0% referencing as well there's this idea of we<01:36:33.880> call<01:36:34.280> something<01:36:35.040> X<01:36:35.480> because<01:36:35.639> we<01:36:35.760> don't<01:36:35.960> yet 01:36:36.070 --> 01:36:36.080 align:start position:0% we call something X because we don't yet 01:36:36.080 --> 01:36:37.310 align:start position:0% we call something X because we don't yet know<01:36:36.239> what<01:36:36.360> to<01:36:36.480> call<01:36:36.600> it<01:36:36.760> it's<01:36:36.920> it's<01:36:37.040> pointing 01:36:37.310 --> 01:36:37.320 align:start position:0% know what to call it it's it's pointing 01:36:37.320 --> 01:36:38.830 align:start position:0% know what to call it it's it's pointing at<01:36:37.440> the<01:36:37.560> idea<01:36:37.840> that<01:36:38.119> the<01:36:38.280> words<01:36:38.600> that<01:36:38.679> we're 01:36:38.830 --> 01:36:38.840 align:start position:0% at the idea that the words that we're 01:36:38.840 --> 01:36:40.910 align:start position:0% at the idea that the words that we're using<01:36:39.080> to<01:36:39.239> describe<01:36:39.719> these<01:36:39.920> systems<01:36:40.560> are 01:36:40.910 --> 01:36:40.920 align:start position:0% using to describe these systems are 01:36:40.920 --> 01:36:42.830 align:start position:0% using to describe these systems are placeholders<01:36:41.880> and<01:36:42.000> they<01:36:42.159> represent<01:36:42.560> the<01:36:42.679> fact 01:36:42.830 --> 01:36:42.840 align:start position:0% placeholders and they represent the fact 01:36:42.840 --> 01:36:44.350 align:start position:0% placeholders and they represent the fact that<01:36:42.960> we<01:36:43.119> just<01:36:43.239> don't<01:36:43.480> have<01:36:43.600> a<01:36:43.719> better 01:36:44.350 --> 01:36:44.360 align:start position:0% that we just don't have a better 01:36:44.360 --> 01:36:46.229 align:start position:0% that we just don't have a better understanding<01:36:44.760> yet<01:36:45.440> so<01:36:45.560> we<01:36:45.679> called<01:36:45.880> it<01:36:46.000> zero 01:36:46.229 --> 01:36:46.239 align:start position:0% understanding yet so we called it zero 01:36:46.239 --> 01:36:47.310 align:start position:0% understanding yet so we called it zero knowledge<01:36:46.560> because<01:36:46.719> we<01:36:46.840> didn't<01:36:47.000> know<01:36:47.119> what<01:36:47.199> to 01:36:47.310 --> 01:36:47.320 align:start position:0% knowledge because we didn't know what to 01:36:47.320 --> 01:36:49.149 align:start position:0% knowledge because we didn't know what to call<01:36:47.480> it<01:36:48.199> um<01:36:48.320> now<01:36:48.440> we're<01:36:48.560> moving<01:36:48.760> to<01:36:48.880> a<01:36:48.960> world 01:36:49.149 --> 01:36:49.159 align:start position:0% call it um now we're moving to a world 01:36:49.159 --> 01:36:51.350 align:start position:0% call it um now we're moving to a world of<01:36:49.480> some<01:36:49.679> maybe<01:36:49.880> something<01:36:50.119> like<01:36:50.360> proofs 01:36:51.350 --> 01:36:51.360 align:start position:0% of some maybe something like proofs 01:36:51.360 --> 01:36:52.910 align:start position:0% of some maybe something like proofs maybe<01:36:51.639> we<01:36:51.760> call<01:36:51.880> it<01:36:52.040> encryption<01:36:52.639> because<01:36:52.800> we 01:36:52.910 --> 01:36:52.920 align:start position:0% maybe we call it encryption because we 01:36:52.920 --> 01:36:54.510 align:start position:0% maybe we call it encryption because we don't<01:36:53.040> know<01:36:53.159> what<01:36:53.239> to<01:36:53.320> call<01:36:53.719> it<01:36:54.119> and<01:36:54.239> maybe 01:36:54.510 --> 01:36:54.520 align:start position:0% don't know what to call it and maybe 01:36:54.520 --> 01:36:56.750 align:start position:0% don't know what to call it and maybe it's<01:36:54.800> actually<01:36:55.159> about<01:36:55.560> creating<01:36:56.080> worlds<01:36:56.560> with 01:36:56.750 --> 01:36:56.760 align:start position:0% it's actually about creating worlds with 01:36:56.760 --> 01:36:59.350 align:start position:0% it's actually about creating worlds with somehow<01:36:57.520> mathematically<01:36:58.520> unwind 01:36:59.350 --> 01:36:59.360 align:start position:0% somehow mathematically unwind 01:36:59.360 --> 01:37:01.149 align:start position:0% somehow mathematically unwind codependencies<01:36:59.960> between 01:37:01.149 --> 01:37:01.159 align:start position:0% codependencies between 01:37:01.159 --> 01:37:03.430 align:start position:0% codependencies between everything<01:37:02.159> maybe<01:37:02.400> we<01:37:02.560> call<01:37:02.679> it<01:37:02.880> cryptography 01:37:03.430 --> 01:37:03.440 align:start position:0% everything maybe we call it cryptography 01:37:03.440 --> 01:37:05.189 align:start position:0% everything maybe we call it cryptography or<01:37:03.600> programmable<01:37:04.119> cryptography<01:37:04.920> because<01:37:05.119> we 01:37:05.189 --> 01:37:05.199 align:start position:0% or programmable cryptography because we 01:37:05.199 --> 01:37:07.229 align:start position:0% or programmable cryptography because we don't<01:37:05.360> know<01:37:05.480> what<01:37:05.600> to<01:37:05.760> call 01:37:07.229 --> 01:37:07.239 align:start position:0% don't know what to call 01:37:07.239 --> 01:37:12.270 align:start position:0% don't know what to call it<01:37:08.560> so<01:37:09.560> that's<01:37:09.800> it<01:37:10.040> basically<01:37:10.480> for<01:37:10.960> contact<01:37:11.960> um 01:37:12.270 --> 01:37:12.280 align:start position:0% it so that's it basically for contact um 01:37:12.280 --> 01:37:14.870 align:start position:0% it so that's it basically for contact um you<01:37:12.400> can<01:37:12.600> find<01:37:12.760> out<01:37:12.960> more<01:37:13.280> about<01:37:13.600> what's<01:37:13.920> next 01:37:14.870 --> 01:37:14.880 align:start position:0% you can find out more about what's next 01:37:14.880 --> 01:37:16.109 align:start position:0% you can find out more about what's next uh<01:37:15.119> this 01:37:16.109 --> 01:37:16.119 align:start position:0% uh this 01:37:16.119 --> 01:37:18.350 align:start position:0% uh this afternoon<01:37:17.119> uh<01:37:17.239> we<01:37:17.360> will<01:37:17.639> be<01:37:17.800> talking<01:37:18.080> about<01:37:18.239> a 01:37:18.350 --> 01:37:18.360 align:start position:0% afternoon uh we will be talking about a 01:37:18.360 --> 01:37:19.510 align:start position:0% afternoon uh we will be talking about a bunch<01:37:18.520> of<01:37:18.639> these<01:37:18.800> different<01:37:19.040> systems<01:37:19.440> that 01:37:19.510 --> 01:37:19.520 align:start position:0% bunch of these different systems that 01:37:19.520 --> 01:37:21.070 align:start position:0% bunch of these different systems that we've<01:37:19.679> put<01:37:19.840> into<01:37:20.080> varying<01:37:20.520> stages<01:37:20.880> of 01:37:21.070 --> 01:37:21.080 align:start position:0% we've put into varying stages of 01:37:21.080 --> 01:37:23.149 align:start position:0% we've put into varying stages of production<01:37:22.080> um<01:37:22.400> hopefully<01:37:22.719> over<01:37:22.880> the<01:37:22.960> next 01:37:23.149 --> 01:37:23.159 align:start position:0% production um hopefully over the next 01:37:23.159 --> 01:37:24.470 align:start position:0% production um hopefully over the next couple<01:37:23.360> years<01:37:23.560> years<01:37:23.760> we<01:37:23.920> essentially<01:37:24.280> take 01:37:24.470 --> 01:37:24.480 align:start position:0% couple years years we essentially take 01:37:24.480 --> 01:37:26.229 align:start position:0% couple years years we essentially take these<01:37:24.600> mental<01:37:24.920> models<01:37:25.440> and<01:37:25.639> we<01:37:25.760> can<01:37:26.000> start 01:37:26.229 --> 01:37:26.239 align:start position:0% these mental models and we can start 01:37:26.239 --> 01:37:28.590 align:start position:0% these mental models and we can start building<01:37:26.480> out<01:37:26.600> a<01:37:26.679> lot<01:37:26.800> more<01:37:26.920> mature<01:37:27.600> systems 01:37:28.590 --> 01:37:28.600 align:start position:0% building out a lot more mature systems 01:37:28.600 --> 01:37:30.109 align:start position:0% building out a lot more mature systems uh<01:37:28.800> and<01:37:29.000> thank<01:37:29.159> you<01:37:29.360> everybody<01:37:29.679> if<01:37:29.760> you<01:37:29.880> want<01:37:30.000> a 01:37:30.109 --> 01:37:30.119 align:start position:0% uh and thank you everybody if you want a 01:37:30.119 --> 01:37:31.629 align:start position:0% uh and thank you everybody if you want a little<01:37:30.280> froggy<01:37:30.679> gift<01:37:30.920> feel<01:37:31.080> free<01:37:31.280> to<01:37:31.400> scan 01:37:31.629 --> 01:37:31.639 align:start position:0% little froggy gift feel free to scan 01:37:31.639 --> 01:37:35.270 align:start position:0% little froggy gift feel free to scan this<01:37:31.760> QR<01:37:32.080> code<01:37:32.320> as 01:37:35.270 --> 01:37:35.280 align:start position:0% 01:37:35.280 --> 01:37:38.870 align:start position:0% well<01:37:36.280> any<01:37:36.480> froggy 01:37:38.870 --> 01:37:38.880 align:start position:0% well any froggy 01:37:38.880 --> 01:37:41.669 align:start position:0% well any froggy gift<01:37:39.880> it's<01:37:40.119> not<01:37:40.360> any<01:37:40.599> froggy<01:37:41.040> gift<01:37:41.360> this<01:37:41.440> is 01:37:41.669 --> 01:37:41.679 align:start position:0% gift it's not any froggy gift this is 01:37:41.679 --> 01:37:44.520 align:start position:0% gift it's not any froggy gift this is most