WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:10.709 align:start position:0% [Music] 00:00:10.709 --> 00:00:10.719 align:start position:0% [Music] 00:00:10.719 --> 00:00:14.990 align:start position:0% [Music] hi<00:00:11.320> um<00:00:12.200> yes<00:00:12.400> so<00:00:12.679> I'm<00:00:12.880> Pier<00:00:13.679> working<00:00:13.960> at<00:00:14.120> PSC<00:00:14.839> and 00:00:14.990 --> 00:00:15.000 align:start position:0% hi um yes so I'm Pier working at PSC and 00:00:15.000 --> 00:00:17.630 align:start position:0% hi um yes so I'm Pier working at PSC and this<00:00:15.120> is<00:00:15.200> a<00:00:15.360> presentation<00:00:16.000> done<00:00:16.160> GLE<00:00:16.600> with<00:00:17.320> ar 00:00:17.630 --> 00:00:17.640 align:start position:0% this is a presentation done GLE with ar 00:00:17.640 --> 00:00:19.349 align:start position:0% this is a presentation done GLE with ar now<00:00:17.800> who's<00:00:17.960> working<00:00:18.160> at<00:00:18.279> zerx<00:00:18.680> Park<00:00:19.000> so<00:00:19.160> we<00:00:19.240> are 00:00:19.349 --> 00:00:19.359 align:start position:0% now who's working at zerx Park so we are 00:00:19.359 --> 00:00:22.230 align:start position:0% now who's working at zerx Park so we are going<00:00:19.560> to<00:00:19.720> walk<00:00:19.920> you<00:00:20.439> through<00:00:21.439> uh<00:00:21.560> the<00:00:21.720> library 00:00:22.230 --> 00:00:22.240 align:start position:0% going to walk you through uh the library 00:00:22.240 --> 00:00:24.750 align:start position:0% going to walk you through uh the library that<00:00:22.560> uh<00:00:22.680> we<00:00:22.800> have<00:00:22.920> been<00:00:23.119> working<00:00:23.439> on<00:00:24.000> with 00:00:24.750 --> 00:00:24.760 align:start position:0% that uh we have been working on with 00:00:24.760 --> 00:00:28.429 align:start position:0% that uh we have been working on with winda<00:00:25.480> as<00:00:25.640> well<00:00:26.160> and<00:00:26.560> Carlos<00:00:27.000> over<00:00:27.240> the<00:00:27.400> past 00:00:28.429 --> 00:00:28.439 align:start position:0% winda as well and Carlos over the past 00:00:28.439 --> 00:00:31.269 align:start position:0% winda as well and Carlos over the past year<00:00:29.439> so<00:00:29.759> let's<00:00:30.000> let<00:00:30.119> me<00:00:30.320> first<00:00:30.679> introduce<00:00:31.119> you 00:00:31.269 --> 00:00:31.279 align:start position:0% year so let's let me first introduce you 00:00:31.279 --> 00:00:34.310 align:start position:0% year so let's let me first introduce you a<00:00:31.400> bit<00:00:31.599> to<00:00:31.800> the<00:00:32.239> concept<00:00:32.680> of<00:00:33.079> IVC<00:00:33.600> which<00:00:33.760> means 00:00:34.310 --> 00:00:34.320 align:start position:0% a bit to the concept of IVC which means 00:00:34.320 --> 00:00:36.510 align:start position:0% a bit to the concept of IVC which means incrementally<00:00:35.000> verifiable 00:00:36.510 --> 00:00:36.520 align:start position:0% incrementally verifiable 00:00:36.520 --> 00:00:40.430 align:start position:0% incrementally verifiable computation<00:00:37.520> so<00:00:38.280> um<00:00:38.960> the<00:00:39.440> main<00:00:39.760> entry<00:00:40.160> point 00:00:40.430 --> 00:00:40.440 align:start position:0% computation so um the main entry point 00:00:40.440 --> 00:00:43.029 align:start position:0% computation so um the main entry point to<00:00:41.000> understanding<00:00:41.680> what<00:00:42.079> is<00:00:42.399> incrementally 00:00:43.029 --> 00:00:43.039 align:start position:0% to understanding what is incrementally 00:00:43.039 --> 00:00:46.630 align:start position:0% to understanding what is incrementally verifiable<00:00:43.840> computations<00:00:44.840> is<00:00:45.120> that<00:00:45.800> um<00:00:46.440> those 00:00:46.630 --> 00:00:46.640 align:start position:0% verifiable computations is that um those 00:00:46.640 --> 00:00:48.189 align:start position:0% verifiable computations is that um those are<00:00:47.079> kind<00:00:47.239> of<00:00:47.399> computations<00:00:47.879> that<00:00:48.000> are 00:00:48.189 --> 00:00:48.199 align:start position:0% are kind of computations that are 00:00:48.199 --> 00:00:51.549 align:start position:0% are kind of computations that are repetitive<00:00:49.039> so<00:00:50.039> um<00:00:50.600> for<00:00:50.760> instance<00:00:51.120> you<00:00:51.239> see 00:00:51.549 --> 00:00:51.559 align:start position:0% repetitive so um for instance you see 00:00:51.559 --> 00:00:55.110 align:start position:0% repetitive so um for instance you see this<00:00:51.760> little<00:00:52.079> math<00:00:52.879> formula<00:00:53.480> states<00:00:54.039> that<00:00:54.879> you 00:00:55.110 --> 00:00:55.120 align:start position:0% this little math formula states that you 00:00:55.120 --> 00:00:58.189 align:start position:0% this little math formula states that you can<00:00:55.320> obtain<00:00:55.680> the<00:00:55.840> result<00:00:56.280> SN<00:00:57.280> when<00:00:57.440> you<00:00:57.640> apply 00:00:58.189 --> 00:00:58.199 align:start position:0% can obtain the result SN when you apply 00:00:58.199 --> 00:01:02.310 align:start position:0% can obtain the result SN when you apply a<00:00:58.399> function<00:00:58.840> n<00:00:59.160> times<00:00:59.519> on<00:01:00.160> initial<00:01:00.519> state<00:01:01.320> zero 00:01:02.310 --> 00:01:02.320 align:start position:0% a function n times on initial state zero 00:01:02.320 --> 00:01:03.830 align:start position:0% a function n times on initial state zero so<00:01:02.640> to<00:01:02.800> give<00:01:02.920> you<00:01:03.039> some<00:01:03.239> more<00:01:03.480> concrete 00:01:03.830 --> 00:01:03.840 align:start position:0% so to give you some more concrete 00:01:03.840 --> 00:01:06.590 align:start position:0% so to give you some more concrete example<00:01:04.280> you<00:01:04.400> can<00:01:04.600> think<00:01:04.760> of<00:01:04.920> it<00:01:05.200> as<00:01:06.200> a<00:01:06.320> machine 00:01:06.590 --> 00:01:06.600 align:start position:0% example you can think of it as a machine 00:01:06.600 --> 00:01:08.870 align:start position:0% example you can think of it as a machine learning<00:01:06.920> model<00:01:07.520> which<00:01:08.119> always<00:01:08.439> does<00:01:08.759> the 00:01:08.870 --> 00:01:08.880 align:start position:0% learning model which always does the 00:01:08.880 --> 00:01:12.550 align:start position:0% learning model which always does the same<00:01:09.400> inferences<00:01:10.400> uh<00:01:10.759> on<00:01:11.759> uh<00:01:11.920> some<00:01:12.240> different 00:01:12.550 --> 00:01:12.560 align:start position:0% same inferences uh on uh some different 00:01:12.560 --> 00:01:14.910 align:start position:0% same inferences uh on uh some different data<00:01:12.880> points<00:01:13.600> or<00:01:13.799> maybe<00:01:14.200> some<00:01:14.520> virtual 00:01:14.910 --> 00:01:14.920 align:start position:0% data points or maybe some virtual 00:01:14.920 --> 00:01:17.670 align:start position:0% data points or maybe some virtual machine<00:01:15.479> with<00:01:15.600> a<00:01:15.759> fixed<00:01:16.400> set<00:01:16.640> of<00:01:16.840> op<00:01:17.159> codes 00:01:17.670 --> 00:01:17.680 align:start position:0% machine with a fixed set of op codes 00:01:17.680 --> 00:01:20.310 align:start position:0% machine with a fixed set of op codes which<00:01:18.080> which<00:01:18.280> does<00:01:19.159> some<00:01:19.560> repetitive 00:01:20.310 --> 00:01:20.320 align:start position:0% which which does some repetitive 00:01:20.320 --> 00:01:23.510 align:start position:0% which which does some repetitive computations<00:01:21.320> uh<00:01:21.439> or<00:01:21.640> a<00:01:21.759> rollup<00:01:22.759> which<00:01:23.079> always 00:01:23.510 --> 00:01:23.520 align:start position:0% computations uh or a rollup which always 00:01:23.520 --> 00:01:25.630 align:start position:0% computations uh or a rollup which always batch<00:01:23.960> verify<00:01:24.479> signatures<00:01:25.040> again<00:01:25.240> and<00:01:25.439> again 00:01:25.630 --> 00:01:25.640 align:start position:0% batch verify signatures again and again 00:01:25.640 --> 00:01:27.469 align:start position:0% batch verify signatures again and again and<00:01:25.840> again<00:01:26.479> and<00:01:26.600> even<00:01:26.840> the<00:01:26.960> blockchain 00:01:27.469 --> 00:01:27.479 align:start position:0% and again and even the blockchain 00:01:27.479 --> 00:01:30.230 align:start position:0% and again and even the blockchain consensus<00:01:28.479> U<00:01:29.040> where<00:01:29.479> the<00:01:29.640> same<00:01:29.960> same 00:01:30.230 --> 00:01:30.240 align:start position:0% consensus U where the same same 00:01:30.240 --> 00:01:33.109 align:start position:0% consensus U where the same same consensus<00:01:30.720> algorithm<00:01:31.560> is<00:01:31.799> apply 00:01:33.109 --> 00:01:33.119 align:start position:0% consensus algorithm is apply 00:01:33.119 --> 00:01:35.789 align:start position:0% consensus algorithm is apply um<00:01:34.119> again<00:01:34.320> and 00:01:35.789 --> 00:01:35.799 align:start position:0% um again and 00:01:35.799 --> 00:01:39.870 align:start position:0% um again and again<00:01:36.799> so<00:01:37.320> what<00:01:37.439> are<00:01:37.640> the<00:01:37.920> benefits<00:01:38.920> of<00:01:39.360> IVC 00:01:39.870 --> 00:01:39.880 align:start position:0% again so what are the benefits of IVC 00:01:39.880 --> 00:01:44.350 align:start position:0% again so what are the benefits of IVC schemes<00:01:40.720> that<00:01:40.960> use<00:01:41.720> uh<00:01:42.280> folding<00:01:43.280> so<00:01:44.119> uh<00:01:44.240> this 00:01:44.350 --> 00:01:44.360 align:start position:0% schemes that use uh folding so uh this 00:01:44.360 --> 00:01:46.630 align:start position:0% schemes that use uh folding so uh this is<00:01:44.479> where<00:01:44.640> the<00:01:44.759> folding<00:01:45.159> schemes<00:01:45.719> thing<00:01:46.399> comes 00:01:46.630 --> 00:01:46.640 align:start position:0% is where the folding schemes thing comes 00:01:46.640 --> 00:01:49.270 align:start position:0% is where the folding schemes thing comes in<00:01:47.399> uh<00:01:47.560> so<00:01:48.040> folding<00:01:48.399> SCS<00:01:48.680> are<00:01:48.799> used<00:01:49.000> to 00:01:49.270 --> 00:01:49.280 align:start position:0% in uh so folding SCS are used to 00:01:49.280 --> 00:01:51.429 align:start position:0% in uh so folding SCS are used to basically<00:01:49.880> realize<00:01:50.880> incrementally 00:01:51.429 --> 00:01:51.439 align:start position:0% basically realize incrementally 00:01:51.439 --> 00:01:54.109 align:start position:0% basically realize incrementally verifiable<00:01:52.200> computation<00:01:53.200> and<00:01:53.360> you<00:01:53.479> can<00:01:53.640> see 00:01:54.109 --> 00:01:54.119 align:start position:0% verifiable computation and you can see 00:01:54.119 --> 00:01:57.789 align:start position:0% verifiable computation and you can see on<00:01:54.360> this<00:01:54.640> diagram<00:01:55.640> that<00:01:55.880> the<00:01:56.079> idea<00:01:56.759> is<00:01:57.039> that<00:01:57.439> at 00:01:57.789 --> 00:01:57.799 align:start position:0% on this diagram that the idea is that at 00:01:57.799 --> 00:02:00.749 align:start position:0% on this diagram that the idea is that at every<00:01:58.200> step<00:01:58.640> of<00:01:58.799> the<00:01:59.000> function<00:01:59.640> you<00:01:59.960> will<00:02:00.159> get 00:02:00.749 --> 00:02:00.759 align:start position:0% every step of the function you will get 00:02:00.759 --> 00:02:05.389 align:start position:0% every step of the function you will get a<00:02:01.000> public<00:02:01.439> input<00:02:02.000> so<00:02:02.320> the<00:02:02.560> Z<00:02:02.960> little<00:02:03.280> Z<00:02:04.399> and 00:02:05.389 --> 00:02:05.399 align:start position:0% a public input so the Z little Z and 00:02:05.399 --> 00:02:10.109 align:start position:0% a public input so the Z little Z and sorry<00:02:06.360> and<00:02:07.079> um<00:02:07.799> uh<00:02:08.119> witness<00:02:08.800> so<00:02:09.200> w<00:02:09.679> the<00:02:09.800> little 00:02:10.109 --> 00:02:10.119 align:start position:0% sorry and um uh witness so w the little 00:02:10.119 --> 00:02:13.510 align:start position:0% sorry and um uh witness so w the little W<00:02:10.640> thing<00:02:11.640> and<00:02:11.920> at<00:02:12.200> every<00:02:12.560> time<00:02:13.280> the 00:02:13.510 --> 00:02:13.520 align:start position:0% W thing and at every time the 00:02:13.520 --> 00:02:17.430 align:start position:0% W thing and at every time the computation<00:02:14.440> is<00:02:15.120> uh<00:02:15.280> being<00:02:16.040> uh<00:02:16.239> done<00:02:17.239> uh<00:02:17.360> you 00:02:17.430 --> 00:02:17.440 align:start position:0% computation is uh being uh done uh you 00:02:17.440 --> 00:02:19.910 align:start position:0% computation is uh being uh done uh you will<00:02:17.599> have<00:02:17.760> a<00:02:17.879> new<00:02:18.160> public<00:02:18.440> States<00:02:18.879> Z1<00:02:19.680> and 00:02:19.910 --> 00:02:19.920 align:start position:0% will have a new public States Z1 and 00:02:19.920 --> 00:02:22.070 align:start position:0% will have a new public States Z1 and maybe<00:02:20.280> if<00:02:20.400> you<00:02:20.519> want<00:02:20.680> to<00:02:21.000> redo<00:02:21.519> another<00:02:21.879> step 00:02:22.070 --> 00:02:22.080 align:start position:0% maybe if you want to redo another step 00:02:22.080 --> 00:02:23.430 align:start position:0% maybe if you want to redo another step of<00:02:22.200> the<00:02:22.319> computation<00:02:22.760> you<00:02:22.840> will<00:02:23.000> have<00:02:23.120> a<00:02:23.280> new 00:02:23.430 --> 00:02:23.440 align:start position:0% of the computation you will have a new 00:02:23.440 --> 00:02:26.589 align:start position:0% of the computation you will have a new witness<00:02:24.360> W1<00:02:25.360> so<00:02:25.640> what<00:02:25.800> you<00:02:25.920> can<00:02:26.120> see<00:02:26.360> and 00:02:26.589 --> 00:02:26.599 align:start position:0% witness W1 so what you can see and 00:02:26.599 --> 00:02:28.830 align:start position:0% witness W1 so what you can see and that's<00:02:26.920> interesting<00:02:27.400> is<00:02:27.599> that<00:02:27.959> the<00:02:28.319> F 00:02:28.830 --> 00:02:28.840 align:start position:0% that's interesting is that the F 00:02:28.840 --> 00:02:31.270 align:start position:0% that's interesting is that the F function<00:02:29.440> is<00:02:29.560> a<00:02:29.879> lied<00:02:30.239> independently<00:02:31.040> every 00:02:31.270 --> 00:02:31.280 align:start position:0% function is a lied independently every 00:02:31.280 --> 00:02:34.830 align:start position:0% function is a lied independently every time<00:02:32.160> you<00:02:32.280> do<00:02:32.440> not<00:02:32.800> have<00:02:33.319> like<00:02:33.680> a<00:02:33.840> big<00:02:34.120> circuit 00:02:34.830 --> 00:02:34.840 align:start position:0% time you do not have like a big circuit 00:02:34.840 --> 00:02:37.509 align:start position:0% time you do not have like a big circuit where<00:02:35.120> you<00:02:35.319> do<00:02:35.680> some<00:02:35.920> kind<00:02:36.080> of<00:02:36.239> loop<00:02:37.239> and<00:02:37.400> you 00:02:37.509 --> 00:02:37.519 align:start position:0% where you do some kind of loop and you 00:02:37.519 --> 00:02:42.630 align:start position:0% where you do some kind of loop and you say<00:02:38.000> from<00:02:38.760> uh<00:02:39.280> IAL<00:02:39.879> 0<00:02:40.319> to<00:02:40.879> IAL<00:02:41.480> n<00:02:41.920> apply<00:02:42.280> the<00:02:42.400> F 00:02:42.630 --> 00:02:42.640 align:start position:0% say from uh IAL 0 to IAL n apply the F 00:02:42.640 --> 00:02:45.190 align:start position:0% say from uh IAL 0 to IAL n apply the F function<00:02:43.120> no<00:02:43.400> that's<00:02:43.560> not<00:02:43.800> how<00:02:43.959> it<00:02:44.080> works<00:02:44.879> here 00:02:45.190 --> 00:02:45.200 align:start position:0% function no that's not how it works here 00:02:45.200 --> 00:02:46.790 align:start position:0% function no that's not how it works here the<00:02:45.360> F<00:02:45.599> function<00:02:46.000> is<00:02:46.120> really<00:02:46.400> applied 00:02:46.790 --> 00:02:46.800 align:start position:0% the F function is really applied 00:02:46.800 --> 00:02:50.509 align:start position:0% the F function is really applied independently<00:02:47.599> every<00:02:47.879> time<00:02:48.720> so<00:02:49.360> you<00:02:49.720> get<00:02:50.280> a 00:02:50.509 --> 00:02:50.519 align:start position:0% independently every time so you get a 00:02:50.519 --> 00:02:53.430 align:start position:0% independently every time so you get a prover<00:02:51.080> that<00:02:52.040> uh<00:02:52.239> whose<00:02:52.480> memory<00:02:52.840> is<00:02:53.040> basically 00:02:53.430 --> 00:02:53.440 align:start position:0% prover that uh whose memory is basically 00:02:53.440 --> 00:02:56.430 align:start position:0% prover that uh whose memory is basically dependent<00:02:53.879> on<00:02:54.599> the<00:02:54.959> size<00:02:55.239> of<00:02:55.480> the<00:02:55.959> function 00:02:56.430 --> 00:02:56.440 align:start position:0% dependent on the size of the function 00:02:56.440 --> 00:02:58.270 align:start position:0% dependent on the size of the function that<00:02:56.560> you<00:02:56.640> are<00:02:56.840> applying<00:02:57.360> not<00:02:57.560> on<00:02:57.720> the<00:02:57.920> number 00:02:58.270 --> 00:02:58.280 align:start position:0% that you are applying not on the number 00:02:58.280 --> 00:02:59.910 align:start position:0% that you are applying not on the number of<00:02:58.560> time<00:02:58.920> that<00:02:59.000> you<00:02:59.120> are<00:02:59.239> applying<00:02:59.560> that<00:02:59.680> the 00:02:59.910 --> 00:02:59.920 align:start position:0% of time that you are applying that the 00:02:59.920 --> 00:03:03.910 align:start position:0% of time that you are applying that the function<00:03:00.400> so<00:03:00.680> that<00:03:00.879> makes<00:03:01.360> things<00:03:01.840> very 00:03:03.910 --> 00:03:03.920 align:start position:0% function so that makes things very 00:03:03.920 --> 00:03:07.470 align:start position:0% function so that makes things very interesting<00:03:04.920> so<00:03:05.799> uh<00:03:05.959> you<00:03:06.159> can<00:03:06.720> use<00:03:07.080> folding 00:03:07.470 --> 00:03:07.480 align:start position:0% interesting so uh you can use folding 00:03:07.480 --> 00:03:09.910 align:start position:0% interesting so uh you can use folding schemes<00:03:07.920> for<00:03:08.159> recursion<00:03:09.159> this<00:03:09.319> is<00:03:09.480> some<00:03:09.720> form 00:03:09.910 --> 00:03:09.920 align:start position:0% schemes for recursion this is some form 00:03:09.920 --> 00:03:12.390 align:start position:0% schemes for recursion this is some form of<00:03:10.080> recursion<00:03:10.560> that<00:03:10.720> we<00:03:10.840> have<00:03:10.959> seen<00:03:11.799> because 00:03:12.390 --> 00:03:12.400 align:start position:0% of recursion that we have seen because 00:03:12.400 --> 00:03:14.309 align:start position:0% of recursion that we have seen because um<00:03:12.799> we<00:03:12.920> are<00:03:13.120> just<00:03:13.400> inputting<00:03:13.840> the<00:03:13.959> previous 00:03:14.309 --> 00:03:14.319 align:start position:0% um we are just inputting the previous 00:03:14.319 --> 00:03:17.630 align:start position:0% um we are just inputting the previous state<00:03:14.599> into<00:03:14.840> the<00:03:14.959> next<00:03:15.519> St<00:03:16.519> and<00:03:17.040> uh<00:03:17.120> folding 00:03:17.630 --> 00:03:17.640 align:start position:0% state into the next St and uh folding 00:03:17.640 --> 00:03:20.110 align:start position:0% state into the next St and uh folding schemes<00:03:18.640> um<00:03:18.959> a<00:03:19.040> folding<00:03:19.360> scheme<00:03:19.640> is<00:03:19.720> a<00:03:19.840> coin 00:03:20.110 --> 00:03:20.120 align:start position:0% schemes um a folding scheme is a coin 00:03:20.120 --> 00:03:21.990 align:start position:0% schemes um a folding scheme is a coin that<00:03:20.319> has<00:03:20.519> been<00:03:21.200> is<00:03:21.319> a<00:03:21.440> term<00:03:21.640> that<00:03:21.760> has<00:03:21.879> been 00:03:21.990 --> 00:03:22.000 align:start position:0% that has been is a term that has been 00:03:22.000 --> 00:03:23.550 align:start position:0% that has been is a term that has been coined<00:03:22.280> in<00:03:22.360> the<00:03:22.440> Nova<00:03:22.760> paper<00:03:23.080> so<00:03:23.319> it's 00:03:23.550 --> 00:03:23.560 align:start position:0% coined in the Nova paper so it's 00:03:23.560 --> 00:03:25.830 align:start position:0% coined in the Nova paper so it's something<00:03:24.040> different<00:03:24.560> from<00:03:25.360> what<00:03:25.480> you<00:03:25.640> can 00:03:25.830 --> 00:03:25.840 align:start position:0% something different from what you can 00:03:25.840 --> 00:03:29.309 align:start position:0% something different from what you can see<00:03:26.360> in<00:03:26.799> some<00:03:27.480> um<00:03:27.920> in<00:03:28.200> some<00:03:28.400> stack<00:03:28.760> protocols 00:03:29.309 --> 00:03:29.319 align:start position:0% see in some um in some stack protocols 00:03:29.319 --> 00:03:32.229 align:start position:0% see in some um in some stack protocols it's<00:03:29.920> here<00:03:30.840> what<00:03:30.959> we<00:03:31.080> mean<00:03:31.280> by<00:03:31.439> folding<00:03:32.040> is 00:03:32.229 --> 00:03:32.239 align:start position:0% it's here what we mean by folding is 00:03:32.239 --> 00:03:35.350 align:start position:0% it's here what we mean by folding is really<00:03:32.640> just<00:03:33.519> basically<00:03:34.080> taking<00:03:34.920> random 00:03:35.350 --> 00:03:35.360 align:start position:0% really just basically taking random 00:03:35.360 --> 00:03:39.110 align:start position:0% really just basically taking random linear<00:03:35.799> combinations<00:03:36.680> of<00:03:37.120> uh<00:03:37.760> Witnesses<00:03:38.760> um 00:03:39.110 --> 00:03:39.120 align:start position:0% linear combinations of uh Witnesses um 00:03:39.120 --> 00:03:41.229 align:start position:0% linear combinations of uh Witnesses um and<00:03:39.360> the<00:03:39.640> main<00:03:39.959> intuition<00:03:40.519> is<00:03:40.680> that<00:03:40.879> you<00:03:41.040> can 00:03:41.229 --> 00:03:41.239 align:start position:0% and the main intuition is that you can 00:03:41.239 --> 00:03:45.229 align:start position:0% and the main intuition is that you can have<00:03:41.360> a<00:03:41.480> folding<00:03:42.040> scheme<00:03:43.040> uh<00:03:43.280> when<00:03:44.000> um<00:03:44.400> you<00:03:44.560> are 00:03:45.229 --> 00:03:45.239 align:start position:0% have a folding scheme uh when um you are 00:03:45.239 --> 00:03:47.429 align:start position:0% have a folding scheme uh when um you are uh<00:03:45.400> taking<00:03:46.319> this<00:03:46.519> kind<00:03:46.760> of<00:03:46.959> combination 00:03:47.429 --> 00:03:47.439 align:start position:0% uh taking this kind of combination 00:03:47.439 --> 00:03:49.869 align:start position:0% uh taking this kind of combination between<00:03:47.720> Witnesses<00:03:48.319> because<00:03:48.959> you<00:03:49.080> can<00:03:49.319> show 00:03:49.869 --> 00:03:49.879 align:start position:0% between Witnesses because you can show 00:03:49.879 --> 00:03:52.750 align:start position:0% between Witnesses because you can show that<00:03:50.239> if<00:03:50.400> you<00:03:50.760> know<00:03:51.239> two<00:03:51.599> satisfying 00:03:52.750 --> 00:03:52.760 align:start position:0% that if you know two satisfying 00:03:52.760 --> 00:03:54.869 align:start position:0% that if you know two satisfying Witnesses<00:03:53.760> then<00:03:54.000> if<00:03:54.079> you<00:03:54.239> take<00:03:54.400> the<00:03:54.519> linear 00:03:54.869 --> 00:03:54.879 align:start position:0% Witnesses then if you take the linear 00:03:54.879 --> 00:03:57.470 align:start position:0% Witnesses then if you take the linear combination<00:03:55.760> of<00:03:55.959> those<00:03:56.319> then<00:03:56.439> you<00:03:56.560> can<00:03:57.040> obtain 00:03:57.470 --> 00:03:57.480 align:start position:0% combination of those then you can obtain 00:03:57.480 --> 00:04:02.550 align:start position:0% combination of those then you can obtain another<00:03:58.159> satisfying<00:03:59.120> uh<00:03:59.239> Witness 00:04:02.550 --> 00:04:02.560 align:start position:0% 00:04:02.560 --> 00:04:05.509 align:start position:0% um<00:04:02.920> also<00:04:03.840> um<00:04:04.079> the<00:04:04.280> main<00:04:04.599> workflow<00:04:05.280> when<00:04:05.439> you 00:04:05.509 --> 00:04:05.519 align:start position:0% um also um the main workflow when you 00:04:05.519 --> 00:04:08.550 align:start position:0% um also um the main workflow when you are<00:04:05.680> using<00:04:06.280> um<00:04:06.480> folding<00:04:06.879> schemes<00:04:07.200> to<00:04:07.319> do<00:04:07.560> IVC 00:04:08.550 --> 00:04:08.560 align:start position:0% are using um folding schemes to do IVC 00:04:08.560 --> 00:04:11.429 align:start position:0% are using um folding schemes to do IVC is<00:04:08.799> that<00:04:09.200> you<00:04:09.360> will<00:04:09.560> do<00:04:09.879> your<00:04:10.480> uh<00:04:10.640> IVC 00:04:11.429 --> 00:04:11.439 align:start position:0% is that you will do your uh IVC 00:04:11.439 --> 00:04:13.910 align:start position:0% is that you will do your uh IVC computation<00:04:12.079> maybe<00:04:12.319> for<00:04:12.599> end<00:04:12.879> steps<00:04:13.599> you<00:04:13.720> will 00:04:13.910 --> 00:04:13.920 align:start position:0% computation maybe for end steps you will 00:04:13.920 --> 00:04:16.990 align:start position:0% computation maybe for end steps you will get<00:04:14.079> an<00:04:14.280> IVC<00:04:14.799> proof<00:04:15.400> and<00:04:15.640> this<00:04:16.000> proof<00:04:16.560> is<00:04:16.759> not 00:04:16.990 --> 00:04:17.000 align:start position:0% get an IVC proof and this proof is not 00:04:17.000 --> 00:04:21.789 align:start position:0% get an IVC proof and this proof is not suent<00:04:17.759> so<00:04:18.040> you<00:04:18.199> will<00:04:18.440> want<00:04:19.160> to<00:04:19.919> um<00:04:20.720> um<00:04:21.519> you<00:04:21.639> will 00:04:21.789 --> 00:04:21.799 align:start position:0% suent so you will want to um um you will 00:04:21.799 --> 00:04:23.990 align:start position:0% suent so you will want to um um you will want<00:04:21.959> to<00:04:22.120> compress<00:04:22.520> it<00:04:22.800> basically<00:04:23.520> using 00:04:23.990 --> 00:04:24.000 align:start position:0% want to compress it basically using 00:04:24.000 --> 00:04:26.830 align:start position:0% want to compress it basically using something<00:04:24.440> that<00:04:24.800> is<00:04:25.000> called<00:04:25.360> a<00:04:25.600> decider<00:04:26.600> and 00:04:26.830 --> 00:04:26.840 align:start position:0% something that is called a decider and 00:04:26.840 --> 00:04:30.550 align:start position:0% something that is called a decider and it's<00:04:27.520> basically<00:04:28.000> a<00:04:28.160> znar<00:04:28.840> proof<00:04:29.240> so<00:04:29.479> we<00:04:29.880> just 00:04:30.550 --> 00:04:30.560 align:start position:0% it's basically a znar proof so we just 00:04:30.560 --> 00:04:35.270 align:start position:0% it's basically a znar proof so we just snarfy<00:04:31.560> the<00:04:31.840> IVC<00:04:32.720> proof<00:04:33.720> and<00:04:33.960> obtain<00:04:34.479> a<00:04:35.080> more 00:04:35.270 --> 00:04:35.280 align:start position:0% snarfy the IVC proof and obtain a more 00:04:35.280 --> 00:04:37.430 align:start position:0% snarfy the IVC proof and obtain a more sucin<00:04:35.800> proof<00:04:36.160> that<00:04:36.320> you<00:04:36.479> can<00:04:36.680> then<00:04:36.880> verify 00:04:37.430 --> 00:04:37.440 align:start position:0% sucin proof that you can then verify 00:04:37.440 --> 00:04:41.390 align:start position:0% sucin proof that you can then verify wherever<00:04:37.880> you<00:04:38.000> want<00:04:38.680> such<00:04:38.919> as 00:04:41.390 --> 00:04:41.400 align:start position:0% wherever you want such as 00:04:41.400 --> 00:04:44.629 align:start position:0% wherever you want such as onchain<00:04:42.400> all<00:04:42.560> right<00:04:42.880> so<00:04:43.160> let's<00:04:43.639> just<00:04:44.240> take<00:04:44.440> a 00:04:44.629 --> 00:04:44.639 align:start position:0% onchain all right so let's just take a 00:04:44.639 --> 00:04:46.749 align:start position:0% onchain all right so let's just take a step<00:04:44.919> back<00:04:45.120> and<00:04:45.280> try<00:04:45.479> to<00:04:45.680> think<00:04:45.880> a<00:04:46.000> bit<00:04:46.240> about 00:04:46.749 --> 00:04:46.759 align:start position:0% step back and try to think a bit about 00:04:46.759 --> 00:04:49.909 align:start position:0% step back and try to think a bit about what<00:04:47.160> folding<00:04:47.800> schemes<00:04:48.800> how<00:04:49.000> folding<00:04:49.360> schemes 00:04:49.909 --> 00:04:49.919 align:start position:0% what folding schemes how folding schemes 00:04:49.919 --> 00:04:53.510 align:start position:0% what folding schemes how folding schemes look<00:04:50.240> like<00:04:51.240> so<00:04:52.000> there<00:04:52.160> is<00:04:52.360> now<00:04:53.039> what<00:04:53.160> I<00:04:53.280> call 00:04:53.510 --> 00:04:53.520 align:start position:0% look like so there is now what I call 00:04:53.520 --> 00:04:56.310 align:start position:0% look like so there is now what I call the<00:04:53.680> folding<00:04:54.080> schemes<00:04:54.759> Zoo<00:04:55.440> so<00:04:55.720> there<00:04:55.840> are<00:04:56.120> a 00:04:56.310 --> 00:04:56.320 align:start position:0% the folding schemes Zoo so there are a 00:04:56.320 --> 00:04:58.749 align:start position:0% the folding schemes Zoo so there are a lot<00:04:56.560> of<00:04:56.759> different<00:04:57.320> kind<00:04:57.520> of<00:04:57.919> folding<00:04:58.280> schemes 00:04:58.749 --> 00:04:58.759 align:start position:0% lot of different kind of folding schemes 00:04:58.759 --> 00:05:00.629 align:start position:0% lot of different kind of folding schemes because<00:04:59.360> you<00:04:59.680> you<00:04:59.759> have<00:04:59.919> a<00:05:00.039> lot<00:05:00.160> of<00:05:00.360> different 00:05:00.629 --> 00:05:00.639 align:start position:0% because you you have a lot of different 00:05:00.639 --> 00:05:02.629 align:start position:0% because you you have a lot of different kinds<00:05:00.880> of<00:05:01.120> aromatizations<00:05:02.120> you<00:05:02.240> have<00:05:02.400> a<00:05:02.479> lot 00:05:02.629 --> 00:05:02.639 align:start position:0% kinds of aromatizations you have a lot 00:05:02.639 --> 00:05:04.510 align:start position:0% kinds of aromatizations you have a lot of<00:05:02.800> different<00:05:03.080> kinds<00:05:03.280> of<00:05:03.440> use<00:05:03.759> cases<00:05:04.080> some<00:05:04.240> use 00:05:04.510 --> 00:05:04.520 align:start position:0% of different kinds of use cases some use 00:05:04.520 --> 00:05:07.469 align:start position:0% of different kinds of use cases some use case<00:05:04.680> use<00:05:04.919> lookups<00:05:05.600> other<00:05:05.960> DS<00:05:06.440> some<00:05:07.039> have<00:05:07.360> a 00:05:07.469 --> 00:05:07.479 align:start position:0% case use lookups other DS some have a 00:05:07.479 --> 00:05:10.469 align:start position:0% case use lookups other DS some have a uniform<00:05:08.360> computation<00:05:09.080> some<00:05:09.280> have<00:05:09.479> nonuniform 00:05:10.469 --> 00:05:10.479 align:start position:0% uniform computation some have nonuniform 00:05:10.479 --> 00:05:13.430 align:start position:0% uniform computation some have nonuniform computations<00:05:11.479> so<00:05:11.880> you<00:05:12.520> we<00:05:12.680> end<00:05:12.880> up<00:05:13.120> with 00:05:13.430 --> 00:05:13.440 align:start position:0% computations so you we end up with 00:05:13.440 --> 00:05:15.270 align:start position:0% computations so you we end up with really<00:05:13.960> a<00:05:14.160> bunch<00:05:14.400> of<00:05:14.560> different<00:05:14.840> folding 00:05:15.270 --> 00:05:15.280 align:start position:0% really a bunch of different folding 00:05:15.280 --> 00:05:19.550 align:start position:0% really a bunch of different folding schemes<00:05:16.280> some<00:05:16.720> are<00:05:17.400> used<00:05:17.680> for<00:05:17.880> plish<00:05:18.560> circuits 00:05:19.550 --> 00:05:19.560 align:start position:0% schemes some are used for plish circuits 00:05:19.560 --> 00:05:21.629 align:start position:0% schemes some are used for plish circuits other<00:05:20.039> use<00:05:20.360> some<00:05:20.639> specific<00:05:21.120> kind<00:05:21.400> of 00:05:21.629 --> 00:05:21.639 align:start position:0% other use some specific kind of 00:05:21.639 --> 00:05:23.469 align:start position:0% other use some specific kind of arithmetization 00:05:23.469 --> 00:05:23.479 align:start position:0% arithmetization 00:05:23.479 --> 00:05:28.189 align:start position:0% arithmetization um<00:05:24.479> uh<00:05:24.720> thing<00:05:25.400> that<00:05:25.600> are<00:05:26.560> adapted<00:05:26.960> to<00:05:27.319> folding 00:05:28.189 --> 00:05:28.199 align:start position:0% um uh thing that are adapted to folding 00:05:28.199 --> 00:05:30.830 align:start position:0% um uh thing that are adapted to folding some<00:05:28.479> do<00:05:28.720> many<00:05:29.039> to<00:05:29.280> one<00:05:29.680> folding<00:05:30.039> so<00:05:30.240> not<00:05:30.560> two 00:05:30.830 --> 00:05:30.840 align:start position:0% some do many to one folding so not two 00:05:30.840 --> 00:05:33.749 align:start position:0% some do many to one folding so not two to<00:05:31.039> one<00:05:31.400> but<00:05:31.560> many<00:05:31.840> to<00:05:32.000> one<00:05:32.199> folding<00:05:32.759> meaning 00:05:33.749 --> 00:05:33.759 align:start position:0% to one but many to one folding meaning 00:05:33.759 --> 00:05:35.510 align:start position:0% to one but many to one folding meaning uh<00:05:33.960> instead<00:05:34.280> of<00:05:34.400> folding<00:05:34.800> two<00:05:34.960> witnesses 00:05:35.510 --> 00:05:35.520 align:start position:0% uh instead of folding two witnesses 00:05:35.520 --> 00:05:37.510 align:start position:0% uh instead of folding two witnesses together<00:05:35.759> you<00:05:35.880> can<00:05:36.039> fold<00:05:36.440> n<00:05:36.680> of<00:05:36.880> them<00:05:37.240> together 00:05:37.510 --> 00:05:37.520 align:start position:0% together you can fold n of them together 00:05:37.520 --> 00:05:39.830 align:start position:0% together you can fold n of them together so<00:05:37.759> it's<00:05:38.000> a<00:05:38.160> very<00:05:38.440> efficient<00:05:38.800> form<00:05:39.000> of<00:05:39.120> folding 00:05:39.830 --> 00:05:39.840 align:start position:0% so it's a very efficient form of folding 00:05:39.840 --> 00:05:41.790 align:start position:0% so it's a very efficient form of folding you<00:05:39.960> have<00:05:40.160> also<00:05:40.479> ltis<00:05:40.960> bit<00:05:41.240> folding<00:05:41.600> more 00:05:41.790 --> 00:05:41.800 align:start position:0% you have also ltis bit folding more 00:05:41.800 --> 00:05:43.550 align:start position:0% you have also ltis bit folding more recently<00:05:42.440> so<00:05:42.639> that's<00:05:42.840> interesting<00:05:43.240> for<00:05:43.400> the 00:05:43.550 --> 00:05:43.560 align:start position:0% recently so that's interesting for the 00:05:43.560 --> 00:05:45.830 align:start position:0% recently so that's interesting for the postquantum<00:05:43.960> uh<00:05:44.759> security<00:05:45.199> properties<00:05:45.600> of 00:05:45.830 --> 00:05:45.840 align:start position:0% postquantum uh security properties of 00:05:45.840 --> 00:05:48.790 align:start position:0% postquantum uh security properties of those<00:05:46.199> kind<00:05:46.360> of<00:05:46.759> things<00:05:47.759> and<00:05:47.919> so<00:05:48.360> we<00:05:48.560> really 00:05:48.790 --> 00:05:48.800 align:start position:0% those kind of things and so we really 00:05:48.800 --> 00:05:52.150 align:start position:0% those kind of things and so we really end<00:05:49.000> up<00:05:49.199> with<00:05:49.400> some<00:05:49.600> kind<00:05:49.759> of<00:05:49.919> zoo<00:05:50.919> um<00:05:51.919> with 00:05:52.150 --> 00:05:52.160 align:start position:0% end up with some kind of zoo um with 00:05:52.160 --> 00:05:54.469 align:start position:0% end up with some kind of zoo um with many<00:05:52.680> different<00:05:52.960> folding 00:05:54.469 --> 00:05:54.479 align:start position:0% many different folding 00:05:54.479 --> 00:05:57.550 align:start position:0% many different folding schemes<00:05:55.479> and<00:05:56.360> even<00:05:56.560> in<00:05:56.680> terms<00:05:56.919> of<00:05:57.080> research 00:05:57.550 --> 00:05:57.560 align:start position:0% schemes and even in terms of research 00:05:57.560 --> 00:06:00.430 align:start position:0% schemes and even in terms of research it's<00:05:57.680> a<00:05:57.880> very<00:05:58.160> active<00:05:58.520> area<00:05:58.840> of<00:05:59.000> research<00:05:59.880> so 00:06:00.430 --> 00:06:00.440 align:start position:0% it's a very active area of research so 00:06:00.440 --> 00:06:03.469 align:start position:0% it's a very active area of research so for<00:06:00.639> instance<00:06:01.120> just<00:06:01.400> in<00:06:01.680> April<00:06:02.360> 2023<00:06:03.360> there 00:06:03.469 --> 00:06:03.479 align:start position:0% for instance just in April 2023 there 00:06:03.479 --> 00:06:05.990 align:start position:0% for instance just in April 2023 there was<00:06:03.759> like<00:06:04.400> four<00:06:04.759> different<00:06:05.120> kind<00:06:05.319> of<00:06:05.639> folding 00:06:05.990 --> 00:06:06.000 align:start position:0% was like four different kind of folding 00:06:06.000 --> 00:06:08.469 align:start position:0% was like four different kind of folding schemes<00:06:06.400> proposal<00:06:06.960> and<00:06:07.199> way<00:06:07.440> to<00:06:07.680> do<00:06:07.880> VMS<00:06:08.360> with 00:06:08.469 --> 00:06:08.479 align:start position:0% schemes proposal and way to do VMS with 00:06:08.479 --> 00:06:11.150 align:start position:0% schemes proposal and way to do VMS with folding<00:06:08.840> schemes<00:06:09.160> so<00:06:09.360> it's<00:06:09.479> a<00:06:09.639> really<00:06:10.039> active 00:06:11.150 --> 00:06:11.160 align:start position:0% folding schemes so it's a really active 00:06:11.160 --> 00:06:14.830 align:start position:0% folding schemes so it's a really active um<00:06:12.160> area<00:06:12.479> of<00:06:12.720> research<00:06:13.720> um<00:06:14.080> recently<00:06:14.720> there 00:06:14.830 --> 00:06:14.840 align:start position:0% um area of research um recently there 00:06:14.840 --> 00:06:17.390 align:start position:0% um area of research um recently there was<00:06:15.319> some<00:06:16.120> uh<00:06:16.240> zero<00:06:16.560> knowledge<00:06:16.880> layer<00:06:17.280> that 00:06:17.390 --> 00:06:17.400 align:start position:0% was some uh zero knowledge layer that 00:06:17.400 --> 00:06:20.830 align:start position:0% was some uh zero knowledge layer that was<00:06:17.639> proposed<00:06:18.199> for<00:06:18.880> IVC<00:06:19.360> proofs<00:06:20.240> so<00:06:20.479> you<00:06:20.639> can 00:06:20.830 --> 00:06:20.840 align:start position:0% was proposed for IVC proofs so you can 00:06:20.840 --> 00:06:23.790 align:start position:0% was proposed for IVC proofs so you can generate<00:06:21.199> your<00:06:21.400> IVC<00:06:21.800> proof<00:06:22.120> on<00:06:22.240> a<00:06:22.440> client<00:06:23.199> and 00:06:23.790 --> 00:06:23.800 align:start position:0% generate your IVC proof on a client and 00:06:23.800 --> 00:06:26.589 align:start position:0% generate your IVC proof on a client and then<00:06:24.000> make<00:06:24.199> it<00:06:24.400> ZK<00:06:25.000> it's<00:06:25.400> very<00:06:25.639> efficient<00:06:26.440> and 00:06:26.589 --> 00:06:26.599 align:start position:0% then make it ZK it's very efficient and 00:06:26.599 --> 00:06:28.270 align:start position:0% then make it ZK it's very efficient and then<00:06:26.759> for<00:06:26.919> instance<00:06:27.240> send<00:06:27.520> that<00:06:27.680> to<00:06:27.800> a<00:06:27.919> server 00:06:28.270 --> 00:06:28.280 align:start position:0% then for instance send that to a server 00:06:28.280 --> 00:06:30.309 align:start position:0% then for instance send that to a server to<00:06:28.919> have<00:06:29.080> the<00:06:29.199> server<00:06:29.639> compress<00:06:30.000> the<00:06:30.080> proof 00:06:30.309 --> 00:06:30.319 align:start position:0% to have the server compress the proof 00:06:30.319 --> 00:06:32.430 align:start position:0% to have the server compress the proof and<00:06:30.440> send<00:06:30.680> the<00:06:30.800> proof<00:06:31.000> on<00:06:31.160> chain<00:06:31.520> so<00:06:32.120> those 00:06:32.430 --> 00:06:32.440 align:start position:0% and send the proof on chain so those 00:06:32.440 --> 00:06:35.510 align:start position:0% and send the proof on chain so those have<00:06:32.840> some<00:06:33.479> really<00:06:33.720> interesting<00:06:34.440> um<00:06:35.199> zero 00:06:35.510 --> 00:06:35.520 align:start position:0% have some really interesting um zero 00:06:35.520 --> 00:06:38.629 align:start position:0% have some really interesting um zero knowledge<00:06:36.360> properties<00:06:37.360> um<00:06:37.880> you<00:06:38.080> we<00:06:38.240> also<00:06:38.440> have 00:06:38.629 --> 00:06:38.639 align:start position:0% knowledge properties um you we also have 00:06:38.639 --> 00:06:40.629 align:start position:0% knowledge properties um you we also have latis<00:06:39.000> fold<00:06:39.360> which<00:06:39.479> is<00:06:39.840> postquantum<00:06:40.240> ready 00:06:40.629 --> 00:06:40.639 align:start position:0% latis fold which is postquantum ready 00:06:40.639 --> 00:06:45.070 align:start position:0% latis fold which is postquantum ready and<00:06:40.919> is<00:06:41.120> a<00:06:41.479> pretty<00:06:42.039> efficient<00:06:43.039> form<00:06:43.400> of<00:06:43.880> um<00:06:44.280> of 00:06:45.070 --> 00:06:45.080 align:start position:0% and is a pretty efficient form of um of 00:06:45.080 --> 00:06:48.230 align:start position:0% and is a pretty efficient form of um of folding<00:06:46.080> and<00:06:46.520> um<00:06:46.800> yeah<00:06:46.960> so<00:06:47.560> there<00:06:47.680> is<00:06:47.919> really<00:06:48.120> a 00:06:48.230 --> 00:06:48.240 align:start position:0% folding and um yeah so there is really a 00:06:48.240 --> 00:06:50.749 align:start position:0% folding and um yeah so there is really a bunch<00:06:48.440> of<00:06:48.599> stuff<00:06:48.840> to<00:06:49.120> to<00:06:49.319> to<00:06:49.479> talk<00:06:49.680> about<00:06:49.919> today 00:06:50.749 --> 00:06:50.759 align:start position:0% bunch of stuff to to to talk about today 00:06:50.759 --> 00:06:53.629 align:start position:0% bunch of stuff to to to talk about today uh<00:06:50.960> about<00:06:51.199> what's<00:06:51.400> going<00:06:51.639> on<00:06:52.000> in<00:06:52.800> in<00:06:53.160> the<00:06:53.440> this 00:06:53.629 --> 00:06:53.639 align:start position:0% uh about what's going on in in the this 00:06:53.639 --> 00:06:54.670 align:start position:0% uh about what's going on in in the this area<00:06:53.880> of 00:06:54.670 --> 00:06:54.680 align:start position:0% area of 00:06:54.680 --> 00:06:57.309 align:start position:0% area of research<00:06:55.680> but<00:06:55.919> let's<00:06:56.160> talk<00:06:56.319> a<00:06:56.440> bit<00:06:56.639> also<00:06:56.919> about 00:06:57.309 --> 00:06:57.319 align:start position:0% research but let's talk a bit also about 00:06:57.319 --> 00:06:59.270 align:start position:0% research but let's talk a bit also about applications<00:06:58.199> because<00:06:58.520> I<00:06:58.680> I<00:06:58.800> think<00:06:59.000> that<00:06:59.120> some 00:06:59.270 --> 00:06:59.280 align:start position:0% applications because I I think that some 00:06:59.280 --> 00:07:01.749 align:start position:0% applications because I I think that some of<00:06:59.360> you<00:06:59.680> are<00:06:59.879> interested<00:07:00.759> to<00:07:00.960> know<00:07:01.440> what's 00:07:01.749 --> 00:07:01.759 align:start position:0% of you are interested to know what's 00:07:01.759 --> 00:07:04.270 align:start position:0% of you are interested to know what's what's<00:07:01.960> happening<00:07:02.440> there<00:07:03.440> um<00:07:03.840> so<00:07:04.080> for 00:07:04.270 --> 00:07:04.280 align:start position:0% what's happening there um so for 00:07:04.280 --> 00:07:07.189 align:start position:0% what's happening there um so for instance<00:07:05.080> um<00:07:05.479> we<00:07:05.639> did<00:07:06.039> one<00:07:06.360> experiment<00:07:07.000> where 00:07:07.189 --> 00:07:07.199 align:start position:0% instance um we did one experiment where 00:07:07.199 --> 00:07:11.230 align:start position:0% instance um we did one experiment where we<00:07:07.440> were<00:07:08.560> um<00:07:09.560> uh<00:07:09.720> building<00:07:10.199> a<00:07:10.360> Bitcoin<00:07:10.720> light 00:07:11.230 --> 00:07:11.240 align:start position:0% we were um uh building a Bitcoin light 00:07:11.240 --> 00:07:14.710 align:start position:0% we were um uh building a Bitcoin light client<00:07:12.240> so<00:07:12.479> the<00:07:12.639> idea<00:07:12.960> was<00:07:13.160> just<00:07:13.360> to<00:07:13.639> prove<00:07:14.560> uh 00:07:14.710 --> 00:07:14.720 align:start position:0% client so the idea was just to prove uh 00:07:14.720 --> 00:07:16.869 align:start position:0% client so the idea was just to prove uh that<00:07:14.919> the<00:07:15.080> current<00:07:15.560> blockage<00:07:16.039> that<00:07:16.199> we<00:07:16.400> have 00:07:16.869 --> 00:07:16.879 align:start position:0% that the current blockage that we have 00:07:16.879 --> 00:07:20.150 align:start position:0% that the current blockage that we have is<00:07:17.560> um<00:07:18.000> has<00:07:18.160> been<00:07:18.319> obtained<00:07:18.680> after<00:07:18.879> end<00:07:19.160> blocks 00:07:20.150 --> 00:07:20.160 align:start position:0% is um has been obtained after end blocks 00:07:20.160 --> 00:07:24.430 align:start position:0% is um has been obtained after end blocks and<00:07:20.360> so<00:07:20.800> we<00:07:21.199> for<00:07:21.400> instance<00:07:21.759> run<00:07:22.440> an<00:07:23.440> uh<00:07:23.960> Nova 00:07:24.430 --> 00:07:24.440 align:start position:0% and so we for instance run an uh Nova 00:07:24.440 --> 00:07:26.589 align:start position:0% and so we for instance run an uh Nova which<00:07:24.560> is<00:07:24.639> a<00:07:24.720> folding<00:07:25.080> scheme<00:07:26.080> uh<00:07:26.160> on<00:07:26.440> the 00:07:26.589 --> 00:07:26.599 align:start position:0% which is a folding scheme uh on the 00:07:26.599 --> 00:07:31.309 align:start position:0% which is a folding scheme uh on the proof<00:07:26.840> of<00:07:27.080> work<00:07:27.919> um<00:07:28.800> uh<00:07:29.000> Bitcoin<00:07:29.960> um<00:07:30.479> algorithm 00:07:31.309 --> 00:07:31.319 align:start position:0% proof of work um uh Bitcoin um algorithm 00:07:31.319 --> 00:07:34.869 align:start position:0% proof of work um uh Bitcoin um algorithm for<00:07:31.879> 100k<00:07:32.400> blocks<00:07:33.400> and<00:07:33.680> in<00:07:33.879> total<00:07:34.240> that<00:07:34.440> costs 00:07:34.869 --> 00:07:34.879 align:start position:0% for 100k blocks and in total that costs 00:07:34.879 --> 00:07:39.350 align:start position:0% for 100k blocks and in total that costs us<00:07:35.599> uh<00:07:35.680> $30<00:07:36.599> to<00:07:36.800> verify<00:07:37.160> an<00:07:37.720> optimism<00:07:38.720> uh<00:07:38.840> for 00:07:39.350 --> 00:07:39.360 align:start position:0% us uh $30 to verify an optimism uh for 00:07:39.360 --> 00:07:41.510 align:start position:0% us uh $30 to verify an optimism uh for running<00:07:39.759> such<00:07:39.960> a<00:07:40.120> huge<00:07:40.680> absolutely<00:07:41.120> huge 00:07:41.510 --> 00:07:41.520 align:start position:0% running such a huge absolutely huge 00:07:41.520 --> 00:07:44.469 align:start position:0% running such a huge absolutely huge computation<00:07:42.039> that<00:07:42.360> we<00:07:42.479> wouldn't<00:07:42.879> do<00:07:43.440> using 00:07:44.469 --> 00:07:44.479 align:start position:0% computation that we wouldn't do using 00:07:44.479 --> 00:07:50.350 align:start position:0% computation that we wouldn't do using a<00:07:45.479> traditional<00:07:46.159> ways<00:07:46.599> of<00:07:47.199> um<00:07:47.960> of<00:07:48.479> znar<00:07:49.400> proving 00:07:50.350 --> 00:07:50.360 align:start position:0% a traditional ways of um of znar proving 00:07:50.360 --> 00:07:52.270 align:start position:0% a traditional ways of um of znar proving libraries<00:07:50.919> that<00:07:51.039> we<00:07:51.159> have 00:07:52.270 --> 00:07:52.280 align:start position:0% libraries that we have 00:07:52.280 --> 00:07:55.350 align:start position:0% libraries that we have today<00:07:53.280> we<00:07:53.520> also<00:07:53.720> have<00:07:53.879> Z<00:07:54.080> kvms<00:07:54.560> today<00:07:54.879> that<00:07:55.000> use 00:07:55.350 --> 00:07:55.360 align:start position:0% today we also have Z kvms today that use 00:07:55.360 --> 00:07:57.749 align:start position:0% today we also have Z kvms today that use folding<00:07:56.080> so<00:07:56.280> there<00:07:56.400> is<00:07:56.560> the<00:07:56.720> Nexus<00:07:57.199> team<00:07:57.639> I 00:07:57.749 --> 00:07:57.759 align:start position:0% folding so there is the Nexus team I 00:07:57.759 --> 00:08:01.110 align:start position:0% folding so there is the Nexus team I think<00:07:58.280> that<00:07:58.440> is<00:07:58.960> that<00:07:59.080> is<00:07:59.520> led<00:07:59.759> by<00:08:00.240> Yan<00:08:00.560> gr<00:08:00.960> and 00:08:01.110 --> 00:08:01.120 align:start position:0% think that is that is led by Yan gr and 00:08:01.120 --> 00:08:04.110 align:start position:0% think that is that is led by Yan gr and Daniel<00:08:01.479> Marin<00:08:02.479> uh<00:08:02.639> they<00:08:02.800> use<00:08:03.440> I<00:08:03.639> think 00:08:04.110 --> 00:08:04.120 align:start position:0% Daniel Marin uh they use I think 00:08:04.120 --> 00:08:06.430 align:start position:0% Daniel Marin uh they use I think hypernova<00:08:04.759> for<00:08:04.960> that<00:08:05.800> there<00:08:05.919> is<00:08:06.080> also<00:08:06.319> the 00:08:06.430 --> 00:08:06.440 align:start position:0% hypernova for that there is also the 00:08:06.440 --> 00:08:10.510 align:start position:0% hypernova for that there is also the jolt<00:08:06.879> team<00:08:07.720> um<00:08:08.599> uh<00:08:08.840> they<00:08:09.319> I<00:08:09.599> they<00:08:09.919> published<00:08:10.319> an 00:08:10.510 --> 00:08:10.520 align:start position:0% jolt team um uh they I they published an 00:08:10.520 --> 00:08:12.869 align:start position:0% jolt team um uh they I they published an update<00:08:10.919> actually<00:08:11.199> today<00:08:12.159> uh<00:08:12.360> stating<00:08:12.720> that 00:08:12.869 --> 00:08:12.879 align:start position:0% update actually today uh stating that 00:08:12.879 --> 00:08:14.790 align:start position:0% update actually today uh stating that they<00:08:12.960> were<00:08:13.159> interesting<00:08:14.080> interested<00:08:14.479> into 00:08:14.790 --> 00:08:14.800 align:start position:0% they were interesting interested into 00:08:14.800 --> 00:08:16.670 align:start position:0% they were interesting interested into folding<00:08:15.319> and<00:08:15.520> I<00:08:15.680> think<00:08:15.960> they<00:08:16.080> are<00:08:16.280> interested 00:08:16.670 --> 00:08:16.680 align:start position:0% folding and I think they are interested 00:08:16.680 --> 00:08:18.510 align:start position:0% folding and I think they are interested for<00:08:16.879> it<00:08:17.159> regarding<00:08:17.599> their<00:08:17.800> memory<00:08:18.159> checking 00:08:18.510 --> 00:08:18.520 align:start position:0% for it regarding their memory checking 00:08:18.520 --> 00:08:21.350 align:start position:0% for it regarding their memory checking algorithm<00:08:19.400> for<00:08:19.639> their<00:08:19.840> for<00:08:20.039> their<00:08:20.159> ZK<00:08:20.479> VM 00:08:21.350 --> 00:08:21.360 align:start position:0% algorithm for their for their ZK VM 00:08:21.360 --> 00:08:23.990 align:start position:0% algorithm for their for their ZK VM there<00:08:21.479> is<00:08:21.680> also<00:08:22.120> ZK<00:08:22.560> machine<00:08:22.840> learning<00:08:23.759> uh 00:08:23.990 --> 00:08:24.000 align:start position:0% there is also ZK machine learning uh 00:08:24.000 --> 00:08:28.550 align:start position:0% there is also ZK machine learning uh someone<00:08:25.000> Beed<00:08:25.639> into<00:08:26.360> Nova<00:08:27.360> um<00:08:28.039> a<00:08:28.199> billion 00:08:28.550 --> 00:08:28.560 align:start position:0% someone Beed into Nova um a billion 00:08:28.560 --> 00:08:31.469 align:start position:0% someone Beed into Nova um a billion parameter<00:08:29.080> I<00:08:29.199> think<00:08:29.840> or<00:08:30.639> yes<00:08:30.840> something<00:08:31.360> a 00:08:31.469 --> 00:08:31.479 align:start position:0% parameter I think or yes something a 00:08:31.479 --> 00:08:35.829 align:start position:0% parameter I think or yes something a billion<00:08:32.080> parameter<00:08:33.080> at<00:08:33.599> least<00:08:34.599> there<00:08:34.760> was<00:08:35.760> it 00:08:35.829 --> 00:08:35.839 align:start position:0% billion parameter at least there was it 00:08:35.839 --> 00:08:36.829 align:start position:0% billion parameter at least there was it was<00:08:36.000> a 00:08:36.829 --> 00:08:36.839 align:start position:0% was a 00:08:36.839 --> 00:08:41.469 align:start position:0% was a 512<00:08:38.159> CNN<00:08:39.159> um<00:08:39.800> Network 00:08:41.469 --> 00:08:41.479 align:start position:0% 512 CNN um Network 00:08:41.479 --> 00:08:44.790 align:start position:0% 512 CNN um Network um<00:08:42.479> that<00:08:42.760> they<00:08:42.959> bed<00:08:43.320> into<00:08:43.839> Nova<00:08:44.279> and<00:08:44.399> for<00:08:44.600> which 00:08:44.790 --> 00:08:44.800 align:start position:0% um that they bed into Nova and for which 00:08:44.800 --> 00:08:46.430 align:start position:0% um that they bed into Nova and for which they<00:08:44.959> generated<00:08:45.360> a<00:08:45.519> proof<00:08:45.920> and<00:08:46.040> I<00:08:46.120> think<00:08:46.279> it 00:08:46.430 --> 00:08:46.440 align:start position:0% they generated a proof and I think it 00:08:46.440 --> 00:08:47.829 align:start position:0% they generated a proof and I think it amounted<00:08:46.800> to<00:08:46.959> something<00:08:47.200> like<00:08:47.320> a<00:08:47.480> billion 00:08:47.829 --> 00:08:47.839 align:start position:0% amounted to something like a billion 00:08:47.839 --> 00:08:51.310 align:start position:0% amounted to something like a billion parameters<00:08:49.240> model<00:08:50.240> uh<00:08:50.360> so<00:08:50.519> you<00:08:50.640> have<00:08:50.760> also<00:08:51.000> ZK 00:08:51.310 --> 00:08:51.320 align:start position:0% parameters model uh so you have also ZK 00:08:51.320 --> 00:08:53.310 align:start position:0% parameters model uh so you have also ZK machine<00:08:51.560> learning<00:08:52.399> um<00:08:52.680> yes<00:08:52.920> so<00:08:53.080> there<00:08:53.200> is 00:08:53.310 --> 00:08:53.320 align:start position:0% machine learning um yes so there is 00:08:53.320 --> 00:08:54.630 align:start position:0% machine learning um yes so there is really<00:08:53.560> a<00:08:53.680> bunch<00:08:53.880> of<00:08:54.040> projects<00:08:54.399> that<00:08:54.519> have 00:08:54.630 --> 00:08:54.640 align:start position:0% really a bunch of projects that have 00:08:54.640 --> 00:08:56.750 align:start position:0% really a bunch of projects that have been<00:08:54.959> um<00:08:55.200> building<00:08:55.519> on<00:08:55.720> folding<00:08:56.040> schemes 00:08:56.750 --> 00:08:56.760 align:start position:0% been um building on folding schemes 00:08:56.760 --> 00:09:00.110 align:start position:0% been um building on folding schemes lately<00:08:57.760> so<00:08:58.480> yeah<00:08:59.000> for<00:08:59.240> that<00:08:59.600> we<00:08:59.720> have<00:08:59.839> built 00:09:00.110 --> 00:09:00.120 align:start position:0% lately so yeah for that we have built 00:09:00.120 --> 00:09:02.829 align:start position:0% lately so yeah for that we have built Sono<00:09:01.079> and<00:09:01.440> this<00:09:01.560> is<00:09:01.760> what<00:09:02.040> Arno<00:09:02.440> is<00:09:02.519> going<00:09:02.680> to 00:09:02.829 --> 00:09:02.839 align:start position:0% Sono and this is what Arno is going to 00:09:02.839 --> 00:09:03.990 align:start position:0% Sono and this is what Arno is going to talk 00:09:03.990 --> 00:09:04.000 align:start position:0% talk 00:09:04.000 --> 00:09:09.509 align:start position:0% talk about<00:09:05.000> hi<00:09:05.560> so<00:09:06.160> yeah<00:09:06.440> so<00:09:06.839> on<00:09:07.320> you<00:09:08.240> thanks<00:09:09.079> uh<00:09:09.240> on 00:09:09.509 --> 00:09:09.519 align:start position:0% about hi so yeah so on you thanks uh on 00:09:09.519 --> 00:09:10.949 align:start position:0% about hi so yeah so on you thanks uh on you<00:09:09.600> are<00:09:09.760> interested<00:09:10.120> into<00:09:10.480> like<00:09:10.680> uh<00:09:10.800> being 00:09:10.949 --> 00:09:10.959 align:start position:0% you are interested into like uh being 00:09:10.959 --> 00:09:13.069 align:start position:0% you are interested into like uh being able<00:09:11.200> to<00:09:11.600> use<00:09:11.839> folding<00:09:12.200> schemes<00:09:12.519> for<00:09:12.680> your 00:09:13.069 --> 00:09:13.079 align:start position:0% able to use folding schemes for your 00:09:13.079 --> 00:09:16.630 align:start position:0% able to use folding schemes for your like<00:09:13.399> uh<00:09:14.160> recursive<00:09:14.839> circuits<00:09:15.839> um<00:09:16.079> so<00:09:16.320> we<00:09:16.440> have 00:09:16.630 --> 00:09:16.640 align:start position:0% like uh recursive circuits um so we have 00:09:16.640 --> 00:09:18.389 align:start position:0% like uh recursive circuits um so we have this<00:09:16.920> uh<00:09:17.079> Library<00:09:17.519> it's<00:09:17.680> a<00:09:17.880> like<00:09:18.000> a<00:09:18.160> very 00:09:18.389 --> 00:09:18.399 align:start position:0% this uh Library it's a like a very 00:09:18.399 --> 00:09:21.389 align:start position:0% this uh Library it's a like a very experimental<00:09:19.240> um<00:09:19.560> thing<00:09:20.560> um<00:09:20.839> intended<00:09:21.240> for 00:09:21.389 --> 00:09:21.399 align:start position:0% experimental um thing um intended for 00:09:21.399 --> 00:09:23.389 align:start position:0% experimental um thing um intended for research<00:09:21.880> but<00:09:22.040> we<00:09:22.160> are<00:09:22.360> starting<00:09:22.680> to<00:09:23.000> like<00:09:23.160> now 00:09:23.389 --> 00:09:23.399 align:start position:0% research but we are starting to like now 00:09:23.399 --> 00:09:25.829 align:start position:0% research but we are starting to like now polish<00:09:23.760> things<00:09:24.600> uh<00:09:24.680> so<00:09:24.839> the<00:09:24.959> idea<00:09:25.240> was<00:09:25.399> to<00:09:25.640> have 00:09:25.829 --> 00:09:25.839 align:start position:0% polish things uh so the idea was to have 00:09:25.839 --> 00:09:28.230 align:start position:0% polish things uh so the idea was to have this<00:09:26.000> model<00:09:26.440> Library<00:09:26.920> where<00:09:27.079> we<00:09:27.200> are<00:09:27.399> able<00:09:27.640> to 00:09:28.230 --> 00:09:28.240 align:start position:0% this model Library where we are able to 00:09:28.240 --> 00:09:29.910 align:start position:0% this model Library where we are able to add<00:09:28.440> and<00:09:28.600> Test<00:09:28.839> new<00:09:28.959> folding<00:09:29.399> schemes<00:09:29.800> uh 00:09:29.910 --> 00:09:29.920 align:start position:0% add and Test new folding schemes uh 00:09:29.920 --> 00:09:31.990 align:start position:0% add and Test new folding schemes uh compare<00:09:30.279> schemes<00:09:30.600> like<00:09:30.720> aples<00:09:31.000> to<00:09:31.160> aples<00:09:31.880> and 00:09:31.990 --> 00:09:32.000 align:start position:0% compare schemes like aples to aples and 00:09:32.000 --> 00:09:33.829 align:start position:0% compare schemes like aples to aples and also<00:09:32.279> that<00:09:32.399> allow<00:09:32.800> researchers<00:09:33.360> to<00:09:33.560> easily 00:09:33.829 --> 00:09:33.839 align:start position:0% also that allow researchers to easily 00:09:33.839 --> 00:09:35.590 align:start position:0% also that allow researchers to easily add<00:09:34.079> their<00:09:34.240> own<00:09:34.440> schemes<00:09:34.959> as<00:09:35.160> happened<00:09:35.480> with 00:09:35.590 --> 00:09:35.600 align:start position:0% add their own schemes as happened with 00:09:35.600 --> 00:09:38.190 align:start position:0% add their own schemes as happened with the<00:09:35.720> MOBA<00:09:36.040> paper<00:09:36.360> by<00:09:36.519> nether<00:09:37.160> uh<00:09:37.279> they<00:09:37.839> publish 00:09:38.190 --> 00:09:38.200 align:start position:0% the MOBA paper by nether uh they publish 00:09:38.200 --> 00:09:40.670 align:start position:0% the MOBA paper by nether uh they publish the<00:09:38.320> paper<00:09:38.720> where<00:09:38.920> they<00:09:39.040> use<00:09:39.279> sonov<00:09:39.720> to<00:09:39.920> test 00:09:40.670 --> 00:09:40.680 align:start position:0% the paper where they use sonov to test 00:09:40.680 --> 00:09:43.630 align:start position:0% the paper where they use sonov to test their<00:09:41.160> their<00:09:41.640> like<00:09:42.040> new<00:09:42.320> design<00:09:43.120> uh<00:09:43.440> which 00:09:43.630 --> 00:09:43.640 align:start position:0% their their like new design uh which 00:09:43.640 --> 00:09:45.990 align:start position:0% their their like new design uh which they<00:09:43.800> implemented<00:09:44.440> in<00:09:44.640> on<00:09:44.800> top<00:09:44.920> of<00:09:45.040> sonov<00:09:45.880> uh 00:09:45.990 --> 00:09:46.000 align:start position:0% they implemented in on top of sonov uh 00:09:46.000 --> 00:09:47.710 align:start position:0% they implemented in on top of sonov uh and<00:09:46.160> now<00:09:46.360> this<00:09:46.519> is<00:09:46.880> this<00:09:47.000> was<00:09:47.120> a<00:09:47.360> request<00:09:47.600> in 00:09:47.710 --> 00:09:47.720 align:start position:0% and now this is this was a request in 00:09:47.720 --> 00:09:50.069 align:start position:0% and now this is this was a request in son<00:09:48.079> so<00:09:48.160> now<00:09:48.279> this<00:09:48.399> is<00:09:48.480> mered<00:09:48.880> so<00:09:49.399> now<00:09:49.760> like 00:09:50.069 --> 00:09:50.079 align:start position:0% son so now this is mered so now like 00:09:50.079 --> 00:09:52.670 align:start position:0% son so now this is mered so now like part<00:09:50.279> of<00:09:50.360> it<00:09:50.519> is<00:09:50.640> in<00:09:50.959> in<00:09:51.200> in<00:09:51.320> the<00:09:51.560> library<00:09:52.440> Al 00:09:52.670 --> 00:09:52.680 align:start position:0% part of it is in in in the library Al 00:09:52.680 --> 00:09:54.590 align:start position:0% part of it is in in in the library Al but<00:09:52.800> also<00:09:53.079> the<00:09:53.160> idea<00:09:53.480> is<00:09:53.600> to<00:09:53.760> make<00:09:53.880> it<00:09:54.000> easy<00:09:54.360> for 00:09:54.590 --> 00:09:54.600 align:start position:0% but also the idea is to make it easy for 00:09:54.600 --> 00:09:56.150 align:start position:0% but also the idea is to make it easy for for<00:09:54.760> deps<00:09:55.000> to<00:09:55.079> use<00:09:55.240> folding<00:09:55.600> like<00:09:55.720> the<00:09:55.800> idea<00:09:56.040> is 00:09:56.150 --> 00:09:56.160 align:start position:0% for deps to use folding like the idea is 00:09:56.160 --> 00:09:58.550 align:start position:0% for deps to use folding like the idea is that<00:09:56.839> uh<00:09:57.000> they<00:09:57.079> should<00:09:57.399> have<00:09:57.680> a<00:09:57.800> minimal<00:09:58.200> code 00:09:58.550 --> 00:09:58.560 align:start position:0% that uh they should have a minimal code 00:09:58.560 --> 00:10:00.310 align:start position:0% that uh they should have a minimal code to<00:09:58.800> to<00:09:58.920> be<00:09:59.000> able<00:09:59.160> to<00:09:59.399> then<00:09:59.519> fold<00:09:59.760> the<00:09:59.839> circuits 00:10:00.310 --> 00:10:00.320 align:start position:0% to to be able to then fold the circuits 00:10:00.320 --> 00:10:02.910 align:start position:0% to to be able to then fold the circuits this<00:10:00.519> idea<00:10:00.800> of<00:10:00.959> plaque<00:10:01.360> and<00:10:01.560> fold<00:10:02.560> and<00:10:02.760> but 00:10:02.910 --> 00:10:02.920 align:start position:0% this idea of plaque and fold and but 00:10:02.920 --> 00:10:05.190 align:start position:0% this idea of plaque and fold and but also<00:10:03.200> allow<00:10:03.920> since<00:10:04.120> we<00:10:04.279> are<00:10:04.440> building<00:10:04.839> this<00:10:05.040> on 00:10:05.190 --> 00:10:05.200 align:start position:0% also allow since we are building this on 00:10:05.200 --> 00:10:08.389 align:start position:0% also allow since we are building this on top<00:10:05.360> of<00:10:05.760> the<00:10:05.880> artworks<00:10:06.560> set<00:10:06.760> of<00:10:07.160> Library<00:10:08.160> um 00:10:08.389 --> 00:10:08.399 align:start position:0% top of the artworks set of Library um 00:10:08.399 --> 00:10:10.550 align:start position:0% top of the artworks set of Library um the<00:10:08.519> IDE<00:10:08.760> is<00:10:09.000> that<00:10:09.200> that<00:10:09.640> um<00:10:10.000> it's<00:10:10.200> easy<00:10:10.440> to 00:10:10.550 --> 00:10:10.560 align:start position:0% the IDE is that that um it's easy to 00:10:10.560 --> 00:10:12.910 align:start position:0% the IDE is that that um it's easy to switch<00:10:11.480> thanks<00:10:11.720> to<00:10:11.839> artworks<00:10:12.440> between 00:10:12.910 --> 00:10:12.920 align:start position:0% switch thanks to artworks between 00:10:12.920 --> 00:10:15.630 align:start position:0% switch thanks to artworks between different<00:10:13.200> curves<00:10:13.640> but<00:10:13.920> then<00:10:14.279> uh<00:10:14.360> in<00:10:14.519> son<00:10:15.440> also 00:10:15.630 --> 00:10:15.640 align:start position:0% different curves but then uh in son also 00:10:15.640 --> 00:10:17.750 align:start position:0% different curves but then uh in son also switching<00:10:16.040> between<00:10:16.399> different<00:10:17.079> uh<00:10:17.200> folding 00:10:17.750 --> 00:10:17.760 align:start position:0% switching between different uh folding 00:10:17.760 --> 00:10:19.949 align:start position:0% switching between different uh folding schemes<00:10:18.760> uh<00:10:18.880> and<00:10:19.040> also<00:10:19.440> we<00:10:19.600> have<00:10:19.720> some 00:10:19.949 --> 00:10:19.959 align:start position:0% schemes uh and also we have some 00:10:19.959 --> 00:10:22.190 align:start position:0% schemes uh and also we have some experimental<00:10:20.680> like<00:10:21.000> ZK<00:10:21.279> circuit<00:10:21.600> language 00:10:22.190 --> 00:10:22.200 align:start position:0% experimental like ZK circuit language 00:10:22.200 --> 00:10:24.949 align:start position:0% experimental like ZK circuit language kind<00:10:22.320> of<00:10:22.480> like<00:10:22.839> um<00:10:23.800> uh<00:10:23.959> interfaces<00:10:24.680> where<00:10:24.839> you 00:10:24.949 --> 00:10:24.959 align:start position:0% kind of like um uh interfaces where you 00:10:24.959 --> 00:10:28.350 align:start position:0% kind of like um uh interfaces where you can<00:10:25.120> use<00:10:25.440> like<00:10:25.760> uh<00:10:26.640> other<00:10:27.240> uh<00:10:27.360> than<00:10:27.560> artworks 00:10:28.350 --> 00:10:28.360 align:start position:0% can use like uh other uh than artworks 00:10:28.360 --> 00:10:30.470 align:start position:0% can use like uh other uh than artworks um<00:10:29.000> um 00:10:30.470 --> 00:10:30.480 align:start position:0% um um 00:10:30.480 --> 00:10:32.230 align:start position:0% um um languages<00:10:31.000> to<00:10:31.240> to<00:10:31.399> define<00:10:31.720> the<00:10:31.839> circuit<00:10:32.160> that 00:10:32.230 --> 00:10:32.240 align:start position:0% languages to to define the circuit that 00:10:32.240 --> 00:10:34.150 align:start position:0% languages to to define the circuit that you<00:10:32.320> want<00:10:32.399> to<00:10:32.480> fold<00:10:33.120> and<00:10:33.279> also<00:10:33.600> like<00:10:33.720> the<00:10:33.839> third 00:10:34.150 --> 00:10:34.160 align:start position:0% you want to fold and also like the third 00:10:34.160 --> 00:10:35.990 align:start position:0% you want to fold and also like the third kind<00:10:34.279> of<00:10:34.440> like<00:10:34.600> pillar<00:10:34.880> of<00:10:35.000> son<00:10:35.480> was<00:10:35.600> to<00:10:35.839> be 00:10:35.990 --> 00:10:36.000 align:start position:0% kind of like pillar of son was to be 00:10:36.000 --> 00:10:38.990 align:start position:0% kind of like pillar of son was to be able<00:10:36.200> to<00:10:36.519> verify<00:10:36.839> on<00:10:37.040> chain<00:10:37.959> um<00:10:38.480> the<00:10:38.680> the<00:10:38.920> the 00:10:38.990 --> 00:10:39.000 align:start position:0% able to verify on chain um the the the 00:10:39.000 --> 00:10:41.110 align:start position:0% able to verify on chain um the the the folding<00:10:39.360> proof<00:10:40.279> because<00:10:40.560> this<00:10:40.680> was<00:10:40.839> something 00:10:41.110 --> 00:10:41.120 align:start position:0% folding proof because this was something 00:10:41.120 --> 00:10:43.030 align:start position:0% folding proof because this was something that<00:10:41.399> uh<00:10:41.560> we<00:10:41.800> we<00:10:41.920> were<00:10:42.079> not<00:10:42.240> able<00:10:42.440> to<00:10:42.560> find<00:10:42.800> in 00:10:43.030 --> 00:10:43.040 align:start position:0% that uh we we were not able to find in 00:10:43.040 --> 00:10:44.550 align:start position:0% that uh we we were not able to find in any<00:10:43.320> any<00:10:43.639> of<00:10:43.800> the<00:10:43.920> other<00:10:44.160> folding 00:10:44.550 --> 00:10:44.560 align:start position:0% any any of the other folding 00:10:44.560 --> 00:10:46.829 align:start position:0% any any of the other folding implementations<00:10:45.560> because<00:10:45.800> of<00:10:46.440> the<00:10:46.560> the 00:10:46.829 --> 00:10:46.839 align:start position:0% implementations because of the the 00:10:46.839 --> 00:10:48.990 align:start position:0% implementations because of the the characteristics<00:10:47.639> so<00:10:47.880> so<00:10:48.120> yeah<00:10:48.720> uh<00:10:48.800> as<00:10:48.920> I 00:10:48.990 --> 00:10:49.000 align:start position:0% characteristics so so yeah uh as I 00:10:49.000 --> 00:10:50.069 align:start position:0% characteristics so so yeah uh as I remarked<00:10:49.360> this<00:10:49.440> is<00:10:49.560> like<00:10:49.680> a<00:10:49.839> very 00:10:50.069 --> 00:10:50.079 align:start position:0% remarked this is like a very 00:10:50.079 --> 00:10:51.949 align:start position:0% remarked this is like a very experimental<00:10:50.560> and<00:10:50.680> research<00:10:51.000> library<00:10:51.639> and 00:10:51.949 --> 00:10:51.959 align:start position:0% experimental and research library and 00:10:51.959 --> 00:10:53.230 align:start position:0% experimental and research library and for<00:10:52.120> the<00:10:52.240> moment<00:10:52.480> it's 00:10:53.230 --> 00:10:53.240 align:start position:0% for the moment it's 00:10:53.240 --> 00:10:54.750 align:start position:0% for the moment it's unoptimized 00:10:54.750 --> 00:10:54.760 align:start position:0% unoptimized 00:10:54.760 --> 00:10:57.230 align:start position:0% unoptimized so<00:10:55.760> yeah<00:10:56.120> so<00:10:56.440> that's<00:10:56.639> the<00:10:56.839> developer 00:10:57.230 --> 00:10:57.240 align:start position:0% so yeah so that's the developer 00:10:57.240 --> 00:10:59.350 align:start position:0% so yeah so that's the developer experience<00:10:57.600> of<00:10:57.680> sonov<00:10:58.639> this<00:10:58.760> is<00:10:58.959> like<00:10:59.120> what 00:10:59.350 --> 00:10:59.360 align:start position:0% experience of sonov this is like what 00:10:59.360 --> 00:11:01.069 align:start position:0% experience of sonov this is like what you<00:10:59.440> already<00:10:59.680> saw<00:11:00.040> um<00:11:00.200> this<00:11:00.320> is<00:11:00.440> like<00:11:00.600> the<00:11:00.800> the 00:11:01.069 --> 00:11:01.079 align:start position:0% you already saw um this is like the the 00:11:01.079 --> 00:11:04.350 align:start position:0% you already saw um this is like the the the<00:11:01.440> idea<00:11:02.040> of<00:11:02.360> of<00:11:02.560> the<00:11:03.440> folding<00:11:03.839> schemes<00:11:04.240> and 00:11:04.350 --> 00:11:04.360 align:start position:0% the idea of of the folding schemes and 00:11:04.360 --> 00:11:07.110 align:start position:0% the idea of of the folding schemes and this<00:11:04.440> is<00:11:04.600> like<00:11:04.760> how<00:11:04.959> this<00:11:05.120> maps<00:11:05.440> to<00:11:05.920> son<00:11:06.920> uh 00:11:07.110 --> 00:11:07.120 align:start position:0% this is like how this maps to son uh 00:11:07.120 --> 00:11:08.990 align:start position:0% this is like how this maps to son uh they<00:11:07.399> it's<00:11:07.560> very<00:11:07.720> simple<00:11:08.040> like<00:11:08.240> the<00:11:08.480> the<00:11:08.839> the 00:11:08.990 --> 00:11:09.000 align:start position:0% they it's very simple like the the the 00:11:09.000 --> 00:11:10.230 align:start position:0% they it's very simple like the the the dev<00:11:09.200> just<00:11:09.320> needs<00:11:09.519> to<00:11:09.600> define<00:11:09.839> the<00:11:09.959> circuit 00:11:10.230 --> 00:11:10.240 align:start position:0% dev just needs to define the circuit 00:11:10.240 --> 00:11:12.430 align:start position:0% dev just needs to define the circuit that<00:11:10.360> wants<00:11:10.560> to<00:11:10.680> be<00:11:10.760> fold<00:11:11.560> uh<00:11:11.959> select<00:11:12.320> which 00:11:12.430 --> 00:11:12.440 align:start position:0% that wants to be fold uh select which 00:11:12.440 --> 00:11:14.870 align:start position:0% that wants to be fold uh select which folding<00:11:12.880> scheme<00:11:13.240> to<00:11:13.360> be<00:11:13.519> used<00:11:14.079> for<00:11:14.240> example 00:11:14.870 --> 00:11:14.880 align:start position:0% folding scheme to be used for example 00:11:14.880 --> 00:11:16.509 align:start position:0% folding scheme to be used for example Nova<00:11:15.399> plus<00:11:15.639> cycle<00:11:15.880> fold<00:11:16.120> but<00:11:16.200> then<00:11:16.320> you<00:11:16.399> can 00:11:16.509 --> 00:11:16.519 align:start position:0% Nova plus cycle fold but then you can 00:11:16.519 --> 00:11:18.870 align:start position:0% Nova plus cycle fold but then you can swap<00:11:17.279> uh<00:11:17.480> and<00:11:17.760> with<00:11:18.000> just<00:11:18.240> changing<00:11:18.600> one<00:11:18.760> line 00:11:18.870 --> 00:11:18.880 align:start position:0% swap uh and with just changing one line 00:11:18.880 --> 00:11:20.829 align:start position:0% swap uh and with just changing one line of<00:11:19.040> code<00:11:19.320> into<00:11:19.560> using<00:11:19.880> hypernova<00:11:20.440> or<00:11:20.600> Proto 00:11:20.829 --> 00:11:20.839 align:start position:0% of code into using hypernova or Proto 00:11:20.839 --> 00:11:22.629 align:start position:0% of code into using hypernova or Proto Galaxy<00:11:21.600> then<00:11:21.720> also<00:11:21.959> setting<00:11:22.279> the<00:11:22.399> final 00:11:22.629 --> 00:11:22.639 align:start position:0% Galaxy then also setting the final 00:11:22.639 --> 00:11:24.590 align:start position:0% Galaxy then also setting the final decider<00:11:23.600> uh<00:11:23.680> that<00:11:23.800> generates<00:11:24.160> this<00:11:24.440> um 00:11:24.590 --> 00:11:24.600 align:start position:0% decider uh that generates this um 00:11:24.600 --> 00:11:28.710 align:start position:0% decider uh that generates this um compressed<00:11:25.519> snar<00:11:25.880> proof<00:11:26.839> um<00:11:27.279> and<00:11:27.880> and<00:11:28.279> then<00:11:28.639> uh 00:11:28.710 --> 00:11:28.720 align:start position:0% compressed snar proof um and and then uh 00:11:28.720 --> 00:11:29.990 align:start position:0% compressed snar proof um and and then uh in<00:11:28.839> the<00:11:28.959> case<00:11:29.320> that<00:11:29.440> you<00:11:29.519> are<00:11:29.639> using<00:11:29.880> the 00:11:29.990 --> 00:11:30.000 align:start position:0% in the case that you are using the 00:11:30.000 --> 00:11:32.550 align:start position:0% in the case that you are using the onchain<00:11:30.720> uh<00:11:30.839> decider<00:11:31.720> uh<00:11:31.800> you<00:11:31.920> can<00:11:32.079> then<00:11:32.360> also 00:11:32.550 --> 00:11:32.560 align:start position:0% onchain uh decider uh you can then also 00:11:32.560 --> 00:11:35.150 align:start position:0% onchain uh decider uh you can then also generate<00:11:32.920> the<00:11:33.040> solidity<00:11:33.920> uh<00:11:34.040> code<00:11:34.600> like<00:11:34.800> the 00:11:35.150 --> 00:11:35.160 align:start position:0% generate the solidity uh code like the 00:11:35.160 --> 00:11:36.990 align:start position:0% generate the solidity uh code like the template<00:11:35.680> that<00:11:35.800> you<00:11:35.880> can<00:11:36.040> then<00:11:36.200> deploy<00:11:36.880> and 00:11:36.990 --> 00:11:37.000 align:start position:0% template that you can then deploy and 00:11:37.000 --> 00:11:38.430 align:start position:0% template that you can then deploy and you<00:11:37.079> can<00:11:37.279> use<00:11:37.480> this<00:11:37.600> to<00:11:37.720> verify<00:11:38.240> the<00:11:38.360> the 00:11:38.430 --> 00:11:38.440 align:start position:0% you can use this to verify the the 00:11:38.440 --> 00:11:40.509 align:start position:0% you can use this to verify the the proofs<00:11:38.720> on 00:11:40.509 --> 00:11:40.519 align:start position:0% proofs on 00:11:40.519 --> 00:11:43.710 align:start position:0% proofs on chain<00:11:41.519> status<00:11:41.880> of<00:11:42.040> the<00:11:42.200> library<00:11:42.800> um<00:11:43.120> so<00:11:43.320> so<00:11:43.480> far 00:11:43.710 --> 00:11:43.720 align:start position:0% chain status of the library um so so far 00:11:43.720 --> 00:11:45.430 align:start position:0% chain status of the library um so so far what<00:11:43.880> we<00:11:44.040> have<00:11:44.440> like<00:11:44.639> uh<00:11:44.760> fully<00:11:45.000> implemented 00:11:45.430 --> 00:11:45.440 align:start position:0% what we have like uh fully implemented 00:11:45.440 --> 00:11:47.910 align:start position:0% what we have like uh fully implemented is<00:11:45.639> like<00:11:46.160> Nova<00:11:46.560> hyper<00:11:46.920> nova<00:11:47.200> and<00:11:47.360> Proto<00:11:47.639> Galaxy 00:11:47.910 --> 00:11:47.920 align:start position:0% is like Nova hyper nova and Proto Galaxy 00:11:47.920 --> 00:11:49.990 align:start position:0% is like Nova hyper nova and Proto Galaxy folding<00:11:48.279> schemes<00:11:48.839> the<00:11:48.959> three<00:11:49.120> of<00:11:49.279> them<00:11:49.600> using 00:11:49.990 --> 00:11:50.000 align:start position:0% folding schemes the three of them using 00:11:50.000 --> 00:11:53.910 align:start position:0% folding schemes the three of them using cycle<00:11:50.320> fold<00:11:51.000> uh<00:11:51.360> techniques<00:11:52.360> uh<00:11:52.560> so<00:11:53.240> um<00:11:53.800> and 00:11:53.910 --> 00:11:53.920 align:start position:0% cycle fold uh techniques uh so um and 00:11:53.920 --> 00:11:55.750 align:start position:0% cycle fold uh techniques uh so um and then<00:11:54.079> also<00:11:54.320> for<00:11:54.600> for<00:11:54.760> Nova<00:11:55.079> we<00:11:55.240> have<00:11:55.480> like<00:11:55.639> the 00:11:55.750 --> 00:11:55.760 align:start position:0% then also for for Nova we have like the 00:11:55.760 --> 00:11:57.790 align:start position:0% then also for for Nova we have like the full<00:11:56.279> solidity<00:11:56.760> verifier<00:11:57.279> there<00:11:57.560> for 00:11:57.790 --> 00:11:57.800 align:start position:0% full solidity verifier there for 00:11:57.800 --> 00:11:59.470 align:start position:0% full solidity verifier there for hypernova<00:11:58.320> Proto<00:11:58.519> Galaxy<00:11:58.920> like<00:11:59.040> we<00:11:59.240> we<00:11:59.320> have 00:11:59.470 --> 00:11:59.480 align:start position:0% hypernova Proto Galaxy like we we have 00:11:59.480 --> 00:12:01.110 align:start position:0% hypernova Proto Galaxy like we we have the<00:11:59.639> the<00:11:59.720> code<00:11:59.959> in<00:12:00.360> that<00:12:00.480> generates<00:12:00.880> the<00:12:01.000> the 00:12:01.110 --> 00:12:01.120 align:start position:0% the the code in that generates the the 00:12:01.120 --> 00:12:02.949 align:start position:0% the the code in that generates the the proofs<00:12:01.399> and<00:12:01.519> so<00:12:01.600> on<00:12:01.839> but<00:12:02.480> uh<00:12:02.600> it's<00:12:02.760> just<00:12:02.880> a 00:12:02.949 --> 00:12:02.959 align:start position:0% proofs and so on but uh it's just a 00:12:02.959 --> 00:12:04.350 align:start position:0% proofs and so on but uh it's just a matter<00:12:03.160> of<00:12:03.279> like<00:12:03.399> putting<00:12:03.639> time<00:12:03.800> to<00:12:03.959> doing<00:12:04.200> the 00:12:04.350 --> 00:12:04.360 align:start position:0% matter of like putting time to doing the 00:12:04.360 --> 00:12:06.670 align:start position:0% matter of like putting time to doing the solity<00:12:04.880> also<00:12:05.600> then<00:12:05.760> also<00:12:06.040> we<00:12:06.200> we<00:12:06.320> started<00:12:06.560> to 00:12:06.670 --> 00:12:06.680 align:start position:0% solity also then also we we started to 00:12:06.680 --> 00:12:08.910 align:start position:0% solity also then also we we started to introduce<00:12:07.079> this<00:12:07.240> MOA<00:12:07.560> an<00:12:07.720> NOA<00:12:08.360> these<00:12:08.480> are<00:12:08.680> just 00:12:08.910 --> 00:12:08.920 align:start position:0% introduce this MOA an NOA these are just 00:12:08.920 --> 00:12:12.350 align:start position:0% introduce this MOA an NOA these are just like<00:12:09.399> variant<00:12:10.120> to<00:12:10.279> the<00:12:10.480> Nova<00:12:11.120> scheme<00:12:12.079> uh<00:12:12.200> so 00:12:12.350 --> 00:12:12.360 align:start position:0% like variant to the Nova scheme uh so 00:12:12.360 --> 00:12:13.949 align:start position:0% like variant to the Nova scheme uh so it's<00:12:12.480> like<00:12:12.720> with<00:12:13.000> some<00:12:13.240> tweaking<00:12:13.639> and<00:12:13.800> some 00:12:13.949 --> 00:12:13.959 align:start position:0% it's like with some tweaking and some 00:12:13.959 --> 00:12:15.590 align:start position:0% it's like with some tweaking and some abstractions<00:12:14.440> we<00:12:14.560> can<00:12:14.720> reuse<00:12:15.040> most<00:12:15.279> of<00:12:15.440> the 00:12:15.590 --> 00:12:15.600 align:start position:0% abstractions we can reuse most of the 00:12:15.600 --> 00:12:17.629 align:start position:0% abstractions we can reuse most of the already<00:12:15.920> existing<00:12:16.240> Nova<00:12:16.560> code<00:12:17.160> that<00:12:17.279> we<00:12:17.440> have 00:12:17.629 --> 00:12:17.639 align:start position:0% already existing Nova code that we have 00:12:17.639 --> 00:12:19.710 align:start position:0% already existing Nova code that we have there<00:12:17.920> um<00:12:18.079> so<00:12:18.320> it<00:12:18.440> should<00:12:18.639> be<00:12:18.760> easy<00:12:18.959> to<00:12:19.440> fit 00:12:19.710 --> 00:12:19.720 align:start position:0% there um so it should be easy to fit 00:12:19.720 --> 00:12:21.629 align:start position:0% there um so it should be easy to fit them<00:12:19.920> in<00:12:20.160> also<00:12:20.519> and<00:12:20.639> then<00:12:20.920> for<00:12:21.120> the<00:12:21.199> front<00:12:21.399> end 00:12:21.629 --> 00:12:21.639 align:start position:0% them in also and then for the front end 00:12:21.639 --> 00:12:23.310 align:start position:0% them in also and then for the front end like<00:12:21.800> how<00:12:21.959> you<00:12:22.079> can<00:12:22.399> Define<00:12:22.760> the<00:12:22.880> circuit<00:12:23.199> that 00:12:23.310 --> 00:12:23.320 align:start position:0% like how you can Define the circuit that 00:12:23.320 --> 00:12:25.550 align:start position:0% like how you can Define the circuit that you<00:12:23.360> want<00:12:23.480> to<00:12:23.600> fold<00:12:24.279> um<00:12:24.519> this<00:12:24.639> is<00:12:24.800> done<00:12:25.160> through 00:12:25.550 --> 00:12:25.560 align:start position:0% you want to fold um this is done through 00:12:25.560 --> 00:12:27.710 align:start position:0% you want to fold um this is done through some<00:12:25.800> interface<00:12:26.680> by<00:12:26.800> default<00:12:27.120> is<00:12:27.199> artworks 00:12:27.710 --> 00:12:27.720 align:start position:0% some interface by default is artworks 00:12:27.720 --> 00:12:29.910 align:start position:0% some interface by default is artworks but<00:12:28.199> uh<00:12:28.399> as<00:12:28.639> experimental<00:12:29.240> thing<00:12:29.600> which<00:12:29.720> is<00:12:29.839> a 00:12:29.910 --> 00:12:29.920 align:start position:0% but uh as experimental thing which is a 00:12:29.920 --> 00:12:32.430 align:start position:0% but uh as experimental thing which is a bit<00:12:30.120> slower<00:12:30.920> uh<00:12:31.000> you<00:12:31.120> can<00:12:31.279> also<00:12:31.480> use<00:12:31.800> uh<00:12:31.920> circum 00:12:32.430 --> 00:12:32.440 align:start position:0% bit slower uh you can also use uh circum 00:12:32.440 --> 00:12:35.430 align:start position:0% bit slower uh you can also use uh circum Noah<00:12:32.720> and<00:12:32.880> no<00:12:33.079> name<00:12:34.000> but<00:12:34.199> yeah<00:12:34.360> so<00:12:34.639> just<00:12:35.040> to 00:12:35.430 --> 00:12:35.440 align:start position:0% Noah and no name but yeah so just to 00:12:35.440 --> 00:12:38.430 align:start position:0% Noah and no name but yeah so just to give<00:12:35.560> you<00:12:35.680> a<00:12:35.800> bit<00:12:35.920> of<00:12:36.279> like<00:12:36.560> a<00:12:36.720> sense<00:12:37.720> Nova<00:12:38.279> is 00:12:38.430 --> 00:12:38.440 align:start position:0% give you a bit of like a sense Nova is 00:12:38.440 --> 00:12:39.949 align:start position:0% give you a bit of like a sense Nova is using<00:12:38.720> this<00:12:38.880> random<00:12:39.120> linear<00:12:39.360> combination<00:12:39.800> for 00:12:39.949 --> 00:12:39.959 align:start position:0% using this random linear combination for 00:12:39.959 --> 00:12:43.069 align:start position:0% using this random linear combination for the<00:12:40.079> folding<00:12:40.720> part<00:12:41.279> which<00:12:41.560> this<00:12:41.720> is<00:12:42.480> then<00:12:42.760> need 00:12:43.069 --> 00:12:43.079 align:start position:0% the folding part which this is then need 00:12:43.079 --> 00:12:46.470 align:start position:0% the folding part which this is then need this<00:12:43.240> needs<00:12:43.440> to<00:12:43.600> be<00:12:44.240> um<00:12:45.160> checked<00:12:45.600> inside<00:12:46.360> a 00:12:46.470 --> 00:12:46.480 align:start position:0% this needs to be um checked inside a 00:12:46.480 --> 00:12:50.150 align:start position:0% this needs to be um checked inside a circuit<00:12:47.399> so<00:12:47.920> then<00:12:48.360> uh<00:12:48.760> H<00:12:49.000> hypernova<00:12:49.920> instead 00:12:50.150 --> 00:12:50.160 align:start position:0% circuit so then uh H hypernova instead 00:12:50.160 --> 00:12:52.310 align:start position:0% circuit so then uh H hypernova instead of<00:12:50.240> doing<00:12:50.399> this<00:12:50.560> randomly<00:12:51.000> combination<00:12:51.480> uses 00:12:52.310 --> 00:12:52.320 align:start position:0% of doing this randomly combination uses 00:12:52.320 --> 00:12:54.710 align:start position:0% of doing this randomly combination uses it<00:12:52.440> linearizes<00:12:53.399> the<00:12:53.519> the<00:12:53.639> instances<00:12:54.040> and<00:12:54.199> then 00:12:54.710 --> 00:12:54.720 align:start position:0% it linearizes the the instances and then 00:12:54.720 --> 00:12:58.189 align:start position:0% it linearizes the the instances and then runs<00:12:55.000> the<00:12:55.120> S<00:12:55.399> check<00:12:56.160> uh<00:12:56.279> to<00:12:56.480> to<00:12:56.600> prove<00:12:56.920> the<00:12:57.639> the 00:12:58.189 --> 00:12:58.199 align:start position:0% runs the S check uh to to prove the the 00:12:58.199 --> 00:13:00.710 align:start position:0% runs the S check uh to to prove the the relation<00:12:59.279> uh<00:12:59.399> and<00:12:59.519> then<00:12:59.720> Proto<00:13:00.000> Galaxy<00:13:00.519> is 00:13:00.710 --> 00:13:00.720 align:start position:0% relation uh and then Proto Galaxy is 00:13:00.720 --> 00:13:02.150 align:start position:0% relation uh and then Proto Galaxy is instead<00:13:00.959> of<00:13:01.120> random<00:13:01.399> linear<00:13:01.639> combination<00:13:02.000> is 00:13:02.150 --> 00:13:02.160 align:start position:0% instead of random linear combination is 00:13:02.160 --> 00:13:03.750 align:start position:0% instead of random linear combination is doing<00:13:02.720> linear<00:13:03.000> combinations<00:13:03.440> with<00:13:03.600> the 00:13:03.750 --> 00:13:03.760 align:start position:0% doing linear combinations with the 00:13:03.760 --> 00:13:06.069 align:start position:0% doing linear combinations with the lrange<00:13:04.120> bases<00:13:05.079> uh<00:13:05.199> in<00:13:05.320> one<00:13:05.440> of<00:13:05.560> the<00:13:05.720> settings 00:13:06.069 --> 00:13:06.079 align:start position:0% lrange bases uh in one of the settings 00:13:06.079 --> 00:13:07.389 align:start position:0% lrange bases uh in one of the settings and<00:13:06.240> in<00:13:06.360> the<00:13:06.480> other<00:13:06.639> setting<00:13:06.880> is<00:13:06.959> also<00:13:07.160> using 00:13:07.389 --> 00:13:07.399 align:start position:0% and in the other setting is also using 00:13:07.399 --> 00:13:09.189 align:start position:0% and in the other setting is also using the<00:13:07.720> S<00:13:08.000> check<00:13:08.199> but<00:13:08.360> just<00:13:08.519> to<00:13:08.720> give<00:13:08.839> you<00:13:08.959> a<00:13:09.079> bit 00:13:09.189 --> 00:13:09.199 align:start position:0% the S check but just to give you a bit 00:13:09.199 --> 00:13:11.430 align:start position:0% the S check but just to give you a bit of<00:13:09.560> sense<00:13:09.800> of<00:13:10.120> that<00:13:10.320> different<00:13:10.639> schemes<00:13:11.199> use 00:13:11.430 --> 00:13:11.440 align:start position:0% of sense of that different schemes use 00:13:11.440 --> 00:13:13.230 align:start position:0% of sense of that different schemes use different<00:13:11.720> techniques<00:13:12.199> so<00:13:12.639> one<00:13:12.760> of<00:13:12.880> the<00:13:13.000> goals 00:13:13.230 --> 00:13:13.240 align:start position:0% different techniques so one of the goals 00:13:13.240 --> 00:13:15.269 align:start position:0% different techniques so one of the goals also<00:13:13.480> here<00:13:13.600> is<00:13:13.760> like<00:13:13.920> to<00:13:14.279> be<00:13:14.440> able<00:13:14.639> to<00:13:14.760> see<00:13:15.079> in 00:13:15.269 --> 00:13:15.279 align:start position:0% also here is like to be able to see in 00:13:15.279 --> 00:13:17.110 align:start position:0% also here is like to be able to see in in<00:13:15.399> different<00:13:15.680> use<00:13:15.920> cases<00:13:16.480> which<00:13:16.600> one<00:13:16.800> fits 00:13:17.110 --> 00:13:17.120 align:start position:0% in different use cases which one fits 00:13:17.120 --> 00:13:19.230 align:start position:0% in different use cases which one fits better<00:13:17.440> and<00:13:17.639> and<00:13:17.800> so<00:13:17.959> on<00:13:18.120> so<00:13:18.320> having<00:13:18.560> this 00:13:19.230 --> 00:13:19.240 align:start position:0% better and and so on so having this 00:13:19.240 --> 00:13:22.430 align:start position:0% better and and so on so having this modularity<00:13:20.240> then<00:13:20.800> okay<00:13:21.160> so<00:13:21.920> this<00:13:22.000> is<00:13:22.160> how<00:13:22.320> it 00:13:22.430 --> 00:13:22.440 align:start position:0% modularity then okay so this is how it 00:13:22.440 --> 00:13:24.509 align:start position:0% modularity then okay so this is how it looks<00:13:22.680> like<00:13:22.880> the<00:13:23.240> F<00:13:23.560> circuit<00:13:23.959> interface<00:13:24.440> this 00:13:24.509 --> 00:13:24.519 align:start position:0% looks like the F circuit interface this 00:13:24.519 --> 00:13:25.910 align:start position:0% looks like the F circuit interface this is<00:13:24.680> like<00:13:24.839> the<00:13:25.000> the<00:13:25.079> circuit<00:13:25.399> that<00:13:25.519> you<00:13:25.600> want<00:13:25.760> to 00:13:25.910 --> 00:13:25.920 align:start position:0% is like the the circuit that you want to 00:13:25.920 --> 00:13:27.790 align:start position:0% is like the the circuit that you want to actually<00:13:26.160> fold<00:13:27.040> uh<00:13:27.240> you<00:13:27.360> just<00:13:27.519> need<00:13:27.680> to 00:13:27.790 --> 00:13:27.800 align:start position:0% actually fold uh you just need to 00:13:27.800 --> 00:13:30.949 align:start position:0% actually fold uh you just need to implement<00:13:28.279> this<00:13:28.519> like<00:13:28.920> the<00:13:29.160> the<00:13:29.320> first<00:13:29.959> three 00:13:30.949 --> 00:13:30.959 align:start position:0% implement this like the the first three 00:13:30.959 --> 00:13:33.230 align:start position:0% implement this like the the first three methods<00:13:31.560> are<00:13:31.760> just<00:13:31.959> like<00:13:32.360> very<00:13:32.560> simple<00:13:32.839> things 00:13:33.230 --> 00:13:33.240 align:start position:0% methods are just like very simple things 00:13:33.240 --> 00:13:34.990 align:start position:0% methods are just like very simple things and<00:13:33.360> then<00:13:33.519> step<00:13:33.800> native<00:13:34.160> and<00:13:34.320> generative<00:13:34.760> step 00:13:34.990 --> 00:13:35.000 align:start position:0% and then step native and generative step 00:13:35.000 --> 00:13:36.910 align:start position:0% and then step native and generative step constraints<00:13:35.800> those<00:13:35.920> are<00:13:36.120> like<00:13:36.360> the<00:13:36.639> the<00:13:36.839> the 00:13:36.910 --> 00:13:36.920 align:start position:0% constraints those are like the the the 00:13:36.920 --> 00:13:39.430 align:start position:0% constraints those are like the the the logic<00:13:37.279> that<00:13:37.399> you<00:13:37.480> want<00:13:37.680> to<00:13:38.199> do<00:13:38.600> at<00:13:38.760> each<00:13:38.959> fault 00:13:39.430 --> 00:13:39.440 align:start position:0% logic that you want to do at each fault 00:13:39.440 --> 00:13:41.189 align:start position:0% logic that you want to do at each fault step<00:13:39.680> native<00:13:40.040> is<00:13:40.160> what<00:13:40.279> you<00:13:40.399> do<00:13:40.600> in<00:13:40.760> Ras<00:13:41.079> like 00:13:41.189 --> 00:13:41.199 align:start position:0% step native is what you do in Ras like 00:13:41.199 --> 00:13:42.990 align:start position:0% step native is what you do in Ras like outside<00:13:41.560> the<00:13:41.680> circuit<00:13:42.199> and<00:13:42.399> generate<00:13:42.760> step 00:13:42.990 --> 00:13:43.000 align:start position:0% outside the circuit and generate step 00:13:43.000 --> 00:13:44.590 align:start position:0% outside the circuit and generate step constraints<00:13:43.720> is<00:13:43.880> where<00:13:44.040> you<00:13:44.199> define<00:13:44.480> the 00:13:44.590 --> 00:13:44.600 align:start position:0% constraints is where you define the 00:13:44.600 --> 00:13:45.750 align:start position:0% constraints is where you define the logic<00:13:44.839> of<00:13:44.959> the<00:13:45.079> circuit<00:13:45.399> that<00:13:45.480> you<00:13:45.560> want<00:13:45.680> to 00:13:45.750 --> 00:13:45.760 align:start position:0% logic of the circuit that you want to 00:13:45.760 --> 00:13:47.310 align:start position:0% logic of the circuit that you want to fold<00:13:46.000> so<00:13:46.120> this<00:13:46.240> is<00:13:46.360> like<00:13:46.480> the<00:13:46.600> constraint<00:13:47.079> that 00:13:47.310 --> 00:13:47.320 align:start position:0% fold so this is like the constraint that 00:13:47.320 --> 00:13:49.550 align:start position:0% fold so this is like the constraint that you<00:13:47.440> are<00:13:47.560> folding<00:13:47.959> actually<00:13:48.880> just<00:13:49.120> by 00:13:49.550 --> 00:13:49.560 align:start position:0% you are folding actually just by 00:13:49.560 --> 00:13:51.790 align:start position:0% you are folding actually just by defining<00:13:50.480> this<00:13:50.880> interface<00:13:51.399> like<00:13:51.560> if<00:13:51.680> you 00:13:51.790 --> 00:13:51.800 align:start position:0% defining this interface like if you 00:13:51.800 --> 00:13:53.829 align:start position:0% defining this interface like if you implement<00:13:52.199> it<00:13:52.560> then<00:13:52.720> you<00:13:52.839> can<00:13:53.079> plug<00:13:53.399> this<00:13:53.560> into 00:13:53.829 --> 00:13:53.839 align:start position:0% implement it then you can plug this into 00:13:53.839 --> 00:13:56.350 align:start position:0% implement it then you can plug this into sonov<00:13:54.639> and<00:13:55.000> then<00:13:55.320> uh<00:13:55.399> sonov<00:13:55.800> takes<00:13:56.000> care<00:13:56.160> of 00:13:56.350 --> 00:13:56.360 align:start position:0% sonov and then uh sonov takes care of 00:13:56.360 --> 00:13:58.269 align:start position:0% sonov and then uh sonov takes care of like<00:13:56.519> wrapping<00:13:56.880> this<00:13:57.079> inside<00:13:57.399> the<00:13:57.800> augmented 00:13:58.269 --> 00:13:58.279 align:start position:0% like wrapping this inside the augmented 00:13:58.279 --> 00:14:01.110 align:start position:0% like wrapping this inside the augmented function<00:13:59.120> cirquit<00:13:59.880> um<00:14:00.360> and<00:14:00.560> and<00:14:00.680> doing<00:14:00.920> the 00:14:01.110 --> 00:14:01.120 align:start position:0% function cirquit um and and doing the 00:14:01.120 --> 00:14:03.189 align:start position:0% function cirquit um and and doing the IBC<00:14:01.480> folding<00:14:01.959> and<00:14:02.199> and<00:14:02.440> and<00:14:02.600> the<00:14:02.720> rest<00:14:02.920> of<00:14:03.079> of 00:14:03.189 --> 00:14:03.199 align:start position:0% IBC folding and and and the rest of of 00:14:03.199 --> 00:14:04.870 align:start position:0% IBC folding and and and the rest of of checks<00:14:03.480> and<00:14:03.639> so<00:14:03.759> on<00:14:04.079> so<00:14:04.240> the<00:14:04.320> idea<00:14:04.519> is<00:14:04.600> to<00:14:04.720> have 00:14:04.870 --> 00:14:04.880 align:start position:0% checks and so on so the idea is to have 00:14:04.880 --> 00:14:07.269 align:start position:0% checks and so on so the idea is to have this<00:14:05.079> very<00:14:05.279> simple<00:14:05.560> interface<00:14:06.399> that<00:14:06.680> uh<00:14:06.800> also 00:14:07.269 --> 00:14:07.279 align:start position:0% this very simple interface that uh also 00:14:07.279 --> 00:14:09.710 align:start position:0% this very simple interface that uh also this<00:14:07.560> is<00:14:07.759> used<00:14:08.240> so<00:14:08.440> when<00:14:08.560> you<00:14:08.680> want<00:14:08.839> to<00:14:09.240> include 00:14:09.710 --> 00:14:09.720 align:start position:0% this is used so when you want to include 00:14:09.720 --> 00:14:12.749 align:start position:0% this is used so when you want to include a<00:14:09.839> new<00:14:10.320> uh<00:14:10.440> Zig<00:14:10.800> language<00:14:11.240> into<00:14:12.120> being<00:14:12.320> able<00:14:12.519> to 00:14:12.749 --> 00:14:12.759 align:start position:0% a new uh Zig language into being able to 00:14:12.759 --> 00:14:15.550 align:start position:0% a new uh Zig language into being able to use<00:14:13.000> sonov<00:14:13.720> just<00:14:13.959> by<00:14:14.160> implementing<00:14:14.759> this<00:14:15.320> for 00:14:15.550 --> 00:14:15.560 align:start position:0% use sonov just by implementing this for 00:14:15.560 --> 00:14:17.949 align:start position:0% use sonov just by implementing this for for<00:14:15.720> the<00:14:15.880> language<00:14:16.600> that<00:14:16.720> you<00:14:16.800> want<00:14:16.959> to<00:14:17.199> use<00:14:17.720> uh 00:14:17.949 --> 00:14:17.959 align:start position:0% for the language that you want to use uh 00:14:17.959 --> 00:14:20.910 align:start position:0% for the language that you want to use uh you<00:14:18.160> you<00:14:18.320> you<00:14:18.440> already<00:14:18.720> have<00:14:18.880> it<00:14:19.880> then<00:14:20.639> this<00:14:20.759> is 00:14:20.910 --> 00:14:20.920 align:start position:0% you you you already have it then this is 00:14:20.920 --> 00:14:22.509 align:start position:0% you you you already have it then this is like<00:14:21.160> the<00:14:21.399> the<00:14:21.600> the<00:14:21.680> usual<00:14:22.000> code<00:14:22.240> that<00:14:22.360> you 00:14:22.509 --> 00:14:22.519 align:start position:0% like the the the usual code that you 00:14:22.519 --> 00:14:25.629 align:start position:0% like the the the usual code that you need<00:14:23.000> uh<00:14:23.199> using<00:14:23.440> sonov<00:14:24.040> to<00:14:24.199> fold<00:14:24.600> the<00:14:24.759> circuit 00:14:25.629 --> 00:14:25.639 align:start position:0% need uh using sonov to fold the circuit 00:14:25.639 --> 00:14:28.189 align:start position:0% need uh using sonov to fold the circuit so<00:14:26.079> the<00:14:26.240> main<00:14:26.480> idea<00:14:26.720> is<00:14:26.880> that<00:14:27.120> here<00:14:27.399> you<00:14:27.600> define 00:14:28.189 --> 00:14:28.199 align:start position:0% so the main idea is that here you define 00:14:28.199 --> 00:14:30.269 align:start position:0% so the main idea is that here you define which<00:14:28.360> folding<00:14:28.720> schemes<00:14:29.480> you<00:14:29.560> want<00:14:29.720> to<00:14:29.839> use 00:14:30.269 --> 00:14:30.279 align:start position:0% which folding schemes you want to use 00:14:30.279 --> 00:14:32.470 align:start position:0% which folding schemes you want to use and<00:14:30.440> also<00:14:30.720> like<00:14:30.880> as<00:14:31.000> you<00:14:31.079> see<00:14:31.279> this<00:14:31.440> PS<00:14:31.759> and<00:14:31.920> G1 00:14:32.470 --> 00:14:32.480 align:start position:0% and also like as you see this PS and G1 00:14:32.480 --> 00:14:35.150 align:start position:0% and also like as you see this PS and G1 PS<00:14:32.800> and<00:14:32.920> G2<00:14:33.399> so<00:14:33.759> the<00:14:33.839> G1<00:14:34.240> G2<00:14:34.720> those<00:14:34.880> are<00:14:35.040> like 00:14:35.150 --> 00:14:35.160 align:start position:0% PS and G2 so the G1 G2 those are like 00:14:35.160 --> 00:14:37.150 align:start position:0% PS and G2 so the G1 G2 those are like the<00:14:35.279> cures<00:14:35.600> that<00:14:35.680> you<00:14:35.800> use<00:14:36.360> we<00:14:36.480> need<00:14:36.720> a<00:14:36.880> cycle 00:14:37.150 --> 00:14:37.160 align:start position:0% the cures that you use we need a cycle 00:14:37.160 --> 00:14:40.069 align:start position:0% the cures that you use we need a cycle of<00:14:37.279> Curves<00:14:37.720> but<00:14:38.040> you<00:14:38.160> can<00:14:38.639> pick<00:14:39.399> uh<00:14:39.759> most<00:14:39.959> of 00:14:40.069 --> 00:14:40.079 align:start position:0% of Curves but you can pick uh most of 00:14:40.079 --> 00:14:41.590 align:start position:0% of Curves but you can pick uh most of the<00:14:40.160> curves<00:14:40.480> that<00:14:40.560> are<00:14:40.839> available<00:14:41.240> in 00:14:41.590 --> 00:14:41.600 align:start position:0% the curves that are available in 00:14:41.600 --> 00:14:44.949 align:start position:0% the curves that are available in artworks<00:14:42.519> and<00:14:42.639> then<00:14:42.759> the<00:14:42.920> pson<00:14:43.480> G1<00:14:44.040> Pon<00:14:44.360> G2 00:14:44.949 --> 00:14:44.959 align:start position:0% artworks and then the pson G1 Pon G2 00:14:44.959 --> 00:14:46.189 align:start position:0% artworks and then the pson G1 Pon G2 this<00:14:45.160> is<00:14:45.279> like<00:14:45.399> the<00:14:45.480> commitment<00:14:45.839> scheme<00:14:46.079> that 00:14:46.189 --> 00:14:46.199 align:start position:0% this is like the commitment scheme that 00:14:46.199 --> 00:14:47.749 align:start position:0% this is like the commitment scheme that we<00:14:46.320> use<00:14:46.600> in<00:14:46.720> the<00:14:46.839> first<00:14:47.199> curve<00:14:47.480> and<00:14:47.639> the 00:14:47.749 --> 00:14:47.759 align:start position:0% we use in the first curve and the 00:14:47.759 --> 00:14:50.230 align:start position:0% we use in the first curve and the secondary<00:14:48.120> curve<00:14:48.480> of<00:14:48.600> the<00:14:48.759> curve<00:14:49.079> cycle<00:14:50.040> and 00:14:50.230 --> 00:14:50.240 align:start position:0% secondary curve of the curve cycle and 00:14:50.240 --> 00:14:51.470 align:start position:0% secondary curve of the curve cycle and and<00:14:50.360> then<00:14:50.519> the<00:14:50.639> rest<00:14:50.800> is<00:14:50.959> like<00:14:51.079> more<00:14:51.240> or<00:14:51.360> less 00:14:51.470 --> 00:14:51.480 align:start position:0% and then the rest is like more or less 00:14:51.480 --> 00:14:53.110 align:start position:0% and then the rest is like more or less will<00:14:51.600> be<00:14:51.720> the<00:14:51.839> same<00:14:52.040> like<00:14:52.199> here<00:14:52.360> we<00:14:52.480> are<00:14:52.600> doing 00:14:53.110 --> 00:14:53.120 align:start position:0% will be the same like here we are doing 00:14:53.120 --> 00:14:55.350 align:start position:0% will be the same like here we are doing 100<00:14:53.440> steps<00:14:54.000> of<00:14:54.199> this<00:14:54.519> uh<00:14:54.639> proof<00:14:54.920> step<00:14:55.160> which<00:14:55.279> is 00:14:55.350 --> 00:14:55.360 align:start position:0% 100 steps of this uh proof step which is 00:14:55.360 --> 00:14:57.389 align:start position:0% 100 steps of this uh proof step which is like<00:14:55.519> the<00:14:55.680> the<00:14:55.800> actual<00:14:56.079> folding<00:14:56.519> of<00:14:56.639> the<00:14:56.720> IBC 00:14:57.389 --> 00:14:57.399 align:start position:0% like the the actual folding of the IBC 00:14:57.399 --> 00:14:58.790 align:start position:0% like the the actual folding of the IBC and<00:14:57.519> at<00:14:57.639> the<00:14:57.720> end<00:14:57.959> you<00:14:58.040> can<00:14:58.160> just<00:14:58.279> verify<00:14:58.680> the 00:14:58.790 --> 00:14:58.800 align:start position:0% and at the end you can just verify the 00:14:58.800 --> 00:15:00.990 align:start position:0% and at the end you can just verify the last<00:14:58.920> one<00:14:59.120> one<00:14:59.639> and<00:14:59.839> so<00:15:00.320> here<00:15:00.440> you<00:15:00.519> are<00:15:00.680> proving 00:15:00.990 --> 00:15:01.000 align:start position:0% last one one and so here you are proving 00:15:01.000 --> 00:15:03.310 align:start position:0% last one one and so here you are proving like<00:15:01.199> that<00:15:01.680> after<00:15:02.199> 100<00:15:02.480> repetitions<00:15:02.959> of<00:15:03.120> this 00:15:03.310 --> 00:15:03.320 align:start position:0% like that after 100 repetitions of this 00:15:03.320 --> 00:15:05.470 align:start position:0% like that after 100 repetitions of this computation<00:15:04.120> you<00:15:04.279> obtain<00:15:04.600> this<00:15:04.759> final<00:15:05.079> step 00:15:05.470 --> 00:15:05.480 align:start position:0% computation you obtain this final step 00:15:05.480 --> 00:15:08.069 align:start position:0% computation you obtain this final step coming<00:15:05.759> from<00:15:05.920> the<00:15:06.079> first<00:15:06.480> initial<00:15:07.000> St<00:15:07.240> State 00:15:08.069 --> 00:15:08.079 align:start position:0% coming from the first initial St State 00:15:08.079 --> 00:15:10.269 align:start position:0% coming from the first initial St State um<00:15:09.079> so<00:15:09.279> so<00:15:09.440> yeah<00:15:09.560> so<00:15:09.720> that<00:15:09.839> that's<00:15:09.959> the<00:15:10.079> main 00:15:10.269 --> 00:15:10.279 align:start position:0% um so so yeah so that that's the main 00:15:10.279 --> 00:15:13.110 align:start position:0% um so so yeah so that that's the main idea<00:15:10.720> as<00:15:10.839> you<00:15:10.959> can<00:15:11.079> see<00:15:11.320> I<00:15:11.399> mean<00:15:12.279> it's<00:15:12.560> quite<00:15:12.920> uh 00:15:13.110 --> 00:15:13.120 align:start position:0% idea as you can see I mean it's quite uh 00:15:13.120 --> 00:15:16.350 align:start position:0% idea as you can see I mean it's quite uh like<00:15:13.800> simplified<00:15:14.800> and<00:15:15.040> and<00:15:15.279> easy<00:15:15.519> to<00:15:16.000> I<00:15:16.079> mean 00:15:16.350 --> 00:15:16.360 align:start position:0% like simplified and and easy to I mean 00:15:16.360 --> 00:15:18.310 align:start position:0% like simplified and and easy to I mean easy<00:15:16.519> to<00:15:16.639> reason<00:15:16.959> is<00:15:17.079> it<00:15:17.360> easy<00:15:17.600> to<00:15:17.839> to<00:15:18.079> have 00:15:18.310 --> 00:15:18.320 align:start position:0% easy to reason is it easy to to have 00:15:18.320 --> 00:15:21.509 align:start position:0% easy to reason is it easy to to have this<00:15:18.680> uh<00:15:18.800> working<00:15:19.120> and<00:15:19.240> so<00:15:19.360> on<00:15:19.720> and<00:15:19.920> then<00:15:20.519> when 00:15:21.509 --> 00:15:21.519 align:start position:0% this uh working and so on and then when 00:15:21.519 --> 00:15:23.310 align:start position:0% this uh working and so on and then when you<00:15:21.720> want<00:15:21.880> to<00:15:22.000> change<00:15:22.399> which<00:15:22.560> folding<00:15:23.000> scheme 00:15:23.310 --> 00:15:23.320 align:start position:0% you want to change which folding scheme 00:15:23.320 --> 00:15:25.790 align:start position:0% you want to change which folding scheme you<00:15:23.440> are<00:15:23.600> using<00:15:24.360> it's<00:15:24.600> as<00:15:24.759> simple<00:15:25.160> as<00:15:25.440> just 00:15:25.790 --> 00:15:25.800 align:start position:0% you are using it's as simple as just 00:15:25.800 --> 00:15:28.470 align:start position:0% you are using it's as simple as just taking<00:15:26.279> this<00:15:26.519> line<00:15:27.519> and<00:15:27.680> then<00:15:27.839> you<00:15:27.959> can<00:15:28.160> say 00:15:28.470 --> 00:15:28.480 align:start position:0% taking this line and then you can say 00:15:28.480 --> 00:15:31.870 align:start position:0% taking this line and then you can say okay<00:15:29.040> I<00:15:29.120> want<00:15:29.319> to<00:15:29.480> use<00:15:30.240> still<00:15:30.480> Nova<00:15:31.319> but<00:15:31.519> now<00:15:31.800> I 00:15:31.870 --> 00:15:31.880 align:start position:0% okay I want to use still Nova but now I 00:15:31.880 --> 00:15:33.910 align:start position:0% okay I want to use still Nova but now I want<00:15:32.079> to<00:15:32.319> have<00:15:33.040> uh<00:15:33.199> in<00:15:33.360> the<00:15:33.519> in<00:15:33.600> the<00:15:33.680> first 00:15:33.910 --> 00:15:33.920 align:start position:0% want to have uh in the in the first 00:15:33.920 --> 00:15:36.110 align:start position:0% want to have uh in the in the first curve<00:15:34.199> I<00:15:34.279> will<00:15:34.399> use<00:15:34.639> kg<00:15:35.079> commitments<00:15:35.800> so<00:15:35.959> that 00:15:36.110 --> 00:15:36.120 align:start position:0% curve I will use kg commitments so that 00:15:36.120 --> 00:15:39.030 align:start position:0% curve I will use kg commitments so that then<00:15:36.279> I<00:15:36.360> can<00:15:36.560> use<00:15:36.800> the<00:15:37.079> final<00:15:37.560> uh<00:15:37.759> decider<00:15:38.759> uh 00:15:39.030 --> 00:15:39.040 align:start position:0% then I can use the final uh decider uh 00:15:39.040 --> 00:15:40.949 align:start position:0% then I can use the final uh decider uh the<00:15:39.120> unchain<00:15:39.480> decider<00:15:39.959> that<00:15:40.079> I<00:15:40.199> can<00:15:40.480> then<00:15:40.839> uh 00:15:40.949 --> 00:15:40.959 align:start position:0% the unchain decider that I can then uh 00:15:40.959 --> 00:15:44.350 align:start position:0% the unchain decider that I can then uh send<00:15:41.279> proofs<00:15:42.000> to<00:15:43.000> ethereum<00:15:43.480> and<00:15:43.600> be<00:15:43.759> verified 00:15:44.350 --> 00:15:44.360 align:start position:0% send proofs to ethereum and be verified 00:15:44.360 --> 00:15:46.069 align:start position:0% send proofs to ethereum and be verified or<00:15:44.519> you<00:15:44.600> can<00:15:44.720> say<00:15:45.000> oh<00:15:45.279> you<00:15:45.399> know<00:15:45.600> what<00:15:45.959> I'm 00:15:46.069 --> 00:15:46.079 align:start position:0% or you can say oh you know what I'm 00:15:46.079 --> 00:15:47.509 align:start position:0% or you can say oh you know what I'm going<00:15:46.240> to<00:15:46.360> change<00:15:46.600> to<00:15:46.759> hypernova<00:15:47.319> so<00:15:47.440> you 00:15:47.509 --> 00:15:47.519 align:start position:0% going to change to hypernova so you 00:15:47.519 --> 00:15:49.150 align:start position:0% going to change to hypernova so you don't<00:15:47.680> need<00:15:47.839> to<00:15:48.240> throw<00:15:48.519> away<00:15:48.680> your<00:15:48.839> code<00:15:49.079> you 00:15:49.150 --> 00:15:49.160 align:start position:0% don't need to throw away your code you 00:15:49.160 --> 00:15:51.069 align:start position:0% don't need to throw away your code you can<00:15:49.360> just<00:15:49.720> replace<00:15:50.120> this<00:15:50.240> line<00:15:50.720> and<00:15:50.880> now<00:15:51.000> you 00:15:51.069 --> 00:15:51.079 align:start position:0% can just replace this line and now you 00:15:51.079 --> 00:15:53.710 align:start position:0% can just replace this line and now you are<00:15:51.199> using<00:15:51.480> hypernova<00:15:52.440> or<00:15:52.759> I'm<00:15:53.319> I'm<00:15:53.440> going<00:15:53.600> to 00:15:53.710 --> 00:15:53.720 align:start position:0% are using hypernova or I'm I'm going to 00:15:53.720 --> 00:15:56.590 align:start position:0% are using hypernova or I'm I'm going to use<00:15:53.959> Proto<00:15:54.240> Galaxy<00:15:54.639> so<00:15:54.800> you<00:15:54.920> can<00:15:55.120> then<00:15:55.800> um 00:15:56.590 --> 00:15:56.600 align:start position:0% use Proto Galaxy so you can then um 00:15:56.600 --> 00:15:59.269 align:start position:0% use Proto Galaxy so you can then um doing<00:15:56.920> this<00:15:57.120> like<00:15:57.440> easy<00:15:57.839> line<00:15:58.639> one<00:15:59.040> line 00:15:59.269 --> 00:15:59.279 align:start position:0% doing this like easy line one line 00:15:59.279 --> 00:16:01.430 align:start position:0% doing this like easy line one line change<00:16:00.000> uh<00:16:00.120> you<00:16:00.240> should<00:16:00.440> be<00:16:00.560> able<00:16:00.759> to<00:16:00.959> to<00:16:01.160> have 00:16:01.430 --> 00:16:01.440 align:start position:0% change uh you should be able to to have 00:16:01.440 --> 00:16:03.829 align:start position:0% change uh you should be able to to have this<00:16:02.360> um 00:16:03.829 --> 00:16:03.839 align:start position:0% this um 00:16:03.839 --> 00:16:06.430 align:start position:0% this um then<00:16:04.839> when<00:16:05.000> it<00:16:05.120> comes<00:16:05.319> to<00:16:05.519> to<00:16:05.639> the<00:16:05.800> decider<00:16:06.240> so 00:16:06.430 --> 00:16:06.440 align:start position:0% then when it comes to to the decider so 00:16:06.440 --> 00:16:08.110 align:start position:0% then when it comes to to the decider so we<00:16:06.639> we<00:16:06.800> we've<00:16:07.000> been<00:16:07.120> folding<00:16:07.519> we<00:16:07.639> have<00:16:07.839> this 00:16:08.110 --> 00:16:08.120 align:start position:0% we we we've been folding we have this 00:16:08.120 --> 00:16:11.189 align:start position:0% we we we've been folding we have this last<00:16:08.440> IBC<00:16:09.120> state<00:16:09.480> with<00:16:09.600> the<00:16:09.920> last<00:16:10.160> IBC<00:16:10.600> proof 00:16:11.189 --> 00:16:11.199 align:start position:0% last IBC state with the last IBC proof 00:16:11.199 --> 00:16:13.069 align:start position:0% last IBC state with the last IBC proof so<00:16:11.399> now<00:16:11.639> what<00:16:11.759> we<00:16:11.880> can<00:16:12.040> do<00:16:12.240> is<00:16:12.480> is<00:16:12.680> like<00:16:12.839> we<00:16:12.920> can 00:16:13.069 --> 00:16:13.079 align:start position:0% so now what we can do is is like we can 00:16:13.079 --> 00:16:14.710 align:start position:0% so now what we can do is is like we can compress<00:16:13.440> it<00:16:13.519> with<00:16:13.639> the<00:16:13.759> deider<00:16:14.319> so<00:16:14.480> we<00:16:14.600> have 00:16:14.710 --> 00:16:14.720 align:start position:0% compress it with the deider so we have 00:16:14.720 --> 00:16:16.230 align:start position:0% compress it with the deider so we have the<00:16:14.880> offchain<00:16:15.279> decider<00:16:15.639> and<00:16:15.759> the<00:16:15.839> onchain 00:16:16.230 --> 00:16:16.240 align:start position:0% the offchain decider and the onchain 00:16:16.240 --> 00:16:18.230 align:start position:0% the offchain decider and the onchain decider<00:16:16.759> so<00:16:16.920> it's<00:16:17.160> also<00:16:17.399> like<00:16:17.600> a<00:16:17.839> similar 00:16:18.230 --> 00:16:18.240 align:start position:0% decider so it's also like a similar 00:16:18.240 --> 00:16:20.430 align:start position:0% decider so it's also like a similar interface<00:16:19.079> and<00:16:19.240> then<00:16:19.440> here<00:16:19.639> is<00:16:20.040> how<00:16:20.199> do<00:16:20.279> you 00:16:20.430 --> 00:16:20.440 align:start position:0% interface and then here is how do you 00:16:20.440 --> 00:16:22.069 align:start position:0% interface and then here is how do you use<00:16:20.639> it 00:16:22.069 --> 00:16:22.079 align:start position:0% use it 00:16:22.079 --> 00:16:24.790 align:start position:0% use it um<00:16:23.079> and<00:16:23.519> the<00:16:23.680> the<00:16:23.839> one<00:16:23.959> of<00:16:24.079> the<00:16:24.160> key<00:16:24.319> things<00:16:24.560> was 00:16:24.790 --> 00:16:24.800 align:start position:0% um and the the one of the key things was 00:16:24.800 --> 00:16:28.150 align:start position:0% um and the the one of the key things was this<00:16:24.920> unchain<00:16:25.399> verification<00:16:26.399> um<00:16:27.120> so<00:16:27.880> was<00:16:28.040> one 00:16:28.150 --> 00:16:28.160 align:start position:0% this unchain verification um so was one 00:16:28.160 --> 00:16:29.749 align:start position:0% this unchain verification um so was one of<00:16:28.240> the<00:16:28.360> goals<00:16:28.639> because<00:16:29.000> and<00:16:29.160> and<00:16:29.360> we've<00:16:29.600> not 00:16:29.749 --> 00:16:29.759 align:start position:0% of the goals because and and we've not 00:16:29.759 --> 00:16:31.189 align:start position:0% of the goals because and and we've not seen<00:16:30.120> many<00:16:30.399> other<00:16:30.600> folding<00:16:30.920> schemes 00:16:31.189 --> 00:16:31.199 align:start position:0% seen many other folding schemes 00:16:31.199 --> 00:16:33.430 align:start position:0% seen many other folding schemes libraries<00:16:31.800> having<00:16:32.079> this<00:16:32.399> onchain<00:16:33.319> uh 00:16:33.430 --> 00:16:33.440 align:start position:0% libraries having this onchain uh 00:16:33.440 --> 00:16:35.870 align:start position:0% libraries having this onchain uh verification<00:16:33.959> so<00:16:34.120> the<00:16:34.240> idea<00:16:34.920> is<00:16:35.079> that<00:16:35.279> in<00:16:35.480> the 00:16:35.870 --> 00:16:35.880 align:start position:0% verification so the idea is that in the 00:16:35.880 --> 00:16:37.590 align:start position:0% verification so the idea is that in the original<00:16:36.279> Nova<00:16:36.880> this<00:16:37.040> decider<00:16:37.440> this 00:16:37.590 --> 00:16:37.600 align:start position:0% original Nova this decider this 00:16:37.600 --> 00:16:39.629 align:start position:0% original Nova this decider this compressing<00:16:38.120> of<00:16:38.240> the<00:16:38.360> IBC<00:16:38.720> proof<00:16:39.240> is<00:16:39.399> done 00:16:39.629 --> 00:16:39.639 align:start position:0% compressing of the IBC proof is done 00:16:39.639 --> 00:16:41.509 align:start position:0% compressing of the IBC proof is done through<00:16:39.880> two<00:16:40.079> Spartan<00:16:40.480> proofs<00:16:40.839> one<00:16:41.040> on<00:16:41.240> each 00:16:41.509 --> 00:16:41.519 align:start position:0% through two Spartan proofs one on each 00:16:41.519 --> 00:16:44.749 align:start position:0% through two Spartan proofs one on each of<00:16:41.639> the<00:16:41.800> cures<00:16:42.759> um<00:16:43.519> in<00:16:43.639> our<00:16:43.880> case<00:16:44.120> since<00:16:44.480> we<00:16:44.639> are 00:16:44.749 --> 00:16:44.759 align:start position:0% of the cures um in our case since we are 00:16:44.759 --> 00:16:47.309 align:start position:0% of the cures um in our case since we are interested<00:16:45.199> to<00:16:45.279> verify<00:16:45.800> inside<00:16:46.160> the<00:16:46.279> evm<00:16:47.199> uh 00:16:47.309 --> 00:16:47.319 align:start position:0% interested to verify inside the evm uh 00:16:47.319 --> 00:16:50.189 align:start position:0% interested to verify inside the evm uh the<00:16:47.440> evm<00:16:47.839> has<00:16:48.120> some<00:16:48.399> kind<00:16:48.560> of<00:16:49.040> restrictions<00:16:50.040> uh 00:16:50.189 --> 00:16:50.199 align:start position:0% the evm has some kind of restrictions uh 00:16:50.199 --> 00:16:52.150 align:start position:0% the evm has some kind of restrictions uh like<00:16:50.600> we<00:16:50.720> are<00:16:50.839> limited<00:16:51.160> to<00:16:51.360> a<00:16:51.440> single<00:16:51.720> cure<00:16:52.040> the 00:16:52.150 --> 00:16:52.160 align:start position:0% like we are limited to a single cure the 00:16:52.160 --> 00:16:55.030 align:start position:0% like we are limited to a single cure the V<00:16:52.440> 2504<00:16:53.440> and<00:16:53.600> also<00:16:53.839> constrained<00:16:54.279> by<00:16:54.399> the<00:16:54.519> gas<00:16:54.759> C 00:16:55.030 --> 00:16:55.040 align:start position:0% V 2504 and also constrained by the gas C 00:16:55.040 --> 00:16:57.069 align:start position:0% V 2504 and also constrained by the gas C costs<00:16:55.720> so<00:16:56.000> we<00:16:56.240> had<00:16:56.440> to<00:16:56.519> do<00:16:56.680> a<00:16:56.759> bit<00:16:56.880> of 00:16:57.069 --> 00:16:57.079 align:start position:0% costs so we had to do a bit of 00:16:57.079 --> 00:16:59.629 align:start position:0% costs so we had to do a bit of gymnastics<00:16:58.000> to<00:16:58.160> fit<00:16:58.480> this<00:16:59.000> so<00:16:59.199> this<00:16:59.319> is<00:16:59.440> like<00:16:59.560> a 00:16:59.629 --> 00:16:59.639 align:start position:0% gymnastics to fit this so this is like a 00:16:59.639 --> 00:17:01.870 align:start position:0% gymnastics to fit this so this is like a very<00:16:59.839> high<00:17:00.040> level<00:17:00.519> idea<00:17:00.880> so<00:17:01.360> we<00:17:01.480> are<00:17:01.600> using 00:17:01.870 --> 00:17:01.880 align:start position:0% very high level idea so we are using 00:17:01.880 --> 00:17:04.069 align:start position:0% very high level idea so we are using cycle<00:17:02.160> fold<00:17:02.399> we<00:17:02.480> end<00:17:02.639> up<00:17:02.800> having<00:17:03.519> um<00:17:03.800> some 00:17:04.069 --> 00:17:04.079 align:start position:0% cycle fold we end up having um some 00:17:04.079 --> 00:17:07.590 align:start position:0% cycle fold we end up having um some instances<00:17:04.559> and<00:17:04.919> what<00:17:05.079> we<00:17:05.280> do<00:17:05.600> is<00:17:06.280> we<00:17:06.880> combine 00:17:07.590 --> 00:17:07.600 align:start position:0% instances and what we do is we combine 00:17:07.600 --> 00:17:10.429 align:start position:0% instances and what we do is we combine some<00:17:08.600> uh<00:17:08.760> growth<00:17:09.039> 16<00:17:09.400> circuit<00:17:09.919> that<00:17:10.120> also 00:17:10.429 --> 00:17:10.439 align:start position:0% some uh growth 16 circuit that also 00:17:10.439 --> 00:17:11.990 align:start position:0% some uh growth 16 circuit that also contains<00:17:10.799> some<00:17:11.000> non-native<00:17:11.520> arithmetic 00:17:11.990 --> 00:17:12.000 align:start position:0% contains some non-native arithmetic 00:17:12.000 --> 00:17:14.189 align:start position:0% contains some non-native arithmetic stuff<00:17:12.799> uh<00:17:13.000> combined<00:17:13.480> with<00:17:13.640> the<00:17:13.799> KGC 00:17:14.189 --> 00:17:14.199 align:start position:0% stuff uh combined with the KGC 00:17:14.199 --> 00:17:15.510 align:start position:0% stuff uh combined with the KGC commitments<00:17:14.559> proof<00:17:14.919> so<00:17:15.039> at<00:17:15.120> the<00:17:15.199> end<00:17:15.439> in 00:17:15.510 --> 00:17:15.520 align:start position:0% commitments proof so at the end in 00:17:15.520 --> 00:17:17.350 align:start position:0% commitments proof so at the end in ethereum<00:17:15.880> we<00:17:15.959> just<00:17:16.120> verify<00:17:16.559> one<00:17:16.720> growth<00:17:16.959> 16 00:17:17.350 --> 00:17:17.360 align:start position:0% ethereum we just verify one growth 16 00:17:17.360 --> 00:17:19.230 align:start position:0% ethereum we just verify one growth 16 and<00:17:17.480> two<00:17:17.640> kg<00:17:18.000> commitments<00:17:18.720> for<00:17:18.880> the<00:17:19.000> case<00:17:19.160> of 00:17:19.230 --> 00:17:19.240 align:start position:0% and two kg commitments for the case of 00:17:19.240 --> 00:17:22.150 align:start position:0% and two kg commitments for the case of Nova<00:17:19.520> for<00:17:19.679> example<00:17:20.640> um<00:17:21.240> so<00:17:21.640> this<00:17:21.839> is<00:17:22.000> very 00:17:22.150 --> 00:17:22.160 align:start position:0% Nova for example um so this is very 00:17:22.160 --> 00:17:26.549 align:start position:0% Nova for example um so this is very suene<00:17:22.640> and<00:17:23.280> cheap<00:17:23.799> in<00:17:23.919> terms<00:17:24.160> of<00:17:24.360> gas<00:17:24.640> costs<00:17:25.640> um 00:17:26.549 --> 00:17:26.559 align:start position:0% suene and cheap in terms of gas costs um 00:17:26.559 --> 00:17:28.429 align:start position:0% suene and cheap in terms of gas costs um and<00:17:26.720> also<00:17:27.160> yes<00:17:27.480> so<00:17:27.600> you<00:17:27.679> can<00:17:27.839> generate<00:17:28.160> the 00:17:28.429 --> 00:17:28.439 align:start position:0% and also yes so you can generate the 00:17:28.439 --> 00:17:30.750 align:start position:0% and also yes so you can generate the solidity<00:17:28.919> Cote<00:17:29.120> also<00:17:29.320> from<00:17:29.559> from<00:17:29.679> the<00:17:29.799> library 00:17:30.750 --> 00:17:30.760 align:start position:0% solidity Cote also from from the library 00:17:30.760 --> 00:17:34.669 align:start position:0% solidity Cote also from from the library um<00:17:31.679> so<00:17:32.679> uh<00:17:32.799> to<00:17:32.960> to<00:17:33.320> wrap<00:17:33.600> up<00:17:33.760> some<00:17:34.000> preliminary 00:17:34.669 --> 00:17:34.679 align:start position:0% um so uh to to wrap up some preliminary 00:17:34.679 --> 00:17:37.830 align:start position:0% um so uh to to wrap up some preliminary numbers<00:17:35.559> uh<00:17:35.760> just<00:17:35.960> as<00:17:36.080> a<00:17:36.400> remark<00:17:36.799> um<00:17:37.400> until<00:17:37.679> now 00:17:37.830 --> 00:17:37.840 align:start position:0% numbers uh just as a remark um until now 00:17:37.840 --> 00:17:39.710 align:start position:0% numbers uh just as a remark um until now we've<00:17:38.000> been<00:17:38.160> focusing<00:17:38.520> on<00:17:39.039> implementing<00:17:39.600> the 00:17:39.710 --> 00:17:39.720 align:start position:0% we've been focusing on implementing the 00:17:39.720 --> 00:17:41.390 align:start position:0% we've been focusing on implementing the various<00:17:39.919> folding<00:17:40.280> schemes<00:17:40.960> not<00:17:41.160> on 00:17:41.390 --> 00:17:41.400 align:start position:0% various folding schemes not on 00:17:41.400 --> 00:17:43.270 align:start position:0% various folding schemes not on optimizing<00:17:42.000> so<00:17:42.280> that's<00:17:42.480> why<00:17:42.760> now<00:17:42.880> so<00:17:43.039> now<00:17:43.160> we 00:17:43.270 --> 00:17:43.280 align:start position:0% optimizing so that's why now so now we 00:17:43.280 --> 00:17:45.150 align:start position:0% optimizing so that's why now so now we have<00:17:43.440> the<00:17:43.600> Nova<00:17:43.880> hypernova<00:17:44.280> and<00:17:44.360> Proto<00:17:44.559> Galaxy 00:17:45.150 --> 00:17:45.160 align:start position:0% have the Nova hypernova and Proto Galaxy 00:17:45.160 --> 00:17:47.390 align:start position:0% have the Nova hypernova and Proto Galaxy all<00:17:45.320> of<00:17:45.440> them<00:17:45.600> using<00:17:45.919> cycle<00:17:46.240> fold<00:17:46.960> um<00:17:47.200> we've 00:17:47.390 --> 00:17:47.400 align:start position:0% all of them using cycle fold um we've 00:17:47.400 --> 00:17:49.909 align:start position:0% all of them using cycle fold um we've not<00:17:47.520> been<00:17:47.679> focusing<00:17:48.120> on<00:17:48.880> optimization<00:17:49.520> and 00:17:49.909 --> 00:17:49.919 align:start position:0% not been focusing on optimization and 00:17:49.919 --> 00:17:52.909 align:start position:0% not been focusing on optimization and efficiency<00:17:50.919> um<00:17:51.320> but<00:17:52.200> looks<00:17:52.480> like<00:17:52.679> the<00:17:52.799> the 00:17:52.909 --> 00:17:52.919 align:start position:0% efficiency um but looks like the the 00:17:52.919 --> 00:17:54.310 align:start position:0% efficiency um but looks like the the current<00:17:53.120> numbers<00:17:53.360> that<00:17:53.480> we<00:17:53.600> have<00:17:53.760> when<00:17:53.960> we 00:17:54.310 --> 00:17:54.320 align:start position:0% current numbers that we have when we 00:17:54.320 --> 00:17:56.470 align:start position:0% current numbers that we have when we Rand<00:17:54.720> some<00:17:55.039> preliminary<00:17:55.600> benchmarks<00:17:56.360> they 00:17:56.470 --> 00:17:56.480 align:start position:0% Rand some preliminary benchmarks they 00:17:56.480 --> 00:17:59.230 align:start position:0% Rand some preliminary benchmarks they look<00:17:56.919> promising<00:17:57.919> um<00:17:58.240> and<00:17:58.360> and<00:17:58.480> the<00:17:58.600> next<00:17:58.960> steps 00:17:59.230 --> 00:17:59.240 align:start position:0% look promising um and and the next steps 00:17:59.240 --> 00:18:01.110 align:start position:0% look promising um and and the next steps will<00:17:59.400> be<00:17:59.520> to<00:17:59.880> start<00:18:00.200> profiling<00:18:00.640> optimizing 00:18:01.110 --> 00:18:01.120 align:start position:0% will be to start profiling optimizing 00:18:01.120 --> 00:18:02.950 align:start position:0% will be to start profiling optimizing and<00:18:01.240> adding<00:18:01.440> benchmarks<00:18:01.919> and<00:18:02.280> like<00:18:02.400> stopping 00:18:02.950 --> 00:18:02.960 align:start position:0% and adding benchmarks and like stopping 00:18:02.960 --> 00:18:06.990 align:start position:0% and adding benchmarks and like stopping adding<00:18:03.960> new<00:18:04.520> papers<00:18:04.919> that<00:18:05.480> are<00:18:05.799> appearing<00:18:06.559> and 00:18:06.990 --> 00:18:07.000 align:start position:0% adding new papers that are appearing and 00:18:07.000 --> 00:18:09.270 align:start position:0% adding new papers that are appearing and focus<00:18:07.320> for<00:18:07.679> few<00:18:07.880> months<00:18:08.159> to<00:18:08.600> like<00:18:08.760> optimizing 00:18:09.270 --> 00:18:09.280 align:start position:0% focus for few months to like optimizing 00:18:09.280 --> 00:18:10.909 align:start position:0% focus for few months to like optimizing things<00:18:09.520> and<00:18:09.640> making<00:18:09.960> them<00:18:10.320> a<00:18:10.400> bit<00:18:10.559> more<00:18:10.720> fast 00:18:10.909 --> 00:18:10.919 align:start position:0% things and making them a bit more fast 00:18:10.919 --> 00:18:12.750 align:start position:0% things and making them a bit more fast and<00:18:11.080> paralyzing<00:18:11.679> and<00:18:11.880> and<00:18:12.000> so<00:18:12.159> on<00:18:12.480> and<00:18:12.600> then 00:18:12.750 --> 00:18:12.760 align:start position:0% and paralyzing and and so on and then 00:18:12.760 --> 00:18:15.190 align:start position:0% and paralyzing and and so on and then getting<00:18:12.960> to<00:18:13.080> a<00:18:13.159> f<00:18:13.480> release<00:18:14.000> because<00:18:14.720> until<00:18:14.960> now 00:18:15.190 --> 00:18:15.200 align:start position:0% getting to a f release because until now 00:18:15.200 --> 00:18:18.390 align:start position:0% getting to a f release because until now is<00:18:15.480> just<00:18:15.679> like<00:18:16.240> commit<00:18:16.520> after<00:18:16.799> commit<00:18:17.280> and<00:18:18.280> the 00:18:18.390 --> 00:18:18.400 align:start position:0% is just like commit after commit and the 00:18:18.400 --> 00:18:20.710 align:start position:0% is just like commit after commit and the interface<00:18:18.840> might<00:18:19.159> break<00:18:19.880> so<00:18:20.320> some 00:18:20.710 --> 00:18:20.720 align:start position:0% interface might break so some 00:18:20.720 --> 00:18:22.909 align:start position:0% interface might break so some unoptimized<00:18:21.440> preliminary<00:18:21.960> numbers<00:18:22.559> so<00:18:22.799> each 00:18:22.909 --> 00:18:22.919 align:start position:0% unoptimized preliminary numbers so each 00:18:22.919 --> 00:18:24.310 align:start position:0% unoptimized preliminary numbers so each folding<00:18:23.320> step<00:18:23.559> this<00:18:23.640> is<00:18:23.760> the<00:18:23.880> recursive 00:18:24.310 --> 00:18:24.320 align:start position:0% folding step this is the recursive 00:18:24.320 --> 00:18:26.470 align:start position:0% folding step this is the recursive iteration<00:18:25.200> uh<00:18:25.280> for<00:18:25.400> a<00:18:25.520> minimal<00:18:25.799> circuit<00:18:26.400> it 00:18:26.470 --> 00:18:26.480 align:start position:0% iteration uh for a minimal circuit it 00:18:26.480 --> 00:18:29.390 align:start position:0% iteration uh for a minimal circuit it takes<00:18:26.720> like<00:18:26.880> 300<00:18:27.440> milliseconds<00:18:28.440> um 00:18:29.390 --> 00:18:29.400 align:start position:0% takes like 300 milliseconds um 00:18:29.400 --> 00:18:31.710 align:start position:0% takes like 300 milliseconds um this<00:18:29.520> is<00:18:30.480> there<00:18:30.559> is<00:18:30.720> this<00:18:30.840> overhead<00:18:31.280> of<00:18:31.480> the 00:18:31.710 --> 00:18:31.720 align:start position:0% this is there is this overhead of the 00:18:31.720 --> 00:18:36.310 align:start position:0% this is there is this overhead of the the<00:18:31.880> fixed<00:18:32.240> cost<00:18:32.480> of<00:18:32.640> the<00:18:32.919> five<00:18:33.559> 50,000<00:18:34.559> uh<00:18:35.400> uh 00:18:36.310 --> 00:18:36.320 align:start position:0% the fixed cost of the five 50,000 uh uh 00:18:36.320 --> 00:18:40.270 align:start position:0% the fixed cost of the five 50,000 uh uh sorry<00:18:36.559> 50,000<00:18:37.280> a1cs<00:18:37.960> constraints<00:18:38.960> um<00:18:39.880> then 00:18:40.270 --> 00:18:40.280 align:start position:0% sorry 50,000 a1cs constraints um then 00:18:40.280 --> 00:18:42.789 align:start position:0% sorry 50,000 a1cs constraints um then when<00:18:40.679> but<00:18:40.799> so<00:18:41.080> it<00:18:41.200> Tak<00:18:41.520> this<00:18:41.720> like<00:18:41.880> about<00:18:42.360> uh 00:18:42.789 --> 00:18:42.799 align:start position:0% when but so it Tak this like about uh 00:18:42.799 --> 00:18:45.710 align:start position:0% when but so it Tak this like about uh 300<00:18:43.240> milliseconds<00:18:43.799> on<00:18:43.919> a<00:18:44.280> like<00:18:44.600> uh<00:18:45.280> today's 00:18:45.710 --> 00:18:45.720 align:start position:0% 300 milliseconds on a like uh today's 00:18:45.720 --> 00:18:50.830 align:start position:0% 300 milliseconds on a like uh today's laptop<00:18:46.480> then<00:18:47.480> when<00:18:47.720> you<00:18:48.000> want<00:18:48.240> to<00:18:49.400> um<00:18:50.400> prove 00:18:50.830 --> 00:18:50.840 align:start position:0% laptop then when you want to um prove 00:18:50.840 --> 00:18:52.830 align:start position:0% laptop then when you want to um prove offchain<00:18:51.280> the<00:18:51.440> decider<00:18:52.000> and<00:18:52.159> Kur<00:18:52.520> takes<00:18:52.679> less 00:18:52.830 --> 00:18:52.840 align:start position:0% offchain the decider and Kur takes less 00:18:52.840 --> 00:18:55.230 align:start position:0% offchain the decider and Kur takes less than<00:18:52.960> one<00:18:53.080> minute<00:18:53.440> it<00:18:53.559> should<00:18:53.760> be<00:18:53.960> much<00:18:54.320> less 00:18:55.230 --> 00:18:55.240 align:start position:0% than one minute it should be much less 00:18:55.240 --> 00:18:57.430 align:start position:0% than one minute it should be much less uh<00:18:55.440> but<00:18:55.640> it's<00:18:55.799> just<00:18:56.000> that<00:18:56.480> we<00:18:56.559> are<00:18:56.720> using<00:18:57.080> pting 00:18:57.430 --> 00:18:57.440 align:start position:0% uh but it's just that we are using pting 00:18:57.440 --> 00:19:01.070 align:start position:0% uh but it's just that we are using pting based<00:18:57.760> snarks<00:18:58.200> on<00:18:58.480> both<00:18:58.880> both<00:18:59.880> sides<00:19:00.120> of<00:19:00.280> the<00:19:00.520> C 00:19:01.070 --> 00:19:01.080 align:start position:0% based snarks on both both sides of the C 00:19:01.080 --> 00:19:03.029 align:start position:0% based snarks on both both sides of the C cycle<00:19:01.600> the<00:19:01.720> idea<00:19:01.960> is<00:19:02.039> that<00:19:02.240> this<00:19:02.400> should<00:19:02.679> be 00:19:03.029 --> 00:19:03.039 align:start position:0% cycle the idea is that this should be 00:19:03.039 --> 00:19:05.029 align:start position:0% cycle the idea is that this should be using<00:19:03.559> Spartan<00:19:04.000> at<00:19:04.120> some<00:19:04.280> point<00:19:04.720> and<00:19:04.880> the 00:19:05.029 --> 00:19:05.039 align:start position:0% using Spartan at some point and the 00:19:05.039 --> 00:19:06.430 align:start position:0% using Spartan at some point and the modified<00:19:05.440> version<00:19:05.679> of<00:19:05.799> Spartan<00:19:06.159> that<00:19:06.240> uses 00:19:06.430 --> 00:19:06.440 align:start position:0% modified version of Spartan that uses 00:19:06.440 --> 00:19:08.590 align:start position:0% modified version of Spartan that uses the<00:19:06.520> relaxer<00:19:06.919> 1cs<00:19:07.480> so<00:19:07.640> then<00:19:07.799> it<00:19:07.919> should<00:19:08.159> be 00:19:08.590 --> 00:19:08.600 align:start position:0% the relaxer 1cs so then it should be 00:19:08.600 --> 00:19:10.950 align:start position:0% the relaxer 1cs so then it should be also<00:19:08.919> quite<00:19:09.200> efficient<00:19:10.120> um<00:19:10.440> and<00:19:10.559> then<00:19:10.679> for<00:19:10.840> the 00:19:10.950 --> 00:19:10.960 align:start position:0% also quite efficient um and then for the 00:19:10.960 --> 00:19:12.830 align:start position:0% also quite efficient um and then for the offchain<00:19:11.320> decider<00:19:11.720> which<00:19:11.840> is<00:19:12.440> one<00:19:12.600> of<00:19:12.720> the 00:19:12.830 --> 00:19:12.840 align:start position:0% offchain decider which is one of the 00:19:12.840 --> 00:19:15.230 align:start position:0% offchain decider which is one of the main<00:19:13.120> contributions<00:19:13.600> from<00:19:13.760> sonov<00:19:14.600> um<00:19:14.960> we<00:19:15.080> have 00:19:15.230 --> 00:19:15.240 align:start position:0% main contributions from sonov um we have 00:19:15.240 --> 00:19:16.710 align:start position:0% main contributions from sonov um we have this<00:19:15.400> big<00:19:15.600> circuit<00:19:15.960> at<00:19:16.080> the<00:19:16.159> end<00:19:16.400> that<00:19:16.520> does 00:19:16.710 --> 00:19:16.720 align:start position:0% this big circuit at the end that does 00:19:16.720 --> 00:19:18.669 align:start position:0% this big circuit at the end that does this<00:19:16.960> gymnastics<00:19:17.440> and<00:19:17.679> non-native 00:19:18.669 --> 00:19:18.679 align:start position:0% this gymnastics and non-native 00:19:18.679 --> 00:19:20.549 align:start position:0% this gymnastics and non-native arithmetic<00:19:19.200> stuff<00:19:19.520> to<00:19:19.799> fit<00:19:20.080> into<00:19:20.320> the 00:19:20.549 --> 00:19:20.559 align:start position:0% arithmetic stuff to fit into the 00:19:20.559 --> 00:19:23.190 align:start position:0% arithmetic stuff to fit into the ethereum<00:19:21.440> uh<00:19:21.600> curve<00:19:22.320> um<00:19:22.520> that<00:19:22.760> it<00:19:22.840> takes<00:19:23.080> less 00:19:23.190 --> 00:19:23.200 align:start position:0% ethereum uh curve um that it takes less 00:19:23.200 --> 00:19:25.350 align:start position:0% ethereum uh curve um that it takes less than<00:19:23.320> 3<00:19:23.480> minutes<00:19:23.799> in<00:19:23.960> in<00:19:24.080> a<00:19:24.280> like<00:19:24.720> in<00:19:24.799> a<00:19:25.159> in<00:19:25.240> my 00:19:25.350 --> 00:19:25.360 align:start position:0% than 3 minutes in in a like in a in my 00:19:25.360 --> 00:19:27.750 align:start position:0% than 3 minutes in in a like in a in my ThinkPad<00:19:26.080> uh<00:19:26.200> and<00:19:26.320> the<00:19:26.440> gas<00:19:26.600> costs<00:19:26.880> are<00:19:27.120> 800k 00:19:27.750 --> 00:19:27.760 align:start position:0% ThinkPad uh and the gas costs are 800k 00:19:27.760 --> 00:19:30.390 align:start position:0% ThinkPad uh and the gas costs are 800k of<00:19:27.880> gas<00:19:28.039> mostly<00:19:28.280> from<00:19:28.480> GR<00:19:28.919> 16<00:19:29.159> proofs<00:19:29.520> and<00:19:29.679> kg 00:19:30.390 --> 00:19:30.400 align:start position:0% of gas mostly from GR 16 proofs and kg 00:19:30.400 --> 00:19:32.669 align:start position:0% of gas mostly from GR 16 proofs and kg proof<00:19:31.159> um<00:19:31.400> well<00:19:31.559> one<00:19:31.720> growth<00:19:31.960> 16<00:19:32.200> and<00:19:32.280> two<00:19:32.400> kg 00:19:32.669 --> 00:19:32.679 align:start position:0% proof um well one growth 16 and two kg 00:19:32.679 --> 00:19:34.310 align:start position:0% proof um well one growth 16 and two kg proof<00:19:32.880> in<00:19:32.960> case<00:19:33.120> of<00:19:33.200> Nova<00:19:33.840> uh<00:19:33.960> the<00:19:34.039> idea<00:19:34.240> is 00:19:34.310 --> 00:19:34.320 align:start position:0% proof in case of Nova uh the idea is 00:19:34.320 --> 00:19:36.350 align:start position:0% proof in case of Nova uh the idea is that<00:19:34.480> this<00:19:34.600> should<00:19:34.840> be<00:19:35.480> reduced<00:19:35.840> to<00:19:36.039> less<00:19:36.200> than 00:19:36.350 --> 00:19:36.360 align:start position:0% that this should be reduced to less than 00:19:36.360 --> 00:19:38.590 align:start position:0% that this should be reduced to less than 500<00:19:36.880> with<00:19:37.000> some<00:19:37.200> tricks<00:19:37.520> of<00:19:37.640> the<00:19:37.760> hashing<00:19:38.200> and 00:19:38.590 --> 00:19:38.600 align:start position:0% 500 with some tricks of the hashing and 00:19:38.600 --> 00:19:41.549 align:start position:0% 500 with some tricks of the hashing and of<00:19:38.679> the<00:19:38.760> bound<00:19:39.080> inputs<00:19:39.400> and<00:19:39.600> and<00:19:39.760> of<00:19:39.919> the<00:19:40.600> um<00:19:41.360> um 00:19:41.549 --> 00:19:41.559 align:start position:0% of the bound inputs and and of the um um 00:19:41.559 --> 00:19:44.430 align:start position:0% of the bound inputs and and of the um um combinations<00:19:42.000> of<00:19:42.120> pings<00:19:43.039> um<00:19:43.559> yeah<00:19:43.919> so<00:19:44.159> just<00:19:44.320> as 00:19:44.430 --> 00:19:44.440 align:start position:0% combinations of pings um yeah so just as 00:19:44.440 --> 00:19:47.149 align:start position:0% combinations of pings um yeah so just as a<00:19:44.679> wrap<00:19:44.919> up<00:19:45.360> uh<00:19:45.559> main<00:19:45.880> takeaways<00:19:46.440> that<00:19:46.600> you<00:19:46.960> can 00:19:47.149 --> 00:19:47.159 align:start position:0% a wrap up uh main takeaways that you can 00:19:47.159 --> 00:19:49.549 align:start position:0% a wrap up uh main takeaways that you can get<00:19:47.320> from<00:19:47.600> from<00:19:47.720> this<00:19:47.880> t<00:19:48.679> uh<00:19:49.120> first<00:19:49.320> of<00:19:49.440> all 00:19:49.549 --> 00:19:49.559 align:start position:0% get from from this t uh first of all 00:19:49.559 --> 00:19:51.029 align:start position:0% get from from this t uh first of all folding<00:19:49.880> schemes<00:19:50.159> are<00:19:50.280> not<00:19:50.440> a<00:19:50.559> tool<00:19:50.720> that<00:19:50.840> fits 00:19:51.029 --> 00:19:51.039 align:start position:0% folding schemes are not a tool that fits 00:19:51.039 --> 00:19:52.789 align:start position:0% folding schemes are not a tool that fits in<00:19:51.159> all<00:19:51.280> the<00:19:51.360> use<00:19:51.600> cases<00:19:51.880> but<00:19:52.159> when<00:19:52.480> when<00:19:52.640> it 00:19:52.789 --> 00:19:52.799 align:start position:0% in all the use cases but when when it 00:19:52.799 --> 00:19:54.710 align:start position:0% in all the use cases but when when it fits<00:19:53.120> into<00:19:53.400> some<00:19:53.600> use<00:19:53.840> case<00:19:54.000> that<00:19:54.120> you<00:19:54.240> have<00:19:54.360> a 00:19:54.710 --> 00:19:54.720 align:start position:0% fits into some use case that you have a 00:19:54.720 --> 00:19:55.710 align:start position:0% fits into some use case that you have a something<00:19:55.039> that<00:19:55.159> is<00:19:55.280> like<00:19:55.440> the<00:19:55.520> same 00:19:55.710 --> 00:19:55.720 align:start position:0% something that is like the same 00:19:55.720 --> 00:19:57.950 align:start position:0% something that is like the same structure<00:19:56.080> of<00:19:56.159> the<00:19:56.280> circuit<00:19:56.880> very<00:19:57.080> repetitive 00:19:57.950 --> 00:19:57.960 align:start position:0% structure of the circuit very repetitive 00:19:57.960 --> 00:20:00.990 align:start position:0% structure of the circuit very repetitive and<00:19:58.120> and<00:19:58.280> done<00:19:59.120> uh<00:19:59.400> a<00:19:59.520> lot<00:19:59.679> of<00:19:59.840> times<00:20:00.600> uh<00:20:00.799> again 00:20:00.990 --> 00:20:01.000 align:start position:0% and and done uh a lot of times uh again 00:20:01.000 --> 00:20:03.070 align:start position:0% and and done uh a lot of times uh again and<00:20:01.159> again<00:20:01.360> and<00:20:01.520> again<00:20:01.799> then<00:20:02.080> folding 00:20:03.070 --> 00:20:03.080 align:start position:0% and again and again then folding 00:20:03.080 --> 00:20:05.390 align:start position:0% and again and again then folding presents<00:20:03.480> a<00:20:03.760> big<00:20:04.159> uh<00:20:04.280> speed<00:20:04.559> up<00:20:04.880> compared<00:20:05.240> to 00:20:05.390 --> 00:20:05.400 align:start position:0% presents a big uh speed up compared to 00:20:05.400 --> 00:20:08.390 align:start position:0% presents a big uh speed up compared to full<00:20:05.640> recursion<00:20:06.159> of<00:20:06.799> other<00:20:07.360> approaches<00:20:08.240> and 00:20:08.390 --> 00:20:08.400 align:start position:0% full recursion of other approaches and 00:20:08.400 --> 00:20:10.510 align:start position:0% full recursion of other approaches and then<00:20:08.799> uh<00:20:08.960> well<00:20:09.080> some<00:20:09.240> of<00:20:09.360> is<00:20:09.520> experimental<00:20:10.360> uh 00:20:10.510 --> 00:20:10.520 align:start position:0% then uh well some of is experimental uh 00:20:10.520 --> 00:20:12.350 align:start position:0% then uh well some of is experimental uh the<00:20:10.600> schemes<00:20:10.919> that<00:20:11.080> we<00:20:11.280> have<00:20:11.559> and<00:20:11.919> we<00:20:12.080> have<00:20:12.240> the 00:20:12.350 --> 00:20:12.360 align:start position:0% the schemes that we have and we have the 00:20:12.360 --> 00:20:14.669 align:start position:0% the schemes that we have and we have the onchain<00:20:12.720> verification<00:20:13.559> and<00:20:13.799> preliminary<00:20:14.400> V 00:20:14.669 --> 00:20:14.679 align:start position:0% onchain verification and preliminary V 00:20:14.679 --> 00:20:16.830 align:start position:0% onchain verification and preliminary V marks<00:20:14.880> look<00:20:15.080> promising<00:20:15.840> and<00:20:16.000> the<00:20:16.120> next<00:20:16.360> steps 00:20:16.830 --> 00:20:16.840 align:start position:0% marks look promising and the next steps 00:20:16.840 --> 00:20:18.870 align:start position:0% marks look promising and the next steps uh<00:20:16.960> in<00:20:17.080> the<00:20:17.159> short<00:20:17.400> term<00:20:17.600> is<00:20:17.760> to<00:20:18.080> optimize<00:20:18.640> and 00:20:18.870 --> 00:20:18.880 align:start position:0% uh in the short term is to optimize and 00:20:18.880 --> 00:20:22.190 align:start position:0% uh in the short term is to optimize and and<00:20:19.200> Benchmark<00:20:19.720> well<00:20:20.000> and<00:20:20.919> um<00:20:21.440> do<00:20:21.720> me<00:20:21.880> memory 00:20:22.190 --> 00:20:22.200 align:start position:0% and Benchmark well and um do me memory 00:20:22.200 --> 00:20:27.100 align:start position:0% and Benchmark well and um do me memory profiling<00:20:22.600> and<00:20:22.840> and<00:20:22.960> so<00:20:23.120> on<00:20:23.760> and<00:20:23.919> that's<00:20:24.120> it 00:20:27.100 --> 00:20:27.110 align:start position:0% profiling and and so on and that's it 00:20:27.110 --> 00:20:29.470 align:start position:0% profiling and and so on and that's it [Applause] 00:20:29.470 --> 00:20:29.480 align:start position:0% [Applause] 00:20:29.480 --> 00:20:32.270 align:start position:0% [Applause] cool<00:20:29.760> cool 00:20:32.270 --> 00:20:32.280 align:start position:0% cool cool 00:20:32.280 --> 00:20:35.830 align:start position:0% cool cool gra<00:20:33.360> um<00:20:34.360> yeah<00:20:34.480> so<00:20:34.640> I<00:20:34.799> personally<00:20:35.280> actually<00:20:35.559> use 00:20:35.830 --> 00:20:35.840 align:start position:0% gra um yeah so I personally actually use 00:20:35.840 --> 00:20:38.669 align:start position:0% gra um yeah so I personally actually use son<00:20:36.280> and<00:20:36.400> I<00:20:36.520> can<00:20:36.720> tell<00:20:36.960> that<00:20:37.080> it<00:20:37.200> is<00:20:37.679> quite 00:20:38.669 --> 00:20:38.679 align:start position:0% son and I can tell that it is quite 00:20:38.679 --> 00:20:41.029 align:start position:0% son and I can tell that it is quite generic<00:20:39.159> and<00:20:39.320> also<00:20:39.559> easy<00:20:39.760> to<00:20:39.919> use<00:20:40.440> so<00:20:40.799> if<00:20:40.919> we 00:20:41.029 --> 00:20:41.039 align:start position:0% generic and also easy to use so if we 00:20:41.039 --> 00:20:43.909 align:start position:0% generic and also easy to use so if we take<00:20:41.240> some<00:20:41.640> questions<00:20:42.640> so<00:20:42.840> the<00:20:43.000> most<00:20:43.360> upvoted 00:20:43.909 --> 00:20:43.919 align:start position:0% take some questions so the most upvoted 00:20:43.919 --> 00:20:46.310 align:start position:0% take some questions so the most upvoted one<00:20:44.080> is<00:20:44.200> the<00:20:44.360> first<00:20:44.559> one<00:20:45.200> so<00:20:45.400> folding<00:20:45.840> schemes 00:20:46.310 --> 00:20:46.320 align:start position:0% one is the first one so folding schemes 00:20:46.320 --> 00:20:48.470 align:start position:0% one is the first one so folding schemes initially<00:20:46.720> gained<00:20:47.000> a<00:20:47.120> lot<00:20:47.320> of<00:20:47.520> attention<00:20:48.240> but 00:20:48.470 --> 00:20:48.480 align:start position:0% initially gained a lot of attention but 00:20:48.480 --> 00:20:50.789 align:start position:0% initially gained a lot of attention but we<00:20:48.640> haven't<00:20:48.919> seen<00:20:49.280> many<00:20:49.600> advantages<00:20:50.559> in 00:20:50.789 --> 00:20:50.799 align:start position:0% we haven't seen many advantages in 00:20:50.799 --> 00:20:52.510 align:start position:0% we haven't seen many advantages in Practical<00:20:51.240> implementation<00:20:51.799> against<00:20:52.159> stocks 00:20:52.510 --> 00:20:52.520 align:start position:0% Practical implementation against stocks 00:20:52.520 --> 00:20:54.590 align:start position:0% Practical implementation against stocks can<00:20:52.679> you<00:20:52.799> compare<00:20:53.200> them<00:20:53.559> with<00:20:53.760> stocks<00:20:54.400> and 00:20:54.590 --> 00:20:54.600 align:start position:0% can you compare them with stocks and 00:20:54.600 --> 00:20:57.390 align:start position:0% can you compare them with stocks and what<00:20:54.760> are<00:20:55.000> the<00:20:55.480> advantages<00:20:56.480> quite<00:20:56.720> opiniated 00:20:57.390 --> 00:20:57.400 align:start position:0% what are the advantages quite opiniated 00:20:57.400 --> 00:21:01.190 align:start position:0% what are the advantages quite opiniated question<00:20:57.760> right<00:20:58.320> yeah<00:20:58.840> so<00:20:59.840> who<00:21:00.640> one<00:21:00.799> of<00:21:00.960> the 00:21:01.190 --> 00:21:01.200 align:start position:0% question right yeah so who one of the 00:21:01.200 --> 00:21:02.870 align:start position:0% question right yeah so who one of the perspectives<00:21:01.760> that<00:21:01.880> we<00:21:02.039> have<00:21:02.200> on<00:21:02.400> on<00:21:02.520> folding 00:21:02.870 --> 00:21:02.880 align:start position:0% perspectives that we have on on folding 00:21:02.880 --> 00:21:05.070 align:start position:0% perspectives that we have on on folding schemes<00:21:03.200> in<00:21:03.280> general<00:21:03.720> is<00:21:03.880> that<00:21:04.080> is<00:21:04.240> not<00:21:04.480> this 00:21:05.070 --> 00:21:05.080 align:start position:0% schemes in general is that is not this 00:21:05.080 --> 00:21:07.350 align:start position:0% schemes in general is that is not this tool<00:21:05.679> that<00:21:05.880> fits<00:21:06.240> into<00:21:06.480> all<00:21:06.640> use<00:21:06.919> cases<00:21:07.200> like 00:21:07.350 --> 00:21:07.360 align:start position:0% tool that fits into all use cases like 00:21:07.360 --> 00:21:08.830 align:start position:0% tool that fits into all use cases like the<00:21:07.480> same<00:21:07.679> Hammer<00:21:08.000> that<00:21:08.120> you<00:21:08.200> can<00:21:08.360> use<00:21:08.559> on 00:21:08.830 --> 00:21:08.840 align:start position:0% the same Hammer that you can use on 00:21:08.840 --> 00:21:11.549 align:start position:0% the same Hammer that you can use on everything<00:21:09.760> uh<00:21:09.919> it's<00:21:10.159> very<00:21:10.559> kind<00:21:10.679> of<00:21:10.960> specific 00:21:11.549 --> 00:21:11.559 align:start position:0% everything uh it's very kind of specific 00:21:11.559 --> 00:21:14.269 align:start position:0% everything uh it's very kind of specific and<00:21:12.200> like<00:21:12.559> uh<00:21:12.919> spe<00:21:13.279> specifically<00:21:13.679> in<00:21:13.760> son<00:21:14.159> we 00:21:14.269 --> 00:21:14.279 align:start position:0% and like uh spe specifically in son we 00:21:14.279 --> 00:21:17.590 align:start position:0% and like uh spe specifically in son we have<00:21:14.440> this<00:21:14.840> IBC<00:21:15.600> uh<00:21:15.720> model<00:21:16.440> so<00:21:16.760> this<00:21:17.320> you<00:21:17.520> you 00:21:17.590 --> 00:21:17.600 align:start position:0% have this IBC uh model so this you you 00:21:17.600 --> 00:21:19.830 align:start position:0% have this IBC uh model so this you you need<00:21:17.760> to<00:21:17.919> model<00:21:18.279> your<00:21:18.679> your<00:21:18.919> use<00:21:19.240> case<00:21:19.480> to<00:21:19.679> to 00:21:19.830 --> 00:21:19.840 align:start position:0% need to model your your use case to to 00:21:19.840 --> 00:21:21.990 align:start position:0% need to model your your use case to to that<00:21:20.279> so<00:21:20.799> it<00:21:20.919> will<00:21:21.120> not<00:21:21.320> fit<00:21:21.520> all<00:21:21.679> the<00:21:21.760> use 00:21:21.990 --> 00:21:22.000 align:start position:0% that so it will not fit all the use 00:21:22.000 --> 00:21:24.070 align:start position:0% that so it will not fit all the use cases<00:21:22.400> but<00:21:22.600> for<00:21:22.760> the<00:21:22.880> ones<00:21:23.120> that<00:21:23.240> it<00:21:23.360> fits<00:21:23.840> then 00:21:24.070 --> 00:21:24.080 align:start position:0% cases but for the ones that it fits then 00:21:24.080 --> 00:21:26.230 align:start position:0% cases but for the ones that it fits then it's<00:21:24.279> it's<00:21:24.480> like<00:21:24.720> it's<00:21:24.919> sub<00:21:25.400> substantially 00:21:26.230 --> 00:21:26.240 align:start position:0% it's it's like it's sub substantially 00:21:26.240 --> 00:21:27.870 align:start position:0% it's it's like it's sub substantially faster<00:21:26.600> than<00:21:26.880> doing<00:21:27.120> full<00:21:27.279> recursion<00:21:27.679> with 00:21:27.870 --> 00:21:27.880 align:start position:0% faster than doing full recursion with 00:21:27.880 --> 00:21:30.830 align:start position:0% faster than doing full recursion with Starks<00:21:28.799> uh<00:21:29.240> but<00:21:29.559> it's<00:21:29.720> not<00:21:29.960> as<00:21:30.240> as<00:21:30.440> like 00:21:30.830 --> 00:21:30.840 align:start position:0% Starks uh but it's not as as like 00:21:30.840 --> 00:21:32.750 align:start position:0% Starks uh but it's not as as like flexible<00:21:31.440> as<00:21:31.640> as<00:21:31.760> you<00:21:31.880> would<00:21:32.080> have<00:21:32.360> with<00:21:32.640> when 00:21:32.750 --> 00:21:32.760 align:start position:0% flexible as as you would have with when 00:21:32.760 --> 00:21:34.510 align:start position:0% flexible as as you would have with when you<00:21:32.880> are<00:21:33.000> doing<00:21:33.200> full<00:21:33.400> recursion<00:21:34.000> like<00:21:34.320> uh 00:21:34.510 --> 00:21:34.520 align:start position:0% you are doing full recursion like uh 00:21:34.520 --> 00:21:36.590 align:start position:0% you are doing full recursion like uh like<00:21:34.760> for<00:21:34.919> example<00:21:35.200> taking<00:21:35.440> a<00:21:35.840> plony<00:21:36.320> to 00:21:36.590 --> 00:21:36.600 align:start position:0% like for example taking a plony to 00:21:36.600 --> 00:21:38.269 align:start position:0% like for example taking a plony to Circuit<00:21:37.039> where<00:21:37.240> inside<00:21:37.600> you<00:21:37.760> verify<00:21:38.120> a 00:21:38.269 --> 00:21:38.279 align:start position:0% Circuit where inside you verify a 00:21:38.279 --> 00:21:40.029 align:start position:0% Circuit where inside you verify a previous<00:21:38.559> plit<00:21:38.880> to<00:21:39.000> proof<00:21:39.480> this<00:21:39.600> is<00:21:39.720> like<00:21:39.840> full 00:21:40.029 --> 00:21:40.039 align:start position:0% previous plit to proof this is like full 00:21:40.039 --> 00:21:42.230 align:start position:0% previous plit to proof this is like full recursion<00:21:40.919> and<00:21:41.080> so<00:21:41.360> part<00:21:41.480> of<00:21:41.600> your<00:21:41.720> circuit<00:21:42.080> is 00:21:42.230 --> 00:21:42.240 align:start position:0% recursion and so part of your circuit is 00:21:42.240 --> 00:21:43.510 align:start position:0% recursion and so part of your circuit is doing<00:21:42.480> the<00:21:42.600> full<00:21:42.799> verification<00:21:43.240> of<00:21:43.360> the 00:21:43.510 --> 00:21:43.520 align:start position:0% doing the full verification of the 00:21:43.520 --> 00:21:45.630 align:start position:0% doing the full verification of the previous<00:21:43.919> Stark<00:21:44.240> proof<00:21:45.039> uh<00:21:45.240> this<00:21:45.360> is<00:21:45.480> more 00:21:45.630 --> 00:21:45.640 align:start position:0% previous Stark proof uh this is more 00:21:45.640 --> 00:21:47.590 align:start position:0% previous Stark proof uh this is more expensive<00:21:46.279> this<00:21:46.480> is<00:21:46.600> a<00:21:46.720> bit<00:21:46.880> slower<00:21:47.279> but<00:21:47.400> it's 00:21:47.590 --> 00:21:47.600 align:start position:0% expensive this is a bit slower but it's 00:21:47.600 --> 00:21:49.950 align:start position:0% expensive this is a bit slower but it's much<00:21:47.799> more<00:21:48.039> flexible<00:21:48.919> and<00:21:49.200> and<00:21:49.360> easy<00:21:49.640> to<00:21:49.840> to 00:21:49.950 --> 00:21:49.960 align:start position:0% much more flexible and and easy to to 00:21:49.960 --> 00:21:51.909 align:start position:0% much more flexible and and easy to to manage<00:21:50.320> and<00:21:50.440> from<00:21:50.559> the<00:21:51.000> engineering<00:21:51.640> point<00:21:51.799> of 00:21:51.909 --> 00:21:51.919 align:start position:0% manage and from the engineering point of 00:21:51.919 --> 00:21:54.310 align:start position:0% manage and from the engineering point of view<00:21:52.120> also<00:21:52.640> with<00:21:52.799> folding<00:21:53.120> is<00:21:53.279> more<00:21:53.600> specific 00:21:54.310 --> 00:21:54.320 align:start position:0% view also with folding is more specific 00:21:54.320 --> 00:21:56.669 align:start position:0% view also with folding is more specific so<00:21:54.520> not<00:21:54.679> for<00:21:54.799> all<00:21:54.919> the<00:21:55.000> use<00:21:55.240> cases<00:21:55.640> but<00:21:56.480> when 00:21:56.669 --> 00:21:56.679 align:start position:0% so not for all the use cases but when 00:21:56.679 --> 00:21:58.830 align:start position:0% so not for all the use cases but when you<00:21:56.840> have<00:21:57.159> a<00:21:57.240> use<00:21:57.559> case<00:21:57.720> that<00:21:57.840> it<00:21:57.960> fits<00:21:58.279> well 00:21:58.830 --> 00:21:58.840 align:start position:0% you have a use case that it fits well 00:21:58.840 --> 00:22:00.630 align:start position:0% you have a use case that it fits well it's<00:21:59.039> it's<00:21:59.200> like<00:21:59.360> in<00:21:59.559> 300<00:21:59.960> milliseconds<00:22:00.480> you 00:22:00.630 --> 00:22:00.640 align:start position:0% it's it's like in 300 milliseconds you 00:22:00.640 --> 00:22:02.350 align:start position:0% it's it's like in 300 milliseconds you you<00:22:00.760> can<00:22:01.120> like<00:22:01.240> do<00:22:01.480> each<00:22:01.679> one<00:22:01.840> of<00:22:02.000> the 00:22:02.350 --> 00:22:02.360 align:start position:0% you can like do each one of the 00:22:02.360 --> 00:22:05.070 align:start position:0% you can like do each one of the recursive<00:22:03.360> recursive<00:22:03.760> steps<00:22:04.279> makes<00:22:04.480> sense 00:22:05.070 --> 00:22:05.080 align:start position:0% recursive recursive steps makes sense 00:22:05.080 --> 00:22:06.549 align:start position:0% recursive recursive steps makes sense maybe<00:22:05.279> you<00:22:05.360> can<00:22:05.520> also<00:22:05.679> do<00:22:05.840> folding<00:22:06.240> with 00:22:06.549 --> 00:22:06.559 align:start position:0% maybe you can also do folding with 00:22:06.559 --> 00:22:08.390 align:start position:0% maybe you can also do folding with stocks<00:22:06.919> which<00:22:07.120> takes<00:22:07.440> us<00:22:07.640> to<00:22:07.799> the<00:22:08.000> second 00:22:08.390 --> 00:22:08.400 align:start position:0% stocks which takes us to the second 00:22:08.400 --> 00:22:10.549 align:start position:0% stocks which takes us to the second question<00:22:09.080> what's<00:22:09.320> the<00:22:09.480> status<00:22:09.799> of<00:22:09.960> folding<00:22:10.360> of 00:22:10.549 --> 00:22:10.559 align:start position:0% question what's the status of folding of 00:22:10.559 --> 00:22:12.110 align:start position:0% question what's the status of folding of of 00:22:12.110 --> 00:22:12.120 align:start position:0% of 00:22:12.120 --> 00:22:15.149 align:start position:0% of stocks<00:22:13.120> so<00:22:13.400> our<00:22:13.640> team<00:22:13.880> didn't<00:22:14.360> really<00:22:14.720> work<00:22:14.960> on 00:22:15.149 --> 00:22:15.159 align:start position:0% stocks so our team didn't really work on 00:22:15.159 --> 00:22:18.310 align:start position:0% stocks so our team didn't really work on that<00:22:15.559> uh<00:22:15.840> so<00:22:16.720> maybe<00:22:16.960> you<00:22:17.080> want<00:22:17.240> to<00:22:18.000> you<00:22:18.200> have 00:22:18.310 --> 00:22:18.320 align:start position:0% that uh so maybe you want to you have 00:22:18.320 --> 00:22:20.190 align:start position:0% that uh so maybe you want to you have something<00:22:18.520> to<00:22:18.760> so<00:22:18.960> there<00:22:19.080> was<00:22:19.240> there<00:22:19.400> was<00:22:19.720> um 00:22:20.190 --> 00:22:20.200 align:start position:0% something to so there was there was um 00:22:20.200 --> 00:22:21.990 align:start position:0% something to so there was there was um some<00:22:20.440> paper<00:22:20.799> where<00:22:21.000> they<00:22:21.320> were<00:22:21.480> showing<00:22:21.840> how 00:22:21.990 --> 00:22:22.000 align:start position:0% some paper where they were showing how 00:22:22.000 --> 00:22:25.230 align:start position:0% some paper where they were showing how to<00:22:22.159> do<00:22:22.320> folding<00:22:22.799> of<00:22:23.080> starks<00:22:24.080> uh<00:22:24.360> bonded<00:22:24.840> to<00:22:25.080> a 00:22:25.230 --> 00:22:25.240 align:start position:0% to do folding of starks uh bonded to a 00:22:25.240 --> 00:22:28.230 align:start position:0% to do folding of starks uh bonded to a certain<00:22:25.720> number<00:22:25.919> of<00:22:26.240> repetitions<00:22:27.240> um<00:22:27.960> and<00:22:28.159> I 00:22:28.230 --> 00:22:28.240 align:start position:0% certain number of repetitions um and I 00:22:28.240 --> 00:22:30.669 align:start position:0% certain number of repetitions um and I think<00:22:28.559> The<00:22:28.640> Arc<00:22:28.919> paper<00:22:29.360> came<00:22:29.840> last<00:22:30.039> month<00:22:30.360> or 00:22:30.669 --> 00:22:30.679 align:start position:0% think The Arc paper came last month or 00:22:30.679 --> 00:22:32.269 align:start position:0% think The Arc paper came last month or something<00:22:30.960> like<00:22:31.120> this<00:22:31.679> I<00:22:31.760> think<00:22:31.880> the<00:22:31.960> one<00:22:32.120> was 00:22:32.269 --> 00:22:32.279 align:start position:0% something like this I think the one was 00:22:32.279 --> 00:22:34.950 align:start position:0% something like this I think the one was like<00:22:32.600> MOA<00:22:33.600> does<00:22:33.880> stocks<00:22:34.240> fold<00:22:34.480> in<00:22:34.640> or<00:22:34.840> it 00:22:34.950 --> 00:22:34.960 align:start position:0% like MOA does stocks fold in or it 00:22:34.960 --> 00:22:36.669 align:start position:0% like MOA does stocks fold in or it something<00:22:35.200> else<00:22:35.679> MOA<00:22:35.919> is<00:22:36.039> with<00:22:36.279> is<00:22:36.480> like<00:22:36.600> a 00:22:36.669 --> 00:22:36.679 align:start position:0% something else MOA is with is like a 00:22:36.679 --> 00:22:38.350 align:start position:0% something else MOA is with is like a variant<00:22:37.000> of<00:22:37.159> Nova 00:22:38.350 --> 00:22:38.360 align:start position:0% variant of Nova 00:22:38.360 --> 00:22:41.230 align:start position:0% variant of Nova okay<00:22:39.360> there<00:22:39.480> are<00:22:39.679> being<00:22:40.000> improvements<00:22:40.760> and 00:22:41.230 --> 00:22:41.240 align:start position:0% okay there are being improvements and 00:22:41.240 --> 00:22:43.950 align:start position:0% okay there are being improvements and and<00:22:41.760> so<00:22:42.120> but<00:22:42.679> so<00:22:42.919> far<00:22:43.279> uh<00:22:43.400> this<00:22:43.520> library<00:22:43.880> has 00:22:43.950 --> 00:22:43.960 align:start position:0% and so but so far uh this library has 00:22:43.960 --> 00:22:46.710 align:start position:0% and so but so far uh this library has been<00:22:44.120> focusing<00:22:44.520> on<00:22:44.679> IBC<00:22:45.440> uh<00:22:45.600> with<00:22:45.840> like<00:22:46.279> Air1 00:22:46.710 --> 00:22:46.720 align:start position:0% been focusing on IBC uh with like Air1 00:22:46.720 --> 00:22:49.870 align:start position:0% been focusing on IBC uh with like Air1 CS<00:22:47.080> or<00:22:47.200> CCS<00:22:48.000> surrounding<00:22:48.960> things<00:22:49.400> not<00:22:49.640> with 00:22:49.870 --> 00:22:49.880 align:start position:0% CS or CCS surrounding things not with 00:22:49.880 --> 00:22:51.710 align:start position:0% CS or CCS surrounding things not with with<00:22:50.039> Starks<00:22:50.640> the<00:22:50.760> same<00:22:50.919> for<00:22:51.120> ltis<00:22:51.400> fault<00:22:51.640> I 00:22:51.710 --> 00:22:51.720 align:start position:0% with Starks the same for ltis fault I 00:22:51.720 --> 00:22:54.870 align:start position:0% with Starks the same for ltis fault I see<00:22:52.240> next<00:22:52.520> question<00:22:52.880> regarding<00:22:53.279> to<00:22:53.440> ltis<00:22:54.200> ltis 00:22:54.870 --> 00:22:54.880 align:start position:0% see next question regarding to ltis ltis 00:22:54.880 --> 00:22:57.110 align:start position:0% see next question regarding to ltis ltis also<00:22:55.080> requires<00:22:55.440> a<00:22:55.640> different<00:22:56.240> like<00:22:56.559> uh<00:22:56.679> so<00:22:57.000> you 00:22:57.110 --> 00:22:57.120 align:start position:0% also requires a different like uh so you 00:22:57.120 --> 00:22:59.789 align:start position:0% also requires a different like uh so you work<00:22:57.360> over<00:22:57.640> the<00:22:58.080> uh<00:22:58.559> of<00:22:58.640> polinomial<00:22:59.240> and<00:22:59.640> not 00:22:59.789 --> 00:22:59.799 align:start position:0% work over the uh of polinomial and not 00:22:59.799 --> 00:23:01.669 align:start position:0% work over the uh of polinomial and not on<00:23:00.039> the<00:23:00.360> like<00:23:00.480> finite<00:23:00.799> fields<00:23:01.039> that<00:23:01.159> we<00:23:01.279> use<00:23:01.480> in 00:23:01.669 --> 00:23:01.679 align:start position:0% on the like finite fields that we use in 00:23:01.679 --> 00:23:05.230 align:start position:0% on the like finite fields that we use in in<00:23:01.799> the<00:23:02.159> traditional<00:23:02.600> snarks<00:23:03.480> um<00:23:04.320> so<00:23:04.840> also<00:23:05.120> it 00:23:05.230 --> 00:23:05.240 align:start position:0% in the traditional snarks um so also it 00:23:05.240 --> 00:23:07.669 align:start position:0% in the traditional snarks um so also it will<00:23:05.440> require<00:23:05.919> like<00:23:06.120> having<00:23:06.480> F<00:23:06.840> like<00:23:06.960> some 00:23:07.669 --> 00:23:07.679 align:start position:0% will require like having F like some 00:23:07.679 --> 00:23:09.789 align:start position:0% will require like having F like some layer<00:23:08.159> of<00:23:08.360> of<00:23:08.520> all<00:23:08.679> this<00:23:09.000> like<00:23:09.240> uh<00:23:09.480> instead<00:23:09.720> of 00:23:09.789 --> 00:23:09.799 align:start position:0% layer of of all this like uh instead of 00:23:09.799 --> 00:23:12.350 align:start position:0% layer of of all this like uh instead of the<00:23:09.880> field<00:23:10.120> arithmetic<00:23:10.679> the<00:23:11.000> the<00:23:11.120> ring<00:23:11.440> stuff 00:23:12.350 --> 00:23:12.360 align:start position:0% the field arithmetic the the ring stuff 00:23:12.360 --> 00:23:14.070 align:start position:0% the field arithmetic the the ring stuff uh<00:23:12.600> that<00:23:12.880> that<00:23:13.159> it's<00:23:13.320> not<00:23:13.559> at<00:23:13.679> least<00:23:13.840> in<00:23:13.960> in 00:23:14.070 --> 00:23:14.080 align:start position:0% uh that that it's not at least in in 00:23:14.080 --> 00:23:16.830 align:start position:0% uh that that it's not at least in in artworks<00:23:15.080> uh<00:23:15.320> so<00:23:15.600> so<00:23:15.840> yeah<00:23:16.120> and<00:23:16.279> the<00:23:16.360> folding 00:23:16.830 --> 00:23:16.840 align:start position:0% artworks uh so so yeah and the folding 00:23:16.840 --> 00:23:19.310 align:start position:0% artworks uh so so yeah and the folding Starks<00:23:17.360> it<00:23:17.520> looks<00:23:17.799> promising<00:23:18.360> because<00:23:18.960> Starks 00:23:19.310 --> 00:23:19.320 align:start position:0% Starks it looks promising because Starks 00:23:19.320 --> 00:23:21.630 align:start position:0% Starks it looks promising because Starks are<00:23:19.440> already<00:23:19.760> fast<00:23:20.440> uh<00:23:20.640> if<00:23:20.799> we<00:23:20.960> can<00:23:21.200> get<00:23:21.360> to<00:23:21.520> a 00:23:21.630 --> 00:23:21.640 align:start position:0% are already fast uh if we can get to a 00:23:21.640 --> 00:23:23.269 align:start position:0% are already fast uh if we can get to a state<00:23:21.880> where<00:23:22.039> we<00:23:22.159> can<00:23:22.640> use<00:23:22.880> the<00:23:22.960> folding 00:23:23.269 --> 00:23:23.279 align:start position:0% state where we can use the folding 00:23:23.279 --> 00:23:24.909 align:start position:0% state where we can use the folding techniques<00:23:23.840> uh<00:23:24.039> so<00:23:24.279> the<00:23:24.360> main<00:23:24.520> idea<00:23:24.720> is<00:23:24.799> that 00:23:24.909 --> 00:23:24.919 align:start position:0% techniques uh so the main idea is that 00:23:24.919 --> 00:23:27.350 align:start position:0% techniques uh so the main idea is that with<00:23:25.080> folding<00:23:25.760> uh<00:23:26.000> without<00:23:26.440> Starks<00:23:26.960> we<00:23:27.120> use 00:23:27.350 --> 00:23:27.360 align:start position:0% with folding uh without Starks we use 00:23:27.360 --> 00:23:29.590 align:start position:0% with folding uh without Starks we use this<00:23:27.760> uh<00:23:27.919> amorphic<00:23:28.520> commitment<00:23:28.840> schemes<00:23:29.400> so 00:23:29.590 --> 00:23:29.600 align:start position:0% this uh amorphic commitment schemes so 00:23:29.600 --> 00:23:32.190 align:start position:0% this uh amorphic commitment schemes so that<00:23:29.840> you<00:23:30.000> can<00:23:30.400> uh<00:23:30.600> combine<00:23:31.600> commitments<00:23:32.039> to 00:23:32.190 --> 00:23:32.200 align:start position:0% that you can uh combine commitments to 00:23:32.200 --> 00:23:34.750 align:start position:0% that you can uh combine commitments to some<00:23:32.720> vectors<00:23:33.039> or<00:23:33.240> polinomial<00:23:34.080> and<00:23:34.240> then<00:23:34.600> uh 00:23:34.750 --> 00:23:34.760 align:start position:0% some vectors or polinomial and then uh 00:23:34.760 --> 00:23:36.549 align:start position:0% some vectors or polinomial and then uh this<00:23:35.000> result<00:23:35.320> of<00:23:35.520> the<00:23:35.679> this<00:23:36.159> linear 00:23:36.549 --> 00:23:36.559 align:start position:0% this result of the this linear 00:23:36.559 --> 00:23:39.630 align:start position:0% this result of the this linear combination<00:23:37.279> of<00:23:37.480> them<00:23:37.960> uh<00:23:38.320> still<00:23:38.919> holds<00:23:39.360> some 00:23:39.630 --> 00:23:39.640 align:start position:0% combination of them uh still holds some 00:23:39.640 --> 00:23:41.710 align:start position:0% combination of them uh still holds some relations<00:23:40.640> with<00:23:40.880> Starks<00:23:41.400> since<00:23:41.600> the 00:23:41.710 --> 00:23:41.720 align:start position:0% relations with Starks since the 00:23:41.720 --> 00:23:43.789 align:start position:0% relations with Starks since the commitments<00:23:42.080> are<00:23:42.240> not<00:23:42.760> um<00:23:43.320> additively 00:23:43.789 --> 00:23:43.799 align:start position:0% commitments are not um additively 00:23:43.799 --> 00:23:46.430 align:start position:0% commitments are not um additively homomorphic<00:23:44.799> um<00:23:45.559> uh<00:23:45.720> we<00:23:45.840> are<00:23:45.919> not<00:23:46.080> there<00:23:46.240> yet 00:23:46.430 --> 00:23:46.440 align:start position:0% homomorphic um uh we are not there yet 00:23:46.440 --> 00:23:48.870 align:start position:0% homomorphic um uh we are not there yet but<00:23:46.840> uh<00:23:46.960> it<00:23:47.120> looks<00:23:47.360> like<00:23:47.720> uh<00:23:48.120> the<00:23:48.360> people<00:23:48.720> in 00:23:48.870 --> 00:23:48.880 align:start position:0% but uh it looks like uh the people in 00:23:48.880 --> 00:23:50.549 align:start position:0% but uh it looks like uh the people in the<00:23:49.000> Academia<00:23:49.400> or<00:23:49.559> in<00:23:49.720> behind<00:23:49.960> the<00:23:50.039> papers 00:23:50.549 --> 00:23:50.559 align:start position:0% the Academia or in behind the papers 00:23:50.559 --> 00:23:53.750 align:start position:0% the Academia or in behind the papers will<00:23:50.919> bring<00:23:51.400> some<00:23:52.120> uh<00:23:52.480> improvements<00:23:53.480> yeah<00:23:53.679> I 00:23:53.750 --> 00:23:53.760 align:start position:0% will bring some uh improvements yeah I 00:23:53.760 --> 00:23:55.269 align:start position:0% will bring some uh improvements yeah I think<00:23:53.960> Dan<00:23:54.200> Bon<00:23:54.440> is<00:23:54.520> waiting<00:23:54.760> for<00:23:54.919> you<00:23:55.039> to 00:23:55.269 --> 00:23:55.279 align:start position:0% think Dan Bon is waiting for you to 00:23:55.279 --> 00:23:57.310 align:start position:0% think Dan Bon is waiting for you to implement<00:23:56.279> that<00:23:56.480> his 00:23:57.310 --> 00:23:57.320 align:start position:0% implement that his 00:23:57.320 --> 00:24:01.390 align:start position:0% implement that his fault<00:23:58.320> uh<00:23:58.679> um<00:23:58.960> so<00:23:59.279> next<00:23:59.720> question<00:24:00.720> uh<00:24:00.840> folding 00:24:01.390 --> 00:24:01.400 align:start position:0% fault uh um so next question uh folding 00:24:01.400 --> 00:24:03.430 align:start position:0% fault uh um so next question uh folding papers<00:24:01.960> work<00:24:02.919> with<00:24:03.120> different 00:24:03.430 --> 00:24:03.440 align:start position:0% papers work with different 00:24:03.440 --> 00:24:06.750 align:start position:0% papers work with different arithmetization<00:24:03.919> A1<00:24:04.559> CS<00:24:04.919> blage<00:24:05.480> CCS<00:24:06.480> now<00:24:06.640> that 00:24:06.750 --> 00:24:06.760 align:start position:0% arithmetization A1 CS blage CCS now that 00:24:06.760 --> 00:24:08.630 align:start position:0% arithmetization A1 CS blage CCS now that you<00:24:06.919> did<00:24:07.120> the<00:24:07.240> implementation<00:24:08.159> is<00:24:08.279> it 00:24:08.630 --> 00:24:08.640 align:start position:0% you did the implementation is it 00:24:08.640 --> 00:24:10.590 align:start position:0% you did the implementation is it efficient<00:24:09.080> for<00:24:09.360> anything<00:24:09.799> other<00:24:10.000> than<00:24:10.200> Air1 00:24:10.590 --> 00:24:10.600 align:start position:0% efficient for anything other than Air1 00:24:10.600 --> 00:24:12.909 align:start position:0% efficient for anything other than Air1 CS<00:24:10.919> another<00:24:11.200> op<00:24:11.480> answered 00:24:12.909 --> 00:24:12.919 align:start position:0% CS another op answered 00:24:12.919 --> 00:24:15.990 align:start position:0% CS another op answered question<00:24:13.919> um<00:24:14.520> is<00:24:14.640> it<00:24:14.840> efficient<00:24:15.200> for<00:24:15.440> anything 00:24:15.990 --> 00:24:16.000 align:start position:0% question um is it efficient for anything 00:24:16.000 --> 00:24:18.470 align:start position:0% question um is it efficient for anything other<00:24:16.400> than<00:24:17.159> one 00:24:18.470 --> 00:24:18.480 align:start position:0% other than one 00:24:18.480 --> 00:24:20.230 align:start position:0% other than one CS 00:24:20.230 --> 00:24:20.240 align:start position:0% CS 00:24:20.240 --> 00:24:24.269 align:start position:0% CS uh<00:24:21.240> well<00:24:21.679> uh<00:24:21.799> so<00:24:22.080> there<00:24:22.240> is<00:24:22.919> basically<00:24:23.840> let 00:24:24.269 --> 00:24:24.279 align:start position:0% uh well uh so there is basically let 00:24:24.279 --> 00:24:26.430 align:start position:0% uh well uh so there is basically let lettis<00:24:24.600> fold<00:24:24.919> that<00:24:25.039> is<00:24:25.159> not<00:24:25.320> using<00:24:25.640> the<00:24:25.760> R1<00:24:26.120> CS 00:24:26.430 --> 00:24:26.440 align:start position:0% lettis fold that is not using the R1 CS 00:24:26.440 --> 00:24:29.110 align:start position:0% lettis fold that is not using the R1 CS optimization<00:24:27.080> where<00:24:27.200> you<00:24:27.360> can<00:24:28.399> use<00:24:28.600> the<00:24:28.760> idea 00:24:29.110 --> 00:24:29.120 align:start position:0% optimization where you can use the idea 00:24:29.120 --> 00:24:31.110 align:start position:0% optimization where you can use the idea that<00:24:29.440> are<00:24:30.039> from<00:24:30.200> the<00:24:30.360> previous<00:24:30.679> folding 00:24:31.110 --> 00:24:31.120 align:start position:0% that are from the previous folding 00:24:31.120 --> 00:24:33.430 align:start position:0% that are from the previous folding papers<00:24:32.080> uh<00:24:32.360> for<00:24:32.679> a<00:24:32.840> different<00:24:33.159> kind<00:24:33.320> of 00:24:33.430 --> 00:24:33.440 align:start position:0% papers uh for a different kind of 00:24:33.440 --> 00:24:34.590 align:start position:0% papers uh for a different kind of arithmetization 00:24:34.590 --> 00:24:34.600 align:start position:0% arithmetization 00:24:34.600 --> 00:24:37.830 align:start position:0% arithmetization so<00:24:35.600> uh<00:24:36.200> there<00:24:36.360> is<00:24:36.520> also<00:24:36.799> the<00:24:37.080> question<00:24:37.440> above 00:24:37.830 --> 00:24:37.840 align:start position:0% so uh there is also the question above 00:24:37.840 --> 00:24:40.070 align:start position:0% so uh there is also the question above what's<00:24:38.039> the<00:24:38.200> status<00:24:38.600> of<00:24:38.760> folding<00:24:39.080> for<00:24:39.320> Stacks 00:24:40.070 --> 00:24:40.080 align:start position:0% what's the status of folding for Stacks 00:24:40.080 --> 00:24:42.269 align:start position:0% what's the status of folding for Stacks you<00:24:40.200> can<00:24:40.480> reuse<00:24:40.960> the<00:24:41.520> ideas<00:24:41.840> that<00:24:41.960> were<00:24:42.159> in 00:24:42.269 --> 00:24:42.279 align:start position:0% you can reuse the ideas that were in 00:24:42.279 --> 00:24:45.430 align:start position:0% you can reuse the ideas that were in folding<00:24:42.679> papers<00:24:43.080> for<00:24:43.880> another<00:24:44.360> kind<00:24:44.520> of<00:24:44.679> AR<00:24:45.279> I 00:24:45.430 --> 00:24:45.440 align:start position:0% folding papers for another kind of AR I 00:24:45.440 --> 00:24:47.310 align:start position:0% folding papers for another kind of AR I guess<00:24:45.640> the<00:24:46.080> arithmetization 00:24:47.310 --> 00:24:47.320 align:start position:0% guess the arithmetization 00:24:47.320 --> 00:24:50.310 align:start position:0% guess the arithmetization um<00:24:48.320> so<00:24:48.559> for<00:24:48.760> a<00:24:48.880> different<00:24:49.200> kind<00:24:49.360> of<00:24:49.840> for<00:24:50.159> an 00:24:50.310 --> 00:24:50.320 align:start position:0% um so for a different kind of for an 00:24:50.320 --> 00:24:51.669 align:start position:0% um so for a different kind of for an arithmetization<00:24:50.760> that<00:24:51.080> is<00:24:51.240> different<00:24:51.520> from 00:24:51.669 --> 00:24:51.679 align:start position:0% arithmetization that is different from 00:24:51.679 --> 00:24:54.070 align:start position:0% arithmetization that is different from R1<00:24:52.520> CS 00:24:54.070 --> 00:24:54.080 align:start position:0% R1 CS 00:24:54.080 --> 00:24:56.990 align:start position:0% R1 CS um<00:24:55.080> and<00:24:55.760> uh<00:24:55.880> so<00:24:56.159> yeah<00:24:56.320> I<00:24:56.440> guess<00:24:56.679> that<00:24:56.880> that 00:24:56.990 --> 00:24:57.000 align:start position:0% um and uh so yeah I guess that that 00:24:57.000 --> 00:24:58.789 align:start position:0% um and uh so yeah I guess that that answer<00:24:57.320> the<00:24:57.480> question<00:24:57.799> if<00:24:57.880> I<00:24:58.159> understand<00:24:58.559> so 00:24:58.789 --> 00:24:58.799 align:start position:0% answer the question if I understand so 00:24:58.799 --> 00:25:01.789 align:start position:0% answer the question if I understand so yeah<00:24:59.360> if<00:24:59.480> we<00:24:59.600> can<00:24:59.799> just<00:24:59.919> scroll<00:25:00.320> down<00:25:00.559> to<00:25:00.799> see 00:25:01.789 --> 00:25:01.799 align:start position:0% yeah if we can just scroll down to see 00:25:01.799 --> 00:25:03.350 align:start position:0% yeah if we can just scroll down to see the<00:25:01.960> questions<00:25:02.240> or<00:25:02.440> maybe<00:25:02.600> I<00:25:02.720> can<00:25:03.039> check<00:25:03.240> them 00:25:03.350 --> 00:25:03.360 align:start position:0% the questions or maybe I can check them 00:25:03.360 --> 00:25:04.909 align:start position:0% the questions or maybe I can check them on<00:25:03.480> my<00:25:03.640> phone 00:25:04.909 --> 00:25:04.919 align:start position:0% on my phone 00:25:04.919 --> 00:25:07.590 align:start position:0% on my phone yeah<00:25:05.919> so<00:25:06.120> how<00:25:06.360> does<00:25:06.520> sonobi<00:25:07.000> compareed<00:25:07.360> to 00:25:07.590 --> 00:25:07.600 align:start position:0% yeah so how does sonobi compareed to 00:25:07.600 --> 00:25:11.149 align:start position:0% yeah so how does sonobi compareed to Nexus<00:25:08.600> so<00:25:09.360> um<00:25:10.000> first<00:25:10.200> of<00:25:10.320> all<00:25:10.440> Nexus<00:25:10.799> is<00:25:10.919> like<00:25:11.039> a 00:25:11.149 --> 00:25:11.159 align:start position:0% Nexus so um first of all Nexus is like a 00:25:11.159 --> 00:25:13.630 align:start position:0% Nexus so um first of all Nexus is like a full<00:25:11.840> uh<00:25:12.080> Company<00:25:12.480> veed<00:25:12.760> by<00:25:12.919> VCS<00:25:13.320> and<00:25:13.480> their 00:25:13.630 --> 00:25:13.640 align:start position:0% full uh Company veed by VCS and their 00:25:13.640 --> 00:25:15.070 align:start position:0% full uh Company veed by VCS and their team<00:25:13.799> is<00:25:13.919> amazing<00:25:14.240> like<00:25:14.440> it's<00:25:14.640> a<00:25:14.799> bunch<00:25:15.000> of 00:25:15.070 --> 00:25:15.080 align:start position:0% team is amazing like it's a bunch of 00:25:15.080 --> 00:25:16.870 align:start position:0% team is amazing like it's a bunch of people<00:25:15.279> from<00:25:15.399> Stanford<00:25:15.880> and<00:25:16.039> and<00:25:16.200> so<00:25:16.679> very 00:25:16.870 --> 00:25:16.880 align:start position:0% people from Stanford and and so very 00:25:16.880 --> 00:25:19.149 align:start position:0% people from Stanford and and so very good<00:25:17.039> team<00:25:17.480> so<00:25:17.760> no<00:25:17.960> it's<00:25:18.039> like<00:25:18.159> a<00:25:18.240> small<00:25:18.480> team 00:25:19.149 --> 00:25:19.159 align:start position:0% good team so no it's like a small team 00:25:19.159 --> 00:25:21.389 align:start position:0% good team so no it's like a small team like<00:25:19.440> we<00:25:19.559> are<00:25:19.679> like<00:25:19.840> three<00:25:20.039> four<00:25:20.320> people<00:25:21.159> uh 00:25:21.389 --> 00:25:21.399 align:start position:0% like we are like three four people uh 00:25:21.399 --> 00:25:24.269 align:start position:0% like we are like three four people uh and<00:25:21.799> and<00:25:22.080> we've<00:25:22.360> been<00:25:23.159> doing<00:25:23.520> this<00:25:23.720> but<00:25:23.919> like 00:25:24.269 --> 00:25:24.279 align:start position:0% and and we've been doing this but like 00:25:24.279 --> 00:25:27.149 align:start position:0% and and we've been doing this but like uh<00:25:24.960> uh<00:25:25.080> in<00:25:25.159> a<00:25:25.279> more<00:25:25.480> experimental<00:25:26.240> uh<00:25:26.399> like<00:25:26.520> not 00:25:27.149 --> 00:25:27.159 align:start position:0% uh uh in a more experimental uh like not 00:25:27.159 --> 00:25:29.990 align:start position:0% uh uh in a more experimental uh like not production<00:25:28.000> uh<00:25:28.360> focused<00:25:29.279> but<00:25:29.440> so<00:25:29.640> far<00:25:29.880> the 00:25:29.990 --> 00:25:30.000 align:start position:0% production uh focused but so far the 00:25:30.000 --> 00:25:31.990 align:start position:0% production uh focused but so far the benchmarks<00:25:30.399> that<00:25:30.520> we<00:25:30.640> run<00:25:31.320> uh<00:25:31.559> when<00:25:31.679> you<00:25:31.799> run 00:25:31.990 --> 00:25:32.000 align:start position:0% benchmarks that we run uh when you run 00:25:32.000 --> 00:25:33.310 align:start position:0% benchmarks that we run uh when you run the<00:25:32.080> Benchmark<00:25:32.440> in<00:25:32.520> the<00:25:32.600> same<00:25:32.760> machine<00:25:33.120> for 00:25:33.310 --> 00:25:33.320 align:start position:0% the Benchmark in the same machine for 00:25:33.320 --> 00:25:35.310 align:start position:0% the Benchmark in the same machine for the<00:25:33.520> now<00:25:33.679> implementation<00:25:34.399> it's<00:25:34.720> almost<00:25:35.120> like 00:25:35.310 --> 00:25:35.320 align:start position:0% the now implementation it's almost like 00:25:35.320 --> 00:25:37.549 align:start position:0% the now implementation it's almost like the<00:25:35.440> same<00:25:35.760> like<00:25:35.919> it's<00:25:36.080> like<00:25:36.640> from<00:25:37.000> 300 00:25:37.549 --> 00:25:37.559 align:start position:0% the same like it's like from 300 00:25:37.559 --> 00:25:41.389 align:start position:0% the same like it's like from 300 milliseconds<00:25:38.240> in<00:25:38.480> Nexus<00:25:39.480> Nova<00:25:40.080> to<00:25:40.399> 310 00:25:41.389 --> 00:25:41.399 align:start position:0% milliseconds in Nexus Nova to 310 00:25:41.399 --> 00:25:43.909 align:start position:0% milliseconds in Nexus Nova to 310 milliseconds<00:25:42.039> in<00:25:42.200> sonov<00:25:43.159> so<00:25:43.279> it's<00:25:43.520> almost<00:25:43.799> the 00:25:43.909 --> 00:25:43.919 align:start position:0% milliseconds in sonov so it's almost the 00:25:43.919 --> 00:25:46.029 align:start position:0% milliseconds in sonov so it's almost the same<00:25:44.320> hypernova<00:25:44.799> in<00:25:44.880> son<00:25:45.240> is<00:25:45.320> much<00:25:45.480> slower<00:25:45.880> but 00:25:46.029 --> 00:25:46.039 align:start position:0% same hypernova in son is much slower but 00:25:46.039 --> 00:25:47.549 align:start position:0% same hypernova in son is much slower but because<00:25:46.279> it's<00:25:46.520> it's<00:25:46.919> far<00:25:47.159> from<00:25:47.320> being 00:25:47.549 --> 00:25:47.559 align:start position:0% because it's it's far from being 00:25:47.559 --> 00:25:50.430 align:start position:0% because it's it's far from being optimized<00:25:48.559> and<00:25:48.720> then<00:25:49.440> uh<00:25:49.799> we<00:25:49.919> also<00:25:50.120> have<00:25:50.279> the 00:25:50.430 --> 00:25:50.440 align:start position:0% optimized and then uh we also have the 00:25:50.440 --> 00:25:52.630 align:start position:0% optimized and then uh we also have the Proto<00:25:50.679> Galaxy<00:25:51.200> uh<00:25:51.360> but<00:25:51.640> in<00:25:51.760> Nexus<00:25:52.320> is<00:25:52.440> not 00:25:52.630 --> 00:25:52.640 align:start position:0% Proto Galaxy uh but in Nexus is not 00:25:52.640 --> 00:25:55.110 align:start position:0% Proto Galaxy uh but in Nexus is not there<00:25:52.840> but<00:25:53.200> so<00:25:53.840> the<00:25:53.960> thing<00:25:54.120> is<00:25:54.240> that<00:25:54.520> both 00:25:55.110 --> 00:25:55.120 align:start position:0% there but so the thing is that both 00:25:55.120 --> 00:25:57.350 align:start position:0% there but so the thing is that both libraries<00:25:55.880> are<00:25:56.039> based<00:25:56.279> on<00:25:56.399> artworks<00:25:56.880> so<00:25:57.120> like 00:25:57.350 --> 00:25:57.360 align:start position:0% libraries are based on artworks so like 00:25:57.360 --> 00:26:00.950 align:start position:0% libraries are based on artworks so like the<00:25:57.679> the<00:25:57.880> the<00:25:57.960> max<00:25:58.559> speed<00:25:59.240> should<00:25:59.520> be<00:25:59.960> similar 00:26:00.950 --> 00:26:00.960 align:start position:0% the the the max speed should be similar 00:26:00.960 --> 00:26:02.750 align:start position:0% the the the max speed should be similar um<00:26:01.200> and<00:26:01.399> both<00:26:01.559> are<00:26:01.720> using<00:26:02.000> cycle<00:26:02.279> fault<00:26:02.600> which 00:26:02.750 --> 00:26:02.760 align:start position:0% um and both are using cycle fault which 00:26:02.760 --> 00:26:04.190 align:start position:0% um and both are using cycle fault which like<00:26:02.919> the<00:26:03.120> Microsoft<00:26:03.559> Nova<00:26:03.799> is<00:26:03.880> not<00:26:04.000> using 00:26:04.190 --> 00:26:04.200 align:start position:0% like the Microsoft Nova is not using 00:26:04.200 --> 00:26:06.830 align:start position:0% like the Microsoft Nova is not using cycle<00:26:04.480> fault<00:26:05.120> it<00:26:05.279> has<00:26:05.399> a<00:26:05.520> different<00:26:05.799> R<00:26:06.440> so<00:26:06.679> we 00:26:06.830 --> 00:26:06.840 align:start position:0% cycle fault it has a different R so we 00:26:06.840 --> 00:26:10.549 align:start position:0% cycle fault it has a different R so we have<00:26:07.080> time<00:26:07.480> for<00:26:07.799> the<00:26:07.960> Q&A<00:26:08.919> so<00:26:09.399> why<00:26:09.520> if<00:26:09.679> we<00:26:10.240> thank 00:26:10.549 --> 00:26:10.559 align:start position:0% have time for the Q&A so why if we thank 00:26:10.559 --> 00:26:12.630 align:start position:0% have time for the Q&A so why if we thank again<00:26:10.799> our<00:26:11.159> speakers<00:26:11.840> and<00:26:12.039> give<00:26:12.200> them<00:26:12.320> a<00:26:12.480> round 00:26:12.630 --> 00:26:12.640 align:start position:0% again our speakers and give them a round 00:26:12.640 --> 00:26:16.200 align:start position:0% again our speakers and give them a round of<00:26:12.799> applause<00:26:13.440> thank<00:26:13.600> you