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:15.550 align:start position:0% [Music] 00:00:15.550 --> 00:00:15.560 align:start position:0% 00:00:15.560 --> 00:00:18.769 align:start position:0% application<00:00:16.560> design<00:00:16.800> patterns<00:00:17.400> but<00:00:17.880> ye<00:00:18.480> and<00:00:18.660> I 00:00:18.769 --> 00:00:18.779 align:start position:0% application design patterns but ye and I 00:00:18.779 --> 00:00:20.630 align:start position:0% application design patterns but ye and I got<00:00:18.960> together<00:00:19.140> and<00:00:19.859> started<00:00:20.160> talking<00:00:20.340> we 00:00:20.630 --> 00:00:20.640 align:start position:0% got together and started talking we 00:00:20.640 --> 00:00:21.650 align:start position:0% got together and started talking we realized 00:00:21.650 --> 00:00:21.660 align:start position:0% realized 00:00:21.660 --> 00:00:23.210 align:start position:0% realized a<00:00:21.960> lot<00:00:22.140> of<00:00:22.260> what<00:00:22.380> we<00:00:22.500> really<00:00:22.680> wanted<00:00:22.920> to<00:00:23.100> talk 00:00:23.210 --> 00:00:23.220 align:start position:0% a lot of what we really wanted to talk 00:00:23.220 --> 00:00:25.790 align:start position:0% a lot of what we really wanted to talk about<00:00:23.400> was<00:00:23.939> like<00:00:24.660> what<00:00:25.019> is<00:00:25.140> the<00:00:25.320> landscape<00:00:25.680> of 00:00:25.790 --> 00:00:25.800 align:start position:0% about was like what is the landscape of 00:00:25.800 --> 00:00:30.050 align:start position:0% about was like what is the landscape of ZK<00:00:26.100> applications<00:00:26.580> uh<00:00:27.480> ZK<00:00:27.900> or<00:00:28.260> zkp<00:00:28.800> or<00:00:28.980> snark<00:00:29.400> is 00:00:30.050 --> 00:00:30.060 align:start position:0% ZK applications uh ZK or zkp or snark is 00:00:30.060 --> 00:00:32.690 align:start position:0% ZK applications uh ZK or zkp or snark is quickly<00:00:30.420> becoming<00:00:30.779> like<00:00:31.140> a<00:00:31.800> big<00:00:31.980> data-esque 00:00:32.690 --> 00:00:32.700 align:start position:0% quickly becoming like a big data-esque 00:00:32.700 --> 00:00:35.450 align:start position:0% quickly becoming like a big data-esque buzzword<00:00:33.660> and<00:00:34.020> very<00:00:34.260> jargony<00:00:34.739> it's<00:00:35.340> starting 00:00:35.450 --> 00:00:35.460 align:start position:0% buzzword and very jargony it's starting 00:00:35.460 --> 00:00:37.910 align:start position:0% buzzword and very jargony it's starting to<00:00:35.640> mean<00:00:35.760> a<00:00:35.940> lot<00:00:36.059> of<00:00:36.180> different<00:00:36.300> things 00:00:37.910 --> 00:00:37.920 align:start position:0% to mean a lot of different things 00:00:37.920 --> 00:00:39.350 align:start position:0% to mean a lot of different things um and<00:00:38.219> so<00:00:38.340> we<00:00:38.460> hoping<00:00:38.700> to<00:00:38.820> talk<00:00:38.940> to<00:00:39.120> sort<00:00:39.239> of 00:00:39.350 --> 00:00:39.360 align:start position:0% um and so we hoping to talk to sort of 00:00:39.360 --> 00:00:41.209 align:start position:0% um and so we hoping to talk to sort of like<00:00:39.540> talk<00:00:40.260> through<00:00:40.500> some<00:00:40.739> of<00:00:40.860> the<00:00:41.040> different 00:00:41.209 --> 00:00:41.219 align:start position:0% like talk through some of the different 00:00:41.219 --> 00:00:42.830 align:start position:0% like talk through some of the different application<00:00:42.059> classes<00:00:42.540> we're<00:00:42.660> seeing 00:00:42.830 --> 00:00:42.840 align:start position:0% application classes we're seeing 00:00:42.840 --> 00:00:44.510 align:start position:0% application classes we're seeing emerging<00:00:43.320> emerging<00:00:43.739> today 00:00:44.510 --> 00:00:44.520 align:start position:0% emerging emerging today 00:00:44.520 --> 00:00:47.090 align:start position:0% emerging emerging today and<00:00:45.420> in<00:00:45.840> in<00:00:45.899> in<00:00:46.020> the<00:00:46.440> process<00:00:46.620> sort<00:00:46.860> of<00:00:46.980> like 00:00:47.090 --> 00:00:47.100 align:start position:0% and in in in the process sort of like 00:00:47.100 --> 00:00:49.369 align:start position:0% and in in in the process sort of like plot<00:00:47.579> what<00:00:47.940> we<00:00:48.059> think<00:00:48.239> the<00:00:48.420> next<00:00:48.600> six<00:00:49.020> months 00:00:49.369 --> 00:00:49.379 align:start position:0% plot what we think the next six months 00:00:49.379 --> 00:00:51.590 align:start position:0% plot what we think the next six months to<00:00:49.500> one<00:00:49.680> year<00:00:49.920> of<00:00:50.340> like<00:00:50.579> new<00:00:50.760> ideas<00:00:51.000> coming<00:00:51.420> out 00:00:51.590 --> 00:00:51.600 align:start position:0% to one year of like new ideas coming out 00:00:51.600 --> 00:00:53.090 align:start position:0% to one year of like new ideas coming out look<00:00:51.840> like 00:00:53.090 --> 00:00:53.100 align:start position:0% look like 00:00:53.100 --> 00:00:55.670 align:start position:0% look like um<00:00:53.280> and<00:00:53.640> if<00:00:54.059> the<00:00:54.300> course<00:00:54.360> data<00:00:54.840> core<00:00:55.379> thesis 00:00:55.670 --> 00:00:55.680 align:start position:0% um and if the course data core thesis 00:00:55.680 --> 00:00:57.049 align:start position:0% um and if the course data core thesis were<00:00:55.860> stated<00:00:56.100> in<00:00:56.219> a<00:00:56.340> single<00:00:56.520> statement<00:00:56.820> it's 00:00:57.049 --> 00:00:57.059 align:start position:0% were stated in a single statement it's 00:00:57.059 --> 00:00:58.310 align:start position:0% were stated in a single statement it's basically 00:00:58.310 --> 00:00:58.320 align:start position:0% basically 00:00:58.320 --> 00:00:59.930 align:start position:0% basically um<00:00:58.379> maybe<00:00:58.680> unsurprisingly<00:00:59.399> to<00:00:59.579> many<00:00:59.699> people 00:00:59.930 --> 00:00:59.940 align:start position:0% um maybe unsurprisingly to many people 00:00:59.940 --> 00:01:01.369 align:start position:0% um maybe unsurprisingly to many people who<00:01:00.059> work<00:01:00.180> and<00:01:00.360> say<00:01:00.480> hey<00:01:00.660> that's<00:01:00.840> succinctness 00:01:01.369 --> 00:01:01.379 align:start position:0% who work and say hey that's succinctness 00:01:01.379 --> 00:01:03.650 align:start position:0% who work and say hey that's succinctness and<00:01:01.559> privacy<00:01:01.920> are<00:01:02.160> are<00:01:02.520> kind<00:01:02.760> of<00:01:02.879> like<00:01:03.059> the<00:01:03.359> two 00:01:03.650 --> 00:01:03.660 align:start position:0% and privacy are are kind of like the two 00:01:03.660 --> 00:01:06.050 align:start position:0% and privacy are are kind of like the two sort<00:01:04.440> of<00:01:04.559> features<00:01:05.220> of<00:01:05.400> ZK<00:01:05.700> that<00:01:05.939> are 00:01:06.050 --> 00:01:06.060 align:start position:0% sort of features of ZK that are 00:01:06.060 --> 00:01:07.910 align:start position:0% sort of features of ZK that are interesting<00:01:06.420> and<00:01:07.140> understanding<00:01:07.680> what 00:01:07.910 --> 00:01:07.920 align:start position:0% interesting and understanding what 00:01:07.920 --> 00:01:10.010 align:start position:0% interesting and understanding what succinct<00:01:08.400> private<00:01:08.820> succinct<00:01:09.420> apps<00:01:09.780> require 00:01:10.010 --> 00:01:10.020 align:start position:0% succinct private succinct apps require 00:01:10.020 --> 00:01:11.510 align:start position:0% succinct private succinct apps require and<00:01:10.260> what<00:01:10.439> private<00:01:10.740> apps<00:01:10.979> require<00:01:11.100> like 00:01:11.510 --> 00:01:11.520 align:start position:0% and what private apps require like 00:01:11.520 --> 00:01:13.130 align:start position:0% and what private apps require like independent<00:01:12.000> of<00:01:12.119> one<00:01:12.240> another<00:01:12.360> might<00:01:12.780> help<00:01:12.960> us 00:01:13.130 --> 00:01:13.140 align:start position:0% independent of one another might help us 00:01:13.140 --> 00:01:14.210 align:start position:0% independent of one another might help us understand<00:01:13.380> how<00:01:13.740> like<00:01:13.920> these<00:01:14.100> two 00:01:14.210 --> 00:01:14.220 align:start position:0% understand how like these two 00:01:14.220 --> 00:01:15.770 align:start position:0% understand how like these two applications<00:01:14.640> exist 00:01:15.770 --> 00:01:15.780 align:start position:0% applications exist 00:01:15.780 --> 00:01:18.170 align:start position:0% applications exist so<00:01:16.200> as<00:01:16.320> Alexa<00:01:16.500> mentioned<00:01:17.040> we<00:01:17.340> really<00:01:17.460> think<00:01:17.760> of 00:01:18.170 --> 00:01:18.180 align:start position:0% so as Alexa mentioned we really think of 00:01:18.180 --> 00:01:22.310 align:start position:0% so as Alexa mentioned we really think of ZK<00:01:18.840> as<00:01:19.680> this<00:01:19.979> Matrix<00:01:20.400> where<00:01:21.299> your<00:01:21.659> proof<00:01:22.020> can 00:01:22.310 --> 00:01:22.320 align:start position:0% ZK as this Matrix where your proof can 00:01:22.320 --> 00:01:25.190 align:start position:0% ZK as this Matrix where your proof can be<00:01:22.500> either<00:01:22.680> succinct<00:01:23.580> or<00:01:23.939> not<00:01:24.060> succinct<00:01:24.659> and 00:01:25.190 --> 00:01:25.200 align:start position:0% be either succinct or not succinct and 00:01:25.200 --> 00:01:27.050 align:start position:0% be either succinct or not succinct and your<00:01:25.320> proof<00:01:25.619> can<00:01:25.740> either<00:01:25.860> be<00:01:26.100> private<00:01:26.640> or<00:01:26.880> not 00:01:27.050 --> 00:01:27.060 align:start position:0% your proof can either be private or not 00:01:27.060 --> 00:01:28.070 align:start position:0% your proof can either be private or not private 00:01:28.070 --> 00:01:28.080 align:start position:0% private 00:01:28.080 --> 00:01:31.190 align:start position:0% private so<00:01:28.799> we<00:01:29.280> think<00:01:29.460> that<00:01:29.759> each<00:01:30.119> of<00:01:30.299> these<00:01:30.600> quadrants 00:01:31.190 --> 00:01:31.200 align:start position:0% so we think that each of these quadrants 00:01:31.200 --> 00:01:32.749 align:start position:0% so we think that each of these quadrants is<00:01:31.560> useful<00:01:31.860> in<00:01:32.220> a<00:01:32.340> different<00:01:32.460> type<00:01:32.700> of 00:01:32.749 --> 00:01:32.759 align:start position:0% is useful in a different type of 00:01:32.759 --> 00:01:33.830 align:start position:0% is useful in a different type of application 00:01:33.830 --> 00:01:33.840 align:start position:0% application 00:01:33.840 --> 00:01:36.590 align:start position:0% application so<00:01:34.259> in<00:01:34.380> the<00:01:34.619> top<00:01:34.740> left<00:01:34.920> if<00:01:35.759> you<00:01:35.939> have<00:01:36.060> a<00:01:36.299> private 00:01:36.590 --> 00:01:36.600 align:start position:0% so in the top left if you have a private 00:01:36.600 --> 00:01:38.810 align:start position:0% so in the top left if you have a private proof<00:01:36.900> that's<00:01:37.560> not<00:01:37.799> succinct<00:01:38.340> well<00:01:38.700> it's 00:01:38.810 --> 00:01:38.820 align:start position:0% proof that's not succinct well it's 00:01:38.820 --> 00:01:40.490 align:start position:0% proof that's not succinct well it's going<00:01:38.939> to<00:01:39.000> be<00:01:39.119> hard<00:01:39.240> to<00:01:39.479> verify<00:01:39.840> it<00:01:39.960> on<00:01:40.259> chain 00:01:40.490 --> 00:01:40.500 align:start position:0% going to be hard to verify it on chain 00:01:40.500 --> 00:01:42.289 align:start position:0% going to be hard to verify it on chain but<00:01:41.100> you<00:01:41.280> can<00:01:41.400> still<00:01:41.579> use<00:01:41.820> it<00:01:42.000> in<00:01:42.180> some 00:01:42.289 --> 00:01:42.299 align:start position:0% but you can still use it in some 00:01:42.299 --> 00:01:44.870 align:start position:0% but you can still use it in some off-chain<00:01:42.780> applications<00:01:43.520> in<00:01:44.520> the<00:01:44.640> bottom 00:01:44.870 --> 00:01:44.880 align:start position:0% off-chain applications in the bottom 00:01:44.880 --> 00:01:47.090 align:start position:0% off-chain applications in the bottom left<00:01:45.000> if<00:01:45.780> you<00:01:45.960> have<00:01:46.079> a<00:01:46.200> succinct<00:01:46.619> proof<00:01:46.920> that's 00:01:47.090 --> 00:01:47.100 align:start position:0% left if you have a succinct proof that's 00:01:47.100 --> 00:01:49.370 align:start position:0% left if you have a succinct proof that's not<00:01:47.340> private<00:01:47.759> well<00:01:48.299> that's<00:01:48.479> perfect<00:01:48.780> for 00:01:49.370 --> 00:01:49.380 align:start position:0% not private well that's perfect for 00:01:49.380 --> 00:01:51.830 align:start position:0% not private well that's perfect for on-chain<00:01:50.100> infrastructure<00:01:50.700> applications<00:01:51.119> but 00:01:51.830 --> 00:01:51.840 align:start position:0% on-chain infrastructure applications but 00:01:51.840 --> 00:01:52.969 align:start position:0% on-chain infrastructure applications but not<00:01:52.020> so<00:01:52.200> good<00:01:52.320> if<00:01:52.500> you're<00:01:52.619> trying<00:01:52.799> to<00:01:52.860> hide 00:01:52.969 --> 00:01:52.979 align:start position:0% not so good if you're trying to hide 00:01:52.979 --> 00:01:54.170 align:start position:0% not so good if you're trying to hide information 00:01:54.170 --> 00:01:54.180 align:start position:0% information 00:01:54.180 --> 00:01:55.969 align:start position:0% information and<00:01:54.659> of<00:01:54.840> course<00:01:54.960> you<00:01:55.320> can<00:01:55.439> have<00:01:55.560> the<00:01:55.740> best<00:01:55.860> of 00:01:55.969 --> 00:01:55.979 align:start position:0% and of course you can have the best of 00:01:55.979 --> 00:01:57.830 align:start position:0% and of course you can have the best of both<00:01:56.159> worlds<00:01:56.520> in<00:01:56.700> the<00:01:56.820> top<00:01:56.939> right<00:01:57.119> where<00:01:57.720> you 00:01:57.830 --> 00:01:57.840 align:start position:0% both worlds in the top right where you 00:01:57.840 --> 00:02:00.289 align:start position:0% both worlds in the top right where you have<00:01:57.960> both<00:01:58.140> succinctness<00:01:58.920> and<00:01:59.220> privacy<00:01:59.700> but 00:02:00.289 --> 00:02:00.299 align:start position:0% have both succinctness and privacy but 00:02:00.299 --> 00:02:01.850 align:start position:0% have both succinctness and privacy but as<00:02:00.479> we'll<00:02:00.600> talk<00:02:00.720> about<00:02:00.899> a<00:02:01.079> bit<00:02:01.200> later<00:02:01.439> in<00:02:01.680> the 00:02:01.850 --> 00:02:01.860 align:start position:0% as we'll talk about a bit later in the 00:02:01.860 --> 00:02:03.770 align:start position:0% as we'll talk about a bit later in the talk<00:02:01.979> that's<00:02:02.520> extremely<00:02:03.000> challenging<00:02:03.420> to<00:02:03.659> do 00:02:03.770 --> 00:02:03.780 align:start position:0% talk that's extremely challenging to do 00:02:03.780 --> 00:02:05.990 align:start position:0% talk that's extremely challenging to do so<00:02:04.560> we<00:02:04.680> think<00:02:04.860> that<00:02:05.100> almost<00:02:05.340> all<00:02:05.579> applications 00:02:05.990 --> 00:02:06.000 align:start position:0% so we think that almost all applications 00:02:06.000 --> 00:02:09.830 align:start position:0% so we think that almost all applications right<00:02:06.600> now<00:02:06.920> fit<00:02:07.920> into<00:02:08.160> one<00:02:09.000> of<00:02:09.119> the<00:02:09.239> left<00:02:09.479> two 00:02:09.830 --> 00:02:09.840 align:start position:0% right now fit into one of the left two 00:02:09.840 --> 00:02:11.089 align:start position:0% right now fit into one of the left two quadrants 00:02:11.089 --> 00:02:11.099 align:start position:0% quadrants 00:02:11.099 --> 00:02:13.430 align:start position:0% quadrants so<00:02:11.520> just<00:02:11.700> to<00:02:11.879> talk<00:02:12.000> through<00:02:12.180> some<00:02:12.480> of<00:02:12.599> them<00:02:12.720> on 00:02:13.430 --> 00:02:13.440 align:start position:0% so just to talk through some of them on 00:02:13.440 --> 00:02:15.369 align:start position:0% so just to talk through some of them on the<00:02:13.620> on<00:02:14.099> the<00:02:14.280> top<00:02:14.400> left 00:02:15.369 --> 00:02:15.379 align:start position:0% the on the top left 00:02:15.379 --> 00:02:19.490 align:start position:0% the on the top left we<00:02:16.379> have<00:02:16.760> uh<00:02:17.760> more<00:02:18.000> social<00:02:18.239> type<00:02:18.720> explorations 00:02:19.490 --> 00:02:19.500 align:start position:0% we have uh more social type explorations 00:02:19.500 --> 00:02:21.530 align:start position:0% we have uh more social type explorations of<00:02:20.160> what<00:02:20.340> you<00:02:20.459> can<00:02:20.580> do<00:02:20.700> when<00:02:21.000> you<00:02:21.120> can<00:02:21.239> hide 00:02:21.530 --> 00:02:21.540 align:start position:0% of what you can do when you can hide 00:02:21.540 --> 00:02:23.930 align:start position:0% of what you can do when you can hide information<00:02:21.860> about<00:02:22.860> what<00:02:23.160> groups<00:02:23.520> you<00:02:23.640> belong 00:02:23.930 --> 00:02:23.940 align:start position:0% information about what groups you belong 00:02:23.940 --> 00:02:25.970 align:start position:0% information about what groups you belong to<00:02:24.060> and<00:02:24.840> what<00:02:25.020> statements<00:02:25.500> you<00:02:25.560> want<00:02:25.739> to<00:02:25.860> make 00:02:25.970 --> 00:02:25.980 align:start position:0% to and what statements you want to make 00:02:25.980 --> 00:02:29.089 align:start position:0% to and what statements you want to make with<00:02:26.520> partial<00:02:26.940> revelation<00:02:27.480> of<00:02:27.900> information 00:02:29.089 --> 00:02:29.099 align:start position:0% with partial revelation of information 00:02:29.099 --> 00:02:31.430 align:start position:0% with partial revelation of information on<00:02:29.640> the<00:02:29.819> top<00:02:29.940> left<00:02:30.180> there<00:02:30.780> are<00:02:30.959> in<00:02:31.140> the<00:02:31.260> bottom 00:02:31.430 --> 00:02:31.440 align:start position:0% on the top left there are in the bottom 00:02:31.440 --> 00:02:32.750 align:start position:0% on the top left there are in the bottom left<00:02:31.560> there<00:02:32.040> are<00:02:32.099> a<00:02:32.160> lot<00:02:32.280> of<00:02:32.340> projects 00:02:32.750 --> 00:02:32.760 align:start position:0% left there are a lot of projects 00:02:32.760 --> 00:02:34.729 align:start position:0% left there are a lot of projects surrounding<00:02:33.300> making<00:02:33.480> blockchains<00:02:34.260> more 00:02:34.729 --> 00:02:34.739 align:start position:0% surrounding making blockchains more 00:02:34.739 --> 00:02:36.290 align:start position:0% surrounding making blockchains more scalable<00:02:35.160> or<00:02:35.640> giving<00:02:35.819> additional 00:02:36.290 --> 00:02:36.300 align:start position:0% scalable or giving additional 00:02:36.300 --> 00:02:37.970 align:start position:0% scalable or giving additional capabilities<00:02:36.780> to<00:02:37.379> decentralized 00:02:37.970 --> 00:02:37.980 align:start position:0% capabilities to decentralized 00:02:37.980 --> 00:02:40.130 align:start position:0% capabilities to decentralized applications<00:02:38.400> using<00:02:39.360> the<00:02:39.599> succinctness 00:02:40.130 --> 00:02:40.140 align:start position:0% applications using the succinctness 00:02:40.140 --> 00:02:41.690 align:start position:0% applications using the succinctness property<00:02:40.500> but<00:02:40.980> where<00:02:41.099> everything's<00:02:41.519> public 00:02:41.690 --> 00:02:41.700 align:start position:0% property but where everything's public 00:02:41.700 --> 00:02:43.309 align:start position:0% property but where everything's public already<00:02:42.000> so<00:02:42.480> we<00:02:42.599> don't<00:02:42.720> care<00:02:42.840> too<00:02:43.019> much<00:02:43.200> about 00:02:43.309 --> 00:02:43.319 align:start position:0% already so we don't care too much about 00:02:43.319 --> 00:02:44.509 align:start position:0% already so we don't care too much about privacy 00:02:44.509 --> 00:02:44.519 align:start position:0% privacy 00:02:44.519 --> 00:02:47.809 align:start position:0% privacy and<00:02:44.940> finally<00:02:45.180> in<00:02:45.540> the<00:02:45.660> top<00:02:45.780> right<00:02:46.019> there<00:02:46.980> are<00:02:47.160> a 00:02:47.809 --> 00:02:47.819 align:start position:0% and finally in the top right there are a 00:02:47.819 --> 00:02:49.670 align:start position:0% and finally in the top right there are a very<00:02:47.940> small<00:02:48.180> number<00:02:48.360> of<00:02:48.540> applications<00:02:48.959> that 00:02:49.670 --> 00:02:49.680 align:start position:0% very small number of applications that 00:02:49.680 --> 00:02:51.290 align:start position:0% very small number of applications that have<00:02:49.800> managed<00:02:50.160> to<00:02:50.400> both<00:02:50.700> achieve 00:02:51.290 --> 00:02:51.300 align:start position:0% have managed to both achieve 00:02:51.300 --> 00:02:54.710 align:start position:0% have managed to both achieve succinctness<00:02:51.900> and<00:02:52.379> privacy<00:02:52.879> and<00:02:53.879> you're 00:02:54.710 --> 00:02:54.720 align:start position:0% succinctness and privacy and you're 00:02:54.720 --> 00:02:56.330 align:start position:0% succinctness and privacy and you're probably<00:02:54.959> probably<00:02:55.440> everyone<00:02:55.739> is<00:02:56.040> familiar 00:02:56.330 --> 00:02:56.340 align:start position:0% probably probably everyone is familiar 00:02:56.340 --> 00:02:58.670 align:start position:0% probably probably everyone is familiar with<00:02:56.640> those<00:02:56.819> shown<00:02:57.239> okay<00:02:57.900> so<00:02:58.200> we're<00:02:58.379> now<00:02:58.560> going 00:02:58.670 --> 00:02:58.680 align:start position:0% with those shown okay so we're now going 00:02:58.680 --> 00:03:00.170 align:start position:0% with those shown okay so we're now going to<00:02:58.800> give<00:02:58.860> an<00:02:58.980> overview<00:02:59.280> of<00:02:59.640> where<00:02:59.879> we<00:03:00.000> are 00:03:00.170 --> 00:03:00.180 align:start position:0% to give an overview of where we are 00:03:00.180 --> 00:03:01.850 align:start position:0% to give an overview of where we are today<00:03:00.420> on<00:03:01.019> each<00:03:01.200> of<00:03:01.319> these<00:03:01.560> factors 00:03:01.850 --> 00:03:01.860 align:start position:0% today on each of these factors 00:03:01.860 --> 00:03:04.430 align:start position:0% today on each of these factors succinctness<00:03:02.819> and<00:03:03.060> privacy<00:03:03.540> so<00:03:04.140> in<00:03:04.319> the 00:03:04.430 --> 00:03:04.440 align:start position:0% succinctness and privacy so in the 00:03:04.440 --> 00:03:06.710 align:start position:0% succinctness and privacy so in the bottom<00:03:04.680> left<00:03:04.860> corner<00:03:05.280> if<00:03:05.879> we<00:03:06.060> ask<00:03:06.360> for<00:03:06.540> a 00:03:06.710 --> 00:03:06.720 align:start position:0% bottom left corner if we ask for a 00:03:06.720 --> 00:03:09.229 align:start position:0% bottom left corner if we ask for a succinctness<00:03:07.260> but<00:03:07.680> not<00:03:07.860> privacy<00:03:08.340> the<00:03:09.120> general 00:03:09.229 --> 00:03:09.239 align:start position:0% succinctness but not privacy the general 00:03:09.239 --> 00:03:12.350 align:start position:0% succinctness but not privacy the general theme<00:03:09.599> is<00:03:10.200> that<00:03:10.379> zkps<00:03:11.099> are<00:03:11.580> used<00:03:11.760> to<00:03:12.000> scale 00:03:12.350 --> 00:03:12.360 align:start position:0% theme is that zkps are used to scale 00:03:12.360 --> 00:03:14.930 align:start position:0% theme is that zkps are used to scale trustless<00:03:13.019> off-chain<00:03:13.680> compute<00:03:14.280> and<00:03:14.700> the 00:03:14.930 --> 00:03:14.940 align:start position:0% trustless off-chain compute and the 00:03:14.940 --> 00:03:17.089 align:start position:0% trustless off-chain compute and the theoretical<00:03:15.480> principle<00:03:15.840> behind<00:03:16.260> this<00:03:16.440> is 00:03:17.089 --> 00:03:17.099 align:start position:0% theoretical principle behind this is 00:03:17.099 --> 00:03:19.030 align:start position:0% theoretical principle behind this is that<00:03:17.220> if<00:03:17.400> you<00:03:17.519> run<00:03:17.760> code<00:03:18.060> on<00:03:18.360> ethereum<00:03:18.840> today 00:03:19.030 --> 00:03:19.040 align:start position:0% that if you run code on ethereum today 00:03:19.040 --> 00:03:22.610 align:start position:0% that if you run code on ethereum today every<00:03:20.040> ethereum<00:03:20.519> full<00:03:20.700> node<00:03:21.060> has<00:03:21.959> to<00:03:22.140> rerun 00:03:22.610 --> 00:03:22.620 align:start position:0% every ethereum full node has to rerun 00:03:22.620 --> 00:03:24.890 align:start position:0% every ethereum full node has to rerun that<00:03:22.800> code<00:03:22.980> to<00:03:23.640> validate<00:03:24.060> that<00:03:24.360> the<00:03:24.480> execution 00:03:24.890 --> 00:03:24.900 align:start position:0% that code to validate that the execution 00:03:24.900 --> 00:03:27.770 align:start position:0% that code to validate that the execution of<00:03:25.319> your<00:03:25.440> transaction<00:03:25.920> was<00:03:26.519> correct<00:03:27.360> so 00:03:27.770 --> 00:03:27.780 align:start position:0% of your transaction was correct so 00:03:27.780 --> 00:03:31.910 align:start position:0% of your transaction was correct so that's<00:03:27.959> about<00:03:28.280> 100K<00:03:29.280> at<00:03:29.819> times<00:03:30.319> overhead<00:03:31.319> and 00:03:31.910 --> 00:03:31.920 align:start position:0% that's about 100K at times overhead and 00:03:31.920 --> 00:03:33.949 align:start position:0% that's about 100K at times overhead and it<00:03:32.099> has<00:03:32.220> very<00:03:32.459> high<00:03:32.640> duplication 00:03:33.949 --> 00:03:33.959 align:start position:0% it has very high duplication 00:03:33.959 --> 00:03:36.890 align:start position:0% it has very high duplication the<00:03:34.379> new<00:03:34.640> capability<00:03:35.640> that<00:03:36.060> succinct<00:03:36.599> proofs 00:03:36.890 --> 00:03:36.900 align:start position:0% the new capability that succinct proofs 00:03:36.900 --> 00:03:39.949 align:start position:0% the new capability that succinct proofs give<00:03:37.080> us<00:03:37.260> is<00:03:38.040> that<00:03:38.340> only<00:03:38.640> one<00:03:39.060> party<00:03:39.300> needs<00:03:39.840> to 00:03:39.949 --> 00:03:39.959 align:start position:0% give us is that only one party needs to 00:03:39.959 --> 00:03:42.890 align:start position:0% give us is that only one party needs to execute<00:03:40.440> the<00:03:40.860> transaction<00:03:41.340> and<00:03:42.180> generate<00:03:42.599> a 00:03:42.890 --> 00:03:42.900 align:start position:0% execute the transaction and generate a 00:03:42.900 --> 00:03:44.990 align:start position:0% execute the transaction and generate a validity<00:03:43.319> proof<00:03:43.620> of<00:03:43.739> that<00:03:43.860> transaction 00:03:44.990 --> 00:03:45.000 align:start position:0% validity proof of that transaction 00:03:45.000 --> 00:03:47.030 align:start position:0% validity proof of that transaction everyone<00:03:45.360> else<00:03:45.720> simply<00:03:46.200> needs<00:03:46.440> to<00:03:46.560> validate 00:03:47.030 --> 00:03:47.040 align:start position:0% everyone else simply needs to validate 00:03:47.040 --> 00:03:48.170 align:start position:0% everyone else simply needs to validate that<00:03:47.280> proof 00:03:48.170 --> 00:03:48.180 align:start position:0% that proof 00:03:48.180 --> 00:03:50.750 align:start position:0% that proof so<00:03:48.480> this<00:03:48.659> removes<00:03:49.140> the<00:03:49.319> duplication<00:03:49.799> but<00:03:50.459> just 00:03:50.750 --> 00:03:50.760 align:start position:0% so this removes the duplication but just 00:03:50.760 --> 00:03:53.390 align:start position:0% so this removes the duplication but just incurs<00:03:51.360> a<00:03:51.900> very<00:03:52.019> high<00:03:52.260> overhead<00:03:52.739> on<00:03:53.280> the 00:03:53.390 --> 00:03:53.400 align:start position:0% incurs a very high overhead on the 00:03:53.400 --> 00:03:55.490 align:start position:0% incurs a very high overhead on the prover<00:03:53.640> and<00:03:54.420> so<00:03:54.659> examples<00:03:55.260> about 00:03:55.490 --> 00:03:55.500 align:start position:0% prover and so examples about 00:03:55.500 --> 00:03:57.530 align:start position:0% prover and so examples about applications<00:03:56.099> that<00:03:56.580> use<00:03:56.760> this<00:03:57.000> pattern<00:03:57.299> today 00:03:57.530 --> 00:03:57.540 align:start position:0% applications that use this pattern today 00:03:57.540 --> 00:04:00.229 align:start position:0% applications that use this pattern today are<00:03:58.260> all<00:03:58.440> of<00:03:58.560> the<00:03:58.620> ZK<00:03:58.920> Roll-Ups<00:03:59.519> as<00:03:59.940> well<00:04:00.120> as 00:04:00.229 --> 00:04:00.239 align:start position:0% are all of the ZK Roll-Ups as well as 00:04:00.239 --> 00:04:02.330 align:start position:0% are all of the ZK Roll-Ups as well as the<00:04:00.540> sort<00:04:00.720> of<00:04:00.840> app<00:04:01.140> specific<00:04:01.560> Roll-Ups<00:04:02.099> like 00:04:02.330 --> 00:04:02.340 align:start position:0% the sort of app specific Roll-Ups like 00:04:02.340 --> 00:04:05.570 align:start position:0% the sort of app specific Roll-Ups like dydx<00:04:03.060> or<00:04:03.299> Loop<00:04:03.599> ring<00:04:04.379> so<00:04:04.860> another<00:04:05.040> capability 00:04:05.570 --> 00:04:05.580 align:start position:0% dydx or Loop ring so another capability 00:04:05.580 --> 00:04:08.570 align:start position:0% dydx or Loop ring so another capability that<00:04:06.060> we<00:04:06.299> see<00:04:06.540> ZK<00:04:07.200> uh<00:04:07.860> succinct<00:04:08.280> proof 00:04:08.570 --> 00:04:08.580 align:start position:0% that we see ZK uh succinct proof 00:04:08.580 --> 00:04:10.190 align:start position:0% that we see ZK uh succinct proof springing<00:04:09.000> is<00:04:09.480> cryptographic 00:04:10.190 --> 00:04:10.200 align:start position:0% springing is cryptographic 00:04:10.200 --> 00:04:12.710 align:start position:0% springing is cryptographic interoperability<00:04:11.099> so<00:04:11.819> one<00:04:12.060> thing<00:04:12.180> that<00:04:12.360> ZK 00:04:12.710 --> 00:04:12.720 align:start position:0% interoperability so one thing that ZK 00:04:12.720 --> 00:04:15.110 align:start position:0% interoperability so one thing that ZK allows<00:04:13.080> you<00:04:13.140> to<00:04:13.319> do<00:04:13.500> is<00:04:14.099> to<00:04:14.280> take<00:04:14.519> anything 00:04:15.110 --> 00:04:15.120 align:start position:0% allows you to do is to take anything 00:04:15.120 --> 00:04:16.930 align:start position:0% allows you to do is to take anything from<00:04:15.599> the<00:04:15.720> grab<00:04:16.019> bag<00:04:16.199> of<00:04:16.560> crypto 00:04:16.930 --> 00:04:16.940 align:start position:0% from the grab bag of crypto 00:04:16.940 --> 00:04:19.909 align:start position:0% from the grab bag of crypto cryptographic<00:04:17.940> Primitives<00:04:18.359> on<00:04:18.840> the<00:04:18.959> left<00:04:19.079> and 00:04:19.909 --> 00:04:19.919 align:start position:0% cryptographic Primitives on the left and 00:04:19.919 --> 00:04:22.310 align:start position:0% cryptographic Primitives on the left and allow<00:04:20.160> you<00:04:20.280> to<00:04:20.519> wrap<00:04:20.820> it<00:04:20.940> in<00:04:21.299> a<00:04:21.479> uniform<00:04:21.780> format 00:04:22.310 --> 00:04:22.320 align:start position:0% allow you to wrap it in a uniform format 00:04:22.320 --> 00:04:25.070 align:start position:0% allow you to wrap it in a uniform format namely<00:04:23.160> a<00:04:23.400> ZK<00:04:23.699> snark 00:04:25.070 --> 00:04:25.080 align:start position:0% namely a ZK snark 00:04:25.080 --> 00:04:26.930 align:start position:0% namely a ZK snark so<00:04:25.440> while<00:04:25.680> each<00:04:25.919> of<00:04:26.040> these<00:04:26.160> Primitives<00:04:26.639> is 00:04:26.930 --> 00:04:26.940 align:start position:0% so while each of these Primitives is 00:04:26.940 --> 00:04:28.810 align:start position:0% so while each of these Primitives is useful<00:04:27.240> for<00:04:27.479> a<00:04:27.600> different<00:04:27.720> thing 00:04:28.810 --> 00:04:28.820 align:start position:0% useful for a different thing 00:04:28.820 --> 00:04:31.430 align:start position:0% useful for a different thing they<00:04:29.820> are<00:04:29.940> designed<00:04:30.360> in<00:04:30.600> a<00:04:30.780> somewhat<00:04:31.080> single 00:04:31.430 --> 00:04:31.440 align:start position:0% they are designed in a somewhat single 00:04:31.440 --> 00:04:33.650 align:start position:0% they are designed in a somewhat single purpose<00:04:31.800> way<00:04:32.040> and<00:04:32.820> that<00:04:32.940> makes<00:04:33.180> it<00:04:33.419> very 00:04:33.650 --> 00:04:33.660 align:start position:0% purpose way and that makes it very 00:04:33.660 --> 00:04:36.230 align:start position:0% purpose way and that makes it very difficult<00:04:33.960> to<00:04:34.500> aggregate<00:04:35.040> or<00:04:35.400> compose<00:04:35.820> these 00:04:36.230 --> 00:04:36.240 align:start position:0% difficult to aggregate or compose these 00:04:36.240 --> 00:04:37.129 align:start position:0% difficult to aggregate or compose these things 00:04:37.129 --> 00:04:37.139 align:start position:0% things 00:04:37.139 --> 00:04:39.770 align:start position:0% things so<00:04:37.560> ZK<00:04:37.979> provides<00:04:38.460> an<00:04:38.639> interoperability<00:04:39.300> layer 00:04:39.770 --> 00:04:39.780 align:start position:0% so ZK provides an interoperability layer 00:04:39.780 --> 00:04:41.990 align:start position:0% so ZK provides an interoperability layer that<00:04:40.320> turns<00:04:40.680> all<00:04:40.800> of<00:04:40.919> these<00:04:41.100> into<00:04:41.580> a<00:04:41.759> snark 00:04:41.990 --> 00:04:42.000 align:start position:0% that turns all of these into a snark 00:04:42.000 --> 00:04:44.210 align:start position:0% that turns all of these into a snark proof<00:04:42.479> that<00:04:42.900> is<00:04:43.080> arbitrarily<00:04:43.680> composable 00:04:44.210 --> 00:04:44.220 align:start position:0% proof that is arbitrarily composable 00:04:44.220 --> 00:04:46.550 align:start position:0% proof that is arbitrarily composable using<00:04:44.880> recursion<00:04:45.479> and<00:04:45.900> while<00:04:46.080> that<00:04:46.259> snark 00:04:46.550 --> 00:04:46.560 align:start position:0% using recursion and while that snark 00:04:46.560 --> 00:04:49.189 align:start position:0% using recursion and while that snark proof<00:04:46.919> adds<00:04:47.280> some<00:04:47.400> overhead<00:04:47.820> it<00:04:48.600> makes<00:04:48.780> this 00:04:49.189 --> 00:04:49.199 align:start position:0% proof adds some overhead it makes this 00:04:49.199 --> 00:04:52.129 align:start position:0% proof adds some overhead it makes this open<00:04:49.680> interoperability<00:04:50.580> possible<00:04:51.360> okay<00:04:51.840> so 00:04:52.129 --> 00:04:52.139 align:start position:0% open interoperability possible okay so 00:04:52.139 --> 00:04:54.110 align:start position:0% open interoperability possible okay so let's<00:04:52.320> talk<00:04:52.620> about<00:04:52.740> now<00:04:53.100> what's<00:04:53.639> necessary 00:04:54.110 --> 00:04:54.120 align:start position:0% let's talk about now what's necessary 00:04:54.120 --> 00:04:56.330 align:start position:0% let's talk about now what's necessary today<00:04:54.419> to<00:04:54.960> make<00:04:55.139> this<00:04:55.320> happen<00:04:55.560> the<00:04:56.160> first 00:04:56.330 --> 00:04:56.340 align:start position:0% today to make this happen the first 00:04:56.340 --> 00:04:58.610 align:start position:0% today to make this happen the first thing<00:04:56.520> is<00:04:57.060> that<00:04:57.240> because<00:04:57.479> we're<00:04:58.020> only<00:04:58.199> asking 00:04:58.610 --> 00:04:58.620 align:start position:0% thing is that because we're only asking 00:04:58.620 --> 00:05:00.950 align:start position:0% thing is that because we're only asking for<00:04:58.860> a<00:04:59.040> succinct<00:04:59.400> proof<00:04:59.759> we<00:05:00.240> can<00:05:00.360> really<00:05:00.600> scale 00:05:00.950 --> 00:05:00.960 align:start position:0% for a succinct proof we can really scale 00:05:00.960 --> 00:05:04.010 align:start position:0% for a succinct proof we can really scale the<00:05:01.199> prover<00:05:02.040> in<00:05:02.520> particular<00:05:02.880> we<00:05:03.540> can<00:05:03.720> first 00:05:04.010 --> 00:05:04.020 align:start position:0% the prover in particular we can first 00:05:04.020 --> 00:05:06.530 align:start position:0% the prover in particular we can first not<00:05:04.560> prove<00:05:04.860> in<00:05:04.979> the<00:05:05.100> browser<00:05:05.400> we<00:05:05.639> can<00:05:05.759> prove<00:05:06.180> on 00:05:06.530 --> 00:05:06.540 align:start position:0% not prove in the browser we can prove on 00:05:06.540 --> 00:05:09.050 align:start position:0% not prove in the browser we can prove on the<00:05:06.720> user's<00:05:07.080> bare<00:05:07.380> metal<00:05:07.500> CPU<00:05:08.100> so<00:05:08.699> that<00:05:08.880> gives 00:05:09.050 --> 00:05:09.060 align:start position:0% the user's bare metal CPU so that gives 00:05:09.060 --> 00:05:11.870 align:start position:0% the user's bare metal CPU so that gives us<00:05:09.240> a<00:05:09.540> really<00:05:09.660> high<00:05:10.199> 5<00:05:10.800> to<00:05:10.979> 10x<00:05:11.340> Improvement 00:05:11.870 --> 00:05:11.880 align:start position:0% us a really high 5 to 10x Improvement 00:05:11.880 --> 00:05:14.570 align:start position:0% us a really high 5 to 10x Improvement secondly<00:05:12.780> we<00:05:13.080> can<00:05:13.259> Outsource<00:05:13.680> the<00:05:13.860> prover<00:05:14.160> to 00:05:14.570 --> 00:05:14.580 align:start position:0% secondly we can Outsource the prover to 00:05:14.580 --> 00:05:16.610 align:start position:0% secondly we can Outsource the prover to the<00:05:14.699> cloud<00:05:14.880> so<00:05:15.600> we<00:05:15.780> can<00:05:15.900> send<00:05:16.080> the<00:05:16.320> user<00:05:16.560> can 00:05:16.610 --> 00:05:16.620 align:start position:0% the cloud so we can send the user can 00:05:16.620 --> 00:05:19.010 align:start position:0% the cloud so we can send the user can send<00:05:16.800> a<00:05:16.979> request<00:05:17.280> for<00:05:18.000> a<00:05:18.180> snark<00:05:18.419> proof<00:05:18.840> of 00:05:19.010 --> 00:05:19.020 align:start position:0% send a request for a snark proof of 00:05:19.020 --> 00:05:20.270 align:start position:0% send a request for a snark proof of something<00:05:19.199> that's<00:05:19.500> already<00:05:19.740> going<00:05:20.040> to<00:05:20.160> be 00:05:20.270 --> 00:05:20.280 align:start position:0% something that's already going to be 00:05:20.280 --> 00:05:21.170 align:start position:0% something that's already going to be public 00:05:21.170 --> 00:05:21.180 align:start position:0% public 00:05:21.180 --> 00:05:23.890 align:start position:0% public and<00:05:21.660> then<00:05:21.720> the<00:05:21.900> cloud-based<00:05:22.500> server<00:05:22.740> can<00:05:23.580> run 00:05:23.890 --> 00:05:23.900 align:start position:0% and then the cloud-based server can run 00:05:23.900 --> 00:05:27.950 align:start position:0% and then the cloud-based server can run a<00:05:24.900> big<00:05:25.080> large<00:05:25.860> AWS<00:05:26.520> instance<00:05:27.060> it<00:05:27.479> can<00:05:27.600> run<00:05:27.780> a 00:05:27.950 --> 00:05:27.960 align:start position:0% a big large AWS instance it can run a 00:05:27.960 --> 00:05:30.710 align:start position:0% a big large AWS instance it can run a GPU<00:05:28.380> it<00:05:28.740> can<00:05:28.860> run<00:05:28.979> an<00:05:29.100> fpga<00:05:29.520> or<00:05:30.180> eventually<00:05:30.539> an 00:05:30.710 --> 00:05:30.720 align:start position:0% GPU it can run an fpga or eventually an 00:05:30.720 --> 00:05:33.110 align:start position:0% GPU it can run an fpga or eventually an Asic<00:05:31.139> and<00:05:31.740> that<00:05:31.860> can<00:05:31.979> give<00:05:32.100> another<00:05:32.340> 5<00:05:32.580> to<00:05:32.759> 10x 00:05:33.110 --> 00:05:33.120 align:start position:0% Asic and that can give another 5 to 10x 00:05:33.120 --> 00:05:35.570 align:start position:0% Asic and that can give another 5 to 10x speed<00:05:33.300> up<00:05:33.539> in<00:05:34.199> the<00:05:34.320> proving<00:05:34.680> time 00:05:35.570 --> 00:05:35.580 align:start position:0% speed up in the proving time 00:05:35.580 --> 00:05:37.550 align:start position:0% speed up in the proving time and<00:05:36.060> finally<00:05:36.360> I<00:05:36.600> wanted<00:05:36.720> to<00:05:36.900> talk<00:05:37.020> about<00:05:37.199> the 00:05:37.550 --> 00:05:37.560 align:start position:0% and finally I wanted to talk about the 00:05:37.560 --> 00:05:39.110 align:start position:0% and finally I wanted to talk about the last<00:05:37.740> constraint<00:05:38.220> when<00:05:38.759> you<00:05:38.940> use 00:05:39.110 --> 00:05:39.120 align:start position:0% last constraint when you use 00:05:39.120 --> 00:05:41.810 align:start position:0% last constraint when you use succinctness<00:05:39.960> on<00:05:40.320> chain<00:05:40.560> and<00:05:41.400> this<00:05:41.580> is<00:05:41.639> a 00:05:41.810 --> 00:05:41.820 align:start position:0% succinctness on chain and this is a 00:05:41.820 --> 00:05:43.610 align:start position:0% succinctness on chain and this is a pretty<00:05:41.940> heavy<00:05:42.240> one<00:05:42.419> which<00:05:43.020> is<00:05:43.139> that<00:05:43.320> you<00:05:43.440> have 00:05:43.610 --> 00:05:43.620 align:start position:0% pretty heavy one which is that you have 00:05:43.620 --> 00:05:45.529 align:start position:0% pretty heavy one which is that you have to<00:05:43.740> verify<00:05:44.280> all<00:05:44.759> of<00:05:44.880> your<00:05:45.000> zero<00:05:45.300> knowledge 00:05:45.529 --> 00:05:45.539 align:start position:0% to verify all of your zero knowledge 00:05:45.539 --> 00:05:47.450 align:start position:0% to verify all of your zero knowledge proofs<00:05:45.900> on<00:05:46.500> chain 00:05:47.450 --> 00:05:47.460 align:start position:0% proofs on chain 00:05:47.460 --> 00:05:49.490 align:start position:0% proofs on chain and<00:05:48.000> in<00:05:48.120> this<00:05:48.240> case<00:05:48.419> the<00:05:48.900> gas<00:05:49.020> cost<00:05:49.259> of 00:05:49.490 --> 00:05:49.500 align:start position:0% and in this case the gas cost of 00:05:49.500 --> 00:05:52.490 align:start position:0% and in this case the gas cost of verification<00:05:49.919> really<00:05:50.699> differs<00:05:51.180> from<00:05:51.840> the<00:05:52.080> CPU 00:05:52.490 --> 00:05:52.500 align:start position:0% verification really differs from the CPU 00:05:52.500 --> 00:05:54.710 align:start position:0% verification really differs from the CPU cost<00:05:52.740> it's<00:05:53.400> going<00:05:53.639> to<00:05:53.759> depend<00:05:54.000> on<00:05:54.300> the<00:05:54.419> proving 00:05:54.710 --> 00:05:54.720 align:start position:0% cost it's going to depend on the proving 00:05:54.720 --> 00:05:57.290 align:start position:0% cost it's going to depend on the proving system<00:05:54.960> you<00:05:55.320> used<00:05:55.440> the<00:05:56.220> choice<00:05:56.400> of<00:05:56.639> curve<00:05:57.120> for 00:05:57.290 --> 00:05:57.300 align:start position:0% system you used the choice of curve for 00:05:57.300 --> 00:05:59.330 align:start position:0% system you used the choice of curve for that<00:05:57.479> proving<00:05:57.780> system<00:05:58.020> and<00:05:58.919> also<00:05:59.160> some 00:05:59.330 --> 00:05:59.340 align:start position:0% that proving system and also some 00:05:59.340 --> 00:06:01.370 align:start position:0% that proving system and also some proving<00:05:59.699> system<00:05:59.940> specific<00:06:00.479> implementation 00:06:01.370 --> 00:06:01.380 align:start position:0% proving system specific implementation 00:06:01.380 --> 00:06:03.950 align:start position:0% proving system specific implementation choices<00:06:01.860> the<00:06:02.639> most<00:06:02.759> restrictive<00:06:03.300> of<00:06:03.479> these<00:06:03.660> is 00:06:03.950 --> 00:06:03.960 align:start position:0% choices the most restrictive of these is 00:06:03.960 --> 00:06:06.230 align:start position:0% choices the most restrictive of these is the<00:06:04.080> choice<00:06:04.259> of<00:06:04.500> curve<00:06:04.860> so<00:06:05.400> on<00:06:05.580> ethereum<00:06:06.000> there 00:06:06.230 --> 00:06:06.240 align:start position:0% the choice of curve so on ethereum there 00:06:06.240 --> 00:06:08.810 align:start position:0% the choice of curve so on ethereum there are<00:06:06.360> pre-compiles<00:06:06.960> for<00:06:07.199> the<00:06:07.320> BN<00:06:07.560> 254<00:06:08.220> elliptic 00:06:08.810 --> 00:06:08.820 align:start position:0% are pre-compiles for the BN 254 elliptic 00:06:08.820 --> 00:06:10.969 align:start position:0% are pre-compiles for the BN 254 elliptic curve<00:06:09.120> and<00:06:09.660> those<00:06:09.900> operations<00:06:10.380> are<00:06:10.800> much 00:06:10.969 --> 00:06:10.979 align:start position:0% curve and those operations are much 00:06:10.979 --> 00:06:14.270 align:start position:0% curve and those operations are much cheaper<00:06:11.880> unfortunately<00:06:12.780> other<00:06:13.620> curves<00:06:14.039> are 00:06:14.270 --> 00:06:14.280 align:start position:0% cheaper unfortunately other curves are 00:06:14.280 --> 00:06:16.370 align:start position:0% cheaper unfortunately other curves are somewhat<00:06:14.580> prohibitive<00:06:15.000> to<00:06:15.300> do<00:06:15.419> directly<00:06:16.199> in 00:06:16.370 --> 00:06:16.380 align:start position:0% somewhat prohibitive to do directly in 00:06:16.380 --> 00:06:18.650 align:start position:0% somewhat prohibitive to do directly in evm<00:06:16.800> hence<00:06:17.460> the<00:06:17.639> need<00:06:17.759> for<00:06:17.940> a<00:06:18.000> pre-compile<00:06:18.479> in 00:06:18.650 --> 00:06:18.660 align:start position:0% evm hence the need for a pre-compile in 00:06:18.660 --> 00:06:21.230 align:start position:0% evm hence the need for a pre-compile in the<00:06:18.840> first<00:06:18.960> place<00:06:19.139> one<00:06:20.100> way<00:06:20.340> that<00:06:20.699> is<00:06:20.940> commonly 00:06:21.230 --> 00:06:21.240 align:start position:0% the first place one way that is commonly 00:06:21.240 --> 00:06:23.390 align:start position:0% the first place one way that is commonly used<00:06:21.479> right<00:06:21.780> now<00:06:21.960> to<00:06:22.319> get<00:06:22.440> around<00:06:22.560> this<00:06:22.860> for 00:06:23.390 --> 00:06:23.400 align:start position:0% used right now to get around this for 00:06:23.400 --> 00:06:26.210 align:start position:0% used right now to get around this for example<00:06:23.580> in<00:06:23.819> the<00:06:23.940> zkevm<00:06:25.020> is<00:06:25.680> the<00:06:25.860> operation 00:06:26.210 --> 00:06:26.220 align:start position:0% example in the zkevm is the operation 00:06:26.220 --> 00:06:28.249 align:start position:0% example in the zkevm is the operation known<00:06:26.520> as<00:06:26.699> aggregation 00:06:28.249 --> 00:06:28.259 align:start position:0% known as aggregation 00:06:28.259 --> 00:06:30.290 align:start position:0% known as aggregation the<00:06:28.620> strategy<00:06:28.979> here<00:06:29.220> is<00:06:29.400> that<00:06:29.580> if<00:06:29.759> you<00:06:29.940> want<00:06:30.120> to 00:06:30.290 --> 00:06:30.300 align:start position:0% the strategy here is that if you want to 00:06:30.300 --> 00:06:33.290 align:start position:0% the strategy here is that if you want to use<00:06:30.539> a<00:06:31.020> snark<00:06:31.259> a<00:06:31.860> very<00:06:31.979> big<00:06:32.160> one<00:06:32.400> that's<00:06:33.060> not 00:06:33.290 --> 00:06:33.300 align:start position:0% use a snark a very big one that's not 00:06:33.300 --> 00:06:36.529 align:start position:0% use a snark a very big one that's not natively<00:06:33.780> compatible<00:06:34.319> for<00:06:34.800> evm<00:06:35.340> verification 00:06:36.529 --> 00:06:36.539 align:start position:0% natively compatible for evm verification 00:06:36.539 --> 00:06:39.230 align:start position:0% natively compatible for evm verification you<00:06:37.080> first<00:06:37.259> generate<00:06:37.620> your<00:06:37.800> snark<00:06:38.100> a 00:06:39.230 --> 00:06:39.240 align:start position:0% you first generate your snark a 00:06:39.240 --> 00:06:42.230 align:start position:0% you first generate your snark a and<00:06:39.720> then<00:06:39.960> you<00:06:40.259> produce<00:06:40.620> a<00:06:40.919> recursive<00:06:41.280> snark<00:06:41.639> B 00:06:42.230 --> 00:06:42.240 align:start position:0% and then you produce a recursive snark B 00:06:42.240 --> 00:06:45.290 align:start position:0% and then you produce a recursive snark B which<00:06:43.139> proves<00:06:43.440> the<00:06:43.620> claim<00:06:43.919> that<00:06:44.340> you<00:06:44.580> know<00:06:44.819> a 00:06:45.290 --> 00:06:45.300 align:start position:0% which proves the claim that you know a 00:06:45.300 --> 00:06:47.870 align:start position:0% which proves the claim that you know a large<00:06:45.419> snark<00:06:45.840> a<00:06:46.139> that<00:06:46.919> proves<00:06:47.340> the<00:06:47.580> statement 00:06:47.870 --> 00:06:47.880 align:start position:0% large snark a that proves the statement 00:06:47.880 --> 00:06:50.450 align:start position:0% large snark a that proves the statement you<00:06:48.060> claimed<00:06:48.840> in<00:06:49.440> this<00:06:49.560> case<00:06:49.680> you<00:06:50.100> can<00:06:50.220> choose 00:06:50.450 --> 00:06:50.460 align:start position:0% you claimed in this case you can choose 00:06:50.460 --> 00:06:52.490 align:start position:0% you claimed in this case you can choose B<00:06:50.819> to<00:06:51.419> come<00:06:51.539> from<00:06:51.780> a<00:06:51.960> different<00:06:52.080> proving 00:06:52.490 --> 00:06:52.500 align:start position:0% B to come from a different proving 00:06:52.500 --> 00:06:55.010 align:start position:0% B to come from a different proving system<00:06:52.740> than<00:06:53.280> your<00:06:53.460> original<00:06:53.639> snark<00:06:54.120> and<00:06:54.840> that 00:06:55.010 --> 00:06:55.020 align:start position:0% system than your original snark and that 00:06:55.020 --> 00:06:56.749 align:start position:0% system than your original snark and that proving<00:06:55.259> system<00:06:55.500> could<00:06:55.919> be<00:06:56.100> very<00:06:56.220> cheap<00:06:56.520> to 00:06:56.749 --> 00:06:56.759 align:start position:0% proving system could be very cheap to 00:06:56.759 --> 00:06:59.210 align:start position:0% proving system could be very cheap to verify<00:06:57.180> on<00:06:57.539> ethereum<00:06:58.020> in<00:06:58.440> this<00:06:58.560> way<00:06:58.740> you<00:06:59.100> can 00:06:59.210 --> 00:06:59.220 align:start position:0% verify on ethereum in this way you can 00:06:59.220 --> 00:07:01.850 align:start position:0% verify on ethereum in this way you can sort<00:06:59.460> of<00:06:59.580> transmute<00:07:00.300> a<00:07:01.080> very<00:07:01.199> large<00:07:01.440> snark 00:07:01.850 --> 00:07:01.860 align:start position:0% sort of transmute a very large snark 00:07:01.860 --> 00:07:04.670 align:start position:0% sort of transmute a very large snark from<00:07:02.100> an<00:07:02.220> arbitrary<00:07:02.580> proving<00:07:02.880> system<00:07:03.199> to<00:07:04.199> an 00:07:04.670 --> 00:07:04.680 align:start position:0% from an arbitrary proving system to an 00:07:04.680 --> 00:07:07.730 align:start position:0% from an arbitrary proving system to an on-chain<00:07:05.100> verifiable<00:07:05.759> snark<00:07:06.539> from<00:07:07.319> something 00:07:07.730 --> 00:07:07.740 align:start position:0% on-chain verifiable snark from something 00:07:07.740 --> 00:07:10.010 align:start position:0% on-chain verifiable snark from something that's<00:07:07.979> compatible<00:07:08.460> with<00:07:08.699> ethereum 00:07:10.010 --> 00:07:10.020 align:start position:0% that's compatible with ethereum 00:07:10.020 --> 00:07:12.170 align:start position:0% that's compatible with ethereum the<00:07:10.440> only<00:07:10.500> caveat<00:07:10.979> here<00:07:11.280> is<00:07:11.639> that<00:07:11.759> you<00:07:11.940> of 00:07:12.170 --> 00:07:12.180 align:start position:0% the only caveat here is that you of 00:07:12.180 --> 00:07:14.629 align:start position:0% the only caveat here is that you of course<00:07:12.300> incur<00:07:12.900> the<00:07:13.259> overhead<00:07:13.560> over<00:07:14.160> this 00:07:14.629 --> 00:07:14.639 align:start position:0% course incur the overhead over this 00:07:14.639 --> 00:07:17.570 align:start position:0% course incur the overhead over this recursive<00:07:15.060> proof<00:07:15.840> cool<00:07:16.440> thank<00:07:16.800> you 00:07:17.570 --> 00:07:17.580 align:start position:0% recursive proof cool thank you 00:07:17.580 --> 00:07:20.150 align:start position:0% recursive proof cool thank you um<00:07:17.699> yeah<00:07:18.419> now<00:07:18.660> I'll<00:07:18.840> talk<00:07:19.259> about<00:07:19.380> the<00:07:19.919> the 00:07:20.150 --> 00:07:20.160 align:start position:0% um yeah now I'll talk about the the 00:07:20.160 --> 00:07:21.890 align:start position:0% um yeah now I'll talk about the the other<00:07:20.460> kind<00:07:20.940> of<00:07:21.000> interesting<00:07:21.360> cluster<00:07:21.780> we're 00:07:21.890 --> 00:07:21.900 align:start position:0% other kind of interesting cluster we're 00:07:21.900 --> 00:07:23.689 align:start position:0% other kind of interesting cluster we're seeing<00:07:22.139> in<00:07:22.259> the<00:07:22.380> top<00:07:22.500> left<00:07:22.740> which<00:07:23.099> is<00:07:23.280> uh 00:07:23.689 --> 00:07:23.699 align:start position:0% seeing in the top left which is uh 00:07:23.699 --> 00:07:26.050 align:start position:0% seeing in the top left which is uh application<00:07:24.599> classes<00:07:25.080> that<00:07:25.259> seem<00:07:25.500> to<00:07:25.620> require 00:07:26.050 --> 00:07:26.060 align:start position:0% application classes that seem to require 00:07:26.060 --> 00:07:28.969 align:start position:0% application classes that seem to require privacy<00:07:27.060> or<00:07:27.419> pseudonymity<00:07:28.080> of<00:07:28.319> some<00:07:28.500> sort<00:07:28.680> but 00:07:28.969 --> 00:07:28.979 align:start position:0% privacy or pseudonymity of some sort but 00:07:28.979 --> 00:07:31.730 align:start position:0% privacy or pseudonymity of some sort but don't<00:07:29.099> necessarily<00:07:29.520> require<00:07:29.699> six<00:07:30.060> sickness 00:07:31.730 --> 00:07:31.740 align:start position:0% don't necessarily require six sickness 00:07:31.740 --> 00:07:34.309 align:start position:0% don't necessarily require six sickness um<00:07:31.800> this<00:07:32.340> is<00:07:32.460> kind<00:07:32.639> of<00:07:32.699> like<00:07:32.819> a<00:07:33.120> more<00:07:33.319> nascent 00:07:34.309 --> 00:07:34.319 align:start position:0% um this is kind of like a more nascent 00:07:34.319 --> 00:07:36.409 align:start position:0% um this is kind of like a more nascent uh<00:07:34.919> ecosystem<00:07:35.340> of<00:07:35.580> things 00:07:36.409 --> 00:07:36.419 align:start position:0% uh ecosystem of things 00:07:36.419 --> 00:07:37.070 align:start position:0% uh ecosystem of things um 00:07:37.070 --> 00:07:37.080 align:start position:0% um 00:07:37.080 --> 00:07:40.010 align:start position:0% um many<00:07:37.560> of<00:07:37.680> them<00:07:37.800> don't<00:07:37.979> require<00:07:38.220> chains<00:07:38.940> and<00:07:39.180> so 00:07:40.010 --> 00:07:40.020 align:start position:0% many of them don't require chains and so 00:07:40.020 --> 00:07:42.230 align:start position:0% many of them don't require chains and so uh<00:07:40.800> I<00:07:40.979> think<00:07:41.099> relative<00:07:41.520> to<00:07:41.699> maybe<00:07:41.880> a<00:07:42.120> lot<00:07:42.180> of 00:07:42.230 --> 00:07:42.240 align:start position:0% uh I think relative to maybe a lot of 00:07:42.240 --> 00:07:43.430 align:start position:0% uh I think relative to maybe a lot of the<00:07:42.360> things<00:07:42.479> that<00:07:42.660> you<00:07:42.780> talked<00:07:43.020> about<00:07:43.080> they're 00:07:43.430 --> 00:07:43.440 align:start position:0% the things that you talked about they're 00:07:43.440 --> 00:07:46.089 align:start position:0% the things that you talked about they're perhaps<00:07:43.800> less<00:07:44.099> familiar<00:07:44.819> to<00:07:45.240> the<00:07:45.720> average 00:07:46.089 --> 00:07:46.099 align:start position:0% perhaps less familiar to the average 00:07:46.099 --> 00:07:48.950 align:start position:0% perhaps less familiar to the average ethereum<00:07:47.099> conference<00:07:47.460> attendee 00:07:48.950 --> 00:07:48.960 align:start position:0% ethereum conference attendee 00:07:48.960 --> 00:07:50.450 align:start position:0% ethereum conference attendee um<00:07:49.020> but<00:07:49.319> what<00:07:49.680> we're<00:07:49.800> seeing<00:07:50.099> is<00:07:50.220> that<00:07:50.340> they 00:07:50.450 --> 00:07:50.460 align:start position:0% um but what we're seeing is that they 00:07:50.460 --> 00:07:51.850 align:start position:0% um but what we're seeing is that they seem<00:07:50.639> to<00:07:50.819> they<00:07:51.000> seem<00:07:51.240> to<00:07:51.360> Cluster<00:07:51.660> around 00:07:51.850 --> 00:07:51.860 align:start position:0% seem to they seem to Cluster around 00:07:51.860 --> 00:07:54.529 align:start position:0% seem to they seem to Cluster around social<00:07:52.860> type<00:07:53.400> things 00:07:54.529 --> 00:07:54.539 align:start position:0% social type things 00:07:54.539 --> 00:07:56.510 align:start position:0% social type things um<00:07:54.599> this<00:07:54.780> doesn't<00:07:55.259> mean<00:07:55.500> that<00:07:55.740> this<00:07:55.979> is<00:07:56.160> all<00:07:56.340> it 00:07:56.510 --> 00:07:56.520 align:start position:0% um this doesn't mean that this is all it 00:07:56.520 --> 00:07:58.189 align:start position:0% um this doesn't mean that this is all it is<00:07:56.639> in<00:07:56.759> the<00:07:56.880> future<00:07:57.000> but<00:07:57.360> kind<00:07:57.840> of<00:07:57.960> want<00:07:58.080> to 00:07:58.189 --> 00:07:58.199 align:start position:0% is in the future but kind of want to 00:07:58.199 --> 00:08:02.270 align:start position:0% is in the future but kind of want to talk<00:07:58.319> about<00:07:58.500> what<00:07:59.220> we're<00:07:59.639> seeing<00:07:59.880> today 00:08:02.270 --> 00:08:02.280 align:start position:0% 00:08:02.280 --> 00:08:04.909 align:start position:0% um<00:08:02.460> and<00:08:02.940> so<00:08:03.120> in<00:08:03.840> thinking<00:08:04.080> about 00:08:04.909 --> 00:08:04.919 align:start position:0% um and so in thinking about 00:08:04.919 --> 00:08:07.610 align:start position:0% um and so in thinking about this<00:08:05.759> quadrant<00:08:06.300> I<00:08:06.660> spend<00:08:06.900> a<00:08:07.319> lot<00:08:07.440> of<00:08:07.500> time 00:08:07.610 --> 00:08:07.620 align:start position:0% this quadrant I spend a lot of time 00:08:07.620 --> 00:08:09.409 align:start position:0% this quadrant I spend a lot of time thinking<00:08:07.919> about<00:08:08.039> sort<00:08:08.340> of<00:08:08.400> this<00:08:08.580> spectrum 00:08:09.409 --> 00:08:09.419 align:start position:0% thinking about sort of this spectrum 00:08:09.419 --> 00:08:11.629 align:start position:0% thinking about sort of this spectrum there's<00:08:10.319> a<00:08:10.440> Spectra<00:08:10.800> so<00:08:11.039> let's<00:08:11.160> say<00:08:11.340> think 00:08:11.629 --> 00:08:11.639 align:start position:0% there's a Spectra so let's say think 00:08:11.639 --> 00:08:13.790 align:start position:0% there's a Spectra so let's say think about<00:08:11.819> those<00:08:12.120> arrows<00:08:12.599> or<00:08:12.840> zero<00:08:13.560> knowledge 00:08:13.790 --> 00:08:13.800 align:start position:0% about those arrows or zero knowledge 00:08:13.800 --> 00:08:15.890 align:start position:0% about those arrows or zero knowledge proofs<00:08:14.099> being<00:08:14.280> made<00:08:14.460> the<00:08:15.120> computers<00:08:15.479> are<00:08:15.720> like 00:08:15.890 --> 00:08:15.900 align:start position:0% proofs being made the computers are like 00:08:15.900 --> 00:08:18.350 align:start position:0% proofs being made the computers are like say<00:08:16.259> like<00:08:16.440> an<00:08:16.560> end<00:08:16.680> user<00:08:16.979> computer<00:08:17.360> ethereum 00:08:18.350 --> 00:08:18.360 align:start position:0% say like an end user computer ethereum 00:08:18.360 --> 00:08:21.710 align:start position:0% say like an end user computer ethereum there<00:08:19.199> obviously<00:08:19.680> is<00:08:19.919> a<00:08:20.580> decentralized<00:08:21.539> state 00:08:21.710 --> 00:08:21.720 align:start position:0% there obviously is a decentralized state 00:08:21.720 --> 00:08:24.770 align:start position:0% there obviously is a decentralized state machine<00:08:22.080> with<00:08:22.919> a<00:08:23.340> high-ish<00:08:23.759> block<00:08:24.060> or<00:08:24.360> a<00:08:24.479> low 00:08:24.770 --> 00:08:24.780 align:start position:0% machine with a high-ish block or a low 00:08:24.780 --> 00:08:27.529 align:start position:0% machine with a high-ish block or a low low<00:08:24.900> ish<00:08:25.860> relative<00:08:26.099> to<00:08:26.280> congestion<00:08:26.819> block<00:08:27.240> gas 00:08:27.529 --> 00:08:27.539 align:start position:0% low ish relative to congestion block gas 00:08:27.539 --> 00:08:28.490 align:start position:0% low ish relative to congestion block gas limit 00:08:28.490 --> 00:08:28.500 align:start position:0% limit 00:08:28.500 --> 00:08:30.830 align:start position:0% limit those<00:08:29.039> those<00:08:29.099> bottom<00:08:29.699> two<00:08:29.819> icons<00:08:30.180> are<00:08:30.479> sort<00:08:30.720> of 00:08:30.830 --> 00:08:30.840 align:start position:0% those those bottom two icons are sort of 00:08:30.840 --> 00:08:33.829 align:start position:0% those those bottom two icons are sort of uh<00:08:31.800> how<00:08:32.520> proofs<00:08:32.880> are<00:08:33.000> being<00:08:33.180> consumed<00:08:33.539> and<00:08:33.719> the 00:08:33.829 --> 00:08:33.839 align:start position:0% uh how proofs are being consumed and the 00:08:33.839 --> 00:08:35.269 align:start position:0% uh how proofs are being consumed and the top<00:08:33.959> two<00:08:34.080> icons<00:08:34.440> are<00:08:34.560> how<00:08:34.740> proofs<00:08:34.979> are<00:08:35.099> being 00:08:35.269 --> 00:08:35.279 align:start position:0% top two icons are how proofs are being 00:08:35.279 --> 00:08:36.829 align:start position:0% top two icons are how proofs are being produced<00:08:35.640> it<00:08:36.180> feels<00:08:36.360> like<00:08:36.479> there's<00:08:36.599> a 00:08:36.829 --> 00:08:36.839 align:start position:0% produced it feels like there's a 00:08:36.839 --> 00:08:40.010 align:start position:0% produced it feels like there's a spectrum<00:08:37.200> of<00:08:37.919> applications<00:08:38.700> and<00:08:39.539> how<00:08:39.899> we 00:08:40.010 --> 00:08:40.020 align:start position:0% spectrum of applications and how we 00:08:40.020 --> 00:08:41.930 align:start position:0% spectrum of applications and how we think<00:08:40.140> about<00:08:40.320> what<00:08:40.620> is<00:08:40.740> consumed<00:08:41.279> is<00:08:41.700> it<00:08:41.880> being 00:08:41.930 --> 00:08:41.940 align:start position:0% think about what is consumed is it being 00:08:41.940 --> 00:08:44.029 align:start position:0% think about what is consumed is it being consumed<00:08:42.360> by<00:08:42.479> a<00:08:42.599> human<00:08:42.719> is<00:08:43.020> it<00:08:43.200> be<00:08:43.320> consumed<00:08:43.680> by 00:08:44.029 --> 00:08:44.039 align:start position:0% consumed by a human is it be consumed by 00:08:44.039 --> 00:08:46.130 align:start position:0% consumed by a human is it be consumed by a<00:08:44.339> state<00:08:44.459> machine<00:08:44.700> or<00:08:45.240> a<00:08:45.420> decentralized<00:08:45.899> date 00:08:46.130 --> 00:08:46.140 align:start position:0% a state machine or a decentralized date 00:08:46.140 --> 00:08:47.269 align:start position:0% a state machine or a decentralized date machine 00:08:47.269 --> 00:08:47.279 align:start position:0% machine 00:08:47.279 --> 00:08:48.350 align:start position:0% machine um it's<00:08:47.640> being<00:08:47.880> consumed<00:08:48.180> by<00:08:48.300> a 00:08:48.350 --> 00:08:48.360 align:start position:0% um it's being consumed by a 00:08:48.360 --> 00:08:49.310 align:start position:0% um it's being consumed by a decentralized<00:08:48.720> state<00:08:48.959> machine<00:08:49.140> like 00:08:49.310 --> 00:08:49.320 align:start position:0% decentralized state machine like 00:08:49.320 --> 00:08:50.329 align:start position:0% decentralized state machine like ethereum 00:08:50.329 --> 00:08:50.339 align:start position:0% ethereum 00:08:50.339 --> 00:08:53.210 align:start position:0% ethereum hence<00:08:50.820> like<00:08:51.120> on-chain<00:08:51.540> verification<00:08:52.080> uh<00:08:52.980> you 00:08:53.210 --> 00:08:53.220 align:start position:0% hence like on-chain verification uh you 00:08:53.220 --> 00:08:54.350 align:start position:0% hence like on-chain verification uh you need<00:08:53.339> things<00:08:53.459> to<00:08:53.640> be<00:08:53.760> considerably<00:08:54.180> more 00:08:54.350 --> 00:08:54.360 align:start position:0% need things to be considerably more 00:08:54.360 --> 00:08:56.870 align:start position:0% need things to be considerably more succinct<00:08:54.839> this<00:08:55.620> being<00:08:55.980> interpreted<00:08:56.580> by<00:08:56.760> a 00:08:56.870 --> 00:08:56.880 align:start position:0% succinct this being interpreted by a 00:08:56.880 --> 00:08:59.509 align:start position:0% succinct this being interpreted by a human<00:08:57.060> maybe<00:08:57.600> you<00:08:57.899> don't<00:08:58.019> maybe<00:08:58.800> it<00:08:59.100> can<00:08:59.279> be 00:08:59.509 --> 00:08:59.519 align:start position:0% human maybe you don't maybe it can be 00:08:59.519 --> 00:09:01.370 align:start position:0% human maybe you don't maybe it can be like<00:08:59.940> a<00:09:00.240> much<00:09:00.360> larger<00:09:00.779> piece<00:09:01.140> of<00:09:01.200> information 00:09:01.370 --> 00:09:01.380 align:start position:0% like a much larger piece of information 00:09:01.380 --> 00:09:03.470 align:start position:0% like a much larger piece of information that<00:09:01.920> is<00:09:02.040> like<00:09:02.220> human<00:09:02.459> interpretable<00:09:03.060> or<00:09:03.300> has 00:09:03.470 --> 00:09:03.480 align:start position:0% that is like human interpretable or has 00:09:03.480 --> 00:09:05.210 align:start position:0% that is like human interpretable or has like<00:09:03.660> some<00:09:03.899> kind<00:09:04.080> of<00:09:04.140> like<00:09:04.440> interesting 00:09:05.210 --> 00:09:05.220 align:start position:0% like some kind of like interesting 00:09:05.220 --> 00:09:08.030 align:start position:0% like some kind of like interesting graphical<00:09:05.640> representation 00:09:08.030 --> 00:09:08.040 align:start position:0% graphical representation 00:09:08.040 --> 00:09:10.070 align:start position:0% graphical representation and<00:09:08.459> so<00:09:08.640> in<00:09:09.120> thinking<00:09:09.420> about<00:09:09.540> this<00:09:09.779> spectrum 00:09:10.070 --> 00:09:10.080 align:start position:0% and so in thinking about this spectrum 00:09:10.080 --> 00:09:11.930 align:start position:0% and so in thinking about this spectrum and<00:09:10.260> again<00:09:10.380> this<00:09:10.560> is<00:09:10.680> this<00:09:10.920> is<00:09:11.100> not<00:09:11.279> including 00:09:11.930 --> 00:09:11.940 align:start position:0% and again this is this is not including 00:09:11.940 --> 00:09:13.009 align:start position:0% and again this is this is not including a<00:09:12.060> lot<00:09:12.120> of<00:09:12.240> things<00:09:12.360> in<00:09:12.480> the<00:09:12.540> middle<00:09:12.660> so<00:09:12.839> things 00:09:13.009 --> 00:09:13.019 align:start position:0% a lot of things in the middle so things 00:09:13.019 --> 00:09:15.350 align:start position:0% a lot of things in the middle so things in<00:09:13.140> the<00:09:13.200> middle<00:09:13.320> might<00:09:13.560> be<00:09:13.680> things<00:09:13.920> like<00:09:14.360> uh 00:09:15.350 --> 00:09:15.360 align:start position:0% in the middle might be things like uh 00:09:15.360 --> 00:09:18.410 align:start position:0% in the middle might be things like uh like<00:09:16.019> being<00:09:16.320> consumed<00:09:16.920> by<00:09:17.399> like<00:09:17.880> an<00:09:18.060> app<00:09:18.180> chain 00:09:18.410 --> 00:09:18.420 align:start position:0% like being consumed by like an app chain 00:09:18.420 --> 00:09:21.889 align:start position:0% like being consumed by like an app chain or<00:09:18.660> a<00:09:18.779> layer<00:09:19.019> two<00:09:19.200> or<00:09:19.800> a<00:09:20.160> a<00:09:20.880> lower<00:09:21.300> congestion 00:09:21.889 --> 00:09:21.899 align:start position:0% or a layer two or a a lower congestion 00:09:21.899 --> 00:09:23.690 align:start position:0% or a layer two or a a lower congestion layer<00:09:22.260> one<00:09:22.380> or<00:09:22.740> a<00:09:22.860> short-lived<00:09:23.279> chain<00:09:23.459> or 00:09:23.690 --> 00:09:23.700 align:start position:0% layer one or a short-lived chain or 00:09:23.700 --> 00:09:24.769 align:start position:0% layer one or a short-lived chain or something<00:09:23.880> like<00:09:24.120> that 00:09:24.769 --> 00:09:24.779 align:start position:0% something like that 00:09:24.779 --> 00:09:27.350 align:start position:0% something like that but<00:09:25.260> these<00:09:25.500> two<00:09:25.620> ends<00:09:25.920> of<00:09:25.980> the<00:09:26.100> spectrum<00:09:26.459> I 00:09:27.350 --> 00:09:27.360 align:start position:0% but these two ends of the spectrum I 00:09:27.360 --> 00:09:29.269 align:start position:0% but these two ends of the spectrum I think<00:09:27.480> we<00:09:27.660> all<00:09:27.779> quite<00:09:28.019> understand<00:09:28.200> like<00:09:28.680> the 00:09:29.269 --> 00:09:29.279 align:start position:0% think we all quite understand like the 00:09:29.279 --> 00:09:31.009 align:start position:0% think we all quite understand like the chain<00:09:29.399> side<00:09:29.700> of<00:09:30.060> applications<00:09:30.480> like<00:09:30.779> things 00:09:31.009 --> 00:09:31.019 align:start position:0% chain side of applications like things 00:09:31.019 --> 00:09:32.630 align:start position:0% chain side of applications like things that<00:09:31.320> that<00:09:31.440> use<00:09:31.680> your<00:09:31.920> knowledge<00:09:32.220> proofs<00:09:32.519> that 00:09:32.630 --> 00:09:32.640 align:start position:0% that that use your knowledge proofs that 00:09:32.640 --> 00:09:33.910 align:start position:0% that that use your knowledge proofs that are<00:09:32.760> that 00:09:33.910 --> 00:09:33.920 align:start position:0% are that 00:09:33.920 --> 00:09:36.470 align:start position:0% are that requires<00:09:34.920> tend<00:09:35.580> to<00:09:35.640> benefit<00:09:35.820> from<00:09:36.120> being<00:09:36.300> very 00:09:36.470 --> 00:09:36.480 align:start position:0% requires tend to benefit from being very 00:09:36.480 --> 00:09:38.030 align:start position:0% requires tend to benefit from being very composable<00:09:36.959> creating<00:09:37.620> things<00:09:37.800> that<00:09:37.920> are 00:09:38.030 --> 00:09:38.040 align:start position:0% composable creating things that are 00:09:38.040 --> 00:09:40.550 align:start position:0% composable creating things that are canonical<00:09:38.399> on<00:09:39.120> the<00:09:39.240> other<00:09:39.300> hand<00:09:39.480> if<00:09:40.380> we're 00:09:40.550 --> 00:09:40.560 align:start position:0% canonical on the other hand if we're 00:09:40.560 --> 00:09:42.050 align:start position:0% canonical on the other hand if we're talking<00:09:40.680> about<00:09:40.860> like<00:09:41.160> humans<00:09:41.580> interpreting 00:09:42.050 --> 00:09:42.060 align:start position:0% talking about like humans interpreting 00:09:42.060 --> 00:09:44.389 align:start position:0% talking about like humans interpreting proofs<00:09:42.480> it<00:09:43.019> feels<00:09:43.260> like<00:09:43.440> it's<00:09:43.740> the 00:09:44.389 --> 00:09:44.399 align:start position:0% proofs it feels like it's the 00:09:44.399 --> 00:09:46.370 align:start position:0% proofs it feels like it's the applications<00:09:44.820> want<00:09:45.360> to<00:09:45.480> be<00:09:45.600> higher<00:09:45.959> velocity 00:09:46.370 --> 00:09:46.380 align:start position:0% applications want to be higher velocity 00:09:46.380 --> 00:09:47.570 align:start position:0% applications want to be higher velocity or<00:09:46.560> can<00:09:46.740> benefit<00:09:46.860> from<00:09:47.160> being<00:09:47.279> higher 00:09:47.570 --> 00:09:47.580 align:start position:0% or can benefit from being higher 00:09:47.580 --> 00:09:49.550 align:start position:0% or can benefit from being higher velocity<00:09:48.000> because<00:09:48.300> uh<00:09:48.959> you<00:09:49.080> don't<00:09:49.200> need<00:09:49.380> a 00:09:49.550 --> 00:09:49.560 align:start position:0% velocity because uh you don't need a 00:09:49.560 --> 00:09:51.590 align:start position:0% velocity because uh you don't need a chain<00:09:49.740> verifying<00:09:50.279> every<00:09:50.399> proof<00:09:50.880> uh<00:09:51.420> things 00:09:51.590 --> 00:09:51.600 align:start position:0% chain verifying every proof uh things 00:09:51.600 --> 00:09:53.750 align:start position:0% chain verifying every proof uh things are<00:09:51.839> more<00:09:51.959> ephemeral<00:09:52.440> maybe<00:09:52.800> you<00:09:53.279> know<00:09:53.339> humans 00:09:53.750 --> 00:09:53.760 align:start position:0% are more ephemeral maybe you know humans 00:09:53.760 --> 00:09:55.910 align:start position:0% are more ephemeral maybe you know humans don't<00:09:54.060> necessarily<00:09:54.660> have<00:09:54.959> like<00:09:55.260> persistent 00:09:55.910 --> 00:09:55.920 align:start position:0% don't necessarily have like persistent 00:09:55.920 --> 00:09:58.009 align:start position:0% don't necessarily have like persistent memory<00:09:56.220> themselves<00:09:56.700> right<00:09:57.060> like<00:09:57.300> we<00:09:57.480> see<00:09:57.899> a 00:09:58.009 --> 00:09:58.019 align:start position:0% memory themselves right like we see a 00:09:58.019 --> 00:09:59.449 align:start position:0% memory themselves right like we see a lot<00:09:58.140> of<00:09:58.260> things<00:09:58.440> on<00:09:58.680> Twitter<00:09:58.800> and<00:09:59.100> sort<00:09:59.339> of 00:09:59.449 --> 00:09:59.459 align:start position:0% lot of things on Twitter and sort of 00:09:59.459 --> 00:10:01.550 align:start position:0% lot of things on Twitter and sort of like<00:09:59.640> form<00:09:59.940> a<00:10:00.600> vague<00:10:00.839> understanding<00:10:01.380> of 00:10:01.550 --> 00:10:01.560 align:start position:0% like form a vague understanding of 00:10:01.560 --> 00:10:04.009 align:start position:0% like form a vague understanding of what's<00:10:01.740> going<00:10:01.920> on 00:10:04.009 --> 00:10:04.019 align:start position:0% what's going on 00:10:04.019 --> 00:10:06.769 align:start position:0% what's going on um<00:10:04.080> another<00:10:04.260> mental<00:10:04.680> model<00:10:04.800> I<00:10:04.980> think<00:10:05.100> about<00:10:05.220> is 00:10:06.769 --> 00:10:06.779 align:start position:0% um another mental model I think about is 00:10:06.779 --> 00:10:10.250 align:start position:0% um another mental model I think about is um<00:10:07.100> zkps<00:10:08.100> on<00:10:08.820> the<00:10:08.940> on<00:10:09.060> the<00:10:09.180> Privacy<00:10:09.720> not<00:10:09.959> just 00:10:10.250 --> 00:10:10.260 align:start position:0% um zkps on the on the Privacy not just 00:10:10.260 --> 00:10:13.490 align:start position:0% um zkps on the on the Privacy not just inside<00:10:10.500> is<00:10:10.920> uh<00:10:11.820> like<00:10:12.060> vkp<00:10:12.839> sort<00:10:13.019> of<00:10:13.080> creating<00:10:13.320> a 00:10:13.490 --> 00:10:13.500 align:start position:0% inside is uh like vkp sort of creating a 00:10:13.500 --> 00:10:15.949 align:start position:0% inside is uh like vkp sort of creating a new<00:10:13.680> content<00:10:14.040> type<00:10:14.279> which<00:10:15.000> is<00:10:15.120> like<00:10:15.420> all<00:10:15.779> these 00:10:15.949 --> 00:10:15.959 align:start position:0% new content type which is like all these 00:10:15.959 --> 00:10:18.170 align:start position:0% new content type which is like all these places<00:10:16.140> where<00:10:16.680> people<00:10:17.399> create<00:10:17.640> content 00:10:18.170 --> 00:10:18.180 align:start position:0% places where people create content 00:10:18.180 --> 00:10:20.030 align:start position:0% places where people create content online<00:10:18.779> today 00:10:20.030 --> 00:10:20.040 align:start position:0% online today 00:10:20.040 --> 00:10:21.889 align:start position:0% online today um<00:10:20.100> what<00:10:20.279> if<00:10:20.459> they<00:10:20.580> now<00:10:20.820> were<00:10:21.120> enriched<00:10:21.779> with 00:10:21.889 --> 00:10:21.899 align:start position:0% um what if they now were enriched with 00:10:21.899 --> 00:10:23.509 align:start position:0% um what if they now were enriched with the<00:10:22.019> zkp<00:10:22.500> of<00:10:22.680> some<00:10:22.800> sort<00:10:22.980> it<00:10:23.100> kind<00:10:23.220> of<00:10:23.339> means 00:10:23.509 --> 00:10:23.519 align:start position:0% the zkp of some sort it kind of means 00:10:23.519 --> 00:10:24.710 align:start position:0% the zkp of some sort it kind of means something<00:10:23.640> a<00:10:23.880> little<00:10:23.940> bit<00:10:24.060> different<00:10:24.240> which 00:10:24.710 --> 00:10:24.720 align:start position:0% something a little bit different which 00:10:24.720 --> 00:10:26.449 align:start position:0% something a little bit different which which<00:10:24.899> is<00:10:25.320> quite<00:10:25.500> cool 00:10:26.449 --> 00:10:26.459 align:start position:0% which is quite cool 00:10:26.459 --> 00:10:28.130 align:start position:0% which is quite cool um<00:10:26.940> so<00:10:27.180> I<00:10:27.360> didn't<00:10:27.480> really<00:10:27.600> talk<00:10:27.720> about<00:10:27.839> I 00:10:28.130 --> 00:10:28.140 align:start position:0% um so I didn't really talk about I 00:10:28.140 --> 00:10:29.690 align:start position:0% um so I didn't really talk about I realized<00:10:28.500> I<00:10:29.100> probably<00:10:29.220> should<00:10:29.399> have<00:10:29.459> had<00:10:29.580> a 00:10:29.690 --> 00:10:29.700 align:start position:0% realized I probably should have had a 00:10:29.700 --> 00:10:31.070 align:start position:0% realized I probably should have had a slide<00:10:29.940> here<00:10:30.060> presenting<00:10:30.480> some<00:10:30.600> applications 00:10:31.070 --> 00:10:31.080 align:start position:0% slide here presenting some applications 00:10:31.080 --> 00:10:32.870 align:start position:0% slide here presenting some applications but 00:10:32.870 --> 00:10:32.880 align:start position:0% but 00:10:32.880 --> 00:10:37.009 align:start position:0% but um some<00:10:33.480> examples<00:10:33.899> are<00:10:34.580> uh<00:10:35.580> like 00:10:37.009 --> 00:10:37.019 align:start position:0% um some examples are uh like 00:10:37.019 --> 00:10:38.389 align:start position:0% um some examples are uh like um<00:10:37.080> actually<00:10:37.320> let<00:10:37.560> me<00:10:37.680> just<00:10:37.800> pull<00:10:37.920> back<00:10:38.100> go 00:10:38.389 --> 00:10:38.399 align:start position:0% um actually let me just pull back go 00:10:38.399 --> 00:10:40.430 align:start position:0% um actually let me just pull back go back<00:10:38.580> to<00:10:38.700> this<00:10:39.480> slide 00:10:40.430 --> 00:10:40.440 align:start position:0% back to this slide 00:10:40.440 --> 00:10:41.870 align:start position:0% back to this slide so<00:10:40.800> it's<00:10:40.980> done<00:10:41.100> before<00:10:41.279> which<00:10:41.519> is<00:10:41.640> a<00:10:41.760> project 00:10:41.870 --> 00:10:41.880 align:start position:0% so it's done before which is a project 00:10:41.880 --> 00:10:44.509 align:start position:0% so it's done before which is a project of<00:10:42.060> the<00:10:42.180> PSE<00:10:42.480> uh<00:10:43.200> which<00:10:43.380> is<00:10:43.500> kind<00:10:43.680> of<00:10:43.740> group<00:10:43.980> uh 00:10:44.509 --> 00:10:44.519 align:start position:0% of the PSE uh which is kind of group uh 00:10:44.519 --> 00:10:47.990 align:start position:0% of the PSE uh which is kind of group uh group<00:10:44.760> membership<00:10:45.120> in<00:10:45.899> like<00:10:46.320> proving 00:10:47.990 --> 00:10:48.000 align:start position:0% group membership in like proving 00:10:48.000 --> 00:10:49.610 align:start position:0% group membership in like proving private<00:10:48.600> group<00:10:48.779> membership<00:10:49.140> so<00:10:49.380> you<00:10:49.560> can 00:10:49.610 --> 00:10:49.620 align:start position:0% private group membership so you can 00:10:49.620 --> 00:10:51.170 align:start position:0% private group membership so you can prove<00:10:49.800> that<00:10:49.920> you<00:10:50.160> are<00:10:50.279> one<00:10:50.519> of<00:10:50.640> the<00:10:50.820> people<00:10:50.940> in 00:10:51.170 --> 00:10:51.180 align:start position:0% prove that you are one of the people in 00:10:51.180 --> 00:10:52.370 align:start position:0% prove that you are one of the people in a<00:10:51.300> group<00:10:51.420> and<00:10:51.600> so<00:10:51.720> you<00:10:51.779> can<00:10:51.899> use<00:10:51.959> this<00:10:52.079> to<00:10:52.200> do 00:10:52.370 --> 00:10:52.380 align:start position:0% a group and so you can use this to do 00:10:52.380 --> 00:10:54.530 align:start position:0% a group and so you can use this to do like<00:10:52.500> private<00:10:52.860> like<00:10:53.279> uh<00:10:53.880> synonymous<00:10:54.360> message 00:10:54.530 --> 00:10:54.540 align:start position:0% like private like uh synonymous message 00:10:54.540 --> 00:10:56.630 align:start position:0% like private like uh synonymous message board<00:10:54.839> or<00:10:55.079> something<00:10:55.200> like<00:10:55.440> this 00:10:56.630 --> 00:10:56.640 align:start position:0% board or something like this 00:10:56.640 --> 00:10:58.430 align:start position:0% board or something like this um things<00:10:56.880> like<00:10:57.060> CK<00:10:57.480> email<00:10:57.720> like<00:10:58.019> proving 00:10:58.430 --> 00:10:58.440 align:start position:0% um things like CK email like proving 00:10:58.440 --> 00:10:59.449 align:start position:0% um things like CK email like proving that 00:10:59.449 --> 00:10:59.459 align:start position:0% that 00:10:59.459 --> 00:11:01.730 align:start position:0% that you<00:10:59.820> know<00:10:59.880> mail<00:11:00.120> servers<00:11:00.660> it<00:11:01.140> turns<00:11:01.440> out<00:11:01.500> many 00:11:01.730 --> 00:11:01.740 align:start position:0% you know mail servers it turns out many 00:11:01.740 --> 00:11:05.690 align:start position:0% you know mail servers it turns out many of<00:11:01.920> them<00:11:02.040> uh<00:11:02.880> like<00:11:03.240> sign<00:11:04.040> uh<00:11:05.040> sign<00:11:05.339> the<00:11:05.579> email 00:11:05.690 --> 00:11:05.700 align:start position:0% of them uh like sign uh sign the email 00:11:05.700 --> 00:11:08.870 align:start position:0% of them uh like sign uh sign the email body<00:11:06.000> so<00:11:06.540> uh<00:11:07.200> you<00:11:07.440> can<00:11:07.560> you<00:11:07.920> can<00:11:08.040> do<00:11:08.339> a<00:11:08.519> zero 00:11:08.870 --> 00:11:08.880 align:start position:0% body so uh you can you can do a zero 00:11:08.880 --> 00:11:09.949 align:start position:0% body so uh you can you can do a zero knowledge<00:11:09.060> proof<00:11:09.360> that<00:11:09.420> you<00:11:09.540> received<00:11:09.839> an 00:11:09.949 --> 00:11:09.959 align:start position:0% knowledge proof that you received an 00:11:09.959 --> 00:11:11.210 align:start position:0% knowledge proof that you received an email<00:11:10.079> with<00:11:10.380> certain<00:11:10.620> Properties<00:11:10.980> or 00:11:11.210 --> 00:11:11.220 align:start position:0% email with certain Properties or 00:11:11.220 --> 00:11:12.290 align:start position:0% email with certain Properties or something<00:11:11.399> like<00:11:11.579> that<00:11:11.700> which<00:11:11.880> is<00:11:12.000> kind<00:11:12.180> of 00:11:12.290 --> 00:11:12.300 align:start position:0% something like that which is kind of 00:11:12.300 --> 00:11:14.810 align:start position:0% something like that which is kind of cool<00:11:12.899> and<00:11:13.440> and<00:11:13.620> do<00:11:13.800> things<00:11:14.040> like<00:11:14.220> it's<00:11:14.700> not 00:11:14.810 --> 00:11:14.820 align:start position:0% cool and and do things like it's not 00:11:14.820 --> 00:11:16.370 align:start position:0% cool and and do things like it's not obvious<00:11:15.120> that<00:11:15.360> that's<00:11:15.480> your<00:11:15.720> knowledge<00:11:16.200> proof 00:11:16.370 --> 00:11:16.380 align:start position:0% obvious that that's your knowledge proof 00:11:16.380 --> 00:11:17.509 align:start position:0% obvious that that's your knowledge proof in<00:11:16.500> either<00:11:16.620> these<00:11:16.920> cases<00:11:17.100> needs<00:11:17.339> to<00:11:17.399> be 00:11:17.509 --> 00:11:17.519 align:start position:0% in either these cases needs to be 00:11:17.519 --> 00:11:20.509 align:start position:0% in either these cases needs to be interpreted<00:11:18.000> by<00:11:18.120> a<00:11:18.240> chain 00:11:20.509 --> 00:11:20.519 align:start position:0% 00:11:20.519 --> 00:11:21.769 align:start position:0% um<00:11:20.579> and<00:11:20.820> so<00:11:20.940> the<00:11:21.120> requirements<00:11:21.480> in<00:11:21.660> this 00:11:21.769 --> 00:11:21.779 align:start position:0% um and so the requirements in this 00:11:21.779 --> 00:11:23.930 align:start position:0% um and so the requirements in this quadrant<00:11:22.140> are<00:11:22.500> quite<00:11:23.040> a<00:11:23.220> bit<00:11:23.220> different<00:11:23.940> um 00:11:23.930 --> 00:11:23.940 align:start position:0% quadrant are quite a bit different um 00:11:23.940 --> 00:11:25.610 align:start position:0% quadrant are quite a bit different um than<00:11:24.180> and<00:11:24.420> then<00:11:24.600> the<00:11:24.779> the<00:11:24.839> quantity<00:11:25.260> e<00:11:25.380> was 00:11:25.610 --> 00:11:25.620 align:start position:0% than and then the the quantity e was 00:11:25.620 --> 00:11:27.590 align:start position:0% than and then the the quantity e was talking<00:11:25.740> about<00:11:25.920> and<00:11:26.220> that<00:11:26.399> like<00:11:26.640> verification 00:11:27.590 --> 00:11:27.600 align:start position:0% talking about and that like verification 00:11:27.600 --> 00:11:28.670 align:start position:0% talking about and that like verification complexity<00:11:28.079> doesn't<00:11:28.260> matter<00:11:28.440> as<00:11:28.560> much 00:11:28.670 --> 00:11:28.680 align:start position:0% complexity doesn't matter as much 00:11:28.680 --> 00:11:30.889 align:start position:0% complexity doesn't matter as much verification<00:11:29.220> complexity<00:11:29.820> matters<00:11:30.660> its 00:11:30.889 --> 00:11:30.899 align:start position:0% verification complexity matters its 00:11:30.899 --> 00:11:32.449 align:start position:0% verification complexity matters its thickness<00:11:31.200> because 00:11:32.449 --> 00:11:32.459 align:start position:0% thickness because 00:11:32.459 --> 00:11:34.250 align:start position:0% thickness because um or<00:11:32.940> matters<00:11:33.300> when<00:11:33.540> you're<00:11:33.660> verifying<00:11:34.140> on 00:11:34.250 --> 00:11:34.260 align:start position:0% um or matters when you're verifying on 00:11:34.260 --> 00:11:35.750 align:start position:0% um or matters when you're verifying on chain<00:11:34.440> because<00:11:34.800> you<00:11:35.160> don't<00:11:35.279> want<00:11:35.459> the<00:11:35.579> chain 00:11:35.750 --> 00:11:35.760 align:start position:0% chain because you don't want the chain 00:11:35.760 --> 00:11:37.850 align:start position:0% chain because you don't want the chain to<00:11:36.000> have<00:11:36.120> to<00:11:36.300> spend<00:11:36.660> a<00:11:36.839> lot<00:11:36.899> of<00:11:37.019> gas<00:11:37.140> to<00:11:37.500> verify 00:11:37.850 --> 00:11:37.860 align:start position:0% to have to spend a lot of gas to verify 00:11:37.860 --> 00:11:39.710 align:start position:0% to have to spend a lot of gas to verify your<00:11:37.980> proof<00:11:38.279> but<00:11:38.700> if<00:11:38.880> a<00:11:39.000> human's<00:11:39.240> verifying<00:11:39.600> it 00:11:39.710 --> 00:11:39.720 align:start position:0% your proof but if a human's verifying it 00:11:39.720 --> 00:11:41.750 align:start position:0% your proof but if a human's verifying it like<00:11:39.839> whatever<00:11:40.019> right<00:11:40.440> like<00:11:40.740> uh<00:11:41.399> it<00:11:41.579> can<00:11:41.640> be 00:11:41.750 --> 00:11:41.760 align:start position:0% like whatever right like uh it can be 00:11:41.760 --> 00:11:44.150 align:start position:0% like whatever right like uh it can be done<00:11:41.940> somewhere<00:11:42.420> else<00:11:42.540> uh<00:11:43.200> like<00:11:43.440> off<00:11:43.860> chain 00:11:44.150 --> 00:11:44.160 align:start position:0% done somewhere else uh like off chain 00:11:44.160 --> 00:11:46.069 align:start position:0% done somewhere else uh like off chain and<00:11:44.519> or<00:11:45.000> like<00:11:45.180> you<00:11:45.300> know<00:11:45.420> it<00:11:45.540> can<00:11:45.720> use<00:11:45.839> like 00:11:46.069 --> 00:11:46.079 align:start position:0% and or like you know it can use like 00:11:46.079 --> 00:11:46.850 align:start position:0% and or like you know it can use like some 00:11:46.850 --> 00:11:46.860 align:start position:0% some 00:11:46.860 --> 00:11:48.949 align:start position:0% some like<00:11:47.519> even<00:11:47.820> consumer<00:11:48.300> Hardware<00:11:48.480> is<00:11:48.779> more 00:11:48.949 --> 00:11:48.959 align:start position:0% like even consumer Hardware is more 00:11:48.959 --> 00:11:50.930 align:start position:0% like even consumer Hardware is more powerful<00:11:49.200> than<00:11:49.500> a<00:11:49.800> chain 00:11:50.930 --> 00:11:50.940 align:start position:0% powerful than a chain 00:11:50.940 --> 00:11:52.610 align:start position:0% powerful than a chain um<00:11:51.000> proving<00:11:51.540> complexity<00:11:51.959> tends<00:11:52.260> to<00:11:52.320> matter<00:11:52.440> a 00:11:52.610 --> 00:11:52.620 align:start position:0% um proving complexity tends to matter a 00:11:52.620 --> 00:11:53.810 align:start position:0% um proving complexity tends to matter a lot<00:11:52.680> more<00:11:52.800> because<00:11:52.980> we<00:11:53.279> are<00:11:53.459> operating 00:11:53.810 --> 00:11:53.820 align:start position:0% lot more because we are operating 00:11:53.820 --> 00:11:55.730 align:start position:0% lot more because we are operating usually<00:11:54.180> on<00:11:54.360> a<00:11:54.480> consumer<00:11:54.839> device<00:11:54.959> for<00:11:55.260> proving 00:11:55.730 --> 00:11:55.740 align:start position:0% usually on a consumer device for proving 00:11:55.740 --> 00:11:57.590 align:start position:0% usually on a consumer device for proving so<00:11:56.220> consumer<00:11:56.640> device<00:11:56.760> proving<00:11:57.120> friendliness 00:11:57.590 --> 00:11:57.600 align:start position:0% so consumer device proving friendliness 00:11:57.600 --> 00:11:59.269 align:start position:0% so consumer device proving friendliness as<00:11:57.779> well<00:11:58.380> um<00:11:58.440> this<00:11:58.620> is<00:11:58.740> something<00:11:58.860> we<00:11:59.100> think 00:11:59.269 --> 00:11:59.279 align:start position:0% as well um this is something we think 00:11:59.279 --> 00:12:01.009 align:start position:0% as well um this is something we think about<00:11:59.399> a<00:11:59.640> lot<00:11:59.760> is<00:12:00.060> how<00:12:00.600> do<00:12:00.660> we<00:12:00.779> make<00:12:00.839> things 00:12:01.009 --> 00:12:01.019 align:start position:0% about a lot is how do we make things 00:12:01.019 --> 00:12:02.210 align:start position:0% about a lot is how do we make things work<00:12:01.140> in<00:12:01.260> a<00:12:01.380> web<00:12:01.500> browser<00:12:01.800> how<00:12:01.920> do<00:12:02.040> we<00:12:02.100> make 00:12:02.210 --> 00:12:02.220 align:start position:0% work in a web browser how do we make 00:12:02.220 --> 00:12:04.069 align:start position:0% work in a web browser how do we make things<00:12:02.339> work<00:12:02.519> in<00:12:02.640> a<00:12:02.820> mobile<00:12:02.880> device 00:12:04.069 --> 00:12:04.079 align:start position:0% things work in a mobile device 00:12:04.079 --> 00:12:06.170 align:start position:0% things work in a mobile device another<00:12:04.560> piece<00:12:04.920> is<00:12:05.100> you<00:12:05.399> know<00:12:05.459> like<00:12:05.700> given 00:12:06.170 --> 00:12:06.180 align:start position:0% another piece is you know like given 00:12:06.180 --> 00:12:07.550 align:start position:0% another piece is you know like given that<00:12:06.300> we<00:12:06.480> care<00:12:06.600> about<00:12:06.720> privacy<00:12:07.260> in<00:12:07.500> the 00:12:07.550 --> 00:12:07.560 align:start position:0% that we care about privacy in the 00:12:07.560 --> 00:12:09.350 align:start position:0% that we care about privacy in the Squadron<00:12:07.860> is<00:12:08.100> respect<00:12:08.519> for<00:12:08.700> sensitive<00:12:09.000> user 00:12:09.350 --> 00:12:09.360 align:start position:0% Squadron is respect for sensitive user 00:12:09.360 --> 00:12:11.870 align:start position:0% Squadron is respect for sensitive user information<00:12:09.540> so<00:12:09.899> if<00:12:10.079> anyone<00:12:10.500> was<00:12:10.800> around<00:12:10.980> for 00:12:11.870 --> 00:12:11.880 align:start position:0% information so if anyone was around for 00:12:11.880 --> 00:12:15.410 align:start position:0% information so if anyone was around for um<00:12:12.360> like<00:12:12.779> you<00:12:13.019> should<00:12:13.200> talk<00:12:13.440> earlier<00:12:14.220> today<00:12:14.459> uh 00:12:15.410 --> 00:12:15.420 align:start position:0% um like you should talk earlier today uh 00:12:15.420 --> 00:12:16.670 align:start position:0% um like you should talk earlier today uh where<00:12:15.600> where<00:12:15.779> he's<00:12:16.019> sort<00:12:16.200> of<00:12:16.260> been<00:12:16.380> developing 00:12:16.670 --> 00:12:16.680 align:start position:0% where where he's sort of been developing 00:12:16.680 --> 00:12:19.430 align:start position:0% where where he's sort of been developing this<00:12:16.980> new<00:12:17.160> deterministic<00:12:18.000> nullifier<00:12:18.420> scheme 00:12:19.430 --> 00:12:19.440 align:start position:0% this new deterministic nullifier scheme 00:12:19.440 --> 00:12:21.290 align:start position:0% this new deterministic nullifier scheme um<00:12:19.560> that<00:12:20.040> came<00:12:20.220> from<00:12:20.459> realizing<00:12:20.940> that<00:12:21.060> we<00:12:21.180> just 00:12:21.290 --> 00:12:21.300 align:start position:0% um that came from realizing that we just 00:12:21.300 --> 00:12:22.730 align:start position:0% um that came from realizing that we just couldn't<00:12:21.420> do<00:12:21.660> a<00:12:21.839> lot<00:12:21.899> of<00:12:22.019> things<00:12:22.140> with<00:12:22.380> private 00:12:22.730 --> 00:12:22.740 align:start position:0% couldn't do a lot of things with private 00:12:22.740 --> 00:12:26.329 align:start position:0% couldn't do a lot of things with private key<00:12:22.940> uh<00:12:23.940> in<00:12:24.480> in<00:12:24.720> uh<00:12:25.260> in<00:12:25.920> a<00:12:25.980> client<00:12:26.160> device 00:12:26.329 --> 00:12:26.339 align:start position:0% key uh in in uh in a client device 00:12:26.339 --> 00:12:28.550 align:start position:0% key uh in in uh in a client device because<00:12:26.700> it<00:12:26.880> would<00:12:27.000> we<00:12:27.480> would<00:12:27.899> need<00:12:28.079> to<00:12:28.320> pass 00:12:28.550 --> 00:12:28.560 align:start position:0% because it would we would need to pass 00:12:28.560 --> 00:12:30.050 align:start position:0% because it would we would need to pass this<00:12:28.920> very<00:12:29.100> sensitive<00:12:29.519> piece<00:12:29.820> of<00:12:29.880> information 00:12:30.050 --> 00:12:30.060 align:start position:0% this very sensitive piece of information 00:12:30.060 --> 00:12:31.610 align:start position:0% this very sensitive piece of information around<00:12:30.540> different<00:12:30.839> parts<00:12:31.019> of<00:12:31.200> application 00:12:31.610 --> 00:12:31.620 align:start position:0% around different parts of application 00:12:31.620 --> 00:12:32.930 align:start position:0% around different parts of application memory 00:12:32.930 --> 00:12:32.940 align:start position:0% memory 00:12:32.940 --> 00:12:34.430 align:start position:0% memory um<00:12:33.000> and<00:12:33.180> so<00:12:33.360> we<00:12:33.600> have<00:12:33.720> to<00:12:33.779> think<00:12:33.899> of<00:12:34.019> new<00:12:34.200> kind 00:12:34.430 --> 00:12:34.440 align:start position:0% um and so we have to think of new kind 00:12:34.440 --> 00:12:36.769 align:start position:0% um and so we have to think of new kind of<00:12:34.500> like<00:12:34.620> mechanisms<00:12:35.279> for<00:12:35.640> not<00:12:36.240> having<00:12:36.420> to<00:12:36.660> do 00:12:36.769 --> 00:12:36.779 align:start position:0% of like mechanisms for not having to do 00:12:36.779 --> 00:12:39.769 align:start position:0% of like mechanisms for not having to do that<00:12:36.959> oh<00:12:37.620> this<00:12:37.920> is<00:12:37.980> still<00:12:38.100> me<00:12:38.339> oh<00:12:38.820> cool 00:12:39.769 --> 00:12:39.779 align:start position:0% that oh this is still me oh cool 00:12:39.779 --> 00:12:42.290 align:start position:0% that oh this is still me oh cool all<00:12:40.320> right<00:12:40.440> so<00:12:40.680> some<00:12:40.920> of<00:12:41.040> the<00:12:41.160> some<00:12:41.339> of<00:12:41.519> the 00:12:42.290 --> 00:12:42.300 align:start position:0% all right so some of the some of the 00:12:42.300 --> 00:12:43.970 align:start position:0% all right so some of the some of the some<00:12:42.660> of<00:12:42.839> the<00:12:42.899> challenges 00:12:43.970 --> 00:12:43.980 align:start position:0% some of the challenges 00:12:43.980 --> 00:12:46.670 align:start position:0% some of the challenges um<00:12:44.040> that<00:12:44.279> we<00:12:44.459> see<00:12:44.760> uh<00:12:45.600> technical<00:12:45.959> technical 00:12:46.670 --> 00:12:46.680 align:start position:0% um that we see uh technical technical 00:12:46.680 --> 00:12:48.470 align:start position:0% um that we see uh technical technical challenges<00:12:46.980> in<00:12:47.160> the<00:12:47.220> next<00:12:47.339> six<00:12:47.519> months<00:12:48.300> um<00:12:48.360> so 00:12:48.470 --> 00:12:48.480 align:start position:0% challenges in the next six months um so 00:12:48.480 --> 00:12:49.670 align:start position:0% challenges in the next six months um so as<00:12:48.600> I<00:12:48.720> mentioned<00:12:48.899> earlier<00:12:49.139> like<00:12:49.320> we<00:12:49.440> need<00:12:49.620> to 00:12:49.670 --> 00:12:49.680 align:start position:0% as I mentioned earlier like we need to 00:12:49.680 --> 00:12:52.490 align:start position:0% as I mentioned earlier like we need to be<00:12:49.860> very<00:12:50.040> friendly<00:12:50.399> unlike<00:12:50.880> for<00:12:51.360> privacy<00:12:52.079> not 00:12:52.490 --> 00:12:52.500 align:start position:0% be very friendly unlike for privacy not 00:12:52.500 --> 00:12:55.670 align:start position:0% be very friendly unlike for privacy not succinct<00:12:52.980> uh<00:12:53.940> applications<00:12:54.480> and<00:12:55.139> in<00:12:55.380> research 00:12:55.670 --> 00:12:55.680 align:start position:0% succinct uh applications and in research 00:12:55.680 --> 00:12:56.690 align:start position:0% succinct uh applications and in research constraint<00:12:56.040> environments<00:12:56.399> like<00:12:56.519> mobile 00:12:56.690 --> 00:12:56.700 align:start position:0% constraint environments like mobile 00:12:56.700 --> 00:12:59.329 align:start position:0% constraint environments like mobile devices<00:12:57.000> like<00:12:57.720> like<00:12:58.320> uh 00:12:59.329 --> 00:12:59.339 align:start position:0% devices like like uh 00:12:59.339 --> 00:13:03.170 align:start position:0% devices like like uh web<00:12:59.760> browsers<00:13:00.240> I<00:13:00.720> think<00:13:00.839> a<00:13:01.019> lot<00:13:01.079> of<00:13:01.260> like 00:13:03.170 --> 00:13:03.180 align:start position:0% web browsers I think a lot of like 00:13:03.180 --> 00:13:06.350 align:start position:0% web browsers I think a lot of like um<00:13:03.779> a<00:13:04.320> lot<00:13:04.380> of<00:13:04.500> the<00:13:04.620> VK<00:13:04.980> space<00:13:05.279> is<00:13:05.760> assuming 00:13:06.350 --> 00:13:06.360 align:start position:0% um a lot of the VK space is assuming 00:13:06.360 --> 00:13:09.949 align:start position:0% um a lot of the VK space is assuming that<00:13:07.079> most<00:13:07.380> VK<00:13:07.800> proofs<00:13:08.399> will<00:13:08.579> be<00:13:08.820> produced<00:13:09.600> on 00:13:09.949 --> 00:13:09.959 align:start position:0% that most VK proofs will be produced on 00:13:09.959 --> 00:13:13.850 align:start position:0% that most VK proofs will be produced on like<00:13:10.200> very<00:13:10.560> large<00:13:11.000> servers<00:13:12.000> or<00:13:12.600> with<00:13:13.019> fpgas<00:13:13.620> or 00:13:13.850 --> 00:13:13.860 align:start position:0% like very large servers or with fpgas or 00:13:13.860 --> 00:13:15.949 align:start position:0% like very large servers or with fpgas or gpus<00:13:14.399> you<00:13:14.760> know<00:13:14.880> there's<00:13:15.000> some<00:13:15.240> like<00:13:15.420> debate 00:13:15.949 --> 00:13:15.959 align:start position:0% gpus you know there's some like debate 00:13:15.959 --> 00:13:17.389 align:start position:0% gpus you know there's some like debate around<00:13:16.139> which<00:13:16.380> of<00:13:16.560> those<00:13:16.620> two<00:13:16.740> things<00:13:16.920> wins<00:13:17.279> of 00:13:17.389 --> 00:13:17.399 align:start position:0% around which of those two things wins of 00:13:17.399 --> 00:13:18.410 align:start position:0% around which of those two things wins of course 00:13:18.410 --> 00:13:18.420 align:start position:0% course 00:13:18.420 --> 00:13:21.350 align:start position:0% course um<00:13:18.839> but<00:13:19.560> if<00:13:20.040> users<00:13:20.519> are<00:13:20.700> making<00:13:20.820> proofs<00:13:21.180> to 00:13:21.350 --> 00:13:21.360 align:start position:0% um but if users are making proofs to 00:13:21.360 --> 00:13:22.970 align:start position:0% um but if users are making proofs to other<00:13:21.480> or<00:13:21.720> humans<00:13:22.079> are<00:13:22.200> making<00:13:22.320> you<00:13:22.500> proofs<00:13:22.860> to 00:13:22.970 --> 00:13:22.980 align:start position:0% other or humans are making you proofs to 00:13:22.980 --> 00:13:25.430 align:start position:0% other or humans are making you proofs to other<00:13:23.100> humans<00:13:23.820> uh<00:13:24.420> we<00:13:24.600> perhaps<00:13:24.899> can't<00:13:25.139> quite 00:13:25.430 --> 00:13:25.440 align:start position:0% other humans uh we perhaps can't quite 00:13:25.440 --> 00:13:26.569 align:start position:0% other humans uh we perhaps can't quite make<00:13:25.560> that<00:13:25.740> assumption<00:13:26.040> so<00:13:26.160> we<00:13:26.279> spent<00:13:26.399> a<00:13:26.519> lot 00:13:26.569 --> 00:13:26.579 align:start position:0% make that assumption so we spent a lot 00:13:26.579 --> 00:13:27.590 align:start position:0% make that assumption so we spent a lot of<00:13:26.639> time<00:13:26.760> thinking<00:13:27.000> about<00:13:27.060> performance<00:13:27.480> and 00:13:27.590 --> 00:13:27.600 align:start position:0% of time thinking about performance and 00:13:27.600 --> 00:13:29.629 align:start position:0% of time thinking about performance and research<00:13:27.899> in<00:13:28.079> certain<00:13:28.200> environments 00:13:29.629 --> 00:13:29.639 align:start position:0% research in certain environments 00:13:29.639 --> 00:13:31.129 align:start position:0% research in certain environments um<00:13:29.760> I 00:13:31.129 --> 00:13:31.139 align:start position:0% um I 00:13:31.139 --> 00:13:32.990 align:start position:0% um I so<00:13:31.560> specific<00:13:31.860> like<00:13:32.160> you<00:13:32.459> know<00:13:32.579> the<00:13:32.700> specific 00:13:32.990 --> 00:13:33.000 align:start position:0% so specific like you know the specific 00:13:33.000 --> 00:13:34.970 align:start position:0% so specific like you know the specific example<00:13:33.360> that<00:13:33.600> I<00:13:33.720> gave<00:13:33.959> earlier<00:13:34.260> earlier<00:13:34.620> with 00:13:34.970 --> 00:13:34.980 align:start position:0% example that I gave earlier earlier with 00:13:34.980 --> 00:13:38.090 align:start position:0% example that I gave earlier earlier with ayush<00:13:35.100> uh<00:13:35.700> we<00:13:35.760> need<00:13:35.880> to<00:13:36.000> think<00:13:36.120> a<00:13:36.300> lot<00:13:36.360> about 00:13:38.090 --> 00:13:38.100 align:start position:0% ayush uh we need to think a lot about 00:13:38.100 --> 00:13:40.490 align:start position:0% ayush uh we need to think a lot about um<00:13:38.420> non-private<00:13:39.420> key<00:13:39.600> nullifiers<00:13:40.320> like 00:13:40.490 --> 00:13:40.500 align:start position:0% um non-private key nullifiers like 00:13:40.500 --> 00:13:44.090 align:start position:0% um non-private key nullifiers like non-private<00:13:41.160> key<00:13:41.279> uniqueness<00:13:41.880> of<00:13:42.839> identity 00:13:44.090 --> 00:13:44.100 align:start position:0% non-private key uniqueness of identity 00:13:44.100 --> 00:13:46.129 align:start position:0% non-private key uniqueness of identity um<00:13:44.220> because<00:13:44.639> we<00:13:45.000> don't<00:13:45.120> want<00:13:45.300> to<00:13:45.420> have<00:13:45.660> to<00:13:45.779> deal 00:13:46.129 --> 00:13:46.139 align:start position:0% um because we don't want to have to deal 00:13:46.139 --> 00:13:47.509 align:start position:0% um because we don't want to have to deal with<00:13:46.380> private<00:13:46.680> key<00:13:46.800> we<00:13:47.040> don't<00:13:47.160> want<00:13:47.279> to<00:13:47.399> have 00:13:47.509 --> 00:13:47.519 align:start position:0% with private key we don't want to have 00:13:47.519 --> 00:13:49.850 align:start position:0% with private key we don't want to have to<00:13:47.760> create<00:13:48.420> like<00:13:48.839> an<00:13:49.079> environment<00:13:49.440> or<00:13:49.740> a 00:13:49.850 --> 00:13:49.860 align:start position:0% to create like an environment or a 00:13:49.860 --> 00:13:52.550 align:start position:0% to create like an environment or a platform<00:13:50.220> or<00:13:50.639> anything<00:13:51.000> where<00:13:51.540> we<00:13:52.019> we<00:13:52.200> assume 00:13:52.550 --> 00:13:52.560 align:start position:0% platform or anything where we we assume 00:13:52.560 --> 00:13:54.590 align:start position:0% platform or anything where we we assume private<00:13:52.920> key<00:13:53.040> is<00:13:53.220> passed<00:13:53.519> for<00:13:53.639> map<00:13:53.820> to<00:13:54.000> app<00:13:54.180> and 00:13:54.590 --> 00:13:54.600 align:start position:0% private key is passed for map to app and 00:13:54.600 --> 00:13:55.550 align:start position:0% private key is passed for map to app and then<00:13:54.660> we<00:13:54.779> also<00:13:55.019> spend<00:13:55.139> a<00:13:55.260> lot<00:13:55.380> of<00:13:55.440> time 00:13:55.550 --> 00:13:55.560 align:start position:0% then we also spend a lot of time 00:13:55.560 --> 00:13:57.350 align:start position:0% then we also spend a lot of time thinking<00:13:55.860> about 00:13:57.350 --> 00:13:57.360 align:start position:0% thinking about 00:13:57.360 --> 00:13:58.069 align:start position:0% thinking about um 00:13:58.069 --> 00:13:58.079 align:start position:0% um 00:13:58.079 --> 00:14:00.530 align:start position:0% um representing<00:13:58.980> more<00:13:59.279> crypto<00:13:59.639> systems<00:14:00.120> where 00:14:00.530 --> 00:14:00.540 align:start position:0% representing more crypto systems where 00:14:00.540 --> 00:14:02.449 align:start position:0% representing more crypto systems where identity<00:14:01.260> matters 00:14:02.449 --> 00:14:02.459 align:start position:0% identity matters 00:14:02.459 --> 00:14:04.850 align:start position:0% identity matters um<00:14:02.579> in<00:14:02.880> snarks<00:14:03.420> so<00:14:03.720> you<00:14:04.019> know<00:14:04.079> ethereum<00:14:04.620> we<00:14:04.740> all 00:14:04.850 --> 00:14:04.860 align:start position:0% um in snarks so you know ethereum we all 00:14:04.860 --> 00:14:06.470 align:start position:0% um in snarks so you know ethereum we all interact<00:14:05.100> with<00:14:05.279> ethereum<00:14:05.760> that's<00:14:06.240> quite 00:14:06.470 --> 00:14:06.480 align:start position:0% interact with ethereum that's quite 00:14:06.480 --> 00:14:07.970 align:start position:0% interact with ethereum that's quite obvious<00:14:06.720> there's<00:14:06.779> a<00:14:06.899> lot<00:14:07.019> of<00:14:07.079> interesting 00:14:07.970 --> 00:14:07.980 align:start position:0% obvious there's a lot of interesting 00:14:07.980 --> 00:14:09.889 align:start position:0% obvious there's a lot of interesting things<00:14:08.399> you<00:14:08.519> can<00:14:08.639> say<00:14:08.820> about<00:14:09.060> ethereum<00:14:09.660> stuff 00:14:09.889 --> 00:14:09.899 align:start position:0% things you can say about ethereum stuff 00:14:09.899 --> 00:14:12.769 align:start position:0% things you can say about ethereum stuff but<00:14:10.200> there<00:14:10.620> are<00:14:10.800> other<00:14:11.000> like<00:14:12.000> networks<00:14:12.480> in<00:14:12.600> the 00:14:12.769 --> 00:14:12.779 align:start position:0% but there are other like networks in the 00:14:12.779 --> 00:14:15.350 align:start position:0% but there are other like networks in the world<00:14:12.899> where<00:14:13.440> uh<00:14:14.339> you<00:14:14.639> know<00:14:14.700> cryptographic 00:14:15.350 --> 00:14:15.360 align:start position:0% world where uh you know cryptographic 00:14:15.360 --> 00:14:17.389 align:start position:0% world where uh you know cryptographic signatures<00:14:15.779> are<00:14:15.899> made<00:14:16.079> like<00:14:16.260> like<00:14:16.740> email<00:14:17.040> mail 00:14:17.389 --> 00:14:17.399 align:start position:0% signatures are made like like email mail 00:14:17.399 --> 00:14:19.490 align:start position:0% signatures are made like like email mail service<00:14:17.700> like<00:14:17.940> I<00:14:18.120> mentioned<00:14:18.300> earlier<00:14:18.600> so 00:14:19.490 --> 00:14:19.500 align:start position:0% service like I mentioned earlier so 00:14:19.500 --> 00:14:20.750 align:start position:0% service like I mentioned earlier so um<00:14:19.560> we're<00:14:19.740> constantly<00:14:20.100> looking<00:14:20.220> around<00:14:20.459> to 00:14:20.750 --> 00:14:20.760 align:start position:0% um we're constantly looking around to 00:14:20.760 --> 00:14:23.329 align:start position:0% um we're constantly looking around to understand<00:14:21.079> where<00:14:22.079> new<00:14:22.380> networks<00:14:23.220> are 00:14:23.329 --> 00:14:23.339 align:start position:0% understand where new networks are 00:14:23.339 --> 00:14:24.829 align:start position:0% understand where new networks are forming<00:14:23.639> and<00:14:23.820> how<00:14:24.000> to<00:14:24.060> like<00:14:24.240> put<00:14:24.480> those 00:14:24.829 --> 00:14:24.839 align:start position:0% forming and how to like put those 00:14:24.839 --> 00:14:27.710 align:start position:0% forming and how to like put those operations<00:14:25.560> inside<00:14:25.860> snarks<00:14:26.880> so<00:14:27.240> lock<00:14:27.480> swans 00:14:27.710 --> 00:14:27.720 align:start position:0% operations inside snarks so lock swans 00:14:27.720 --> 00:14:29.150 align:start position:0% operations inside snarks so lock swans talk<00:14:27.899> a<00:14:28.079> bit<00:14:28.079> about<00:14:28.320> some<00:14:28.620> of<00:14:28.740> the<00:14:28.800> challenges 00:14:29.150 --> 00:14:29.160 align:start position:0% talk a bit about some of the challenges 00:14:29.160 --> 00:14:31.370 align:start position:0% talk a bit about some of the challenges ahead<00:14:29.579> for<00:14:29.820> privacy<00:14:30.240> and<00:14:30.899> a<00:14:30.959> lot<00:14:31.079> of<00:14:31.139> that<00:14:31.260> was 00:14:31.370 --> 00:14:31.380 align:start position:0% ahead for privacy and a lot of that was 00:14:31.380 --> 00:14:33.949 align:start position:0% ahead for privacy and a lot of that was dominated<00:14:31.740> by<00:14:32.040> finding<00:14:32.459> new<00:14:33.060> ways<00:14:33.360> to<00:14:33.600> improve 00:14:33.949 --> 00:14:33.959 align:start position:0% dominated by finding new ways to improve 00:14:33.959 --> 00:14:35.629 align:start position:0% dominated by finding new ways to improve the<00:14:34.200> user<00:14:34.500> experience<00:14:34.860> and<00:14:35.519> find 00:14:35.629 --> 00:14:35.639 align:start position:0% the user experience and find 00:14:35.639 --> 00:14:38.269 align:start position:0% the user experience and find applications<00:14:36.240> I<00:14:37.139> think<00:14:37.260> on<00:14:37.500> the<00:14:37.620> sickness 00:14:38.269 --> 00:14:38.279 align:start position:0% applications I think on the sickness 00:14:38.279 --> 00:14:41.629 align:start position:0% applications I think on the sickness side<00:14:38.519> uh<00:14:39.360> the<00:14:39.540> split<00:14:39.839> is<00:14:40.019> the<00:14:40.560> other<00:14:40.680> way<00:14:40.920> where 00:14:41.629 --> 00:14:41.639 align:start position:0% side uh the split is the other way where 00:14:41.639 --> 00:14:43.370 align:start position:0% side uh the split is the other way where what<00:14:42.060> you<00:14:42.240> want<00:14:42.420> to<00:14:42.540> build<00:14:42.660> is<00:14:42.959> somewhat<00:14:43.260> more 00:14:43.370 --> 00:14:43.380 align:start position:0% what you want to build is somewhat more 00:14:43.380 --> 00:14:45.470 align:start position:0% what you want to build is somewhat more clear<00:14:43.620> but<00:14:44.339> you<00:14:44.519> need<00:14:44.639> to<00:14:44.820> have<00:14:45.000> good<00:14:45.300> enough 00:14:45.470 --> 00:14:45.480 align:start position:0% clear but you need to have good enough 00:14:45.480 --> 00:14:47.870 align:start position:0% clear but you need to have good enough performance<00:14:45.959> to<00:14:46.380> actually<00:14:46.560> build<00:14:46.860> it<00:14:47.100> so<00:14:47.699> in 00:14:47.870 --> 00:14:47.880 align:start position:0% performance to actually build it so in 00:14:47.880 --> 00:14:49.910 align:start position:0% performance to actually build it so in that<00:14:48.000> sense<00:14:48.240> what<00:14:48.720> what<00:14:49.139> I<00:14:49.500> view<00:14:49.680> the 00:14:49.910 --> 00:14:49.920 align:start position:0% that sense what what I view the 00:14:49.920 --> 00:14:52.610 align:start position:0% that sense what what I view the challenge<00:14:50.160> ahead<00:14:50.579> as<00:14:51.060> really<00:14:51.300> optimizing<00:14:52.019> the 00:14:52.610 --> 00:14:52.620 align:start position:0% challenge ahead as really optimizing the 00:14:52.620 --> 00:14:54.530 align:start position:0% challenge ahead as really optimizing the performance<00:14:52.920> of<00:14:53.160> our<00:14:53.279> proving<00:14:53.639> systems<00:14:54.060> and 00:14:54.530 --> 00:14:54.540 align:start position:0% performance of our proving systems and 00:14:54.540 --> 00:14:56.030 align:start position:0% performance of our proving systems and our<00:14:54.660> architectures 00:14:56.030 --> 00:14:56.040 align:start position:0% our architectures 00:14:56.040 --> 00:14:59.389 align:start position:0% our architectures so<00:14:56.760> One<00:14:57.240> Direction<00:14:57.480> is<00:14:58.019> to<00:14:58.260> really<00:14:58.440> weaponize 00:14:59.389 --> 00:14:59.399 align:start position:0% so One Direction is to really weaponize 00:14:59.399 --> 00:15:01.430 align:start position:0% so One Direction is to really weaponize this<00:15:00.060> operation<00:15:00.360> of<00:15:00.600> aggregation<00:15:01.079> and 00:15:01.430 --> 00:15:01.440 align:start position:0% this operation of aggregation and 00:15:01.440 --> 00:15:03.470 align:start position:0% this operation of aggregation and recursion<00:15:01.980> that<00:15:02.220> I<00:15:02.339> mentioned<00:15:02.639> earlier 00:15:03.470 --> 00:15:03.480 align:start position:0% recursion that I mentioned earlier 00:15:03.480 --> 00:15:05.389 align:start position:0% recursion that I mentioned earlier and<00:15:03.959> the<00:15:04.079> reason<00:15:04.199> here<00:15:04.500> is<00:15:04.680> that<00:15:04.860> if<00:15:05.100> you<00:15:05.220> want 00:15:05.389 --> 00:15:05.399 align:start position:0% and the reason here is that if you want 00:15:05.399 --> 00:15:07.310 align:start position:0% and the reason here is that if you want a<00:15:05.699> very<00:15:05.820> rich<00:15:06.120> infrastructure<00:15:06.839> application 00:15:07.310 --> 00:15:07.320 align:start position:0% a very rich infrastructure application 00:15:07.320 --> 00:15:09.530 align:start position:0% a very rich infrastructure application you<00:15:08.040> need<00:15:08.160> a<00:15:08.339> proof<00:15:08.639> for<00:15:08.820> a<00:15:09.000> much<00:15:09.180> larger 00:15:09.530 --> 00:15:09.540 align:start position:0% you need a proof for a much larger 00:15:09.540 --> 00:15:11.389 align:start position:0% you need a proof for a much larger circuit<00:15:09.899> than<00:15:10.320> is<00:15:10.500> even<00:15:10.680> possible<00:15:11.040> than<00:15:11.279> the 00:15:11.389 --> 00:15:11.399 align:start position:0% circuit than is even possible than the 00:15:11.399 --> 00:15:13.910 align:start position:0% circuit than is even possible than the large<00:15:11.579> in<00:15:12.060> the<00:15:12.180> largest<00:15:12.420> circuits<00:15:12.839> today 00:15:13.910 --> 00:15:13.920 align:start position:0% large in the largest circuits today 00:15:13.920 --> 00:15:15.530 align:start position:0% large in the largest circuits today and<00:15:14.279> so<00:15:14.399> there<00:15:14.579> are<00:15:14.639> a<00:15:14.699> couple<00:15:14.820> ideas<00:15:15.060> here 00:15:15.530 --> 00:15:15.540 align:start position:0% and so there are a couple ideas here 00:15:15.540 --> 00:15:17.569 align:start position:0% and so there are a couple ideas here that<00:15:16.079> are<00:15:16.260> only<00:15:16.380> beginning<00:15:16.620> to<00:15:16.920> be<00:15:17.040> exploited 00:15:17.569 --> 00:15:17.579 align:start position:0% that are only beginning to be exploited 00:15:17.579 --> 00:15:19.550 align:start position:0% that are only beginning to be exploited by<00:15:18.120> projects<00:15:18.600> right<00:15:18.839> now 00:15:19.550 --> 00:15:19.560 align:start position:0% by projects right now 00:15:19.560 --> 00:15:21.710 align:start position:0% by projects right now one<00:15:20.220> is<00:15:20.399> to<00:15:20.639> maximize<00:15:21.060> what's<00:15:21.360> called<00:15:21.540> a 00:15:21.710 --> 00:15:21.720 align:start position:0% one is to maximize what's called a 00:15:21.720 --> 00:15:23.689 align:start position:0% one is to maximize what's called a prover<00:15:21.959> verifier<00:15:22.500> trade-off<00:15:22.980> there's<00:15:23.459> a 00:15:23.689 --> 00:15:23.699 align:start position:0% prover verifier trade-off there's a 00:15:23.699 --> 00:15:25.670 align:start position:0% prover verifier trade-off there's a fundamental<00:15:24.120> trade-off<00:15:24.480> between<00:15:24.959> the 00:15:25.670 --> 00:15:25.680 align:start position:0% fundamental trade-off between the 00:15:25.680 --> 00:15:28.490 align:start position:0% fundamental trade-off between the proving<00:15:26.100> time<00:15:26.480> and<00:15:27.480> the<00:15:27.779> complexity<00:15:28.199> of 00:15:28.490 --> 00:15:28.500 align:start position:0% proving time and the complexity of 00:15:28.500 --> 00:15:30.769 align:start position:0% proving time and the complexity of verifying<00:15:29.040> a<00:15:29.160> proof<00:15:29.459> If<00:15:30.000> you<00:15:30.120> feed<00:15:30.300> in<00:15:30.540> more 00:15:30.769 --> 00:15:30.779 align:start position:0% verifying a proof If you feed in more 00:15:30.779 --> 00:15:33.290 align:start position:0% verifying a proof If you feed in more compute<00:15:31.260> you<00:15:31.740> can<00:15:31.800> get<00:15:32.040> an<00:15:32.279> easier<00:15:32.639> to<00:15:32.820> verify 00:15:33.290 --> 00:15:33.300 align:start position:0% compute you can get an easier to verify 00:15:33.300 --> 00:15:35.030 align:start position:0% compute you can get an easier to verify proof 00:15:35.030 --> 00:15:35.040 align:start position:0% proof 00:15:35.040 --> 00:15:37.310 align:start position:0% proof um so<00:15:35.339> we<00:15:35.760> can<00:15:35.880> do<00:15:36.060> things<00:15:36.360> like<00:15:37.079> starting 00:15:37.310 --> 00:15:37.320 align:start position:0% um so we can do things like starting 00:15:37.320 --> 00:15:40.730 align:start position:0% um so we can do things like starting with<00:15:37.740> a<00:15:37.920> very<00:15:38.040> fast<00:15:38.279> to<00:15:38.639> prove<00:15:39.060> uh<00:15:39.779> system<00:15:40.079> and 00:15:40.730 --> 00:15:40.740 align:start position:0% with a very fast to prove uh system and 00:15:40.740 --> 00:15:42.949 align:start position:0% with a very fast to prove uh system and then<00:15:40.860> wrapping<00:15:41.339> it<00:15:41.519> in<00:15:41.940> an<00:15:42.120> aggregation<00:15:42.540> layer 00:15:42.949 --> 00:15:42.959 align:start position:0% then wrapping it in an aggregation layer 00:15:42.959 --> 00:15:46.189 align:start position:0% then wrapping it in an aggregation layer with<00:15:43.680> which<00:15:44.279> transforms<00:15:45.060> it<00:15:45.240> to<00:15:45.660> a<00:15:45.779> cheaper<00:15:46.079> to 00:15:46.189 --> 00:15:46.199 align:start position:0% with which transforms it to a cheaper to 00:15:46.199 --> 00:15:48.350 align:start position:0% with which transforms it to a cheaper to verify<00:15:46.620> system<00:15:46.860> one<00:15:47.699> form<00:15:47.880> of<00:15:48.060> that<00:15:48.180> is 00:15:48.350 --> 00:15:48.360 align:start position:0% verify system one form of that is 00:15:48.360 --> 00:15:50.389 align:start position:0% verify system one form of that is already<00:15:48.540> in<00:15:48.779> use<00:15:48.959> with<00:15:49.500> basic<00:15:49.920> aggregation 00:15:50.389 --> 00:15:50.399 align:start position:0% already in use with basic aggregation 00:15:50.399 --> 00:15:53.030 align:start position:0% already in use with basic aggregation but<00:15:51.000> we<00:15:51.180> can<00:15:51.300> push<00:15:51.420> it<00:15:51.600> much<00:15:51.839> further<00:15:52.199> using 00:15:53.030 --> 00:15:53.040 align:start position:0% but we can push it much further using 00:15:53.040 --> 00:15:55.069 align:start position:0% but we can push it much further using multiple<00:15:53.519> aggregation<00:15:54.000> layers 00:15:55.069 --> 00:15:55.079 align:start position:0% multiple aggregation layers 00:15:55.079 --> 00:15:57.110 align:start position:0% multiple aggregation layers and<00:15:55.500> the<00:15:55.680> things<00:15:55.800> here<00:15:56.100> to<00:15:56.399> really<00:15:56.519> optimize 00:15:57.110 --> 00:15:57.120 align:start position:0% and the things here to really optimize 00:15:57.120 --> 00:15:59.689 align:start position:0% and the things here to really optimize are<00:15:57.720> non-native<00:15:58.139> arithmetic<00:15:58.800> and<00:15:59.220> elliptic 00:15:59.689 --> 00:15:59.699 align:start position:0% are non-native arithmetic and elliptic 00:15:59.699 --> 00:16:01.850 align:start position:0% are non-native arithmetic and elliptic curve<00:15:59.940> operations<00:16:00.360> for<00:16:00.959> these<00:16:01.139> snark-based 00:16:01.850 --> 00:16:01.860 align:start position:0% curve operations for these snark-based 00:16:01.860 --> 00:16:04.550 align:start position:0% curve operations for these snark-based systems<00:16:02.160> and<00:16:02.459> a<00:16:02.699> second<00:16:02.880> direction<00:16:03.320> is<00:16:04.320> that 00:16:04.550 --> 00:16:04.560 align:start position:0% systems and a second direction is that 00:16:04.560 --> 00:16:06.530 align:start position:0% systems and a second direction is that even<00:16:04.860> if<00:16:05.160> we<00:16:05.279> really<00:16:05.459> optimize<00:16:05.940> aggregation 00:16:06.530 --> 00:16:06.540 align:start position:0% even if we really optimize aggregation 00:16:06.540 --> 00:16:08.449 align:start position:0% even if we really optimize aggregation it's<00:16:07.079> likely<00:16:07.380> that<00:16:07.740> the<00:16:07.980> most<00:16:08.100> interesting 00:16:08.449 --> 00:16:08.459 align:start position:0% it's likely that the most interesting 00:16:08.459 --> 00:16:10.490 align:start position:0% it's likely that the most interesting operation<00:16:08.880> statements<00:16:09.600> to<00:16:09.720> make<00:16:09.839> are<00:16:10.320> going 00:16:10.490 --> 00:16:10.500 align:start position:0% operation statements to make are going 00:16:10.500 --> 00:16:12.470 align:start position:0% operation statements to make are going to<00:16:10.620> require<00:16:10.740> multiple<00:16:11.519> circuits<00:16:12.000> to<00:16:12.180> prove 00:16:12.470 --> 00:16:12.480 align:start position:0% to require multiple circuits to prove 00:16:12.480 --> 00:16:15.410 align:start position:0% to require multiple circuits to prove and<00:16:13.380> so<00:16:13.500> in<00:16:13.620> this<00:16:13.800> schema<00:16:14.220> you<00:16:14.760> divide<00:16:15.000> up<00:16:15.180> a 00:16:15.410 --> 00:16:15.420 align:start position:0% and so in this schema you divide up a 00:16:15.420 --> 00:16:18.230 align:start position:0% and so in this schema you divide up a large<00:16:15.540> computation<00:16:16.139> with<00:16:17.100> into<00:16:17.820> multiple 00:16:18.230 --> 00:16:18.240 align:start position:0% large computation with into multiple 00:16:18.240 --> 00:16:21.290 align:start position:0% large computation with into multiple pieces<00:16:18.660> and<00:16:19.260> then<00:16:19.320> you<00:16:19.560> verify<00:16:19.980> each<00:16:20.399> piece<00:16:20.760> in 00:16:21.290 --> 00:16:21.300 align:start position:0% pieces and then you verify each piece in 00:16:21.300 --> 00:16:23.689 align:start position:0% pieces and then you verify each piece in a<00:16:21.420> snark<00:16:21.660> and<00:16:22.199> then<00:16:22.320> you<00:16:22.500> verify<00:16:22.920> those<00:16:23.160> snarks 00:16:23.689 --> 00:16:23.699 align:start position:0% a snark and then you verify those snarks 00:16:23.699 --> 00:16:25.009 align:start position:0% a snark and then you verify those snarks recursively 00:16:25.009 --> 00:16:25.019 align:start position:0% recursively 00:16:25.019 --> 00:16:28.310 align:start position:0% recursively so<00:16:25.560> with<00:16:25.860> the<00:16:25.980> ZK<00:16:26.279> VM<00:16:26.699> and<00:16:27.240> other<00:16:27.420> ZK<00:16:27.839> roll-up 00:16:28.310 --> 00:16:28.320 align:start position:0% so with the ZK VM and other ZK roll-up 00:16:28.320 --> 00:16:30.949 align:start position:0% so with the ZK VM and other ZK roll-up VMS<00:16:28.920> we're<00:16:29.279> seeing<00:16:29.519> the<00:16:29.760> beginnings<00:16:30.180> of 00:16:30.949 --> 00:16:30.959 align:start position:0% VMS we're seeing the beginnings of 00:16:30.959 --> 00:16:33.110 align:start position:0% VMS we're seeing the beginnings of building<00:16:31.260> virtual<00:16:31.800> machines<00:16:32.220> in<00:16:32.820> this<00:16:33.000> way 00:16:33.110 --> 00:16:33.120 align:start position:0% building virtual machines in this way 00:16:33.120 --> 00:16:35.930 align:start position:0% building virtual machines in this way and<00:16:33.779> I<00:16:33.959> think<00:16:34.079> that<00:16:34.440> VMS<00:16:35.399> for<00:16:35.579> transaction 00:16:35.930 --> 00:16:35.940 align:start position:0% and I think that VMS for transaction 00:16:35.940 --> 00:16:38.030 align:start position:0% and I think that VMS for transaction execution<00:16:36.600> are<00:16:37.139> just<00:16:37.320> the<00:16:37.500> beginning<00:16:37.620> of<00:16:37.920> this 00:16:38.030 --> 00:16:38.040 align:start position:0% execution are just the beginning of this 00:16:38.040 --> 00:16:41.269 align:start position:0% execution are just the beginning of this trend<00:16:38.339> in<00:16:39.180> a<00:16:39.300> separate<00:16:39.540> Direction<00:16:40.220> in<00:16:41.220> the 00:16:41.269 --> 00:16:41.279 align:start position:0% trend in a separate Direction in the 00:16:41.279 --> 00:16:43.189 align:start position:0% trend in a separate Direction in the last<00:16:41.399> five<00:16:41.639> years<00:16:41.880> a<00:16:42.420> lot<00:16:42.540> of<00:16:42.660> the<00:16:42.720> progress<00:16:43.019> in 00:16:43.189 --> 00:16:43.199 align:start position:0% last five years a lot of the progress in 00:16:43.199 --> 00:16:46.310 align:start position:0% last five years a lot of the progress in ZK<00:16:43.560> has<00:16:44.160> been<00:16:44.279> driven<00:16:44.639> by<00:16:44.940> the<00:16:45.120> emergence<00:16:45.600> of 00:16:46.310 --> 00:16:46.320 align:start position:0% ZK has been driven by the emergence of 00:16:46.320 --> 00:16:48.889 align:start position:0% ZK has been driven by the emergence of many<00:16:46.560> new<00:16:46.920> types<00:16:47.399> of<00:16:47.459> proof<00:16:47.940> systems<00:16:48.420> that 00:16:48.889 --> 00:16:48.899 align:start position:0% many new types of proof systems that 00:16:48.899 --> 00:16:50.810 align:start position:0% many new types of proof systems that really<00:16:49.139> pushed<00:16:49.440> the<00:16:49.560> envelope<00:16:49.980> on<00:16:50.459> what<00:16:50.639> we 00:16:50.810 --> 00:16:50.820 align:start position:0% really pushed the envelope on what we 00:16:50.820 --> 00:16:54.170 align:start position:0% really pushed the envelope on what we can<00:16:50.940> do<00:16:51.060> inside<00:16:51.420> a<00:16:51.720> ZK<00:16:52.019> circuit<00:16:52.920> so<00:16:53.459> Justin<00:16:53.699> as 00:16:54.170 --> 00:16:54.180 align:start position:0% can do inside a ZK circuit so Justin as 00:16:54.180 --> 00:16:57.829 align:start position:0% can do inside a ZK circuit so Justin as recently<00:16:54.480> as<00:16:54.600> 2016<00:16:55.220> really<00:16:56.220> the<00:16:56.759> most<00:16:57.480> viable 00:16:57.829 --> 00:16:57.839 align:start position:0% recently as 2016 really the most viable 00:16:57.839 --> 00:17:00.530 align:start position:0% recently as 2016 really the most viable ZK<00:16:58.500> proof<00:16:58.920> system<00:16:59.100> we<00:16:59.339> had<00:16:59.459> access<00:16:59.639> to<00:16:59.940> was 00:17:00.530 --> 00:17:00.540 align:start position:0% ZK proof system we had access to was 00:17:00.540 --> 00:17:03.530 align:start position:0% ZK proof system we had access to was Groth<00:17:00.959> 16<00:17:01.279> but<00:17:02.279> since<00:17:02.519> then<00:17:02.699> we've<00:17:03.060> added<00:17:03.360> many 00:17:03.530 --> 00:17:03.540 align:start position:0% Groth 16 but since then we've added many 00:17:03.540 --> 00:17:06.049 align:start position:0% Groth 16 but since then we've added many capabilities<00:17:04.020> like<00:17:04.439> custom<00:17:04.740> Gates<00:17:05.220> lookup 00:17:06.049 --> 00:17:06.059 align:start position:0% capabilities like custom Gates lookup 00:17:06.059 --> 00:17:07.850 align:start position:0% capabilities like custom Gates lookup arguments<00:17:06.600> and<00:17:07.020> we've<00:17:07.140> been<00:17:07.260> able<00:17:07.439> to<00:17:07.559> remove 00:17:07.850 --> 00:17:07.860 align:start position:0% arguments and we've been able to remove 00:17:07.860 --> 00:17:10.429 align:start position:0% arguments and we've been able to remove some<00:17:08.640> aspects<00:17:09.000> of<00:17:09.120> The<00:17:09.240> Trusted<00:17:09.600> setup<00:17:09.959> in 00:17:10.429 --> 00:17:10.439 align:start position:0% some aspects of The Trusted setup in 00:17:10.439 --> 00:17:13.490 align:start position:0% some aspects of The Trusted setup in newer<00:17:10.799> systems<00:17:11.160> like<00:17:11.400> Planck<00:17:12.059> Halo<00:17:12.720> 2<00:17:12.900> and<00:17:13.260> in 00:17:13.490 --> 00:17:13.500 align:start position:0% newer systems like Planck Halo 2 and in 00:17:13.500 --> 00:17:15.650 align:start position:0% newer systems like Planck Halo 2 and in Starks 00:17:15.650 --> 00:17:15.660 align:start position:0% Starks 00:17:15.660 --> 00:17:17.329 align:start position:0% Starks um in<00:17:15.959> the<00:17:16.079> landscape<00:17:16.380> today<00:17:16.620> there<00:17:17.220> are 00:17:17.329 --> 00:17:17.339 align:start position:0% um in the landscape today there are 00:17:17.339 --> 00:17:18.890 align:start position:0% um in the landscape today there are actually<00:17:17.459> a<00:17:17.939> number<00:17:18.059> of<00:17:18.179> New<00:17:18.480> Primitives 00:17:18.890 --> 00:17:18.900 align:start position:0% actually a number of New Primitives 00:17:18.900 --> 00:17:22.069 align:start position:0% actually a number of New Primitives emerging<00:17:19.439> which<00:17:20.280> may<00:17:20.579> be<00:17:20.819> equally<00:17:21.480> or<00:17:21.839> more 00:17:22.069 --> 00:17:22.079 align:start position:0% emerging which may be equally or more 00:17:22.079 --> 00:17:25.370 align:start position:0% emerging which may be equally or more exciting<00:17:22.919> so<00:17:23.579> systems<00:17:24.000> like<00:17:24.120> Nova<00:17:24.720> allow<00:17:25.199> for 00:17:25.370 --> 00:17:25.380 align:start position:0% exciting so systems like Nova allow for 00:17:25.380 --> 00:17:28.010 align:start position:0% exciting so systems like Nova allow for much<00:17:25.620> more<00:17:25.799> efficient<00:17:26.160> accumulation<00:17:27.020> some 00:17:28.010 --> 00:17:28.020 align:start position:0% much more efficient accumulation some 00:17:28.020 --> 00:17:29.990 align:start position:0% much more efficient accumulation some check<00:17:28.199> based<00:17:28.620> systems<00:17:28.860> like<00:17:29.040> gkr<00:17:29.640> or 00:17:29.990 --> 00:17:30.000 align:start position:0% check based systems like gkr or 00:17:30.000 --> 00:17:34.430 align:start position:0% check based systems like gkr or hyperplunk<00:17:30.540> allow<00:17:31.200> for<00:17:31.440> fast<00:17:32.220> and<00:17:32.760> faster<00:17:33.440> but 00:17:34.430 --> 00:17:34.440 align:start position:0% hyperplunk allow for fast and faster but 00:17:34.440 --> 00:17:36.830 align:start position:0% hyperplunk allow for fast and faster but larger<00:17:34.860> proofs<00:17:35.400> which<00:17:35.880> could<00:17:36.059> get<00:17:36.299> then<00:17:36.539> be 00:17:36.830 --> 00:17:36.840 align:start position:0% larger proofs which could get then be 00:17:36.840 --> 00:17:39.049 align:start position:0% larger proofs which could get then be recursively<00:17:37.500> aggregated<00:17:37.980> in<00:17:38.580> other<00:17:38.760> proof 00:17:39.049 --> 00:17:39.059 align:start position:0% recursively aggregated in other proof 00:17:39.059 --> 00:17:40.549 align:start position:0% recursively aggregated in other proof systems<00:17:39.419> that<00:17:39.600> we<00:17:39.780> already<00:17:39.900> control<00:17:40.200> very 00:17:40.549 --> 00:17:40.559 align:start position:0% systems that we already control very 00:17:40.559 --> 00:17:41.510 align:start position:0% systems that we already control very well 00:17:41.510 --> 00:17:41.520 align:start position:0% well 00:17:41.520 --> 00:17:43.430 align:start position:0% well and<00:17:42.120> finally<00:17:42.360> there's<00:17:42.720> the<00:17:42.840> potential<00:17:43.140> for 00:17:43.430 --> 00:17:43.440 align:start position:0% and finally there's the potential for 00:17:43.440 --> 00:17:45.350 align:start position:0% and finally there's the potential for much<00:17:43.620> more<00:17:43.740> efficient<00:17:44.039> lookups<00:17:44.640> and<00:17:45.120> new 00:17:45.350 --> 00:17:45.360 align:start position:0% much more efficient lookups and new 00:17:45.360 --> 00:17:47.690 align:start position:0% much more efficient lookups and new systems<00:17:45.660> such<00:17:45.840> as<00:17:45.960> caulk<00:17:46.440> and<00:17:47.160> so<00:17:47.340> each<00:17:47.520> of 00:17:47.690 --> 00:17:47.700 align:start position:0% systems such as caulk and so each of 00:17:47.700 --> 00:17:50.090 align:start position:0% systems such as caulk and so each of these<00:17:48.000> represent<00:17:48.600> a<00:17:48.900> pretty<00:17:49.020> big<00:17:49.200> shift<00:17:49.620> in 00:17:50.090 --> 00:17:50.100 align:start position:0% these represent a pretty big shift in 00:17:50.100 --> 00:17:52.190 align:start position:0% these represent a pretty big shift in the<00:17:50.280> way<00:17:50.400> that<00:17:50.640> we<00:17:50.820> can<00:17:50.940> design<00:17:51.120> ZK<00:17:51.660> circuits 00:17:52.190 --> 00:17:52.200 align:start position:0% the way that we can design ZK circuits 00:17:52.200 --> 00:17:54.890 align:start position:0% the way that we can design ZK circuits and<00:17:52.799> what<00:17:53.039> type<00:17:53.280> of<00:17:53.640> programs<00:17:54.179> we<00:17:54.539> can<00:17:54.720> express 00:17:54.890 --> 00:17:54.900 align:start position:0% and what type of programs we can express 00:17:54.900 --> 00:17:57.110 align:start position:0% and what type of programs we can express efficiently<00:17:55.559> in<00:17:55.740> them<00:17:55.919> and<00:17:56.580> so<00:17:56.760> it'll<00:17:56.940> be 00:17:57.110 --> 00:17:57.120 align:start position:0% efficiently in them and so it'll be 00:17:57.120 --> 00:17:59.630 align:start position:0% efficiently in them and so it'll be exciting<00:17:57.419> to<00:17:57.660> see<00:17:57.960> how<00:17:58.620> fast<00:17:58.740> these<00:17:59.100> can<00:17:59.520> come 00:17:59.630 --> 00:17:59.640 align:start position:0% exciting to see how fast these can come 00:17:59.640 --> 00:18:01.430 align:start position:0% exciting to see how fast these can come to<00:17:59.760> production<00:18:00.120> and<00:18:00.660> what<00:18:00.840> new<00:18:01.020> applications 00:18:01.430 --> 00:18:01.440 align:start position:0% to production and what new applications 00:18:01.440 --> 00:18:03.950 align:start position:0% to production and what new applications they<00:18:01.980> can<00:18:02.100> enable<00:18:02.400> oh<00:18:03.179> yeah 00:18:03.950 --> 00:18:03.960 align:start position:0% they can enable oh yeah 00:18:03.960 --> 00:18:06.590 align:start position:0% they can enable oh yeah um<00:18:04.080> and<00:18:04.440> so<00:18:04.620> so<00:18:04.860> finally 00:18:06.590 --> 00:18:06.600 align:start position:0% um and so so finally 00:18:06.600 --> 00:18:08.270 align:start position:0% um and so so finally um and<00:18:07.200> to<00:18:07.320> talk<00:18:07.500> a<00:18:07.620> little<00:18:07.679> bit<00:18:07.740> about<00:18:07.919> where 00:18:08.270 --> 00:18:08.280 align:start position:0% um and to talk a little bit about where 00:18:08.280 --> 00:18:09.590 align:start position:0% um and to talk a little bit about where we<00:18:08.400> see<00:18:08.580> kind<00:18:08.820> of<00:18:08.940> these<00:18:09.179> two<00:18:09.360> things 00:18:09.590 --> 00:18:09.600 align:start position:0% we see kind of these two things 00:18:09.600 --> 00:18:12.350 align:start position:0% we see kind of these two things converging<00:18:10.320> in<00:18:10.559> the<00:18:10.679> third<00:18:10.799> quadrant 00:18:12.350 --> 00:18:12.360 align:start position:0% converging in the third quadrant 00:18:12.360 --> 00:18:16.010 align:start position:0% converging in the third quadrant um<00:18:12.960> this<00:18:13.679> is<00:18:13.919> probably<00:18:14.419> what<00:18:15.419> the<00:18:15.600> future<00:18:15.720> will 00:18:16.010 --> 00:18:16.020 align:start position:0% um this is probably what the future will 00:18:16.020 --> 00:18:17.990 align:start position:0% um this is probably what the future will look<00:18:16.200> like<00:18:16.320> in<00:18:16.679> the<00:18:16.740> sense<00:18:16.919> that<00:18:17.160> so<00:18:17.460> so<00:18:17.520> that 00:18:17.990 --> 00:18:18.000 align:start position:0% look like in the sense that so so that 00:18:18.000 --> 00:18:21.049 align:start position:0% look like in the sense that so so that the<00:18:18.059> left<00:18:18.419> side<00:18:18.660> is<00:18:19.080> the<00:18:19.440> kind<00:18:19.679> of<00:18:19.799> uh<00:18:20.580> privacy 00:18:21.049 --> 00:18:21.059 align:start position:0% the left side is the kind of uh privacy 00:18:21.059 --> 00:18:22.669 align:start position:0% the left side is the kind of uh privacy side<00:18:21.299> and<00:18:21.600> the<00:18:21.780> right<00:18:21.900> side<00:18:22.080> is<00:18:22.260> sort<00:18:22.440> of<00:18:22.559> the 00:18:22.669 --> 00:18:22.679 align:start position:0% side and the right side is sort of the 00:18:22.679 --> 00:18:24.830 align:start position:0% side and the right side is sort of the succinct<00:18:23.100> proving<00:18:23.400> side<00:18:23.640> and<00:18:24.299> the<00:18:24.419> idea<00:18:24.660> being 00:18:24.830 --> 00:18:24.840 align:start position:0% succinct proving side and the idea being 00:18:24.840 --> 00:18:27.049 align:start position:0% succinct proving side and the idea being that<00:18:25.200> hopefully<00:18:25.919> we<00:18:26.280> reduce<00:18:26.460> the<00:18:26.760> surface 00:18:27.049 --> 00:18:27.059 align:start position:0% that hopefully we reduce the surface 00:18:27.059 --> 00:18:30.409 align:start position:0% that hopefully we reduce the surface area<00:18:27.240> of<00:18:27.720> the<00:18:27.960> private<00:18:28.320> to<00:18:28.620> public<00:18:29.000> ish<00:18:30.000> proof 00:18:30.409 --> 00:18:30.419 align:start position:0% area of the private to public ish proof 00:18:30.419 --> 00:18:32.090 align:start position:0% area of the private to public ish proof to<00:18:30.720> something<00:18:30.960> quite<00:18:31.320> small<00:18:31.500> that<00:18:31.799> could<00:18:31.980> then 00:18:32.090 --> 00:18:32.100 align:start position:0% to something quite small that could then 00:18:32.100 --> 00:18:34.250 align:start position:0% to something quite small that could then be<00:18:32.280> recursively<00:18:32.940> included<00:18:33.539> in<00:18:33.840> a<00:18:33.960> larger 00:18:34.250 --> 00:18:34.260 align:start position:0% be recursively included in a larger 00:18:34.260 --> 00:18:37.549 align:start position:0% be recursively included in a larger proof<00:18:34.679> uh<00:18:35.520> that<00:18:35.820> is<00:18:36.000> that<00:18:36.539> you<00:18:36.960> know<00:18:37.020> that<00:18:37.260> that 00:18:37.549 --> 00:18:37.559 align:start position:0% proof uh that is that you know that that 00:18:37.559 --> 00:18:39.350 align:start position:0% proof uh that is that you know that that is<00:18:37.799> in<00:18:37.919> the<00:18:38.100> kind<00:18:38.220> of<00:18:38.280> like<00:18:38.460> succinct<00:18:39.059> but<00:18:39.240> not 00:18:39.350 --> 00:18:39.360 align:start position:0% is in the kind of like succinct but not 00:18:39.360 --> 00:18:42.770 align:start position:0% is in the kind of like succinct but not private<00:18:39.919> uh<00:18:40.919> kind<00:18:41.100> of<00:18:41.160> like<00:18:41.820> um<00:18:41.880> technological 00:18:42.770 --> 00:18:42.780 align:start position:0% private uh kind of like um technological 00:18:42.780 --> 00:18:44.390 align:start position:0% private uh kind of like um technological requirement<00:18:43.200> land<00:18:43.500> and<00:18:43.980> then<00:18:44.100> that<00:18:44.280> is 00:18:44.390 --> 00:18:44.400 align:start position:0% requirement land and then that is 00:18:44.400 --> 00:18:45.770 align:start position:0% requirement land and then that is interpreted<00:18:44.880> on<00:18:45.000> chain<00:18:45.179> and<00:18:45.360> then<00:18:45.480> this<00:18:45.660> way 00:18:45.770 --> 00:18:45.780 align:start position:0% interpreted on chain and then this way 00:18:45.780 --> 00:18:47.510 align:start position:0% interpreted on chain and then this way we<00:18:45.960> get<00:18:46.080> all<00:18:46.620> you<00:18:46.919> know<00:18:46.980> all<00:18:47.100> of<00:18:47.280> the<00:18:47.400> nice 00:18:47.510 --> 00:18:47.520 align:start position:0% we get all you know all of the nice 00:18:47.520 --> 00:18:49.070 align:start position:0% we get all you know all of the nice benefits<00:18:47.940> the<00:18:48.059> Privacy<00:18:48.360> answering<00:18:48.840> thickness 00:18:49.070 --> 00:18:49.080 align:start position:0% benefits the Privacy answering thickness 00:18:49.080 --> 00:18:50.090 align:start position:0% benefits the Privacy answering thickness and 00:18:50.090 --> 00:18:50.100 align:start position:0% and 00:18:50.100 --> 00:18:52.190 align:start position:0% and on-chain<00:18:50.820> applications<00:18:51.299> with<00:18:51.600> pseudonymity 00:18:52.190 --> 00:18:52.200 align:start position:0% on-chain applications with pseudonymity 00:18:52.200 --> 00:18:54.710 align:start position:0% on-chain applications with pseudonymity and<00:18:52.500> cool<00:18:52.799> stuff<00:18:52.980> like<00:18:53.160> that 00:18:54.710 --> 00:18:54.720 align:start position:0% and cool stuff like that 00:18:54.720 --> 00:18:57.830 align:start position:0% and cool stuff like that um<00:18:54.780> yeah<00:18:55.140> that's<00:18:55.380> it<00:18:56.100> sorry<00:18:56.580> maybe<00:18:56.940> a<00:18:57.299> silly 00:18:57.830 --> 00:18:57.840 align:start position:0% um yeah that's it sorry maybe a silly 00:18:57.840 --> 00:18:59.990 align:start position:0% um yeah that's it sorry maybe a silly question<00:18:57.960> for<00:18:58.260> the<00:18:58.440> audience<00:18:58.740> but<00:18:59.580> um<00:18:59.640> can<00:18:59.820> you 00:18:59.990 --> 00:19:00.000 align:start position:0% question for the audience but um can you 00:19:00.000 --> 00:19:01.549 align:start position:0% question for the audience but um can you explain<00:19:00.120> a<00:19:00.360> bit<00:19:00.539> more<00:19:00.660> like<00:19:00.840> what<00:19:01.260> actually 00:19:01.549 --> 00:19:01.559 align:start position:0% explain a bit more like what actually 00:19:01.559 --> 00:19:05.090 align:start position:0% explain a bit more like what actually sing<00:19:02.520> means<00:19:03.179> like<00:19:03.419> what's<00:19:03.660> that<00:19:03.900> probably 00:19:05.090 --> 00:19:05.100 align:start position:0% sing means like what's that probably 00:19:05.100 --> 00:19:07.810 align:start position:0% sing means like what's that probably um<00:19:05.220> you<00:19:05.700> know<00:19:05.760> in<00:19:05.880> the<00:19:06.000> Layman<00:19:06.600> Layman 00:19:07.810 --> 00:19:07.820 align:start position:0% um you know in the Layman Layman 00:19:07.820 --> 00:19:10.669 align:start position:0% um you know in the Layman Layman layman's<00:19:08.820> terms<00:19:09.480> yeah 00:19:10.669 --> 00:19:10.679 align:start position:0% layman's terms yeah 00:19:10.679 --> 00:19:12.710 align:start position:0% layman's terms yeah yeah so<00:19:11.280> succinct<00:19:12.120> this<00:19:12.299> is<00:19:12.360> a<00:19:12.480> property<00:19:12.660> of 00:19:12.710 --> 00:19:12.720 align:start position:0% yeah so succinct this is a property of 00:19:12.720 --> 00:19:14.510 align:start position:0% yeah so succinct this is a property of zero<00:19:13.020> knowledge<00:19:13.260> proofs<00:19:13.559> which<00:19:13.980> says<00:19:14.280> that 00:19:14.510 --> 00:19:14.520 align:start position:0% zero knowledge proofs which says that 00:19:14.520 --> 00:19:16.630 align:start position:0% zero knowledge proofs which says that the<00:19:14.760> size<00:19:14.880> of<00:19:15.120> the<00:19:15.299> proof<00:19:15.600> can<00:19:16.320> be 00:19:16.630 --> 00:19:16.640 align:start position:0% the size of the proof can be 00:19:16.640 --> 00:19:18.950 align:start position:0% the size of the proof can be asymptotically<00:19:17.640> smaller<00:19:18.179> than<00:19:18.480> the<00:19:18.660> size<00:19:18.780> of 00:19:18.950 --> 00:19:18.960 align:start position:0% asymptotically smaller than the size of 00:19:18.960 --> 00:19:20.930 align:start position:0% asymptotically smaller than the size of the<00:19:19.080> computation<00:19:19.500> you're<00:19:19.740> able<00:19:19.980> to<00:19:20.100> do<00:19:20.220> so 00:19:20.930 --> 00:19:20.940 align:start position:0% the computation you're able to do so 00:19:20.940 --> 00:19:23.090 align:start position:0% the computation you're able to do so depending<00:19:21.299> on<00:19:21.539> the<00:19:21.660> proof<00:19:21.960> system<00:19:22.140> either<00:19:22.860> the 00:19:23.090 --> 00:19:23.100 align:start position:0% depending on the proof system either the 00:19:23.100 --> 00:19:24.890 align:start position:0% depending on the proof system either the size<00:19:23.280> of<00:19:23.400> the<00:19:23.520> proof<00:19:23.760> could<00:19:24.000> be<00:19:24.179> constant<00:19:24.600> size 00:19:24.890 --> 00:19:24.900 align:start position:0% size of the proof could be constant size 00:19:24.900 --> 00:19:27.110 align:start position:0% size of the proof could be constant size in<00:19:25.380> the<00:19:25.559> size<00:19:25.679> of<00:19:25.799> the<00:19:25.919> computation<00:19:26.340> or<00:19:26.940> it 00:19:27.110 --> 00:19:27.120 align:start position:0% in the size of the computation or it 00:19:27.120 --> 00:19:29.090 align:start position:0% in the size of the computation or it could<00:19:27.240> be<00:19:27.299> logarithmic<00:19:28.020> but<00:19:28.559> either<00:19:28.740> way<00:19:28.919> the 00:19:29.090 --> 00:19:29.100 align:start position:0% could be logarithmic but either way the 00:19:29.100 --> 00:19:31.310 align:start position:0% could be logarithmic but either way the point<00:19:29.280> is<00:19:29.460> that<00:19:29.760> you<00:19:30.240> can<00:19:30.360> verify<00:19:30.780> this<00:19:31.020> proof 00:19:31.310 --> 00:19:31.320 align:start position:0% point is that you can verify this proof 00:19:31.320 --> 00:19:33.590 align:start position:0% point is that you can verify this proof in<00:19:31.799> much<00:19:32.039> less<00:19:32.160> compute<00:19:32.700> than<00:19:33.000> doing<00:19:33.360> the 00:19:33.590 --> 00:19:33.600 align:start position:0% in much less compute than doing the 00:19:33.600 --> 00:19:35.750 align:start position:0% in much less compute than doing the actual<00:19:33.780> computation<00:19:34.260> itself 00:19:35.750 --> 00:19:35.760 align:start position:0% actual computation itself 00:19:35.760 --> 00:19:37.850 align:start position:0% actual computation itself hey<00:19:36.299> and<00:19:36.600> perhaps<00:19:37.020> there's<00:19:37.140> another<00:19:37.320> distinct 00:19:37.850 --> 00:19:37.860 align:start position:0% hey and perhaps there's another distinct 00:19:37.860 --> 00:19:39.830 align:start position:0% hey and perhaps there's another distinct slight<00:19:38.400> thing<00:19:38.580> which<00:19:38.820> is 00:19:39.830 --> 00:19:39.840 align:start position:0% slight thing which is 00:19:39.840 --> 00:19:42.169 align:start position:0% slight thing which is um<00:19:39.900> many<00:19:40.320> many<00:19:40.919> of<00:19:41.160> many<00:19:41.400> I<00:19:41.700> mean<00:19:41.820> most<00:19:42.059> of 00:19:42.169 --> 00:19:42.179 align:start position:0% um many many of many I mean most of 00:19:42.179 --> 00:19:44.330 align:start position:0% um many many of many I mean most of these<00:19:42.299> proof<00:19:42.539> systems<00:19:42.960> do<00:19:43.559> have<00:19:43.799> constant 00:19:44.330 --> 00:19:44.340 align:start position:0% these proof systems do have constant 00:19:44.340 --> 00:19:46.789 align:start position:0% these proof systems do have constant proof<00:19:44.640> sizes<00:19:44.940> but<00:19:45.120> also<00:19:45.360> like<00:19:45.539> the<00:19:45.900> the<00:19:46.140> lower 00:19:46.789 --> 00:19:46.799 align:start position:0% proof sizes but also like the the lower 00:19:46.799 --> 00:19:48.529 align:start position:0% proof sizes but also like the the lower the<00:19:47.400> lower<00:19:47.520> the<00:19:47.700> constant<00:19:48.000> proof<00:19:48.240> size<00:19:48.360> the 00:19:48.529 --> 00:19:48.539 align:start position:0% the lower the constant proof size the 00:19:48.539 --> 00:19:50.150 align:start position:0% the lower the constant proof size the better<00:19:48.720> for<00:19:49.140> uh<00:19:49.679> something<00:19:49.860> that<00:19:50.039> is 00:19:50.150 --> 00:19:50.160 align:start position:0% better for uh something that is 00:19:50.160 --> 00:19:52.190 align:start position:0% better for uh something that is interpreted<00:19:50.580> on<00:19:50.700> chain<00:19:50.880> obviously 00:19:52.190 --> 00:19:52.200 align:start position:0% interpreted on chain obviously 00:19:52.200 --> 00:19:53.870 align:start position:0% interpreted on chain obviously um<00:19:52.320> but<00:19:52.740> yeah<00:19:52.919> use<00:19:53.160> answer<00:19:53.400> is<00:19:53.640> better<00:19:53.760> than 00:19:53.870 --> 00:19:53.880 align:start position:0% um but yeah use answer is better than 00:19:53.880 --> 00:19:54.770 align:start position:0% um but yeah use answer is better than mine<00:19:54.059> would<00:19:54.179> have<00:19:54.240> been<00:19:54.360> I<00:19:54.480> was<00:19:54.600> just<00:19:54.660> gonna 00:19:54.770 --> 00:19:54.780 align:start position:0% mine would have been I was just gonna 00:19:54.780 --> 00:19:56.930 align:start position:0% mine would have been I was just gonna say<00:19:54.900> small 00:19:56.930 --> 00:19:56.940 align:start position:0% say small 00:19:56.940 --> 00:20:00.770 align:start position:0% say small Hey<00:19:57.480> so<00:19:58.260> uh<00:19:58.919> when<00:19:59.280> we<00:19:59.700> recursively<00:20:00.360> prove 00:20:00.770 --> 00:20:00.780 align:start position:0% Hey so uh when we recursively prove 00:20:00.780 --> 00:20:03.710 align:start position:0% Hey so uh when we recursively prove stuff<00:20:00.960> so<00:20:01.380> over<00:20:01.679> here<00:20:01.919> sorry<00:20:02.539> when<00:20:03.539> we 00:20:03.710 --> 00:20:03.720 align:start position:0% stuff so over here sorry when we 00:20:03.720 --> 00:20:06.409 align:start position:0% stuff so over here sorry when we recursively<00:20:04.440> prove<00:20:05.039> so<00:20:05.700> there<00:20:05.880> is<00:20:06.000> a<00:20:06.120> proof 00:20:06.409 --> 00:20:06.419 align:start position:0% recursively prove so there is a proof 00:20:06.419 --> 00:20:08.510 align:start position:0% recursively prove so there is a proof and<00:20:06.780> then<00:20:06.900> you<00:20:07.140> are<00:20:07.320> proving<00:20:07.740> the<00:20:07.980> proof<00:20:08.280> right 00:20:08.510 --> 00:20:08.520 align:start position:0% and then you are proving the proof right 00:20:08.520 --> 00:20:13.070 align:start position:0% and then you are proving the proof right so<00:20:09.360> uh<00:20:09.840> there<00:20:10.320> are<00:20:10.500> multiple<00:20:11.100> layers<00:20:11.760> of<00:20:12.179> uh 00:20:13.070 --> 00:20:13.080 align:start position:0% so uh there are multiple layers of uh 00:20:13.080 --> 00:20:15.409 align:start position:0% so uh there are multiple layers of uh Integrity<00:20:13.679> checks<00:20:14.220> right<00:20:14.400> that<00:20:14.700> that<00:20:14.820> is<00:20:15.059> the 00:20:15.409 --> 00:20:15.419 align:start position:0% Integrity checks right that that is the 00:20:15.419 --> 00:20:18.529 align:start position:0% Integrity checks right that that is the assurance<00:20:15.720> that<00:20:16.080> you<00:20:16.200> get<00:20:16.320> so<00:20:17.100> uh<00:20:18.059> and<00:20:18.299> these 00:20:18.529 --> 00:20:18.539 align:start position:0% assurance that you get so uh and these 00:20:18.539 --> 00:20:20.690 align:start position:0% assurance that you get so uh and these circuits<00:20:19.020> are<00:20:19.260> super<00:20:19.620> complex<00:20:20.100> and<00:20:20.520> there 00:20:20.690 --> 00:20:20.700 align:start position:0% circuits are super complex and there 00:20:20.700 --> 00:20:23.270 align:start position:0% circuits are super complex and there could<00:20:20.880> be<00:20:21.000> like<00:20:21.240> a<00:20:21.840> million<00:20:22.280> arithmeticians 00:20:23.270 --> 00:20:23.280 align:start position:0% could be like a million arithmeticians 00:20:23.280 --> 00:20:25.610 align:start position:0% could be like a million arithmeticians in<00:20:23.520> in<00:20:23.700> there<00:20:23.940> right<00:20:24.179> so<00:20:24.720> what<00:20:25.080> about<00:20:25.260> the 00:20:25.610 --> 00:20:25.620 align:start position:0% in in there right so what about the 00:20:25.620 --> 00:20:28.850 align:start position:0% in in there right so what about the security<00:20:25.860> of<00:20:26.700> uh<00:20:27.120> these<00:20:27.480> proofs<00:20:27.900> because<00:20:28.140> if 00:20:28.850 --> 00:20:28.860 align:start position:0% security of uh these proofs because if 00:20:28.860 --> 00:20:31.190 align:start position:0% security of uh these proofs because if you<00:20:28.980> have<00:20:29.160> a<00:20:29.520> single<00:20:29.760> bug<00:20:30.059> in<00:20:30.419> a<00:20:30.539> circuit<00:20:30.900> right 00:20:31.190 --> 00:20:31.200 align:start position:0% you have a single bug in a circuit right 00:20:31.200 --> 00:20:33.830 align:start position:0% you have a single bug in a circuit right that<00:20:31.740> is<00:20:31.860> gonna<00:20:32.100> Traverse<00:20:32.700> down<00:20:33.000> to<00:20:33.240> like<00:20:33.539> this 00:20:33.830 --> 00:20:33.840 align:start position:0% that is gonna Traverse down to like this 00:20:33.840 --> 00:20:35.870 align:start position:0% that is gonna Traverse down to like this very<00:20:34.200> small<00:20:34.440> proof<00:20:34.919> that<00:20:35.039> you<00:20:35.220> will<00:20:35.340> post<00:20:35.580> on 00:20:35.870 --> 00:20:35.880 align:start position:0% very small proof that you will post on 00:20:35.880 --> 00:20:37.669 align:start position:0% very small proof that you will post on chain<00:20:36.059> so<00:20:36.660> what<00:20:36.900> are<00:20:37.080> your<00:20:37.200> thoughts<00:20:37.500> about 00:20:37.669 --> 00:20:37.679 align:start position:0% chain so what are your thoughts about 00:20:37.679 --> 00:20:40.130 align:start position:0% chain so what are your thoughts about that<00:20:38.039> how<00:20:38.580> is<00:20:39.120> the<00:20:39.240> security<00:20:39.419> landscape 00:20:40.130 --> 00:20:40.140 align:start position:0% that how is the security landscape 00:20:40.140 --> 00:20:43.430 align:start position:0% that how is the security landscape around<00:20:40.400> verifying<00:20:41.400> CK<00:20:41.760> systems<00:20:42.660> glad<00:20:43.140> to<00:20:43.320> hear 00:20:43.430 --> 00:20:43.440 align:start position:0% around verifying CK systems glad to hear 00:20:43.440 --> 00:20:46.310 align:start position:0% around verifying CK systems glad to hear that<00:20:44.160> yeah<00:20:44.640> definitely<00:20:44.940> I<00:20:45.419> would<00:20:45.600> say<00:20:45.720> on<00:20:46.080> the 00:20:46.310 --> 00:20:46.320 align:start position:0% that yeah definitely I would say on the 00:20:46.320 --> 00:20:48.289 align:start position:0% that yeah definitely I would say on the second<00:20:46.440> side<00:20:47.340> definitely<00:20:47.640> recursion<00:20:48.120> and 00:20:48.289 --> 00:20:48.299 align:start position:0% second side definitely recursion and 00:20:48.299 --> 00:20:50.270 align:start position:0% second side definitely recursion and aggregation<00:20:48.780> make<00:20:49.500> it<00:20:49.620> substantially<00:20:50.039> more 00:20:50.270 --> 00:20:50.280 align:start position:0% aggregation make it substantially more 00:20:50.280 --> 00:20:52.730 align:start position:0% aggregation make it substantially more difficult<00:20:50.700> to<00:20:51.660> verify<00:20:52.080> that<00:20:52.260> your<00:20:52.380> circuits 00:20:52.730 --> 00:20:52.740 align:start position:0% difficult to verify that your circuits 00:20:52.740 --> 00:20:54.529 align:start position:0% difficult to verify that your circuits are<00:20:52.860> correct<00:20:53.160> so<00:20:53.880> we<00:20:54.059> have<00:20:54.179> obviously 00:20:54.529 --> 00:20:54.539 align:start position:0% are correct so we have obviously 00:20:54.539 --> 00:20:56.870 align:start position:0% are correct so we have obviously traditional<00:20:55.080> unit<00:20:55.440> testing<00:20:55.980> we<00:20:56.760> have 00:20:56.870 --> 00:20:56.880 align:start position:0% traditional unit testing we have 00:20:56.880 --> 00:20:58.909 align:start position:0% traditional unit testing we have randomized<00:20:57.419> fuzzing<00:20:57.840> and<00:20:58.380> we<00:20:58.500> have<00:20:58.620> some 00:20:58.909 --> 00:20:58.919 align:start position:0% randomized fuzzing and we have some 00:20:58.919 --> 00:21:01.010 align:start position:0% randomized fuzzing and we have some emerging<00:20:59.580> formal<00:20:59.940> verification<00:21:00.419> approaches 00:21:01.010 --> 00:21:01.020 align:start position:0% emerging formal verification approaches 00:21:01.020 --> 00:21:03.590 align:start position:0% emerging formal verification approaches for<00:21:01.559> ensuring<00:21:01.980> circuits<00:21:02.340> are<00:21:02.460> correct<00:21:02.760> where 00:21:03.590 --> 00:21:03.600 align:start position:0% for ensuring circuits are correct where 00:21:03.600 --> 00:21:05.210 align:start position:0% for ensuring circuits are correct where recursion<00:21:04.140> makes<00:21:04.320> these<00:21:04.620> more<00:21:04.799> complicated 00:21:05.210 --> 00:21:05.220 align:start position:0% recursion makes these more complicated 00:21:05.220 --> 00:21:07.070 align:start position:0% recursion makes these more complicated is<00:21:05.820> that<00:21:06.000> you<00:21:06.179> may<00:21:06.360> need<00:21:06.539> to<00:21:06.720> encode 00:21:07.070 --> 00:21:07.080 align:start position:0% is that you may need to encode 00:21:07.080 --> 00:21:09.289 align:start position:0% is that you may need to encode assumptions<00:21:07.620> slightly<00:21:08.460> external<00:21:09.000> to<00:21:09.179> your 00:21:09.289 --> 00:21:09.299 align:start position:0% assumptions slightly external to your 00:21:09.299 --> 00:21:11.630 align:start position:0% assumptions slightly external to your circuit<00:21:09.600> itself<00:21:09.900> to<00:21:10.440> check<00:21:10.559> things<00:21:10.860> I'm<00:21:11.460> sure 00:21:11.630 --> 00:21:11.640 align:start position:0% circuit itself to check things I'm sure 00:21:11.640 --> 00:21:13.010 align:start position:0% circuit itself to check things I'm sure locksman<00:21:12.059> has<00:21:12.240> some<00:21:12.299> views<00:21:12.539> on<00:21:12.660> how<00:21:12.900> that 00:21:13.010 --> 00:21:13.020 align:start position:0% locksman has some views on how that 00:21:13.020 --> 00:21:15.770 align:start position:0% locksman has some views on how that affects<00:21:13.320> privacy<00:21:13.679> as<00:21:13.860> well<00:21:14.039> oh<00:21:14.460> I<00:21:14.880> mean<00:21:14.940> I<00:21:15.360> like 00:21:15.770 --> 00:21:15.780 align:start position:0% affects privacy as well oh I mean I like 00:21:15.780 --> 00:21:17.690 align:start position:0% affects privacy as well oh I mean I like I<00:21:16.140> I<00:21:16.380> think<00:21:16.559> this<00:21:16.799> is<00:21:16.980> actually<00:21:17.100> something<00:21:17.400> we 00:21:17.690 --> 00:21:17.700 align:start position:0% I I think this is actually something we 00:21:17.700 --> 00:21:19.970 align:start position:0% I I think this is actually something we need<00:21:17.820> to<00:21:17.940> think<00:21:18.059> about<00:21:18.200> very<00:21:19.200> seriously<00:21:19.679> it 00:21:19.970 --> 00:21:19.980 align:start position:0% need to think about very seriously it 00:21:19.980 --> 00:21:21.710 align:start position:0% need to think about very seriously it feels<00:21:20.220> like<00:21:20.400> I<00:21:20.940> mean<00:21:21.059> if<00:21:21.179> any<00:21:21.360> of<00:21:21.480> you<00:21:21.600> are 00:21:21.710 --> 00:21:21.720 align:start position:0% feels like I mean if any of you are 00:21:21.720 --> 00:21:23.210 align:start position:0% feels like I mean if any of you are familiar<00:21:21.900> with<00:21:22.020> like<00:21:22.260> supply<00:21:22.500> chain<00:21:22.740> attacks 00:21:23.210 --> 00:21:23.220 align:start position:0% familiar with like supply chain attacks 00:21:23.220 --> 00:21:25.789 align:start position:0% familiar with like supply chain attacks and<00:21:23.340> the<00:21:23.580> node.js<00:21:24.179> ecosystem<00:21:24.780> it<00:21:25.500> feels<00:21:25.740> like 00:21:25.789 --> 00:21:25.799 align:start position:0% and the node.js ecosystem it feels like 00:21:25.799 --> 00:21:27.710 align:start position:0% and the node.js ecosystem it feels like we<00:21:25.919> could<00:21:26.039> easily<00:21:26.400> that<00:21:27.120> that<00:21:27.179> is<00:21:27.419> like<00:21:27.539> I 00:21:27.710 --> 00:21:27.720 align:start position:0% we could easily that that is like I 00:21:27.720 --> 00:21:29.090 align:start position:0% we could easily that that is like I don't<00:21:27.840> want<00:21:27.960> to<00:21:28.080> get<00:21:28.200> too<00:21:28.380> pessimistic<00:21:28.919> but 00:21:29.090 --> 00:21:29.100 align:start position:0% don't want to get too pessimistic but 00:21:29.100 --> 00:21:30.770 align:start position:0% don't want to get too pessimistic but that<00:21:29.220> is<00:21:29.340> like<00:21:29.580> a<00:21:30.000> very<00:21:30.059> bad<00:21:30.240> worst<00:21:30.539> case<00:21:30.600> here 00:21:30.770 --> 00:21:30.780 align:start position:0% that is like a very bad worst case here 00:21:30.780 --> 00:21:32.570 align:start position:0% that is like a very bad worst case here because<00:21:30.960> it's<00:21:31.080> like<00:21:31.200> it's<00:21:31.380> very<00:21:31.559> hard<00:21:31.860> for<00:21:32.280> the 00:21:32.570 --> 00:21:32.580 align:start position:0% because it's like it's very hard for the 00:21:32.580 --> 00:21:35.029 align:start position:0% because it's like it's very hard for the the<00:21:33.179> recursing<00:21:33.720> proof<00:21:34.020> to<00:21:34.260> make<00:21:34.440> strong 00:21:35.029 --> 00:21:35.039 align:start position:0% the recursing proof to make strong 00:21:35.039 --> 00:21:37.490 align:start position:0% the recursing proof to make strong assumptions<00:21:35.520> around<00:21:35.820> the<00:21:36.059> soundness<00:21:36.480> of<00:21:37.020> like 00:21:37.490 --> 00:21:37.500 align:start position:0% assumptions around the soundness of like 00:21:37.500 --> 00:21:40.190 align:start position:0% assumptions around the soundness of like proof<00:21:37.919> that<00:21:38.039> is<00:21:38.220> recursing<00:21:38.820> on 00:21:40.190 --> 00:21:40.200 align:start position:0% proof that is recursing on 00:21:40.200 --> 00:21:40.789 align:start position:0% proof that is recursing on um 00:21:40.789 --> 00:21:40.799 align:start position:0% um 00:21:40.799 --> 00:21:42.710 align:start position:0% um I<00:21:41.280> don't<00:21:41.580> have<00:21:41.760> any<00:21:41.940> optimistic<00:21:42.480> takes 00:21:42.710 --> 00:21:42.720 align:start position:0% I don't have any optimistic takes 00:21:42.720 --> 00:21:43.850 align:start position:0% I don't have any optimistic takes unfortunately<00:21:43.140> but<00:21:43.380> I<00:21:43.500> think<00:21:43.620> it's<00:21:43.679> something 00:21:43.850 --> 00:21:43.860 align:start position:0% unfortunately but I think it's something 00:21:43.860 --> 00:21:45.110 align:start position:0% unfortunately but I think it's something we<00:21:44.039> need<00:21:44.159> to<00:21:44.220> think<00:21:44.340> about<00:21:44.400> there<00:21:44.580> are<00:21:44.760> lots<00:21:45.000> of 00:21:45.110 --> 00:21:45.120 align:start position:0% we need to think about there are lots of 00:21:45.120 --> 00:21:46.549 align:start position:0% we need to think about there are lots of great<00:21:45.480> people<00:21:45.720> like<00:21:46.080> especially<00:21:46.320> in<00:21:46.440> the 00:21:46.549 --> 00:21:46.559 align:start position:0% great people like especially in the 00:21:46.559 --> 00:21:48.710 align:start position:0% great people like especially in the Xerox<00:21:46.860> Park<00:21:47.100> ecosystem<00:21:47.880> kind<00:21:48.240> of<00:21:48.299> thinking<00:21:48.539> a 00:21:48.710 --> 00:21:48.720 align:start position:0% Xerox Park ecosystem kind of thinking a 00:21:48.720 --> 00:21:50.870 align:start position:0% Xerox Park ecosystem kind of thinking a lot<00:21:48.780> about<00:21:48.960> about<00:21:49.740> like<00:21:50.280> uh<00:21:50.460> formal 00:21:50.870 --> 00:21:50.880 align:start position:0% lot about about like uh formal 00:21:50.880 --> 00:21:52.250 align:start position:0% lot about about like uh formal verification<00:21:51.299> and<00:21:51.480> things<00:21:51.600> like<00:21:51.780> this<00:21:51.960> and 00:21:52.250 --> 00:21:52.260 align:start position:0% verification and things like this and 00:21:52.260 --> 00:21:54.590 align:start position:0% verification and things like this and maybe<00:21:52.620> like<00:21:53.039> yeah<00:21:53.640> there's<00:21:53.940> formal 00:21:54.590 --> 00:21:54.600 align:start position:0% maybe like yeah there's formal 00:21:54.600 --> 00:21:56.149 align:start position:0% maybe like yeah there's formal verification<00:21:55.020> of<00:21:55.320> the<00:21:55.440> dependency<00:21:55.799> graph 00:21:56.149 --> 00:21:56.159 align:start position:0% verification of the dependency graph 00:21:56.159 --> 00:21:58.190 align:start position:0% verification of the dependency graph type<00:21:56.400> things<00:21:56.640> needs<00:21:57.179> to<00:21:57.240> needs<00:21:57.960> to<00:21:58.020> start 00:21:58.190 --> 00:21:58.200 align:start position:0% type things needs to needs to start 00:21:58.200 --> 00:22:01.250 align:start position:0% type things needs to needs to start happening<00:21:58.620> I<00:21:58.860> I<00:21:59.039> don't<00:21:59.220> know<00:21:59.340> hello<00:21:59.900> uh<00:22:00.900> what 00:22:01.250 --> 00:22:01.260 align:start position:0% happening I I don't know hello uh what 00:22:01.260 --> 00:22:03.710 align:start position:0% happening I I don't know hello uh what measures<00:22:01.799> can<00:22:02.100> we<00:22:02.340> take<00:22:02.640> uh<00:22:03.240> to<00:22:03.419> make<00:22:03.539> our 00:22:03.710 --> 00:22:03.720 align:start position:0% measures can we take uh to make our 00:22:03.720 --> 00:22:06.350 align:start position:0% measures can we take uh to make our proofs<00:22:04.200> Quantum<00:22:04.860> resistance<00:22:05.460> for<00:22:06.000> the<00:22:06.240> long 00:22:06.350 --> 00:22:06.360 align:start position:0% proofs Quantum resistance for the long 00:22:06.360 --> 00:22:07.549 align:start position:0% proofs Quantum resistance for the long term 00:22:07.549 --> 00:22:07.559 align:start position:0% term 00:22:07.559 --> 00:22:09.110 align:start position:0% term so<00:22:08.039> I<00:22:08.220> think<00:22:08.340> of<00:22:08.460> the<00:22:08.580> different<00:22:08.700> proof 00:22:09.110 --> 00:22:09.120 align:start position:0% so I think of the different proof 00:22:09.120 --> 00:22:11.029 align:start position:0% so I think of the different proof systems<00:22:09.600> most<00:22:10.080> of<00:22:10.200> the<00:22:10.260> ones<00:22:10.500> which<00:22:10.679> are<00:22:10.799> based 00:22:11.029 --> 00:22:11.039 align:start position:0% systems most of the ones which are based 00:22:11.039 --> 00:22:12.950 align:start position:0% systems most of the ones which are based on<00:22:11.159> elliptic<00:22:11.580> curve<00:22:11.760> cryptography<00:22:12.360> are<00:22:12.780> not 00:22:12.950 --> 00:22:12.960 align:start position:0% on elliptic curve cryptography are not 00:22:12.960 --> 00:22:15.289 align:start position:0% on elliptic curve cryptography are not going<00:22:13.080> to<00:22:13.140> be<00:22:13.200> Quantum<00:22:13.919> resistant<00:22:14.520> since<00:22:15.059> they 00:22:15.289 --> 00:22:15.299 align:start position:0% going to be Quantum resistant since they 00:22:15.299 --> 00:22:17.090 align:start position:0% going to be Quantum resistant since they will<00:22:15.720> require<00:22:16.020> at<00:22:16.380> least<00:22:16.500> a<00:22:16.679> discrete<00:22:16.980> log 00:22:17.090 --> 00:22:17.100 align:start position:0% will require at least a discrete log 00:22:17.100 --> 00:22:19.130 align:start position:0% will require at least a discrete log assumption<00:22:17.700> but<00:22:18.360> we<00:22:18.539> actually<00:22:18.659> do<00:22:18.900> already 00:22:19.130 --> 00:22:19.140 align:start position:0% assumption but we actually do already 00:22:19.140 --> 00:22:20.990 align:start position:0% assumption but we actually do already know<00:22:19.559> proof<00:22:19.980> systems<00:22:20.340> which<00:22:20.460> are<00:22:20.580> quantum 00:22:20.990 --> 00:22:21.000 align:start position:0% know proof systems which are quantum 00:22:21.000 --> 00:22:23.930 align:start position:0% know proof systems which are quantum resistant<00:22:21.780> like<00:22:22.500> Starks<00:22:23.220> which<00:22:23.460> only<00:22:23.640> require 00:22:23.930 --> 00:22:23.940 align:start position:0% resistant like Starks which only require 00:22:23.940 --> 00:22:26.870 align:start position:0% resistant like Starks which only require a<00:22:24.419> random<00:22:24.720> Oracle<00:22:25.020> hash<00:22:25.260> assumption 00:22:26.870 --> 00:22:26.880 align:start position:0% a random Oracle hash assumption 00:22:26.880 --> 00:22:29.330 align:start position:0% a random Oracle hash assumption um so<00:22:27.240> if<00:22:27.840> you<00:22:28.020> want<00:22:28.260> something<00:22:28.620> to<00:22:28.980> be<00:22:29.100> really 00:22:29.330 --> 00:22:29.340 align:start position:0% um so if you want something to be really 00:22:29.340 --> 00:22:31.310 align:start position:0% um so if you want something to be really standing<00:22:29.820> the<00:22:29.940> test<00:22:30.120> of<00:22:30.360> time<00:22:30.539> you<00:22:31.200> probably 00:22:31.310 --> 00:22:31.320 align:start position:0% standing the test of time you probably 00:22:31.320 --> 00:22:32.570 align:start position:0% standing the test of time you probably want<00:22:31.500> to<00:22:31.620> use<00:22:31.860> one<00:22:32.039> of<00:22:32.100> those<00:22:32.159> Quantum 00:22:32.570 --> 00:22:32.580 align:start position:0% want to use one of those Quantum 00:22:32.580 --> 00:22:34.130 align:start position:0% want to use one of those Quantum resistant<00:22:33.000> systems 00:22:34.130 --> 00:22:34.140 align:start position:0% resistant systems 00:22:34.140 --> 00:22:35.630 align:start position:0% resistant systems um<00:22:34.200> I<00:22:34.440> just<00:22:34.559> wanted<00:22:34.740> to<00:22:34.919> add<00:22:35.100> to<00:22:35.280> the<00:22:35.520> 16 00:22:35.630 --> 00:22:35.640 align:start position:0% um I just wanted to add to the 16 00:22:35.640 --> 00:22:37.010 align:start position:0% um I just wanted to add to the 16 minutes<00:22:36.000> part<00:22:36.240> there's<00:22:36.720> a<00:22:36.900> difference 00:22:37.010 --> 00:22:37.020 align:start position:0% minutes part there's a difference 00:22:37.020 --> 00:22:38.930 align:start position:0% minutes part there's a difference between<00:22:37.260> space<00:22:37.679> succinctness<00:22:38.580> and<00:22:38.820> time 00:22:38.930 --> 00:22:38.940 align:start position:0% between space succinctness and time 00:22:38.940 --> 00:22:40.190 align:start position:0% between space succinctness and time succinctness 00:22:40.190 --> 00:22:40.200 align:start position:0% succinctness 00:22:40.200 --> 00:22:41.990 align:start position:0% succinctness um<00:22:40.260> and<00:22:40.380> usually<00:22:40.620> six<00:22:40.799> things<00:22:41.039> will<00:22:41.460> mean<00:22:41.760> like 00:22:41.990 --> 00:22:42.000 align:start position:0% um and usually six things will mean like 00:22:42.000 --> 00:22:43.190 align:start position:0% um and usually six things will mean like both 00:22:43.190 --> 00:22:43.200 align:start position:0% both 00:22:43.200 --> 00:22:45.470 align:start position:0% both um<00:22:43.320> a<00:22:43.559> question<00:22:43.919> on<00:22:44.220> calc 00:22:45.470 --> 00:22:45.480 align:start position:0% um a question on calc 00:22:45.480 --> 00:22:47.570 align:start position:0% um a question on calc um<00:22:45.539> what<00:22:45.840> do<00:22:45.900> you<00:22:45.960> mean<00:22:46.080> by<00:22:46.200> caulk<00:22:46.740> being<00:22:47.340> more 00:22:47.570 --> 00:22:47.580 align:start position:0% um what do you mean by caulk being more 00:22:47.580 --> 00:22:50.630 align:start position:0% um what do you mean by caulk being more efficient<00:22:47.880> than<00:22:48.659> um<00:22:49.200> the<00:22:49.559> easiest<00:22:50.039> World<00:22:50.280> Cups 00:22:50.630 --> 00:22:50.640 align:start position:0% efficient than um the easiest World Cups 00:22:50.640 --> 00:22:53.570 align:start position:0% efficient than um the easiest World Cups so<00:22:51.059> it<00:22:52.260> from<00:22:52.679> all<00:22:52.860> it<00:22:53.039> seems<00:22:53.159> to<00:22:53.280> me<00:22:53.340> that<00:22:53.460> you 00:22:53.570 --> 00:22:53.580 align:start position:0% so it from all it seems to me that you 00:22:53.580 --> 00:22:55.190 align:start position:0% so it from all it seems to me that you can<00:22:53.700> actually<00:22:53.760> be<00:22:54.059> applied<00:22:54.360> to<00:22:54.480> like<00:22:54.720> local 00:22:55.190 --> 00:22:55.200 align:start position:0% can actually be applied to like local 00:22:55.200 --> 00:22:57.289 align:start position:0% can actually be applied to like local arguments<00:22:55.679> in<00:22:55.799> circuits<00:22:56.280> or<00:22:56.640> in<00:22:56.940> the<00:22:57.000> Mercury 00:22:57.289 --> 00:22:57.299 align:start position:0% arguments in circuits or in the Mercury 00:22:57.299 --> 00:22:59.090 align:start position:0% arguments in circuits or in the Mercury setting<00:22:57.720> where<00:22:57.900> you<00:22:58.080> want<00:22:58.200> to<00:22:58.320> have<00:22:58.500> you<00:22:58.980> know 00:22:59.090 --> 00:22:59.100 align:start position:0% setting where you want to have you know 00:22:59.100 --> 00:23:01.490 align:start position:0% setting where you want to have you know zero<00:22:59.880> knowledge<00:23:00.179> membership<00:23:00.600> roofs<00:23:01.140> because 00:23:01.490 --> 00:23:01.500 align:start position:0% zero knowledge membership roofs because 00:23:01.500 --> 00:23:02.690 align:start position:0% zero knowledge membership roofs because that<00:23:01.860> the 00:23:02.690 --> 00:23:02.700 align:start position:0% that the 00:23:02.700 --> 00:23:04.789 align:start position:0% that the there's<00:23:03.179> a<00:23:03.480> like<00:23:04.020> there's<00:23:04.140> a<00:23:04.260> linear<00:23:04.500> overhead 00:23:04.789 --> 00:23:04.799 align:start position:0% there's a like there's a linear overhead 00:23:04.799 --> 00:23:06.409 align:start position:0% there's a like there's a linear overhead when<00:23:05.159> maintaining<00:23:05.640> this<00:23:05.940> you<00:23:06.120> know<00:23:06.240> free 00:23:06.409 --> 00:23:06.419 align:start position:0% when maintaining this you know free 00:23:06.419 --> 00:23:07.669 align:start position:0% when maintaining this you know free process<00:23:06.720> of<00:23:06.840> proofs 00:23:07.669 --> 00:23:07.679 align:start position:0% process of proofs 00:23:07.679 --> 00:23:09.529 align:start position:0% process of proofs yeah<00:23:07.919> definitely<00:23:08.580> like<00:23:08.820> I<00:23:09.059> would<00:23:09.299> say<00:23:09.360> we're 00:23:09.529 --> 00:23:09.539 align:start position:0% yeah definitely like I would say we're 00:23:09.539 --> 00:23:10.730 align:start position:0% yeah definitely like I would say we're being<00:23:09.720> a<00:23:09.840> bit<00:23:09.900> sloppy<00:23:10.260> with<00:23:10.380> the<00:23:10.500> use<00:23:10.620> of 00:23:10.730 --> 00:23:10.740 align:start position:0% being a bit sloppy with the use of 00:23:10.740 --> 00:23:12.710 align:start position:0% being a bit sloppy with the use of succinctness<00:23:11.220> here<00:23:11.400> in<00:23:11.880> most<00:23:12.059> of<00:23:12.179> the<00:23:12.240> systems 00:23:12.710 --> 00:23:12.720 align:start position:0% succinctness here in most of the systems 00:23:12.720 --> 00:23:16.010 align:start position:0% succinctness here in most of the systems that<00:23:13.020> are<00:23:13.500> deployed<00:23:13.860> today<00:23:14.039> you<00:23:14.520> get<00:23:14.700> both<00:23:15.059> uh 00:23:16.010 --> 00:23:16.020 align:start position:0% that are deployed today you get both uh 00:23:16.020 --> 00:23:18.890 align:start position:0% that are deployed today you get both uh verifier<00:23:16.980> and<00:23:17.220> size<00:23:17.400> success<00:23:18.059> uh<00:23:18.720> with 00:23:18.890 --> 00:23:18.900 align:start position:0% verifier and size success uh with 00:23:18.900 --> 00:23:20.330 align:start position:0% verifier and size success uh with regards<00:23:19.260> to<00:23:19.320> call<00:23:19.559> I'm<00:23:19.860> more<00:23:20.039> trying<00:23:20.220> to 00:23:20.330 --> 00:23:20.340 align:start position:0% regards to call I'm more trying to 00:23:20.340 --> 00:23:22.549 align:start position:0% regards to call I'm more trying to gesture<00:23:20.640> towards<00:23:21.000> the<00:23:21.240> idea<00:23:21.539> that<00:23:21.960> there<00:23:22.440> are 00:23:22.549 --> 00:23:22.559 align:start position:0% gesture towards the idea that there are 00:23:22.559 --> 00:23:24.830 align:start position:0% gesture towards the idea that there are people<00:23:22.679> working<00:23:23.100> on<00:23:23.640> enabling<00:23:24.360> lookup 00:23:24.830 --> 00:23:24.840 align:start position:0% people working on enabling lookup 00:23:24.840 --> 00:23:26.750 align:start position:0% people working on enabling lookup arguments<00:23:25.260> to<00:23:25.500> be<00:23:25.559> more<00:23:25.799> efficient<00:23:26.100> and<00:23:26.640> that 00:23:26.750 --> 00:23:26.760 align:start position:0% arguments to be more efficient and that 00:23:26.760 --> 00:23:28.789 align:start position:0% arguments to be more efficient and that that<00:23:26.940> would<00:23:27.120> really<00:23:27.299> transform<00:23:27.900> uh<00:23:28.500> how<00:23:28.679> we 00:23:28.789 --> 00:23:28.799 align:start position:0% that would really transform uh how we 00:23:28.799 --> 00:23:31.130 align:start position:0% that would really transform uh how we write<00:23:28.980> these<00:23:29.220> circuits<00:23:29.659> I<00:23:30.659> totally<00:23:30.960> agree 00:23:31.130 --> 00:23:31.140 align:start position:0% write these circuits I totally agree 00:23:31.140 --> 00:23:32.690 align:start position:0% write these circuits I totally agree that<00:23:31.320> they're<00:23:31.440> not<00:23:31.620> caulk<00:23:32.100> is<00:23:32.220> not<00:23:32.340> like<00:23:32.460> today 00:23:32.690 --> 00:23:32.700 align:start position:0% that they're not caulk is not like today 00:23:32.700 --> 00:23:33.950 align:start position:0% that they're not caulk is not like today going<00:23:33.000> to<00:23:33.120> enable<00:23:33.240> much<00:23:33.539> more<00:23:33.659> efficient 00:23:33.950 --> 00:23:33.960 align:start position:0% going to enable much more efficient 00:23:33.960 --> 00:23:35.630 align:start position:0% going to enable much more efficient lookups 00:23:35.630 --> 00:23:35.640 align:start position:0% lookups 00:23:35.640 --> 00:23:37.850 align:start position:0% lookups while<00:23:36.240> the<00:23:36.419> music<00:23:36.539> is<00:23:36.720> coming<00:23:36.960> I<00:23:37.380> guess<00:23:37.559> we're 00:23:37.850 --> 00:23:37.860 align:start position:0% while the music is coming I guess we're 00:23:37.860 --> 00:23:39.950 align:start position:0% while the music is coming I guess we're coming<00:23:38.100> to<00:23:38.340> an<00:23:38.460> end 00:23:39.950 --> 00:23:39.960 align:start position:0% coming to an end 00:23:39.960 --> 00:23:42.110 align:start position:0% coming to an end uh<00:23:40.620> thank<00:23:40.799> you<00:23:40.860> so<00:23:40.980> much<00:23:41.100> speaker<00:23:41.400> of<00:23:41.700> Applause 00:23:42.110 --> 00:23:42.120 align:start position:0% uh thank you so much speaker of Applause 00:23:42.120 --> 00:23:45.500 align:start position:0% uh thank you so much speaker of Applause to<00:23:42.360> lakshman<00:23:42.900> and<00:23:43.140> Yi