WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:10.589 align:start position:0% [Music] 00:00:10.589 --> 00:00:10.599 align:start position:0% 00:00:10.599 --> 00:00:13.910 align:start position:0% good<00:00:10.759> morning<00:00:11.519> everyone<00:00:12.519> so<00:00:12.759> today<00:00:13.200> I'll<00:00:13.679> talk 00:00:13.910 --> 00:00:13.920 align:start position:0% good morning everyone so today I'll talk 00:00:13.920 --> 00:00:15.990 align:start position:0% good morning everyone so today I'll talk about<00:00:14.480> fuzzing<00:00:15.040> for<00:00:15.320> zero<00:00:15.639> knowledge 00:00:15.990 --> 00:00:16.000 align:start position:0% about fuzzing for zero knowledge 00:00:16.000 --> 00:00:18.150 align:start position:0% about fuzzing for zero knowledge infrastructure<00:00:16.840> and<00:00:17.039> this<00:00:17.160> is<00:00:17.359> Joint<00:00:17.680> work 00:00:18.150 --> 00:00:18.160 align:start position:0% infrastructure and this is Joint work 00:00:18.160 --> 00:00:20.750 align:start position:0% infrastructure and this is Joint work with<00:00:18.400> my<00:00:18.920> collaborators<00:00:19.560> from<00:00:19.880> the<00:00:20.199> Technical 00:00:20.750 --> 00:00:20.760 align:start position:0% with my collaborators from the Technical 00:00:20.760 --> 00:00:22.790 align:start position:0% with my collaborators from the Technical University<00:00:21.480> of 00:00:22.790 --> 00:00:22.800 align:start position:0% University of 00:00:22.800 --> 00:00:26.109 align:start position:0% University of Vienna<00:00:23.800> so<00:00:24.760> just<00:00:24.920> to<00:00:25.119> kind<00:00:25.279> of<00:00:25.599> make<00:00:25.760> sure<00:00:26.000> we 00:00:26.109 --> 00:00:26.119 align:start position:0% Vienna so just to kind of make sure we 00:00:26.119 --> 00:00:29.990 align:start position:0% Vienna so just to kind of make sure we are<00:00:26.320> all<00:00:26.720> on<00:00:26.840> the<00:00:27.000> same<00:00:27.240> page<00:00:28.039> um<00:00:28.760> let's<00:00:29.480> have<00:00:29.640> a 00:00:29.990 --> 00:00:30.000 align:start position:0% are all on the same page um let's have a 00:00:30.000 --> 00:00:31.830 align:start position:0% are all on the same page um let's have a short<00:00:30.279> definition<00:00:30.640> of<00:00:30.800> what<00:00:30.920> I<00:00:31.359> understand<00:00:31.640> by 00:00:31.830 --> 00:00:31.840 align:start position:0% short definition of what I understand by 00:00:31.840 --> 00:00:35.389 align:start position:0% short definition of what I understand by zero<00:00:32.160> knowledge<00:00:33.440> infrastructure<00:00:34.440> so<00:00:35.120> uh<00:00:35.200> for 00:00:35.389 --> 00:00:35.399 align:start position:0% zero knowledge infrastructure so uh for 00:00:35.399 --> 00:00:39.069 align:start position:0% zero knowledge infrastructure so uh for this<00:00:36.120> talk<00:00:36.680> I'll<00:00:37.600> um<00:00:37.960> Define<00:00:38.480> zero<00:00:38.800> knowledge 00:00:39.069 --> 00:00:39.079 align:start position:0% this talk I'll um Define zero knowledge 00:00:39.079 --> 00:00:41.190 align:start position:0% this talk I'll um Define zero knowledge infrastructure<00:00:39.840> as<00:00:40.200> software<00:00:40.640> components 00:00:41.190 --> 00:00:41.200 align:start position:0% infrastructure as software components 00:00:41.200 --> 00:00:44.029 align:start position:0% infrastructure as software components that<00:00:41.280> are<00:00:41.440> used<00:00:41.680> for<00:00:42.039> compiling<00:00:43.039> executing 00:00:44.029 --> 00:00:44.039 align:start position:0% that are used for compiling executing 00:00:44.039 --> 00:00:47.549 align:start position:0% that are used for compiling executing proving<00:00:44.480> and<00:00:44.680> verifying<00:00:45.160> ZK<00:00:46.320> circuits<00:00:47.320> so 00:00:47.549 --> 00:00:47.559 align:start position:0% proving and verifying ZK circuits so 00:00:47.559 --> 00:00:50.430 align:start position:0% proving and verifying ZK circuits so examples<00:00:48.360> would<00:00:48.559> be<00:00:49.559> the<00:00:49.879> processing 00:00:50.430 --> 00:00:50.440 align:start position:0% examples would be the processing 00:00:50.440 --> 00:00:53.110 align:start position:0% examples would be the processing pipelines<00:00:50.920> that<00:00:51.000> are<00:00:51.160> commonly<00:00:51.559> used<00:00:52.000> by<00:00:52.960> uh 00:00:53.110 --> 00:00:53.120 align:start position:0% pipelines that are commonly used by uh 00:00:53.120 --> 00:00:57.349 align:start position:0% pipelines that are commonly used by uh dsls<00:00:53.680> for<00:00:54.000> describing<00:00:54.680> ZK<00:00:55.600> uh<00:00:55.879> circuits<00:00:56.879> or 00:00:57.349 --> 00:00:57.359 align:start position:0% dsls for describing ZK uh circuits or 00:00:57.359 --> 00:00:59.229 align:start position:0% dsls for describing ZK uh circuits or maybe<00:00:57.800> in<00:00:57.920> the<00:00:58.039> future<00:00:58.320> we'll<00:00:58.559> also<00:00:58.800> look<00:00:58.960> at 00:00:59.229 --> 00:00:59.239 align:start position:0% maybe in the future we'll also look at 00:00:59.239 --> 00:01:02.509 align:start position:0% maybe in the future we'll also look at entire<00:00:59.600> ZK 00:01:02.509 --> 00:01:02.519 align:start position:0% 00:01:02.519 --> 00:01:06.630 align:start position:0% EVMS<00:01:03.600> so<00:01:04.600> um<00:01:04.879> with<00:01:05.080> this<00:01:05.199> out<00:01:05.360> of<00:01:05.479> the<00:01:05.600> way<00:01:06.320> um 00:01:06.630 --> 00:01:06.640 align:start position:0% EVMS so um with this out of the way um 00:01:06.640 --> 00:01:09.550 align:start position:0% EVMS so um with this out of the way um let's<00:01:07.640> um<00:01:08.240> look<00:01:08.479> at<00:01:08.880> why<00:01:09.119> this<00:01:09.280> is<00:01:09.400> an 00:01:09.550 --> 00:01:09.560 align:start position:0% let's um look at why this is an 00:01:09.560 --> 00:01:12.590 align:start position:0% let's um look at why this is an important<00:01:10.000> topic<00:01:10.400> and<00:01:10.680> why<00:01:11.640> um<00:01:11.880> more<00:01:12.159> people 00:01:12.590 --> 00:01:12.600 align:start position:0% important topic and why um more people 00:01:12.600 --> 00:01:15.710 align:start position:0% important topic and why um more people should<00:01:12.799> be<00:01:12.960> doing<00:01:13.280> this<00:01:14.280> well<00:01:15.040> first<00:01:15.400> zero 00:01:15.710 --> 00:01:15.720 align:start position:0% should be doing this well first zero 00:01:15.720 --> 00:01:17.550 align:start position:0% should be doing this well first zero knowledge<00:01:16.080> infrastructure<00:01:16.799> is<00:01:17.200> highly 00:01:17.550 --> 00:01:17.560 align:start position:0% knowledge infrastructure is highly 00:01:17.560 --> 00:01:20.109 align:start position:0% knowledge infrastructure is highly complex<00:01:18.159> and<00:01:18.360> highly<00:01:18.640> critical<00:01:19.600> for<00:01:19.799> instance 00:01:20.109 --> 00:01:20.119 align:start position:0% complex and highly critical for instance 00:01:20.119 --> 00:01:23.630 align:start position:0% complex and highly critical for instance it's<00:01:20.280> used<00:01:20.600> in<00:01:21.040> several<00:01:21.439> L2<00:01:22.040> chains<00:01:22.759> so<00:01:23.479> kind 00:01:23.630 --> 00:01:23.640 align:start position:0% it's used in several L2 chains so kind 00:01:23.640 --> 00:01:26.630 align:start position:0% it's used in several L2 chains so kind of<00:01:23.799> bugs<00:01:24.280> there<00:01:25.119> uh<00:01:25.280> could<00:01:25.520> have<00:01:26.400> uh 00:01:26.630 --> 00:01:26.640 align:start position:0% of bugs there uh could have uh 00:01:26.640 --> 00:01:29.749 align:start position:0% of bugs there uh could have uh catastrophic<00:01:27.600> financial<00:01:28.119> and<00:01:28.759> reputational 00:01:29.749 --> 00:01:29.759 align:start position:0% catastrophic financial and reputational 00:01:29.759 --> 00:01:33.149 align:start position:0% catastrophic financial and reputational uh<00:01:30.159> impact<00:01:31.159> and<00:01:31.759> we<00:01:31.880> should<00:01:32.159> really<00:01:32.600> make<00:01:32.799> sure 00:01:33.149 --> 00:01:33.159 align:start position:0% uh impact and we should really make sure 00:01:33.159 --> 00:01:35.630 align:start position:0% uh impact and we should really make sure these<00:01:33.600> components<00:01:34.119> are<00:01:34.479> as<00:01:34.759> bulletproof<00:01:35.479> as 00:01:35.630 --> 00:01:35.640 align:start position:0% these components are as bulletproof as 00:01:35.640 --> 00:01:37.270 align:start position:0% these components are as bulletproof as they<00:01:35.759> can 00:01:37.270 --> 00:01:37.280 align:start position:0% they can 00:01:37.280 --> 00:01:41.069 align:start position:0% they can get<00:01:38.280> um<00:01:38.759> while<00:01:38.920> we<00:01:39.040> haven't<00:01:39.320> seen<00:01:40.320> a<00:01:40.680> really 00:01:41.069 --> 00:01:41.079 align:start position:0% get um while we haven't seen a really 00:01:41.079 --> 00:01:43.950 align:start position:0% get um while we haven't seen a really catastrophic<00:01:41.640> incident<00:01:42.520> uh<00:01:42.640> in<00:01:42.799> this<00:01:42.960> field 00:01:43.950 --> 00:01:43.960 align:start position:0% catastrophic incident uh in this field 00:01:43.960 --> 00:01:46.550 align:start position:0% catastrophic incident uh in this field may<00:01:44.240> maybe<00:01:44.680> perhaps<00:01:45.680> uh<00:01:45.880> comparable<00:01:46.280> to<00:01:46.399> the 00:01:46.550 --> 00:01:46.560 align:start position:0% may maybe perhaps uh comparable to the 00:01:46.560 --> 00:01:48.510 align:start position:0% may maybe perhaps uh comparable to the Dow<00:01:46.880> hack<00:01:47.439> in 00:01:48.510 --> 00:01:48.520 align:start position:0% Dow hack in 00:01:48.520 --> 00:01:52.709 align:start position:0% Dow hack in 2016<00:01:49.520> uh<00:01:49.640> it's<00:01:49.799> really<00:01:50.040> important<00:01:51.040> that<00:01:51.600> um<00:01:51.840> we 00:01:52.709 --> 00:01:52.719 align:start position:0% 2016 uh it's really important that um we 00:01:52.719 --> 00:01:55.029 align:start position:0% 2016 uh it's really important that um we have<00:01:53.399> uh<00:01:53.560> rigorous<00:01:54.040> testing<00:01:54.520> for<00:01:54.759> these 00:01:55.029 --> 00:01:55.039 align:start position:0% have uh rigorous testing for these 00:01:55.039 --> 00:01:59.230 align:start position:0% have uh rigorous testing for these components<00:01:56.039> and<00:01:56.360> we<00:01:56.840> use<00:01:57.799> um<00:01:58.399> you<00:01:58.560> know<00:01:59.039> the 00:01:59.230 --> 00:01:59.240 align:start position:0% components and we use um you know the 00:01:59.240 --> 00:02:04.350 align:start position:0% components and we use um you know the best<00:02:00.079> ering<00:02:00.560> uh<00:02:00.719> discipline<00:02:01.680> that<00:02:01.960> we<00:02:02.640> can<00:02:03.520> um 00:02:04.350 --> 00:02:04.360 align:start position:0% best ering uh discipline that we can um 00:02:04.360 --> 00:02:06.870 align:start position:0% best ering uh discipline that we can um have<00:02:04.880> right<00:02:05.880> uh<00:02:06.000> because<00:02:06.240> these<00:02:06.399> components 00:02:06.870 --> 00:02:06.880 align:start position:0% have right uh because these components 00:02:06.880 --> 00:02:09.270 align:start position:0% have right uh because these components are<00:02:07.560> really<00:02:07.960> complex<00:02:08.560> and<00:02:08.800> getting<00:02:09.039> them 00:02:09.270 --> 00:02:09.280 align:start position:0% are really complex and getting them 00:02:09.280 --> 00:02:11.790 align:start position:0% are really complex and getting them right<00:02:09.599> is<00:02:09.879> is<00:02:10.000> not 00:02:11.790 --> 00:02:11.800 align:start position:0% right is is not 00:02:11.800 --> 00:02:14.670 align:start position:0% right is is not easy<00:02:12.800> so<00:02:13.000> what<00:02:13.120> is<00:02:13.239> fuzzing<00:02:13.959> I<00:02:14.160> don't<00:02:14.360> think<00:02:14.519> I 00:02:14.670 --> 00:02:14.680 align:start position:0% easy so what is fuzzing I don't think I 00:02:14.680 --> 00:02:17.830 align:start position:0% easy so what is fuzzing I don't think I have<00:02:14.800> to<00:02:15.120> like<00:02:15.519> explain<00:02:16.040> this<00:02:16.440> after<00:02:16.800> the<00:02:17.239> last 00:02:17.830 --> 00:02:17.840 align:start position:0% have to like explain this after the last 00:02:17.840 --> 00:02:20.750 align:start position:0% have to like explain this after the last uh<00:02:18.000> talk<00:02:18.480> but<00:02:19.120> fuzzing<00:02:19.599> is<00:02:20.040> widely<00:02:20.360> used<00:02:20.599> in 00:02:20.750 --> 00:02:20.760 align:start position:0% uh talk but fuzzing is widely used in 00:02:20.760 --> 00:02:23.430 align:start position:0% uh talk but fuzzing is widely used in industry<00:02:21.680> um<00:02:21.959> for<00:02:22.120> instance<00:02:22.360> at<00:02:22.560> Microsoft 00:02:23.430 --> 00:02:23.440 align:start position:0% industry um for instance at Microsoft 00:02:23.440 --> 00:02:25.670 align:start position:0% industry um for instance at Microsoft Google<00:02:23.879> meta<00:02:24.720> uh<00:02:24.840> they're<00:02:24.959> fuzzing<00:02:25.360> a<00:02:25.440> lot<00:02:25.560> of 00:02:25.670 --> 00:02:25.680 align:start position:0% Google meta uh they're fuzzing a lot of 00:02:25.680 --> 00:02:27.869 align:start position:0% Google meta uh they're fuzzing a lot of their<00:02:25.879> infrastructure<00:02:26.879> uh<00:02:26.959> to<00:02:27.160> catch<00:02:27.440> Buck 00:02:27.869 --> 00:02:27.879 align:start position:0% their infrastructure uh to catch Buck 00:02:27.879 --> 00:02:30.030 align:start position:0% their infrastructure uh to catch Buck before<00:02:28.599> um<00:02:28.760> hackers<00:02:29.080> can<00:02:29.239> actually<00:02:29.480> exploit 00:02:30.030 --> 00:02:30.040 align:start position:0% before um hackers can actually exploit 00:02:30.040 --> 00:02:32.030 align:start position:0% before um hackers can actually exploit them<00:02:30.360> in 00:02:32.030 --> 00:02:32.040 align:start position:0% them in 00:02:32.040 --> 00:02:34.670 align:start position:0% them in practice<00:02:33.040> so<00:02:33.480> in<00:02:33.599> this<00:02:33.800> talk<00:02:34.080> I'll<00:02:34.440> give<00:02:34.560> you 00:02:34.670 --> 00:02:34.680 align:start position:0% practice so in this talk I'll give you 00:02:34.680 --> 00:02:38.869 align:start position:0% practice so in this talk I'll give you an<00:02:34.840> overview<00:02:35.519> of<00:02:35.879> our<00:02:36.200> fuzzer<00:02:37.200> for<00:02:38.200> um<00:02:38.480> finding 00:02:38.869 --> 00:02:38.879 align:start position:0% an overview of our fuzzer for um finding 00:02:38.879 --> 00:02:41.229 align:start position:0% an overview of our fuzzer for um finding critical<00:02:39.319> bugs<00:02:39.800> in<00:02:40.319> processing<00:02:40.800> pipelines 00:02:41.229 --> 00:02:41.239 align:start position:0% critical bugs in processing pipelines 00:02:41.239 --> 00:02:44.149 align:start position:0% critical bugs in processing pipelines for<00:02:41.400> zero<00:02:41.720> knowledge<00:02:42.280> circuits<00:02:43.280> um<00:02:44.040> the 00:02:44.149 --> 00:02:44.159 align:start position:0% for zero knowledge circuits um the 00:02:44.159 --> 00:02:47.589 align:start position:0% for zero knowledge circuits um the fuzzer<00:02:44.480> is<00:02:44.599> called<00:02:44.800> Circus<00:02:45.640> and<00:02:46.400> it<00:02:47.319> already 00:02:47.589 --> 00:02:47.599 align:start position:0% fuzzer is called Circus and it already 00:02:47.599 --> 00:02:51.550 align:start position:0% fuzzer is called Circus and it already supports<00:02:48.159> four<00:02:48.519> of<00:02:48.840> these<00:02:49.800> pipelines<00:02:50.800> namely 00:02:51.550 --> 00:02:51.560 align:start position:0% supports four of these pipelines namely 00:02:51.560 --> 00:02:56.190 align:start position:0% supports four of these pipelines namely uh<00:02:51.680> circum<00:02:52.640> cor<00:02:53.640> uh<00:02:53.879> gar<00:02:54.280> and<00:02:54.920> Noir<00:02:55.920> and 00:02:56.190 --> 00:02:56.200 align:start position:0% uh circum cor uh gar and Noir and 00:02:56.200 --> 00:02:59.430 align:start position:0% uh circum cor uh gar and Noir and there's<00:02:56.720> you<00:02:56.840> know<00:02:57.120> like<00:02:57.440> a<00:02:58.440> a<00:02:58.800> gazillion<00:02:59.280> of 00:02:59.430 --> 00:02:59.440 align:start position:0% there's you know like a a gazillion of 00:02:59.440 --> 00:03:00.430 align:start position:0% there's you know like a a gazillion of different 00:03:00.430 --> 00:03:00.440 align:start position:0% different 00:03:00.440 --> 00:03:03.309 align:start position:0% different dsls<00:03:01.239> popping<00:03:01.560> up<00:03:01.879> it<00:03:02.000> seems<00:03:02.519> like<00:03:02.760> you<00:03:03.040> walk 00:03:03.309 --> 00:03:03.319 align:start position:0% dsls popping up it seems like you walk 00:03:03.319 --> 00:03:05.750 align:start position:0% dsls popping up it seems like you walk around<00:03:03.680> here<00:03:03.959> and<00:03:04.159> you<00:03:04.680> see<00:03:04.959> another<00:03:05.239> one<00:03:05.640> in 00:03:05.750 --> 00:03:05.760 align:start position:0% around here and you see another one in 00:03:05.760 --> 00:03:10.190 align:start position:0% around here and you see another one in the<00:03:06.280> corner<00:03:07.440> um<00:03:08.440> and<00:03:08.879> we've<00:03:09.120> already<00:03:09.360> found<00:03:10.080> uh 00:03:10.190 --> 00:03:10.200 align:start position:0% the corner um and we've already found uh 00:03:10.200 --> 00:03:12.509 align:start position:0% the corner um and we've already found uh 16<00:03:10.599> bugs<00:03:10.879> in<00:03:11.000> total<00:03:11.440> for<00:03:11.720> the<00:03:11.840> four<00:03:12.400> uh 00:03:12.509 --> 00:03:12.519 align:start position:0% 16 bugs in total for the four uh 00:03:12.519 --> 00:03:15.470 align:start position:0% 16 bugs in total for the four uh pipelines<00:03:12.959> we<00:03:13.120> looked<00:03:13.480> at<00:03:14.480> um<00:03:14.959> 15<00:03:15.360> have 00:03:15.470 --> 00:03:15.480 align:start position:0% pipelines we looked at um 15 have 00:03:15.480 --> 00:03:17.270 align:start position:0% pipelines we looked at um 15 have already<00:03:15.680> been<00:03:15.879> fixed<00:03:16.319> so<00:03:16.519> that<00:03:16.760> kind<00:03:16.879> of<00:03:17.000> shows 00:03:17.270 --> 00:03:17.280 align:start position:0% already been fixed so that kind of shows 00:03:17.280 --> 00:03:19.509 align:start position:0% already been fixed so that kind of shows that<00:03:17.480> these<00:03:17.640> bugs<00:03:17.959> are<00:03:18.200> really<00:03:18.920> uh<00:03:19.080> taken 00:03:19.509 --> 00:03:19.519 align:start position:0% that these bugs are really uh taken 00:03:19.519 --> 00:03:22.750 align:start position:0% that these bugs are really uh taken seriously<00:03:20.519> and<00:03:21.120> um<00:03:21.519> developers<00:03:22.519> sometimes 00:03:22.750 --> 00:03:22.760 align:start position:0% seriously and um developers sometimes 00:03:22.760 --> 00:03:24.670 align:start position:0% seriously and um developers sometimes respond<00:03:23.120> within<00:03:23.400> hours<00:03:24.000> to<00:03:24.239> actually<00:03:24.519> get 00:03:24.670 --> 00:03:24.680 align:start position:0% respond within hours to actually get 00:03:24.680 --> 00:03:25.750 align:start position:0% respond within hours to actually get them 00:03:25.750 --> 00:03:25.760 align:start position:0% them 00:03:25.760 --> 00:03:28.630 align:start position:0% them fixed<00:03:26.760> um<00:03:26.959> you<00:03:27.080> can<00:03:27.200> also<00:03:27.360> see<00:03:27.560> a<00:03:27.720> kind<00:03:27.840> of<00:03:28.480> uh 00:03:28.630 --> 00:03:28.640 align:start position:0% fixed um you can also see a kind of uh 00:03:28.640 --> 00:03:30.309 align:start position:0% fixed um you can also see a kind of uh breakdown<00:03:29.159> of<00:03:29.319> the<00:03:29.400> different 00:03:30.309 --> 00:03:30.319 align:start position:0% breakdown of the different 00:03:30.319 --> 00:03:32.550 align:start position:0% breakdown of the different bugs<00:03:30.680> and<00:03:30.840> where<00:03:31.000> we<00:03:31.159> found<00:03:31.439> them<00:03:32.239> and<00:03:32.400> as<00:03:32.480> you 00:03:32.550 --> 00:03:32.560 align:start position:0% bugs and where we found them and as you 00:03:32.560 --> 00:03:34.229 align:start position:0% bugs and where we found them and as you can<00:03:32.720> see<00:03:32.959> they're<00:03:33.200> kind<00:03:33.319> of<00:03:33.680> very<00:03:33.879> evenly 00:03:34.229 --> 00:03:34.239 align:start position:0% can see they're kind of very evenly 00:03:34.239 --> 00:03:36.830 align:start position:0% can see they're kind of very evenly spread<00:03:34.560> across<00:03:34.799> the<00:03:35.000> different<00:03:35.680> uh<00:03:35.840> pipelines 00:03:36.830 --> 00:03:36.840 align:start position:0% spread across the different uh pipelines 00:03:36.840 --> 00:03:39.710 align:start position:0% spread across the different uh pipelines so<00:03:37.080> it's<00:03:37.239> not<00:03:37.480> like<00:03:38.000> there's<00:03:38.720> one<00:03:39.280> pipeline 00:03:39.710 --> 00:03:39.720 align:start position:0% so it's not like there's one pipeline 00:03:39.720 --> 00:03:41.670 align:start position:0% so it's not like there's one pipeline that's<00:03:40.040> you<00:03:40.159> know<00:03:40.720> responsible<00:03:41.200> for<00:03:41.400> all<00:03:41.560> the 00:03:41.670 --> 00:03:41.680 align:start position:0% that's you know responsible for all the 00:03:41.680 --> 00:03:44.589 align:start position:0% that's you know responsible for all the bugs<00:03:42.599> uh<00:03:42.680> that<00:03:42.799> we 00:03:44.589 --> 00:03:44.599 align:start position:0% bugs uh that we 00:03:44.599 --> 00:03:48.350 align:start position:0% bugs uh that we found<00:03:45.599> um<00:03:46.159> now<00:03:46.879> kind<00:03:47.000> of<00:03:47.239> to<00:03:47.400> make<00:03:47.560> sure<00:03:47.920> that 00:03:48.350 --> 00:03:48.360 align:start position:0% found um now kind of to make sure that 00:03:48.360 --> 00:03:51.390 align:start position:0% found um now kind of to make sure that everybody<00:03:49.040> understands<00:03:49.640> I<00:03:49.720> mean<00:03:50.560> like<00:03:50.879> I<00:03:51.280> yeah 00:03:51.390 --> 00:03:51.400 align:start position:0% everybody understands I mean like I yeah 00:03:51.400 --> 00:03:54.030 align:start position:0% everybody understands I mean like I yeah I<00:03:51.560> assume<00:03:52.000> not<00:03:52.560> all<00:03:52.840> people<00:03:53.120> are<00:03:53.319> aware<00:03:53.560> of 00:03:54.030 --> 00:03:54.040 align:start position:0% I assume not all people are aware of 00:03:54.040 --> 00:03:56.190 align:start position:0% I assume not all people are aware of what<00:03:54.280> these<00:03:54.920> uh<00:03:55.040> processing<00:03:55.480> pipelines<00:03:55.920> look 00:03:56.190 --> 00:03:56.200 align:start position:0% what these uh processing pipelines look 00:03:56.200 --> 00:04:00.309 align:start position:0% what these uh processing pipelines look like<00:03:56.439> look<00:03:56.640> like<00:03:57.519> uh<00:03:57.640> here's<00:03:57.840> a<00:03:58.360> short<00:03:59.159> kind<00:03:59.319> of 00:04:00.309 --> 00:04:00.319 align:start position:0% like look like uh here's a short kind of 00:04:00.319 --> 00:04:03.390 align:start position:0% like look like uh here's a short kind of summary<00:04:01.319> um<00:04:01.799> you<00:04:01.920> can<00:04:02.040> see<00:04:02.439> in<00:04:02.640> the<00:04:03.079> sort<00:04:03.239> of 00:04:03.390 --> 00:04:03.400 align:start position:0% summary um you can see in the sort of 00:04:03.400 --> 00:04:06.910 align:start position:0% summary um you can see in the sort of yellow<00:04:03.720> box<00:04:04.480> um<00:04:04.879> there<00:04:05.000> is<00:04:06.000> a<00:04:06.120> circuit<00:04:06.799> that 00:04:06.910 --> 00:04:06.920 align:start position:0% yellow box um there is a circuit that 00:04:06.920 --> 00:04:09.589 align:start position:0% yellow box um there is a circuit that the<00:04:07.040> user<00:04:07.319> writes<00:04:08.159> um<00:04:08.720> that<00:04:08.840> goes<00:04:09.040> into<00:04:09.280> the 00:04:09.589 --> 00:04:09.599 align:start position:0% the user writes um that goes into the 00:04:09.599 --> 00:04:13.270 align:start position:0% the user writes um that goes into the compiler<00:04:10.599> and<00:04:10.760> then<00:04:10.959> the<00:04:11.280> compiler<00:04:12.280> um<00:04:12.599> hands 00:04:13.270 --> 00:04:13.280 align:start position:0% compiler and then the compiler um hands 00:04:13.280 --> 00:04:16.110 align:start position:0% compiler and then the compiler um hands some<00:04:13.519> output<00:04:13.840> to<00:04:13.959> the<00:04:14.079> witness<00:04:14.680> generator<00:04:15.680> and 00:04:16.110 --> 00:04:16.120 align:start position:0% some output to the witness generator and 00:04:16.120 --> 00:04:18.349 align:start position:0% some output to the witness generator and the<00:04:16.239> witness<00:04:16.600> generator<00:04:17.160> can<00:04:17.359> then<00:04:17.720> take<00:04:18.079> the 00:04:18.349 --> 00:04:18.359 align:start position:0% the witness generator can then take the 00:04:18.359 --> 00:04:21.590 align:start position:0% the witness generator can then take the input<00:04:19.000> so<00:04:19.199> the<00:04:19.400> you<00:04:19.880> the<00:04:20.079> user<00:04:20.440> input<00:04:21.320> uh<00:04:21.440> to 00:04:21.590 --> 00:04:21.600 align:start position:0% input so the you the user input uh to 00:04:21.600 --> 00:04:25.270 align:start position:0% input so the you the user input uh to the<00:04:21.960> circuit<00:04:22.960> and<00:04:23.320> generate<00:04:23.759> a<00:04:24.120> witness<00:04:25.120> uh 00:04:25.270 --> 00:04:25.280 align:start position:0% the circuit and generate a witness uh 00:04:25.280 --> 00:04:27.590 align:start position:0% the circuit and generate a witness uh that<00:04:25.400> can<00:04:25.520> be<00:04:25.720> then<00:04:25.960> used<00:04:26.320> by<00:04:26.440> the<00:04:26.600> prover<00:04:27.479> and 00:04:27.590 --> 00:04:27.600 align:start position:0% that can be then used by the prover and 00:04:27.600 --> 00:04:29.230 align:start position:0% that can be then used by the prover and then<00:04:27.720> theover<00:04:28.120> generates<00:04:28.479> a<00:04:28.600> proof<00:04:28.919> that<00:04:29.039> can 00:04:29.230 --> 00:04:29.240 align:start position:0% then theover generates a proof that can 00:04:29.240 --> 00:04:31.310 align:start position:0% then theover generates a proof that can then<00:04:29.360> be<00:04:29.479> very<00:04:29.720> verified<00:04:30.639> to<00:04:30.919> essentially 00:04:31.310 --> 00:04:31.320 align:start position:0% then be very verified to essentially 00:04:31.320 --> 00:04:35.870 align:start position:0% then be very verified to essentially check<00:04:31.759> that<00:04:32.280> the<00:04:32.440> circuit<00:04:32.919> was<00:04:33.400> actually 00:04:35.870 --> 00:04:35.880 align:start position:0% 00:04:35.880 --> 00:04:40.189 align:start position:0% executed<00:04:37.160> so<00:04:38.160> um<00:04:38.360> now<00:04:38.560> that<00:04:38.759> we<00:04:39.280> have<00:04:39.440> a<00:04:39.919> bit<00:04:40.080> of 00:04:40.189 --> 00:04:40.199 align:start position:0% executed so um now that we have a bit of 00:04:40.199 --> 00:04:41.870 align:start position:0% executed so um now that we have a bit of an<00:04:40.560> understanding<00:04:40.840> of<00:04:41.039> how<00:04:41.240> these<00:04:41.440> pipelines 00:04:41.870 --> 00:04:41.880 align:start position:0% an understanding of how these pipelines 00:04:41.880 --> 00:04:46.029 align:start position:0% an understanding of how these pipelines look<00:04:42.120> like<00:04:42.919> let's<00:04:43.800> uh<00:04:44.080> dive<00:04:44.320> a<00:04:44.479> bit<00:04:45.199> uh<00:04:45.320> deeper 00:04:46.029 --> 00:04:46.039 align:start position:0% look like let's uh dive a bit uh deeper 00:04:46.039 --> 00:04:49.270 align:start position:0% look like let's uh dive a bit uh deeper to<00:04:46.639> understand<00:04:47.120> how<00:04:47.400> we<00:04:47.639> find<00:04:47.960> these 00:04:49.270 --> 00:04:49.280 align:start position:0% to understand how we find these 00:04:49.280 --> 00:04:53.230 align:start position:0% to understand how we find these bugs<00:04:50.280> so<00:04:50.759> first<00:04:51.199> I<00:04:51.280> want<00:04:51.400> to<00:04:51.479> be<00:04:51.639> very<00:04:51.800> clear<00:04:52.440> um 00:04:53.230 --> 00:04:53.240 align:start position:0% bugs so first I want to be very clear um 00:04:53.240 --> 00:04:55.270 align:start position:0% bugs so first I want to be very clear um we<00:04:53.400> are<00:04:53.520> not<00:04:53.840> cryptographers<00:04:54.840> this<00:04:54.960> is<00:04:55.080> not 00:04:55.270 --> 00:04:55.280 align:start position:0% we are not cryptographers this is not 00:04:55.280 --> 00:04:56.749 align:start position:0% we are not cryptographers this is not our<00:04:55.680> uh<00:04:55.800> this<00:04:55.880> is<00:04:56.000> not<00:04:56.120> my<00:04:56.240> background<00:04:56.639> my 00:04:56.749 --> 00:04:56.759 align:start position:0% our uh this is not my background my 00:04:56.759 --> 00:04:58.909 align:start position:0% our uh this is not my background my background<00:04:57.080> is<00:04:57.199> in<00:04:57.800> you<00:04:57.919> know<00:04:58.360> uh<00:04:58.479> software 00:04:58.909 --> 00:04:58.919 align:start position:0% background is in you know uh software 00:04:58.919 --> 00:05:00.749 align:start position:0% background is in you know uh software security<00:04:59.759> uh<00:04:59.880> program 00:05:00.749 --> 00:05:00.759 align:start position:0% security uh program 00:05:00.759 --> 00:05:04.510 align:start position:0% security uh program analysis<00:05:01.759> um<00:05:02.360> and<00:05:02.800> for<00:05:03.000> this<00:05:03.199> reason<00:05:03.880> I<00:05:04.240> can't 00:05:04.510 --> 00:05:04.520 align:start position:0% analysis um and for this reason I can't 00:05:04.520 --> 00:05:06.870 align:start position:0% analysis um and for this reason I can't really<00:05:04.960> you<00:05:05.080> know<00:05:05.320> try<00:05:05.560> to<00:05:06.000> understand<00:05:06.600> the 00:05:06.870 --> 00:05:06.880 align:start position:0% really you know try to understand the 00:05:06.880 --> 00:05:10.270 align:start position:0% really you know try to understand the the<00:05:07.000> logic<00:05:07.720> that's<00:05:08.280> in<00:05:09.280> the<00:05:09.400> integrate<00:05:09.880> log 00:05:10.270 --> 00:05:10.280 align:start position:0% the logic that's in the integrate log 00:05:10.280 --> 00:05:11.870 align:start position:0% the logic that's in the integrate log logic<00:05:10.639> in<00:05:10.800> many<00:05:11.000> of<00:05:11.160> these 00:05:11.870 --> 00:05:11.880 align:start position:0% logic in many of these 00:05:11.880 --> 00:05:15.990 align:start position:0% logic in many of these components<00:05:12.880> um<00:05:13.080> which<00:05:13.240> is<00:05:13.919> uh<00:05:14.199> why<00:05:14.680> we<00:05:15.000> treat 00:05:15.990 --> 00:05:16.000 align:start position:0% components um which is uh why we treat 00:05:16.000 --> 00:05:18.029 align:start position:0% components um which is uh why we treat these<00:05:16.240> essentially<00:05:16.600> as<00:05:16.720> a<00:05:16.840> blackbox<00:05:17.440> so<00:05:17.800> much 00:05:18.029 --> 00:05:18.039 align:start position:0% these essentially as a blackbox so much 00:05:18.039 --> 00:05:20.830 align:start position:0% these essentially as a blackbox so much like<00:05:18.440> what<00:05:18.759> a<00:05:19.080> typical<00:05:19.400> user<00:05:19.680> would<00:05:19.880> do<00:05:20.600> uh<00:05:20.680> we 00:05:20.830 --> 00:05:20.840 align:start position:0% like what a typical user would do uh we 00:05:20.840 --> 00:05:22.990 align:start position:0% like what a typical user would do uh we just<00:05:20.960> view<00:05:21.280> them<00:05:21.560> as<00:05:21.639> a 00:05:22.990 --> 00:05:23.000 align:start position:0% just view them as a 00:05:23.000 --> 00:05:25.189 align:start position:0% just view them as a blackbox<00:05:24.000> so<00:05:24.240> how<00:05:24.360> can<00:05:24.520> we<00:05:24.639> still<00:05:24.840> find<00:05:25.039> all 00:05:25.189 --> 00:05:25.199 align:start position:0% blackbox so how can we still find all 00:05:25.199 --> 00:05:28.790 align:start position:0% blackbox so how can we still find all these<00:05:25.360> bugs<00:05:26.080> right<00:05:26.880> well<00:05:27.440> first<00:05:28.160> we<00:05:28.560> have<00:05:28.720> a 00:05:28.790 --> 00:05:28.800 align:start position:0% these bugs right well first we have a 00:05:28.800 --> 00:05:30.150 align:start position:0% these bugs right well first we have a lot<00:05:28.960> of<00:05:29.120> experience 00:05:30.150 --> 00:05:30.160 align:start position:0% lot of experience 00:05:30.160 --> 00:05:33.950 align:start position:0% lot of experience uh<00:05:30.319> in<00:05:30.880> testing<00:05:31.880> uh<00:05:32.199> complex<00:05:33.199> or<00:05:33.440> software<00:05:33.759> for 00:05:33.950 --> 00:05:33.960 align:start position:0% uh in testing uh complex or software for 00:05:33.960 --> 00:05:36.270 align:start position:0% uh in testing uh complex or software for complex<00:05:34.319> domains<00:05:35.280> and<00:05:35.440> building<00:05:35.680> fuzzers<00:05:36.080> for 00:05:36.270 --> 00:05:36.280 align:start position:0% complex domains and building fuzzers for 00:05:36.280 --> 00:05:39.150 align:start position:0% complex domains and building fuzzers for them<00:05:37.039> so<00:05:37.440> we've<00:05:37.720> done<00:05:38.280> quite<00:05:38.440> a<00:05:38.560> bit<00:05:38.680> of<00:05:38.840> work 00:05:39.150 --> 00:05:39.160 align:start position:0% them so we've done quite a bit of work 00:05:39.160 --> 00:05:41.710 align:start position:0% them so we've done quite a bit of work on<00:05:39.800> uh<00:05:39.919> fuzzing<00:05:40.360> for<00:05:40.600> smart<00:05:40.960> contracts<00:05:41.520> it's 00:05:41.710 --> 00:05:41.720 align:start position:0% on uh fuzzing for smart contracts it's 00:05:41.720 --> 00:05:44.590 align:start position:0% on uh fuzzing for smart contracts it's probably<00:05:42.039> the<00:05:42.319> work<00:05:42.600> that's<00:05:42.800> most<00:05:43.360> closely<00:05:44.360> to 00:05:44.590 --> 00:05:44.600 align:start position:0% probably the work that's most closely to 00:05:44.600 --> 00:05:48.189 align:start position:0% probably the work that's most closely to the<00:05:44.720> audience<00:05:45.160> that's<00:05:45.600> here<00:05:46.600> um<00:05:47.560> and<00:05:48.000> for 00:05:48.189 --> 00:05:48.199 align:start position:0% the audience that's here um and for 00:05:48.199 --> 00:05:51.350 align:start position:0% the audience that's here um and for instance<00:05:48.479> we<00:05:48.639> created<00:05:49.000> the<00:05:49.199> Harvey<00:05:49.919> fuzzer<00:05:50.919> um 00:05:51.350 --> 00:05:51.360 align:start position:0% instance we created the Harvey fuzzer um 00:05:51.360 --> 00:05:52.950 align:start position:0% instance we created the Harvey fuzzer um many<00:05:51.600> years<00:05:51.800> ago<00:05:52.120> and<00:05:52.240> we're<00:05:52.440> still<00:05:52.720> kind<00:05:52.840> of 00:05:52.950 --> 00:05:52.960 align:start position:0% many years ago and we're still kind of 00:05:52.960 --> 00:05:55.830 align:start position:0% many years ago and we're still kind of maintaining<00:05:53.600> it<00:05:54.600> um<00:05:55.000> we<00:05:55.120> also<00:05:55.319> did<00:05:55.440> some<00:05:55.600> work 00:05:55.830 --> 00:05:55.840 align:start position:0% maintaining it um we also did some work 00:05:55.840 --> 00:05:59.670 align:start position:0% maintaining it um we also did some work on<00:05:56.039> ML<00:05:56.600> models<00:05:57.600> um<00:05:57.840> and<00:05:58.039> on<00:05:58.600> on<00:05:58.800> testing<00:05:59.280> ml 00:05:59.670 --> 00:05:59.680 align:start position:0% on ML models um and on on testing ml 00:05:59.680 --> 00:06:02.309 align:start position:0% on ML models um and on on testing ml models<00:06:00.039> and<00:06:00.520> testing<00:06:01.000> program<00:06:01.360> analysis 00:06:02.309 --> 00:06:02.319 align:start position:0% models and testing program analysis 00:06:02.319 --> 00:06:04.909 align:start position:0% models and testing program analysis tools<00:06:03.319> um<00:06:03.720> yeah<00:06:03.840> if<00:06:03.919> you<00:06:04.039> want<00:06:04.120> to<00:06:04.240> know<00:06:04.440> more 00:06:04.909 --> 00:06:04.919 align:start position:0% tools um yeah if you want to know more 00:06:04.919 --> 00:06:09.270 align:start position:0% tools um yeah if you want to know more check<00:06:05.120> out<00:06:05.280> the<00:06:05.479> papers<00:06:05.919> that<00:06:06.280> are<00:06:07.280> um<00:06:08.280> online 00:06:09.270 --> 00:06:09.280 align:start position:0% check out the papers that are um online 00:06:09.280 --> 00:06:11.990 align:start position:0% check out the papers that are um online um<00:06:09.639> and<00:06:09.919> the<00:06:10.080> second<00:06:10.759> reason<00:06:11.280> why<00:06:11.599> we<00:06:11.840> were 00:06:11.990 --> 00:06:12.000 align:start position:0% um and the second reason why we were 00:06:12.000 --> 00:06:13.670 align:start position:0% um and the second reason why we were able<00:06:12.199> to<00:06:12.319> find<00:06:12.560> these<00:06:12.720> bugs<00:06:13.199> is<00:06:13.319> that<00:06:13.479> we<00:06:13.560> have 00:06:13.670 --> 00:06:13.680 align:start position:0% able to find these bugs is that we have 00:06:13.680 --> 00:06:15.670 align:start position:0% able to find these bugs is that we have a<00:06:13.880> not<00:06:14.160> so<00:06:14.319> secret<00:06:14.720> weapon<00:06:15.240> which<00:06:15.360> is<00:06:15.440> called 00:06:15.670 --> 00:06:15.680 align:start position:0% a not so secret weapon which is called 00:06:15.680 --> 00:06:17.830 align:start position:0% a not so secret weapon which is called metamorphic 00:06:17.830 --> 00:06:17.840 align:start position:0% metamorphic 00:06:17.840 --> 00:06:21.830 align:start position:0% metamorphic testing<00:06:18.840> so<00:06:19.120> before<00:06:20.039> um<00:06:20.479> explaining<00:06:21.479> in<00:06:21.599> a<00:06:21.680> bit 00:06:21.830 --> 00:06:21.840 align:start position:0% testing so before um explaining in a bit 00:06:21.840 --> 00:06:23.629 align:start position:0% testing so before um explaining in a bit more<00:06:22.000> detail<00:06:22.360> what<00:06:22.520> metamorphic<00:06:23.120> testing<00:06:23.440> is 00:06:23.629 --> 00:06:23.639 align:start position:0% more detail what metamorphic testing is 00:06:23.639 --> 00:06:26.110 align:start position:0% more detail what metamorphic testing is let<00:06:23.759> me<00:06:23.919> just<00:06:24.080> give<00:06:24.199> you<00:06:24.400> kind<00:06:24.520> of<00:06:24.759> a<00:06:25.520> uh<00:06:25.840> short 00:06:26.110 --> 00:06:26.120 align:start position:0% let me just give you kind of a uh short 00:06:26.120 --> 00:06:28.070 align:start position:0% let me just give you kind of a uh short summary<00:06:26.520> of<00:06:26.840> how<00:06:27.000> we<00:06:27.160> got<00:06:27.400> here<00:06:27.639> how<00:06:27.759> we<00:06:27.919> got 00:06:28.070 --> 00:06:28.080 align:start position:0% summary of how we got here how we got 00:06:28.080 --> 00:06:31.629 align:start position:0% summary of how we got here how we got into<00:06:28.360> this<00:06:28.800> uh<00:06:28.919> interested<00:06:29.280> in<00:06:29.400> this<00:06:29.919> topic<00:06:30.919> um 00:06:31.629 --> 00:06:31.639 align:start position:0% into this uh interested in this topic um 00:06:31.639 --> 00:06:35.070 align:start position:0% into this uh interested in this topic um so<00:06:31.960> we<00:06:32.599> as<00:06:32.720> I<00:06:32.840> said<00:06:33.400> we<00:06:33.560> were<00:06:34.160> um<00:06:34.280> working<00:06:34.599> on 00:06:35.070 --> 00:06:35.080 align:start position:0% so we as I said we were um working on 00:06:35.080 --> 00:06:37.670 align:start position:0% so we as I said we were um working on fuzzing<00:06:35.479> for<00:06:35.639> smart<00:06:35.919> contracts<00:06:36.479> mainly<00:06:37.479> uh 00:06:37.670 --> 00:06:37.680 align:start position:0% fuzzing for smart contracts mainly uh 00:06:37.680 --> 00:06:40.309 align:start position:0% fuzzing for smart contracts mainly uh for<00:06:37.880> many<00:06:38.120> years<00:06:38.639> and<00:06:38.840> then<00:06:39.080> at<00:06:39.199> some<00:06:39.400> point<00:06:40.160> um 00:06:40.309 --> 00:06:40.319 align:start position:0% for many years and then at some point um 00:06:40.319 --> 00:06:43.629 align:start position:0% for many years and then at some point um I<00:06:40.440> guess<00:06:40.880> maybe<00:06:41.199> like<00:06:41.639> a<00:06:41.759> year<00:06:41.960> ago<00:06:42.440> roughly<00:06:43.440> um 00:06:43.629 --> 00:06:43.639 align:start position:0% I guess maybe like a year ago roughly um 00:06:43.639 --> 00:06:45.469 align:start position:0% I guess maybe like a year ago roughly um consensus<00:06:44.160> they<00:06:44.319> released<00:06:44.840> the<00:06:45.039> linear 00:06:45.469 --> 00:06:45.479 align:start position:0% consensus they released the linear 00:06:45.479 --> 00:06:48.510 align:start position:0% consensus they released the linear blockchain<00:06:46.479> um<00:06:47.199> that<00:06:47.440> is<00:06:47.639> one<00:06:47.759> of<00:06:47.880> the<00:06:48.000> first 00:06:48.510 --> 00:06:48.520 align:start position:0% blockchain um that is one of the first 00:06:48.520 --> 00:06:49.749 align:start position:0% blockchain um that is one of the first ZK 00:06:49.749 --> 00:06:49.759 align:start position:0% ZK 00:06:49.759 --> 00:06:52.430 align:start position:0% ZK EVMS<00:06:50.759> and<00:06:50.919> we<00:06:51.080> were<00:06:51.360> like<00:06:51.919> well<00:06:52.160> this<00:06:52.280> is 00:06:52.430 --> 00:06:52.440 align:start position:0% EVMS and we were like well this is 00:06:52.440 --> 00:06:54.270 align:start position:0% EVMS and we were like well this is really<00:06:52.720> complex<00:06:53.360> uh<00:06:53.560> we<00:06:53.720> started<00:06:54.039> looking 00:06:54.270 --> 00:06:54.280 align:start position:0% really complex uh we started looking 00:06:54.280 --> 00:06:56.749 align:start position:0% really complex uh we started looking into<00:06:54.479> it<00:06:54.639> a<00:06:54.759> bit<00:06:55.400> um<00:06:56.120> and<00:06:56.240> we<00:06:56.360> saw<00:06:56.560> that<00:06:56.680> there 00:06:56.749 --> 00:06:56.759 align:start position:0% into it a bit um and we saw that there 00:06:56.759 --> 00:06:58.710 align:start position:0% into it a bit um and we saw that there are<00:06:56.960> these<00:06:57.240> components<00:06:57.840> like<00:06:58.160> the<00:06:58.360> Gnar 00:06:58.710 --> 00:06:58.720 align:start position:0% are these components like the Gnar 00:06:58.720 --> 00:07:02.110 align:start position:0% are these components like the Gnar library<00:06:59.360> and<00:06:59.599> and<00:06:59.759> the<00:07:00.039> corset<00:07:01.039> language<00:07:01.440> for 00:07:02.110 --> 00:07:02.120 align:start position:0% library and and the corset language for 00:07:02.120 --> 00:07:05.110 align:start position:0% library and and the corset language for um<00:07:02.360> processing<00:07:02.840> zero<00:07:03.240> knowledge<00:07:03.879> circuits<00:07:04.879> so 00:07:05.110 --> 00:07:05.120 align:start position:0% um processing zero knowledge circuits so 00:07:05.120 --> 00:07:07.390 align:start position:0% um processing zero knowledge circuits so we<00:07:05.240> were<00:07:05.479> like<00:07:05.879> oh<00:07:06.240> what<00:07:06.360> can<00:07:06.440> we<00:07:06.599> do<00:07:06.759> to<00:07:07.280> you 00:07:07.390 --> 00:07:07.400 align:start position:0% we were like oh what can we do to you 00:07:07.400 --> 00:07:10.469 align:start position:0% we were like oh what can we do to you know<00:07:08.240> um<00:07:09.120> test<00:07:09.479> these<00:07:09.759> what<00:07:09.919> can<00:07:10.039> we<00:07:10.160> do<00:07:10.319> to 00:07:10.469 --> 00:07:10.479 align:start position:0% know um test these what can we do to 00:07:10.479 --> 00:07:12.830 align:start position:0% know um test these what can we do to make<00:07:10.639> sure<00:07:10.800> that<00:07:10.919> there<00:07:11.120> no<00:07:11.280> bugs<00:07:11.759> in<00:07:12.000> these 00:07:12.830 --> 00:07:12.840 align:start position:0% make sure that there no bugs in these 00:07:12.840 --> 00:07:15.309 align:start position:0% make sure that there no bugs in these components<00:07:13.840> um<00:07:14.039> and<00:07:14.160> that's<00:07:14.319> when<00:07:14.479> we<00:07:14.680> started 00:07:15.309 --> 00:07:15.319 align:start position:0% components um and that's when we started 00:07:15.319 --> 00:07:17.830 align:start position:0% components um and that's when we started building<00:07:16.199> um<00:07:16.599> kind<00:07:16.720> of<00:07:16.800> a<00:07:16.919> predecessor<00:07:17.599> to 00:07:17.830 --> 00:07:17.840 align:start position:0% building um kind of a predecessor to 00:07:17.840 --> 00:07:20.270 align:start position:0% building um kind of a predecessor to this<00:07:18.000> fuzzer<00:07:18.800> uh<00:07:18.960> I'm<00:07:19.120> presenting<00:07:19.479> today<00:07:20.160> uh 00:07:20.270 --> 00:07:20.280 align:start position:0% this fuzzer uh I'm presenting today uh 00:07:20.280 --> 00:07:21.430 align:start position:0% this fuzzer uh I'm presenting today uh which<00:07:20.400> is<00:07:20.639> called 00:07:21.430 --> 00:07:21.440 align:start position:0% which is called 00:07:21.440 --> 00:07:26.230 align:start position:0% which is called Rio<00:07:22.440> um<00:07:22.840> so<00:07:23.120> the<00:07:23.280> Rio<00:07:24.120> is<00:07:24.199> a<00:07:24.319> fer<00:07:24.720> for<00:07:25.199> the<00:07:25.440> Gnar 00:07:26.230 --> 00:07:26.240 align:start position:0% Rio um so the Rio is a fer for the Gnar 00:07:26.240 --> 00:07:27.950 align:start position:0% Rio um so the Rio is a fer for the Gnar Library<00:07:26.759> specifically<00:07:27.680> and<00:07:27.800> then 00:07:27.950 --> 00:07:27.960 align:start position:0% Library specifically and then 00:07:27.960 --> 00:07:30.110 align:start position:0% Library specifically and then essentially<00:07:28.440> this<00:07:29.120> uh<00:07:29.240> C<00:07:29.520> ccus<00:07:29.720> fuzzer<00:07:30.000> I'm 00:07:30.110 --> 00:07:30.120 align:start position:0% essentially this uh C ccus fuzzer I'm 00:07:30.120 --> 00:07:31.390 align:start position:0% essentially this uh C ccus fuzzer I'm presenting<00:07:30.440> today<00:07:30.759> is<00:07:30.879> essentially<00:07:31.240> an 00:07:31.390 --> 00:07:31.400 align:start position:0% presenting today is essentially an 00:07:31.400 --> 00:07:34.309 align:start position:0% presenting today is essentially an evolution<00:07:32.199> of<00:07:32.520> this<00:07:33.080> uh<00:07:33.199> fuzzer<00:07:34.000> that<00:07:34.120> is<00:07:34.199> a 00:07:34.309 --> 00:07:34.319 align:start position:0% evolution of this uh fuzzer that is a 00:07:34.319 --> 00:07:37.350 align:start position:0% evolution of this uh fuzzer that is a bit<00:07:34.479> more<00:07:34.639> General<00:07:35.199> and<00:07:35.599> can<00:07:35.800> Target<00:07:36.479> multiple 00:07:37.350 --> 00:07:37.360 align:start position:0% bit more General and can Target multiple 00:07:37.360 --> 00:07:39.469 align:start position:0% bit more General and can Target multiple um 00:07:39.469 --> 00:07:39.479 align:start position:0% um 00:07:39.479 --> 00:07:42.550 align:start position:0% um dsls<00:07:40.479> all<00:07:40.639> right<00:07:41.280> now<00:07:41.879> uh<00:07:42.080> back<00:07:42.240> to 00:07:42.550 --> 00:07:42.560 align:start position:0% dsls all right now uh back to 00:07:42.560 --> 00:07:44.350 align:start position:0% dsls all right now uh back to metamorphic<00:07:43.160> testing<00:07:43.960> so<00:07:44.159> what<00:07:44.240> is 00:07:44.350 --> 00:07:44.360 align:start position:0% metamorphic testing so what is 00:07:44.360 --> 00:07:46.189 align:start position:0% metamorphic testing so what is metamorphic<00:07:44.919> testing<00:07:45.639> um<00:07:45.800> I<00:07:45.879> think<00:07:46.039> the 00:07:46.189 --> 00:07:46.199 align:start position:0% metamorphic testing um I think the 00:07:46.199 --> 00:07:48.070 align:start position:0% metamorphic testing um I think the shortest<00:07:46.560> way<00:07:46.680> to<00:07:46.840> summarize<00:07:47.280> it<00:07:47.599> it's<00:07:47.960> kind 00:07:48.070 --> 00:07:48.080 align:start position:0% shortest way to summarize it it's kind 00:07:48.080 --> 00:07:51.270 align:start position:0% shortest way to summarize it it's kind of<00:07:48.199> a<00:07:48.319> way<00:07:48.440> to<00:07:48.639> define<00:07:49.000> test<00:07:49.440> oracles<00:07:50.440> uh<00:07:50.560> in<00:07:50.639> a 00:07:51.270 --> 00:07:51.280 align:start position:0% of a way to define test oracles uh in a 00:07:51.280 --> 00:07:54.830 align:start position:0% of a way to define test oracles uh in a pretty<00:07:51.639> elegant<00:07:52.280> and<00:07:52.639> concise<00:07:53.159> way<00:07:54.159> so<00:07:54.639> to 00:07:54.830 --> 00:07:54.840 align:start position:0% pretty elegant and concise way so to 00:07:54.840 --> 00:07:58.869 align:start position:0% pretty elegant and concise way so to illustrate<00:07:55.720> I've<00:07:56.639> um<00:07:57.639> I've<00:07:58.159> uh<00:07:58.400> collected<00:07:58.759> a 00:07:58.869 --> 00:07:58.879 align:start position:0% illustrate I've um I've uh collected a 00:07:58.879 --> 00:08:02.710 align:start position:0% illustrate I've um I've uh collected a few<00:07:59.080> examples<00:07:59.840> that<00:08:00.360> um<00:08:01.120> yeah<00:08:01.759> explain<00:08:02.199> this 00:08:02.710 --> 00:08:02.720 align:start position:0% few examples that um yeah explain this 00:08:02.720 --> 00:08:04.990 align:start position:0% few examples that um yeah explain this uh<00:08:02.800> and<00:08:02.919> try<00:08:03.159> to<00:08:03.879> um<00:08:04.440> explain<00:08:04.879> what 00:08:04.990 --> 00:08:05.000 align:start position:0% uh and try to um explain what 00:08:05.000 --> 00:08:08.029 align:start position:0% uh and try to um explain what metamorphic<00:08:05.560> testing<00:08:05.960> is<00:08:06.759> so<00:08:07.680> the<00:08:07.800> first 00:08:08.029 --> 00:08:08.039 align:start position:0% metamorphic testing is so the first 00:08:08.039 --> 00:08:10.270 align:start position:0% metamorphic testing is so the first example<00:08:08.319> is<00:08:08.599> how<00:08:08.800> to<00:08:09.360> actually<00:08:09.680> test<00:08:10.000> that<00:08:10.159> the 00:08:10.270 --> 00:08:10.280 align:start position:0% example is how to actually test that the 00:08:10.280 --> 00:08:13.390 align:start position:0% example is how to actually test that the Sorting<00:08:10.639> function<00:08:11.479> uh<00:08:11.599> sort<00:08:12.319> for<00:08:12.720> an<00:08:12.879> input 00:08:13.390 --> 00:08:13.400 align:start position:0% Sorting function uh sort for an input 00:08:13.400 --> 00:08:15.589 align:start position:0% Sorting function uh sort for an input let's<00:08:13.560> say<00:08:13.720> an<00:08:13.840> array<00:08:14.240> of<00:08:14.400> integers<00:08:14.879> X 00:08:15.589 --> 00:08:15.599 align:start position:0% let's say an array of integers X 00:08:15.599 --> 00:08:17.510 align:start position:0% let's say an array of integers X actually<00:08:15.800> does<00:08:16.039> the<00:08:16.159> right<00:08:16.360> thing<00:08:17.360> well 00:08:17.510 --> 00:08:17.520 align:start position:0% actually does the right thing well 00:08:17.520 --> 00:08:19.950 align:start position:0% actually does the right thing well there's<00:08:17.800> many<00:08:18.039> ways<00:08:18.280> to<00:08:18.520> to<00:08:18.680> check<00:08:19.039> this<00:08:19.720> but 00:08:19.950 --> 00:08:19.960 align:start position:0% there's many ways to to check this but 00:08:19.960 --> 00:08:22.589 align:start position:0% there's many ways to to check this but here's<00:08:20.879> uh<00:08:21.000> a<00:08:21.120> way<00:08:21.280> to<00:08:21.440> check<00:08:21.680> it<00:08:22.240> um<00:08:22.319> using 00:08:22.589 --> 00:08:22.599 align:start position:0% here's uh a way to check it um using 00:08:22.599 --> 00:08:26.629 align:start position:0% here's uh a way to check it um using metamorphic<00:08:23.440> testing<00:08:24.440> so<00:08:24.720> you<00:08:24.960> take<00:08:25.560> you<00:08:25.720> sort 00:08:26.629 --> 00:08:26.639 align:start position:0% metamorphic testing so you take you sort 00:08:26.639 --> 00:08:29.510 align:start position:0% metamorphic testing so you take you sort um<00:08:26.879> the<00:08:27.080> input<00:08:27.479> X<00:08:28.479> and<00:08:28.639> then<00:08:28.840> you<00:08:29.000> also<00:08:29.199> sort 00:08:29.510 --> 00:08:29.520 align:start position:0% um the input X and then you also sort 00:08:29.520 --> 00:08:32.430 align:start position:0% um the input X and then you also sort for<00:08:30.199> uh<00:08:30.360> X<00:08:30.800> but<00:08:30.919> you<00:08:31.039> Shuffle<00:08:31.400> it<00:08:31.599> randomly 00:08:32.430 --> 00:08:32.440 align:start position:0% for uh X but you Shuffle it randomly 00:08:32.440 --> 00:08:35.870 align:start position:0% for uh X but you Shuffle it randomly right<00:08:33.200> and<00:08:33.440> these<00:08:33.719> two<00:08:34.719> um<00:08:35.120> the<00:08:35.279> output<00:08:35.640> of 00:08:35.870 --> 00:08:35.880 align:start position:0% right and these two um the output of 00:08:35.880 --> 00:08:37.670 align:start position:0% right and these two um the output of both<00:08:36.039> of<00:08:36.240> these<00:08:36.680> invocations<00:08:37.279> of<00:08:37.519> the 00:08:37.670 --> 00:08:37.680 align:start position:0% both of these invocations of the 00:08:37.680 --> 00:08:39.589 align:start position:0% both of these invocations of the function<00:08:38.440> they<00:08:38.560> should<00:08:39.039> have<00:08:39.240> the<00:08:39.360> same 00:08:39.589 --> 00:08:39.599 align:start position:0% function they should have the same 00:08:39.599 --> 00:08:43.509 align:start position:0% function they should have the same output<00:08:40.279> right<00:08:41.080> so<00:08:41.719> pretty<00:08:42.399> nice<00:08:42.719> and<00:08:42.919> concise 00:08:43.509 --> 00:08:43.519 align:start position:0% output right so pretty nice and concise 00:08:43.519 --> 00:08:46.150 align:start position:0% output right so pretty nice and concise uh<00:08:44.040> specification<00:08:45.040> so<00:08:45.680> let's<00:08:45.880> look<00:08:46.000> at 00:08:46.150 --> 00:08:46.160 align:start position:0% uh specification so let's look at 00:08:46.160 --> 00:08:49.790 align:start position:0% uh specification so let's look at another<00:08:46.480> example<00:08:47.399> uh<00:08:47.600> here<00:08:48.440> um<00:08:49.320> we<00:08:49.480> want<00:08:49.600> to 00:08:49.790 --> 00:08:49.800 align:start position:0% another example uh here um we want to 00:08:49.800 --> 00:08:51.990 align:start position:0% another example uh here um we want to test<00:08:50.519> um<00:08:50.720> essentially<00:08:51.040> some<00:08:51.240> procedure<00:08:51.760> for 00:08:51.990 --> 00:08:52.000 align:start position:0% test um essentially some procedure for 00:08:52.000 --> 00:08:54.949 align:start position:0% test um essentially some procedure for computing<00:08:52.360> the<00:08:52.440> shortest<00:08:52.920> path<00:08:53.760> in<00:08:54.480> uh<00:08:54.640> graph 00:08:54.949 --> 00:08:54.959 align:start position:0% computing the shortest path in uh graph 00:08:54.959 --> 00:08:59.069 align:start position:0% computing the shortest path in uh graph G<00:08:55.920> between<00:08:56.279> the<00:08:56.399> nodes<00:08:56.880> n<00:08:57.160> and<00:08:57.600> M<00:08:58.600> so<00:08:58.839> how<00:08:59.000> can 00:08:59.069 --> 00:08:59.079 align:start position:0% G between the nodes n and M so how can 00:08:59.079 --> 00:09:01.150 align:start position:0% G between the nodes n and M so how can we<00:08:59.200> do<00:08:59.320> this<00:08:59.480> this<00:08:59.640> with<00:08:59.760> metamorphic<00:09:00.320> testing 00:09:01.150 --> 00:09:01.160 align:start position:0% we do this this with metamorphic testing 00:09:01.160 --> 00:09:03.470 align:start position:0% we do this this with metamorphic testing well<00:09:01.360> one<00:09:01.519> way<00:09:01.680> to<00:09:01.839> do<00:09:02.000> it<00:09:02.240> is<00:09:02.320> to<00:09:02.519> say<00:09:03.200> you<00:09:03.320> know 00:09:03.470 --> 00:09:03.480 align:start position:0% well one way to do it is to say you know 00:09:03.480 --> 00:09:07.230 align:start position:0% well one way to do it is to say you know the<00:09:03.560> shortest<00:09:04.040> path<00:09:04.839> um<00:09:05.240> between<00:09:05.680> n<00:09:06.000> and<00:09:06.200> M<00:09:07.120> in 00:09:07.230 --> 00:09:07.240 align:start position:0% the shortest path um between n and M in 00:09:07.240 --> 00:09:10.670 align:start position:0% the shortest path um between n and M in the<00:09:07.399> graph<00:09:07.640> G<00:09:08.640> is<00:09:08.920> less<00:09:09.240> than<00:09:10.000> uh<00:09:10.120> the<00:09:10.240> shortest 00:09:10.670 --> 00:09:10.680 align:start position:0% the graph G is less than uh the shortest 00:09:10.680 --> 00:09:15.190 align:start position:0% the graph G is less than uh the shortest path<00:09:11.279> between<00:09:11.680> n<00:09:11.959> and<00:09:12.320> n<00:09:12.640> and<00:09:13.079> n<00:09:13.320> and<00:09:13.760> M<00:09:14.760> um<00:09:15.040> in 00:09:15.190 --> 00:09:15.200 align:start position:0% path between n and n and n and M um in 00:09:15.200 --> 00:09:18.230 align:start position:0% path between n and n and n and M um in the<00:09:15.440> graph<00:09:15.839> where<00:09:16.040> we<00:09:16.519> take<00:09:16.760> G<00:09:17.200> but<00:09:17.360> we<00:09:17.519> remove 00:09:18.230 --> 00:09:18.240 align:start position:0% the graph where we take G but we remove 00:09:18.240 --> 00:09:21.389 align:start position:0% the graph where we take G but we remove uh<00:09:18.360> some<00:09:18.600> random<00:09:18.959> Edge<00:09:19.560> right<00:09:20.560> because<00:09:21.240> that 00:09:21.389 --> 00:09:21.399 align:start position:0% uh some random Edge right because that 00:09:21.399 --> 00:09:23.269 align:start position:0% uh some random Edge right because that edge<00:09:21.680> might<00:09:21.880> have<00:09:22.000> been<00:09:22.200> on<00:09:22.440> the<00:09:22.800> the<00:09:22.880> shortest 00:09:23.269 --> 00:09:23.279 align:start position:0% edge might have been on the the shortest 00:09:23.279 --> 00:09:25.990 align:start position:0% edge might have been on the the shortest path<00:09:23.760> and<00:09:23.920> then<00:09:24.560> the<00:09:24.720> shortest<00:09:25.160> path<00:09:25.720> could 00:09:25.990 --> 00:09:26.000 align:start position:0% path and then the shortest path could 00:09:26.000 --> 00:09:27.990 align:start position:0% path and then the shortest path could become<00:09:26.360> longer 00:09:27.990 --> 00:09:28.000 align:start position:0% become longer 00:09:28.000 --> 00:09:30.069 align:start position:0% become longer right<00:09:29.000> so 00:09:30.069 --> 00:09:30.079 align:start position:0% right so 00:09:30.079 --> 00:09:32.630 align:start position:0% right so we<00:09:30.200> can<00:09:30.399> also<00:09:31.040> do<00:09:31.440> apply<00:09:31.800> the<00:09:31.959> same<00:09:32.279> kind<00:09:32.399> of 00:09:32.630 --> 00:09:32.640 align:start position:0% we can also do apply the same kind of 00:09:32.640 --> 00:09:34.910 align:start position:0% we can also do apply the same kind of principle<00:09:33.000> to<00:09:33.200> more<00:09:33.440> complex<00:09:34.279> uh<00:09:34.440> components 00:09:34.910 --> 00:09:34.920 align:start position:0% principle to more complex uh components 00:09:34.920 --> 00:09:37.990 align:start position:0% principle to more complex uh components like<00:09:35.040> a<00:09:35.480> entire<00:09:35.800> compiler<00:09:36.440> right<00:09:37.200> so<00:09:37.800> here's 00:09:37.990 --> 00:09:38.000 align:start position:0% like a entire compiler right so here's 00:09:38.000 --> 00:09:39.750 align:start position:0% like a entire compiler right so here's an<00:09:38.200> example<00:09:38.560> of<00:09:38.720> how<00:09:38.880> to<00:09:39.040> do<00:09:39.240> this<00:09:39.600> with 00:09:39.750 --> 00:09:39.760 align:start position:0% an example of how to do this with 00:09:39.760 --> 00:09:42.870 align:start position:0% an example of how to do this with metamorphic<00:09:40.399> testing<00:09:41.399> um<00:09:42.279> when<00:09:42.399> you<00:09:42.560> take<00:09:42.720> a 00:09:42.870 --> 00:09:42.880 align:start position:0% metamorphic testing um when you take a 00:09:42.880 --> 00:09:45.069 align:start position:0% metamorphic testing um when you take a program<00:09:43.200> p<00:09:44.000> and<00:09:44.160> you<00:09:44.320> compile<00:09:44.680> it<00:09:44.800> and<00:09:44.959> then 00:09:45.069 --> 00:09:45.079 align:start position:0% program p and you compile it and then 00:09:45.079 --> 00:09:47.150 align:start position:0% program p and you compile it and then run<00:09:45.279> it<00:09:46.000> you<00:09:46.120> should<00:09:46.360> essentially<00:09:46.720> see<00:09:47.000> the 00:09:47.150 --> 00:09:47.160 align:start position:0% run it you should essentially see the 00:09:47.160 --> 00:09:50.230 align:start position:0% run it you should essentially see the same<00:09:47.399> behavior<00:09:48.240> as<00:09:48.399> when<00:09:48.519> you<00:09:48.720> take<00:09:49.680> um<00:09:50.079> the 00:09:50.230 --> 00:09:50.240 align:start position:0% same behavior as when you take um the 00:09:50.240 --> 00:09:52.710 align:start position:0% same behavior as when you take um the program<00:09:50.560> P<00:09:51.160> but<00:09:51.320> you<00:09:51.600> add<00:09:51.880> some<00:09:52.160> dead<00:09:52.440> code 00:09:52.710 --> 00:09:52.720 align:start position:0% program P but you add some dead code 00:09:52.720 --> 00:09:55.230 align:start position:0% program P but you add some dead code somewhere<00:09:53.279> randomly<00:09:54.279> right<00:09:54.640> and<00:09:54.760> you<00:09:54.920> compile 00:09:55.230 --> 00:09:55.240 align:start position:0% somewhere randomly right and you compile 00:09:55.240 --> 00:09:57.350 align:start position:0% somewhere randomly right and you compile it<00:09:55.399> and<00:09:55.519> you<00:09:55.640> run<00:09:55.839> it<00:09:56.480> shouldn't<00:09:56.800> matter<00:09:57.200> right 00:09:57.350 --> 00:09:57.360 align:start position:0% it and you run it shouldn't matter right 00:09:57.360 --> 00:09:58.509 align:start position:0% it and you run it shouldn't matter right should<00:09:57.560> give<00:09:57.680> you<00:09:57.800> the<00:09:57.920> same<00:09:58.120> output 00:09:58.509 --> 00:09:58.519 align:start position:0% should give you the same output 00:09:58.519 --> 00:10:01.269 align:start position:0% should give you the same output essentially 00:10:01.269 --> 00:10:01.279 align:start position:0% essentially 00:10:01.279 --> 00:10:05.310 align:start position:0% essentially so<00:10:02.279> with<00:10:02.480> this<00:10:03.120> um<00:10:04.000> let's<00:10:04.200> look<00:10:04.360> at<00:10:04.600> how<00:10:04.800> we<00:10:04.959> can 00:10:05.310 --> 00:10:05.320 align:start position:0% so with this um let's look at how we can 00:10:05.320 --> 00:10:06.990 align:start position:0% so with this um let's look at how we can apply<00:10:05.800> kind<00:10:05.920> of<00:10:06.040> the<00:10:06.160> same<00:10:06.519> reasoning 00:10:06.990 --> 00:10:07.000 align:start position:0% apply kind of the same reasoning 00:10:07.000 --> 00:10:10.190 align:start position:0% apply kind of the same reasoning principle<00:10:08.000> to<00:10:08.680> uh<00:10:08.839> zero<00:10:09.200> knowledge<00:10:09.839> uh 00:10:10.190 --> 00:10:10.200 align:start position:0% principle to uh zero knowledge uh 00:10:10.200 --> 00:10:13.230 align:start position:0% principle to uh zero knowledge uh circuits<00:10:11.200> so<00:10:11.399> the<00:10:11.519> fuzzer<00:10:11.920> what<00:10:12.040> it<00:10:12.200> does<00:10:12.680> is 00:10:13.230 --> 00:10:13.240 align:start position:0% circuits so the fuzzer what it does is 00:10:13.240 --> 00:10:15.750 align:start position:0% circuits so the fuzzer what it does is uh<00:10:13.320> it<00:10:13.440> first<00:10:13.640> generates<00:10:14.040> a<00:10:14.200> random<00:10:14.760> circuit 00:10:15.750 --> 00:10:15.760 align:start position:0% uh it first generates a random circuit 00:10:15.760 --> 00:10:19.350 align:start position:0% uh it first generates a random circuit uh<00:10:16.279> C1<00:10:17.279> and<00:10:17.480> then<00:10:17.959> it<00:10:18.480> applies<00:10:18.839> a<00:10:19.040> random 00:10:19.350 --> 00:10:19.360 align:start position:0% uh C1 and then it applies a random 00:10:19.360 --> 00:10:21.590 align:start position:0% uh C1 and then it applies a random transformation<00:10:20.040> to<00:10:20.240> C1<00:10:20.760> to<00:10:20.959> get<00:10:21.160> a<00:10:21.399> new 00:10:21.590 --> 00:10:21.600 align:start position:0% transformation to C1 to get a new 00:10:21.600 --> 00:10:24.430 align:start position:0% transformation to C1 to get a new circuit<00:10:22.079> C2<00:10:22.839> so<00:10:23.000> now<00:10:23.120> we<00:10:23.200> have<00:10:23.360> two<00:10:23.560> circuits 00:10:24.430 --> 00:10:24.440 align:start position:0% circuit C2 so now we have two circuits 00:10:24.440 --> 00:10:26.790 align:start position:0% circuit C2 so now we have two circuits that<00:10:24.560> are<00:10:25.000> essentially 00:10:26.790 --> 00:10:26.800 align:start position:0% that are essentially 00:10:26.800 --> 00:10:28.550 align:start position:0% that are essentially syntactically<00:10:27.800> perhaps<00:10:28.120> completely 00:10:28.550 --> 00:10:28.560 align:start position:0% syntactically perhaps completely 00:10:28.560 --> 00:10:30.310 align:start position:0% syntactically perhaps completely different<00:10:29.200> uh<00:10:29.440> but<00:10:29.560> semantically<00:10:30.200> they 00:10:30.310 --> 00:10:30.320 align:start position:0% different uh but semantically they 00:10:30.320 --> 00:10:32.910 align:start position:0% different uh but semantically they should<00:10:30.640> have<00:10:31.279> uh<00:10:31.399> the<00:10:31.519> same 00:10:32.910 --> 00:10:32.920 align:start position:0% should have uh the same 00:10:32.920 --> 00:10:36.030 align:start position:0% should have uh the same behavior<00:10:33.920> and<00:10:34.760> now<00:10:35.000> we<00:10:35.279> the<00:10:35.399> fuzzer<00:10:35.720> generates 00:10:36.030 --> 00:10:36.040 align:start position:0% behavior and now we the fuzzer generates 00:10:36.040 --> 00:10:40.710 align:start position:0% behavior and now we the fuzzer generates an<00:10:36.200> input<00:10:36.680> I<00:10:37.760> and<00:10:38.760> um<00:10:39.120> invokes<00:10:39.959> the<00:10:40.240> processing 00:10:40.710 --> 00:10:40.720 align:start position:0% an input I and um invokes the processing 00:10:40.720 --> 00:10:42.310 align:start position:0% an input I and um invokes the processing pipelines<00:10:41.120> for<00:10:41.320> both<00:10:41.440> of<00:10:41.639> these 00:10:42.310 --> 00:10:42.320 align:start position:0% pipelines for both of these 00:10:42.320 --> 00:10:44.949 align:start position:0% pipelines for both of these circuits<00:10:43.320> um<00:10:44.040> and<00:10:44.360> if<00:10:44.519> there's<00:10:44.760> any 00:10:44.949 --> 00:10:44.959 align:start position:0% circuits um and if there's any 00:10:44.959 --> 00:10:47.190 align:start position:0% circuits um and if there's any difference<00:10:45.519> in<00:10:46.040> you<00:10:46.160> know<00:10:46.320> the<00:10:46.480> output<00:10:46.920> or<00:10:47.040> the 00:10:47.190 --> 00:10:47.200 align:start position:0% difference in you know the output or the 00:10:47.200 --> 00:10:49.670 align:start position:0% difference in you know the output or the behavior<00:10:48.040> then<00:10:48.399> that's<00:10:48.600> a<00:10:48.760> bug<00:10:49.120> somewhere<00:10:49.519> in 00:10:49.670 --> 00:10:49.680 align:start position:0% behavior then that's a bug somewhere in 00:10:49.680 --> 00:10:51.190 align:start position:0% behavior then that's a bug somewhere in this<00:10:50.040> processing 00:10:51.190 --> 00:10:51.200 align:start position:0% this processing 00:10:51.200 --> 00:10:54.910 align:start position:0% this processing pipeline<00:10:52.200> so<00:10:52.399> for<00:10:52.560> instance<00:10:53.240> um<00:10:54.040> the<00:10:54.560> for<00:10:54.760> one 00:10:54.910 --> 00:10:54.920 align:start position:0% pipeline so for instance um the for one 00:10:54.920 --> 00:10:56.670 align:start position:0% pipeline so for instance um the for one circuit<00:10:55.320> we<00:10:55.440> might<00:10:55.839> not<00:10:56.040> be<00:10:56.120> able<00:10:56.279> to<00:10:56.399> generate 00:10:56.670 --> 00:10:56.680 align:start position:0% circuit we might not be able to generate 00:10:56.680 --> 00:10:58.829 align:start position:0% circuit we might not be able to generate a<00:10:56.839> witness<00:10:57.320> but<00:10:57.440> for<00:10:57.600> the<00:10:57.720> other<00:10:57.880> one<00:10:58.160> we<00:10:58.279> would 00:10:58.829 --> 00:10:58.839 align:start position:0% a witness but for the other one we would 00:10:58.839 --> 00:11:00.310 align:start position:0% a witness but for the other one we would then<00:10:59.320> there's<00:10:59.440> probably<00:10:59.680> a<00:10:59.760> bar<00:11:00.000> somewhere<00:11:00.240> in 00:11:00.310 --> 00:11:00.320 align:start position:0% then there's probably a bar somewhere in 00:11:00.320 --> 00:11:03.829 align:start position:0% then there's probably a bar somewhere in the<00:11:00.440> compiler<00:11:01.000> or<00:11:01.120> in<00:11:01.200> the<00:11:01.320> witness 00:11:03.829 --> 00:11:03.839 align:start position:0% 00:11:03.839 --> 00:11:07.069 align:start position:0% generator<00:11:04.880> so<00:11:05.880> um<00:11:06.079> let's<00:11:06.240> look<00:11:06.399> at<00:11:06.560> a<00:11:06.680> few<00:11:06.880> of 00:11:07.069 --> 00:11:07.079 align:start position:0% generator so um let's look at a few of 00:11:07.079 --> 00:11:09.629 align:start position:0% generator so um let's look at a few of these<00:11:07.560> uh<00:11:07.880> Transformations<00:11:08.880> uh<00:11:09.000> to<00:11:09.160> kind<00:11:09.240> of 00:11:09.629 --> 00:11:09.639 align:start position:0% these uh Transformations uh to kind of 00:11:09.639 --> 00:11:12.230 align:start position:0% these uh Transformations uh to kind of understand<00:11:09.880> how<00:11:10.079> the<00:11:10.160> fuzzer<00:11:10.600> does<00:11:10.959> this<00:11:11.959> um 00:11:12.230 --> 00:11:12.240 align:start position:0% understand how the fuzzer does this um 00:11:12.240 --> 00:11:14.190 align:start position:0% understand how the fuzzer does this um so<00:11:12.440> here's<00:11:12.600> a<00:11:12.760> very<00:11:12.920> simple<00:11:13.200> transformation 00:11:14.190 --> 00:11:14.200 align:start position:0% so here's a very simple transformation 00:11:14.200 --> 00:11:16.230 align:start position:0% so here's a very simple transformation uh<00:11:14.320> if<00:11:14.399> you<00:11:14.600> have<00:11:15.279> somewhere<00:11:15.560> in<00:11:15.680> your<00:11:15.839> circuit 00:11:16.230 --> 00:11:16.240 align:start position:0% uh if you have somewhere in your circuit 00:11:16.240 --> 00:11:20.190 align:start position:0% uh if you have somewhere in your circuit an<00:11:16.440> expression<00:11:17.000> e<00:11:18.000> uh<00:11:18.200> you<00:11:18.279> can<00:11:18.480> always<00:11:19.200> apply 00:11:20.190 --> 00:11:20.200 align:start position:0% an expression e uh you can always apply 00:11:20.200 --> 00:11:21.509 align:start position:0% an expression e uh you can always apply um<00:11:20.440> you<00:11:20.560> can<00:11:20.680> always<00:11:20.880> multiply<00:11:21.399> the 00:11:21.509 --> 00:11:21.519 align:start position:0% um you can always multiply the 00:11:21.519 --> 00:11:23.750 align:start position:0% um you can always multiply the expression<00:11:22.120> by<00:11:22.560> one<00:11:23.000> right<00:11:23.320> that<00:11:23.440> should<00:11:23.600> not 00:11:23.750 --> 00:11:23.760 align:start position:0% expression by one right that should not 00:11:23.760 --> 00:11:26.750 align:start position:0% expression by one right that should not change<00:11:24.120> anything<00:11:25.079> um<00:11:25.920> or<00:11:26.160> you<00:11:26.240> can<00:11:26.440> also 00:11:26.750 --> 00:11:26.760 align:start position:0% change anything um or you can also 00:11:26.760 --> 00:11:28.949 align:start position:0% change anything um or you can also divide<00:11:27.120> by<00:11:27.320> one<00:11:28.000> again<00:11:28.279> shouldn't<00:11:28.600> have<00:11:28.760> any 00:11:28.949 --> 00:11:28.959 align:start position:0% divide by one again shouldn't have any 00:11:28.959 --> 00:11:31.269 align:start position:0% divide by one again shouldn't have any effect<00:11:29.480> on<00:11:30.120> the 00:11:31.269 --> 00:11:31.279 align:start position:0% effect on the 00:11:31.279 --> 00:11:34.629 align:start position:0% effect on the circuits<00:11:32.320> um<00:11:33.320> another<00:11:33.600> transformation<00:11:34.160> is<00:11:34.240> to 00:11:34.629 --> 00:11:34.639 align:start position:0% circuits um another transformation is to 00:11:34.639 --> 00:11:38.590 align:start position:0% circuits um another transformation is to basically<00:11:35.600> negate<00:11:36.320> the<00:11:36.560> expression<00:11:36.959> e 00:11:38.590 --> 00:11:38.600 align:start position:0% basically negate the expression e 00:11:38.600 --> 00:11:41.030 align:start position:0% basically negate the expression e twice<00:11:39.600> or<00:11:39.839> you<00:11:39.920> can<00:11:40.120> also<00:11:40.399> apply<00:11:40.720> other 00:11:41.030 --> 00:11:41.040 align:start position:0% twice or you can also apply other 00:11:41.040 --> 00:11:44.910 align:start position:0% twice or you can also apply other Transformations<00:11:42.040> like<00:11:42.720> um<00:11:43.519> swapping<00:11:44.519> um<00:11:44.760> the 00:11:44.910 --> 00:11:44.920 align:start position:0% Transformations like um swapping um the 00:11:44.920 --> 00:11:48.069 align:start position:0% Transformations like um swapping um the two<00:11:45.120> oper<00:11:45.639> of<00:11:45.760> a 00:11:48.069 --> 00:11:48.079 align:start position:0% 00:11:48.079 --> 00:11:51.710 align:start position:0% multiplication<00:11:49.079> and<00:11:49.160> then<00:11:49.320> we<00:11:49.440> also<00:11:49.720> have<00:11:50.720> um 00:11:51.710 --> 00:11:51.720 align:start position:0% multiplication and then we also have um 00:11:51.720 --> 00:11:53.949 align:start position:0% multiplication and then we also have um um<00:11:52.079> some<00:11:52.600> Transformations<00:11:53.399> that<00:11:53.600> use 00:11:53.949 --> 00:11:53.959 align:start position:0% um some Transformations that use 00:11:53.959 --> 00:11:55.710 align:start position:0% um some Transformations that use essentially<00:11:54.360> new<00:11:54.760> randomly<00:11:55.200> generated 00:11:55.710 --> 00:11:55.720 align:start position:0% essentially new randomly generated 00:11:55.720 --> 00:11:57.710 align:start position:0% essentially new randomly generated Expressions<00:11:56.720> so<00:11:56.959> here<00:11:57.120> for<00:11:57.240> instance<00:11:57.519> we 00:11:57.710 --> 00:11:57.720 align:start position:0% Expressions so here for instance we 00:11:57.720 --> 00:12:00.990 align:start position:0% Expressions so here for instance we replace<00:11:58.240> an<00:11:58.399> expression<00:11:58.760> e<00:11:59.720> with<00:12:00.120> e<00:12:00.639> minus 00:12:00.990 --> 00:12:01.000 align:start position:0% replace an expression e with e minus 00:12:01.000 --> 00:12:03.590 align:start position:0% replace an expression e with e minus some<00:12:01.320> random<00:12:01.639> expression<00:12:02.480> plus<00:12:03.000> some<00:12:03.279> random 00:12:03.590 --> 00:12:03.600 align:start position:0% some random expression plus some random 00:12:03.600 --> 00:12:05.750 align:start position:0% some random expression plus some random expression<00:12:04.360> right<00:12:04.680> that<00:12:04.800> should<00:12:05.079> again<00:12:05.519> not 00:12:05.750 --> 00:12:05.760 align:start position:0% expression right that should again not 00:12:05.760 --> 00:12:08.030 align:start position:0% expression right that should again not have<00:12:05.959> any<00:12:06.200> effect 00:12:08.030 --> 00:12:08.040 align:start position:0% have any effect 00:12:08.040 --> 00:12:12.150 align:start position:0% have any effect um<00:12:09.040> and<00:12:09.880> we<00:12:10.040> have<00:12:10.160> a<00:12:10.440> small<00:12:10.760> DSL<00:12:11.600> for 00:12:12.150 --> 00:12:12.160 align:start position:0% um and we have a small DSL for 00:12:12.160 --> 00:12:13.910 align:start position:0% um and we have a small DSL for describing<00:12:12.760> these<00:12:13.160> circuits<00:12:13.600> so<00:12:13.720> there's 00:12:13.910 --> 00:12:13.920 align:start position:0% describing these circuits so there's 00:12:13.920 --> 00:12:16.350 align:start position:0% describing these circuits so there's many<00:12:14.120> more<00:12:14.600> of<00:12:14.800> these<00:12:14.959> transform 00:12:16.350 --> 00:12:16.360 align:start position:0% many more of these transform 00:12:16.360 --> 00:12:19.230 align:start position:0% many more of these transform formations<00:12:17.360> um<00:12:17.839> So<00:12:18.199> currently<00:12:18.560> we<00:12:18.720> support 00:12:19.230 --> 00:12:19.240 align:start position:0% formations um So currently we support 00:12:19.240 --> 00:12:22.629 align:start position:0% formations um So currently we support roughly<00:12:19.720> 90<00:12:20.560> uh<00:12:20.680> such<00:12:21.079> rules<00:12:22.079> but<00:12:22.240> you<00:12:22.320> can 00:12:22.629 --> 00:12:22.639 align:start position:0% roughly 90 uh such rules but you can 00:12:22.639 --> 00:12:24.710 align:start position:0% roughly 90 uh such rules but you can easily<00:12:22.959> add<00:12:23.240> more<00:12:23.399> of<00:12:23.600> them<00:12:23.839> and<00:12:24.160> think<00:12:24.360> of<00:12:24.519> new 00:12:24.710 --> 00:12:24.720 align:start position:0% easily add more of them and think of new 00:12:24.720 --> 00:12:27.150 align:start position:0% easily add more of them and think of new ones<00:12:25.079> if<00:12:25.199> you<00:12:25.360> want<00:12:25.639> like 00:12:27.150 --> 00:12:27.160 align:start position:0% ones if you want like 00:12:27.160 --> 00:12:30.550 align:start position:0% ones if you want like to<00:12:28.160> so<00:12:28.720> uh<00:12:28.800> we<00:12:28.920> also<00:12:29.240> found<00:12:29.560> a<00:12:29.680> number<00:12:29.880> of<00:12:30.000> bugs 00:12:30.550 --> 00:12:30.560 align:start position:0% to so uh we also found a number of bugs 00:12:30.560 --> 00:12:35.030 align:start position:0% to so uh we also found a number of bugs in<00:12:31.279> um<00:12:31.920> the<00:12:32.920> different<00:12:33.600> uh<00:12:33.920> pipelines<00:12:34.920> and 00:12:35.030 --> 00:12:35.040 align:start position:0% in um the different uh pipelines and 00:12:35.040 --> 00:12:38.430 align:start position:0% in um the different uh pipelines and let's<00:12:35.240> look<00:12:35.360> at<00:12:35.519> a<00:12:36.000> few<00:12:36.240> of<00:12:36.399> them<00:12:37.040> um<00:12:38.040> just<00:12:38.199> to 00:12:38.430 --> 00:12:38.440 align:start position:0% let's look at a few of them um just to 00:12:38.440 --> 00:12:40.430 align:start position:0% let's look at a few of them um just to kind<00:12:38.560> of<00:12:38.720> give<00:12:38.839> you<00:12:39.079> the<00:12:39.440> the<00:12:39.600> idea<00:12:39.959> and<00:12:40.120> show 00:12:40.430 --> 00:12:40.440 align:start position:0% kind of give you the the idea and show 00:12:40.440 --> 00:12:42.750 align:start position:0% kind of give you the the idea and show give<00:12:40.560> you<00:12:40.639> a<00:12:40.760> concrete<00:12:41.120> example<00:12:42.000> um<00:12:42.519> that<00:12:42.639> you 00:12:42.750 --> 00:12:42.760 align:start position:0% give you a concrete example um that you 00:12:42.760 --> 00:12:47.150 align:start position:0% give you a concrete example um that you can<00:12:43.720> look<00:12:44.399> at<00:12:45.399> so<00:12:45.680> here<00:12:45.880> on<00:12:46.040> the<00:12:46.199> left<00:12:46.920> uh<00:12:47.040> we 00:12:47.150 --> 00:12:47.160 align:start position:0% can look at so here on the left uh we 00:12:47.160 --> 00:12:51.870 align:start position:0% can look at so here on the left uh we see<00:12:48.079> uh<00:12:48.199> a<00:12:48.360> small<00:12:49.320> uh<00:12:49.480> example<00:12:50.279> circuit<00:12:51.240> in<00:12:51.680> in 00:12:51.870 --> 00:12:51.880 align:start position:0% see uh a small uh example circuit in in 00:12:51.880 --> 00:12:55.629 align:start position:0% see uh a small uh example circuit in in the<00:12:52.199> circuit<00:12:52.720> circum<00:12:53.680> um<00:12:54.440> language<00:12:55.440> uh<00:12:55.560> you 00:12:55.629 --> 00:12:55.639 align:start position:0% the circuit circum um language uh you 00:12:55.639 --> 00:12:57.870 align:start position:0% the circuit circum um language uh you can<00:12:55.760> also<00:12:55.959> look<00:12:56.120> up<00:12:56.480> the<00:12:56.639> GitHub<00:12:57.000> issue<00:12:57.639> uh<00:12:57.760> if 00:12:57.870 --> 00:12:57.880 align:start position:0% can also look up the GitHub issue uh if 00:12:57.880 --> 00:12:59.790 align:start position:0% can also look up the GitHub issue uh if you<00:12:58.199> if<00:12:58.320> you'd<00:12:58.519> like<00:12:58.680> to 00:12:59.790 --> 00:12:59.800 align:start position:0% you if you'd like to 00:12:59.800 --> 00:13:02.110 align:start position:0% you if you'd like to um<00:13:00.399> but<00:13:00.519> this<00:13:00.720> essentially<00:13:01.040> a<00:13:01.120> minimized<00:13:01.959> uh 00:13:02.110 --> 00:13:02.120 align:start position:0% um but this essentially a minimized uh 00:13:02.120 --> 00:13:05.629 align:start position:0% um but this essentially a minimized uh cleaned<00:13:02.480> up<00:13:03.440> um<00:13:04.440> version<00:13:04.800> of<00:13:04.959> the 00:13:05.629 --> 00:13:05.639 align:start position:0% cleaned up um version of the 00:13:05.639 --> 00:13:09.110 align:start position:0% cleaned up um version of the circuit<00:13:06.639> um<00:13:06.920> and<00:13:07.800> as<00:13:07.880> you<00:13:08.000> can<00:13:08.120> see<00:13:08.279> there's<00:13:08.480> a 00:13:09.110 --> 00:13:09.120 align:start position:0% circuit um and as you can see there's a 00:13:09.120 --> 00:13:11.350 align:start position:0% circuit um and as you can see there's a variable<00:13:09.600> P<00:13:10.279> um<00:13:10.560> in<00:13:10.720> practice<00:13:11.040> this<00:13:11.199> is 00:13:11.350 --> 00:13:11.360 align:start position:0% variable P um in practice this is 00:13:11.360 --> 00:13:13.110 align:start position:0% variable P um in practice this is essentially<00:13:11.720> just<00:13:11.800> a<00:13:12.000> constant<00:13:12.760> uh<00:13:12.959> just 00:13:13.110 --> 00:13:13.120 align:start position:0% essentially just a constant uh just 00:13:13.120 --> 00:13:18.189 align:start position:0% essentially just a constant uh just didn't<00:13:13.399> fit<00:13:13.639> on<00:13:14.760> the<00:13:15.760> on<00:13:15.920> the<00:13:16.040> slide<00:13:16.639> so<00:13:16.959> I<00:13:17.480> um 00:13:18.189 --> 00:13:18.199 align:start position:0% didn't fit on the on the slide so I um 00:13:18.199 --> 00:13:22.069 align:start position:0% didn't fit on the on the slide so I um yeah<00:13:18.920> put<00:13:19.079> it<00:13:19.199> at<00:13:19.320> the<00:13:19.440> bottom<00:13:20.399> um<00:13:21.399> but<00:13:21.880> think 00:13:22.069 --> 00:13:22.079 align:start position:0% yeah put it at the bottom um but think 00:13:22.079 --> 00:13:24.670 align:start position:0% yeah put it at the bottom um but think of<00:13:22.320> P<00:13:22.600> just<00:13:22.760> as<00:13:22.920> a<00:13:23.199> normal<00:13:23.519> constant<00:13:23.880> in<00:13:24.040> your 00:13:24.670 --> 00:13:24.680 align:start position:0% of P just as a normal constant in your 00:13:24.680 --> 00:13:27.550 align:start position:0% of P just as a normal constant in your program<00:13:25.680> and<00:13:25.839> now<00:13:26.079> what<00:13:26.199> the<00:13:26.279> fuzzer<00:13:27.199> does<00:13:27.440> is 00:13:27.550 --> 00:13:27.560 align:start position:0% program and now what the fuzzer does is 00:13:27.560 --> 00:13:29.150 align:start position:0% program and now what the fuzzer does is it<00:13:27.720> generates<00:13:28.079> a<00:13:28.199> transformation<00:13:28.800> of<00:13:28.959> this 00:13:29.150 --> 00:13:29.160 align:start position:0% it generates a transformation of this 00:13:29.160 --> 00:13:31.590 align:start position:0% it generates a transformation of this this<00:13:29.360> circuit<00:13:30.360> which<00:13:30.480> is<00:13:30.680> the<00:13:30.800> one<00:13:31.320> uh<00:13:31.440> that's 00:13:31.590 --> 00:13:31.600 align:start position:0% this circuit which is the one uh that's 00:13:31.600 --> 00:13:35.230 align:start position:0% this circuit which is the one uh that's shown<00:13:31.800> on<00:13:31.920> the<00:13:32.320> right<00:13:33.320> and<00:13:33.560> here<00:13:34.560> it<00:13:34.720> applies<00:13:35.079> a 00:13:35.230 --> 00:13:35.240 align:start position:0% shown on the right and here it applies a 00:13:35.240 --> 00:13:38.590 align:start position:0% shown on the right and here it applies a number<00:13:35.519> of<00:13:36.120> um<00:13:37.000> metamorphic<00:13:37.600> Transformations 00:13:38.590 --> 00:13:38.600 align:start position:0% number of um metamorphic Transformations 00:13:38.600 --> 00:13:40.470 align:start position:0% number of um metamorphic Transformations so<00:13:38.760> for<00:13:38.920> instance<00:13:39.160> it<00:13:39.279> seems<00:13:39.519> like<00:13:39.639> the<00:13:39.760> fuzer 00:13:40.470 --> 00:13:40.480 align:start position:0% so for instance it seems like the fuzer 00:13:40.480 --> 00:13:41.790 align:start position:0% so for instance it seems like the fuzer first 00:13:41.790 --> 00:13:41.800 align:start position:0% first 00:13:41.800 --> 00:13:45.670 align:start position:0% first um<00:13:42.800> multiplied<00:13:43.639> the<00:13:43.800> expression<00:13:44.199> P<00:13:44.519> by<00:13:44.720> one 00:13:45.670 --> 00:13:45.680 align:start position:0% um multiplied the expression P by one 00:13:45.680 --> 00:13:48.509 align:start position:0% um multiplied the expression P by one then<00:13:45.959> subtracted<00:13:46.639> Zero<00:13:46.959> from<00:13:47.160> one<00:13:47.880> and<00:13:48.000> then 00:13:48.509 --> 00:13:48.519 align:start position:0% then subtracted Zero from one and then 00:13:48.519 --> 00:13:53.470 align:start position:0% then subtracted Zero from one and then divided<00:13:49.519> um<00:13:49.800> that<00:13:50.000> expression<00:13:51.000> uh<00:13:51.160> by<00:13:51.839> one<00:13:52.839> and 00:13:53.470 --> 00:13:53.480 align:start position:0% divided um that expression uh by one and 00:13:53.480 --> 00:13:58.310 align:start position:0% divided um that expression uh by one and when<00:13:54.040> we<00:13:54.639> execute<00:13:55.600> this<00:13:56.600> um<00:13:57.279> when<00:13:57.399> we<00:13:57.600> execute 00:13:58.310 --> 00:13:58.320 align:start position:0% when we execute this um when we execute 00:13:58.320 --> 00:13:59.910 align:start position:0% when we execute this um when we execute these<00:13:58.480> two<00:13:58.680> circuit 00:13:59.910 --> 00:13:59.920 align:start position:0% these two circuit 00:13:59.920 --> 00:14:02.590 align:start position:0% these two circuit we<00:14:00.240> can<00:14:00.440> see<00:14:00.720> that 00:14:02.590 --> 00:14:02.600 align:start position:0% we can see that 00:14:02.600 --> 00:14:06.389 align:start position:0% we can see that um<00:14:03.600> that<00:14:03.959> the<00:14:04.120> output<00:14:04.839> out<00:14:05.160> one<00:14:05.440> and<00:14:05.600> out<00:14:05.880> two 00:14:06.389 --> 00:14:06.399 align:start position:0% um that the output out one and out two 00:14:06.399 --> 00:14:08.829 align:start position:0% um that the output out one and out two actually<00:14:07.120> are<00:14:07.320> not<00:14:07.519> the 00:14:08.829 --> 00:14:08.839 align:start position:0% actually are not the 00:14:08.839 --> 00:14:11.790 align:start position:0% actually are not the same<00:14:09.839> so<00:14:10.000> this<00:14:10.120> is<00:14:10.279> bad<00:14:10.759> and<00:14:11.079> this<00:14:11.199> is<00:14:11.519> was<00:14:11.680> a 00:14:11.790 --> 00:14:11.800 align:start position:0% same so this is bad and this is was a 00:14:11.800 --> 00:14:14.310 align:start position:0% same so this is bad and this is was a bug<00:14:12.040> that<00:14:12.160> we<00:14:12.279> found<00:14:13.120> um<00:14:13.639> seemed<00:14:13.920> like<00:14:14.120> there 00:14:14.310 --> 00:14:14.320 align:start position:0% bug that we found um seemed like there 00:14:14.320 --> 00:14:17.910 align:start position:0% bug that we found um seemed like there was<00:14:14.440> a<00:14:14.519> bug<00:14:14.720> in<00:14:15.120> the<00:14:16.120> witness<00:14:16.519> generation 00:14:17.910 --> 00:14:17.920 align:start position:0% was a bug in the witness generation 00:14:17.920 --> 00:14:21.949 align:start position:0% was a bug in the witness generation part<00:14:18.920> um<00:14:19.880> and<00:14:20.440> here's<00:14:20.680> another<00:14:21.000> bug<00:14:21.720> um<00:14:21.839> that 00:14:21.949 --> 00:14:21.959 align:start position:0% part um and here's another bug um that 00:14:21.959 --> 00:14:25.310 align:start position:0% part um and here's another bug um that we<00:14:22.079> found<00:14:22.279> in<00:14:22.639> gnark<00:14:23.639> um<00:14:24.480> so<00:14:24.639> at<00:14:24.800> the<00:14:24.959> top<00:14:25.240> you 00:14:25.310 --> 00:14:25.320 align:start position:0% we found in gnark um so at the top you 00:14:25.320 --> 00:14:27.550 align:start position:0% we found in gnark um so at the top you can<00:14:25.600> again<00:14:25.839> see<00:14:26.199> the<00:14:26.519> the<00:14:26.639> original<00:14:27.040> circuit 00:14:27.550 --> 00:14:27.560 align:start position:0% can again see the the original circuit 00:14:27.560 --> 00:14:30.590 align:start position:0% can again see the the original circuit that<00:14:27.680> the<00:14:27.759> fuzer<00:14:28.120> generated<00:14:29.519> and<00:14:29.720> then<00:14:30.320> we<00:14:30.440> can 00:14:30.590 --> 00:14:30.600 align:start position:0% that the fuzer generated and then we can 00:14:30.600 --> 00:14:34.350 align:start position:0% that the fuzer generated and then we can also<00:14:30.839> see<00:14:31.519> the<00:14:32.079> transform<00:14:32.600> circuit<00:14:33.519> um<00:14:34.000> where 00:14:34.350 --> 00:14:34.360 align:start position:0% also see the transform circuit um where 00:14:34.360 --> 00:14:37.269 align:start position:0% also see the transform circuit um where the<00:14:34.480> fuzzer<00:14:35.160> essentially<00:14:35.680> changed<00:14:36.680> the 00:14:37.269 --> 00:14:37.279 align:start position:0% the fuzzer essentially changed the 00:14:37.279 --> 00:14:40.910 align:start position:0% the fuzzer essentially changed the expression<00:14:37.759> zero<00:14:38.320> to<00:14:38.720> just<00:14:39.480> zero<00:14:40.000> or<00:14:40.360> zero 00:14:40.910 --> 00:14:40.920 align:start position:0% expression zero to just zero or zero 00:14:40.920 --> 00:14:44.430 align:start position:0% expression zero to just zero or zero which<00:14:41.079> should<00:14:41.279> be<00:14:41.959> um<00:14:42.160> equivalent<00:14:43.199> right<00:14:44.199> and 00:14:44.430 --> 00:14:44.440 align:start position:0% which should be um equivalent right and 00:14:44.440 --> 00:14:48.030 align:start position:0% which should be um equivalent right and here<00:14:45.320> um<00:14:45.600> we<00:14:45.720> observed<00:14:46.199> that<00:14:46.560> for<00:14:46.880> C1<00:14:47.800> uh<00:14:47.920> there 00:14:48.030 --> 00:14:48.040 align:start position:0% here um we observed that for C1 uh there 00:14:48.040 --> 00:14:50.189 align:start position:0% here um we observed that for C1 uh there was<00:14:48.160> no<00:14:48.360> witness<00:14:48.920> that<00:14:49.040> was<00:14:49.199> generated<00:14:50.040> uh 00:14:50.189 --> 00:14:50.199 align:start position:0% was no witness that was generated uh 00:14:50.199 --> 00:14:53.430 align:start position:0% was no witness that was generated uh whereas<00:14:50.440> for<00:14:50.560> C2<00:14:51.040> there<00:14:51.199> was<00:14:51.920> so<00:14:52.240> this<00:14:52.639> again 00:14:53.430 --> 00:14:53.440 align:start position:0% whereas for C2 there was so this again 00:14:53.440 --> 00:14:56.550 align:start position:0% whereas for C2 there was so this again is<00:14:54.120> um<00:14:54.399> a<00:14:54.600> bar<00:14:55.199> somewhere<00:14:55.720> in<00:14:55.920> this<00:14:56.360> uh 00:14:56.550 --> 00:14:56.560 align:start position:0% is um a bar somewhere in this uh 00:14:56.560 --> 00:14:59.949 align:start position:0% is um a bar somewhere in this uh pipeline 00:14:59.949 --> 00:14:59.959 align:start position:0% 00:14:59.959 --> 00:15:03.069 align:start position:0% and<00:15:00.480> yeah<00:15:00.800> now<00:15:01.000> that<00:15:01.160> You'<00:15:01.639> kind<00:15:01.800> of<00:15:02.519> hopefully 00:15:03.069 --> 00:15:03.079 align:start position:0% and yeah now that You' kind of hopefully 00:15:03.079 --> 00:15:04.910 align:start position:0% and yeah now that You' kind of hopefully got<00:15:03.279> an<00:15:03.440> overview<00:15:03.839> of<00:15:04.000> the<00:15:04.320> of<00:15:04.399> the<00:15:04.519> tool<00:15:04.800> and 00:15:04.910 --> 00:15:04.920 align:start position:0% got an overview of the of the tool and 00:15:04.920 --> 00:15:07.310 align:start position:0% got an overview of the of the tool and saw<00:15:05.160> a<00:15:05.320> bit<00:15:05.959> how<00:15:06.120> these<00:15:06.279> bugs<00:15:06.560> look<00:15:06.759> like<00:15:06.920> in 00:15:07.310 --> 00:15:07.320 align:start position:0% saw a bit how these bugs look like in 00:15:07.320 --> 00:15:10.470 align:start position:0% saw a bit how these bugs look like in practice<00:15:08.320> um<00:15:08.480> I<00:15:08.600> hope<00:15:09.040> more<00:15:09.360> people<00:15:09.720> will<00:15:10.360> you 00:15:10.470 --> 00:15:10.480 align:start position:0% practice um I hope more people will you 00:15:10.480 --> 00:15:12.910 align:start position:0% practice um I hope more people will you know<00:15:11.240> uh<00:15:11.720> uh<00:15:11.800> start<00:15:12.079> looking<00:15:12.399> into<00:15:12.680> this 00:15:12.910 --> 00:15:12.920 align:start position:0% know uh uh start looking into this 00:15:12.920 --> 00:15:14.870 align:start position:0% know uh uh start looking into this problem<00:15:13.560> uh<00:15:13.680> because<00:15:13.880> I<00:15:14.000> think<00:15:14.160> it's<00:15:14.440> a<00:15:14.680> it's<00:15:14.759> a 00:15:14.870 --> 00:15:14.880 align:start position:0% problem uh because I think it's a it's a 00:15:14.880 --> 00:15:17.030 align:start position:0% problem uh because I think it's a it's a very<00:15:15.320> important<00:15:15.759> problem<00:15:16.600> uh<00:15:16.680> we<00:15:16.800> need<00:15:16.920> to 00:15:17.030 --> 00:15:17.040 align:start position:0% very important problem uh we need to 00:15:17.040 --> 00:15:18.509 align:start position:0% very important problem uh we need to really<00:15:17.199> make<00:15:17.360> sure<00:15:17.560> that<00:15:17.759> these<00:15:17.959> components 00:15:18.509 --> 00:15:18.519 align:start position:0% really make sure that these components 00:15:18.519 --> 00:15:21.150 align:start position:0% really make sure that these components are<00:15:19.120> uh<00:15:19.240> bulletproof<00:15:20.240> uh<00:15:20.360> because<00:15:20.600> otherwise 00:15:21.150 --> 00:15:21.160 align:start position:0% are uh bulletproof uh because otherwise 00:15:21.160 --> 00:15:23.310 align:start position:0% are uh bulletproof uh because otherwise you<00:15:21.279> know<00:15:21.880> pretty<00:15:22.120> bad<00:15:22.320> things<00:15:22.519> can<00:15:22.720> happen 00:15:23.310 --> 00:15:23.320 align:start position:0% you know pretty bad things can happen 00:15:23.320 --> 00:15:25.870 align:start position:0% you know pretty bad things can happen and<00:15:23.600> it's<00:15:23.720> better<00:15:23.959> to<00:15:24.120> do<00:15:24.680> this<00:15:25.120> before<00:15:25.560> the 00:15:25.870 --> 00:15:25.880 align:start position:0% and it's better to do this before the 00:15:25.880 --> 00:15:30.030 align:start position:0% and it's better to do this before the some<00:15:26.320> you<00:15:26.440> know<00:15:27.120> attacker<00:15:27.560> does<00:15:27.720> it<00:15:28.000> right<00:15:29.240> um 00:15:30.030 --> 00:15:30.040 align:start position:0% some you know attacker does it right um 00:15:30.040 --> 00:15:32.269 align:start position:0% some you know attacker does it right um and<00:15:30.440> you<00:15:30.560> don't<00:15:30.720> need<00:15:30.839> to<00:15:30.959> be<00:15:31.120> a<00:15:31.319> cryptographer 00:15:32.269 --> 00:15:32.279 align:start position:0% and you don't need to be a cryptographer 00:15:32.279 --> 00:15:34.990 align:start position:0% and you don't need to be a cryptographer to<00:15:32.560> actually<00:15:32.920> find<00:15:33.240> these<00:15:33.440> bugs<00:15:33.959> so<00:15:34.639> you<00:15:34.759> know 00:15:34.990 --> 00:15:35.000 align:start position:0% to actually find these bugs so you know 00:15:35.000 --> 00:15:39.189 align:start position:0% to actually find these bugs so you know that<00:15:35.560> makes<00:15:36.480> um<00:15:36.839> gives<00:15:37.120> us<00:15:37.399> a<00:15:37.560> lot<00:15:37.959> more<00:15:38.959> um 00:15:39.189 --> 00:15:39.199 align:start position:0% that makes um gives us a lot more um 00:15:39.199 --> 00:15:41.790 align:start position:0% that makes um gives us a lot more um people<00:15:39.519> that<00:15:39.680> can<00:15:40.000> actually<00:15:41.000> uh<00:15:41.120> look<00:15:41.319> into 00:15:41.790 --> 00:15:41.800 align:start position:0% people that can actually uh look into 00:15:41.800 --> 00:15:44.670 align:start position:0% people that can actually uh look into this<00:15:42.800> um<00:15:43.240> because<00:15:43.440> I<00:15:43.560> think<00:15:43.839> so<00:15:44.040> far<00:15:44.240> we<00:15:44.440> only 00:15:44.670 --> 00:15:44.680 align:start position:0% this um because I think so far we only 00:15:44.680 --> 00:15:46.389 align:start position:0% this um because I think so far we only really<00:15:45.000> scratch<00:15:45.360> the<00:15:45.480> surface<00:15:45.920> so<00:15:46.120> there's 00:15:46.389 --> 00:15:46.399 align:start position:0% really scratch the surface so there's 00:15:46.399 --> 00:15:48.509 align:start position:0% really scratch the surface so there's more<00:15:46.639> more<00:15:46.880> things<00:15:47.279> that<00:15:47.399> need<00:15:47.519> to<00:15:47.639> be<00:15:47.800> done<00:15:48.279> to 00:15:48.509 --> 00:15:48.519 align:start position:0% more more things that need to be done to 00:15:48.519 --> 00:15:50.590 align:start position:0% more more things that need to be done to to<00:15:48.680> test<00:15:48.920> these<00:15:49.120> components<00:15:49.759> also<00:15:50.000> there's 00:15:50.590 --> 00:15:50.600 align:start position:0% to test these components also there's 00:15:50.600 --> 00:15:54.189 align:start position:0% to test these components also there's components<00:15:51.600> like<00:15:51.839> this<00:15:52.040> popping<00:15:52.360> up<00:15:52.959> um<00:15:53.959> uh 00:15:54.189 --> 00:15:54.199 align:start position:0% components like this popping up um uh 00:15:54.199 --> 00:15:57.189 align:start position:0% components like this popping up um uh every<00:15:54.399> now<00:15:54.560> and<00:15:54.720> then<00:15:55.199> so<00:15:55.600> we<00:15:55.839> really<00:15:56.079> need<00:15:56.279> to 00:15:57.189 --> 00:15:57.199 align:start position:0% every now and then so we really need to 00:15:57.199 --> 00:15:59.710 align:start position:0% every now and then so we really need to uh<00:15:57.319> make<00:15:57.480> sure<00:15:57.800> they're<00:15:58.360> safe<00:15:59.279> and<00:15:59.399> we<00:15:59.519> also 00:15:59.710 --> 00:15:59.720 align:start position:0% uh make sure they're safe and we also 00:15:59.720 --> 00:16:01.710 align:start position:0% uh make sure they're safe and we also should<00:15:59.959> do<00:16:00.480> um<00:16:00.680> continuous<00:16:01.079> fuzzing<00:16:01.440> of<00:16:01.560> all 00:16:01.710 --> 00:16:01.720 align:start position:0% should do um continuous fuzzing of all 00:16:01.720 --> 00:16:04.030 align:start position:0% should do um continuous fuzzing of all these<00:16:01.920> components<00:16:02.639> so<00:16:03.000> for<00:16:03.240> the<00:16:03.480> gnark<00:16:03.839> team 00:16:04.030 --> 00:16:04.040 align:start position:0% these components so for the gnark team 00:16:04.040 --> 00:16:05.910 align:start position:0% these components so for the gnark team we<00:16:04.199> actually<00:16:04.440> implemented<00:16:05.319> a<00:16:05.480> continuous 00:16:05.910 --> 00:16:05.920 align:start position:0% we actually implemented a continuous 00:16:05.920 --> 00:16:08.509 align:start position:0% we actually implemented a continuous fuzzing<00:16:06.560> setup<00:16:07.199> where<00:16:07.680> you<00:16:07.759> know<00:16:08.120> they<00:16:08.319> when 00:16:08.509 --> 00:16:08.519 align:start position:0% fuzzing setup where you know they when 00:16:08.519 --> 00:16:10.550 align:start position:0% fuzzing setup where you know they when they<00:16:08.680> whenever<00:16:09.040> they<00:16:09.240> commit<00:16:10.079> the<00:16:10.240> latest 00:16:10.550 --> 00:16:10.560 align:start position:0% they whenever they commit the latest 00:16:10.560 --> 00:16:13.509 align:start position:0% they whenever they commit the latest version<00:16:10.920> to<00:16:11.319> master<00:16:12.319> uh<00:16:12.519> we<00:16:12.959> we<00:16:13.079> start<00:16:13.319> a<00:16:13.399> new 00:16:13.509 --> 00:16:13.519 align:start position:0% version to master uh we we start a new 00:16:13.519 --> 00:16:15.990 align:start position:0% version to master uh we we start a new fuzzing<00:16:13.920> campaign<00:16:14.639> uh<00:16:14.759> we<00:16:14.880> run<00:16:15.079> for<00:16:15.199> 24<00:16:15.560> hours 00:16:15.990 --> 00:16:16.000 align:start position:0% fuzzing campaign uh we run for 24 hours 00:16:16.000 --> 00:16:18.350 align:start position:0% fuzzing campaign uh we run for 24 hours we<00:16:16.199> tell<00:16:16.480> them<00:16:16.839> if<00:16:17.079> something<00:16:17.360> is<00:16:17.519> wrong<00:16:18.240> and 00:16:18.350 --> 00:16:18.360 align:start position:0% we tell them if something is wrong and 00:16:18.360 --> 00:16:21.470 align:start position:0% we tell them if something is wrong and then<00:16:18.560> the<00:16:18.720> next<00:16:18.959> day<00:16:19.360> same<00:16:19.600> thing<00:16:20.199> happens<00:16:21.199> um 00:16:21.470 --> 00:16:21.480 align:start position:0% then the next day same thing happens um 00:16:21.480 --> 00:16:23.350 align:start position:0% then the next day same thing happens um we're<00:16:21.680> also<00:16:22.160> planning<00:16:22.480> to<00:16:22.600> do<00:16:22.800> the<00:16:22.959> same<00:16:23.120> for 00:16:23.350 --> 00:16:23.360 align:start position:0% we're also planning to do the same for 00:16:23.360 --> 00:16:26.350 align:start position:0% we're also planning to do the same for cors<00:16:24.079> and<00:16:24.319> if<00:16:24.399> you're<00:16:24.680> interested<00:16:25.079> in<00:16:25.720> um<00:16:26.120> you 00:16:26.350 --> 00:16:26.360 align:start position:0% cors and if you're interested in um you 00:16:26.360 --> 00:16:29.710 align:start position:0% cors and if you're interested in um you know<00:16:27.360> us<00:16:27.880> uh<00:16:28.040> taking<00:16:28.279> a<00:16:28.360> look<00:16:28.519> at<00:16:28.639> your<00:16:29.199> uh<00:16:29.319> ZK 00:16:29.710 --> 00:16:29.720 align:start position:0% know us uh taking a look at your uh ZK 00:16:29.720 --> 00:16:31.710 align:start position:0% know us uh taking a look at your uh ZK infrastructure<00:16:30.600> uh<00:16:30.720> please<00:16:30.920> reach 00:16:31.710 --> 00:16:31.720 align:start position:0% infrastructure uh please reach 00:16:31.720 --> 00:16:35.230 align:start position:0% infrastructure uh please reach out<00:16:32.720> and<00:16:33.000> if<00:16:33.120> you<00:16:33.440> want<00:16:33.560> to<00:16:33.800> know<00:16:34.040> more<00:16:34.319> about 00:16:35.230 --> 00:16:35.240 align:start position:0% out and if you want to know more about 00:16:35.240 --> 00:16:37.309 align:start position:0% out and if you want to know more about uh<00:16:35.600> what's<00:16:35.839> going<00:16:36.000> on<00:16:36.199> in<00:16:36.319> the<00:16:36.440> fuzzer<00:16:37.079> then 00:16:37.309 --> 00:16:37.319 align:start position:0% uh what's going on in the fuzzer then 00:16:37.319 --> 00:16:40.069 align:start position:0% uh what's going on in the fuzzer then please<00:16:37.560> just<00:16:37.880> check<00:16:38.079> out<00:16:38.440> our<00:16:38.920> paper<00:16:39.920> uh<00:16:40.000> you 00:16:40.069 --> 00:16:40.079 align:start position:0% please just check out our paper uh you 00:16:40.079 --> 00:16:43.990 align:start position:0% please just check out our paper uh you can<00:16:40.199> scan<00:16:40.480> the<00:16:40.639> QR<00:16:41.000> code<00:16:41.399> there<00:16:42.160> um<00:16:42.920> and<00:16:43.399> if<00:16:43.560> you 00:16:43.990 --> 00:16:44.000 align:start position:0% can scan the QR code there um and if you 00:16:44.000 --> 00:16:45.990 align:start position:0% can scan the QR code there um and if you you<00:16:44.120> know<00:16:44.360> want<00:16:44.519> to<00:16:44.720> let<00:16:44.920> take<00:16:45.040> a 00:16:45.990 --> 00:16:46.000 align:start position:0% you know want to let take a 00:16:46.000 --> 00:16:51.189 align:start position:0% you know want to let take a look<00:16:47.000> um 00:16:51.189 --> 00:16:51.199 align:start position:0% 00:16:51.199 --> 00:16:55.230 align:start position:0% yeah<00:16:52.680> fantastic<00:16:53.680> thank<00:16:53.839> you<00:16:54.040> Val<00:16:54.519> Valentine 00:16:55.230 --> 00:16:55.240 align:start position:0% yeah fantastic thank you Val Valentine 00:16:55.240 --> 00:16:58.550 align:start position:0% yeah fantastic thank you Val Valentine for<00:16:55.759> this<00:16:56.560> presentation<00:16:57.560> um<00:16:58.079> let's<00:16:58.319> get<00:16:58.440> to 00:16:58.550 --> 00:16:58.560 align:start position:0% for this presentation um let's get to 00:16:58.560 --> 00:17:01.269 align:start position:0% for this presentation um let's get to the<00:16:58.639> question<00:16:59.199> shall<00:16:59.440> we<00:16:59.800> yeah<00:17:00.040> all<00:17:00.199> right<00:17:00.680> so 00:17:01.269 --> 00:17:01.279 align:start position:0% the question shall we yeah all right so 00:17:01.279 --> 00:17:02.990 align:start position:0% the question shall we yeah all right so I've<00:17:01.440> sorted<00:17:01.839> the<00:17:02.000> questions<00:17:02.519> again<00:17:02.759> you<00:17:02.880> have 00:17:02.990 --> 00:17:03.000 align:start position:0% I've sorted the questions again you have 00:17:03.000 --> 00:17:04.710 align:start position:0% I've sorted the questions again you have a<00:17:03.160> QR<00:17:03.480> code<00:17:03.800> here<00:17:04.000> you<00:17:04.120> can<00:17:04.319> ask<00:17:04.480> your 00:17:04.710 --> 00:17:04.720 align:start position:0% a QR code here you can ask your 00:17:04.720 --> 00:17:06.309 align:start position:0% a QR code here you can ask your questions<00:17:05.160> and<00:17:05.280> I'll<00:17:05.480> ask<00:17:05.720> the<00:17:05.799> ones<00:17:06.039> that<00:17:06.120> are 00:17:06.309 --> 00:17:06.319 align:start position:0% questions and I'll ask the ones that are 00:17:06.319 --> 00:17:09.429 align:start position:0% questions and I'll ask the ones that are the<00:17:06.439> most<00:17:07.280> voted<00:17:08.280> so<00:17:08.559> let's<00:17:08.760> get<00:17:08.880> to<00:17:09.039> the<00:17:09.199> first 00:17:09.429 --> 00:17:09.439 align:start position:0% the most voted so let's get to the first 00:17:09.439 --> 00:17:12.590 align:start position:0% the most voted so let's get to the first one<00:17:10.360> when<00:17:10.480> you<00:17:10.679> identify<00:17:11.480> a<00:17:11.679> bug<00:17:12.240> can<00:17:12.360> you<00:17:12.439> just 00:17:12.590 --> 00:17:12.600 align:start position:0% one when you identify a bug can you just 00:17:12.600 --> 00:17:14.710 align:start position:0% one when you identify a bug can you just say<00:17:12.880> hey<00:17:13.039> there's<00:17:13.240> a<00:17:13.360> bug<00:17:13.640> or<00:17:13.760> do<00:17:13.880> you<00:17:14.079> provide 00:17:14.710 --> 00:17:14.720 align:start position:0% say hey there's a bug or do you provide 00:17:14.720 --> 00:17:16.669 align:start position:0% say hey there's a bug or do you provide a<00:17:14.919> path<00:17:15.160> to<00:17:15.319> fix<00:17:15.520> it<00:17:15.679> like<00:17:15.799> do<00:17:15.919> you<00:17:16.079> identify 00:17:16.669 --> 00:17:16.679 align:start position:0% a path to fix it like do you identify 00:17:16.679 --> 00:17:19.590 align:start position:0% a path to fix it like do you identify where<00:17:17.199> the<00:17:17.360> bug<00:17:17.679> exist<00:17:18.039> within<00:17:18.280> the<00:17:18.600> circuit 00:17:19.590 --> 00:17:19.600 align:start position:0% where the bug exist within the circuit 00:17:19.600 --> 00:17:22.350 align:start position:0% where the bug exist within the circuit uh<00:17:19.760> we<00:17:19.880> don't<00:17:20.880> directly<00:17:21.360> identify<00:17:21.880> where<00:17:22.240> the 00:17:22.350 --> 00:17:22.360 align:start position:0% uh we don't directly identify where the 00:17:22.360 --> 00:17:27.110 align:start position:0% uh we don't directly identify where the bug<00:17:22.640> is<00:17:23.240> but<00:17:23.679> when<00:17:23.919> we<00:17:24.400> generate<00:17:25.679> the<00:17:26.679> the<00:17:26.839> test 00:17:27.110 --> 00:17:27.120 align:start position:0% bug is but when we generate the the test 00:17:27.120 --> 00:17:29.510 align:start position:0% bug is but when we generate the the test inputs<00:17:27.640> like<00:17:27.839> the<00:17:27.919> circuits<00:17:29.000> uh<00:17:29.120> we<00:17:29.240> try<00:17:29.440> to 00:17:29.510 --> 00:17:29.520 align:start position:0% inputs like the circuits uh we try to 00:17:29.520 --> 00:17:31.270 align:start position:0% inputs like the circuits uh we try to minimize<00:17:30.000> them<00:17:30.280> so<00:17:30.440> we<00:17:30.559> try<00:17:30.760> to<00:17:30.840> keep<00:17:31.000> them<00:17:31.160> as 00:17:31.270 --> 00:17:31.280 align:start position:0% minimize them so we try to keep them as 00:17:31.280 --> 00:17:34.110 align:start position:0% minimize them so we try to keep them as small<00:17:31.600> as<00:17:31.799> possible<00:17:32.679> so<00:17:33.000> the<00:17:33.200> developers<00:17:33.679> can 00:17:34.110 --> 00:17:34.120 align:start position:0% small as possible so the developers can 00:17:34.120 --> 00:17:36.590 align:start position:0% small as possible so the developers can really<00:17:35.039> hopefully<00:17:35.440> quite<00:17:35.640> easily<00:17:35.960> identify 00:17:36.590 --> 00:17:36.600 align:start position:0% really hopefully quite easily identify 00:17:36.600 --> 00:17:41.310 align:start position:0% really hopefully quite easily identify where<00:17:36.919> things<00:17:37.120> go<00:17:37.520> wrong<00:17:38.520> um<00:17:39.400> and<00:17:40.240> yeah<00:17:40.480> so<00:17:40.679> far 00:17:41.310 --> 00:17:41.320 align:start position:0% where things go wrong um and yeah so far 00:17:41.320 --> 00:17:44.470 align:start position:0% where things go wrong um and yeah so far I<00:17:41.440> think<00:17:41.760> the<00:17:41.880> complaint<00:17:42.679> the<00:17:43.400> the<00:17:44.360> the 00:17:44.470 --> 00:17:44.480 align:start position:0% I think the complaint the the the 00:17:44.480 --> 00:17:46.669 align:start position:0% I think the complaint the the the developers<00:17:45.039> very<00:17:45.400> very<00:17:45.600> happy<00:17:45.840> with<00:17:45.960> the<00:17:46.080> bugs 00:17:46.669 --> 00:17:46.679 align:start position:0% developers very very happy with the bugs 00:17:46.679 --> 00:17:50.150 align:start position:0% developers very very happy with the bugs reported<00:17:47.679> um<00:17:48.440> and<00:17:48.880> I<00:17:49.000> think<00:17:49.720> there<00:17:49.840> was<00:17:50.000> no 00:17:50.150 --> 00:17:50.160 align:start position:0% reported um and I think there was no 00:17:50.160 --> 00:17:53.029 align:start position:0% reported um and I think there was no issues<00:17:50.760> finding<00:17:51.240> the<00:17:51.480> the<00:17:51.600> bug<00:17:52.039> once<00:17:52.520> they<00:17:52.679> had 00:17:53.029 --> 00:17:53.039 align:start position:0% issues finding the the bug once they had 00:17:53.039 --> 00:17:56.350 align:start position:0% issues finding the the bug once they had the<00:17:53.720> the<00:17:53.880> input<00:17:54.640> makes<00:17:54.880> sense<00:17:55.240> thank<00:17:55.400> you 00:17:56.350 --> 00:17:56.360 align:start position:0% the the input makes sense thank you 00:17:56.360 --> 00:17:58.870 align:start position:0% the the input makes sense thank you second<00:17:56.799> question<00:17:57.440> do<00:17:57.600> you<00:17:57.799> fuzz<00:17:58.240> logical 00:17:58.870 --> 00:17:58.880 align:start position:0% second question do you fuzz logical 00:17:58.880 --> 00:18:01.190 align:start position:0% second question do you fuzz logical Expressions<00:17:59.760> they're<00:18:00.000> encoding<00:18:00.440> in 00:18:01.190 --> 00:18:01.200 align:start position:0% Expressions they're encoding in 00:18:01.200 --> 00:18:04.070 align:start position:0% Expressions they're encoding in circuits<00:18:02.200> uh<00:18:02.400> yeah<00:18:02.559> we<00:18:02.679> do<00:18:03.200> I<00:18:03.320> think<00:18:03.799> yeah<00:18:03.919> so 00:18:04.070 --> 00:18:04.080 align:start position:0% circuits uh yeah we do I think yeah so 00:18:04.080 --> 00:18:06.149 align:start position:0% circuits uh yeah we do I think yeah so for<00:18:04.159> instance<00:18:04.400> we<00:18:04.559> apply<00:18:04.960> some<00:18:05.360> you<00:18:05.480> know<00:18:05.679> some 00:18:06.149 --> 00:18:06.159 align:start position:0% for instance we apply some you know some 00:18:06.159 --> 00:18:08.549 align:start position:0% for instance we apply some you know some common<00:18:07.120> uh<00:18:07.240> Transformations<00:18:08.000> like<00:18:08.159> applying 00:18:08.549 --> 00:18:08.559 align:start position:0% common uh Transformations like applying 00:18:08.559 --> 00:18:10.870 align:start position:0% common uh Transformations like applying the<00:18:08.679> Morgan's<00:18:09.120> Rule<00:18:09.480> and<00:18:09.600> so<00:18:09.760> on<00:18:10.440> um<00:18:10.720> so 00:18:10.870 --> 00:18:10.880 align:start position:0% the Morgan's Rule and so on um so 00:18:10.880 --> 00:18:13.029 align:start position:0% the Morgan's Rule and so on um so there's<00:18:11.039> a<00:18:11.159> bunch<00:18:11.360> of<00:18:12.280> um<00:18:12.840> these 00:18:13.029 --> 00:18:13.039 align:start position:0% there's a bunch of um these 00:18:13.039 --> 00:18:14.909 align:start position:0% there's a bunch of um these Transformations<00:18:13.720> that<00:18:13.919> we<00:18:14.280> that<00:18:14.400> we<00:18:14.520> use<00:18:14.799> in 00:18:14.909 --> 00:18:14.919 align:start position:0% Transformations that we that we use in 00:18:14.919 --> 00:18:16.909 align:start position:0% Transformations that we that we use in the<00:18:15.400> fuzer 00:18:16.909 --> 00:18:16.919 align:start position:0% the fuzer 00:18:16.919 --> 00:18:18.430 align:start position:0% the fuzer wonderful 00:18:18.430 --> 00:18:18.440 align:start position:0% wonderful 00:18:18.440 --> 00:18:20.990 align:start position:0% wonderful third<00:18:19.440> where<00:18:19.600> is<00:18:19.760> the<00:18:19.880> bug<00:18:20.159> Nest<00:18:20.600> where<00:18:20.720> do 00:18:20.990 --> 00:18:21.000 align:start position:0% third where is the bug Nest where do 00:18:21.000 --> 00:18:23.350 align:start position:0% third where is the bug Nest where do bugs<00:18:21.360> usually<00:18:21.799> reside<00:18:22.200> in<00:18:22.320> your<00:18:22.840> historical 00:18:23.350 --> 00:18:23.360 align:start position:0% bugs usually reside in your historical 00:18:23.360 --> 00:18:26.830 align:start position:0% bugs usually reside in your historical fuzing<00:18:23.799> like<00:18:23.960> from<00:18:24.120> what<00:18:24.240> you've<00:18:24.480> seen<00:18:25.760> um<00:18:26.760> I 00:18:26.830 --> 00:18:26.840 align:start position:0% fuzing like from what you've seen um I 00:18:26.840 --> 00:18:28.590 align:start position:0% fuzing like from what you've seen um I think<00:18:27.000> it's<00:18:27.200> it's<00:18:27.360> hard<00:18:27.559> to<00:18:28.000> like<00:18:28.400> can<00:18:28.480> you 00:18:28.590 --> 00:18:28.600 align:start position:0% think it's it's hard to like can you 00:18:28.600 --> 00:18:31.350 align:start position:0% think it's it's hard to like can you read<00:18:28.919> derive<00:18:29.600> U<00:18:30.000> enough<00:18:30.400> data<00:18:30.679> from<00:18:30.919> you<00:18:31.080> found 00:18:31.350 --> 00:18:31.360 align:start position:0% read derive U enough data from you found 00:18:31.360 --> 00:18:33.710 align:start position:0% read derive U enough data from you found 17<00:18:32.159> yeah<00:18:32.440> yeah<00:18:32.679> I<00:18:32.760> think<00:18:32.960> it's<00:18:33.240> yeah<00:18:33.480> it's 00:18:33.710 --> 00:18:33.720 align:start position:0% 17 yeah yeah I think it's yeah it's 00:18:33.720 --> 00:18:35.830 align:start position:0% 17 yeah yeah I think it's yeah it's probably<00:18:34.039> too<00:18:34.240> early<00:18:34.520> to<00:18:34.640> say<00:18:34.919> but<00:18:35.120> we<00:18:35.360> did 00:18:35.830 --> 00:18:35.840 align:start position:0% probably too early to say but we did 00:18:35.840 --> 00:18:39.390 align:start position:0% probably too early to say but we did observe<00:18:36.360> that<00:18:37.360> um<00:18:37.520> the<00:18:37.600> fer<00:18:38.480> found<00:18:38.840> bugs 00:18:39.390 --> 00:18:39.400 align:start position:0% observe that um the fer found bugs 00:18:39.400 --> 00:18:43.310 align:start position:0% observe that um the fer found bugs basically<00:18:40.120> in<00:18:41.120> um<00:18:41.559> different<00:18:42.039> components<00:18:42.880> so 00:18:43.310 --> 00:18:43.320 align:start position:0% basically in um different components so 00:18:43.320 --> 00:18:45.430 align:start position:0% basically in um different components so we<00:18:43.440> found<00:18:43.679> bugs<00:18:43.960> in<00:18:44.200> the<00:18:44.360> compilers<00:18:45.080> we<00:18:45.200> found 00:18:45.430 --> 00:18:45.440 align:start position:0% we found bugs in the compilers we found 00:18:45.440 --> 00:18:48.830 align:start position:0% we found bugs in the compilers we found bugs<00:18:46.320> in<00:18:46.559> the<00:18:47.000> witness<00:18:47.440> generator<00:18:48.360> we<00:18:48.520> found 00:18:48.830 --> 00:18:48.840 align:start position:0% bugs in the witness generator we found 00:18:48.840 --> 00:18:51.149 align:start position:0% bugs in the witness generator we found bugs<00:18:49.200> in<00:18:49.400> the<00:18:49.760> approver<00:18:50.200> as<00:18:50.360> well<00:18:50.919> I<00:18:51.000> don't 00:18:51.149 --> 00:18:51.159 align:start position:0% bugs in the approver as well I don't 00:18:51.159 --> 00:18:52.909 align:start position:0% bugs in the approver as well I don't think<00:18:51.320> we<00:18:51.440> found<00:18:51.679> bugs<00:18:51.919> in<00:18:52.039> the<00:18:52.159> verifier 00:18:52.909 --> 00:18:52.919 align:start position:0% think we found bugs in the verifier 00:18:52.919 --> 00:18:55.669 align:start position:0% think we found bugs in the verifier seems<00:18:53.240> like<00:18:53.679> yeah<00:18:54.360> that's<00:18:54.640> kind<00:18:54.760> of<00:18:55.360> towards 00:18:55.669 --> 00:18:55.679 align:start position:0% seems like yeah that's kind of towards 00:18:55.679 --> 00:18:57.990 align:start position:0% seems like yeah that's kind of towards the<00:18:55.799> end<00:18:55.960> of<00:18:56.080> the<00:18:56.280> pipeline<00:18:57.280> uh<00:18:57.400> and<00:18:57.559> I<00:18:57.679> think 00:18:57.990 --> 00:18:58.000 align:start position:0% the end of the pipeline uh and I think 00:18:58.000 --> 00:18:59.950 align:start position:0% the end of the pipeline uh and I think many<00:18:58.240> people<00:18:58.480> are<00:18:58.799> are<00:18:59.120> you<00:18:59.240> know<00:18:59.720> very 00:18:59.950 --> 00:18:59.960 align:start position:0% many people are are you know very 00:18:59.960 --> 00:19:01.789 align:start position:0% many people are are you know very concerned<00:19:00.360> about<00:19:00.640> the<00:19:01.240> you<00:19:01.320> know<00:19:01.440> getting<00:19:01.679> the 00:19:01.789 --> 00:19:01.799 align:start position:0% concerned about the you know getting the 00:19:01.799 --> 00:19:04.149 align:start position:0% concerned about the you know getting the verifier<00:19:02.360> right<00:19:03.000> so<00:19:03.240> maybe<00:19:03.559> that's<00:19:03.919> also 00:19:04.149 --> 00:19:04.159 align:start position:0% verifier right so maybe that's also 00:19:04.159 --> 00:19:06.510 align:start position:0% verifier right so maybe that's also paying<00:19:04.480> off<00:19:04.919> uh<00:19:05.120> here<00:19:05.760> um<00:19:05.919> but<00:19:06.080> we'll<00:19:06.360> we'll 00:19:06.510 --> 00:19:06.520 align:start position:0% paying off uh here um but we'll we'll 00:19:06.520 --> 00:19:11.870 align:start position:0% paying off uh here um but we'll we'll keep<00:19:06.760> trying<00:19:07.600> um<00:19:08.200> we'll<00:19:09.200> yeah<00:19:09.480> we'll<00:19:09.720> see<00:19:10.880> nice 00:19:11.870 --> 00:19:11.880 align:start position:0% keep trying um we'll yeah we'll see nice 00:19:11.880 --> 00:19:14.270 align:start position:0% keep trying um we'll yeah we'll see nice um<00:19:12.320> okay<00:19:12.720> when<00:19:13.039> Kyo 00:19:14.270 --> 00:19:14.280 align:start position:0% um okay when Kyo 00:19:14.280 --> 00:19:18.110 align:start position:0% um okay when Kyo fuzzing<00:19:15.480> um<00:19:16.480> yeah<00:19:16.840> we're<00:19:17.440> I<00:19:17.559> guess<00:19:17.679> you<00:19:17.799> insert 00:19:18.110 --> 00:19:18.120 align:start position:0% fuzzing um yeah we're I guess you insert 00:19:18.120 --> 00:19:19.750 align:start position:0% fuzzing um yeah we're I guess you insert it<00:19:18.240> in<00:19:18.360> your<00:19:18.520> slide<00:19:18.799> if<00:19:18.919> we're<00:19:19.159> interested 00:19:19.750 --> 00:19:19.760 align:start position:0% it in your slide if we're interested 00:19:19.760 --> 00:19:21.270 align:start position:0% it in your slide if we're interested people<00:19:20.400> talk<00:19:20.559> to 00:19:21.270 --> 00:19:21.280 align:start position:0% people talk to 00:19:21.280 --> 00:19:24.549 align:start position:0% people talk to you<00:19:22.280> somebody<00:19:22.520> from<00:19:22.640> starware<00:19:23.320> wants<00:19:23.559> to<00:19:24.320> you 00:19:24.549 --> 00:19:24.559 align:start position:0% you somebody from starware wants to you 00:19:24.559 --> 00:19:28.390 align:start position:0% you somebody from starware wants to you know<00:19:25.559> uh<00:19:26.360> us<00:19:26.520> to<00:19:26.720> look<00:19:26.840> at<00:19:27.240> more<00:19:27.440> at<00:19:27.720> CYO<00:19:28.159> then 00:19:28.390 --> 00:19:28.400 align:start position:0% know uh us to look at more at CYO then 00:19:28.400 --> 00:19:30.310 align:start position:0% know uh us to look at more at CYO then yeah<00:19:28.520> please<00:19:28.720> please<00:19:28.880> reach<00:19:29.080> out<00:19:29.679> um<00:19:30.080> we're 00:19:30.310 --> 00:19:30.320 align:start position:0% yeah please please reach out um we're 00:19:30.320 --> 00:19:32.950 align:start position:0% yeah please please reach out um we're interested<00:19:31.080> um<00:19:31.240> it's<00:19:31.400> definitely<00:19:31.960> a<00:19:32.600> a<00:19:32.799> good 00:19:32.950 --> 00:19:32.960 align:start position:0% interested um it's definitely a a good 00:19:32.960 --> 00:19:35.750 align:start position:0% interested um it's definitely a a good idea<00:19:33.280> to<00:19:33.600> to<00:19:33.720> do<00:19:33.919> that<00:19:34.200> yeah<00:19:34.919> wonderful<00:19:35.559> well 00:19:35.750 --> 00:19:35.760 align:start position:0% idea to to do that yeah wonderful well 00:19:35.760 --> 00:19:38.510 align:start position:0% idea to to do that yeah wonderful well I'll<00:19:36.000> reach<00:19:36.440> out<00:19:37.440> um<00:19:37.720> what<00:19:37.840> do<00:19:37.960> you<00:19:38.080> think<00:19:38.280> of 00:19:38.510 --> 00:19:38.520 align:start position:0% I'll reach out um what do you think of 00:19:38.520 --> 00:19:41.070 align:start position:0% I'll reach out um what do you think of concolic<00:19:39.159> testing<00:19:39.600> of<00:19:39.799> Z 00:19:41.070 --> 00:19:41.080 align:start position:0% concolic testing of Z 00:19:41.080 --> 00:19:44.270 align:start position:0% concolic testing of Z circuits<00:19:42.080> um<00:19:42.960> I<00:19:43.039> had<00:19:43.200> to<00:19:43.320> ask<00:19:43.480> chat<00:19:43.760> GPT<00:19:44.120> what 00:19:44.270 --> 00:19:44.280 align:start position:0% circuits um I had to ask chat GPT what 00:19:44.280 --> 00:19:46.070 align:start position:0% circuits um I had to ask chat GPT what concolic<00:19:44.760> testing<00:19:45.120> is<00:19:45.520> okay<00:19:45.640> and<00:19:45.760> I<00:19:45.840> still 00:19:46.070 --> 00:19:46.080 align:start position:0% concolic testing is okay and I still 00:19:46.080 --> 00:19:49.070 align:start position:0% concolic testing is okay and I still don't<00:19:46.480> understand<00:19:46.600> it<00:19:47.280> okay<00:19:48.280> um<00:19:48.720> yeah<00:19:48.880> so 00:19:49.070 --> 00:19:49.080 align:start position:0% don't understand it okay um yeah so 00:19:49.080 --> 00:19:51.909 align:start position:0% don't understand it okay um yeah so concolic<00:19:49.559> testing<00:19:50.559> um<00:19:51.000> essentially<00:19:51.480> I<00:19:51.520> mean 00:19:51.909 --> 00:19:51.919 align:start position:0% concolic testing um essentially I mean 00:19:51.919 --> 00:19:53.830 align:start position:0% concolic testing um essentially I mean for<00:19:52.159> the<00:19:52.280> audience<00:19:52.760> maybe<00:19:53.280> it's<00:19:53.480> essentially 00:19:53.830 --> 00:19:53.840 align:start position:0% for the audience maybe it's essentially 00:19:53.840 --> 00:19:58.909 align:start position:0% for the audience maybe it's essentially a<00:19:53.960> way<00:19:54.440> to<00:19:55.280> you<00:19:55.400> know<00:19:55.600> generate<00:19:56.880> um<00:19:57.880> new<00:19:58.120> inputs 00:19:58.909 --> 00:19:58.919 align:start position:0% a way to you know generate um new inputs 00:19:58.919 --> 00:20:02.510 align:start position:0% a way to you know generate um new inputs by<00:19:59.159> doing<00:19:59.880> some<00:20:00.120> kind<00:20:00.240> of<00:20:00.400> symbolic<00:20:01.520> execution 00:20:02.510 --> 00:20:02.520 align:start position:0% by doing some kind of symbolic execution 00:20:02.520 --> 00:20:04.789 align:start position:0% by doing some kind of symbolic execution uh<00:20:02.720> but<00:20:03.280> basically<00:20:03.720> for<00:20:04.000> some<00:20:04.280> Expressions 00:20:04.789 --> 00:20:04.799 align:start position:0% uh but basically for some Expressions 00:20:04.799 --> 00:20:06.870 align:start position:0% uh but basically for some Expressions that<00:20:04.960> might<00:20:05.120> be<00:20:05.559> really<00:20:05.880> complex<00:20:06.480> like<00:20:06.720> you 00:20:06.870 --> 00:20:06.880 align:start position:0% that might be really complex like you 00:20:06.880 --> 00:20:09.630 align:start position:0% that might be really complex like you have<00:20:07.080> non<00:20:07.919> nonlinear<00:20:08.919> expressions<00:20:09.360> in<00:20:09.480> these 00:20:09.630 --> 00:20:09.640 align:start position:0% have non nonlinear expressions in these 00:20:09.640 --> 00:20:12.029 align:start position:0% have non nonlinear expressions in these circuits<00:20:10.400> so<00:20:10.640> there<00:20:10.799> you<00:20:10.919> might<00:20:11.080> want<00:20:11.200> to<00:20:11.880> uh 00:20:12.029 --> 00:20:12.039 align:start position:0% circuits so there you might want to uh 00:20:12.039 --> 00:20:14.909 align:start position:0% circuits so there you might want to uh concretize<00:20:12.600> some<00:20:13.000> inputs<00:20:13.919> um<00:20:14.400> and<00:20:14.559> that's<00:20:14.720> a 00:20:14.909 --> 00:20:14.919 align:start position:0% concretize some inputs um and that's a 00:20:14.919 --> 00:20:17.470 align:start position:0% concretize some inputs um and that's a con<00:20:15.679> concolic<00:20:16.240> part<00:20:16.440> so<00:20:16.600> it's<00:20:16.720> like<00:20:16.919> concrete 00:20:17.470 --> 00:20:17.480 align:start position:0% con concolic part so it's like concrete 00:20:17.480 --> 00:20:22.590 align:start position:0% con concolic part so it's like concrete and<00:20:18.039> symbolic<00:20:19.039> um<00:20:19.880> but<00:20:20.320> yeah<00:20:20.480> so<00:20:21.240> the<00:20:22.240> I<00:20:22.360> think 00:20:22.590 --> 00:20:22.600 align:start position:0% and symbolic um but yeah so the I think 00:20:22.600 --> 00:20:24.190 align:start position:0% and symbolic um but yeah so the I think that's<00:20:22.960> that's<00:20:23.080> an<00:20:23.240> interesting<00:20:23.840> area<00:20:24.080> it's 00:20:24.190 --> 00:20:24.200 align:start position:0% that's that's an interesting area it's 00:20:24.200 --> 00:20:26.149 align:start position:0% that's that's an interesting area it's not<00:20:24.600> sort<00:20:24.720> of<00:20:24.840> what<00:20:24.960> we<00:20:25.159> focused<00:20:25.559> on<00:20:26.000> uh 00:20:26.149 --> 00:20:26.159 align:start position:0% not sort of what we focused on uh 00:20:26.159 --> 00:20:27.830 align:start position:0% not sort of what we focused on uh because<00:20:26.440> we<00:20:26.799> we're<00:20:26.960> not<00:20:27.080> so<00:20:27.240> much<00:20:27.400> interested 00:20:27.830 --> 00:20:27.840 align:start position:0% because we we're not so much interested 00:20:27.840 --> 00:20:31.029 align:start position:0% because we we're not so much interested in<00:20:28.039> actually<00:20:28.799> ating<00:20:29.080> inputs<00:20:29.600> for<00:20:29.880> these<00:20:30.679> uh 00:20:31.029 --> 00:20:31.039 align:start position:0% in actually ating inputs for these uh 00:20:31.039 --> 00:20:33.070 align:start position:0% in actually ating inputs for these uh circuits<00:20:32.039> um<00:20:32.200> that's<00:20:32.360> something<00:20:32.640> you<00:20:32.760> would 00:20:33.070 --> 00:20:33.080 align:start position:0% circuits um that's something you would 00:20:33.080 --> 00:20:35.430 align:start position:0% circuits um that's something you would probably<00:20:33.320> want<00:20:33.400> to<00:20:33.600> do<00:20:34.000> if<00:20:34.159> you<00:20:34.799> want<00:20:34.960> to<00:20:35.320> have 00:20:35.430 --> 00:20:35.440 align:start position:0% probably want to do if you want to have 00:20:35.440 --> 00:20:37.310 align:start position:0% probably want to do if you want to have a<00:20:35.679> specific<00:20:36.080> circuit<00:20:36.640> that<00:20:36.760> you<00:20:36.840> want<00:20:36.960> to<00:20:37.240> you 00:20:37.310 --> 00:20:37.320 align:start position:0% a specific circuit that you want to you 00:20:37.320 --> 00:20:39.070 align:start position:0% a specific circuit that you want to you know<00:20:37.520> get<00:20:37.799> right<00:20:38.200> and<00:20:38.320> you<00:20:38.400> want<00:20:38.520> to<00:20:38.679> make<00:20:38.799> sure 00:20:39.070 --> 00:20:39.080 align:start position:0% know get right and you want to make sure 00:20:39.080 --> 00:20:41.669 align:start position:0% know get right and you want to make sure it<00:20:39.480> h<00:20:39.679> satisfies<00:20:40.200> some<00:20:40.400> properties<00:20:41.280> then<00:20:41.520> you 00:20:41.669 --> 00:20:41.679 align:start position:0% it h satisfies some properties then you 00:20:41.679 --> 00:20:43.390 align:start position:0% it h satisfies some properties then you probably<00:20:42.000> should<00:20:42.679> think<00:20:42.919> about<00:20:43.120> you<00:20:43.240> know 00:20:43.390 --> 00:20:43.400 align:start position:0% probably should think about you know 00:20:43.400 --> 00:20:46.789 align:start position:0% probably should think about you know concolic<00:20:43.880> testing<00:20:44.240> for<00:20:44.480> that<00:20:45.000> circuit<00:20:46.000> um 00:20:46.789 --> 00:20:46.799 align:start position:0% concolic testing for that circuit um 00:20:46.799 --> 00:20:50.149 align:start position:0% concolic testing for that circuit um yeah<00:20:47.799> perfect<00:20:48.240> thank<00:20:48.600> you<00:20:49.600> how<00:20:49.720> does<00:20:49.880> it<00:20:50.000> feel 00:20:50.149 --> 00:20:50.159 align:start position:0% yeah perfect thank you how does it feel 00:20:50.159 --> 00:20:52.350 align:start position:0% yeah perfect thank you how does it feel to<00:20:50.280> find<00:20:50.480> a<00:20:50.640> bug<00:20:51.159> it<00:20:51.400> like<00:20:51.679> literally<00:20:52.080> when<00:20:52.200> you 00:20:52.350 --> 00:20:52.360 align:start position:0% to find a bug it like literally when you 00:20:52.360 --> 00:20:55.590 align:start position:0% to find a bug it like literally when you find<00:20:52.960> one<00:20:53.960> is<00:20:54.039> it<00:20:54.440> is<00:20:54.559> it<00:20:54.760> scary<00:20:55.280> is<00:20:55.400> it 00:20:55.590 --> 00:20:55.600 align:start position:0% find one is it is it scary is it 00:20:55.600 --> 00:20:57.110 align:start position:0% find one is it is it scary is it exciting<00:20:56.000> I<00:20:56.080> mean<00:20:56.200> you're<00:20:56.440> looking<00:20:56.679> for<00:20:56.880> those 00:20:57.110 --> 00:20:57.120 align:start position:0% exciting I mean you're looking for those 00:20:57.120 --> 00:20:58.870 align:start position:0% exciting I mean you're looking for those so<00:20:57.240> it's<00:20:57.400> probably<00:20:57.679> a<00:20:57.799> bit<00:20:58.039> exciting<00:20:58.640> but<00:20:58.720> it's 00:20:58.870 --> 00:20:58.880 align:start position:0% so it's probably a bit exciting but it's 00:20:58.880 --> 00:21:00.230 align:start position:0% so it's probably a bit exciting but it's also<00:20:59.159> SEC<00:20:59.480> there's<00:20:59.600> probably<00:20:59.840> money<00:21:00.039> on<00:21:00.120> the 00:21:00.230 --> 00:21:00.240 align:start position:0% also SEC there's probably money on the 00:21:00.240 --> 00:21:02.470 align:start position:0% also SEC there's probably money on the line<00:21:00.679> how<00:21:00.760> does<00:21:00.960> it<00:21:01.120> feel<00:21:01.799> no<00:21:01.960> it's<00:21:02.120> definitely 00:21:02.470 --> 00:21:02.480 align:start position:0% line how does it feel no it's definitely 00:21:02.480 --> 00:21:04.470 align:start position:0% line how does it feel no it's definitely I<00:21:02.559> mean<00:21:02.679> it's<00:21:02.799> definitely<00:21:03.120> exciting<00:21:03.919> um<00:21:04.240> and<00:21:04.360> I 00:21:04.470 --> 00:21:04.480 align:start position:0% I mean it's definitely exciting um and I 00:21:04.480 --> 00:21:09.110 align:start position:0% I mean it's definitely exciting um and I work<00:21:04.960> a<00:21:05.000> lot<00:21:05.240> with<00:21:05.679> students<00:21:07.120> um<00:21:08.120> and<00:21:08.440> you<00:21:08.559> know 00:21:09.110 --> 00:21:09.120 align:start position:0% work a lot with students um and you know 00:21:09.120 --> 00:21:11.269 align:start position:0% work a lot with students um and you know it<00:21:09.480> it<00:21:09.640> really<00:21:10.279> you<00:21:10.400> know<00:21:10.679> they<00:21:10.840> you<00:21:10.919> can<00:21:11.039> see 00:21:11.269 --> 00:21:11.279 align:start position:0% it it really you know they you can see 00:21:11.279 --> 00:21:12.630 align:start position:0% it it really you know they you can see they're<00:21:11.600> they're<00:21:11.799> excited<00:21:12.120> when<00:21:12.240> they<00:21:12.360> find<00:21:12.520> a 00:21:12.630 --> 00:21:12.640 align:start position:0% they're they're excited when they find a 00:21:12.640 --> 00:21:15.029 align:start position:0% they're they're excited when they find a bark<00:21:13.400> uh<00:21:13.559> they're<00:21:13.760> happy<00:21:14.039> they're<00:21:14.360> making<00:21:14.919> you 00:21:15.029 --> 00:21:15.039 align:start position:0% bark uh they're happy they're making you 00:21:15.039 --> 00:21:18.350 align:start position:0% bark uh they're happy they're making you know<00:21:15.200> an<00:21:15.360> impact<00:21:16.279> um<00:21:17.120> and<00:21:17.320> also<00:21:17.600> the<00:21:17.760> reactions 00:21:18.350 --> 00:21:18.360 align:start position:0% know an impact um and also the reactions 00:21:18.360 --> 00:21:20.630 align:start position:0% know an impact um and also the reactions from<00:21:18.679> the<00:21:19.159> developers<00:21:19.840> are<00:21:20.120> a<00:21:20.320> great 00:21:20.630 --> 00:21:20.640 align:start position:0% from the developers are a great 00:21:20.640 --> 00:21:23.269 align:start position:0% from the developers are a great motivation<00:21:21.320> to<00:21:21.799> find<00:21:22.400> more<00:21:22.679> bugs<00:21:23.039> because 00:21:23.269 --> 00:21:23.279 align:start position:0% motivation to find more bugs because 00:21:23.279 --> 00:21:26.029 align:start position:0% motivation to find more bugs because usually<00:21:23.600> they're<00:21:24.039> very<00:21:25.039> um<00:21:25.360> yeah<00:21:25.640> they<00:21:25.840> have 00:21:26.029 --> 00:21:26.039 align:start position:0% usually they're very um yeah they have 00:21:26.039 --> 00:21:28.310 align:start position:0% usually they're very um yeah they have been<00:21:26.200> very<00:21:26.440> positive<00:21:27.159> I<00:21:27.279> don't<00:21:27.559> believe<00:21:27.960> you 00:21:28.310 --> 00:21:28.320 align:start position:0% been very positive I don't believe you 00:21:28.320 --> 00:21:29.590 align:start position:0% been very positive I don't believe you there<00:21:28.600> there's<00:21:28.760> no<00:21:28.880> way<00:21:29.000> you<00:21:29.120> go<00:21:29.240> to<00:21:29.400> people 00:21:29.590 --> 00:21:29.600 align:start position:0% there there's no way you go to people 00:21:29.600 --> 00:21:31.269 align:start position:0% there there's no way you go to people and<00:21:29.720> say<00:21:29.960> Yeah<00:21:30.159> I<00:21:30.279> broke<00:21:30.559> your<00:21:31.200> and 00:21:31.269 --> 00:21:31.279 align:start position:0% and say Yeah I broke your and 00:21:31.279 --> 00:21:32.870 align:start position:0% and say Yeah I broke your and they're<00:21:31.480> like<00:21:31.720> oh<00:21:31.960> yeah 00:21:32.870 --> 00:21:32.880 align:start position:0% they're like oh yeah 00:21:32.880 --> 00:21:35.909 align:start position:0% they're like oh yeah amazing<00:21:33.880> yeah<00:21:34.320> I<00:21:34.400> mean<00:21:34.600> if<00:21:34.799> if<00:21:35.120> if<00:21:35.240> you're<00:21:35.720> sort 00:21:35.909 --> 00:21:35.919 align:start position:0% amazing yeah I mean if if if you're sort 00:21:35.919 --> 00:21:37.350 align:start position:0% amazing yeah I mean if if if you're sort of<00:21:36.279> yeah<00:21:36.480> if 00:21:37.350 --> 00:21:37.360 align:start position:0% of yeah if 00:21:37.360 --> 00:21:41.310 align:start position:0% of yeah if you're<00:21:38.360> um<00:21:38.919> yeah<00:21:39.559> L2<00:21:40.000> and<00:21:40.200> one<00:21:40.400> bug<00:21:40.760> like<00:21:40.960> this 00:21:41.310 --> 00:21:41.320 align:start position:0% you're um yeah L2 and one bug like this 00:21:41.320 --> 00:21:44.269 align:start position:0% you're um yeah L2 and one bug like this can<00:21:41.559> you<00:21:41.679> know<00:21:41.880> wreck<00:21:42.200> your<00:21:42.400> system<00:21:43.120> then<00:21:44.120> yeah 00:21:44.269 --> 00:21:44.279 align:start position:0% can you know wreck your system then yeah 00:21:44.279 --> 00:21:46.470 align:start position:0% can you know wreck your system then yeah in<00:21:44.440> some<00:21:44.840> sense<00:21:45.159> your<00:21:45.440> your<00:21:45.600> job<00:21:45.840> is<00:21:46.000> also<00:21:46.320> on 00:21:46.470 --> 00:21:46.480 align:start position:0% in some sense your your job is also on 00:21:46.480 --> 00:21:49.029 align:start position:0% in some sense your your job is also on the<00:21:46.640> line<00:21:47.159> so<00:21:47.440> you<00:21:47.559> should<00:21:48.360> you<00:21:48.520> want<00:21:48.640> to<00:21:48.799> find 00:21:49.029 --> 00:21:49.039 align:start position:0% the line so you should you want to find 00:21:49.039 --> 00:21:50.430 align:start position:0% the line so you should you want to find those<00:21:49.240> bugs<00:21:49.480> I'm<00:21:49.559> not<00:21:49.640> saying<00:21:49.880> you<00:21:50.000> don't<00:21:50.279> want 00:21:50.430 --> 00:21:50.440 align:start position:0% those bugs I'm not saying you don't want 00:21:50.440 --> 00:21:53.470 align:start position:0% those bugs I'm not saying you don't want to<00:21:50.640> it's<00:21:50.799> just<00:21:51.840> scary<00:21:52.840> when<00:21:52.960> I<00:21:53.039> think<00:21:53.240> about 00:21:53.470 --> 00:21:53.480 align:start position:0% to it's just scary when I think about 00:21:53.480 --> 00:21:55.669 align:start position:0% to it's just scary when I think about bugs<00:21:53.720> I<00:21:53.840> think<00:21:54.000> like<00:21:54.200> yes<00:21:54.360> I<00:21:54.440> want<00:21:54.559> to<00:21:54.720> fix<00:21:55.039> them 00:21:55.669 --> 00:21:55.679 align:start position:0% bugs I think like yes I want to fix them 00:21:55.679 --> 00:21:56.830 align:start position:0% bugs I think like yes I want to fix them the<00:21:55.760> first<00:21:55.919> thing<00:21:56.080> that<00:21:56.240> comes<00:21:56.400> to<00:21:56.520> mind<00:21:56.679> is 00:21:56.830 --> 00:21:56.840 align:start position:0% the first thing that comes to mind is 00:21:56.840 --> 00:21:59.110 align:start position:0% the first thing that comes to mind is like<00:21:57.159> oh<00:21:57.480> yes<00:21:57.880> no 00:21:59.110 --> 00:21:59.120 align:start position:0% like oh yes no 00:21:59.120 --> 00:22:00.510 align:start position:0% like oh yes no but<00:21:59.279> you're<00:21:59.480> right<00:21:59.640> it's<00:21:59.799> better<00:22:00.000> to<00:22:00.120> be<00:22:00.240> aware 00:22:00.510 --> 00:22:00.520 align:start position:0% but you're right it's better to be aware 00:22:00.520 --> 00:22:02.470 align:start position:0% but you're right it's better to be aware of<00:22:00.880> FR<00:22:01.240> than<00:22:01.400> not<00:22:01.720> okay<00:22:01.880> we<00:22:01.960> can<00:22:02.120> actually<00:22:02.320> take 00:22:02.470 --> 00:22:02.480 align:start position:0% of FR than not okay we can actually take 00:22:02.480 --> 00:22:05.390 align:start position:0% of FR than not okay we can actually take the<00:22:02.720> last<00:22:03.039> oh<00:22:03.400> one<00:22:03.640> seconds<00:22:04.039> left<00:22:05.000> let's<00:22:05.159> wrap 00:22:05.390 --> 00:22:05.400 align:start position:0% the last oh one seconds left let's wrap 00:22:05.400 --> 00:22:07.950 align:start position:0% the last oh one seconds left let's wrap it<00:22:05.520> up<00:22:05.679> or<00:22:05.840> do<00:22:05.919> you<00:22:06.039> want<00:22:06.320> to<00:22:07.320> are<00:22:07.440> you<00:22:07.600> using 00:22:07.950 --> 00:22:07.960 align:start position:0% it up or do you want to are you using 00:22:07.960 --> 00:22:10.110 align:start position:0% it up or do you want to are you using property<00:22:08.320> based<00:22:08.600> testing<00:22:08.880> for<00:22:09.080> choosing<00:22:09.440> the 00:22:10.110 --> 00:22:10.120 align:start position:0% property based testing for choosing the 00:22:10.120 --> 00:22:13.350 align:start position:0% property based testing for choosing the input<00:22:11.120> um<00:22:12.080> we're<00:22:12.480> I<00:22:12.559> mean<00:22:12.720> you<00:22:12.799> can<00:22:13.000> call<00:22:13.200> it 00:22:13.350 --> 00:22:13.360 align:start position:0% input um we're I mean you can call it 00:22:13.360 --> 00:22:14.710 align:start position:0% input um we're I mean you can call it property<00:22:13.679> based<00:22:13.960> testing<00:22:14.400> but<00:22:14.559> we're 00:22:14.710 --> 00:22:14.720 align:start position:0% property based testing but we're 00:22:14.720 --> 00:22:16.750 align:start position:0% property based testing but we're generating<00:22:15.159> the<00:22:15.279> inputs<00:22:15.720> right<00:22:15.880> now<00:22:16.600> uh 00:22:16.750 --> 00:22:16.760 align:start position:0% generating the inputs right now uh 00:22:16.760 --> 00:22:18.149 align:start position:0% generating the inputs right now uh completely<00:22:17.200> randomly<00:22:17.640> so<00:22:17.799> it's<00:22:17.919> kind<00:22:18.000> of 00:22:18.149 --> 00:22:18.159 align:start position:0% completely randomly so it's kind of 00:22:18.159 --> 00:22:20.390 align:start position:0% completely randomly so it's kind of blackbox<00:22:18.600> fuzzing<00:22:19.200> that<00:22:19.360> we're<00:22:19.520> doing<00:22:20.279> and 00:22:20.390 --> 00:22:20.400 align:start position:0% blackbox fuzzing that we're doing and 00:22:20.400 --> 00:22:22.070 align:start position:0% blackbox fuzzing that we're doing and we're<00:22:20.520> also<00:22:20.720> considering<00:22:21.080> to<00:22:21.240> do<00:22:21.480> more<00:22:21.960> you 00:22:22.070 --> 00:22:22.080 align:start position:0% we're also considering to do more you 00:22:22.080 --> 00:22:23.990 align:start position:0% we're also considering to do more you know<00:22:22.320> feedback<00:22:22.799> directed<00:22:23.159> fuzzing<00:22:23.760> like<00:22:23.919> you 00:22:23.990 --> 00:22:24.000 align:start position:0% know feedback directed fuzzing like you 00:22:24.000 --> 00:22:27.909 align:start position:0% know feedback directed fuzzing like you saw<00:22:24.400> in<00:22:24.520> the<00:22:24.679> last<00:22:24.880> talk<00:22:25.600> um<00:22:26.360> yeah<00:22:27.279> fantastic 00:22:27.909 --> 00:22:27.919 align:start position:0% saw in the last talk um yeah fantastic 00:22:27.919 --> 00:22:32.799 align:start position:0% saw in the last talk um yeah fantastic thank<00:22:28.080> you<00:22:28.240> thank<00:22:28.360> you<00:22:28.600> Valentine<00:22:29.600> thank<00:22:29.799> you