WEBVTT Kind: captions Language: en 00:00:03.270 --> 00:00:09.470 align:start position:0% [Music] 00:00:09.470 --> 00:00:09.480 align:start position:0% [Music] 00:00:09.480 --> 00:00:11.589 align:start position:0% [Music] hi<00:00:09.639> everyone<00:00:10.360> uh<00:00:10.519> I'm<00:00:10.679> Pina<00:00:11.080> from<00:00:11.200> runtime 00:00:11.589 --> 00:00:11.599 align:start position:0% hi everyone uh I'm Pina from runtime 00:00:11.599 --> 00:00:13.150 align:start position:0% hi everyone uh I'm Pina from runtime verification<00:00:12.280> and<00:00:12.400> today<00:00:12.639> I'm<00:00:12.759> going<00:00:12.960> to 00:00:13.150 --> 00:00:13.160 align:start position:0% verification and today I'm going to 00:00:13.160 --> 00:00:14.869 align:start position:0% verification and today I'm going to present<00:00:13.440> our<00:00:13.719> comprehensive<00:00:14.400> approach<00:00:14.679> to 00:00:14.869 --> 00:00:14.879 align:start position:0% present our comprehensive approach to 00:00:14.879 --> 00:00:17.429 align:start position:0% present our comprehensive approach to security<00:00:15.719> that<00:00:15.920> we<00:00:16.119> have<00:00:16.320> R<00:00:16.520> RV<00:00:16.960> because<00:00:17.320> I 00:00:17.429 --> 00:00:17.439 align:start position:0% security that we have R RV because I 00:00:17.439 --> 00:00:19.230 align:start position:0% security that we have R RV because I believe<00:00:17.760> that<00:00:17.960> it's<00:00:18.320> it<00:00:18.439> can<00:00:18.640> significantly 00:00:19.230 --> 00:00:19.240 align:start position:0% believe that it's it can significantly 00:00:19.240 --> 00:00:21.070 align:start position:0% believe that it's it can significantly improve<00:00:19.560> the<00:00:19.640> security<00:00:20.000> stance<00:00:20.359> of<00:00:20.560> projects 00:00:21.070 --> 00:00:21.080 align:start position:0% improve the security stance of projects 00:00:21.080 --> 00:00:23.550 align:start position:0% improve the security stance of projects and<00:00:21.320> even<00:00:21.560> make<00:00:21.720> it<00:00:21.880> more<00:00:22.119> sustainable<00:00:22.880> for 00:00:23.550 --> 00:00:23.560 align:start position:0% and even make it more sustainable for 00:00:23.560 --> 00:00:25.910 align:start position:0% and even make it more sustainable for them<00:00:24.560> um<00:00:24.760> I'd<00:00:24.920> like<00:00:25.039> to<00:00:25.199> represent<00:00:25.680> this 00:00:25.910 --> 00:00:25.920 align:start position:0% them um I'd like to represent this 00:00:25.920 --> 00:00:28.349 align:start position:0% them um I'd like to represent this project<00:00:26.240> as<00:00:26.359> a<00:00:26.519> pyramid<00:00:27.000> where<00:00:27.240> lower<00:00:27.640> layers 00:00:28.349 --> 00:00:28.359 align:start position:0% project as a pyramid where lower layers 00:00:28.359 --> 00:00:30.749 align:start position:0% project as a pyramid where lower layers uh<00:00:28.519> enable<00:00:28.880> or<00:00:29.080> at<00:00:29.199> least<00:00:29.599> make<00:00:30.119> easier<00:00:30.480> to<00:00:30.599> get 00:00:30.749 --> 00:00:30.759 align:start position:0% uh enable or at least make easier to get 00:00:30.759 --> 00:00:33.069 align:start position:0% uh enable or at least make easier to get the<00:00:30.880> higher<00:00:31.279> lay<00:00:31.560> layers<00:00:32.040> right<00:00:32.880> and 00:00:33.069 --> 00:00:33.079 align:start position:0% the higher lay layers right and 00:00:33.079 --> 00:00:35.110 align:start position:0% the higher lay layers right and currently<00:00:33.480> the<00:00:33.680> standard<00:00:34.239> is<00:00:34.399> to<00:00:34.680> implement 00:00:35.110 --> 00:00:35.120 align:start position:0% currently the standard is to implement 00:00:35.120 --> 00:00:36.910 align:start position:0% currently the standard is to implement the<00:00:35.239> code<00:00:35.480> and<00:00:35.640> just<00:00:35.840> hand<00:00:36.000> it<00:00:36.160> over<00:00:36.360> to<00:00:36.559> some 00:00:36.910 --> 00:00:36.920 align:start position:0% the code and just hand it over to some 00:00:36.920 --> 00:00:40.029 align:start position:0% the code and just hand it over to some external<00:00:37.360> auditor<00:00:37.960> or<00:00:38.200> a<00:00:38.600> contest<00:00:39.480> for<00:00:39.800> a 00:00:40.029 --> 00:00:40.039 align:start position:0% external auditor or a contest for a 00:00:40.039 --> 00:00:42.229 align:start position:0% external auditor or a contest for a one-off<00:00:40.480> audit<00:00:40.800> or<00:00:40.960> code<00:00:41.239> review<00:00:41.840> and<00:00:42.039> while 00:00:42.229 --> 00:00:42.239 align:start position:0% one-off audit or code review and while 00:00:42.239 --> 00:00:44.869 align:start position:0% one-off audit or code review and while it<00:00:42.320> is<00:00:42.440> a<00:00:42.600> pretty<00:00:43.320> good<00:00:43.600> Baseline<00:00:44.520> it<00:00:44.640> also 00:00:44.869 --> 00:00:44.879 align:start position:0% it is a pretty good Baseline it also 00:00:44.879 --> 00:00:46.590 align:start position:0% it is a pretty good Baseline it also doesn't<00:00:45.160> do<00:00:45.360> much<00:00:45.520> in<00:00:45.640> terms<00:00:45.960> of<00:00:46.120> continuous 00:00:46.590 --> 00:00:46.600 align:start position:0% doesn't do much in terms of continuous 00:00:46.600 --> 00:00:48.350 align:start position:0% doesn't do much in terms of continuous security<00:00:47.000> assurance<00:00:47.719> and<00:00:47.920> that<00:00:48.039> is<00:00:48.199> very 00:00:48.350 --> 00:00:48.360 align:start position:0% security assurance and that is very 00:00:48.360 --> 00:00:50.150 align:start position:0% security assurance and that is very important<00:00:48.920> especially<00:00:49.239> for<00:00:49.480> protocols<00:00:49.879> under 00:00:50.150 --> 00:00:50.160 align:start position:0% important especially for protocols under 00:00:50.160 --> 00:00:51.150 align:start position:0% important especially for protocols under active 00:00:51.150 --> 00:00:51.160 align:start position:0% active 00:00:51.160 --> 00:00:53.950 align:start position:0% active development<00:00:52.160> um<00:00:52.399> if<00:00:52.520> the<00:00:52.719> team<00:00:53.079> has<00:00:53.320> resources 00:00:53.950 --> 00:00:53.960 align:start position:0% development um if the team has resources 00:00:53.960 --> 00:00:55.990 align:start position:0% development um if the team has resources or<00:00:54.160> feels<00:00:54.440> like<00:00:54.640> it<00:00:55.079> uh<00:00:55.199> some<00:00:55.359> projects<00:00:55.719> also 00:00:55.990 --> 00:00:56.000 align:start position:0% or feels like it uh some projects also 00:00:56.000 --> 00:00:57.750 align:start position:0% or feels like it uh some projects also have<00:00:56.160> some<00:00:56.359> documentation<00:00:57.039> outlining<00:00:57.600> what 00:00:57.750 --> 00:00:57.760 align:start position:0% have some documentation outlining what 00:00:57.760 --> 00:01:00.029 align:start position:0% have some documentation outlining what the<00:00:57.879> code<00:00:58.359> um<00:00:58.480> is<00:00:58.600> actually<00:00:58.879> supposed<00:00:59.199> to<00:00:59.320> do 00:01:00.029 --> 00:01:00.039 align:start position:0% the code um is actually supposed to do 00:01:00.039 --> 00:01:03.150 align:start position:0% the code um is actually supposed to do or<00:01:00.320> even<00:01:00.680> use<00:01:01.039> some<00:01:01.359> tooling<00:01:02.359> um<00:01:02.519> to<00:01:02.680> do<00:01:02.879> unit 00:01:03.150 --> 00:01:03.160 align:start position:0% or even use some tooling um to do unit 00:01:03.160 --> 00:01:04.950 align:start position:0% or even use some tooling um to do unit testing<00:01:03.519> or<00:01:03.680> fuzzing<00:01:04.360> and<00:01:04.519> while<00:01:04.760> the 00:01:04.950 --> 00:01:04.960 align:start position:0% testing or fuzzing and while the 00:01:04.960 --> 00:01:07.190 align:start position:0% testing or fuzzing and while the completeness<00:01:05.640> of<00:01:05.880> those<00:01:06.600> is<00:01:06.799> very<00:01:07.000> much 00:01:07.190 --> 00:01:07.200 align:start position:0% completeness of those is very much 00:01:07.200 --> 00:01:09.670 align:start position:0% completeness of those is very much hindered<00:01:07.640> by<00:01:07.759> the<00:01:07.960> constraints<00:01:08.600> in<00:01:09.080> um<00:01:09.320> devel 00:01:09.670 --> 00:01:09.680 align:start position:0% hindered by the constraints in um devel 00:01:09.680 --> 00:01:12.950 align:start position:0% hindered by the constraints in um devel the<00:01:09.759> development<00:01:10.680> process<00:01:11.680> um<00:01:12.040> having<00:01:12.680> more 00:01:12.950 --> 00:01:12.960 align:start position:0% the development process um having more 00:01:12.960 --> 00:01:15.469 align:start position:0% the development process um having more complete<00:01:13.320> documentation<00:01:14.159> and<00:01:14.400> some<00:01:14.600> tests 00:01:15.469 --> 00:01:15.479 align:start position:0% complete documentation and some tests 00:01:15.479 --> 00:01:17.830 align:start position:0% complete documentation and some tests actually<00:01:15.720> makes<00:01:16.159> helps<00:01:16.439> make<00:01:16.640> sure<00:01:17.360> uh<00:01:17.560> that 00:01:17.830 --> 00:01:17.840 align:start position:0% actually makes helps make sure uh that 00:01:17.840 --> 00:01:20.429 align:start position:0% actually makes helps make sure uh that the<00:01:18.240> audit<00:01:18.720> is<00:01:18.920> actually<00:01:19.159> going<00:01:19.360> to<00:01:19.520> go<00:01:19.759> well 00:01:20.429 --> 00:01:20.439 align:start position:0% the audit is actually going to go well 00:01:20.439 --> 00:01:22.149 align:start position:0% the audit is actually going to go well because<00:01:20.759> it<00:01:20.920> adds<00:01:21.119> an<00:01:21.240> additional<00:01:21.680> Dimension 00:01:22.149 --> 00:01:22.159 align:start position:0% because it adds an additional Dimension 00:01:22.159 --> 00:01:23.749 align:start position:0% because it adds an additional Dimension to<00:01:22.320> it<00:01:22.479> since<00:01:22.720> the<00:01:22.840> auditor<00:01:23.280> can<00:01:23.439> not<00:01:23.560> only 00:01:23.749 --> 00:01:23.759 align:start position:0% to it since the auditor can not only 00:01:23.759 --> 00:01:25.950 align:start position:0% to it since the auditor can not only check<00:01:24.000> for<00:01:24.280> some<00:01:24.439> common<00:01:24.960> vulnerabilities 00:01:25.950 --> 00:01:25.960 align:start position:0% check for some common vulnerabilities 00:01:25.960 --> 00:01:28.749 align:start position:0% check for some common vulnerabilities but<00:01:26.280> also<00:01:27.040> uh<00:01:27.200> for<00:01:27.880> the<00:01:28.079> adherence<00:01:28.520> of<00:01:28.640> the 00:01:28.749 --> 00:01:28.759 align:start position:0% but also uh for the adherence of the 00:01:28.759 --> 00:01:30.550 align:start position:0% but also uh for the adherence of the code<00:01:29.079> to<00:01:29.280> the<00:01:29.439> business<00:01:29.720> law<00:01:29.920> project<00:01:30.360> uh<00:01:30.439> that 00:01:30.550 --> 00:01:30.560 align:start position:0% code to the business law project uh that 00:01:30.560 --> 00:01:31.789 align:start position:0% code to the business law project uh that they're<00:01:30.799> supposed<00:01:31.040> to 00:01:31.789 --> 00:01:31.799 align:start position:0% they're supposed to 00:01:31.799 --> 00:01:34.030 align:start position:0% they're supposed to implement<00:01:32.799> um<00:01:33.079> and<00:01:33.240> having<00:01:33.439> tests<00:01:33.759> obviously 00:01:34.030 --> 00:01:34.040 align:start position:0% implement um and having tests obviously 00:01:34.040 --> 00:01:36.230 align:start position:0% implement um and having tests obviously is<00:01:34.159> good<00:01:34.280> too<00:01:35.280> uh<00:01:35.360> a<00:01:35.479> more<00:01:35.680> comprehensive 00:01:36.230 --> 00:01:36.240 align:start position:0% is good too uh a more comprehensive 00:01:36.240 --> 00:01:38.429 align:start position:0% is good too uh a more comprehensive approach<00:01:36.759> however<00:01:37.240> uh<00:01:37.399> add<00:01:37.600> some<00:01:37.720> more<00:01:37.920> layers 00:01:38.429 --> 00:01:38.439 align:start position:0% approach however uh add some more layers 00:01:38.439 --> 00:01:40.590 align:start position:0% approach however uh add some more layers and<00:01:38.600> maybe<00:01:39.119> counterintuitively<00:01:40.119> we<00:01:40.320> actually 00:01:40.590 --> 00:01:40.600 align:start position:0% and maybe counterintuitively we actually 00:01:40.600 --> 00:01:42.350 align:start position:0% and maybe counterintuitively we actually think<00:01:40.799> that<00:01:40.920> it<00:01:41.079> makes<00:01:41.600> the<00:01:41.720> security<00:01:42.079> model 00:01:42.350 --> 00:01:42.360 align:start position:0% think that it makes the security model 00:01:42.360 --> 00:01:45.429 align:start position:0% think that it makes the security model more<00:01:43.000> sustainable<00:01:44.000> and<00:01:44.560> uh<00:01:44.680> one<00:01:44.799> of<00:01:44.920> the<00:01:45.079> steps 00:01:45.429 --> 00:01:45.439 align:start position:0% more sustainable and uh one of the steps 00:01:45.439 --> 00:01:47.230 align:start position:0% more sustainable and uh one of the steps that<00:01:45.520> is<00:01:45.640> often<00:01:45.960> overlooked<00:01:46.479> is<00:01:46.680> the<00:01:46.960> design 00:01:47.230 --> 00:01:47.240 align:start position:0% that is often overlooked is the design 00:01:47.240 --> 00:01:49.270 align:start position:0% that is often overlooked is the design review<00:01:47.840> that's<00:01:48.040> where<00:01:48.360> some<00:01:48.680> person<00:01:49.119> an 00:01:49.270 --> 00:01:49.280 align:start position:0% review that's where some person an 00:01:49.280 --> 00:01:51.670 align:start position:0% review that's where some person an auditor<00:01:49.840> looks<00:01:50.079> through<00:01:50.399> the<00:01:50.920> design 00:01:51.670 --> 00:01:51.680 align:start position:0% auditor looks through the design 00:01:51.680 --> 00:01:52.830 align:start position:0% auditor looks through the design understands<00:01:51.880> what<00:01:52.000> the<00:01:52.159> project<00:01:52.399> is<00:01:52.560> actually 00:01:52.830 --> 00:01:52.840 align:start position:0% understands what the project is actually 00:01:52.840 --> 00:01:55.550 align:start position:0% understands what the project is actually supposed<00:01:53.159> to<00:01:53.280> do<00:01:54.119> and<00:01:54.640> um<00:01:55.079> how<00:01:55.280> does<00:01:55.439> the 00:01:55.550 --> 00:01:55.560 align:start position:0% supposed to do and um how does the 00:01:55.560 --> 00:01:57.270 align:start position:0% supposed to do and um how does the architecture<00:01:56.039> looks<00:01:56.280> like<00:01:56.600> and<00:01:56.719> sees<00:01:57.039> if<00:01:57.159> it 00:01:57.270 --> 00:01:57.280 align:start position:0% architecture looks like and sees if it 00:01:57.280 --> 00:01:58.590 align:start position:0% architecture looks like and sees if it actually<00:01:57.520> makes<00:01:57.719> sense<00:01:58.039> because<00:01:58.280> if<00:01:58.439> the 00:01:58.590 --> 00:01:58.600 align:start position:0% actually makes sense because if the 00:01:58.600 --> 00:02:00.830 align:start position:0% actually makes sense because if the design<00:01:58.960> doesn't<00:02:00.000> um<00:02:00.159> then<00:02:00.320> none<00:02:00.520> of<00:02:00.680> that 00:02:00.830 --> 00:02:00.840 align:start position:0% design doesn't um then none of that 00:02:00.840 --> 00:02:02.630 align:start position:0% design doesn't um then none of that matters<00:02:01.520> actually<00:02:01.880> because<00:02:02.119> the<00:02:02.280> protocol 00:02:02.630 --> 00:02:02.640 align:start position:0% matters actually because the protocol 00:02:02.640 --> 00:02:04.350 align:start position:0% matters actually because the protocol can<00:02:02.759> still<00:02:02.920> be<00:02:03.079> compromised<00:02:03.920> and<00:02:04.079> the<00:02:04.200> good 00:02:04.350 --> 00:02:04.360 align:start position:0% can still be compromised and the good 00:02:04.360 --> 00:02:06.670 align:start position:0% can still be compromised and the good byproduct<00:02:04.880> of<00:02:05.039> that<00:02:05.360> is<00:02:05.680> that<00:02:06.039> it<00:02:06.200> also<00:02:06.439> allows 00:02:06.670 --> 00:02:06.680 align:start position:0% byproduct of that is that it also allows 00:02:06.680 --> 00:02:08.430 align:start position:0% byproduct of that is that it also allows you<00:02:06.799> to<00:02:06.920> write<00:02:07.119> Better<00:02:07.439> Properties<00:02:08.239> and 00:02:08.430 --> 00:02:08.440 align:start position:0% you to write Better Properties and 00:02:08.440 --> 00:02:10.389 align:start position:0% you to write Better Properties and specification<00:02:09.160> outlining<00:02:09.679> what<00:02:09.800> the<00:02:09.920> Cod<00:02:10.160> is 00:02:10.389 --> 00:02:10.399 align:start position:0% specification outlining what the Cod is 00:02:10.399 --> 00:02:13.110 align:start position:0% specification outlining what the Cod is should<00:02:10.640> or<00:02:10.800> should<00:02:11.039> not<00:02:11.239> do<00:02:12.239> and<00:02:12.879> once 00:02:13.110 --> 00:02:13.120 align:start position:0% should or should not do and once 00:02:13.120 --> 00:02:14.990 align:start position:0% should or should not do and once formalized<00:02:13.720> in<00:02:13.800> the<00:02:13.920> forms<00:02:14.200> of<00:02:14.400> tests<00:02:14.760> or 00:02:14.990 --> 00:02:15.000 align:start position:0% formalized in the forms of tests or 00:02:15.000 --> 00:02:17.390 align:start position:0% formalized in the forms of tests or proofs<00:02:15.440> we<00:02:15.720> that<00:02:15.920> actually<00:02:16.200> enables<00:02:17.120> uh<00:02:17.280> the 00:02:17.390 --> 00:02:17.400 align:start position:0% proofs we that actually enables uh the 00:02:17.400 --> 00:02:19.070 align:start position:0% proofs we that actually enables uh the application<00:02:17.840> of<00:02:18.000> more<00:02:18.200> advanced<00:02:18.560> tooling<00:02:19.000> we 00:02:19.070 --> 00:02:19.080 align:start position:0% application of more advanced tooling we 00:02:19.080 --> 00:02:21.670 align:start position:0% application of more advanced tooling we can<00:02:19.280> have<00:02:20.040> more<00:02:20.319> complete<00:02:20.720> fuzzing<00:02:21.120> test<00:02:21.360> SS 00:02:21.670 --> 00:02:21.680 align:start position:0% can have more complete fuzzing test SS 00:02:21.680 --> 00:02:23.229 align:start position:0% can have more complete fuzzing test SS we<00:02:21.760> can<00:02:21.879> do<00:02:22.000> formal<00:02:22.280> verification<00:02:22.879> for<00:02:23.040> even 00:02:23.229 --> 00:02:23.239 align:start position:0% we can do formal verification for even 00:02:23.239 --> 00:02:25.229 align:start position:0% we can do formal verification for even better<00:02:23.480> security<00:02:23.879> guarantees<00:02:24.720> and<00:02:24.879> the<00:02:25.040> best 00:02:25.229 --> 00:02:25.239 align:start position:0% better security guarantees and the best 00:02:25.239 --> 00:02:26.750 align:start position:0% better security guarantees and the best part<00:02:25.400> of<00:02:25.599> that<00:02:25.840> is<00:02:26.000> that<00:02:26.120> we<00:02:26.239> can<00:02:26.360> also<00:02:26.560> run 00:02:26.750 --> 00:02:26.760 align:start position:0% part of that is that we can also run 00:02:26.760 --> 00:02:29.470 align:start position:0% part of that is that we can also run them<00:02:26.879> on<00:02:27.040> CI<00:02:27.959> and<00:02:28.239> I<00:02:28.480> generally<00:02:28.959> believe<00:02:29.280> that 00:02:29.470 --> 00:02:29.480 align:start position:0% them on CI and I generally believe that 00:02:29.480 --> 00:02:32.229 align:start position:0% them on CI and I generally believe that having<00:02:30.000> automated<00:02:30.519> security<00:02:31.000> processes<00:02:32.000> um 00:02:32.229 --> 00:02:32.239 align:start position:0% having automated security processes um 00:02:32.239 --> 00:02:33.910 align:start position:0% having automated security processes um is<00:02:32.400> good<00:02:32.599> eding<00:02:32.840> more<00:02:33.040> automation<00:02:33.440> is<00:02:33.599> better 00:02:33.910 --> 00:02:33.920 align:start position:0% is good eding more automation is better 00:02:33.920 --> 00:02:35.869 align:start position:0% is good eding more automation is better because<00:02:34.120> it<00:02:34.239> makes<00:02:34.480> it<00:02:34.640> harder<00:02:35.040> to<00:02:35.440> just<00:02:35.640> skip 00:02:35.869 --> 00:02:35.879 align:start position:0% because it makes it harder to just skip 00:02:35.879 --> 00:02:38.190 align:start position:0% because it makes it harder to just skip through<00:02:36.080> certain<00:02:36.360> steps<00:02:37.080> it<00:02:37.239> ensures<00:02:37.879> that 00:02:38.190 --> 00:02:38.200 align:start position:0% through certain steps it ensures that 00:02:38.200 --> 00:02:40.390 align:start position:0% through certain steps it ensures that the<00:02:38.800> the<00:02:39.000> security<00:02:39.400> protocol<00:02:39.959> is<00:02:40.159> actually 00:02:40.390 --> 00:02:40.400 align:start position:0% the the security protocol is actually 00:02:40.400 --> 00:02:43.509 align:start position:0% the the security protocol is actually followed<00:02:41.040> consistently<00:02:42.040> and<00:02:42.280> also<00:02:42.680> CI<00:02:43.319> in 00:02:43.509 --> 00:02:43.519 align:start position:0% followed consistently and also CI in 00:02:43.519 --> 00:02:45.750 align:start position:0% followed consistently and also CI in that<00:02:43.720> sense<00:02:44.200> works<00:02:44.560> as<00:02:44.720> sort<00:02:44.920> of<00:02:45.040> an<00:02:45.239> automated 00:02:45.750 --> 00:02:45.760 align:start position:0% that sense works as sort of an automated 00:02:45.760 --> 00:02:47.589 align:start position:0% that sense works as sort of an automated audit<00:02:46.159> that<00:02:46.239> is<00:02:46.360> going<00:02:46.519> to<00:02:46.640> be<00:02:46.800> run<00:02:47.120> on<00:02:47.319> every 00:02:47.589 --> 00:02:47.599 align:start position:0% audit that is going to be run on every 00:02:47.599 --> 00:02:52.070 align:start position:0% audit that is going to be run on every PR<00:02:48.080> or<00:02:48.360> every<00:02:48.920> commit<00:02:49.920> uh<00:02:50.400> and<00:02:51.400> um<00:02:51.680> well<00:02:51.879> that's 00:02:52.070 --> 00:02:52.080 align:start position:0% PR or every commit uh and um well that's 00:02:52.080 --> 00:02:54.390 align:start position:0% PR or every commit uh and um well that's less<00:02:52.319> expensive<00:02:52.720> than<00:02:52.920> having<00:02:53.280> a<00:02:53.519> human<00:02:54.159> looks 00:02:54.390 --> 00:02:54.400 align:start position:0% less expensive than having a human looks 00:02:54.400 --> 00:02:56.670 align:start position:0% less expensive than having a human looks through<00:02:54.560> it<00:02:54.840> over<00:02:55.040> and<00:02:55.159> over<00:02:55.400> again<00:02:56.120> so<00:02:56.360> as<00:02:56.480> an 00:02:56.670 --> 00:02:56.680 align:start position:0% through it over and over again so as an 00:02:56.680 --> 00:02:58.149 align:start position:0% through it over and over again so as an example<00:02:57.200> of 00:02:58.149 --> 00:02:58.159 align:start position:0% example of 00:02:58.159 --> 00:03:01.190 align:start position:0% example of something<00:02:59.159> um<00:02:59.599> that 00:03:01.190 --> 00:03:01.200 align:start position:0% something um that 00:03:01.200 --> 00:03:03.589 align:start position:0% something um that as<00:03:01.319> an<00:03:01.480> example<00:03:01.840> of<00:03:02.040> how<00:03:02.200> it<00:03:02.319> is<00:03:02.920> important<00:03:03.400> to 00:03:03.589 --> 00:03:03.599 align:start position:0% as an example of how it is important to 00:03:03.599 --> 00:03:05.550 align:start position:0% as an example of how it is important to follow<00:03:04.000> through<00:03:04.440> this<00:03:04.599> whole<00:03:04.879> process<00:03:05.239> I<00:03:05.360> have 00:03:05.550 --> 00:03:05.560 align:start position:0% follow through this whole process I have 00:03:05.560 --> 00:03:08.550 align:start position:0% follow through this whole process I have this<00:03:06.480> well<00:03:06.760> example<00:03:07.159> that<00:03:07.319> mayor<00:03:07.680> may<00:03:07.879> not<00:03:08.400> be 00:03:08.550 --> 00:03:08.560 align:start position:0% this well example that mayor may not be 00:03:08.560 --> 00:03:10.309 align:start position:0% this well example that mayor may not be based<00:03:08.760> on<00:03:08.879> a<00:03:09.000> recent<00:03:09.280> hack<00:03:09.879> and<00:03:09.959> that<00:03:10.080> happened 00:03:10.309 --> 00:03:10.319 align:start position:0% based on a recent hack and that happened 00:03:10.319 --> 00:03:12.949 align:start position:0% based on a recent hack and that happened to<00:03:10.440> the<00:03:10.680> protocol<00:03:11.680> that<00:03:12.080> uh<00:03:12.200> helped<00:03:12.519> users 00:03:12.949 --> 00:03:12.959 align:start position:0% to the protocol that uh helped users 00:03:12.959 --> 00:03:15.070 align:start position:0% to the protocol that uh helped users convert<00:03:13.400> their<00:03:13.640> BDC<00:03:14.239> into<00:03:14.480> an<00:03:14.680> equivalent 00:03:15.070 --> 00:03:15.080 align:start position:0% convert their BDC into an equivalent 00:03:15.080 --> 00:03:17.149 align:start position:0% convert their BDC into an equivalent amount<00:03:15.400> of<00:03:15.599> R<00:03:15.879> BDC<00:03:16.280> that<00:03:16.360> we'll<00:03:16.519> call<00:03:16.720> Defcon 00:03:17.149 --> 00:03:17.159 align:start position:0% amount of R BDC that we'll call Defcon 00:03:17.159 --> 00:03:19.830 align:start position:0% amount of R BDC that we'll call Defcon BTC<00:03:18.159> and<00:03:18.360> it<00:03:18.480> was<00:03:18.599> running<00:03:18.840> on<00:03:19.000> BTC<00:03:19.360> chains<00:03:19.720> so 00:03:19.830 --> 00:03:19.840 align:start position:0% BTC and it was running on BTC chains so 00:03:19.840 --> 00:03:21.070 align:start position:0% BTC and it was running on BTC chains so it<00:03:19.959> was<00:03:20.080> supposed<00:03:20.360> to<00:03:20.440> work<00:03:20.640> with<00:03:20.760> Native 00:03:21.070 --> 00:03:21.080 align:start position:0% it was supposed to work with Native 00:03:21.080 --> 00:03:22.949 align:start position:0% it was supposed to work with Native tokens<00:03:21.680> but<00:03:21.840> it<00:03:21.920> was<00:03:22.080> also<00:03:22.239> running<00:03:22.519> on<00:03:22.680> other 00:03:22.949 --> 00:03:22.959 align:start position:0% tokens but it was also running on other 00:03:22.959 --> 00:03:24.630 align:start position:0% tokens but it was also running on other networks<00:03:23.440> which<00:03:23.599> had<00:03:23.799> ethereum<00:03:24.159> as<00:03:24.280> a<00:03:24.360> native 00:03:24.630 --> 00:03:24.640 align:start position:0% networks which had ethereum as a native 00:03:24.640 --> 00:03:26.229 align:start position:0% networks which had ethereum as a native token<00:03:25.239> and<00:03:25.360> there<00:03:25.480> was<00:03:25.599> a<00:03:25.720> change<00:03:26.080> that 00:03:26.229 --> 00:03:26.239 align:start position:0% token and there was a change that 00:03:26.239 --> 00:03:28.190 align:start position:0% token and there was a change that actually<00:03:26.480> made<00:03:26.640> it<00:03:26.879> possible<00:03:27.200> for<00:03:27.440> users<00:03:28.000> to 00:03:28.190 --> 00:03:28.200 align:start position:0% actually made it possible for users to 00:03:28.200 --> 00:03:30.670 align:start position:0% actually made it possible for users to Mint<00:03:29.159> uh<00:03:29.280> an<00:03:29.400> equivalent<00:03:29.879> amount<00:03:30.159> of<00:03:30.280> Defcon 00:03:30.670 --> 00:03:30.680 align:start position:0% Mint uh an equivalent amount of Defcon 00:03:30.680 --> 00:03:32.830 align:start position:0% Mint uh an equivalent amount of Defcon BDC<00:03:31.080> for<00:03:31.280> eer<00:03:31.680> and<00:03:31.799> iser<00:03:32.080> is<00:03:32.159> like<00:03:32.319> 20<00:03:32.599> times 00:03:32.830 --> 00:03:32.840 align:start position:0% BDC for eer and iser is like 20 times 00:03:32.840 --> 00:03:35.110 align:start position:0% BDC for eer and iser is like 20 times cheaper<00:03:33.319> so<00:03:33.480> the<00:03:33.640> hacker<00:03:34.120> actually<00:03:34.760> just<00:03:34.920> made 00:03:35.110 --> 00:03:35.120 align:start position:0% cheaper so the hacker actually just made 00:03:35.120 --> 00:03:38.670 align:start position:0% cheaper so the hacker actually just made it<00:03:35.200> a<00:03:35.319> lot<00:03:35.400> of<00:03:35.519> free<00:03:35.720> money<00:03:36.080> basically<00:03:37.560> and<00:03:38.560> the 00:03:38.670 --> 00:03:38.680 align:start position:0% it a lot of free money basically and the 00:03:38.680 --> 00:03:40.270 align:start position:0% it a lot of free money basically and the thing<00:03:38.879> is<00:03:39.080> there<00:03:39.200> was<00:03:39.319> a<00:03:39.480> property<00:03:39.920> that<00:03:40.080> just 00:03:40.270 --> 00:03:40.280 align:start position:0% thing is there was a property that just 00:03:40.280 --> 00:03:42.470 align:start position:0% thing is there was a property that just hasn't<00:03:40.519> been<00:03:40.680> informed<00:03:41.480> or<00:03:42.040> maybe<00:03:42.280> hasn't 00:03:42.470 --> 00:03:42.480 align:start position:0% hasn't been informed or maybe hasn't 00:03:42.480 --> 00:03:43.990 align:start position:0% hasn't been informed or maybe hasn't been<00:03:42.640> formulated<00:03:43.239> that<00:03:43.400> the<00:03:43.480> user<00:03:43.720> should 00:03:43.990 --> 00:03:44.000 align:start position:0% been formulated that the user should 00:03:44.000 --> 00:03:46.470 align:start position:0% been formulated that the user should also<00:03:44.280> not<00:03:44.519> be<00:03:44.680> able<00:03:45.280> to<00:03:45.480> convert<00:03:45.879> non<00:03:46.080> BTC 00:03:46.470 --> 00:03:46.480 align:start position:0% also not be able to convert non BTC 00:03:46.480 --> 00:03:49.750 align:start position:0% also not be able to convert non BTC tokens<00:03:47.040> into<00:03:47.680> U<00:03:47.920> well<00:03:48.120> the<00:03:48.239> rupt<00:03:48.560> version<00:03:48.840> of 00:03:49.750 --> 00:03:49.760 align:start position:0% tokens into U well the rupt version of 00:03:49.760 --> 00:03:52.550 align:start position:0% tokens into U well the rupt version of BTC<00:03:50.760> and<00:03:51.239> this<00:03:51.560> property<00:03:52.000> could<00:03:52.280> actually 00:03:52.550 --> 00:03:52.560 align:start position:0% BTC and this property could actually 00:03:52.560 --> 00:03:53.869 align:start position:0% BTC and this property could actually have<00:03:52.680> been<00:03:52.879> enforced<00:03:53.280> with<00:03:53.439> something<00:03:53.760> as 00:03:53.869 --> 00:03:53.879 align:start position:0% have been enforced with something as 00:03:53.879 --> 00:03:55.710 align:start position:0% have been enforced with something as simple<00:03:54.159> as<00:03:54.239> a<00:03:54.400> unit<00:03:54.720> test<00:03:55.000> or<00:03:55.200> this<00:03:55.360> fuzzing 00:03:55.710 --> 00:03:55.720 align:start position:0% simple as a unit test or this fuzzing 00:03:55.720 --> 00:03:57.750 align:start position:0% simple as a unit test or this fuzzing test<00:03:56.000> that<00:03:56.120> you<00:03:56.200> can<00:03:56.319> see<00:03:56.480> on<00:03:56.599> the<00:03:56.720> slide<00:03:57.599> um 00:03:57.750 --> 00:03:57.760 align:start position:0% test that you can see on the slide um 00:03:57.760 --> 00:04:00.550 align:start position:0% test that you can see on the slide um that<00:03:57.920> just<00:03:58.079> checks<00:03:58.439> that<00:03:58.760> if<00:03:59.519> um<00:04:00.040> the<00:04:00.200> protocol 00:04:00.550 --> 00:04:00.560 align:start position:0% that just checks that if um the protocol 00:04:00.560 --> 00:04:02.830 align:start position:0% that just checks that if um the protocol is<00:04:00.680> running<00:04:00.959> on<00:04:01.159> ethereum<00:04:01.560> Main<00:04:01.799> net<00:04:02.560> then 00:04:02.830 --> 00:04:02.840 align:start position:0% is running on ethereum Main net then 00:04:02.840 --> 00:04:04.470 align:start position:0% is running on ethereum Main net then whenever<00:04:03.159> someone<00:04:03.439> tries<00:04:03.680> to<00:04:03.799> Mint<00:04:04.120> tokens 00:04:04.470 --> 00:04:04.480 align:start position:0% whenever someone tries to Mint tokens 00:04:04.480 --> 00:04:07.750 align:start position:0% whenever someone tries to Mint tokens using<00:04:04.799> eer<00:04:05.599> um<00:04:05.799> this<00:04:05.959> transaction<00:04:06.640> fails<00:04:07.640> uh 00:04:07.750 --> 00:04:07.760 align:start position:0% using eer um this transaction fails uh 00:04:07.760 --> 00:04:09.869 align:start position:0% using eer um this transaction fails uh so<00:04:07.879> that<00:04:07.959> is<00:04:08.040> a<00:04:08.159> Foundry<00:04:08.519> test<00:04:09.400> uh<00:04:09.519> has<00:04:09.640> it<00:04:09.760> been 00:04:09.869 --> 00:04:09.879 align:start position:0% so that is a Foundry test uh has it been 00:04:09.879 --> 00:04:13.229 align:start position:0% so that is a Foundry test uh has it been running<00:04:10.159> on<00:04:10.319> CI<00:04:10.959> it<00:04:11.560> maybe<00:04:11.959> could<00:04:12.200> have<00:04:12.400> caught 00:04:13.229 --> 00:04:13.239 align:start position:0% running on CI it maybe could have caught 00:04:13.239 --> 00:04:15.229 align:start position:0% running on CI it maybe could have caught um<00:04:13.439> the<00:04:13.640> issue<00:04:14.040> as<00:04:14.159> soon<00:04:14.319> as<00:04:14.480> this<00:04:14.640> code<00:04:15.000> was 00:04:15.229 --> 00:04:15.239 align:start position:0% um the issue as soon as this code was 00:04:15.239 --> 00:04:16.870 align:start position:0% um the issue as soon as this code was pushed<00:04:15.560> but<00:04:15.760> before<00:04:15.959> the 00:04:16.870 --> 00:04:16.880 align:start position:0% pushed but before the 00:04:16.880 --> 00:04:19.349 align:start position:0% pushed but before the deployment<00:04:17.880> uh<00:04:18.000> so<00:04:18.160> to<00:04:18.320> summarize<00:04:19.000> the<00:04:19.120> points 00:04:19.349 --> 00:04:19.359 align:start position:0% deployment uh so to summarize the points 00:04:19.359 --> 00:04:20.949 align:start position:0% deployment uh so to summarize the points I<00:04:19.440> want<00:04:19.519> to<00:04:19.639> make<00:04:19.880> here<00:04:20.079> is<00:04:20.239> that<00:04:20.440> security<00:04:20.799> is 00:04:20.949 --> 00:04:20.959 align:start position:0% I want to make here is that security is 00:04:20.959 --> 00:04:22.270 align:start position:0% I want to make here is that security is complicated<00:04:21.479> I<00:04:21.560> think<00:04:21.720> everyone<00:04:21.959> knows<00:04:22.160> it 00:04:22.270 --> 00:04:22.280 align:start position:0% complicated I think everyone knows it 00:04:22.280 --> 00:04:23.909 align:start position:0% complicated I think everyone knows it there<00:04:22.360> are<00:04:22.479> a<00:04:22.560> lot<00:04:22.680> of<00:04:22.800> steps<00:04:23.160> in<00:04:23.320> this<00:04:23.479> process 00:04:23.909 --> 00:04:23.919 align:start position:0% there are a lot of steps in this process 00:04:23.919 --> 00:04:26.310 align:start position:0% there are a lot of steps in this process it's<00:04:24.080> very<00:04:24.240> important<00:04:25.160> to<00:04:25.560> get<00:04:25.800> all<00:04:25.960> of<00:04:26.080> them 00:04:26.310 --> 00:04:26.320 align:start position:0% it's very important to get all of them 00:04:26.320 --> 00:04:28.909 align:start position:0% it's very important to get all of them right<00:04:27.320> um<00:04:27.520> automation<00:04:28.199> is<00:04:28.360> very<00:04:28.520> useful 00:04:28.909 --> 00:04:28.919 align:start position:0% right um automation is very useful 00:04:28.919 --> 00:04:31.790 align:start position:0% right um automation is very useful because<00:04:29.120> it<00:04:29.199> helps<00:04:29.440> Ure<00:04:29.840> sure<00:04:30.360> uh<00:04:30.560> that<00:04:31.560> the 00:04:31.790 --> 00:04:31.800 align:start position:0% because it helps Ure sure uh that the 00:04:31.800 --> 00:04:34.590 align:start position:0% because it helps Ure sure uh that the process<00:04:32.520> the<00:04:32.639> security<00:04:33.120> process<00:04:33.479> is<00:04:33.639> followed 00:04:34.590 --> 00:04:34.600 align:start position:0% process the security process is followed 00:04:34.600 --> 00:04:36.749 align:start position:0% process the security process is followed um<00:04:34.800> consistently<00:04:35.520> and<00:04:35.639> is<00:04:35.840> enforced<00:04:36.440> and<00:04:36.600> in 00:04:36.749 --> 00:04:36.759 align:start position:0% um consistently and is enforced and in 00:04:36.759 --> 00:04:38.710 align:start position:0% um consistently and is enforced and in addition<00:04:37.080> CI<00:04:37.520> also<00:04:37.960> provides<00:04:38.280> a<00:04:38.440> very 00:04:38.710 --> 00:04:38.720 align:start position:0% addition CI also provides a very 00:04:38.720 --> 00:04:41.749 align:start position:0% addition CI also provides a very efficient<00:04:39.320> and<00:04:39.440> a<00:04:39.600> very<00:04:40.120> cost<00:04:40.520> effective<00:04:41.440> um 00:04:41.749 --> 00:04:41.759 align:start position:0% efficient and a very cost effective um 00:04:41.759 --> 00:04:43.270 align:start position:0% efficient and a very cost effective um way<00:04:41.960> to<00:04:42.160> ensure<00:04:42.479> that<00:04:42.600> new<00:04:42.759> updates<00:04:43.080> don't 00:04:43.270 --> 00:04:43.280 align:start position:0% way to ensure that new updates don't 00:04:43.280 --> 00:04:45.469 align:start position:0% way to ensure that new updates don't break<00:04:43.759> anything<00:04:44.759> uh<00:04:44.880> one<00:04:45.039> last<00:04:45.199> thing<00:04:45.320> that 00:04:45.469 --> 00:04:45.479 align:start position:0% break anything uh one last thing that 00:04:45.479 --> 00:04:47.189 align:start position:0% break anything uh one last thing that has<00:04:45.600> been<00:04:45.759> missing<00:04:46.120> so<00:04:46.280> far<00:04:46.600> is<00:04:46.759> this<00:04:46.919> base 00:04:47.189 --> 00:04:47.199 align:start position:0% has been missing so far is this base 00:04:47.199 --> 00:04:48.749 align:start position:0% has been missing so far is this base layer<00:04:47.560> which<00:04:47.680> I<00:04:47.759> haven't<00:04:48.000> really<00:04:48.240> touched<00:04:48.600> in 00:04:48.749 --> 00:04:48.759 align:start position:0% layer which I haven't really touched in 00:04:48.759 --> 00:04:50.950 align:start position:0% layer which I haven't really touched in detail<00:04:49.240> that<00:04:49.360> is<00:04:49.680> uh<00:04:49.840> obsc<00:04:50.720> because 00:04:50.950 --> 00:04:50.960 align:start position:0% detail that is uh obsc because 00:04:50.960 --> 00:04:52.830 align:start position:0% detail that is uh obsc because unfortunately<00:04:51.680> there<00:04:51.880> have<00:04:52.039> been<00:04:52.320> a<00:04:52.479> lot<00:04:52.639> of 00:04:52.830 --> 00:04:52.840 align:start position:0% unfortunately there have been a lot of 00:04:52.840 --> 00:04:55.230 align:start position:0% unfortunately there have been a lot of private<00:04:53.160> key<00:04:53.320> compromises<00:04:54.280> um<00:04:54.680> in<00:04:54.800> the<00:04:55.000> past 00:04:55.230 --> 00:04:55.240 align:start position:0% private key compromises um in the past 00:04:55.240 --> 00:04:56.710 align:start position:0% private key compromises um in the past year<00:04:55.720> and<00:04:55.960> if<00:04:56.080> the<00:04:56.199> private<00:04:56.479> key<00:04:56.600> is 00:04:56.710 --> 00:04:56.720 align:start position:0% year and if the private key is 00:04:56.720 --> 00:04:58.430 align:start position:0% year and if the private key is compromised<00:04:57.160> then<00:04:57.280> unfortunately<00:04:57.960> even<00:04:58.160> have 00:04:58.430 --> 00:04:58.440 align:start position:0% compromised then unfortunately even have 00:04:58.440 --> 00:05:00.790 align:start position:0% compromised then unfortunately even have very<00:04:58.639> secure<00:04:59.240> smart<00:04:59.720> contract<00:05:00.120> code<00:05:00.520> uh<00:05:00.639> can 00:05:00.790 --> 00:05:00.800 align:start position:0% very secure smart contract code uh can 00:05:00.800 --> 00:05:01.670 align:start position:0% very secure smart contract code uh can also<00:05:01.000> be 00:05:01.670 --> 00:05:01.680 align:start position:0% also be 00:05:01.680 --> 00:05:03.550 align:start position:0% also be exploited<00:05:02.680> and<00:05:02.840> and<00:05:02.960> there<00:05:03.039> are<00:05:03.160> a<00:05:03.280> lot<00:05:03.400> of 00:05:03.550 --> 00:05:03.560 align:start position:0% exploited and and there are a lot of 00:05:03.560 --> 00:05:05.350 align:start position:0% exploited and and there are a lot of resources<00:05:04.400> about<00:05:04.639> how<00:05:04.720> to<00:05:04.840> get<00:05:04.960> it<00:05:05.120> right<00:05:05.240> on 00:05:05.350 --> 00:05:05.360 align:start position:0% resources about how to get it right on 00:05:05.360 --> 00:05:07.469 align:start position:0% resources about how to get it right on the<00:05:05.479> internet<00:05:05.840> so<00:05:06.000> I<00:05:06.160> encourage<00:05:06.560> all<00:05:06.680> of<00:05:06.840> you 00:05:07.469 --> 00:05:07.479 align:start position:0% the internet so I encourage all of you 00:05:07.479 --> 00:05:08.990 align:start position:0% the internet so I encourage all of you um<00:05:07.600> to<00:05:07.759> look<00:05:07.919> through<00:05:08.160> it<00:05:08.400> and<00:05:08.600> yeah<00:05:08.759> thank<00:05:08.880> you 00:05:08.990 --> 00:05:09.000 align:start position:0% um to look through it and yeah thank you 00:05:09.000 --> 00:05:09.909 align:start position:0% um to look through it and yeah thank you very 00:05:09.909 --> 00:05:09.919 align:start position:0% very 00:05:09.919 --> 00:05:11.600 align:start position:0% very much<00:05:10.919> thanks 00:05:11.600 --> 00:05:11.610 align:start position:0% much thanks 00:05:11.610 --> 00:05:14.110 align:start position:0% much thanks [Applause] 00:05:14.110 --> 00:05:14.120 align:start position:0% [Applause] 00:05:14.120 --> 00:05:23.230 align:start position:0% [Applause] Pina<00:05:15.120> any<00:05:15.400> questions<00:05:15.960> for 00:05:23.230 --> 00:05:23.240 align:start position:0% 00:05:23.240 --> 00:05:26.469 align:start position:0% pina<00:05:24.240> I<00:05:24.360> guess<00:05:24.560> my<00:05:24.720> one<00:05:25.000> question<00:05:25.360> would<00:05:25.560> be 00:05:26.469 --> 00:05:26.479 align:start position:0% pina I guess my one question would be 00:05:26.479 --> 00:05:29.670 align:start position:0% pina I guess my one question would be around<00:05:27.479> maybe<00:05:27.919> fatigue<00:05:28.720> in<00:05:28.880> terms<00:05:29.160> of 00:05:29.670 --> 00:05:29.680 align:start position:0% around maybe fatigue in terms of 00:05:29.680 --> 00:05:31.469 align:start position:0% around maybe fatigue in terms of continuing<00:05:30.000> to<00:05:30.080> be<00:05:30.280> diligent<00:05:30.919> about<00:05:31.240> making 00:05:31.469 --> 00:05:31.479 align:start position:0% continuing to be diligent about making 00:05:31.479 --> 00:05:34.430 align:start position:0% continuing to be diligent about making sure<00:05:31.759> that<00:05:31.919> the<00:05:32.080> basics<00:05:32.400> are<00:05:32.600> in<00:05:32.880> place<00:05:33.880> and 00:05:34.430 --> 00:05:34.440 align:start position:0% sure that the basics are in place and 00:05:34.440 --> 00:05:37.790 align:start position:0% sure that the basics are in place and I'm<00:05:34.720> curious<00:05:35.319> for<00:05:35.600> you<00:05:36.039> what<00:05:36.280> has<00:05:36.560> helped<00:05:36.960> to 00:05:37.790 --> 00:05:37.800 align:start position:0% I'm curious for you what has helped to 00:05:37.800 --> 00:05:40.510 align:start position:0% I'm curious for you what has helped to maintain<00:05:38.800> those<00:05:39.160> habits<00:05:39.639> over 00:05:40.510 --> 00:05:40.520 align:start position:0% maintain those habits over 00:05:40.520 --> 00:05:43.990 align:start position:0% maintain those habits over time<00:05:41.520> thank<00:05:41.680> you<00:05:41.960> yeah<00:05:42.160> we<00:05:42.319> try<00:05:42.639> to<00:05:43.639> follow 00:05:43.990 --> 00:05:44.000 align:start position:0% time thank you yeah we try to follow 00:05:44.000 --> 00:05:46.670 align:start position:0% time thank you yeah we try to follow these<00:05:44.199> processes<00:05:44.639> religiously<00:05:45.600> uh<00:05:45.880> at<00:05:46.039> RV 00:05:46.670 --> 00:05:46.680 align:start position:0% these processes religiously uh at RV 00:05:46.680 --> 00:05:48.909 align:start position:0% these processes religiously uh at RV automation<00:05:47.199> helps<00:05:47.440> a<00:05:47.560> lot<00:05:47.919> because<00:05:48.680> uh<00:05:48.840> you 00:05:48.909 --> 00:05:48.919 align:start position:0% automation helps a lot because uh you 00:05:48.919 --> 00:05:51.909 align:start position:0% automation helps a lot because uh you don't<00:05:49.199> have<00:05:49.639> to<00:05:50.639> you<00:05:50.759> know<00:05:51.000> go<00:05:51.199> over<00:05:51.479> the<00:05:51.600> same 00:05:51.909 --> 00:05:51.919 align:start position:0% don't have to you know go over the same 00:05:51.919 --> 00:05:54.110 align:start position:0% don't have to you know go over the same things<00:05:52.919> uh<00:05:53.039> over<00:05:53.240> and<00:05:53.360> over<00:05:53.600> again<00:05:53.840> instead 00:05:54.110 --> 00:05:54.120 align:start position:0% things uh over and over again instead 00:05:54.120 --> 00:05:55.629 align:start position:0% things uh over and over again instead you<00:05:54.240> write<00:05:54.479> some<00:05:54.680> properties<00:05:55.280> that<00:05:55.479> you 00:05:55.629 --> 00:05:55.639 align:start position:0% you write some properties that you 00:05:55.639 --> 00:05:57.070 align:start position:0% you write some properties that you specify<00:05:56.039> some<00:05:56.199> properties<00:05:56.680> and<00:05:56.840> then<00:05:56.960> you 00:05:57.070 --> 00:05:57.080 align:start position:0% specify some properties and then you 00:05:57.080 --> 00:05:58.710 align:start position:0% specify some properties and then you formalize<00:05:57.560> them<00:05:57.680> in<00:05:57.800> the<00:05:57.919> forms<00:05:58.160> of<00:05:58.280> tests<00:05:58.560> or 00:05:58.710 --> 00:05:58.720 align:start position:0% formalize them in the forms of tests or 00:05:58.720 --> 00:06:00.710 align:start position:0% formalize them in the forms of tests or proofs<00:05:59.360> with<00:05:59.680> a<00:05:59.720> lot<00:05:59.840> of<00:05:59.919> formal<00:06:00.160> verification 00:06:00.710 --> 00:06:00.720 align:start position:0% proofs with a lot of formal verification 00:06:00.720 --> 00:06:02.350 align:start position:0% proofs with a lot of formal verification so<00:06:00.919> that's<00:06:01.120> that's<00:06:01.280> what<00:06:01.400> we<00:06:01.520> try<00:06:01.680> to<00:06:01.840> set<00:06:02.000> up 00:06:02.350 --> 00:06:02.360 align:start position:0% so that's that's what we try to set up 00:06:02.360 --> 00:06:06.110 align:start position:0% so that's that's what we try to set up and<00:06:02.639> then<00:06:03.000> as<00:06:03.960> whenever<00:06:04.319> code<00:06:04.759> changes<00:06:05.759> that 00:06:06.110 --> 00:06:06.120 align:start position:0% and then as whenever code changes that 00:06:06.120 --> 00:06:08.430 align:start position:0% and then as whenever code changes that actually<00:06:06.360> handles<00:06:06.680> it<00:06:06.840> for<00:06:07.039> us<00:06:07.800> uh<00:06:07.880> for<00:06:08.039> a<00:06:08.199> LGE 00:06:08.430 --> 00:06:08.440 align:start position:0% actually handles it for us uh for a LGE 00:06:08.440 --> 00:06:10.790 align:start position:0% actually handles it for us uh for a LGE to<00:06:08.560> a<00:06:08.680> large<00:06:08.960> degree<00:06:09.520> um<00:06:09.680> I<00:06:09.759> think<00:06:09.880> it<00:06:10.039> actually 00:06:10.790 --> 00:06:10.800 align:start position:0% to a large degree um I think it actually 00:06:10.800 --> 00:06:15.029 align:start position:0% to a large degree um I think it actually the<00:06:10.919> having<00:06:11.160> the<00:06:11.280> process<00:06:11.560> makes<00:06:11.720> it 00:06:15.029 --> 00:06:15.039 align:start position:0% 00:06:15.039 --> 00:06:20.150 align:start position:0% easier<00:06:16.039> cool<00:06:16.440> next<00:06:17.440> uh<00:06:17.639> yeah<00:06:18.000> question<00:06:19.120> on 00:06:20.150 --> 00:06:20.160 align:start position:0% easier cool next uh yeah question on 00:06:20.160 --> 00:06:22.909 align:start position:0% easier cool next uh yeah question on like<00:06:21.160> uh<00:06:21.400> blockchain<00:06:22.039> security<00:06:22.599> the<00:06:22.720> way<00:06:22.840> you 00:06:22.909 --> 00:06:22.919 align:start position:0% like uh blockchain security the way you 00:06:22.919 --> 00:06:24.670 align:start position:0% like uh blockchain security the way you have<00:06:23.080> Smart<00:06:23.319> contract<00:06:23.759> which<00:06:23.880> is<00:06:24.039> immutable 00:06:24.670 --> 00:06:24.680 align:start position:0% have Smart contract which is immutable 00:06:24.680 --> 00:06:27.589 align:start position:0% have Smart contract which is immutable versus<00:06:25.639> let's<00:06:25.800> say<00:06:25.960> on<00:06:26.120> web<00:06:26.360> 2<00:06:26.880> where<00:06:27.120> you<00:06:27.240> can 00:06:27.589 --> 00:06:27.599 align:start position:0% versus let's say on web 2 where you can 00:06:27.599 --> 00:06:29.990 align:start position:0% versus let's say on web 2 where you can update<00:06:28.000> your<00:06:28.199> code<00:06:28.840> if<00:06:28.960> you<00:06:29.319> discover 00:06:29.990 --> 00:06:30.000 align:start position:0% update your code if you discover 00:06:30.000 --> 00:06:33.629 align:start position:0% update your code if you discover security<00:06:31.000> problem<00:06:31.440> after<00:06:31.720> the<00:06:31.919> fact<00:06:32.880> so<00:06:33.520> how 00:06:33.629 --> 00:06:33.639 align:start position:0% security problem after the fact so how 00:06:33.639 --> 00:06:36.990 align:start position:0% security problem after the fact so how does<00:06:33.800> that<00:06:34.000> factor<00:06:34.800> in<00:06:35.800> Oh<00:06:35.960> you<00:06:36.080> mean 00:06:36.990 --> 00:06:37.000 align:start position:0% does that factor in Oh you mean 00:06:37.000 --> 00:06:39.230 align:start position:0% does that factor in Oh you mean upgradability<00:06:38.000> uh<00:06:38.160> not<00:06:38.400> necessarily<00:06:39.080> but 00:06:39.230 --> 00:06:39.240 align:start position:0% upgradability uh not necessarily but 00:06:39.240 --> 00:06:40.110 align:start position:0% upgradability uh not necessarily but like<00:06:39.400> let's<00:06:39.560> say<00:06:39.680> you<00:06:39.800> don't<00:06:39.960> have 00:06:40.110 --> 00:06:40.120 align:start position:0% like let's say you don't have 00:06:40.120 --> 00:06:43.029 align:start position:0% like let's say you don't have upgradeability<00:06:41.000> then<00:06:41.319> how<00:06:41.479> would<00:06:41.680> you<00:06:42.520> modify 00:06:43.029 --> 00:06:43.039 align:start position:0% upgradeability then how would you modify 00:06:43.039 --> 00:06:45.350 align:start position:0% upgradeability then how would you modify your<00:06:43.280> security<00:06:43.720> practices<00:06:44.319> such<00:06:44.639> that<00:06:45.199> that 00:06:45.350 --> 00:06:45.360 align:start position:0% your security practices such that that 00:06:45.360 --> 00:06:48.589 align:start position:0% your security practices such that that doesn't<00:06:46.120> uh<00:06:46.440> like<00:06:47.039> so<00:06:47.280> that<00:06:47.440> you<00:06:48.080> mitigate 00:06:48.589 --> 00:06:48.599 align:start position:0% doesn't uh like so that you mitigate 00:06:48.599 --> 00:06:51.110 align:start position:0% doesn't uh like so that you mitigate that<00:06:48.919> I<00:06:49.080> guess<00:06:49.880> right<00:06:50.120> got<00:06:50.240> it<00:06:50.400> thank<00:06:50.560> you<00:06:50.919> um 00:06:51.110 --> 00:06:51.120 align:start position:0% that I guess right got it thank you um 00:06:51.120 --> 00:06:52.350 align:start position:0% that I guess right got it thank you um well<00:06:51.240> I<00:06:51.360> guess<00:06:51.520> that's<00:06:51.720> why<00:06:51.840> you<00:06:51.960> try<00:06:52.120> to<00:06:52.240> get 00:06:52.350 --> 00:06:52.360 align:start position:0% well I guess that's why you try to get 00:06:52.360 --> 00:06:53.589 align:start position:0% well I guess that's why you try to get it<00:06:52.520> right<00:06:52.800> the<00:06:52.919> first<00:06:53.120> time<00:06:53.280> before 00:06:53.589 --> 00:06:53.599 align:start position:0% it right the first time before 00:06:53.599 --> 00:06:55.909 align:start position:0% it right the first time before deployment<00:06:54.199> that's<00:06:54.400> why<00:06:54.520> we<00:06:54.680> advocate<00:06:55.120> for<00:06:55.680> a 00:06:55.909 --> 00:06:55.919 align:start position:0% deployment that's why we advocate for a 00:06:55.919 --> 00:06:58.110 align:start position:0% deployment that's why we advocate for a very<00:06:56.160> comprehensive<00:06:57.080> security<00:06:57.520> analysis 00:06:58.110 --> 00:06:58.120 align:start position:0% very comprehensive security analysis 00:06:58.120 --> 00:07:00.230 align:start position:0% very comprehensive security analysis that<00:06:58.240> you<00:06:58.400> perform<00:06:58.759> before<00:06:58.960> deployment<00:07:00.000> uh<00:07:00.120> to 00:07:00.230 --> 00:07:00.240 align:start position:0% that you perform before deployment uh to 00:07:00.240 --> 00:07:01.390 align:start position:0% that you perform before deployment uh to make<00:07:00.400> sure<00:07:00.599> that<00:07:00.680> you<00:07:00.800> go<00:07:00.960> through<00:07:01.120> all<00:07:01.280> the 00:07:01.390 --> 00:07:01.400 align:start position:0% make sure that you go through all the 00:07:01.400 --> 00:07:03.150 align:start position:0% make sure that you go through all the stages<00:07:01.919> that<00:07:02.160> the<00:07:02.280> team<00:07:02.680> you<00:07:02.759> know<00:07:02.879> writes 00:07:03.150 --> 00:07:03.160 align:start position:0% stages that the team you know writes 00:07:03.160 --> 00:07:05.390 align:start position:0% stages that the team you know writes proper<00:07:03.440> documentation<00:07:04.199> helps<00:07:04.440> us<00:07:04.639> formulate 00:07:05.390 --> 00:07:05.400 align:start position:0% proper documentation helps us formulate 00:07:05.400 --> 00:07:06.749 align:start position:0% proper documentation helps us formulate the<00:07:05.639> properties<00:07:06.000> and<00:07:06.160> invariance<00:07:06.639> that 00:07:06.749 --> 00:07:06.759 align:start position:0% the properties and invariance that 00:07:06.759 --> 00:07:08.710 align:start position:0% the properties and invariance that should<00:07:06.960> hold<00:07:07.560> that<00:07:07.759> they<00:07:07.919> can<00:07:08.120> that<00:07:08.280> can<00:07:08.440> later 00:07:08.710 --> 00:07:08.720 align:start position:0% should hold that they can that can later 00:07:08.720 --> 00:07:12.749 align:start position:0% should hold that they can that can later be<00:07:09.240> monitored<00:07:10.479> um<00:07:11.479> we<00:07:11.639> advocate<00:07:12.039> for<00:07:12.560> like 00:07:12.749 --> 00:07:12.759 align:start position:0% be monitored um we advocate for like 00:07:12.759 --> 00:07:14.510 align:start position:0% be monitored um we advocate for like formal<00:07:13.120> verification<00:07:13.720> to<00:07:13.919> ensure<00:07:14.280> that<00:07:14.400> there 00:07:14.510 --> 00:07:14.520 align:start position:0% formal verification to ensure that there 00:07:14.520 --> 00:07:16.629 align:start position:0% formal verification to ensure that there are<00:07:14.800> like<00:07:14.919> the<00:07:15.039> bus<00:07:15.240> security<00:07:15.599> guarantees<00:07:16.520> I 00:07:16.629 --> 00:07:16.639 align:start position:0% are like the bus security guarantees I 00:07:16.639 --> 00:07:19.189 align:start position:0% are like the bus security guarantees I guess<00:07:16.800> there<00:07:16.919> are<00:07:17.160> some<00:07:18.160> there<00:07:18.280> is<00:07:18.400> a<00:07:18.599> field 00:07:19.189 --> 00:07:19.199 align:start position:0% guess there are some there is a field 00:07:19.199 --> 00:07:21.110 align:start position:0% guess there are some there is a field that<00:07:19.520> that<00:07:19.639> deals<00:07:20.000> with<00:07:20.240> like<00:07:20.479> some<00:07:20.759> posst 00:07:21.110 --> 00:07:21.120 align:start position:0% that that deals with like some posst 00:07:21.120 --> 00:07:23.350 align:start position:0% that that deals with like some posst Haack<00:07:21.319> things<00:07:21.520> or<00:07:22.000> recoveries<00:07:22.879> um<00:07:23.120> but<00:07:23.240> I 00:07:23.350 --> 00:07:23.360 align:start position:0% Haack things or recoveries um but I 00:07:23.360 --> 00:07:25.309 align:start position:0% Haack things or recoveries um but I guess<00:07:23.599> that's<00:07:24.520> um<00:07:24.879> that's<00:07:25.080> that's<00:07:25.199> a 00:07:25.309 --> 00:07:25.319 align:start position:0% guess that's um that's that's a 00:07:25.319 --> 00:07:26.790 align:start position:0% guess that's um that's that's a different<00:07:25.560> story<00:07:25.840> we<00:07:25.960> just<00:07:26.120> we<00:07:26.240> just<00:07:26.400> suggest 00:07:26.790 --> 00:07:26.800 align:start position:0% different story we just we just suggest 00:07:26.800 --> 00:07:28.469 align:start position:0% different story we just we just suggest that<00:07:26.960> people<00:07:27.120> should<00:07:27.319> get<00:07:27.440> it<00:07:27.639> right<00:07:28.000> and<00:07:28.360> I 00:07:28.469 --> 00:07:28.479 align:start position:0% that people should get it right and I 00:07:28.479 --> 00:07:29.749 align:start position:0% that people should get it right and I think<00:07:29.120> you<00:07:29.199> know<00:07:29.319> I<00:07:29.400> think<00:07:29.520> I<00:07:29.520> think<00:07:29.599> we're 00:07:29.749 --> 00:07:29.759 align:start position:0% think you know I think I think we're 00:07:29.759 --> 00:07:31.550 align:start position:0% think you know I think I think we're getting 00:07:31.550 --> 00:07:31.560 align:start position:0% getting 00:07:31.560 --> 00:07:34.830 align:start position:0% getting better<00:07:32.759> cool<00:07:33.759> is<00:07:33.879> there<00:07:34.080> something<00:07:34.400> like<00:07:34.599> the 00:07:34.830 --> 00:07:34.840 align:start position:0% better cool is there something like the 00:07:34.840 --> 00:07:38.790 align:start position:0% better cool is there something like the oosp<00:07:35.720> Zed<00:07:36.080> attack<00:07:36.720> proxy<00:07:37.720> equivalent<00:07:38.360> in 00:07:38.790 --> 00:07:38.800 align:start position:0% oosp Zed attack proxy equivalent in 00:07:38.800 --> 00:07:41.150 align:start position:0% oosp Zed attack proxy equivalent in smart<00:07:39.160> contracts<00:07:39.840> or<00:07:40.080> blockchain<00:07:40.680> Frameworks 00:07:41.150 --> 00:07:41.160 align:start position:0% smart contracts or blockchain Frameworks 00:07:41.160 --> 00:07:42.070 align:start position:0% smart contracts or blockchain Frameworks that<00:07:41.280> you'd 00:07:42.070 --> 00:07:42.080 align:start position:0% that you'd 00:07:42.080 --> 00:07:44.309 align:start position:0% that you'd recommend<00:07:43.080> s<00:07:43.440> can<00:07:43.560> you<00:07:43.680> please<00:07:43.919> repeat<00:07:44.159> once 00:07:44.309 --> 00:07:44.319 align:start position:0% recommend s can you please repeat once 00:07:44.319 --> 00:07:46.830 align:start position:0% recommend s can you please repeat once again<00:07:44.599> the<00:07:44.840> O<00:07:45.120> the<00:07:45.280> open<00:07:45.680> web<00:07:46.159> application 00:07:46.830 --> 00:07:46.840 align:start position:0% again the O the open web application 00:07:46.840 --> 00:07:49.510 align:start position:0% again the O the open web application standards<00:07:47.400> project<00:07:47.879> The<00:07:48.199> Zed<00:07:48.520> attack<00:07:49.000> proxy 00:07:49.510 --> 00:07:49.520 align:start position:0% standards project The Zed attack proxy 00:07:49.520 --> 00:07:51.629 align:start position:0% standards project The Zed attack proxy that<00:07:49.720> they<00:07:49.879> have<00:07:50.360> we<00:07:50.520> used<00:07:50.680> to<00:07:50.840> use<00:07:51.000> it<00:07:51.159> in<00:07:51.280> our 00:07:51.629 --> 00:07:51.639 align:start position:0% that they have we used to use it in our 00:07:51.639 --> 00:07:55.149 align:start position:0% that they have we used to use it in our CI<00:07:52.039> Tooling<00:07:53.039> in<00:07:54.000> like<00:07:54.280> web<00:07:54.520> 2<00:07:54.840> sort<00:07:55.039> of 00:07:55.149 --> 00:07:55.159 align:start position:0% CI Tooling in like web 2 sort of 00:07:55.159 --> 00:07:58.869 align:start position:0% CI Tooling in like web 2 sort of development<00:07:55.639> to<00:07:56.039> test<00:07:56.360> for<00:07:57.080> the<00:07:57.280> top<00:07:57.479> 10<00:07:57.879> oasp 00:07:58.869 --> 00:07:58.879 align:start position:0% development to test for the top 10 oasp 00:07:58.879 --> 00:08:00.149 align:start position:0% development to test for the top 10 oasp uh<00:07:59.000> security 00:08:00.149 --> 00:08:00.159 align:start position:0% uh security 00:08:00.159 --> 00:08:01.830 align:start position:0% uh security vulnerabilities<00:08:01.159> right<00:08:01.400> yeah<00:08:01.520> I<00:08:01.599> haven't 00:08:01.830 --> 00:08:01.840 align:start position:0% vulnerabilities right yeah I haven't 00:08:01.840 --> 00:08:03.510 align:start position:0% vulnerabilities right yeah I haven't been<00:08:02.000> aware<00:08:02.240> of<00:08:02.400> that<00:08:02.720> but<00:08:02.919> it's<00:08:03.159> it<00:08:03.240> sounds 00:08:03.510 --> 00:08:03.520 align:start position:0% been aware of that but it's it sounds 00:08:03.520 --> 00:08:05.430 align:start position:0% been aware of that but it's it sounds pretty<00:08:03.720> useful<00:08:04.199> I'm<00:08:04.360> all<00:08:04.560> up<00:08:04.720> for<00:08:05.000> using<00:08:05.280> any 00:08:05.430 --> 00:08:05.440 align:start position:0% pretty useful I'm all up for using any 00:08:05.440 --> 00:08:07.270 align:start position:0% pretty useful I'm all up for using any tool<00:08:05.639> in<00:08:05.840> that<00:08:05.960> helps<00:08:06.159> and<00:08:06.319> having<00:08:06.520> it<00:08:06.639> on<00:08:06.759> CI<00:08:07.199> I 00:08:07.270 --> 00:08:07.280 align:start position:0% tool in that helps and having it on CI I 00:08:07.280 --> 00:08:08.550 align:start position:0% tool in that helps and having it on CI I guess<00:08:07.639> anything<00:08:07.960> would<00:08:08.120> help<00:08:08.319> static 00:08:08.550 --> 00:08:08.560 align:start position:0% guess anything would help static 00:08:08.560 --> 00:08:11.309 align:start position:0% guess anything would help static analyzers<00:08:09.080> are<00:08:09.319> great<00:08:10.280> uh<00:08:10.400> as<00:08:10.599> the<00:08:10.759> first<00:08:11.000> step 00:08:11.309 --> 00:08:11.319 align:start position:0% analyzers are great uh as the first step 00:08:11.319 --> 00:08:14.309 align:start position:0% analyzers are great uh as the first step especially<00:08:12.240> um<00:08:12.599> having<00:08:12.919> unit<00:08:13.280> tests<00:08:13.960> is<00:08:14.080> also 00:08:14.309 --> 00:08:14.319 align:start position:0% especially um having unit tests is also 00:08:14.319 --> 00:08:16.350 align:start position:0% especially um having unit tests is also extremely<00:08:14.680> helpful<00:08:15.000> and<00:08:15.120> very<00:08:15.280> efficient<00:08:16.199> um 00:08:16.350 --> 00:08:16.360 align:start position:0% extremely helpful and very efficient um 00:08:16.360 --> 00:08:17.430 align:start position:0% extremely helpful and very efficient um fing<00:08:16.680> can<00:08:16.759> uncover<00:08:17.080> a<00:08:17.120> lot<00:08:17.199> of 00:08:17.430 --> 00:08:17.440 align:start position:0% fing can uncover a lot of 00:08:17.440 --> 00:08:19.589 align:start position:0% fing can uncover a lot of vulnerabilities<00:08:18.440> so<00:08:18.960> uh<00:08:19.120> yeah<00:08:19.240> thanks<00:08:19.440> for 00:08:19.589 --> 00:08:19.599 align:start position:0% vulnerabilities so uh yeah thanks for 00:08:19.599 --> 00:08:21.510 align:start position:0% vulnerabilities so uh yeah thanks for letting<00:08:19.800> me<00:08:19.919> know<00:08:20.039> about 00:08:21.510 --> 00:08:21.520 align:start position:0% letting me know about 00:08:21.520 --> 00:08:25.749 align:start position:0% letting me know about that<00:08:22.520> okay<00:08:22.759> one<00:08:22.960> more 00:08:25.749 --> 00:08:25.759 align:start position:0% 00:08:25.759 --> 00:08:28.550 align:start position:0% question<00:08:26.759> thanks<00:08:27.319> um<00:08:27.440> you<00:08:27.560> mentioned<00:08:28.199> like<00:08:28.319> a 00:08:28.550 --> 00:08:28.560 align:start position:0% question thanks um you mentioned like a 00:08:28.560 --> 00:08:30.230 align:start position:0% question thanks um you mentioned like a design<00:08:28.919> review<00:08:29.240> as<00:08:29.319> a<00:08:29.560> precursor<00:08:30.000> to<00:08:30.120> the 00:08:30.230 --> 00:08:30.240 align:start position:0% design review as a precursor to the 00:08:30.240 --> 00:08:33.790 align:start position:0% design review as a precursor to the actual<00:08:30.520> code<00:08:30.879> review<00:08:31.879> is<00:08:32.080> your<00:08:32.919> like<00:08:33.200> hope<00:08:33.560> or 00:08:33.790 --> 00:08:33.800 align:start position:0% actual code review is your like hope or 00:08:33.800 --> 00:08:35.389 align:start position:0% actual code review is your like hope or expectation<00:08:34.320> from<00:08:34.440> an<00:08:34.599> audit<00:08:34.880> point<00:08:35.039> of<00:08:35.159> view 00:08:35.389 --> 00:08:35.399 align:start position:0% expectation from an audit point of view 00:08:35.399 --> 00:08:37.670 align:start position:0% expectation from an audit point of view that<00:08:35.800> a<00:08:35.919> team<00:08:36.200> comes<00:08:36.399> to<00:08:36.560> you<00:08:36.839> with<00:08:37.000> the<00:08:37.200> design 00:08:37.670 --> 00:08:37.680 align:start position:0% that a team comes to you with the design 00:08:37.680 --> 00:08:39.269 align:start position:0% that a team comes to you with the design before<00:08:37.880> they<00:08:38.039> even<00:08:38.240> write<00:08:38.519> the<00:08:38.640> code<00:08:39.000> or<00:08:39.120> were 00:08:39.269 --> 00:08:39.279 align:start position:0% before they even write the code or were 00:08:39.279 --> 00:08:41.149 align:start position:0% before they even write the code or were you<00:08:39.399> just<00:08:39.519> talking<00:08:39.800> about<00:08:40.080> that<00:08:40.360> as<00:08:40.959> a 00:08:41.149 --> 00:08:41.159 align:start position:0% you just talking about that as a 00:08:41.159 --> 00:08:43.870 align:start position:0% you just talking about that as a separate<00:08:41.640> a<00:08:41.800> specific<00:08:42.200> phase<00:08:42.479> of<00:08:42.640> the<00:08:42.880> audit 00:08:43.870 --> 00:08:43.880 align:start position:0% separate a specific phase of the audit 00:08:43.880 --> 00:08:45.790 align:start position:0% separate a specific phase of the audit that<00:08:44.159> is<00:08:44.440> perfect<00:08:44.880> but<00:08:45.040> that<00:08:45.160> almost<00:08:45.519> never 00:08:45.790 --> 00:08:45.800 align:start position:0% that is perfect but that almost never 00:08:45.800 --> 00:08:49.630 align:start position:0% that is perfect but that almost never happens<00:08:46.600> so<00:08:46.959> the<00:08:47.160> sooner<00:08:47.680> we<00:08:48.200> introduce 00:08:49.630 --> 00:08:49.640 align:start position:0% happens so the sooner we introduce 00:08:49.640 --> 00:08:52.710 align:start position:0% happens so the sooner we introduce security<00:08:50.640> and<00:08:50.920> you<00:08:51.040> know<00:08:51.279> some<00:08:51.600> testing<00:08:52.560> any 00:08:52.710 --> 00:08:52.720 align:start position:0% security and you know some testing any 00:08:52.720 --> 00:08:54.870 align:start position:0% security and you know some testing any of<00:08:52.959> that<00:08:53.360> uh<00:08:53.560> into<00:08:53.920> the<00:08:54.399> process<00:08:54.680> of 00:08:54.870 --> 00:08:54.880 align:start position:0% of that uh into the process of 00:08:54.880 --> 00:08:56.670 align:start position:0% of that uh into the process of development<00:08:55.440> the<00:08:55.560> easier<00:08:55.880> it<00:08:56.000> becomes<00:08:56.279> for 00:08:56.670 --> 00:08:56.680 align:start position:0% development the easier it becomes for 00:08:56.680 --> 00:08:58.710 align:start position:0% development the easier it becomes for everyone<00:08:57.680> uh<00:08:57.839> that's<00:08:58.040> something<00:08:58.360> that<00:08:58.480> we 00:08:58.710 --> 00:08:58.720 align:start position:0% everyone uh that's something that we 00:08:58.720 --> 00:09:00.550 align:start position:0% everyone uh that's something that we have<00:08:58.880> found<00:08:59.079> out<00:08:59.440> ourselves<00:09:00.200> uh<00:09:00.320> but<00:09:00.440> it 00:09:00.550 --> 00:09:00.560 align:start position:0% have found out ourselves uh but it 00:09:00.560 --> 00:09:03.790 align:start position:0% have found out ourselves uh but it almost<00:09:00.800> never<00:09:01.040> happens<00:09:01.680> so<00:09:02.680> we<00:09:03.320> at<00:09:03.440> least<00:09:03.600> try 00:09:03.790 --> 00:09:03.800 align:start position:0% almost never happens so we at least try 00:09:03.800 --> 00:09:05.590 align:start position:0% almost never happens so we at least try to<00:09:03.959> allocate<00:09:04.440> some<00:09:04.640> time<00:09:04.760> for<00:09:04.959> design<00:09:05.279> review 00:09:05.590 --> 00:09:05.600 align:start position:0% to allocate some time for design review 00:09:05.600 --> 00:09:07.069 align:start position:0% to allocate some time for design review first<00:09:05.839> before<00:09:06.040> we<00:09:06.200> dive<00:09:06.480> into<00:09:06.680> the<00:09:06.800> code 00:09:07.069 --> 00:09:07.079 align:start position:0% first before we dive into the code 00:09:07.079 --> 00:09:08.710 align:start position:0% first before we dive into the code itself<00:09:07.680> to<00:09:07.800> make<00:09:07.920> sure<00:09:08.120> that<00:09:08.240> we<00:09:08.360> also 00:09:08.710 --> 00:09:08.720 align:start position:0% itself to make sure that we also 00:09:08.720 --> 00:09:10.750 align:start position:0% itself to make sure that we also understand<00:09:08.880> what<00:09:08.959> it's<00:09:09.120> supposed<00:09:09.399> to<00:09:09.519> do<00:09:10.440> um 00:09:10.750 --> 00:09:10.760 align:start position:0% understand what it's supposed to do um 00:09:10.760 --> 00:09:14.030 align:start position:0% understand what it's supposed to do um but<00:09:11.160> I<00:09:11.240> mean<00:09:11.720> having<00:09:12.560> the<00:09:12.760> team<00:09:13.519> providing<00:09:13.880> us 00:09:14.030 --> 00:09:14.040 align:start position:0% but I mean having the team providing us 00:09:14.040 --> 00:09:15.790 align:start position:0% but I mean having the team providing us the<00:09:14.160> design<00:09:14.440> first<00:09:14.800> is<00:09:14.959> ideal<00:09:15.399> and<00:09:15.519> we<00:09:15.680> can 00:09:15.790 --> 00:09:15.800 align:start position:0% the design first is ideal and we can 00:09:15.800 --> 00:09:17.630 align:start position:0% the design first is ideal and we can also<00:09:16.120> like<00:09:16.240> help<00:09:16.480> us<00:09:16.920> help<00:09:17.120> out<00:09:17.320> with<00:09:17.480> the 00:09:17.630 --> 00:09:17.640 align:start position:0% also like help us help out with the 00:09:17.640 --> 00:09:19.550 align:start position:0% also like help us help out with the stages<00:09:18.399> uh<00:09:18.560> but<00:09:18.680> it's<00:09:18.800> pretty<00:09:19.079> rare<00:09:19.360> because 00:09:19.550 --> 00:09:19.560 align:start position:0% stages uh but it's pretty rare because 00:09:19.560 --> 00:09:21.470 align:start position:0% stages uh but it's pretty rare because of<00:09:19.680> the<00:09:19.880> resource<00:09:20.200> constraints<00:09:20.600> I<00:09:20.720> guess 00:09:21.470 --> 00:09:21.480 align:start position:0% of the resource constraints I guess 00:09:21.480 --> 00:09:25.550 align:start position:0% of the resource constraints I guess great 00:09:25.550 --> 00:09:25.560 align:start position:0% 00:09:25.560 --> 00:09:28.630 align:start position:0% thanks<00:09:26.560> okay<00:09:26.959> we<00:09:27.160> can<00:09:27.600> take<00:09:27.959> one<00:09:28.200> more 00:09:28.630 --> 00:09:28.640 align:start position:0% thanks okay we can take one more 00:09:28.640 --> 00:09:30.150 align:start position:0% thanks okay we can take one more question 00:09:30.150 --> 00:09:30.160 align:start position:0% question 00:09:30.160 --> 00:09:31.710 align:start position:0% question if<00:09:30.360> there<00:09:30.480> is 00:09:31.710 --> 00:09:31.720 align:start position:0% if there is 00:09:31.720 --> 00:09:36.550 align:start position:0% if there is any<00:09:32.720> oh<00:09:32.880> there's<00:09:33.079> one 00:09:36.550 --> 00:09:36.560 align:start position:0% 00:09:36.560 --> 00:09:40.710 align:start position:0% there<00:09:37.560> thank<00:09:37.959> you<00:09:38.959> uh<00:09:39.240> I<00:09:39.320> would<00:09:39.480> like<00:09:39.720> to<00:09:40.000> know 00:09:40.710 --> 00:09:40.720 align:start position:0% there thank you uh I would like to know 00:09:40.720 --> 00:09:43.670 align:start position:0% there thank you uh I would like to know if<00:09:41.600> uh<00:09:42.600> if<00:09:43.000> there 00:09:43.670 --> 00:09:43.680 align:start position:0% if uh if there 00:09:43.680 --> 00:09:47.829 align:start position:0% if uh if there are<00:09:44.680> some<00:09:45.079> security<00:09:45.839> best<00:09:46.480> practices<00:09:47.480> for 00:09:47.829 --> 00:09:47.839 align:start position:0% are some security best practices for 00:09:47.839 --> 00:09:51.670 align:start position:0% are some security best practices for smart<00:09:48.240> contract<00:09:48.800> based<00:09:49.200> on<00:09:49.959> artificial 00:09:51.670 --> 00:09:51.680 align:start position:0% smart contract based on artificial 00:09:51.680 --> 00:09:53.670 align:start position:0% smart contract based on artificial intelligence<00:09:52.680> thank 00:09:53.670 --> 00:09:53.680 align:start position:0% intelligence thank 00:09:53.680 --> 00:09:56.389 align:start position:0% intelligence thank you<00:09:54.680> based<00:09:54.920> on<00:09:55.279> artificial<00:09:55.800> intelligence 00:09:56.389 --> 00:09:56.399 align:start position:0% you based on artificial intelligence 00:09:56.399 --> 00:10:00.150 align:start position:0% you based on artificial intelligence right<00:09:57.000> yes<00:09:57.880> right<00:09:58.240> um<00:09:58.560> I<00:09:58.839> am<00:09:59.440> aware<00:09:59.720> of<00:09:59.839> a<00:09:59.959> few 00:10:00.150 --> 00:10:00.160 align:start position:0% right yes right um I am aware of a few 00:10:00.160 --> 00:10:02.470 align:start position:0% right yes right um I am aware of a few tools<00:10:00.519> that<00:10:00.680> do<00:10:00.880> it<00:10:01.480> um<00:10:01.640> I<00:10:01.720> think<00:10:01.839> you<00:10:01.959> can<00:10:02.120> also 00:10:02.470 --> 00:10:02.480 align:start position:0% tools that do it um I think you can also 00:10:02.480 --> 00:10:05.150 align:start position:0% tools that do it um I think you can also Ask<00:10:02.880> Jud<00:10:03.440> to<00:10:03.560> generate<00:10:03.920> you<00:10:04.320> some<00:10:04.600> security 00:10:05.150 --> 00:10:05.160 align:start position:0% Ask Jud to generate you some security 00:10:05.160 --> 00:10:07.190 align:start position:0% Ask Jud to generate you some security practices<00:10:06.160> uh<00:10:06.279> and<00:10:06.360> it<00:10:06.480> will<00:10:06.640> be<00:10:06.800> pretty 00:10:07.190 --> 00:10:07.200 align:start position:0% practices uh and it will be pretty 00:10:07.200 --> 00:10:08.590 align:start position:0% practices uh and it will be pretty helpful<00:10:07.640> when<00:10:07.760> it<00:10:07.880> comes<00:10:08.040> to<00:10:08.200> like<00:10:08.320> common 00:10:08.590 --> 00:10:08.600 align:start position:0% helpful when it comes to like common 00:10:08.600 --> 00:10:10.269 align:start position:0% helpful when it comes to like common vulnerabilities<00:10:09.360> I<00:10:09.440> guess<00:10:09.600> the<00:10:09.800> current 00:10:10.269 --> 00:10:10.279 align:start position:0% vulnerabilities I guess the current 00:10:10.279 --> 00:10:12.110 align:start position:0% vulnerabilities I guess the current common<00:10:10.680> problem<00:10:11.000> with<00:10:11.160> all<00:10:11.320> this<00:10:11.480> AA<00:10:11.839> based 00:10:12.110 --> 00:10:12.120 align:start position:0% common problem with all this AA based 00:10:12.120 --> 00:10:14.350 align:start position:0% common problem with all this AA based tooling<00:10:12.640> is<00:10:12.839> that<00:10:13.480> it<00:10:13.640> it<00:10:13.720> is<00:10:13.839> good<00:10:13.959> at<00:10:14.079> pattern 00:10:14.350 --> 00:10:14.360 align:start position:0% tooling is that it it is good at pattern 00:10:14.360 --> 00:10:15.990 align:start position:0% tooling is that it it is good at pattern matching<00:10:14.800> right<00:10:14.959> so<00:10:15.079> it<00:10:15.200> can<00:10:15.360> definitely<00:10:15.800> help 00:10:15.990 --> 00:10:16.000 align:start position:0% matching right so it can definitely help 00:10:16.000 --> 00:10:17.670 align:start position:0% matching right so it can definitely help you<00:10:16.200> find<00:10:16.480> some<00:10:16.800> common<00:10:17.120> issues<00:10:17.440> that<00:10:17.560> are 00:10:17.670 --> 00:10:17.680 align:start position:0% you find some common issues that are 00:10:17.680 --> 00:10:19.269 align:start position:0% you find some common issues that are known<00:10:17.880> for<00:10:18.000> a<00:10:18.120> long<00:10:18.360> time<00:10:18.600> but<00:10:18.720> it<00:10:18.959> probably 00:10:19.269 --> 00:10:19.279 align:start position:0% known for a long time but it probably 00:10:19.279 --> 00:10:20.870 align:start position:0% known for a long time but it probably has<00:10:19.440> bigger<00:10:19.760> issues<00:10:20.120> with<00:10:20.360> like<00:10:20.519> business 00:10:20.870 --> 00:10:20.880 align:start position:0% has bigger issues with like business 00:10:20.880 --> 00:10:24.350 align:start position:0% has bigger issues with like business logic<00:10:21.240> or<00:10:21.480> design<00:10:21.760> review<00:10:22.200> Parts<00:10:23.200> um<00:10:24.040> so<00:10:24.240> I 00:10:24.350 --> 00:10:24.360 align:start position:0% logic or design review Parts um so I 00:10:24.360 --> 00:10:25.710 align:start position:0% logic or design review Parts um so I guess<00:10:24.519> it's<00:10:24.720> it's<00:10:24.839> pretty<00:10:25.079> helpful<00:10:25.440> at<00:10:25.519> least 00:10:25.710 --> 00:10:25.720 align:start position:0% guess it's it's pretty helpful at least 00:10:25.720 --> 00:10:27.870 align:start position:0% guess it's it's pretty helpful at least when<00:10:25.800> it<00:10:25.920> comes<00:10:26.120> to<00:10:26.600> the<00:10:26.760> the<00:10:26.880> first 00:10:27.870 --> 00:10:27.880 align:start position:0% when it comes to the the first 00:10:27.880 --> 00:10:31.670 align:start position:0% when it comes to the the first part<00:10:28.880> thank<00:10:29.040> you 00:10:31.670 --> 00:10:31.680 align:start position:0% 00:10:31.680 --> 00:10:34.470 align:start position:0% okay<00:10:32.320> that's<00:10:33.000> everything<00:10:33.560> thank<00:10:33.760> you<00:10:33.959> Pina 00:10:34.470 --> 00:10:34.480 align:start position:0% okay that's everything thank you Pina 00:10:34.480 --> 00:10:36.320 align:start position:0% okay that's everything thank you Pina let's<00:10:34.720> give<00:10:34.880> it<00:10:35.000> up<00:10:35.160> to<00:10:35.320> Pina 00:10:36.320 --> 00:10:36.330 align:start position:0% let's give it up to Pina 00:10:36.330 --> 00:10:39.779 align:start position:0% let's give it up to Pina [Applause]