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:11.750 align:start position:0% [Music] 00:00:11.750 --> 00:00:11.760 align:start position:0% 00:00:11.760 --> 00:00:16.550 align:start position:0% so<00:00:12.660> our<00:00:12.840> next<00:00:13.019> panel<00:00:13.559> is<00:00:13.980> on<00:00:14.219> dsls<00:00:15.120> and<00:00:15.240> IRS<00:00:15.839> for 00:00:16.550 --> 00:00:16.560 align:start position:0% so our next panel is on dsls and IRS for 00:00:16.560 --> 00:00:20.090 align:start position:0% so our next panel is on dsls and IRS for ZK<00:00:16.980> circuits<00:00:17.699> yeah<00:00:18.420> these<00:00:18.960> are<00:00:19.140> all 00:00:20.090 --> 00:00:20.100 align:start position:0% ZK circuits yeah these are all 00:00:20.100 --> 00:00:22.730 align:start position:0% ZK circuits yeah these are all um<00:00:20.160> implementers<00:00:20.880> and<00:00:21.119> authors<00:00:21.600> of<00:00:22.080> some<00:00:22.439> very 00:00:22.730 --> 00:00:22.740 align:start position:0% um implementers and authors of some very 00:00:22.740 --> 00:00:27.470 align:start position:0% um implementers and authors of some very popular<00:00:23.359> CK<00:00:24.359> dsls<00:00:25.140> and<00:00:25.199> IRS<00:00:26.060> and<00:00:27.060> so<00:00:27.300> today 00:00:27.470 --> 00:00:27.480 align:start position:0% popular CK dsls and IRS and so today 00:00:27.480 --> 00:00:30.170 align:start position:0% popular CK dsls and IRS and so today we're<00:00:27.840> gonna<00:00:28.019> get<00:00:28.320> together<00:00:28.560> and 00:00:30.170 --> 00:00:30.180 align:start position:0% we're gonna get together and 00:00:30.180 --> 00:00:33.170 align:start position:0% we're gonna get together and um I've<00:00:30.720> prepared<00:00:31.320> a<00:00:32.220> few<00:00:32.399> high-level 00:00:33.170 --> 00:00:33.180 align:start position:0% um I've prepared a few high-level 00:00:33.180 --> 00:00:35.450 align:start position:0% um I've prepared a few high-level questions<00:00:33.600> here<00:00:34.200> I'm<00:00:34.800> going<00:00:34.980> to<00:00:35.160> read<00:00:35.280> them 00:00:35.450 --> 00:00:35.460 align:start position:0% questions here I'm going to read them 00:00:35.460 --> 00:00:36.170 align:start position:0% questions here I'm going to read them out 00:00:36.170 --> 00:00:36.180 align:start position:0% out 00:00:36.180 --> 00:00:38.870 align:start position:0% out um so<00:00:36.719> the<00:00:36.960> first<00:00:37.140> one<00:00:37.440> is<00:00:37.980> sort<00:00:38.520> of<00:00:38.700> an 00:00:38.870 --> 00:00:38.880 align:start position:0% um so the first one is sort of an 00:00:38.880 --> 00:00:41.690 align:start position:0% um so the first one is sort of an exercise<00:00:39.120> to<00:00:39.660> locate<00:00:40.200> each<00:00:40.559> other<00:00:40.800> on<00:00:41.520> the 00:00:41.690 --> 00:00:41.700 align:start position:0% exercise to locate each other on the 00:00:41.700 --> 00:00:44.389 align:start position:0% exercise to locate each other on the language<00:00:41.940> stack<00:00:42.540> and<00:00:42.780> see<00:00:43.079> how<00:00:43.440> we<00:00:43.980> relate<00:00:44.280> to 00:00:44.389 --> 00:00:44.399 align:start position:0% language stack and see how we relate to 00:00:44.399 --> 00:00:45.229 align:start position:0% language stack and see how we relate to each<00:00:44.579> other 00:00:45.229 --> 00:00:45.239 align:start position:0% each other 00:00:45.239 --> 00:00:47.930 align:start position:0% each other and<00:00:45.960> the<00:00:46.140> second<00:00:46.320> afterwards<00:00:47.280> is<00:00:47.520> to<00:00:47.760> then 00:00:47.930 --> 00:00:47.940 align:start position:0% and the second afterwards is to then 00:00:47.940 --> 00:00:50.510 align:start position:0% and the second afterwards is to then figure<00:00:48.239> out<00:00:49.200> um<00:00:49.200> to<00:00:49.500> what<00:00:49.739> extent<00:00:50.039> can<00:00:50.340> we 00:00:50.510 --> 00:00:50.520 align:start position:0% figure out um to what extent can we 00:00:50.520 --> 00:00:52.310 align:start position:0% figure out um to what extent can we share<00:00:50.760> infrastructure 00:00:52.310 --> 00:00:52.320 align:start position:0% share infrastructure 00:00:52.320 --> 00:00:55.430 align:start position:0% share infrastructure or<00:00:52.980> should<00:00:53.160> we<00:00:53.340> even<00:00:53.520> try<00:00:53.840> is<00:00:54.840> it<00:00:54.960> impossible 00:00:55.430 --> 00:00:55.440 align:start position:0% or should we even try is it impossible 00:00:55.440 --> 00:00:58.010 align:start position:0% or should we even try is it impossible after<00:00:55.920> a<00:00:56.160> certain<00:00:56.280> point 00:00:58.010 --> 00:00:58.020 align:start position:0% after a certain point 00:00:58.020 --> 00:01:00.889 align:start position:0% after a certain point um<00:00:58.140> and<00:00:58.680> over<00:00:58.860> here<00:00:59.219> I<00:00:59.399> want<00:00:59.579> to<00:00:59.699> note<00:00:59.879> also<00:01:00.480> a 00:01:00.889 --> 00:01:00.899 align:start position:0% um and over here I want to note also a 00:01:00.899 --> 00:01:03.470 align:start position:0% um and over here I want to note also a lot<00:01:00.960> of<00:01:01.079> Prior<00:01:01.320> work<00:01:01.620> from<00:01:02.039> the<00:01:02.579> compiler<00:01:03.180> and 00:01:03.470 --> 00:01:03.480 align:start position:0% lot of Prior work from the compiler and 00:01:03.480 --> 00:01:07.609 align:start position:0% lot of Prior work from the compiler and smt<00:01:04.100> verifier<00:01:05.299> communities<00:01:06.299> so<00:01:06.720> can<00:01:06.900> we<00:01:07.140> also 00:01:07.609 --> 00:01:07.619 align:start position:0% smt verifier communities so can we also 00:01:07.619 --> 00:01:10.969 align:start position:0% smt verifier communities so can we also reuse<00:01:08.580> some<00:01:08.820> of<00:01:08.939> their<00:01:09.119> work<00:01:09.380> and<00:01:10.380> then<00:01:10.500> lastly 00:01:10.969 --> 00:01:10.979 align:start position:0% reuse some of their work and then lastly 00:01:10.979 --> 00:01:14.270 align:start position:0% reuse some of their work and then lastly I<00:01:11.700> had<00:01:11.939> a<00:01:12.180> high<00:01:12.360> level<00:01:12.540> question<00:01:13.020> about 00:01:14.270 --> 00:01:14.280 align:start position:0% I had a high level question about 00:01:14.280 --> 00:01:16.370 align:start position:0% I had a high level question about you<00:01:14.820> know<00:01:15.000> what<00:01:15.240> programming<00:01:15.720> in<00:01:15.840> ZK<00:01:16.140> should 00:01:16.370 --> 00:01:16.380 align:start position:0% you know what programming in ZK should 00:01:16.380 --> 00:01:19.490 align:start position:0% you know what programming in ZK should look<00:01:16.560> like<00:01:16.740> what's<00:01:17.100> your<00:01:17.400> ideal<00:01:17.760> DSL<00:01:18.420> is<00:01:19.140> it 00:01:19.490 --> 00:01:19.500 align:start position:0% look like what's your ideal DSL is it 00:01:19.500 --> 00:01:21.590 align:start position:0% look like what's your ideal DSL is it very<00:01:20.100> different<00:01:20.340> from<00:01:20.640> normal<00:01:20.880> programming 00:01:21.590 --> 00:01:21.600 align:start position:0% very different from normal programming 00:01:21.600 --> 00:01:26.510 align:start position:0% very different from normal programming yeah<00:01:22.640> so<00:01:23.640> just<00:01:24.479> keep<00:01:24.780> these<00:01:25.200> in<00:01:25.560> your<00:01:25.740> head<00:01:25.979> and 00:01:26.510 --> 00:01:26.520 align:start position:0% yeah so just keep these in your head and 00:01:26.520 --> 00:01:29.210 align:start position:0% yeah so just keep these in your head and I<00:01:26.759> think<00:01:26.939> I<00:01:27.360> want<00:01:27.479> to<00:01:27.659> save<00:01:27.900> maybe<00:01:28.259> 25<00:01:28.680> minutes 00:01:29.210 --> 00:01:29.220 align:start position:0% I think I want to save maybe 25 minutes 00:01:29.220 --> 00:01:32.030 align:start position:0% I think I want to save maybe 25 minutes for<00:01:29.759> audience<00:01:30.479> questions<00:01:30.720> at<00:01:31.140> the<00:01:31.259> end 00:01:32.030 --> 00:01:32.040 align:start position:0% for audience questions at the end 00:01:32.040 --> 00:01:35.690 align:start position:0% for audience questions at the end so<00:01:32.640> I<00:01:33.000> think<00:01:33.180> let's<00:01:34.140> start<00:01:34.439> with<00:01:34.799> a<00:01:35.040> round<00:01:35.220> of 00:01:35.690 --> 00:01:35.700 align:start position:0% so I think let's start with a round of 00:01:35.700 --> 00:01:37.490 align:start position:0% so I think let's start with a round of introductions 00:01:37.490 --> 00:01:37.500 align:start position:0% introductions 00:01:37.500 --> 00:01:38.090 align:start position:0% introductions um 00:01:38.090 --> 00:01:38.100 align:start position:0% um 00:01:38.100 --> 00:01:41.230 align:start position:0% um I<00:01:38.820> have<00:01:39.060> like<00:01:39.960> I<00:01:40.439> have 00:01:41.230 --> 00:01:41.240 align:start position:0% I have like I have 00:01:41.240 --> 00:01:45.230 align:start position:0% I have like I have pre-prepared<00:01:42.240> some<00:01:42.479> visuals<00:01:43.140> for<00:01:43.920> you 00:01:45.230 --> 00:01:45.240 align:start position:0% pre-prepared some visuals for you 00:01:45.240 --> 00:01:46.310 align:start position:0% pre-prepared some visuals for you um 00:01:46.310 --> 00:01:46.320 align:start position:0% um 00:01:46.320 --> 00:01:48.710 align:start position:0% um in<00:01:46.740> case<00:01:46.920> you<00:01:47.100> need<00:01:47.220> them<00:01:47.460> so<00:01:47.759> the<00:01:48.060> first<00:01:48.299> first 00:01:48.710 --> 00:01:48.720 align:start position:0% in case you need them so the first first 00:01:48.720 --> 00:01:52.429 align:start position:0% in case you need them so the first first one<00:01:49.079> is<00:01:49.439> pill<00:01:49.979> Jordy<00:01:50.820> so<00:01:51.060> can<00:01:51.299> you<00:01:51.479> give<00:01:51.659> us<00:01:51.899> an 00:01:52.429 --> 00:01:52.439 align:start position:0% one is pill Jordy so can you give us an 00:01:52.439 --> 00:01:55.749 align:start position:0% one is pill Jordy so can you give us an introduction<00:01:52.860> to<00:01:53.280> what<00:01:53.880> pill<00:01:54.119> is 00:01:55.749 --> 00:01:55.759 align:start position:0% introduction to what pill is 00:01:55.759 --> 00:01:58.490 align:start position:0% introduction to what pill is a<00:01:56.759> language<00:01:57.060> mainly<00:01:57.659> it's<00:01:57.960> Bill<00:01:58.200> means 00:01:58.490 --> 00:01:58.500 align:start position:0% a language mainly it's Bill means 00:01:58.500 --> 00:02:00.830 align:start position:0% a language mainly it's Bill means polynomial<00:01:58.920> identity<00:01:59.399> language<00:01:59.700> and<00:02:00.479> mainly 00:02:00.830 --> 00:02:00.840 align:start position:0% polynomial identity language and mainly 00:02:00.840 --> 00:02:03.649 align:start position:0% polynomial identity language and mainly what<00:02:01.079> it<00:02:01.200> is<00:02:01.320> is<00:02:01.560> when<00:02:01.740> you<00:02:01.920> define<00:02:02.100> a<00:02:02.659> circuit 00:02:03.649 --> 00:02:03.659 align:start position:0% what it is is when you define a circuit 00:02:03.659 --> 00:02:06.050 align:start position:0% what it is is when you define a circuit that's<00:02:03.960> based<00:02:04.439> on<00:02:04.560> polynomials<00:02:05.460> for<00:02:05.880> example 00:02:06.050 --> 00:02:06.060 align:start position:0% that's based on polynomials for example 00:02:06.060 --> 00:02:10.669 align:start position:0% that's based on polynomials for example a<00:02:06.299> Planck<00:02:06.719> is<00:02:06.780> an<00:02:06.960> example<00:02:07.200> of<00:02:07.520> a<00:02:08.520> way<00:02:08.819> of 00:02:10.669 --> 00:02:10.679 align:start position:0% a Planck is an example of a way of 00:02:10.679 --> 00:02:11.350 align:start position:0% a Planck is an example of a way of um 00:02:11.350 --> 00:02:11.360 align:start position:0% um 00:02:11.360 --> 00:02:14.330 align:start position:0% um circuit<00:02:12.360> that's<00:02:13.260> based<00:02:13.620> on<00:02:13.680> polynomials<00:02:14.220> but 00:02:14.330 --> 00:02:14.340 align:start position:0% circuit that's based on polynomials but 00:02:14.340 --> 00:02:16.490 align:start position:0% circuit that's based on polynomials but you<00:02:14.459> can<00:02:14.520> do<00:02:14.700> much<00:02:14.879> more<00:02:15.120> things<00:02:15.599> much<00:02:16.379> more 00:02:16.490 --> 00:02:16.500 align:start position:0% you can do much more things much more 00:02:16.500 --> 00:02:18.770 align:start position:0% you can do much more things much more complex<00:02:17.220> uh<00:02:17.940> that's<00:02:18.180> our<00:02:18.360> base<00:02:18.599> in 00:02:18.770 --> 00:02:18.780 align:start position:0% complex uh that's our base in 00:02:18.780 --> 00:02:20.630 align:start position:0% complex uh that's our base in polynomials<00:02:19.319> that<00:02:19.500> still<00:02:19.680> allows<00:02:20.220> you<00:02:20.340> to 00:02:20.630 --> 00:02:20.640 align:start position:0% polynomials that still allows you to 00:02:20.640 --> 00:02:22.850 align:start position:0% polynomials that still allows you to just<00:02:20.879> write<00:02:21.239> those<00:02:21.480> identities<00:02:21.900> and<00:02:22.379> then<00:02:22.500> out 00:02:22.850 --> 00:02:22.860 align:start position:0% just write those identities and then out 00:02:22.860 --> 00:02:24.470 align:start position:0% just write those identities and then out of<00:02:23.040> those<00:02:23.160> identities<00:02:23.580> just<00:02:23.879> build<00:02:24.060> the<00:02:24.239> proof 00:02:24.470 --> 00:02:24.480 align:start position:0% of those identities just build the proof 00:02:24.480 --> 00:02:25.850 align:start position:0% of those identities just build the proof automatically<00:02:24.900> the<00:02:25.140> same<00:02:25.260> way<00:02:25.440> that<00:02:25.620> you<00:02:25.739> do 00:02:25.850 --> 00:02:25.860 align:start position:0% automatically the same way that you do 00:02:25.860 --> 00:02:29.330 align:start position:0% automatically the same way that you do in<00:02:26.520> a<00:02:26.640> normal<00:02:27.140> uh<00:02:28.140> zero<00:02:28.680> knowledge<00:02:28.920> language 00:02:29.330 --> 00:02:29.340 align:start position:0% in a normal uh zero knowledge language 00:02:29.340 --> 00:02:31.250 align:start position:0% in a normal uh zero knowledge language the<00:02:29.640> same<00:02:29.760> way<00:02:29.879> that<00:02:30.000> you<00:02:30.120> did<00:02:30.300> in<00:02:30.480> circum<00:02:30.840> you 00:02:31.250 --> 00:02:31.260 align:start position:0% the same way that you did in circum you 00:02:31.260 --> 00:02:33.050 align:start position:0% the same way that you did in circum you can<00:02:31.319> do<00:02:31.500> it<00:02:31.620> in<00:02:31.800> peel<00:02:32.220> here<00:02:32.580> you<00:02:32.700> need<00:02:32.819> to<00:02:32.940> do 00:02:33.050 --> 00:02:33.060 align:start position:0% can do it in peel here you need to do 00:02:33.060 --> 00:02:35.150 align:start position:0% can do it in peel here you need to do something<00:02:33.239> else<00:02:33.480> because<00:02:33.840> you<00:02:34.140> need<00:02:34.260> to 00:02:35.150 --> 00:02:35.160 align:start position:0% something else because you need to 00:02:35.160 --> 00:02:37.850 align:start position:0% something else because you need to maybe<00:02:35.700> write<00:02:36.000> the<00:02:36.239> weakness<00:02:36.540> somehow<00:02:37.200> but 00:02:37.850 --> 00:02:37.860 align:start position:0% maybe write the weakness somehow but 00:02:37.860 --> 00:02:40.610 align:start position:0% maybe write the weakness somehow but it's<00:02:38.220> just<00:02:38.640> a<00:02:39.000> kind<00:02:39.420> of<00:02:39.540> abstraction<00:02:39.959> where 00:02:40.610 --> 00:02:40.620 align:start position:0% it's just a kind of abstraction where 00:02:40.620 --> 00:02:43.610 align:start position:0% it's just a kind of abstraction where you<00:02:40.860> can<00:02:40.980> just<00:02:41.280> focus<00:02:42.060> in<00:02:42.360> writing<00:02:42.900> what<00:02:43.440> are 00:02:43.610 --> 00:02:43.620 align:start position:0% you can just focus in writing what are 00:02:43.620 --> 00:02:45.770 align:start position:0% you can just focus in writing what are the<00:02:43.680> identities<00:02:44.160> uh<00:02:44.879> that<00:02:45.360> you<00:02:45.480> want<00:02:45.660> to 00:02:45.770 --> 00:02:45.780 align:start position:0% the identities uh that you want to 00:02:45.780 --> 00:02:46.790 align:start position:0% the identities uh that you want to fulfill 00:02:46.790 --> 00:02:46.800 align:start position:0% fulfill 00:02:46.800 --> 00:02:50.690 align:start position:0% fulfill and<00:02:47.700> yeah<00:02:48.300> this<00:02:49.140> is<00:02:49.260> mainly<00:02:49.500> what<00:02:49.680> Spiel<00:02:49.920> and 00:02:50.690 --> 00:02:50.700 align:start position:0% and yeah this is mainly what Spiel and 00:02:50.700 --> 00:02:55.430 align:start position:0% and yeah this is mainly what Spiel and Jordy<00:02:51.360> also<00:02:52.019> is<00:02:52.920> the<00:02:53.160> author<00:02:53.760> of<00:02:53.879> circom 00:02:55.430 --> 00:02:55.440 align:start position:0% Jordy also is the author of circom 00:02:55.440 --> 00:02:57.350 align:start position:0% Jordy also is the author of circom um<00:02:55.560> which<00:02:55.980> is<00:02:56.160> a<00:02:56.400> very<00:02:56.580> another<00:02:56.940> popular 00:02:57.350 --> 00:02:57.360 align:start position:0% um which is a very another popular 00:02:57.360 --> 00:02:59.930 align:start position:0% um which is a very another popular Library<00:02:57.780> so<00:02:58.140> how<00:02:58.440> does<00:02:58.620> pill<00:02:58.860> relate<00:02:59.760> to 00:02:59.930 --> 00:02:59.940 align:start position:0% Library so how does pill relate to 00:02:59.940 --> 00:03:00.890 align:start position:0% Library so how does pill relate to circom 00:03:00.890 --> 00:03:00.900 align:start position:0% circom 00:03:00.900 --> 00:03:04.610 align:start position:0% circom well<00:03:01.200> bill<00:03:01.560> is<00:03:01.860> for<00:03:02.340> polynomials<00:03:03.239> and<00:03:04.080> circuit 00:03:04.610 --> 00:03:04.620 align:start position:0% well bill is for polynomials and circuit 00:03:04.620 --> 00:03:08.030 align:start position:0% well bill is for polynomials and circuit is<00:03:04.860> more<00:03:05.220> for<00:03:05.640> uh<00:03:06.379> signals<00:03:07.379> you're<00:03:07.800> just 00:03:08.030 --> 00:03:08.040 align:start position:0% is more for uh signals you're just 00:03:08.040 --> 00:03:09.050 align:start position:0% is more for uh signals you're just working<00:03:08.220> we<00:03:08.459> are<00:03:08.580> not<00:03:08.700> working<00:03:08.819> with 00:03:09.050 --> 00:03:09.060 align:start position:0% working we are not working with 00:03:09.060 --> 00:03:10.430 align:start position:0% working we are not working with polynomials<00:03:09.599> at<00:03:09.720> all<00:03:09.900> you<00:03:10.019> are<00:03:10.200> just<00:03:10.260> building 00:03:10.430 --> 00:03:10.440 align:start position:0% polynomials at all you are just building 00:03:10.440 --> 00:03:11.630 align:start position:0% polynomials at all you are just building uh 00:03:11.630 --> 00:03:11.640 align:start position:0% uh 00:03:11.640 --> 00:03:13.850 align:start position:0% uh um<00:03:11.760> you<00:03:12.000> have<00:03:12.120> just<00:03:12.360> signals<00:03:13.319> and<00:03:13.500> you<00:03:13.680> just 00:03:13.850 --> 00:03:13.860 align:start position:0% um you have just signals and you just 00:03:13.860 --> 00:03:16.190 align:start position:0% um you have just signals and you just build<00:03:14.640> constraints<00:03:15.180> around<00:03:15.540> those<00:03:15.840> signals 00:03:16.190 --> 00:03:16.200 align:start position:0% build constraints around those signals 00:03:16.200 --> 00:03:19.670 align:start position:0% build constraints around those signals not<00:03:16.379> constraints<00:03:16.800> around<00:03:16.980> polynomials<00:03:18.239> so 00:03:19.670 --> 00:03:19.680 align:start position:0% not constraints around polynomials so 00:03:19.680 --> 00:03:23.149 align:start position:0% not constraints around polynomials so um the<00:03:19.980> idea<00:03:20.220> of<00:03:20.400> circum<00:03:21.000> is<00:03:21.720> uh<00:03:22.140> it's<00:03:22.800> circum 00:03:23.149 --> 00:03:23.159 align:start position:0% um the idea of circum is uh it's circum 00:03:23.159 --> 00:03:24.949 align:start position:0% um the idea of circum is uh it's circum is<00:03:23.280> a<00:03:23.459> low<00:03:23.580> level<00:03:23.760> language<00:03:24.060> because<00:03:24.420> you<00:03:24.840> can 00:03:24.949 --> 00:03:24.959 align:start position:0% is a low level language because you can 00:03:24.959 --> 00:03:28.309 align:start position:0% is a low level language because you can write<00:03:25.200> everything<00:03:25.620> every<00:03:26.220> every<00:03:26.840> uh<00:03:27.840> every 00:03:28.309 --> 00:03:28.319 align:start position:0% write everything every every uh every 00:03:28.319 --> 00:03:30.530 align:start position:0% write everything every every uh every circuit<00:03:29.159> you<00:03:29.400> can<00:03:29.519> write<00:03:29.700> it<00:03:29.940> in<00:03:30.120> circum 00:03:30.530 --> 00:03:30.540 align:start position:0% circuit you can write it in circum 00:03:30.540 --> 00:03:34.070 align:start position:0% circuit you can write it in circum circum<00:03:31.019> does<00:03:31.260> not<00:03:31.440> have<00:03:31.680> any<00:03:32.099> special<00:03:33.080> library 00:03:34.070 --> 00:03:34.080 align:start position:0% circum does not have any special library 00:03:34.080 --> 00:03:36.290 align:start position:0% circum does not have any special library right<00:03:34.680> it's<00:03:35.159> better<00:03:35.340> than<00:03:35.580> you<00:03:35.819> need<00:03:36.060> any 00:03:36.290 --> 00:03:36.300 align:start position:0% right it's better than you need any 00:03:36.300 --> 00:03:38.390 align:start position:0% right it's better than you need any plugin<00:03:36.840> special<00:03:37.379> so<00:03:37.680> all<00:03:37.800> the<00:03:37.980> circum<00:03:38.280> is 00:03:38.390 --> 00:03:38.400 align:start position:0% plugin special so all the circum is 00:03:38.400 --> 00:03:41.449 align:start position:0% plugin special so all the circum is rated<00:03:38.640> in<00:03:38.760> circum<00:03:39.120> so<00:03:39.360> it's<00:03:39.680> on<00:03:40.680> there<00:03:40.799> but<00:03:41.280> at 00:03:41.449 --> 00:03:41.459 align:start position:0% rated in circum so it's on there but at 00:03:41.459 --> 00:03:43.970 align:start position:0% rated in circum so it's on there but at the<00:03:41.580> same<00:03:41.700> time<00:03:41.879> is<00:03:42.239> a<00:03:43.080> high<00:03:43.500> level<00:03:43.680> language 00:03:43.970 --> 00:03:43.980 align:start position:0% the same time is a high level language 00:03:43.980 --> 00:03:45.830 align:start position:0% the same time is a high level language because<00:03:44.340> it<00:03:44.640> allows<00:03:44.940> you<00:03:45.000> connections<00:03:45.540> so<00:03:45.720> you 00:03:45.830 --> 00:03:45.840 align:start position:0% because it allows you connections so you 00:03:45.840 --> 00:03:47.570 align:start position:0% because it allows you connections so you can<00:03:45.900> have<00:03:46.080> you<00:03:46.200> have<00:03:46.379> blocks<00:03:46.860> and<00:03:47.220> and<00:03:47.340> then 00:03:47.570 --> 00:03:47.580 align:start position:0% can have you have blocks and and then 00:03:47.580 --> 00:03:49.369 align:start position:0% can have you have blocks and and then you<00:03:47.700> connect<00:03:47.879> blocks<00:03:48.299> even<00:03:48.599> small<00:03:48.959> blocks<00:03:49.260> you 00:03:49.369 --> 00:03:49.379 align:start position:0% you connect blocks even small blocks you 00:03:49.379 --> 00:03:51.110 align:start position:0% you connect blocks even small blocks you do<00:03:49.620> Big<00:03:49.739> Blocks<00:03:49.980> Big<00:03:50.220> Blocks<00:03:50.519> you<00:03:50.580> do<00:03:50.760> a<00:03:50.879> bigger 00:03:51.110 --> 00:03:51.120 align:start position:0% do Big Blocks Big Blocks you do a bigger 00:03:51.120 --> 00:03:53.630 align:start position:0% do Big Blocks Big Blocks you do a bigger blocks<00:03:51.480> and<00:03:52.200> so<00:03:52.500> in<00:03:52.860> this<00:03:52.980> sense<00:03:53.159> you<00:03:53.340> can<00:03:53.459> go 00:03:53.630 --> 00:03:53.640 align:start position:0% blocks and so in this sense you can go 00:03:53.640 --> 00:03:56.390 align:start position:0% blocks and so in this sense you can go all<00:03:53.819> the<00:03:53.940> way<00:03:54.000> down<00:03:54.239> and<00:03:55.140> on<00:03:55.260> the<00:03:55.379> way<00:03:55.440> up<00:03:55.680> uh<00:03:56.280> on 00:03:56.390 --> 00:03:56.400 align:start position:0% all the way down and on the way up uh on 00:03:56.400 --> 00:03:58.670 align:start position:0% all the way down and on the way up uh on circum<00:03:56.760> that's<00:03:56.879> why<00:03:57.060> it's<00:03:57.180> so<00:03:57.420> flexible<00:03:57.900> and 00:03:58.670 --> 00:03:58.680 align:start position:0% circum that's why it's so flexible and 00:03:58.680 --> 00:04:00.770 align:start position:0% circum that's why it's so flexible and then<00:03:58.799> it<00:03:58.980> connects<00:03:59.280> very<00:03:59.400> good<00:03:59.640> with<00:04:00.000> snark.js 00:04:00.770 --> 00:04:00.780 align:start position:0% then it connects very good with snark.js 00:04:00.780 --> 00:04:03.530 align:start position:0% then it connects very good with snark.js and<00:04:01.019> other<00:04:01.280> proving<00:04:02.280> systems<00:04:02.700> and<00:04:03.000> yeah<00:04:03.299> it 00:04:03.530 --> 00:04:03.540 align:start position:0% and other proving systems and yeah it 00:04:03.540 --> 00:04:05.509 align:start position:0% and other proving systems and yeah it has<00:04:03.720> been<00:04:03.900> there<00:04:04.080> for<00:04:04.379> years<00:04:04.920> has<00:04:05.340> been 00:04:05.509 --> 00:04:05.519 align:start position:0% has been there for years has been 00:04:05.519 --> 00:04:07.850 align:start position:0% has been there for years has been already<00:04:05.760> a<00:04:06.120> full<00:04:06.360> rebrite<00:04:06.840> we<00:04:07.200> now<00:04:07.379> introduce 00:04:07.850 --> 00:04:07.860 align:start position:0% already a full rebrite we now introduce 00:04:07.860 --> 00:04:11.509 align:start position:0% already a full rebrite we now introduce uh<00:04:08.340> introduced<00:04:09.239> uh<00:04:09.860> these<00:04:10.860> new<00:04:10.920> extensions<00:04:11.340> of 00:04:11.509 --> 00:04:11.519 align:start position:0% uh introduced uh these new extensions of 00:04:11.519 --> 00:04:14.170 align:start position:0% uh introduced uh these new extensions of the<00:04:11.700> language<00:04:11.819> it's<00:04:12.120> mainly<00:04:12.959> um<00:04:13.019> mainly<00:04:13.739> our 00:04:14.170 --> 00:04:14.180 align:start position:0% the language it's mainly um mainly our 00:04:14.180 --> 00:04:16.789 align:start position:0% the language it's mainly um mainly our Anonymous<00:04:15.180> templates<00:04:15.780> and<00:04:16.079> we<00:04:16.440> also<00:04:16.680> already 00:04:16.789 --> 00:04:16.799 align:start position:0% Anonymous templates and we also already 00:04:16.799 --> 00:04:19.789 align:start position:0% Anonymous templates and we also already are<00:04:17.160> adapting<00:04:17.639> to<00:04:17.820> Planck<00:04:18.440> circum<00:04:19.440> was<00:04:19.620> born 00:04:19.789 --> 00:04:19.799 align:start position:0% are adapting to Planck circum was born 00:04:19.799 --> 00:04:23.090 align:start position:0% are adapting to Planck circum was born in<00:04:19.979> Darwin<00:04:20.459> CS<00:04:20.820> era<00:04:21.720> okay<00:04:22.260> and<00:04:22.500> now<00:04:22.680> but<00:04:22.919> in 00:04:23.090 --> 00:04:23.100 align:start position:0% in Darwin CS era okay and now but in 00:04:23.100 --> 00:04:25.129 align:start position:0% in Darwin CS era okay and now but in Noble<00:04:23.400> works<00:04:23.699> perfectly<00:04:23.940> in<00:04:24.180> Planck<00:04:24.600> so<00:04:25.020> we 00:04:25.129 --> 00:04:25.139 align:start position:0% Noble works perfectly in Planck so we 00:04:25.139 --> 00:04:27.050 align:start position:0% Noble works perfectly in Planck so we have<00:04:25.320> also<00:04:25.620> custom<00:04:25.800> Gates<00:04:26.220> and<00:04:26.580> yeah<00:04:26.940> we're 00:04:27.050 --> 00:04:27.060 align:start position:0% have also custom Gates and yeah we're 00:04:27.060 --> 00:04:29.150 align:start position:0% have also custom Gates and yeah we're extending<00:04:27.600> uh<00:04:28.020> the<00:04:28.199> language<00:04:28.380> and<00:04:28.680> it's<00:04:28.979> a 00:04:29.150 --> 00:04:29.160 align:start position:0% extending uh the language and it's a 00:04:29.160 --> 00:04:31.249 align:start position:0% extending uh the language and it's a full<00:04:29.460> community<00:04:29.639> that's<00:04:30.060> working<00:04:30.300> on<00:04:30.540> there 00:04:31.249 --> 00:04:31.259 align:start position:0% full community that's working on there 00:04:31.259 --> 00:04:33.350 align:start position:0% full community that's working on there thanks<00:04:31.740> Jody<00:04:32.040> so<00:04:32.520> yeah<00:04:32.880> to<00:04:33.060> me<00:04:33.240> it's 00:04:33.350 --> 00:04:33.360 align:start position:0% thanks Jody so yeah to me it's 00:04:33.360 --> 00:04:34.969 align:start position:0% thanks Jody so yeah to me it's interesting<00:04:33.900> this 00:04:34.969 --> 00:04:34.979 align:start position:0% interesting this 00:04:34.979 --> 00:04:36.409 align:start position:0% interesting this um<00:04:35.040> distinction<00:04:35.460> between 00:04:36.409 --> 00:04:36.419 align:start position:0% um distinction between 00:04:36.419 --> 00:04:38.030 align:start position:0% um distinction between um<00:04:36.479> a<00:04:36.660> language<00:04:36.780> for<00:04:37.080> polynomials<00:04:37.860> versus 00:04:38.030 --> 00:04:38.040 align:start position:0% um a language for polynomials versus 00:04:38.040 --> 00:04:42.590 align:start position:0% um a language for polynomials versus first<00:04:38.460> signals<00:04:39.120> and<00:04:39.660> I'm<00:04:39.840> gonna<00:04:40.080> skip<00:04:40.560> to<00:04:41.600> Noir 00:04:42.590 --> 00:04:42.600 align:start position:0% first signals and I'm gonna skip to Noir 00:04:42.600 --> 00:04:46.070 align:start position:0% first signals and I'm gonna skip to Noir because<00:04:43.199> as<00:04:44.160> I<00:04:44.340> understand<00:04:44.520> it<00:04:44.940> nor<00:04:45.300> can 00:04:46.070 --> 00:04:46.080 align:start position:0% because as I understand it nor can 00:04:46.080 --> 00:04:51.530 align:start position:0% because as I understand it nor can Target<00:04:46.919> both<00:04:47.780> Planck<00:04:48.780> and<00:04:48.960> r1cs<00:04:49.680> and<00:04:50.520> air<00:04:51.120> and 00:04:51.530 --> 00:04:51.540 align:start position:0% Target both Planck and r1cs and air and 00:04:51.540 --> 00:04:54.469 align:start position:0% Target both Planck and r1cs and air and even<00:04:51.660> more<00:04:51.960> back<00:04:52.259> ends<00:04:52.680> so<00:04:53.040> Kev<00:04:53.940> what's<00:04:54.120> nor 00:04:54.469 --> 00:04:54.479 align:start position:0% even more back ends so Kev what's nor 00:04:54.479 --> 00:04:56.749 align:start position:0% even more back ends so Kev what's nor about 00:04:56.749 --> 00:04:56.759 align:start position:0% about 00:04:56.759 --> 00:05:00.290 align:start position:0% about um can<00:04:57.300> you<00:04:57.479> hear<00:04:57.540> me<00:04:57.740> yeah<00:04:58.740> so<00:04:58.979> Noir<00:04:59.400> is<00:04:59.639> a<00:04:59.940> lot 00:05:00.290 --> 00:05:00.300 align:start position:0% um can you hear me yeah so Noir is a lot 00:05:00.300 --> 00:05:02.749 align:start position:0% um can you hear me yeah so Noir is a lot more<00:05:00.479> high<00:05:00.660> level<00:05:00.919> uh<00:05:01.919> it<00:05:02.100> compiles<00:05:02.520> it 00:05:02.749 --> 00:05:02.759 align:start position:0% more high level uh it compiles it 00:05:02.759 --> 00:05:04.930 align:start position:0% more high level uh it compiles it compiles<00:05:03.120> down<00:05:03.240> to<00:05:03.419> something<00:05:03.720> called<00:05:03.960> a<00:05:04.139> Sear 00:05:04.930 --> 00:05:04.940 align:start position:0% compiles down to something called a Sear 00:05:04.940 --> 00:05:07.610 align:start position:0% compiles down to something called a Sear and<00:05:05.940> essentially<00:05:06.360> you<00:05:07.020> never<00:05:07.199> tell<00:05:07.440> the 00:05:07.610 --> 00:05:07.620 align:start position:0% and essentially you never tell the 00:05:07.620 --> 00:05:10.310 align:start position:0% and essentially you never tell the proving<00:05:07.919> system<00:05:08.220> how<00:05:08.759> to<00:05:08.940> do<00:05:09.060> something<00:05:09.320> you 00:05:10.310 --> 00:05:10.320 align:start position:0% proving system how to do something you 00:05:10.320 --> 00:05:12.710 align:start position:0% proving system how to do something you just<00:05:10.440> tell<00:05:10.560> it<00:05:10.740> what<00:05:11.040> you<00:05:11.160> want<00:05:11.280> to<00:05:11.400> do<00:05:11.600> so<00:05:12.600> for 00:05:12.710 --> 00:05:12.720 align:start position:0% just tell it what you want to do so for 00:05:12.720 --> 00:05:15.230 align:start position:0% just tell it what you want to do so for example<00:05:13.080> uh<00:05:13.800> if<00:05:13.979> you<00:05:14.100> want<00:05:14.160> to<00:05:14.280> do<00:05:14.340> a<00:05:14.400> char-256 00:05:15.230 --> 00:05:15.240 align:start position:0% example uh if you want to do a char-256 00:05:15.240 --> 00:05:17.570 align:start position:0% example uh if you want to do a char-256 uh<00:05:15.780> you<00:05:16.020> don't<00:05:16.139> tell<00:05:16.320> it<00:05:16.500> to<00:05:16.620> use<00:05:16.800> custom<00:05:17.100> Gates 00:05:17.570 --> 00:05:17.580 align:start position:0% uh you don't tell it to use custom Gates 00:05:17.580 --> 00:05:20.030 align:start position:0% uh you don't tell it to use custom Gates the<00:05:18.120> proving<00:05:18.479> system<00:05:18.720> just<00:05:19.020> decides<00:05:19.560> uh 00:05:20.030 --> 00:05:20.040 align:start position:0% the proving system just decides uh 00:05:20.040 --> 00:05:22.010 align:start position:0% the proving system just decides uh what's<00:05:20.280> the<00:05:20.460> best<00:05:20.580> way<00:05:20.759> to<00:05:20.940> do<00:05:21.060> it 00:05:22.010 --> 00:05:22.020 align:start position:0% what's the best way to do it 00:05:22.020 --> 00:05:24.170 align:start position:0% what's the best way to do it so<00:05:22.500> in<00:05:22.680> this<00:05:22.800> way<00:05:22.979> we're<00:05:23.220> sort<00:05:23.400> of<00:05:23.520> back-end 00:05:24.170 --> 00:05:24.180 align:start position:0% so in this way we're sort of back-end 00:05:24.180 --> 00:05:27.350 align:start position:0% so in this way we're sort of back-end agnostic<00:05:24.840> fully<00:05:25.639> so<00:05:26.639> for<00:05:26.820> example<00:05:27.000> you'll 00:05:27.350 --> 00:05:27.360 align:start position:0% agnostic fully so for example you'll 00:05:27.360 --> 00:05:29.629 align:start position:0% agnostic fully so for example you'll never<00:05:27.479> see<00:05:27.720> like<00:05:28.020> uh<00:05:28.440> custom<00:05:28.620> Gates<00:05:29.100> inside<00:05:29.340> of 00:05:29.629 --> 00:05:29.639 align:start position:0% never see like uh custom Gates inside of 00:05:29.639 --> 00:05:32.390 align:start position:0% never see like uh custom Gates inside of Noir<00:05:30.240> or<00:05:30.660> any<00:05:30.840> sort<00:05:31.020> of<00:05:31.139> that<00:05:31.320> syntax<00:05:31.740> or 00:05:32.390 --> 00:05:32.400 align:start position:0% Noir or any sort of that syntax or 00:05:32.400 --> 00:05:34.670 align:start position:0% Noir or any sort of that syntax or lookup<00:05:32.759> tables<00:05:33.240> you<00:05:33.780> might<00:05:33.900> see<00:05:34.020> maps<00:05:34.440> for 00:05:34.670 --> 00:05:34.680 align:start position:0% lookup tables you might see maps for 00:05:34.680 --> 00:05:35.749 align:start position:0% lookup tables you might see maps for example 00:05:35.749 --> 00:05:35.759 align:start position:0% example 00:05:35.759 --> 00:05:37.850 align:start position:0% example yeah<00:05:36.360> so<00:05:36.660> yeah 00:05:37.850 --> 00:05:37.860 align:start position:0% yeah so yeah 00:05:37.860 --> 00:05:39.650 align:start position:0% yeah so yeah cool 00:05:39.650 --> 00:05:39.660 align:start position:0% cool 00:05:39.660 --> 00:05:41.990 align:start position:0% cool um<00:05:39.780> I'll<00:05:40.680> just<00:05:40.860> go<00:05:41.100> around<00:05:41.220> I<00:05:41.639> have<00:05:41.759> questions 00:05:41.990 --> 00:05:42.000 align:start position:0% um I'll just go around I have questions 00:05:42.000 --> 00:05:45.529 align:start position:0% um I'll just go around I have questions I'll<00:05:42.720> just<00:05:42.840> go<00:05:43.020> around<00:05:43.139> the<00:05:43.500> intros<00:05:44.039> first 00:05:45.529 --> 00:05:45.539 align:start position:0% I'll just go around the intros first 00:05:45.539 --> 00:05:47.870 align:start position:0% I'll just go around the intros first um<00:05:45.600> so<00:05:46.380> this<00:05:46.740> is<00:05:46.860> the<00:05:47.160> picture<00:05:47.280> I<00:05:47.520> found<00:05:47.699> for 00:05:47.870 --> 00:05:47.880 align:start position:0% um so this is the picture I found for 00:05:47.880 --> 00:05:51.110 align:start position:0% um so this is the picture I found for Cairo<00:05:48.419> I<00:05:48.780> really<00:05:48.960> apologize<00:05:49.639> I'm<00:05:50.639> sure<00:05:50.880> that 00:05:51.110 --> 00:05:51.120 align:start position:0% Cairo I really apologize I'm sure that 00:05:51.120 --> 00:05:54.590 align:start position:0% Cairo I really apologize I'm sure that better<00:05:51.360> pictures<00:05:51.660> exist<00:05:52.380> but 00:05:54.590 --> 00:05:54.600 align:start position:0% better pictures exist but 00:05:54.600 --> 00:05:56.330 align:start position:0% better pictures exist but um this<00:05:55.320> is<00:05:55.440> the<00:05:55.560> best 00:05:56.330 --> 00:05:56.340 align:start position:0% um this is the best 00:05:56.340 --> 00:05:59.210 align:start position:0% um this is the best either<00:05:56.639> produced<00:05:57.180> 100 00:05:59.210 --> 00:05:59.220 align:start position:0% either produced 100 00:05:59.220 --> 00:06:02.930 align:start position:0% either produced 100 um<00:05:59.759> so<00:06:00.720> um<00:06:00.720> yeah<00:06:01.020> so<00:06:01.199> I<00:06:01.620> guess<00:06:01.740> Cairo<00:06:02.340> deferred 00:06:02.930 --> 00:06:02.940 align:start position:0% um so um yeah so I guess Cairo deferred 00:06:02.940 --> 00:06:05.930 align:start position:0% um so um yeah so I guess Cairo deferred to<00:06:03.360> um<00:06:03.440> to<00:06:04.440> some<00:06:04.560> extent<00:06:04.860> I<00:06:05.039> wouldn't<00:06:05.460> be<00:06:05.699> able 00:06:05.930 --> 00:06:05.940 align:start position:0% to um to some extent I wouldn't be able 00:06:05.940 --> 00:06:08.629 align:start position:0% to um to some extent I wouldn't be able to<00:06:06.060> actually<00:06:06.500> go<00:06:07.500> into<00:06:07.620> I<00:06:08.220> want<00:06:08.460> to<00:06:08.520> see 00:06:08.629 --> 00:06:08.639 align:start position:0% to actually go into I want to see 00:06:08.639 --> 00:06:10.070 align:start position:0% to actually go into I want to see friends<00:06:08.820> but<00:06:09.060> Carol<00:06:09.479> is<00:06:09.600> just<00:06:09.720> during 00:06:10.070 --> 00:06:10.080 align:start position:0% friends but Carol is just during 00:06:10.080 --> 00:06:12.529 align:start position:0% friends but Carol is just during complete<00:06:10.560> language<00:06:10.759> so<00:06:11.759> you<00:06:12.060> were<00:06:12.180> writing 00:06:12.529 --> 00:06:12.539 align:start position:0% complete language so you were writing 00:06:12.539 --> 00:06:13.550 align:start position:0% complete language so you were writing Cairo<00:06:12.840> you<00:06:12.960> were<00:06:13.080> the<00:06:13.199> same<00:06:13.259> way<00:06:13.380> you're 00:06:13.550 --> 00:06:13.560 align:start position:0% Cairo you were the same way you're 00:06:13.560 --> 00:06:15.469 align:start position:0% Cairo you were the same way you're writing<00:06:13.800> solidity<00:06:14.280> or<00:06:14.699> in<00:06:15.120> any<00:06:15.240> smart 00:06:15.469 --> 00:06:15.479 align:start position:0% writing solidity or in any smart 00:06:15.479 --> 00:06:16.850 align:start position:0% writing solidity or in any smart contract<00:06:15.780> language<00:06:16.080> that<00:06:16.259> you<00:06:16.440> can<00:06:16.560> think<00:06:16.680> of 00:06:16.850 --> 00:06:16.860 align:start position:0% contract language that you can think of 00:06:16.860 --> 00:06:20.330 align:start position:0% contract language that you can think of so<00:06:17.360> from<00:06:18.360> the<00:06:18.660> perspective<00:06:19.139> of<00:06:19.440> Cairo<00:06:20.039> you 00:06:20.330 --> 00:06:20.340 align:start position:0% so from the perspective of Cairo you 00:06:20.340 --> 00:06:22.010 align:start position:0% so from the perspective of Cairo you write<00:06:20.520> a<00:06:20.699> program<00:06:20.880> this<00:06:21.660> program<00:06:21.840> is 00:06:22.010 --> 00:06:22.020 align:start position:0% write a program this program is 00:06:22.020 --> 00:06:23.749 align:start position:0% write a program this program is completed<00:06:22.500> to<00:06:22.620> a<00:06:22.740> carabite<00:06:23.160> code<00:06:23.340> which<00:06:23.639> is 00:06:23.749 --> 00:06:23.759 align:start position:0% completed to a carabite code which is 00:06:23.759 --> 00:06:26.390 align:start position:0% completed to a carabite code which is run<00:06:24.120> into<00:06:24.300> the<00:06:24.479> Cairo<00:06:24.840> VM<00:06:25.139> and<00:06:25.380> prove<00:06:25.800> among 00:06:26.390 --> 00:06:26.400 align:start position:0% run into the Cairo VM and prove among 00:06:26.400 --> 00:06:27.890 align:start position:0% run into the Cairo VM and prove among all<00:06:26.580> the<00:06:26.759> programs<00:06:27.060> that<00:06:27.180> are<00:06:27.300> proven<00:06:27.539> within 00:06:27.890 --> 00:06:27.900 align:start position:0% all the programs that are proven within 00:06:27.900 --> 00:06:30.710 align:start position:0% all the programs that are proven within the<00:06:28.020> same<00:06:28.139> proof<00:06:28.639> so<00:06:29.639> in<00:06:30.060> that<00:06:30.180> sense<00:06:30.419> it's 00:06:30.710 --> 00:06:30.720 align:start position:0% the same proof so in that sense it's 00:06:30.720 --> 00:06:32.809 align:start position:0% the same proof so in that sense it's like<00:06:30.900> there<00:06:31.500> is<00:06:31.620> not<00:06:31.800> things<00:06:32.100> much<00:06:32.520> much 00:06:32.809 --> 00:06:32.819 align:start position:0% like there is not things much much 00:06:32.819 --> 00:06:34.909 align:start position:0% like there is not things much much difference<00:06:33.360> you<00:06:34.199> don't<00:06:34.380> have<00:06:34.500> things<00:06:34.740> in 00:06:34.909 --> 00:06:34.919 align:start position:0% difference you don't have things in 00:06:34.919 --> 00:06:35.990 align:start position:0% difference you don't have things in there<00:06:35.039> you<00:06:35.220> don't<00:06:35.340> have<00:06:35.400> lookups<00:06:35.819> you<00:06:35.880> just 00:06:35.990 --> 00:06:36.000 align:start position:0% there you don't have lookups you just 00:06:36.000 --> 00:06:37.909 align:start position:0% there you don't have lookups you just have<00:06:36.120> like 00:06:37.909 --> 00:06:37.919 align:start position:0% have like 00:06:37.919 --> 00:06:39.950 align:start position:0% have like um<00:06:37.979> you<00:06:38.220> know<00:06:38.280> programming<00:06:38.819> and<00:06:39.180> sometime<00:06:39.720> for 00:06:39.950 --> 00:06:39.960 align:start position:0% um you know programming and sometime for 00:06:39.960 --> 00:06:41.450 align:start position:0% um you know programming and sometime for some<00:06:40.080> operations<00:06:40.500> we<00:06:40.860> do<00:06:40.919> have<00:06:41.039> this<00:06:41.160> notion 00:06:41.450 --> 00:06:41.460 align:start position:0% some operations we do have this notion 00:06:41.460 --> 00:06:43.909 align:start position:0% some operations we do have this notion of<00:06:41.580> built-in<00:06:42.000> but<00:06:42.900> built-in<00:06:43.560> are<00:06:43.800> just 00:06:43.909 --> 00:06:43.919 align:start position:0% of built-in but built-in are just 00:06:43.919 --> 00:06:45.469 align:start position:0% of built-in but built-in are just something<00:06:44.100> you<00:06:44.400> call<00:06:44.580> as<00:06:44.940> part<00:06:45.360> of<00:06:45.419> the 00:06:45.469 --> 00:06:45.479 align:start position:0% something you call as part of the 00:06:45.479 --> 00:06:48.710 align:start position:0% something you call as part of the function 00:06:48.710 --> 00:06:48.720 align:start position:0% 00:06:48.720 --> 00:06:52.990 align:start position:0% and<00:06:49.440> the<00:06:49.620> best<00:06:50.160> for<00:06:50.460> last<00:06:51.199> kimchi<00:06:52.199> slash 00:06:52.990 --> 00:06:53.000 align:start position:0% and the best for last kimchi slash 00:06:53.000 --> 00:06:55.730 align:start position:0% and the best for last kimchi slash snarky<00:06:54.000> JS 00:06:55.730 --> 00:06:55.740 align:start position:0% snarky JS 00:06:55.740 --> 00:06:58.490 align:start position:0% snarky JS um<00:06:55.860> Brandon<00:06:56.400> hello 00:06:58.490 --> 00:06:58.500 align:start position:0% um Brandon hello 00:06:58.500 --> 00:07:02.990 align:start position:0% um Brandon hello um<00:06:58.620> thank<00:06:58.979> you<00:06:59.160> yes<00:06:59.639> uh<00:07:00.419> so<00:07:01.080> uh<00:07:01.919> this<00:07:02.220> is<00:07:02.280> snarky 00:07:02.990 --> 00:07:03.000 align:start position:0% um thank you yes uh so uh this is snarky 00:07:03.000 --> 00:07:06.050 align:start position:0% um thank you yes uh so uh this is snarky JS<00:07:03.539> with<00:07:03.900> a<00:07:04.080> Y<00:07:04.199> different<00:07:04.500> from<00:07:04.800> snark.js<00:07:05.520> had 00:07:06.050 --> 00:07:06.060 align:start position:0% JS with a Y different from snark.js had 00:07:06.060 --> 00:07:08.749 align:start position:0% JS with a Y different from snark.js had a<00:07:06.240> few<00:07:06.479> people<00:07:06.600> confused<00:07:07.259> this<00:07:07.800> week 00:07:08.749 --> 00:07:08.759 align:start position:0% a few people confused this week 00:07:08.759 --> 00:07:12.350 align:start position:0% a few people confused this week um<00:07:09.020> yeah<00:07:10.020> uh<00:07:10.380> you<00:07:10.500> know<00:07:10.620> name<00:07:10.979> name<00:07:11.580> might 00:07:12.350 --> 00:07:12.360 align:start position:0% um yeah uh you know name name might 00:07:12.360 --> 00:07:15.290 align:start position:0% um yeah uh you know name name might evolve<00:07:12.840> I<00:07:12.960> don't<00:07:13.080> know<00:07:13.680> um<00:07:13.800> so<00:07:14.639> uh<00:07:15.000> yeah<00:07:15.120> so 00:07:15.290 --> 00:07:15.300 align:start position:0% evolve I don't know um so uh yeah so 00:07:15.300 --> 00:07:17.210 align:start position:0% evolve I don't know um so uh yeah so kimchi<00:07:15.780> is<00:07:15.900> our<00:07:16.139> is<00:07:16.319> the<00:07:16.500> proof<00:07:16.740> system<00:07:16.919> that 00:07:17.210 --> 00:07:17.220 align:start position:0% kimchi is our is the proof system that 00:07:17.220 --> 00:07:19.909 align:start position:0% kimchi is our is the proof system that snarky<00:07:17.639> JS<00:07:17.940> is<00:07:18.120> built<00:07:18.300> on<00:07:18.419> top<00:07:18.539> of<00:07:18.660> uh<00:07:19.259> right 00:07:19.909 --> 00:07:19.919 align:start position:0% snarky JS is built on top of uh right 00:07:19.919 --> 00:07:20.629 align:start position:0% snarky JS is built on top of uh right now 00:07:20.629 --> 00:07:20.639 align:start position:0% now 00:07:20.639 --> 00:07:22.550 align:start position:0% now um<00:07:20.759> the<00:07:20.940> way<00:07:21.060> that<00:07:21.120> it's<00:07:21.300> built<00:07:21.599> we<00:07:21.780> can<00:07:22.020> plug 00:07:22.550 --> 00:07:22.560 align:start position:0% um the way that it's built we can plug 00:07:22.560 --> 00:07:23.930 align:start position:0% um the way that it's built we can plug into<00:07:22.740> other<00:07:22.979> proof<00:07:23.280> systems<00:07:23.580> we<00:07:23.699> just<00:07:23.819> haven't 00:07:23.930 --> 00:07:23.940 align:start position:0% into other proof systems we just haven't 00:07:23.940 --> 00:07:26.390 align:start position:0% into other proof systems we just haven't yet<00:07:24.720> um<00:07:24.780> kimchi<00:07:25.259> is<00:07:25.380> the<00:07:25.500> proof<00:07:25.740> system<00:07:25.860> that 00:07:26.390 --> 00:07:26.400 align:start position:0% yet um kimchi is the proof system that 00:07:26.400 --> 00:07:30.830 align:start position:0% yet um kimchi is the proof system that is<00:07:26.639> in<00:07:27.539> uh<00:07:27.900> Mina<00:07:28.199> or<00:07:28.560> well<00:07:28.860> in<00:07:29.340> in<00:07:30.120> the<00:07:30.479> test<00:07:30.599> net 00:07:30.830 --> 00:07:30.840 align:start position:0% is in uh Mina or well in in the test net 00:07:30.840 --> 00:07:34.249 align:start position:0% is in uh Mina or well in in the test net of<00:07:31.380> mina<00:07:32.160> that<00:07:32.699> will<00:07:32.880> be<00:07:33.120> hard<00:07:33.360> forked<00:07:33.900> pending 00:07:34.249 --> 00:07:34.259 align:start position:0% of mina that will be hard forked pending 00:07:34.259 --> 00:07:36.110 align:start position:0% of mina that will be hard forked pending Community<00:07:34.620> voting 00:07:36.110 --> 00:07:36.120 align:start position:0% Community voting 00:07:36.120 --> 00:07:39.110 align:start position:0% Community voting um<00:07:36.720> but<00:07:37.259> the<00:07:37.500> idea<00:07:37.740> is<00:07:37.919> I<00:07:38.160> mean<00:07:38.280> kimchi<00:07:38.880> is<00:07:39.000> a 00:07:39.110 --> 00:07:39.120 align:start position:0% um but the idea is I mean kimchi is a 00:07:39.120 --> 00:07:42.770 align:start position:0% um but the idea is I mean kimchi is a Planck<00:07:39.720> 15<00:07:39.960> type<00:07:40.860> proof<00:07:41.340> system<00:07:41.520> it<00:07:42.300> has<00:07:42.479> no 00:07:42.770 --> 00:07:42.780 align:start position:0% Planck 15 type proof system it has no 00:07:42.780 --> 00:07:47.749 align:start position:0% Planck 15 type proof system it has no trusted<00:07:43.199> setup<00:07:43.940> it's<00:07:44.940> Universal<00:07:45.599> uh<00:07:46.500> and<00:07:46.919> uh 00:07:47.749 --> 00:07:47.759 align:start position:0% trusted setup it's Universal uh and uh 00:07:47.759 --> 00:07:49.909 align:start position:0% trusted setup it's Universal uh and uh we<00:07:48.300> support<00:07:48.539> like<00:07:48.960> infinite<00:07:49.380> and<00:07:49.560> efficient 00:07:49.909 --> 00:07:49.919 align:start position:0% we support like infinite and efficient 00:07:49.919 --> 00:07:51.290 align:start position:0% we support like infinite and efficient recursion<00:07:50.340> which<00:07:50.580> is<00:07:50.639> important<00:07:50.880> for<00:07:51.000> mina 00:07:51.290 --> 00:07:51.300 align:start position:0% recursion which is important for mina 00:07:51.300 --> 00:07:53.390 align:start position:0% recursion which is important for mina this<00:07:51.840> is<00:07:51.960> sync<00:07:52.259> blockchain 00:07:53.390 --> 00:07:53.400 align:start position:0% this is sync blockchain 00:07:53.400 --> 00:07:55.189 align:start position:0% this is sync blockchain um<00:07:53.520> but<00:07:53.940> it<00:07:54.060> but<00:07:54.300> the<00:07:54.479> cool<00:07:54.599> thing<00:07:54.780> is<00:07:54.900> you<00:07:55.080> can 00:07:55.189 --> 00:07:55.199 align:start position:0% um but it but the cool thing is you can 00:07:55.199 --> 00:07:57.770 align:start position:0% um but it but the cool thing is you can also<00:07:55.380> use<00:07:55.560> this<00:07:55.740> proof<00:07:56.039> system<00:07:56.220> to<00:07:56.639> build<00:07:56.819> Uh 00:07:57.770 --> 00:07:57.780 align:start position:0% also use this proof system to build Uh 00:07:57.780 --> 00:08:00.469 align:start position:0% also use this proof system to build Uh custom<00:07:58.020> zkps<00:07:58.800> which<00:07:59.400> are<00:07:59.819> our<00:08:00.240> smart 00:08:00.469 --> 00:08:00.479 align:start position:0% custom zkps which are our smart 00:08:00.479 --> 00:08:02.330 align:start position:0% custom zkps which are our smart contracts<00:08:01.020> on<00:08:01.199> Mina 00:08:02.330 --> 00:08:02.340 align:start position:0% contracts on Mina 00:08:02.340 --> 00:08:05.749 align:start position:0% contracts on Mina um<00:08:02.819> and<00:08:03.599> uh<00:08:04.080> and<00:08:04.380> you<00:08:04.500> can<00:08:04.620> build<00:08:04.800> circuits 00:08:05.749 --> 00:08:05.759 align:start position:0% um and uh and you can build circuits 00:08:05.759 --> 00:08:09.710 align:start position:0% um and uh and you can build circuits outside<00:08:06.180> of<00:08:06.419> mina<00:08:06.660> as<00:08:06.900> well<00:08:07.080> so<00:08:07.919> uh<00:08:08.699> I<00:08:09.300> I<00:08:09.479> don't 00:08:09.710 --> 00:08:09.720 align:start position:0% outside of mina as well so uh I I don't 00:08:09.720 --> 00:08:10.790 align:start position:0% outside of mina as well so uh I I don't know<00:08:09.840> there's<00:08:09.960> not<00:08:10.139> much<00:08:10.259> in<00:08:10.380> this<00:08:10.500> picture<00:08:10.620> I 00:08:10.790 --> 00:08:10.800 align:start position:0% know there's not much in this picture I 00:08:10.800 --> 00:08:12.350 align:start position:0% know there's not much in this picture I want<00:08:10.919> to<00:08:10.979> explain<00:08:11.099> I<00:08:11.340> guess<00:08:11.460> the<00:08:11.639> the<00:08:11.819> one 00:08:12.350 --> 00:08:12.360 align:start position:0% want to explain I guess the the one 00:08:12.360 --> 00:08:14.270 align:start position:0% want to explain I guess the the one really<00:08:12.599> important<00:08:13.020> thing<00:08:13.199> about<00:08:13.380> snarky<00:08:13.919> JS 00:08:14.270 --> 00:08:14.280 align:start position:0% really important thing about snarky JS 00:08:14.280 --> 00:08:16.850 align:start position:0% really important thing about snarky JS you<00:08:14.699> can<00:08:14.819> see<00:08:14.880> on<00:08:15.060> the<00:08:15.240> top<00:08:15.360> left<00:08:15.539> there 00:08:16.850 --> 00:08:16.860 align:start position:0% you can see on the top left there 00:08:16.860 --> 00:08:18.770 align:start position:0% you can see on the top left there um<00:08:16.919> the<00:08:17.099> the<00:08:17.220> code<00:08:17.460> snippet 00:08:18.770 --> 00:08:18.780 align:start position:0% um the the code snippet 00:08:18.780 --> 00:08:21.830 align:start position:0% um the the code snippet um it<00:08:19.379> is<00:08:19.560> typescript<00:08:20.160> and<00:08:21.120> is<00:08:21.360> extremely 00:08:21.830 --> 00:08:21.840 align:start position:0% um it is typescript and is extremely 00:08:21.840 --> 00:08:23.629 align:start position:0% um it is typescript and is extremely high<00:08:22.020> level<00:08:22.199> language 00:08:23.629 --> 00:08:23.639 align:start position:0% high level language 00:08:23.639 --> 00:08:26.270 align:start position:0% high level language um<00:08:23.699> and<00:08:24.180> and<00:08:24.419> there's<00:08:24.780> this<00:08:25.259> sort<00:08:25.560> of 00:08:26.270 --> 00:08:26.280 align:start position:0% um and and there's this sort of 00:08:26.280 --> 00:08:29.029 align:start position:0% um and and there's this sort of uh<00:08:27.060> I<00:08:27.419> guess<00:08:27.539> there's<00:08:27.660> a<00:08:27.840> lot<00:08:27.960> of<00:08:28.080> reasons<00:08:28.500> why 00:08:29.029 --> 00:08:29.039 align:start position:0% uh I guess there's a lot of reasons why 00:08:29.039 --> 00:08:30.890 align:start position:0% uh I guess there's a lot of reasons why we<00:08:29.220> designed<00:08:29.580> it<00:08:29.699> the<00:08:29.819> way<00:08:29.940> we<00:08:30.060> did<00:08:30.180> I'll<00:08:30.780> just 00:08:30.890 --> 00:08:30.900 align:start position:0% we designed it the way we did I'll just 00:08:30.900 --> 00:08:33.170 align:start position:0% we designed it the way we did I'll just point<00:08:31.020> out<00:08:31.199> a<00:08:31.379> couple<00:08:31.500> things<00:08:31.800> one<00:08:32.580> is<00:08:32.820> we<00:08:33.060> get 00:08:33.170 --> 00:08:33.180 align:start position:0% point out a couple things one is we get 00:08:33.180 --> 00:08:34.550 align:start position:0% point out a couple things one is we get all<00:08:33.360> the<00:08:33.479> tooling<00:08:33.839> and<00:08:33.959> infrastructure<00:08:34.380> and 00:08:34.550 --> 00:08:34.560 align:start position:0% all the tooling and infrastructure and 00:08:34.560 --> 00:08:37.070 align:start position:0% all the tooling and infrastructure and ecosystem<00:08:34.979> that<00:08:35.339> comes<00:08:35.459> with<00:08:35.580> typescript 00:08:37.070 --> 00:08:37.080 align:start position:0% ecosystem that comes with typescript 00:08:37.080 --> 00:08:37.670 align:start position:0% ecosystem that comes with typescript um 00:08:37.670 --> 00:08:37.680 align:start position:0% um 00:08:37.680 --> 00:08:40.550 align:start position:0% um so<00:08:38.219> you<00:08:38.580> know<00:08:38.700> npm<00:08:39.360> is<00:08:39.539> great<00:08:39.719> vs<00:08:40.200> code<00:08:40.380> is 00:08:40.550 --> 00:08:40.560 align:start position:0% so you know npm is great vs code is 00:08:40.560 --> 00:08:42.709 align:start position:0% so you know npm is great vs code is great<00:08:40.680> all<00:08:40.979> the<00:08:41.159> Integrations<00:08:41.580> already<00:08:42.240> work 00:08:42.709 --> 00:08:42.719 align:start position:0% great all the Integrations already work 00:08:42.719 --> 00:08:44.209 align:start position:0% great all the Integrations already work and<00:08:42.959> are<00:08:43.140> good 00:08:44.209 --> 00:08:44.219 align:start position:0% and are good 00:08:44.219 --> 00:08:47.329 align:start position:0% and are good um and<00:08:44.940> uh<00:08:45.480> we<00:08:45.779> think<00:08:45.959> that<00:08:46.440> you<00:08:47.100> know<00:08:47.160> when 00:08:47.329 --> 00:08:47.339 align:start position:0% um and uh we think that you know when 00:08:47.339 --> 00:08:49.730 align:start position:0% um and uh we think that you know when people<00:08:47.519> are<00:08:47.760> writing<00:08:48.240> zero<00:08:49.200> knowledge<00:08:49.380> proofs 00:08:49.730 --> 00:08:49.740 align:start position:0% people are writing zero knowledge proofs 00:08:49.740 --> 00:08:52.610 align:start position:0% people are writing zero knowledge proofs or<00:08:50.519> writing<00:08:51.000> any<00:08:51.120> programs<00:08:51.600> like<00:08:52.019> the<00:08:52.440> model 00:08:52.610 --> 00:08:52.620 align:start position:0% or writing any programs like the model 00:08:52.620 --> 00:08:54.769 align:start position:0% or writing any programs like the model that<00:08:53.100> people<00:08:53.339> are<00:08:53.700> used<00:08:53.940> to<00:08:54.060> thinking<00:08:54.720> about 00:08:54.769 --> 00:08:54.779 align:start position:0% that people are used to thinking about 00:08:54.779 --> 00:08:57.350 align:start position:0% that people are used to thinking about computations<00:08:55.380> is<00:08:55.920> you<00:08:56.519> know<00:08:56.580> you<00:08:57.120> have<00:08:57.240> a 00:08:57.350 --> 00:08:57.360 align:start position:0% computations is you know you have a 00:08:57.360 --> 00:08:59.269 align:start position:0% computations is you know you have a function<00:08:57.660> it<00:08:58.140> takes<00:08:58.320> some<00:08:58.500> input<00:08:58.860> and<00:08:59.160> you 00:08:59.269 --> 00:08:59.279 align:start position:0% function it takes some input and you 00:08:59.279 --> 00:09:01.610 align:start position:0% function it takes some input and you produce<00:08:59.519> some<00:08:59.700> output<00:09:00.060> so<00:09:01.019> one<00:09:01.380> of<00:09:01.440> the<00:09:01.500> things 00:09:01.610 --> 00:09:01.620 align:start position:0% produce some output so one of the things 00:09:01.620 --> 00:09:04.070 align:start position:0% produce some output so one of the things that<00:09:01.740> snarky.js<00:09:02.399> does<00:09:02.640> is<00:09:03.060> it<00:09:03.540> lets<00:09:03.779> you<00:09:03.839> write 00:09:04.070 --> 00:09:04.080 align:start position:0% that snarky.js does is it lets you write 00:09:04.080 --> 00:09:07.430 align:start position:0% that snarky.js does is it lets you write your<00:09:04.760> computations<00:09:05.760> with<00:09:06.600> your<00:09:06.779> circuits<00:09:07.260> at 00:09:07.430 --> 00:09:07.440 align:start position:0% your computations with your circuits at 00:09:07.440 --> 00:09:10.009 align:start position:0% your computations with your circuits at the<00:09:07.560> same<00:09:07.680> time<00:09:07.940> and<00:09:08.940> the<00:09:09.300> output<00:09:09.600> of<00:09:09.839> those 00:09:10.009 --> 00:09:10.019 align:start position:0% the same time and the output of those 00:09:10.019 --> 00:09:11.990 align:start position:0% the same time and the output of those functions<00:09:10.500> gets<00:09:11.220> sort<00:09:11.279> of<00:09:11.399> fed<00:09:11.580> in<00:09:11.700> as<00:09:11.880> a 00:09:11.990 --> 00:09:12.000 align:start position:0% functions gets sort of fed in as a 00:09:12.000 --> 00:09:14.509 align:start position:0% functions gets sort of fed in as a public<00:09:12.120> input<00:09:12.540> automatically<00:09:13.200> for<00:09:13.440> you<00:09:13.560> so<00:09:14.160> in 00:09:14.509 --> 00:09:14.519 align:start position:0% public input automatically for you so in 00:09:14.519 --> 00:09:16.070 align:start position:0% public input automatically for you so in the<00:09:14.640> end<00:09:14.760> your<00:09:15.060> your<00:09:15.240> code<00:09:15.480> actually<00:09:15.720> looks 00:09:16.070 --> 00:09:16.080 align:start position:0% the end your your code actually looks 00:09:16.080 --> 00:09:19.870 align:start position:0% the end your your code actually looks like<00:09:16.200> normal<00:09:16.800> code<00:09:17.480> cool<00:09:18.480> thank<00:09:18.899> you 00:09:19.870 --> 00:09:19.880 align:start position:0% like normal code cool thank you 00:09:19.880 --> 00:09:23.690 align:start position:0% like normal code cool thank you so<00:09:20.880> I'm<00:09:21.600> gonna<00:09:21.839> start<00:09:22.260> with<00:09:22.680> an<00:09:23.040> opinionated 00:09:23.690 --> 00:09:23.700 align:start position:0% so I'm gonna start with an opinionated 00:09:23.700 --> 00:09:26.269 align:start position:0% so I'm gonna start with an opinionated question<00:09:24.560> which<00:09:25.560> is 00:09:26.269 --> 00:09:26.279 align:start position:0% question which is 00:09:26.279 --> 00:09:28.790 align:start position:0% question which is um what<00:09:26.640> is<00:09:26.820> what<00:09:27.480> do<00:09:27.600> you<00:09:27.720> think<00:09:27.839> of 00:09:28.790 --> 00:09:28.800 align:start position:0% um what is what do you think of 00:09:28.800 --> 00:09:29.389 align:start position:0% um what is what do you think of um 00:09:29.389 --> 00:09:29.399 align:start position:0% um 00:09:29.399 --> 00:09:32.630 align:start position:0% um intermediate<00:09:30.300> representations<00:09:30.899> so<00:09:31.640> what 00:09:32.630 --> 00:09:32.640 align:start position:0% intermediate representations so what 00:09:32.640 --> 00:09:35.930 align:start position:0% intermediate representations so what Cersei<00:09:33.300> is<00:09:33.839> this<00:09:34.500> project 00:09:35.930 --> 00:09:35.940 align:start position:0% Cersei is this project 00:09:35.940 --> 00:09:39.650 align:start position:0% Cersei is this project um<00:09:36.000> that's<00:09:36.420> inspired<00:09:37.080> very<00:09:37.380> much<00:09:37.500> by<00:09:37.860> llvm<00:09:38.660> and 00:09:39.650 --> 00:09:39.660 align:start position:0% um that's inspired very much by llvm and 00:09:39.660 --> 00:09:41.150 align:start position:0% um that's inspired very much by llvm and everyone's<00:09:40.140> turning<00:09:40.440> to<00:09:40.560> look<00:09:40.740> at<00:09:40.860> the<00:09:40.980> screen 00:09:41.150 --> 00:09:41.160 align:start position:0% everyone's turning to look at the screen 00:09:41.160 --> 00:09:45.889 align:start position:0% everyone's turning to look at the screen but<00:09:41.779> so<00:09:42.779> the<00:09:43.320> idea<00:09:43.740> behind<00:09:44.519> that<00:09:44.820> is<00:09:45.360> to<00:09:45.720> define 00:09:45.889 --> 00:09:45.899 align:start position:0% but so the idea behind that is to define 00:09:45.899 --> 00:09:50.210 align:start position:0% but so the idea behind that is to define a<00:09:46.620> common<00:09:47.060> standard<00:09:48.060> IR 00:09:50.210 --> 00:09:50.220 align:start position:0% a common standard IR 00:09:50.220 --> 00:09:52.850 align:start position:0% a common standard IR um<00:09:50.339> to<00:09:51.000> which<00:09:51.240> many<00:09:51.959> different<00:09:52.200> front<00:09:52.500> ends 00:09:52.850 --> 00:09:52.860 align:start position:0% um to which many different front ends 00:09:52.860 --> 00:09:56.030 align:start position:0% um to which many different front ends compile<00:09:53.279> and<00:09:54.060> from<00:09:54.360> which<00:09:54.660> many<00:09:55.080> backend<00:09:55.620> many 00:09:56.030 --> 00:09:56.040 align:start position:0% compile and from which many backend many 00:09:56.040 --> 00:09:58.610 align:start position:0% compile and from which many backend many different<00:09:56.220> back-ends<00:09:56.880> can<00:09:57.000> compile<00:09:57.420> so<00:09:58.200> how 00:09:58.610 --> 00:09:58.620 align:start position:0% different back-ends can compile so how 00:09:58.620 --> 00:10:01.250 align:start position:0% different back-ends can compile so how well<00:09:58.800> do<00:09:59.100> you<00:09:59.279> think<00:09:59.459> your<00:10:00.240> project<00:10:00.540> would<00:10:01.019> fit 00:10:01.250 --> 00:10:01.260 align:start position:0% well do you think your project would fit 00:10:01.260 --> 00:10:07.490 align:start position:0% well do you think your project would fit into<00:10:01.680> a<00:10:02.459> model<00:10:02.580> like<00:10:02.940> that 00:10:07.490 --> 00:10:07.500 align:start position:0% 00:10:07.500 --> 00:10:13.269 align:start position:0% okay<00:10:08.240> like<00:10:09.240> yeah 00:10:13.269 --> 00:10:13.279 align:start position:0% 00:10:13.279 --> 00:10:16.190 align:start position:0% okay<00:10:14.279> yeah<00:10:14.820> I'll<00:10:14.940> start<00:10:15.120> I<00:10:15.360> mean<00:10:15.480> yeah<00:10:15.720> so<00:10:15.899> so 00:10:16.190 --> 00:10:16.200 align:start position:0% okay yeah I'll start I mean yeah so so 00:10:16.200 --> 00:10:17.810 align:start position:0% okay yeah I'll start I mean yeah so so uh 00:10:17.810 --> 00:10:17.820 align:start position:0% uh 00:10:17.820 --> 00:10:20.810 align:start position:0% uh snarky<00:10:18.540> JS<00:10:18.899> is<00:10:19.620> like<00:10:19.920> I<00:10:20.100> said<00:10:20.220> like<00:10:20.459> super<00:10:20.580> high 00:10:20.810 --> 00:10:20.820 align:start position:0% snarky JS is like I said like super high 00:10:20.820 --> 00:10:21.769 align:start position:0% snarky JS is like I said like super high level 00:10:21.769 --> 00:10:21.779 align:start position:0% level 00:10:21.779 --> 00:10:23.690 align:start position:0% level um<00:10:21.899> and<00:10:22.260> right<00:10:22.620> now<00:10:22.740> it's<00:10:22.980> directly<00:10:23.339> connected 00:10:23.690 --> 00:10:23.700 align:start position:0% um and right now it's directly connected 00:10:23.700 --> 00:10:26.930 align:start position:0% um and right now it's directly connected to<00:10:23.880> kimchi<00:10:24.360> but<00:10:25.140> um<00:10:25.200> we<00:10:25.620> could<00:10:25.920> and<00:10:26.640> probably 00:10:26.930 --> 00:10:26.940 align:start position:0% to kimchi but um we could and probably 00:10:26.940 --> 00:10:29.269 align:start position:0% to kimchi but um we could and probably should<00:10:27.420> connect<00:10:28.260> to<00:10:28.560> some<00:10:28.800> intermediate 00:10:29.269 --> 00:10:29.279 align:start position:0% should connect to some intermediate 00:10:29.279 --> 00:10:32.329 align:start position:0% should connect to some intermediate representation<00:10:29.760> so<00:10:30.180> that<00:10:30.420> uh<00:10:31.320> we<00:10:31.740> can<00:10:31.920> you 00:10:32.329 --> 00:10:32.339 align:start position:0% representation so that uh we can you 00:10:32.339 --> 00:10:34.490 align:start position:0% representation so that uh we can you know<00:10:32.399> share<00:10:32.820> that<00:10:33.300> work<00:10:33.480> of<00:10:33.839> connecting<00:10:34.320> to 00:10:34.490 --> 00:10:34.500 align:start position:0% know share that work of connecting to 00:10:34.500 --> 00:10:36.230 align:start position:0% know share that work of connecting to custom<00:10:34.680> back-ends 00:10:36.230 --> 00:10:36.240 align:start position:0% custom back-ends 00:10:36.240 --> 00:10:39.530 align:start position:0% custom back-ends in<00:10:36.899> the<00:10:37.019> case<00:10:37.140> of<00:10:37.820> circum<00:10:38.820> actually<00:10:39.180> it 00:10:39.530 --> 00:10:39.540 align:start position:0% in the case of circum actually it 00:10:39.540 --> 00:10:41.410 align:start position:0% in the case of circum actually it exports<00:10:40.019> to<00:10:40.140> two<00:10:40.380> different<00:10:40.560> languages 00:10:41.410 --> 00:10:41.420 align:start position:0% exports to two different languages 00:10:41.420 --> 00:10:43.630 align:start position:0% exports to two different languages [Music] 00:10:43.630 --> 00:10:43.640 align:start position:0% [Music] 00:10:43.640 --> 00:10:46.130 align:start position:0% [Music] internally<00:10:44.640> it<00:10:45.000> has<00:10:45.180> an<00:10:45.480> intermediate 00:10:46.130 --> 00:10:46.140 align:start position:0% internally it has an intermediate 00:10:46.140 --> 00:10:48.889 align:start position:0% internally it has an intermediate representation<00:10:46.800> already<00:10:47.399> is<00:10:47.880> uh<00:10:48.300> second<00:10:48.600> one 00:10:48.889 --> 00:10:48.899 align:start position:0% representation already is uh second one 00:10:48.899 --> 00:10:51.410 align:start position:0% representation already is uh second one so<00:10:49.140> exporting<00:10:49.800> that<00:10:50.040> to<00:10:50.279> other<00:10:50.579> language<00:10:51.000> like 00:10:51.410 --> 00:10:51.420 align:start position:0% so exporting that to other language like 00:10:51.420 --> 00:10:54.170 align:start position:0% so exporting that to other language like rust<00:10:51.899> or<00:10:52.140> like<00:10:52.320> go<00:10:52.560> is<00:10:53.279> in<00:10:53.459> the<00:10:53.640> in<00:10:53.880> the<00:10:54.060> road 00:10:54.170 --> 00:10:54.180 align:start position:0% rust or like go is in the in the road 00:10:54.180 --> 00:10:57.350 align:start position:0% rust or like go is in the in the road map<00:10:54.500> and<00:10:55.500> uh<00:10:55.860> okay<00:10:56.160> exporting<00:10:56.700> to<00:10:56.820> maybe<00:10:57.000> some 00:10:57.350 --> 00:10:57.360 align:start position:0% map and uh okay exporting to maybe some 00:10:57.360 --> 00:10:59.449 align:start position:0% map and uh okay exporting to maybe some other<00:10:57.540> intermediate<00:10:58.140> representation<00:10:58.680> if<00:10:59.220> it 00:10:59.449 --> 00:10:59.459 align:start position:0% other intermediate representation if it 00:10:59.459 --> 00:11:03.290 align:start position:0% other intermediate representation if it looks<00:10:59.760> like<00:11:00.000> uh<00:11:00.540> good<00:11:00.959> enough<00:11:01.399> uh<00:11:02.399> that's<00:11:02.820> uh 00:11:03.290 --> 00:11:03.300 align:start position:0% looks like uh good enough uh that's uh 00:11:03.300 --> 00:11:05.630 align:start position:0% looks like uh good enough uh that's uh that<00:11:03.720> that<00:11:04.019> would<00:11:04.380> be<00:11:04.500> definitely<00:11:05.040> possible 00:11:05.630 --> 00:11:05.640 align:start position:0% that that would be definitely possible 00:11:05.640 --> 00:11:08.150 align:start position:0% that that would be definitely possible here<00:11:06.480> I'm<00:11:07.200> not<00:11:07.380> sure<00:11:07.620> about<00:11:07.920> the 00:11:08.150 --> 00:11:08.160 align:start position:0% here I'm not sure about the 00:11:08.160 --> 00:11:09.769 align:start position:0% here I'm not sure about the specification<00:11:08.579> I<00:11:08.760> have<00:11:08.940> not<00:11:09.060> read<00:11:09.240> it<00:11:09.420> yet<00:11:09.540> but 00:11:09.769 --> 00:11:09.779 align:start position:0% specification I have not read it yet but 00:11:09.779 --> 00:11:12.470 align:start position:0% specification I have not read it yet but for<00:11:09.959> example<00:11:10.140> there<00:11:10.440> are<00:11:10.560> things<00:11:10.800> that<00:11:11.480> how 00:11:12.470 --> 00:11:12.480 align:start position:0% for example there are things that how 00:11:12.480 --> 00:11:15.290 align:start position:0% for example there are things that how you<00:11:12.600> paralyze<00:11:13.200> uh<00:11:14.040> witness<00:11:14.279> computation<00:11:14.820> in 00:11:15.290 --> 00:11:15.300 align:start position:0% you paralyze uh witness computation in 00:11:15.300 --> 00:11:17.210 align:start position:0% you paralyze uh witness computation in circum<00:11:15.660> we<00:11:15.839> have<00:11:16.019> a<00:11:16.320> way<00:11:16.620> that<00:11:16.920> you<00:11:17.040> have 00:11:17.210 --> 00:11:17.220 align:start position:0% circum we have a way that you have 00:11:17.220 --> 00:11:18.470 align:start position:0% circum we have a way that you have different<00:11:17.399> components<00:11:17.880> because<00:11:18.060> there<00:11:18.300> are 00:11:18.470 --> 00:11:18.480 align:start position:0% different components because there are 00:11:18.480 --> 00:11:20.810 align:start position:0% different components because there are components<00:11:18.839> you<00:11:19.079> can<00:11:19.200> say<00:11:20.100> that<00:11:20.339> this 00:11:20.810 --> 00:11:20.820 align:start position:0% components you can say that this 00:11:20.820 --> 00:11:23.269 align:start position:0% components you can say that this component<00:11:21.120> this<00:11:21.300> company<00:11:21.480> is<00:11:21.839> is<00:11:22.260> can<00:11:22.980> be<00:11:23.100> run 00:11:23.269 --> 00:11:23.279 align:start position:0% component this company is is can be run 00:11:23.279 --> 00:11:24.710 align:start position:0% component this company is is can be run in<00:11:23.459> parallel<00:11:23.820> so<00:11:24.000> the<00:11:24.120> windows<00:11:24.420> computation 00:11:24.710 --> 00:11:24.720 align:start position:0% in parallel so the windows computation 00:11:24.720 --> 00:11:26.449 align:start position:0% in parallel so the windows computation can<00:11:24.959> be<00:11:25.019> run<00:11:25.320> in<00:11:25.500> parallel<00:11:25.860> this<00:11:26.160> is<00:11:26.339> very 00:11:26.449 --> 00:11:26.459 align:start position:0% can be run in parallel this is very 00:11:26.459 --> 00:11:27.470 align:start position:0% can be run in parallel this is very important<00:11:26.700> especially<00:11:27.000> when<00:11:27.180> you<00:11:27.300> are<00:11:27.360> doing 00:11:27.470 --> 00:11:27.480 align:start position:0% important especially when you are doing 00:11:27.480 --> 00:11:31.370 align:start position:0% important especially when you are doing big<00:11:27.660> circuits<00:11:28.140> so<00:11:28.920> uh<00:11:29.880> you<00:11:30.420> know<00:11:30.540> I'm<00:11:31.079> not<00:11:31.200> sure 00:11:31.370 --> 00:11:31.380 align:start position:0% big circuits so uh you know I'm not sure 00:11:31.380 --> 00:11:33.110 align:start position:0% big circuits so uh you know I'm not sure maybe<00:11:31.740> some<00:11:32.100> somebody<00:11:32.279> that's<00:11:32.640> explained 00:11:33.110 --> 00:11:33.120 align:start position:0% maybe some somebody that's explained 00:11:33.120 --> 00:11:34.910 align:start position:0% maybe some somebody that's explained that<00:11:33.240> would<00:11:33.480> that<00:11:34.200> would<00:11:34.320> be<00:11:34.440> maybe<00:11:34.560> an<00:11:34.740> answer 00:11:34.910 --> 00:11:34.920 align:start position:0% that would that would be maybe an answer 00:11:34.920 --> 00:11:37.790 align:start position:0% that would that would be maybe an answer for<00:11:35.100> for<00:11:35.279> them<00:11:35.760> but<00:11:36.000> they<00:11:36.300> uh<00:11:37.140> sometimes<00:11:37.620> there 00:11:37.790 --> 00:11:37.800 align:start position:0% for for them but they uh sometimes there 00:11:37.800 --> 00:11:40.550 align:start position:0% for for them but they uh sometimes there are<00:11:37.920> details<00:11:38.399> there<00:11:39.360> that<00:11:39.660> are<00:11:39.839> not<00:11:39.959> that<00:11:40.320> that 00:11:40.550 --> 00:11:40.560 align:start position:0% are details there that are not that that 00:11:40.560 --> 00:11:44.269 align:start position:0% are details there that are not that that easy 00:11:44.269 --> 00:11:44.279 align:start position:0% 00:11:44.279 --> 00:11:46.850 align:start position:0% so<00:11:44.760> in<00:11:44.940> the<00:11:45.180> context<00:11:45.480> of<00:11:45.720> Cairo 00:11:46.850 --> 00:11:46.860 align:start position:0% so in the context of Cairo 00:11:46.860 --> 00:11:49.610 align:start position:0% so in the context of Cairo um<00:11:47.399> so<00:11:47.820> it<00:11:48.000> won't<00:11:48.300> really<00:11:48.480> even<00:11:48.720> work 00:11:49.610 --> 00:11:49.620 align:start position:0% um so it won't really even work 00:11:49.620 --> 00:11:52.130 align:start position:0% um so it won't really even work um<00:11:49.680> I<00:11:49.860> mean<00:11:50.040> because<00:11:50.700> Cairo<00:11:51.420> as<00:11:51.779> of<00:11:51.959> now 00:11:52.130 --> 00:11:52.140 align:start position:0% um I mean because Cairo as of now 00:11:52.140 --> 00:11:53.990 align:start position:0% um I mean because Cairo as of now doesn't<00:11:52.500> have<00:11:52.680> internet<00:11:52.800> representation<00:11:53.519> and 00:11:53.990 --> 00:11:54.000 align:start position:0% doesn't have internet representation and 00:11:54.000 --> 00:11:57.170 align:start position:0% doesn't have internet representation and directly<00:11:54.420> by<00:11:55.320> basically<00:11:55.680> just<00:11:55.920> a<00:11:56.160> very<00:11:56.760> high 00:11:57.170 --> 00:11:57.180 align:start position:0% directly by basically just a very high 00:11:57.180 --> 00:12:00.970 align:start position:0% directly by basically just a very high level<00:11:57.360> you<00:11:57.779> know<00:11:57.839> like<00:11:57.959> a<00:11:58.140> bit<00:11:58.260> like<00:11:58.440> Seas 00:12:00.970 --> 00:12:00.980 align:start position:0% 00:12:00.980 --> 00:12:03.350 align:start position:0% representation<00:12:01.980> just<00:12:02.220> like<00:12:02.459> compared<00:12:03.300> to 00:12:03.350 --> 00:12:03.360 align:start position:0% representation just like compared to 00:12:03.360 --> 00:12:06.710 align:start position:0% representation just like compared to assembly<00:12:03.720> and<00:12:04.560> Carol<00:12:05.160> itself<00:12:05.760> Carol<00:12:06.420> the 00:12:06.710 --> 00:12:06.720 align:start position:0% assembly and Carol itself Carol the 00:12:06.720 --> 00:12:08.210 align:start position:0% assembly and Carol itself Carol the current<00:12:06.899> version<00:12:07.140> at<00:12:07.560> least<00:12:07.680> to<00:12:07.860> just 00:12:08.210 --> 00:12:08.220 align:start position:0% current version at least to just 00:12:08.220 --> 00:12:10.730 align:start position:0% current version at least to just directly<00:12:08.459> generated<00:12:08.880> by<00:12:09.060> code<00:12:09.779> that<00:12:10.440> said 00:12:10.730 --> 00:12:10.740 align:start position:0% directly generated by code that said 00:12:10.740 --> 00:12:13.069 align:start position:0% directly generated by code that said Cairo<00:12:11.640> we<00:12:11.820> have<00:12:11.940> carrier<00:12:12.300> one<00:12:12.420> coming<00:12:12.660> in<00:12:12.899> a 00:12:13.069 --> 00:12:13.079 align:start position:0% Cairo we have carrier one coming in a 00:12:13.079 --> 00:12:16.430 align:start position:0% Cairo we have carrier one coming in a couple<00:12:13.140> of<00:12:13.700> months<00:12:14.700> uh<00:12:15.180> and<00:12:15.300> camera<00:12:15.480> one<00:12:15.839> has 00:12:16.430 --> 00:12:16.440 align:start position:0% couple of months uh and camera one has 00:12:16.440 --> 00:12:18.949 align:start position:0% couple of months uh and camera one has don't<00:12:17.100> have<00:12:17.459> something<00:12:17.760> called<00:12:18.060> Sierra<00:12:18.540> and 00:12:18.949 --> 00:12:18.959 align:start position:0% don't have something called Sierra and 00:12:18.959 --> 00:12:21.110 align:start position:0% don't have something called Sierra and Sierra<00:12:19.380> is<00:12:19.560> within<00:12:20.100> literally<00:12:20.519> means<00:12:20.940> safe 00:12:21.110 --> 00:12:21.120 align:start position:0% Sierra is within literally means safe 00:12:21.120 --> 00:12:23.690 align:start position:0% Sierra is within literally means safe intimate<00:12:21.839> representation<00:12:22.320> and<00:12:23.279> the<00:12:23.399> purpose 00:12:23.690 --> 00:12:23.700 align:start position:0% intimate representation and the purpose 00:12:23.700 --> 00:12:27.110 align:start position:0% intimate representation and the purpose of<00:12:23.880> Sierra<00:12:24.360> is<00:12:24.720> to<00:12:25.079> enable<00:12:25.640> uh<00:12:26.640> the<00:12:26.940> language 00:12:27.110 --> 00:12:27.120 align:start position:0% of Sierra is to enable uh the language 00:12:27.120 --> 00:12:29.690 align:start position:0% of Sierra is to enable uh the language to<00:12:27.720> turn<00:12:28.019> deterministic<00:12:28.740> actually<00:12:28.920> so<00:12:29.339> Caro 00:12:29.690 --> 00:12:29.700 align:start position:0% to turn deterministic actually so Caro 00:12:29.700 --> 00:12:31.790 align:start position:0% to turn deterministic actually so Caro is<00:12:29.820> not<00:12:29.940> deterministic<00:12:30.480> but<00:12:30.660> Sarah<00:12:31.140> will<00:12:31.620> make 00:12:31.790 --> 00:12:31.800 align:start position:0% is not deterministic but Sarah will make 00:12:31.800 --> 00:12:34.130 align:start position:0% is not deterministic but Sarah will make it<00:12:31.920> deeper<00:12:32.220> Mystic<00:12:32.519> because<00:12:32.700> when<00:12:33.180> you<00:12:33.420> make<00:12:33.959> a 00:12:34.130 --> 00:12:34.140 align:start position:0% it deeper Mystic because when you make a 00:12:34.140 --> 00:12:36.829 align:start position:0% it deeper Mystic because when you make a language<00:12:34.380> for<00:12:34.860> an<00:12:35.160> L1<00:12:35.519> or<00:12:35.700> two<00:12:36.480> four<00:12:36.660> four 00:12:36.829 --> 00:12:36.839 align:start position:0% language for an L1 or two four four 00:12:36.839 --> 00:12:38.090 align:start position:0% language for an L1 or two four four blockchain<00:12:37.440> itself<00:12:37.680> if<00:12:37.860> you<00:12:37.980> want 00:12:38.090 --> 00:12:38.100 align:start position:0% blockchain itself if you want 00:12:38.100 --> 00:12:39.829 align:start position:0% blockchain itself if you want determinism<00:12:38.519> you<00:12:38.940> want<00:12:39.060> determinism<00:12:39.480> for<00:12:39.779> a 00:12:39.829 --> 00:12:39.839 align:start position:0% determinism you want determinism for a 00:12:39.839 --> 00:12:41.630 align:start position:0% determinism you want determinism for a very<00:12:39.959> specific<00:12:40.079> reason<00:12:40.560> actually<00:12:40.920> which<00:12:41.519> is 00:12:41.630 --> 00:12:41.640 align:start position:0% very specific reason actually which is 00:12:41.640 --> 00:12:43.190 align:start position:0% very specific reason actually which is you<00:12:41.820> want<00:12:42.000> to<00:12:42.060> be<00:12:42.240> able<00:12:42.420> to<00:12:42.540> prove<00:12:42.959> a<00:12:43.079> fair 00:12:43.190 --> 00:12:43.200 align:start position:0% you want to be able to prove a fair 00:12:43.200 --> 00:12:45.949 align:start position:0% you want to be able to prove a fair transactions<00:12:44.279> without<00:12:44.820> determinism<00:12:45.480> you 00:12:45.949 --> 00:12:45.959 align:start position:0% transactions without determinism you 00:12:45.959 --> 00:12:48.949 align:start position:0% transactions without determinism you screw<00:12:46.260> it<00:12:46.320> for<00:12:46.740> that<00:12:46.920> and<00:12:47.579> so<00:12:47.820> we<00:12:48.240> for<00:12:48.600> now<00:12:48.779> we 00:12:48.949 --> 00:12:48.959 align:start position:0% screw it for that and so we for now we 00:12:48.959 --> 00:12:51.470 align:start position:0% screw it for that and so we for now we don't<00:12:49.079> have<00:12:49.260> it<00:12:49.440> and<00:12:50.040> it<00:12:50.279> is<00:12:50.399> those<00:12:51.000> Vector 00:12:51.470 --> 00:12:51.480 align:start position:0% don't have it and it is those Vector 00:12:51.480 --> 00:12:54.110 align:start position:0% don't have it and it is those Vector that<00:12:52.139> we<00:12:52.260> control<00:12:52.440> by<00:12:52.860> making<00:12:53.339> by<00:12:53.639> right<00:12:53.940> now 00:12:54.110 --> 00:12:54.120 align:start position:0% that we control by making by right now 00:12:54.120 --> 00:12:55.490 align:start position:0% that we control by making by right now whitelisting<00:12:54.660> the<00:12:54.779> contract<00:12:55.079> but<00:12:55.260> tomorrow 00:12:55.490 --> 00:12:55.500 align:start position:0% whitelisting the contract but tomorrow 00:12:55.500 --> 00:12:56.930 align:start position:0% whitelisting the contract but tomorrow when<00:12:55.860> we're<00:12:56.040> going<00:12:56.279> to<00:12:56.459> go<00:12:56.579> for 00:12:56.930 --> 00:12:56.940 align:start position:0% when we're going to go for 00:12:56.940 --> 00:12:58.069 align:start position:0% when we're going to go for permissionlessness<00:12:57.540> and<00:12:57.959> then 00:12:58.069 --> 00:12:58.079 align:start position:0% permissionlessness and then 00:12:58.079 --> 00:12:59.810 align:start position:0% permissionlessness and then centralization<00:12:58.860> you<00:12:59.100> can<00:12:59.220> obviously<00:12:59.519> do<00:12:59.700> that 00:12:59.810 --> 00:12:59.820 align:start position:0% centralization you can obviously do that 00:12:59.820 --> 00:13:02.690 align:start position:0% centralization you can obviously do that so<00:13:00.060> we<00:13:00.839> are<00:13:01.079> working<00:13:01.380> to<00:13:01.800> have<00:13:01.980> this<00:13:02.339> safe 00:13:02.690 --> 00:13:02.700 align:start position:0% so we are working to have this safe 00:13:02.700 --> 00:13:04.490 align:start position:0% so we are working to have this safe internet<00:13:03.060> presentation<00:13:03.779> which<00:13:04.200> will<00:13:04.320> be 00:13:04.490 --> 00:13:04.500 align:start position:0% internet presentation which will be 00:13:04.500 --> 00:13:07.370 align:start position:0% internet presentation which will be deterministic<00:13:05.100> and<00:13:06.060> this<00:13:06.480> the<00:13:06.959> intermediate 00:13:07.370 --> 00:13:07.380 align:start position:0% deterministic and this the intermediate 00:13:07.380 --> 00:13:09.230 align:start position:0% deterministic and this the intermediate step<00:13:07.560> will<00:13:08.040> be<00:13:08.160> able<00:13:08.339> to<00:13:08.459> actually<00:13:08.700> compile<00:13:09.060> to 00:13:09.230 --> 00:13:09.240 align:start position:0% step will be able to actually compile to 00:13:09.240 --> 00:13:11.569 align:start position:0% step will be able to actually compile to multiple<00:13:09.660> backend<00:13:10.019> so<00:13:10.260> either<00:13:10.680> Cabo<00:13:11.220> or<00:13:11.459> like 00:13:11.569 --> 00:13:11.579 align:start position:0% multiple backend so either Cabo or like 00:13:11.579 --> 00:13:14.269 align:start position:0% multiple backend so either Cabo or like an<00:13:11.820> optimize<00:13:12.240> for<00:13:12.420> xc6<00:13:13.019> for<00:13:13.320> execution<00:13:13.800> layer 00:13:14.269 --> 00:13:14.279 align:start position:0% an optimize for xc6 for execution layer 00:13:14.279 --> 00:13:16.850 align:start position:0% an optimize for xc6 for execution layer and<00:13:14.820> potentially<00:13:15.180> from<00:13:15.420> phoenixes<00:13:16.019> but<00:13:16.200> in 00:13:16.850 --> 00:13:16.860 align:start position:0% and potentially from phoenixes but in 00:13:16.860 --> 00:13:18.530 align:start position:0% and potentially from phoenixes but in that<00:13:16.980> case<00:13:17.160> we'll<00:13:17.639> probably<00:13:17.760> lose<00:13:18.060> most<00:13:18.420> of 00:13:18.530 --> 00:13:18.540 align:start position:0% that case we'll probably lose most of 00:13:18.540 --> 00:13:19.790 align:start position:0% that case we'll probably lose most of what<00:13:18.720> you're<00:13:18.899> gaining<00:13:19.200> and<00:13:19.320> what<00:13:19.500> you<00:13:19.620> wanted 00:13:19.790 --> 00:13:19.800 align:start position:0% what you're gaining and what you wanted 00:13:19.800 --> 00:13:22.370 align:start position:0% what you're gaining and what you wanted so<00:13:20.220> uh<00:13:20.880> I<00:13:21.060> I<00:13:21.180> don't<00:13:21.360> see<00:13:21.540> I<00:13:21.839> don't<00:13:21.899> know<00:13:22.019> if<00:13:22.139> it's 00:13:22.370 --> 00:13:22.380 align:start position:0% so uh I I don't see I don't know if it's 00:13:22.380 --> 00:13:24.590 align:start position:0% so uh I I don't see I don't know if it's practical<00:13:22.920> to<00:13:23.160> compile<00:13:23.639> for<00:13:23.880> I<00:13:24.120> I<00:13:24.240> don't<00:13:24.540> know 00:13:24.590 --> 00:13:24.600 align:start position:0% practical to compile for I I don't know 00:13:24.600 --> 00:13:26.150 align:start position:0% practical to compile for I I don't know about<00:13:24.720> Cersei<00:13:25.139> but<00:13:25.260> I<00:13:25.440> would<00:13:25.560> be<00:13:25.680> it's<00:13:25.860> a<00:13:26.040> great 00:13:26.150 --> 00:13:26.160 align:start position:0% about Cersei but I would be it's a great 00:13:26.160 --> 00:13:28.730 align:start position:0% about Cersei but I would be it's a great name<00:13:26.339> for<00:13:26.519> Stark<00:13:26.760> by<00:13:26.940> the<00:13:27.060> way<00:13:27.180> uh<00:13:28.079> but<00:13:28.320> uh<00:13:28.620> yeah 00:13:28.730 --> 00:13:28.740 align:start position:0% name for Stark by the way uh but uh yeah 00:13:28.740 --> 00:13:30.829 align:start position:0% name for Stark by the way uh but uh yeah I<00:13:28.920> don't<00:13:29.220> know<00:13:29.399> uh<00:13:29.820> I<00:13:30.180> don't<00:13:30.300> expect<00:13:30.480> so<00:13:30.720> I 00:13:30.829 --> 00:13:30.839 align:start position:0% I don't know uh I don't expect so I 00:13:30.839 --> 00:13:33.050 align:start position:0% I don't know uh I don't expect so I don't<00:13:30.899> know<00:13:30.959> if<00:13:31.079> you<00:13:31.200> could<00:13:31.320> do<00:13:31.440> that 00:13:33.050 --> 00:13:33.060 align:start position:0% don't know if you could do that 00:13:33.060 --> 00:13:36.410 align:start position:0% don't know if you could do that yeah<00:13:33.660> so<00:13:34.260> we<00:13:34.440> did<00:13:34.680> once<00:13:35.100> have<00:13:35.279> an<00:13:35.519> effort<00:13:35.940> to 00:13:36.410 --> 00:13:36.420 align:start position:0% yeah so we did once have an effort to 00:13:36.420 --> 00:13:39.710 align:start position:0% yeah so we did once have an effort to integrate<00:13:37.079> a<00:13:37.500> Seer<00:13:37.980> with<00:13:38.100> Cersei<00:13:38.760> uh<00:13:39.540> we 00:13:39.710 --> 00:13:39.720 align:start position:0% integrate a Seer with Cersei uh we 00:13:39.720 --> 00:13:42.170 align:start position:0% integrate a Seer with Cersei uh we dropped<00:13:40.019> it<00:13:40.139> just<00:13:40.260> due<00:13:40.500> to<00:13:40.680> priorities<00:13:41.180> uh 00:13:42.170 --> 00:13:42.180 align:start position:0% dropped it just due to priorities uh 00:13:42.180 --> 00:13:45.590 align:start position:0% dropped it just due to priorities uh from<00:13:42.420> what<00:13:42.540> I<00:13:42.660> remember<00:13:43.279> it<00:13:44.279> was<00:13:44.700> fairly<00:13:45.240> easy 00:13:45.590 --> 00:13:45.600 align:start position:0% from what I remember it was fairly easy 00:13:45.600 --> 00:13:48.530 align:start position:0% from what I remember it was fairly easy if<00:13:45.959> we<00:13:46.139> extend<00:13:46.500> Cersei<00:13:47.100> to<00:13:47.220> have<00:13:47.459> uh<00:13:48.060> these 00:13:48.530 --> 00:13:48.540 align:start position:0% if we extend Cersei to have uh these 00:13:48.540 --> 00:13:50.990 align:start position:0% if we extend Cersei to have uh these black<00:13:48.660> box<00:13:48.839> functions<00:13:49.500> uh<00:13:50.399> just<00:13:50.579> because<00:13:50.760> the 00:13:50.990 --> 00:13:51.000 align:start position:0% black box functions uh just because the 00:13:51.000 --> 00:13:54.290 align:start position:0% black box functions uh just because the Cersei<00:13:51.480> IR<00:13:51.600> just<00:13:51.959> can't<00:13:52.079> optimize<00:13:53.060> uh<00:13:54.060> for 00:13:54.290 --> 00:13:54.300 align:start position:0% Cersei IR just can't optimize uh for 00:13:54.300 --> 00:13:57.230 align:start position:0% Cersei IR just can't optimize uh for these<00:13:54.660> black<00:13:54.779> box<00:13:54.959> functions 00:13:57.230 --> 00:13:57.240 align:start position:0% these black box functions 00:13:57.240 --> 00:13:59.449 align:start position:0% these black box functions um<00:13:57.360> so<00:13:57.959> yeah<00:13:58.139> it's<00:13:58.320> possible<00:13:58.620> we<00:13:59.160> just<00:13:59.339> haven't 00:13:59.449 --> 00:13:59.459 align:start position:0% um so yeah it's possible we just haven't 00:13:59.459 --> 00:14:01.430 align:start position:0% um so yeah it's possible we just haven't picked<00:13:59.760> back<00:13:59.880> up<00:14:00.060> on<00:14:00.180> it 00:14:01.430 --> 00:14:01.440 align:start position:0% picked back up on it 00:14:01.440 --> 00:14:05.210 align:start position:0% picked back up on it yeah<00:14:02.100> I<00:14:02.760> I<00:14:03.000> think<00:14:03.600> nor<00:14:04.019> is<00:14:04.560> probably<00:14:04.740> the 00:14:05.210 --> 00:14:05.220 align:start position:0% yeah I I think nor is probably the 00:14:05.220 --> 00:14:07.550 align:start position:0% yeah I I think nor is probably the newest<00:14:05.880> shiniest<00:14:06.360> language<00:14:06.720> like<00:14:07.139> it<00:14:07.320> just 00:14:07.550 --> 00:14:07.560 align:start position:0% newest shiniest language like it just 00:14:07.560 --> 00:14:10.069 align:start position:0% newest shiniest language like it just dropped<00:14:08.459> um<00:14:08.579> and<00:14:09.000> I'm<00:14:09.240> I<00:14:09.540> have<00:14:09.720> lots<00:14:10.019> of 00:14:10.069 --> 00:14:10.079 align:start position:0% dropped um and I'm I have lots of 00:14:10.079 --> 00:14:11.470 align:start position:0% dropped um and I'm I have lots of questions<00:14:10.260> about 00:14:11.470 --> 00:14:11.480 align:start position:0% questions about 00:14:11.480 --> 00:14:15.590 align:start position:0% questions about Acer<00:14:12.480> acir<00:14:13.440> is<00:14:14.040> noir's<00:14:15.000> intermediate 00:14:15.590 --> 00:14:15.600 align:start position:0% Acer acir is noir's intermediate 00:14:15.600 --> 00:14:17.870 align:start position:0% Acer acir is noir's intermediate representation<00:14:16.079> so 00:14:17.870 --> 00:14:17.880 align:start position:0% representation so 00:14:17.880 --> 00:14:22.610 align:start position:0% representation so it<00:14:18.480> can<00:14:18.600> compile<00:14:19.200> both<00:14:19.680> to<00:14:20.100> r1cs<00:14:21.060> and<00:14:21.360> Planck 00:14:22.610 --> 00:14:22.620 align:start position:0% it can compile both to r1cs and Planck 00:14:22.620 --> 00:14:25.610 align:start position:0% it can compile both to r1cs and Planck um<00:14:22.740> so<00:14:22.920> how<00:14:23.160> does<00:14:23.339> this<00:14:23.519> IR<00:14:23.760> capture<00:14:24.540> both<00:14:25.380> of 00:14:25.610 --> 00:14:25.620 align:start position:0% um so how does this IR capture both of 00:14:25.620 --> 00:14:26.449 align:start position:0% um so how does this IR capture both of these 00:14:26.449 --> 00:14:26.459 align:start position:0% these 00:14:26.459 --> 00:14:30.350 align:start position:0% these um very<00:14:27.060> different<00:14:27.600> arithmetizations 00:14:30.350 --> 00:14:30.360 align:start position:0% um very different arithmetizations 00:14:30.360 --> 00:14:33.530 align:start position:0% um very different arithmetizations um<00:14:30.920> uh<00:14:31.920> essentially<00:14:32.399> you<00:14:33.240> have<00:14:33.360> these 00:14:33.530 --> 00:14:33.540 align:start position:0% um uh essentially you have these 00:14:33.540 --> 00:14:35.389 align:start position:0% um uh essentially you have these arithmetic<00:14:34.139> Gates<00:14:34.380> which<00:14:34.620> are<00:14:34.800> just<00:14:34.980> linear 00:14:35.389 --> 00:14:35.399 align:start position:0% arithmetic Gates which are just linear 00:14:35.399 --> 00:14:38.990 align:start position:0% arithmetic Gates which are just linear Expressions<00:14:35.820> which<00:14:36.779> aren't<00:14:36.959> bounded<00:14:37.820> so<00:14:38.820> for 00:14:38.990 --> 00:14:39.000 align:start position:0% Expressions which aren't bounded so for 00:14:39.000 --> 00:14:41.629 align:start position:0% Expressions which aren't bounded so for r1cs<00:14:39.660> that's<00:14:40.019> quite<00:14:40.320> simple<00:14:40.620> to<00:14:41.100> compile<00:14:41.459> down 00:14:41.629 --> 00:14:41.639 align:start position:0% r1cs that's quite simple to compile down 00:14:41.639 --> 00:14:43.730 align:start position:0% r1cs that's quite simple to compile down to<00:14:41.880> for<00:14:42.180> plunk<00:14:42.540> because<00:14:42.839> you<00:14:43.199> usually<00:14:43.560> have 00:14:43.730 --> 00:14:43.740 align:start position:0% to for plunk because you usually have 00:14:43.740 --> 00:14:48.230 align:start position:0% to for plunk because you usually have like<00:14:43.920> width<00:14:44.339> 4<00:14:44.519> or<00:14:45.060> some<00:14:45.560> uh<00:14:46.560> fixed<00:14:46.980> width<00:14:47.339> we 00:14:48.230 --> 00:14:48.240 align:start position:0% like width 4 or some uh fixed width we 00:14:48.240 --> 00:14:50.030 align:start position:0% like width 4 or some uh fixed width we have<00:14:48.360> something<00:14:48.540> in<00:14:48.779> a<00:14:48.899> sear<00:14:49.079> which<00:14:49.500> basically 00:14:50.030 --> 00:14:50.040 align:start position:0% have something in a sear which basically 00:14:50.040 --> 00:14:52.490 align:start position:0% have something in a sear which basically chops<00:14:50.519> the<00:14:50.639> gates<00:14:50.880> into<00:14:51.300> the<00:14:51.779> perfect<00:14:51.959> width 00:14:52.490 --> 00:14:52.500 align:start position:0% chops the gates into the perfect width 00:14:52.500 --> 00:14:55.670 align:start position:0% chops the gates into the perfect width for<00:14:52.860> a<00:14:53.040> blank<00:14:53.480> for<00:14:54.480> the<00:14:54.600> Black<00:14:54.839> Box<00:14:55.019> functions 00:14:55.670 --> 00:14:55.680 align:start position:0% for a blank for the Black Box functions 00:14:55.680 --> 00:14:58.870 align:start position:0% for a blank for the Black Box functions it's<00:14:56.639> really<00:14:56.880> just<00:14:57.180> the<00:14:57.480> proving<00:14:58.139> system<00:14:58.320> just 00:14:58.870 --> 00:14:58.880 align:start position:0% it's really just the proving system just 00:14:58.880 --> 00:15:01.370 align:start position:0% it's really just the proving system just takes<00:14:59.880> in<00:15:00.060> the<00:15:00.240> witness<00:15:00.420> indices<00:15:00.899> and<00:15:01.199> just 00:15:01.370 --> 00:15:01.380 align:start position:0% takes in the witness indices and just 00:15:01.380 --> 00:15:04.790 align:start position:0% takes in the witness indices and just fills<00:15:01.800> in<00:15:02.579> the<00:15:02.820> constraints<00:15:03.240> for<00:15:03.420> them<00:15:03.800> so 00:15:04.790 --> 00:15:04.800 align:start position:0% fills in the constraints for them so 00:15:04.800 --> 00:15:07.069 align:start position:0% fills in the constraints for them so it's<00:15:05.040> quite<00:15:05.519> simple<00:15:05.760> what<00:15:06.600> it's<00:15:06.720> doing<00:15:06.899> it's 00:15:07.069 --> 00:15:07.079 align:start position:0% it's quite simple what it's doing it's 00:15:07.079 --> 00:15:09.069 align:start position:0% it's quite simple what it's doing it's not<00:15:07.260> doing<00:15:07.380> anything<00:15:07.560> complicated 00:15:09.069 --> 00:15:09.079 align:start position:0% not doing anything complicated 00:15:09.079 --> 00:15:11.990 align:start position:0% not doing anything complicated yeah<00:15:10.079> that<00:15:10.320> makes<00:15:10.500> sense<00:15:10.740> Brandon<00:15:11.639> did<00:15:11.820> you 00:15:11.990 --> 00:15:12.000 align:start position:0% yeah that makes sense Brandon did you 00:15:12.000 --> 00:15:14.150 align:start position:0% yeah that makes sense Brandon did you have<00:15:12.180> thoughts<00:15:13.199> um 00:15:14.150 --> 00:15:14.160 align:start position:0% have thoughts um 00:15:14.160 --> 00:15:17.150 align:start position:0% have thoughts um on<00:15:14.639> the<00:15:14.760> IR<00:15:15.000> thing<00:15:15.420> yeah<00:15:16.079> well<00:15:16.320> I<00:15:16.500> I<00:15:16.620> think<00:15:16.980> I 00:15:17.150 --> 00:15:17.160 align:start position:0% on the IR thing yeah well I I think I 00:15:17.160 --> 00:15:19.069 align:start position:0% on the IR thing yeah well I I think I spoke<00:15:17.339> in<00:15:17.940> the<00:15:18.060> in<00:15:18.180> the<00:15:18.360> beginning<00:15:18.420> a<00:15:18.660> bit<00:15:18.779> I 00:15:19.069 --> 00:15:19.079 align:start position:0% spoke in the in the beginning a bit I 00:15:19.079 --> 00:15:21.410 align:start position:0% spoke in the in the beginning a bit I mean<00:15:19.199> yeah<00:15:19.800> I<00:15:20.220> I<00:15:20.399> guess 00:15:21.410 --> 00:15:21.420 align:start position:0% mean yeah I I guess 00:15:21.420 --> 00:15:23.389 align:start position:0% mean yeah I I guess yeah<00:15:21.540> I<00:15:21.959> don't<00:15:22.139> have<00:15:22.320> anything<00:15:22.500> else<00:15:22.680> to<00:15:22.800> add 00:15:23.389 --> 00:15:23.399 align:start position:0% yeah I don't have anything else to add 00:15:23.399 --> 00:15:24.949 align:start position:0% yeah I don't have anything else to add um<00:15:23.579> cool 00:15:24.949 --> 00:15:24.959 align:start position:0% um cool 00:15:24.959 --> 00:15:28.490 align:start position:0% um cool um<00:15:25.139> so<00:15:25.920> what<00:15:26.399> I'm<00:15:26.579> hearing<00:15:26.940> is<00:15:27.360> like<00:15:27.959> basically 00:15:28.490 --> 00:15:28.500 align:start position:0% um so what I'm hearing is like basically 00:15:28.500 --> 00:15:31.730 align:start position:0% um so what I'm hearing is like basically compiling<00:15:29.279> to<00:15:29.519> an<00:15:29.820> IR<00:15:30.180> you 00:15:31.730 --> 00:15:31.740 align:start position:0% compiling to an IR you 00:15:31.740 --> 00:15:35.030 align:start position:0% compiling to an IR you could<00:15:32.339> stand<00:15:32.639> to<00:15:32.940> lose<00:15:33.300> some 00:15:35.030 --> 00:15:35.040 align:start position:0% could stand to lose some 00:15:35.040 --> 00:15:35.689 align:start position:0% could stand to lose some um 00:15:35.689 --> 00:15:35.699 align:start position:0% um 00:15:35.699 --> 00:15:38.329 align:start position:0% um some<00:15:36.600> very<00:15:36.839> specific<00:15:37.339> performance 00:15:38.329 --> 00:15:38.339 align:start position:0% some very specific performance 00:15:38.339 --> 00:15:41.150 align:start position:0% some very specific performance optimizations<00:15:39.199> uh<00:15:40.199> unless<00:15:40.560> the<00:15:40.800> the<00:15:40.980> IR 00:15:41.150 --> 00:15:41.160 align:start position:0% optimizations uh unless the the IR 00:15:41.160 --> 00:15:44.150 align:start position:0% optimizations uh unless the the IR allows<00:15:41.699> you<00:15:41.760> to<00:15:41.940> Black<00:15:42.120> Box<00:15:42.420> things<00:15:42.839> easily 00:15:44.150 --> 00:15:44.160 align:start position:0% allows you to Black Box things easily 00:15:44.160 --> 00:15:45.490 align:start position:0% allows you to Black Box things easily cool 00:15:45.490 --> 00:15:45.500 align:start position:0% cool 00:15:45.500 --> 00:15:48.470 align:start position:0% cool I<00:15:46.500> don't<00:15:46.620> have<00:15:46.800> a<00:15:46.980> question<00:15:47.160> for<00:15:47.579> Louie<00:15:48.120> as 00:15:48.470 --> 00:15:48.480 align:start position:0% I don't have a question for Louie as 00:15:48.480 --> 00:15:50.629 align:start position:0% I don't have a question for Louie as well<00:15:48.600> what<00:15:48.959> do<00:15:49.079> you<00:15:49.199> mean<00:15:49.320> when<00:15:49.560> you<00:15:49.740> say<00:15:49.920> uh 00:15:50.629 --> 00:15:50.639 align:start position:0% well what do you mean when you say uh 00:15:50.639 --> 00:15:52.970 align:start position:0% well what do you mean when you say uh Cairo<00:15:51.120> is<00:15:51.300> not<00:15:51.540> deterministic<00:15:52.320> and<00:15:52.620> that<00:15:52.800> your 00:15:52.970 --> 00:15:52.980 align:start position:0% Cairo is not deterministic and that your 00:15:52.980 --> 00:15:56.629 align:start position:0% Cairo is not deterministic and that your IR<00:15:53.160> is<00:15:53.579> deterministic<00:15:54.300> so<00:15:54.660> so<00:15:55.040> Cairo<00:15:56.040> today<00:15:56.220> so 00:15:56.629 --> 00:15:56.639 align:start position:0% IR is deterministic so so Cairo today so 00:15:56.639 --> 00:16:00.110 align:start position:0% IR is deterministic so so Cairo today so proof<00:15:57.060> our<00:15:57.240> dkps<00:15:57.959> or<00:15:58.260> Language<00:15:58.699> basic<00:15:59.699> you<00:15:59.940> can 00:16:00.110 --> 00:16:00.120 align:start position:0% proof our dkps or Language basic you can 00:16:00.120 --> 00:16:03.470 align:start position:0% proof our dkps or Language basic you can create<00:16:00.540> hint<00:16:01.079> and<00:16:01.380> in<00:16:01.620> that<00:16:01.740> break<00:16:02.040> vitaminism 00:16:03.470 --> 00:16:03.480 align:start position:0% create hint and in that break vitaminism 00:16:03.480 --> 00:16:06.650 align:start position:0% create hint and in that break vitaminism um<00:16:03.540> but<00:16:04.160> we<00:16:05.160> we<00:16:05.579> Carriage<00:16:06.060> there<00:16:06.360> is<00:16:06.540> not 00:16:06.650 --> 00:16:06.660 align:start position:0% um but we we Carriage there is not 00:16:06.660 --> 00:16:08.870 align:start position:0% um but we we Carriage there is not domestic<00:16:07.199> so<00:16:07.500> for<00:16:07.980> men<00:16:08.160> to<00:16:08.339> be<00:16:08.399> more<00:16:08.579> specific 00:16:08.870 --> 00:16:08.880 align:start position:0% domestic so for men to be more specific 00:16:08.880 --> 00:16:10.970 align:start position:0% domestic so for men to be more specific we<00:16:09.240> actually<00:16:09.360> have<00:16:09.540> two<00:16:09.779> flavors<00:16:10.199> of<00:16:10.320> Cairo<00:16:10.740> uh 00:16:10.970 --> 00:16:10.980 align:start position:0% we actually have two flavors of Cairo uh 00:16:10.980 --> 00:16:12.590 align:start position:0% we actually have two flavors of Cairo uh what<00:16:11.220> we<00:16:11.399> like<00:16:11.579> what<00:16:11.820> I<00:16:11.940> like<00:16:12.000> to<00:16:12.180> call<00:16:12.300> Pure 00:16:12.590 --> 00:16:12.600 align:start position:0% what we like what I like to call Pure 00:16:12.600 --> 00:16:14.269 align:start position:0% what we like what I like to call Pure Caro<00:16:13.079> which<00:16:13.440> is<00:16:13.560> the<00:16:13.680> one<00:16:13.860> you<00:16:13.980> would<00:16:14.100> just 00:16:14.269 --> 00:16:14.279 align:start position:0% Caro which is the one you would just 00:16:14.279 --> 00:16:16.490 align:start position:0% Caro which is the one you would just directly<00:16:14.639> prove<00:16:15.060> a<00:16:15.180> program<00:16:15.420> within<00:16:15.959> within 00:16:16.490 --> 00:16:16.500 align:start position:0% directly prove a program within within 00:16:16.500 --> 00:16:18.410 align:start position:0% directly prove a program within within sharp<00:16:16.860> or<00:16:17.100> sharp<00:16:17.579> being<00:16:17.699> the<00:16:17.880> shareproof 00:16:18.410 --> 00:16:18.420 align:start position:0% sharp or sharp being the shareproof 00:16:18.420 --> 00:16:21.590 align:start position:0% sharp or sharp being the shareproof infrastructure<00:16:19.260> that<00:16:19.440> we<00:16:19.560> provide<00:16:19.860> or 00:16:21.590 --> 00:16:21.600 align:start position:0% infrastructure that we provide or 00:16:21.600 --> 00:16:24.170 align:start position:0% infrastructure that we provide or um<00:16:21.660> or<00:16:22.440> um<00:16:22.500> that's<00:16:23.040> your<00:16:23.220> pure<00:16:23.459> Caro<00:16:23.880> and 00:16:24.170 --> 00:16:24.180 align:start position:0% um or um that's your pure Caro and 00:16:24.180 --> 00:16:26.090 align:start position:0% um or um that's your pure Caro and what's<00:16:24.360> dark<00:16:24.540> X<00:16:24.720> is<00:16:24.959> star<00:16:25.260> X<00:16:25.440> is<00:16:25.620> built<00:16:25.860> on<00:16:25.920> and 00:16:26.090 --> 00:16:26.100 align:start position:0% what's dark X is star X is built on and 00:16:26.100 --> 00:16:29.030 align:start position:0% what's dark X is star X is built on and even<00:16:26.279> Stark<00:16:26.519> net<00:16:26.760> itself<00:16:27.120> is<00:16:27.360> built<00:16:27.959> with<00:16:28.079> and 00:16:29.030 --> 00:16:29.040 align:start position:0% even Stark net itself is built with and 00:16:29.040 --> 00:16:31.129 align:start position:0% even Stark net itself is built with and you<00:16:29.279> have<00:16:29.399> what<00:16:29.699> we<00:16:29.820> call<00:16:30.000> Stark<00:16:30.540> net<00:16:30.779> Cairo 00:16:31.129 --> 00:16:31.139 align:start position:0% you have what we call Stark net Cairo 00:16:31.139 --> 00:16:32.990 align:start position:0% you have what we call Stark net Cairo and<00:16:31.320> Stockton<00:16:31.620> Cairo<00:16:32.040> don't<00:16:32.339> have<00:16:32.639> a<00:16:32.760> notion 00:16:32.990 --> 00:16:33.000 align:start position:0% and Stockton Cairo don't have a notion 00:16:33.000 --> 00:16:35.930 align:start position:0% and Stockton Cairo don't have a notion of<00:16:33.180> State<00:16:33.300> Dove<00:16:33.839> has<00:16:34.019> a<00:16:34.139> notion<00:16:34.440> of<00:16:34.620> like<00:16:34.940> Cisco 00:16:35.930 --> 00:16:35.940 align:start position:0% of State Dove has a notion of like Cisco 00:16:35.940 --> 00:16:37.249 align:start position:0% of State Dove has a notion of like Cisco and<00:16:36.180> plenty<00:16:36.540> of<00:16:36.600> things<00:16:36.779> that<00:16:36.959> you<00:16:37.019> get<00:16:37.139> from 00:16:37.249 --> 00:16:37.259 align:start position:0% and plenty of things that you get from 00:16:37.259 --> 00:16:39.350 align:start position:0% and plenty of things that you get from the<00:16:37.380> OS<00:16:37.680> itself<00:16:37.920> so<00:16:38.160> you<00:16:38.339> have<00:16:38.519> like<00:16:38.639> Cairo<00:16:39.240> for 00:16:39.350 --> 00:16:39.360 align:start position:0% the OS itself so you have like Cairo for 00:16:39.360 --> 00:16:41.030 align:start position:0% the OS itself so you have like Cairo for a<00:16:39.540> start<00:16:39.660> net<00:16:39.839> you<00:16:40.019> have<00:16:40.139> Cairo<00:16:40.440> for<00:16:40.620> real<00:16:40.800> pure 00:16:41.030 --> 00:16:41.040 align:start position:0% a start net you have Cairo for real pure 00:16:41.040 --> 00:16:43.069 align:start position:0% a start net you have Cairo for real pure Cairo<00:16:41.399> so<00:16:41.820> the<00:16:42.000> thing<00:16:42.120> is<00:16:42.240> that<00:16:42.420> the<00:16:42.600> Cairo 00:16:43.069 --> 00:16:43.079 align:start position:0% Cairo so the thing is that the Cairo 00:16:43.079 --> 00:16:45.110 align:start position:0% Cairo so the thing is that the Cairo Force<00:16:43.440> darknet<00:16:44.160> cannot<00:16:45.000> be 00:16:45.110 --> 00:16:45.120 align:start position:0% Force darknet cannot be 00:16:45.120 --> 00:16:49.069 align:start position:0% Force darknet cannot be non-deterministic<00:16:46.440> and<00:16:47.160> that<00:16:47.459> is<00:16:47.639> for<00:16:48.000> a<00:16:48.899> very 00:16:49.069 --> 00:16:49.079 align:start position:0% non-deterministic and that is for a very 00:16:49.079 --> 00:16:53.030 align:start position:0% non-deterministic and that is for a very pure<00:16:50.240> incentive<00:16:51.240> reason<00:16:51.420> because<00:16:52.380> if<00:16:52.920> you 00:16:53.030 --> 00:16:53.040 align:start position:0% pure incentive reason because if you 00:16:53.040 --> 00:16:54.710 align:start position:0% pure incentive reason because if you don't<00:16:53.220> have<00:16:53.339> determinism<00:16:53.880> that<00:16:54.180> you<00:16:54.360> can<00:16:54.480> make 00:16:54.710 --> 00:16:54.720 align:start position:0% don't have determinism that you can make 00:16:54.720 --> 00:16:56.269 align:start position:0% don't have determinism that you can make transactions<00:16:55.320> that<00:16:55.500> are<00:16:55.680> not<00:16:55.860> provable 00:16:56.269 --> 00:16:56.279 align:start position:0% transactions that are not provable 00:16:56.279 --> 00:16:58.370 align:start position:0% transactions that are not provable meaning<00:16:56.940> I'm<00:16:57.300> the<00:16:57.480> only<00:16:57.660> one<00:16:57.839> we<00:16:58.019> know<00:16:58.199> that 00:16:58.370 --> 00:16:58.380 align:start position:0% meaning I'm the only one we know that 00:16:58.380 --> 00:16:59.870 align:start position:0% meaning I'm the only one we know that this<00:16:58.560> transaction<00:16:58.860> is<00:16:59.040> done<00:16:59.220> in<00:16:59.399> and<00:16:59.519> I<00:16:59.639> only 00:16:59.870 --> 00:16:59.880 align:start position:0% this transaction is done in and I only 00:16:59.880 --> 00:17:01.790 align:start position:0% this transaction is done in and I only want<00:17:00.180> to<00:17:00.300> know<00:17:00.420> the<00:17:00.600> hint<00:17:00.779> and<00:17:01.320> therefore<00:17:01.620> the 00:17:01.790 --> 00:17:01.800 align:start position:0% want to know the hint and therefore the 00:17:01.800 --> 00:17:03.769 align:start position:0% want to know the hint and therefore the rest<00:17:01.920> of<00:17:02.040> the<00:17:02.160> word<00:17:02.279> cannot<00:17:02.699> prove<00:17:03.000> it<00:17:03.060> and<00:17:03.600> so 00:17:03.769 --> 00:17:03.779 align:start position:0% rest of the word cannot prove it and so 00:17:03.779 --> 00:17:05.030 align:start position:0% rest of the word cannot prove it and so for<00:17:03.899> instance<00:17:04.079> let's<00:17:04.260> give<00:17:04.439> an<00:17:04.559> example<00:17:04.860> that 00:17:05.030 --> 00:17:05.040 align:start position:0% for instance let's give an example that 00:17:05.040 --> 00:17:06.710 align:start position:0% for instance let's give an example that people<00:17:05.220> like<00:17:05.400> to<00:17:05.579> choose<00:17:05.819> you<00:17:06.179> know<00:17:06.299> I<00:17:06.480> want<00:17:06.600> to 00:17:06.710 --> 00:17:06.720 align:start position:0% people like to choose you know I want to 00:17:06.720 --> 00:17:08.990 align:start position:0% people like to choose you know I want to do<00:17:06.839> a<00:17:06.959> force<00:17:07.199> transaction<00:17:07.559> for<00:17:08.220> man<00:17:08.400> one<00:17:08.699> you 00:17:08.990 --> 00:17:09.000 align:start position:0% do a force transaction for man one you 00:17:09.000 --> 00:17:10.669 align:start position:0% do a force transaction for man one you know<00:17:09.059> being<00:17:09.179> that<00:17:09.360> optimistic<00:17:09.900> roll-up<00:17:10.380> push 00:17:10.669 --> 00:17:10.679 align:start position:0% know being that optimistic roll-up push 00:17:10.679 --> 00:17:12.890 align:start position:0% know being that optimistic roll-up push I<00:17:11.220> mean<00:17:11.339> talks<00:17:11.579> a<00:17:11.640> lot<00:17:11.699> about 00:17:12.890 --> 00:17:12.900 align:start position:0% I mean talks a lot about 00:17:12.900 --> 00:17:15.230 align:start position:0% I mean talks a lot about um<00:17:12.959> then<00:17:13.559> in<00:17:13.980> this<00:17:14.160> context<00:17:14.520> with<00:17:14.699> determinism 00:17:15.230 --> 00:17:15.240 align:start position:0% um then in this context with determinism 00:17:15.240 --> 00:17:18.169 align:start position:0% um then in this context with determinism I<00:17:16.140> can't<00:17:16.319> this<00:17:16.860> is<00:17:16.919> a<00:17:17.100> dose<00:17:17.339> Vector<00:17:17.640> because<00:17:17.819> I 00:17:18.169 --> 00:17:18.179 align:start position:0% I can't this is a dose Vector because I 00:17:18.179 --> 00:17:20.030 align:start position:0% I can't this is a dose Vector because I don't<00:17:18.299> know<00:17:18.600> if<00:17:19.140> the<00:17:19.380> transaction<00:17:19.679> is<00:17:19.919> getting 00:17:20.030 --> 00:17:20.040 align:start position:0% don't know if the transaction is getting 00:17:20.040 --> 00:17:23.270 align:start position:0% don't know if the transaction is getting pushed<00:17:20.400> to<00:17:20.459> me<00:17:20.640> is<00:17:21.120> provable<00:17:21.780> by<00:17:22.020> me<00:17:22.620> I<00:17:23.100> don't 00:17:23.270 --> 00:17:23.280 align:start position:0% pushed to me is provable by me I don't 00:17:23.280 --> 00:17:25.610 align:start position:0% pushed to me is provable by me I don't know<00:17:23.400> that<00:17:23.579> and<00:17:24.179> so<00:17:24.419> and<00:17:25.020> another<00:17:25.260> thing<00:17:25.500> that 00:17:25.610 --> 00:17:25.620 align:start position:0% know that and so and another thing that 00:17:25.620 --> 00:17:26.990 align:start position:0% know that and so and another thing that is<00:17:25.799> important<00:17:26.220> to<00:17:26.339> you<00:17:26.520> that<00:17:26.640> fair 00:17:26.990 --> 00:17:27.000 align:start position:0% is important to you that fair 00:17:27.000 --> 00:17:29.090 align:start position:0% is important to you that fair transactions<00:17:27.660> so<00:17:27.900> fair<00:17:28.199> transaction<00:17:28.679> can<00:17:28.980> be 00:17:29.090 --> 00:17:29.100 align:start position:0% transactions so fair transaction can be 00:17:29.100 --> 00:17:31.310 align:start position:0% transactions so fair transaction can be valid<00:17:29.460> you<00:17:29.580> know<00:17:29.760> the<00:17:29.940> price<00:17:30.240> of<00:17:30.419> this<00:17:31.200> pool 00:17:31.310 --> 00:17:31.320 align:start position:0% valid you know the price of this pool 00:17:31.320 --> 00:17:33.110 align:start position:0% valid you know the price of this pool only<00:17:31.559> swap<00:17:31.919> move<00:17:32.100> and<00:17:32.340> now<00:17:32.520> for<00:17:32.760> my 00:17:33.110 --> 00:17:33.120 align:start position:0% only swap move and now for my 00:17:33.120 --> 00:17:35.630 align:start position:0% only swap move and now for my transaction<00:17:33.480> failed<00:17:33.960> and<00:17:34.620> otherwise<00:17:35.039> it<00:17:35.460> can 00:17:35.630 --> 00:17:35.640 align:start position:0% transaction failed and otherwise it can 00:17:35.640 --> 00:17:38.330 align:start position:0% transaction failed and otherwise it can be<00:17:35.820> uh<00:17:36.299> malicious<00:17:36.840> so<00:17:37.140> I'm<00:17:37.559> spamming<00:17:38.160> the 00:17:38.330 --> 00:17:38.340 align:start position:0% be uh malicious so I'm spamming the 00:17:38.340 --> 00:17:41.510 align:start position:0% be uh malicious so I'm spamming the network<00:17:38.720> with<00:17:39.720> transaction<00:17:40.380> hoping<00:17:41.100> to<00:17:41.220> get 00:17:41.510 --> 00:17:41.520 align:start position:0% network with transaction hoping to get 00:17:41.520 --> 00:17:43.310 align:start position:0% network with transaction hoping to get what<00:17:41.820> I<00:17:42.000> want<00:17:42.120> but<00:17:42.419> if<00:17:42.660> I<00:17:42.780> don't<00:17:42.900> I<00:17:43.080> don't<00:17:43.200> think 00:17:43.310 --> 00:17:43.320 align:start position:0% what I want but if I don't I don't think 00:17:43.320 --> 00:17:44.630 align:start position:0% what I want but if I don't I don't think I<00:17:43.440> don't<00:17:43.559> pay<00:17:43.679> anything<00:17:43.860> and<00:17:44.220> that's<00:17:44.340> why<00:17:44.520> I 00:17:44.630 --> 00:17:44.640 align:start position:0% I don't pay anything and that's why I 00:17:44.640 --> 00:17:46.430 align:start position:0% I don't pay anything and that's why I can<00:17:44.760> spam<00:17:45.179> the<00:17:45.299> network<00:17:45.419> for<00:17:45.720> anything<00:17:45.900> and<00:17:46.320> I 00:17:46.430 --> 00:17:46.440 align:start position:0% can spam the network for anything and I 00:17:46.440 --> 00:17:47.930 align:start position:0% can spam the network for anything and I need<00:17:46.559> to<00:17:46.620> run<00:17:46.740> it<00:17:46.919> and<00:17:47.100> so<00:17:47.280> creating<00:17:47.760> those 00:17:47.930 --> 00:17:47.940 align:start position:0% need to run it and so creating those 00:17:47.940 --> 00:17:51.590 align:start position:0% need to run it and so creating those Vector<00:17:48.419> so<00:17:49.080> Force<00:17:49.679> darknet<00:17:50.220> we<00:17:50.940> have<00:17:51.059> to<00:17:51.360> make 00:17:51.590 --> 00:17:51.600 align:start position:0% Vector so Force darknet we have to make 00:17:51.600 --> 00:17:53.810 align:start position:0% Vector so Force darknet we have to make Cairo<00:17:52.140> deterministic<00:17:52.740> or<00:17:52.919> I<00:17:53.160> mean<00:17:53.280> the 00:17:53.810 --> 00:17:53.820 align:start position:0% Cairo deterministic or I mean the 00:17:53.820 --> 00:17:55.490 align:start position:0% Cairo deterministic or I mean the version<00:17:54.179> of<00:17:54.419> Cairo<00:17:54.720> for<00:17:54.840> Stockton<00:17:55.200> will<00:17:55.380> be 00:17:55.490 --> 00:17:55.500 align:start position:0% version of Cairo for Stockton will be 00:17:55.500 --> 00:17:57.529 align:start position:0% version of Cairo for Stockton will be deterministic<00:17:55.980> for<00:17:56.100> that<00:17:56.280> purpose<00:17:56.460> and<00:17:57.360> to 00:17:57.529 --> 00:17:57.539 align:start position:0% deterministic for that purpose and to 00:17:57.539 --> 00:17:59.390 align:start position:0% deterministic for that purpose and to make<00:17:57.720> it<00:17:57.840> deterministic<00:17:58.380> we<00:17:58.559> need<00:17:58.740> to<00:17:59.039> prove 00:17:59.390 --> 00:17:59.400 align:start position:0% make it deterministic we need to prove 00:17:59.400 --> 00:18:01.549 align:start position:0% make it deterministic we need to prove that<00:17:59.700> the<00:18:00.240> program<00:18:00.480> was<00:18:00.960> compiled<00:18:01.500> into 00:18:01.549 --> 00:18:01.559 align:start position:0% that the program was compiled into 00:18:01.559 --> 00:18:03.289 align:start position:0% that the program was compiled into deterministic<00:18:02.340> version<00:18:02.460> of<00:18:02.640> Cairo<00:18:03.059> which<00:18:03.240> is 00:18:03.289 --> 00:18:03.299 align:start position:0% deterministic version of Cairo which is 00:18:03.299 --> 00:18:04.610 align:start position:0% deterministic version of Cairo which is a<00:18:03.480> safe<00:18:03.660> intermediate<00:18:04.140> representation 00:18:04.610 --> 00:18:04.620 align:start position:0% a safe intermediate representation 00:18:04.620 --> 00:18:07.070 align:start position:0% a safe intermediate representation called<00:18:04.860> Sierra<00:18:05.280> and<00:18:06.059> the<00:18:06.299> Sierra<00:18:06.840> will 00:18:07.070 --> 00:18:07.080 align:start position:0% called Sierra and the Sierra will 00:18:07.080 --> 00:18:09.470 align:start position:0% called Sierra and the Sierra will compile<00:18:07.559> to<00:18:07.860> Cairo<00:18:08.340> itself 00:18:09.470 --> 00:18:09.480 align:start position:0% compile to Cairo itself 00:18:09.480 --> 00:18:11.390 align:start position:0% compile to Cairo itself and<00:18:10.200> so 00:18:11.390 --> 00:18:11.400 align:start position:0% and so 00:18:11.400 --> 00:18:13.250 align:start position:0% and so right<00:18:12.120> stuff<00:18:12.360> will<00:18:12.600> be<00:18:12.720> proven<00:18:12.960> within 00:18:13.250 --> 00:18:13.260 align:start position:0% right stuff will be proven within 00:18:13.260 --> 00:18:15.110 align:start position:0% right stuff will be proven within starnet<00:18:13.679> when<00:18:13.860> I'm<00:18:14.039> deploying<00:18:14.400> a<00:18:14.520> contract<00:18:14.880> I 00:18:15.110 --> 00:18:15.120 align:start position:0% starnet when I'm deploying a contract I 00:18:15.120 --> 00:18:17.330 align:start position:0% starnet when I'm deploying a contract I will<00:18:15.299> be<00:18:15.480> proving<00:18:16.020> to<00:18:16.260> use<00:18:16.440> darknet<00:18:16.980> that<00:18:17.220> this 00:18:17.330 --> 00:18:17.340 align:start position:0% will be proving to use darknet that this 00:18:17.340 --> 00:18:20.630 align:start position:0% will be proving to use darknet that this contract<00:18:17.700> was<00:18:17.940> compiled<00:18:18.480> with<00:18:18.720> using<00:18:19.320> CLM<00:18:20.100> so 00:18:20.630 --> 00:18:20.640 align:start position:0% contract was compiled with using CLM so 00:18:20.640 --> 00:18:22.850 align:start position:0% contract was compiled with using CLM so this<00:18:20.940> is<00:18:21.000> what<00:18:21.179> I<00:18:21.360> mean<00:18:21.480> by<00:18:21.840> Carol<00:18:22.500> become 00:18:22.850 --> 00:18:22.860 align:start position:0% this is what I mean by Carol become 00:18:22.860 --> 00:18:26.740 align:start position:0% this is what I mean by Carol become deterministic<00:18:23.460> in<00:18:23.700> that<00:18:23.880> conflict 00:18:26.740 --> 00:18:26.750 align:start position:0% 00:18:26.750 --> 00:18:37.850 align:start position:0% [Music] 00:18:37.850 --> 00:18:37.860 align:start position:0% 00:18:37.860 --> 00:18:41.090 align:start position:0% I<00:18:38.280> guess<00:18:38.460> my<00:18:38.760> next<00:18:38.940> question<00:18:39.240> is<00:18:40.020> uh<00:18:40.919> number 00:18:41.090 --> 00:18:41.100 align:start position:0% I guess my next question is uh number 00:18:41.100 --> 00:18:43.310 align:start position:0% I guess my next question is uh number three<00:18:41.580> which<00:18:42.419> is 00:18:43.310 --> 00:18:43.320 align:start position:0% three which is 00:18:43.320 --> 00:18:46.250 align:start position:0% three which is yeah<00:18:44.100> when<00:18:44.700> you<00:18:45.059> were<00:18:45.240> writing<00:18:45.780> your 00:18:46.250 --> 00:18:46.260 align:start position:0% yeah when you were writing your 00:18:46.260 --> 00:18:48.770 align:start position:0% yeah when you were writing your languages<00:18:46.679> what<00:18:47.400> features<00:18:47.940> did<00:18:48.480> you 00:18:48.770 --> 00:18:48.780 align:start position:0% languages what features did you 00:18:48.780 --> 00:18:52.549 align:start position:0% languages what features did you prioritize<00:18:49.740> so<00:18:50.460> for<00:18:50.940> example 00:18:52.549 --> 00:18:52.559 align:start position:0% prioritize so for example 00:18:52.559 --> 00:18:55.430 align:start position:0% prioritize so for example um<00:18:52.620> Noir<00:18:53.039> is<00:18:53.340> very<00:18:53.520> rust-like<00:18:54.299> they<00:18:55.020> even<00:18:55.200> have 00:18:55.430 --> 00:18:55.440 align:start position:0% um Noir is very rust-like they even have 00:18:55.440 --> 00:18:58.370 align:start position:0% um Noir is very rust-like they even have a<00:18:55.679> version<00:18:55.919> of<00:18:56.160> cargo<00:18:56.520> called<00:18:56.820> nargo 00:18:58.370 --> 00:18:58.380 align:start position:0% a version of cargo called nargo 00:18:58.380 --> 00:19:01.730 align:start position:0% a version of cargo called nargo um<00:18:58.500> and<00:18:59.340> then<00:18:59.580> uh<00:19:00.419> snarky<00:19:00.900> js's<00:19:01.440> like 00:19:01.730 --> 00:19:01.740 align:start position:0% um and then uh snarky js's like 00:19:01.740 --> 00:19:03.350 align:start position:0% um and then uh snarky js's like typescript 00:19:03.350 --> 00:19:03.360 align:start position:0% typescript 00:19:03.360 --> 00:19:05.390 align:start position:0% typescript um<00:19:03.480> Cairo<00:19:04.080> is<00:19:04.260> also<00:19:04.620> a<00:19:04.740> pretty<00:19:04.919> high<00:19:05.160> level 00:19:05.390 --> 00:19:05.400 align:start position:0% um Cairo is also a pretty high level 00:19:05.400 --> 00:19:07.430 align:start position:0% um Cairo is also a pretty high level yeah<00:19:06.000> it's<00:19:06.480> Miss<00:19:06.660> right<00:19:06.840> now<00:19:07.020> it's<00:19:07.140> a<00:19:07.260> mix<00:19:07.320> of 00:19:07.430 --> 00:19:07.440 align:start position:0% yeah it's Miss right now it's a mix of 00:19:07.440 --> 00:19:09.010 align:start position:0% yeah it's Miss right now it's a mix of scene 00:19:09.010 --> 00:19:09.020 align:start position:0% scene 00:19:09.020 --> 00:19:11.870 align:start position:0% scene but<00:19:10.020> right<00:19:10.320> the<00:19:10.620> new<00:19:10.799> version<00:19:10.980> will<00:19:11.280> be<00:19:11.520> very 00:19:11.870 --> 00:19:11.880 align:start position:0% but right the new version will be very 00:19:11.880 --> 00:19:13.789 align:start position:0% but right the new version will be very rust-like<00:19:12.539> which<00:19:12.900> is<00:19:13.080> coming<00:19:13.260> in<00:19:13.380> the<00:19:13.559> I<00:19:13.679> say 00:19:13.789 --> 00:19:13.799 align:start position:0% rust-like which is coming in the I say 00:19:13.799 --> 00:19:16.130 align:start position:0% rust-like which is coming in the I say three<00:19:13.980> months<00:19:14.160> right<00:19:15.059> and<00:19:15.660> for<00:19:15.900> example 00:19:16.130 --> 00:19:16.140 align:start position:0% three months right and for example 00:19:16.140 --> 00:19:19.090 align:start position:0% three months right and for example ganark<00:19:16.860> was<00:19:17.160> just<00:19:17.280> written<00:19:17.640> directly<00:19:18.120> in<00:19:18.419> go 00:19:19.090 --> 00:19:19.100 align:start position:0% ganark was just written directly in go 00:19:19.100 --> 00:19:22.490 align:start position:0% ganark was just written directly in go Halo<00:19:20.100> 2<00:19:20.220> is<00:19:20.460> written<00:19:20.700> directly<00:19:21.059> in<00:19:21.240> Rust<00:19:21.500> but 00:19:22.490 --> 00:19:22.500 align:start position:0% Halo 2 is written directly in Rust but 00:19:22.500 --> 00:19:24.770 align:start position:0% Halo 2 is written directly in Rust but but<00:19:22.679> pill<00:19:22.919> and<00:19:23.160> circum<00:19:23.580> are<00:19:23.940> like<00:19:24.240> kind<00:19:24.660> of 00:19:24.770 --> 00:19:24.780 align:start position:0% but pill and circum are like kind of 00:19:24.780 --> 00:19:27.830 align:start position:0% but pill and circum are like kind of closer<00:19:25.200> to<00:19:25.380> the<00:19:25.620> metal<00:19:25.799> I<00:19:26.760> think<00:19:27.000> so<00:19:27.179> is<00:19:27.360> Halo 00:19:27.830 --> 00:19:27.840 align:start position:0% closer to the metal I think so is Halo 00:19:27.840 --> 00:19:30.590 align:start position:0% closer to the metal I think so is Halo the<00:19:28.320> metal<00:19:28.500> the<00:19:28.980> circuit<00:19:29.340> I<00:19:29.520> mean 00:19:30.590 --> 00:19:30.600 align:start position:0% the metal the circuit I mean 00:19:30.600 --> 00:19:34.190 align:start position:0% the metal the circuit I mean um<00:19:30.720> and<00:19:30.960> so<00:19:31.080> is<00:19:31.260> Halo<00:19:31.620> 2<00:19:31.799> so<00:19:32.280> yeah<00:19:33.059> what<00:19:34.020> are 00:19:34.190 --> 00:19:34.200 align:start position:0% um and so is Halo 2 so yeah what are 00:19:34.200 --> 00:19:37.010 align:start position:0% um and so is Halo 2 so yeah what are your<00:19:34.320> thoughts<00:19:34.799> on<00:19:35.120> uh<00:19:36.120> the<00:19:36.419> trade-offs 00:19:37.010 --> 00:19:37.020 align:start position:0% your thoughts on uh the trade-offs 00:19:37.020 --> 00:19:38.570 align:start position:0% your thoughts on uh the trade-offs between<00:19:37.380> like<00:19:37.919> higher<00:19:38.400> level 00:19:38.570 --> 00:19:38.580 align:start position:0% between like higher level 00:19:38.580 --> 00:19:40.130 align:start position:0% between like higher level representations<00:19:39.419> and<00:19:39.720> lower<00:19:39.960> level 00:19:40.130 --> 00:19:40.140 align:start position:0% representations and lower level 00:19:40.140 --> 00:19:42.110 align:start position:0% representations and lower level representations<00:19:40.740> and 00:19:42.110 --> 00:19:42.120 align:start position:0% representations and 00:19:42.120 --> 00:19:45.230 align:start position:0% representations and um<00:19:42.240> how<00:19:42.419> did<00:19:42.600> you<00:19:42.840> you<00:19:43.500> know<00:19:43.679> decide<00:19:44.460> on<00:19:45.059> the 00:19:45.230 --> 00:19:45.240 align:start position:0% um how did you you know decide on the 00:19:45.240 --> 00:19:48.230 align:start position:0% um how did you you know decide on the designs<00:19:45.660> that<00:19:45.840> you<00:19:46.080> did 00:19:48.230 --> 00:19:48.240 align:start position:0% designs that you did 00:19:48.240 --> 00:19:50.330 align:start position:0% designs that you did can<00:19:48.600> maybe<00:19:48.780> start<00:19:49.020> so<00:19:49.320> the<00:19:49.740> first<00:19:49.980> that's 00:19:50.330 --> 00:19:50.340 align:start position:0% can maybe start so the first that's 00:19:50.340 --> 00:19:51.890 align:start position:0% can maybe start so the first that's actually<00:19:50.520> an<00:19:50.760> interesting<00:19:51.179> story<00:19:51.360> from<00:19:51.660> from 00:19:51.890 --> 00:19:51.900 align:start position:0% actually an interesting story from from 00:19:51.900 --> 00:19:54.049 align:start position:0% actually an interesting story from from uh<00:19:52.140> from<00:19:52.440> Star<00:19:52.620> War<00:19:52.799> expertise<00:19:53.220> experience<00:19:53.820> so 00:19:54.049 --> 00:19:54.059 align:start position:0% uh from Star War expertise experience so 00:19:54.059 --> 00:19:56.090 align:start position:0% uh from Star War expertise experience so the<00:19:54.539> first<00:19:54.660> version<00:19:54.840> of<00:19:55.020> Star<00:19:55.260> Kick<00:19:55.500> so<00:19:55.620> starcx 00:19:56.090 --> 00:19:56.100 align:start position:0% the first version of Star Kick so starcx 00:19:56.100 --> 00:19:58.430 align:start position:0% the first version of Star Kick so starcx was<00:19:56.400> and<00:19:56.880> it<00:19:57.179> is<00:19:57.360> the<00:19:57.539> first<00:19:57.660> product<00:19:58.200> in 00:19:58.430 --> 00:19:58.440 align:start position:0% was and it is the first product in 00:19:58.440 --> 00:20:00.890 align:start position:0% was and it is the first product in stockward<00:19:58.919> and<00:19:59.160> which<00:19:59.640> is<00:19:59.820> basically<00:20:00.299> a 00:20:00.890 --> 00:20:00.900 align:start position:0% stockward and which is basically a 00:20:00.900 --> 00:20:03.110 align:start position:0% stockward and which is basically a centralized<00:20:01.380> but<00:20:01.559> non-custodial<00:20:02.220> back<00:20:02.940> end 00:20:03.110 --> 00:20:03.120 align:start position:0% centralized but non-custodial back end 00:20:03.120 --> 00:20:05.750 align:start position:0% centralized but non-custodial back end for<00:20:03.600> uh<00:20:04.080> dabs<00:20:04.500> who<00:20:04.620> need<00:20:04.740> scalability<00:20:05.280> so<00:20:05.520> you 00:20:05.750 --> 00:20:05.760 align:start position:0% for uh dabs who need scalability so you 00:20:05.760 --> 00:20:08.750 align:start position:0% for uh dabs who need scalability so you know<00:20:05.880> customers<00:20:06.179> are<00:20:06.299> dydx<00:20:07.100> diversify<00:20:08.100> uh 00:20:08.750 --> 00:20:08.760 align:start position:0% know customers are dydx diversify uh 00:20:08.760 --> 00:20:11.630 align:start position:0% know customers are dydx diversify uh immutable<00:20:09.299> and<00:20:09.600> so<00:20:09.780> rare<00:20:10.380> and<00:20:11.100> so<00:20:11.340> the<00:20:11.520> first 00:20:11.630 --> 00:20:11.640 align:start position:0% immutable and so rare and so the first 00:20:11.640 --> 00:20:13.610 align:start position:0% immutable and so rare and so the first version<00:20:11.880> were<00:20:12.240> written<00:20:12.660> you<00:20:12.900> know<00:20:13.020> very<00:20:13.380> low 00:20:13.610 --> 00:20:13.620 align:start position:0% version were written you know very low 00:20:13.620 --> 00:20:16.310 align:start position:0% version were written you know very low level<00:20:13.799> literally<00:20:14.280> in<00:20:14.580> polynoms<00:20:15.120> uh<00:20:15.780> and<00:20:15.960> this 00:20:16.310 --> 00:20:16.320 align:start position:0% level literally in polynoms uh and this 00:20:16.320 --> 00:20:19.850 align:start position:0% level literally in polynoms uh and this thing<00:20:16.559> does<00:20:16.860> transfer<00:20:17.460> and<00:20:17.640> swaps<00:20:18.240> and<00:20:19.140> so<00:20:19.440> we 00:20:19.850 --> 00:20:19.860 align:start position:0% thing does transfer and swaps and so we 00:20:19.860 --> 00:20:23.210 align:start position:0% thing does transfer and swaps and so we started<00:20:20.160> to<00:20:20.340> work<00:20:20.460> in<00:20:20.580> Cairo<00:20:21.000> it<00:20:21.179> was<00:20:21.740> 2019<00:20:22.740> and 00:20:23.210 --> 00:20:23.220 align:start position:0% started to work in Cairo it was 2019 and 00:20:23.220 --> 00:20:26.570 align:start position:0% started to work in Cairo it was 2019 and it<00:20:23.820> became<00:20:24.059> production<00:20:24.360> ready<00:20:24.660> uh<00:20:25.620> in<00:20:25.919> uh<00:20:26.160> in 00:20:26.570 --> 00:20:26.580 align:start position:0% it became production ready uh in uh in 00:20:26.580 --> 00:20:28.250 align:start position:0% it became production ready uh in uh in May<00:20:26.760> 2020 00:20:28.250 --> 00:20:28.260 align:start position:0% May 2020 00:20:28.260 --> 00:20:29.690 align:start position:0% May 2020 um the<00:20:28.500> first<00:20:28.620> case<00:20:28.799> of<00:20:28.980> actually<00:20:29.160> uh<00:20:29.460> where 00:20:29.690 --> 00:20:29.700 align:start position:0% um the first case of actually uh where 00:20:29.700 --> 00:20:31.610 align:start position:0% um the first case of actually uh where we<00:20:29.880> used<00:20:30.059> it<00:20:30.299> for<00:20:30.720> what's<00:20:30.900> for<00:20:31.140> the<00:20:31.260> ready<00:20:31.440> to 00:20:31.610 --> 00:20:31.620 align:start position:0% we used it for what's for the ready to 00:20:31.620 --> 00:20:34.370 align:start position:0% we used it for what's for the ready to bake<00:20:32.220> off<00:20:32.340> in<00:20:32.760> June<00:20:33.000> 2020. 00:20:34.370 --> 00:20:34.380 align:start position:0% bake off in June 2020. 00:20:34.380 --> 00:20:35.870 align:start position:0% bake off in June 2020. um<00:20:34.440> and<00:20:34.740> so 00:20:35.870 --> 00:20:35.880 align:start position:0% um and so 00:20:35.880 --> 00:20:37.970 align:start position:0% um and so um the<00:20:36.179> funny<00:20:36.299> story<00:20:36.660> that<00:20:36.900> the<00:20:37.260> improve<00:20:37.679> the 00:20:37.970 --> 00:20:37.980 align:start position:0% um the funny story that the improve the 00:20:37.980 --> 00:20:40.750 align:start position:0% um the funny story that the improve the performance<00:20:38.400> of<00:20:39.240> the<00:20:39.660> of<00:20:40.260> the<00:20:40.559> system 00:20:40.750 --> 00:20:40.760 align:start position:0% performance of the of the system 00:20:40.760 --> 00:20:42.710 align:start position:0% performance of the of the system massively<00:20:41.760> improved<00:20:42.059> when<00:20:42.120> we<00:20:42.299> start<00:20:42.480> using 00:20:42.710 --> 00:20:42.720 align:start position:0% massively improved when we start using 00:20:42.720 --> 00:20:44.330 align:start position:0% massively improved when we start using Cairo<00:20:43.140> because<00:20:43.380> it<00:20:43.620> was<00:20:43.740> much<00:20:43.919> higher<00:20:44.220> level 00:20:44.330 --> 00:20:44.340 align:start position:0% Cairo because it was much higher level 00:20:44.340 --> 00:20:47.330 align:start position:0% Cairo because it was much higher level and<00:20:44.880> who<00:20:45.179> had<00:20:45.480> a<00:20:45.600> lot<00:20:45.660> more<00:20:45.840> flexibility<00:20:46.340> in 00:20:47.330 --> 00:20:47.340 align:start position:0% and who had a lot more flexibility in 00:20:47.340 --> 00:20:48.590 align:start position:0% and who had a lot more flexibility in the<00:20:47.520> way<00:20:47.640> we<00:20:47.760> could<00:20:47.880> reason<00:20:48.059> about<00:20:48.240> the<00:20:48.480> system 00:20:48.590 --> 00:20:48.600 align:start position:0% the way we could reason about the system 00:20:48.600 --> 00:20:49.789 align:start position:0% the way we could reason about the system in<00:20:48.840> the<00:20:48.960> way<00:20:49.020> we<00:20:49.140> could<00:20:49.320> write<00:20:49.440> about<00:20:49.620> the 00:20:49.789 --> 00:20:49.799 align:start position:0% in the way we could write about the 00:20:49.799 --> 00:20:51.470 align:start position:0% in the way we could write about the system<00:20:49.980> Not<00:20:50.400> only<00:20:50.580> was<00:20:50.760> again<00:20:50.940> in<00:20:51.120> philosophy 00:20:51.470 --> 00:20:51.480 align:start position:0% system Not only was again in philosophy 00:20:51.480 --> 00:20:53.630 align:start position:0% system Not only was again in philosophy in<00:20:51.660> velocity<00:20:52.080> but<00:20:52.260> also<00:20:52.620> again<00:20:52.799> in<00:20:53.400> actual 00:20:53.630 --> 00:20:53.640 align:start position:0% in velocity but also again in actual 00:20:53.640 --> 00:20:57.110 align:start position:0% in velocity but also again in actual Pure<00:20:53.940> Performance<00:20:54.620> and<00:20:55.620> so 00:20:57.110 --> 00:20:57.120 align:start position:0% Pure Performance and so 00:20:57.120 --> 00:20:59.810 align:start position:0% Pure Performance and so um<00:20:57.179> there<00:20:57.720> is<00:20:57.840> you<00:20:58.200> know<00:20:58.320> in<00:20:58.500> some<00:20:58.919> green<00:20:59.160> of 00:20:59.810 --> 00:20:59.820 align:start position:0% um there is you know in some green of 00:20:59.820 --> 00:21:01.250 align:start position:0% um there is you know in some green of and<00:21:00.120> when<00:21:00.360> you<00:21:00.539> need<00:21:00.720> that<00:21:00.840> performance 00:21:01.250 --> 00:21:01.260 align:start position:0% and when you need that performance 00:21:01.260 --> 00:21:02.870 align:start position:0% and when you need that performance Improvement<00:21:01.679> we<00:21:02.100> have<00:21:02.340> these<00:21:02.520> things<00:21:02.640> that 00:21:02.870 --> 00:21:02.880 align:start position:0% Improvement we have these things that 00:21:02.880 --> 00:21:04.490 align:start position:0% Improvement we have these things that are<00:21:03.000> built<00:21:03.299> in<00:21:03.419> the<00:21:03.600> same<00:21:03.780> built-in<00:21:04.320> as 00:21:04.490 --> 00:21:04.500 align:start position:0% are built in the same built-in as 00:21:04.500 --> 00:21:07.070 align:start position:0% are built in the same built-in as equivalent<00:21:04.980> to<00:21:05.100> Cairo<00:21:05.460> to<00:21:05.640> those<00:21:06.539> specific 00:21:07.070 --> 00:21:07.080 align:start position:0% equivalent to Cairo to those specific 00:21:07.080 --> 00:21:08.870 align:start position:0% equivalent to Cairo to those specific shape<00:21:07.559> on<00:21:07.740> your<00:21:07.860> CPU<00:21:08.160> like<00:21:08.340> the<00:21:08.520> one<00:21:08.580> that<00:21:08.700> does 00:21:08.870 --> 00:21:08.880 align:start position:0% shape on your CPU like the one that does 00:21:08.880 --> 00:21:11.029 align:start position:0% shape on your CPU like the one that does 64<00:21:09.240> bits 00:21:11.029 --> 00:21:11.039 align:start position:0% 64 bits 00:21:11.039 --> 00:21:13.250 align:start position:0% 64 bits and<00:21:11.700> so<00:21:11.940> if<00:21:12.539> you<00:21:12.660> really<00:21:12.840> need<00:21:13.080> like 00:21:13.250 --> 00:21:13.260 align:start position:0% and so if you really need like 00:21:13.260 --> 00:21:15.470 align:start position:0% and so if you really need like optimization<00:21:13.980> at<00:21:14.340> the<00:21:14.520> very<00:21:14.580> low<00:21:14.760> level<00:21:14.940> for<00:21:15.360> a 00:21:15.470 --> 00:21:15.480 align:start position:0% optimization at the very low level for a 00:21:15.480 --> 00:21:18.470 align:start position:0% optimization at the very low level for a specific<00:21:15.780> operation<00:21:16.260> like<00:21:16.740> say<00:21:17.220> proving<00:21:18.419> um 00:21:18.470 --> 00:21:18.480 align:start position:0% specific operation like say proving um 00:21:18.480 --> 00:21:20.150 align:start position:0% specific operation like say proving um right<00:21:18.780> now<00:21:18.900> we<00:21:19.020> did<00:21:19.140> it<00:21:19.260> first<00:21:19.380> okay<00:21:19.620> check<00:21:19.919> we 00:21:20.150 --> 00:21:20.160 align:start position:0% right now we did it first okay check we 00:21:20.160 --> 00:21:21.590 align:start position:0% right now we did it first okay check we did<00:21:20.280> it<00:21:20.460> for<00:21:20.880> um 00:21:21.590 --> 00:21:21.600 align:start position:0% did it for um 00:21:21.600 --> 00:21:23.770 align:start position:0% did it for um um<00:21:21.720> for<00:21:22.320> um<00:21:22.320> uh<00:21:22.740> for<00:21:23.100> a 00:21:23.770 --> 00:21:23.780 align:start position:0% um for um uh for a 00:21:23.780 --> 00:21:26.810 align:start position:0% um for um uh for a seriesic<00:21:24.780> signatures<00:21:25.440> we<00:21:25.679> in<00:21:25.980> the<00:21:26.100> range 00:21:26.810 --> 00:21:26.820 align:start position:0% seriesic signatures we in the range 00:21:26.820 --> 00:21:28.610 align:start position:0% seriesic signatures we in the range proof<00:21:27.120> and<00:21:27.179> sort<00:21:27.480> of<00:21:27.600> things<00:21:27.720> that<00:21:28.260> we<00:21:28.380> write 00:21:28.610 --> 00:21:28.620 align:start position:0% proof and sort of things that we write 00:21:28.620 --> 00:21:30.950 align:start position:0% proof and sort of things that we write them<00:21:28.799> in<00:21:28.980> those<00:21:29.220> and<00:21:30.000> for<00:21:30.240> the<00:21:30.419> rest<00:21:30.539> we<00:21:30.780> just 00:21:30.950 --> 00:21:30.960 align:start position:0% them in those and for the rest we just 00:21:30.960 --> 00:21:33.890 align:start position:0% them in those and for the rest we just write<00:21:31.080> in<00:21:31.260> and<00:21:31.860> so<00:21:32.340> there<00:21:33.000> was<00:21:33.120> not<00:21:33.360> really<00:21:33.539> any 00:21:33.890 --> 00:21:33.900 align:start position:0% write in and so there was not really any 00:21:33.900 --> 00:21:37.010 align:start position:0% write in and so there was not really any trade-off<00:21:34.440> in<00:21:35.039> many<00:21:35.220> way<00:21:35.760> except<00:21:36.179> that<00:21:36.419> much 00:21:37.010 --> 00:21:37.020 align:start position:0% trade-off in many way except that much 00:21:37.020 --> 00:21:42.289 align:start position:0% trade-off in many way except that much simpler<00:21:37.380> and<00:21:37.500> nicer<00:21:37.799> to<00:21:37.980> write 00:21:42.289 --> 00:21:42.299 align:start position:0% 00:21:42.299 --> 00:21:44.149 align:start position:0% nowhere<00:21:42.900> too 00:21:44.149 --> 00:21:44.159 align:start position:0% nowhere too 00:21:44.159 --> 00:21:46.070 align:start position:0% nowhere too yeah<00:21:44.640> that's<00:21:44.880> interesting<00:21:45.299> that<00:21:45.539> like<00:21:45.780> a 00:21:46.070 --> 00:21:46.080 align:start position:0% yeah that's interesting that like a 00:21:46.080 --> 00:21:48.110 align:start position:0% yeah that's interesting that like a higher<00:21:46.380> level<00:21:46.500> language<00:21:46.919> actually<00:21:47.400> improve 00:21:48.110 --> 00:21:48.120 align:start position:0% higher level language actually improve 00:21:48.120 --> 00:21:50.149 align:start position:0% higher level language actually improve your<00:21:48.240> performance<00:21:48.780> but<00:21:49.140> yeah<00:21:49.559> I<00:21:49.799> guess<00:21:49.919> so 00:21:50.149 --> 00:21:50.159 align:start position:0% your performance but yeah I guess so 00:21:50.159 --> 00:21:51.890 align:start position:0% your performance but yeah I guess so you're<00:21:50.400> pushing<00:21:50.820> a<00:21:51.120> lot<00:21:51.240> of<00:21:51.419> the<00:21:51.539> manual 00:21:51.890 --> 00:21:51.900 align:start position:0% you're pushing a lot of the manual 00:21:51.900 --> 00:21:55.250 align:start position:0% you're pushing a lot of the manual optimization<00:21:52.500> to<00:21:53.159> the<00:21:53.580> compilers<00:21:54.419> and<00:21:54.900> like 00:21:55.250 --> 00:21:55.260 align:start position:0% optimization to the compilers and like 00:21:55.260 --> 00:21:57.770 align:start position:0% optimization to the compilers and like stuff<00:21:55.860> that<00:21:56.159> computers<00:21:56.640> are<00:21:56.880> better<00:21:57.059> at<00:21:57.299> and 00:21:57.770 --> 00:21:57.780 align:start position:0% stuff that computers are better at and 00:21:57.780 --> 00:21:59.810 align:start position:0% stuff that computers are better at and then<00:21:57.960> the<00:21:58.380> commonly<00:21:58.860> used<00:21:59.100> so-called 00:21:59.810 --> 00:21:59.820 align:start position:0% then the commonly used so-called 00:21:59.820 --> 00:22:07.610 align:start position:0% then the commonly used so-called pre-compiles<00:22:00.960> um<00:22:01.020> you<00:22:01.320> do<00:22:01.440> hand<00:22:01.679> write<00:22:01.919> that 00:22:07.610 --> 00:22:07.620 align:start position:0% 00:22:07.620 --> 00:22:10.010 align:start position:0% you<00:22:07.799> started<00:22:08.280> when<00:22:08.880> when<00:22:09.059> I<00:22:09.419> started<00:22:09.659> to<00:22:09.840> write 00:22:10.010 --> 00:22:10.020 align:start position:0% you started when when I started to write 00:22:10.020 --> 00:22:12.590 align:start position:0% you started when when I started to write circum<00:22:10.559> the<00:22:10.799> main<00:22:11.220> purpose<00:22:11.640> is 00:22:12.590 --> 00:22:12.600 align:start position:0% circum the main purpose is 00:22:12.600 --> 00:22:15.409 align:start position:0% circum the main purpose is as<00:22:12.960> I<00:22:13.200> said<00:22:13.380> before<00:22:13.559> is<00:22:13.799> circum<00:22:14.340> is<00:22:14.580> at<00:22:15.000> the<00:22:15.360> end 00:22:15.409 --> 00:22:15.419 align:start position:0% as I said before is circum is at the end 00:22:15.419 --> 00:22:18.529 align:start position:0% as I said before is circum is at the end it's<00:22:15.600> a<00:22:15.720> low<00:22:15.840> level<00:22:16.020> language<00:22:16.320> so<00:22:16.860> it<00:22:17.640> is<00:22:17.820> that 00:22:18.529 --> 00:22:18.539 align:start position:0% it's a low level language so it is that 00:22:18.539 --> 00:22:20.029 align:start position:0% it's a low level language so it is that if<00:22:18.900> you're<00:22:19.020> writing<00:22:19.380> silicon<00:22:19.740> you<00:22:19.919> should 00:22:20.029 --> 00:22:20.039 align:start position:0% if you're writing silicon you should 00:22:20.039 --> 00:22:22.130 align:start position:0% if you're writing silicon you should understand<00:22:20.159> what<00:22:20.880> you<00:22:21.000> are<00:22:21.120> doing<00:22:21.240> you<00:22:21.960> should 00:22:22.130 --> 00:22:22.140 align:start position:0% understand what you are doing you should 00:22:22.140 --> 00:22:23.289 align:start position:0% understand what you are doing you should understand 00:22:23.289 --> 00:22:23.299 align:start position:0% understand 00:22:23.299 --> 00:22:25.970 align:start position:0% understand what's<00:22:24.299> in<00:22:24.539> the<00:22:24.720> what's<00:22:25.320> behind<00:22:25.740> the<00:22:25.860> the 00:22:25.970 --> 00:22:25.980 align:start position:0% what's in the what's behind the the 00:22:25.980 --> 00:22:28.190 align:start position:0% what's in the what's behind the the circuit 00:22:28.190 --> 00:22:28.200 align:start position:0% circuit 00:22:28.200 --> 00:22:30.770 align:start position:0% circuit level<00:22:28.500> of<00:22:28.860> course<00:22:28.980> you<00:22:29.159> can<00:22:29.280> do<00:22:29.460> things<00:22:29.760> in<00:22:30.780> um 00:22:30.770 --> 00:22:30.780 align:start position:0% level of course you can do things in um 00:22:30.780 --> 00:22:32.810 align:start position:0% level of course you can do things in um in<00:22:31.260> a<00:22:31.440> high<00:22:31.559> level<00:22:31.799> because<00:22:32.280> you<00:22:32.520> can<00:22:32.640> connect 00:22:32.810 --> 00:22:32.820 align:start position:0% in a high level because you can connect 00:22:32.820 --> 00:22:35.810 align:start position:0% in a high level because you can connect things<00:22:33.179> but<00:22:33.539> the<00:22:33.780> idea<00:22:34.020> is<00:22:34.260> that<00:22:34.620> you<00:22:35.220> have 00:22:35.810 --> 00:22:35.820 align:start position:0% things but the idea is that you have 00:22:35.820 --> 00:22:37.669 align:start position:0% things but the idea is that you have precise<00:22:36.360> and<00:22:36.659> this<00:22:36.900> is<00:22:37.080> some<00:22:37.440> something 00:22:37.669 --> 00:22:37.679 align:start position:0% precise and this is some something 00:22:37.679 --> 00:22:41.510 align:start position:0% precise and this is some something that's<00:22:38.039> very<00:22:38.280> specific<00:22:38.580> to<00:22:38.880> circum<00:22:39.419> is<00:22:39.960> you<00:22:40.679> it 00:22:41.510 --> 00:22:41.520 align:start position:0% that's very specific to circum is you it 00:22:41.520 --> 00:22:43.010 align:start position:0% that's very specific to circum is you it should<00:22:41.700> not<00:22:41.820> be<00:22:42.000> any<00:22:42.120> hidden<00:22:42.600> constraint 00:22:43.010 --> 00:22:43.020 align:start position:0% should not be any hidden constraint 00:22:43.020 --> 00:22:44.270 align:start position:0% should not be any hidden constraint anywhere 00:22:44.270 --> 00:22:44.280 align:start position:0% anywhere 00:22:44.280 --> 00:22:46.430 align:start position:0% anywhere so<00:22:44.820> other<00:22:45.059> constraints<00:22:45.600> are<00:22:45.900> there<00:22:46.020> you<00:22:46.320> can 00:22:46.430 --> 00:22:46.440 align:start position:0% so other constraints are there you can 00:22:46.440 --> 00:22:47.870 align:start position:0% so other constraints are there you can check<00:22:46.559> the<00:22:46.740> code<00:22:46.860> maybe<00:22:47.159> you<00:22:47.340> need<00:22:47.460> to<00:22:47.580> go 00:22:47.870 --> 00:22:47.880 align:start position:0% check the code maybe you need to go 00:22:47.880 --> 00:22:49.970 align:start position:0% check the code maybe you need to go inside<00:22:48.059> the<00:22:48.360> circum<00:22:48.840> leap<00:22:49.080> or<00:22:49.260> someplace<00:22:49.740> in 00:22:49.970 --> 00:22:49.980 align:start position:0% inside the circum leap or someplace in 00:22:49.980 --> 00:22:51.830 align:start position:0% inside the circum leap or someplace in the<00:22:50.100> library<00:22:50.159> but<00:22:50.640> you<00:22:50.760> will<00:22:50.880> find<00:22:51.240> all<00:22:51.720> the 00:22:51.830 --> 00:22:51.840 align:start position:0% the library but you will find all the 00:22:51.840 --> 00:22:54.470 align:start position:0% the library but you will find all the constraints<00:22:52.260> there<00:22:52.620> and<00:22:53.100> you<00:22:53.400> can<00:22:53.520> track<00:22:54.179> them 00:22:54.470 --> 00:22:54.480 align:start position:0% constraints there and you can track them 00:22:54.480 --> 00:22:56.330 align:start position:0% constraints there and you can track them and<00:22:54.840> you<00:22:55.020> can<00:22:55.140> see<00:22:55.380> them<00:22:55.559> so<00:22:55.799> you<00:22:55.980> can<00:22:56.100> have 00:22:56.330 --> 00:22:56.340 align:start position:0% and you can see them so you can have 00:22:56.340 --> 00:22:58.850 align:start position:0% and you can see them so you can have full<00:22:56.640> control<00:22:56.880> of<00:22:57.720> what<00:22:58.080> you<00:22:58.260> are<00:22:58.380> doing<00:22:58.559> this 00:22:58.850 --> 00:22:58.860 align:start position:0% full control of what you are doing this 00:22:58.860 --> 00:23:01.250 align:start position:0% full control of what you are doing this of<00:22:59.039> course<00:22:59.220> is<00:22:59.520> dangerous<00:23:00.240> I'm<00:23:00.720> not<00:23:01.020> saying 00:23:01.250 --> 00:23:01.260 align:start position:0% of course is dangerous I'm not saying 00:23:01.260 --> 00:23:02.870 align:start position:0% of course is dangerous I'm not saying that<00:23:01.380> that's<00:23:01.740> why<00:23:01.980> because<00:23:02.340> you<00:23:02.580> know<00:23:02.700> you 00:23:02.870 --> 00:23:02.880 align:start position:0% that that's why because you know you 00:23:02.880 --> 00:23:04.250 align:start position:0% that that's why because you know you need<00:23:03.000> to<00:23:03.059> understand<00:23:03.179> if<00:23:03.600> you're<00:23:03.720> I've<00:23:04.080> seen 00:23:04.250 --> 00:23:04.260 align:start position:0% need to understand if you're I've seen 00:23:04.260 --> 00:23:06.110 align:start position:0% need to understand if you're I've seen people<00:23:04.440> that<00:23:04.740> writing<00:23:05.100> circum<00:23:05.460> language<00:23:05.640> that 00:23:06.110 --> 00:23:06.120 align:start position:0% people that writing circum language that 00:23:06.120 --> 00:23:08.510 align:start position:0% people that writing circum language that they<00:23:06.419> don't<00:23:06.539> know<00:23:06.780> what<00:23:07.620> they<00:23:07.740> are<00:23:07.860> writing<00:23:08.220> so 00:23:08.510 --> 00:23:08.520 align:start position:0% they don't know what they are writing so 00:23:08.520 --> 00:23:10.930 align:start position:0% they don't know what they are writing so it's<00:23:09.299> not<00:23:09.480> going<00:23:09.659> to<00:23:09.780> work<00:23:09.900> okay<00:23:10.320> and<00:23:10.559> this<00:23:10.799> is 00:23:10.930 --> 00:23:10.940 align:start position:0% it's not going to work okay and this is 00:23:10.940 --> 00:23:14.870 align:start position:0% it's not going to work okay and this is we<00:23:11.940> we<00:23:12.000> understand<00:23:12.780> this<00:23:13.200> is<00:23:13.380> a<00:23:13.679> a<00:23:14.159> thing<00:23:14.580> but 00:23:14.870 --> 00:23:14.880 align:start position:0% we we understand this is a a thing but 00:23:14.880 --> 00:23:18.529 align:start position:0% we we understand this is a a thing but this<00:23:15.120> is<00:23:15.299> what<00:23:15.780> circum<00:23:16.320> is<00:23:16.860> uh<00:23:17.400> for<00:23:17.820> circum<00:23:18.419> is 00:23:18.529 --> 00:23:18.539 align:start position:0% this is what circum is uh for circum is 00:23:18.539 --> 00:23:21.890 align:start position:0% this is what circum is uh for circum is for<00:23:18.720> writing<00:23:19.080> would<00:23:19.740> say<00:23:20.419> Circle<00:23:21.419> means<00:23:21.840> for 00:23:21.890 --> 00:23:21.900 align:start position:0% for writing would say Circle means for 00:23:21.900 --> 00:23:24.409 align:start position:0% for writing would say Circle means for people<00:23:22.080> that<00:23:22.380> understand<00:23:22.620> what's<00:23:23.520> happening 00:23:24.409 --> 00:23:24.419 align:start position:0% people that understand what's happening 00:23:24.419 --> 00:23:27.230 align:start position:0% people that understand what's happening underneath<00:23:25.020> that's<00:23:25.559> the<00:23:25.940> that's<00:23:26.940> the<00:23:27.120> thing 00:23:27.230 --> 00:23:27.240 align:start position:0% underneath that's the that's the thing 00:23:27.240 --> 00:23:28.370 align:start position:0% underneath that's the that's the thing okay 00:23:28.370 --> 00:23:28.380 align:start position:0% okay 00:23:28.380 --> 00:23:30.110 align:start position:0% okay um<00:23:28.500> said<00:23:29.039> that 00:23:30.110 --> 00:23:30.120 align:start position:0% um said that 00:23:30.120 --> 00:23:33.649 align:start position:0% um said that the<00:23:30.780> disease<00:23:31.260> will<00:23:31.440> be<00:23:31.679> linking<00:23:32.159> with<00:23:32.940> what<00:23:33.480> he 00:23:33.649 --> 00:23:33.659 align:start position:0% the disease will be linking with what he 00:23:33.659 --> 00:23:36.130 align:start position:0% the disease will be linking with what he said<00:23:33.900> is<00:23:34.140> I<00:23:34.620> think<00:23:34.799> that<00:23:35.220> in<00:23:35.820> the<00:23:35.940> future 00:23:36.130 --> 00:23:36.140 align:start position:0% said is I think that in the future 00:23:36.140 --> 00:23:40.010 align:start position:0% said is I think that in the future nobody<00:23:37.140> will<00:23:37.679> have<00:23:37.860> to<00:23:38.220> write<00:23:38.460> circuits 00:23:40.010 --> 00:23:40.020 align:start position:0% nobody will have to write circuits 00:23:40.020 --> 00:23:42.770 align:start position:0% nobody will have to write circuits and<00:23:40.620> because<00:23:41.220> uh<00:23:41.820> Siri<00:23:42.000> is<00:23:42.299> a<00:23:42.419> very<00:23:42.480> specific 00:23:42.770 --> 00:23:42.780 align:start position:0% and because uh Siri is a very specific 00:23:42.780 --> 00:23:44.870 align:start position:0% and because uh Siri is a very specific thing<00:23:43.080> for<00:23:43.500> politics<00:23:44.039> and<00:23:44.220> and<00:23:44.400> then<00:23:44.640> you<00:23:44.760> can 00:23:44.870 --> 00:23:44.880 align:start position:0% thing for politics and and then you can 00:23:44.880 --> 00:23:46.370 align:start position:0% thing for politics and and then you can write<00:23:45.059> you<00:23:45.360> you<00:23:45.539> will<00:23:45.720> be<00:23:45.840> able<00:23:46.020> to<00:23:46.140> write 00:23:46.370 --> 00:23:46.380 align:start position:0% write you you will be able to write 00:23:46.380 --> 00:23:49.190 align:start position:0% write you you will be able to write things<00:23:46.620> in<00:23:47.039> in<00:23:47.400> Cairo<00:23:47.940> for<00:23:48.059> example<00:23:48.299> or<00:23:48.900> things 00:23:49.190 --> 00:23:49.200 align:start position:0% things in in Cairo for example or things 00:23:49.200 --> 00:23:51.830 align:start position:0% things in in Cairo for example or things in<00:23:49.500> maybe<00:23:49.799> some<00:23:50.220> high<00:23:50.580> level<00:23:50.760> or<00:23:51.059> even<00:23:51.240> in<00:23:51.539> in 00:23:51.830 --> 00:23:51.840 align:start position:0% in maybe some high level or even in in 00:23:51.840 --> 00:23:54.110 align:start position:0% in maybe some high level or even in in solidity<00:23:52.320> there's<00:23:52.500> a<00:23:52.679> kbm<00:23:53.100> at<00:23:53.340> the<00:23:53.460> end<00:23:53.520> is<00:23:53.940> a 00:23:54.110 --> 00:23:54.120 align:start position:0% solidity there's a kbm at the end is a 00:23:54.120 --> 00:23:55.430 align:start position:0% solidity there's a kbm at the end is a language<00:23:54.360> that<00:23:54.659> you're<00:23:54.780> writing<00:23:55.140> a<00:23:55.260> language 00:23:55.430 --> 00:23:55.440 align:start position:0% language that you're writing a language 00:23:55.440 --> 00:23:57.470 align:start position:0% language that you're writing a language and<00:23:55.679> you<00:23:55.860> you're<00:23:56.340> building<00:23:56.580> a<00:23:56.820> zero<00:23:57.179> knowledge 00:23:57.470 --> 00:23:57.480 align:start position:0% and you you're building a zero knowledge 00:23:57.480 --> 00:23:59.090 align:start position:0% and you you're building a zero knowledge you're<00:23:57.900> building<00:23:58.140> a<00:23:58.380> zero<00:23:58.679> knowledge<00:23:58.860> there 00:23:59.090 --> 00:23:59.100 align:start position:0% you're building a zero knowledge there 00:23:59.100 --> 00:24:01.549 align:start position:0% you're building a zero knowledge there so<00:23:59.340> you<00:23:59.880> can<00:24:00.059> uh<00:24:00.659> there<00:24:00.900> is<00:24:01.080> other<00:24:01.200> projects 00:24:01.549 --> 00:24:01.559 align:start position:0% so you can uh there is other projects 00:24:01.559 --> 00:24:04.190 align:start position:0% so you can uh there is other projects like<00:24:01.740> Risk<00:24:02.520> 5<00:24:02.640> that<00:24:03.240> are<00:24:03.360> also<00:24:03.659> building<00:24:03.900> on 00:24:04.190 --> 00:24:04.200 align:start position:0% like Risk 5 that are also building on 00:24:04.200 --> 00:24:09.950 align:start position:0% like Risk 5 that are also building on top<00:24:04.320> of<00:24:04.440> that<00:24:04.559> so<00:24:04.799> it's<00:24:05.280> uh<00:24:06.380> the<00:24:07.380> the<00:24:07.700> zkbm<00:24:08.960> what 00:24:09.950 --> 00:24:09.960 align:start position:0% top of that so it's uh the the zkbm what 00:24:09.960 --> 00:24:13.010 align:start position:0% top of that so it's uh the the zkbm what brings<00:24:10.580> behind<00:24:11.580> to<00:24:11.880> the<00:24:12.120> to<00:24:12.299> the<00:24:12.480> to<00:24:12.659> the<00:24:12.900> world 00:24:13.010 --> 00:24:13.020 align:start position:0% brings behind to the to the to the world 00:24:13.020 --> 00:24:16.070 align:start position:0% brings behind to the to the to the world is<00:24:13.260> that<00:24:13.700> you<00:24:14.700> can 00:24:16.070 --> 00:24:16.080 align:start position:0% is that you can 00:24:16.080 --> 00:24:21.130 align:start position:0% is that you can have<00:24:16.980> any<00:24:17.940> any<00:24:18.780> processor<00:24:19.620> any<00:24:19.980> base<00:24:20.220> a<00:24:20.580> risk<00:24:20.940> 5 00:24:21.130 --> 00:24:21.140 align:start position:0% have any any processor any base a risk 5 00:24:21.140 --> 00:24:26.210 align:start position:0% have any any processor any base a risk 5 an<00:24:22.140> ebm<00:24:22.620> or<00:24:24.020> chiro-like<00:24:25.020> or<00:24:25.260> some<00:24:25.980> some 00:24:26.210 --> 00:24:26.220 align:start position:0% an ebm or chiro-like or some some 00:24:26.220 --> 00:24:28.390 align:start position:0% an ebm or chiro-like or some some specific 00:24:28.390 --> 00:24:28.400 align:start position:0% specific 00:24:28.400 --> 00:24:31.370 align:start position:0% specific virtual<00:24:29.400> machine<00:24:29.580> so<00:24:29.940> some<00:24:30.120> processor<00:24:30.659> and 00:24:31.370 --> 00:24:31.380 align:start position:0% virtual machine so some processor and 00:24:31.380 --> 00:24:33.230 align:start position:0% virtual machine so some processor and then<00:24:31.500> you<00:24:31.860> build<00:24:32.039> on<00:24:32.340> top<00:24:32.460> of<00:24:32.640> that<00:24:32.760> processor 00:24:33.230 --> 00:24:33.240 align:start position:0% then you build on top of that processor 00:24:33.240 --> 00:24:34.789 align:start position:0% then you build on top of that processor but<00:24:33.539> the<00:24:33.720> circuit<00:24:33.960> is<00:24:34.140> the<00:24:34.320> processor<00:24:34.620> the 00:24:34.789 --> 00:24:34.799 align:start position:0% but the circuit is the processor the 00:24:34.799 --> 00:24:36.470 align:start position:0% but the circuit is the processor the circuit<00:24:35.039> is<00:24:35.159> like<00:24:35.340> the<00:24:35.460> hardware 00:24:36.470 --> 00:24:36.480 align:start position:0% circuit is like the hardware 00:24:36.480 --> 00:24:39.529 align:start position:0% circuit is like the hardware okay<00:24:36.900> so<00:24:37.380> it's<00:24:38.280> like<00:24:38.520> maybe<00:24:39.000> we<00:24:39.240> can<00:24:39.419> talk 00:24:39.529 --> 00:24:39.539 align:start position:0% okay so it's like maybe we can talk 00:24:39.539 --> 00:24:41.450 align:start position:0% okay so it's like maybe we can talk about<00:24:39.720> Hardware<00:24:40.200> language<00:24:40.679> and<00:24:41.039> software 00:24:41.450 --> 00:24:41.460 align:start position:0% about Hardware language and software 00:24:41.460 --> 00:24:43.250 align:start position:0% about Hardware language and software language<00:24:41.700> uh<00:24:42.419> silicon<00:24:42.900> is<00:24:43.020> a<00:24:43.140> hardware 00:24:43.250 --> 00:24:43.260 align:start position:0% language uh silicon is a hardware 00:24:43.260 --> 00:24:45.830 align:start position:0% language uh silicon is a hardware language<00:24:43.679> okay<00:24:44.400> and<00:24:44.880> so<00:24:45.120> for<00:24:45.299> language<00:24:45.539> should 00:24:45.830 --> 00:24:45.840 align:start position:0% language okay and so for language should 00:24:45.840 --> 00:24:50.289 align:start position:0% language okay and so for language should be<00:24:46.100> normal<00:24:47.100> so<00:24:47.460> for<00:24:47.700> language<00:24:47.940> C<00:24:48.919> solidity 00:24:50.289 --> 00:24:50.299 align:start position:0% be normal so for language C solidity 00:24:50.299 --> 00:24:54.529 align:start position:0% be normal so for language C solidity python<00:24:51.559> or<00:24:52.559> any<00:24:52.740> other<00:24:52.980> language<00:24:53.700> that<00:24:54.240> builds 00:24:54.529 --> 00:24:54.539 align:start position:0% python or any other language that builds 00:24:54.539 --> 00:24:58.490 align:start position:0% python or any other language that builds on<00:24:54.659> top<00:24:54.780> of<00:24:54.960> that<00:24:55.200> I<00:24:55.860> don't<00:24:55.980> see<00:24:56.280> a<00:24:56.460> space<00:24:56.760> for 00:24:58.490 --> 00:24:58.500 align:start position:0% on top of that I don't see a space for 00:24:58.500 --> 00:24:59.990 align:start position:0% on top of that I don't see a space for um<00:24:58.559> I<00:24:58.799> don't<00:24:58.919> see<00:24:59.039> but<00:24:59.280> this<00:24:59.400> is<00:24:59.520> a<00:24:59.700> it's 00:24:59.990 --> 00:25:00.000 align:start position:0% um I don't see but this is a it's 00:25:00.000 --> 00:25:01.909 align:start position:0% um I don't see but this is a it's opinionated<00:25:00.539> on<00:25:00.840> me<00:25:01.020> but<00:25:01.260> I<00:25:01.380> don't<00:25:01.500> see<00:25:01.740> a 00:25:01.909 --> 00:25:01.919 align:start position:0% opinionated on me but I don't see a 00:25:01.919 --> 00:25:05.450 align:start position:0% opinionated on me but I don't see a space<00:25:02.220> for<00:25:02.900> a<00:25:03.900> specific 00:25:05.450 --> 00:25:05.460 align:start position:0% space for a specific 00:25:05.460 --> 00:25:07.610 align:start position:0% space for a specific language<00:25:06.240> as<00:25:06.600> a<00:25:06.840> specific<00:25:07.080> high<00:25:07.320> level 00:25:07.610 --> 00:25:07.620 align:start position:0% language as a specific high level 00:25:07.620 --> 00:25:10.310 align:start position:0% language as a specific high level language<00:25:08.039> because<00:25:08.580> I<00:25:09.240> think<00:25:09.360> that 00:25:10.310 --> 00:25:10.320 align:start position:0% language because I think that 00:25:10.320 --> 00:25:12.950 align:start position:0% language because I think that a<00:25:10.740> very<00:25:10.980> high<00:25:11.159> level<00:25:11.340> language<00:25:11.780> should<00:25:12.780> be 00:25:12.950 --> 00:25:12.960 align:start position:0% a very high level language should be 00:25:12.960 --> 00:25:17.390 align:start position:0% a very high level language should be enough<00:25:13.260> to<00:25:14.100> to<00:25:14.280> run<00:25:14.520> on<00:25:14.700> top<00:25:14.820> of<00:25:14.940> that 00:25:17.390 --> 00:25:17.400 align:start position:0% 00:25:17.400 --> 00:25:19.549 align:start position:0% can<00:25:17.760> I<00:25:17.940> just<00:25:18.059> add<00:25:18.240> one<00:25:18.480> thing<00:25:18.600> but<00:25:18.840> it's<00:25:19.320> what 00:25:19.549 --> 00:25:19.559 align:start position:0% can I just add one thing but it's what 00:25:19.559 --> 00:25:20.570 align:start position:0% can I just add one thing but it's what you<00:25:19.620> said 00:25:20.570 --> 00:25:20.580 align:start position:0% you said 00:25:20.580 --> 00:25:22.549 align:start position:0% you said um I<00:25:21.000> tend<00:25:21.240> to<00:25:21.360> agree<00:25:21.539> with<00:25:22.080> the<00:25:22.260> entire 00:25:22.549 --> 00:25:22.559 align:start position:0% um I tend to agree with the entire 00:25:22.559 --> 00:25:24.529 align:start position:0% um I tend to agree with the entire statement<00:25:22.860> about<00:25:23.039> however<00:25:23.460> language<00:25:23.700> there 00:25:24.529 --> 00:25:24.539 align:start position:0% statement about however language there 00:25:24.539 --> 00:25:26.149 align:start position:0% statement about however language there is<00:25:24.720> one<00:25:24.960> thing<00:25:25.200> though 00:25:26.149 --> 00:25:26.159 align:start position:0% is one thing though 00:25:26.159 --> 00:25:28.970 align:start position:0% is one thing though um<00:25:26.279> I<00:25:26.880> don't<00:25:27.179> I<00:25:27.600> I'm<00:25:28.260> not<00:25:28.440> sure<00:25:28.559> and<00:25:28.799> I<00:25:28.919> don't 00:25:28.970 --> 00:25:28.980 align:start position:0% um I don't I I'm not sure and I don't 00:25:28.980 --> 00:25:30.230 align:start position:0% um I don't I I'm not sure and I don't think<00:25:29.100> necessary<00:25:29.520> that<00:25:29.760> you<00:25:29.940> know<00:25:30.059> things 00:25:30.230 --> 00:25:30.240 align:start position:0% think necessary that you know things 00:25:30.240 --> 00:25:32.090 align:start position:0% think necessary that you know things like<00:25:30.419> python<00:25:30.779> or<00:25:30.900> Russ<00:25:31.260> will<00:25:31.440> run<00:25:31.620> enable<00:25:31.919> you 00:25:32.090 --> 00:25:32.100 align:start position:0% like python or Russ will run enable you 00:25:32.100 --> 00:25:34.370 align:start position:0% like python or Russ will run enable you to<00:25:32.220> write<00:25:32.340> vkps<00:25:32.820> tomorrow<00:25:33.059> because<00:25:33.840> there<00:25:34.200> is 00:25:34.370 --> 00:25:34.380 align:start position:0% to write vkps tomorrow because there is 00:25:34.380 --> 00:25:36.710 align:start position:0% to write vkps tomorrow because there is still<00:25:34.500> a<00:25:34.679> very<00:25:34.799> strong<00:25:35.299> Paradigm<00:25:36.299> competing 00:25:36.710 --> 00:25:36.720 align:start position:0% still a very strong Paradigm competing 00:25:36.720 --> 00:25:37.970 align:start position:0% still a very strong Paradigm competing Paradigm<00:25:37.080> Beyond<00:25:37.320> it<00:25:37.440> a<00:25:37.620> very<00:25:37.740> strong 00:25:37.970 --> 00:25:37.980 align:start position:0% Paradigm Beyond it a very strong 00:25:37.980 --> 00:25:39.649 align:start position:0% Paradigm Beyond it a very strong differences<00:25:38.400> which<00:25:38.760> might<00:25:39.240> require<00:25:39.419> you 00:25:39.649 --> 00:25:39.659 align:start position:0% differences which might require you 00:25:39.659 --> 00:25:41.330 align:start position:0% differences which might require you still<00:25:39.900> to<00:25:40.140> have<00:25:40.320> like<00:25:40.500> a<00:25:40.679> different 00:25:41.330 --> 00:25:41.340 align:start position:0% still to have like a different 00:25:41.340 --> 00:25:42.470 align:start position:0% still to have like a different accepting<00:25:41.940> that<00:25:42.059> you're<00:25:42.179> working<00:25:42.360> on 00:25:42.470 --> 00:25:42.480 align:start position:0% accepting that you're working on 00:25:42.480 --> 00:25:44.450 align:start position:0% accepting that you're working on something<00:25:42.600> different 00:25:44.450 --> 00:25:44.460 align:start position:0% something different 00:25:44.460 --> 00:25:46.610 align:start position:0% something different yeah<00:25:44.940> probably<00:25:45.179> this<00:25:45.720> is<00:25:45.900> but<00:25:46.080> this<00:25:46.260> is<00:25:46.320> this 00:25:46.610 --> 00:25:46.620 align:start position:0% yeah probably this is but this is this 00:25:46.620 --> 00:25:48.169 align:start position:0% yeah probably this is but this is this is<00:25:46.679> at<00:25:46.919> this<00:25:47.100> point<00:25:47.220> we<00:25:47.400> are<00:25:47.520> running<00:25:47.700> faster 00:25:48.169 --> 00:25:48.179 align:start position:0% is at this point we are running faster 00:25:48.179 --> 00:25:50.570 align:start position:0% is at this point we are running faster so<00:25:48.600> it's<00:25:48.900> uh<00:25:49.440> I<00:25:49.620> think<00:25:49.740> it's<00:25:49.860> just<00:25:50.039> a<00:25:50.220> matter<00:25:50.340> of 00:25:50.570 --> 00:25:50.580 align:start position:0% so it's uh I think it's just a matter of 00:25:50.580 --> 00:25:53.690 align:start position:0% so it's uh I think it's just a matter of uh<00:25:51.299> times<00:25:51.659> and<00:25:52.020> yeah<00:25:52.679> and<00:25:52.919> how<00:25:53.039> difficult<00:25:53.520> it 00:25:53.690 --> 00:25:53.700 align:start position:0% uh times and yeah and how difficult it 00:25:53.700 --> 00:25:55.549 align:start position:0% uh times and yeah and how difficult it is<00:25:53.820> you<00:25:53.940> know<00:25:54.059> right<00:25:54.179> now<00:25:54.419> uh<00:25:54.900> depending<00:25:55.260> is<00:25:55.320> if 00:25:55.549 --> 00:25:55.559 align:start position:0% is you know right now uh depending is if 00:25:55.559 --> 00:25:57.169 align:start position:0% is you know right now uh depending is if you<00:25:55.620> are<00:25:55.799> if<00:25:56.159> you<00:25:56.279> want<00:25:56.400> to<00:25:56.520> run<00:25:56.640> a<00:25:56.880> very<00:25:57.000> very 00:25:57.169 --> 00:25:57.179 align:start position:0% you are if you want to run a very very 00:25:57.179 --> 00:26:00.649 align:start position:0% you are if you want to run a very very complex<00:25:57.659> uh<00:25:58.559> uh<00:25:59.159> language<00:25:59.460> very<00:26:00.360> complex 00:26:00.649 --> 00:26:00.659 align:start position:0% complex uh uh language very complex 00:26:00.659 --> 00:26:03.409 align:start position:0% complex uh uh language very complex thing<00:26:00.840> it's<00:26:01.020> one<00:26:01.200> thing<00:26:01.380> but<00:26:02.000> if<00:26:03.000> it's<00:26:03.120> complex 00:26:03.409 --> 00:26:03.419 align:start position:0% thing it's one thing but if it's complex 00:26:03.419 --> 00:26:04.669 align:start position:0% thing it's one thing but if it's complex it's<00:26:03.600> going<00:26:03.779> to<00:26:03.900> be<00:26:03.960> also<00:26:04.140> difficult<00:26:04.380> to<00:26:04.559> write 00:26:04.669 --> 00:26:04.679 align:start position:0% it's going to be also difficult to write 00:26:04.679 --> 00:26:07.370 align:start position:0% it's going to be also difficult to write a<00:26:04.799> complexity<00:26:05.220> so<00:26:05.520> I<00:26:06.000> I<00:26:06.120> think<00:26:06.480> the<00:26:06.840> way<00:26:07.020> to<00:26:07.200> go 00:26:07.370 --> 00:26:07.380 align:start position:0% a complexity so I I think the way to go 00:26:07.380 --> 00:26:14.810 align:start position:0% a complexity so I I think the way to go is<00:26:07.620> high<00:26:07.980> level<00:26:08.220> language 00:26:14.810 --> 00:26:14.820 align:start position:0% 00:26:14.820 --> 00:26:18.830 align:start position:0% cool<00:26:15.360> yeah<00:26:15.720> so<00:26:16.559> um<00:26:16.620> I<00:26:17.279> uh<00:26:17.700> I<00:26:18.000> and<00:26:18.120> my<00:26:18.360> team<00:26:18.480> have 00:26:18.830 --> 00:26:18.840 align:start position:0% cool yeah so um I uh I and my team have 00:26:18.840 --> 00:26:21.289 align:start position:0% cool yeah so um I uh I and my team have a<00:26:19.140> very<00:26:19.440> very<00:26:19.679> strong<00:26:19.980> opinion<00:26:20.520> about<00:26:20.640> this<00:26:20.880> so 00:26:21.289 --> 00:26:21.299 align:start position:0% a very very strong opinion about this so 00:26:21.299 --> 00:26:23.330 align:start position:0% a very very strong opinion about this so I<00:26:21.659> guess<00:26:21.779> for<00:26:22.080> for<00:26:22.260> background 00:26:23.330 --> 00:26:23.340 align:start position:0% I guess for for background 00:26:23.340 --> 00:26:26.690 align:start position:0% I guess for for background um<00:26:23.400> so<00:26:23.880> Mina<00:26:24.480> the<00:26:25.020> the<00:26:25.200> Mina<00:26:25.559> protocol 00:26:26.690 --> 00:26:26.700 align:start position:0% um so Mina the the Mina protocol 00:26:26.700 --> 00:26:30.830 align:start position:0% um so Mina the the Mina protocol um we<00:26:27.419> started<00:26:27.720> building<00:26:28.020> it<00:26:28.320> in<00:26:28.799> uh<00:26:29.100> 2017. 00:26:30.830 --> 00:26:30.840 align:start position:0% um we started building it in uh 2017. 00:26:30.840 --> 00:26:33.289 align:start position:0% um we started building it in uh 2017. um<00:26:30.900> and<00:26:31.380> uh<00:26:31.860> for<00:26:32.039> those<00:26:32.400> that<00:26:32.580> don't<00:26:32.700> know<00:26:32.820> Mina 00:26:33.289 --> 00:26:33.299 align:start position:0% um and uh for those that don't know Mina 00:26:33.299 --> 00:26:36.649 align:start position:0% um and uh for those that don't know Mina basically<00:26:34.200> is<00:26:34.380> just<00:26:34.620> like<00:26:34.799> an<00:26:35.159> enormous<00:26:35.659> uh 00:26:36.649 --> 00:26:36.659 align:start position:0% basically is just like an enormous uh 00:26:36.659 --> 00:26:39.169 align:start position:0% basically is just like an enormous uh like<00:26:37.020> zkp<00:26:37.679> circuit<00:26:38.159> that<00:26:38.760> that<00:26:38.940> powers 00:26:39.169 --> 00:26:39.179 align:start position:0% like zkp circuit that that powers 00:26:39.179 --> 00:26:43.190 align:start position:0% like zkp circuit that that powers everything<00:26:39.600> so<00:26:40.140> there's<00:26:41.279> um<00:26:41.340> a<00:26:41.580> recursive<00:26:42.200> uh 00:26:43.190 --> 00:26:43.200 align:start position:0% everything so there's um a recursive uh 00:26:43.200 --> 00:26:46.370 align:start position:0% everything so there's um a recursive uh a<00:26:43.500> like<00:26:43.860> linearly<00:26:44.279> recursive<00:26:44.940> proof<00:26:45.419> for<00:26:46.020> uh 00:26:46.370 --> 00:26:46.380 align:start position:0% a like linearly recursive proof for uh 00:26:46.380 --> 00:26:48.710 align:start position:0% a like linearly recursive proof for uh compressing<00:26:46.799> the<00:26:46.980> blockchain<00:26:47.400> that<00:26:48.240> follows 00:26:48.710 --> 00:26:48.720 align:start position:0% compressing the blockchain that follows 00:26:48.720 --> 00:26:52.130 align:start position:0% compressing the blockchain that follows you<00:26:49.260> know<00:26:49.440> the<00:26:49.620> rules<00:26:49.860> of<00:26:50.220> blockchains 00:26:52.130 --> 00:26:52.140 align:start position:0% you know the rules of blockchains 00:26:52.140 --> 00:26:53.990 align:start position:0% you know the rules of blockchains um<00:26:52.200> uh<00:26:52.679> there's<00:26:52.860> like<00:26:53.039> consensus<00:26:53.580> logic 00:26:53.990 --> 00:26:54.000 align:start position:0% um uh there's like consensus logic 00:26:54.000 --> 00:26:55.669 align:start position:0% um uh there's like consensus logic there's<00:26:54.299> verifiable<00:26:54.840> random<00:26:55.260> functions 00:26:55.669 --> 00:26:55.679 align:start position:0% there's verifiable random functions 00:26:55.679 --> 00:26:58.610 align:start position:0% there's verifiable random functions where<00:26:56.279> like<00:26:56.940> uh<00:26:57.659> fractional<00:26:58.200> numbers<00:26:58.320> are 00:26:58.610 --> 00:26:58.620 align:start position:0% where like uh fractional numbers are 00:26:58.620 --> 00:27:01.370 align:start position:0% where like uh fractional numbers are approximated<00:26:59.100> using<00:26:59.700> like<00:27:00.059> crazy<00:27:00.480> uh 00:27:01.370 --> 00:27:01.380 align:start position:0% approximated using like crazy uh 00:27:01.380 --> 00:27:03.890 align:start position:0% approximated using like crazy uh calculus<00:27:01.980> things<00:27:02.520> basically<00:27:03.299> enormous 00:27:03.890 --> 00:27:03.900 align:start position:0% calculus things basically enormous 00:27:03.900 --> 00:27:06.649 align:start position:0% calculus things basically enormous enormous<00:27:04.320> programs<00:27:04.799> and<00:27:05.279> and<00:27:05.580> uh<00:27:06.240> enormous 00:27:06.649 --> 00:27:06.659 align:start position:0% enormous programs and and uh enormous 00:27:06.659 --> 00:27:08.510 align:start position:0% enormous programs and and uh enormous circuits<00:27:07.020> and<00:27:07.440> and<00:27:07.559> we<00:27:07.799> realized<00:27:08.159> very<00:27:08.340> early 00:27:08.510 --> 00:27:08.520 align:start position:0% circuits and and we realized very early 00:27:08.520 --> 00:27:11.390 align:start position:0% circuits and and we realized very early on<00:27:08.700> in<00:27:09.000> 2017<00:27:09.360> that<00:27:10.020> like<00:27:10.200> we<00:27:10.500> could<00:27:10.679> not<00:27:10.919> write 00:27:11.390 --> 00:27:11.400 align:start position:0% on in 2017 that like we could not write 00:27:11.400 --> 00:27:13.490 align:start position:0% on in 2017 that like we could not write the<00:27:11.940> circuits<00:27:12.360> manually 00:27:13.490 --> 00:27:13.500 align:start position:0% the circuits manually 00:27:13.500 --> 00:27:15.830 align:start position:0% the circuits manually um<00:27:13.559> and<00:27:13.799> and<00:27:13.919> I<00:27:14.159> agree<00:27:14.340> it's<00:27:14.460> I<00:27:14.760> I<00:27:15.179> would<00:27:15.480> I 00:27:15.830 --> 00:27:15.840 align:start position:0% um and and I agree it's I I would I 00:27:15.840 --> 00:27:17.750 align:start position:0% um and and I agree it's I I would I would<00:27:16.020> sort<00:27:16.500> of<00:27:16.620> I<00:27:16.980> mean<00:27:17.100> in<00:27:17.340> some<00:27:17.460> ways<00:27:17.640> it's 00:27:17.750 --> 00:27:17.760 align:start position:0% would sort of I mean in some ways it's 00:27:17.760 --> 00:27:19.970 align:start position:0% would sort of I mean in some ways it's like<00:27:17.940> it's<00:27:18.179> like<00:27:18.360> programming<00:27:18.900> directly<00:27:19.740> with 00:27:19.970 --> 00:27:19.980 align:start position:0% like it's like programming directly with 00:27:19.980 --> 00:27:22.370 align:start position:0% like it's like programming directly with Hardware<00:27:20.159> but<00:27:20.940> I<00:27:21.179> think<00:27:21.539> you<00:27:21.900> can<00:27:22.020> also<00:27:22.260> kind 00:27:22.370 --> 00:27:22.380 align:start position:0% Hardware but I think you can also kind 00:27:22.380 --> 00:27:23.810 align:start position:0% Hardware but I think you can also kind of<00:27:22.500> think<00:27:22.559> of<00:27:22.740> it<00:27:22.860> metaphorically<00:27:23.460> like 00:27:23.810 --> 00:27:23.820 align:start position:0% of think of it metaphorically like 00:27:23.820 --> 00:27:25.789 align:start position:0% of think of it metaphorically like writing<00:27:24.179> Assembly<00:27:24.600> Language 00:27:25.789 --> 00:27:25.799 align:start position:0% writing Assembly Language 00:27:25.799 --> 00:27:28.130 align:start position:0% writing Assembly Language um<00:27:25.860> and<00:27:26.039> and<00:27:26.159> you<00:27:26.340> know<00:27:26.460> you<00:27:27.360> can't 00:27:28.130 --> 00:27:28.140 align:start position:0% um and and you know you can't 00:27:28.140 --> 00:27:31.070 align:start position:0% um and and you know you can't like<00:27:28.740> uh<00:27:29.640> these<00:27:30.120> days<00:27:30.240> when<00:27:30.600> you're<00:27:30.779> trying<00:27:30.960> to 00:27:31.070 --> 00:27:31.080 align:start position:0% like uh these days when you're trying to 00:27:31.080 --> 00:27:32.930 align:start position:0% like uh these days when you're trying to write<00:27:31.200> a<00:27:31.559> really<00:27:31.679> complex<00:27:32.100> program<00:27:32.460> you<00:27:32.820> don't 00:27:32.930 --> 00:27:32.940 align:start position:0% write a really complex program you don't 00:27:32.940 --> 00:27:34.430 align:start position:0% write a really complex program you don't use<00:27:33.059> Assembly<00:27:33.419> Language<00:27:33.600> you<00:27:33.779> use<00:27:34.020> a<00:27:34.200> higher 00:27:34.430 --> 00:27:34.440 align:start position:0% use Assembly Language you use a higher 00:27:34.440 --> 00:27:37.490 align:start position:0% use Assembly Language you use a higher level<00:27:34.500> language<00:27:34.799> so<00:27:35.880> um<00:27:36.419> so<00:27:36.720> we<00:27:36.840> so<00:27:37.080> we<00:27:37.260> built 00:27:37.490 --> 00:27:37.500 align:start position:0% level language so um so we so we built 00:27:37.500 --> 00:27:38.990 align:start position:0% level language so um so we so we built the<00:27:37.620> first<00:27:37.740> version<00:27:37.919> of<00:27:38.159> snarky<00:27:38.580> which<00:27:38.760> is<00:27:38.880> an 00:27:38.990 --> 00:27:39.000 align:start position:0% the first version of snarky which is an 00:27:39.000 --> 00:27:42.950 align:start position:0% the first version of snarky which is an embedded<00:27:39.360> ocamel<00:27:40.020> DSL<00:27:40.980> in<00:27:41.520> 2017 00:27:42.950 --> 00:27:42.960 align:start position:0% embedded ocamel DSL in 2017 00:27:42.960 --> 00:27:45.049 align:start position:0% embedded ocamel DSL in 2017 um<00:27:43.020> and<00:27:43.440> uh<00:27:43.679> we<00:27:43.860> used<00:27:44.039> it<00:27:44.279> for<00:27:44.520> and<00:27:44.700> we<00:27:44.940> still 00:27:45.049 --> 00:27:45.059 align:start position:0% um and uh we used it for and we still 00:27:45.059 --> 00:27:47.690 align:start position:0% um and uh we used it for and we still use<00:27:45.240> it<00:27:45.419> you<00:27:45.900> know<00:27:46.020> whatever<00:27:46.380> five<00:27:47.340> years<00:27:47.460> six 00:27:47.690 --> 00:27:47.700 align:start position:0% use it you know whatever five years six 00:27:47.700 --> 00:27:48.890 align:start position:0% use it you know whatever five years six years<00:27:47.820> later 00:27:48.890 --> 00:27:48.900 align:start position:0% years later 00:27:48.900 --> 00:27:51.169 align:start position:0% years later um<00:27:48.960> and<00:27:49.860> uh<00:27:50.159> it's<00:27:50.340> great<00:27:50.460> and<00:27:50.640> we've<00:27:50.820> learned<00:27:51.059> a 00:27:51.169 --> 00:27:51.179 align:start position:0% um and uh it's great and we've learned a 00:27:51.179 --> 00:27:53.870 align:start position:0% um and uh it's great and we've learned a lot<00:27:51.299> and<00:27:51.779> and<00:27:52.020> the<00:27:52.380> the<00:27:52.500> specific 00:27:53.870 --> 00:27:53.880 align:start position:0% lot and and the the specific 00:27:53.880 --> 00:27:55.250 align:start position:0% lot and and the the specific um<00:27:53.940> you<00:27:54.059> know<00:27:54.179> we've<00:27:54.480> taken<00:27:54.720> those<00:27:54.840> ideas<00:27:55.020> and 00:27:55.250 --> 00:27:55.260 align:start position:0% um you know we've taken those ideas and 00:27:55.260 --> 00:27:57.350 align:start position:0% um you know we've taken those ideas and brought<00:27:55.380> them<00:27:55.559> to<00:27:55.679> snarky<00:27:56.159> JS<00:27:56.700> which<00:27:57.059> is<00:27:57.179> just 00:27:57.350 --> 00:27:57.360 align:start position:0% brought them to snarky JS which is just 00:27:57.360 --> 00:27:58.970 align:start position:0% brought them to snarky JS which is just sort<00:27:57.539> of<00:27:57.600> like<00:27:57.720> bringing<00:27:58.200> that<00:27:58.440> into<00:27:58.679> into 00:27:58.970 --> 00:27:58.980 align:start position:0% sort of like bringing that into into 00:27:58.980 --> 00:28:01.010 align:start position:0% sort of like bringing that into into typescript<00:27:59.400> instead<00:27:59.760> of<00:27:59.820> ocamel 00:28:01.010 --> 00:28:01.020 align:start position:0% typescript instead of ocamel 00:28:01.020 --> 00:28:04.010 align:start position:0% typescript instead of ocamel um<00:28:01.500> the<00:28:02.340> uh<00:28:02.820> you<00:28:03.120> know<00:28:03.179> we<00:28:03.299> we<00:28:03.600> thought<00:28:03.840> about 00:28:04.010 --> 00:28:04.020 align:start position:0% um the uh you know we we thought about 00:28:04.020 --> 00:28:05.930 align:start position:0% um the uh you know we we thought about like<00:28:04.320> okay<00:28:04.559> if<00:28:05.039> we<00:28:05.159> could<00:28:05.279> build<00:28:05.460> a<00:28:05.640> high<00:28:05.760> level 00:28:05.930 --> 00:28:05.940 align:start position:0% like okay if we could build a high level 00:28:05.940 --> 00:28:08.149 align:start position:0% like okay if we could build a high level language<00:28:06.600> that<00:28:06.960> compiles<00:28:07.559> into<00:28:07.860> something 00:28:08.149 --> 00:28:08.159 align:start position:0% language that compiles into something 00:28:08.159 --> 00:28:09.350 align:start position:0% language that compiles into something and<00:28:08.400> then<00:28:08.520> like<00:28:08.640> Implement<00:28:09.000> a<00:28:09.179> bunch<00:28:09.240> of 00:28:09.350 --> 00:28:09.360 align:start position:0% and then like Implement a bunch of 00:28:09.360 --> 00:28:12.169 align:start position:0% and then like Implement a bunch of optimizations<00:28:09.840> but<00:28:10.620> the<00:28:10.860> the<00:28:10.919> landscape<00:28:11.700> of 00:28:12.169 --> 00:28:12.179 align:start position:0% optimizations but the the landscape of 00:28:12.179 --> 00:28:15.950 align:start position:0% optimizations but the the landscape of proof<00:28:12.900> systems<00:28:13.380> is<00:28:14.220> we<00:28:15.120> thought<00:28:15.360> would<00:28:15.600> evolve 00:28:15.950 --> 00:28:15.960 align:start position:0% proof systems is we thought would evolve 00:28:15.960 --> 00:28:17.630 align:start position:0% proof systems is we thought would evolve quickly<00:28:16.260> it<00:28:16.559> has<00:28:16.860> evolved<00:28:17.279> quickly<00:28:17.460> it 00:28:17.630 --> 00:28:17.640 align:start position:0% quickly it has evolved quickly it 00:28:17.640 --> 00:28:19.070 align:start position:0% quickly it has evolved quickly it continues<00:28:17.880> to<00:28:18.000> evolve<00:28:18.299> quickly 00:28:19.070 --> 00:28:19.080 align:start position:0% continues to evolve quickly 00:28:19.080 --> 00:28:22.549 align:start position:0% continues to evolve quickly um<00:28:19.140> and<00:28:19.380> so<00:28:19.679> uh<00:28:20.400> it<00:28:20.640> makes<00:28:20.760> sense<00:28:21.059> right<00:28:21.539> now 00:28:22.549 --> 00:28:22.559 align:start position:0% um and so uh it makes sense right now 00:28:22.559 --> 00:28:24.230 align:start position:0% um and so uh it makes sense right now um<00:28:22.679> I<00:28:23.039> guess<00:28:23.220> it's<00:28:23.400> similar<00:28:23.700> to<00:28:23.820> what<00:28:23.940> we<00:28:24.120> were 00:28:24.230 --> 00:28:24.240 align:start position:0% um I guess it's similar to what we were 00:28:24.240 --> 00:28:26.269 align:start position:0% um I guess it's similar to what we were just<00:28:24.419> talking<00:28:24.539> about<00:28:24.659> like<00:28:25.080> uh<00:28:25.679> you<00:28:25.919> you<00:28:26.159> you 00:28:26.269 --> 00:28:26.279 align:start position:0% just talking about like uh you you you 00:28:26.279 --> 00:28:29.330 align:start position:0% just talking about like uh you you you can't<00:28:26.940> today<00:28:27.299> efficiently<00:28:28.200> use<00:28:28.500> like<00:28:28.980> a 00:28:29.330 --> 00:28:29.340 align:start position:0% can't today efficiently use like a 00:28:29.340 --> 00:28:32.210 align:start position:0% can't today efficiently use like a regular<00:28:29.640> language<00:28:30.299> directly<00:28:30.960> like<00:28:31.320> uh<00:28:31.980> like 00:28:32.210 --> 00:28:32.220 align:start position:0% regular language directly like uh like 00:28:32.220 --> 00:28:35.029 align:start position:0% regular language directly like uh like you<00:28:32.460> can't<00:28:32.580> write<00:28:32.820> a<00:28:33.059> rust<00:28:33.299> program 00:28:35.029 --> 00:28:35.039 align:start position:0% you can't write a rust program 00:28:35.039 --> 00:28:35.630 align:start position:0% you can't write a rust program um 00:28:35.630 --> 00:28:35.640 align:start position:0% um 00:28:35.640 --> 00:28:38.930 align:start position:0% um and<00:28:36.120> have<00:28:36.240> it<00:28:36.360> run<00:28:36.539> efficiently<00:28:37.020> uh 00:28:38.930 --> 00:28:38.940 align:start position:0% and have it run efficiently uh 00:28:38.940 --> 00:28:40.850 align:start position:0% and have it run efficiently uh in<00:28:39.659> you<00:28:39.840> know<00:28:39.900> for<00:28:40.080> some<00:28:40.440> definition<00:28:40.620> of 00:28:40.850 --> 00:28:40.860 align:start position:0% in you know for some definition of 00:28:40.860 --> 00:28:42.049 align:start position:0% in you know for some definition of efficiency 00:28:42.049 --> 00:28:42.059 align:start position:0% efficiency 00:28:42.059 --> 00:28:43.850 align:start position:0% efficiency um uh<00:28:42.960> but 00:28:43.850 --> 00:28:43.860 align:start position:0% um uh but 00:28:43.860 --> 00:28:46.669 align:start position:0% um uh but um<00:28:43.919> but<00:28:44.279> you<00:28:44.520> can<00:28:44.700> uh<00:28:45.419> you<00:28:45.659> can<00:28:45.779> build<00:28:46.080> like<00:28:46.380> a 00:28:46.669 --> 00:28:46.679 align:start position:0% um but you can uh you can build like a 00:28:46.679 --> 00:28:49.850 align:start position:0% um but you can uh you can build like a little<00:28:46.799> library<00:28:47.460> or<00:28:47.880> framework<00:28:48.299> in<00:28:49.260> in<00:28:49.620> a 00:28:49.850 --> 00:28:49.860 align:start position:0% little library or framework in in a 00:28:49.860 --> 00:28:52.430 align:start position:0% little library or framework in in a language<00:28:50.220> that<00:28:50.880> already<00:28:51.000> exists<00:28:51.539> embedded<00:28:52.320> in 00:28:52.430 --> 00:28:52.440 align:start position:0% language that already exists embedded in 00:28:52.440 --> 00:28:53.930 align:start position:0% language that already exists embedded in it<00:28:52.559> so<00:28:52.799> that's<00:28:52.919> what<00:28:53.100> we<00:28:53.220> did<00:28:53.279> with<00:28:53.460> ocamel 00:28:53.930 --> 00:28:53.940 align:start position:0% it so that's what we did with ocamel 00:28:53.940 --> 00:28:55.970 align:start position:0% it so that's what we did with ocamel it's<00:28:54.059> what<00:28:54.179> we<00:28:54.299> did<00:28:54.419> with<00:28:54.720> typescript 00:28:55.970 --> 00:28:55.980 align:start position:0% it's what we did with typescript 00:28:55.980 --> 00:28:59.570 align:start position:0% it's what we did with typescript um<00:28:56.039> and<00:28:56.940> uh<00:28:57.539> and<00:28:58.080> and<00:28:58.200> and<00:28:58.320> you<00:28:58.919> can<00:28:59.039> you<00:28:59.340> can 00:28:59.570 --> 00:28:59.580 align:start position:0% um and uh and and and you can you can 00:28:59.580 --> 00:29:00.649 align:start position:0% um and uh and and and you can you can build 00:29:00.649 --> 00:29:00.659 align:start position:0% build 00:29:00.659 --> 00:29:02.690 align:start position:0% build um you<00:29:01.080> can<00:29:01.140> expose<00:29:01.500> the<00:29:01.740> lowest<00:29:02.039> level<00:29:02.220> so<00:29:02.520> so 00:29:02.690 --> 00:29:02.700 align:start position:0% um you can expose the lowest level so so 00:29:02.700 --> 00:29:04.850 align:start position:0% um you can expose the lowest level so so like<00:29:03.059> the<00:29:03.480> there<00:29:03.779> are<00:29:04.080> people<00:29:04.260> who<00:29:04.559> are<00:29:04.679> like 00:29:04.850 --> 00:29:04.860 align:start position:0% like the there are people who are like 00:29:04.860 --> 00:29:07.070 align:start position:0% like the there are people who are like experts<00:29:05.279> at<00:29:05.400> optimizing<00:29:05.940> constraints<00:29:06.600> for 00:29:07.070 --> 00:29:07.080 align:start position:0% experts at optimizing constraints for 00:29:07.080 --> 00:29:08.450 align:start position:0% experts at optimizing constraints for the<00:29:07.200> proof<00:29:07.440> system<00:29:07.559> and<00:29:07.980> then<00:29:08.039> you<00:29:08.159> can<00:29:08.279> build 00:29:08.450 --> 00:29:08.460 align:start position:0% the proof system and then you can build 00:29:08.460 --> 00:29:11.149 align:start position:0% the proof system and then you can build abstractions<00:29:09.179> over<00:29:09.299> that<00:29:09.600> uh<00:29:10.320> and<00:29:10.500> with<00:29:10.740> types 00:29:11.149 --> 00:29:11.159 align:start position:0% abstractions over that uh and with types 00:29:11.159 --> 00:29:13.970 align:start position:0% abstractions over that uh and with types builds<00:29:12.120> um<00:29:12.120> you<00:29:12.299> know<00:29:12.360> type<00:29:12.779> structures<00:29:13.380> build 00:29:13.970 --> 00:29:13.980 align:start position:0% builds um you know type structures build 00:29:13.980 --> 00:29:15.769 align:start position:0% builds um you know type structures build computations 00:29:15.769 --> 00:29:15.779 align:start position:0% computations 00:29:15.779 --> 00:29:17.690 align:start position:0% computations um<00:29:15.900> and<00:29:16.380> and<00:29:16.500> this<00:29:16.980> has<00:29:17.100> worked<00:29:17.400> for<00:29:17.520> building 00:29:17.690 --> 00:29:17.700 align:start position:0% um and and this has worked for building 00:29:17.700 --> 00:29:20.210 align:start position:0% um and and this has worked for building this<00:29:18.059> enormous<00:29:18.480> uh<00:29:19.320> system<00:29:19.559> that<00:29:19.860> we<00:29:19.980> have<00:29:20.100> in 00:29:20.210 --> 00:29:20.220 align:start position:0% this enormous uh system that we have in 00:29:20.220 --> 00:29:22.730 align:start position:0% this enormous uh system that we have in Mina<00:29:20.520> and<00:29:20.880> we<00:29:21.480> see<00:29:21.720> it<00:29:21.899> starting<00:29:22.140> to<00:29:22.380> work<00:29:22.559> as 00:29:22.730 --> 00:29:22.740 align:start position:0% Mina and we see it starting to work as 00:29:22.740 --> 00:29:24.470 align:start position:0% Mina and we see it starting to work as well<00:29:22.980> for<00:29:23.460> building<00:29:23.640> really<00:29:24.000> complicated 00:29:24.470 --> 00:29:24.480 align:start position:0% well for building really complicated 00:29:24.480 --> 00:29:26.690 align:start position:0% well for building really complicated applications<00:29:25.020> with<00:29:25.799> crazy<00:29:25.980> recursion<00:29:26.520> and 00:29:26.690 --> 00:29:26.700 align:start position:0% applications with crazy recursion and 00:29:26.700 --> 00:29:32.470 align:start position:0% applications with crazy recursion and all<00:29:26.820> this<00:29:26.940> stuff<00:29:27.120> in<00:29:27.419> in<00:29:27.539> snacky.js 00:29:32.470 --> 00:29:32.480 align:start position:0% 00:29:32.480 --> 00:29:33.500 align:start position:0% yeah 00:29:33.500 --> 00:29:33.510 align:start position:0% yeah 00:29:33.510 --> 00:29:34.070 align:start position:0% yeah [Music] 00:29:34.070 --> 00:29:34.080 align:start position:0% [Music] 00:29:34.080 --> 00:29:35.330 align:start position:0% [Music] um 00:29:35.330 --> 00:29:35.340 align:start position:0% um 00:29:35.340 --> 00:29:39.769 align:start position:0% um I<00:29:36.000> think<00:29:36.120> I<00:29:36.360> disagree<00:29:36.720> with<00:29:36.840> everybody 00:29:39.769 --> 00:29:39.779 align:start position:0% 00:29:39.779 --> 00:29:43.730 align:start position:0% that's<00:29:39.960> okay<00:29:40.200> that's<00:29:40.440> why<00:29:40.620> you're<00:29:40.860> here 00:29:43.730 --> 00:29:43.740 align:start position:0% that's okay that's why you're here 00:29:43.740 --> 00:29:44.409 align:start position:0% that's okay that's why you're here um 00:29:44.409 --> 00:29:44.419 align:start position:0% um 00:29:44.419 --> 00:29:48.409 align:start position:0% um from<00:29:45.419> like<00:29:45.600> uh<00:29:46.140> I<00:29:46.919> I<00:29:47.039> think<00:29:47.520> that<00:29:47.700> using<00:29:48.059> rust 00:29:48.409 --> 00:29:48.419 align:start position:0% from like uh I I think that using rust 00:29:48.419 --> 00:29:50.269 align:start position:0% from like uh I I think that using rust at<00:29:48.779> least<00:29:48.899> for<00:29:49.080> our<00:29:49.260> use<00:29:49.500> case 00:29:50.269 --> 00:29:50.279 align:start position:0% at least for our use case 00:29:50.279 --> 00:29:50.930 align:start position:0% at least for our use case um 00:29:50.930 --> 00:29:50.940 align:start position:0% um 00:29:50.940 --> 00:29:54.169 align:start position:0% um it<00:29:51.419> would<00:29:51.539> be<00:29:51.659> a<00:29:51.779> bit<00:29:51.960> clunky<00:29:52.500> to<00:29:52.919> encode<00:29:53.399> like 00:29:54.169 --> 00:29:54.179 align:start position:0% it would be a bit clunky to encode like 00:29:54.179 --> 00:29:54.830 align:start position:0% it would be a bit clunky to encode like um 00:29:54.830 --> 00:29:54.840 align:start position:0% um 00:29:54.840 --> 00:29:57.590 align:start position:0% um semantics<00:29:55.559> for<00:29:55.799> like<00:29:55.980> privacy<00:29:56.460> like<00:29:57.179> private 00:29:57.590 --> 00:29:57.600 align:start position:0% semantics for like privacy like private 00:29:57.600 --> 00:30:00.230 align:start position:0% semantics for like privacy like private State<00:29:57.720> and<00:29:57.960> public<00:29:58.200> state<00:29:58.500> so<00:29:59.279> I<00:29:59.580> mean<00:29:59.640> it<00:29:59.880> it's 00:30:00.230 --> 00:30:00.240 align:start position:0% State and public state so I mean it it's 00:30:00.240 --> 00:30:01.789 align:start position:0% State and public state so I mean it it's possible<00:30:00.659> but 00:30:01.789 --> 00:30:01.799 align:start position:0% possible but 00:30:01.799 --> 00:30:04.310 align:start position:0% possible but um<00:30:01.919> I<00:30:02.399> think<00:30:02.520> for<00:30:02.700> the<00:30:02.880> user<00:30:03.179> just<00:30:03.539> be<00:30:03.899> a<00:30:04.140> bit 00:30:04.310 --> 00:30:04.320 align:start position:0% um I think for the user just be a bit 00:30:04.320 --> 00:30:08.210 align:start position:0% um I think for the user just be a bit clunkier<00:30:04.980> which<00:30:05.760> is<00:30:05.880> why<00:30:06.120> uh 00:30:08.210 --> 00:30:08.220 align:start position:0% clunkier which is why uh 00:30:08.220 --> 00:30:10.130 align:start position:0% clunkier which is why uh I<00:30:08.640> think<00:30:08.760> maybe<00:30:08.940> if<00:30:09.179> you're<00:30:09.299> not<00:30:09.480> using<00:30:09.899> it<00:30:10.020> for 00:30:10.130 --> 00:30:10.140 align:start position:0% I think maybe if you're not using it for 00:30:10.140 --> 00:30:12.169 align:start position:0% I think maybe if you're not using it for the<00:30:10.320> Privacy<00:30:10.620> use<00:30:10.860> case<00:30:11.100> then<00:30:11.520> high<00:30:12.000> level 00:30:12.169 --> 00:30:12.179 align:start position:0% the Privacy use case then high level 00:30:12.179 --> 00:30:15.649 align:start position:0% the Privacy use case then high level languages<00:30:12.659> like<00:30:12.899> rust<00:30:13.260> and<00:30:13.500> go<00:30:13.679> might<00:30:13.980> work 00:30:15.649 --> 00:30:15.659 align:start position:0% languages like rust and go might work 00:30:15.659 --> 00:30:16.389 align:start position:0% languages like rust and go might work um 00:30:16.389 --> 00:30:16.399 align:start position:0% um 00:30:16.399 --> 00:30:18.409 align:start position:0% um for<00:30:17.399> uh 00:30:18.409 --> 00:30:18.419 align:start position:0% for uh 00:30:18.419 --> 00:30:21.289 align:start position:0% for uh for<00:30:18.899> for<00:30:19.020> using<00:30:19.799> typescript<00:30:20.279> and<00:30:21.000> uh 00:30:21.289 --> 00:30:21.299 align:start position:0% for for using typescript and uh 00:30:21.299 --> 00:30:23.149 align:start position:0% for for using typescript and uh languages<00:30:21.779> like<00:30:22.020> that<00:30:22.140> right<00:30:22.440> now 00:30:23.149 --> 00:30:23.159 align:start position:0% languages like that right now 00:30:23.159 --> 00:30:23.990 align:start position:0% languages like that right now um 00:30:23.990 --> 00:30:24.000 align:start position:0% um 00:30:24.000 --> 00:30:26.210 align:start position:0% um when<00:30:24.539> we<00:30:24.659> were<00:30:24.840> designing<00:30:25.320> Noir<00:30:25.679> it<00:30:26.100> just 00:30:26.210 --> 00:30:26.220 align:start position:0% when we were designing Noir it just 00:30:26.220 --> 00:30:28.070 align:start position:0% when we were designing Noir it just seemed<00:30:26.520> like<00:30:26.640> we<00:30:27.000> needed<00:30:27.240> to<00:30:27.419> restrict<00:30:27.779> the 00:30:28.070 --> 00:30:28.080 align:start position:0% seemed like we needed to restrict the 00:30:28.080 --> 00:30:31.070 align:start position:0% seemed like we needed to restrict the user<00:30:28.380> from<00:30:28.620> doing<00:30:28.860> uh<00:30:29.640> very<00:30:30.299> specific<00:30:30.720> things 00:30:31.070 --> 00:30:31.080 align:start position:0% user from doing uh very specific things 00:30:31.080 --> 00:30:33.769 align:start position:0% user from doing uh very specific things that<00:30:31.640> it<00:30:32.640> seems<00:30:32.880> like<00:30:32.940> in<00:30:33.120> typescript<00:30:33.539> they 00:30:33.769 --> 00:30:33.779 align:start position:0% that it seems like in typescript they 00:30:33.779 --> 00:30:36.830 align:start position:0% that it seems like in typescript they could<00:30:33.960> just<00:30:34.140> counteract<00:30:35.039> it<00:30:35.299> and<00:30:36.299> uh<00:30:36.539> I<00:30:36.720> guess 00:30:36.830 --> 00:30:36.840 align:start position:0% could just counteract it and uh I guess 00:30:36.840 --> 00:30:38.450 align:start position:0% could just counteract it and uh I guess one<00:30:37.020> example<00:30:37.320> that<00:30:37.559> I<00:30:37.679> always<00:30:37.799> bring<00:30:37.980> up<00:30:38.220> is 00:30:38.450 --> 00:30:38.460 align:start position:0% one example that I always bring up is 00:30:38.460 --> 00:30:41.630 align:start position:0% one example that I always bring up is the<00:30:38.760> if<00:30:39.000> statements<00:30:39.620> like<00:30:40.620> uh<00:30:41.039> if<00:30:41.520> you're 00:30:41.630 --> 00:30:41.640 align:start position:0% the if statements like uh if you're 00:30:41.640 --> 00:30:43.130 align:start position:0% the if statements like uh if you're using<00:30:41.880> like<00:30:42.059> a<00:30:42.179> high<00:30:42.299> level<00:30:42.480> language<00:30:42.779> you 00:30:43.130 --> 00:30:43.140 align:start position:0% using like a high level language you 00:30:43.140 --> 00:30:45.470 align:start position:0% using like a high level language you sort<00:30:43.380> of<00:30:43.500> can't<00:30:43.740> just<00:30:44.039> do<00:30:44.220> if<00:30:44.640> something<00:30:45.179> else 00:30:45.470 --> 00:30:45.480 align:start position:0% sort of can't just do if something else 00:30:45.480 --> 00:30:48.649 align:start position:0% sort of can't just do if something else something<00:30:45.840> because<00:30:46.740> in<00:30:47.279> typescript<00:30:47.700> or<00:30:48.299> high 00:30:48.649 --> 00:30:48.659 align:start position:0% something because in typescript or high 00:30:48.659 --> 00:30:50.029 align:start position:0% something because in typescript or high level<00:30:48.899> languages<00:30:49.320> that<00:30:49.620> works<00:30:49.860> different 00:30:50.029 --> 00:30:50.039 align:start position:0% level languages that works different 00:30:50.039 --> 00:30:52.870 align:start position:0% level languages that works different from<00:30:50.399> like<00:30:50.760> a<00:30:50.880> circuit<00:30:51.240> based<00:30:51.659> if 00:30:52.870 --> 00:30:52.880 align:start position:0% from like a circuit based if 00:30:52.880 --> 00:30:55.970 align:start position:0% from like a circuit based if so<00:30:53.880> in<00:30:54.179> Cairo<00:30:54.659> we<00:30:55.320> actually 00:30:55.970 --> 00:30:55.980 align:start position:0% so in Cairo we actually 00:30:55.980 --> 00:30:58.029 align:start position:0% so in Cairo we actually do<00:30:56.760> a 00:30:58.029 --> 00:30:58.039 align:start position:0% do a 00:30:58.039 --> 00:31:01.250 align:start position:0% do a cattle<00:30:59.240> at<00:31:00.240> the<00:31:00.360> runtime<00:31:00.659> so<00:31:00.960> we<00:31:01.140> don't 00:31:01.250 --> 00:31:01.260 align:start position:0% cattle at the runtime so we don't 00:31:01.260 --> 00:31:04.430 align:start position:0% cattle at the runtime so we don't evaluate<00:31:02.100> if<00:31:02.460> statements<00:31:03.480> we<00:31:03.840> only<00:31:04.080> evaluate 00:31:04.430 --> 00:31:04.440 align:start position:0% evaluate if statements we only evaluate 00:31:04.440 --> 00:31:05.750 align:start position:0% evaluate if statements we only evaluate the<00:31:04.559> path<00:31:04.740> we<00:31:04.919> take 00:31:05.750 --> 00:31:05.760 align:start position:0% the path we take 00:31:05.760 --> 00:31:09.230 align:start position:0% the path we take that's<00:31:06.360> why<00:31:06.539> uh<00:31:06.860> yeah<00:31:07.860> uh<00:31:08.279> of<00:31:08.520> course<00:31:08.640> I<00:31:08.880> have<00:31:09.059> a 00:31:09.230 --> 00:31:09.240 align:start position:0% that's why uh yeah uh of course I have a 00:31:09.240 --> 00:31:12.169 align:start position:0% that's why uh yeah uh of course I have a counter<00:31:09.899> opinion<00:31:10.380> to<00:31:10.620> that 00:31:12.169 --> 00:31:12.179 align:start position:0% counter opinion to that 00:31:12.179 --> 00:31:14.990 align:start position:0% counter opinion to that um<00:31:12.299> yeah<00:31:12.659> I<00:31:12.899> think<00:31:13.260> uh 00:31:14.990 --> 00:31:15.000 align:start position:0% um yeah I think uh 00:31:15.000 --> 00:31:18.649 align:start position:0% um yeah I think uh um<00:31:15.179> the<00:31:15.720> the<00:31:15.840> costs<00:31:16.559> uh<00:31:17.520> of<00:31:17.760> of<00:31:18.000> using<00:31:18.360> a<00:31:18.480> custom 00:31:18.649 --> 00:31:18.659 align:start position:0% um the the costs uh of of using a custom 00:31:18.659 --> 00:31:19.730 align:start position:0% um the the costs uh of of using a custom language 00:31:19.730 --> 00:31:19.740 align:start position:0% language 00:31:19.740 --> 00:31:23.149 align:start position:0% language in<00:31:20.399> in<00:31:20.580> my<00:31:20.880> opinion<00:31:21.179> in<00:31:21.600> my<00:31:21.960> team's<00:31:22.200> opinion<00:31:22.559> uh 00:31:23.149 --> 00:31:23.159 align:start position:0% in in my opinion in my team's opinion uh 00:31:23.159 --> 00:31:25.970 align:start position:0% in in my opinion in my team's opinion uh severely<00:31:23.659> outweigh<00:31:24.659> the<00:31:24.840> the<00:31:24.960> benefits<00:31:25.500> so<00:31:25.740> I 00:31:25.970 --> 00:31:25.980 align:start position:0% severely outweigh the the benefits so I 00:31:25.980 --> 00:31:27.710 align:start position:0% severely outweigh the the benefits so I guess<00:31:26.100> just<00:31:26.520> to<00:31:26.640> talk<00:31:26.880> about<00:31:27.000> the<00:31:27.120> if<00:31:27.240> example 00:31:27.710 --> 00:31:27.720 align:start position:0% guess just to talk about the if example 00:31:27.720 --> 00:31:29.630 align:start position:0% guess just to talk about the if example yes<00:31:28.200> you<00:31:28.440> you<00:31:28.559> can't<00:31:28.860> use<00:31:29.039> the<00:31:29.340> built-in 00:31:29.630 --> 00:31:29.640 align:start position:0% yes you you can't use the built-in 00:31:29.640 --> 00:31:32.690 align:start position:0% yes you you can't use the built-in typescript<00:31:30.000> if<00:31:30.360> in<00:31:30.899> the<00:31:31.080> context<00:31:31.440> of<00:31:31.980> uh<00:31:32.460> like 00:31:32.690 --> 00:31:32.700 align:start position:0% typescript if in the context of uh like 00:31:32.700 --> 00:31:35.690 align:start position:0% typescript if in the context of uh like within<00:31:33.059> a<00:31:33.299> circuit<00:31:33.600> but<00:31:34.440> if<00:31:34.740> you<00:31:34.980> are<00:31:35.100> if<00:31:35.520> you 00:31:35.690 --> 00:31:35.700 align:start position:0% within a circuit but if you are if you 00:31:35.700 --> 00:31:37.430 align:start position:0% within a circuit but if you are if you are<00:31:35.880> Computing<00:31:36.539> a<00:31:36.720> value<00:31:36.899> that<00:31:37.200> you're<00:31:37.320> then 00:31:37.430 --> 00:31:37.440 align:start position:0% are Computing a value that you're then 00:31:37.440 --> 00:31:38.990 align:start position:0% are Computing a value that you're then using<00:31:37.740> in<00:31:37.860> a<00:31:37.980> circuit<00:31:38.279> you<00:31:38.460> can<00:31:38.520> use<00:31:38.700> if 00:31:38.990 --> 00:31:39.000 align:start position:0% using in a circuit you can use if 00:31:39.000 --> 00:31:41.090 align:start position:0% using in a circuit you can use if statements<00:31:39.659> and<00:31:39.899> and<00:31:40.200> if<00:31:40.500> you're<00:31:40.679> if<00:31:40.919> you're 00:31:41.090 --> 00:31:41.100 align:start position:0% statements and and if you're if you're 00:31:41.100 --> 00:31:42.950 align:start position:0% statements and and if you're if you're actually<00:31:41.279> in<00:31:41.520> the<00:31:41.640> circuit<00:31:42.000> there<00:31:42.419> are<00:31:42.539> tools 00:31:42.950 --> 00:31:42.960 align:start position:0% actually in the circuit there are tools 00:31:42.960 --> 00:31:45.230 align:start position:0% actually in the circuit there are tools in<00:31:43.200> in<00:31:43.320> the<00:31:43.500> typescript<00:31:43.799> ecosystem<00:31:44.340> that<00:31:45.059> can 00:31:45.230 --> 00:31:45.240 align:start position:0% in in the typescript ecosystem that can 00:31:45.240 --> 00:31:48.409 align:start position:0% in in the typescript ecosystem that can help<00:31:45.480> us<00:31:45.659> actually<00:31:46.140> Warn<00:31:46.860> and<00:31:47.340> or<00:31:47.640> error<00:31:48.179> to 00:31:48.409 --> 00:31:48.419 align:start position:0% help us actually Warn and or error to 00:31:48.419 --> 00:31:51.110 align:start position:0% help us actually Warn and or error to the<00:31:48.779> user<00:31:49.080> like<00:31:49.500> we<00:31:49.679> can<00:31:49.740> use<00:31:49.919> eslint<00:31:50.580> to 00:31:51.110 --> 00:31:51.120 align:start position:0% the user like we can use eslint to 00:31:51.120 --> 00:31:52.490 align:start position:0% the user like we can use eslint to provide<00:31:51.419> an<00:31:51.539> error<00:31:51.840> if<00:31:51.960> you're<00:31:52.020> using<00:31:52.260> an<00:31:52.380> if 00:31:52.490 --> 00:31:52.500 align:start position:0% provide an error if you're using an if 00:31:52.500 --> 00:31:54.769 align:start position:0% provide an error if you're using an if statement<00:31:52.860> in<00:31:53.159> in<00:31:53.279> a<00:31:53.520> place<00:31:53.640> that<00:31:54.120> uh<00:31:54.480> you 00:31:54.769 --> 00:31:54.779 align:start position:0% statement in in a place that uh you 00:31:54.779 --> 00:31:56.570 align:start position:0% statement in in a place that uh you shouldn't<00:31:55.020> be<00:31:55.140> and<00:31:55.380> and<00:31:55.559> that<00:31:55.860> and<00:31:56.220> of<00:31:56.399> course 00:31:56.570 --> 00:31:56.580 align:start position:0% shouldn't be and and that and of course 00:31:56.580 --> 00:31:58.850 align:start position:0% shouldn't be and and that and of course that<00:31:56.760> won't<00:31:56.880> be<00:31:57.059> perfect<00:31:57.299> but<00:31:58.260> um<00:31:58.320> we've<00:31:58.679> found 00:31:58.850 --> 00:31:58.860 align:start position:0% that won't be perfect but um we've found 00:31:58.860 --> 00:32:01.010 align:start position:0% that won't be perfect but um we've found that<00:31:59.039> that<00:31:59.220> actually<00:31:59.520> uh<00:32:00.419> is<00:32:00.600> is<00:32:00.720> working 00:32:01.010 --> 00:32:01.020 align:start position:0% that that actually uh is is working 00:32:01.020 --> 00:32:03.529 align:start position:0% that that actually uh is is working really<00:32:01.260> well<00:32:01.500> so<00:32:02.220> I<00:32:02.520> actually<00:32:02.880> I'm<00:32:03.240> agreeing 00:32:03.529 --> 00:32:03.539 align:start position:0% really well so I actually I'm agreeing 00:32:03.539 --> 00:32:05.210 align:start position:0% really well so I actually I'm agreeing with<00:32:03.600> both<00:32:03.960> of<00:32:04.140> you 00:32:05.210 --> 00:32:05.220 align:start position:0% with both of you 00:32:05.220 --> 00:32:07.669 align:start position:0% with both of you so<00:32:05.580> I'm<00:32:05.760> gonna<00:32:05.880> explain<00:32:06.000> what<00:32:06.240> I<00:32:06.360> mean<00:32:06.480> by<00:32:06.659> that 00:32:07.669 --> 00:32:07.679 align:start position:0% so I'm gonna explain what I mean by that 00:32:07.679 --> 00:32:11.149 align:start position:0% so I'm gonna explain what I mean by that um<00:32:07.740> I<00:32:08.279> agree<00:32:08.460> that<00:32:09.179> you<00:32:10.080> should<00:32:10.200> have 00:32:11.149 --> 00:32:11.159 align:start position:0% um I agree that you should have 00:32:11.159 --> 00:32:13.490 align:start position:0% um I agree that you should have um<00:32:11.279> basically<00:32:11.940> your<00:32:12.120> specific<00:32:12.480> language<00:32:12.720> at 00:32:13.490 --> 00:32:13.500 align:start position:0% um basically your specific language at 00:32:13.500 --> 00:32:15.950 align:start position:0% um basically your specific language at the<00:32:13.620> same<00:32:13.740> time<00:32:13.860> that<00:32:14.700> um<00:32:14.700> that<00:32:15.120> I<00:32:15.299> mean<00:32:15.480> that 00:32:15.950 --> 00:32:15.960 align:start position:0% the same time that um that I mean that 00:32:15.960 --> 00:32:17.810 align:start position:0% the same time that um that I mean that tends<00:32:16.260> to<00:32:16.320> help<00:32:16.500> you<00:32:16.740> think<00:32:17.220> about<00:32:17.460> the 00:32:17.810 --> 00:32:17.820 align:start position:0% tends to help you think about the 00:32:17.820 --> 00:32:20.990 align:start position:0% tends to help you think about the Computing<00:32:18.600> model<00:32:18.779> you<00:32:19.080> are<00:32:19.260> in<00:32:19.520> and<00:32:20.520> at<00:32:20.880> the 00:32:20.990 --> 00:32:21.000 align:start position:0% Computing model you are in and at the 00:32:21.000 --> 00:32:23.330 align:start position:0% Computing model you are in and at the same<00:32:21.120> time<00:32:21.360> you<00:32:21.779> also<00:32:22.140> want<00:32:22.559> a<00:32:22.919> language<00:32:23.159> that 00:32:23.330 --> 00:32:23.340 align:start position:0% same time you also want a language that 00:32:23.340 --> 00:32:24.830 align:start position:0% same time you also want a language that are<00:32:23.460> familiar<00:32:23.820> to<00:32:23.940> the<00:32:24.059> public<00:32:24.120> or<00:32:24.360> people<00:32:24.720> are 00:32:24.830 --> 00:32:24.840 align:start position:0% are familiar to the public or people are 00:32:24.840 --> 00:32:27.529 align:start position:0% are familiar to the public or people are already<00:32:25.020> using<00:32:25.440> and<00:32:26.100> so<00:32:26.340> one<00:32:26.760> solution<00:32:27.179> that 00:32:27.529 --> 00:32:27.539 align:start position:0% already using and so one solution that 00:32:27.539 --> 00:32:29.750 align:start position:0% already using and so one solution that we<00:32:27.720> I<00:32:28.080> mean<00:32:28.200> first<00:32:28.799> of<00:32:28.919> all<00:32:29.039> I'm<00:32:29.460> saying<00:32:29.640> I 00:32:29.750 --> 00:32:29.760 align:start position:0% we I mean first of all I'm saying I 00:32:29.760 --> 00:32:31.250 align:start position:0% we I mean first of all I'm saying I didn't<00:32:29.880> say<00:32:30.000> about<00:32:30.059> Cairo<00:32:30.419> so<00:32:30.600> Cairo<00:32:31.020> actually 00:32:31.250 --> 00:32:31.260 align:start position:0% didn't say about Cairo so Cairo actually 00:32:31.260 --> 00:32:33.350 align:start position:0% didn't say about Cairo so Cairo actually been<00:32:31.440> CPU<00:32:31.980> air<00:32:32.159> so<00:32:32.399> roughly<00:32:32.880> Cairo<00:32:33.179> can 00:32:33.350 --> 00:32:33.360 align:start position:0% been CPU air so roughly Cairo can 00:32:33.360 --> 00:32:35.450 align:start position:0% been CPU air so roughly Cairo can evaluate<00:32:34.020> any<00:32:34.320> program<00:32:34.559> and<00:32:34.799> it<00:32:35.039> was<00:32:35.159> clear<00:32:35.279> to 00:32:35.450 --> 00:32:35.460 align:start position:0% evaluate any program and it was clear to 00:32:35.460 --> 00:32:37.730 align:start position:0% evaluate any program and it was clear to everyone<00:32:35.580> here<00:32:35.880> but<00:32:36.059> it's<00:32:36.539> and<00:32:36.960> notably<00:32:37.500> what 00:32:37.730 --> 00:32:37.740 align:start position:0% everyone here but it's and notably what 00:32:37.740 --> 00:32:39.169 align:start position:0% everyone here but it's and notably what it<00:32:37.860> means<00:32:38.100> that<00:32:38.279> there<00:32:38.580> is<00:32:38.760> two<00:32:38.880> things<00:32:39.000> that 00:32:39.169 --> 00:32:39.179 align:start position:0% it means that there is two things that 00:32:39.179 --> 00:32:40.430 align:start position:0% it means that there is two things that you<00:32:39.299> get<00:32:39.480> that<00:32:39.600> you<00:32:39.720> don't<00:32:39.840> get<00:32:39.960> in<00:32:40.080> circuit 00:32:40.430 --> 00:32:40.440 align:start position:0% you get that you don't get in circuit 00:32:40.440 --> 00:32:43.190 align:start position:0% you get that you don't get in circuit usually<00:32:40.740> which<00:32:41.100> you<00:32:41.399> you<00:32:41.880> only<00:32:42.179> get<00:32:42.480> you<00:32:43.080> get 00:32:43.190 --> 00:32:43.200 align:start position:0% usually which you you only get you get 00:32:43.200 --> 00:32:45.710 align:start position:0% usually which you you only get you get recursion<00:32:44.520> um<00:32:44.580> very<00:32:44.940> easy<00:32:45.059> recursion<00:32:45.539> you 00:32:45.710 --> 00:32:45.720 align:start position:0% recursion um very easy recursion you 00:32:45.720 --> 00:32:47.090 align:start position:0% recursion um very easy recursion you don't<00:32:45.779> have<00:32:45.899> to<00:32:45.960> evaluate<00:32:46.260> your<00:32:46.440> circuit<00:32:46.860> and 00:32:47.090 --> 00:32:47.100 align:start position:0% don't have to evaluate your circuit and 00:32:47.100 --> 00:32:48.409 align:start position:0% don't have to evaluate your circuit and second<00:32:47.279> thing<00:32:47.580> that<00:32:47.700> you<00:32:47.820> get<00:32:47.880> for<00:32:48.059> free<00:32:48.179> is 00:32:48.409 --> 00:32:48.419 align:start position:0% second thing that you get for free is 00:32:48.419 --> 00:32:50.090 align:start position:0% second thing that you get for free is you<00:32:48.720> only<00:32:48.840> evaluate<00:32:49.260> the<00:32:49.440> if<00:32:49.620> statement<00:32:49.980> the 00:32:50.090 --> 00:32:50.100 align:start position:0% you only evaluate the if statement the 00:32:50.100 --> 00:32:51.710 align:start position:0% you only evaluate the if statement the path<00:32:50.279> you're<00:32:50.460> taking<00:32:50.640> so<00:32:51.179> when<00:32:51.299> you<00:32:51.419> have<00:32:51.539> many 00:32:51.710 --> 00:32:51.720 align:start position:0% path you're taking so when you have many 00:32:51.720 --> 00:32:53.990 align:start position:0% path you're taking so when you have many many<00:32:51.899> ifs<00:32:52.320> then<00:32:52.740> you<00:32:52.980> actually<00:32:53.220> only<00:32:53.520> you 00:32:53.990 --> 00:32:54.000 align:start position:0% many ifs then you actually only you 00:32:54.000 --> 00:32:55.549 align:start position:0% many ifs then you actually only you don't<00:32:54.120> pay<00:32:54.299> for<00:32:54.480> all<00:32:54.659> the<00:32:54.840> branches<00:32:55.260> you<00:32:55.440> only 00:32:55.549 --> 00:32:55.559 align:start position:0% don't pay for all the branches you only 00:32:55.559 --> 00:32:58.850 align:start position:0% don't pay for all the branches you only pay<00:32:55.799> for<00:32:55.980> the<00:32:56.159> the<00:32:56.340> one<00:32:56.520> you're<00:32:56.700> using<00:32:57.000> and<00:32:57.779> so 00:32:58.850 --> 00:32:58.860 align:start position:0% pay for the the one you're using and so 00:32:58.860 --> 00:33:01.250 align:start position:0% pay for the the one you're using and so um one<00:32:59.820> consequence<00:33:00.299> of<00:33:00.480> this<00:33:00.600> one<00:33:00.960> thing 00:33:01.250 --> 00:33:01.260 align:start position:0% um one consequence of this one thing 00:33:01.260 --> 00:33:02.990 align:start position:0% um one consequence of this one thing that<00:33:01.440> we<00:33:01.559> were<00:33:01.679> able<00:33:01.919> to<00:33:02.039> do<00:33:02.220> was<00:33:02.399> I<00:33:02.700> think<00:33:02.820> all 00:33:02.990 --> 00:33:03.000 align:start position:0% that we were able to do was I think all 00:33:03.000 --> 00:33:05.570 align:start position:0% that we were able to do was I think all the<00:33:03.179> team<00:33:03.299> built<00:33:03.720> is<00:33:04.020> they<00:33:04.620> started<00:33:04.980> to<00:33:05.039> see 00:33:05.570 --> 00:33:05.580 align:start position:0% the team built is they started to see 00:33:05.580 --> 00:33:09.049 align:start position:0% the team built is they started to see trans<00:33:06.240> compiler<00:33:07.140> from<00:33:07.500> one<00:33:07.740> for<00:33:08.159> the<00:33:08.460> higher 00:33:09.049 --> 00:33:09.059 align:start position:0% trans compiler from one for the higher 00:33:09.059 --> 00:33:11.269 align:start position:0% trans compiler from one for the higher than<00:33:09.120> other<00:33:09.360> language<00:33:09.960> two<00:33:10.260> characters<00:33:10.440> so<00:33:10.980> we 00:33:11.269 --> 00:33:11.279 align:start position:0% than other language two characters so we 00:33:11.279 --> 00:33:13.450 align:start position:0% than other language two characters so we have<00:33:11.460> one<00:33:11.700> right<00:33:11.940> now 00:33:13.450 --> 00:33:13.460 align:start position:0% have one right now 00:33:13.460 --> 00:33:17.269 align:start position:0% have one right now a<00:33:14.460> language<00:33:14.779> compiler<00:33:15.779> called<00:33:15.960> skyro<00:33:16.440> made<00:33:17.100> by 00:33:17.269 --> 00:33:17.279 align:start position:0% a language compiler called skyro made by 00:33:17.279 --> 00:33:19.549 align:start position:0% a language compiler called skyro made by your<00:33:17.460> team<00:33:17.640> out<00:33:18.179> of<00:33:18.299> Switzerland<00:33:18.840> which<00:33:19.440> is 00:33:19.549 --> 00:33:19.559 align:start position:0% your team out of Switzerland which is 00:33:19.559 --> 00:33:21.970 align:start position:0% your team out of Switzerland which is combining<00:33:19.980> Idris<00:33:20.340> or<00:33:20.640> just<00:33:20.820> being<00:33:21.059> a 00:33:21.970 --> 00:33:21.980 align:start position:0% combining Idris or just being a 00:33:21.980 --> 00:33:24.950 align:start position:0% combining Idris or just being a functional<00:33:22.980> language<00:33:23.159> to<00:33:23.640> Cairo<00:33:24.179> for<00:33:24.720> the 00:33:24.950 --> 00:33:24.960 align:start position:0% functional language to Cairo for the 00:33:24.960 --> 00:33:26.930 align:start position:0% functional language to Cairo for the story<00:33:25.140> if<00:33:25.740> you<00:33:25.919> are<00:33:26.159> if<00:33:26.340> you<00:33:26.519> want<00:33:26.580> to<00:33:26.760> use<00:33:26.820> it 00:33:26.930 --> 00:33:26.940 align:start position:0% story if you are if you want to use it 00:33:26.940 --> 00:33:28.250 align:start position:0% story if you are if you want to use it you'll<00:33:27.120> be<00:33:27.240> the<00:33:27.360> first<00:33:27.480> one<00:33:27.600> to<00:33:27.720> ever<00:33:27.899> use<00:33:28.140> it 00:33:28.250 --> 00:33:28.260 align:start position:0% you'll be the first one to ever use it 00:33:28.260 --> 00:33:30.769 align:start position:0% you'll be the first one to ever use it so<00:33:28.799> have<00:33:29.100> fun<00:33:29.340> uh<00:33:30.059> I<00:33:30.240> actually<00:33:30.360> never<00:33:30.539> found 00:33:30.769 --> 00:33:30.779 align:start position:0% so have fun uh I actually never found 00:33:30.779 --> 00:33:31.970 align:start position:0% so have fun uh I actually never found anyone<00:33:31.080> who<00:33:31.200> wants<00:33:31.380> to<00:33:31.440> use<00:33:31.559> a<00:33:31.740> functional 00:33:31.970 --> 00:33:31.980 align:start position:0% anyone who wants to use a functional 00:33:31.980 --> 00:33:33.529 align:start position:0% anyone who wants to use a functional language<00:33:32.159> so<00:33:32.460> maybe<00:33:32.760> there<00:33:33.000> is<00:33:33.120> one<00:33:33.240> in<00:33:33.360> this 00:33:33.529 --> 00:33:33.539 align:start position:0% language so maybe there is one in this 00:33:33.539 --> 00:33:37.190 align:start position:0% language so maybe there is one in this room<00:33:33.720> uh<00:33:34.620> but<00:33:34.980> uh<00:33:35.640> just<00:33:36.360> like<00:33:36.899> functional 00:33:37.190 --> 00:33:37.200 align:start position:0% room uh but uh just like functional 00:33:37.200 --> 00:33:40.130 align:start position:0% room uh but uh just like functional languages<00:33:37.380> so<00:33:37.740> go<00:33:37.980> for<00:33:38.159> it<00:33:38.279> uh<00:33:38.700> Idris 00:33:40.130 --> 00:33:40.140 align:start position:0% languages so go for it uh Idris 00:33:40.140 --> 00:33:40.930 align:start position:0% languages so go for it uh Idris um 00:33:40.930 --> 00:33:40.940 align:start position:0% um 00:33:40.940 --> 00:33:43.190 align:start position:0% um so<00:33:41.940> seriously<00:33:42.419> if<00:33:42.539> you<00:33:42.600> want<00:33:42.720> to<00:33:42.779> do<00:33:42.899> have<00:33:43.080> fun 00:33:43.190 --> 00:33:43.200 align:start position:0% so seriously if you want to do have fun 00:33:43.200 --> 00:33:45.769 align:start position:0% so seriously if you want to do have fun go<00:33:43.380> for<00:33:43.559> it<00:33:43.679> seriously<00:33:44.220> it's<00:33:44.399> crazy<00:33:44.760> but<00:33:45.419> uh 00:33:45.769 --> 00:33:45.779 align:start position:0% go for it seriously it's crazy but uh 00:33:45.779 --> 00:33:47.630 align:start position:0% go for it seriously it's crazy but uh but<00:33:46.080> so<00:33:46.260> I'm<00:33:46.380> trying<00:33:46.620> to<00:33:46.740> say<00:33:46.919> that 00:33:47.630 --> 00:33:47.640 align:start position:0% but so I'm trying to say that 00:33:47.640 --> 00:33:49.250 align:start position:0% but so I'm trying to say that um I<00:33:48.240> don't<00:33:48.419> know<00:33:48.539> if<00:33:48.600> it's<00:33:48.720> the<00:33:48.840> ultimate 00:33:49.250 --> 00:33:49.260 align:start position:0% um I don't know if it's the ultimate 00:33:49.260 --> 00:33:51.230 align:start position:0% um I don't know if it's the ultimate path<00:33:49.559> but<00:33:50.100> uh 00:33:51.230 --> 00:33:51.240 align:start position:0% path but uh 00:33:51.240 --> 00:33:53.210 align:start position:0% path but uh um<00:33:51.360> they<00:33:51.899> there<00:33:52.440> is<00:33:52.620> like<00:33:52.740> there<00:33:52.919> is<00:33:53.039> a<00:33:53.159> middle 00:33:53.210 --> 00:33:53.220 align:start position:0% um they there is like there is a middle 00:33:53.220 --> 00:33:58.130 align:start position:0% um they there is like there is a middle ground<00:33:53.519> can<00:33:54.299> I<00:33:54.539> uh<00:33:55.080> yeah<00:33:55.919> so<00:33:57.000> um<00:33:57.000> yeah<00:33:57.360> so<00:33:57.659> just 00:33:58.130 --> 00:33:58.140 align:start position:0% ground can I uh yeah so um yeah so just 00:33:58.140 --> 00:34:00.649 align:start position:0% ground can I uh yeah so um yeah so just uh<00:33:58.740> for<00:33:59.159> for<00:33:59.340> in<00:33:59.580> in<00:33:59.760> snarky.js<00:34:00.419> today 00:34:00.649 --> 00:34:00.659 align:start position:0% uh for for in in snarky.js today 00:34:00.659 --> 00:34:02.330 align:start position:0% uh for for in in snarky.js today connected<00:34:01.140> to<00:34:01.260> kimchi<00:34:01.679> I<00:34:01.860> mean<00:34:01.980> this<00:34:02.220> is 00:34:02.330 --> 00:34:02.340 align:start position:0% connected to kimchi I mean this is 00:34:02.340 --> 00:34:05.269 align:start position:0% connected to kimchi I mean this is powered<00:34:02.640> by<00:34:02.760> kimchi<00:34:03.179> of<00:34:03.360> course<00:34:03.480> but<00:34:03.720> uh<00:34:04.500> we<00:34:05.039> we 00:34:05.269 --> 00:34:05.279 align:start position:0% powered by kimchi of course but uh we we 00:34:05.279 --> 00:34:07.430 align:start position:0% powered by kimchi of course but uh we we also<00:34:05.580> can<00:34:05.760> handle<00:34:06.120> recursion<00:34:06.779> infinite 00:34:07.430 --> 00:34:07.440 align:start position:0% also can handle recursion infinite 00:34:07.440 --> 00:34:09.290 align:start position:0% also can handle recursion infinite recursion<00:34:07.860> and<00:34:08.040> in<00:34:08.339> snarky.js<00:34:08.940> we've<00:34:09.179> built 00:34:09.290 --> 00:34:09.300 align:start position:0% recursion and in snarky.js we've built 00:34:09.300 --> 00:34:11.510 align:start position:0% recursion and in snarky.js we've built an<00:34:09.419> interface<00:34:09.780> that's<00:34:10.020> just<00:34:10.379> it's<00:34:11.099> like 00:34:11.510 --> 00:34:11.520 align:start position:0% an interface that's just it's like 00:34:11.520 --> 00:34:13.369 align:start position:0% an interface that's just it's like essentially<00:34:12.300> the<00:34:12.419> same<00:34:12.599> is<00:34:13.020> writing<00:34:13.260> a 00:34:13.369 --> 00:34:13.379 align:start position:0% essentially the same is writing a 00:34:13.379 --> 00:34:15.409 align:start position:0% essentially the same is writing a recursive<00:34:13.740> function<00:34:14.040> so<00:34:14.339> you<00:34:14.820> just<00:34:15.000> you<00:34:15.240> you 00:34:15.409 --> 00:34:15.419 align:start position:0% recursive function so you just you you 00:34:15.419 --> 00:34:17.270 align:start position:0% recursive function so you just you you know<00:34:15.839> you<00:34:16.200> you<00:34:16.379> put<00:34:16.619> your<00:34:16.800> function<00:34:16.980> in<00:34:17.159> a 00:34:17.270 --> 00:34:17.280 align:start position:0% know you you put your function in a 00:34:17.280 --> 00:34:18.530 align:start position:0% know you you put your function in a JavaScript<00:34:17.639> object<00:34:18.000> that's<00:34:18.240> the<00:34:18.419> only 00:34:18.530 --> 00:34:18.540 align:start position:0% JavaScript object that's the only 00:34:18.540 --> 00:34:19.430 align:start position:0% JavaScript object that's the only difference 00:34:19.430 --> 00:34:19.440 align:start position:0% difference 00:34:19.440 --> 00:34:21.409 align:start position:0% difference um and<00:34:19.740> whatever<00:34:20.040> arguments<00:34:20.639> you<00:34:20.820> have<00:34:20.940> if 00:34:21.409 --> 00:34:21.419 align:start position:0% um and whatever arguments you have if 00:34:21.419 --> 00:34:24.470 align:start position:0% um and whatever arguments you have if you<00:34:21.540> type<00:34:21.659> them<00:34:21.899> as<00:34:22.080> like<00:34:22.320> proof<00:34:22.740> then<00:34:23.639> uh<00:34:24.179> the 00:34:24.470 --> 00:34:24.480 align:start position:0% you type them as like proof then uh the 00:34:24.480 --> 00:34:26.089 align:start position:0% you type them as like proof then uh the system<00:34:24.599> will<00:34:24.899> know<00:34:25.080> that<00:34:25.440> you<00:34:25.619> are<00:34:25.800> trying<00:34:25.980> to 00:34:26.089 --> 00:34:26.099 align:start position:0% system will know that you are trying to 00:34:26.099 --> 00:34:27.710 align:start position:0% system will know that you are trying to do<00:34:26.220> something<00:34:26.399> recursively<00:34:27.060> and<00:34:27.359> it'll<00:34:27.599> do 00:34:27.710 --> 00:34:27.720 align:start position:0% do something recursively and it'll do 00:34:27.720 --> 00:34:29.810 align:start position:0% do something recursively and it'll do all<00:34:27.899> the<00:34:28.020> complicated<00:34:28.740> for<00:34:28.919> you<00:34:29.040> uh<00:34:29.700> and 00:34:29.810 --> 00:34:29.820 align:start position:0% all the complicated for you uh and 00:34:29.820 --> 00:34:31.190 align:start position:0% all the complicated for you uh and in<00:34:30.119> your<00:34:30.240> in<00:34:30.359> your<00:34:30.540> code<00:34:30.659> you<00:34:30.839> can<00:34:30.960> just<00:34:31.080> say 00:34:31.190 --> 00:34:31.200 align:start position:0% in your in your code you can just say 00:34:31.200 --> 00:34:33.770 align:start position:0% in your in your code you can just say like<00:34:31.500> you<00:34:31.740> know<00:34:31.859> if<00:34:32.280> if<00:34:32.460> like<00:34:32.760> P<00:34:33.119> is<00:34:33.419> your<00:34:33.599> proof 00:34:33.770 --> 00:34:33.780 align:start position:0% like you know if if like P is your proof 00:34:33.780 --> 00:34:36.050 align:start position:0% like you know if if like P is your proof you<00:34:33.839> just<00:34:33.960> say<00:34:34.080> like<00:34:34.200> P<00:34:34.320> dot<00:34:34.679> verify<00:34:35.040> and<00:34:35.940> that 00:34:36.050 --> 00:34:36.060 align:start position:0% you just say like P dot verify and that 00:34:36.060 --> 00:34:38.570 align:start position:0% you just say like P dot verify and that sets<00:34:36.480> up<00:34:36.540> all<00:34:36.839> the<00:34:37.020> constraints<00:34:37.560> for<00:34:38.460> your 00:34:38.570 --> 00:34:38.580 align:start position:0% sets up all the constraints for your 00:34:38.580 --> 00:34:40.669 align:start position:0% sets up all the constraints for your circuit<00:34:38.940> uh<00:34:39.659> and<00:34:39.839> then<00:34:39.899> and<00:34:40.080> then<00:34:40.260> the<00:34:40.440> other 00:34:40.669 --> 00:34:40.679 align:start position:0% circuit uh and then and then the other 00:34:40.679 --> 00:34:42.530 align:start position:0% circuit uh and then and then the other bit<00:34:40.859> about<00:34:41.040> the<00:34:41.220> if<00:34:41.520> statement<00:34:41.940> branching 00:34:42.530 --> 00:34:42.540 align:start position:0% bit about the if statement branching 00:34:42.540 --> 00:34:46.129 align:start position:0% bit about the if statement branching thing<00:34:42.720> like<00:34:43.500> today<00:34:43.919> in<00:34:44.520> I<00:34:45.119> think<00:34:45.179> any<00:34:45.720> proof 00:34:46.129 --> 00:34:46.139 align:start position:0% thing like today in I think any proof 00:34:46.139 --> 00:34:48.409 align:start position:0% thing like today in I think any proof system<00:34:46.320> that<00:34:47.220> I'm<00:34:47.339> aware<00:34:47.639> of<00:34:47.760> including 00:34:48.409 --> 00:34:48.419 align:start position:0% system that I'm aware of including 00:34:48.419 --> 00:34:49.909 align:start position:0% system that I'm aware of including kimchi<00:34:48.899> including<00:34:49.379> the<00:34:49.500> current<00:34:49.560> version<00:34:49.740> of 00:34:49.909 --> 00:34:49.919 align:start position:0% kimchi including the current version of 00:34:49.919 --> 00:34:51.889 align:start position:0% kimchi including the current version of kimchi<00:34:50.700> um<00:34:50.820> yeah<00:34:50.940> you<00:34:51.119> have<00:34:51.359> to<00:34:51.480> pay<00:34:51.599> for<00:34:51.720> both 00:34:51.889 --> 00:34:51.899 align:start position:0% kimchi um yeah you have to pay for both 00:34:51.899 --> 00:34:53.869 align:start position:0% kimchi um yeah you have to pay for both branches<00:34:52.440> and<00:34:52.800> you<00:34:52.980> can<00:34:53.099> kind<00:34:53.220> of<00:34:53.339> approximate 00:34:53.869 --> 00:34:53.879 align:start position:0% branches and you can kind of approximate 00:34:53.879 --> 00:34:56.210 align:start position:0% branches and you can kind of approximate branching<00:34:54.780> by<00:34:55.080> like<00:34:55.260> multiplying<00:34:55.800> by<00:34:55.919> zero<00:34:56.220> or 00:34:56.210 --> 00:34:56.220 align:start position:0% branching by like multiplying by zero or 00:34:56.220 --> 00:34:57.109 align:start position:0% branching by like multiplying by zero or one 00:34:57.109 --> 00:34:57.119 align:start position:0% one 00:34:57.119 --> 00:35:00.109 align:start position:0% one um<00:34:57.240> but<00:34:57.599> we<00:34:57.839> are<00:34:58.020> actually<00:34:58.560> working<00:34:58.920> on<00:34:59.400> an 00:35:00.109 --> 00:35:00.119 align:start position:0% um but we are actually working on an 00:35:00.119 --> 00:35:04.150 align:start position:0% um but we are actually working on an extension<00:35:00.540> to<00:35:00.720> the<00:35:00.839> proof<00:35:01.140> system<00:35:01.820> that<00:35:03.140> will 00:35:04.150 --> 00:35:04.160 align:start position:0% extension to the proof system that will 00:35:04.160 --> 00:35:07.370 align:start position:0% extension to the proof system that will uh<00:35:05.160> will<00:35:05.520> allow<00:35:05.820> you<00:35:06.060> to<00:35:06.480> do<00:35:06.780> these<00:35:07.140> kind<00:35:07.260> of 00:35:07.370 --> 00:35:07.380 align:start position:0% uh will allow you to do these kind of 00:35:07.380 --> 00:35:09.470 align:start position:0% uh will allow you to do these kind of like<00:35:07.680> arbitrary<00:35:08.220> jumps<00:35:08.700> in<00:35:08.940> an<00:35:09.060> efficient<00:35:09.359> way 00:35:09.470 --> 00:35:09.480 align:start position:0% like arbitrary jumps in an efficient way 00:35:09.480 --> 00:35:12.290 align:start position:0% like arbitrary jumps in an efficient way and<00:35:09.960> that<00:35:10.200> though<00:35:10.500> is<00:35:10.800> uh<00:35:11.579> you<00:35:11.760> know<00:35:11.880> I'm<00:35:12.180> not 00:35:12.290 --> 00:35:12.300 align:start position:0% and that though is uh you know I'm not 00:35:12.300 --> 00:35:13.490 align:start position:0% and that though is uh you know I'm not working<00:35:12.359> on 00:35:13.490 --> 00:35:13.500 align:start position:0% working on 00:35:13.500 --> 00:35:15.290 align:start position:0% working on oh<00:35:13.920> is<00:35:14.160> it<00:35:14.220> not<00:35:14.339> a<00:35:14.460> CPU<00:35:14.760> like<00:35:14.940> you<00:35:15.060> know<00:35:15.180> like 00:35:15.290 --> 00:35:15.300 align:start position:0% oh is it not a CPU like you know like 00:35:15.300 --> 00:35:17.030 align:start position:0% oh is it not a CPU like you know like basically<00:35:15.660> running<00:35:16.440> in<00:35:16.619> the<00:35:16.740> arbitrary 00:35:17.030 --> 00:35:17.040 align:start position:0% basically running in the arbitrary 00:35:17.040 --> 00:35:18.230 align:start position:0% basically running in the arbitrary program<00:35:17.280> then 00:35:18.230 --> 00:35:18.240 align:start position:0% program then 00:35:18.240 --> 00:35:20.930 align:start position:0% program then um<00:35:18.300> yeah<00:35:18.480> I<00:35:18.660> always<00:35:18.900> VM<00:35:19.680> basically<00:35:19.980> at<00:35:20.700> that 00:35:20.930 --> 00:35:20.940 align:start position:0% um yeah I always VM basically at that 00:35:20.940 --> 00:35:23.450 align:start position:0% um yeah I always VM basically at that point<00:35:21.599> um<00:35:21.720> you<00:35:21.900> you<00:35:22.079> get<00:35:22.380> essentially<00:35:22.859> the<00:35:23.220> the 00:35:23.450 --> 00:35:23.460 align:start position:0% point um you you get essentially the the 00:35:23.460 --> 00:35:25.670 align:start position:0% point um you you get essentially the the power<00:35:23.700> of<00:35:23.880> a<00:35:24.000> VM<00:35:24.240> with<00:35:24.660> the<00:35:24.900> performance<00:35:25.320> of 00:35:25.670 --> 00:35:25.680 align:start position:0% power of a VM with the performance of 00:35:25.680 --> 00:35:27.230 align:start position:0% power of a VM with the performance of direct<00:35:25.859> circuit<00:35:26.400> yeah<00:35:26.640> so<00:35:26.820> it's<00:35:26.940> kind<00:35:27.060> of<00:35:27.180> the 00:35:27.230 --> 00:35:27.240 align:start position:0% direct circuit yeah so it's kind of the 00:35:27.240 --> 00:35:28.790 align:start position:0% direct circuit yeah so it's kind of the Holy<00:35:27.480> Grail<00:35:27.720> and<00:35:28.020> and<00:35:28.140> the<00:35:28.440> I<00:35:28.680> mean<00:35:28.740> the 00:35:28.790 --> 00:35:28.800 align:start position:0% Holy Grail and and the I mean the 00:35:28.800 --> 00:35:30.829 align:start position:0% Holy Grail and and the I mean the intuition<00:35:29.160> behind<00:35:29.460> it<00:35:29.640> is<00:35:29.760> like<00:35:30.000> uh<00:35:30.599> there's 00:35:30.829 --> 00:35:30.839 align:start position:0% intuition behind it is like uh there's 00:35:30.839 --> 00:35:32.690 align:start position:0% intuition behind it is like uh there's you<00:35:31.079> know<00:35:31.140> there's<00:35:31.500> like<00:35:31.619> look<00:35:31.800> up<00:35:31.980> tables<00:35:32.460> and 00:35:32.690 --> 00:35:32.700 align:start position:0% you know there's like look up tables and 00:35:32.700 --> 00:35:34.310 align:start position:0% you know there's like look up tables and and<00:35:32.940> custom<00:35:33.359> Gates<00:35:33.660> and<00:35:33.780> all<00:35:33.900> these<00:35:34.020> things<00:35:34.140> in 00:35:34.310 --> 00:35:34.320 align:start position:0% and custom Gates and all these things in 00:35:34.320 --> 00:35:37.550 align:start position:0% and custom Gates and all these things in Planck<00:35:35.160> um<00:35:35.280> you<00:35:35.760> can<00:35:35.820> sort<00:35:36.240> of<00:35:36.359> extend<00:35:36.780> that<00:35:37.079> to 00:35:37.550 --> 00:35:37.560 align:start position:0% Planck um you can sort of extend that to 00:35:37.560 --> 00:35:39.290 align:start position:0% Planck um you can sort of extend that to uh<00:35:38.220> allow 00:35:39.290 --> 00:35:39.300 align:start position:0% uh allow 00:35:39.300 --> 00:35:41.510 align:start position:0% uh allow um<00:35:39.359> for<00:35:39.599> like<00:35:39.780> arbitrary<00:35:40.320> Ram<00:35:40.619> like<00:35:41.220> random 00:35:41.510 --> 00:35:41.520 align:start position:0% um for like arbitrary Ram like random 00:35:41.520 --> 00:35:42.710 align:start position:0% um for like arbitrary Ram like random access<00:35:41.579> memory<00:35:42.060> and<00:35:42.240> then<00:35:42.359> you<00:35:42.420> can<00:35:42.540> kind<00:35:42.599> of 00:35:42.710 --> 00:35:42.720 align:start position:0% access memory and then you can kind of 00:35:42.720 --> 00:35:44.450 align:start position:0% access memory and then you can kind of do<00:35:42.839> another<00:35:43.020> fancy<00:35:43.440> thing<00:35:43.619> to<00:35:43.920> get<00:35:43.980> arbitrary 00:35:44.450 --> 00:35:44.460 align:start position:0% do another fancy thing to get arbitrary 00:35:44.460 --> 00:35:45.890 align:start position:0% do another fancy thing to get arbitrary jumps<00:35:44.820> efficiently 00:35:45.890 --> 00:35:45.900 align:start position:0% jumps efficiently 00:35:45.900 --> 00:35:48.410 align:start position:0% jumps efficiently um<00:35:45.960> and<00:35:46.500> the<00:35:46.680> details<00:35:47.339> of<00:35:47.400> this<00:35:47.640> I'd<00:35:48.119> have<00:35:48.300> to 00:35:48.410 --> 00:35:48.420 align:start position:0% um and the details of this I'd have to 00:35:48.420 --> 00:35:50.089 align:start position:0% um and the details of this I'd have to connect<00:35:48.540> you<00:35:48.780> with<00:35:49.079> a<00:35:49.260> cryptographer<00:35:49.859> on<00:35:49.980> my 00:35:50.089 --> 00:35:50.099 align:start position:0% connect you with a cryptographer on my 00:35:50.099 --> 00:35:53.089 align:start position:0% connect you with a cryptographer on my team<00:35:50.280> but<00:35:51.000> um<00:35:51.060> I<00:35:51.480> am<00:35:51.660> told<00:35:51.839> that<00:35:52.320> this<00:35:52.859> is<00:35:52.980> the 00:35:53.089 --> 00:35:53.099 align:start position:0% team but um I am told that this is the 00:35:53.099 --> 00:35:54.650 align:start position:0% team but um I am told that this is the path<00:35:53.339> that<00:35:53.520> we're<00:35:53.640> going<00:35:53.760> towards<00:35:54.060> I've<00:35:54.420> seen 00:35:54.650 --> 00:35:54.660 align:start position:0% path that we're going towards I've seen 00:35:54.660 --> 00:35:56.930 align:start position:0% path that we're going towards I've seen that<00:35:54.839> I've<00:35:55.020> seen<00:35:55.260> that<00:35:55.440> in<00:35:55.619> your<00:35:55.859> repo<00:35:56.339> is<00:35:56.640> the 00:35:56.930 --> 00:35:56.940 align:start position:0% that I've seen that in your repo is the 00:35:56.940 --> 00:36:00.050 align:start position:0% that I've seen that in your repo is the dynamic<00:35:57.359> lookup<00:35:57.720> table<00:35:57.960> right<00:35:58.680> yeah 00:36:00.050 --> 00:36:00.060 align:start position:0% dynamic lookup table right yeah 00:36:00.060 --> 00:36:03.530 align:start position:0% dynamic lookup table right yeah Jordan<00:36:00.720> has<00:36:01.200> been<00:36:01.440> silent<00:36:01.800> for<00:36:02.160> a<00:36:02.280> while<00:36:02.540> you 00:36:03.530 --> 00:36:03.540 align:start position:0% Jordan has been silent for a while you 00:36:03.540 --> 00:36:05.569 align:start position:0% Jordan has been silent for a while you know<00:36:03.660> at<00:36:04.020> the<00:36:04.140> end<00:36:04.260> is<00:36:04.440> this<00:36:04.619> is<00:36:04.800> what<00:36:05.280> are<00:36:05.400> you 00:36:05.569 --> 00:36:05.579 align:start position:0% know at the end is this is what are you 00:36:05.579 --> 00:36:07.490 align:start position:0% know at the end is this is what are you writing<00:36:05.880> Hardware<00:36:06.240> or<00:36:06.540> software<00:36:06.900> if<00:36:07.440> you're 00:36:07.490 --> 00:36:07.500 align:start position:0% writing Hardware or software if you're 00:36:07.500 --> 00:36:08.930 align:start position:0% writing Hardware or software if you're writing<00:36:07.859> Hardware<00:36:07.980> you<00:36:08.579> need<00:36:08.640> a<00:36:08.760> hardware 00:36:08.930 --> 00:36:08.940 align:start position:0% writing Hardware you need a hardware 00:36:08.940 --> 00:36:11.170 align:start position:0% writing Hardware you need a hardware language<00:36:09.359> if<00:36:09.720> you're<00:36:09.839> writing<00:36:10.140> software 00:36:11.170 --> 00:36:11.180 align:start position:0% language if you're writing software 00:36:11.180 --> 00:36:15.890 align:start position:0% language if you're writing software my<00:36:12.180> my<00:36:12.180> my<00:36:12.380> opinion<00:36:13.380> is<00:36:13.560> just<00:36:13.859> use<00:36:14.099> a<00:36:14.940> standard 00:36:15.890 --> 00:36:15.900 align:start position:0% my my my opinion is just use a standard 00:36:15.900 --> 00:36:19.069 align:start position:0% my my my opinion is just use a standard software<00:36:16.200> language<00:36:16.820> and<00:36:17.820> uh<00:36:18.180> why<00:36:18.599> because<00:36:18.780> the 00:36:19.069 --> 00:36:19.079 align:start position:0% software language and uh why because the 00:36:19.079 --> 00:36:21.650 align:start position:0% software language and uh why because the hardware<00:36:19.220> and<00:36:20.220> the<00:36:21.060> problem<00:36:21.180> is<00:36:21.420> that<00:36:21.540> you 00:36:21.650 --> 00:36:21.660 align:start position:0% hardware and the problem is that you 00:36:21.660 --> 00:36:22.790 align:start position:0% hardware and the problem is that you need<00:36:21.720> the<00:36:21.839> piece<00:36:22.020> of<00:36:22.079> Hardware<00:36:22.260> you<00:36:22.560> need<00:36:22.680> the 00:36:22.790 --> 00:36:22.800 align:start position:0% need the piece of Hardware you need the 00:36:22.800 --> 00:36:24.410 align:start position:0% need the piece of Hardware you need the process<00:36:22.980> or<00:36:23.160> the<00:36:23.280> hardware<00:36:23.460> that<00:36:23.820> that<00:36:24.060> can 00:36:24.410 --> 00:36:24.420 align:start position:0% process or the hardware that that can 00:36:24.420 --> 00:36:27.109 align:start position:0% process or the hardware that that can compile<00:36:24.720> to<00:36:24.900> this<00:36:25.020> software<00:36:25.440> but 00:36:27.109 --> 00:36:27.119 align:start position:0% compile to this software but 00:36:27.119 --> 00:36:30.230 align:start position:0% compile to this software but this<00:36:27.599> is<00:36:27.780> there<00:36:27.960> so<00:36:28.500> this<00:36:28.920> is<00:36:29.040> where<00:36:29.220> to<00:36:29.339> go 00:36:30.230 --> 00:36:30.240 align:start position:0% this is there so this is where to go 00:36:30.240 --> 00:36:31.730 align:start position:0% this is there so this is where to go cool 00:36:31.730 --> 00:36:31.740 align:start position:0% cool 00:36:31.740 --> 00:36:34.670 align:start position:0% cool um<00:36:31.859> I<00:36:32.220> want<00:36:32.400> to<00:36:32.640> save<00:36:32.940> some<00:36:33.240> time<00:36:33.540> for<00:36:34.140> the 00:36:34.670 --> 00:36:34.680 align:start position:0% um I want to save some time for the 00:36:34.680 --> 00:36:36.170 align:start position:0% um I want to save some time for the audience<00:36:34.920> to<00:36:35.160> ask<00:36:35.339> questions<00:36:35.520> so<00:36:35.820> we<00:36:36.000> have 00:36:36.170 --> 00:36:36.180 align:start position:0% audience to ask questions so we have 00:36:36.180 --> 00:36:39.050 align:start position:0% audience to ask questions so we have about<00:36:36.540> 15<00:36:36.900> minutes<00:36:37.320> so 00:36:39.050 --> 00:36:39.060 align:start position:0% about 15 minutes so 00:36:39.060 --> 00:36:46.690 align:start position:0% about 15 minutes so any<00:36:39.599> questions<00:36:39.839> from<00:36:40.320> the<00:36:40.440> audience 00:36:46.690 --> 00:36:46.700 align:start position:0% 00:36:46.700 --> 00:36:49.510 align:start position:0% so 00:36:49.510 --> 00:36:49.520 align:start position:0% so 00:36:49.520 --> 00:36:52.010 align:start position:0% so we<00:36:50.520> actually<00:36:50.700> touched<00:36:51.180> on<00:36:51.240> Hardware<00:36:51.540> a<00:36:51.900> lot 00:36:52.010 --> 00:36:52.020 align:start position:0% we actually touched on Hardware a lot 00:36:52.020 --> 00:36:53.390 align:start position:0% we actually touched on Hardware a lot during<00:36:52.320> this<00:36:52.500> conversation<00:36:52.859> it'd<00:36:53.280> be 00:36:53.390 --> 00:36:53.400 align:start position:0% during this conversation it'd be 00:36:53.400 --> 00:36:55.190 align:start position:0% during this conversation it'd be interesting<00:36:53.820> to<00:36:54.060> hear<00:36:54.300> uh<00:36:54.780> from<00:36:55.079> the 00:36:55.190 --> 00:36:55.200 align:start position:0% interesting to hear uh from the 00:36:55.200 --> 00:36:56.510 align:start position:0% interesting to hear uh from the different<00:36:55.320> panelists<00:36:55.980> like<00:36:56.099> what<00:36:56.339> you 00:36:56.510 --> 00:36:56.520 align:start position:0% different panelists like what you 00:36:56.520 --> 00:36:59.089 align:start position:0% different panelists like what you actually<00:36:56.700> see<00:36:56.940> the<00:36:57.240> kind<00:36:57.960> of<00:36:58.079> future<00:36:58.260> of<00:36:58.680> ZK 00:36:59.089 --> 00:36:59.099 align:start position:0% actually see the kind of future of ZK 00:36:59.099 --> 00:37:00.950 align:start position:0% actually see the kind of future of ZK Hardware<00:36:59.280> to<00:36:59.640> be<00:36:59.760> in<00:37:00.119> like<00:37:00.240> what<00:37:00.720> direction 00:37:00.950 --> 00:37:00.960 align:start position:0% Hardware to be in like what direction 00:37:00.960 --> 00:37:02.930 align:start position:0% Hardware to be in like what direction it's<00:37:01.260> going<00:37:01.440> not<00:37:01.800> that<00:37:02.040> kind<00:37:02.220> of<00:37:02.339> Hardware<00:37:02.520> we 00:37:02.930 --> 00:37:02.940 align:start position:0% it's going not that kind of Hardware we 00:37:02.940 --> 00:37:04.190 align:start position:0% it's going not that kind of Hardware we were<00:37:03.060> talking<00:37:03.240> about<00:37:03.480> I<00:37:03.839> think<00:37:03.960> we're<00:37:04.079> talking 00:37:04.190 --> 00:37:04.200 align:start position:0% were talking about I think we're talking 00:37:04.200 --> 00:37:05.450 align:start position:0% were talking about I think we're talking about<00:37:04.320> but<00:37:04.500> yeah<00:37:04.680> we<00:37:04.800> can<00:37:04.980> talk<00:37:05.099> about<00:37:05.220> that 00:37:05.450 --> 00:37:05.460 align:start position:0% about but yeah we can talk about that 00:37:05.460 --> 00:37:08.089 align:start position:0% about but yeah we can talk about that too<00:37:05.640> but<00:37:05.880> we<00:37:06.119> should<00:37:06.300> we<00:37:07.020> we<00:37:07.200> can't<00:37:07.680> we<00:37:07.920> can't 00:37:08.089 --> 00:37:08.099 align:start position:0% too but we should we we can't we can't 00:37:08.099 --> 00:37:09.470 align:start position:0% too but we should we we can't we can't talk<00:37:08.220> about<00:37:08.400> like<00:37:08.640> real<00:37:08.820> physical<00:37:09.180> Hardware 00:37:09.470 --> 00:37:09.480 align:start position:0% talk about like real physical Hardware 00:37:09.480 --> 00:37:10.550 align:start position:0% talk about like real physical Hardware as<00:37:09.780> well 00:37:10.550 --> 00:37:10.560 align:start position:0% as well 00:37:10.560 --> 00:37:12.470 align:start position:0% as well yeah<00:37:10.980> we're<00:37:11.160> talking<00:37:11.339> about<00:37:11.460> the<00:37:11.880> polynomial 00:37:12.470 --> 00:37:12.480 align:start position:0% yeah we're talking about the polynomial 00:37:12.480 --> 00:37:15.530 align:start position:0% yeah we're talking about the polynomial Hardware<00:37:12.780> it's<00:37:13.200> like<00:37:13.380> you<00:37:14.099> know<00:37:14.540> arithmetic 00:37:15.530 --> 00:37:15.540 align:start position:0% Hardware it's like you know arithmetic 00:37:15.540 --> 00:37:18.109 align:start position:0% Hardware it's like you know arithmetic Hardware<00:37:15.660> I<00:37:16.560> recognize<00:37:16.859> that<00:37:17.099> I<00:37:17.280> I<00:37:17.460> can<00:37:17.940> no 00:37:18.109 --> 00:37:18.119 align:start position:0% Hardware I recognize that I I can no 00:37:18.119 --> 00:37:20.150 align:start position:0% Hardware I recognize that I I can no we're<00:37:18.599> making<00:37:18.780> a<00:37:18.960> joke<00:37:19.079> but<00:37:19.260> let's<00:37:19.560> uh<00:37:19.800> on<00:37:19.980> the 00:37:20.150 --> 00:37:20.160 align:start position:0% we're making a joke but let's uh on the 00:37:20.160 --> 00:37:22.310 align:start position:0% we're making a joke but let's uh on the artwork<00:37:20.339> acceleration<00:37:20.760> so<00:37:21.180> I'm<00:37:21.599> gonna<00:37:21.780> take<00:37:22.140> a 00:37:22.310 --> 00:37:22.320 align:start position:0% artwork acceleration so I'm gonna take a 00:37:22.320 --> 00:37:26.030 align:start position:0% artwork acceleration so I'm gonna take a hot<00:37:22.820> stake<00:37:23.820> here<00:37:24.300> um<00:37:24.420> star<00:37:24.960> query<00:37:25.440> at<00:37:25.800> this 00:37:26.030 --> 00:37:26.040 align:start position:0% hot stake here um star query at this 00:37:26.040 --> 00:37:28.370 align:start position:0% hot stake here um star query at this stage<00:37:26.280> do<00:37:26.520> not<00:37:26.700> believe<00:37:26.880> that<00:37:27.119> we<00:37:27.300> need<00:37:27.420> them 00:37:28.370 --> 00:37:28.380 align:start position:0% stage do not believe that we need them 00:37:28.380 --> 00:37:29.810 align:start position:0% stage do not believe that we need them um<00:37:28.500> as<00:37:28.680> simple<00:37:28.859> as<00:37:29.099> that 00:37:29.810 --> 00:37:29.820 align:start position:0% um as simple as that 00:37:29.820 --> 00:37:31.670 align:start position:0% um as simple as that um the<00:37:30.060> reason<00:37:30.180> is<00:37:30.420> because<00:37:30.599> the<00:37:31.380> software 00:37:31.670 --> 00:37:31.680 align:start position:0% um the reason is because the software 00:37:31.680 --> 00:37:34.130 align:start position:0% um the reason is because the software itself<00:37:32.040> is<00:37:32.640> being<00:37:32.820> improving<00:37:33.359> so<00:37:33.660> fast<00:37:33.839> and 00:37:34.130 --> 00:37:34.140 align:start position:0% itself is being improving so fast and 00:37:34.140 --> 00:37:35.630 align:start position:0% itself is being improving so fast and the<00:37:34.260> structure<00:37:34.560> in<00:37:34.800> the<00:37:34.859> architecture<00:37:35.220> of<00:37:35.400> how 00:37:35.630 --> 00:37:35.640 align:start position:0% the structure in the architecture of how 00:37:35.640 --> 00:37:37.310 align:start position:0% the structure in the architecture of how you<00:37:35.760> do<00:37:35.940> things<00:37:36.180> has<00:37:36.480> been<00:37:36.660> improving<00:37:37.020> so<00:37:37.140> far 00:37:37.310 --> 00:37:37.320 align:start position:0% you do things has been improving so far 00:37:37.320 --> 00:37:40.310 align:start position:0% you do things has been improving so far that<00:37:37.619> at<00:37:38.220> this<00:37:38.460> stage<00:37:38.700> we<00:37:39.300> we<00:37:39.599> don't<00:37:39.900> know<00:37:40.079> what 00:37:40.310 --> 00:37:40.320 align:start position:0% that at this stage we we don't know what 00:37:40.320 --> 00:37:42.170 align:start position:0% that at this stage we we don't know what the<00:37:40.440> future<00:37:40.619> will<00:37:40.859> look<00:37:41.040> like<00:37:41.220> and<00:37:41.700> so<00:37:41.880> what<00:37:42.060> I 00:37:42.170 --> 00:37:42.180 align:start position:0% the future will look like and so what I 00:37:42.180 --> 00:37:44.810 align:start position:0% the future will look like and so what I mean<00:37:42.359> by<00:37:42.480> this<00:37:42.780> is<00:37:43.200> hardware<00:37:43.680> development<00:37:44.579> is 00:37:44.810 --> 00:37:44.820 align:start position:0% mean by this is hardware development is 00:37:44.820 --> 00:37:46.250 align:start position:0% mean by this is hardware development is you're<00:37:45.060> roughly<00:37:45.420> a<00:37:45.540> year<00:37:45.599> and<00:37:45.720> a<00:37:45.900> half<00:37:45.960> before 00:37:46.250 --> 00:37:46.260 align:start position:0% you're roughly a year and a half before 00:37:46.260 --> 00:37:48.290 align:start position:0% you're roughly a year and a half before getting<00:37:46.560> to<00:37:46.800> production<00:37:47.040> and<00:37:47.460> a<00:37:47.880> year<00:37:48.060> and<00:37:48.180> a 00:37:48.290 --> 00:37:48.300 align:start position:0% getting to production and a year and a 00:37:48.300 --> 00:37:50.870 align:start position:0% getting to production and a year and a half<00:37:48.420> from<00:37:48.900> a<00:37:49.079> year<00:37:49.200> and<00:37:49.320> a<00:37:49.500> half<00:37:49.500> ago<00:37:49.800> uh<00:37:50.579> Cairo 00:37:50.870 --> 00:37:50.880 align:start position:0% half from a year and a half ago uh Cairo 00:37:50.880 --> 00:37:53.270 align:start position:0% half from a year and a half ago uh Cairo were<00:37:51.060> barely<00:37:51.359> working<00:37:51.599> started<00:37:52.440> with<00:37:52.740> in 00:37:53.270 --> 00:37:53.280 align:start position:0% were barely working started with in 00:37:53.280 --> 00:37:56.690 align:start position:0% were barely working started with in premises<00:37:53.760> uh<00:37:54.540> recursion<00:37:55.020> wasn't<00:37:55.200> working 00:37:56.690 --> 00:37:56.700 align:start position:0% premises uh recursion wasn't working 00:37:56.700 --> 00:37:58.730 align:start position:0% premises uh recursion wasn't working um<00:37:56.760> we<00:37:57.300> and<00:37:57.720> and<00:37:57.780> so<00:37:58.079> for<00:37:58.260> instance<00:37:58.380> the<00:37:58.560> thing 00:37:58.730 --> 00:37:58.740 align:start position:0% um we and and so for instance the thing 00:37:58.740 --> 00:38:00.470 align:start position:0% um we and and so for instance the thing that<00:37:58.920> we<00:37:59.099> are<00:37:59.220> working<00:37:59.339> on<00:37:59.579> right<00:37:59.760> now<00:37:59.940> so<00:38:00.240> we 00:38:00.470 --> 00:38:00.480 align:start position:0% that we are working on right now so we 00:38:00.480 --> 00:38:02.569 align:start position:0% that we are working on right now so we already<00:38:00.720> do<00:38:00.960> recursive<00:38:01.440> recursive<00:38:02.040> proof<00:38:02.400> on 00:38:02.569 --> 00:38:02.579 align:start position:0% already do recursive recursive proof on 00:38:02.579 --> 00:38:05.329 align:start position:0% already do recursive recursive proof on production<00:38:03.000> today<00:38:03.359> of<00:38:03.960> approve<00:38:04.440> ourself<00:38:04.740> but 00:38:05.329 --> 00:38:05.339 align:start position:0% production today of approve ourself but 00:38:05.339 --> 00:38:06.650 align:start position:0% production today of approve ourself but like<00:38:05.460> for<00:38:05.640> instance<00:38:05.820> one<00:38:06.060> architecture<00:38:06.480> we're 00:38:06.650 --> 00:38:06.660 align:start position:0% like for instance one architecture we're 00:38:06.660 --> 00:38:08.930 align:start position:0% like for instance one architecture we're not<00:38:06.839> doing<00:38:07.020> it<00:38:07.200> at<00:38:07.320> the<00:38:07.500> moment<00:38:07.680> is 00:38:08.930 --> 00:38:08.940 align:start position:0% not doing it at the moment is 00:38:08.940 --> 00:38:10.490 align:start position:0% not doing it at the moment is um<00:38:09.000> basically<00:38:09.480> a 00:38:10.490 --> 00:38:10.500 align:start position:0% um basically a 00:38:10.500 --> 00:38:12.349 align:start position:0% um basically a three<00:38:10.859> of<00:38:11.040> proofs<00:38:11.339> like<00:38:11.640> basically<00:38:11.940> right<00:38:12.180> now 00:38:12.349 --> 00:38:12.359 align:start position:0% three of proofs like basically right now 00:38:12.359 --> 00:38:14.030 align:start position:0% three of proofs like basically right now the<00:38:12.480> only<00:38:12.599> thing<00:38:12.839> we<00:38:12.960> do<00:38:13.140> is<00:38:13.320> we<00:38:13.740> have<00:38:13.800> what<00:38:13.920> you 00:38:14.030 --> 00:38:14.040 align:start position:0% the only thing we do is we have what you 00:38:14.040 --> 00:38:17.210 align:start position:0% the only thing we do is we have what you call<00:38:14.220> jobs<00:38:14.460> and<00:38:14.940> jobs<00:38:15.180> are<00:38:15.660> like<00:38:15.900> those<00:38:16.560> Stark 00:38:17.210 --> 00:38:17.220 align:start position:0% call jobs and jobs are like those Stark 00:38:17.220 --> 00:38:19.609 align:start position:0% call jobs and jobs are like those Stark Nets<00:38:17.700> starkware<00:38:18.300> infrastructure<00:38:19.079> used<00:38:19.380> all 00:38:19.609 --> 00:38:19.619 align:start position:0% Nets starkware infrastructure used all 00:38:19.619 --> 00:38:21.349 align:start position:0% Nets starkware infrastructure used all of<00:38:19.740> that<00:38:19.859> to<00:38:19.980> Sharp<00:38:20.460> and<00:38:20.640> so<00:38:20.820> all<00:38:21.000> the 00:38:21.349 --> 00:38:21.359 align:start position:0% of that to Sharp and so all the 00:38:21.359 --> 00:38:23.750 align:start position:0% of that to Sharp and so all the customers<00:38:21.839> and<00:38:22.260> you<00:38:22.380> start<00:38:22.560> and<00:38:22.800> included<00:38:23.220> of 00:38:23.750 --> 00:38:23.760 align:start position:0% customers and you start and included of 00:38:23.760 --> 00:38:25.430 align:start position:0% customers and you start and included of the<00:38:24.000> infrastructure<00:38:24.599> are<00:38:24.839> sharing<00:38:25.200> the<00:38:25.320> same 00:38:25.430 --> 00:38:25.440 align:start position:0% the infrastructure are sharing the same 00:38:25.440 --> 00:38:28.069 align:start position:0% the infrastructure are sharing the same proof<00:38:25.740> so<00:38:26.040> every<00:38:26.700> every<00:38:27.240> one<00:38:27.540> of<00:38:27.720> that<00:38:27.839> is 00:38:28.069 --> 00:38:28.079 align:start position:0% proof so every every one of that is 00:38:28.079 --> 00:38:29.690 align:start position:0% proof so every every one of that is using<00:38:28.380> is<00:38:28.619> basically<00:38:28.920> everyone<00:38:29.099> is<00:38:29.400> paying<00:38:29.640> a 00:38:29.690 --> 00:38:29.700 align:start position:0% using is basically everyone is paying a 00:38:29.700 --> 00:38:31.490 align:start position:0% using is basically everyone is paying a marginal<00:38:30.060> cost<00:38:30.240> of<00:38:30.420> the<00:38:30.540> proof<00:38:30.839> cost<00:38:31.079> on<00:38:31.380> that 00:38:31.490 --> 00:38:31.500 align:start position:0% marginal cost of the proof cost on that 00:38:31.500 --> 00:38:33.349 align:start position:0% marginal cost of the proof cost on that and<00:38:32.160> so 00:38:33.349 --> 00:38:33.359 align:start position:0% and so 00:38:33.359 --> 00:38:35.270 align:start position:0% and so um<00:38:33.420> so<00:38:34.020> for<00:38:34.200> instance<00:38:34.380> diversify<00:38:35.040> or 00:38:35.270 --> 00:38:35.280 align:start position:0% um so for instance diversify or 00:38:35.280 --> 00:38:36.890 align:start position:0% um so for instance diversify or immutable<00:38:35.640> like<00:38:35.940> right<00:38:36.119> now<00:38:36.300> is<00:38:36.420> having<00:38:36.599> like 00:38:36.890 --> 00:38:36.900 align:start position:0% immutable like right now is having like 00:38:36.900 --> 00:38:38.750 align:start position:0% immutable like right now is having like 70ps<00:38:37.380> in<00:38:37.859> their<00:38:38.040> environment<00:38:38.400> and<00:38:38.579> they're 00:38:38.750 --> 00:38:38.760 align:start position:0% 70ps in their environment and they're 00:38:38.760 --> 00:38:41.510 align:start position:0% 70ps in their environment and they're using<00:38:39.060> a<00:38:39.540> significant<00:38:40.140> amount<00:38:40.500> of<00:38:40.560> a<00:38:41.280> step 00:38:41.510 --> 00:38:41.520 align:start position:0% using a significant amount of a step 00:38:41.520 --> 00:38:43.670 align:start position:0% using a significant amount of a step within<00:38:41.820> this<00:38:41.940> proof<00:38:42.240> so<00:38:42.599> they<00:38:42.839> do<00:38:43.020> one<00:38:43.200> job<00:38:43.380> and 00:38:43.670 --> 00:38:43.680 align:start position:0% within this proof so they do one job and 00:38:43.680 --> 00:38:45.829 align:start position:0% within this proof so they do one job and we<00:38:43.980> have<00:38:44.160> other<00:38:44.640> proof<00:38:45.119> and<00:38:45.240> also<00:38:45.720> another 00:38:45.829 --> 00:38:45.839 align:start position:0% we have other proof and also another 00:38:45.839 --> 00:38:49.849 align:start position:0% we have other proof and also another type<00:38:46.200> of<00:38:46.260> of<00:38:46.619> the<00:38:47.099> job<00:38:47.280> is<00:38:47.460> approved<00:38:48.240> so<00:38:48.359> we 00:38:49.849 --> 00:38:49.859 align:start position:0% type of of the job is approved so we 00:38:49.859 --> 00:38:52.609 align:start position:0% type of of the job is approved so we um<00:38:49.920> so<00:38:50.460> we<00:38:50.880> don't<00:38:51.240> really<00:38:51.540> we<00:38:51.839> didn't<00:38:52.079> went<00:38:52.380> all 00:38:52.609 --> 00:38:52.619 align:start position:0% um so we don't really we didn't went all 00:38:52.619 --> 00:38:54.650 align:start position:0% um so we don't really we didn't went all the<00:38:52.800> way<00:38:52.859> yet<00:38:53.099> into<00:38:53.579> that<00:38:53.940> uh<00:38:54.359> tree 00:38:54.650 --> 00:38:54.660 align:start position:0% the way yet into that uh tree 00:38:54.660 --> 00:38:56.990 align:start position:0% the way yet into that uh tree architecture<00:38:55.200> and<00:38:55.920> so 00:38:56.990 --> 00:38:57.000 align:start position:0% architecture and so 00:38:57.000 --> 00:38:58.849 align:start position:0% architecture and so full<00:38:57.599> Hardware 00:38:58.849 --> 00:38:58.859 align:start position:0% full Hardware 00:38:58.859 --> 00:39:00.530 align:start position:0% full Hardware um there<00:38:59.400> is<00:38:59.460> already<00:38:59.700> a<00:38:59.940> significant<00:39:00.359> like 00:39:00.530 --> 00:39:00.540 align:start position:0% um there is already a significant like 00:39:00.540 --> 00:39:02.510 align:start position:0% um there is already a significant like you<00:39:00.720> know<00:39:00.780> the<00:39:00.960> the<00:39:01.140> thing<00:39:01.740> Central<00:39:01.980> fact<00:39:02.339> that 00:39:02.510 --> 00:39:02.520 align:start position:0% you know the the thing Central fact that 00:39:02.520 --> 00:39:04.190 align:start position:0% you know the the thing Central fact that we<00:39:02.760> can't<00:39:02.940> really<00:39:03.119> say<00:39:03.420> this<00:39:03.720> is<00:39:03.839> very<00:39:03.960> good 00:39:04.190 --> 00:39:04.200 align:start position:0% we can't really say this is very good 00:39:04.200 --> 00:39:06.770 align:start position:0% we can't really say this is very good that<00:39:04.980> said<00:39:05.160> I<00:39:05.880> have<00:39:06.000> a<00:39:06.119> friend<00:39:06.240> of<00:39:06.359> mine<00:39:06.540> I 00:39:06.770 --> 00:39:06.780 align:start position:0% that said I have a friend of mine I 00:39:06.780 --> 00:39:07.750 align:start position:0% that said I have a friend of mine I guess 00:39:07.750 --> 00:39:07.760 align:start position:0% guess 00:39:07.760 --> 00:39:10.790 align:start position:0% guess umovich<00:39:08.760> from<00:39:09.000> uh<00:39:09.240> the<00:39:09.960> company<00:39:10.079> called<00:39:10.440> wait 00:39:10.790 --> 00:39:10.800 align:start position:0% umovich from uh the company called wait 00:39:10.800 --> 00:39:13.490 align:start position:0% umovich from uh the company called wait uh<00:39:11.280> it's<00:39:11.460> uh<00:39:11.960> which<00:39:12.960> is<00:39:13.020> a<00:39:13.140> very<00:39:13.260> good<00:39:13.380> friend 00:39:13.490 --> 00:39:13.500 align:start position:0% uh it's uh which is a very good friend 00:39:13.500 --> 00:39:15.050 align:start position:0% uh it's uh which is a very good friend of<00:39:13.680> mine<00:39:13.800> he's<00:39:14.220> also<00:39:14.579> already<00:39:14.579> working<00:39:14.880> on 00:39:15.050 --> 00:39:15.060 align:start position:0% of mine he's also already working on 00:39:15.060 --> 00:39:16.310 align:start position:0% of mine he's also already working on this<00:39:15.180> making<00:39:15.420> uh<00:39:15.900> groundbreaking 00:39:16.310 --> 00:39:16.320 align:start position:0% this making uh groundbreaking 00:39:16.320 --> 00:39:18.650 align:start position:0% this making uh groundbreaking Improvement<00:39:16.800> on<00:39:17.160> outbreakable<00:39:18.000> explanation 00:39:18.650 --> 00:39:18.660 align:start position:0% Improvement on outbreakable explanation 00:39:18.660 --> 00:39:20.690 align:start position:0% Improvement on outbreakable explanation Shake<00:39:19.380> pronunciation<00:39:19.740> or<00:39:20.099> even<00:39:20.220> like<00:39:20.520> you 00:39:20.690 --> 00:39:20.700 align:start position:0% Shake pronunciation or even like you 00:39:20.700 --> 00:39:23.030 align:start position:0% Shake pronunciation or even like you know<00:39:20.820> uh<00:39:21.359> MSM<00:39:22.079> which<00:39:22.260> I<00:39:22.380> have<00:39:22.440> no<00:39:22.560> idea<00:39:22.800> what<00:39:22.920> it 00:39:23.030 --> 00:39:23.040 align:start position:0% know uh MSM which I have no idea what it 00:39:23.040 --> 00:39:26.030 align:start position:0% know uh MSM which I have no idea what it means<00:39:23.280> but<00:39:23.880> uh<00:39:24.480> I<00:39:24.839> would<00:39:24.960> let<00:39:25.079> him<00:39:25.260> to<00:39:25.500> you<00:39:25.859> he's 00:39:26.030 --> 00:39:26.040 align:start position:0% means but uh I would let him to you he's 00:39:26.040 --> 00:39:27.589 align:start position:0% means but uh I would let him to you he's not<00:39:26.220> here<00:39:26.400> today<00:39:26.520> but<00:39:26.760> yeah<00:39:26.940> I<00:39:27.180> would<00:39:27.300> let<00:39:27.420> him 00:39:27.589 --> 00:39:27.599 align:start position:0% not here today but yeah I would let him 00:39:27.599 --> 00:39:30.950 align:start position:0% not here today but yeah I would let him answer<00:39:28.260> that<00:39:28.560> another<00:39:28.800> day 00:39:30.950 --> 00:39:30.960 align:start position:0% answer that another day 00:39:30.960 --> 00:39:33.829 align:start position:0% answer that another day um<00:39:31.020> I<00:39:31.260> I<00:39:31.500> yeah<00:39:31.920> so<00:39:32.460> different<00:39:32.940> I<00:39:33.660> guess 00:39:33.829 --> 00:39:33.839 align:start position:0% um I I yeah so different I guess 00:39:33.839 --> 00:39:36.109 align:start position:0% um I I yeah so different I guess slightly<00:39:34.260> different<00:39:34.440> opinion<00:39:35.160> um<00:39:35.220> so<00:39:35.520> in<00:39:35.820> in 00:39:36.109 --> 00:39:36.119 align:start position:0% slightly different opinion um so in in 00:39:36.119 --> 00:39:39.050 align:start position:0% slightly different opinion um so in in uh<00:39:36.599> in<00:39:37.140> snarky<00:39:37.500> when<00:39:37.680> you<00:39:37.800> use<00:39:37.920> snarky<00:39:38.280> JS<00:39:38.579> for 00:39:39.050 --> 00:39:39.060 align:start position:0% uh in snarky when you use snarky JS for 00:39:39.060 --> 00:39:41.270 align:start position:0% uh in snarky when you use snarky JS for writing<00:39:39.420> applications<00:39:39.839> on<00:39:40.020> Mina<00:39:40.380> or<00:39:40.800> just<00:39:40.980> in 00:39:41.270 --> 00:39:41.280 align:start position:0% writing applications on Mina or just in 00:39:41.280 --> 00:39:43.790 align:start position:0% writing applications on Mina or just in general<00:39:41.400> we're<00:39:42.300> encouraging 00:39:43.790 --> 00:39:43.800 align:start position:0% general we're encouraging 00:39:43.800 --> 00:39:45.650 align:start position:0% general we're encouraging um<00:39:43.859> the<00:39:44.280> the<00:39:44.460> proof<00:39:44.820> computation<00:39:45.240> to<00:39:45.480> happen 00:39:45.650 --> 00:39:45.660 align:start position:0% um the the proof computation to happen 00:39:45.660 --> 00:39:48.109 align:start position:0% um the the proof computation to happen actually<00:39:46.140> like<00:39:46.440> on<00:39:46.680> the<00:39:46.800> user's<00:39:47.220> machine 00:39:48.109 --> 00:39:48.119 align:start position:0% actually like on the user's machine 00:39:48.119 --> 00:39:50.690 align:start position:0% actually like on the user's machine um<00:39:48.240> in<00:39:48.420> this<00:39:48.540> way<00:39:48.660> you<00:39:48.900> get<00:39:49.079> uh<00:39:49.619> privacy<00:39:50.040> and 00:39:50.690 --> 00:39:50.700 align:start position:0% um in this way you get uh privacy and 00:39:50.700 --> 00:39:53.270 align:start position:0% um in this way you get uh privacy and and<00:39:50.940> uh<00:39:51.420> you<00:39:51.780> know<00:39:51.900> there's<00:39:52.380> there<00:39:52.680> are<00:39:52.980> ways 00:39:53.270 --> 00:39:53.280 align:start position:0% and uh you know there's there are ways 00:39:53.280 --> 00:39:54.829 align:start position:0% and uh you know there's there are ways that<00:39:53.400> you<00:39:53.579> can<00:39:53.700> sort<00:39:53.940> of<00:39:54.060> do<00:39:54.240> part<00:39:54.540> of<00:39:54.720> the 00:39:54.829 --> 00:39:54.839 align:start position:0% that you can sort of do part of the 00:39:54.839 --> 00:39:56.990 align:start position:0% that you can sort of do part of the computation<00:39:55.320> on<00:39:55.980> the<00:39:56.099> machine<00:39:56.280> to<00:39:56.760> get<00:39:56.880> the 00:39:56.990 --> 00:39:57.000 align:start position:0% computation on the machine to get the 00:39:57.000 --> 00:39:58.970 align:start position:0% computation on the machine to get the privacy<00:39:57.300> and<00:39:57.480> do<00:39:57.599> the<00:39:57.720> rest<00:39:57.839> on<00:39:58.020> a<00:39:58.200> server<00:39:58.500> all 00:39:58.970 --> 00:39:58.980 align:start position:0% privacy and do the rest on a server all 00:39:58.980 --> 00:40:00.109 align:start position:0% privacy and do the rest on a server all these<00:39:59.099> things<00:39:59.220> but 00:40:00.109 --> 00:40:00.119 align:start position:0% these things but 00:40:00.119 --> 00:40:00.710 align:start position:0% these things but um 00:40:00.710 --> 00:40:00.720 align:start position:0% um 00:40:00.720 --> 00:40:02.690 align:start position:0% um when<00:40:01.380> you<00:40:01.560> have<00:40:01.680> a<00:40:01.859> proof<00:40:02.099> system<00:40:02.220> that<00:40:02.460> has<00:40:02.579> a 00:40:02.690 --> 00:40:02.700 align:start position:0% when you have a proof system that has a 00:40:02.700 --> 00:40:04.370 align:start position:0% when you have a proof system that has a lot<00:40:02.760> of<00:40:02.880> cool<00:40:02.940> features<00:40:03.359> in<00:40:03.480> it<00:40:03.660> uh<00:40:04.260> like 00:40:04.370 --> 00:40:04.380 align:start position:0% lot of cool features in it uh like 00:40:04.380 --> 00:40:05.510 align:start position:0% lot of cool features in it uh like kimchi 00:40:05.510 --> 00:40:05.520 align:start position:0% kimchi 00:40:05.520 --> 00:40:07.250 align:start position:0% kimchi um<00:40:05.579> it's<00:40:05.880> it's<00:40:06.119> slower<00:40:06.540> than<00:40:06.720> a<00:40:06.900> proof<00:40:07.140> system 00:40:07.250 --> 00:40:07.260 align:start position:0% um it's it's slower than a proof system 00:40:07.260 --> 00:40:09.470 align:start position:0% um it's it's slower than a proof system that<00:40:07.560> has<00:40:07.680> a<00:40:07.859> lot<00:40:07.920> less<00:40:08.040> features<00:40:08.460> in<00:40:08.579> it 00:40:09.470 --> 00:40:09.480 align:start position:0% that has a lot less features in it 00:40:09.480 --> 00:40:12.170 align:start position:0% that has a lot less features in it um<00:40:09.540> and<00:40:10.200> uh<00:40:10.619> Hardware<00:40:10.859> acceleration<00:40:11.579> would 00:40:12.170 --> 00:40:12.180 align:start position:0% um and uh Hardware acceleration would 00:40:12.180 --> 00:40:14.870 align:start position:0% um and uh Hardware acceleration would then<00:40:12.420> kind<00:40:12.780> of<00:40:12.900> you<00:40:13.140> know<00:40:13.200> make<00:40:13.500> it<00:40:13.619> faster<00:40:13.859> I<00:40:14.579> I 00:40:14.870 --> 00:40:14.880 align:start position:0% then kind of you know make it faster I I 00:40:14.880 --> 00:40:17.690 align:start position:0% then kind of you know make it faster I I think<00:40:15.119> it<00:40:15.480> would<00:40:15.599> be<00:40:15.839> uh<00:40:16.500> cool<00:40:16.740> I<00:40:17.099> guess<00:40:17.460> like 00:40:17.690 --> 00:40:17.700 align:start position:0% think it would be uh cool I guess like 00:40:17.700 --> 00:40:19.609 align:start position:0% think it would be uh cool I guess like you<00:40:18.240> know<00:40:18.359> we're<00:40:18.780> encouraging<00:40:19.200> people<00:40:19.440> with 00:40:19.609 --> 00:40:19.619 align:start position:0% you know we're encouraging people with 00:40:19.619 --> 00:40:23.450 align:start position:0% you know we're encouraging people with snarky<00:40:19.980> Jazz<00:40:20.160> to<00:40:20.820> write<00:40:21.060> uh<00:40:22.020> circuits<00:40:22.980> with 00:40:23.450 --> 00:40:23.460 align:start position:0% snarky Jazz to write uh circuits with 00:40:23.460 --> 00:40:25.490 align:start position:0% snarky Jazz to write uh circuits with recursion<00:40:24.119> with<00:40:24.540> with<00:40:24.660> linear<00:40:25.020> recursion<00:40:25.380> or 00:40:25.490 --> 00:40:25.500 align:start position:0% recursion with with linear recursion or 00:40:25.500 --> 00:40:27.170 align:start position:0% recursion with with linear recursion or tree<00:40:25.680> recursion<00:40:26.160> that's<00:40:26.520> been<00:40:26.700> working<00:40:26.940> in 00:40:27.170 --> 00:40:27.180 align:start position:0% tree recursion that's been working in 00:40:27.180 --> 00:40:29.030 align:start position:0% tree recursion that's been working in Mina<00:40:27.540> and<00:40:27.900> Mina's<00:40:28.260> mainnet<00:40:28.560> for<00:40:28.680> a<00:40:28.740> year<00:40:28.800> and<00:40:28.920> a 00:40:29.030 --> 00:40:29.040 align:start position:0% Mina and Mina's mainnet for a year and a 00:40:29.040 --> 00:40:31.370 align:start position:0% Mina and Mina's mainnet for a year and a half<00:40:29.099> sort<00:40:29.520> of<00:40:29.640> internally<00:40:30.119> and<00:40:30.420> and<00:40:30.720> now<00:40:31.020> on 00:40:31.370 --> 00:40:31.380 align:start position:0% half sort of internally and and now on 00:40:31.380 --> 00:40:33.410 align:start position:0% half sort of internally and and now on our<00:40:31.500> decentralized<00:40:32.040> test<00:40:32.160> net<00:40:32.339> we<00:40:32.640> have<00:40:32.820> uh 00:40:33.410 --> 00:40:33.420 align:start position:0% our decentralized test net we have uh 00:40:33.420 --> 00:40:34.370 align:start position:0% our decentralized test net we have uh you<00:40:33.540> know<00:40:33.599> you<00:40:33.720> can<00:40:33.839> do<00:40:33.900> it<00:40:34.020> with<00:40:34.140> custom 00:40:34.370 --> 00:40:34.380 align:start position:0% you know you can do it with custom 00:40:34.380 --> 00:40:36.710 align:start position:0% you know you can do it with custom circuits<00:40:34.980> and<00:40:35.400> and<00:40:35.640> settle<00:40:36.119> on<00:40:36.240> chain<00:40:36.359> and<00:40:36.599> all 00:40:36.710 --> 00:40:36.720 align:start position:0% circuits and and settle on chain and all 00:40:36.720 --> 00:40:38.329 align:start position:0% circuits and and settle on chain and all that<00:40:36.960> stuff<00:40:37.079> and<00:40:37.200> it<00:40:37.320> works 00:40:38.329 --> 00:40:38.339 align:start position:0% that stuff and it works 00:40:38.339 --> 00:40:40.250 align:start position:0% that stuff and it works um<00:40:38.400> uh<00:40:39.000> and<00:40:39.180> and<00:40:39.300> yeah<00:40:39.599> and<00:40:39.780> it's<00:40:39.900> a<00:40:40.079> little<00:40:40.140> bit 00:40:40.250 --> 00:40:40.260 align:start position:0% um uh and and yeah and it's a little bit 00:40:40.260 --> 00:40:41.270 align:start position:0% um uh and and yeah and it's a little bit slow<00:40:40.380> right<00:40:40.619> now<00:40:40.800> we're<00:40:40.920> working<00:40:41.040> on 00:40:41.270 --> 00:40:41.280 align:start position:0% slow right now we're working on 00:40:41.280 --> 00:40:44.089 align:start position:0% slow right now we're working on optimizing<00:40:41.760> it<00:40:42.359> um<00:40:42.480> but<00:40:42.900> I<00:40:43.140> I<00:40:43.320> am<00:40:43.500> imagining<00:40:43.920> a 00:40:44.089 --> 00:40:44.099 align:start position:0% optimizing it um but I I am imagining a 00:40:44.099 --> 00:40:46.250 align:start position:0% optimizing it um but I I am imagining a world<00:40:44.280> like<00:40:44.880> I<00:40:45.119> think<00:40:45.240> a<00:40:45.420> cool<00:40:45.540> world<00:40:45.780> would<00:40:46.079> be 00:40:46.250 --> 00:40:46.260 align:start position:0% world like I think a cool world would be 00:40:46.260 --> 00:40:49.130 align:start position:0% world like I think a cool world would be one<00:40:46.740> in<00:40:46.920> which<00:40:47.099> like<00:40:47.339> The<00:40:47.640> Ledger<00:40:48.000> that<00:40:48.780> we<00:40:48.900> all 00:40:49.130 --> 00:40:49.140 align:start position:0% one in which like The Ledger that we all 00:40:49.140 --> 00:40:50.030 align:start position:0% one in which like The Ledger that we all have 00:40:50.030 --> 00:40:50.040 align:start position:0% have 00:40:50.040 --> 00:40:51.829 align:start position:0% have um<00:40:50.099> or<00:40:50.280> something<00:40:50.640> like<00:40:50.880> that<00:40:51.060> uh<00:40:51.540> that<00:40:51.720> has 00:40:51.829 --> 00:40:51.839 align:start position:0% um or something like that uh that has 00:40:51.839 --> 00:40:54.050 align:start position:0% um or something like that uh that has our<00:40:51.960> wallet<00:40:52.260> on<00:40:52.380> it<00:40:52.500> also<00:40:52.800> would<00:40:52.980> have<00:40:53.160> like<00:40:53.640> a 00:40:54.050 --> 00:40:54.060 align:start position:0% our wallet on it also would have like a 00:40:54.060 --> 00:40:57.349 align:start position:0% our wallet on it also would have like a a<00:40:54.540> snark<00:40:54.960> accelerator<00:40:55.520> uh<00:40:56.520> companionship<00:40:57.119> or 00:40:57.349 --> 00:40:57.359 align:start position:0% a snark accelerator uh companionship or 00:40:57.359 --> 00:40:58.670 align:start position:0% a snark accelerator uh companionship or something 00:40:58.670 --> 00:40:58.680 align:start position:0% something 00:40:58.680 --> 00:41:00.530 align:start position:0% something um<00:40:58.800> I<00:40:59.220> I<00:40:59.400> don't<00:40:59.640> think<00:40:59.760> that's<00:40:59.880> coming<00:41:00.240> anytime 00:41:00.530 --> 00:41:00.540 align:start position:0% um I I don't think that's coming anytime 00:41:00.540 --> 00:41:02.930 align:start position:0% um I I don't think that's coming anytime soon<00:41:00.660> but<00:41:01.800> um<00:41:01.859> something<00:41:02.160> like<00:41:02.400> that<00:41:02.520> could<00:41:02.760> be 00:41:02.930 --> 00:41:02.940 align:start position:0% soon but um something like that could be 00:41:02.940 --> 00:41:06.410 align:start position:0% soon but um something like that could be cool<00:41:03.440> and<00:41:04.440> and<00:41:04.560> even<00:41:04.800> like<00:41:05.640> obviously<00:41:06.180> in<00:41:06.300> the 00:41:06.410 --> 00:41:06.420 align:start position:0% cool and and even like obviously in the 00:41:06.420 --> 00:41:08.150 align:start position:0% cool and and even like obviously in the shorter<00:41:06.660> term<00:41:06.839> taking<00:41:07.440> advantage<00:41:07.800> of<00:41:07.980> like 00:41:08.150 --> 00:41:08.160 align:start position:0% shorter term taking advantage of like 00:41:08.160 --> 00:41:11.450 align:start position:0% shorter term taking advantage of like gpus<00:41:08.640> fpgas<00:41:09.300> and<00:41:09.540> silicon<00:41:10.020> like<00:41:10.619> at<00:41:10.980> any<00:41:11.220> level 00:41:11.450 --> 00:41:11.460 align:start position:0% gpus fpgas and silicon like at any level 00:41:11.460 --> 00:41:12.950 align:start position:0% gpus fpgas and silicon like at any level I<00:41:12.000> think 00:41:12.950 --> 00:41:12.960 align:start position:0% I think 00:41:12.960 --> 00:41:15.050 align:start position:0% I think would<00:41:13.380> be<00:41:13.500> helpful<00:41:13.800> uh<00:41:14.339> because<00:41:14.520> it<00:41:14.700> would<00:41:14.880> it 00:41:15.050 --> 00:41:15.060 align:start position:0% would be helpful uh because it would it 00:41:15.060 --> 00:41:17.270 align:start position:0% would be helpful uh because it would it makes<00:41:15.359> these<00:41:15.839> proof<00:41:16.200> systems<00:41:16.500> that<00:41:16.740> are<00:41:16.920> I 00:41:17.270 --> 00:41:17.280 align:start position:0% makes these proof systems that are I 00:41:17.280 --> 00:41:19.490 align:start position:0% makes these proof systems that are I think<00:41:17.460> like<00:41:17.640> have<00:41:17.820> a<00:41:17.940> lot<00:41:18.060> more<00:41:18.180> features 00:41:19.490 --> 00:41:19.500 align:start position:0% think like have a lot more features 00:41:19.500 --> 00:41:22.670 align:start position:0% think like have a lot more features um<00:41:19.560> uh<00:41:20.400> more<00:41:20.760> you<00:41:21.180> know<00:41:21.300> faster<00:41:22.020> so<00:41:22.260> you<00:41:22.440> can<00:41:22.500> do 00:41:22.670 --> 00:41:22.680 align:start position:0% um uh more you know faster so you can do 00:41:22.680 --> 00:41:24.290 align:start position:0% um uh more you know faster so you can do different<00:41:23.099> kinds<00:41:23.460> of<00:41:23.460> applications<00:41:23.880> than<00:41:24.119> you 00:41:24.290 --> 00:41:24.300 align:start position:0% different kinds of applications than you 00:41:24.300 --> 00:41:27.410 align:start position:0% different kinds of applications than you could<00:41:24.480> if<00:41:25.140> if<00:41:25.320> they<00:41:25.560> were<00:41:25.680> slower 00:41:27.410 --> 00:41:27.420 align:start position:0% could if if they were slower 00:41:27.420 --> 00:41:30.770 align:start position:0% could if if they were slower I<00:41:27.960> would<00:41:28.200> distinguish<00:41:28.859> this<00:41:29.760> is<00:41:29.880> actually<00:41:30.240> a 00:41:30.770 --> 00:41:30.780 align:start position:0% I would distinguish this is actually a 00:41:30.780 --> 00:41:33.710 align:start position:0% I would distinguish this is actually a very<00:41:31.200> um<00:41:31.460> very<00:41:32.460> different<00:41:32.700> so<00:41:33.119> talk<00:41:33.599> about 00:41:33.710 --> 00:41:33.720 align:start position:0% very um very different so talk about 00:41:33.720 --> 00:41:35.150 align:start position:0% very um very different so talk about zero<00:41:34.079> watch<00:41:34.260> proof<00:41:34.560> we<00:41:34.740> can<00:41:34.800> distinguish 00:41:35.150 --> 00:41:35.160 align:start position:0% zero watch proof we can distinguish 00:41:35.160 --> 00:41:37.790 align:start position:0% zero watch proof we can distinguish between<00:41:35.339> a<00:41:35.640> small<00:41:35.820> small<00:41:36.420> proofs<00:41:36.900> and<00:41:37.140> uh<00:41:37.619> big 00:41:37.790 --> 00:41:37.800 align:start position:0% between a small small proofs and uh big 00:41:37.800 --> 00:41:41.030 align:start position:0% between a small small proofs and uh big proofs<00:41:38.220> because<00:41:38.460> the<00:41:39.000> big<00:41:39.480> profile<00:41:39.900> for<00:41:40.079> ckvms 00:41:41.030 --> 00:41:41.040 align:start position:0% proofs because the big profile for ckvms 00:41:41.040 --> 00:41:43.130 align:start position:0% proofs because the big profile for ckvms and<00:41:41.280> for<00:41:41.460> uh<00:41:41.760> roll<00:41:42.000> ups<00:41:42.359> and<00:41:42.420> for<00:41:42.660> when<00:41:43.020> you 00:41:43.130 --> 00:41:43.140 align:start position:0% and for uh roll ups and for when you 00:41:43.140 --> 00:41:44.390 align:start position:0% and for uh roll ups and for when you want<00:41:43.260> to<00:41:43.380> do<00:41:43.440> aggregation<00:41:43.920> and<00:41:44.099> these<00:41:44.280> high 00:41:44.390 --> 00:41:44.400 align:start position:0% want to do aggregation and these high 00:41:44.400 --> 00:41:46.970 align:start position:0% want to do aggregation and these high computation<00:41:44.820> stuff<00:41:45.180> and<00:41:45.599> then<00:41:45.839> small<00:41:46.619> proof 00:41:46.970 --> 00:41:46.980 align:start position:0% computation stuff and then small proof 00:41:46.980 --> 00:41:48.410 align:start position:0% computation stuff and then small proof more<00:41:47.160> questions<00:41:47.700> but<00:41:47.940> they're<00:41:48.060> more<00:41:48.180> related 00:41:48.410 --> 00:41:48.420 align:start position:0% more questions but they're more related 00:41:48.420 --> 00:41:50.329 align:start position:0% more questions but they're more related to<00:41:48.540> something<00:41:48.720> like<00:41:48.960> Identity<00:41:49.500> or<00:41:49.800> a<00:41:49.980> game<00:41:50.099> or 00:41:50.329 --> 00:41:50.339 align:start position:0% to something like Identity or a game or 00:41:50.339 --> 00:41:51.109 align:start position:0% to something like Identity or a game or something<00:41:50.460> that<00:41:50.700> you<00:41:50.820> want<00:41:50.940> to<00:41:51.000> run 00:41:51.109 --> 00:41:51.119 align:start position:0% something that you want to run 00:41:51.119 --> 00:41:53.210 align:start position:0% something that you want to run especially<00:41:51.540> in<00:41:51.720> the<00:41:51.839> client 00:41:53.210 --> 00:41:53.220 align:start position:0% especially in the client 00:41:53.220 --> 00:41:56.990 align:start position:0% especially in the client I<00:41:53.700> think<00:41:53.820> the<00:41:54.119> client<00:41:54.420> has<00:41:55.200> a<00:41:55.560> lot<00:41:55.740> of<00:41:55.859> sense<00:41:56.040> uh 00:41:56.990 --> 00:41:57.000 align:start position:0% I think the client has a lot of sense uh 00:41:57.000 --> 00:41:58.849 align:start position:0% I think the client has a lot of sense uh because<00:41:57.300> it's<00:41:57.780> uh<00:41:58.079> it's<00:41:58.380> where<00:41:58.560> the<00:41:58.680> hardware 00:41:58.849 --> 00:41:58.859 align:start position:0% because it's uh it's where the hardware 00:41:58.859 --> 00:42:02.450 align:start position:0% because it's uh it's where the hardware you<00:41:59.520> know<00:41:59.579> you<00:41:59.820> are<00:42:00.060> building<00:42:00.300> you<00:42:00.900> do<00:42:01.079> a<00:42:01.320> a<00:42:01.680> big 00:42:02.450 --> 00:42:02.460 align:start position:0% you know you are building you do a a big 00:42:02.460 --> 00:42:04.849 align:start position:0% you know you are building you do a a big investment<00:42:02.880> but<00:42:03.180> then<00:42:03.420> you<00:42:03.780> you<00:42:03.960> you<00:42:04.079> you<00:42:04.260> can 00:42:04.849 --> 00:42:04.859 align:start position:0% investment but then you you you you can 00:42:04.859 --> 00:42:07.310 align:start position:0% investment but then you you you you can uh<00:42:05.700> spread<00:42:06.000> to<00:42:06.119> many<00:42:06.359> mobile<00:42:06.599> phones<00:42:07.020> or<00:42:07.200> too 00:42:07.310 --> 00:42:07.320 align:start position:0% uh spread to many mobile phones or too 00:42:07.320 --> 00:42:10.010 align:start position:0% uh spread to many mobile phones or too many<00:42:07.500> uh<00:42:07.920> places<00:42:08.160> so<00:42:08.640> this<00:42:08.820> makes<00:42:09.119> a<00:42:09.780> lot<00:42:09.900> of 00:42:10.010 --> 00:42:10.020 align:start position:0% many uh places so this makes a lot of 00:42:10.020 --> 00:42:13.030 align:start position:0% many uh places so this makes a lot of sense<00:42:10.200> and<00:42:10.800> for<00:42:11.280> things<00:42:11.579> like<00:42:11.940> you<00:42:12.300> know<00:42:12.420> these 00:42:13.030 --> 00:42:13.040 align:start position:0% sense and for things like you know these 00:42:13.040 --> 00:42:16.370 align:start position:0% sense and for things like you know these privacy<00:42:14.040> things<00:42:14.220> for<00:42:14.579> for<00:42:14.820> things<00:42:15.119> like<00:42:15.420> uh<00:42:15.839> uh 00:42:16.370 --> 00:42:16.380 align:start position:0% privacy things for for things like uh uh 00:42:16.380 --> 00:42:19.130 align:start position:0% privacy things for for things like uh uh gaming<00:42:16.800> for<00:42:17.099> things<00:42:17.220> like<00:42:17.400> identity<00:42:18.060> uh<00:42:18.839> just 00:42:19.130 --> 00:42:19.140 align:start position:0% gaming for things like identity uh just 00:42:19.140 --> 00:42:21.410 align:start position:0% gaming for things like identity uh just proving<00:42:19.980> things<00:42:20.099> about<00:42:20.280> your<00:42:20.579> data<00:42:21.000> I<00:42:21.240> know 00:42:21.410 --> 00:42:21.420 align:start position:0% proving things about your data I know 00:42:21.420 --> 00:42:24.530 align:start position:0% proving things about your data I know all<00:42:21.660> this<00:42:21.780> that<00:42:22.079> so<00:42:22.380> uh<00:42:23.220> I<00:42:23.520> think<00:42:23.640> this<00:42:23.820> makes<00:42:24.060> a 00:42:24.530 --> 00:42:24.540 align:start position:0% all this that so uh I think this makes a 00:42:24.540 --> 00:42:27.650 align:start position:0% all this that so uh I think this makes a lot<00:42:24.960> of<00:42:25.079> sense<00:42:25.320> in<00:42:25.920> in<00:42:26.099> in<00:42:26.220> that<00:42:26.640> direction 00:42:27.650 --> 00:42:27.660 align:start position:0% lot of sense in in in that direction 00:42:27.660 --> 00:42:29.630 align:start position:0% lot of sense in in in that direction for<00:42:28.200> the<00:42:28.440> hardware 00:42:29.630 --> 00:42:29.640 align:start position:0% for the hardware 00:42:29.640 --> 00:42:31.430 align:start position:0% for the hardware um<00:42:29.700> so<00:42:29.880> for<00:42:30.180> the<00:42:30.359> big<00:42:30.480> things<00:42:30.660> and<00:42:31.079> I'm<00:42:31.260> talking 00:42:31.430 --> 00:42:31.440 align:start position:0% um so for the big things and I'm talking 00:42:31.440 --> 00:42:33.650 align:start position:0% um so for the big things and I'm talking more<00:42:31.800> specific<00:42:32.160> to<00:42:32.460> maybe<00:42:33.240> a<00:42:33.420> specific 00:42:33.650 --> 00:42:33.660 align:start position:0% more specific to maybe a specific 00:42:33.660 --> 00:42:35.510 align:start position:0% more specific to maybe a specific project<00:42:33.900> which<00:42:34.200> is<00:42:34.320> the<00:42:34.440> ckvm<00:42:35.040> but<00:42:35.220> so 00:42:35.510 --> 00:42:35.520 align:start position:0% project which is the ckvm but so 00:42:35.520 --> 00:42:38.870 align:start position:0% project which is the ckvm but so representativity<00:42:36.240> is<00:42:36.480> that<00:42:36.720> for<00:42:37.320> us<00:42:37.500> we<00:42:38.099> are<00:42:38.280> I 00:42:38.870 --> 00:42:38.880 align:start position:0% representativity is that for us we are I 00:42:38.880 --> 00:42:40.849 align:start position:0% representativity is that for us we are I tell<00:42:39.060> you<00:42:39.180> why<00:42:39.420> we<00:42:39.660> are<00:42:39.839> interested<00:42:40.320> in 00:42:40.849 --> 00:42:40.859 align:start position:0% tell you why we are interested in 00:42:40.859 --> 00:42:43.849 align:start position:0% tell you why we are interested in Hardware<00:42:41.400> uh<00:42:42.359> maybe<00:42:42.540> here<00:42:42.780> you<00:42:43.079> will<00:42:43.260> you<00:42:43.680> will 00:42:43.849 --> 00:42:43.859 align:start position:0% Hardware uh maybe here you will you will 00:42:43.859 --> 00:42:46.849 align:start position:0% Hardware uh maybe here you will you will you<00:42:44.339> will<00:42:44.579> see<00:42:44.700> why<00:42:44.940> the<00:42:45.480> idea<00:42:45.720> is<00:42:45.960> that 00:42:46.849 --> 00:42:46.859 align:start position:0% you will see why the idea is that 00:42:46.859 --> 00:42:49.970 align:start position:0% you will see why the idea is that um<00:42:47.280> uh<00:42:48.119> in<00:42:48.420> a<00:42:48.599> so<00:42:49.260> if<00:42:49.380> you<00:42:49.500> want<00:42:49.560> to<00:42:49.680> have<00:42:49.800> a 00:42:49.970 --> 00:42:49.980 align:start position:0% um uh in a so if you want to have a 00:42:49.980 --> 00:42:51.710 align:start position:0% um uh in a so if you want to have a competition<00:42:50.280> the<00:42:50.820> days<00:42:51.240> that<00:42:51.420> you<00:42:51.540> want<00:42:51.660> to 00:42:51.710 --> 00:42:51.720 align:start position:0% competition the days that you want to 00:42:51.720 --> 00:42:54.410 align:start position:0% competition the days that you want to have<00:42:51.839> a<00:42:51.960> competition<00:42:52.260> uh 00:42:54.410 --> 00:42:54.420 align:start position:0% have a competition uh 00:42:54.420 --> 00:42:56.210 align:start position:0% have a competition uh that<00:42:55.020> approving<00:42:55.440> competition<00:42:55.800> you<00:42:56.099> know 00:42:56.210 --> 00:42:56.220 align:start position:0% that approving competition you know 00:42:56.220 --> 00:42:58.069 align:start position:0% that approving competition you know disaster<00:42:56.640> there<00:42:56.940> is<00:42:57.060> a<00:42:57.119> market<00:42:57.240> for<00:42:57.660> for<00:42:57.900> for 00:42:58.069 --> 00:42:58.079 align:start position:0% disaster there is a market for for for 00:42:58.079 --> 00:43:00.829 align:start position:0% disaster there is a market for for for uh<00:42:58.859> generating<00:42:59.220> proofs<00:42:59.640> big<00:43:00.000> those<00:43:00.359> big 00:43:00.829 --> 00:43:00.839 align:start position:0% uh generating proofs big those big 00:43:00.839 --> 00:43:04.250 align:start position:0% uh generating proofs big those big proofs<00:43:01.200> uh<00:43:02.160> here<00:43:02.700> you<00:43:03.000> can<00:43:03.180> have<00:43:03.599> there<00:43:03.960> is<00:43:04.140> a 00:43:04.250 --> 00:43:04.260 align:start position:0% proofs uh here you can have there is a 00:43:04.260 --> 00:43:06.290 align:start position:0% proofs uh here you can have there is a problem<00:43:04.740> is<00:43:05.040> that<00:43:05.339> you<00:43:05.520> have<00:43:05.640> a<00:43:05.760> centralized 00:43:06.290 --> 00:43:06.300 align:start position:0% problem is that you have a centralized 00:43:06.300 --> 00:43:09.109 align:start position:0% problem is that you have a centralized maybe<00:43:07.020> you<00:43:07.260> have<00:43:07.500> some<00:43:07.680> provider<00:43:08.220> that<00:43:08.700> has<00:43:08.880> a 00:43:09.109 --> 00:43:09.119 align:start position:0% maybe you have some provider that has a 00:43:09.119 --> 00:43:13.069 align:start position:0% maybe you have some provider that has a lot<00:43:09.240> of<00:43:09.420> power<00:43:09.859> and<00:43:10.859> these<00:43:11.460> monopolites<00:43:12.300> the 00:43:13.069 --> 00:43:13.079 align:start position:0% lot of power and these monopolites the 00:43:13.079 --> 00:43:14.870 align:start position:0% lot of power and these monopolites the the<00:43:13.440> the<00:43:13.500> system 00:43:14.870 --> 00:43:14.880 align:start position:0% the the system 00:43:14.880 --> 00:43:16.910 align:start position:0% the the system in<00:43:15.480> the<00:43:15.599> case<00:43:15.720> of<00:43:15.839> ckvm<00:43:16.440> this<00:43:16.560> is<00:43:16.680> not<00:43:16.740> a<00:43:16.800> big 00:43:16.910 --> 00:43:16.920 align:start position:0% in the case of ckvm this is not a big 00:43:16.920 --> 00:43:18.290 align:start position:0% in the case of ckvm this is not a big problem<00:43:17.099> because<00:43:17.400> you<00:43:17.700> can<00:43:17.819> only<00:43:17.940> build<00:43:18.119> the 00:43:18.290 --> 00:43:18.300 align:start position:0% problem because you can only build the 00:43:18.300 --> 00:43:19.970 align:start position:0% problem because you can only build the proof<00:43:18.599> that's<00:43:18.780> already<00:43:19.020> deterministic<00:43:19.859> so 00:43:19.970 --> 00:43:19.980 align:start position:0% proof that's already deterministic so 00:43:19.980 --> 00:43:22.190 align:start position:0% proof that's already deterministic so you<00:43:20.280> cannot<00:43:20.460> do<00:43:20.700> crazy<00:43:20.940> things<00:43:21.300> but<00:43:21.900> you<00:43:22.140> can 00:43:22.190 --> 00:43:22.200 align:start position:0% you cannot do crazy things but you can 00:43:22.200 --> 00:43:24.530 align:start position:0% you cannot do crazy things but you can degrade<00:43:22.619> the<00:43:22.800> network<00:43:22.980> so<00:43:23.880> the<00:43:24.240> problem<00:43:24.359> is 00:43:24.530 --> 00:43:24.540 align:start position:0% degrade the network so the problem is 00:43:24.540 --> 00:43:25.970 align:start position:0% degrade the network so the problem is that<00:43:24.720> somebody<00:43:24.900> that<00:43:25.260> has<00:43:25.440> a<00:43:25.619> huge<00:43:25.800> power 00:43:25.970 --> 00:43:25.980 align:start position:0% that somebody that has a huge power 00:43:25.980 --> 00:43:28.430 align:start position:0% that somebody that has a huge power that's<00:43:26.640> able<00:43:27.300> to<00:43:27.359> generate<00:43:27.660> a<00:43:27.839> lot<00:43:27.960> of<00:43:28.079> proofs 00:43:28.430 --> 00:43:28.440 align:start position:0% that's able to generate a lot of proofs 00:43:28.440 --> 00:43:31.970 align:start position:0% that's able to generate a lot of proofs maybe<00:43:28.680> just<00:43:28.980> stops<00:43:29.819> and<00:43:30.500> stops<00:43:31.500> doing<00:43:31.680> that 00:43:31.970 --> 00:43:31.980 align:start position:0% maybe just stops and stops doing that 00:43:31.980 --> 00:43:35.870 align:start position:0% maybe just stops and stops doing that and<00:43:32.400> and<00:43:32.640> and<00:43:32.819> then<00:43:33.359> uh<00:43:33.960> the<00:43:34.920> the<00:43:35.040> network<00:43:35.579> just 00:43:35.870 --> 00:43:35.880 align:start position:0% and and and then uh the the network just 00:43:35.880 --> 00:43:39.829 align:start position:0% and and and then uh the the network just degrades<00:43:36.380> so<00:43:37.380> in<00:43:38.040> for<00:43:38.460> us<00:43:38.640> the<00:43:38.940> way<00:43:39.060> for<00:43:39.540> us<00:43:39.660> to 00:43:39.829 --> 00:43:39.839 align:start position:0% degrades so in for us the way for us to 00:43:39.839 --> 00:43:42.890 align:start position:0% degrades so in for us the way for us to to<00:43:40.140> to<00:43:40.260> to<00:43:40.560> to<00:43:40.619> avoid<00:43:41.400> that<00:43:41.579> is<00:43:42.060> to<00:43:42.359> have<00:43:42.540> the 00:43:42.890 --> 00:43:42.900 align:start position:0% to to to to avoid that is to have the 00:43:42.900 --> 00:43:45.770 align:start position:0% to to to to avoid that is to have the best<00:43:43.140> the<00:43:44.040> best<00:43:44.280> proverb 00:43:45.770 --> 00:43:45.780 align:start position:0% best the best proverb 00:43:45.780 --> 00:43:47.990 align:start position:0% best the best proverb available<00:43:46.319> even<00:43:46.920> in<00:43:47.160> Hardware<00:43:47.339> when<00:43:47.819> I'm 00:43:47.990 --> 00:43:48.000 align:start position:0% available even in Hardware when I'm 00:43:48.000 --> 00:43:49.670 align:start position:0% available even in Hardware when I'm saying<00:43:48.119> Hardware<00:43:48.300> at<00:43:48.599> least<00:43:48.720> in<00:43:48.900> fpgas<00:43:49.440> or 00:43:49.670 --> 00:43:49.680 align:start position:0% saying Hardware at least in fpgas or 00:43:49.680 --> 00:43:52.550 align:start position:0% saying Hardware at least in fpgas or whatever<00:43:50.040> even<00:43:50.579> Asics<00:43:51.119> if<00:43:51.300> it's<00:43:51.480> required<00:43:51.900> so 00:43:52.550 --> 00:43:52.560 align:start position:0% whatever even Asics if it's required so 00:43:52.560 --> 00:43:54.349 align:start position:0% whatever even Asics if it's required so but<00:43:52.680> the<00:43:52.859> idea<00:43:53.040> is<00:43:53.220> to<00:43:53.400> have<00:43:53.640> the<00:43:54.240> best 00:43:54.349 --> 00:43:54.359 align:start position:0% but the idea is to have the best 00:43:54.359 --> 00:43:57.710 align:start position:0% but the idea is to have the best approver<00:43:55.319> a<00:43:55.740> valuable<00:43:56.099> open<00:43:56.339> source 00:43:57.710 --> 00:43:57.720 align:start position:0% approver a valuable open source 00:43:57.720 --> 00:43:59.690 align:start position:0% approver a valuable open source and<00:43:58.020> a<00:43:58.200> valuable<00:43:58.440> for<00:43:58.680> everybody<00:43:58.859> so<00:43:59.520> that 00:43:59.690 --> 00:43:59.700 align:start position:0% and a valuable for everybody so that 00:43:59.700 --> 00:44:03.589 align:start position:0% and a valuable for everybody so that there<00:43:59.880> is<00:44:00.119> no<00:44:00.420> monopolistic<00:44:01.280> uh<00:44:02.280> proverb<00:44:02.940> that 00:44:03.589 --> 00:44:03.599 align:start position:0% there is no monopolistic uh proverb that 00:44:03.599 --> 00:44:06.050 align:start position:0% there is no monopolistic uh proverb that can<00:44:03.839> take<00:44:04.140> that<00:44:04.440> that's<00:44:04.980> why<00:44:05.160> for<00:44:05.400> us<00:44:05.640> it's<00:44:05.819> so 00:44:06.050 --> 00:44:06.060 align:start position:0% can take that that's why for us it's so 00:44:06.060 --> 00:44:07.550 align:start position:0% can take that that's why for us it's so important<00:44:06.420> that<00:44:06.780> the<00:44:06.900> proverb<00:44:07.260> is<00:44:07.380> open 00:44:07.550 --> 00:44:07.560 align:start position:0% important that the proverb is open 00:44:07.560 --> 00:44:09.290 align:start position:0% important that the proverb is open source<00:44:08.040> that<00:44:08.520> the<00:44:08.640> property<00:44:09.060> is<00:44:09.180> available 00:44:09.290 --> 00:44:09.300 align:start position:0% source that the property is available 00:44:09.300 --> 00:44:11.930 align:start position:0% source that the property is available for<00:44:09.720> everybody<00:44:09.839> and<00:44:10.440> not<00:44:10.680> only<00:44:10.800> that<00:44:11.099> that<00:44:11.640> the 00:44:11.930 --> 00:44:11.940 align:start position:0% for everybody and not only that that the 00:44:11.940 --> 00:44:13.309 align:start position:0% for everybody and not only that that the technology 00:44:13.309 --> 00:44:13.319 align:start position:0% technology 00:44:13.319 --> 00:44:15.950 align:start position:0% technology to<00:44:13.740> build<00:44:13.800> the<00:44:14.040> Brewer<00:44:14.460> is<00:44:15.000> available 00:44:15.950 --> 00:44:15.960 align:start position:0% to build the Brewer is available 00:44:15.960 --> 00:44:19.190 align:start position:0% to build the Brewer is available for<00:44:16.859> for<00:44:17.220> the<00:44:17.520> community<00:44:17.700> because<00:44:18.420> this<00:44:19.079> is 00:44:19.190 --> 00:44:19.200 align:start position:0% for for the community because this is 00:44:19.200 --> 00:44:21.230 align:start position:0% for for the community because this is the<00:44:19.380> guarantee<00:44:19.920> that<00:44:20.460> we<00:44:20.640> have<00:44:20.819> that<00:44:21.060> the 00:44:21.230 --> 00:44:21.240 align:start position:0% the guarantee that we have that the 00:44:21.240 --> 00:44:24.109 align:start position:0% the guarantee that we have that the network<00:44:21.420> would<00:44:21.780> not<00:44:21.960> be<00:44:22.079> degraded 00:44:24.109 --> 00:44:24.119 align:start position:0% network would not be degraded 00:44:24.119 --> 00:44:26.630 align:start position:0% network would not be degraded it<00:44:24.480> won't<00:44:24.720> even<00:44:24.839> have<00:44:25.140> to<00:44:25.260> on<00:44:25.440> top<00:44:25.560> of<00:44:25.619> this 00:44:26.630 --> 00:44:26.640 align:start position:0% it won't even have to on top of this 00:44:26.640 --> 00:44:28.490 align:start position:0% it won't even have to on top of this um in<00:44:27.300> the<00:44:27.359> context<00:44:27.599> of<00:44:27.720> stock<00:44:27.900> net<00:44:28.200> the<00:44:28.440> way 00:44:28.490 --> 00:44:28.500 align:start position:0% um in the context of stock net the way 00:44:28.500 --> 00:44:29.690 align:start position:0% um in the context of stock net the way we<00:44:28.619> are<00:44:28.740> looking<00:44:28.859> we're<00:44:29.099> going<00:44:29.220> to<00:44:29.280> look<00:44:29.520> at 00:44:29.690 --> 00:44:29.700 align:start position:0% we are looking we're going to look at 00:44:29.700 --> 00:44:31.910 align:start position:0% we are looking we're going to look at this<00:44:29.940> proving<00:44:30.480> Market<00:44:30.660> is<00:44:31.440> by<00:44:31.680> actually 00:44:31.910 --> 00:44:31.920 align:start position:0% this proving Market is by actually 00:44:31.920 --> 00:44:35.329 align:start position:0% this proving Market is by actually having<00:44:32.400> uh<00:44:33.240> like<00:44:33.839> a<00:44:34.140> kind<00:44:34.500> of<00:44:34.680> POS<00:44:34.800> exam 00:44:35.329 --> 00:44:35.339 align:start position:0% having uh like a kind of POS exam 00:44:35.339 --> 00:44:36.710 align:start position:0% having uh like a kind of POS exam mechanism<00:44:35.640> where<00:44:35.819> we<00:44:35.940> have<00:44:36.060> a<00:44:36.180> leader<00:44:36.420> who 00:44:36.710 --> 00:44:36.720 align:start position:0% mechanism where we have a leader who 00:44:36.720 --> 00:44:37.849 align:start position:0% mechanism where we have a leader who would<00:44:36.900> be<00:44:37.020> the<00:44:37.140> proving<00:44:37.380> one<00:44:37.500> and<00:44:37.619> we<00:44:37.740> have 00:44:37.849 --> 00:44:37.859 align:start position:0% would be the proving one and we have 00:44:37.859 --> 00:44:39.470 align:start position:0% would be the proving one and we have like<00:44:37.980> a<00:44:38.099> in<00:44:38.339> Cascade<00:44:38.700> another<00:44:38.940> one<00:44:39.180> and<00:44:39.300> second 00:44:39.470 --> 00:44:39.480 align:start position:0% like a in Cascade another one and second 00:44:39.480 --> 00:44:41.630 align:start position:0% like a in Cascade another one and second one<00:44:39.720> would<00:44:39.900> come<00:44:40.079> afterwards<00:44:40.500> uh<00:44:41.099> if<00:44:41.280> there<00:44:41.460> is 00:44:41.630 --> 00:44:41.640 align:start position:0% one would come afterwards uh if there is 00:44:41.640 --> 00:44:44.690 align:start position:0% one would come afterwards uh if there is degradation<00:44:42.180> and<00:44:42.660> so<00:44:43.200> um<00:44:43.680> the<00:44:44.220> the<00:44:44.220> other 00:44:44.690 --> 00:44:44.700 align:start position:0% degradation and so um the the other 00:44:44.700 --> 00:44:46.970 align:start position:0% degradation and so um the the other thing<00:44:45.000> is<00:44:45.240> that<00:44:45.420> I<00:44:46.140> just<00:44:46.200> want<00:44:46.319> to<00:44:46.440> say<00:44:46.560> I 00:44:46.970 --> 00:44:46.980 align:start position:0% thing is that I just want to say I 00:44:46.980 --> 00:44:49.970 align:start position:0% thing is that I just want to say I forgot<00:44:47.160> to<00:44:47.220> say<00:44:47.339> let's<00:44:48.060> talk<00:44:48.839> about<00:44:48.960> that<00:44:49.140> but 00:44:49.970 --> 00:44:49.980 align:start position:0% forgot to say let's talk about that but 00:44:49.980 --> 00:44:52.190 align:start position:0% forgot to say let's talk about that but um<00:44:50.099> people<00:44:50.760> have<00:44:51.000> been<00:44:51.119> very<00:44:51.300> focusing<00:44:51.900> a<00:44:52.079> lot 00:44:52.190 --> 00:44:52.200 align:start position:0% um people have been very focusing a lot 00:44:52.200 --> 00:44:55.609 align:start position:0% um people have been very focusing a lot on<00:44:52.619> on<00:44:53.339> um<00:44:53.339> on<00:44:54.240> acceleration<00:44:54.780> because<00:44:55.140> Stark 00:44:55.609 --> 00:44:55.619 align:start position:0% on on um on acceleration because Stark 00:44:55.619 --> 00:44:57.109 align:start position:0% on on um on acceleration because Stark are<00:44:55.800> very<00:44:55.920> slow<00:44:56.099> and<00:44:56.400> there<00:44:56.700> is<00:44:56.819> no<00:44:56.940> because 00:44:57.109 --> 00:44:57.119 align:start position:0% are very slow and there is no because 00:44:57.119 --> 00:44:58.490 align:start position:0% are very slow and there is no because the<00:44:57.300> operation<00:44:57.599> that<00:44:57.780> he<00:44:57.900> did<00:44:58.020> curve<00:44:58.260> and<00:44:58.380> so 00:44:58.490 --> 00:44:58.500 align:start position:0% the operation that he did curve and so 00:44:58.500 --> 00:45:02.870 align:start position:0% the operation that he did curve and so on<00:44:58.680> uh<00:44:59.599> and<00:45:00.599> some<00:45:00.900> means<00:45:01.319> I<00:45:01.859> mean<00:45:01.980> I<00:45:02.400> mean<00:45:02.520> but<00:45:02.700> I 00:45:02.870 --> 00:45:02.880 align:start position:0% on uh and some means I mean I mean but I 00:45:02.880 --> 00:45:04.970 align:start position:0% on uh and some means I mean I mean but I mean<00:45:03.000> at<00:45:03.180> least<00:45:03.300> uh<00:45:03.540> Jordy<00:45:04.079> and<00:45:04.200> I<00:45:04.319> uh<00:45:04.800> working 00:45:04.970 --> 00:45:04.980 align:start position:0% mean at least uh Jordy and I uh working 00:45:04.980 --> 00:45:07.010 align:start position:0% mean at least uh Jordy and I uh working more<00:45:05.220> on<00:45:05.400> stocks<00:45:05.760> which<00:45:06.000> are<00:45:06.180> much<00:45:06.420> faster<00:45:06.720> and 00:45:07.010 --> 00:45:07.020 align:start position:0% more on stocks which are much faster and 00:45:07.020 --> 00:45:09.530 align:start position:0% more on stocks which are much faster and much<00:45:07.200> easier<00:45:07.380> to<00:45:07.740> to<00:45:07.920> use<00:45:08.339> to<00:45:08.579> to<00:45:08.760> work<00:45:09.180> on<00:45:09.359> on 00:45:09.530 --> 00:45:09.540 align:start position:0% much easier to to use to to work on on 00:45:09.540 --> 00:45:11.809 align:start position:0% much easier to to use to to work on on regular<00:45:09.900> servers<00:45:10.440> so<00:45:10.740> I<00:45:11.099> think<00:45:11.220> that<00:45:11.339> maybe<00:45:11.579> a 00:45:11.809 --> 00:45:11.819 align:start position:0% regular servers so I think that maybe a 00:45:11.819 --> 00:45:13.550 align:start position:0% regular servers so I think that maybe a difference<00:45:11.940> of<00:45:12.240> nor<00:45:12.540> take<00:45:12.720> relate<00:45:13.319> to<00:45:13.440> that 00:45:13.550 --> 00:45:13.560 align:start position:0% difference of nor take relate to that 00:45:13.560 --> 00:45:18.589 align:start position:0% difference of nor take relate to that machine 00:45:18.589 --> 00:45:18.599 align:start position:0% 00:45:18.599 --> 00:45:20.930 align:start position:0% I<00:45:19.200> mean<00:45:19.440> uh<00:45:19.980> so<00:45:20.160> I'm<00:45:20.339> gonna<00:45:20.460> answer<00:45:20.640> the 00:45:20.930 --> 00:45:20.940 align:start position:0% I mean uh so I'm gonna answer the 00:45:20.940 --> 00:45:22.790 align:start position:0% I mean uh so I'm gonna answer the question<00:45:21.180> I<00:45:21.720> wanted<00:45:21.839> to<00:45:22.079> hear<00:45:22.260> instead<00:45:22.560> of<00:45:22.680> the 00:45:22.790 --> 00:45:22.800 align:start position:0% question I wanted to hear instead of the 00:45:22.800 --> 00:45:25.069 align:start position:0% question I wanted to hear instead of the one<00:45:22.920> you<00:45:23.099> actually<00:45:23.280> asked<00:45:23.880> uh<00:45:24.119> because<00:45:24.900> I 00:45:25.069 --> 00:45:25.079 align:start position:0% one you actually asked uh because I 00:45:25.079 --> 00:45:27.170 align:start position:0% one you actually asked uh because I don't<00:45:25.200> really<00:45:25.319> know<00:45:25.500> much<00:45:25.740> about<00:45:25.980> uh<00:45:26.700> Hardware 00:45:27.170 --> 00:45:27.180 align:start position:0% don't really know much about uh Hardware 00:45:27.180 --> 00:45:30.109 align:start position:0% don't really know much about uh Hardware acceleration<00:45:28.040> uh<00:45:29.040> in<00:45:29.280> terms<00:45:29.520> of<00:45:29.640> uh 00:45:30.109 --> 00:45:30.119 align:start position:0% acceleration uh in terms of uh 00:45:30.119 --> 00:45:31.490 align:start position:0% acceleration uh in terms of uh programming<00:45:30.599> for<00:45:30.780> Hardware<00:45:31.020> versus 00:45:31.490 --> 00:45:31.500 align:start position:0% programming for Hardware versus 00:45:31.500 --> 00:45:33.710 align:start position:0% programming for Hardware versus programming<00:45:32.099> for<00:45:32.280> a<00:45:32.460> software<00:45:32.819> I<00:45:33.660> think 00:45:33.710 --> 00:45:33.720 align:start position:0% programming for a software I think 00:45:33.720 --> 00:45:35.390 align:start position:0% programming for a software I think proving<00:45:34.140> systems<00:45:34.500> are<00:45:34.680> changing<00:45:34.980> too<00:45:35.280> much 00:45:35.390 --> 00:45:35.400 align:start position:0% proving systems are changing too much 00:45:35.400 --> 00:45:39.829 align:start position:0% proving systems are changing too much for<00:45:35.900> at<00:45:36.900> least<00:45:37.079> us<00:45:37.380> to<00:45:37.619> focus<00:45:37.980> on<00:45:38.480> uh<00:45:39.480> sort<00:45:39.780> of 00:45:39.829 --> 00:45:39.839 align:start position:0% for at least us to focus on uh sort of 00:45:39.839 --> 00:45:42.109 align:start position:0% for at least us to focus on uh sort of being<00:45:40.140> so<00:45:40.380> close<00:45:40.619> to<00:45:40.800> the<00:45:40.920> metal<00:45:41.099> just<00:45:41.880> because 00:45:42.109 --> 00:45:42.119 align:start position:0% being so close to the metal just because 00:45:42.119 --> 00:45:44.809 align:start position:0% being so close to the metal just because the<00:45:42.359> muscle<00:45:42.599> might<00:45:43.020> change<00:45:43.319> next<00:45:44.220> year<00:45:44.400> or<00:45:44.640> the 00:45:44.809 --> 00:45:44.819 align:start position:0% the muscle might change next year or the 00:45:44.819 --> 00:45:46.609 align:start position:0% the muscle might change next year or the year<00:45:44.940> or<00:45:45.359> the<00:45:45.599> year<00:45:45.780> after 00:45:46.609 --> 00:45:46.619 align:start position:0% year or the year after 00:45:46.619 --> 00:45:49.730 align:start position:0% year or the year after uh<00:45:47.579> I<00:45:47.880> will<00:45:48.000> say<00:45:48.180> that<00:45:48.359> for<00:45:48.540> privacy<00:45:48.900> it's<00:45:49.560> sort 00:45:49.730 --> 00:45:49.740 align:start position:0% uh I will say that for privacy it's sort 00:45:49.740 --> 00:45:52.430 align:start position:0% uh I will say that for privacy it's sort of<00:45:49.920> a<00:45:50.160> different<00:45:50.460> space<00:45:51.060> uh<00:45:51.900> if<00:45:52.200> you<00:45:52.319> have 00:45:52.430 --> 00:45:52.440 align:start position:0% of a different space uh if you have 00:45:52.440 --> 00:45:53.930 align:start position:0% of a different space uh if you have privacy<00:45:52.859> you<00:45:53.099> need<00:45:53.220> to<00:45:53.400> sort<00:45:53.520> of<00:45:53.640> think<00:45:53.760> about 00:45:53.930 --> 00:45:53.940 align:start position:0% privacy you need to sort of think about 00:45:53.940 --> 00:45:56.930 align:start position:0% privacy you need to sort of think about how<00:45:54.300> to<00:45:54.480> accelerate<00:45:55.319> approver<00:45:55.800> like<00:45:56.640> because 00:45:56.930 --> 00:45:56.940 align:start position:0% how to accelerate approver like because 00:45:56.940 --> 00:45:59.329 align:start position:0% how to accelerate approver like because we<00:45:57.119> usually<00:45:57.359> use<00:45:57.480> wasm<00:45:57.980> whereas<00:45:58.980> if<00:45:59.160> you<00:45:59.220> don't 00:45:59.329 --> 00:45:59.339 align:start position:0% we usually use wasm whereas if you don't 00:45:59.339 --> 00:46:01.670 align:start position:0% we usually use wasm whereas if you don't have<00:45:59.460> privacy<00:45:59.819> it's<00:46:00.060> really<00:46:00.359> fpgas<00:46:01.260> and<00:46:01.500> GPS 00:46:01.670 --> 00:46:01.680 align:start position:0% have privacy it's really fpgas and GPS 00:46:01.680 --> 00:46:04.730 align:start position:0% have privacy it's really fpgas and GPS like<00:46:02.339> how<00:46:02.579> do<00:46:02.760> you<00:46:02.880> accelerate<00:46:03.359> uh<00:46:04.319> this<00:46:04.500> this 00:46:04.730 --> 00:46:04.740 align:start position:0% like how do you accelerate uh this this 00:46:04.740 --> 00:46:12.410 align:start position:0% like how do you accelerate uh this this massive<00:46:05.040> beefy<00:46:05.520> machine 00:46:12.410 --> 00:46:12.420 align:start position:0% 00:46:12.420 --> 00:46:14.450 align:start position:0% I<00:46:12.839> I<00:46:12.900> guess<00:46:13.380> just<00:46:13.680> to 00:46:14.450 --> 00:46:14.460 align:start position:0% I I guess just to 00:46:14.460 --> 00:46:16.790 align:start position:0% I I guess just to um there<00:46:14.940> was<00:46:15.359> this<00:46:15.599> discussion<00:46:16.140> about<00:46:16.319> like 00:46:16.790 --> 00:46:16.800 align:start position:0% um there was this discussion about like 00:46:16.800 --> 00:46:19.250 align:start position:0% um there was this discussion about like uh<00:46:17.520> you<00:46:17.760> know<00:46:17.819> markets<00:46:18.480> for<00:46:18.660> decentralized 00:46:19.250 --> 00:46:19.260 align:start position:0% uh you know markets for decentralized 00:46:19.260 --> 00:46:20.809 align:start position:0% uh you know markets for decentralized provers 00:46:20.809 --> 00:46:20.819 align:start position:0% provers 00:46:20.819 --> 00:46:22.970 align:start position:0% provers um and<00:46:21.359> this<00:46:21.660> is<00:46:21.780> just<00:46:21.960> my<00:46:22.260> I<00:46:22.560> just<00:46:22.740> have<00:46:22.859> to 00:46:22.970 --> 00:46:22.980 align:start position:0% um and this is just my I just have to 00:46:22.980 --> 00:46:25.010 align:start position:0% um and this is just my I just have to say<00:46:23.160> this<00:46:23.339> because<00:46:23.579> too<00:46:24.119> many<00:46:24.300> people<00:46:24.540> are 00:46:25.010 --> 00:46:25.020 align:start position:0% say this because too many people are 00:46:25.020 --> 00:46:26.569 align:start position:0% say this because too many people are surprised<00:46:25.380> by<00:46:25.560> this<00:46:25.740> at<00:46:26.040> this<00:46:26.280> conference 00:46:26.569 --> 00:46:26.579 align:start position:0% surprised by this at this conference 00:46:26.579 --> 00:46:28.250 align:start position:0% surprised by this at this conference sorry<00:46:27.060> if<00:46:27.240> it's<00:46:27.359> a<00:46:27.420> little<00:46:27.480> bit<00:46:27.599> off<00:46:27.720> topic<00:46:28.079> but 00:46:28.250 --> 00:46:28.260 align:start position:0% sorry if it's a little bit off topic but 00:46:28.260 --> 00:46:30.950 align:start position:0% sorry if it's a little bit off topic but Mina<00:46:28.859> has<00:46:29.520> a<00:46:29.940> decentralized<00:46:30.480> sequencers 00:46:30.950 --> 00:46:30.960 align:start position:0% Mina has a decentralized sequencers 00:46:30.960 --> 00:46:33.109 align:start position:0% Mina has a decentralized sequencers decentralized<00:46:31.500> provers<00:46:32.040> a<00:46:32.460> Marketplace<00:46:32.819> for 00:46:33.109 --> 00:46:33.119 align:start position:0% decentralized provers a Marketplace for 00:46:33.119 --> 00:46:34.730 align:start position:0% decentralized provers a Marketplace for producing<00:46:33.540> proofs 00:46:34.730 --> 00:46:34.740 align:start position:0% producing proofs 00:46:34.740 --> 00:46:36.470 align:start position:0% producing proofs um<00:46:34.859> that<00:46:35.280> are<00:46:35.520> sort<00:46:35.700> of<00:46:35.760> needed<00:46:36.060> by<00:46:36.180> the<00:46:36.359> system 00:46:36.470 --> 00:46:36.480 align:start position:0% um that are sort of needed by the system 00:46:36.480 --> 00:46:38.030 align:start position:0% um that are sort of needed by the system and<00:46:36.900> this<00:46:37.020> has<00:46:37.140> been<00:46:37.260> in<00:46:37.380> production<00:46:37.619> for<00:46:37.920> a 00:46:38.030 --> 00:46:38.040 align:start position:0% and this has been in production for a 00:46:38.040 --> 00:46:41.089 align:start position:0% and this has been in production for a while<00:46:38.160> and<00:46:39.000> uh<00:46:39.359> we 00:46:41.089 --> 00:46:41.099 align:start position:0% while and uh we 00:46:41.099 --> 00:46:43.550 align:start position:0% while and uh we um<00:46:41.160> encourage<00:46:42.000> more<00:46:42.420> people<00:46:42.599> to<00:46:43.020> look<00:46:43.260> at<00:46:43.440> it 00:46:43.550 --> 00:46:43.560 align:start position:0% um encourage more people to look at it 00:46:43.560 --> 00:46:44.630 align:start position:0% um encourage more people to look at it when<00:46:43.740> they're<00:46:43.859> thinking<00:46:44.160> about<00:46:44.280> their 00:46:44.630 --> 00:46:44.640 align:start position:0% when they're thinking about their 00:46:44.640 --> 00:46:47.450 align:start position:0% when they're thinking about their marketplaces<00:46:45.359> and<00:46:45.780> and<00:46:46.079> everything<00:46:46.460> cool 00:46:47.450 --> 00:46:47.460 align:start position:0% marketplaces and and everything cool 00:46:47.460 --> 00:46:50.390 align:start position:0% marketplaces and and everything cool great<00:46:47.880> answers<00:46:48.180> thanks<00:46:48.480> guys 00:46:50.390 --> 00:46:50.400 align:start position:0% great answers thanks guys 00:46:50.400 --> 00:46:54.290 align:start position:0% great answers thanks guys actually 00:46:54.290 --> 00:46:54.300 align:start position:0% 00:46:54.300 --> 00:46:58.550 align:start position:0% there's<00:46:54.900> a<00:46:55.020> worker 00:46:58.550 --> 00:46:58.560 align:start position:0% 00:46:58.560 --> 00:47:00.530 align:start position:0% okay<00:46:59.579> um<00:46:59.640> I<00:46:59.760> have<00:46:59.940> a<00:47:00.000> question<00:47:00.119> it's<00:47:00.359> like 00:47:00.530 --> 00:47:00.540 align:start position:0% okay um I have a question it's like 00:47:00.540 --> 00:47:02.030 align:start position:0% okay um I have a question it's like maybe<00:47:00.780> continuing<00:47:01.260> on<00:47:01.380> the<00:47:01.500> hardware<00:47:01.619> thing 00:47:02.030 --> 00:47:02.040 align:start position:0% maybe continuing on the hardware thing 00:47:02.040 --> 00:47:04.370 align:start position:0% maybe continuing on the hardware thing but<00:47:02.220> most<00:47:02.460> of<00:47:02.700> the<00:47:02.880> I<00:47:03.480> mean<00:47:03.660> a<00:47:04.020> lot<00:47:04.140> of<00:47:04.260> people 00:47:04.370 --> 00:47:04.380 align:start position:0% but most of the I mean a lot of people 00:47:04.380 --> 00:47:07.430 align:start position:0% but most of the I mean a lot of people kind<00:47:05.099> of 00:47:07.430 --> 00:47:07.440 align:start position:0% 00:47:07.440 --> 00:47:09.890 align:start position:0% um<00:47:07.560> compiling<00:47:08.160> Target<00:47:08.400> now<00:47:08.819> is<00:47:09.300> actually 00:47:09.890 --> 00:47:09.900 align:start position:0% um compiling Target now is actually 00:47:09.900 --> 00:47:11.390 align:start position:0% um compiling Target now is actually solidity<00:47:10.440> so<00:47:10.680> actually<00:47:10.800> a<00:47:10.980> lot<00:47:11.099> of<00:47:11.160> people<00:47:11.280> are 00:47:11.390 --> 00:47:11.400 align:start position:0% solidity so actually a lot of people are 00:47:11.400 --> 00:47:13.309 align:start position:0% solidity so actually a lot of people are moving<00:47:11.700> on<00:47:11.880> ethereum 00:47:13.309 --> 00:47:13.319 align:start position:0% moving on ethereum 00:47:13.319 --> 00:47:16.670 align:start position:0% moving on ethereum and<00:47:13.560> kind<00:47:13.740> of<00:47:13.859> this<00:47:13.980> is<00:47:14.099> Defcon<00:47:14.520> so<00:47:14.819> like<00:47:15.060> uh 00:47:16.670 --> 00:47:16.680 align:start position:0% and kind of this is Defcon so like uh 00:47:16.680 --> 00:47:19.430 align:start position:0% and kind of this is Defcon so like uh the<00:47:17.460> most<00:47:18.119> artificial<00:47:18.720> kind<00:47:18.960> of<00:47:19.079> constraints 00:47:19.430 --> 00:47:19.440 align:start position:0% the most artificial kind of constraints 00:47:19.440 --> 00:47:21.650 align:start position:0% the most artificial kind of constraints that<00:47:19.680> I'm<00:47:19.859> seeing<00:47:20.160> is<00:47:20.819> probably<00:47:21.060> the<00:47:21.420> fact 00:47:21.650 --> 00:47:21.660 align:start position:0% that I'm seeing is probably the fact 00:47:21.660 --> 00:47:24.770 align:start position:0% that I'm seeing is probably the fact that<00:47:21.960> we<00:47:22.319> have<00:47:22.740> one<00:47:23.040> pre-compiled<00:47:24.000> curve<00:47:24.599> to 00:47:24.770 --> 00:47:24.780 align:start position:0% that we have one pre-compiled curve to 00:47:24.780 --> 00:47:27.109 align:start position:0% that we have one pre-compiled curve to work<00:47:24.960> with<00:47:25.200> but<00:47:25.920> we<00:47:26.160> can<00:47:26.220> only<00:47:26.339> work<00:47:26.579> with<00:47:26.760> BN 00:47:27.109 --> 00:47:27.119 align:start position:0% work with but we can only work with BN 00:47:27.119 --> 00:47:28.670 align:start position:0% work with but we can only work with BN 128 00:47:28.670 --> 00:47:28.680 align:start position:0% 128 00:47:28.680 --> 00:47:30.650 align:start position:0% 128 so<00:47:29.099> wondering<00:47:29.460> what's<00:47:29.579> your<00:47:29.760> intuition<00:47:30.060> why 00:47:30.650 --> 00:47:30.660 align:start position:0% so wondering what's your intuition why 00:47:30.660 --> 00:47:32.270 align:start position:0% so wondering what's your intuition why why<00:47:30.720> don't<00:47:31.140> we<00:47:31.319> have<00:47:31.440> more<00:47:31.619> curves<00:47:31.980> to<00:47:32.099> walk 00:47:32.270 --> 00:47:32.280 align:start position:0% why don't we have more curves to walk 00:47:32.280 --> 00:47:34.190 align:start position:0% why don't we have more curves to walk with 00:47:34.190 --> 00:47:34.200 align:start position:0% with 00:47:34.200 --> 00:47:36.530 align:start position:0% with in<00:47:34.680> your<00:47:35.099> opinion<00:47:35.400> I<00:47:35.579> don't<00:47:35.700> know<00:47:35.760> it<00:47:36.300> seems 00:47:36.530 --> 00:47:36.540 align:start position:0% in your opinion I don't know it seems 00:47:36.540 --> 00:47:38.329 align:start position:0% in your opinion I don't know it seems like<00:47:36.599> it<00:47:36.780> will<00:47:36.960> kind<00:47:37.200> of<00:47:37.380> release<00:47:37.680> a<00:47:38.040> lot<00:47:38.160> of 00:47:38.329 --> 00:47:38.339 align:start position:0% like it will kind of release a lot of 00:47:38.339 --> 00:47:40.970 align:start position:0% like it will kind of release a lot of the<00:47:38.760> bottleneck<00:47:39.180> so<00:47:39.720> okay<00:47:39.960> I<00:47:40.260> I<00:47:40.380> can<00:47:40.619> make<00:47:40.800> two 00:47:40.970 --> 00:47:40.980 align:start position:0% the bottleneck so okay I I can make two 00:47:40.980 --> 00:47:43.010 align:start position:0% the bottleneck so okay I I can make two comments<00:47:41.460> uh<00:47:42.000> the<00:47:42.180> first<00:47:42.300> one<00:47:42.420> in<00:47:42.540> the<00:47:42.780> pure 00:47:43.010 --> 00:47:43.020 align:start position:0% comments uh the first one in the pure 00:47:43.020 --> 00:47:44.690 align:start position:0% comments uh the first one in the pure application<00:47:43.500> Level<00:47:43.740> and<00:47:44.040> why<00:47:44.220> people<00:47:44.400> should 00:47:44.690 --> 00:47:44.700 align:start position:0% application Level and why people should 00:47:44.700 --> 00:47:46.910 align:start position:0% application Level and why people should care<00:47:44.940> about<00:47:45.060> what<00:47:45.300> you're<00:47:45.420> describing 00:47:46.910 --> 00:47:46.920 align:start position:0% care about what you're describing 00:47:46.920 --> 00:47:50.510 align:start position:0% care about what you're describing um<00:47:47.040> so<00:47:47.520> I<00:47:47.760> think<00:47:47.880> that<00:47:48.060> one<00:47:48.359> of<00:47:48.480> the<00:47:48.599> biggest 00:47:50.510 --> 00:47:50.520 align:start position:0% um so I think that one of the biggest 00:47:50.520 --> 00:47:52.790 align:start position:0% um so I think that one of the biggest original<00:47:50.940> saying<00:47:51.540> that<00:47:51.599> if<00:47:51.960> you're<00:47:52.140> made<00:47:52.500> when 00:47:52.790 --> 00:47:52.800 align:start position:0% original saying that if you're made when 00:47:52.800 --> 00:47:54.530 align:start position:0% original saying that if you're made when they<00:47:52.920> were<00:47:53.040> built<00:47:53.339> in<00:47:53.819> order<00:47:54.000> to<00:47:54.180> see<00:47:54.300> in 00:47:54.530 --> 00:47:54.540 align:start position:0% they were built in order to see in 00:47:54.540 --> 00:47:56.630 align:start position:0% they were built in order to see in retrospect<00:47:54.960> right<00:47:55.140> we<00:47:55.440> couldn't<00:47:55.560> know<00:47:55.859> is<00:47:56.400> to 00:47:56.630 --> 00:47:56.640 align:start position:0% retrospect right we couldn't know is to 00:47:56.640 --> 00:47:58.309 align:start position:0% retrospect right we couldn't know is to have<00:47:56.819> had<00:47:57.240> EOS 00:47:58.309 --> 00:47:58.319 align:start position:0% have had EOS 00:47:58.319 --> 00:48:02.930 align:start position:0% have had EOS I<00:47:58.740> think<00:47:58.859> EOS<00:47:59.160> was<00:47:59.460> a<00:47:59.579> mistake<00:48:00.300> but<00:48:00.960> and<00:48:01.500> and 00:48:02.930 --> 00:48:02.940 align:start position:0% I think EOS was a mistake but and and 00:48:02.940 --> 00:48:05.510 align:start position:0% I think EOS was a mistake but and and um<00:48:03.119> and<00:48:03.900> you're<00:48:04.260> right<00:48:04.440> having<00:48:04.740> new<00:48:05.040> curve 00:48:05.510 --> 00:48:05.520 align:start position:0% um and you're right having new curve 00:48:05.520 --> 00:48:07.790 align:start position:0% um and you're right having new curve like<00:48:06.119> you<00:48:06.420> know<00:48:06.480> uh<00:48:06.780> being<00:48:06.960> able<00:48:07.140> to<00:48:07.319> use<00:48:07.500> the 00:48:07.790 --> 00:48:07.800 align:start position:0% like you know uh being able to use the 00:48:07.800 --> 00:48:10.609 align:start position:0% like you know uh being able to use the p2056<00:48:08.760> when<00:48:09.119> it<00:48:09.240> is<00:48:09.359> on<00:48:09.480> your<00:48:09.599> phone<00:48:09.780> or<00:48:10.260> even 00:48:10.609 --> 00:48:10.619 align:start position:0% p2056 when it is on your phone or even 00:48:10.619 --> 00:48:12.710 align:start position:0% p2056 when it is on your phone or even being<00:48:10.859> able<00:48:11.040> to<00:48:11.280> RSA<00:48:11.940> verification<00:48:12.359> I<00:48:12.599> mean 00:48:12.710 --> 00:48:12.720 align:start position:0% being able to RSA verification I mean 00:48:12.720 --> 00:48:15.050 align:start position:0% being able to RSA verification I mean just<00:48:13.020> to<00:48:13.140> throw<00:48:13.380> random<00:48:13.740> ideas<00:48:13.859> right 00:48:15.050 --> 00:48:15.060 align:start position:0% just to throw random ideas right 00:48:15.060 --> 00:48:16.970 align:start position:0% just to throw random ideas right um<00:48:15.119> would<00:48:15.540> be<00:48:15.660> unlocking<00:48:16.200> a<00:48:16.319> lot<00:48:16.500> of<00:48:16.619> use<00:48:16.740> cases 00:48:16.970 --> 00:48:16.980 align:start position:0% um would be unlocking a lot of use cases 00:48:16.980 --> 00:48:19.430 align:start position:0% um would be unlocking a lot of use cases I<00:48:17.339> mean<00:48:17.460> just<00:48:17.640> to<00:48:17.760> give<00:48:17.880> you<00:48:18.000> an<00:48:18.119> example 00:48:19.430 --> 00:48:19.440 align:start position:0% I mean just to give you an example 00:48:19.440 --> 00:48:21.290 align:start position:0% I mean just to give you an example um<00:48:19.500> starting<00:48:20.400> running<00:48:20.760> through<00:48:21.000> the<00:48:21.119> company 00:48:21.290 --> 00:48:21.300 align:start position:0% um starting running through the company 00:48:21.300 --> 00:48:23.510 align:start position:0% um starting running through the company on<00:48:21.599> gaming<00:48:21.900> that<00:48:22.200> is<00:48:22.380> using<00:48:23.099> the<00:48:23.220> construction 00:48:23.510 --> 00:48:23.520 align:start position:0% on gaming that is using the construction 00:48:23.520 --> 00:48:27.470 align:start position:0% on gaming that is using the construction to<00:48:24.119> verify<00:48:24.920> p2056<00:48:25.920> the<00:48:26.160> the<00:48:26.339> you're<00:48:27.060> using 00:48:27.470 --> 00:48:27.480 align:start position:0% to verify p2056 the the you're using 00:48:27.480 --> 00:48:29.150 align:start position:0% to verify p2056 the the you're using your<00:48:27.720> securing<00:48:28.140> clip<00:48:28.440> of<00:48:28.560> your<00:48:28.680> phone<00:48:28.800> to<00:48:28.980> sign 00:48:29.150 --> 00:48:29.160 align:start position:0% your securing clip of your phone to sign 00:48:29.160 --> 00:48:30.770 align:start position:0% your securing clip of your phone to sign signatures<00:48:29.700> for<00:48:29.819> gaming<00:48:30.119> that's<00:48:30.540> awesome 00:48:30.770 --> 00:48:30.780 align:start position:0% signatures for gaming that's awesome 00:48:30.780 --> 00:48:32.569 align:start position:0% signatures for gaming that's awesome which<00:48:31.079> is<00:48:31.260> awesome 00:48:32.569 --> 00:48:32.579 align:start position:0% which is awesome 00:48:32.579 --> 00:48:34.490 align:start position:0% which is awesome um<00:48:32.700> that's<00:48:33.420> actually<00:48:33.599> not<00:48:33.839> for<00:48:34.079> me<00:48:34.260> the 00:48:34.490 --> 00:48:34.500 align:start position:0% um that's actually not for me the 00:48:34.500 --> 00:48:36.770 align:start position:0% um that's actually not for me the biggest<00:48:34.800> you<00:48:35.220> know<00:48:35.280> lock<00:48:35.579> of<00:48:36.060> the<00:48:36.240> verifying 00:48:36.770 --> 00:48:36.780 align:start position:0% biggest you know lock of the verifying 00:48:36.780 --> 00:48:38.510 align:start position:0% biggest you know lock of the verifying the<00:48:36.839> evm<00:48:37.260> the<00:48:37.440> main<00:48:37.800> difference<00:48:37.980> the<00:48:38.280> one 00:48:38.510 --> 00:48:38.520 align:start position:0% the evm the main difference the one 00:48:38.520 --> 00:48:40.069 align:start position:0% the evm the main difference the one problem<00:48:38.760> is<00:48:39.000> that 00:48:40.069 --> 00:48:40.079 align:start position:0% problem is that 00:48:40.079 --> 00:48:41.089 align:start position:0% problem is that um 00:48:41.089 --> 00:48:41.099 align:start position:0% um 00:48:41.099 --> 00:48:43.550 align:start position:0% um either<00:48:41.700> you<00:48:42.119> the<00:48:42.359> Computing<00:48:42.720> Paradigm<00:48:43.260> of<00:48:43.380> the 00:48:43.550 --> 00:48:43.560 align:start position:0% either you the Computing Paradigm of the 00:48:43.560 --> 00:48:44.930 align:start position:0% either you the Computing Paradigm of the VM<00:48:43.920> is<00:48:44.040> very<00:48:44.220> different<00:48:44.400> from<00:48:44.579> when<00:48:44.760> you<00:48:44.880> have 00:48:44.930 --> 00:48:44.940 align:start position:0% VM is very different from when you have 00:48:44.940 --> 00:48:47.450 align:start position:0% VM is very different from when you have nvk<00:48:45.420> I<00:48:45.839> mean<00:48:45.900> beats<00:48:46.680> Boolean<00:48:46.980> logic<00:48:47.339> is 00:48:47.450 --> 00:48:47.460 align:start position:0% nvk I mean beats Boolean logic is 00:48:47.460 --> 00:48:49.670 align:start position:0% nvk I mean beats Boolean logic is expensive<00:48:48.119> and<00:48:48.300> ZK<00:48:48.720> is<00:48:48.900> cheap<00:48:49.079> on<00:48:49.200> the<00:48:49.319> evm 00:48:49.670 --> 00:48:49.680 align:start position:0% expensive and ZK is cheap on the evm 00:48:49.680 --> 00:48:50.990 align:start position:0% expensive and ZK is cheap on the evm right<00:48:49.800> so<00:48:49.980> this<00:48:50.400> is<00:48:50.460> kind<00:48:50.640> of<00:48:50.760> the<00:48:50.819> starting 00:48:50.990 --> 00:48:51.000 align:start position:0% right so this is kind of the starting 00:48:51.000 --> 00:48:52.309 align:start position:0% right so this is kind of the starting point 00:48:52.309 --> 00:48:52.319 align:start position:0% point 00:48:52.319 --> 00:48:53.990 align:start position:0% point um<00:48:52.440> and 00:48:53.990 --> 00:48:54.000 align:start position:0% um and 00:48:54.000 --> 00:48:55.970 align:start position:0% um and um<00:48:54.060> while<00:48:54.480> if<00:48:54.900> like<00:48:55.140> you<00:48:55.319> know<00:48:55.380> a<00:48:55.619> lot<00:48:55.740> of<00:48:55.800> team 00:48:55.970 --> 00:48:55.980 align:start position:0% um while if like you know a lot of team 00:48:55.980 --> 00:48:57.770 align:start position:0% um while if like you know a lot of team are<00:48:56.160> looking<00:48:56.400> into<00:48:56.640> I<00:48:56.819> mean<00:48:56.880> diving<00:48:57.240> I<00:48:57.420> mean<00:48:57.540> or 00:48:57.770 --> 00:48:57.780 align:start position:0% are looking into I mean diving I mean or 00:48:57.780 --> 00:49:00.109 align:start position:0% are looking into I mean diving I mean or you<00:48:57.960> would<00:48:58.140> talk<00:48:58.260> more<00:48:58.500> about<00:48:58.859> that<00:48:59.099> than<00:48:59.339> me 00:49:00.109 --> 00:49:00.119 align:start position:0% you would talk more about that than me 00:49:00.119 --> 00:49:02.390 align:start position:0% you would talk more about that than me um<00:49:00.240> about<00:49:00.420> you<00:49:00.720> know<00:49:00.839> putting<00:49:01.079> the<00:49:01.200> vvm<00:49:01.560> uh<00:49:02.220> we 00:49:02.390 --> 00:49:02.400 align:start position:0% um about you know putting the vvm uh we 00:49:02.400 --> 00:49:04.970 align:start position:0% um about you know putting the vvm uh we didn't<00:49:02.520> make<00:49:02.760> the<00:49:02.940> choice<00:49:03.240> because<00:49:03.740> we<00:49:04.740> were 00:49:04.970 --> 00:49:04.980 align:start position:0% didn't make the choice because we were 00:49:04.980 --> 00:49:07.210 align:start position:0% didn't make the choice because we were in<00:49:05.579> our<00:49:05.700> opinion<00:49:06.000> we<00:49:06.180> were<00:49:06.359> optimizing<00:49:06.960> for 00:49:07.210 --> 00:49:07.220 align:start position:0% in our opinion we were optimizing for 00:49:07.220 --> 00:49:10.130 align:start position:0% in our opinion we were optimizing for performance<00:49:08.220> of<00:49:08.640> The<00:49:08.760> Proving<00:49:09.119> system<00:49:09.300> and 00:49:10.130 --> 00:49:10.140 align:start position:0% performance of The Proving system and 00:49:10.140 --> 00:49:12.589 align:start position:0% performance of The Proving system and then<00:49:10.319> now<00:49:10.800> that<00:49:11.040> we<00:49:11.220> have<00:49:11.339> that<00:49:11.520> can<00:49:12.060> we<00:49:12.300> back 00:49:12.589 --> 00:49:12.599 align:start position:0% then now that we have that can we back 00:49:12.599 --> 00:49:15.530 align:start position:0% then now that we have that can we back work<00:49:12.839> make<00:49:13.140> it<00:49:13.319> Backward<00:49:13.619> Compatible<00:49:14.119> and<00:49:15.119> so 00:49:15.530 --> 00:49:15.540 align:start position:0% work make it Backward Compatible and so 00:49:15.540 --> 00:49:18.530 align:start position:0% work make it Backward Compatible and so we<00:49:15.960> have<00:49:16.140> in<00:49:16.920> our<00:49:17.040> case<00:49:17.220> warp<00:49:17.880> which<00:49:18.119> is<00:49:18.180> like<00:49:18.359> a 00:49:18.530 --> 00:49:18.540 align:start position:0% we have in our case warp which is like a 00:49:18.540 --> 00:49:20.270 align:start position:0% we have in our case warp which is like a tooling<00:49:18.900> that<00:49:19.140> enables<00:49:19.560> you<00:49:19.680> to<00:49:19.800> transpire 00:49:20.270 --> 00:49:20.280 align:start position:0% tooling that enables you to transpire 00:49:20.280 --> 00:49:24.290 align:start position:0% tooling that enables you to transpire from<00:49:20.640> uh<00:49:21.359> solidity<00:49:21.839> to<00:49:22.020> Cairo<00:49:22.440> and 00:49:24.290 --> 00:49:24.300 align:start position:0% from uh solidity to Cairo and 00:49:24.300 --> 00:49:26.450 align:start position:0% from uh solidity to Cairo and the<00:49:24.839> practicality<00:49:25.440> of<00:49:25.680> it<00:49:25.800> I<00:49:26.220> can't<00:49:26.339> really 00:49:26.450 --> 00:49:26.460 align:start position:0% the practicality of it I can't really 00:49:26.460 --> 00:49:27.890 align:start position:0% the practicality of it I can't really judge<00:49:26.819> no<00:49:26.940> one<00:49:27.119> really<00:49:27.300> used<00:49:27.599> it<00:49:27.839> in 00:49:27.890 --> 00:49:27.900 align:start position:0% judge no one really used it in 00:49:27.900 --> 00:49:29.750 align:start position:0% judge no one really used it in production<00:49:28.200> but<00:49:28.619> they<00:49:28.800> managed<00:49:29.160> to<00:49:29.280> recently 00:49:29.750 --> 00:49:29.760 align:start position:0% production but they managed to recently 00:49:29.760 --> 00:49:31.010 align:start position:0% production but they managed to recently announce<00:49:30.060> they<00:49:30.240> managed<00:49:30.599> to<00:49:30.660> compile<00:49:30.900> to 00:49:31.010 --> 00:49:31.020 align:start position:0% announce they managed to compile to 00:49:31.020 --> 00:49:35.030 align:start position:0% announce they managed to compile to unifa<00:49:31.440> V3<00:49:31.680> which<00:49:31.859> is<00:49:31.980> a<00:49:32.099> significant<00:49:32.579> bit<00:49:33.119> and 00:49:35.030 --> 00:49:35.040 align:start position:0% unifa V3 which is a significant bit and 00:49:35.040 --> 00:49:36.829 align:start position:0% unifa V3 which is a significant bit and um there<00:49:35.520> are<00:49:35.700> an<00:49:35.940> existing<00:49:36.240> effort<00:49:36.660> right 00:49:36.829 --> 00:49:36.839 align:start position:0% um there are an existing effort right 00:49:36.839 --> 00:49:39.770 align:start position:0% um there are an existing effort right now<00:49:36.960> to<00:49:37.140> rewrite<00:49:37.500> the<00:49:37.619> vvm<00:49:37.980> in<00:49:38.099> Cairo<00:49:38.880> so<00:49:39.359> I 00:49:39.770 --> 00:49:39.780 align:start position:0% now to rewrite the vvm in Cairo so I 00:49:39.780 --> 00:49:41.270 align:start position:0% now to rewrite the vvm in Cairo so I don't<00:49:39.900> know<00:49:40.020> once<00:49:40.260> again<00:49:40.319> if<00:49:40.500> it's<00:49:40.619> a<00:49:40.740> POC<00:49:41.160> if 00:49:41.270 --> 00:49:41.280 align:start position:0% don't know once again if it's a POC if 00:49:41.280 --> 00:49:42.650 align:start position:0% don't know once again if it's a POC if it's<00:49:41.339> for<00:49:41.520> fun<00:49:41.700> or<00:49:41.880> I<00:49:42.000> don't<00:49:42.060> know<00:49:42.180> maybe<00:49:42.420> maybe 00:49:42.650 --> 00:49:42.660 align:start position:0% it's for fun or I don't know maybe maybe 00:49:42.660 --> 00:49:44.569 align:start position:0% it's for fun or I don't know maybe maybe it<00:49:42.839> would<00:49:42.960> be<00:49:43.079> practical<00:49:43.380> to<00:49:44.040> prove<00:49:44.280> that<00:49:44.460> I 00:49:44.569 --> 00:49:44.579 align:start position:0% it would be practical to prove that I 00:49:44.579 --> 00:49:45.650 align:start position:0% it would be practical to prove that I want<00:49:44.700> to<00:49:44.760> see<00:49:44.940> the<00:49:45.060> numbers<00:49:45.180> I<00:49:45.420> won't<00:49:45.480> believe 00:49:45.650 --> 00:49:45.660 align:start position:0% want to see the numbers I won't believe 00:49:45.660 --> 00:49:49.010 align:start position:0% want to see the numbers I won't believe it 00:49:49.010 --> 00:49:49.020 align:start position:0% 00:49:49.020 --> 00:49:50.750 align:start position:0% going<00:49:49.380> to<00:49:49.619> your<00:49:49.800> question 00:49:50.750 --> 00:49:50.760 align:start position:0% going to your question 00:49:50.760 --> 00:49:52.250 align:start position:0% going to your question um 00:49:52.250 --> 00:49:52.260 align:start position:0% um 00:49:52.260 --> 00:49:56.390 align:start position:0% um why<00:49:53.060> uh<00:49:54.060> why<00:49:54.540> not<00:49:54.660> others<00:49:55.140> I<00:49:55.980> think<00:49:56.040> maybe<00:49:56.160> you 00:49:56.390 --> 00:49:56.400 align:start position:0% why uh why not others I think maybe you 00:49:56.400 --> 00:49:58.910 align:start position:0% why uh why not others I think maybe you should<00:49:56.520> ask<00:49:56.700> to<00:49:57.060> the<00:49:57.240> EF<00:49:57.720> people<00:49:57.960> maybe<00:49:58.619> better 00:49:58.910 --> 00:49:58.920 align:start position:0% should ask to the EF people maybe better 00:49:58.920 --> 00:50:02.150 align:start position:0% should ask to the EF people maybe better but<00:49:59.339> what's<00:50:00.180> clear<00:50:00.420> is<00:50:00.839> that<00:50:01.200> at<00:50:01.800> least<00:50:01.920> the 00:50:02.150 --> 00:50:02.160 align:start position:0% but what's clear is that at least the 00:50:02.160 --> 00:50:05.930 align:start position:0% but what's clear is that at least the BLS<00:50:03.079> 381<00:50:04.079> this<00:50:04.260> is<00:50:04.440> a<00:50:04.560> must<00:50:04.680> and<00:50:05.460> this<00:50:05.640> is<00:50:05.760> will 00:50:05.930 --> 00:50:05.940 align:start position:0% BLS 381 this is a must and this is will 00:50:05.940 --> 00:50:08.630 align:start position:0% BLS 381 this is a must and this is will be<00:50:06.060> introduced<00:50:06.420> sooner<00:50:06.780> or<00:50:06.900> later<00:50:07.099> uh<00:50:08.099> in<00:50:08.460> in 00:50:08.630 --> 00:50:08.640 align:start position:0% be introduced sooner or later uh in in 00:50:08.640 --> 00:50:11.290 align:start position:0% be introduced sooner or later uh in in ethereum<00:50:09.119> among<00:50:10.079> other<00:50:10.200> things<00:50:10.500> because 00:50:11.290 --> 00:50:11.300 align:start position:0% ethereum among other things because 00:50:11.300 --> 00:50:15.170 align:start position:0% ethereum among other things because signatures<00:50:12.560> so<00:50:13.560> because<00:50:13.740> all<00:50:14.339> the<00:50:14.520> all<00:50:14.940> the 00:50:15.170 --> 00:50:15.180 align:start position:0% signatures so because all the all the 00:50:15.180 --> 00:50:18.109 align:start position:0% signatures so because all the all the staking<00:50:15.540> stuff<00:50:15.960> it's<00:50:16.380> it's<00:50:16.740> done<00:50:17.280> with<00:50:17.579> this 00:50:18.109 --> 00:50:18.119 align:start position:0% staking stuff it's it's done with this 00:50:18.119 --> 00:50:21.349 align:start position:0% staking stuff it's it's done with this BLS<00:50:18.660> stuff<00:50:19.380> and<00:50:19.680> also<00:50:19.920> bien<00:50:20.700> well<00:50:21.060> at<00:50:21.240> the 00:50:21.349 --> 00:50:21.359 align:start position:0% BLS stuff and also bien well at the 00:50:21.359 --> 00:50:22.849 align:start position:0% BLS stuff and also bien well at the beginning<00:50:21.420> was<00:50:21.720> that<00:50:21.900> was<00:50:22.140> not 00:50:22.849 --> 00:50:22.859 align:start position:0% beginning was that was not 00:50:22.859 --> 00:50:24.650 align:start position:0% beginning was that was not safe<00:50:23.760> because<00:50:24.119> there<00:50:24.359> was<00:50:24.480> something 00:50:24.650 --> 00:50:24.660 align:start position:0% safe because there was something 00:50:24.660 --> 00:50:26.930 align:start position:0% safe because there was something discovered<00:50:25.200> but<00:50:25.380> then<00:50:25.560> it's<00:50:25.800> much<00:50:26.520> more<00:50:26.700> safe 00:50:26.930 --> 00:50:26.940 align:start position:0% discovered but then it's much more safe 00:50:26.940 --> 00:50:28.790 align:start position:0% discovered but then it's much more safe that<00:50:27.240> we<00:50:27.480> thought<00:50:27.720> that<00:50:27.960> was<00:50:28.140> safe<00:50:28.380> so<00:50:28.619> it's 00:50:28.790 --> 00:50:28.800 align:start position:0% that we thought that was safe so it's 00:50:28.800 --> 00:50:31.010 align:start position:0% that we thought that was safe so it's it's<00:50:29.099> there<00:50:29.520> you<00:50:30.060> know<00:50:30.180> it's<00:50:30.359> some<00:50:30.599> there<00:50:30.900> are 00:50:31.010 --> 00:50:31.020 align:start position:0% it's there you know it's some there are 00:50:31.020 --> 00:50:33.050 align:start position:0% it's there you know it's some there are some<00:50:31.079> doubts<00:50:31.500> of<00:50:31.740> the<00:50:31.859> BN<00:50:32.280> Corp<00:50:32.460> so<00:50:32.760> I<00:50:32.940> think 00:50:33.050 --> 00:50:33.060 align:start position:0% some doubts of the BN Corp so I think 00:50:33.060 --> 00:50:35.870 align:start position:0% some doubts of the BN Corp so I think that<00:50:33.240> sooner<00:50:33.660> or<00:50:33.720> later<00:50:33.920> ethereum<00:50:34.920> will<00:50:35.579> have 00:50:35.870 --> 00:50:35.880 align:start position:0% that sooner or later ethereum will have 00:50:35.880 --> 00:50:37.670 align:start position:0% that sooner or later ethereum will have there<00:50:36.180> has<00:50:36.359> been<00:50:36.480> some<00:50:36.660> efforts<00:50:37.079> I<00:50:37.319> know<00:50:37.500> that 00:50:37.670 --> 00:50:37.680 align:start position:0% there has been some efforts I know that 00:50:37.680 --> 00:50:41.390 align:start position:0% there has been some efforts I know that there<00:50:37.859> has<00:50:38.040> been<00:50:38.220> some<00:50:38.700> uh<00:50:39.180> stops<00:50:40.099> uh<00:50:41.099> at<00:50:41.280> some 00:50:41.390 --> 00:50:41.400 align:start position:0% there has been some uh stops uh at some 00:50:41.400 --> 00:50:44.750 align:start position:0% there has been some uh stops uh at some point<00:50:41.579> uh<00:50:42.420> on<00:50:42.660> these<00:50:42.900> this<00:50:43.380> this<00:50:43.520> adding<00:50:44.520> this 00:50:44.750 --> 00:50:44.760 align:start position:0% point uh on these this this adding this 00:50:44.760 --> 00:50:47.329 align:start position:0% point uh on these this this adding this and<00:50:45.300> here<00:50:45.660> is<00:50:45.780> for<00:50:45.960> example<00:50:46.200> uh<00:50:46.740> we<00:50:47.220> are 00:50:47.329 --> 00:50:47.339 align:start position:0% and here is for example uh we are 00:50:47.339 --> 00:50:48.890 align:start position:0% and here is for example uh we are implementing<00:50:47.700> the<00:50:47.819> fully<00:50:48.059> VM<00:50:48.359> right<00:50:48.540> now<00:50:48.660> we 00:50:48.890 --> 00:50:48.900 align:start position:0% implementing the fully VM right now we 00:50:48.900 --> 00:50:51.410 align:start position:0% implementing the fully VM right now we don't<00:50:49.619> have<00:50:49.740> to<00:50:49.859> compile<00:50:50.099> anything<00:50:50.400> like<00:50:50.819> we 00:50:51.410 --> 00:50:51.420 align:start position:0% don't have to compile anything like we 00:50:51.420 --> 00:50:55.849 align:start position:0% don't have to compile anything like we just<00:50:52.140> get<00:50:52.559> the<00:50:52.800> code<00:50:52.920> and<00:50:53.160> put<00:50:53.520> it<00:50:53.640> there 00:50:55.849 --> 00:50:55.859 align:start position:0% 00:50:55.859 --> 00:50:58.430 align:start position:0% doing<00:50:56.520> that<00:50:56.700> what<00:50:56.940> has<00:50:57.119> been<00:50:57.240> an<00:50:57.420> effort<00:50:57.780> but 00:50:58.430 --> 00:50:58.440 align:start position:0% doing that what has been an effort but 00:50:58.440 --> 00:51:00.589 align:start position:0% doing that what has been an effort but what<00:50:59.160> are<00:50:59.280> the<00:50:59.400> difficult<00:50:59.640> things<00:50:59.940> what<00:51:00.359> what 00:51:00.589 --> 00:51:00.599 align:start position:0% what are the difficult things what what 00:51:00.599 --> 00:51:02.630 align:start position:0% what are the difficult things what what what<00:51:00.660> what's<00:51:01.200> the<00:51:01.500> what<00:51:01.980> are<00:51:02.160> the<00:51:02.280> piece 00:51:02.630 --> 00:51:02.640 align:start position:0% what what's the what are the piece 00:51:02.640 --> 00:51:05.089 align:start position:0% what what's the what are the piece that's<00:51:03.000> really<00:51:03.660> difficult<00:51:04.140> to<00:51:04.500> add<00:51:04.680> so<00:51:04.980> we 00:51:05.089 --> 00:51:05.099 align:start position:0% that's really difficult to add so we 00:51:05.099 --> 00:51:07.309 align:start position:0% that's really difficult to add so we were<00:51:05.280> able<00:51:05.579> to<00:51:05.700> to<00:51:06.000> build<00:51:06.480> the<00:51:06.599> evm<00:51:07.020> but<00:51:07.200> there 00:51:07.309 --> 00:51:07.319 align:start position:0% were able to to build the evm but there 00:51:07.319 --> 00:51:09.650 align:start position:0% were able to to build the evm but there is<00:51:07.440> one<00:51:07.559> one<00:51:07.800> piece<00:51:08.099> that's<00:51:08.819> complex<00:51:09.180> we'll<00:51:09.480> do 00:51:09.650 --> 00:51:09.660 align:start position:0% is one one piece that's complex we'll do 00:51:09.660 --> 00:51:12.290 align:start position:0% is one one piece that's complex we'll do it<00:51:09.780> but<00:51:10.020> it's<00:51:10.140> really<00:51:10.380> difficult<00:51:10.680> to<00:51:10.920> do<00:51:11.040> it 00:51:12.290 --> 00:51:12.300 align:start position:0% it but it's really difficult to do it 00:51:12.300 --> 00:51:14.690 align:start position:0% it but it's really difficult to do it um<00:51:12.420> this<00:51:12.960> pre-compile<00:51:13.440> contract<00:51:13.800> of<00:51:14.040> the<00:51:14.160> bn1 00:51:14.690 --> 00:51:14.700 align:start position:0% um this pre-compile contract of the bn1 00:51:14.700 --> 00:51:19.190 align:start position:0% um this pre-compile contract of the bn1 so<00:51:15.619> complicating<00:51:16.619> the<00:51:17.220> complicating<00:51:17.880> the<00:51:18.420> uh 00:51:19.190 --> 00:51:19.200 align:start position:0% so complicating the complicating the uh 00:51:19.200 --> 00:51:23.270 align:start position:0% so complicating the complicating the uh the<00:51:19.500> layer<00:51:19.800> ones<00:51:20.220> uh<00:51:20.700> VMS<00:51:21.260> uh<00:51:22.260> is<00:51:22.800> not<00:51:22.980> a<00:51:23.160> good 00:51:23.270 --> 00:51:23.280 align:start position:0% the layer ones uh VMS uh is not a good 00:51:23.280 --> 00:51:25.490 align:start position:0% the layer ones uh VMS uh is not a good thing<00:51:23.520> and<00:51:24.119> this<00:51:24.359> is<00:51:24.480> uh<00:51:24.780> there<00:51:25.140> are<00:51:25.260> you<00:51:25.380> know 00:51:25.490 --> 00:51:25.500 align:start position:0% thing and this is uh there are you know 00:51:25.500 --> 00:51:26.809 align:start position:0% thing and this is uh there are you know there<00:51:25.680> are<00:51:25.800> some<00:51:25.980> of<00:51:26.280> course<00:51:26.400> there<00:51:26.579> are<00:51:26.700> some 00:51:26.809 --> 00:51:26.819 align:start position:0% there are some of course there are some 00:51:26.819 --> 00:51:28.490 align:start position:0% there are some of course there are some mistakes<00:51:27.059> we<00:51:27.300> did<00:51:27.420> with<00:51:27.599> the<00:51:27.720> IBM<00:51:28.079> was<00:51:28.260> created 00:51:28.490 --> 00:51:28.500 align:start position:0% mistakes we did with the IBM was created 00:51:28.500 --> 00:51:31.069 align:start position:0% mistakes we did with the IBM was created one<00:51:28.740> was<00:51:28.920> created<00:51:29.280> uh<00:51:29.819> wasm<00:51:30.480> was<00:51:30.599> not<00:51:30.720> even<00:51:30.839> an 00:51:31.069 --> 00:51:31.079 align:start position:0% one was created uh wasm was not even an 00:51:31.079 --> 00:51:33.530 align:start position:0% one was created uh wasm was not even an option<00:51:31.319> at<00:51:31.680> that<00:51:31.800> point<00:51:31.980> just<00:51:32.280> for<00:51:32.579> you<00:51:32.760> to 00:51:33.530 --> 00:51:33.540 align:start position:0% option at that point just for you to 00:51:33.540 --> 00:51:36.290 align:start position:0% option at that point just for you to just<00:51:34.020> people<00:51:34.260> to<00:51:34.500> realize<00:51:34.800> on<00:51:35.099> that<00:51:35.280> of<00:51:35.700> ZK 00:51:36.290 --> 00:51:36.300 align:start position:0% just people to realize on that of ZK 00:51:36.300 --> 00:51:38.109 align:start position:0% just people to realize on that of ZK nobody<00:51:37.020> knows 00:51:38.109 --> 00:51:38.119 align:start position:0% nobody knows 00:51:38.119 --> 00:51:42.950 align:start position:0% nobody knows they<00:51:39.119> didn't<00:51:39.240> exist<00:51:39.660> but<00:51:40.619> uh<00:51:41.220> so<00:51:42.059> here<00:51:42.240> and<00:51:42.660> and 00:51:42.950 --> 00:51:42.960 align:start position:0% they didn't exist but uh so here and and 00:51:42.960 --> 00:51:46.069 align:start position:0% they didn't exist but uh so here and and the<00:51:43.319> wife<00:51:44.220> what<00:51:44.880> I've<00:51:45.000> been<00:51:45.119> hearing<00:51:45.420> what<00:51:45.900> I 00:51:46.069 --> 00:51:46.079 align:start position:0% the wife what I've been hearing what I 00:51:46.079 --> 00:51:50.390 align:start position:0% the wife what I've been hearing what I see<00:51:46.200> is<00:51:46.500> that<00:51:46.800> uh<00:51:47.640> dbm<00:51:48.240> should<00:51:49.079> tend<00:51:49.800> to 00:51:50.390 --> 00:51:50.400 align:start position:0% see is that uh dbm should tend to 00:51:50.400 --> 00:51:54.589 align:start position:0% see is that uh dbm should tend to simplify<00:51:51.020> not<00:51:52.020> to<00:51:52.440> get<00:51:52.680> more<00:51:53.280> not<00:51:54.000> to<00:51:54.180> get<00:51:54.359> more 00:51:54.589 --> 00:51:54.599 align:start position:0% simplify not to get more not to get more 00:51:54.599 --> 00:51:58.010 align:start position:0% simplify not to get more not to get more complex<00:51:54.960> and<00:51:55.920> this<00:51:56.400> is<00:51:56.579> I<00:51:56.819> think<00:51:57.000> this<00:51:57.240> is<00:51:57.420> a 00:51:58.010 --> 00:51:58.020 align:start position:0% complex and this is I think this is a 00:51:58.020 --> 00:52:00.190 align:start position:0% complex and this is I think this is a feeling<00:51:58.500> that 00:52:00.190 --> 00:52:00.200 align:start position:0% feeling that 00:52:00.200 --> 00:52:02.870 align:start position:0% feeling that uh<00:52:01.200> in<00:52:01.380> ethereum<00:52:01.859> the<00:52:02.220> people<00:52:02.339> that's<00:52:02.640> working 00:52:02.870 --> 00:52:02.880 align:start position:0% uh in ethereum the people that's working 00:52:02.880 --> 00:52:06.230 align:start position:0% uh in ethereum the people that's working scissoring<00:52:03.540> we<00:52:04.140> have<00:52:04.380> uh<00:52:04.859> ebm<00:52:05.520> is<00:52:05.760> probably 00:52:06.230 --> 00:52:06.240 align:start position:0% scissoring we have uh ebm is probably 00:52:06.240 --> 00:52:08.329 align:start position:0% scissoring we have uh ebm is probably too<00:52:06.540> complex<00:52:06.839> and<00:52:07.260> we<00:52:07.500> need<00:52:07.800> to<00:52:07.980> tend<00:52:08.160> to 00:52:08.329 --> 00:52:08.339 align:start position:0% too complex and we need to tend to 00:52:08.339 --> 00:52:11.089 align:start position:0% too complex and we need to tend to simplify<00:52:08.760> the<00:52:09.000> gas<00:52:09.180> models<00:52:09.720> the<00:52:10.020> the<00:52:10.260> sum<00:52:10.980> of 00:52:11.089 --> 00:52:11.099 align:start position:0% simplify the gas models the the sum of 00:52:11.099 --> 00:52:13.250 align:start position:0% simplify the gas models the the sum of codes<00:52:11.339> and<00:52:11.760> and<00:52:11.940> if<00:52:12.180> you<00:52:12.300> see<00:52:12.420> the<00:52:12.599> proposals 00:52:13.250 --> 00:52:13.260 align:start position:0% codes and and if you see the proposals 00:52:13.260 --> 00:52:18.109 align:start position:0% codes and and if you see the proposals that<00:52:13.559> are<00:52:13.819> uh<00:52:14.819> coming<00:52:15.420> are<00:52:16.020> more<00:52:16.200> in<00:52:16.740> the<00:52:17.119> not 00:52:18.109 --> 00:52:18.119 align:start position:0% that are uh coming are more in the not 00:52:18.119 --> 00:52:21.770 align:start position:0% that are uh coming are more in the not in<00:52:18.619> extending<00:52:19.619> the<00:52:19.800> ABM<00:52:20.280> but<00:52:20.640> in<00:52:20.880> simplifying 00:52:21.770 --> 00:52:21.780 align:start position:0% in extending the ABM but in simplifying 00:52:21.780 --> 00:52:25.670 align:start position:0% in extending the ABM but in simplifying dbm<00:52:22.740> and<00:52:23.160> said<00:52:23.400> that<00:52:23.579> I<00:52:24.180> think<00:52:24.780> that<00:52:25.079> the<00:52:25.200> BLS 00:52:25.670 --> 00:52:25.680 align:start position:0% dbm and said that I think that the BLS 00:52:25.680 --> 00:52:28.730 align:start position:0% dbm and said that I think that the BLS is<00:52:25.980> is<00:52:26.280> a<00:52:26.579> must 00:52:28.730 --> 00:52:28.740 align:start position:0% 00:52:28.740 --> 00:52:32.109 align:start position:0% yeah<00:52:29.339> so<00:52:30.059> um<00:52:30.059> I<00:52:30.300> guess<00:52:30.420> similar<00:52:30.839> similar<00:52:31.319> to 00:52:32.109 --> 00:52:32.119 align:start position:0% yeah so um I guess similar similar to 00:52:32.119 --> 00:52:35.450 align:start position:0% yeah so um I guess similar similar to uh<00:52:33.119> Stark<00:52:33.359> where<00:52:33.599> we<00:52:33.839> we<00:52:34.200> started<00:52:34.740> not<00:52:35.099> with 00:52:35.450 --> 00:52:35.460 align:start position:0% uh Stark where we we started not with 00:52:35.460 --> 00:52:39.470 align:start position:0% uh Stark where we we started not with evm<00:52:36.119> compatibility<00:52:36.900> in<00:52:37.140> mind<00:52:37.319> for<00:52:37.920> for<00:52:38.160> mina 00:52:39.470 --> 00:52:39.480 align:start position:0% evm compatibility in mind for for mina 00:52:39.480 --> 00:52:41.510 align:start position:0% evm compatibility in mind for for mina um and<00:52:39.660> snarky.js<00:52:40.440> and<00:52:40.559> our<00:52:40.680> proof<00:52:40.859> system 00:52:41.510 --> 00:52:41.520 align:start position:0% um and snarky.js and our proof system 00:52:41.520 --> 00:52:43.490 align:start position:0% um and snarky.js and our proof system um<00:52:41.640> but<00:52:41.819> differently<00:52:42.300> from<00:52:42.660> starkware<00:52:43.200> we 00:52:43.490 --> 00:52:43.500 align:start position:0% um but differently from starkware we 00:52:43.500 --> 00:52:44.750 align:start position:0% um but differently from starkware we didn't<00:52:43.619> we<00:52:43.920> didn't<00:52:44.040> start<00:52:44.280> with<00:52:44.520> like 00:52:44.750 --> 00:52:44.760 align:start position:0% didn't we didn't start with like 00:52:44.760 --> 00:52:46.250 align:start position:0% didn't we didn't start with like performance<00:52:45.300> in<00:52:45.480> mind 00:52:46.250 --> 00:52:46.260 align:start position:0% performance in mind 00:52:46.260 --> 00:52:47.569 align:start position:0% performance in mind um because<00:52:46.440> we're<00:52:46.800> we're<00:52:47.040> not<00:52:47.280> trying<00:52:47.460> to 00:52:47.569 --> 00:52:47.579 align:start position:0% um because we're we're not trying to 00:52:47.579 --> 00:52:50.510 align:start position:0% um because we're we're not trying to build<00:52:47.760> like<00:52:48.180> uh<00:52:48.540> CK<00:52:49.079> ZK<00:52:49.619> roll<00:52:49.859> up<00:52:49.980> scalability 00:52:50.510 --> 00:52:50.520 align:start position:0% build like uh CK ZK roll up scalability 00:52:50.520 --> 00:52:52.069 align:start position:0% build like uh CK ZK roll up scalability solution 00:52:52.069 --> 00:52:52.079 align:start position:0% solution 00:52:52.079 --> 00:52:53.990 align:start position:0% solution um<00:52:52.200> we<00:52:52.440> we<00:52:52.680> were<00:52:52.859> like<00:52:53.040> okay<00:52:53.400> there's<00:52:53.819> all 00:52:53.990 --> 00:52:54.000 align:start position:0% um we we were like okay there's all 00:52:54.000 --> 00:52:56.210 align:start position:0% um we we were like okay there's all these<00:52:54.180> cool<00:52:54.300> things<00:52:54.599> you<00:52:54.780> can<00:52:54.900> do<00:52:54.960> with<00:52:55.200> ZK<00:52:55.559> uh 00:52:56.210 --> 00:52:56.220 align:start position:0% these cool things you can do with ZK uh 00:52:56.220 --> 00:52:58.730 align:start position:0% these cool things you can do with ZK uh with<00:52:56.400> with<00:52:56.579> privacy<00:52:57.059> and<00:52:57.540> recursion 00:52:58.730 --> 00:52:58.740 align:start position:0% with with privacy and recursion 00:52:58.740 --> 00:53:00.349 align:start position:0% with with privacy and recursion um<00:52:58.800> and<00:52:59.099> and<00:52:59.280> we<00:52:59.579> want<00:52:59.700> to<00:52:59.819> build<00:52:59.940> a<00:53:00.119> proof 00:53:00.349 --> 00:53:00.359 align:start position:0% um and and we want to build a proof 00:53:00.359 --> 00:53:03.710 align:start position:0% um and and we want to build a proof system<00:53:00.540> uh<00:53:01.380> that<00:53:01.619> enables<00:53:02.220> uh<00:53:03.000> people<00:53:03.359> to<00:53:03.599> take 00:53:03.710 --> 00:53:03.720 align:start position:0% system uh that enables uh people to take 00:53:03.720 --> 00:53:05.690 align:start position:0% system uh that enables uh people to take advantage<00:53:04.020> of<00:53:04.140> all<00:53:04.260> those<00:53:04.440> cool<00:53:04.619> things 00:53:05.690 --> 00:53:05.700 align:start position:0% advantage of all those cool things 00:53:05.700 --> 00:53:08.210 align:start position:0% advantage of all those cool things um<00:53:05.760> and<00:53:06.180> uh<00:53:06.900> and<00:53:07.140> and<00:53:07.260> so 00:53:08.210 --> 00:53:08.220 align:start position:0% um and uh and and so 00:53:08.220 --> 00:53:09.650 align:start position:0% um and uh and and so um<00:53:08.339> in<00:53:08.700> the<00:53:08.819> same<00:53:08.880> vein<00:53:09.240> as<00:53:09.359> what<00:53:09.480> you<00:53:09.540> were 00:53:09.650 --> 00:53:09.660 align:start position:0% um in the same vein as what you were 00:53:09.660 --> 00:53:11.030 align:start position:0% um in the same vein as what you were talking<00:53:09.780> about<00:53:09.900> like<00:53:10.200> there's<00:53:10.740> all<00:53:10.859> these 00:53:11.030 --> 00:53:11.040 align:start position:0% talking about like there's all these 00:53:11.040 --> 00:53:13.130 align:start position:0% talking about like there's all these cool<00:53:11.160> things<00:53:11.400> now<00:53:11.579> that<00:53:11.760> you<00:53:11.880> can<00:53:12.000> do<00:53:12.180> in<00:53:12.960> in 00:53:13.130 --> 00:53:13.140 align:start position:0% cool things now that you can do in in 00:53:13.140 --> 00:53:15.410 align:start position:0% cool things now that you can do in in our<00:53:13.380> proof<00:53:13.680> system<00:53:13.800> and<00:53:14.099> on<00:53:14.400> Mina<00:53:14.700> and<00:53:15.240> you 00:53:15.410 --> 00:53:15.420 align:start position:0% our proof system and on Mina and you 00:53:15.420 --> 00:53:17.390 align:start position:0% our proof system and on Mina and you know<00:53:15.480> we're<00:53:15.660> working<00:53:15.900> on<00:53:16.140> an<00:53:16.380> uh<00:53:16.859> ethereum 00:53:17.390 --> 00:53:17.400 align:start position:0% know we're working on an uh ethereum 00:53:17.400 --> 00:53:19.549 align:start position:0% know we're working on an uh ethereum Bridge<00:53:17.579> so<00:53:17.880> that<00:53:18.059> the<00:53:18.300> mean<00:53:18.540> estate<00:53:18.780> can<00:53:19.380> just 00:53:19.549 --> 00:53:19.559 align:start position:0% Bridge so that the mean estate can just 00:53:19.559 --> 00:53:21.710 align:start position:0% Bridge so that the mean estate can just be<00:53:19.800> fully<00:53:20.160> verified<00:53:20.579> from<00:53:20.940> within<00:53:21.240> ethereum 00:53:21.710 --> 00:53:21.720 align:start position:0% be fully verified from within ethereum 00:53:21.720 --> 00:53:24.410 align:start position:0% be fully verified from within ethereum and<00:53:22.140> and<00:53:22.260> the<00:53:22.619> idea<00:53:22.859> here<00:53:23.160> is<00:53:23.339> like<00:53:23.579> we<00:53:24.180> want<00:53:24.300> to 00:53:24.410 --> 00:53:24.420 align:start position:0% and and the idea here is like we want to 00:53:24.420 --> 00:53:27.049 align:start position:0% and and the idea here is like we want to bring<00:53:24.540> all<00:53:24.780> these<00:53:25.020> great<00:53:25.260> features<00:53:25.819> uh<00:53:26.819> to 00:53:27.049 --> 00:53:27.059 align:start position:0% bring all these great features uh to 00:53:27.059 --> 00:53:28.930 align:start position:0% bring all these great features uh to ethereum<00:53:27.780> Developers 00:53:28.930 --> 00:53:28.940 align:start position:0% ethereum Developers 00:53:28.940 --> 00:53:32.870 align:start position:0% ethereum Developers but<00:53:29.940> uh<00:53:30.359> you<00:53:30.599> know<00:53:30.660> like<00:53:31.440> I<00:53:32.040> guess<00:53:32.160> typescript 00:53:32.870 --> 00:53:32.880 align:start position:0% but uh you know like I guess typescript 00:53:32.880 --> 00:53:34.970 align:start position:0% but uh you know like I guess typescript is<00:53:33.540> you<00:53:33.960> know<00:53:34.079> people<00:53:34.380> are<00:53:34.559> writing<00:53:34.859> front 00:53:34.970 --> 00:53:34.980 align:start position:0% is you know people are writing front 00:53:34.980 --> 00:53:36.650 align:start position:0% is you know people are writing front ends<00:53:35.220> into<00:53:35.339> typescript<00:53:35.700> anyway<00:53:35.940> so<00:53:36.300> hopefully 00:53:36.650 --> 00:53:36.660 align:start position:0% ends into typescript anyway so hopefully 00:53:36.660 --> 00:53:37.910 align:start position:0% ends into typescript anyway so hopefully it's<00:53:36.780> not<00:53:36.960> too<00:53:37.079> bad 00:53:37.910 --> 00:53:37.920 align:start position:0% it's not too bad 00:53:37.920 --> 00:53:40.069 align:start position:0% it's not too bad um<00:53:38.040> but<00:53:38.819> uh<00:53:39.000> but<00:53:39.300> yeah<00:53:39.420> rather<00:53:39.599> rather<00:53:39.960> than 00:53:40.069 --> 00:53:40.079 align:start position:0% um but uh but yeah rather rather than 00:53:40.079 --> 00:53:42.290 align:start position:0% um but uh but yeah rather rather than like<00:53:40.500> kind<00:53:40.859> of<00:53:40.980> trying<00:53:41.280> to<00:53:41.460> put<00:53:41.700> all<00:53:42.000> these 00:53:42.290 --> 00:53:42.300 align:start position:0% like kind of trying to put all these 00:53:42.300 --> 00:53:44.690 align:start position:0% like kind of trying to put all these things<00:53:42.900> inside<00:53:43.140> evm<00:53:43.740> it's<00:53:43.920> like<00:53:44.099> okay<00:53:44.280> let's 00:53:44.690 --> 00:53:44.700 align:start position:0% things inside evm it's like okay let's 00:53:44.700 --> 00:53:47.150 align:start position:0% things inside evm it's like okay let's use<00:53:45.059> you<00:53:45.660> know<00:53:45.720> efficient<00:53:46.260> uh<00:53:46.680> elliptic 00:53:47.150 --> 00:53:47.160 align:start position:0% use you know efficient uh elliptic 00:53:47.160 --> 00:53:49.430 align:start position:0% use you know efficient uh elliptic curves<00:53:47.400> and<00:53:47.579> all<00:53:47.700> these<00:53:47.880> things<00:53:48.059> uh<00:53:48.780> to<00:53:48.900> to<00:53:49.140> do 00:53:49.430 --> 00:53:49.440 align:start position:0% curves and all these things uh to to do 00:53:49.440 --> 00:53:52.069 align:start position:0% curves and all these things uh to to do these<00:53:49.920> interesting<00:53:50.579> privacy<00:53:51.180> and<00:53:51.599> recursion 00:53:52.069 --> 00:53:52.079 align:start position:0% these interesting privacy and recursion 00:53:52.079 --> 00:53:54.410 align:start position:0% these interesting privacy and recursion all<00:53:52.440> this<00:53:52.559> stuff<00:53:52.740> and<00:53:52.980> then<00:53:53.160> uh<00:53:53.700> wrap<00:53:53.940> it<00:53:54.059> up<00:53:54.180> in 00:53:54.410 --> 00:53:54.420 align:start position:0% all this stuff and then uh wrap it up in 00:53:54.420 --> 00:53:55.910 align:start position:0% all this stuff and then uh wrap it up in a<00:53:54.540> nice<00:53:54.660> present<00:53:55.079> that<00:53:55.440> can<00:53:55.559> be<00:53:55.680> verified 00:53:55.910 --> 00:53:55.920 align:start position:0% a nice present that can be verified 00:53:55.920 --> 00:53:58.010 align:start position:0% a nice present that can be verified quickly<00:53:56.339> on<00:53:56.520> evm 00:53:58.010 --> 00:53:58.020 align:start position:0% quickly on evm 00:53:58.020 --> 00:54:00.589 align:start position:0% quickly on evm I<00:53:58.440> can<00:53:58.680> say<00:53:58.859> my<00:53:59.040> question<00:53:59.460> is<00:53:59.700> because<00:53:59.880> uh<00:54:00.420> you 00:54:00.589 --> 00:54:00.599 align:start position:0% I can say my question is because uh you 00:54:00.599 --> 00:54:02.450 align:start position:0% I can say my question is because uh you know<00:54:00.720> start<00:54:00.960> the<00:54:01.319> standards<00:54:01.920> are<00:54:01.980> evolving 00:54:02.450 --> 00:54:02.460 align:start position:0% know start the standards are evolving 00:54:02.460 --> 00:54:05.089 align:start position:0% know start the standards are evolving sometimes<00:54:03.420> and<00:54:03.720> this<00:54:03.960> is<00:54:04.079> like<00:54:04.260> a 00:54:05.089 --> 00:54:05.099 align:start position:0% sometimes and this is like a 00:54:05.099 --> 00:54:08.089 align:start position:0% sometimes and this is like a like<00:54:05.760> the<00:54:06.059> the<00:54:06.839> hottest<00:54:07.260> the<00:54:07.440> metal<00:54:07.559> will<00:54:07.920> be 00:54:08.089 --> 00:54:08.099 align:start position:0% like the the hottest the metal will be 00:54:08.099 --> 00:54:11.390 align:start position:0% like the the hottest the metal will be in<00:54:08.460> terms<00:54:08.640> of<00:54:08.700> zero<00:54:09.480> knowledge<00:54:09.800> standards<00:54:10.800> so 00:54:11.390 --> 00:54:11.400 align:start position:0% in terms of zero knowledge standards so 00:54:11.400 --> 00:54:12.890 align:start position:0% in terms of zero knowledge standards so some<00:54:11.700> of<00:54:11.819> the<00:54:11.880> time<00:54:12.059> the<00:54:12.180> constraints<00:54:12.540> on<00:54:12.780> the 00:54:12.890 --> 00:54:12.900 align:start position:0% some of the time the constraints on the 00:54:12.900 --> 00:54:15.470 align:start position:0% some of the time the constraints on the standards<00:54:13.319> come<00:54:13.500> from<00:54:13.740> things<00:54:13.980> that<00:54:14.220> are<00:54:14.819> not 00:54:15.470 --> 00:54:15.480 align:start position:0% standards come from things that are not 00:54:15.480 --> 00:54:16.849 align:start position:0% standards come from things that are not necessarily<00:54:15.900> very 00:54:16.849 --> 00:54:16.859 align:start position:0% necessarily very 00:54:16.859 --> 00:54:19.130 align:start position:0% necessarily very efficient<00:54:17.640> and<00:54:18.119> eventually<00:54:18.420> Downstream<00:54:19.020> you 00:54:19.130 --> 00:54:19.140 align:start position:0% efficient and eventually Downstream you 00:54:19.140 --> 00:54:20.930 align:start position:0% efficient and eventually Downstream you you<00:54:19.559> don't<00:54:20.099> understand<00:54:20.280> how<00:54:20.640> you<00:54:20.760> got 00:54:20.930 --> 00:54:20.940 align:start position:0% you don't understand how you got 00:54:20.940 --> 00:54:24.170 align:start position:0% you don't understand how you got something<00:54:21.300> that<00:54:21.660> is<00:54:21.839> using<00:54:22.440> a<00:54:22.680> certain<00:54:23.180> aspect 00:54:24.170 --> 00:54:24.180 align:start position:0% something that is using a certain aspect 00:54:24.180 --> 00:54:26.510 align:start position:0% something that is using a certain aspect so<00:54:24.359> a<00:54:24.720> lot<00:54:24.780> of<00:54:24.839> it<00:54:25.020> down<00:54:25.319> Downstream<00:54:26.099> decisions 00:54:26.510 --> 00:54:26.520 align:start position:0% so a lot of it down Downstream decisions 00:54:26.520 --> 00:54:29.089 align:start position:0% so a lot of it down Downstream decisions are<00:54:26.760> being<00:54:27.059> taken<00:54:27.420> because<00:54:27.720> of<00:54:28.020> of<00:54:28.619> that<00:54:28.859> right 00:54:29.089 --> 00:54:29.099 align:start position:0% are being taken because of of that right 00:54:29.099 --> 00:54:32.210 align:start position:0% are being taken because of of that right we<00:54:29.339> have<00:54:29.460> baby<00:54:29.700> jab<00:54:30.059> jar<00:54:30.300> because<00:54:30.480> it<00:54:31.260> fits<00:54:32.099> the 00:54:32.210 --> 00:54:32.220 align:start position:0% we have baby jab jar because it fits the 00:54:32.220 --> 00:54:35.450 align:start position:0% we have baby jab jar because it fits the prime<00:54:32.400> field<00:54:33.079> and<00:54:34.079> and<00:54:34.500> I<00:54:34.859> mean<00:54:35.040> it<00:54:35.220> could<00:54:35.339> be 00:54:35.450 --> 00:54:35.460 align:start position:0% prime field and and I mean it could be 00:54:35.460 --> 00:54:37.130 align:start position:0% prime field and and I mean it could be more<00:54:35.579> efficient<00:54:35.819> to<00:54:35.940> amazing<00:54:36.300> like<00:54:36.599> uh<00:54:36.900> kind 00:54:37.130 --> 00:54:37.140 align:start position:0% more efficient to amazing like uh kind 00:54:37.140 --> 00:54:39.170 align:start position:0% more efficient to amazing like uh kind of<00:54:37.260> from<00:54:37.680> a<00:54:37.859> philosophical<00:54:38.460> kind<00:54:38.700> of<00:54:38.819> aspect 00:54:39.170 --> 00:54:39.180 align:start position:0% of from a philosophical kind of aspect 00:54:39.180 --> 00:54:40.069 align:start position:0% of from a philosophical kind of aspect of 00:54:40.069 --> 00:54:40.079 align:start position:0% of 00:54:40.079 --> 00:54:41.569 align:start position:0% of at<00:54:40.619> some<00:54:40.800> point<00:54:40.920> you<00:54:41.040> need<00:54:41.160> to<00:54:41.280> leave<00:54:41.400> with 00:54:41.569 --> 00:54:41.579 align:start position:0% at some point you need to leave with 00:54:41.579 --> 00:54:43.730 align:start position:0% at some point you need to leave with with<00:54:41.760> there<00:54:42.059> that's<00:54:42.660> the<00:54:42.900> point<00:54:43.020> and<00:54:43.319> and<00:54:43.500> and 00:54:43.730 --> 00:54:43.740 align:start position:0% with there that's the point and and and 00:54:43.740 --> 00:54:45.890 align:start position:0% with there that's the point and and and you<00:54:44.280> you<00:54:44.400> can<00:54:44.880> I<00:54:45.059> mean<00:54:45.180> you<00:54:45.359> know<00:54:45.420> you<00:54:45.540> can<00:54:45.660> wish 00:54:45.890 --> 00:54:45.900 align:start position:0% you you can I mean you know you can wish 00:54:45.900 --> 00:54:48.650 align:start position:0% you you can I mean you know you can wish us<00:54:46.140> we<00:54:46.559> we<00:54:46.740> could<00:54:46.980> wish<00:54:47.160> and<00:54:47.400> we<00:54:47.640> did<00:54:47.819> many 00:54:48.650 --> 00:54:48.660 align:start position:0% us we we could wish and we did many 00:54:48.660 --> 00:54:50.750 align:start position:0% us we we could wish and we did many times<00:54:48.900> you<00:54:49.079> know<00:54:49.200> uh<00:54:49.920> wish<00:54:50.160> I<00:54:50.339> suppose<00:54:50.460> if<00:54:50.640> we 00:54:50.750 --> 00:54:50.760 align:start position:0% times you know uh wish I suppose if we 00:54:50.760 --> 00:54:53.210 align:start position:0% times you know uh wish I suppose if we can't<00:54:50.880> but<00:54:51.180> the<00:54:51.900> reality<00:54:52.200> that<00:54:52.559> you<00:54:52.680> you<00:54:52.980> won't 00:54:53.210 --> 00:54:53.220 align:start position:0% can't but the reality that you you won't 00:54:53.220 --> 00:54:55.730 align:start position:0% can't but the reality that you you won't get<00:54:53.579> to<00:54:54.300> adapt<00:54:54.660> I<00:54:54.839> mean<00:54:54.960> we<00:54:55.079> may<00:54:55.380> be<00:54:55.500> all 00:54:55.730 --> 00:54:55.740 align:start position:0% get to adapt I mean we may be all 00:54:55.740 --> 00:54:57.049 align:start position:0% get to adapt I mean we may be all convinced<00:54:56.099> here<00:54:56.160> and<00:54:56.280> Decay<00:54:56.640> the<00:54:56.760> future<00:54:56.880> but 00:54:57.049 --> 00:54:57.059 align:start position:0% convinced here and Decay the future but 00:54:57.059 --> 00:54:59.150 align:start position:0% convinced here and Decay the future but maybe<00:54:57.240> other<00:54:57.480> people<00:54:57.720> outside<00:54:57.900> or<00:54:58.260> not<00:54:58.440> and<00:54:59.040> so 00:54:59.150 --> 00:54:59.160 align:start position:0% maybe other people outside or not and so 00:54:59.160 --> 00:55:01.309 align:start position:0% maybe other people outside or not and so we<00:54:59.460> it's<00:54:59.760> a<00:55:00.000> consensus<00:55:00.300> we<00:55:00.540> want<00:55:00.720> to<00:55:00.900> agree<00:55:01.140> on 00:55:01.309 --> 00:55:01.319 align:start position:0% we it's a consensus we want to agree on 00:55:01.319 --> 00:55:03.530 align:start position:0% we it's a consensus we want to agree on what's<00:55:01.440> what's<00:55:01.680> good<00:55:01.980> so<00:55:02.760> I<00:55:03.059> tend<00:55:03.300> to<00:55:03.420> agree 00:55:03.530 --> 00:55:03.540 align:start position:0% what's what's good so I tend to agree 00:55:03.540 --> 00:55:05.270 align:start position:0% what's what's good so I tend to agree with<00:55:03.660> Jordy<00:55:04.020> we<00:55:04.260> need<00:55:04.380> actually<00:55:04.619> a<00:55:04.980> much<00:55:05.160> more 00:55:05.270 --> 00:55:05.280 align:start position:0% with Jordy we need actually a much more 00:55:05.280 --> 00:55:07.370 align:start position:0% with Jordy we need actually a much more in<00:55:05.460> favor<00:55:05.579> of<00:55:05.760> simplifying<00:55:06.300> the<00:55:06.420> network<00:55:06.599> than 00:55:07.370 --> 00:55:07.380 align:start position:0% in favor of simplifying the network than 00:55:07.380 --> 00:55:09.410 align:start position:0% in favor of simplifying the network than doing<00:55:07.680> it<00:55:07.859> than<00:55:08.040> trying<00:55:08.579> to<00:55:08.760> bring<00:55:09.000> more<00:55:09.240> more 00:55:09.410 --> 00:55:09.420 align:start position:0% doing it than trying to bring more more 00:55:09.420 --> 00:55:11.690 align:start position:0% doing it than trying to bring more more things<00:55:09.720> to<00:55:10.200> make<00:55:10.260> our<00:55:10.559> life<00:55:11.099> simpler<00:55:11.520> right 00:55:11.690 --> 00:55:11.700 align:start position:0% things to make our life simpler right 00:55:11.700 --> 00:55:14.630 align:start position:0% things to make our life simpler right now<00:55:12.359> and<00:55:13.079> uh<00:55:13.260> just<00:55:13.440> to<00:55:13.559> give<00:55:13.680> you<00:55:13.800> yeah<00:55:14.160> that's 00:55:14.630 --> 00:55:14.640 align:start position:0% now and uh just to give you yeah that's 00:55:14.640 --> 00:55:16.910 align:start position:0% now and uh just to give you yeah that's basically 00:55:16.910 --> 00:55:16.920 align:start position:0% 00:55:16.920 --> 00:55:24.349 align:start position:0% yeah<00:55:17.040> I<00:55:17.579> don't<00:55:17.700> know 00:55:24.349 --> 00:55:24.359 align:start position:0% 00:55:24.359 --> 00:55:27.410 align:start position:0% for<00:55:24.780> this<00:55:25.140> is<00:55:25.380> uh<00:55:25.859> look<00:55:26.460> in<00:55:26.760> in<00:55:26.880> the<00:55:27.240> second 00:55:27.410 --> 00:55:27.420 align:start position:0% for this is uh look in in the second 00:55:27.420 --> 00:55:29.510 align:start position:0% for this is uh look in in the second circuit<00:55:28.079> we<00:55:28.319> are<00:55:28.500> using<00:55:28.800> a<00:55:29.160> different<00:55:29.280> Prime 00:55:29.510 --> 00:55:29.520 align:start position:0% circuit we are using a different Prime 00:55:29.520 --> 00:55:31.069 align:start position:0% circuit we are using a different Prime field<00:55:29.819> we<00:55:30.000> are<00:55:30.119> using<00:55:30.300> the<00:55:30.420> goldilock<00:55:30.839> spring 00:55:31.069 --> 00:55:31.079 align:start position:0% field we are using the goldilock spring 00:55:31.079 --> 00:55:33.829 align:start position:0% field we are using the goldilock spring field<00:55:31.319> we<00:55:32.040> are<00:55:32.220> building<00:55:32.640> a<00:55:33.240> stark<00:55:33.480> we<00:55:33.720> are 00:55:33.829 --> 00:55:33.839 align:start position:0% field we are building a stark we are 00:55:33.839 --> 00:55:35.390 align:start position:0% field we are building a stark we are building<00:55:33.900> a<00:55:34.079> recursion<00:55:34.500> of<00:55:34.680> a<00:55:34.800> stark<00:55:35.040> we<00:55:35.280> are 00:55:35.390 --> 00:55:35.400 align:start position:0% building a recursion of a stark we are 00:55:35.400 --> 00:55:37.309 align:start position:0% building a recursion of a stark we are doing<00:55:35.520> a<00:55:35.700> lot<00:55:35.819> of<00:55:35.940> crazy<00:55:36.180> cryptography<00:55:37.020> in 00:55:37.309 --> 00:55:37.319 align:start position:0% doing a lot of crazy cryptography in 00:55:37.319 --> 00:55:40.010 align:start position:0% doing a lot of crazy cryptography in there<00:55:37.500> and<00:55:38.220> just<00:55:38.460> in<00:55:38.640> the<00:55:38.819> last<00:55:38.940> moment<00:55:39.240> we 00:55:40.010 --> 00:55:40.020 align:start position:0% there and just in the last moment we 00:55:40.020 --> 00:55:42.230 align:start position:0% there and just in the last moment we just<00:55:40.200> built<00:55:40.559> the<00:55:40.680> glow<00:55:40.920> 16<00:55:41.040> or<00:55:41.400> a<00:55:41.520> plonk<00:55:41.940> that's 00:55:42.230 --> 00:55:42.240 align:start position:0% just built the glow 16 or a plonk that's 00:55:42.240 --> 00:55:44.270 align:start position:0% just built the glow 16 or a plonk that's just<00:55:42.480> but<00:55:42.660> this<00:55:42.780> is<00:55:42.900> the<00:55:43.020> last<00:55:43.200> the<00:55:43.859> last<00:55:44.040> piece 00:55:44.270 --> 00:55:44.280 align:start position:0% just but this is the last the last piece 00:55:44.280 --> 00:55:47.150 align:start position:0% just but this is the last the last piece so<00:55:44.579> it's<00:55:44.819> like<00:55:44.940> the<00:55:45.180> adapter<00:55:45.960> if<00:55:46.380> you<00:55:46.500> want<00:55:46.680> to 00:55:47.150 --> 00:55:47.160 align:start position:0% so it's like the adapter if you want to 00:55:47.160 --> 00:55:49.670 align:start position:0% so it's like the adapter if you want to the<00:55:47.280> network<00:55:47.460> if<00:55:47.880> if<00:55:48.059> so 00:55:49.670 --> 00:55:49.680 align:start position:0% the network if if so 00:55:49.680 --> 00:55:53.150 align:start position:0% the network if if so maybe<00:55:50.339> then<00:55:50.640> that<00:55:50.880> so<00:55:51.300> maybe<00:55:51.480> the<00:55:51.660> IBM<00:55:52.160> you<00:55:53.160> you 00:55:53.150 --> 00:55:53.160 align:start position:0% maybe then that so maybe the IBM you you 00:55:53.160 --> 00:55:54.849 align:start position:0% maybe then that so maybe the IBM you you just<00:55:53.700> need<00:55:53.819> one<00:55:54.119> thing 00:55:54.849 --> 00:55:54.859 align:start position:0% just need one thing 00:55:54.859 --> 00:55:57.170 align:start position:0% just need one thing hash<00:55:55.859> functions<00:55:56.220> how<00:55:56.400> many<00:55:56.520> hash<00:55:56.760> functions 00:55:57.170 --> 00:55:57.180 align:start position:0% hash functions how many hash functions 00:55:57.180 --> 00:56:00.010 align:start position:0% hash functions how many hash functions needs<00:55:57.720> uh<00:55:57.960> requires<00:55:58.380> the<00:55:58.500> ABM 00:56:00.010 --> 00:56:00.020 align:start position:0% needs uh requires the ABM 00:56:00.020 --> 00:56:03.829 align:start position:0% needs uh requires the ABM well<00:56:01.020> we<00:56:01.260> have<00:56:01.380> ketchak<00:56:01.859> we<00:56:02.400> have<00:56:02.640> a<00:56:03.000> a<00:56:03.359> shadow 00:56:03.829 --> 00:56:03.839 align:start position:0% well we have ketchak we have a a shadow 00:56:03.839 --> 00:56:07.430 align:start position:0% well we have ketchak we have a a shadow 56<00:56:04.339> recently<00:56:05.339> a<00:56:05.579> 30<00:56:05.760> minute<00:56:06.119> Blake 00:56:07.430 --> 00:56:07.440 align:start position:0% 56 recently a 30 minute Blake 00:56:07.440 --> 00:56:11.630 align:start position:0% 56 recently a 30 minute Blake uh<00:56:08.640> is<00:56:09.119> it<00:56:09.240> necessary 00:56:11.630 --> 00:56:11.640 align:start position:0% uh is it necessary 00:56:11.640 --> 00:56:14.150 align:start position:0% uh is it necessary maybe<00:56:12.059> with<00:56:12.420> Shadow<00:56:12.960> 56<00:56:13.440> would<00:56:13.680> be<00:56:13.800> more<00:56:13.920> more 00:56:14.150 --> 00:56:14.160 align:start position:0% maybe with Shadow 56 would be more more 00:56:14.160 --> 00:56:16.609 align:start position:0% maybe with Shadow 56 would be more more than<00:56:14.339> enough<00:56:14.520> from<00:56:14.819> the<00:56:14.940> beginning 00:56:16.609 --> 00:56:16.619 align:start position:0% than enough from the beginning 00:56:16.619 --> 00:56:19.130 align:start position:0% than enough from the beginning you<00:56:17.040> couldn't<00:56:17.099> argue<00:56:17.640> that<00:56:17.880> the<00:56:18.540> pre-compile 00:56:19.130 --> 00:56:19.140 align:start position:0% you couldn't argue that the pre-compile 00:56:19.140 --> 00:56:21.049 align:start position:0% you couldn't argue that the pre-compile could<00:56:19.319> have<00:56:19.440> been<00:56:19.619> you<00:56:19.800> know<00:56:19.920> like<00:56:20.160> we<00:56:20.940> could 00:56:21.049 --> 00:56:21.059 align:start position:0% could have been you know like we could 00:56:21.059 --> 00:56:22.549 align:start position:0% could have been you know like we could have<00:56:21.180> made<00:56:21.300> things<00:56:21.480> cheaper<00:56:21.839> or<00:56:22.319> in<00:56:22.440> first 00:56:22.549 --> 00:56:22.559 align:start position:0% have made things cheaper or in first 00:56:22.559 --> 00:56:23.990 align:start position:0% have made things cheaper or in first place<00:56:22.680> or<00:56:22.859> maybe<00:56:23.099> you<00:56:23.220> know<00:56:23.339> made<00:56:23.579> many<00:56:23.760> things 00:56:23.990 --> 00:56:24.000 align:start position:0% place or maybe you know made many things 00:56:24.000 --> 00:56:25.790 align:start position:0% place or maybe you know made many things that<00:56:24.180> are<00:56:24.359> wide<00:56:25.079> if<00:56:25.260> more<00:56:25.440> so<00:56:25.559> much<00:56:25.740> more 00:56:25.790 --> 00:56:25.800 align:start position:0% that are wide if more so much more 00:56:25.800 --> 00:56:27.109 align:start position:0% that are wide if more so much more efficient<00:56:26.040> of<00:56:26.280> the<00:56:26.400> spring<00:56:26.520> you<00:56:26.940> know<00:56:27.000> there's 00:56:27.109 --> 00:56:27.119 align:start position:0% efficient of the spring you know there's 00:56:27.119 --> 00:56:28.370 align:start position:0% efficient of the spring you know there's many<00:56:27.240> things<00:56:27.420> you<00:56:27.540> could<00:56:27.660> discuss<00:56:28.020> in<00:56:28.200> the 00:56:28.370 --> 00:56:28.380 align:start position:0% many things you could discuss in the 00:56:28.380 --> 00:56:32.089 align:start position:0% many things you could discuss in the back<00:56:28.440> but<00:56:29.339> this<00:56:29.819> is<00:56:29.940> why<00:56:30.780> why<00:56:31.020> and<00:56:31.319> why<00:56:31.619> this<00:56:31.859> is 00:56:32.089 --> 00:56:32.099 align:start position:0% back but this is why why and why this is 00:56:32.099 --> 00:56:34.730 align:start position:0% back but this is why why and why this is possible<00:56:32.880> right<00:56:33.180> now<00:56:33.359> and<00:56:33.660> maybe<00:56:33.839> and<00:56:34.440> this<00:56:34.619> is 00:56:34.730 --> 00:56:34.740 align:start position:0% possible right now and maybe and this is 00:56:34.740 --> 00:56:37.309 align:start position:0% possible right now and maybe and this is changed<00:56:35.099> from<00:56:35.400> three<00:56:36.059> four<00:56:36.359> years<00:56:36.599> ago<00:56:36.960> it's 00:56:37.309 --> 00:56:37.319 align:start position:0% changed from three four years ago it's 00:56:37.319 --> 00:56:39.650 align:start position:0% changed from three four years ago it's because<00:56:37.500> we<00:56:37.800> have<00:56:37.920> this<00:56:38.099> validity<00:56:38.520> proof<00:56:38.880> we 00:56:39.650 --> 00:56:39.660 align:start position:0% because we have this validity proof we 00:56:39.660 --> 00:56:41.870 align:start position:0% because we have this validity proof we can<00:56:39.900> compute<00:56:40.859> things 00:56:41.870 --> 00:56:41.880 align:start position:0% can compute things 00:56:41.880 --> 00:56:45.650 align:start position:0% can compute things of<00:56:42.480> chain<00:56:42.960> and<00:56:43.559> validate<00:56:44.099> them<00:56:44.280> on<00:56:44.640> chain<00:56:44.880> so 00:56:45.650 --> 00:56:45.660 align:start position:0% of chain and validate them on chain so 00:56:45.660 --> 00:56:47.750 align:start position:0% of chain and validate them on chain so we<00:56:45.960> just<00:56:46.140> need<00:56:46.380> to<00:56:46.680> care<00:56:46.859> how<00:56:47.160> we<00:56:47.339> validate 00:56:47.750 --> 00:56:47.760 align:start position:0% we just need to care how we validate 00:56:47.760 --> 00:56:51.290 align:start position:0% we just need to care how we validate these<00:56:48.000> things<00:56:48.180> on<00:56:48.540> chain<00:56:48.740> and<00:56:50.000> bn128<00:56:51.000> or<00:56:51.180> if 00:56:51.290 --> 00:56:51.300 align:start position:0% these things on chain and bn128 or if 00:56:51.300 --> 00:56:54.410 align:start position:0% these things on chain and bn128 or if you<00:56:51.420> want<00:56:51.480> to<00:56:51.599> BLS<00:56:52.460> it's<00:56:53.460> more<00:56:53.640> than<00:56:53.819> is<00:56:54.180> more 00:56:54.410 --> 00:56:54.420 align:start position:0% you want to BLS it's more than is more 00:56:54.420 --> 00:56:56.870 align:start position:0% you want to BLS it's more than is more than<00:56:54.540> enough<00:56:54.839> so<00:56:55.440> probably<00:56:56.040> if<00:56:56.400> the<00:56:56.520> if<00:56:56.760> the 00:56:56.870 --> 00:56:56.880 align:start position:0% than enough so probably if the if the 00:56:56.880 --> 00:57:00.049 align:start position:0% than enough so probably if the if the ethereum<00:56:57.359> had<00:56:57.660> to<00:56:57.780> be<00:56:57.960> done<00:56:58.140> now<00:56:58.400> uh<00:56:59.400> it<00:56:59.940> would 00:57:00.049 --> 00:57:00.059 align:start position:0% ethereum had to be done now uh it would 00:57:00.059 --> 00:57:03.650 align:start position:0% ethereum had to be done now uh it would be<00:57:00.240> less<00:57:00.540> uh<00:57:01.319> cryptographic<00:57:01.980> Primitives<00:57:02.660> and 00:57:03.650 --> 00:57:03.660 align:start position:0% be less uh cryptographic Primitives and 00:57:03.660 --> 00:57:06.530 align:start position:0% be less uh cryptographic Primitives and uh<00:57:04.440> more<00:57:04.859> basic<00:57:05.220> thing<00:57:05.400> because<00:57:05.760> we<00:57:06.059> can<00:57:06.180> we 00:57:06.530 --> 00:57:06.540 align:start position:0% uh more basic thing because we can we 00:57:06.540 --> 00:57:10.190 align:start position:0% uh more basic thing because we can we can<00:57:06.859> we<00:57:07.859> can<00:57:07.980> accelerate<00:57:08.400> that<00:57:08.640> of<00:57:09.000> chain<00:57:09.599> uh 00:57:10.190 --> 00:57:10.200 align:start position:0% can we can accelerate that of chain uh 00:57:10.200 --> 00:57:13.010 align:start position:0% can we can accelerate that of chain uh and<00:57:10.380> and<00:57:10.619> validate<00:57:11.160> that<00:57:11.460> uh<00:57:12.059> with<00:57:12.660> uh<00:57:12.780> with 00:57:13.010 --> 00:57:13.020 align:start position:0% and and validate that uh with uh with 00:57:13.020 --> 00:57:15.109 align:start position:0% and and validate that uh with uh with the<00:57:13.140> visibility<00:57:13.500> proof<00:57:13.980> on<00:57:14.099> chain 00:57:15.109 --> 00:57:15.119 align:start position:0% the visibility proof on chain 00:57:15.119 --> 00:57:17.329 align:start position:0% the visibility proof on chain and<00:57:15.599> just<00:57:15.720> to<00:57:15.900> conclude<00:57:16.200> on<00:57:16.559> this<00:57:16.740> if<00:57:17.099> you<00:57:17.220> want 00:57:17.329 --> 00:57:17.339 align:start position:0% and just to conclude on this if you want 00:57:17.339 --> 00:57:18.770 align:start position:0% and just to conclude on this if you want to<00:57:17.460> have<00:57:17.640> much<00:57:17.819> more<00:57:17.940> impact<00:57:18.240> and<00:57:18.420> make<00:57:18.599> one 00:57:18.770 --> 00:57:18.780 align:start position:0% to have much more impact and make one 00:57:18.780 --> 00:57:20.630 align:start position:0% to have much more impact and make one change<00:57:19.020> changing<00:57:19.800> I<00:57:20.040> mean<00:57:20.099> it's<00:57:20.280> going<00:57:20.460> very 00:57:20.630 --> 00:57:20.640 align:start position:0% change changing I mean it's going very 00:57:20.640 --> 00:57:23.569 align:start position:0% change changing I mean it's going very ballsy<00:57:21.119> changing<00:57:21.599> kitchen<00:57:22.280> might<00:57:23.280> be<00:57:23.400> more 00:57:23.569 --> 00:57:23.579 align:start position:0% ballsy changing kitchen might be more 00:57:23.579 --> 00:57:25.910 align:start position:0% ballsy changing kitchen might be more helpful 00:57:25.910 --> 00:57:25.920 align:start position:0% 00:57:25.920 --> 00:57:28.430 align:start position:0% no<00:57:26.339> because<00:57:26.579> you<00:57:26.819> change<00:57:27.540> we<00:57:27.780> pass<00:57:27.960> it<00:57:28.140> on<00:57:28.260> in 00:57:28.430 --> 00:57:28.440 align:start position:0% no because you change we pass it on in 00:57:28.440 --> 00:57:31.329 align:start position:0% no because you change we pass it on in which<00:57:28.559> which<00:57:28.800> in<00:57:29.460> which<00:57:29.640> prime<00:57:29.760> field 00:57:31.329 --> 00:57:31.339 align:start position:0% which which in which prime field 00:57:31.339 --> 00:57:33.829 align:start position:0% which which in which prime field yeah<00:57:32.339> yeah<00:57:32.400> but<00:57:32.579> that's<00:57:32.760> that's<00:57:33.000> that's<00:57:33.300> the 00:57:33.829 --> 00:57:33.839 align:start position:0% yeah yeah but that's that's that's the 00:57:33.839 --> 00:57:34.790 align:start position:0% yeah yeah but that's that's that's the thing<00:57:33.960> you<00:57:34.079> know<00:57:34.200> it's<00:57:34.380> and<00:57:34.559> I've<00:57:34.680> been 00:57:34.790 --> 00:57:34.800 align:start position:0% thing you know it's and I've been 00:57:34.800 --> 00:57:36.650 align:start position:0% thing you know it's and I've been thinking<00:57:35.040> you<00:57:35.220> know<00:57:35.280> all<00:57:35.819> of<00:57:35.940> us<00:57:36.059> we<00:57:36.420> haven't 00:57:36.650 --> 00:57:36.660 align:start position:0% thinking you know all of us we haven't 00:57:36.660 --> 00:57:38.870 align:start position:0% thinking you know all of us we haven't have<00:57:37.140> been<00:57:37.380> thinking<00:57:38.220> on<00:57:38.400> that<00:57:38.520> this<00:57:38.700> why 00:57:38.870 --> 00:57:38.880 align:start position:0% have been thinking on that this why 00:57:38.880 --> 00:57:42.170 align:start position:0% have been thinking on that this why Poseidon<00:57:39.420> is<00:57:39.599> not<00:57:39.780> in<00:57:40.020> the<00:57:40.200> or<00:57:40.800> why<00:57:41.099> the<00:57:41.339> so<00:57:41.760> why 00:57:42.170 --> 00:57:42.180 align:start position:0% Poseidon is not in the or why the so why 00:57:42.180 --> 00:57:44.450 align:start position:0% Poseidon is not in the or why the so why don't<00:57:42.359> we<00:57:42.480> have<00:57:42.720> a<00:57:42.900> milk<00:57:43.200> C<00:57:43.440> at<00:57:43.680> some<00:57:43.800> point<00:57:43.980> uh 00:57:44.450 --> 00:57:44.460 align:start position:0% don't we have a milk C at some point uh 00:57:44.460 --> 00:57:46.670 align:start position:0% don't we have a milk C at some point uh it's<00:57:44.640> not<00:57:44.819> in<00:57:45.059> the<00:57:45.180> in<00:57:45.480> the<00:57:45.599> VM<00:57:45.900> and<00:57:46.260> and<00:57:46.500> this 00:57:46.670 --> 00:57:46.680 align:start position:0% it's not in the in the VM and and this 00:57:46.680 --> 00:57:49.549 align:start position:0% it's not in the in the VM and and this is<00:57:46.800> the<00:57:46.859> thing<00:57:47.040> but<00:57:47.460> as<00:57:48.240> we<00:57:48.420> evolve<00:57:48.900> as<00:57:49.380> we 00:57:49.549 --> 00:57:49.559 align:start position:0% is the thing but as we evolve as we 00:57:49.559 --> 00:57:52.010 align:start position:0% is the thing but as we evolve as we evolve<00:57:49.980> we<00:57:50.280> see<00:57:50.460> that<00:57:50.700> this<00:57:51.000> is<00:57:51.240> less 00:57:52.010 --> 00:57:52.020 align:start position:0% evolve we see that this is less 00:57:52.020 --> 00:57:54.970 align:start position:0% evolve we see that this is less important<00:57:52.559> because<00:57:53.280> we<00:57:53.700> have<00:57:53.880> because<00:57:54.480> this 00:57:54.970 --> 00:57:54.980 align:start position:0% important because we have because this 00:57:54.980 --> 00:57:58.190 align:start position:0% important because we have because this computational<00:57:55.980> proof<00:57:56.579> are<00:57:57.420> getting<00:57:57.839> much 00:57:58.190 --> 00:57:58.200 align:start position:0% computational proof are getting much 00:57:58.200 --> 00:58:00.530 align:start position:0% computational proof are getting much faster<00:57:58.500> and<00:57:58.800> much<00:57:59.099> better<00:57:59.339> so<00:57:59.819> we<00:58:00.180> require 00:58:00.530 --> 00:58:00.540 align:start position:0% faster and much better so we require 00:58:00.540 --> 00:58:03.290 align:start position:0% faster and much better so we require less<00:58:01.079> this<00:58:01.500> so<00:58:01.980> we<00:58:02.160> can<00:58:02.339> sacrifice<00:58:02.819> a<00:58:03.180> little 00:58:03.290 --> 00:58:03.300 align:start position:0% less this so we can sacrifice a little 00:58:03.300 --> 00:58:05.089 align:start position:0% less this so we can sacrifice a little bit<00:58:03.480> of<00:58:03.599> optimization<00:58:04.079> right<00:58:04.500> now<00:58:04.740> we<00:58:04.920> can 00:58:05.089 --> 00:58:05.099 align:start position:0% bit of optimization right now we can 00:58:05.099 --> 00:58:08.030 align:start position:0% bit of optimization right now we can look<00:58:05.520> in<00:58:05.819> in<00:58:05.940> in<00:58:06.119> the<00:58:06.480> ABN<00:58:06.839> circuit<00:58:07.140> we<00:58:07.380> can<00:58:07.500> we 00:58:08.030 --> 00:58:08.040 align:start position:0% look in in in the ABN circuit we can we 00:58:08.040 --> 00:58:11.630 align:start position:0% look in in in the ABN circuit we can we can<00:58:08.220> validate<00:58:08.700> for<00:58:09.660> 500<00:58:10.319> catch<00:58:10.920> acts<00:58:11.160> in<00:58:11.520> the 00:58:11.630 --> 00:58:11.640 align:start position:0% can validate for 500 catch acts in the 00:58:11.640 --> 00:58:14.030 align:start position:0% can validate for 500 catch acts in the in<00:58:11.880> the<00:58:12.059> proof<00:58:12.300> we<00:58:12.480> can<00:58:12.599> validate<00:58:13.079> uh<00:58:13.680> I<00:58:13.920> don't 00:58:14.030 --> 00:58:14.040 align:start position:0% in the proof we can validate uh I don't 00:58:14.040 --> 00:58:17.290 align:start position:0% in the proof we can validate uh I don't know<00:58:14.160> like<00:58:14.339> something<00:58:14.640> like<00:58:14.940> 100<00:58:15.420> or<00:58:15.780> 200<00:58:16.319> uh 00:58:17.290 --> 00:58:17.300 align:start position:0% know like something like 100 or 200 uh 00:58:17.300 --> 00:58:21.650 align:start position:0% know like something like 100 or 200 uh cdsas<00:58:18.300> with<00:58:19.140> the<00:58:19.380> cdsa<00:58:20.280> ethereum<00:58:20.819> Corps<00:58:21.480> in 00:58:21.650 --> 00:58:21.660 align:start position:0% cdsas with the cdsa ethereum Corps in 00:58:21.660 --> 00:58:23.990 align:start position:0% cdsas with the cdsa ethereum Corps in there<00:58:21.839> we<00:58:22.200> can<00:58:22.319> do<00:58:22.559> paintings<00:58:23.400> inside<00:58:23.700> there 00:58:23.990 --> 00:58:24.000 align:start position:0% there we can do paintings inside there 00:58:24.000 --> 00:58:26.210 align:start position:0% there we can do paintings inside there we<00:58:24.240> can<00:58:24.359> do<00:58:24.540> everything<00:58:24.839> in<00:58:25.319> there 00:58:26.210 --> 00:58:26.220 align:start position:0% we can do everything in there 00:58:26.220 --> 00:58:29.809 align:start position:0% we can do everything in there silly<00:58:27.059> it's<00:58:27.240> not<00:58:27.359> optimal 00:58:29.809 --> 00:58:29.819 align:start position:0% 00:58:29.819 --> 00:58:33.109 align:start position:0% doable<00:58:30.540> and<00:58:31.140> it's<00:58:31.500> it's<00:58:31.800> getting<00:58:32.460> every<00:58:32.940> time 00:58:33.109 --> 00:58:33.119 align:start position:0% doable and it's it's getting every time 00:58:33.119 --> 00:58:35.870 align:start position:0% doable and it's it's getting every time more<00:58:33.420> efficient<00:58:33.780> so<00:58:34.559> at<00:58:34.920> the<00:58:35.040> point<00:58:35.220> that<00:58:35.579> we 00:58:35.870 --> 00:58:35.880 align:start position:0% more efficient so at the point that we 00:58:35.880 --> 00:58:39.289 align:start position:0% more efficient so at the point that we have<00:58:36.119> this<00:58:36.420> we<00:58:37.140> require<00:58:37.440> less<00:58:37.920> how<00:58:38.760> from<00:58:39.180> the 00:58:39.289 --> 00:58:39.299 align:start position:0% have this we require less how from the 00:58:39.299 --> 00:58:41.270 align:start position:0% have this we require less how from the L1<00:58:39.599> we<00:58:39.900> require<00:58:40.079> less<00:58:40.380> Health<00:58:40.619> from<00:58:40.920> that<00:58:41.040> so 00:58:41.270 --> 00:58:41.280 align:start position:0% L1 we require less Health from that so 00:58:41.280 --> 00:58:43.670 align:start position:0% L1 we require less Health from that so so<00:58:41.640> that's<00:58:41.880> why<00:58:42.180> I<00:58:42.839> think<00:58:42.900> that<00:58:43.140> this<00:58:43.319> tendency 00:58:43.670 --> 00:58:43.680 align:start position:0% so that's why I think that this tendency 00:58:43.680 --> 00:58:51.109 align:start position:0% so that's why I think that this tendency to<00:58:44.099> simplify<00:58:44.880> is<00:58:45.599> is<00:58:45.839> is<00:58:45.960> is<00:58:46.200> is<00:58:46.500> is<00:58:46.799> a<00:58:47.339> trend 00:58:51.109 --> 00:58:51.119 align:start position:0% 00:58:51.119 --> 00:58:53.870 align:start position:0% oh<00:58:51.720> yeah<00:58:51.960> I<00:58:52.260> I<00:58:52.440> also<00:58:52.740> feel<00:58:52.920> like<00:58:53.040> part<00:58:53.339> of<00:58:53.640> dunk 00:58:53.870 --> 00:58:53.880 align:start position:0% oh yeah I I also feel like part of dunk 00:58:53.880 --> 00:58:55.690 align:start position:0% oh yeah I I also feel like part of dunk sharding<00:58:54.359> is<00:58:54.480> moving<00:58:54.839> in<00:58:55.079> that<00:58:55.260> direction 00:58:55.690 --> 00:58:55.700 align:start position:0% sharding is moving in that direction 00:58:55.700 --> 00:58:59.809 align:start position:0% sharding is moving in that direction like<00:58:56.700> they<00:58:57.240> introduced<00:58:57.839> the<00:58:58.260> pre-compile<00:58:59.040> for 00:58:59.809 --> 00:58:59.819 align:start position:0% like they introduced the pre-compile for 00:58:59.819 --> 00:59:03.109 align:start position:0% like they introduced the pre-compile for Point<00:59:00.180> evaluation<00:59:00.720> for<00:59:00.960> kcg<00:59:01.440> and<00:59:02.339> you<00:59:03.000> know 00:59:03.109 --> 00:59:03.119 align:start position:0% Point evaluation for kcg and you know 00:59:03.119 --> 00:59:06.589 align:start position:0% Point evaluation for kcg and you know then<00:59:03.720> you<00:59:03.900> can<00:59:04.079> understand<00:59:04.400> kcg<00:59:05.400> proofs<00:59:05.880> but 00:59:06.589 --> 00:59:06.599 align:start position:0% then you can understand kcg proofs but 00:59:06.599 --> 00:59:09.349 align:start position:0% then you can understand kcg proofs but beyond<00:59:07.200> that<00:59:07.559> it's<00:59:07.980> all<00:59:08.160> blobs<00:59:08.700> you<00:59:08.940> know<00:59:09.059> it's 00:59:09.349 --> 00:59:09.359 align:start position:0% beyond that it's all blobs you know it's 00:59:09.359 --> 00:59:10.430 align:start position:0% beyond that it's all blobs you know it's all 00:59:10.430 --> 00:59:10.440 align:start position:0% all 00:59:10.440 --> 00:59:13.010 align:start position:0% all um<00:59:10.500> delegated<00:59:11.040> to<00:59:11.280> the<00:59:11.400> Roll-Ups<00:59:11.880> well<00:59:12.480> we<00:59:12.900> are 00:59:13.010 --> 00:59:13.020 align:start position:0% um delegated to the Roll-Ups well we are 00:59:13.020 --> 00:59:16.549 align:start position:0% um delegated to the Roll-Ups well we are we<00:59:13.500> are<00:59:13.680> over<00:59:14.220> time<00:59:14.579> so 00:59:16.549 --> 00:59:16.559 align:start position:0% we are over time so 00:59:16.559 --> 00:59:18.890 align:start position:0% we are over time so there's<00:59:17.220> one<00:59:17.520> last<00:59:17.700> question<00:59:17.940> okay<00:59:18.299> ask<00:59:18.720> it 00:59:18.890 --> 00:59:18.900 align:start position:0% there's one last question okay ask it 00:59:18.900 --> 00:59:20.329 align:start position:0% there's one last question okay ask it ask<00:59:19.140> it<00:59:19.319> thanks 00:59:20.329 --> 00:59:20.339 align:start position:0% ask it thanks 00:59:20.339 --> 00:59:21.650 align:start position:0% ask it thanks thanks yeah<00:59:20.700> I<00:59:20.819> just<00:59:20.940> wanted<00:59:21.059> to<00:59:21.240> know<00:59:21.359> that<00:59:21.480> I 00:59:21.650 --> 00:59:21.660 align:start position:0% thanks yeah I just wanted to know that I 00:59:21.660 --> 00:59:23.510 align:start position:0% thanks yeah I just wanted to know that I see<00:59:21.780> a<00:59:21.900> lot<00:59:21.960> of<00:59:22.079> sense<00:59:22.260> in<00:59:22.619> like<00:59:22.980> breaking<00:59:23.339> this 00:59:23.510 --> 00:59:23.520 align:start position:0% see a lot of sense in like breaking this 00:59:23.520 --> 00:59:27.289 align:start position:0% see a lot of sense in like breaking this evm<00:59:24.059> eyes<00:59:24.299> and<00:59:24.839> creating<00:59:25.200> DSL<00:59:26.040> not<00:59:26.700> only<00:59:26.940> for 00:59:27.289 --> 00:59:27.299 align:start position:0% evm eyes and creating DSL not only for 00:59:27.299 --> 00:59:29.870 align:start position:0% evm eyes and creating DSL not only for like<00:59:27.660> opening<00:59:28.200> new<00:59:28.380> area<00:59:28.619> of<00:59:28.859> innovation 00:59:29.870 --> 00:59:29.880 align:start position:0% like opening new area of innovation 00:59:29.880 --> 00:59:32.270 align:start position:0% like opening new area of innovation and<00:59:30.359> like<00:59:30.599> clear<00:59:30.960> question<00:59:31.319> to<00:59:31.619> basically 00:59:32.270 --> 00:59:32.280 align:start position:0% and like clear question to basically 00:59:32.280 --> 00:59:35.870 align:start position:0% and like clear question to basically Amina<00:59:33.000> I<00:59:33.780> mean<00:59:33.900> does<00:59:34.859> it<00:59:35.040> make<00:59:35.220> sense<00:59:35.400> or<00:59:35.640> you 00:59:35.870 --> 00:59:35.880 align:start position:0% Amina I mean does it make sense or you 00:59:35.880 --> 00:59:37.370 align:start position:0% Amina I mean does it make sense or you also<00:59:36.119> like<00:59:36.240> for<00:59:36.540> example<00:59:36.780> to<00:59:36.900> collaborate 00:59:37.370 --> 00:59:37.380 align:start position:0% also like for example to collaborate 00:59:37.380 --> 00:59:40.910 align:start position:0% also like for example to collaborate with<00:59:37.680> Cairo<00:59:38.280> and<00:59:39.240> uh<00:59:39.599> maybe<00:59:40.140> like<00:59:40.500> you<00:59:40.740> know 00:59:40.910 --> 00:59:40.920 align:start position:0% with Cairo and uh maybe like you know 00:59:40.920 --> 00:59:43.849 align:start position:0% with Cairo and uh maybe like you know since<00:59:41.760> like<00:59:42.059> it's<00:59:42.180> better<00:59:42.420> model<00:59:42.720> for<00:59:43.319> the<00:59:43.500> CK 00:59:43.849 --> 00:59:43.859 align:start position:0% since like it's better model for the CK 00:59:43.859 --> 00:59:47.809 align:start position:0% since like it's better model for the CK than<00:59:44.220> uh<00:59:44.700> like<00:59:44.940> imperative<00:59:45.780> languages<00:59:46.460> and<00:59:47.460> uh 00:59:47.809 --> 00:59:47.819 align:start position:0% than uh like imperative languages and uh 00:59:47.819 --> 00:59:50.450 align:start position:0% than uh like imperative languages and uh yeah<00:59:48.180> basically<00:59:48.720> work<00:59:49.020> on<00:59:49.260> better<00:59:49.920> tooling 00:59:50.450 --> 00:59:50.460 align:start position:0% yeah basically work on better tooling 00:59:50.460 --> 00:59:52.670 align:start position:0% yeah basically work on better tooling for<00:59:50.640> uh<00:59:51.240> yeah<00:59:51.599> I<00:59:52.020> mean<00:59:52.140> operational 00:59:52.670 --> 00:59:52.680 align:start position:0% for uh yeah I mean operational 00:59:52.680 --> 00:59:55.430 align:start position:0% for uh yeah I mean operational verification<00:59:53.640> I<00:59:54.240> I<00:59:54.359> think<00:59:54.599> we<00:59:54.839> are<00:59:54.960> we<00:59:55.319> already 00:59:55.430 --> 00:59:55.440 align:start position:0% verification I I think we are we already 00:59:55.440 --> 00:59:58.309 align:start position:0% verification I I think we are we already are<00:59:55.680> right<00:59:55.920> I<00:59:56.160> mean<00:59:56.339> we<00:59:56.940> we<00:59:57.180> have<00:59:57.420> uh<00:59:58.020> someone 00:59:58.309 --> 00:59:58.319 align:start position:0% are right I mean we we have uh someone 00:59:58.319 --> 01:00:01.010 align:start position:0% are right I mean we we have uh someone on<00:59:58.740> on<00:59:58.980> at<00:59:59.520> o1<00:59:59.880> Labs<01:00:00.240> which<01:00:00.359> is<01:00:00.480> like<01:00:00.660> the<01:00:00.839> the 01:00:01.010 --> 01:00:01.020 align:start position:0% on on at o1 Labs which is like the the 01:00:01.020 --> 01:00:03.530 align:start position:0% on on at o1 Labs which is like the the team<01:00:01.319> that<01:00:01.619> incubated<01:00:02.099> Mina<01:00:02.819> um<01:00:02.880> is<01:00:03.180> is 01:00:03.530 --> 01:00:03.540 align:start position:0% team that incubated Mina um is is 01:00:03.540 --> 01:00:06.230 align:start position:0% team that incubated Mina um is is looking<01:00:04.079> into<01:00:04.440> getting<01:00:05.220> Cairo<01:00:05.760> to<01:00:05.940> work<01:00:06.059> with 01:00:06.230 --> 01:00:06.240 align:start position:0% looking into getting Cairo to work with 01:00:06.240 --> 01:00:08.210 align:start position:0% looking into getting Cairo to work with with<01:00:06.420> kimchi<01:00:06.900> yeah<01:00:07.319> and<01:00:07.619> there<01:00:07.740> is<01:00:07.920> even<01:00:08.040> one 01:00:08.210 --> 01:00:08.220 align:start position:0% with kimchi yeah and there is even one 01:00:08.220 --> 01:00:09.530 align:start position:0% with kimchi yeah and there is even one in<01:00:08.339> the<01:00:08.460> room<01:00:08.579> who<01:00:08.760> actually<01:00:08.940> took<01:00:09.180> her<01:00:09.359> work 01:00:09.530 --> 01:00:09.540 align:start position:0% in the room who actually took her work 01:00:09.540 --> 01:00:12.170 align:start position:0% in the room who actually took her work and<01:00:09.900> made<01:00:10.079> it<01:00:10.260> into<01:00:10.380> work<01:00:10.680> with<01:00:10.859> Winterfell 01:00:12.170 --> 01:00:12.180 align:start position:0% and made it into work with Winterfell 01:00:12.180 --> 01:00:14.030 align:start position:0% and made it into work with Winterfell so<01:00:12.599> you<01:00:12.780> can<01:00:12.900> look<01:00:13.020> at<01:00:13.140> the<01:00:13.319> guy<01:00:13.440> in<01:00:13.680> a<01:00:13.859> very 01:00:14.030 --> 01:00:14.040 align:start position:0% so you can look at the guy in a very 01:00:14.040 --> 01:00:17.030 align:start position:0% so you can look at the guy in a very nice<01:00:14.220> blue<01:00:14.400> shirt<01:00:14.579> over<01:00:14.760> there<01:00:15.000> Max 01:00:17.030 --> 01:00:17.040 align:start position:0% nice blue shirt over there Max 01:00:17.040 --> 01:00:19.490 align:start position:0% nice blue shirt over there Max so<01:00:17.280> yeah<01:00:17.460> next<01:00:17.760> has<01:00:18.119> a<01:00:18.359> practical<01:00:18.900> Cairo<01:00:19.380> a 01:00:19.490 --> 01:00:19.500 align:start position:0% so yeah next has a practical Cairo a 01:00:19.500 --> 01:00:22.549 align:start position:0% so yeah next has a practical Cairo a very<01:00:19.680> very<01:00:20.099> fire<01:00:20.339> and<01:00:20.700> prover<01:00:21.299> uh<01:00:21.780> in 01:00:22.549 --> 01:00:22.559 align:start position:0% very very fire and prover uh in 01:00:22.559 --> 01:00:23.930 align:start position:0% very very fire and prover uh in Winterfell<01:00:23.040> today 01:00:23.930 --> 01:00:23.940 align:start position:0% Winterfell today 01:00:23.940 --> 01:00:26.210 align:start position:0% Winterfell today um I<01:00:24.119> mean<01:00:24.299> to<01:00:24.599> be<01:00:24.720> honest<01:00:24.900> it's<01:00:25.260> actually<01:00:25.500> go 01:00:26.210 --> 01:00:26.220 align:start position:0% um I mean to be honest it's actually go 01:00:26.220 --> 01:00:27.410 align:start position:0% um I mean to be honest it's actually go back<01:00:26.460> to<01:00:26.579> the<01:00:26.700> point<01:00:26.819> question<01:00:27.180> about 01:00:27.410 --> 01:00:27.420 align:start position:0% back to the point question about 01:00:27.420 --> 01:00:29.150 align:start position:0% back to the point question about simplifying<01:00:28.020> stuff 01:00:29.150 --> 01:00:29.160 align:start position:0% simplifying stuff 01:00:29.160 --> 01:00:32.210 align:start position:0% simplifying stuff um why<01:00:29.819> we<01:00:30.599> have<01:00:30.720> no<01:00:30.900> l2s<01:00:31.440> we<01:00:31.619> have<01:00:31.680> L2<01:00:32.040> that 01:00:32.210 --> 01:00:32.220 align:start position:0% um why we have no l2s we have L2 that 01:00:32.220 --> 01:00:33.710 align:start position:0% um why we have no l2s we have L2 that can<01:00:32.339> do<01:00:32.520> stuff 01:00:33.710 --> 01:00:33.720 align:start position:0% can do stuff 01:00:33.720 --> 01:00:36.289 align:start position:0% can do stuff um<01:00:33.780> let's<01:00:34.440> use<01:00:34.680> their<01:00:34.920> their<01:00:35.220> advantage<01:00:36.119> to 01:00:36.289 --> 01:00:36.299 align:start position:0% um let's use their their advantage to 01:00:36.299 --> 01:00:38.809 align:start position:0% um let's use their their advantage to bridge<01:00:37.079> where<01:00:37.380> we<01:00:37.500> could<01:00:37.619> do<01:00:37.740> the<01:00:37.859> B4<01:00:38.160> and<01:00:38.640> so 01:00:38.809 --> 01:00:38.819 align:start position:0% bridge where we could do the B4 and so 01:00:38.819 --> 01:00:40.789 align:start position:0% bridge where we could do the B4 and so like<01:00:39.180> you<01:00:39.299> know<01:00:39.420> an<01:00:39.540> example<01:00:39.839> uh<01:00:40.380> there<01:00:40.559> is<01:00:40.680> a 01:00:40.789 --> 01:00:40.799 align:start position:0% like you know an example uh there is a 01:00:40.799 --> 01:00:42.170 align:start position:0% like you know an example uh there is a team<01:00:40.920> actually<01:00:41.160> maybe<01:00:41.520> like<01:00:41.819> maybe<01:00:42.000> in<01:00:42.119> the 01:00:42.170 --> 01:00:42.180 align:start position:0% team actually maybe like maybe in the 01:00:42.180 --> 01:00:44.150 align:start position:0% team actually maybe like maybe in the room<01:00:42.359> actually<01:00:42.480> over<01:00:42.839> there<01:00:43.020> uh<01:00:43.500> snapshot<01:00:43.920> X 01:00:44.150 --> 01:00:44.160 align:start position:0% room actually over there uh snapshot X 01:00:44.160 --> 01:00:47.150 align:start position:0% room actually over there uh snapshot X is<01:00:44.700> working<01:00:44.880> right<01:00:45.180> now<01:00:45.299> to<01:00:45.540> do<01:00:45.799> N1<01:00:46.799> voting 01:00:47.150 --> 01:00:47.160 align:start position:0% is working right now to do N1 voting 01:00:47.160 --> 01:00:49.549 align:start position:0% is working right now to do N1 voting using<01:00:47.400> L2<01:00:47.880> to<01:00:48.299> make<01:00:48.420> them<01:00:48.599> cheap<01:00:48.839> and<01:00:49.440> that's 01:00:49.549 --> 01:00:49.559 align:start position:0% using L2 to make them cheap and that's 01:00:49.559 --> 01:00:50.510 align:start position:0% using L2 to make them cheap and that's something<01:00:49.740> you<01:00:49.920> couldn't<01:00:50.040> do<01:00:50.220> before<01:00:50.280> so 01:00:50.510 --> 01:00:50.520 align:start position:0% something you couldn't do before so 01:00:50.520 --> 01:00:52.730 align:start position:0% something you couldn't do before so that's<01:00:50.760> this<01:00:50.940> kind<01:00:51.119> of<01:00:51.240> thing<01:00:51.420> that<01:00:52.200> we<01:00:52.559> can<01:00:52.619> do 01:00:52.730 --> 01:00:52.740 align:start position:0% that's this kind of thing that we can do 01:00:52.740 --> 01:00:54.049 align:start position:0% that's this kind of thing that we can do with<01:00:52.859> l2s<01:00:53.400> now<01:00:53.460> that<01:00:53.579> we<01:00:53.700> couldn't<01:00:53.760> do<01:00:53.940> and 01:00:54.049 --> 01:00:54.059 align:start position:0% with l2s now that we couldn't do and 01:00:54.059 --> 01:00:55.549 align:start position:0% with l2s now that we couldn't do and then<01:00:54.180> one<01:00:54.299> we<01:00:54.540> don't<01:00:54.660> have<01:00:54.839> to<01:00:55.079> change<01:00:55.380> that 01:00:55.549 --> 01:00:55.559 align:start position:0% then one we don't have to change that 01:00:55.559 --> 01:00:59.510 align:start position:0% then one we don't have to change that one<01:00:55.799> for<01:00:55.920> that<01:00:56.099> so<01:00:56.579> simplify<01:00:57.059> please 01:00:59.510 --> 01:00:59.520 align:start position:0% 01:00:59.520 --> 01:01:02.640 align:start position:0% cool<01:01:00.240> thank<01:01:00.599> you<01:01:00.780> all<01:01:00.960> panelists 01:01:02.640 --> 01:01:02.650 align:start position:0% cool thank you all panelists 01:01:02.650 --> 01:01:07.880 align:start position:0% cool thank you all panelists [Applause]