WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:14.770 align:start position:0% [Music] 00:00:14.770 --> 00:00:14.780 align:start position:0% 00:00:14.780 --> 00:00:17.029 align:start position:0% I'm<00:00:15.780> gupsheep<00:00:16.320> and<00:00:16.500> I<00:00:16.619> work<00:00:16.740> with<00:00:16.920> the 00:00:17.029 --> 00:00:17.039 align:start position:0% I'm gupsheep and I work with the 00:00:17.039 --> 00:00:18.529 align:start position:0% I'm gupsheep and I work with the research<00:00:17.340> focused<00:00:17.760> organization<00:00:18.240> called 00:00:18.529 --> 00:00:18.539 align:start position:0% research focused organization called 00:00:18.539 --> 00:00:21.290 align:start position:0% research focused organization called Xerox<00:00:18.960> park<00:00:19.320> today<00:00:20.100> I<00:00:20.460> will<00:00:20.580> be<00:00:20.699> talking<00:00:20.939> about 00:00:21.290 --> 00:00:21.300 align:start position:0% Xerox park today I will be talking about 00:00:21.300 --> 00:00:23.689 align:start position:0% Xerox park today I will be talking about this<00:00:21.600> idea<00:00:21.900> of<00:00:22.260> zkp's<00:00:22.980> and<00:00:23.220> programmable 00:00:23.689 --> 00:00:23.699 align:start position:0% this idea of zkp's and programmable 00:00:23.699 --> 00:00:26.029 align:start position:0% this idea of zkp's and programmable cryptography<00:00:24.480> which<00:00:25.080> is<00:00:25.260> a<00:00:25.439> phrase<00:00:25.619> that<00:00:25.859> we 00:00:26.029 --> 00:00:26.039 align:start position:0% cryptography which is a phrase that we 00:00:26.039 --> 00:00:28.250 align:start position:0% cryptography which is a phrase that we use<00:00:26.220> to<00:00:26.640> describe<00:00:27.119> a<00:00:27.539> lot<00:00:27.599> of<00:00:27.720> what<00:00:27.840> we<00:00:27.960> focused 00:00:28.250 --> 00:00:28.260 align:start position:0% use to describe a lot of what we focused 00:00:28.260 --> 00:00:31.009 align:start position:0% use to describe a lot of what we focused on<00:00:28.380> at<00:00:28.500> Xerox<00:00:28.800> Park<00:00:29.160> I'll<00:00:30.000> describe<00:00:30.480> what 00:00:31.009 --> 00:00:31.019 align:start position:0% on at Xerox Park I'll describe what 00:00:31.019 --> 00:00:33.709 align:start position:0% on at Xerox Park I'll describe what programmable<00:00:31.500> cryptography<00:00:32.220> means<00:00:32.640> and<00:00:33.360> why 00:00:33.709 --> 00:00:33.719 align:start position:0% programmable cryptography means and why 00:00:33.719 --> 00:00:35.870 align:start position:0% programmable cryptography means and why we<00:00:33.960> think<00:00:34.079> it's<00:00:34.380> important<00:00:34.739> for<00:00:34.980> anyone<00:00:35.280> who 00:00:35.870 --> 00:00:35.880 align:start position:0% we think it's important for anyone who 00:00:35.880 --> 00:00:37.610 align:start position:0% we think it's important for anyone who is<00:00:36.059> interested<00:00:36.480> in<00:00:36.780> the<00:00:36.899> future<00:00:37.079> of<00:00:37.440> Next 00:00:37.610 --> 00:00:37.620 align:start position:0% is interested in the future of Next 00:00:37.620 --> 00:00:39.889 align:start position:0% is interested in the future of Next Generation<00:00:38.120> blockchain<00:00:39.120> and<00:00:39.300> decentralized 00:00:39.889 --> 00:00:39.899 align:start position:0% Generation blockchain and decentralized 00:00:39.899 --> 00:00:42.950 align:start position:0% Generation blockchain and decentralized applications<00:00:40.760> so<00:00:41.760> first<00:00:41.940> off<00:00:42.120> I'll<00:00:42.540> give<00:00:42.719> a 00:00:42.950 --> 00:00:42.960 align:start position:0% applications so first off I'll give a 00:00:42.960 --> 00:00:44.630 align:start position:0% applications so first off I'll give a little<00:00:43.079> bit<00:00:43.200> of<00:00:43.320> context<00:00:43.739> into<00:00:44.100> what<00:00:44.280> Xerox 00:00:44.630 --> 00:00:44.640 align:start position:0% little bit of context into what Xerox 00:00:44.640 --> 00:00:48.049 align:start position:0% little bit of context into what Xerox Park<00:00:44.879> is<00:00:45.180> for<00:00:45.780> folks<00:00:46.260> who<00:00:46.559> have<00:00:46.800> not<00:00:47.100> heard 00:00:48.049 --> 00:00:48.059 align:start position:0% Park is for folks who have not heard 00:00:48.059 --> 00:00:50.270 align:start position:0% Park is for folks who have not heard about<00:00:48.239> this<00:00:48.360> organization<00:00:48.840> Xerox<00:00:49.800> Park<00:00:49.980> is<00:00:50.160> a 00:00:50.270 --> 00:00:50.280 align:start position:0% about this organization Xerox Park is a 00:00:50.280 --> 00:00:51.889 align:start position:0% about this organization Xerox Park is a relatively<00:00:50.579> new<00:00:50.700> research<00:00:51.059> focused<00:00:51.539> org 00:00:51.889 --> 00:00:51.899 align:start position:0% relatively new research focused org 00:00:51.899 --> 00:00:54.049 align:start position:0% relatively new research focused org which<00:00:52.379> supports<00:00:52.800> what<00:00:53.100> we<00:00:53.219> call<00:00:53.460> application 00:00:54.049 --> 00:00:54.059 align:start position:0% which supports what we call application 00:00:54.059 --> 00:00:56.510 align:start position:0% which supports what we call application Level<00:00:54.300> r<00:00:54.660> d<00:00:54.899> on<00:00:55.739> ethereum<00:00:56.219> and<00:00:56.399> other 00:00:56.510 --> 00:00:56.520 align:start position:0% Level r d on ethereum and other 00:00:56.520 --> 00:00:58.250 align:start position:0% Level r d on ethereum and other decentralized<00:00:57.120> platforms<00:00:57.600> so<00:00:57.719> this<00:00:57.960> means 00:00:58.250 --> 00:00:58.260 align:start position:0% decentralized platforms so this means 00:00:58.260 --> 00:01:01.670 align:start position:0% decentralized platforms so this means trying<00:00:59.100> to<00:00:59.340> better<00:00:59.460> understand<00:01:00.320> what<00:01:01.320> is 00:01:01.670 --> 00:01:01.680 align:start position:0% trying to better understand what is 00:01:01.680 --> 00:01:04.609 align:start position:0% trying to better understand what is possible<00:01:02.160> to<00:01:02.399> do<00:01:02.579> on<00:01:03.000> these<00:01:03.300> kinds<00:01:03.660> of<00:01:04.019> you 00:01:04.609 --> 00:01:04.619 align:start position:0% possible to do on these kinds of you 00:01:04.619 --> 00:01:06.530 align:start position:0% possible to do on these kinds of you know<00:01:04.680> smart<00:01:04.920> contract<00:01:05.339> platforms<00:01:05.939> or<00:01:06.299> with 00:01:06.530 --> 00:01:06.540 align:start position:0% know smart contract platforms or with 00:01:06.540 --> 00:01:08.030 align:start position:0% know smart contract platforms or with new<00:01:06.659> decentralized<00:01:07.380> application 00:01:08.030 --> 00:01:08.040 align:start position:0% new decentralized application 00:01:08.040 --> 00:01:10.130 align:start position:0% new decentralized application technologies<00:01:08.640> that<00:01:09.420> isn't<00:01:09.720> necessarily 00:01:10.130 --> 00:01:10.140 align:start position:0% technologies that isn't necessarily 00:01:10.140 --> 00:01:12.289 align:start position:0% technologies that isn't necessarily currently<00:01:10.500> possible<00:01:10.799> today<00:01:11.040> but<00:01:11.400> might<00:01:11.640> be<00:01:11.880> on 00:01:12.289 --> 00:01:12.299 align:start position:0% currently possible today but might be on 00:01:12.299 --> 00:01:14.030 align:start position:0% currently possible today but might be on the<00:01:12.420> horizon 00:01:14.030 --> 00:01:14.040 align:start position:0% the horizon 00:01:14.040 --> 00:01:15.770 align:start position:0% the horizon um projects<00:01:14.580> that<00:01:14.760> we<00:01:14.880> support<00:01:15.119> include 00:01:15.770 --> 00:01:15.780 align:start position:0% um projects that we support include 00:01:15.780 --> 00:01:18.410 align:start position:0% um projects that we support include things<00:01:16.500> like<00:01:16.680> Dark<00:01:16.920> Forest<00:01:17.400> as<00:01:18.180> well<00:01:18.299> as 00:01:18.410 --> 00:01:18.420 align:start position:0% things like Dark Forest as well as 00:01:18.420 --> 00:01:20.390 align:start position:0% things like Dark Forest as well as Persona<00:01:19.200> Labs<00:01:19.560> building<00:01:19.799> things<00:01:20.280> like 00:01:20.390 --> 00:01:20.400 align:start position:0% Persona Labs building things like 00:01:20.400 --> 00:01:22.370 align:start position:0% Persona Labs building things like hanging<00:01:20.820> on<00:01:20.939> or<00:01:21.119> if<00:01:21.360> folks<00:01:21.840> were<00:01:21.900> around<00:01:22.080> the 00:01:22.370 --> 00:01:22.380 align:start position:0% hanging on or if folks were around the 00:01:22.380 --> 00:01:24.350 align:start position:0% hanging on or if folks were around the applied<00:01:22.979> ZK<00:01:23.340> showcase<00:01:23.759> yesterday<00:01:23.939> you<00:01:24.240> might 00:01:24.350 --> 00:01:24.360 align:start position:0% applied ZK showcase yesterday you might 00:01:24.360 --> 00:01:26.810 align:start position:0% applied ZK showcase yesterday you might have<00:01:24.479> seen<00:01:24.600> proof<00:01:24.900> of<00:01:24.960> email<00:01:25.200> or<00:01:25.680> various<00:01:26.040> ZK 00:01:26.810 --> 00:01:26.820 align:start position:0% have seen proof of email or various ZK 00:01:26.820 --> 00:01:30.530 align:start position:0% have seen proof of email or various ZK machine<00:01:27.060> learning<00:01:27.479> experiments<00:01:28.159> we<00:01:29.159> also<00:01:29.580> uh 00:01:30.530 --> 00:01:30.540 align:start position:0% machine learning experiments we also uh 00:01:30.540 --> 00:01:33.170 align:start position:0% machine learning experiments we also uh build<00:01:31.140> circuit<00:01:31.560> Primitives<00:01:31.979> for<00:01:32.280> ZK<00:01:32.580> snarks 00:01:33.170 --> 00:01:33.180 align:start position:0% build circuit Primitives for ZK snarks 00:01:33.180 --> 00:01:35.450 align:start position:0% build circuit Primitives for ZK snarks and<00:01:33.420> focus<00:01:33.780> a<00:01:34.140> lot<00:01:34.259> on<00:01:34.619> infrastructure 00:01:35.450 --> 00:01:35.460 align:start position:0% and focus a lot on infrastructure 00:01:35.460 --> 00:01:37.069 align:start position:0% and focus a lot on infrastructure maintenance<00:01:35.880> and<00:01:36.180> third-party<00:01:36.720> development 00:01:37.069 --> 00:01:37.079 align:start position:0% maintenance and third-party development 00:01:37.079 --> 00:01:39.770 align:start position:0% maintenance and third-party development of<00:01:37.860> tool<00:01:38.100> Stacks<00:01:38.400> like<00:01:38.520> snark.js<00:01:39.240> sir<00:01:39.540> com 00:01:39.770 --> 00:01:39.780 align:start position:0% of tool Stacks like snark.js sir com 00:01:39.780 --> 00:01:42.410 align:start position:0% of tool Stacks like snark.js sir com Halo<00:01:40.200> 2<00:01:40.320> and<00:01:40.500> more<00:01:40.619> and<00:01:41.340> we<00:01:41.460> also<00:01:41.700> do<00:01:41.820> a<00:01:42.000> lot<00:01:42.119> of 00:01:42.410 --> 00:01:42.420 align:start position:0% Halo 2 and more and we also do a lot of 00:01:42.420 --> 00:01:44.330 align:start position:0% Halo 2 and more and we also do a lot of community<00:01:42.659> building<00:01:43.020> efforts<00:01:43.560> and<00:01:44.040> we<00:01:44.220> work 00:01:44.330 --> 00:01:44.340 align:start position:0% community building efforts and we work 00:01:44.340 --> 00:01:46.249 align:start position:0% community building efforts and we work on<00:01:44.520> Cross<00:01:44.759> team<00:01:45.000> and<00:01:45.299> ecosystem-wide 00:01:46.249 --> 00:01:46.259 align:start position:0% on Cross team and ecosystem-wide 00:01:46.259 --> 00:01:49.910 align:start position:0% on Cross team and ecosystem-wide projects<00:01:46.979> as<00:01:47.280> well 00:01:49.910 --> 00:01:49.920 align:start position:0% 00:01:49.920 --> 00:01:52.130 align:start position:0% cool<00:01:50.520> so<00:01:50.880> one<00:01:51.119> of<00:01:51.180> our<00:01:51.299> largest<00:01:51.600> areas<00:01:51.960> of 00:01:52.130 --> 00:01:52.140 align:start position:0% cool so one of our largest areas of 00:01:52.140 --> 00:01:54.710 align:start position:0% cool so one of our largest areas of focus<00:01:52.380> at<00:01:52.680> Xerox<00:01:53.040> Park<00:01:53.340> is<00:01:54.000> applied<00:01:54.360> ZK 00:01:54.710 --> 00:01:54.720 align:start position:0% focus at Xerox Park is applied ZK 00:01:54.720 --> 00:01:56.270 align:start position:0% focus at Xerox Park is applied ZK cryptography 00:01:56.270 --> 00:01:56.280 align:start position:0% cryptography 00:01:56.280 --> 00:01:59.149 align:start position:0% cryptography um which<00:01:56.939> means<00:01:57.360> that<00:01:57.899> a<00:01:58.380> big<00:01:58.619> Focus<00:01:58.860> for<00:01:59.040> us 00:01:59.149 --> 00:01:59.159 align:start position:0% um which means that a big Focus for us 00:01:59.159 --> 00:02:01.609 align:start position:0% um which means that a big Focus for us is<00:01:59.340> understanding<00:02:00.060> what<00:02:00.720> is<00:02:00.840> possible<00:02:01.200> to<00:02:01.500> do 00:02:01.609 --> 00:02:01.619 align:start position:0% is understanding what is possible to do 00:02:01.619 --> 00:02:03.590 align:start position:0% is understanding what is possible to do with<00:02:01.920> DK<00:02:02.280> crypto<00:02:02.759> what<00:02:03.299> you<00:02:03.479> know 00:02:03.590 --> 00:02:03.600 align:start position:0% with DK crypto what you know 00:02:03.600 --> 00:02:05.030 align:start position:0% with DK crypto what you know theoretically<00:02:04.020> should<00:02:04.259> be<00:02:04.380> possible<00:02:04.680> to<00:02:04.860> do 00:02:05.030 --> 00:02:05.040 align:start position:0% theoretically should be possible to do 00:02:05.040 --> 00:02:07.370 align:start position:0% theoretically should be possible to do with<00:02:05.700> DK<00:02:06.000> crypto<00:02:06.299> and<00:02:06.420> decentralized<00:02:07.079> apps 00:02:07.370 --> 00:02:07.380 align:start position:0% with DK crypto and decentralized apps 00:02:07.380 --> 00:02:09.650 align:start position:0% with DK crypto and decentralized apps and<00:02:07.920> what<00:02:08.160> we<00:02:08.280> need<00:02:08.459> to<00:02:08.580> do<00:02:08.759> to<00:02:09.060> to<00:02:09.239> get<00:02:09.479> there 00:02:09.650 --> 00:02:09.660 align:start position:0% and what we need to do to to get there 00:02:09.660 --> 00:02:11.930 align:start position:0% and what we need to do to to get there to<00:02:09.959> eventually<00:02:10.259> bring<00:02:10.860> those<00:02:11.160> kinds<00:02:11.520> of<00:02:11.580> tools 00:02:11.930 --> 00:02:11.940 align:start position:0% to eventually bring those kinds of tools 00:02:11.940 --> 00:02:15.589 align:start position:0% to eventually bring those kinds of tools to<00:02:12.180> production<00:02:12.660> and<00:02:13.500> apply<00:02:13.800> ZK<00:02:14.220> is<00:02:14.700> one<00:02:15.300> of<00:02:15.420> a 00:02:15.589 --> 00:02:15.599 align:start position:0% to production and apply ZK is one of a 00:02:15.599 --> 00:02:18.110 align:start position:0% to production and apply ZK is one of a category<00:02:16.020> of<00:02:16.620> relatively<00:02:17.580> newer 00:02:18.110 --> 00:02:18.120 align:start position:0% category of relatively newer 00:02:18.120 --> 00:02:19.970 align:start position:0% category of relatively newer cryptographic<00:02:18.840> Primitives<00:02:19.260> that<00:02:19.800> we 00:02:19.970 --> 00:02:19.980 align:start position:0% cryptographic Primitives that we 00:02:19.980 --> 00:02:21.770 align:start position:0% cryptographic Primitives that we categorized<00:02:20.580> under<00:02:20.819> this<00:02:21.060> term<00:02:21.180> programmable 00:02:21.770 --> 00:02:21.780 align:start position:0% categorized under this term programmable 00:02:21.780 --> 00:02:23.150 align:start position:0% categorized under this term programmable cryptography 00:02:23.150 --> 00:02:23.160 align:start position:0% cryptography 00:02:23.160 --> 00:02:23.750 align:start position:0% cryptography um 00:02:23.750 --> 00:02:23.760 align:start position:0% um 00:02:23.760 --> 00:02:27.350 align:start position:0% um and<00:02:24.599> in<00:02:25.260> order<00:02:25.440> to<00:02:25.800> describe<00:02:26.520> or<00:02:26.940> you<00:02:27.239> know 00:02:27.350 --> 00:02:27.360 align:start position:0% and in order to describe or you know 00:02:27.360 --> 00:02:30.350 align:start position:0% and in order to describe or you know give<00:02:27.900> a<00:02:28.560> feeling<00:02:28.860> for<00:02:29.220> why<00:02:29.520> uh<00:02:29.940> programmable 00:02:30.350 --> 00:02:30.360 align:start position:0% give a feeling for why uh programmable 00:02:30.360 --> 00:02:32.330 align:start position:0% give a feeling for why uh programmable cryptography<00:02:31.020> is<00:02:31.200> important<00:02:31.560> first<00:02:31.980> I<00:02:32.160> want 00:02:32.330 --> 00:02:32.340 align:start position:0% cryptography is important first I want 00:02:32.340 --> 00:02:34.610 align:start position:0% cryptography is important first I want to<00:02:32.400> go<00:02:32.520> into<00:02:32.640> a<00:02:33.120> little<00:02:33.239> bit<00:02:33.360> about<00:02:33.720> the<00:02:34.200> a 00:02:34.610 --> 00:02:34.620 align:start position:0% to go into a little bit about the a 00:02:34.620 --> 00:02:36.410 align:start position:0% to go into a little bit about the a couple<00:02:34.739> of<00:02:34.920> the<00:02:35.040> reasons<00:02:35.340> that<00:02:35.459> we<00:02:35.640> think<00:02:35.819> that 00:02:36.410 --> 00:02:36.420 align:start position:0% couple of the reasons that we think that 00:02:36.420 --> 00:02:39.470 align:start position:0% couple of the reasons that we think that applied<00:02:36.780> ZK<00:02:37.260> is<00:02:37.440> especially<00:02:37.860> as<00:02:38.040> uh<00:02:38.520> important 00:02:39.470 --> 00:02:39.480 align:start position:0% applied ZK is especially as uh important 00:02:39.480 --> 00:02:40.610 align:start position:0% applied ZK is especially as uh important so 00:02:40.610 --> 00:02:40.620 align:start position:0% so 00:02:40.620 --> 00:02:42.650 align:start position:0% so um there's<00:02:41.040> two<00:02:41.220> concrete<00:02:41.700> reasons<00:02:42.120> that<00:02:42.540> I 00:02:42.650 --> 00:02:42.660 align:start position:0% um there's two concrete reasons that I 00:02:42.660 --> 00:02:44.750 align:start position:0% um there's two concrete reasons that I think<00:02:42.780> are<00:02:43.019> especially<00:02:43.379> compelling<00:02:43.920> in<00:02:44.519> terms 00:02:44.750 --> 00:02:44.760 align:start position:0% think are especially compelling in terms 00:02:44.760 --> 00:02:47.330 align:start position:0% think are especially compelling in terms of<00:02:45.239> why<00:02:45.959> ZK<00:02:46.379> is<00:02:46.560> going<00:02:46.739> to<00:02:46.800> be<00:02:46.920> powerful<00:02:47.160> for 00:02:47.330 --> 00:02:47.340 align:start position:0% of why ZK is going to be powerful for 00:02:47.340 --> 00:02:48.770 align:start position:0% of why ZK is going to be powerful for unlocking<00:02:47.760> the<00:02:47.879> next<00:02:48.000> generation<00:02:48.420> of 00:02:48.770 --> 00:02:48.780 align:start position:0% unlocking the next generation of 00:02:48.780 --> 00:02:50.750 align:start position:0% unlocking the next generation of decentralized<00:02:49.379> applications 00:02:50.750 --> 00:02:50.760 align:start position:0% decentralized applications 00:02:50.760 --> 00:02:53.330 align:start position:0% decentralized applications um<00:02:51.239> and<00:02:52.140> I'll<00:02:52.500> just<00:02:52.680> go<00:02:52.800> through<00:02:52.920> those<00:02:53.160> real 00:02:53.330 --> 00:02:53.340 align:start position:0% um and I'll just go through those real 00:02:53.340 --> 00:02:56.750 align:start position:0% um and I'll just go through those real quick<00:02:53.580> so<00:02:54.300> the<00:02:54.420> first<00:02:54.660> thing<00:02:54.900> is<00:02:55.440> that<00:02:55.860> zero 00:02:56.750 --> 00:02:56.760 align:start position:0% quick so the first thing is that zero 00:02:56.760 --> 00:02:59.449 align:start position:0% quick so the first thing is that zero knowledge<00:02:56.940> cryptography<00:02:57.540> gives<00:02:57.780> us<00:02:58.220> what<00:02:59.220> I 00:02:59.449 --> 00:02:59.459 align:start position:0% knowledge cryptography gives us what I 00:02:59.459 --> 00:03:01.670 align:start position:0% knowledge cryptography gives us what I think<00:02:59.700> of<00:02:59.879> as<00:03:00.180> an<00:03:00.540> expressive<00:03:01.019> language<00:03:01.260> for 00:03:01.670 --> 00:03:01.680 align:start position:0% think of as an expressive language for 00:03:01.680 --> 00:03:02.990 align:start position:0% think of as an expressive language for claims 00:03:02.990 --> 00:03:03.000 align:start position:0% claims 00:03:03.000 --> 00:03:04.790 align:start position:0% claims so<00:03:03.360> what<00:03:03.480> does<00:03:03.660> that<00:03:03.780> mean<00:03:03.959> we'll<00:03:04.500> go<00:03:04.680> through 00:03:04.790 --> 00:03:04.800 align:start position:0% so what does that mean we'll go through 00:03:04.800 --> 00:03:07.729 align:start position:0% so what does that mean we'll go through an<00:03:04.980> example<00:03:05.220> to<00:03:05.519> to<00:03:05.700> get<00:03:05.940> a<00:03:06.120> sense<00:03:06.420> for<00:03:07.319> what<00:03:07.560> an 00:03:07.729 --> 00:03:07.739 align:start position:0% an example to to get a sense for what an 00:03:07.739 --> 00:03:09.110 align:start position:0% an example to to get a sense for what an expressive<00:03:08.099> language<00:03:08.280> for<00:03:08.459> claims<00:03:08.819> looks 00:03:09.110 --> 00:03:09.120 align:start position:0% expressive language for claims looks 00:03:09.120 --> 00:03:12.110 align:start position:0% expressive language for claims looks like<00:03:09.239> let's<00:03:09.900> take<00:03:10.140> the<00:03:10.319> example<00:03:10.739> of<00:03:11.760> um<00:03:11.760> ZK 00:03:12.110 --> 00:03:12.120 align:start position:0% like let's take the example of um ZK 00:03:12.120 --> 00:03:15.170 align:start position:0% like let's take the example of um ZK snarks<00:03:12.720> and<00:03:12.959> group<00:03:13.440> membership<00:03:13.980> proofs<00:03:14.580> in 00:03:15.170 --> 00:03:15.180 align:start position:0% snarks and group membership proofs in 00:03:15.180 --> 00:03:17.509 align:start position:0% snarks and group membership proofs in the<00:03:15.300> context<00:03:15.599> of<00:03:16.019> claims<00:03:16.680> about<00:03:16.980> digital 00:03:17.509 --> 00:03:17.519 align:start position:0% the context of claims about digital 00:03:17.519 --> 00:03:19.190 align:start position:0% the context of claims about digital identity 00:03:19.190 --> 00:03:19.200 align:start position:0% identity 00:03:19.200 --> 00:03:20.690 align:start position:0% identity so 00:03:20.690 --> 00:03:20.700 align:start position:0% so 00:03:20.700 --> 00:03:24.050 align:start position:0% so um<00:03:20.780> the<00:03:21.780> uh<00:03:22.319> simplest<00:03:23.280> kind<00:03:23.459> of<00:03:23.580> identity 00:03:24.050 --> 00:03:24.060 align:start position:0% um the uh simplest kind of identity 00:03:24.060 --> 00:03:26.089 align:start position:0% um the uh simplest kind of identity claim<00:03:24.360> that<00:03:24.480> we<00:03:24.599> have<00:03:24.659> from<00:03:24.840> cryptography<00:03:25.500> and 00:03:26.089 --> 00:03:26.099 align:start position:0% claim that we have from cryptography and 00:03:26.099 --> 00:03:27.470 align:start position:0% claim that we have from cryptography and something<00:03:26.340> that<00:03:26.519> we've<00:03:26.700> known<00:03:26.819> how<00:03:27.060> to<00:03:27.180> do<00:03:27.239> for 00:03:27.470 --> 00:03:27.480 align:start position:0% something that we've known how to do for 00:03:27.480 --> 00:03:30.589 align:start position:0% something that we've known how to do for many<00:03:27.599> decades<00:03:28.019> is<00:03:28.500> prove<00:03:29.340> a<00:03:29.580> statement<00:03:29.940> like<00:03:30.300> I 00:03:30.589 --> 00:03:30.599 align:start position:0% many decades is prove a statement like I 00:03:30.599 --> 00:03:32.990 align:start position:0% many decades is prove a statement like I know<00:03:30.780> a<00:03:30.959> private<00:03:31.200> key<00:03:31.319> corresponding<00:03:32.040> to 00:03:32.990 --> 00:03:33.000 align:start position:0% know a private key corresponding to 00:03:33.000 --> 00:03:34.850 align:start position:0% know a private key corresponding to um someone<00:03:33.239> say<00:03:33.540> like<00:03:33.720> Alice's<00:03:34.260> public<00:03:34.560> key 00:03:34.850 --> 00:03:34.860 align:start position:0% um someone say like Alice's public key 00:03:34.860 --> 00:03:37.309 align:start position:0% um someone say like Alice's public key which<00:03:35.220> implicitly<00:03:35.760> identifies<00:03:36.239> me<00:03:36.540> as<00:03:36.840> Alice 00:03:37.309 --> 00:03:37.319 align:start position:0% which implicitly identifies me as Alice 00:03:37.319 --> 00:03:39.830 align:start position:0% which implicitly identifies me as Alice so<00:03:37.980> this<00:03:38.159> is<00:03:38.220> something<00:03:38.400> that<00:03:38.640> I<00:03:38.760> can<00:03:38.879> do<00:03:39.060> with 00:03:39.830 --> 00:03:39.840 align:start position:0% so this is something that I can do with 00:03:39.840 --> 00:03:42.410 align:start position:0% so this is something that I can do with a<00:03:40.319> digital<00:03:40.680> signature<00:03:41.280> something<00:03:42.000> like<00:03:42.239> you 00:03:42.410 --> 00:03:42.420 align:start position:0% a digital signature something like you 00:03:42.420 --> 00:03:45.289 align:start position:0% a digital signature something like you know<00:03:42.540> RSA<00:03:43.080> or<00:03:43.260> ecdsa<00:03:44.040> the<00:03:44.819> invention<00:03:45.060> of 00:03:45.289 --> 00:03:45.299 align:start position:0% know RSA or ecdsa the invention of 00:03:45.299 --> 00:03:48.589 align:start position:0% know RSA or ecdsa the invention of public<00:03:45.420> key<00:03:45.659> cryptography<00:03:46.319> made<00:03:47.040> uh<00:03:47.819> proof 00:03:48.589 --> 00:03:48.599 align:start position:0% public key cryptography made uh proof 00:03:48.599 --> 00:03:50.809 align:start position:0% public key cryptography made uh proof like<00:03:48.959> this<00:03:49.440> possible<00:03:49.980> or<00:03:50.220> made<00:03:50.400> provable 00:03:50.809 --> 00:03:50.819 align:start position:0% like this possible or made provable 00:03:50.819 --> 00:03:53.449 align:start position:0% like this possible or made provable statements<00:03:51.299> like<00:03:51.480> this<00:03:51.659> possible<00:03:52.159> and<00:03:53.159> this 00:03:53.449 --> 00:03:53.459 align:start position:0% statements like this possible and this 00:03:53.459 --> 00:03:56.210 align:start position:0% statements like this possible and this is<00:03:53.580> infrastructure<00:03:54.180> that<00:03:54.480> underlies<00:03:55.099> so<00:03:56.099> many 00:03:56.210 --> 00:03:56.220 align:start position:0% is infrastructure that underlies so many 00:03:56.220 --> 00:03:58.550 align:start position:0% is infrastructure that underlies so many of<00:03:56.400> the<00:03:56.459> digital<00:03:56.700> systems<00:03:57.180> that<00:03:57.480> we<00:03:57.720> know<00:03:58.319> and 00:03:58.550 --> 00:03:58.560 align:start position:0% of the digital systems that we know and 00:03:58.560 --> 00:04:00.649 align:start position:0% of the digital systems that we know and rely<00:03:58.860> on<00:03:58.920> today<00:03:59.099> including<00:03:59.700> you<00:04:00.120> know<00:04:00.180> secure 00:04:00.649 --> 00:04:00.659 align:start position:0% rely on today including you know secure 00:04:00.659 --> 00:04:03.890 align:start position:0% rely on today including you know secure traffic<00:04:01.159> on<00:04:02.159> the<00:04:02.220> internet<00:04:02.360> as<00:04:03.360> well<00:04:03.540> as 00:04:03.890 --> 00:04:03.900 align:start position:0% traffic on the internet as well as 00:04:03.900 --> 00:04:05.630 align:start position:0% traffic on the internet as well as blockchain<00:04:04.379> systems<00:04:04.860> like<00:04:05.040> ethereum<00:04:05.459> or 00:04:05.630 --> 00:04:05.640 align:start position:0% blockchain systems like ethereum or 00:04:05.640 --> 00:04:09.110 align:start position:0% blockchain systems like ethereum or Bitcoin<00:04:06.120> so<00:04:06.900> going<00:04:07.560> up<00:04:07.739> one<00:04:07.980> level<00:04:08.159> uh<00:04:08.940> in 00:04:09.110 --> 00:04:09.120 align:start position:0% Bitcoin so going up one level uh in 00:04:09.120 --> 00:04:11.630 align:start position:0% Bitcoin so going up one level uh in complexity<00:04:09.599> from<00:04:10.140> the<00:04:10.260> previous<00:04:10.439> slide<00:04:10.920> we 00:04:11.630 --> 00:04:11.640 align:start position:0% complexity from the previous slide we 00:04:11.640 --> 00:04:13.490 align:start position:0% complexity from the previous slide we have<00:04:11.760> claims<00:04:12.180> like<00:04:12.420> I<00:04:12.780> know<00:04:12.959> a<00:04:13.140> private<00:04:13.379> key 00:04:13.490 --> 00:04:13.500 align:start position:0% have claims like I know a private key 00:04:13.500 --> 00:04:16.129 align:start position:0% have claims like I know a private key corresponding<00:04:14.220> to<00:04:14.580> one<00:04:15.299> of<00:04:15.420> the<00:04:15.599> public<00:04:15.720> keys 00:04:16.129 --> 00:04:16.139 align:start position:0% corresponding to one of the public keys 00:04:16.139 --> 00:04:17.569 align:start position:0% corresponding to one of the public keys in<00:04:16.260> a<00:04:16.380> group<00:04:16.500> so<00:04:16.680> for<00:04:16.859> example<00:04:17.040> I<00:04:17.280> know<00:04:17.340> a 00:04:17.569 --> 00:04:17.579 align:start position:0% in a group so for example I know a 00:04:17.579 --> 00:04:18.770 align:start position:0% in a group so for example I know a private<00:04:17.760> key<00:04:17.880> corresponding<00:04:18.359> to<00:04:18.479> one<00:04:18.660> of 00:04:18.770 --> 00:04:18.780 align:start position:0% private key corresponding to one of 00:04:18.780 --> 00:04:22.310 align:start position:0% private key corresponding to one of Alice<00:04:19.139> Bob<00:04:19.739> or<00:04:20.220> Charlie's<00:04:20.760> public<00:04:21.120> keys<00:04:21.660> this 00:04:22.310 --> 00:04:22.320 align:start position:0% Alice Bob or Charlie's public keys this 00:04:22.320 --> 00:04:23.810 align:start position:0% Alice Bob or Charlie's public keys this kind<00:04:22.440> of<00:04:22.560> claim<00:04:22.800> is<00:04:22.919> commonly<00:04:23.340> referred<00:04:23.639> to<00:04:23.699> in 00:04:23.810 --> 00:04:23.820 align:start position:0% kind of claim is commonly referred to in 00:04:23.820 --> 00:04:26.629 align:start position:0% kind of claim is commonly referred to in the<00:04:23.940> literature<00:04:24.300> as<00:04:24.540> a<00:04:25.320> group<00:04:25.500> signature<00:04:26.100> or<00:04:26.400> a 00:04:26.629 --> 00:04:26.639 align:start position:0% the literature as a group signature or a 00:04:26.639 --> 00:04:29.450 align:start position:0% the literature as a group signature or a ring<00:04:26.880> signature<00:04:27.840> we<00:04:28.440> do<00:04:28.560> have<00:04:28.740> cryptographic 00:04:29.450 --> 00:04:29.460 align:start position:0% ring signature we do have cryptographic 00:04:29.460 --> 00:04:31.909 align:start position:0% ring signature we do have cryptographic protocols<00:04:30.000> that<00:04:30.660> are<00:04:30.780> purpose<00:04:31.139> built<00:04:31.560> to 00:04:31.909 --> 00:04:31.919 align:start position:0% protocols that are purpose built to 00:04:31.919 --> 00:04:33.890 align:start position:0% protocols that are purpose built to enable<00:04:32.160> people<00:04:32.400> to<00:04:32.820> generate<00:04:33.240> you<00:04:33.660> know<00:04:33.720> group 00:04:33.890 --> 00:04:33.900 align:start position:0% enable people to generate you know group 00:04:33.900 --> 00:04:37.129 align:start position:0% enable people to generate you know group signatures<00:04:34.320> or<00:04:34.440> ring<00:04:34.680> signatures<00:04:35.419> but<00:04:36.419> they 00:04:37.129 --> 00:04:37.139 align:start position:0% signatures or ring signatures but they 00:04:37.139 --> 00:04:38.990 align:start position:0% signatures or ring signatures but they are<00:04:37.380> again<00:04:37.560> special<00:04:37.919> purpose<00:04:38.280> built<00:04:38.639> for<00:04:38.699> this 00:04:38.990 --> 00:04:39.000 align:start position:0% are again special purpose built for this 00:04:39.000 --> 00:04:41.930 align:start position:0% are again special purpose built for this kind<00:04:39.180> of<00:04:39.360> claim<00:04:39.780> and<00:04:40.500> the<00:04:40.979> math<00:04:41.220> or<00:04:41.639> like<00:04:41.820> the 00:04:41.930 --> 00:04:41.940 align:start position:0% kind of claim and the math or like the 00:04:41.940 --> 00:04:43.550 align:start position:0% kind of claim and the math or like the cryptographic<00:04:42.540> protocols<00:04:42.900> that<00:04:43.139> make<00:04:43.259> these 00:04:43.550 --> 00:04:43.560 align:start position:0% cryptographic protocols that make these 00:04:43.560 --> 00:04:46.030 align:start position:0% cryptographic protocols that make these sorts<00:04:43.740> of<00:04:43.800> claims<00:04:44.100> possible<00:04:44.460> are<00:04:45.240> oftentimes 00:04:46.030 --> 00:04:46.040 align:start position:0% sorts of claims possible are oftentimes 00:04:46.040 --> 00:04:49.010 align:start position:0% sorts of claims possible are oftentimes incompatible<00:04:47.040> with<00:04:47.940> the<00:04:48.419> math<00:04:48.600> used<00:04:48.840> for 00:04:49.010 --> 00:04:49.020 align:start position:0% incompatible with the math used for 00:04:49.020 --> 00:04:52.249 align:start position:0% incompatible with the math used for ordinary<00:04:49.440> signature<00:04:49.919> schemes<00:04:50.300> so<00:04:51.300> you<00:04:52.199> know 00:04:52.249 --> 00:04:52.259 align:start position:0% ordinary signature schemes so you know 00:04:52.259 --> 00:04:53.210 align:start position:0% ordinary signature schemes so you know we<00:04:52.320> figured<00:04:52.560> out<00:04:52.620> how<00:04:52.740> to<00:04:52.860> do<00:04:52.919> these<00:04:53.100> group 00:04:53.210 --> 00:04:53.220 align:start position:0% we figured out how to do these group 00:04:53.220 --> 00:04:55.430 align:start position:0% we figured out how to do these group signature<00:04:53.699> schemes<00:04:54.000> a<00:04:54.180> few<00:04:54.300> years<00:04:54.479> after<00:04:55.080> we 00:04:55.430 --> 00:04:55.440 align:start position:0% signature schemes a few years after we 00:04:55.440 --> 00:04:57.050 align:start position:0% signature schemes a few years after we figured<00:04:55.680> out<00:04:55.740> how<00:04:55.860> to<00:04:55.979> do<00:04:56.100> digital<00:04:56.639> signatures 00:04:57.050 --> 00:04:57.060 align:start position:0% figured out how to do digital signatures 00:04:57.060 --> 00:04:58.030 align:start position:0% figured out how to do digital signatures in<00:04:57.300> general 00:04:58.030 --> 00:04:58.040 align:start position:0% in general 00:04:58.040 --> 00:05:00.590 align:start position:0% in general however<00:04:59.040> it<00:04:59.340> is<00:04:59.520> the<00:04:59.699> case<00:04:59.820> that<00:05:00.120> in<00:05:00.300> order<00:05:00.419> to 00:05:00.590 --> 00:05:00.600 align:start position:0% however it is the case that in order to 00:05:00.600 --> 00:05:02.270 align:start position:0% however it is the case that in order to make<00:05:00.720> claims<00:05:01.080> like<00:05:01.259> these<00:05:01.560> or<00:05:01.860> in<00:05:02.040> order<00:05:02.160> to 00:05:02.270 --> 00:05:02.280 align:start position:0% make claims like these or in order to 00:05:02.280 --> 00:05:04.670 align:start position:0% make claims like these or in order to build<00:05:02.520> up<00:05:02.759> a<00:05:03.300> system<00:05:03.479> or<00:05:03.840> a<00:05:04.020> network<00:05:04.139> in<00:05:04.440> which 00:05:04.670 --> 00:05:04.680 align:start position:0% build up a system or a network in which 00:05:04.680 --> 00:05:06.890 align:start position:0% build up a system or a network in which people<00:05:04.860> can<00:05:05.040> make<00:05:05.220> these<00:05:05.460> claims<00:05:05.759> you<00:05:06.660> have<00:05:06.780> to 00:05:06.890 --> 00:05:06.900 align:start position:0% people can make these claims you have to 00:05:06.900 --> 00:05:08.870 align:start position:0% people can make these claims you have to build<00:05:07.139> uh<00:05:07.740> you<00:05:07.860> have<00:05:07.979> to<00:05:08.040> bootstrap<00:05:08.460> like<00:05:08.639> an 00:05:08.870 --> 00:05:08.880 align:start position:0% build uh you have to bootstrap like an 00:05:08.880 --> 00:05:10.430 align:start position:0% build uh you have to bootstrap like an entirely<00:05:09.300> new 00:05:10.430 --> 00:05:10.440 align:start position:0% entirely new 00:05:10.440 --> 00:05:11.930 align:start position:0% entirely new um<00:05:10.500> you<00:05:10.680> know<00:05:10.740> key<00:05:10.919> registry<00:05:11.460> you<00:05:11.759> have<00:05:11.880> to 00:05:11.930 --> 00:05:11.940 align:start position:0% um you know key registry you have to 00:05:11.940 --> 00:05:14.090 align:start position:0% um you know key registry you have to build<00:05:12.120> a<00:05:12.360> different<00:05:12.540> uh<00:05:13.440> key<00:05:13.680> generation 00:05:14.090 --> 00:05:14.100 align:start position:0% build a different uh key generation 00:05:14.100 --> 00:05:15.710 align:start position:0% build a different uh key generation algorithm<00:05:14.699> and<00:05:14.880> you<00:05:15.000> have<00:05:15.120> to<00:05:15.240> popularize 00:05:15.710 --> 00:05:15.720 align:start position:0% algorithm and you have to popularize 00:05:15.720 --> 00:05:19.310 align:start position:0% algorithm and you have to popularize that<00:05:15.960> so<00:05:16.680> you<00:05:17.520> know<00:05:17.580> the<00:05:18.360> math<00:05:18.600> involved<00:05:19.139> in 00:05:19.310 --> 00:05:19.320 align:start position:0% that so you know the math involved in 00:05:19.320 --> 00:05:20.810 align:start position:0% that so you know the math involved in making<00:05:19.500> a<00:05:19.620> claim<00:05:19.860> like<00:05:19.979> this<00:05:20.100> can<00:05:20.280> be<00:05:20.400> can<00:05:20.639> be 00:05:20.810 --> 00:05:20.820 align:start position:0% making a claim like this can be can be 00:05:20.820 --> 00:05:22.490 align:start position:0% making a claim like this can be can be incompatible<00:05:21.360> and<00:05:21.660> require<00:05:21.780> you<00:05:22.080> to<00:05:22.259> sort<00:05:22.440> of 00:05:22.490 --> 00:05:22.500 align:start position:0% incompatible and require you to sort of 00:05:22.500 --> 00:05:23.990 align:start position:0% incompatible and require you to sort of move<00:05:22.800> to<00:05:23.039> an<00:05:23.160> entirely<00:05:23.460> different<00:05:23.639> system 00:05:23.990 --> 00:05:24.000 align:start position:0% move to an entirely different system 00:05:24.000 --> 00:05:26.810 align:start position:0% move to an entirely different system than<00:05:24.539> if<00:05:24.720> you<00:05:24.900> want<00:05:25.139> to<00:05:25.560> uh<00:05:25.979> you<00:05:26.220> know 00:05:26.810 --> 00:05:26.820 align:start position:0% than if you want to uh you know 00:05:26.820 --> 00:05:29.390 align:start position:0% than if you want to uh you know uh<00:05:27.660> use<00:05:28.199> systems<00:05:28.740> that<00:05:28.800> allow<00:05:29.039> you<00:05:29.160> to<00:05:29.280> make 00:05:29.390 --> 00:05:29.400 align:start position:0% uh use systems that allow you to make 00:05:29.400 --> 00:05:31.670 align:start position:0% uh use systems that allow you to make claims<00:05:29.820> like<00:05:30.000> this<00:05:30.240> so<00:05:30.960> one<00:05:31.259> thing<00:05:31.380> that<00:05:31.500> I 00:05:31.670 --> 00:05:31.680 align:start position:0% claims like this so one thing that I 00:05:31.680 --> 00:05:34.249 align:start position:0% claims like this so one thing that I want<00:05:31.740> to<00:05:31.860> note<00:05:32.039> is<00:05:32.520> that<00:05:32.880> today 00:05:34.249 --> 00:05:34.259 align:start position:0% want to note is that today 00:05:34.259 --> 00:05:37.670 align:start position:0% want to note is that today um however<00:05:34.620> we<00:05:35.160> have<00:05:35.460> uh<00:05:36.419> another<00:05:36.960> much 00:05:37.670 --> 00:05:37.680 align:start position:0% um however we have uh another much 00:05:37.680 --> 00:05:40.790 align:start position:0% um however we have uh another much easier<00:05:38.039> way<00:05:38.340> of<00:05:39.180> uh<00:05:39.780> enabling<00:05:40.199> these<00:05:40.500> kinds<00:05:40.740> of 00:05:40.790 --> 00:05:40.800 align:start position:0% easier way of uh enabling these kinds of 00:05:40.800 --> 00:05:43.850 align:start position:0% easier way of uh enabling these kinds of claims<00:05:41.160> and<00:05:41.460> a<00:05:41.820> manner<00:05:42.360> which<00:05:42.900> a<00:05:43.139> way<00:05:43.440> which<00:05:43.620> is 00:05:43.850 --> 00:05:43.860 align:start position:0% claims and a manner which a way which is 00:05:43.860 --> 00:05:46.010 align:start position:0% claims and a manner which a way which is you<00:05:44.220> know<00:05:44.280> actually<00:05:44.460> compatible<00:05:45.120> with 00:05:46.010 --> 00:05:46.020 align:start position:0% you know actually compatible with 00:05:46.020 --> 00:05:47.930 align:start position:0% you know actually compatible with systems<00:05:46.680> for<00:05:47.039> proving<00:05:47.460> the<00:05:47.520> first<00:05:47.639> kind<00:05:47.820> of 00:05:47.930 --> 00:05:47.940 align:start position:0% systems for proving the first kind of 00:05:47.940 --> 00:05:51.710 align:start position:0% systems for proving the first kind of claim<00:05:48.180> so<00:05:48.419> with<00:05:49.139> DK<00:05:49.560> snarks<00:05:50.160> the<00:05:51.060> problem<00:05:51.300> of 00:05:51.710 --> 00:05:51.720 align:start position:0% claim so with DK snarks the problem of 00:05:51.720 --> 00:05:53.689 align:start position:0% claim so with DK snarks the problem of building<00:05:52.080> a<00:05:52.740> system<00:05:52.919> that<00:05:53.220> allows<00:05:53.460> you<00:05:53.520> to 00:05:53.689 --> 00:05:53.699 align:start position:0% building a system that allows you to 00:05:53.699 --> 00:05:55.550 align:start position:0% building a system that allows you to make<00:05:53.820> these<00:05:54.120> kinds<00:05:54.360> of<00:05:54.419> claims<00:05:54.780> from<00:05:55.259> A<00:05:55.380> system 00:05:55.550 --> 00:05:55.560 align:start position:0% make these kinds of claims from A system 00:05:55.560 --> 00:05:57.409 align:start position:0% make these kinds of claims from A system that<00:05:55.860> allows<00:05:56.160> you<00:05:56.280> to<00:05:56.460> make<00:05:56.639> these<00:05:57.180> kinds<00:05:57.360> of 00:05:57.409 --> 00:05:57.419 align:start position:0% that allows you to make these kinds of 00:05:57.419 --> 00:05:59.450 align:start position:0% that allows you to make these kinds of claims<00:05:57.780> is<00:05:58.440> actually<00:05:58.680> a<00:05:59.039> really<00:05:59.160> simple 00:05:59.450 --> 00:05:59.460 align:start position:0% claims is actually a really simple 00:05:59.460 --> 00:06:02.330 align:start position:0% claims is actually a really simple essentially<00:06:00.300> two-line<00:06:01.020> code<00:06:01.320> change<00:06:01.620> in<00:06:01.919> a<00:06:02.039> ZK 00:06:02.330 --> 00:06:02.340 align:start position:0% essentially two-line code change in a ZK 00:06:02.340 --> 00:06:04.310 align:start position:0% essentially two-line code change in a ZK circuit<00:06:02.880> so<00:06:03.240> rather<00:06:03.479> than<00:06:03.600> having<00:06:03.780> to<00:06:04.020> invent 00:06:04.310 --> 00:06:04.320 align:start position:0% circuit so rather than having to invent 00:06:04.320 --> 00:06:06.110 align:start position:0% circuit so rather than having to invent an<00:06:04.740> entirely<00:06:05.039> new<00:06:05.160> mathematical<00:06:05.639> protocol<00:06:05.940> or 00:06:06.110 --> 00:06:06.120 align:start position:0% an entirely new mathematical protocol or 00:06:06.120 --> 00:06:08.510 align:start position:0% an entirely new mathematical protocol or new<00:06:06.360> key<00:06:06.539> generation<00:06:06.900> algorithm<00:06:07.500> if<00:06:08.100> I<00:06:08.220> have<00:06:08.340> a 00:06:08.510 --> 00:06:08.520 align:start position:0% new key generation algorithm if I have a 00:06:08.520 --> 00:06:11.210 align:start position:0% new key generation algorithm if I have a primitive<00:06:08.880> that<00:06:09.060> allows<00:06:09.300> me<00:06:09.419> to<00:06:09.660> prove<00:06:10.139> in<00:06:10.979> a 00:06:11.210 --> 00:06:11.220 align:start position:0% primitive that allows me to prove in a 00:06:11.220 --> 00:06:14.390 align:start position:0% primitive that allows me to prove in a ZK<00:06:11.580> circuit<00:06:12.060> that<00:06:12.780> I<00:06:13.139> possess<00:06:13.620> a<00:06:13.979> public<00:06:14.100> key 00:06:14.390 --> 00:06:14.400 align:start position:0% ZK circuit that I possess a public key 00:06:14.400 --> 00:06:16.270 align:start position:0% ZK circuit that I possess a public key corresponding<00:06:15.180> to<00:06:15.360> some<00:06:15.600> private<00:06:16.020> secret 00:06:16.270 --> 00:06:16.280 align:start position:0% corresponding to some private secret 00:06:16.280 --> 00:06:18.950 align:start position:0% corresponding to some private secret then<00:06:17.280> what<00:06:17.460> I<00:06:17.580> can<00:06:17.699> do<00:06:17.880> is<00:06:18.240> I<00:06:18.419> can<00:06:18.539> construct<00:06:18.780> a 00:06:18.950 --> 00:06:18.960 align:start position:0% then what I can do is I can construct a 00:06:18.960 --> 00:06:21.529 align:start position:0% then what I can do is I can construct a ZK<00:06:19.259> circuit<00:06:19.620> that<00:06:19.740> says<00:06:19.979> I<00:06:20.699> know<00:06:20.940> some<00:06:21.300> public 00:06:21.529 --> 00:06:21.539 align:start position:0% ZK circuit that says I know some public 00:06:21.539 --> 00:06:24.710 align:start position:0% ZK circuit that says I know some public key<00:06:21.919> corresponding<00:06:22.919> to<00:06:23.160> some<00:06:23.940> secret<00:06:24.180> private 00:06:24.710 --> 00:06:24.720 align:start position:0% key corresponding to some secret private 00:06:24.720 --> 00:06:26.330 align:start position:0% key corresponding to some secret private key 00:06:26.330 --> 00:06:26.340 align:start position:0% key 00:06:26.340 --> 00:06:28.309 align:start position:0% key um<00:06:26.400> I'm<00:06:26.759> going<00:06:26.880> to<00:06:27.000> keep<00:06:27.180> that<00:06:27.539> public<00:06:27.840> key 00:06:28.309 --> 00:06:28.319 align:start position:0% um I'm going to keep that public key 00:06:28.319 --> 00:06:29.570 align:start position:0% um I'm going to keep that public key Secret 00:06:29.570 --> 00:06:29.580 align:start position:0% Secret 00:06:29.580 --> 00:06:33.170 align:start position:0% Secret and<00:06:30.360> uh<00:06:31.080> that<00:06:31.560> public<00:06:31.740> key<00:06:32.039> minus<00:06:32.639> hash<00:06:32.880> one 00:06:33.170 --> 00:06:33.180 align:start position:0% and uh that public key minus hash one 00:06:33.180 --> 00:06:35.330 align:start position:0% and uh that public key minus hash one times<00:06:33.780> public<00:06:34.259> key<00:06:34.500> minus<00:06:34.800> hash<00:06:34.979> two<00:06:35.160> times 00:06:35.330 --> 00:06:35.340 align:start position:0% times public key minus hash two times 00:06:35.340 --> 00:06:37.249 align:start position:0% times public key minus hash two times that<00:06:35.520> public<00:06:35.699> key<00:06:35.880> minus<00:06:36.180> hash<00:06:36.360> three<00:06:36.539> equals 00:06:37.249 --> 00:06:37.259 align:start position:0% that public key minus hash three equals 00:06:37.259 --> 00:06:40.189 align:start position:0% that public key minus hash three equals zero<00:06:37.680> so<00:06:38.220> if<00:06:38.880> I<00:06:39.120> can<00:06:39.240> prove<00:06:39.539> all<00:06:39.720> of<00:06:39.840> this<00:06:39.960> in 00:06:40.189 --> 00:06:40.199 align:start position:0% zero so if I can prove all of this in 00:06:40.199 --> 00:06:41.749 align:start position:0% zero so if I can prove all of this in zero<00:06:40.560> knowledge<00:06:40.800> what<00:06:41.160> I'm<00:06:41.340> effectively 00:06:41.749 --> 00:06:41.759 align:start position:0% zero knowledge what I'm effectively 00:06:41.759 --> 00:06:43.749 align:start position:0% zero knowledge what I'm effectively proving<00:06:42.180> is<00:06:42.660> that<00:06:42.840> I<00:06:43.020> know<00:06:43.139> a<00:06:43.319> private<00:06:43.560> key 00:06:43.749 --> 00:06:43.759 align:start position:0% proving is that I know a private key 00:06:43.759 --> 00:06:47.210 align:start position:0% proving is that I know a private key corresponding<00:06:44.759> to<00:06:45.300> one<00:06:46.020> of<00:06:46.259> these<00:06:46.620> three<00:06:46.800> you 00:06:47.210 --> 00:06:47.220 align:start position:0% corresponding to one of these three you 00:06:47.220 --> 00:06:49.129 align:start position:0% corresponding to one of these three you know<00:06:47.280> public<00:06:47.460> commitments<00:06:48.060> hash<00:06:48.479> one<00:06:48.720> hash 00:06:49.129 --> 00:06:49.139 align:start position:0% know public commitments hash one hash 00:06:49.139 --> 00:06:51.230 align:start position:0% know public commitments hash one hash two<00:06:49.319> or<00:06:49.919> hash<00:06:50.160> three 00:06:51.230 --> 00:06:51.240 align:start position:0% two or hash three 00:06:51.240 --> 00:06:52.730 align:start position:0% two or hash three so 00:06:52.730 --> 00:06:52.740 align:start position:0% so 00:06:52.740 --> 00:06:55.070 align:start position:0% so um<00:06:52.800> this<00:06:53.520> way<00:06:53.639> I<00:06:54.000> now<00:06:54.120> have<00:06:54.300> this<00:06:54.539> system<00:06:54.780> which 00:06:55.070 --> 00:06:55.080 align:start position:0% um this way I now have this system which 00:06:55.080 --> 00:06:56.830 align:start position:0% um this way I now have this system which uses<00:06:55.319> the<00:06:55.500> exact<00:06:55.740> same<00:06:55.919> key<00:06:56.220> generation 00:06:56.830 --> 00:06:56.840 align:start position:0% uses the exact same key generation 00:06:56.840 --> 00:06:59.689 align:start position:0% uses the exact same key generation algorithm<00:06:57.840> or<00:06:57.960> key<00:06:58.199> generation<00:06:58.500> strategy<00:06:59.039> as 00:06:59.689 --> 00:06:59.699 align:start position:0% algorithm or key generation strategy as 00:06:59.699 --> 00:07:01.430 align:start position:0% algorithm or key generation strategy as a<00:07:00.000> system<00:07:00.180> that<00:07:00.419> allows<00:07:00.720> me<00:07:00.840> to<00:07:01.139> you<00:07:01.380> know 00:07:01.430 --> 00:07:01.440 align:start position:0% a system that allows me to you know 00:07:01.440 --> 00:07:02.930 align:start position:0% a system that allows me to you know simply<00:07:01.740> prove<00:07:02.039> that<00:07:02.160> I<00:07:02.340> know<00:07:02.520> the<00:07:02.639> private<00:07:02.819> key 00:07:02.930 --> 00:07:02.940 align:start position:0% simply prove that I know the private key 00:07:02.940 --> 00:07:05.390 align:start position:0% simply prove that I know the private key corresponding<00:07:03.419> to<00:07:03.539> Alice's<00:07:04.139> public<00:07:04.319> key<00:07:04.560> and 00:07:05.390 --> 00:07:05.400 align:start position:0% corresponding to Alice's public key and 00:07:05.400 --> 00:07:07.070 align:start position:0% corresponding to Alice's public key and we've<00:07:05.580> turned<00:07:05.940> essentially<00:07:06.360> this<00:07:06.600> problem<00:07:06.840> of 00:07:07.070 --> 00:07:07.080 align:start position:0% we've turned essentially this problem of 00:07:07.080 --> 00:07:09.830 align:start position:0% we've turned essentially this problem of Building<00:07:07.259> Group<00:07:07.560> signatures<00:07:08.100> from<00:07:08.880> a<00:07:09.419> math 00:07:09.830 --> 00:07:09.840 align:start position:0% Building Group signatures from a math 00:07:09.840 --> 00:07:11.390 align:start position:0% Building Group signatures from a math problem<00:07:10.139> where<00:07:10.740> we<00:07:10.919> have<00:07:11.039> to<00:07:11.100> go<00:07:11.220> to<00:07:11.280> a 00:07:11.390 --> 00:07:11.400 align:start position:0% problem where we have to go to a 00:07:11.400 --> 00:07:12.529 align:start position:0% problem where we have to go to a cryptographer<00:07:11.880> they<00:07:12.000> have<00:07:12.060> to<00:07:12.180> write<00:07:12.240> us<00:07:12.419> a 00:07:12.529 --> 00:07:12.539 align:start position:0% cryptographer they have to write us a 00:07:12.539 --> 00:07:14.749 align:start position:0% cryptographer they have to write us a paper<00:07:12.660> I'll<00:07:12.900> do<00:07:13.080> all<00:07:13.199> this<00:07:13.380> stuff<00:07:13.580> bootstrap<00:07:14.580> a 00:07:14.749 --> 00:07:14.759 align:start position:0% paper I'll do all this stuff bootstrap a 00:07:14.759 --> 00:07:16.550 align:start position:0% paper I'll do all this stuff bootstrap a new<00:07:14.880> key<00:07:15.060> registry<00:07:15.479> into<00:07:15.900> essentially<00:07:16.319> a 00:07:16.550 --> 00:07:16.560 align:start position:0% new key registry into essentially a 00:07:16.560 --> 00:07:18.290 align:start position:0% new key registry into essentially a programming<00:07:16.919> task<00:07:17.160> that 00:07:18.290 --> 00:07:18.300 align:start position:0% programming task that 00:07:18.300 --> 00:07:19.969 align:start position:0% programming task that um you<00:07:18.539> know<00:07:18.600> any<00:07:18.840> developer<00:07:19.319> familiar<00:07:19.740> would 00:07:19.969 --> 00:07:19.979 align:start position:0% um you know any developer familiar would 00:07:19.979 --> 00:07:22.010 align:start position:0% um you know any developer familiar would say<00:07:20.220> Circle<00:07:20.580> can<00:07:20.940> carry<00:07:21.180> out<00:07:21.300> okay<00:07:21.780> so 00:07:22.010 --> 00:07:22.020 align:start position:0% say Circle can carry out okay so 00:07:22.020 --> 00:07:23.510 align:start position:0% say Circle can carry out okay so slightly<00:07:22.440> more<00:07:22.560> complicated<00:07:22.979> than<00:07:23.160> this<00:07:23.340> we 00:07:23.510 --> 00:07:23.520 align:start position:0% slightly more complicated than this we 00:07:23.520 --> 00:07:26.029 align:start position:0% slightly more complicated than this we can<00:07:23.639> go<00:07:23.759> a<00:07:23.880> level<00:07:24.120> even<00:07:24.539> further<00:07:24.900> up<00:07:25.039> and 00:07:26.029 --> 00:07:26.039 align:start position:0% can go a level even further up and 00:07:26.039 --> 00:07:27.830 align:start position:0% can go a level even further up and consider<00:07:26.400> augmentations<00:07:27.060> to<00:07:27.300> this<00:07:27.539> protocol 00:07:27.830 --> 00:07:27.840 align:start position:0% consider augmentations to this protocol 00:07:27.840 --> 00:07:29.930 align:start position:0% consider augmentations to this protocol such<00:07:28.800> as<00:07:28.979> I<00:07:29.220> know<00:07:29.340> a<00:07:29.520> private<00:07:29.759> key 00:07:29.930 --> 00:07:29.940 align:start position:0% such as I know a private key 00:07:29.940 --> 00:07:31.550 align:start position:0% such as I know a private key corresponding<00:07:30.360> to<00:07:30.479> one<00:07:30.780> of<00:07:30.900> Alice<00:07:31.199> bobbert 00:07:31.550 --> 00:07:31.560 align:start position:0% corresponding to one of Alice bobbert 00:07:31.560 --> 00:07:34.249 align:start position:0% corresponding to one of Alice bobbert Charlie's<00:07:31.979> public<00:07:32.099> keys<00:07:32.580> and<00:07:33.360> the<00:07:33.960> other<00:07:34.020> two 00:07:34.249 --> 00:07:34.259 align:start position:0% Charlie's public keys and the other two 00:07:34.259 --> 00:07:37.790 align:start position:0% Charlie's public keys and the other two either<00:07:34.680> can<00:07:35.520> or<00:07:36.120> cannot<00:07:36.840> prove<00:07:37.380> that<00:07:37.500> they<00:07:37.680> did 00:07:37.790 --> 00:07:37.800 align:start position:0% either can or cannot prove that they did 00:07:37.800 --> 00:07:39.650 align:start position:0% either can or cannot prove that they did not<00:07:37.979> generate<00:07:38.400> this<00:07:38.580> message<00:07:38.759> so<00:07:39.240> sometimes 00:07:39.650 --> 00:07:39.660 align:start position:0% not generate this message so sometimes 00:07:39.660 --> 00:07:41.330 align:start position:0% not generate this message so sometimes this<00:07:39.900> is<00:07:40.020> this<00:07:40.319> property<00:07:40.620> is<00:07:40.740> called<00:07:40.919> by 00:07:41.330 --> 00:07:41.340 align:start position:0% this is this property is called by 00:07:41.340 --> 00:07:43.370 align:start position:0% this is this property is called by various<00:07:41.940> different<00:07:42.120> names<00:07:42.840> um<00:07:42.840> some<00:07:43.020> call<00:07:43.259> it 00:07:43.370 --> 00:07:43.380 align:start position:0% various different names um some call it 00:07:43.380 --> 00:07:46.309 align:start position:0% various different names um some call it like<00:07:43.440> disavowel<00:07:44.220> so<00:07:44.759> as<00:07:45.539> an<00:07:45.660> example<00:07:45.960> like 00:07:46.309 --> 00:07:46.319 align:start position:0% like disavowel so as an example like 00:07:46.319 --> 00:07:48.110 align:start position:0% like disavowel so as an example like suppose<00:07:46.800> I'm<00:07:46.979> Bob<00:07:47.160> and<00:07:47.460> I<00:07:47.580> generate<00:07:47.880> a 00:07:48.110 --> 00:07:48.120 align:start position:0% suppose I'm Bob and I generate a 00:07:48.120 --> 00:07:51.170 align:start position:0% suppose I'm Bob and I generate a signature<00:07:48.539> that<00:07:49.319> is<00:07:49.620> uh<00:07:50.340> either<00:07:50.580> coming<00:07:50.880> from 00:07:51.170 --> 00:07:51.180 align:start position:0% signature that is uh either coming from 00:07:51.180 --> 00:07:53.450 align:start position:0% signature that is uh either coming from uh<00:07:51.660> you<00:07:51.840> know<00:07:51.960> you<00:07:52.199> can<00:07:52.380> see<00:07:52.620> is<00:07:52.979> coming<00:07:53.160> from 00:07:53.450 --> 00:07:53.460 align:start position:0% uh you know you can see is coming from 00:07:53.460 --> 00:07:56.089 align:start position:0% uh you know you can see is coming from one<00:07:53.699> of<00:07:53.880> Alice<00:07:54.240> Bob<00:07:54.599> or<00:07:54.960> Charlie 00:07:56.089 --> 00:07:56.099 align:start position:0% one of Alice Bob or Charlie 00:07:56.099 --> 00:07:57.710 align:start position:0% one of Alice Bob or Charlie um Alice<00:07:56.580> or<00:07:56.759> Charlie<00:07:56.940> might<00:07:57.360> be<00:07:57.479> able<00:07:57.599> to 00:07:57.710 --> 00:07:57.720 align:start position:0% um Alice or Charlie might be able to 00:07:57.720 --> 00:08:00.469 align:start position:0% um Alice or Charlie might be able to generate<00:07:58.020> a<00:07:58.199> proof<00:07:58.560> that<00:07:59.039> uh<00:07:59.759> they<00:08:00.120> did<00:08:00.300> not 00:08:00.469 --> 00:08:00.479 align:start position:0% generate a proof that uh they did not 00:08:00.479 --> 00:08:02.330 align:start position:0% generate a proof that uh they did not create<00:08:00.780> that<00:08:01.139> signature 00:08:02.330 --> 00:08:02.340 align:start position:0% create that signature 00:08:02.340 --> 00:08:03.650 align:start position:0% create that signature so 00:08:03.650 --> 00:08:03.660 align:start position:0% so 00:08:03.660 --> 00:08:05.749 align:start position:0% so um yeah<00:08:04.259> there's<00:08:04.560> cryptographic<00:08:05.460> systems 00:08:05.749 --> 00:08:05.759 align:start position:0% um yeah there's cryptographic systems 00:08:05.759 --> 00:08:08.089 align:start position:0% um yeah there's cryptographic systems that<00:08:05.880> allow<00:08:06.180> you<00:08:06.360> to<00:08:06.599> toggle<00:08:07.440> this<00:08:07.740> property 00:08:08.089 --> 00:08:08.099 align:start position:0% that allow you to toggle this property 00:08:08.099 --> 00:08:10.550 align:start position:0% that allow you to toggle this property on<00:08:08.460> or<00:08:08.819> off<00:08:09.060> uh<00:08:09.720> but<00:08:09.840> again<00:08:09.960> these<00:08:10.259> use<00:08:10.380> new 00:08:10.550 --> 00:08:10.560 align:start position:0% on or off uh but again these use new 00:08:10.560 --> 00:08:11.870 align:start position:0% on or off uh but again these use new math<00:08:10.800> are<00:08:10.979> incompatible<00:08:11.400> with<00:08:11.580> previous 00:08:11.870 --> 00:08:11.880 align:start position:0% math are incompatible with previous 00:08:11.880 --> 00:08:13.730 align:start position:0% math are incompatible with previous systems<00:08:12.479> and<00:08:12.900> are<00:08:13.080> generally<00:08:13.319> fairly 00:08:13.730 --> 00:08:13.740 align:start position:0% systems and are generally fairly 00:08:13.740 --> 00:08:15.110 align:start position:0% systems and are generally fairly difficult<00:08:14.039> to<00:08:14.160> engineer 00:08:15.110 --> 00:08:15.120 align:start position:0% difficult to engineer 00:08:15.120 --> 00:08:17.990 align:start position:0% difficult to engineer again<00:08:15.720> however<00:08:16.080> with<00:08:16.259> the<00:08:16.380> DK<00:08:16.620> snarks<00:08:17.160> this<00:08:17.759> is 00:08:17.990 --> 00:08:18.000 align:start position:0% again however with the DK snarks this is 00:08:18.000 --> 00:08:21.050 align:start position:0% again however with the DK snarks this is a<00:08:18.660> pretty<00:08:18.780> trivial<00:08:19.199> like<00:08:19.620> two<00:08:20.220> line<00:08:20.520> circuit 00:08:21.050 --> 00:08:21.060 align:start position:0% a pretty trivial like two line circuit 00:08:21.060 --> 00:08:22.550 align:start position:0% a pretty trivial like two line circuit code<00:08:21.300> change 00:08:22.550 --> 00:08:22.560 align:start position:0% code change 00:08:22.560 --> 00:08:24.830 align:start position:0% code change um so<00:08:23.340> again<00:08:23.460> we're<00:08:23.699> sort<00:08:23.879> of<00:08:24.000> seeing<00:08:24.360> this 00:08:24.830 --> 00:08:24.840 align:start position:0% um so again we're sort of seeing this 00:08:24.840 --> 00:08:27.770 align:start position:0% um so again we're sort of seeing this idea<00:08:25.139> of<00:08:25.620> this<00:08:26.460> language<00:08:26.699> that<00:08:27.060> allows<00:08:27.360> us<00:08:27.479> to 00:08:27.770 --> 00:08:27.780 align:start position:0% idea of this language that allows us to 00:08:27.780 --> 00:08:29.570 align:start position:0% idea of this language that allows us to build<00:08:28.080> these<00:08:28.620> expressive<00:08:28.979> claims<00:08:29.280> that<00:08:29.460> are 00:08:29.570 --> 00:08:29.580 align:start position:0% build these expressive claims that are 00:08:29.580 --> 00:08:31.730 align:start position:0% build these expressive claims that are compatible<00:08:30.000> with<00:08:30.720> uh<00:08:31.139> you<00:08:31.379> know<00:08:31.440> previous 00:08:31.730 --> 00:08:31.740 align:start position:0% compatible with uh you know previous 00:08:31.740 --> 00:08:33.409 align:start position:0% compatible with uh you know previous claims<00:08:32.159> that<00:08:32.279> other<00:08:32.399> cryptographic<00:08:33.000> systems 00:08:33.409 --> 00:08:33.419 align:start position:0% claims that other cryptographic systems 00:08:33.419 --> 00:08:35.329 align:start position:0% claims that other cryptographic systems will<00:08:33.719> allow<00:08:33.959> us<00:08:34.080> to<00:08:34.200> generate 00:08:35.329 --> 00:08:35.339 align:start position:0% will allow us to generate 00:08:35.339 --> 00:08:37.310 align:start position:0% will allow us to generate and<00:08:35.820> finally<00:08:36.000> we<00:08:36.240> can<00:08:36.300> get<00:08:36.479> to<00:08:36.599> claims<00:08:36.959> you 00:08:37.310 --> 00:08:37.320 align:start position:0% and finally we can get to claims you 00:08:37.320 --> 00:08:38.990 align:start position:0% and finally we can get to claims you know<00:08:37.440> of<00:08:37.680> this<00:08:38.219> level<00:08:38.339> of<00:08:38.580> complexity 00:08:38.990 --> 00:08:39.000 align:start position:0% know of this level of complexity 00:08:39.000 --> 00:08:40.610 align:start position:0% know of this level of complexity something<00:08:39.539> like<00:08:39.779> I<00:08:40.020> know<00:08:40.140> a<00:08:40.320> private<00:08:40.500> key 00:08:40.610 --> 00:08:40.620 align:start position:0% something like I know a private key 00:08:40.620 --> 00:08:42.709 align:start position:0% something like I know a private key corresponding<00:08:41.339> to<00:08:41.520> one<00:08:41.820> of<00:08:41.940> Alice<00:08:42.240> Bob<00:08:42.419> or 00:08:42.709 --> 00:08:42.719 align:start position:0% corresponding to one of Alice Bob or 00:08:42.719 --> 00:08:44.750 align:start position:0% corresponding to one of Alice Bob or Charlie's<00:08:43.200> public<00:08:43.320> keys<00:08:43.800> and<00:08:44.520> I<00:08:44.580> either 00:08:44.750 --> 00:08:44.760 align:start position:0% Charlie's public keys and I either 00:08:44.760 --> 00:08:46.790 align:start position:0% Charlie's public keys and I either possess<00:08:45.180> a<00:08:45.360> signed<00:08:45.600> attestation<00:08:46.080> from<00:08:46.440> one<00:08:46.620> of 00:08:46.790 --> 00:08:46.800 align:start position:0% possess a signed attestation from one of 00:08:46.800 --> 00:08:49.550 align:start position:0% possess a signed attestation from one of David<00:08:47.279> Eve<00:08:47.820> or<00:08:47.940> Fred<00:08:48.240> one<00:08:48.959> of<00:08:49.080> these<00:08:49.200> trusted 00:08:49.550 --> 00:08:49.560 align:start position:0% David Eve or Fred one of these trusted 00:08:49.560 --> 00:08:51.230 align:start position:0% David Eve or Fred one of these trusted you<00:08:49.860> know<00:08:49.920> attestation<00:08:50.399> service<00:08:50.700> providers 00:08:51.230 --> 00:08:51.240 align:start position:0% you know attestation service providers 00:08:51.240 --> 00:08:53.750 align:start position:0% you know attestation service providers or<00:08:51.899> during<00:08:52.140> a<00:08:52.320> block<00:08:52.440> with<00:08:52.680> header<00:08:53.040> X<00:08:53.160> I<00:08:53.519> knew 00:08:53.750 --> 00:08:53.760 align:start position:0% or during a block with header X I knew 00:08:53.760 --> 00:08:55.009 align:start position:0% or during a block with header X I knew the<00:08:53.880> private<00:08:54.060> key<00:08:54.180> corresponding<00:08:54.839> to<00:08:54.899> an 00:08:55.009 --> 00:08:55.019 align:start position:0% the private key corresponding to an 00:08:55.019 --> 00:08:57.170 align:start position:0% the private key corresponding to an account<00:08:55.140> with<00:08:55.380> at<00:08:55.560> least<00:08:55.620> 32<00:08:55.980> eth<00:08:56.399> and<00:08:57.000> you 00:08:57.170 --> 00:08:57.180 align:start position:0% account with at least 32 eth and you 00:08:57.180 --> 00:08:59.750 align:start position:0% account with at least 32 eth and you know<00:08:57.240> dot<00:08:57.480> dot<00:08:57.839> you<00:08:58.019> can<00:08:58.140> kind<00:08:58.260> of<00:08:58.380> compose<00:08:59.100> a 00:08:59.750 --> 00:08:59.760 align:start position:0% know dot dot you can kind of compose a 00:08:59.760 --> 00:09:01.550 align:start position:0% know dot dot you can kind of compose a bunch<00:08:59.820> of<00:08:59.940> arbitrary<00:09:00.540> uh<00:09:01.320> you<00:09:01.500> know 00:09:01.550 --> 00:09:01.560 align:start position:0% bunch of arbitrary uh you know 00:09:01.560 --> 00:09:04.009 align:start position:0% bunch of arbitrary uh you know predicates<00:09:02.040> on<00:09:02.220> this<00:09:02.399> identity<00:09:02.760> claim<00:09:03.180> and<00:09:03.839> I 00:09:04.009 --> 00:09:04.019 align:start position:0% predicates on this identity claim and I 00:09:04.019 --> 00:09:05.030 align:start position:0% predicates on this identity claim and I think<00:09:04.140> it's<00:09:04.260> pretty<00:09:04.440> fair<00:09:04.620> to<00:09:04.740> say<00:09:04.860> that 00:09:05.030 --> 00:09:05.040 align:start position:0% think it's pretty fair to say that 00:09:05.040 --> 00:09:06.530 align:start position:0% think it's pretty fair to say that there's<00:09:05.160> like<00:09:05.339> no<00:09:05.519> cryptographer<00:09:06.180> in<00:09:06.420> the 00:09:06.530 --> 00:09:06.540 align:start position:0% there's like no cryptographer in the 00:09:06.540 --> 00:09:08.870 align:start position:0% there's like no cryptographer in the world<00:09:06.600> who<00:09:06.899> you<00:09:07.080> could<00:09:07.200> go<00:09:07.320> to<00:09:07.500> and<00:09:08.459> ask<00:09:08.640> them 00:09:08.870 --> 00:09:08.880 align:start position:0% world who you could go to and ask them 00:09:08.880 --> 00:09:11.630 align:start position:0% world who you could go to and ask them to<00:09:09.180> build<00:09:09.480> a<00:09:10.440> special<00:09:11.040> purpose<00:09:11.399> new 00:09:11.630 --> 00:09:11.640 align:start position:0% to build a special purpose new 00:09:11.640 --> 00:09:13.009 align:start position:0% to build a special purpose new cryptographic<00:09:12.300> tool<00:09:12.540> that<00:09:12.720> would<00:09:12.779> allow<00:09:12.959> you 00:09:13.009 --> 00:09:13.019 align:start position:0% cryptographic tool that would allow you 00:09:13.019 --> 00:09:15.110 align:start position:0% cryptographic tool that would allow you to<00:09:13.200> prove<00:09:13.440> this<00:09:13.740> specific<00:09:14.100> kind<00:09:14.399> of<00:09:14.459> claim<00:09:14.760> nor 00:09:15.110 --> 00:09:15.120 align:start position:0% to prove this specific kind of claim nor 00:09:15.120 --> 00:09:16.970 align:start position:0% to prove this specific kind of claim nor would<00:09:15.360> it<00:09:15.480> even<00:09:15.600> make<00:09:15.779> sense<00:09:15.959> to<00:09:16.260> but<00:09:16.800> again 00:09:16.970 --> 00:09:16.980 align:start position:0% would it even make sense to but again 00:09:16.980 --> 00:09:19.009 align:start position:0% would it even make sense to but again with<00:09:17.640> DK<00:09:17.940> snarks<00:09:18.360> this<00:09:18.480> actually<00:09:18.660> becomes 00:09:19.009 --> 00:09:19.019 align:start position:0% with DK snarks this actually becomes 00:09:19.019 --> 00:09:21.110 align:start position:0% with DK snarks this actually becomes fairly<00:09:19.380> trivial<00:09:19.740> you<00:09:20.700> have<00:09:20.760> your<00:09:20.940> building 00:09:21.110 --> 00:09:21.120 align:start position:0% fairly trivial you have your building 00:09:21.120 --> 00:09:23.570 align:start position:0% fairly trivial you have your building blocks<00:09:21.600> in<00:09:21.779> ZK<00:09:22.080> circuits<00:09:22.740> for<00:09:23.100> each<00:09:23.279> of<00:09:23.399> these 00:09:23.570 --> 00:09:23.580 align:start position:0% blocks in ZK circuits for each of these 00:09:23.580 --> 00:09:25.850 align:start position:0% blocks in ZK circuits for each of these things<00:09:23.760> you<00:09:24.360> know<00:09:24.420> uh<00:09:25.200> key<00:09:25.380> pre-image 00:09:25.850 --> 00:09:25.860 align:start position:0% things you know uh key pre-image 00:09:25.860 --> 00:09:27.949 align:start position:0% things you know uh key pre-image signature<00:09:26.459> recovery 00:09:27.949 --> 00:09:27.959 align:start position:0% signature recovery 00:09:27.959 --> 00:09:30.650 align:start position:0% signature recovery um proof<00:09:28.800> of<00:09:28.860> inclusion<00:09:29.339> in<00:09:29.940> the<00:09:30.180> ethereum 00:09:30.650 --> 00:09:30.660 align:start position:0% um proof of inclusion in the ethereum 00:09:30.660 --> 00:09:32.690 align:start position:0% um proof of inclusion in the ethereum Merkel<00:09:31.019> Patricia<00:09:31.380> try<00:09:31.620> and<00:09:32.399> then<00:09:32.519> you<00:09:32.640> can 00:09:32.690 --> 00:09:32.700 align:start position:0% Merkel Patricia try and then you can 00:09:32.700 --> 00:09:34.550 align:start position:0% Merkel Patricia try and then you can just<00:09:32.820> put<00:09:33.000> all<00:09:33.180> these<00:09:33.360> together<00:09:33.560> essentially 00:09:34.550 --> 00:09:34.560 align:start position:0% just put all these together essentially 00:09:34.560 --> 00:09:35.690 align:start position:0% just put all these together essentially calling<00:09:34.860> all<00:09:34.980> these<00:09:35.100> like<00:09:35.279> different 00:09:35.690 --> 00:09:35.700 align:start position:0% calling all these like different 00:09:35.700 --> 00:09:37.790 align:start position:0% calling all these like different functions<00:09:36.120> in<00:09:36.300> your<00:09:36.420> ZK<00:09:36.660> circuit<00:09:37.080> code<00:09:37.200> to 00:09:37.790 --> 00:09:37.800 align:start position:0% functions in your ZK circuit code to 00:09:37.800 --> 00:09:40.070 align:start position:0% functions in your ZK circuit code to start<00:09:37.980> building<00:09:38.160> out<00:09:38.339> these<00:09:38.580> claims 00:09:40.070 --> 00:09:40.080 align:start position:0% start building out these claims 00:09:40.080 --> 00:09:43.250 align:start position:0% start building out these claims so<00:09:40.620> another<00:09:40.920> framing<00:09:41.459> of<00:09:41.640> this<00:09:41.940> idea<00:09:42.779> of<00:09:43.080> the 00:09:43.250 --> 00:09:43.260 align:start position:0% so another framing of this idea of the 00:09:43.260 --> 00:09:44.690 align:start position:0% so another framing of this idea of the expressive<00:09:43.680> language<00:09:43.860> for<00:09:44.160> claims<00:09:44.459> is<00:09:44.580> that 00:09:44.690 --> 00:09:44.700 align:start position:0% expressive language for claims is that 00:09:44.700 --> 00:09:46.250 align:start position:0% expressive language for claims is that ZK<00:09:44.940> snarks<00:09:45.360> turn<00:09:45.480> math<00:09:45.720> problems<00:09:46.140> into 00:09:46.250 --> 00:09:46.260 align:start position:0% ZK snarks turn math problems into 00:09:46.260 --> 00:09:48.889 align:start position:0% ZK snarks turn math problems into programming<00:09:46.800> tasks<00:09:47.300> rather<00:09:48.300> than<00:09:48.480> having<00:09:48.720> to 00:09:48.889 --> 00:09:48.899 align:start position:0% programming tasks rather than having to 00:09:48.899 --> 00:09:50.750 align:start position:0% programming tasks rather than having to go<00:09:49.080> to<00:09:49.320> a<00:09:49.560> cryptographer<00:09:50.040> to<00:09:50.220> write<00:09:50.339> you<00:09:50.519> a<00:09:50.640> new 00:09:50.750 --> 00:09:50.760 align:start position:0% go to a cryptographer to write you a new 00:09:50.760 --> 00:09:53.030 align:start position:0% go to a cryptographer to write you a new paper<00:09:51.000> every<00:09:51.660> single<00:09:51.959> time<00:09:52.140> you<00:09:52.440> want<00:09:52.620> a<00:09:52.920> new 00:09:53.030 --> 00:09:53.040 align:start position:0% paper every single time you want a new 00:09:53.040 --> 00:09:56.870 align:start position:0% paper every single time you want a new kind<00:09:53.339> of<00:09:53.519> digital<00:09:54.060> identity<00:09:54.480> claim<00:09:55.040> to<00:09:56.040> exist 00:09:56.870 --> 00:09:56.880 align:start position:0% kind of digital identity claim to exist 00:09:56.880 --> 00:09:59.090 align:start position:0% kind of digital identity claim to exist in<00:09:57.000> the<00:09:57.180> world<00:09:57.240> and<00:09:57.480> be<00:09:57.660> provable<00:09:58.080> you<00:09:58.980> can 00:09:59.090 --> 00:09:59.100 align:start position:0% in the world and be provable you can 00:09:59.100 --> 00:10:01.430 align:start position:0% in the world and be provable you can just<00:09:59.220> have<00:09:59.580> a<00:09:59.760> ZK<00:10:00.060> circuit<00:10:00.540> developer<00:10:00.959> compose 00:10:01.430 --> 00:10:01.440 align:start position:0% just have a ZK circuit developer compose 00:10:01.440 --> 00:10:03.710 align:start position:0% just have a ZK circuit developer compose the<00:10:01.620> right<00:10:01.800> Primitives<00:10:02.279> inside<00:10:02.820> ZK<00:10:03.300> circuit 00:10:03.710 --> 00:10:03.720 align:start position:0% the right Primitives inside ZK circuit 00:10:03.720 --> 00:10:06.230 align:start position:0% the right Primitives inside ZK circuit code<00:10:03.899> okay<00:10:04.500> so<00:10:04.860> cool<00:10:05.100> thing<00:10:05.339> number<00:10:05.519> two<00:10:05.820> which 00:10:06.230 --> 00:10:06.240 align:start position:0% code okay so cool thing number two which 00:10:06.240 --> 00:10:07.850 align:start position:0% code okay so cool thing number two which is<00:10:06.360> closely<00:10:06.839> related<00:10:07.140> to<00:10:07.380> cool<00:10:07.500> thing<00:10:07.680> number 00:10:07.850 --> 00:10:07.860 align:start position:0% is closely related to cool thing number 00:10:07.860 --> 00:10:10.850 align:start position:0% is closely related to cool thing number one<00:10:08.040> is<00:10:08.399> that<00:10:08.640> ZK<00:10:09.240> adds<00:10:09.779> interoperability<00:10:10.560> to 00:10:10.850 --> 00:10:10.860 align:start position:0% one is that ZK adds interoperability to 00:10:10.860 --> 00:10:12.889 align:start position:0% one is that ZK adds interoperability to cryptographic<00:10:11.519> systems<00:10:12.000> so<00:10:12.480> what<00:10:12.600> does<00:10:12.779> this 00:10:12.889 --> 00:10:12.899 align:start position:0% cryptographic systems so what does this 00:10:12.899 --> 00:10:13.610 align:start position:0% cryptographic systems so what does this mean 00:10:13.610 --> 00:10:13.620 align:start position:0% mean 00:10:13.620 --> 00:10:15.650 align:start position:0% mean well 00:10:15.650 --> 00:10:15.660 align:start position:0% well 00:10:15.660 --> 00:10:17.449 align:start position:0% well to<00:10:16.019> explain<00:10:16.200> this<00:10:16.500> first<00:10:16.680> I<00:10:16.980> just<00:10:17.100> want<00:10:17.220> to<00:10:17.339> do 00:10:17.449 --> 00:10:17.459 align:start position:0% to explain this first I just want to do 00:10:17.459 --> 00:10:19.370 align:start position:0% to explain this first I just want to do a<00:10:17.700> quick<00:10:17.760> breakdown<00:10:18.120> between<00:10:18.480> two<00:10:19.019> terms 00:10:19.370 --> 00:10:19.380 align:start position:0% a quick breakdown between two terms 00:10:19.380 --> 00:10:21.769 align:start position:0% a quick breakdown between two terms snark<00:10:19.860> friendly<00:10:20.339> versus<00:10:20.640> snark<00:10:21.240> compatible 00:10:21.769 --> 00:10:21.779 align:start position:0% snark friendly versus snark compatible 00:10:21.779 --> 00:10:24.050 align:start position:0% snark friendly versus snark compatible cryptographic<00:10:22.440> Primitives<00:10:22.860> Stark<00:10:23.700> friendly 00:10:24.050 --> 00:10:24.060 align:start position:0% cryptographic Primitives Stark friendly 00:10:24.060 --> 00:10:26.509 align:start position:0% cryptographic Primitives Stark friendly cryptographic<00:10:24.660> Primitives<00:10:25.140> are 00:10:26.509 --> 00:10:26.519 align:start position:0% cryptographic Primitives are 00:10:26.519 --> 00:10:28.310 align:start position:0% cryptographic Primitives are um you<00:10:26.820> know<00:10:26.880> Primitives<00:10:27.360> like<00:10:27.779> hashing 00:10:28.310 --> 00:10:28.320 align:start position:0% um you know Primitives like hashing 00:10:28.320 --> 00:10:30.530 align:start position:0% um you know Primitives like hashing algorithms<00:10:29.040> or<00:10:29.339> digital<00:10:29.700> signature<00:10:30.180> schemes 00:10:30.530 --> 00:10:30.540 align:start position:0% algorithms or digital signature schemes 00:10:30.540 --> 00:10:32.210 align:start position:0% algorithms or digital signature schemes or<00:10:30.720> encryption<00:10:31.080> algorithms<00:10:31.560> that<00:10:32.040> are 00:10:32.210 --> 00:10:32.220 align:start position:0% or encryption algorithms that are 00:10:32.220 --> 00:10:35.210 align:start position:0% or encryption algorithms that are specifically<00:10:32.580> purpose<00:10:33.000> built<00:10:33.540> for 00:10:35.210 --> 00:10:35.220 align:start position:0% specifically purpose built for 00:10:35.220 --> 00:10:38.090 align:start position:0% specifically purpose built for um<00:10:35.279> to<00:10:35.940> be<00:10:36.060> efficiently<00:10:36.660> provable<00:10:37.140> inside<00:10:37.560> of 00:10:38.090 --> 00:10:38.100 align:start position:0% um to be efficiently provable inside of 00:10:38.100 --> 00:10:40.250 align:start position:0% um to be efficiently provable inside of ZK<00:10:38.459> snark<00:10:38.820> proving<00:10:39.180> systems<00:10:39.600> so<00:10:39.899> for<00:10:40.080> example 00:10:40.250 --> 00:10:40.260 align:start position:0% ZK snark proving systems so for example 00:10:40.260 --> 00:10:42.650 align:start position:0% ZK snark proving systems so for example the<00:10:40.560> Mims<00:10:40.800> here<00:10:40.920> Poseidon<00:10:41.459> hash<00:10:41.700> functions<00:10:42.180> or 00:10:42.650 --> 00:10:42.660 align:start position:0% the Mims here Poseidon hash functions or 00:10:42.660 --> 00:10:45.650 align:start position:0% the Mims here Poseidon hash functions or eddsa<00:10:43.560> signatures 00:10:45.650 --> 00:10:45.660 align:start position:0% eddsa signatures 00:10:45.660 --> 00:10:49.190 align:start position:0% eddsa signatures um<00:10:45.800> these<00:10:46.800> uh<00:10:47.339> cryptographic<00:10:47.880> Primitives<00:10:48.300> uh 00:10:49.190 --> 00:10:49.200 align:start position:0% um these uh cryptographic Primitives uh 00:10:49.200 --> 00:10:51.050 align:start position:0% um these uh cryptographic Primitives uh oftentimes<00:10:49.920> have<00:10:50.160> been<00:10:50.339> invented<00:10:50.820> in<00:10:50.940> the 00:10:51.050 --> 00:10:51.060 align:start position:0% oftentimes have been invented in the 00:10:51.060 --> 00:10:53.509 align:start position:0% oftentimes have been invented in the last<00:10:51.180> couple<00:10:51.360> of<00:10:51.480> years<00:10:51.860> and<00:10:52.860> you<00:10:53.279> know<00:10:53.339> the 00:10:53.509 --> 00:10:53.519 align:start position:0% last couple of years and you know the 00:10:53.519 --> 00:10:55.130 align:start position:0% last couple of years and you know the hope<00:10:53.640> is<00:10:53.880> that<00:10:54.060> with<00:10:54.360> these<00:10:54.540> Primitives<00:10:54.899> we 00:10:55.130 --> 00:10:55.140 align:start position:0% hope is that with these Primitives we 00:10:55.140 --> 00:10:56.449 align:start position:0% hope is that with these Primitives we can<00:10:55.260> move<00:10:55.320> towards<00:10:55.620> a<00:10:55.740> world<00:10:55.860> where<00:10:56.040> we<00:10:56.220> can<00:10:56.339> do 00:10:56.449 --> 00:10:56.459 align:start position:0% can move towards a world where we can do 00:10:56.459 --> 00:10:58.730 align:start position:0% can move towards a world where we can do more<00:10:56.640> and<00:10:56.760> more<00:10:56.880> inside<00:10:57.060> of<00:10:57.360> snarks 00:10:58.730 --> 00:10:58.740 align:start position:0% more and more inside of snarks 00:10:58.740 --> 00:11:01.370 align:start position:0% more and more inside of snarks um<00:10:58.800> however<00:10:59.700> most<00:11:00.540> of<00:11:00.720> the<00:11:00.779> cryptographic 00:11:01.370 --> 00:11:01.380 align:start position:0% um however most of the cryptographic 00:11:01.380 --> 00:11:02.870 align:start position:0% um however most of the cryptographic systems<00:11:01.800> that<00:11:02.040> exist<00:11:02.279> in<00:11:02.459> the<00:11:02.579> world<00:11:02.640> use 00:11:02.870 --> 00:11:02.880 align:start position:0% systems that exist in the world use 00:11:02.880 --> 00:11:05.030 align:start position:0% systems that exist in the world use cryptography<00:11:03.480> that<00:11:03.779> was<00:11:04.079> invented<00:11:04.620> before<00:11:04.800> we 00:11:05.030 --> 00:11:05.040 align:start position:0% cryptography that was invented before we 00:11:05.040 --> 00:11:07.850 align:start position:0% cryptography that was invented before we knew<00:11:05.220> about<00:11:05.339> CK<00:11:05.640> snarks<00:11:06.240> so<00:11:06.899> for<00:11:07.079> example<00:11:07.320> a 00:11:07.850 --> 00:11:07.860 align:start position:0% knew about CK snarks so for example a 00:11:07.860 --> 00:11:09.110 align:start position:0% knew about CK snarks so for example a lot<00:11:07.980> of<00:11:08.040> hash<00:11:08.279> functions<00:11:08.640> use<00:11:08.820> a<00:11:08.940> lot<00:11:09.060> of 00:11:09.110 --> 00:11:09.120 align:start position:0% lot of hash functions use a lot of 00:11:09.120 --> 00:11:11.210 align:start position:0% lot of hash functions use a lot of bitwise<00:11:09.540> operations<00:11:10.079> which<00:11:10.560> are<00:11:10.680> very<00:11:10.860> costly 00:11:11.210 --> 00:11:11.220 align:start position:0% bitwise operations which are very costly 00:11:11.220 --> 00:11:13.310 align:start position:0% bitwise operations which are very costly to<00:11:11.459> do<00:11:11.579> inside<00:11:11.760> of<00:11:12.000> ZK<00:11:12.240> snarks 00:11:13.310 --> 00:11:13.320 align:start position:0% to do inside of ZK snarks 00:11:13.320 --> 00:11:14.630 align:start position:0% to do inside of ZK snarks um and<00:11:13.500> so<00:11:13.620> these<00:11:13.860> these<00:11:14.160> systems<00:11:14.399> are<00:11:14.519> not 00:11:14.630 --> 00:11:14.640 align:start position:0% um and so these these systems are not 00:11:14.640 --> 00:11:16.790 align:start position:0% um and so these these systems are not snark<00:11:15.000> friendly<00:11:15.420> but<00:11:15.899> they<00:11:16.079> are<00:11:16.260> what<00:11:16.500> we<00:11:16.620> have 00:11:16.790 --> 00:11:16.800 align:start position:0% snark friendly but they are what we have 00:11:16.800 --> 00:11:18.290 align:start position:0% snark friendly but they are what we have to<00:11:17.040> work<00:11:17.160> with<00:11:17.339> so<00:11:17.519> for<00:11:17.700> example<00:11:17.880> all<00:11:18.120> the 00:11:18.290 --> 00:11:18.300 align:start position:0% to work with so for example all the 00:11:18.300 --> 00:11:21.290 align:start position:0% to work with so for example all the signatures<00:11:18.779> on<00:11:19.560> uh<00:11:20.160> you<00:11:20.339> know<00:11:20.459> emails<00:11:20.940> signed 00:11:21.290 --> 00:11:21.300 align:start position:0% signatures on uh you know emails signed 00:11:21.300 --> 00:11:22.790 align:start position:0% signatures on uh you know emails signed by<00:11:21.420> mail<00:11:21.600> servers<00:11:22.019> that<00:11:22.140> are<00:11:22.260> being<00:11:22.380> sent<00:11:22.620> out 00:11:22.790 --> 00:11:22.800 align:start position:0% by mail servers that are being sent out 00:11:22.800 --> 00:11:25.130 align:start position:0% by mail servers that are being sent out are<00:11:23.160> not<00:11:23.279> going<00:11:23.399> to<00:11:23.519> be<00:11:23.579> snark<00:11:23.880> friendly 00:11:25.130 --> 00:11:25.140 align:start position:0% are not going to be snark friendly 00:11:25.140 --> 00:11:27.470 align:start position:0% are not going to be snark friendly um<00:11:25.680> signatures 00:11:27.470 --> 00:11:27.480 align:start position:0% um signatures 00:11:27.480 --> 00:11:30.530 align:start position:0% um signatures however<00:11:28.279> we<00:11:29.279> can<00:11:29.459> start<00:11:29.760> to<00:11:30.000> at<00:11:30.120> least<00:11:30.240> connect 00:11:30.530 --> 00:11:30.540 align:start position:0% however we can start to at least connect 00:11:30.540 --> 00:11:32.990 align:start position:0% however we can start to at least connect all<00:11:31.019> of<00:11:31.079> these<00:11:31.320> different<00:11:31.500> snark<00:11:32.220> compatible 00:11:32.990 --> 00:11:33.000 align:start position:0% all of these different snark compatible 00:11:33.000 --> 00:11:34.730 align:start position:0% all of these different snark compatible systems<00:11:33.480> together 00:11:34.730 --> 00:11:34.740 align:start position:0% systems together 00:11:34.740 --> 00:11:37.250 align:start position:0% systems together um<00:11:35.220> by<00:11:36.060> embedding<00:11:36.839> these<00:11:37.079> different 00:11:37.250 --> 00:11:37.260 align:start position:0% um by embedding these different 00:11:37.260 --> 00:11:39.110 align:start position:0% um by embedding these different signature<00:11:38.040> algorithms<00:11:38.459> hash<00:11:38.700> functions 00:11:39.110 --> 00:11:39.120 align:start position:0% signature algorithms hash functions 00:11:39.120 --> 00:11:40.970 align:start position:0% signature algorithms hash functions encryption<00:11:39.540> teams<00:11:39.959> Etc<00:11:40.140> inside<00:11:40.380> of<00:11:40.620> snarks 00:11:40.970 --> 00:11:40.980 align:start position:0% encryption teams Etc inside of snarks 00:11:40.980 --> 00:11:43.550 align:start position:0% encryption teams Etc inside of snarks even<00:11:41.100> if<00:11:41.220> it<00:11:41.339> is<00:11:41.459> costly<00:11:41.880> so<00:11:42.779> as<00:11:43.019> an<00:11:43.140> example<00:11:43.380> of 00:11:43.550 --> 00:11:43.560 align:start position:0% even if it is costly so as an example of 00:11:43.560 --> 00:11:45.050 align:start position:0% even if it is costly so as an example of a<00:11:43.680> few<00:11:43.800> crypto<00:11:44.100> systems<00:11:44.399> that<00:11:44.519> exist<00:11:44.760> out<00:11:44.880> in 00:11:45.050 --> 00:11:45.060 align:start position:0% a few crypto systems that exist out in 00:11:45.060 --> 00:11:47.389 align:start position:0% a few crypto systems that exist out in the<00:11:45.240> wild<00:11:45.300> we've<00:11:46.200> got<00:11:46.320> key<00:11:46.680> distribution<00:11:47.160> and 00:11:47.389 --> 00:11:47.399 align:start position:0% the wild we've got key distribution and 00:11:47.399 --> 00:11:49.190 align:start position:0% the wild we've got key distribution and identity<00:11:47.760> Registries<00:11:48.240> such<00:11:48.779> as<00:11:48.899> like<00:11:49.079> you 00:11:49.190 --> 00:11:49.200 align:start position:0% identity Registries such as like you 00:11:49.200 --> 00:11:50.810 align:start position:0% identity Registries such as like you know<00:11:49.320> you<00:11:49.440> can<00:11:49.560> build<00:11:49.680> a<00:11:49.920> an<00:11:50.459> identity 00:11:50.810 --> 00:11:50.820 align:start position:0% know you can build a an identity 00:11:50.820 --> 00:11:53.630 align:start position:0% know you can build a an identity registry<00:11:51.240> of<00:11:51.360> like<00:11:51.480> gpg<00:11:51.899> keys 00:11:53.630 --> 00:11:53.640 align:start position:0% registry of like gpg keys 00:11:53.640 --> 00:11:57.290 align:start position:0% registry of like gpg keys um<00:11:53.700> GitHub<00:11:54.660> allows<00:11:55.380> you<00:11:55.680> to<00:11:56.160> generate<00:11:56.880> locally 00:11:57.290 --> 00:11:57.300 align:start position:0% um GitHub allows you to generate locally 00:11:57.300 --> 00:11:59.750 align:start position:0% um GitHub allows you to generate locally a<00:11:57.540> key<00:11:57.660> pair<00:11:57.899> and<00:11:58.200> upload<00:11:58.500> it<00:11:58.680> and<00:11:59.459> make<00:11:59.579> it 00:11:59.750 --> 00:11:59.760 align:start position:0% a key pair and upload it and make it 00:11:59.760 --> 00:12:01.910 align:start position:0% a key pair and upload it and make it publicly<00:12:00.060> accessible<00:12:00.720> to<00:12:00.959> anyone<00:12:01.380> so<00:12:01.800> that 00:12:01.910 --> 00:12:01.920 align:start position:0% publicly accessible to anyone so that 00:12:01.920 --> 00:12:03.410 align:start position:0% publicly accessible to anyone so that anyone<00:12:02.220> can<00:12:02.339> verify<00:12:02.700> you<00:12:02.940> know<00:12:03.000> your<00:12:03.120> commit 00:12:03.410 --> 00:12:03.420 align:start position:0% anyone can verify you know your commit 00:12:03.420 --> 00:12:05.030 align:start position:0% anyone can verify you know your commit history<00:12:03.540> or<00:12:03.839> things<00:12:04.019> like<00:12:04.200> that<00:12:04.320> repos<00:12:04.740> you've 00:12:05.030 --> 00:12:05.040 align:start position:0% history or things like that repos you've 00:12:05.040 --> 00:12:06.769 align:start position:0% history or things like that repos you've contributed<00:12:05.399> to<00:12:05.640> so<00:12:06.120> for<00:12:06.240> example<00:12:06.420> if<00:12:06.600> you<00:12:06.660> go 00:12:06.769 --> 00:12:06.779 align:start position:0% contributed to so for example if you go 00:12:06.779 --> 00:12:07.750 align:start position:0% contributed to so for example if you go to 00:12:07.750 --> 00:12:07.760 align:start position:0% to 00:12:07.760 --> 00:12:09.470 align:start position:0% to github.comeep.keys<00:12:08.760> you'll<00:12:08.940> see<00:12:09.060> like<00:12:09.240> my 00:12:09.470 --> 00:12:09.480 align:start position:0% github.comeep.keys you'll see like my 00:12:09.480 --> 00:12:11.389 align:start position:0% github.comeep.keys you'll see like my RSA<00:12:09.899> Keys 00:12:11.389 --> 00:12:11.399 align:start position:0% RSA Keys 00:12:11.399 --> 00:12:12.110 align:start position:0% RSA Keys um 00:12:12.110 --> 00:12:12.120 align:start position:0% um 00:12:12.120 --> 00:12:14.930 align:start position:0% um ethereum<00:12:12.959> and<00:12:13.320> Bitcoin<00:12:13.740> rely<00:12:14.100> on<00:12:14.220> the<00:12:14.339> ecdsa 00:12:14.930 --> 00:12:14.940 align:start position:0% ethereum and Bitcoin rely on the ecdsa 00:12:14.940 --> 00:12:18.290 align:start position:0% ethereum and Bitcoin rely on the ecdsa signature<00:12:15.420> scheme<00:12:16.220> so<00:12:17.220> addresses<00:12:17.880> are<00:12:18.120> going 00:12:18.290 --> 00:12:18.300 align:start position:0% signature scheme so addresses are going 00:12:18.300 --> 00:12:21.050 align:start position:0% signature scheme so addresses are going to<00:12:18.420> be<00:12:18.540> you<00:12:18.959> know<00:12:19.019> a<00:12:19.380> hash<00:12:19.560> of<00:12:20.040> an<00:12:20.279> ecbsa<00:12:20.940> public 00:12:21.050 --> 00:12:21.060 align:start position:0% to be you know a hash of an ecbsa public 00:12:21.060 --> 00:12:24.889 align:start position:0% to be you know a hash of an ecbsa public key<00:12:21.300> in<00:12:21.660> ethereum<00:12:22.399> and<00:12:23.399> I<00:12:23.820> think<00:12:23.940> mail<00:12:24.360> servers 00:12:24.889 --> 00:12:24.899 align:start position:0% key in ethereum and I think mail servers 00:12:24.899 --> 00:12:27.110 align:start position:0% key in ethereum and I think mail servers use<00:12:25.380> the<00:12:25.560> dkim<00:12:26.100> protocol<00:12:26.519> to<00:12:26.700> sign<00:12:26.880> and 00:12:27.110 --> 00:12:27.120 align:start position:0% use the dkim protocol to sign and 00:12:27.120 --> 00:12:28.610 align:start position:0% use the dkim protocol to sign and authenticate<00:12:27.540> messages<00:12:27.720> which<00:12:28.200> under<00:12:28.380> the 00:12:28.610 --> 00:12:28.620 align:start position:0% authenticate messages which under the 00:12:28.620 --> 00:12:31.190 align:start position:0% authenticate messages which under the hood<00:12:28.940> relies<00:12:29.940> on<00:12:30.060> RSA 00:12:31.190 --> 00:12:31.200 align:start position:0% hood relies on RSA 00:12:31.200 --> 00:12:34.130 align:start position:0% hood relies on RSA so<00:12:32.240> one<00:12:33.240> of<00:12:33.360> the<00:12:33.480> things<00:12:33.600> that's<00:12:33.839> going<00:12:34.019> on 00:12:34.130 --> 00:12:34.140 align:start position:0% so one of the things that's going on 00:12:34.140 --> 00:12:35.269 align:start position:0% so one of the things that's going on with<00:12:34.320> all<00:12:34.500> these<00:12:34.620> different<00:12:34.800> signature 00:12:35.269 --> 00:12:35.279 align:start position:0% with all these different signature 00:12:35.279 --> 00:12:37.970 align:start position:0% with all these different signature schemes<00:12:35.640> is<00:12:35.880> that<00:12:36.320> they<00:12:37.320> kind<00:12:37.500> of<00:12:37.620> can't 00:12:37.970 --> 00:12:37.980 align:start position:0% schemes is that they kind of can't 00:12:37.980 --> 00:12:39.590 align:start position:0% schemes is that they kind of can't really<00:12:38.339> talk<00:12:38.700> to<00:12:38.940> each<00:12:39.060> other<00:12:39.180> you<00:12:39.420> know<00:12:39.540> if 00:12:39.590 --> 00:12:39.600 align:start position:0% really talk to each other you know if 00:12:39.600 --> 00:12:41.750 align:start position:0% really talk to each other you know if you're<00:12:39.720> running<00:12:39.959> on<00:12:40.260> the<00:12:40.320> RSA<00:12:40.740> protocol<00:12:41.100> you 00:12:41.750 --> 00:12:41.760 align:start position:0% you're running on the RSA protocol you 00:12:41.760 --> 00:12:44.329 align:start position:0% you're running on the RSA protocol you can't<00:12:41.820> really<00:12:42.060> understand<00:12:42.500> an<00:12:43.500> ecdsa 00:12:44.329 --> 00:12:44.339 align:start position:0% can't really understand an ecdsa 00:12:44.339 --> 00:12:45.769 align:start position:0% can't really understand an ecdsa signature 00:12:45.769 --> 00:12:45.779 align:start position:0% signature 00:12:45.779 --> 00:12:48.710 align:start position:0% signature um<00:12:46.320> however<00:12:47.040> by<00:12:47.639> making<00:12:47.820> all<00:12:48.180> of<00:12:48.360> these 00:12:48.710 --> 00:12:48.720 align:start position:0% um however by making all of these 00:12:48.720 --> 00:12:50.690 align:start position:0% um however by making all of these Primitives<00:12:49.320> snark<00:12:49.800> compatible<00:12:50.339> by 00:12:50.690 --> 00:12:50.700 align:start position:0% Primitives snark compatible by 00:12:50.700 --> 00:12:52.670 align:start position:0% Primitives snark compatible by implementing<00:12:51.180> RSA<00:12:51.899> signature<00:12:52.260> verification 00:12:52.670 --> 00:12:52.680 align:start position:0% implementing RSA signature verification 00:12:52.680 --> 00:12:55.129 align:start position:0% implementing RSA signature verification ecdsa<00:12:53.459> signature<00:12:53.820> verification<00:12:54.600> etc<00:12:54.959> etc 00:12:55.129 --> 00:12:55.139 align:start position:0% ecdsa signature verification etc etc 00:12:55.139 --> 00:12:57.949 align:start position:0% ecdsa signature verification etc etc inside<00:12:55.680> of<00:12:55.980> snarks<00:12:56.579> what<00:12:57.300> we<00:12:57.420> can<00:12:57.540> start<00:12:57.660> to<00:12:57.839> do 00:12:57.949 --> 00:12:57.959 align:start position:0% inside of snarks what we can start to do 00:12:57.959 --> 00:12:59.269 align:start position:0% inside of snarks what we can start to do is<00:12:58.079> we<00:12:58.200> can<00:12:58.320> start<00:12:58.380> to<00:12:58.560> build<00:12:58.740> adapters 00:12:59.269 --> 00:12:59.279 align:start position:0% is we can start to build adapters 00:12:59.279 --> 00:13:01.730 align:start position:0% is we can start to build adapters between<00:12:59.579> all<00:12:59.820> these<00:13:00.060> different<00:13:00.180> systems 00:13:01.730 --> 00:13:01.740 align:start position:0% between all these different systems 00:13:01.740 --> 00:13:03.829 align:start position:0% between all these different systems um<00:13:01.800> so<00:13:02.279> again<00:13:02.519> if<00:13:02.760> I<00:13:02.880> have<00:13:03.000> an<00:13:03.120> RSA<00:13:03.480> primitive 00:13:03.829 --> 00:13:03.839 align:start position:0% um so again if I have an RSA primitive 00:13:03.839 --> 00:13:05.690 align:start position:0% um so again if I have an RSA primitive and<00:13:04.019> an<00:13:04.139> ecdsa<00:13:04.680> primitive<00:13:05.040> inside<00:13:05.160> of<00:13:05.339> a<00:13:05.459> snark 00:13:05.690 --> 00:13:05.700 align:start position:0% and an ecdsa primitive inside of a snark 00:13:05.700 --> 00:13:07.250 align:start position:0% and an ecdsa primitive inside of a snark then<00:13:06.060> I<00:13:06.240> can<00:13:06.300> start<00:13:06.420> to<00:13:06.600> make<00:13:06.720> claims<00:13:07.079> like 00:13:07.250 --> 00:13:07.260 align:start position:0% then I can start to make claims like 00:13:07.260 --> 00:13:11.449 align:start position:0% then I can start to make claims like either<00:13:07.980> I<00:13:08.820> have<00:13:09.139> a<00:13:10.139> GitHub<00:13:10.980> account<00:13:11.220> that's 00:13:11.449 --> 00:13:11.459 align:start position:0% either I have a GitHub account that's 00:13:11.459 --> 00:13:13.910 align:start position:0% either I have a GitHub account that's contributed<00:13:12.000> to<00:13:12.420> the<00:13:12.839> you<00:13:13.380> know<00:13:13.440> ethereum 00:13:13.910 --> 00:13:13.920 align:start position:0% contributed to the you know ethereum 00:13:13.920 --> 00:13:17.949 align:start position:0% contributed to the you know ethereum GitHub<00:13:14.279> org<00:13:14.700> or<00:13:15.480> I<00:13:15.779> possess<00:13:16.139> at<00:13:16.560> least<00:13:16.620> 100<00:13:16.860> eth 00:13:17.949 --> 00:13:17.959 align:start position:0% GitHub org or I possess at least 100 eth 00:13:17.959 --> 00:13:20.210 align:start position:0% GitHub org or I possess at least 100 eth and<00:13:18.959> again<00:13:19.320> by<00:13:19.620> making<00:13:19.740> existing 00:13:20.210 --> 00:13:20.220 align:start position:0% and again by making existing 00:13:20.220 --> 00:13:23.030 align:start position:0% and again by making existing cryptography<00:13:20.940> uh<00:13:21.839> snark<00:13:22.200> compatible<00:13:22.680> and 00:13:23.030 --> 00:13:23.040 align:start position:0% cryptography uh snark compatible and 00:13:23.040 --> 00:13:24.350 align:start position:0% cryptography uh snark compatible and combining<00:13:23.459> that<00:13:23.579> with<00:13:23.760> this<00:13:23.940> expressive 00:13:24.350 --> 00:13:24.360 align:start position:0% combining that with this expressive 00:13:24.360 --> 00:13:26.090 align:start position:0% combining that with this expressive language<00:13:24.480> for<00:13:24.720> claims<00:13:25.139> we<00:13:25.500> can<00:13:25.620> start<00:13:25.800> to<00:13:25.920> make 00:13:26.090 --> 00:13:26.100 align:start position:0% language for claims we can start to make 00:13:26.100 --> 00:13:27.889 align:start position:0% language for claims we can start to make statements<00:13:26.459> about<00:13:26.639> all<00:13:27.000> sorts<00:13:27.240> of<00:13:27.300> digital<00:13:27.720> or 00:13:27.889 --> 00:13:27.899 align:start position:0% statements about all sorts of digital or 00:13:27.899 --> 00:13:29.150 align:start position:0% statements about all sorts of digital or online<00:13:28.079> activity 00:13:29.150 --> 00:13:29.160 align:start position:0% online activity 00:13:29.160 --> 00:13:31.850 align:start position:0% online activity so<00:13:29.700> both<00:13:29.940> of<00:13:30.120> these<00:13:30.300> features<00:13:30.720> are<00:13:31.320> examples 00:13:31.850 --> 00:13:31.860 align:start position:0% so both of these features are examples 00:13:31.860 --> 00:13:33.710 align:start position:0% so both of these features are examples of<00:13:32.220> the<00:13:32.459> power<00:13:32.639> of<00:13:33.060> programmable 00:13:33.710 --> 00:13:33.720 align:start position:0% of the power of programmable 00:13:33.720 --> 00:13:35.449 align:start position:0% of the power of programmable cryptography<00:13:34.440> which<00:13:34.740> probably<00:13:34.980> is<00:13:35.220> you've 00:13:35.449 --> 00:13:35.459 align:start position:0% cryptography which probably is you've 00:13:35.459 --> 00:13:37.009 align:start position:0% cryptography which probably is you've grok<00:13:36.000> from<00:13:36.240> now 00:13:37.009 --> 00:13:37.019 align:start position:0% grok from now 00:13:37.019 --> 00:13:38.690 align:start position:0% grok from now um<00:13:37.440> you<00:13:37.860> know<00:13:37.920> both<00:13:38.100> of<00:13:38.220> these<00:13:38.339> features<00:13:38.579> are 00:13:38.690 --> 00:13:38.700 align:start position:0% um you know both of these features are 00:13:38.700 --> 00:13:40.370 align:start position:0% um you know both of these features are giving<00:13:38.880> us<00:13:39.060> these<00:13:39.360> tools<00:13:39.600> to<00:13:39.899> much<00:13:40.200> more 00:13:40.370 --> 00:13:40.380 align:start position:0% giving us these tools to much more 00:13:40.380 --> 00:13:43.069 align:start position:0% giving us these tools to much more flexibly<00:13:40.920> manipulate<00:13:41.399> digital<00:13:41.700> objects<00:13:42.660> so 00:13:43.069 --> 00:13:43.079 align:start position:0% flexibly manipulate digital objects so 00:13:43.079 --> 00:13:44.210 align:start position:0% flexibly manipulate digital objects so now<00:13:43.320> I'm<00:13:43.440> going<00:13:43.620> to<00:13:43.680> kind<00:13:43.800> of<00:13:43.920> give<00:13:44.040> my 00:13:44.210 --> 00:13:44.220 align:start position:0% now I'm going to kind of give my 00:13:44.220 --> 00:13:45.769 align:start position:0% now I'm going to kind of give my description<00:13:44.579> of<00:13:44.760> programmable<00:13:45.120> cryptography 00:13:45.769 --> 00:13:45.779 align:start position:0% description of programmable cryptography 00:13:45.779 --> 00:13:48.110 align:start position:0% description of programmable cryptography which<00:13:45.959> is<00:13:46.019> that<00:13:46.260> it<00:13:46.740> is<00:13:46.920> uh<00:13:47.399> cryptography<00:13:48.000> that 00:13:48.110 --> 00:13:48.120 align:start position:0% which is that it is uh cryptography that 00:13:48.120 --> 00:13:50.569 align:start position:0% which is that it is uh cryptography that can<00:13:48.300> be<00:13:48.420> layered<00:13:49.019> on<00:13:49.380> top<00:13:49.560> of<00:13:49.920> arbitrary 00:13:50.569 --> 00:13:50.579 align:start position:0% can be layered on top of arbitrary 00:13:50.579 --> 00:13:52.190 align:start position:0% can be layered on top of arbitrary computations 00:13:52.190 --> 00:13:52.200 align:start position:0% computations 00:13:52.200 --> 00:13:54.829 align:start position:0% computations to<00:13:52.680> contrast<00:13:53.040> this<00:13:53.399> with<00:13:53.820> cryptography<00:13:54.720> that 00:13:54.829 --> 00:13:54.839 align:start position:0% to contrast this with cryptography that 00:13:54.839 --> 00:13:55.970 align:start position:0% to contrast this with cryptography that we've<00:13:54.959> been<00:13:55.079> using<00:13:55.320> for<00:13:55.440> the<00:13:55.560> last<00:13:55.680> couple<00:13:55.860> of 00:13:55.970 --> 00:13:55.980 align:start position:0% we've been using for the last couple of 00:13:55.980 --> 00:13:57.949 align:start position:0% we've been using for the last couple of decades<00:13:56.519> well<00:13:57.060> for<00:13:57.300> more<00:13:57.480> most<00:13:57.779> of 00:13:57.949 --> 00:13:57.959 align:start position:0% decades well for more most of 00:13:57.959 --> 00:13:59.870 align:start position:0% decades well for more most of cryptography's<00:13:58.500> Short<00:13:58.740> History<00:13:58.980> the<00:13:59.519> set<00:13:59.700> of 00:13:59.870 --> 00:13:59.880 align:start position:0% cryptography's Short History the set of 00:13:59.880 --> 00:14:01.370 align:start position:0% cryptography's Short History the set of mechanisms<00:14:00.300> that<00:14:00.480> we've<00:14:00.660> been<00:14:00.839> able<00:14:01.019> to 00:14:01.370 --> 00:14:01.380 align:start position:0% mechanisms that we've been able to 00:14:01.380 --> 00:14:04.129 align:start position:0% mechanisms that we've been able to instantiate<00:14:02.220> with<00:14:02.639> our<00:14:02.820> tools<00:14:03.120> has<00:14:03.360> been<00:14:03.600> you 00:14:04.129 --> 00:14:04.139 align:start position:0% instantiate with our tools has been you 00:14:04.139 --> 00:14:05.569 align:start position:0% instantiate with our tools has been you know<00:14:04.200> quite<00:14:04.440> narrow<00:14:04.740> so<00:14:04.980> we<00:14:05.220> can<00:14:05.279> say<00:14:05.399> things 00:14:05.569 --> 00:14:05.579 align:start position:0% know quite narrow so we can say things 00:14:05.579 --> 00:14:07.129 align:start position:0% know quite narrow so we can say things like<00:14:05.760> this<00:14:05.940> message<00:14:06.120> originated<00:14:06.600> with<00:14:06.839> Alice 00:14:07.129 --> 00:14:07.139 align:start position:0% like this message originated with Alice 00:14:07.139 --> 00:14:08.930 align:start position:0% like this message originated with Alice as<00:14:07.380> we've<00:14:07.620> seen<00:14:07.740> or<00:14:07.980> this<00:14:08.399> message<00:14:08.519> can<00:14:08.820> only 00:14:08.930 --> 00:14:08.940 align:start position:0% as we've seen or this message can only 00:14:08.940 --> 00:14:12.230 align:start position:0% as we've seen or this message can only be<00:14:09.060> read<00:14:09.240> by<00:14:09.480> Bob<00:14:09.779> but<00:14:10.740> every<00:14:11.459> single<00:14:12.000> new 00:14:12.230 --> 00:14:12.240 align:start position:0% be read by Bob but every single new 00:14:12.240 --> 00:14:14.030 align:start position:0% be read by Bob but every single new mechanism<00:14:12.839> that<00:14:13.260> we<00:14:13.320> want<00:14:13.500> to<00:14:13.620> build<00:14:13.740> whether 00:14:14.030 --> 00:14:14.040 align:start position:0% mechanism that we want to build whether 00:14:14.040 --> 00:14:15.290 align:start position:0% mechanism that we want to build whether it's<00:14:14.160> like<00:14:14.279> you<00:14:14.399> know<00:14:14.519> arbitrary<00:14:14.880> identity 00:14:15.290 --> 00:14:15.300 align:start position:0% it's like you know arbitrary identity 00:14:15.300 --> 00:14:17.210 align:start position:0% it's like you know arbitrary identity predicates<00:14:15.779> or<00:14:16.320> read<00:14:16.500> permissions<00:14:16.920> or<00:14:17.100> things 00:14:17.210 --> 00:14:17.220 align:start position:0% predicates or read permissions or things 00:14:17.220 --> 00:14:19.069 align:start position:0% predicates or read permissions or things like<00:14:17.339> that<00:14:17.459> would<00:14:17.700> require<00:14:17.940> us<00:14:18.180> to<00:14:18.360> build<00:14:18.540> a 00:14:19.069 --> 00:14:19.079 align:start position:0% like that would require us to build a 00:14:19.079 --> 00:14:21.129 align:start position:0% like that would require us to build a new<00:14:19.200> special<00:14:19.440> purpose<00:14:19.980> cryptographic<00:14:20.880> system 00:14:21.129 --> 00:14:21.139 align:start position:0% new special purpose cryptographic system 00:14:21.139 --> 00:14:23.449 align:start position:0% new special purpose cryptographic system however<00:14:22.139> now<00:14:22.440> we're<00:14:22.560> seeing<00:14:22.740> tools<00:14:23.100> like<00:14:23.220> you 00:14:23.449 --> 00:14:23.459 align:start position:0% however now we're seeing tools like you 00:14:23.459 --> 00:14:25.009 align:start position:0% however now we're seeing tools like you know<00:14:23.519> ZK<00:14:23.880> snarks<00:14:24.300> as<00:14:24.420> we've<00:14:24.600> discussed<00:14:24.899> that 00:14:25.009 --> 00:14:25.019 align:start position:0% know ZK snarks as we've discussed that 00:14:25.019 --> 00:14:26.750 align:start position:0% know ZK snarks as we've discussed that allow<00:14:25.260> us<00:14:25.380> to<00:14:25.500> move<00:14:25.680> from<00:14:26.040> this<00:14:26.579> message 00:14:26.750 --> 00:14:26.760 align:start position:0% allow us to move from this message 00:14:26.760 --> 00:14:29.150 align:start position:0% allow us to move from this message originated<00:14:27.300> from<00:14:27.540> Alice<00:14:27.959> to<00:14:28.320> I<00:14:28.860> know<00:14:28.980> a 00:14:29.150 --> 00:14:29.160 align:start position:0% originated from Alice to I know a 00:14:29.160 --> 00:14:30.290 align:start position:0% originated from Alice to I know a private<00:14:29.339> key<00:14:29.519> corresponding<00:14:29.940> to<00:14:30.060> one<00:14:30.240> of 00:14:30.290 --> 00:14:30.300 align:start position:0% private key corresponding to one of 00:14:30.300 --> 00:14:31.910 align:start position:0% private key corresponding to one of these<00:14:30.420> people<00:14:30.600> I<00:14:31.079> have<00:14:31.200> an<00:14:31.320> attestation<00:14:31.680> from 00:14:31.910 --> 00:14:31.920 align:start position:0% these people I have an attestation from 00:14:31.920 --> 00:14:34.970 align:start position:0% these people I have an attestation from one<00:14:32.040> of<00:14:32.100> these<00:14:32.220> service<00:14:32.339> providers<00:14:32.940> etc<00:14:33.300> etc 00:14:34.970 --> 00:14:34.980 align:start position:0% one of these service providers etc etc 00:14:34.980 --> 00:14:37.129 align:start position:0% one of these service providers etc etc um<00:14:35.040> to<00:14:35.579> things<00:14:35.760> like<00:14:35.940> witness<00:14:36.240> encryption<00:14:36.779> uh 00:14:37.129 --> 00:14:37.139 align:start position:0% um to things like witness encryption uh 00:14:37.139 --> 00:14:38.569 align:start position:0% um to things like witness encryption uh witness<00:14:37.320> encryption<00:14:37.860> is<00:14:37.980> a<00:14:38.100> primitive<00:14:38.339> that 00:14:38.569 --> 00:14:38.579 align:start position:0% witness encryption is a primitive that 00:14:38.579 --> 00:14:41.269 align:start position:0% witness encryption is a primitive that essentially<00:14:38.880> allows<00:14:39.420> you<00:14:39.600> to<00:14:40.199> encrypt<00:14:40.680> data 00:14:41.269 --> 00:14:41.279 align:start position:0% essentially allows you to encrypt data 00:14:41.279 --> 00:14:44.509 align:start position:0% essentially allows you to encrypt data not<00:14:41.760> with<00:14:42.060> like<00:14:42.420> a<00:14:43.079> key<00:14:43.560> pair<00:14:43.800> where<00:14:44.339> someone 00:14:44.509 --> 00:14:44.519 align:start position:0% not with like a key pair where someone 00:14:44.519 --> 00:14:45.949 align:start position:0% not with like a key pair where someone has<00:14:44.760> to<00:14:44.820> know<00:14:44.940> a<00:14:45.060> certain<00:14:45.180> secret<00:14:45.420> to<00:14:45.600> decrypt 00:14:45.949 --> 00:14:45.959 align:start position:0% has to know a certain secret to decrypt 00:14:45.959 --> 00:14:47.629 align:start position:0% has to know a certain secret to decrypt the<00:14:46.079> message<00:14:46.199> but<00:14:46.560> it<00:14:46.680> allows<00:14:46.920> you<00:14:46.980> to<00:14:47.160> decrypt 00:14:47.629 --> 00:14:47.639 align:start position:0% the message but it allows you to decrypt 00:14:47.639 --> 00:14:49.670 align:start position:0% the message but it allows you to decrypt messages<00:14:48.120> with<00:14:48.720> or<00:14:48.839> sorry<00:14:49.079> encrypt<00:14:49.500> messages 00:14:49.670 --> 00:14:49.680 align:start position:0% messages with or sorry encrypt messages 00:14:49.680 --> 00:14:52.970 align:start position:0% messages with or sorry encrypt messages with<00:14:50.040> a<00:14:50.279> program<00:14:50.519> so<00:14:51.360> for<00:14:51.540> example<00:14:51.839> uh<00:14:52.560> I<00:14:52.800> can 00:14:52.970 --> 00:14:52.980 align:start position:0% with a program so for example uh I can 00:14:52.980 --> 00:14:55.550 align:start position:0% with a program so for example uh I can encrypt<00:14:53.519> a<00:14:54.000> message<00:14:54.240> with<00:14:54.480> a<00:14:54.600> Sudoku<00:14:55.199> puzzle 00:14:55.550 --> 00:14:55.560 align:start position:0% encrypt a message with a Sudoku puzzle 00:14:55.560 --> 00:14:58.550 align:start position:0% encrypt a message with a Sudoku puzzle and<00:14:56.220> anyone<00:14:57.000> who<00:14:57.300> solves<00:14:57.600> the<00:14:57.720> Sudoku<00:14:58.260> puzzle 00:14:58.550 --> 00:14:58.560 align:start position:0% and anyone who solves the Sudoku puzzle 00:14:58.560 --> 00:14:59.810 align:start position:0% and anyone who solves the Sudoku puzzle will<00:14:58.740> be<00:14:58.860> able<00:14:58.920> to<00:14:59.040> generate<00:14:59.339> a<00:14:59.459> key<00:14:59.579> to 00:14:59.810 --> 00:14:59.820 align:start position:0% will be able to generate a key to 00:14:59.820 --> 00:15:02.389 align:start position:0% will be able to generate a key to decrypt<00:15:00.300> the<00:15:01.019> message<00:15:01.500> that<00:15:01.800> I've<00:15:01.920> encrypted 00:15:02.389 --> 00:15:02.399 align:start position:0% decrypt the message that I've encrypted 00:15:02.399 --> 00:15:04.430 align:start position:0% decrypt the message that I've encrypted uh<00:15:02.820> with<00:15:03.000> witness<00:15:03.120> encryption<00:15:03.660> and<00:15:04.320> this 00:15:04.430 --> 00:15:04.440 align:start position:0% uh with witness encryption and this 00:15:04.440 --> 00:15:06.590 align:start position:0% uh with witness encryption and this allows<00:15:04.740> us<00:15:04.860> to<00:15:05.040> move<00:15:05.220> from<00:15:05.699> systems<00:15:06.180> where<00:15:06.420> we 00:15:06.590 --> 00:15:06.600 align:start position:0% allows us to move from systems where we 00:15:06.600 --> 00:15:08.389 align:start position:0% allows us to move from systems where we can<00:15:06.660> do<00:15:06.839> things<00:15:07.019> like<00:15:07.380> Charlie<00:15:07.800> has<00:15:08.100> published 00:15:08.389 --> 00:15:08.399 align:start position:0% can do things like Charlie has published 00:15:08.399 --> 00:15:09.949 align:start position:0% can do things like Charlie has published some<00:15:08.579> secret<00:15:08.760> vote<00:15:09.060> that<00:15:09.240> only<00:15:09.420> a<00:15:09.600> coordinator 00:15:09.949 --> 00:15:09.959 align:start position:0% some secret vote that only a coordinator 00:15:09.959 --> 00:15:11.629 align:start position:0% some secret vote that only a coordinator can<00:15:10.260> read<00:15:10.440> with<00:15:10.680> the<00:15:10.860> coordinator's<00:15:11.399> private 00:15:11.629 --> 00:15:11.639 align:start position:0% can read with the coordinator's private 00:15:11.639 --> 00:15:13.790 align:start position:0% can read with the coordinator's private key<00:15:11.760> to<00:15:12.480> Charlie<00:15:12.899> has<00:15:13.199> committed<00:15:13.500> to<00:15:13.620> some 00:15:13.790 --> 00:15:13.800 align:start position:0% key to Charlie has committed to some 00:15:13.800 --> 00:15:16.009 align:start position:0% key to Charlie has committed to some secret<00:15:13.980> vote<00:15:14.279> that<00:15:14.880> only<00:15:15.060> a<00:15:15.300> testers<00:15:15.660> with<00:15:15.839> a 00:15:16.009 --> 00:15:16.019 align:start position:0% secret vote that only a testers with a 00:15:16.019 --> 00:15:17.449 align:start position:0% secret vote that only a testers with a certain<00:15:16.199> permission<00:15:16.560> level<00:15:16.800> can<00:15:17.040> decrypt 00:15:17.449 --> 00:15:17.459 align:start position:0% certain permission level can decrypt 00:15:17.459 --> 00:15:19.910 align:start position:0% certain permission level can decrypt today<00:15:17.820> but<00:15:18.540> which<00:15:18.720> a<00:15:18.959> class<00:15:19.079> of<00:15:19.260> Auditors<00:15:19.680> with 00:15:19.910 --> 00:15:19.920 align:start position:0% today but which a class of Auditors with 00:15:19.920 --> 00:15:21.530 align:start position:0% today but which a class of Auditors with a<00:15:20.040> lower<00:15:20.160> permission<00:15:20.519> level<00:15:20.760> can<00:15:21.240> at<00:15:21.420> least 00:15:21.530 --> 00:15:21.540 align:start position:0% a lower permission level can at least 00:15:21.540 --> 00:15:23.449 align:start position:0% a lower permission level can at least partially<00:15:21.899> decrypt<00:15:22.440> in<00:15:22.560> exactly<00:15:22.980> you<00:15:23.339> know 00:15:23.449 --> 00:15:23.459 align:start position:0% partially decrypt in exactly you know 00:15:23.459 --> 00:15:25.790 align:start position:0% partially decrypt in exactly you know one<00:15:23.699> week<00:15:23.959> uh<00:15:24.959> I<00:15:25.139> would<00:15:25.260> say<00:15:25.380> that<00:15:25.560> smart 00:15:25.790 --> 00:15:25.800 align:start position:0% one week uh I would say that smart 00:15:25.800 --> 00:15:28.430 align:start position:0% one week uh I would say that smart contracts<00:15:26.339> Also<00:15:26.639> spiritually<00:15:27.120> uh<00:15:27.959> kind<00:15:28.320> of 00:15:28.430 --> 00:15:28.440 align:start position:0% contracts Also spiritually uh kind of 00:15:28.440 --> 00:15:30.949 align:start position:0% contracts Also spiritually uh kind of fall<00:15:28.860> in<00:15:29.279> the<00:15:29.459> same<00:15:29.639> category<00:15:30.300> as<00:15:30.600> a<00:15:30.839> lot<00:15:30.899> of 00:15:30.949 --> 00:15:30.959 align:start position:0% fall in the same category as a lot of 00:15:30.959 --> 00:15:32.449 align:start position:0% fall in the same category as a lot of these<00:15:31.139> other<00:15:31.260> programmable<00:15:31.860> cryptography 00:15:32.449 --> 00:15:32.459 align:start position:0% these other programmable cryptography 00:15:32.459 --> 00:15:33.829 align:start position:0% these other programmable cryptography Primitives<00:15:32.940> so 00:15:33.829 --> 00:15:33.839 align:start position:0% Primitives so 00:15:33.839 --> 00:15:36.530 align:start position:0% Primitives so um<00:15:34.260> you<00:15:34.740> know<00:15:34.800> imagine<00:15:34.920> very<00:15:35.339> early<00:15:35.579> on<00:15:35.880> in<00:15:36.420> the 00:15:36.530 --> 00:15:36.540 align:start position:0% um you know imagine very early on in the 00:15:36.540 --> 00:15:39.110 align:start position:0% um you know imagine very early on in the history<00:15:36.660> of<00:15:37.440> uh<00:15:37.920> this<00:15:38.279> idea<00:15:38.459> of<00:15:38.519> blockchains 00:15:39.110 --> 00:15:39.120 align:start position:0% history of uh this idea of blockchains 00:15:39.120 --> 00:15:40.970 align:start position:0% history of uh this idea of blockchains uh<00:15:39.660> we<00:15:39.839> would<00:15:39.899> have<00:15:40.079> these<00:15:40.260> consensus<00:15:40.620> engines 00:15:40.970 --> 00:15:40.980 align:start position:0% uh we would have these consensus engines 00:15:40.980 --> 00:15:42.829 align:start position:0% uh we would have these consensus engines where<00:15:41.160> people<00:15:41.279> could<00:15:41.519> come<00:15:41.699> to<00:15:41.820> consensus<00:15:42.300> on 00:15:42.829 --> 00:15:42.839 align:start position:0% where people could come to consensus on 00:15:42.839 --> 00:15:44.990 align:start position:0% where people could come to consensus on only<00:15:43.139> very<00:15:43.440> simple<00:15:43.740> or<00:15:44.160> specific<00:15:44.519> data 00:15:44.990 --> 00:15:45.000 align:start position:0% only very simple or specific data 00:15:45.000 --> 00:15:46.370 align:start position:0% only very simple or specific data Transformations<00:15:45.420> data<00:15:45.959> Transformations 00:15:46.370 --> 00:15:46.380 align:start position:0% Transformations data Transformations 00:15:46.380 --> 00:15:48.650 align:start position:0% Transformations data Transformations like<00:15:46.800> you<00:15:47.339> know<00:15:47.459> Bob<00:15:47.760> can<00:15:48.000> decrement<00:15:48.360> his 00:15:48.650 --> 00:15:48.660 align:start position:0% like you know Bob can decrement his 00:15:48.660 --> 00:15:49.970 align:start position:0% like you know Bob can decrement his balance<00:15:48.839> by<00:15:49.019> 100<00:15:49.139> ether<00:15:49.500> to<00:15:49.740> increment 00:15:49.970 --> 00:15:49.980 align:start position:0% balance by 100 ether to increment 00:15:49.980 --> 00:15:52.370 align:start position:0% balance by 100 ether to increment Alice's<00:15:50.399> balance<00:15:50.699> by<00:15:50.880> 100<00:15:51.060> ether<00:15:51.480> nowadays 00:15:52.370 --> 00:15:52.380 align:start position:0% Alice's balance by 100 ether nowadays 00:15:52.380 --> 00:15:53.990 align:start position:0% Alice's balance by 100 ether nowadays with<00:15:52.560> smart<00:15:52.740> contracts<00:15:53.279> and<00:15:53.579> programmable 00:15:53.990 --> 00:15:54.000 align:start position:0% with smart contracts and programmable 00:15:54.000 --> 00:15:55.790 align:start position:0% with smart contracts and programmable blockchains<00:15:54.720> we<00:15:55.019> can<00:15:55.199> sort<00:15:55.380> of<00:15:55.500> execute 00:15:55.790 --> 00:15:55.800 align:start position:0% blockchains we can sort of execute 00:15:55.800 --> 00:15:57.949 align:start position:0% blockchains we can sort of execute arbitrary<00:15:56.339> predicates<00:15:56.880> you<00:15:57.300> know<00:15:57.360> at<00:15:57.480> Block<00:15:57.720> B 00:15:57.949 --> 00:15:57.959 align:start position:0% arbitrary predicates you know at Block B 00:15:57.959 --> 00:15:59.689 align:start position:0% arbitrary predicates you know at Block B 100.<00:15:58.560> ether<00:15:58.860> will<00:15:59.100> be<00:15:59.220> available<00:15:59.399> for 00:15:59.689 --> 00:15:59.699 align:start position:0% 100. ether will be available for 00:15:59.699 --> 00:16:01.730 align:start position:0% 100. ether will be available for withdrawal<00:16:00.240> by<00:16:00.360> Bob<00:16:00.600> so<00:16:00.959> long<00:16:01.199> as<00:16:01.320> Bob<00:16:01.500> has 00:16:01.730 --> 00:16:01.740 align:start position:0% withdrawal by Bob so long as Bob has 00:16:01.740 --> 00:16:03.710 align:start position:0% withdrawal by Bob so long as Bob has closed<00:16:02.040> his<00:16:02.220> position<00:16:02.399> in<00:16:03.360> some<00:16:03.540> smart 00:16:03.710 --> 00:16:03.720 align:start position:0% closed his position in some smart 00:16:03.720 --> 00:16:05.329 align:start position:0% closed his position in some smart contract<00:16:04.139> and<00:16:04.320> no<00:16:04.440> one<00:16:04.560> submitted<00:16:04.920> a<00:16:05.040> fraud 00:16:05.329 --> 00:16:05.339 align:start position:0% contract and no one submitted a fraud 00:16:05.339 --> 00:16:07.610 align:start position:0% contract and no one submitted a fraud challenge<00:16:05.579> though<00:16:06.480> an<00:16:06.839> early<00:16:06.959> withdrawal<00:16:07.500> may 00:16:07.610 --> 00:16:07.620 align:start position:0% challenge though an early withdrawal may 00:16:07.620 --> 00:16:09.829 align:start position:0% challenge though an early withdrawal may be<00:16:07.740> initiated<00:16:08.100> if<00:16:08.459> two<00:16:09.240> of<00:16:09.480> the<00:16:09.600> following 00:16:09.829 --> 00:16:09.839 align:start position:0% be initiated if two of the following 00:16:09.839 --> 00:16:12.230 align:start position:0% be initiated if two of the following three<00:16:10.019> solvency<00:16:10.620> conditions<00:16:10.980> are<00:16:11.160> met 00:16:12.230 --> 00:16:12.240 align:start position:0% three solvency conditions are met 00:16:12.240 --> 00:16:14.150 align:start position:0% three solvency conditions are met etc<00:16:12.660> etc 00:16:14.150 --> 00:16:14.160 align:start position:0% etc etc 00:16:14.160 --> 00:16:16.009 align:start position:0% etc etc so<00:16:14.519> in<00:16:14.639> each<00:16:14.820> of<00:16:14.940> these<00:16:15.120> examples<00:16:15.480> there's 00:16:16.009 --> 00:16:16.019 align:start position:0% so in each of these examples there's 00:16:16.019 --> 00:16:17.990 align:start position:0% so in each of these examples there's this<00:16:16.260> common<00:16:16.500> thing<00:16:16.740> theme<00:16:17.220> of<00:16:17.579> moving<00:16:17.820> from 00:16:17.990 --> 00:16:18.000 align:start position:0% this common thing theme of moving from 00:16:18.000 --> 00:16:19.790 align:start position:0% this common thing theme of moving from the<00:16:18.120> specific<00:16:18.420> to<00:16:18.600> the<00:16:18.779> general<00:16:18.959> with<00:16:19.440> ZK 00:16:19.790 --> 00:16:19.800 align:start position:0% the specific to the general with ZK 00:16:19.800 --> 00:16:22.189 align:start position:0% the specific to the general with ZK snarks<00:16:20.279> I<00:16:20.459> can<00:16:20.519> move<00:16:20.639> from<00:16:20.959> proofs<00:16:21.959> of 00:16:22.189 --> 00:16:22.199 align:start position:0% snarks I can move from proofs of 00:16:22.199 --> 00:16:24.290 align:start position:0% snarks I can move from proofs of specific<00:16:22.500> claims<00:16:23.040> to<00:16:23.459> a<00:16:23.579> general<00:16:23.760> purpose 00:16:24.290 --> 00:16:24.300 align:start position:0% specific claims to a general purpose 00:16:24.300 --> 00:16:26.150 align:start position:0% specific claims to a general purpose language<00:16:24.779> of<00:16:25.199> claims 00:16:26.150 --> 00:16:26.160 align:start position:0% language of claims 00:16:26.160 --> 00:16:28.610 align:start position:0% language of claims smart<00:16:26.820> contracts<00:16:27.360> allow<00:16:27.660> us<00:16:27.779> to<00:16:27.959> move<00:16:28.199> from 00:16:28.610 --> 00:16:28.620 align:start position:0% smart contracts allow us to move from 00:16:28.620 --> 00:16:30.829 align:start position:0% smart contracts allow us to move from coming<00:16:28.980> to<00:16:29.220> consensus<00:16:29.639> on<00:16:29.880> canonical<00:16:30.420> data 00:16:30.829 --> 00:16:30.839 align:start position:0% coming to consensus on canonical data 00:16:30.839 --> 00:16:32.329 align:start position:0% coming to consensus on canonical data that<00:16:30.959> can<00:16:31.139> be<00:16:31.199> modified<00:16:31.500> in<00:16:31.800> only<00:16:32.040> very 00:16:32.329 --> 00:16:32.339 align:start position:0% that can be modified in only very 00:16:32.339 --> 00:16:34.970 align:start position:0% that can be modified in only very specific<00:16:32.820> or<00:16:33.060> narrow<00:16:33.420> ways<00:16:33.779> to<00:16:34.500> a<00:16:34.860> general 00:16:34.970 --> 00:16:34.980 align:start position:0% specific or narrow ways to a general 00:16:34.980 --> 00:16:37.129 align:start position:0% specific or narrow ways to a general purpose<00:16:35.459> language<00:16:35.760> for<00:16:36.420> modifying<00:16:36.959> or 00:16:37.129 --> 00:16:37.139 align:start position:0% purpose language for modifying or 00:16:37.139 --> 00:16:40.610 align:start position:0% purpose language for modifying or executing<00:16:37.620> code<00:16:37.920> on<00:16:38.399> this<00:16:38.519> canonical<00:16:39.060> data 00:16:40.610 --> 00:16:40.620 align:start position:0% executing code on this canonical data 00:16:40.620 --> 00:16:43.069 align:start position:0% executing code on this canonical data witness<00:16:41.220> encryption<00:16:41.880> moves<00:16:42.300> us<00:16:42.420> from<00:16:42.660> a<00:16:42.899> world 00:16:43.069 --> 00:16:43.079 align:start position:0% witness encryption moves us from a world 00:16:43.079 --> 00:16:46.370 align:start position:0% witness encryption moves us from a world where<00:16:43.940> we<00:16:44.940> can<00:16:45.060> permission<00:16:45.420> data<00:16:45.899> to<00:16:46.019> only<00:16:46.139> be 00:16:46.370 --> 00:16:46.380 align:start position:0% where we can permission data to only be 00:16:46.380 --> 00:16:48.410 align:start position:0% where we can permission data to only be read<00:16:46.560> by<00:16:47.040> a<00:16:47.339> specific<00:16:47.579> person<00:16:47.880> or<00:16:48.120> specific 00:16:48.410 --> 00:16:48.420 align:start position:0% read by a specific person or specific 00:16:48.420 --> 00:16:51.290 align:start position:0% read by a specific person or specific set<00:16:48.660> of<00:16:48.779> people<00:16:48.959> to<00:16:49.800> having<00:16:50.519> a<00:16:50.759> language<00:16:50.880> for 00:16:51.290 --> 00:16:51.300 align:start position:0% set of people to having a language for 00:16:51.300 --> 00:16:53.389 align:start position:0% set of people to having a language for specifying<00:16:51.839> arbitrary<00:16:52.380> predicates<00:16:52.980> for<00:16:53.220> read 00:16:53.389 --> 00:16:53.399 align:start position:0% specifying arbitrary predicates for read 00:16:53.399 --> 00:16:55.550 align:start position:0% specifying arbitrary predicates for read permissions<00:16:53.940> so<00:16:54.540> I<00:16:54.779> kind<00:16:54.899> of<00:16:54.959> imagine<00:16:55.139> this<00:16:55.380> as 00:16:55.550 --> 00:16:55.560 align:start position:0% permissions so I kind of imagine this as 00:16:55.560 --> 00:16:57.949 align:start position:0% permissions so I kind of imagine this as like<00:16:55.800> you<00:16:56.160> know<00:16:56.220> decentralized<00:16:57.000> oauth<00:16:57.600> tokens 00:16:57.949 --> 00:16:57.959 align:start position:0% like you know decentralized oauth tokens 00:16:57.959 --> 00:17:00.650 align:start position:0% like you know decentralized oauth tokens where<00:16:58.259> anyone<00:16:58.740> can<00:16:59.040> plug<00:17:00.000> into<00:17:00.180> this<00:17:00.480> like 00:17:00.650 --> 00:17:00.660 align:start position:0% where anyone can plug into this like 00:17:00.660 --> 00:17:02.389 align:start position:0% where anyone can plug into this like Global<00:17:01.019> authentication<00:17:01.560> system<00:17:01.800> and<00:17:02.040> specify 00:17:02.389 --> 00:17:02.399 align:start position:0% Global authentication system and specify 00:17:02.399 --> 00:17:05.750 align:start position:0% Global authentication system and specify who<00:17:02.639> can<00:17:02.820> read<00:17:02.940> what<00:17:03.180> and<00:17:03.420> when 00:17:05.750 --> 00:17:05.760 align:start position:0% 00:17:05.760 --> 00:17:07.669 align:start position:0% um and<00:17:06.000> there's<00:17:06.179> all<00:17:06.540> these<00:17:06.720> New<00:17:06.959> Primitives 00:17:07.669 --> 00:17:07.679 align:start position:0% um and there's all these New Primitives 00:17:07.679 --> 00:17:08.870 align:start position:0% um and there's all these New Primitives that<00:17:07.919> are<00:17:08.040> continually<00:17:08.280> getting<00:17:08.520> better<00:17:08.699> and 00:17:08.870 --> 00:17:08.880 align:start position:0% that are continually getting better and 00:17:08.880 --> 00:17:10.370 align:start position:0% that are continually getting better and better<00:17:09.059> and<00:17:09.419> more<00:17:09.660> and<00:17:09.720> more<00:17:09.839> feasible<00:17:10.140> things 00:17:10.370 --> 00:17:10.380 align:start position:0% better and more and more feasible things 00:17:10.380 --> 00:17:11.990 align:start position:0% better and more and more feasible things like<00:17:10.559> fully<00:17:11.040> homomorphic<00:17:11.579> encryption 00:17:11.990 --> 00:17:12.000 align:start position:0% like fully homomorphic encryption 00:17:12.000 --> 00:17:14.150 align:start position:0% like fully homomorphic encryption multi-party<00:17:12.660> computation<00:17:13.079> even<00:17:13.799> really<00:17:13.980> far 00:17:14.150 --> 00:17:14.160 align:start position:0% multi-party computation even really far 00:17:14.160 --> 00:17:15.710 align:start position:0% multi-party computation even really far out<00:17:14.339> things<00:17:14.520> like<00:17:14.720> indistinguishability 00:17:15.710 --> 00:17:15.720 align:start position:0% out things like indistinguishability 00:17:15.720 --> 00:17:18.590 align:start position:0% out things like indistinguishability obfuscation<00:17:16.500> uh<00:17:17.339> and<00:17:17.579> more 00:17:18.590 --> 00:17:18.600 align:start position:0% obfuscation uh and more 00:17:18.600 --> 00:17:21.289 align:start position:0% obfuscation uh and more um<00:17:18.720> oh<00:17:19.020> and<00:17:19.260> you<00:17:19.620> know<00:17:19.740> I<00:17:20.400> there's<00:17:20.819> a<00:17:21.000> couple<00:17:21.120> of 00:17:21.289 --> 00:17:21.299 align:start position:0% um oh and you know I there's a couple of 00:17:21.299 --> 00:17:22.909 align:start position:0% um oh and you know I there's a couple of folks<00:17:21.600> who<00:17:21.780> have<00:17:21.959> sort<00:17:22.260> of<00:17:22.380> independently 00:17:22.909 --> 00:17:22.919 align:start position:0% folks who have sort of independently 00:17:22.919 --> 00:17:24.289 align:start position:0% folks who have sort of independently come<00:17:23.100> up<00:17:23.220> with<00:17:23.400> this<00:17:23.579> categorization<00:17:24.120> or 00:17:24.289 --> 00:17:24.299 align:start position:0% come up with this categorization or 00:17:24.299 --> 00:17:25.610 align:start position:0% come up with this categorization or framework<00:17:24.600> I<00:17:24.780> believe<00:17:24.839> this<00:17:25.020> Thursday<00:17:25.199> team 00:17:25.610 --> 00:17:25.620 align:start position:0% framework I believe this Thursday team 00:17:25.620 --> 00:17:28.130 align:start position:0% framework I believe this Thursday team calls<00:17:25.919> these<00:17:26.160> computational<00:17:26.640> crypto<00:17:27.179> systems 00:17:28.130 --> 00:17:28.140 align:start position:0% calls these computational crypto systems 00:17:28.140 --> 00:17:30.409 align:start position:0% calls these computational crypto systems um<00:17:28.260> so<00:17:28.380> you<00:17:28.679> know<00:17:28.740> very<00:17:28.980> similar<00:17:29.400> in<00:17:30.179> general 00:17:30.409 --> 00:17:30.419 align:start position:0% um so you know very similar in general 00:17:30.419 --> 00:17:31.850 align:start position:0% um so you know very similar in general Spirit<00:17:30.840> to<00:17:31.200> what<00:17:31.440> we're<00:17:31.559> calling 00:17:31.850 --> 00:17:31.860 align:start position:0% Spirit to what we're calling 00:17:31.860 --> 00:17:34.490 align:start position:0% Spirit to what we're calling programmable<00:17:32.340> cryptography 00:17:34.490 --> 00:17:34.500 align:start position:0% programmable cryptography 00:17:34.500 --> 00:17:36.770 align:start position:0% programmable cryptography okay<00:17:34.980> so<00:17:35.940> um 00:17:36.770 --> 00:17:36.780 align:start position:0% okay so um 00:17:36.780 --> 00:17:41.029 align:start position:0% okay so um the<00:17:37.559> second<00:17:37.740> part<00:17:38.160> of<00:17:39.120> this<00:17:40.020> basically<00:17:40.620> thesis 00:17:41.029 --> 00:17:41.039 align:start position:0% the second part of this basically thesis 00:17:41.039 --> 00:17:44.150 align:start position:0% the second part of this basically thesis is<00:17:41.700> that<00:17:42.000> programmable<00:17:42.660> cryptography<00:17:43.500> uh 00:17:44.150 --> 00:17:44.160 align:start position:0% is that programmable cryptography uh 00:17:44.160 --> 00:17:45.909 align:start position:0% is that programmable cryptography uh itself<00:17:44.460> seems<00:17:44.760> like<00:17:44.820> a<00:17:44.940> very<00:17:45.059> powerful<00:17:45.360> tool 00:17:45.909 --> 00:17:45.919 align:start position:0% itself seems like a very powerful tool 00:17:45.919 --> 00:17:48.650 align:start position:0% itself seems like a very powerful tool blockchains<00:17:46.919> are<00:17:47.280> also<00:17:47.460> a<00:17:47.640> very<00:17:47.820> powerful<00:17:48.179> a 00:17:48.650 --> 00:17:48.660 align:start position:0% blockchains are also a very powerful a 00:17:48.660 --> 00:17:50.690 align:start position:0% blockchains are also a very powerful a powerful<00:17:49.020> tool<00:17:49.440> but<00:17:50.100> it's<00:17:50.220> not<00:17:50.340> sort<00:17:50.520> of<00:17:50.580> a 00:17:50.690 --> 00:17:50.700 align:start position:0% powerful tool but it's not sort of a 00:17:50.700 --> 00:17:54.049 align:start position:0% powerful tool but it's not sort of a priori<00:17:51.059> obvious<00:17:51.480> uh<00:17:52.440> like<00:17:53.100> why<00:17:53.640> these<00:17:53.940> two 00:17:54.049 --> 00:17:54.059 align:start position:0% priori obvious uh like why these two 00:17:54.059 --> 00:17:55.789 align:start position:0% priori obvious uh like why these two things<00:17:54.240> are<00:17:54.660> related<00:17:54.960> to<00:17:55.140> each<00:17:55.260> other<00:17:55.380> except 00:17:55.789 --> 00:17:55.799 align:start position:0% things are related to each other except 00:17:55.799 --> 00:17:57.890 align:start position:0% things are related to each other except that<00:17:55.919> they<00:17:56.160> both<00:17:56.340> sort<00:17:56.940> of<00:17:57.000> derive<00:17:57.480> from 00:17:57.890 --> 00:17:57.900 align:start position:0% that they both sort of derive from 00:17:57.900 --> 00:18:00.169 align:start position:0% that they both sort of derive from similar<00:17:58.380> mathematical<00:17:59.160> principles<00:17:59.640> but<00:17:59.880> I 00:18:00.169 --> 00:18:00.179 align:start position:0% similar mathematical principles but I 00:18:00.179 --> 00:18:01.669 align:start position:0% similar mathematical principles but I claim<00:18:00.419> that<00:18:00.480> there's<00:18:00.660> actually<00:18:00.900> a<00:18:01.260> very<00:18:01.380> deep 00:18:01.669 --> 00:18:01.679 align:start position:0% claim that there's actually a very deep 00:18:01.679 --> 00:18:03.830 align:start position:0% claim that there's actually a very deep and<00:18:01.919> complementary<00:18:02.520> uh<00:18:03.179> marriage<00:18:03.539> between 00:18:03.830 --> 00:18:03.840 align:start position:0% and complementary uh marriage between 00:18:03.840 --> 00:18:07.370 align:start position:0% and complementary uh marriage between these<00:18:04.740> two<00:18:05.039> powerful<00:18:05.460> things<00:18:05.840> and<00:18:06.840> to<00:18:07.260> explain 00:18:07.370 --> 00:18:07.380 align:start position:0% these two powerful things and to explain 00:18:07.380 --> 00:18:08.990 align:start position:0% these two powerful things and to explain why<00:18:07.679> I<00:18:07.799> think<00:18:07.919> that<00:18:08.039> is<00:18:08.160> first<00:18:08.460> I<00:18:08.640> want<00:18:08.760> to<00:18:08.880> give 00:18:08.990 --> 00:18:09.000 align:start position:0% why I think that is first I want to give 00:18:09.000 --> 00:18:12.110 align:start position:0% why I think that is first I want to give my<00:18:09.360> kind<00:18:09.600> of<00:18:09.720> mental<00:18:10.620> image<00:18:11.039> of<00:18:11.400> what<00:18:11.640> ethereum 00:18:12.110 --> 00:18:12.120 align:start position:0% my kind of mental image of what ethereum 00:18:12.120 --> 00:18:14.450 align:start position:0% my kind of mental image of what ethereum as<00:18:12.299> a<00:18:12.480> data<00:18:12.720> availability<00:18:13.080> layer<00:18:13.679> looks<00:18:14.280> like 00:18:14.450 --> 00:18:14.460 align:start position:0% as a data availability layer looks like 00:18:14.460 --> 00:18:16.909 align:start position:0% as a data availability layer looks like say<00:18:15.120> like<00:18:15.360> five<00:18:15.660> or<00:18:15.960> ten<00:18:16.140> years<00:18:16.260> out<00:18:16.500> from<00:18:16.740> now 00:18:16.909 --> 00:18:16.919 align:start position:0% say like five or ten years out from now 00:18:16.919 --> 00:18:18.590 align:start position:0% say like five or ten years out from now so<00:18:17.280> in<00:18:17.580> my<00:18:17.700> head<00:18:17.820> the<00:18:18.000> way<00:18:18.120> that<00:18:18.240> I<00:18:18.419> kind<00:18:18.539> of 00:18:18.590 --> 00:18:18.600 align:start position:0% so in my head the way that I kind of 00:18:18.600 --> 00:18:20.750 align:start position:0% so in my head the way that I kind of conceptualize<00:18:19.260> the<00:18:19.740> idea<00:18:20.039> of<00:18:20.400> you<00:18:20.700> know 00:18:20.750 --> 00:18:20.760 align:start position:0% conceptualize the idea of you know 00:18:20.760 --> 00:18:22.190 align:start position:0% conceptualize the idea of you know ethereum<00:18:21.179> the<00:18:21.299> global<00:18:21.539> data<00:18:21.840> availability 00:18:22.190 --> 00:18:22.200 align:start position:0% ethereum the global data availability 00:18:22.200 --> 00:18:24.770 align:start position:0% ethereum the global data availability layer<00:18:22.799> is<00:18:23.220> I<00:18:23.640> think<00:18:23.700> of<00:18:23.880> ethereum<00:18:24.299> almost<00:18:24.480> as 00:18:24.770 --> 00:18:24.780 align:start position:0% layer is I think of ethereum almost as 00:18:24.780 --> 00:18:27.490 align:start position:0% layer is I think of ethereum almost as this<00:18:25.020> like<00:18:25.260> you<00:18:25.860> know<00:18:25.919> giant<00:18:26.520> super<00:18:26.940> thick 00:18:27.490 --> 00:18:27.500 align:start position:0% this like you know giant super thick 00:18:27.500 --> 00:18:31.070 align:start position:0% this like you know giant super thick coaxial<00:18:28.500> cable<00:18:29.120> that<00:18:30.120> basically<00:18:30.480> streams 00:18:31.070 --> 00:18:31.080 align:start position:0% coaxial cable that basically streams 00:18:31.080 --> 00:18:32.810 align:start position:0% coaxial cable that basically streams Humanities<00:18:31.559> like<00:18:31.860> Global<00:18:32.340> stream<00:18:32.580> of 00:18:32.810 --> 00:18:32.820 align:start position:0% Humanities like Global stream of 00:18:32.820 --> 00:18:33.950 align:start position:0% Humanities like Global stream of Consciousness 00:18:33.950 --> 00:18:33.960 align:start position:0% Consciousness 00:18:33.960 --> 00:18:35.990 align:start position:0% Consciousness um<00:18:34.020> so<00:18:34.140> Humanities<00:18:34.559> you<00:18:34.740> know<00:18:34.860> promises<00:18:35.340> bets 00:18:35.990 --> 00:18:36.000 align:start position:0% um so Humanities you know promises bets 00:18:36.000 --> 00:18:38.870 align:start position:0% um so Humanities you know promises bets Secrets<00:18:36.360> debts<00:18:36.720> dreams<00:18:37.440> etc<00:18:37.799> etc<00:18:37.919> and<00:18:38.760> this 00:18:38.870 --> 00:18:38.880 align:start position:0% Secrets debts dreams etc etc and this 00:18:38.880 --> 00:18:41.990 align:start position:0% Secrets debts dreams etc etc and this coaxial<00:18:39.299> cable<00:18:39.660> is<00:18:40.559> uh<00:18:41.280> you<00:18:41.520> know<00:18:41.640> made 00:18:41.990 --> 00:18:42.000 align:start position:0% coaxial cable is uh you know made 00:18:42.000 --> 00:18:44.870 align:start position:0% coaxial cable is uh you know made available<00:18:42.380> to<00:18:43.380> any<00:18:43.919> person<00:18:44.160> or<00:18:44.520> Computing 00:18:44.870 --> 00:18:44.880 align:start position:0% available to any person or Computing 00:18:44.880 --> 00:18:46.610 align:start position:0% available to any person or Computing device<00:18:45.120> in<00:18:45.360> the<00:18:45.480> world<00:18:45.600> so 00:18:46.610 --> 00:18:46.620 align:start position:0% device in the world so 00:18:46.620 --> 00:18:49.130 align:start position:0% device in the world so um<00:18:46.679> you<00:18:46.980> know<00:18:47.039> any<00:18:47.460> phone<00:18:47.940> any<00:18:48.419> computer<00:18:48.720> that 00:18:49.130 --> 00:18:49.140 align:start position:0% um you know any phone any computer that 00:18:49.140 --> 00:18:50.830 align:start position:0% um you know any phone any computer that like<00:18:49.320> lives<00:18:49.740> on<00:18:50.160> some<00:18:50.340> you<00:18:50.640> know<00:18:50.760> like 00:18:50.830 --> 00:18:50.840 align:start position:0% like lives on some you know like 00:18:50.840 --> 00:18:52.970 align:start position:0% like lives on some you know like institutional<00:18:51.840> server<00:18:52.260> anything<00:18:52.500> like<00:18:52.740> that 00:18:52.970 --> 00:18:52.980 align:start position:0% institutional server anything like that 00:18:52.980 --> 00:18:54.890 align:start position:0% institutional server anything like that can<00:18:53.400> hook<00:18:53.640> into<00:18:53.880> the<00:18:54.120> one<00:18:54.299> gigabyte<00:18:54.780> per 00:18:54.890 --> 00:18:54.900 align:start position:0% can hook into the one gigabyte per 00:18:54.900 --> 00:18:57.110 align:start position:0% can hook into the one gigabyte per second<00:18:55.080> canonical<00:18:55.919> data<00:18:56.340> stream<00:18:56.460> look<00:18:56.940> up 00:18:57.110 --> 00:18:57.120 align:start position:0% second canonical data stream look up 00:18:57.120 --> 00:18:58.250 align:start position:0% second canonical data stream look up data<00:18:57.419> and<00:18:57.539> know<00:18:57.720> that<00:18:57.840> they're<00:18:57.900> seeing 00:18:58.250 --> 00:18:58.260 align:start position:0% data and know that they're seeing 00:18:58.260 --> 00:18:59.690 align:start position:0% data and know that they're seeing exactly<00:18:58.559> the<00:18:58.740> same<00:18:58.860> thing<00:18:58.980> as<00:18:59.100> someone<00:18:59.280> across 00:18:59.690 --> 00:18:59.700 align:start position:0% exactly the same thing as someone across 00:18:59.700 --> 00:19:02.930 align:start position:0% exactly the same thing as someone across the<00:18:59.820> world<00:19:00.000> is<00:19:00.539> seeing 00:19:02.930 --> 00:19:02.940 align:start position:0% the world is seeing 00:19:02.940 --> 00:19:05.330 align:start position:0% the world is seeing now<00:19:03.539> right<00:19:03.900> now<00:19:04.140> this<00:19:04.620> data<00:19:04.919> stream<00:19:04.980> is 00:19:05.330 --> 00:19:05.340 align:start position:0% now right now this data stream is 00:19:05.340 --> 00:19:07.909 align:start position:0% now right now this data stream is completely<00:19:05.700> transparent<00:19:06.419> and<00:19:07.380> that<00:19:07.500> has<00:19:07.679> been 00:19:07.909 --> 00:19:07.919 align:start position:0% completely transparent and that has been 00:19:07.919 --> 00:19:10.070 align:start position:0% completely transparent and that has been a<00:19:08.340> design<00:19:08.460> decision<00:19:08.940> that<00:19:09.600> has<00:19:09.840> been 00:19:10.070 --> 00:19:10.080 align:start position:0% a design decision that has been 00:19:10.080 --> 00:19:12.470 align:start position:0% a design decision that has been necessary<00:19:10.620> in<00:19:10.919> order<00:19:11.039> to<00:19:11.220> gain<00:19:11.460> acceptance<00:19:12.120> of 00:19:12.470 --> 00:19:12.480 align:start position:0% necessary in order to gain acceptance of 00:19:12.480 --> 00:19:13.870 align:start position:0% necessary in order to gain acceptance of this<00:19:12.720> particular 00:19:13.870 --> 00:19:13.880 align:start position:0% this particular 00:19:13.880 --> 00:19:15.890 align:start position:0% this particular data<00:19:14.880> stream<00:19:14.940> that<00:19:15.299> we're<00:19:15.419> wanting<00:19:15.660> to<00:19:15.780> claim 00:19:15.890 --> 00:19:15.900 align:start position:0% data stream that we're wanting to claim 00:19:15.900 --> 00:19:17.390 align:start position:0% data stream that we're wanting to claim is<00:19:16.080> the<00:19:16.200> canonical<00:19:16.559> data<00:19:16.919> stream<00:19:16.980> or<00:19:17.220> the 00:19:17.390 --> 00:19:17.400 align:start position:0% is the canonical data stream or the 00:19:17.400 --> 00:19:19.970 align:start position:0% is the canonical data stream or the legitimate<00:19:18.299> data<00:19:18.720> stream<00:19:18.840> so<00:19:19.559> in<00:19:19.679> order<00:19:19.860> to 00:19:19.970 --> 00:19:19.980 align:start position:0% legitimate data stream so in order to 00:19:19.980 --> 00:19:21.890 align:start position:0% legitimate data stream so in order to build<00:19:20.160> acceptance<00:19:20.640> we<00:19:21.360> have<00:19:21.480> this<00:19:21.600> principle 00:19:21.890 --> 00:19:21.900 align:start position:0% build acceptance we have this principle 00:19:21.900 --> 00:19:23.690 align:start position:0% build acceptance we have this principle of<00:19:22.080> don't<00:19:22.200> trust<00:19:22.620> verify<00:19:23.160> and<00:19:23.280> in<00:19:23.400> order<00:19:23.580> to 00:19:23.690 --> 00:19:23.700 align:start position:0% of don't trust verify and in order to 00:19:23.700 --> 00:19:25.669 align:start position:0% of don't trust verify and in order to verify<00:19:24.179> you<00:19:24.299> need<00:19:24.419> to<00:19:24.539> be<00:19:24.600> able<00:19:24.720> to<00:19:24.840> see<00:19:25.080> all<00:19:25.559> of 00:19:25.669 --> 00:19:25.679 align:start position:0% verify you need to be able to see all of 00:19:25.679 --> 00:19:27.710 align:start position:0% verify you need to be able to see all of the<00:19:25.919> data<00:19:26.220> but<00:19:27.059> I<00:19:27.179> claim<00:19:27.360> that<00:19:27.419> this<00:19:27.600> is 00:19:27.710 --> 00:19:27.720 align:start position:0% the data but I claim that this is 00:19:27.720 --> 00:19:30.650 align:start position:0% the data but I claim that this is actually<00:19:27.900> extremely<00:19:28.620> limiting<00:19:29.360> there<00:19:30.360> is<00:19:30.480> a 00:19:30.650 --> 00:19:30.660 align:start position:0% actually extremely limiting there is a 00:19:30.660 --> 00:19:33.289 align:start position:0% actually extremely limiting there is a wide<00:19:30.900> class<00:19:31.080> of<00:19:31.320> applications<00:19:31.940> that<00:19:32.940> you 00:19:33.289 --> 00:19:33.299 align:start position:0% wide class of applications that you 00:19:33.299 --> 00:19:34.610 align:start position:0% wide class of applications that you might<00:19:33.419> care<00:19:33.600> about<00:19:33.780> to<00:19:33.960> build<00:19:34.080> where<00:19:34.380> you 00:19:34.610 --> 00:19:34.620 align:start position:0% might care about to build where you 00:19:34.620 --> 00:19:36.770 align:start position:0% might care about to build where you don't<00:19:34.799> want<00:19:35.100> every<00:19:35.700> piece<00:19:36.059> of<00:19:36.179> data<00:19:36.480> to<00:19:36.660> be 00:19:36.770 --> 00:19:36.780 align:start position:0% don't want every piece of data to be 00:19:36.780 --> 00:19:38.169 align:start position:0% don't want every piece of data to be completely<00:19:37.140> public 00:19:38.169 --> 00:19:38.179 align:start position:0% completely public 00:19:38.179 --> 00:19:39.950 align:start position:0% completely public and<00:19:39.179> I<00:19:39.240> think<00:19:39.360> that<00:19:39.419> when<00:19:39.600> a<00:19:39.720> lot<00:19:39.840> of<00:19:39.900> people 00:19:39.950 --> 00:19:39.960 align:start position:0% and I think that when a lot of people 00:19:39.960 --> 00:19:41.630 align:start position:0% and I think that when a lot of people talk<00:19:40.200> about<00:19:40.380> this<00:19:40.679> idea<00:19:40.919> of<00:19:41.039> privacy<00:19:41.400> or 00:19:41.630 --> 00:19:41.640 align:start position:0% talk about this idea of privacy or 00:19:41.640 --> 00:19:43.250 align:start position:0% talk about this idea of privacy or information<00:19:41.820> asymmetry<00:19:42.720> you<00:19:43.020> know<00:19:43.080> people 00:19:43.250 --> 00:19:43.260 align:start position:0% information asymmetry you know people 00:19:43.260 --> 00:19:45.650 align:start position:0% information asymmetry you know people have<00:19:43.500> various<00:19:43.799> different<00:19:43.980> beliefs<00:19:44.460> on<00:19:44.880> uh 00:19:45.650 --> 00:19:45.660 align:start position:0% have various different beliefs on uh 00:19:45.660 --> 00:19:48.289 align:start position:0% have various different beliefs on uh like<00:19:46.020> various<00:19:46.980> ideological<00:19:47.640> nuances<00:19:48.120> around 00:19:48.289 --> 00:19:48.299 align:start position:0% like various ideological nuances around 00:19:48.299 --> 00:19:50.330 align:start position:0% like various ideological nuances around privacy<00:19:48.720> but<00:19:48.960> I<00:19:49.080> want<00:19:49.320> to<00:19:49.380> go<00:19:49.559> even<00:19:49.980> a<00:19:50.160> level 00:19:50.330 --> 00:19:50.340 align:start position:0% privacy but I want to go even a level 00:19:50.340 --> 00:19:51.650 align:start position:0% privacy but I want to go even a level lower<00:19:50.580> to<00:19:50.760> explain<00:19:50.880> why<00:19:51.179> I<00:19:51.299> think<00:19:51.419> this<00:19:51.539> is 00:19:51.650 --> 00:19:51.660 align:start position:0% lower to explain why I think this is 00:19:51.660 --> 00:19:53.390 align:start position:0% lower to explain why I think this is important<00:19:51.960> privacy<00:19:52.559> is<00:19:52.799> important<00:19:53.039> not<00:19:53.220> just 00:19:53.390 --> 00:19:53.400 align:start position:0% important privacy is important not just 00:19:53.400 --> 00:19:55.789 align:start position:0% important privacy is important not just as<00:19:53.580> a<00:19:53.820> matter<00:19:53.940> of<00:19:54.179> ideology<00:19:54.539> but<00:19:55.140> simply<00:19:55.440> as<00:19:55.620> a 00:19:55.789 --> 00:19:55.799 align:start position:0% as a matter of ideology but simply as a 00:19:55.799 --> 00:19:57.710 align:start position:0% as a matter of ideology but simply as a matter<00:19:55.919> of<00:19:56.100> mechanics<00:19:56.820> there's<00:19:57.480> certain 00:19:57.710 --> 00:19:57.720 align:start position:0% matter of mechanics there's certain 00:19:57.720 --> 00:19:59.570 align:start position:0% matter of mechanics there's certain coordination<00:19:58.380> systems<00:19:58.860> that<00:19:59.100> just<00:19:59.280> don't 00:19:59.570 --> 00:19:59.580 align:start position:0% coordination systems that just don't 00:19:59.580 --> 00:20:01.130 align:start position:0% coordination systems that just don't work<00:19:59.940> unless<00:20:00.539> you<00:20:00.720> have<00:20:00.840> information 00:20:01.130 --> 00:20:01.140 align:start position:0% work unless you have information 00:20:01.140 --> 00:20:03.890 align:start position:0% work unless you have information asymmetry<00:20:01.919> and<00:20:02.100> in<00:20:02.220> fact<00:20:02.340> most<00:20:02.940> of<00:20:03.660> the 00:20:03.890 --> 00:20:03.900 align:start position:0% asymmetry and in fact most of the 00:20:03.900 --> 00:20:05.870 align:start position:0% asymmetry and in fact most of the complex<00:20:04.200> systems<00:20:04.860> that<00:20:05.220> we<00:20:05.340> see<00:20:05.520> in<00:20:05.640> the<00:20:05.760> world 00:20:05.870 --> 00:20:05.880 align:start position:0% complex systems that we see in the world 00:20:05.880 --> 00:20:07.250 align:start position:0% complex systems that we see in the world today<00:20:06.059> and<00:20:06.360> most<00:20:06.480> of<00:20:06.600> the<00:20:06.660> organizations<00:20:07.080> we 00:20:07.250 --> 00:20:07.260 align:start position:0% today and most of the organizations we 00:20:07.260 --> 00:20:08.930 align:start position:0% today and most of the organizations we have<00:20:07.380> in<00:20:07.500> the<00:20:07.620> world<00:20:07.740> rely<00:20:08.280> on<00:20:08.460> the<00:20:08.580> idea<00:20:08.760> that 00:20:08.930 --> 00:20:08.940 align:start position:0% have in the world rely on the idea that 00:20:08.940 --> 00:20:11.090 align:start position:0% have in the world rely on the idea that different<00:20:09.179> people<00:20:09.480> know<00:20:10.380> different<00:20:10.620> stuff 00:20:11.090 --> 00:20:11.100 align:start position:0% different people know different stuff 00:20:11.100 --> 00:20:13.610 align:start position:0% different people know different stuff and<00:20:11.460> can<00:20:11.700> do<00:20:11.940> different<00:20:12.240> stuff 00:20:13.610 --> 00:20:13.620 align:start position:0% and can do different stuff 00:20:13.620 --> 00:20:16.190 align:start position:0% and can do different stuff so<00:20:14.280> the<00:20:14.760> way<00:20:14.940> that<00:20:15.000> I<00:20:15.120> think<00:20:15.240> about<00:20:15.360> this<00:20:15.720> is 00:20:16.190 --> 00:20:16.200 align:start position:0% so the way that I think about this is 00:20:16.200 --> 00:20:17.870 align:start position:0% so the way that I think about this is that<00:20:16.440> what<00:20:16.799> we<00:20:16.919> would<00:20:17.039> really<00:20:17.220> like<00:20:17.400> to<00:20:17.580> do<00:20:17.700> is 00:20:17.870 --> 00:20:17.880 align:start position:0% that what we would really like to do is 00:20:17.880 --> 00:20:19.370 align:start position:0% that what we would really like to do is we'd<00:20:18.059> like<00:20:18.179> to<00:20:18.299> be<00:20:18.419> able<00:20:18.539> to<00:20:18.660> enforce<00:20:19.140> read 00:20:19.370 --> 00:20:19.380 align:start position:0% we'd like to be able to enforce read 00:20:19.380 --> 00:20:21.470 align:start position:0% we'd like to be able to enforce read write<00:20:19.679> execute<00:20:20.280> permissions<00:20:20.760> on<00:20:21.360> this 00:20:21.470 --> 00:20:21.480 align:start position:0% write execute permissions on this 00:20:21.480 --> 00:20:24.590 align:start position:0% write execute permissions on this canonical<00:20:22.020> data<00:20:22.500> stream<00:20:22.679> that<00:20:23.460> is<00:20:23.700> uh<00:20:24.360> the 00:20:24.590 --> 00:20:24.600 align:start position:0% canonical data stream that is uh the 00:20:24.600 --> 00:20:26.570 align:start position:0% canonical data stream that is uh the blockchain<00:20:25.020> and<00:20:25.740> the<00:20:25.860> way<00:20:26.039> that<00:20:26.160> we<00:20:26.280> do<00:20:26.400> this 00:20:26.570 --> 00:20:26.580 align:start position:0% blockchain and the way that we do this 00:20:26.580 --> 00:20:28.730 align:start position:0% blockchain and the way that we do this is<00:20:27.120> you<00:20:27.539> know<00:20:27.660> in<00:20:28.020> fact<00:20:28.140> programmable 00:20:28.730 --> 00:20:28.740 align:start position:0% is you know in fact programmable 00:20:28.740 --> 00:20:30.409 align:start position:0% is you know in fact programmable cryptography<00:20:29.340> programmable<00:20:29.760> cryptography 00:20:30.409 --> 00:20:30.419 align:start position:0% cryptography programmable cryptography 00:20:30.419 --> 00:20:33.110 align:start position:0% cryptography programmable cryptography gives<00:20:30.780> us<00:20:30.960> these<00:20:31.559> expressive<00:20:32.100> tools<00:20:32.880> and 00:20:33.110 --> 00:20:33.120 align:start position:0% gives us these expressive tools and 00:20:33.120 --> 00:20:34.850 align:start position:0% gives us these expressive tools and languages<00:20:33.419> for<00:20:33.720> enforcing<00:20:34.140> read<00:20:34.320> permissions 00:20:34.850 --> 00:20:34.860 align:start position:0% languages for enforcing read permissions 00:20:34.860 --> 00:20:36.470 align:start position:0% languages for enforcing read permissions like<00:20:35.160> we<00:20:35.280> mentioned<00:20:35.580> with<00:20:35.820> things<00:20:36.179> like 00:20:36.470 --> 00:20:36.480 align:start position:0% like we mentioned with things like 00:20:36.480 --> 00:20:38.990 align:start position:0% like we mentioned with things like witness<00:20:36.840> encryption<00:20:37.500> or<00:20:38.160> write<00:20:38.340> or<00:20:38.580> execute 00:20:38.990 --> 00:20:39.000 align:start position:0% witness encryption or write or execute 00:20:39.000 --> 00:20:40.850 align:start position:0% witness encryption or write or execute permissions<00:20:39.480> which<00:20:40.380> we're<00:20:40.500> seeing<00:20:40.740> with 00:20:40.850 --> 00:20:40.860 align:start position:0% permissions which we're seeing with 00:20:40.860 --> 00:20:44.630 align:start position:0% permissions which we're seeing with things<00:20:41.039> like<00:20:41.400> you<00:20:41.820> know<00:20:41.940> ZK<00:20:42.360> snarks<00:20:43.340> and<00:20:44.340> smart 00:20:44.630 --> 00:20:44.640 align:start position:0% things like you know ZK snarks and smart 00:20:44.640 --> 00:20:46.549 align:start position:0% things like you know ZK snarks and smart contracts<00:20:45.120> and<00:20:45.240> more 00:20:46.549 --> 00:20:46.559 align:start position:0% contracts and more 00:20:46.559 --> 00:20:49.789 align:start position:0% contracts and more so<00:20:46.919> to<00:20:47.100> give<00:20:47.220> just<00:20:47.400> the<00:20:47.520> toy<00:20:47.820> example<00:20:48.240> of<00:20:49.140> uh 00:20:49.789 --> 00:20:49.799 align:start position:0% so to give just the toy example of uh 00:20:49.799 --> 00:20:52.070 align:start position:0% so to give just the toy example of uh why<00:20:50.400> this<00:20:50.760> kind<00:20:51.000> of<00:20:51.120> permissioning<00:20:51.780> or<00:20:51.900> access 00:20:52.070 --> 00:20:52.080 align:start position:0% why this kind of permissioning or access 00:20:52.080 --> 00:20:53.990 align:start position:0% why this kind of permissioning or access control<00:20:52.380> is<00:20:52.679> really<00:20:52.860> important<00:20:53.220> I<00:20:53.820> want<00:20:53.940> to 00:20:53.990 --> 00:20:54.000 align:start position:0% control is really important I want to 00:20:54.000 --> 00:20:57.350 align:start position:0% control is really important I want to consider<00:20:54.240> the<00:20:54.360> example<00:20:54.660> of<00:20:54.780> games<00:20:55.080> so<00:20:56.360> for 00:20:57.350 --> 00:20:57.360 align:start position:0% consider the example of games so for 00:20:57.360 --> 00:21:00.289 align:start position:0% consider the example of games so for example<00:20:57.600> let's<00:20:58.020> uh<00:20:58.500> let's<00:20:58.740> consider<00:20:58.980> poker<00:20:59.460> in 00:21:00.289 --> 00:21:00.299 align:start position:0% example let's uh let's consider poker in 00:21:00.299 --> 00:21:02.450 align:start position:0% example let's uh let's consider poker in poker<00:21:00.720> a<00:21:01.320> lot<00:21:01.440> of<00:21:01.620> the<00:21:01.799> depth<00:21:02.100> of<00:21:02.280> the<00:21:02.400> game 00:21:02.450 --> 00:21:02.460 align:start position:0% poker a lot of the depth of the game 00:21:02.460 --> 00:21:04.430 align:start position:0% poker a lot of the depth of the game relies<00:21:02.820> on<00:21:03.000> the<00:21:03.120> fact<00:21:03.240> that<00:21:03.480> I<00:21:03.720> know<00:21:03.840> my<00:21:04.080> cards 00:21:04.430 --> 00:21:04.440 align:start position:0% relies on the fact that I know my cards 00:21:04.440 --> 00:21:06.230 align:start position:0% relies on the fact that I know my cards but<00:21:04.799> I<00:21:04.919> don't<00:21:05.039> know<00:21:05.280> your<00:21:05.460> cards<00:21:05.880> and<00:21:06.000> you<00:21:06.120> know 00:21:06.230 --> 00:21:06.240 align:start position:0% but I don't know your cards and you know 00:21:06.240 --> 00:21:07.669 align:start position:0% but I don't know your cards and you know your<00:21:06.360> cards<00:21:06.660> but<00:21:06.780> you<00:21:06.900> don't<00:21:07.020> know<00:21:07.140> my<00:21:07.320> cards 00:21:07.669 --> 00:21:07.679 align:start position:0% your cards but you don't know my cards 00:21:07.679 --> 00:21:11.450 align:start position:0% your cards but you don't know my cards poker<00:21:08.520> as<00:21:08.640> a<00:21:08.820> game<00:21:08.940> would<00:21:09.360> simply<00:21:09.720> not<00:21:10.200> work<00:21:10.620> if 00:21:11.450 --> 00:21:11.460 align:start position:0% poker as a game would simply not work if 00:21:11.460 --> 00:21:13.490 align:start position:0% poker as a game would simply not work if we<00:21:11.760> knew<00:21:12.059> each<00:21:12.299> other's<00:21:12.600> cards<00:21:13.020> it<00:21:13.200> would<00:21:13.320> be 00:21:13.490 --> 00:21:13.500 align:start position:0% we knew each other's cards it would be 00:21:13.500 --> 00:21:15.650 align:start position:0% we knew each other's cards it would be completely<00:21:13.860> degenerate<00:21:14.460> right<00:21:14.700> like<00:21:15.000> it 00:21:15.650 --> 00:21:15.660 align:start position:0% completely degenerate right like it 00:21:15.660 --> 00:21:16.730 align:start position:0% completely degenerate right like it wouldn't<00:21:15.840> really<00:21:16.080> make<00:21:16.260> sense<00:21:16.440> it<00:21:16.620> wouldn't 00:21:16.730 --> 00:21:16.740 align:start position:0% wouldn't really make sense it wouldn't 00:21:16.740 --> 00:21:18.770 align:start position:0% wouldn't really make sense it wouldn't be<00:21:16.980> any<00:21:17.100> fun 00:21:18.770 --> 00:21:18.780 align:start position:0% be any fun 00:21:18.780 --> 00:21:21.409 align:start position:0% be any fun um<00:21:18.840> and<00:21:19.679> uh<00:21:20.220> you<00:21:20.580> know<00:21:20.640> a<00:21:20.820> slightly<00:21:21.179> more 00:21:21.409 --> 00:21:21.419 align:start position:0% um and uh you know a slightly more 00:21:21.419 --> 00:21:23.630 align:start position:0% um and uh you know a slightly more complex<00:21:22.020> example<00:21:22.380> of<00:21:22.559> this<00:21:22.679> might<00:21:22.919> be<00:21:23.100> uh 00:21:23.630 --> 00:21:23.640 align:start position:0% complex example of this might be uh 00:21:23.640 --> 00:21:26.390 align:start position:0% complex example of this might be uh strategy<00:21:24.059> game<00:21:24.179> so<00:21:24.539> a<00:21:24.840> couple<00:21:25.020> of<00:21:25.140> days<00:21:25.320> ago<00:21:25.620> we 00:21:26.390 --> 00:21:26.400 align:start position:0% strategy game so a couple of days ago we 00:21:26.400 --> 00:21:28.250 align:start position:0% strategy game so a couple of days ago we had<00:21:26.520> a<00:21:26.640> talk<00:21:26.760> on<00:21:26.880> Dark<00:21:27.059> Forest<00:21:27.480> which<00:21:27.840> is<00:21:27.960> a 00:21:28.250 --> 00:21:28.260 align:start position:0% had a talk on Dark Forest which is a 00:21:28.260 --> 00:21:30.590 align:start position:0% had a talk on Dark Forest which is a fully<00:21:28.500> on<00:21:28.679> on<00:21:29.220> chain<00:21:29.640> strategy<00:21:30.120> game<00:21:30.240> you<00:21:30.480> can 00:21:30.590 --> 00:21:30.600 align:start position:0% fully on on chain strategy game you can 00:21:30.600 --> 00:21:31.789 align:start position:0% fully on on chain strategy game you can kind<00:21:30.659> of<00:21:30.780> imagine<00:21:30.900> it<00:21:31.200> as<00:21:31.320> something<00:21:31.559> like 00:21:31.789 --> 00:21:31.799 align:start position:0% kind of imagine it as something like 00:21:31.799 --> 00:21:33.950 align:start position:0% kind of imagine it as something like Starcraft<00:21:32.400> on<00:21:32.640> the<00:21:32.760> blockchain<00:21:33.120> and<00:21:33.480> one 00:21:33.950 --> 00:21:33.960 align:start position:0% Starcraft on the blockchain and one 00:21:33.960 --> 00:21:36.049 align:start position:0% Starcraft on the blockchain and one really<00:21:34.080> key<00:21:34.320> mechanic<00:21:34.679> of<00:21:34.860> Dark<00:21:34.980> Forest<00:21:35.460> is 00:21:36.049 --> 00:21:36.059 align:start position:0% really key mechanic of Dark Forest is 00:21:36.059 --> 00:21:37.850 align:start position:0% really key mechanic of Dark Forest is that<00:21:36.240> in<00:21:36.480> Dark<00:21:36.659> Forest 00:21:37.850 --> 00:21:37.860 align:start position:0% that in Dark Forest 00:21:37.860 --> 00:21:40.130 align:start position:0% that in Dark Forest um players<00:21:38.460> respective<00:21:39.120> locations<00:21:39.780> are<00:21:40.020> all 00:21:40.130 --> 00:21:40.140 align:start position:0% um players respective locations are all 00:21:40.140 --> 00:21:42.289 align:start position:0% um players respective locations are all hidden<00:21:40.559> which<00:21:40.980> gave<00:21:41.280> which<00:21:41.640> gives<00:21:41.820> the<00:21:42.000> game<00:21:42.120> a 00:21:42.289 --> 00:21:42.299 align:start position:0% hidden which gave which gives the game a 00:21:42.299 --> 00:21:44.029 align:start position:0% hidden which gave which gives the game a lot<00:21:42.419> of<00:21:42.539> its<00:21:43.380> um<00:21:43.440> you<00:21:43.620> know<00:21:43.679> relative 00:21:44.029 --> 00:21:44.039 align:start position:0% lot of its um you know relative 00:21:44.039 --> 00:21:46.549 align:start position:0% lot of its um you know relative strategic<00:21:44.700> depth<00:21:45.120> so<00:21:45.720> the<00:21:45.840> general<00:21:46.020> pattern 00:21:46.549 --> 00:21:46.559 align:start position:0% strategic depth so the general pattern 00:21:46.559 --> 00:21:49.310 align:start position:0% strategic depth so the general pattern here<00:21:46.799> with<00:21:47.159> games<00:21:47.400> is<00:21:48.240> that<00:21:48.539> uh<00:21:48.960> oftentimes 00:21:49.310 --> 00:21:49.320 align:start position:0% here with games is that uh oftentimes 00:21:49.320 --> 00:21:51.470 align:start position:0% here with games is that uh oftentimes what<00:21:49.500> we're<00:21:49.620> going<00:21:49.740> to<00:21:49.860> do<00:21:49.980> is<00:21:50.700> we're<00:21:51.179> going<00:21:51.360> to 00:21:51.470 --> 00:21:51.480 align:start position:0% what we're going to do is we're going to 00:21:51.480 --> 00:21:54.350 align:start position:0% what we're going to do is we're going to have<00:21:51.600> players<00:21:52.080> commit<00:21:52.740> to<00:21:53.100> a<00:21:53.280> state<00:21:53.460> that<00:21:54.120> they 00:21:54.350 --> 00:21:54.360 align:start position:0% have players commit to a state that they 00:21:54.360 --> 00:21:56.149 align:start position:0% have players commit to a state that they keep<00:21:54.539> private<00:21:55.080> and<00:21:55.500> whenever<00:21:55.740> they<00:21:55.919> want<00:21:56.039> to 00:21:56.149 --> 00:21:56.159 align:start position:0% keep private and whenever they want to 00:21:56.159 --> 00:21:57.950 align:start position:0% keep private and whenever they want to make<00:21:56.280> a<00:21:56.520> state<00:21:56.640> transition<00:21:57.120> they're<00:21:57.659> going<00:21:57.840> to 00:21:57.950 --> 00:21:57.960 align:start position:0% make a state transition they're going to 00:21:57.960 --> 00:22:00.110 align:start position:0% make a state transition they're going to provide<00:21:58.260> a<00:21:58.440> zero<00:21:58.740> knowledge<00:21:58.980> proof<00:21:59.400> that<00:21:59.940> they 00:22:00.110 --> 00:22:00.120 align:start position:0% provide a zero knowledge proof that they 00:22:00.120 --> 00:22:02.390 align:start position:0% provide a zero knowledge proof that they are<00:22:00.299> making<00:22:00.480> a<00:22:00.780> valid<00:22:01.020> update<00:22:01.380> on<00:22:01.799> uh<00:22:02.220> their 00:22:02.390 --> 00:22:02.400 align:start position:0% are making a valid update on uh their 00:22:02.400 --> 00:22:03.950 align:start position:0% are making a valid update on uh their private<00:22:02.700> State<00:22:02.820> and<00:22:03.120> committing<00:22:03.539> you<00:22:03.720> know<00:22:03.840> a 00:22:03.950 --> 00:22:03.960 align:start position:0% private State and committing you know a 00:22:03.960 --> 00:22:05.570 align:start position:0% private State and committing you know a valid<00:22:04.260> State<00:22:04.380> commitment<00:22:04.799> to<00:22:04.980> the<00:22:05.100> network<00:22:05.220> so 00:22:05.570 --> 00:22:05.580 align:start position:0% valid State commitment to the network so 00:22:05.580 --> 00:22:07.310 align:start position:0% valid State commitment to the network so this<00:22:06.000> proof<00:22:06.299> might<00:22:06.419> prove<00:22:06.780> something<00:22:07.020> like 00:22:07.310 --> 00:22:07.320 align:start position:0% this proof might prove something like 00:22:07.320 --> 00:22:10.190 align:start position:0% this proof might prove something like I'm<00:22:08.159> moving<00:22:08.520> my<00:22:08.880> you<00:22:09.059> know<00:22:09.120> secret<00:22:09.419> night<00:22:09.780> from 00:22:10.190 --> 00:22:10.200 align:start position:0% I'm moving my you know secret night from 00:22:10.200 --> 00:22:12.049 align:start position:0% I'm moving my you know secret night from secret<00:22:10.380> location<00:22:10.679> a<00:22:11.039> to<00:22:11.220> secret<00:22:11.400> location<00:22:11.640> B 00:22:12.049 --> 00:22:12.059 align:start position:0% secret location a to secret location B 00:22:12.059 --> 00:22:13.909 align:start position:0% secret location a to secret location B I'm<00:22:12.539> not<00:22:12.720> going<00:22:12.840> to<00:22:12.960> tell<00:22:13.080> you<00:22:13.200> what<00:22:13.380> a<00:22:13.500> or<00:22:13.740> b 00:22:13.909 --> 00:22:13.919 align:start position:0% I'm not going to tell you what a or b 00:22:13.919 --> 00:22:15.950 align:start position:0% I'm not going to tell you what a or b are<00:22:14.159> but<00:22:14.640> this<00:22:14.880> zero<00:22:15.179> knowledge<00:22:15.360> proof<00:22:15.659> proves 00:22:15.950 --> 00:22:15.960 align:start position:0% are but this zero knowledge proof proves 00:22:15.960 --> 00:22:17.570 align:start position:0% are but this zero knowledge proof proves that<00:22:16.140> you<00:22:16.380> know<00:22:16.500> there's<00:22:16.620> an<00:22:16.799> L<00:22:16.980> shape<00:22:17.340> between 00:22:17.570 --> 00:22:17.580 align:start position:0% that you know there's an L shape between 00:22:17.580 --> 00:22:18.409 align:start position:0% that you know there's an L shape between them 00:22:18.409 --> 00:22:18.419 align:start position:0% them 00:22:18.419 --> 00:22:19.850 align:start position:0% them um or<00:22:18.600> zero<00:22:18.900> knowledge<00:22:19.140> proof<00:22:19.440> might<00:22:19.559> prove 00:22:19.850 --> 00:22:19.860 align:start position:0% um or zero knowledge proof might prove 00:22:19.860 --> 00:22:22.549 align:start position:0% um or zero knowledge proof might prove something<00:22:19.980> like<00:22:20.400> drawing<00:22:21.360> some<00:22:21.720> card<00:22:22.260> I'm 00:22:22.549 --> 00:22:22.559 align:start position:0% something like drawing some card I'm 00:22:22.559 --> 00:22:23.930 align:start position:0% something like drawing some card I'm drawing<00:22:22.860> it<00:22:22.980> validly<00:22:23.400> according<00:22:23.700> to<00:22:23.820> the 00:22:23.930 --> 00:22:23.940 align:start position:0% drawing it validly according to the 00:22:23.940 --> 00:22:25.610 align:start position:0% drawing it validly according to the rules<00:22:24.179> I'm<00:22:24.659> drawing<00:22:24.960> it<00:22:25.020> out<00:22:25.140> of<00:22:25.260> a<00:22:25.320> randomly 00:22:25.610 --> 00:22:25.620 align:start position:0% rules I'm drawing it out of a randomly 00:22:25.620 --> 00:22:27.590 align:start position:0% rules I'm drawing it out of a randomly shuffled<00:22:26.039> deck<00:22:26.340> I'm<00:22:26.820> not<00:22:26.940> cheating<00:22:27.240> and<00:22:27.419> just 00:22:27.590 --> 00:22:27.600 align:start position:0% shuffled deck I'm not cheating and just 00:22:27.600 --> 00:22:29.810 align:start position:0% shuffled deck I'm not cheating and just like<00:22:27.780> continually<00:22:28.200> drawing<00:22:28.559> a<00:22:28.679> bunch<00:22:28.799> of<00:22:28.919> aces 00:22:29.810 --> 00:22:29.820 align:start position:0% like continually drawing a bunch of aces 00:22:29.820 --> 00:22:33.409 align:start position:0% like continually drawing a bunch of aces so<00:22:30.059> you<00:22:30.780> know<00:22:30.840> there's<00:22:31.140> a<00:22:31.500> bunch<00:22:31.679> of<00:22:32.220> uh<00:22:32.940> game 00:22:33.409 --> 00:22:33.419 align:start position:0% so you know there's a bunch of uh game 00:22:33.419 --> 00:22:34.909 align:start position:0% so you know there's a bunch of uh game examples<00:22:33.900> which<00:22:34.140> we<00:22:34.320> can<00:22:34.440> kind<00:22:34.620> of<00:22:34.679> Imagine 00:22:34.909 --> 00:22:34.919 align:start position:0% examples which we can kind of Imagine 00:22:34.919 --> 00:22:37.430 align:start position:0% examples which we can kind of Imagine where<00:22:35.880> the<00:22:36.179> game<00:22:36.299> just<00:22:36.600> simply<00:22:36.900> does<00:22:37.080> not<00:22:37.200> work 00:22:37.430 --> 00:22:37.440 align:start position:0% where the game just simply does not work 00:22:37.440 --> 00:22:39.169 align:start position:0% where the game just simply does not work if<00:22:37.740> all<00:22:37.919> of<00:22:37.980> the<00:22:38.100> information<00:22:38.220> is<00:22:38.640> transparent 00:22:39.169 --> 00:22:39.179 align:start position:0% if all of the information is transparent 00:22:39.179 --> 00:22:41.149 align:start position:0% if all of the information is transparent and<00:22:39.659> while<00:22:39.840> those<00:22:40.020> are<00:22:40.200> kind<00:22:40.380> of<00:22:40.500> toy<00:22:40.799> examples 00:22:41.149 --> 00:22:41.159 align:start position:0% and while those are kind of toy examples 00:22:41.159 --> 00:22:43.190 align:start position:0% and while those are kind of toy examples I<00:22:41.460> think<00:22:41.580> they<00:22:41.940> allow<00:22:42.179> us<00:22:42.299> to<00:22:42.480> start<00:22:42.659> to<00:22:42.960> hint 00:22:43.190 --> 00:22:43.200 align:start position:0% I think they allow us to start to hint 00:22:43.200 --> 00:22:45.830 align:start position:0% I think they allow us to start to hint at<00:22:43.620> this<00:22:44.159> more<00:22:44.400> complex<00:22:44.820> future<00:22:45.179> where<00:22:45.659> we're 00:22:45.830 --> 00:22:45.840 align:start position:0% at this more complex future where we're 00:22:45.840 --> 00:22:48.230 align:start position:0% at this more complex future where we're using<00:22:46.080> blockchains<00:22:46.679> for<00:22:46.980> a<00:22:47.520> much<00:22:47.760> wider<00:22:48.059> range 00:22:48.230 --> 00:22:48.240 align:start position:0% using blockchains for a much wider range 00:22:48.240 --> 00:22:49.970 align:start position:0% using blockchains for a much wider range of<00:22:48.360> use<00:22:48.480> cases<00:22:48.720> so<00:22:48.960> you<00:22:49.260> know<00:22:49.380> I<00:22:49.440> think<00:22:49.620> one 00:22:49.970 --> 00:22:49.980 align:start position:0% of use cases so you know I think one 00:22:49.980 --> 00:22:51.470 align:start position:0% of use cases so you know I think one completely<00:22:50.340> digital<00:22:50.700> uh<00:22:51.240> completely 00:22:51.470 --> 00:22:51.480 align:start position:0% completely digital uh completely 00:22:51.480 --> 00:22:53.029 align:start position:0% completely digital uh completely reasonable<00:22:51.900> digital<00:22:52.200> interaction<00:22:52.620> we<00:22:52.860> might 00:22:53.029 --> 00:22:53.039 align:start position:0% reasonable digital interaction we might 00:22:53.039 --> 00:22:54.649 align:start position:0% reasonable digital interaction we might expect<00:22:53.400> to<00:22:53.700> see<00:22:53.880> something<00:22:54.120> like<00:22:54.360> in<00:22:54.539> the 00:22:54.649 --> 00:22:54.659 align:start position:0% expect to see something like in the 00:22:54.659 --> 00:22:56.630 align:start position:0% expect to see something like in the future<00:22:54.780> is<00:22:55.080> you<00:22:55.440> know<00:22:55.559> imagine<00:22:55.679> like<00:22:56.159> I<00:22:56.460> walk 00:22:56.630 --> 00:22:56.640 align:start position:0% future is you know imagine like I walk 00:22:56.640 --> 00:22:58.610 align:start position:0% future is you know imagine like I walk into<00:22:56.820> a<00:22:57.059> store<00:22:57.240> and<00:22:57.539> perform<00:22:57.720> a<00:22:58.080> cryptographic 00:22:58.610 --> 00:22:58.620 align:start position:0% into a store and perform a cryptographic 00:22:58.620 --> 00:23:00.830 align:start position:0% into a store and perform a cryptographic handshake<00:22:59.100> with<00:22:59.700> the<00:22:59.940> merchant<00:23:00.299> and<00:23:00.720> perform 00:23:00.830 --> 00:23:00.840 align:start position:0% handshake with the merchant and perform 00:23:00.840 --> 00:23:02.870 align:start position:0% handshake with the merchant and perform like<00:23:01.200> a<00:23:01.320> multi-party<00:23:01.860> computation<00:23:02.280> with<00:23:02.700> some 00:23:02.870 --> 00:23:02.880 align:start position:0% like a multi-party computation with some 00:23:02.880 --> 00:23:04.450 align:start position:0% like a multi-party computation with some identity<00:23:03.360> provider 00:23:04.450 --> 00:23:04.460 align:start position:0% identity provider 00:23:04.460 --> 00:23:07.130 align:start position:0% identity provider after<00:23:05.460> verifying<00:23:06.360> the<00:23:06.480> Merchant's<00:23:06.840> identity 00:23:07.130 --> 00:23:07.140 align:start position:0% after verifying the Merchant's identity 00:23:07.140 --> 00:23:09.529 align:start position:0% after verifying the Merchant's identity I<00:23:07.440> give<00:23:07.620> the<00:23:08.400> merchant<00:23:08.700> one<00:23:09.059> token<00:23:09.419> that 00:23:09.529 --> 00:23:09.539 align:start position:0% I give the merchant one token that 00:23:09.539 --> 00:23:11.210 align:start position:0% I give the merchant one token that permissions<00:23:09.900> them<00:23:10.080> to<00:23:10.380> access<00:23:10.500> some<00:23:10.919> specific 00:23:11.210 --> 00:23:11.220 align:start position:0% permissions them to access some specific 00:23:11.220 --> 00:23:14.270 align:start position:0% permissions them to access some specific data<00:23:11.760> uh<00:23:12.539> on<00:23:13.200> my<00:23:13.320> preferences<00:23:13.740> for<00:23:13.980> an<00:23:14.100> hour 00:23:14.270 --> 00:23:14.280 align:start position:0% data uh on my preferences for an hour 00:23:14.280 --> 00:23:16.430 align:start position:0% data uh on my preferences for an hour and<00:23:15.059> another<00:23:15.360> token<00:23:15.780> that<00:23:15.840> allows<00:23:16.140> them<00:23:16.260> to 00:23:16.430 --> 00:23:16.440 align:start position:0% and another token that allows them to 00:23:16.440 --> 00:23:18.049 align:start position:0% and another token that allows them to transfer<00:23:16.799> a<00:23:17.280> limited<00:23:17.580> amount<00:23:17.760> from<00:23:17.940> my 00:23:18.049 --> 00:23:18.059 align:start position:0% transfer a limited amount from my 00:23:18.059 --> 00:23:20.149 align:start position:0% transfer a limited amount from my balance<00:23:18.419> after<00:23:18.960> that<00:23:19.200> transaction<00:23:19.559> completes 00:23:20.149 --> 00:23:20.159 align:start position:0% balance after that transaction completes 00:23:20.159 --> 00:23:22.010 align:start position:0% balance after that transaction completes I<00:23:20.520> update<00:23:20.820> my<00:23:21.000> transaction<00:23:21.360> history<00:23:21.659> that's 00:23:22.010 --> 00:23:22.020 align:start position:0% I update my transaction history that's 00:23:22.020 --> 00:23:24.890 align:start position:0% I update my transaction history that's private<00:23:22.500> to<00:23:22.679> me<00:23:22.799> and<00:23:23.280> committed<00:23:23.640> on<00:23:23.880> chain<00:23:24.120> uh 00:23:24.890 --> 00:23:24.900 align:start position:0% private to me and committed on chain uh 00:23:24.900 --> 00:23:27.649 align:start position:0% private to me and committed on chain uh but<00:23:25.020> only<00:23:25.320> visible<00:23:25.679> to<00:23:25.919> myself<00:23:26.100> so<00:23:27.000> you<00:23:27.539> know 00:23:27.649 --> 00:23:27.659 align:start position:0% but only visible to myself so you know 00:23:27.659 --> 00:23:29.090 align:start position:0% but only visible to myself so you know each<00:23:28.140> of<00:23:28.260> the<00:23:28.380> components<00:23:28.860> of<00:23:28.919> this 00:23:29.090 --> 00:23:29.100 align:start position:0% each of the components of this 00:23:29.100 --> 00:23:32.350 align:start position:0% each of the components of this interaction<00:23:29.940> today<00:23:30.539> are<00:23:31.200> not<00:23:31.380> possible 00:23:32.350 --> 00:23:32.360 align:start position:0% interaction today are not possible 00:23:32.360 --> 00:23:35.330 align:start position:0% interaction today are not possible due<00:23:33.360> to<00:23:33.539> the<00:23:33.720> fact<00:23:33.900> that<00:23:34.380> there's<00:23:35.039> so<00:23:35.220> many 00:23:35.330 --> 00:23:35.340 align:start position:0% due to the fact that there's so many 00:23:35.340 --> 00:23:37.250 align:start position:0% due to the fact that there's so many things<00:23:35.640> there's<00:23:36.179> so<00:23:36.360> many<00:23:36.480> constraints<00:23:36.900> on 00:23:37.250 --> 00:23:37.260 align:start position:0% things there's so many constraints on 00:23:37.260 --> 00:23:39.950 align:start position:0% things there's so many constraints on what<00:23:37.380> we<00:23:37.559> can<00:23:37.679> keep<00:23:37.860> private<00:23:38.820> but<00:23:39.240> again<00:23:39.419> with 00:23:39.950 --> 00:23:39.960 align:start position:0% what we can keep private but again with 00:23:39.960 --> 00:23:41.870 align:start position:0% what we can keep private but again with things<00:23:40.200> like<00:23:40.440> fully<00:23:40.919> homomorphic<00:23:41.460> encryption 00:23:41.870 --> 00:23:41.880 align:start position:0% things like fully homomorphic encryption 00:23:41.880 --> 00:23:44.330 align:start position:0% things like fully homomorphic encryption witness<00:23:42.419> encryption<00:23:42.900> ZK<00:23:43.200> snarks<00:23:43.860> etc<00:23:44.159> etc 00:23:44.330 --> 00:23:44.340 align:start position:0% witness encryption ZK snarks etc etc 00:23:44.340 --> 00:23:46.850 align:start position:0% witness encryption ZK snarks etc etc these<00:23:45.120> kinds<00:23:45.299> of<00:23:45.360> interactions<00:23:45.900> may<00:23:46.440> start<00:23:46.620> to 00:23:46.850 --> 00:23:46.860 align:start position:0% these kinds of interactions may start to 00:23:46.860 --> 00:23:49.490 align:start position:0% these kinds of interactions may start to be<00:23:47.039> unlocked<00:23:47.640> uh<00:23:48.299> while<00:23:48.840> still<00:23:49.080> preserving 00:23:49.490 --> 00:23:49.500 align:start position:0% be unlocked uh while still preserving 00:23:49.500 --> 00:23:52.190 align:start position:0% be unlocked uh while still preserving the<00:23:49.679> neutrality<00:23:50.100> uh<00:23:50.760> where<00:23:51.120> all<00:23:51.419> this<00:23:51.600> data<00:23:51.960> is 00:23:52.190 --> 00:23:52.200 align:start position:0% the neutrality uh where all this data is 00:23:52.200 --> 00:23:54.409 align:start position:0% the neutrality uh where all this data is living<00:23:52.440> on<00:23:52.860> some<00:23:53.039> like<00:23:53.280> globally<00:23:53.820> verifiable 00:23:54.409 --> 00:23:54.419 align:start position:0% living on some like globally verifiable 00:23:54.419 --> 00:23:56.090 align:start position:0% living on some like globally verifiable blockchain<00:23:54.840> or<00:23:55.020> data<00:23:55.260> availability<00:23:55.620> system 00:23:56.090 --> 00:23:56.100 align:start position:0% blockchain or data availability system 00:23:56.100 --> 00:23:58.010 align:start position:0% blockchain or data availability system so 00:23:58.010 --> 00:23:58.020 align:start position:0% so 00:23:58.020 --> 00:24:00.470 align:start position:0% so um the<00:23:58.679> last<00:23:58.799> kind<00:23:59.100> of<00:23:59.220> like<00:23:59.520> analogy<00:24:00.059> that<00:24:00.299> I 00:24:00.470 --> 00:24:00.480 align:start position:0% um the last kind of like analogy that I 00:24:00.480 --> 00:24:02.510 align:start position:0% um the last kind of like analogy that I want<00:24:00.539> to<00:24:00.720> make<00:24:00.900> here<00:24:01.200> to<00:24:01.919> kind<00:24:01.980> of<00:24:02.100> create<00:24:02.220> an 00:24:02.510 --> 00:24:02.520 align:start position:0% want to make here to kind of create an 00:24:02.520 --> 00:24:04.909 align:start position:0% want to make here to kind of create an image<00:24:02.820> of<00:24:03.360> what<00:24:04.020> this<00:24:04.200> future<00:24:04.380> might<00:24:04.679> look 00:24:04.909 --> 00:24:04.919 align:start position:0% image of what this future might look 00:24:04.919 --> 00:24:07.190 align:start position:0% image of what this future might look like<00:24:05.039> is<00:24:05.340> you<00:24:05.760> know<00:24:05.820> I<00:24:06.059> want<00:24:06.120> to<00:24:06.299> kind<00:24:06.480> of<00:24:06.659> uh 00:24:07.190 --> 00:24:07.200 align:start position:0% like is you know I want to kind of uh 00:24:07.200 --> 00:24:09.230 align:start position:0% like is you know I want to kind of uh describe<00:24:07.620> the<00:24:07.799> concept<00:24:08.159> of<00:24:08.460> an<00:24:08.700> Ender<00:24:09.000> Chest 00:24:09.230 --> 00:24:09.240 align:start position:0% describe the concept of an Ender Chest 00:24:09.240 --> 00:24:12.110 align:start position:0% describe the concept of an Ender Chest from<00:24:09.480> the<00:24:09.600> game<00:24:09.720> Minecraft<00:24:10.020> so<00:24:10.559> Minecraft<00:24:11.220> is 00:24:12.110 --> 00:24:12.120 align:start position:0% from the game Minecraft so Minecraft is 00:24:12.120 --> 00:24:14.690 align:start position:0% from the game Minecraft so Minecraft is a<00:24:12.720> you<00:24:13.140> know<00:24:13.260> Sandbox<00:24:13.740> game<00:24:14.039> in<00:24:14.220> which<00:24:14.400> you<00:24:14.580> can 00:24:14.690 --> 00:24:14.700 align:start position:0% a you know Sandbox game in which you can 00:24:14.700 --> 00:24:17.029 align:start position:0% a you know Sandbox game in which you can Harvest<00:24:15.059> resources<00:24:15.539> and<00:24:15.720> build<00:24:15.900> stuff<00:24:16.200> and<00:24:16.860> in 00:24:17.029 --> 00:24:17.039 align:start position:0% Harvest resources and build stuff and in 00:24:17.039 --> 00:24:18.590 align:start position:0% Harvest resources and build stuff and in Minecraft<00:24:17.159> there's<00:24:17.460> this<00:24:17.700> concept<00:24:17.940> of<00:24:18.120> chests 00:24:18.590 --> 00:24:18.600 align:start position:0% Minecraft there's this concept of chests 00:24:18.600 --> 00:24:20.930 align:start position:0% Minecraft there's this concept of chests so<00:24:19.080> with<00:24:19.320> a<00:24:19.500> wooden<00:24:19.740> chest<00:24:20.039> if<00:24:20.580> I<00:24:20.760> build<00:24:20.820> a 00:24:20.930 --> 00:24:20.940 align:start position:0% so with a wooden chest if I build a 00:24:20.940 --> 00:24:22.250 align:start position:0% so with a wooden chest if I build a wooden<00:24:21.179> chest<00:24:21.360> I<00:24:21.480> can<00:24:21.600> like<00:24:21.720> place<00:24:21.900> it<00:24:22.080> down 00:24:22.250 --> 00:24:22.260 align:start position:0% wooden chest I can like place it down 00:24:22.260 --> 00:24:24.169 align:start position:0% wooden chest I can like place it down here<00:24:22.380> I<00:24:22.559> can<00:24:22.679> put<00:24:22.799> items<00:24:23.159> in<00:24:23.340> into<00:24:23.760> the<00:24:24.000> chest 00:24:24.169 --> 00:24:24.179 align:start position:0% here I can put items in into the chest 00:24:24.179 --> 00:24:25.970 align:start position:0% here I can put items in into the chest if<00:24:24.659> I<00:24:24.840> leave<00:24:24.960> and<00:24:25.140> come<00:24:25.320> back<00:24:25.440> the<00:24:25.620> items<00:24:25.860> are 00:24:25.970 --> 00:24:25.980 align:start position:0% if I leave and come back the items are 00:24:25.980 --> 00:24:27.649 align:start position:0% if I leave and come back the items are still<00:24:26.100> going<00:24:26.220> to<00:24:26.340> be<00:24:26.400> there<00:24:26.580> the<00:24:27.179> chest<00:24:27.360> is<00:24:27.480> a 00:24:27.649 --> 00:24:27.659 align:start position:0% still going to be there the chest is a 00:24:27.659 --> 00:24:29.510 align:start position:0% still going to be there the chest is a very<00:24:27.780> important<00:24:28.140> like<00:24:28.380> primitive<00:24:28.980> in 00:24:29.510 --> 00:24:29.520 align:start position:0% very important like primitive in 00:24:29.520 --> 00:24:31.549 align:start position:0% very important like primitive in Minecraft<00:24:29.880> if<00:24:30.600> anyone<00:24:30.840> else<00:24:31.020> goes<00:24:31.320> to<00:24:31.380> the 00:24:31.549 --> 00:24:31.559 align:start position:0% Minecraft if anyone else goes to the 00:24:31.559 --> 00:24:32.990 align:start position:0% Minecraft if anyone else goes to the chest<00:24:31.740> and<00:24:31.919> they<00:24:32.100> open<00:24:32.220> it<00:24:32.400> they're<00:24:32.760> going<00:24:32.880> to 00:24:32.990 --> 00:24:33.000 align:start position:0% chest and they open it they're going to 00:24:33.000 --> 00:24:34.430 align:start position:0% chest and they open it they're going to be<00:24:33.059> able<00:24:33.120> to<00:24:33.240> see<00:24:33.360> all<00:24:33.539> the<00:24:33.659> items<00:24:33.900> that<00:24:34.200> I've 00:24:34.430 --> 00:24:34.440 align:start position:0% be able to see all the items that I've 00:24:34.440 --> 00:24:36.470 align:start position:0% be able to see all the items that I've placed<00:24:34.980> in<00:24:35.159> there 00:24:36.470 --> 00:24:36.480 align:start position:0% placed in there 00:24:36.480 --> 00:24:38.510 align:start position:0% placed in there um<00:24:36.539> in<00:24:37.200> Minecraft<00:24:37.320> there's<00:24:37.740> also<00:24:38.039> a<00:24:38.280> very 00:24:38.510 --> 00:24:38.520 align:start position:0% um in Minecraft there's also a very 00:24:38.520 --> 00:24:42.110 align:start position:0% um in Minecraft there's also a very powerful<00:24:39.360> uh<00:24:40.260> tool<00:24:40.740> called<00:24:41.159> the<00:24:41.460> Ender<00:24:41.820> Chest 00:24:42.110 --> 00:24:42.120 align:start position:0% powerful uh tool called the Ender Chest 00:24:42.120 --> 00:24:43.909 align:start position:0% powerful uh tool called the Ender Chest which<00:24:42.720> is<00:24:42.900> sort<00:24:43.080> of<00:24:43.140> similar<00:24:43.380> to<00:24:43.440> a<00:24:43.559> chest<00:24:43.740> but 00:24:43.909 --> 00:24:43.919 align:start position:0% which is sort of similar to a chest but 00:24:43.919 --> 00:24:45.169 align:start position:0% which is sort of similar to a chest but has<00:24:44.039> these<00:24:44.220> kind<00:24:44.340> of<00:24:44.400> this<00:24:44.580> kind<00:24:44.760> of<00:24:44.820> magical 00:24:45.169 --> 00:24:45.179 align:start position:0% has these kind of this kind of magical 00:24:45.179 --> 00:24:48.590 align:start position:0% has these kind of this kind of magical property<00:24:45.659> where<00:24:46.440> ender<00:24:47.159> chests<00:24:47.700> inventories 00:24:48.590 --> 00:24:48.600 align:start position:0% property where ender chests inventories 00:24:48.600 --> 00:24:50.930 align:start position:0% property where ender chests inventories are<00:24:49.260> marked<00:24:49.679> as<00:24:49.860> like<00:24:50.159> per<00:24:50.460> player 00:24:50.930 --> 00:24:50.940 align:start position:0% are marked as like per player 00:24:50.940 --> 00:24:53.570 align:start position:0% are marked as like per player inventories<00:24:51.720> and<00:24:52.380> are<00:24:52.620> sort<00:24:52.860> of<00:24:52.980> shared 00:24:53.570 --> 00:24:53.580 align:start position:0% inventories and are sort of shared 00:24:53.580 --> 00:24:55.430 align:start position:0% inventories and are sort of shared across<00:24:54.000> every<00:24:54.240> Ender<00:24:54.659> Chest<00:24:54.840> that<00:24:55.020> exists<00:24:55.320> in 00:24:55.430 --> 00:24:55.440 align:start position:0% across every Ender Chest that exists in 00:24:55.440 --> 00:24:56.930 align:start position:0% across every Ender Chest that exists in the<00:24:55.559> world<00:24:55.679> so<00:24:55.919> if<00:24:56.159> I<00:24:56.280> put<00:24:56.400> an<00:24:56.520> ender<00:24:56.760> chest 00:24:56.930 --> 00:24:56.940 align:start position:0% the world so if I put an ender chest 00:24:56.940 --> 00:24:59.770 align:start position:0% the world so if I put an ender chest down<00:24:57.120> here<00:24:57.419> and<00:24:58.020> put<00:24:58.260> down<00:24:58.620> like<00:24:59.039> you<00:24:59.580> know 00:24:59.770 --> 00:24:59.780 align:start position:0% down here and put down like you know 00:24:59.780 --> 00:25:02.029 align:start position:0% down here and put down like you know five<00:25:00.780> stone<00:25:01.140> or<00:25:01.440> something<00:25:01.559> and<00:25:01.740> then<00:25:01.860> I<00:25:01.980> put 00:25:02.029 --> 00:25:02.039 align:start position:0% five stone or something and then I put 00:25:02.039 --> 00:25:03.409 align:start position:0% five stone or something and then I put an<00:25:02.159> under<00:25:02.280> chest<00:25:02.580> down<00:25:02.700> over<00:25:02.880> there<00:25:03.059> and<00:25:03.240> like 00:25:03.409 --> 00:25:03.419 align:start position:0% an under chest down over there and like 00:25:03.419 --> 00:25:05.210 align:start position:0% an under chest down over there and like I<00:25:03.600> walk<00:25:03.720> over<00:25:03.900> there<00:25:04.140> and<00:25:04.380> open<00:25:04.740> it<00:25:04.919> I'm<00:25:05.100> gonna 00:25:05.210 --> 00:25:05.220 align:start position:0% I walk over there and open it I'm gonna 00:25:05.220 --> 00:25:08.029 align:start position:0% I walk over there and open it I'm gonna see<00:25:05.340> that<00:25:05.520> same<00:25:05.760> five<00:25:06.240> Stone 00:25:08.029 --> 00:25:08.039 align:start position:0% see that same five Stone 00:25:08.039 --> 00:25:09.710 align:start position:0% see that same five Stone um<00:25:08.100> and<00:25:08.340> if<00:25:08.460> someone<00:25:08.640> else<00:25:08.820> walks<00:25:09.179> into<00:25:09.299> the<00:25:09.480> uh 00:25:09.710 --> 00:25:09.720 align:start position:0% um and if someone else walks into the uh 00:25:09.720 --> 00:25:11.029 align:start position:0% um and if someone else walks into the uh walks<00:25:10.080> over<00:25:10.140> to<00:25:10.320> the<00:25:10.380> under<00:25:10.500> chest<00:25:10.799> they're 00:25:11.029 --> 00:25:11.039 align:start position:0% walks over to the under chest they're 00:25:11.039 --> 00:25:12.350 align:start position:0% walks over to the under chest they're not<00:25:11.220> going<00:25:11.340> to<00:25:11.400> see<00:25:11.580> that<00:25:11.760> same<00:25:11.880> inventory 00:25:12.350 --> 00:25:12.360 align:start position:0% not going to see that same inventory 00:25:12.360 --> 00:25:14.149 align:start position:0% not going to see that same inventory that<00:25:12.539> I<00:25:12.720> have<00:25:12.780> they're<00:25:13.020> only<00:25:13.200> going<00:25:13.380> to<00:25:13.440> see 00:25:14.149 --> 00:25:14.159 align:start position:0% that I have they're only going to see 00:25:14.159 --> 00:25:15.289 align:start position:0% that I have they're only going to see um<00:25:14.220> you<00:25:14.400> know<00:25:14.460> what<00:25:14.640> they've<00:25:14.820> put<00:25:14.940> into<00:25:15.120> the 00:25:15.289 --> 00:25:15.299 align:start position:0% um you know what they've put into the 00:25:15.299 --> 00:25:17.090 align:start position:0% um you know what they've put into the under<00:25:15.419> chest<00:25:15.720> the<00:25:16.260> ender<00:25:16.559> chest<00:25:16.740> is<00:25:16.919> an 00:25:17.090 --> 00:25:17.100 align:start position:0% under chest the ender chest is an 00:25:17.100 --> 00:25:19.909 align:start position:0% under chest the ender chest is an incredibly<00:25:17.720> powerful<00:25:18.720> tool<00:25:19.320> for<00:25:19.679> Minecraft 00:25:19.909 --> 00:25:19.919 align:start position:0% incredibly powerful tool for Minecraft 00:25:19.919 --> 00:25:21.950 align:start position:0% incredibly powerful tool for Minecraft players<00:25:20.460> that<00:25:20.580> allows<00:25:20.880> them<00:25:21.000> to<00:25:21.240> execute<00:25:21.780> on 00:25:21.950 --> 00:25:21.960 align:start position:0% players that allows them to execute on 00:25:21.960 --> 00:25:24.230 align:start position:0% players that allows them to execute on these<00:25:22.140> larger<00:25:22.500> scale<00:25:22.860> strategies<00:25:23.760> build 00:25:24.230 --> 00:25:24.240 align:start position:0% these larger scale strategies build 00:25:24.240 --> 00:25:26.269 align:start position:0% these larger scale strategies build these<00:25:24.539> much<00:25:24.659> more<00:25:24.840> complex<00:25:25.200> constructions<00:25:25.980> it 00:25:26.269 --> 00:25:26.279 align:start position:0% these much more complex constructions it 00:25:26.279 --> 00:25:28.310 align:start position:0% these much more complex constructions it just<00:25:26.460> makes<00:25:26.580> it<00:25:26.820> easier<00:25:27.059> for<00:25:27.299> you<00:25:27.480> to<00:25:27.720> do<00:25:27.900> a<00:25:28.200> lot 00:25:28.310 --> 00:25:28.320 align:start position:0% just makes it easier for you to do a lot 00:25:28.320 --> 00:25:29.630 align:start position:0% just makes it easier for you to do a lot of<00:25:28.620> things 00:25:29.630 --> 00:25:29.640 align:start position:0% of things 00:25:29.640 --> 00:25:32.029 align:start position:0% of things and<00:25:30.360> I<00:25:30.659> think<00:25:30.779> as<00:25:30.960> more<00:25:31.140> of<00:25:31.260> our<00:25:31.440> social<00:25:31.679> and 00:25:32.029 --> 00:25:32.039 align:start position:0% and I think as more of our social and 00:25:32.039 --> 00:25:34.370 align:start position:0% and I think as more of our social and economic<00:25:32.520> activities<00:25:33.059> Move<00:25:33.480> online<00:25:33.779> we're 00:25:34.370 --> 00:25:34.380 align:start position:0% economic activities Move online we're 00:25:34.380 --> 00:25:35.930 align:start position:0% economic activities Move online we're going<00:25:34.620> to<00:25:34.740> need<00:25:34.860> Primitives<00:25:35.340> like<00:25:35.640> these 00:25:35.930 --> 00:25:35.940 align:start position:0% going to need Primitives like these 00:25:35.940 --> 00:25:37.789 align:start position:0% going to need Primitives like these these<00:25:36.419> digital<00:25:36.600> ender<00:25:37.020> chests<00:25:37.320> that<00:25:37.440> allow<00:25:37.679> us 00:25:37.789 --> 00:25:37.799 align:start position:0% these digital ender chests that allow us 00:25:37.799 --> 00:25:39.830 align:start position:0% these digital ender chests that allow us to<00:25:37.980> carry<00:25:38.159> things<00:25:38.340> like<00:25:38.520> our<00:25:38.760> reputation<00:25:39.240> our 00:25:39.830 --> 00:25:39.840 align:start position:0% to carry things like our reputation our 00:25:39.840 --> 00:25:41.810 align:start position:0% to carry things like our reputation our financial<00:25:40.020> history<00:25:40.380> our<00:25:41.039> social<00:25:41.220> context 00:25:41.810 --> 00:25:41.820 align:start position:0% financial history our social context 00:25:41.820 --> 00:25:44.390 align:start position:0% financial history our social context across<00:25:42.720> different<00:25:42.960> platforms<00:25:43.620> and<00:25:44.100> in<00:25:44.220> order 00:25:44.390 --> 00:25:44.400 align:start position:0% across different platforms and in order 00:25:44.400 --> 00:25:45.769 align:start position:0% across different platforms and in order to<00:25:44.580> do<00:25:44.640> that<00:25:44.820> we're<00:25:45.000> going<00:25:45.179> to<00:25:45.240> need<00:25:45.360> these<00:25:45.659> new 00:25:45.769 --> 00:25:45.779 align:start position:0% to do that we're going to need these new 00:25:45.779 --> 00:25:48.049 align:start position:0% to do that we're going to need these new privacy<00:25:46.140> preserving<00:25:46.620> mechanisms<00:25:47.220> uh<00:25:47.820> that 00:25:48.049 --> 00:25:48.059 align:start position:0% privacy preserving mechanisms uh that 00:25:48.059 --> 00:25:49.669 align:start position:0% privacy preserving mechanisms uh that fall<00:25:48.179> under<00:25:48.360> this<00:25:48.600> category<00:25:48.960> of<00:25:49.200> programmable 00:25:49.669 --> 00:25:49.679 align:start position:0% fall under this category of programmable 00:25:49.679 --> 00:25:52.010 align:start position:0% fall under this category of programmable cryptography<00:25:50.400> so<00:25:51.179> that's<00:25:51.419> all<00:25:51.600> I've<00:25:51.720> got<00:25:51.900> for 00:25:52.010 --> 00:25:52.020 align:start position:0% cryptography so that's all I've got for 00:25:52.020 --> 00:25:53.870 align:start position:0% cryptography so that's all I've got for today<00:25:52.200> if<00:25:52.860> you're<00:25:53.039> interested<00:25:53.340> in<00:25:53.520> any<00:25:53.640> of<00:25:53.760> the 00:25:53.870 --> 00:25:53.880 align:start position:0% today if you're interested in any of the 00:25:53.880 --> 00:25:55.250 align:start position:0% today if you're interested in any of the work<00:25:54.000> that<00:25:54.299> we're<00:25:54.600> currently<00:25:54.900> working<00:25:55.080> on 00:25:55.250 --> 00:25:55.260 align:start position:0% work that we're currently working on 00:25:55.260 --> 00:25:56.810 align:start position:0% work that we're currently working on around<00:25:55.500> programmable<00:25:56.100> cryptography<00:25:56.700> or 00:25:56.810 --> 00:25:56.820 align:start position:0% around programmable cryptography or 00:25:56.820 --> 00:25:58.330 align:start position:0% around programmable cryptography or anything<00:25:57.000> else<00:25:57.240> you<00:25:57.720> can<00:25:57.779> check<00:25:57.900> us<00:25:58.080> out<00:25:58.200> at 00:25:58.330 --> 00:25:58.340 align:start position:0% anything else you can check us out at 00:25:58.340 --> 00:26:00.470 align:start position:0% anything else you can check us out at xeroxpark.org<00:25:59.340> or<00:25:59.520> you<00:25:59.580> can<00:25:59.700> find<00:25:59.820> us<00:26:00.059> on 00:26:00.470 --> 00:26:00.480 align:start position:0% xeroxpark.org or you can find us on 00:26:00.480 --> 00:26:03.230 align:start position:0% xeroxpark.org or you can find us on Twitter<00:26:00.600> at<00:26:00.960> Xerox<00:26:01.559> Park<00:26:01.860> but<00:26:02.220> thank<00:26:02.580> you 00:26:03.230 --> 00:26:03.240 align:start position:0% Twitter at Xerox Park but thank you 00:26:03.240 --> 00:26:05.330 align:start position:0% Twitter at Xerox Park but thank you and<00:26:03.840> thank<00:26:04.140> you<00:26:04.260> for<00:26:04.380> the<00:26:04.500> talk 00:26:05.330 --> 00:26:05.340 align:start position:0% and thank you for the talk 00:26:05.340 --> 00:26:06.830 align:start position:0% and thank you for the talk um<00:26:05.460> as<00:26:05.940> we<00:26:06.059> went<00:26:06.240> through<00:26:06.360> a<00:26:06.539> lot<00:26:06.600> of<00:26:06.720> the 00:26:06.830 --> 00:26:06.840 align:start position:0% um as we went through a lot of the 00:26:06.840 --> 00:26:09.649 align:start position:0% um as we went through a lot of the slides<00:26:07.200> there<00:26:07.740> were<00:26:07.860> examples<00:26:08.640> of<00:26:08.940> ZK<00:26:09.360> things 00:26:09.649 --> 00:26:09.659 align:start position:0% slides there were examples of ZK things 00:26:09.659 --> 00:26:11.090 align:start position:0% slides there were examples of ZK things where<00:26:09.960> you<00:26:10.080> have<00:26:10.200> a<00:26:10.320> claim<00:26:10.559> and<00:26:10.679> it's<00:26:10.799> true<00:26:10.980> or 00:26:11.090 --> 00:26:11.100 align:start position:0% where you have a claim and it's true or 00:26:11.100 --> 00:26:12.529 align:start position:0% where you have a claim and it's true or false<00:26:11.400> and<00:26:11.520> you<00:26:11.640> prove<00:26:11.940> it 00:26:12.529 --> 00:26:12.539 align:start position:0% false and you prove it 00:26:12.539 --> 00:26:15.049 align:start position:0% false and you prove it but<00:26:12.960> I<00:26:13.140> guess<00:26:13.260> the<00:26:14.100> bigger<00:26:14.340> picture<00:26:14.520> of<00:26:14.880> all 00:26:15.049 --> 00:26:15.059 align:start position:0% but I guess the bigger picture of all 00:26:15.059 --> 00:26:16.730 align:start position:0% but I guess the bigger picture of all programmable<00:26:15.600> cryptography<00:26:16.320> could<00:26:16.559> have 00:26:16.730 --> 00:26:16.740 align:start position:0% programmable cryptography could have 00:26:16.740 --> 00:26:19.010 align:start position:0% programmable cryptography could have other<00:26:16.860> sorts<00:26:17.220> of<00:26:17.279> statements<00:26:17.760> like<00:26:18.059> I<00:26:18.659> summed 00:26:19.010 --> 00:26:19.020 align:start position:0% other sorts of statements like I summed 00:26:19.020 --> 00:26:20.390 align:start position:0% other sorts of statements like I summed all<00:26:19.080> these<00:26:19.320> numbers<00:26:19.440> and<00:26:19.799> this<00:26:19.980> is<00:26:20.100> the<00:26:20.279> true 00:26:20.390 --> 00:26:20.400 align:start position:0% all these numbers and this is the true 00:26:20.400 --> 00:26:22.250 align:start position:0% all these numbers and this is the true sum<00:26:20.700> and<00:26:21.360> so<00:26:21.480> I<00:26:21.600> guess<00:26:21.720> those<00:26:21.960> are<00:26:22.080> other 00:26:22.250 --> 00:26:22.260 align:start position:0% sum and so I guess those are other 00:26:22.260 --> 00:26:23.810 align:start position:0% sum and so I guess those are other flavors<00:26:22.620> and<00:26:22.799> maybe<00:26:22.980> that's<00:26:23.159> homomorphic 00:26:23.810 --> 00:26:23.820 align:start position:0% flavors and maybe that's homomorphic 00:26:23.820 --> 00:26:25.730 align:start position:0% flavors and maybe that's homomorphic encryption<00:26:24.179> I'm<00:26:24.360> not<00:26:24.480> sure<00:26:24.659> how<00:26:25.260> friendly<00:26:25.620> are 00:26:25.730 --> 00:26:25.740 align:start position:0% encryption I'm not sure how friendly are 00:26:25.740 --> 00:26:27.289 align:start position:0% encryption I'm not sure how friendly are those<00:26:25.919> with<00:26:26.100> each<00:26:26.279> other<00:26:26.400> right<00:26:26.640> now<00:26:26.820> like 00:26:27.289 --> 00:26:27.299 align:start position:0% those with each other right now like 00:26:27.299 --> 00:26:29.690 align:start position:0% those with each other right now like proving<00:26:27.960> things<00:26:28.200> and<00:26:28.500> doing<00:26:28.740> math<00:26:29.039> and 00:26:29.690 --> 00:26:29.700 align:start position:0% proving things and doing math and 00:26:29.700 --> 00:26:30.529 align:start position:0% proving things and doing math and getting 00:26:30.529 --> 00:26:30.539 align:start position:0% getting 00:26:30.539 --> 00:26:32.870 align:start position:0% getting continuous<00:26:31.380> results 00:26:32.870 --> 00:26:32.880 align:start position:0% continuous results 00:26:32.880 --> 00:26:35.570 align:start position:0% continuous results yeah<00:26:33.419> this<00:26:33.840> is<00:26:33.960> a<00:26:34.080> great<00:26:34.200> question<00:26:34.380> so 00:26:35.570 --> 00:26:35.580 align:start position:0% yeah this is a great question so 00:26:35.580 --> 00:26:38.090 align:start position:0% yeah this is a great question so um<00:26:35.640> right<00:26:36.600> now<00:26:36.779> you<00:26:37.380> know<00:26:37.440> as<00:26:37.799> you've<00:26:37.980> probably 00:26:38.090 --> 00:26:38.100 align:start position:0% um right now you know as you've probably 00:26:38.100 --> 00:26:41.029 align:start position:0% um right now you know as you've probably noticed<00:26:38.460> like<00:26:38.900> we<00:26:39.900> are<00:26:40.200> specifically<00:26:40.740> very 00:26:41.029 --> 00:26:41.039 align:start position:0% noticed like we are specifically very 00:26:41.039 --> 00:26:42.890 align:start position:0% noticed like we are specifically very focused<00:26:41.400> on<00:26:41.580> zero<00:26:41.940> knowledge<00:26:42.179> cryptography 00:26:42.890 --> 00:26:42.900 align:start position:0% focused on zero knowledge cryptography 00:26:42.900 --> 00:26:46.130 align:start position:0% focused on zero knowledge cryptography which<00:26:43.200> is<00:26:43.380> you<00:26:43.799> know<00:26:44.000> one<00:26:45.000> of<00:26:45.299> one<00:26:45.779> piece<00:26:46.020> of 00:26:46.130 --> 00:26:46.140 align:start position:0% which is you know one of one piece of 00:26:46.140 --> 00:26:48.169 align:start position:0% which is you know one of one piece of this<00:26:46.260> like<00:26:46.440> much<00:26:46.679> broader<00:26:47.039> category<00:26:47.820> but<00:26:48.059> it 00:26:48.169 --> 00:26:48.179 align:start position:0% this like much broader category but it 00:26:48.179 --> 00:26:49.190 align:start position:0% this like much broader category but it seems<00:26:48.419> like<00:26:48.539> disproportionately 00:26:49.190 --> 00:26:49.200 align:start position:0% seems like disproportionately 00:26:49.200 --> 00:26:51.049 align:start position:0% seems like disproportionately represented<00:26:50.279> um<00:26:50.279> so<00:26:50.460> why<00:26:50.580> is<00:26:50.700> that<00:26:50.820> the<00:26:50.940> case 00:26:51.049 --> 00:26:51.059 align:start position:0% represented um so why is that the case 00:26:51.059 --> 00:26:52.909 align:start position:0% represented um so why is that the case well<00:26:51.299> uh<00:26:51.779> one<00:26:51.960> reason<00:26:52.140> is<00:26:52.320> that<00:26:52.500> zero 00:26:52.909 --> 00:26:52.919 align:start position:0% well uh one reason is that zero 00:26:52.919 --> 00:26:54.710 align:start position:0% well uh one reason is that zero knowledge<00:26:53.159> crypto<00:26:53.520> systems<00:26:53.880> are<00:26:54.240> simply<00:26:54.480> much 00:26:54.710 --> 00:26:54.720 align:start position:0% knowledge crypto systems are simply much 00:26:54.720 --> 00:26:56.750 align:start position:0% knowledge crypto systems are simply much more<00:26:54.840> mature<00:26:55.320> today<00:26:55.559> than<00:26:56.220> a<00:26:56.460> lot<00:26:56.520> of<00:26:56.640> these 00:26:56.750 --> 00:26:56.760 align:start position:0% more mature today than a lot of these 00:26:56.760 --> 00:26:58.370 align:start position:0% more mature today than a lot of these other<00:26:56.880> systems<00:26:57.360> where<00:26:57.600> there's<00:26:57.840> there<00:26:58.200> only 00:26:58.370 --> 00:26:58.380 align:start position:0% other systems where there's there only 00:26:58.380 --> 00:27:00.529 align:start position:0% other systems where there's there only exists<00:26:58.740> theoretical<00:26:59.279> constructions<00:27:00.000> or 00:27:00.529 --> 00:27:00.539 align:start position:0% exists theoretical constructions or 00:27:00.539 --> 00:27:02.570 align:start position:0% exists theoretical constructions or academic<00:27:01.080> implementations 00:27:02.570 --> 00:27:02.580 align:start position:0% academic implementations 00:27:02.580 --> 00:27:04.010 align:start position:0% academic implementations um<00:27:02.640> we<00:27:03.120> expect<00:27:03.240> things<00:27:03.539> like<00:27:03.720> witness 00:27:04.010 --> 00:27:04.020 align:start position:0% um we expect things like witness 00:27:04.020 --> 00:27:05.269 align:start position:0% um we expect things like witness encryption<00:27:04.559> for<00:27:04.679> example<00:27:04.860> to<00:27:04.980> be<00:27:05.159> much 00:27:05.269 --> 00:27:05.279 align:start position:0% encryption for example to be much 00:27:05.279 --> 00:27:06.470 align:start position:0% encryption for example to be much further<00:27:05.520> out<00:27:05.640> and<00:27:05.820> we're<00:27:05.940> still<00:27:06.120> even<00:27:06.240> trying 00:27:06.470 --> 00:27:06.480 align:start position:0% further out and we're still even trying 00:27:06.480 --> 00:27:09.649 align:start position:0% further out and we're still even trying to<00:27:06.600> like<00:27:07.279> describe<00:27:08.279> the<00:27:08.760> landscape<00:27:09.179> of<00:27:09.480> what 00:27:09.649 --> 00:27:09.659 align:start position:0% to like describe the landscape of what 00:27:09.659 --> 00:27:11.149 align:start position:0% to like describe the landscape of what is<00:27:09.779> possible<00:27:10.140> to<00:27:10.260> do<00:27:10.380> with<00:27:10.500> multi-party 00:27:11.149 --> 00:27:11.159 align:start position:0% is possible to do with multi-party 00:27:11.159 --> 00:27:12.529 align:start position:0% is possible to do with multi-party computation 00:27:12.529 --> 00:27:12.539 align:start position:0% computation 00:27:12.539 --> 00:27:13.130 align:start position:0% computation um 00:27:13.130 --> 00:27:13.140 align:start position:0% um 00:27:13.140 --> 00:27:15.529 align:start position:0% um so<00:27:13.980> unfortunately<00:27:14.700> none<00:27:15.000> of<00:27:15.179> these<00:27:15.299> systems 00:27:15.529 --> 00:27:15.539 align:start position:0% so unfortunately none of these systems 00:27:15.539 --> 00:27:17.690 align:start position:0% so unfortunately none of these systems are<00:27:15.720> super<00:27:15.840> compatible<00:27:16.320> because<00:27:16.799> a<00:27:17.520> lot<00:27:17.580> of 00:27:17.690 --> 00:27:17.700 align:start position:0% are super compatible because a lot of 00:27:17.700 --> 00:27:19.610 align:start position:0% are super compatible because a lot of them<00:27:17.820> don't<00:27:18.179> yet<00:27:18.419> like<00:27:18.779> exist<00:27:19.200> in<00:27:19.380> a<00:27:19.559> form 00:27:19.610 --> 00:27:19.620 align:start position:0% them don't yet like exist in a form 00:27:19.620 --> 00:27:20.930 align:start position:0% them don't yet like exist in a form where<00:27:19.860> you<00:27:19.980> can<00:27:20.100> meaningfully<00:27:20.580> start<00:27:20.760> playing 00:27:20.930 --> 00:27:20.940 align:start position:0% where you can meaningfully start playing 00:27:20.940 --> 00:27:22.850 align:start position:0% where you can meaningfully start playing around<00:27:21.120> with<00:27:21.360> them<00:27:21.539> but<00:27:22.200> we<00:27:22.320> hope<00:27:22.500> that<00:27:22.679> that 00:27:22.850 --> 00:27:22.860 align:start position:0% around with them but we hope that that 00:27:22.860 --> 00:27:24.710 align:start position:0% around with them but we hope that that is<00:27:23.159> going<00:27:23.340> to<00:27:23.460> be<00:27:23.520> evolving<00:27:24.000> rapidly<00:27:24.360> over<00:27:24.480> the 00:27:24.710 --> 00:27:24.720 align:start position:0% is going to be evolving rapidly over the 00:27:24.720 --> 00:27:27.409 align:start position:0% is going to be evolving rapidly over the next<00:27:24.840> say<00:27:25.080> like<00:27:25.320> you<00:27:25.559> know<00:27:25.620> a<00:27:25.679> couple<00:27:25.799> of<00:27:25.919> years 00:27:27.409 --> 00:27:27.419 align:start position:0% next say like you know a couple of years 00:27:27.419 --> 00:27:29.510 align:start position:0% next say like you know a couple of years hello<00:27:27.840> thank<00:27:28.320> you<00:27:28.440> very<00:27:28.559> much<00:27:28.679> by<00:27:28.980> the<00:27:29.159> your 00:27:29.510 --> 00:27:29.520 align:start position:0% hello thank you very much by the your 00:27:29.520 --> 00:27:31.370 align:start position:0% hello thank you very much by the your talk<00:27:29.820> haven't<00:27:30.299> made<00:27:30.539> any<00:27:30.659> kind<00:27:30.900> of<00:27:31.020> research 00:27:31.370 --> 00:27:31.380 align:start position:0% talk haven't made any kind of research 00:27:31.380 --> 00:27:36.649 align:start position:0% talk haven't made any kind of research around<00:27:31.679> Quantum<00:27:32.580> cryptography<00:27:33.320> ZK<00:27:34.460> yeah<00:27:35.460> so 00:27:36.649 --> 00:27:36.659 align:start position:0% around Quantum cryptography ZK yeah so 00:27:36.659 --> 00:27:39.830 align:start position:0% around Quantum cryptography ZK yeah so um<00:27:36.779> I<00:27:37.260> think<00:27:37.380> Quantum<00:27:37.980> cryptography<00:27:38.820> is<00:27:39.360> a 00:27:39.830 --> 00:27:39.840 align:start position:0% um I think Quantum cryptography is a 00:27:39.840 --> 00:27:41.049 align:start position:0% um I think Quantum cryptography is a slightly<00:27:40.200> like 00:27:41.049 --> 00:27:41.059 align:start position:0% slightly like 00:27:41.059 --> 00:27:45.049 align:start position:0% slightly like orthogonal<00:27:42.059> direction<00:27:42.980> to<00:27:43.980> what<00:27:44.580> a<00:27:44.820> lot<00:27:44.940> of 00:27:45.049 --> 00:27:45.059 align:start position:0% orthogonal direction to what a lot of 00:27:45.059 --> 00:27:46.730 align:start position:0% orthogonal direction to what a lot of these<00:27:45.360> tools 00:27:46.730 --> 00:27:46.740 align:start position:0% these tools 00:27:46.740 --> 00:27:49.370 align:start position:0% these tools um<00:27:46.799> are<00:27:47.460> going<00:27:47.640> to<00:27:47.760> enable<00:27:48.059> uh<00:27:48.900> specifically 00:27:49.370 --> 00:27:49.380 align:start position:0% um are going to enable uh specifically 00:27:49.380 --> 00:27:50.930 align:start position:0% um are going to enable uh specifically for<00:27:49.559> example<00:27:49.799> like<00:27:50.039> one<00:27:50.279> way<00:27:50.460> that<00:27:50.640> we<00:27:50.760> think 00:27:50.930 --> 00:27:50.940 align:start position:0% for example like one way that we think 00:27:50.940 --> 00:27:52.250 align:start position:0% for example like one way that we think about<00:27:51.059> the<00:27:51.299> interaction<00:27:51.659> of<00:27:51.960> quantum 00:27:52.250 --> 00:27:52.260 align:start position:0% about the interaction of quantum 00:27:52.260 --> 00:27:55.250 align:start position:0% about the interaction of quantum cryptography<00:27:52.980> with<00:27:53.700> these<00:27:54.179> tools<00:27:54.539> is 00:27:55.250 --> 00:27:55.260 align:start position:0% cryptography with these tools is 00:27:55.260 --> 00:27:58.310 align:start position:0% cryptography with these tools is considering<00:27:56.039> which<00:27:56.520> of<00:27:56.700> these<00:27:56.940> tools<00:27:57.419> Quantum 00:27:58.310 --> 00:27:58.320 align:start position:0% considering which of these tools Quantum 00:27:58.320 --> 00:28:00.529 align:start position:0% considering which of these tools Quantum or<00:27:58.559> like<00:27:58.740> which<00:27:59.220> you<00:27:59.640> know<00:27:59.760> for<00:27:59.820> example<00:28:00.059> ZK 00:28:00.529 --> 00:28:00.539 align:start position:0% or like which you know for example ZK 00:28:00.539 --> 00:28:04.010 align:start position:0% or like which you know for example ZK algorithms<00:28:01.200> uh<00:28:01.980> or<00:28:02.100> like<00:28:02.279> fhe<00:28:02.700> algorithms<00:28:03.419> we 00:28:04.010 --> 00:28:04.020 align:start position:0% algorithms uh or like fhe algorithms we 00:28:04.020 --> 00:28:05.690 align:start position:0% algorithms uh or like fhe algorithms we have<00:28:04.140> are<00:28:04.500> quantum<00:28:04.860> resistance<00:28:05.340> in<00:28:05.640> other 00:28:05.690 --> 00:28:05.700 align:start position:0% have are quantum resistance in other 00:28:05.700 --> 00:28:07.970 align:start position:0% have are quantum resistance in other words<00:28:05.820> once<00:28:06.120> we<00:28:06.179> have<00:28:06.240> quantum<00:28:06.659> computers<00:28:07.140> uh 00:28:07.970 --> 00:28:07.980 align:start position:0% words once we have quantum computers uh 00:28:07.980 --> 00:28:09.590 align:start position:0% words once we have quantum computers uh which<00:28:08.460> of<00:28:08.580> these<00:28:08.700> algorithms<00:28:09.120> might<00:28:09.299> we<00:28:09.480> be 00:28:09.590 --> 00:28:09.600 align:start position:0% which of these algorithms might we be 00:28:09.600 --> 00:28:11.870 align:start position:0% which of these algorithms might we be able<00:28:09.840> to<00:28:09.960> break<00:28:10.440> now<00:28:11.100> that's<00:28:11.340> kind<00:28:11.520> of<00:28:11.640> a 00:28:11.870 --> 00:28:11.880 align:start position:0% able to break now that's kind of a 00:28:11.880 --> 00:28:15.049 align:start position:0% able to break now that's kind of a different<00:28:12.059> thing<00:28:12.480> however<00:28:12.900> from<00:28:13.440> necessarily 00:28:15.049 --> 00:28:15.059 align:start position:0% different thing however from necessarily 00:28:15.059 --> 00:28:17.510 align:start position:0% different thing however from necessarily um<00:28:15.120> you<00:28:15.659> know<00:28:15.720> the<00:28:16.080> affordances<00:28:16.679> of<00:28:17.220> these 00:28:17.510 --> 00:28:17.520 align:start position:0% um you know the affordances of these 00:28:17.520 --> 00:28:20.570 align:start position:0% um you know the affordances of these tools<00:28:17.880> so<00:28:18.720> for<00:28:18.960> example<00:28:19.200> like 00:28:20.570 --> 00:28:20.580 align:start position:0% tools so for example like 00:28:20.580 --> 00:28:23.149 align:start position:0% tools so for example like um you<00:28:21.120> know<00:28:21.240> it's<00:28:22.020> when<00:28:22.679> I<00:28:22.919> think<00:28:23.039> about 00:28:23.149 --> 00:28:23.159 align:start position:0% um you know it's when I think about 00:28:23.159 --> 00:28:24.769 align:start position:0% um you know it's when I think about programmable<00:28:23.760> cryptography<00:28:24.419> I<00:28:24.539> usually 00:28:24.769 --> 00:28:24.779 align:start position:0% programmable cryptography I usually 00:28:24.779 --> 00:28:26.390 align:start position:0% programmable cryptography I usually think<00:28:24.960> about<00:28:25.020> it<00:28:25.200> from<00:28:25.320> the<00:28:25.500> perspective<00:28:25.860> of 00:28:26.390 --> 00:28:26.400 align:start position:0% think about it from the perspective of 00:28:26.400 --> 00:28:27.830 align:start position:0% think about it from the perspective of like<00:28:26.640> what<00:28:27.059> these 00:28:27.830 --> 00:28:27.840 align:start position:0% like what these 00:28:27.840 --> 00:28:30.049 align:start position:0% like what these things<00:28:28.440> can<00:28:28.679> do<00:28:28.860> for<00:28:29.039> us<00:28:29.220> rather<00:28:29.940> than 00:28:30.049 --> 00:28:30.059 align:start position:0% things can do for us rather than 00:28:30.059 --> 00:28:32.350 align:start position:0% things can do for us rather than necessarily<00:28:30.659> like<00:28:30.900> what's<00:28:31.140> the<00:28:31.440> underlying 00:28:32.350 --> 00:28:32.360 align:start position:0% necessarily like what's the underlying 00:28:32.360 --> 00:28:34.130 align:start position:0% necessarily like what's the underlying algorithms<00:28:33.360> and<00:28:33.659> what<00:28:33.900> are<00:28:34.020> the 00:28:34.130 --> 00:28:34.140 align:start position:0% algorithms and what are the 00:28:34.140 --> 00:28:35.810 align:start position:0% algorithms and what are the computational<00:28:34.500> models<00:28:34.980> in<00:28:35.159> which<00:28:35.279> they<00:28:35.580> might 00:28:35.810 --> 00:28:35.820 align:start position:0% computational models in which they might 00:28:35.820 --> 00:28:37.730 align:start position:0% computational models in which they might you<00:28:36.299> know<00:28:36.360> broken<00:28:36.600> by<00:28:36.840> or<00:28:37.020> enabled<00:28:37.380> by<00:28:37.500> whether 00:28:37.730 --> 00:28:37.740 align:start position:0% you know broken by or enabled by whether 00:28:37.740 --> 00:28:39.950 align:start position:0% you know broken by or enabled by whether that's<00:28:37.919> Quantum<00:28:38.340> or<00:28:38.580> elliptic<00:28:39.000> curves<00:28:39.299> or<00:28:39.659> you 00:28:39.950 --> 00:28:39.960 align:start position:0% that's Quantum or elliptic curves or you 00:28:39.960 --> 00:28:41.450 align:start position:0% that's Quantum or elliptic curves or you know<00:28:40.020> large<00:28:40.200> Prime<00:28:40.440> fields<00:28:40.919> or<00:28:41.100> things<00:28:41.220> like 00:28:41.450 --> 00:28:41.460 align:start position:0% know large Prime fields or things like 00:28:41.460 --> 00:28:44.690 align:start position:0% know large Prime fields or things like that<00:28:41.640> oh<00:28:42.360> thank<00:28:42.840> you<00:28:42.960> for<00:28:43.080> talk<00:28:43.500> can<00:28:44.400> ask<00:28:44.640> you 00:28:44.690 --> 00:28:44.700 align:start position:0% that oh thank you for talk can ask you 00:28:44.700 --> 00:28:46.669 align:start position:0% that oh thank you for talk can ask you if<00:28:44.820> I<00:28:45.000> understand<00:28:45.120> it<00:28:45.480> correctly<00:28:45.900> the<00:28:46.440> state 00:28:46.669 --> 00:28:46.679 align:start position:0% if I understand it correctly the state 00:28:46.679 --> 00:28:49.850 align:start position:0% if I understand it correctly the state currently<00:28:47.279> in<00:28:47.460> Dark<00:28:47.700> Forest<00:28:48.320> uh<00:28:49.320> you<00:28:49.500> keep<00:28:49.679> it 00:28:49.850 --> 00:28:49.860 align:start position:0% currently in Dark Forest uh you keep it 00:28:49.860 --> 00:28:52.190 align:start position:0% currently in Dark Forest uh you keep it locally<00:28:50.220> and<00:28:50.520> you<00:28:51.120> just<00:28:51.240> put<00:28:51.539> the<00:28:51.659> proofs<00:28:52.080> on 00:28:52.190 --> 00:28:52.200 align:start position:0% locally and you just put the proofs on 00:28:52.200 --> 00:28:53.450 align:start position:0% locally and you just put the proofs on chain 00:28:53.450 --> 00:28:53.460 align:start position:0% chain 00:28:53.460 --> 00:28:55.510 align:start position:0% chain um<00:28:53.520> that<00:28:53.940> may<00:28:54.120> not<00:28:54.299> be<00:28:54.419> ideal<00:28:54.720> for<00:28:55.020> the<00:28:55.200> future 00:28:55.510 --> 00:28:55.520 align:start position:0% um that may not be ideal for the future 00:28:55.520 --> 00:28:58.310 align:start position:0% um that may not be ideal for the future if<00:28:56.520> you<00:28:56.580> lose<00:28:56.700> the<00:28:56.880> state<00:28:57.059> you<00:28:57.299> kind<00:28:57.539> of<00:28:57.659> lose 00:28:58.310 --> 00:28:58.320 align:start position:0% if you lose the state you kind of lose 00:28:58.320 --> 00:29:01.370 align:start position:0% if you lose the state you kind of lose the<00:28:58.559> game<00:28:58.740> uh<00:28:59.279> like<00:28:59.720> what<00:29:00.720> are<00:29:00.840> your<00:29:01.020> thoughts 00:29:01.370 --> 00:29:01.380 align:start position:0% the game uh like what are your thoughts 00:29:01.380 --> 00:29:04.750 align:start position:0% the game uh like what are your thoughts on<00:29:01.620> how<00:29:01.919> to<00:29:02.100> keep<00:29:02.580> the<00:29:02.880> state<00:29:03.240> safe 00:29:04.750 --> 00:29:04.760 align:start position:0% on how to keep the state safe 00:29:04.760 --> 00:29:08.029 align:start position:0% on how to keep the state safe in<00:29:05.760> in<00:29:06.000> other<00:29:06.360> ways<00:29:06.779> either<00:29:07.260> using<00:29:07.679> a<00:29:07.799> homo 00:29:08.029 --> 00:29:08.039 align:start position:0% in in other ways either using a homo 00:29:08.039 --> 00:29:10.490 align:start position:0% in in other ways either using a homo marketing<00:29:08.460> prescription<00:29:08.940> or<00:29:09.900> your<00:29:10.260> general 00:29:10.490 --> 00:29:10.500 align:start position:0% marketing prescription or your general 00:29:10.500 --> 00:29:12.350 align:start position:0% marketing prescription or your general thoughts<00:29:10.980> around<00:29:11.100> it<00:29:11.340> yeah<00:29:11.820> this<00:29:12.000> is<00:29:12.120> a<00:29:12.240> great 00:29:12.350 --> 00:29:12.360 align:start position:0% thoughts around it yeah this is a great 00:29:12.360 --> 00:29:14.570 align:start position:0% thoughts around it yeah this is a great question<00:29:12.659> and<00:29:13.080> I<00:29:13.320> think<00:29:13.440> like<00:29:13.799> you<00:29:14.220> know<00:29:14.279> as<00:29:14.400> an 00:29:14.570 --> 00:29:14.580 align:start position:0% question and I think like you know as an 00:29:14.580 --> 00:29:16.430 align:start position:0% question and I think like you know as an extension<00:29:15.059> of<00:29:15.299> the<00:29:15.419> debate<00:29:15.659> that<00:29:15.900> people<00:29:16.020> have 00:29:16.430 --> 00:29:16.440 align:start position:0% extension of the debate that people have 00:29:16.440 --> 00:29:19.430 align:start position:0% extension of the debate that people have around<00:29:16.860> the<00:29:17.159> viability<00:29:17.700> of<00:29:18.360> uh<00:29:19.140> you<00:29:19.380> know 00:29:19.430 --> 00:29:19.440 align:start position:0% around the viability of uh you know 00:29:19.440 --> 00:29:21.169 align:start position:0% around the viability of uh you know everyone<00:29:19.620> custodying<00:29:20.340> their<00:29:20.460> own<00:29:20.580> keys<00:29:20.940> for 00:29:21.169 --> 00:29:21.179 align:start position:0% everyone custodying their own keys for 00:29:21.179 --> 00:29:22.789 align:start position:0% everyone custodying their own keys for example<00:29:21.360> on<00:29:21.539> a<00:29:21.659> blockchain 00:29:22.789 --> 00:29:22.799 align:start position:0% example on a blockchain 00:29:22.799 --> 00:29:26.090 align:start position:0% example on a blockchain um<00:29:22.860> I<00:29:23.520> think<00:29:23.700> that<00:29:24.179> there<00:29:24.539> are<00:29:24.899> uh<00:29:25.679> a<00:29:25.860> couple<00:29:25.919> of 00:29:26.090 --> 00:29:26.100 align:start position:0% um I think that there are uh a couple of 00:29:26.100 --> 00:29:27.289 align:start position:0% um I think that there are uh a couple of things<00:29:26.279> here<00:29:26.460> that<00:29:26.640> might<00:29:26.760> be<00:29:26.880> possible<00:29:27.120> one 00:29:27.289 --> 00:29:27.299 align:start position:0% things here that might be possible one 00:29:27.299 --> 00:29:28.730 align:start position:0% things here that might be possible one is<00:29:27.419> like<00:29:27.539> you<00:29:27.659> mentioned<00:29:27.779> and<00:29:28.320> fully 00:29:28.730 --> 00:29:28.740 align:start position:0% is like you mentioned and fully 00:29:28.740 --> 00:29:30.889 align:start position:0% is like you mentioned and fully homomorphic<00:29:29.220> encryption<00:29:29.640> might<00:29:30.179> allow<00:29:30.480> us<00:29:30.600> to 00:29:30.889 --> 00:29:30.899 align:start position:0% homomorphic encryption might allow us to 00:29:30.899 --> 00:29:34.549 align:start position:0% homomorphic encryption might allow us to store<00:29:31.140> private<00:29:32.039> State<00:29:32.279> on<00:29:33.059> that<00:29:33.960> is<00:29:34.080> encrypted 00:29:34.549 --> 00:29:34.559 align:start position:0% store private State on that is encrypted 00:29:34.559 --> 00:29:38.389 align:start position:0% store private State on that is encrypted on<00:29:35.399> you<00:29:35.700> know<00:29:35.760> cloud<00:29:36.000> services<00:29:36.860> but<00:29:37.860> still<00:29:38.220> be 00:29:38.389 --> 00:29:38.399 align:start position:0% on you know cloud services but still be 00:29:38.399 --> 00:29:40.549 align:start position:0% on you know cloud services but still be able<00:29:38.520> to<00:29:38.580> like<00:29:38.700> retrieve<00:29:39.120> that<00:29:39.360> data<00:29:39.779> and 00:29:40.549 --> 00:29:40.559 align:start position:0% able to like retrieve that data and 00:29:40.559 --> 00:29:42.590 align:start position:0% able to like retrieve that data and perform<00:29:40.860> operations<00:29:41.520> on<00:29:41.880> it<00:29:42.000> just<00:29:42.179> like<00:29:42.299> we 00:29:42.590 --> 00:29:42.600 align:start position:0% perform operations on it just like we 00:29:42.600 --> 00:29:44.870 align:start position:0% perform operations on it just like we would<00:29:42.779> if<00:29:43.380> it<00:29:43.500> was<00:29:43.679> local<00:29:44.039> while<00:29:44.700> still 00:29:44.870 --> 00:29:44.880 align:start position:0% would if it was local while still 00:29:44.880 --> 00:29:46.190 align:start position:0% would if it was local while still preserving<00:29:45.240> the<00:29:45.360> privacy<00:29:45.659> of<00:29:45.840> that<00:29:45.960> data 00:29:46.190 --> 00:29:46.200 align:start position:0% preserving the privacy of that data 00:29:46.200 --> 00:29:47.750 align:start position:0% preserving the privacy of that data that's<00:29:46.559> pretty<00:29:46.740> far<00:29:46.919> out<00:29:47.100> though<00:29:47.340> and<00:29:47.460> in<00:29:47.640> the 00:29:47.750 --> 00:29:47.760 align:start position:0% that's pretty far out though and in the 00:29:47.760 --> 00:29:49.310 align:start position:0% that's pretty far out though and in the meantime<00:29:48.000> I<00:29:48.240> think<00:29:48.360> the<00:29:48.840> most<00:29:48.960> immediate 00:29:49.310 --> 00:29:49.320 align:start position:0% meantime I think the most immediate 00:29:49.320 --> 00:29:50.810 align:start position:0% meantime I think the most immediate thing<00:29:49.440> that<00:29:49.620> we<00:29:49.679> can<00:29:49.799> focus<00:29:49.980> on<00:29:50.159> doing<00:29:50.340> is<00:29:50.640> like 00:29:50.810 --> 00:29:50.820 align:start position:0% thing that we can focus on doing is like 00:29:50.820 --> 00:29:52.669 align:start position:0% thing that we can focus on doing is like building<00:29:51.240> more<00:29:51.600> user-friendly<00:29:52.260> solutions 00:29:52.669 --> 00:29:52.679 align:start position:0% building more user-friendly solutions 00:29:52.679 --> 00:29:54.409 align:start position:0% building more user-friendly solutions that<00:29:52.980> allow<00:29:53.220> you<00:29:53.340> to<00:29:53.520> keep<00:29:53.760> critical<00:29:54.240> or 00:29:54.409 --> 00:29:54.419 align:start position:0% that allow you to keep critical or 00:29:54.419 --> 00:29:56.389 align:start position:0% that allow you to keep critical or sensitive<00:29:54.779> data<00:29:55.080> on<00:29:55.200> your<00:29:55.320> own<00:29:55.440> machine<00:29:55.679> I 00:29:56.389 --> 00:29:56.399 align:start position:0% sensitive data on your own machine I 00:29:56.399 --> 00:29:58.010 align:start position:0% sensitive data on your own machine I mean<00:29:56.520> everybody<00:29:56.700> already<00:29:57.120> does<00:29:57.720> keep 00:29:58.010 --> 00:29:58.020 align:start position:0% mean everybody already does keep 00:29:58.020 --> 00:30:01.250 align:start position:0% mean everybody already does keep critical<00:29:58.440> and<00:29:58.620> sensitive<00:29:58.980> data<00:29:59.419> so<00:30:00.419> it's<00:30:00.960> a 00:30:01.250 --> 00:30:01.260 align:start position:0% critical and sensitive data so it's a 00:30:01.260 --> 00:30:03.110 align:start position:0% critical and sensitive data so it's a question<00:30:01.440> of<00:30:01.679> like<00:30:01.919> as<00:30:02.279> the<00:30:02.520> volume<00:30:02.700> of<00:30:03.000> that 00:30:03.110 --> 00:30:03.120 align:start position:0% question of like as the volume of that 00:30:03.120 --> 00:30:04.850 align:start position:0% question of like as the volume of that data<00:30:03.360> or<00:30:03.419> has<00:30:03.659> the<00:30:03.779> sensitivity<00:30:04.200> of<00:30:04.380> that<00:30:04.500> data 00:30:04.850 --> 00:30:04.860 align:start position:0% data or has the sensitivity of that data 00:30:04.860 --> 00:30:06.769 align:start position:0% data or has the sensitivity of that data grows<00:30:05.279> then<00:30:05.640> how<00:30:05.820> can<00:30:05.940> we<00:30:06.059> make<00:30:06.240> those<00:30:06.360> systems 00:30:06.769 --> 00:30:06.779 align:start position:0% grows then how can we make those systems 00:30:06.779 --> 00:30:08.450 align:start position:0% grows then how can we make those systems even<00:30:07.200> more<00:30:07.380> and<00:30:07.500> more<00:30:07.679> ergonomic<00:30:08.159> and<00:30:08.279> more 00:30:08.450 --> 00:30:08.460 align:start position:0% even more and more ergonomic and more 00:30:08.460 --> 00:30:10.549 align:start position:0% even more and more ergonomic and more and<00:30:08.520> more<00:30:08.760> secure<00:30:09.059> all<00:30:09.899> right<00:30:10.080> thanks<00:30:10.260> for<00:30:10.440> the 00:30:10.549 --> 00:30:10.559 align:start position:0% and more secure all right thanks for the 00:30:10.559 --> 00:30:11.450 align:start position:0% and more secure all right thanks for the talk 00:30:11.450 --> 00:30:11.460 align:start position:0% talk 00:30:11.460 --> 00:30:13.070 align:start position:0% talk um<00:30:11.580> what<00:30:12.059> do<00:30:12.179> you<00:30:12.299> think<00:30:12.419> about<00:30:12.600> the 00:30:13.070 --> 00:30:13.080 align:start position:0% um what do you think about the 00:30:13.080 --> 00:30:15.470 align:start position:0% um what do you think about the fundamental<00:30:13.500> bottleneck<00:30:13.980> of<00:30:14.159> like<00:30:14.480> zkp's 00:30:15.470 --> 00:30:15.480 align:start position:0% fundamental bottleneck of like zkp's 00:30:15.480 --> 00:30:17.690 align:start position:0% fundamental bottleneck of like zkp's being<00:30:16.260> quite<00:30:16.559> slow<00:30:16.799> and<00:30:17.340> you<00:30:17.460> have<00:30:17.580> this 00:30:17.690 --> 00:30:17.700 align:start position:0% being quite slow and you have this 00:30:17.700 --> 00:30:19.190 align:start position:0% being quite slow and you have this trade-off<00:30:18.059> between<00:30:18.240> like<00:30:18.539> proof<00:30:18.840> generation 00:30:19.190 --> 00:30:19.200 align:start position:0% trade-off between like proof generation 00:30:19.200 --> 00:30:21.769 align:start position:0% trade-off between like proof generation and<00:30:19.440> verification<00:30:20.000> do<00:30:21.000> you<00:30:21.179> think<00:30:21.299> we<00:30:21.600> will 00:30:21.769 --> 00:30:21.779 align:start position:0% and verification do you think we will 00:30:21.779 --> 00:30:23.529 align:start position:0% and verification do you think we will have<00:30:22.020> sort<00:30:22.320> of<00:30:22.440> more<00:30:22.559> like 00:30:23.529 --> 00:30:23.539 align:start position:0% have sort of more like 00:30:23.539 --> 00:30:25.789 align:start position:0% have sort of more like external<00:30:24.539> offram<00:30:25.020> Solutions<00:30:25.380> maybe<00:30:25.620> like 00:30:25.789 --> 00:30:25.799 align:start position:0% external offram Solutions maybe like 00:30:25.799 --> 00:30:28.909 align:start position:0% external offram Solutions maybe like layer<00:30:26.159> 2<00:30:26.340> is<00:30:26.520> for<00:30:26.700> full<00:30:27.120> ZK<00:30:27.539> or<00:30:27.840> like<00:30:28.080> do<00:30:28.679> you 00:30:28.909 --> 00:30:28.919 align:start position:0% layer 2 is for full ZK or like do you 00:30:28.919 --> 00:30:32.149 align:start position:0% layer 2 is for full ZK or like do you see<00:30:29.299> the<00:30:30.299> most<00:30:30.419> promising<00:30:31.020> Solutions<00:30:31.679> being 00:30:32.149 --> 00:30:32.159 align:start position:0% see the most promising Solutions being 00:30:32.159 --> 00:30:34.430 align:start position:0% see the most promising Solutions being in<00:30:32.399> like<00:30:32.580> fundamentals<00:30:33.179> ekp<00:30:33.720> research<00:30:34.140> like 00:30:34.430 --> 00:30:34.440 align:start position:0% in like fundamentals ekp research like 00:30:34.440 --> 00:30:36.710 align:start position:0% in like fundamentals ekp research like what<00:30:34.679> do<00:30:34.799> you<00:30:34.919> think<00:30:34.980> of<00:30:35.159> that<00:30:35.399> whole<00:30:35.880> opponent 00:30:36.710 --> 00:30:36.720 align:start position:0% what do you think of that whole opponent 00:30:36.720 --> 00:30:37.789 align:start position:0% what do you think of that whole opponent trade-off 00:30:37.789 --> 00:30:37.799 align:start position:0% trade-off 00:30:37.799 --> 00:30:40.370 align:start position:0% trade-off yeah<00:30:38.039> so<00:30:38.640> personally 00:30:40.370 --> 00:30:40.380 align:start position:0% yeah so personally 00:30:40.380 --> 00:30:42.169 align:start position:0% yeah so personally um<00:30:40.919> I<00:30:41.279> think<00:30:41.399> that<00:30:41.520> there's<00:30:41.640> still<00:30:41.820> a<00:30:42.000> ton<00:30:42.120> of 00:30:42.169 --> 00:30:42.179 align:start position:0% um I think that there's still a ton of 00:30:42.179 --> 00:30:44.690 align:start position:0% um I think that there's still a ton of low-hanging<00:30:42.899> fruit<00:30:43.159> uh<00:30:44.159> in<00:30:44.399> terms<00:30:44.580> of 00:30:44.690 --> 00:30:44.700 align:start position:0% low-hanging fruit uh in terms of 00:30:44.700 --> 00:30:46.250 align:start position:0% low-hanging fruit uh in terms of performance<00:30:45.120> optimization<00:30:45.659> for<00:30:45.960> these 00:30:46.250 --> 00:30:46.260 align:start position:0% performance optimization for these 00:30:46.260 --> 00:30:48.590 align:start position:0% performance optimization for these currently<00:30:46.559> very<00:30:46.740> expensive<00:30:47.100> crypto<00:30:47.460> systems 00:30:48.590 --> 00:30:48.600 align:start position:0% currently very expensive crypto systems 00:30:48.600 --> 00:30:51.649 align:start position:0% currently very expensive crypto systems um<00:30:48.720> for<00:30:49.320> example<00:30:49.559> with<00:30:49.799> ZK<00:30:50.340> by<00:30:51.059> some<00:30:51.179> metrics 00:30:51.649 --> 00:30:51.659 align:start position:0% um for example with ZK by some metrics 00:30:51.659 --> 00:30:53.750 align:start position:0% um for example with ZK by some metrics over<00:30:51.779> the<00:30:51.899> last<00:30:52.020> three<00:30:52.200> years<00:30:52.440> the<00:30:53.220> or<00:30:53.640> like 00:30:53.750 --> 00:30:53.760 align:start position:0% over the last three years the or like 00:30:53.760 --> 00:30:56.330 align:start position:0% over the last three years the or like over<00:30:53.880> the<00:30:54.059> last<00:30:54.179> four<00:30:54.299> years<00:30:54.500> the<00:30:55.500> size<00:30:55.740> of 00:30:56.330 --> 00:30:56.340 align:start position:0% over the last four years the size of 00:30:56.340 --> 00:30:59.210 align:start position:0% over the last four years the size of circuit<00:30:57.059> or<00:30:57.480> like<00:30:57.720> the<00:30:58.200> size<00:30:58.500> of<00:30:58.740> computation 00:30:59.210 --> 00:30:59.220 align:start position:0% circuit or like the size of computation 00:30:59.220 --> 00:31:00.889 align:start position:0% circuit or like the size of computation that<00:30:59.399> you<00:30:59.520> can<00:30:59.640> ZK<00:30:59.940> prove<00:31:00.299> in<00:31:00.419> browser 00:31:00.889 --> 00:31:00.899 align:start position:0% that you can ZK prove in browser 00:31:00.899 --> 00:31:04.010 align:start position:0% that you can ZK prove in browser efficiently<00:31:01.740> uh<00:31:02.460> has<00:31:02.760> you<00:31:03.299> know<00:31:03.360> expanded<00:31:03.899> by 00:31:04.010 --> 00:31:04.020 align:start position:0% efficiently uh has you know expanded by 00:31:04.020 --> 00:31:05.630 align:start position:0% efficiently uh has you know expanded by like<00:31:04.200> three<00:31:04.380> orders<00:31:04.740> of<00:31:04.860> magnitude<00:31:05.279> and<00:31:05.520> we're 00:31:05.630 --> 00:31:05.640 align:start position:0% like three orders of magnitude and we're 00:31:05.640 --> 00:31:07.549 align:start position:0% like three orders of magnitude and we're still<00:31:05.820> seeing<00:31:06.000> like<00:31:06.120> rapid<00:31:06.299> improvements<00:31:07.020> via 00:31:07.549 --> 00:31:07.559 align:start position:0% still seeing like rapid improvements via 00:31:07.559 --> 00:31:10.130 align:start position:0% still seeing like rapid improvements via new<00:31:08.039> protocols<00:31:08.640> new<00:31:09.299> better<00:31:09.600> engineered 00:31:10.130 --> 00:31:10.140 align:start position:0% new protocols new better engineered 00:31:10.140 --> 00:31:12.169 align:start position:0% new protocols new better engineered libraries<00:31:10.559> for<00:31:10.740> proving<00:31:11.159> Stacks<00:31:11.640> more 00:31:12.169 --> 00:31:12.179 align:start position:0% libraries for proving Stacks more 00:31:12.179 --> 00:31:13.669 align:start position:0% libraries for proving Stacks more efficient<00:31:12.480> circuit<00:31:12.840> implementations<00:31:13.320> and 00:31:13.669 --> 00:31:13.679 align:start position:0% efficient circuit implementations and 00:31:13.679 --> 00:31:15.529 align:start position:0% efficient circuit implementations and things<00:31:13.860> like<00:31:14.100> you<00:31:14.520> know<00:31:14.640> ZK<00:31:15.120> friendly 00:31:15.529 --> 00:31:15.539 align:start position:0% things like you know ZK friendly 00:31:15.539 --> 00:31:18.889 align:start position:0% things like you know ZK friendly Hardware<00:31:15.720> are<00:31:16.620> just<00:31:16.799> getting<00:31:16.980> started<00:31:17.460> so<00:31:18.179> I 00:31:18.889 --> 00:31:18.899 align:start position:0% Hardware are just getting started so I 00:31:18.899 --> 00:31:21.230 align:start position:0% Hardware are just getting started so I think<00:31:19.020> that<00:31:19.140> like<00:31:19.320> well<00:31:19.679> eventually<00:31:20.159> uh<00:31:20.940> there 00:31:21.230 --> 00:31:21.240 align:start position:0% think that like well eventually uh there 00:31:21.240 --> 00:31:23.210 align:start position:0% think that like well eventually uh there may<00:31:21.360> be<00:31:21.539> some<00:31:22.200> industry<00:31:22.559> of<00:31:22.679> services<00:31:22.860> that 00:31:23.210 --> 00:31:23.220 align:start position:0% may be some industry of services that 00:31:23.220 --> 00:31:24.889 align:start position:0% may be some industry of services that arises<00:31:23.640> around<00:31:23.880> you<00:31:24.299> know<00:31:24.360> offloading 00:31:24.889 --> 00:31:24.899 align:start position:0% arises around you know offloading 00:31:24.899 --> 00:31:27.649 align:start position:0% arises around you know offloading computation<00:31:25.380> or<00:31:25.559> things<00:31:25.740> like<00:31:25.919> that<00:31:26.539> at<00:31:27.539> the 00:31:27.649 --> 00:31:27.659 align:start position:0% computation or things like that at the 00:31:27.659 --> 00:31:29.750 align:start position:0% computation or things like that at the moment<00:31:27.840> there<00:31:28.200> are<00:31:28.380> still<00:31:28.620> a<00:31:29.279> lot<00:31:29.399> of 00:31:29.750 --> 00:31:29.760 align:start position:0% moment there are still a lot of 00:31:29.760 --> 00:31:32.210 align:start position:0% moment there are still a lot of optimizations<00:31:30.480> that<00:31:31.020> have<00:31:31.500> not<00:31:31.740> yet<00:31:31.919> been 00:31:32.210 --> 00:31:32.220 align:start position:0% optimizations that have not yet been 00:31:32.220 --> 00:31:34.909 align:start position:0% optimizations that have not yet been fully<00:31:32.640> you<00:31:33.480> know<00:31:33.539> explored 00:31:34.909 --> 00:31:34.919 align:start position:0% fully you know explored 00:31:34.919 --> 00:31:36.950 align:start position:0% fully you know explored um<00:31:34.980> that<00:31:35.279> I<00:31:35.399> think<00:31:35.520> can<00:31:35.820> enable 00:31:36.950 --> 00:31:36.960 align:start position:0% um that I think can enable 00:31:36.960 --> 00:31:39.710 align:start position:0% um that I think can enable some<00:31:37.559> really<00:31:37.740> really<00:31:37.860> complex<00:31:38.279> proofs<00:31:38.820> even 00:31:39.710 --> 00:31:39.720 align:start position:0% some really really complex proofs even 00:31:39.720 --> 00:31:41.210 align:start position:0% some really really complex proofs even on<00:31:39.960> like<00:31:40.080> small<00:31:40.260> client<00:31:40.559> devices<00:31:40.799> like<00:31:41.039> mobile 00:31:41.210 --> 00:31:41.220 align:start position:0% on like small client devices like mobile 00:31:41.220 --> 00:31:43.250 align:start position:0% on like small client devices like mobile phones 00:31:43.250 --> 00:31:43.260 align:start position:0% phones 00:31:43.260 --> 00:31:46.310 align:start position:0% phones is<00:31:43.740> there<00:31:43.919> any<00:31:44.039> other<00:31:44.340> questions 00:31:46.310 --> 00:31:46.320 align:start position:0% is there any other questions 00:31:46.320 --> 00:31:49.279 align:start position:0% is there any other questions cool<00:31:46.799> thank<00:31:47.159> you