WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:12.190 align:start position:0% [Music] 00:00:12.190 --> 00:00:12.200 align:start position:0% 00:00:12.200 --> 00:00:15.410 align:start position:0% I<00:00:13.200> work<00:00:13.500> at<00:00:13.679> optimism<00:00:14.099> I<00:00:14.519> focus<00:00:14.759> on<00:00:14.940> security 00:00:15.410 --> 00:00:15.420 align:start position:0% I work at optimism I focus on security 00:00:15.420 --> 00:00:18.830 align:start position:0% I work at optimism I focus on security in<00:00:16.260> our<00:00:16.440> protocol<00:00:16.800> I<00:00:17.699> previously<00:00:18.240> was<00:00:18.720> an 00:00:18.830 --> 00:00:18.840 align:start position:0% in our protocol I previously was an 00:00:18.840 --> 00:00:20.810 align:start position:0% in our protocol I previously was an auditor<00:00:19.260> and<00:00:19.560> co-founded<00:00:20.220> diligence<00:00:20.640> with 00:00:20.810 --> 00:00:20.820 align:start position:0% auditor and co-founded diligence with 00:00:20.820 --> 00:00:24.470 align:start position:0% auditor and co-founded diligence with Gonzalo<00:00:21.560> and<00:00:22.560> have<00:00:22.859> had<00:00:23.400> the<00:00:23.640> Good<00:00:23.820> Fortune<00:00:24.300> of 00:00:24.470 --> 00:00:24.480 align:start position:0% Gonzalo and have had the Good Fortune of 00:00:24.480 --> 00:00:27.230 align:start position:0% Gonzalo and have had the Good Fortune of working<00:00:24.960> as<00:00:25.500> a<00:00:25.740> client<00:00:25.980> with<00:00:26.580> these<00:00:27.119> three 00:00:27.230 --> 00:00:27.240 align:start position:0% working as a client with these three 00:00:27.240 --> 00:00:30.109 align:start position:0% working as a client with these three gentlemen<00:00:27.599> and<00:00:28.560> not<00:00:28.800> yet<00:00:28.920> sir<00:00:29.099> Torah<00:00:29.580> but<00:00:29.760> have 00:00:30.109 --> 00:00:30.119 align:start position:0% gentlemen and not yet sir Torah but have 00:00:30.119 --> 00:00:31.790 align:start position:0% gentlemen and not yet sir Torah but have had<00:00:30.420> an<00:00:30.539> opportunity<00:00:30.840> to<00:00:31.019> get<00:00:31.260> to<00:00:31.500> know<00:00:31.619> them 00:00:31.790 --> 00:00:31.800 align:start position:0% had an opportunity to get to know them 00:00:31.800 --> 00:00:34.190 align:start position:0% had an opportunity to get to know them really<00:00:32.040> well<00:00:32.420> so<00:00:33.420> I<00:00:33.540> really<00:00:33.660> feel<00:00:33.899> in<00:00:34.079> my 00:00:34.190 --> 00:00:34.200 align:start position:0% really well so I really feel in my 00:00:34.200 --> 00:00:36.470 align:start position:0% really well so I really feel in my element<00:00:34.380> and<00:00:35.340> I'm<00:00:35.579> excited<00:00:35.940> to<00:00:36.120> have<00:00:36.239> this 00:00:36.470 --> 00:00:36.480 align:start position:0% element and I'm excited to have this 00:00:36.480 --> 00:00:39.770 align:start position:0% element and I'm excited to have this conversation<00:00:37.219> so<00:00:38.219> I'll<00:00:39.000> let<00:00:39.239> them<00:00:39.360> introduce 00:00:39.770 --> 00:00:39.780 align:start position:0% conversation so I'll let them introduce 00:00:39.780 --> 00:00:42.290 align:start position:0% conversation so I'll let them introduce themselves<00:00:40.260> quickly<00:00:41.100> if<00:00:41.280> you<00:00:41.399> could<00:00:41.520> you<00:00:41.820> know 00:00:42.290 --> 00:00:42.300 align:start position:0% themselves quickly if you could you know 00:00:42.300 --> 00:00:44.330 align:start position:0% themselves quickly if you could you know give<00:00:42.899> us<00:00:43.020> your<00:00:43.200> names<00:00:43.440> and<00:00:43.860> tell<00:00:44.040> us<00:00:44.160> about 00:00:44.330 --> 00:00:44.340 align:start position:0% give us your names and tell us about 00:00:44.340 --> 00:00:47.750 align:start position:0% give us your names and tell us about your<00:00:44.579> firms<00:00:45.000> and<00:00:45.780> what<00:00:46.260> makes<00:00:46.440> you<00:00:46.620> special<00:00:46.860> I 00:00:47.750 --> 00:00:47.760 align:start position:0% your firms and what makes you special I 00:00:47.760 --> 00:00:50.090 align:start position:0% your firms and what makes you special I can<00:00:47.879> go<00:00:48.059> first<00:00:48.239> hey<00:00:48.719> guys 00:00:50.090 --> 00:00:50.100 align:start position:0% can go first hey guys 00:00:50.100 --> 00:00:52.069 align:start position:0% can go first hey guys um<00:00:50.160> and<00:00:50.399> thank<00:00:50.640> you<00:00:50.760> Richie<00:00:51.239> yeah<00:00:51.600> if<00:00:51.899> you're 00:00:52.069 --> 00:00:52.079 align:start position:0% um and thank you Richie yeah if you're 00:00:52.079 --> 00:00:53.389 align:start position:0% um and thank you Richie yeah if you're watching 00:00:53.389 --> 00:00:53.399 align:start position:0% watching 00:00:53.399 --> 00:00:56.869 align:start position:0% watching um<00:00:53.520> yeah<00:00:54.440> we<00:00:55.440> co-founded<00:00:56.280> consensus 00:00:56.869 --> 00:00:56.879 align:start position:0% um yeah we co-founded consensus 00:00:56.879 --> 00:01:00.650 align:start position:0% um yeah we co-founded consensus diligence<00:00:57.620> almost<00:00:58.620> six<00:00:59.520> years<00:00:59.760> ago<00:01:00.120> now<00:01:00.300> or 00:01:00.650 --> 00:01:00.660 align:start position:0% diligence almost six years ago now or 00:01:00.660 --> 00:01:02.330 align:start position:0% diligence almost six years ago now or going<00:01:01.140> to<00:01:01.379> that 00:01:02.330 --> 00:01:02.340 align:start position:0% going to that 00:01:02.340 --> 00:01:04.910 align:start position:0% going to that um me<00:01:02.940> and<00:01:03.120> John<00:01:03.359> who's<00:01:04.080> now<00:01:04.320> at<00:01:04.440> optimism 00:01:04.910 --> 00:01:04.920 align:start position:0% um me and John who's now at optimism 00:01:04.920 --> 00:01:07.789 align:start position:0% um me and John who's now at optimism unfortunately<00:01:05.880> and<00:01:06.840> the<00:01:07.140> consensus 00:01:07.789 --> 00:01:07.799 align:start position:0% unfortunately and the consensus 00:01:07.799 --> 00:01:10.130 align:start position:0% unfortunately and the consensus diligence<00:01:08.280> is<00:01:08.520> a<00:01:08.820> crypto<00:01:09.659> native<00:01:09.900> security 00:01:10.130 --> 00:01:10.140 align:start position:0% diligence is a crypto native security 00:01:10.140 --> 00:01:13.789 align:start position:0% diligence is a crypto native security firm<00:01:10.740> that<00:01:11.159> has<00:01:11.640> for<00:01:12.600> the<00:01:12.900> entirety<00:01:13.320> of<00:01:13.500> its 00:01:13.789 --> 00:01:13.799 align:start position:0% firm that has for the entirety of its 00:01:13.799 --> 00:01:15.969 align:start position:0% firm that has for the entirety of its life<00:01:13.920> done<00:01:14.340> Security<00:01:14.700> Services 00:01:15.969 --> 00:01:15.979 align:start position:0% life done Security Services 00:01:15.979 --> 00:01:19.969 align:start position:0% life done Security Services and<00:01:16.979> has<00:01:17.460> also<00:01:17.880> a<00:01:18.180> product<00:01:18.360> side<00:01:18.840> which<00:01:19.740> you 00:01:19.969 --> 00:01:19.979 align:start position:0% and has also a product side which you 00:01:19.979 --> 00:01:23.270 align:start position:0% and has also a product side which you might<00:01:20.220> have<00:01:20.400> seen<00:01:20.900> so<00:01:21.900> mythex<00:01:22.560> and<00:01:23.040> more 00:01:23.270 --> 00:01:23.280 align:start position:0% might have seen so mythex and more 00:01:23.280 --> 00:01:25.609 align:start position:0% might have seen so mythex and more recently<00:01:23.700> diligence<00:01:24.299> fuzzing<00:01:24.840> and<00:01:25.259> a<00:01:25.380> bunch 00:01:25.609 --> 00:01:25.619 align:start position:0% recently diligence fuzzing and a bunch 00:01:25.619 --> 00:01:28.670 align:start position:0% recently diligence fuzzing and a bunch of<00:01:25.860> other<00:01:26.340> smaller<00:01:27.180> tools<00:01:27.659> that<00:01:27.960> are<00:01:28.200> all<00:01:28.500> open 00:01:28.670 --> 00:01:28.680 align:start position:0% of other smaller tools that are all open 00:01:28.680 --> 00:01:30.170 align:start position:0% of other smaller tools that are all open source<00:01:29.040> that<00:01:29.159> you<00:01:29.340> can<00:01:29.400> check<00:01:29.520> on<00:01:29.700> our<00:01:29.820> website 00:01:30.170 --> 00:01:30.180 align:start position:0% source that you can check on our website 00:01:30.180 --> 00:01:33.830 align:start position:0% source that you can check on our website hi<00:01:30.540> everyone<00:01:30.960> my<00:01:31.680> name<00:01:31.799> is<00:01:31.860> Chandra<00:01:32.400> and<00:01:33.240> I<00:01:33.659> am 00:01:33.830 --> 00:01:33.840 align:start position:0% hi everyone my name is Chandra and I am 00:01:33.840 --> 00:01:37.069 align:start position:0% hi everyone my name is Chandra and I am from<00:01:33.960> sartora<00:01:34.880> sartora<00:01:35.880> is<00:01:36.119> a<00:01:36.659> automated 00:01:37.069 --> 00:01:37.079 align:start position:0% from sartora sartora is a automated 00:01:37.079 --> 00:01:38.990 align:start position:0% from sartora sartora is a automated auditing<00:01:37.740> company<00:01:37.920> you<00:01:38.340> can<00:01:38.400> think<00:01:38.579> of<00:01:38.700> it<00:01:38.820> as 00:01:38.990 --> 00:01:39.000 align:start position:0% auditing company you can think of it as 00:01:39.000 --> 00:01:42.830 align:start position:0% auditing company you can think of it as that<00:01:39.240> way<00:01:39.360> what<00:01:40.320> we<00:01:40.500> do<00:01:40.680> is<00:01:41.100> we<00:01:41.820> use<00:01:42.420> formal 00:01:42.830 --> 00:01:42.840 align:start position:0% that way what we do is we use formal 00:01:42.840 --> 00:01:45.649 align:start position:0% that way what we do is we use formal verification<00:01:43.320> techniques<00:01:43.860> to<00:01:44.700> prove<00:01:45.360> certain 00:01:45.649 --> 00:01:45.659 align:start position:0% verification techniques to prove certain 00:01:45.659 --> 00:01:47.690 align:start position:0% verification techniques to prove certain properties<00:01:46.079> about<00:01:46.439> your<00:01:46.860> smart<00:01:47.100> contracts 00:01:47.690 --> 00:01:47.700 align:start position:0% properties about your smart contracts 00:01:47.700 --> 00:01:50.350 align:start position:0% properties about your smart contracts and<00:01:48.420> I'm<00:01:48.600> personally<00:01:49.020> more<00:01:49.259> on<00:01:49.439> the<00:01:49.619> r<00:01:49.799> d<00:01:49.979> side 00:01:50.350 --> 00:01:50.360 align:start position:0% and I'm personally more on the r d side 00:01:50.360 --> 00:01:52.850 align:start position:0% and I'm personally more on the r d side and<00:01:51.360> one<00:01:51.960> of<00:01:52.079> the<00:01:52.140> things<00:01:52.259> that<00:01:52.560> we<00:01:52.680> are 00:01:52.850 --> 00:01:52.860 align:start position:0% and one of the things that we are 00:01:52.860 --> 00:01:55.910 align:start position:0% and one of the things that we are focusing<00:01:53.280> on<00:01:53.399> these<00:01:53.759> days<00:01:53.899> is<00:01:54.899> how<00:01:55.560> do<00:01:55.740> you 00:01:55.910 --> 00:01:55.920 align:start position:0% focusing on these days is how do you 00:01:55.920 --> 00:01:58.130 align:start position:0% focusing on these days is how do you have<00:01:56.220> more<00:01:56.640> Trust<00:01:57.119> on<00:01:57.420> the<00:01:57.600> specifications 00:01:58.130 --> 00:01:58.140 align:start position:0% have more Trust on the specifications 00:01:58.140 --> 00:02:00.350 align:start position:0% have more Trust on the specifications that<00:01:58.799> you<00:01:58.979> write<00:01:59.159> because<00:01:59.700> at<00:01:59.939> the<00:02:00.060> end<00:02:00.180> of<00:02:00.240> the 00:02:00.350 --> 00:02:00.360 align:start position:0% that you write because at the end of the 00:02:00.360 --> 00:02:02.870 align:start position:0% that you write because at the end of the day<00:02:00.479> that's<00:02:01.020> really<00:02:01.259> what<00:02:01.680> we're<00:02:02.399> using<00:02:02.700> as 00:02:02.870 --> 00:02:02.880 align:start position:0% day that's really what we're using as 00:02:02.880 --> 00:02:04.850 align:start position:0% day that's really what we're using as the<00:02:03.000> ground<00:02:03.180> Truth<00:02:03.540> for<00:02:03.960> verifying<00:02:04.740> your 00:02:04.850 --> 00:02:04.860 align:start position:0% the ground Truth for verifying your 00:02:04.860 --> 00:02:06.770 align:start position:0% the ground Truth for verifying your smart<00:02:05.159> contracts<00:02:05.759> so<00:02:06.299> if<00:02:06.420> you<00:02:06.540> have<00:02:06.600> any 00:02:06.770 --> 00:02:06.780 align:start position:0% smart contracts so if you have any 00:02:06.780 --> 00:02:08.150 align:start position:0% smart contracts so if you have any questions<00:02:06.960> about<00:02:07.200> formal<00:02:07.560> verification<00:02:07.920> I 00:02:08.150 --> 00:02:08.160 align:start position:0% questions about formal verification I 00:02:08.160 --> 00:02:09.410 align:start position:0% questions about formal verification I would<00:02:08.280> love<00:02:08.399> to<00:02:08.459> hear<00:02:08.580> about<00:02:08.759> those<00:02:09.000> everyone 00:02:09.410 --> 00:02:09.420 align:start position:0% would love to hear about those everyone 00:02:09.420 --> 00:02:11.390 align:start position:0% would love to hear about those everyone my<00:02:10.080> name<00:02:10.200> is<00:02:10.259> Maddie<00:02:10.679> co-founder<00:02:11.220> and 00:02:11.390 --> 00:02:11.400 align:start position:0% my name is Maddie co-founder and 00:02:11.400 --> 00:02:13.309 align:start position:0% my name is Maddie co-founder and director<00:02:11.580> of<00:02:11.760> Sigma<00:02:12.060> Prime<00:02:12.239> we're<00:02:13.140> in 00:02:13.309 --> 00:02:13.319 align:start position:0% director of Sigma Prime we're in 00:02:13.319 --> 00:02:15.410 align:start position:0% director of Sigma Prime we're in information<00:02:13.500> security<00:02:13.860> consultancy<00:02:14.640> focused 00:02:15.410 --> 00:02:15.420 align:start position:0% information security consultancy focused 00:02:15.420 --> 00:02:17.570 align:start position:0% information security consultancy focused on<00:02:15.480> blockchain<00:02:15.900> technology<00:02:16.319> doing<00:02:17.220> a<00:02:17.400> lot<00:02:17.459> of 00:02:17.570 --> 00:02:17.580 align:start position:0% on blockchain technology doing a lot of 00:02:17.580 --> 00:02:18.830 align:start position:0% on blockchain technology doing a lot of smart<00:02:17.700> contract<00:02:18.060> auditing<00:02:18.480> as<00:02:18.599> you<00:02:18.720> can 00:02:18.830 --> 00:02:18.840 align:start position:0% smart contract auditing as you can 00:02:18.840 --> 00:02:20.930 align:start position:0% smart contract auditing as you can imagine<00:02:18.959> but<00:02:19.860> very<00:02:20.099> comfortable<00:02:20.459> diving 00:02:20.930 --> 00:02:20.940 align:start position:0% imagine but very comfortable diving 00:02:20.940 --> 00:02:23.869 align:start position:0% imagine but very comfortable diving deeper<00:02:21.300> into<00:02:21.480> other<00:02:21.900> layers<00:02:22.260> of<00:02:22.379> the<00:02:22.560> stack<00:02:22.879> as 00:02:23.869 --> 00:02:23.879 align:start position:0% deeper into other layers of the stack as 00:02:23.879 --> 00:02:28.130 align:start position:0% deeper into other layers of the stack as John<00:02:24.180> mentioned<00:02:24.660> layer<00:02:25.500> 2<00:02:25.739> systems<00:02:26.300> new<00:02:27.300> l1s 00:02:28.130 --> 00:02:28.140 align:start position:0% John mentioned layer 2 systems new l1s 00:02:28.140 --> 00:02:30.589 align:start position:0% John mentioned layer 2 systems new l1s and<00:02:28.440> whatnot<00:02:28.739> we're<00:02:29.700> also<00:02:29.940> the<00:02:30.120> founders<00:02:30.420> and 00:02:30.589 --> 00:02:30.599 align:start position:0% and whatnot we're also the founders and 00:02:30.599 --> 00:02:32.750 align:start position:0% and whatnot we're also the founders and maintain<00:02:30.900> owners<00:02:31.440> of<00:02:31.620> Lighthouse<00:02:31.920> the<00:02:32.580> rust 00:02:32.750 --> 00:02:32.760 align:start position:0% maintain owners of Lighthouse the rust 00:02:32.760 --> 00:02:35.270 align:start position:0% maintain owners of Lighthouse the rust implementation<00:02:33.360> of<00:02:33.599> the<00:02:33.959> ethereum<00:02:34.680> consensus 00:02:35.270 --> 00:02:35.280 align:start position:0% implementation of the ethereum consensus 00:02:35.280 --> 00:02:37.910 align:start position:0% implementation of the ethereum consensus protocol<00:02:35.760> some<00:02:36.480> of<00:02:36.660> you<00:02:36.900> here<00:02:37.379> I'm<00:02:37.620> sure<00:02:37.800> are 00:02:37.910 --> 00:02:37.920 align:start position:0% protocol some of you here I'm sure are 00:02:37.920 --> 00:02:40.309 align:start position:0% protocol some of you here I'm sure are running<00:02:38.099> validators<00:02:38.840> some<00:02:39.840> of<00:02:39.959> you<00:02:40.020> may<00:02:40.200> be 00:02:40.309 --> 00:02:40.319 align:start position:0% running validators some of you may be 00:02:40.319 --> 00:02:42.589 align:start position:0% running validators some of you may be running<00:02:40.440> Lighthouse<00:02:40.920> as<00:02:41.160> well<00:02:41.360> we<00:02:42.360> had<00:02:42.540> the 00:02:42.589 --> 00:02:42.599 align:start position:0% running Lighthouse as well we had the 00:02:42.599 --> 00:02:44.390 align:start position:0% running Lighthouse as well we had the merge<00:02:42.900> a<00:02:42.959> few<00:02:43.080> weeks<00:02:43.319> ago<00:02:43.500> my<00:02:43.739> six<00:02:43.980> milestone 00:02:44.390 --> 00:02:44.400 align:start position:0% merge a few weeks ago my six milestone 00:02:44.400 --> 00:02:46.250 align:start position:0% merge a few weeks ago my six milestone for<00:02:44.640> everyone<00:02:44.760> massive<00:02:45.420> milestone<00:02:45.720> for<00:02:45.959> Sigma 00:02:46.250 --> 00:02:46.260 align:start position:0% for everyone massive milestone for Sigma 00:02:46.260 --> 00:02:50.210 align:start position:0% for everyone massive milestone for Sigma Prime<00:02:46.440> and<00:02:47.220> yeah<00:02:47.940> hi<00:02:48.540> everybody<00:02:48.780> I'm<00:02:49.620> Jonathan 00:02:50.210 --> 00:02:50.220 align:start position:0% Prime and yeah hi everybody I'm Jonathan 00:02:50.220 --> 00:02:53.390 align:start position:0% Prime and yeah hi everybody I'm Jonathan Alexander<00:02:50.940> I<00:02:51.300> am<00:02:51.480> CTO<00:02:51.959> at<00:02:52.260> open<00:02:52.379> Zeppelin<00:02:53.040> open 00:02:53.390 --> 00:02:53.400 align:start position:0% Alexander I am CTO at open Zeppelin open 00:02:53.400 --> 00:02:57.530 align:start position:0% Alexander I am CTO at open Zeppelin open Zeppelin<00:02:54.120> we<00:02:54.900> are<00:02:55.080> a<00:02:55.379> security<00:02:56.540> advisor 00:02:57.530 --> 00:02:57.540 align:start position:0% Zeppelin we are a security advisor 00:02:57.540 --> 00:02:59.930 align:start position:0% Zeppelin we are a security advisor security<00:02:57.900> auditor<00:02:58.739> we<00:02:59.160> also<00:02:59.400> work<00:02:59.580> on<00:02:59.760> open 00:02:59.930 --> 00:02:59.940 align:start position:0% security auditor we also work on open 00:02:59.940 --> 00:03:01.970 align:start position:0% security auditor we also work on open Zeppelin<00:03:00.480> contracts 00:03:01.970 --> 00:03:01.980 align:start position:0% Zeppelin contracts 00:03:01.980 --> 00:03:05.030 align:start position:0% Zeppelin contracts open<00:03:02.340> Zeppelin<00:03:02.879> Defender<00:03:03.360> and<00:03:03.959> we<00:03:04.200> are<00:03:04.440> core 00:03:05.030 --> 00:03:05.040 align:start position:0% open Zeppelin Defender and we are core 00:03:05.040 --> 00:03:07.910 align:start position:0% open Zeppelin Defender and we are core development<00:03:05.700> contributors<00:03:06.480> to<00:03:06.900> Florida<00:03:07.200> and 00:03:07.910 --> 00:03:07.920 align:start position:0% development contributors to Florida and 00:03:07.920 --> 00:03:09.589 align:start position:0% development contributors to Florida and hi<00:03:08.099> everybody<00:03:08.220> I'm<00:03:08.519> Nick<00:03:08.700> Selby<00:03:09.120> I'm<00:03:09.420> with 00:03:09.589 --> 00:03:09.599 align:start position:0% hi everybody I'm Nick Selby I'm with 00:03:09.599 --> 00:03:12.050 align:start position:0% hi everybody I'm Nick Selby I'm with trail<00:03:09.840> of<00:03:10.080> bits<00:03:10.500> we<00:03:10.920> are<00:03:11.099> an<00:03:11.459> audit<00:03:11.879> and 00:03:12.050 --> 00:03:12.060 align:start position:0% trail of bits we are an audit and 00:03:12.060 --> 00:03:13.910 align:start position:0% trail of bits we are an audit and research<00:03:12.480> company<00:03:12.780> based<00:03:13.440> in<00:03:13.500> New<00:03:13.620> York<00:03:13.739> but 00:03:13.910 --> 00:03:13.920 align:start position:0% research company based in New York but 00:03:13.920 --> 00:03:16.190 align:start position:0% research company based in New York but people<00:03:14.159> are<00:03:14.280> all<00:03:14.459> around<00:03:14.580> the<00:03:14.819> world<00:03:15.019> uh<00:03:16.019> in 00:03:16.190 --> 00:03:16.200 align:start position:0% people are all around the world uh in 00:03:16.200 --> 00:03:18.229 align:start position:0% people are all around the world uh in addition<00:03:16.379> to<00:03:16.739> audits<00:03:17.280> we<00:03:17.400> have<00:03:17.519> a<00:03:17.700> research 00:03:18.229 --> 00:03:18.239 align:start position:0% addition to audits we have a research 00:03:18.239 --> 00:03:20.930 align:start position:0% addition to audits we have a research group<00:03:18.780> that<00:03:19.200> that<00:03:19.379> mainly<00:03:19.800> works<00:03:20.099> on<00:03:20.280> just 00:03:20.930 --> 00:03:20.940 align:start position:0% group that that mainly works on just 00:03:20.940 --> 00:03:23.270 align:start position:0% group that that mainly works on just sort<00:03:21.239> of<00:03:21.300> pushing<00:03:21.599> the<00:03:21.780> edges<00:03:22.080> of<00:03:22.319> of<00:03:22.680> a<00:03:23.040> bunch 00:03:23.270 --> 00:03:23.280 align:start position:0% sort of pushing the edges of of a bunch 00:03:23.280 --> 00:03:24.530 align:start position:0% sort of pushing the edges of of a bunch of<00:03:23.340> different<00:03:23.580> Technologies<00:03:24.060> including 00:03:24.530 --> 00:03:24.540 align:start position:0% of different Technologies including 00:03:24.540 --> 00:03:26.809 align:start position:0% of different Technologies including blockchain<00:03:24.959> uh<00:03:25.920> and<00:03:26.099> where<00:03:26.340> are<00:03:26.459> things<00:03:26.580> going 00:03:26.809 --> 00:03:26.819 align:start position:0% blockchain uh and where are things going 00:03:26.819 --> 00:03:28.910 align:start position:0% blockchain uh and where are things going next<00:03:27.120> and<00:03:27.720> we<00:03:28.080> make<00:03:28.260> some<00:03:28.560> pretty<00:03:28.739> popular 00:03:28.910 --> 00:03:28.920 align:start position:0% next and we make some pretty popular 00:03:28.920 --> 00:03:30.470 align:start position:0% next and we make some pretty popular open<00:03:29.159> source<00:03:29.580> tools<00:03:29.819> like<00:03:29.940> Slither<00:03:30.300> and 00:03:30.470 --> 00:03:30.480 align:start position:0% open source tools like Slither and 00:03:30.480 --> 00:03:31.970 align:start position:0% open source tools like Slither and Echidna<00:03:30.900> which<00:03:31.019> probably<00:03:31.200> several<00:03:31.620> of<00:03:31.739> your 00:03:31.970 --> 00:03:31.980 align:start position:0% Echidna which probably several of your 00:03:31.980 --> 00:03:34.610 align:start position:0% Echidna which probably several of your you<00:03:32.459> know<00:03:32.580> familiar<00:03:33.420> with<00:03:33.599> thanks<00:03:34.200> I'm<00:03:34.440> glad 00:03:34.610 --> 00:03:34.620 align:start position:0% you know familiar with thanks I'm glad 00:03:34.620 --> 00:03:35.630 align:start position:0% you know familiar with thanks I'm glad to<00:03:34.739> be<00:03:34.800> here 00:03:35.630 --> 00:03:35.640 align:start position:0% to be here 00:03:35.640 --> 00:03:38.509 align:start position:0% to be here awesome<00:03:36.239> thanks<00:03:36.659> everyone<00:03:36.920> uh<00:03:37.920> so<00:03:38.220> first 00:03:38.509 --> 00:03:38.519 align:start position:0% awesome thanks everyone uh so first 00:03:38.519 --> 00:03:40.729 align:start position:0% awesome thanks everyone uh so first question<00:03:38.819> I<00:03:39.420> think<00:03:39.540> is<00:03:39.720> like<00:03:40.019> maybe<00:03:40.260> a<00:03:40.500> bit<00:03:40.620> of 00:03:40.729 --> 00:03:40.739 align:start position:0% question I think is like maybe a bit of 00:03:40.739 --> 00:03:42.789 align:start position:0% question I think is like maybe a bit of a<00:03:40.799> softball<00:03:41.159> just<00:03:41.580> to<00:03:41.700> get<00:03:41.819> us<00:03:41.940> going 00:03:42.789 --> 00:03:42.799 align:start position:0% a softball just to get us going 00:03:42.799 --> 00:03:47.630 align:start position:0% a softball just to get us going uh<00:03:43.940> and<00:03:44.940> I'll<00:03:45.659> I'll<00:03:46.200> pose<00:03:46.680> this<00:03:46.920> to<00:03:47.099> Medi<00:03:47.519> first 00:03:47.630 --> 00:03:47.640 align:start position:0% uh and I'll I'll pose this to Medi first 00:03:47.640 --> 00:03:49.190 align:start position:0% uh and I'll I'll pose this to Medi first and<00:03:47.879> then<00:03:48.000> just<00:03:48.180> let<00:03:48.360> the<00:03:48.540> conversation<00:03:48.900> get 00:03:49.190 --> 00:03:49.200 align:start position:0% and then just let the conversation get 00:03:49.200 --> 00:03:50.089 align:start position:0% and then just let the conversation get going 00:03:50.089 --> 00:03:50.099 align:start position:0% going 00:03:50.099 --> 00:03:52.369 align:start position:0% going so<00:03:50.640> it's<00:03:50.940> been<00:03:51.180> three<00:03:51.420> years<00:03:51.599> since<00:03:52.019> the<00:03:52.200> last 00:03:52.369 --> 00:03:52.379 align:start position:0% so it's been three years since the last 00:03:52.379 --> 00:03:54.589 align:start position:0% so it's been three years since the last Devcon<00:03:52.920> what<00:03:53.819> do<00:03:53.940> you<00:03:54.060> see<00:03:54.180> as<00:03:54.299> the<00:03:54.480> biggest 00:03:54.589 --> 00:03:54.599 align:start position:0% Devcon what do you see as the biggest 00:03:54.599 --> 00:03:56.690 align:start position:0% Devcon what do you see as the biggest changes<00:03:55.080> in<00:03:55.319> that<00:03:55.440> time<00:03:55.680> maybe<00:03:56.400> it's 00:03:56.690 --> 00:03:56.700 align:start position:0% changes in that time maybe it's 00:03:56.700 --> 00:03:58.910 align:start position:0% changes in that time maybe it's something<00:03:56.940> you're<00:03:57.239> excited<00:03:57.720> about<00:03:57.920> something 00:03:58.910 --> 00:03:58.920 align:start position:0% something you're excited about something 00:03:58.920 --> 00:04:00.830 align:start position:0% something you're excited about something you're<00:03:59.220> worried<00:03:59.519> about<00:03:59.700> we'd<00:04:00.480> love<00:04:00.599> to<00:04:00.720> hear 00:04:00.830 --> 00:04:00.840 align:start position:0% you're worried about we'd love to hear 00:04:00.840 --> 00:04:02.449 align:start position:0% you're worried about we'd love to hear it<00:04:00.959> yeah<00:04:01.260> interesting 00:04:02.449 --> 00:04:02.459 align:start position:0% it yeah interesting 00:04:02.459 --> 00:04:06.470 align:start position:0% it yeah interesting um<00:04:03.019> let's<00:04:04.019> see<00:04:04.260> I<00:04:05.220> think<00:04:05.459> what<00:04:06.060> I've<00:04:06.239> been 00:04:06.470 --> 00:04:06.480 align:start position:0% um let's see I think what I've been 00:04:06.480 --> 00:04:09.949 align:start position:0% um let's see I think what I've been noticing<00:04:06.959> is<00:04:07.620> the<00:04:08.159> quality<00:04:09.060> of<00:04:09.480> the<00:04:09.659> projects 00:04:09.949 --> 00:04:09.959 align:start position:0% noticing is the quality of the projects 00:04:09.959 --> 00:04:12.710 align:start position:0% noticing is the quality of the projects that<00:04:10.140> we've<00:04:10.319> been<00:04:10.439> reviewing<00:04:10.860> has<00:04:11.720> somewhat 00:04:12.710 --> 00:04:12.720 align:start position:0% that we've been reviewing has somewhat 00:04:12.720 --> 00:04:15.110 align:start position:0% that we've been reviewing has somewhat improved<00:04:13.080> over<00:04:13.260> the<00:04:13.439> past<00:04:13.620> three<00:04:13.860> years<00:04:14.120> uh 00:04:15.110 --> 00:04:15.120 align:start position:0% improved over the past three years uh 00:04:15.120 --> 00:04:17.810 align:start position:0% improved over the past three years uh this<00:04:15.480> caveats<00:04:16.079> obviously<00:04:16.440> we<00:04:17.220> still<00:04:17.340> get<00:04:17.579> the 00:04:17.810 --> 00:04:17.820 align:start position:0% this caveats obviously we still get the 00:04:17.820 --> 00:04:20.870 align:start position:0% this caveats obviously we still get the occasional<00:04:18.359> you<00:04:18.959> know<00:04:19.019> D5<00:04:19.440> projects<00:04:20.100> with<00:04:20.579> you 00:04:20.870 --> 00:04:20.880 align:start position:0% occasional you know D5 projects with you 00:04:20.880 --> 00:04:23.330 align:start position:0% occasional you know D5 projects with you know<00:04:21.000> lack<00:04:21.239> of<00:04:21.419> access<00:04:21.660> control<00:04:22.079> and<00:04:22.620> the 00:04:23.330 --> 00:04:23.340 align:start position:0% know lack of access control and the 00:04:23.340 --> 00:04:25.969 align:start position:0% know lack of access control and the typical<00:04:23.720> unsafe<00:04:24.720> and<00:04:25.080> safe<00:04:25.259> external<00:04:25.740> calls 00:04:25.969 --> 00:04:25.979 align:start position:0% typical unsafe and safe external calls 00:04:25.979 --> 00:04:28.010 align:start position:0% typical unsafe and safe external calls and<00:04:26.100> re-entrances<00:04:26.759> but<00:04:27.060> I'd<00:04:27.540> like<00:04:27.720> to<00:04:27.780> think 00:04:28.010 --> 00:04:28.020 align:start position:0% and re-entrances but I'd like to think 00:04:28.020 --> 00:04:30.230 align:start position:0% and re-entrances but I'd like to think that<00:04:28.320> thanks<00:04:29.040> to<00:04:29.340> some<00:04:29.639> of<00:04:29.820> the<00:04:29.880> tooling 00:04:30.230 --> 00:04:30.240 align:start position:0% that thanks to some of the tooling 00:04:30.240 --> 00:04:32.090 align:start position:0% that thanks to some of the tooling that's<00:04:30.419> been<00:04:30.660> available<00:04:30.840> it's<00:04:31.740> been<00:04:31.979> doing 00:04:32.090 --> 00:04:32.100 align:start position:0% that's been available it's been doing 00:04:32.100 --> 00:04:34.670 align:start position:0% that's been available it's been doing great<00:04:32.280> work<00:04:32.400> on<00:04:32.580> that<00:04:32.699> front<00:04:33.380> developers<00:04:34.380> have 00:04:34.670 --> 00:04:34.680 align:start position:0% great work on that front developers have 00:04:34.680 --> 00:04:37.670 align:start position:0% great work on that front developers have a<00:04:34.860> lot<00:04:35.040> of<00:04:35.660> abilities<00:04:36.660> these<00:04:37.139> days<00:04:37.199> to<00:04:37.500> pick<00:04:37.560> up 00:04:37.670 --> 00:04:37.680 align:start position:0% a lot of abilities these days to pick up 00:04:37.680 --> 00:04:40.249 align:start position:0% a lot of abilities these days to pick up the<00:04:37.860> low<00:04:37.919> hanging<00:04:38.280> fruits<00:04:39.080> contracts<00:04:40.080> are 00:04:40.249 --> 00:04:40.259 align:start position:0% the low hanging fruits contracts are 00:04:40.259 --> 00:04:42.890 align:start position:0% the low hanging fruits contracts are getting<00:04:40.440> more<00:04:40.800> and<00:04:40.919> more<00:04:41.160> complex<00:04:41.580> in<00:04:42.540> the<00:04:42.660> D5 00:04:42.890 --> 00:04:42.900 align:start position:0% getting more and more complex in the D5 00:04:42.900 --> 00:04:45.350 align:start position:0% getting more and more complex in the D5 space<00:04:43.259> particularly<00:04:43.820> some<00:04:44.820> of<00:04:44.940> the<00:04:45.060> lending 00:04:45.350 --> 00:04:45.360 align:start position:0% space particularly some of the lending 00:04:45.360 --> 00:04:47.330 align:start position:0% space particularly some of the lending protocols<00:04:45.780> that<00:04:45.900> we've<00:04:46.080> been<00:04:46.199> reviewing<00:04:46.740> are 00:04:47.330 --> 00:04:47.340 align:start position:0% protocols that we've been reviewing are 00:04:47.340 --> 00:04:51.890 align:start position:0% protocols that we've been reviewing are pretty<00:04:47.940> hectic<00:04:48.740> but<00:04:49.740> yeah<00:04:50.040> yeah<00:04:50.460> I<00:04:50.820> think<00:04:51.060> you 00:04:51.890 --> 00:04:51.900 align:start position:0% pretty hectic but yeah yeah I think you 00:04:51.900 --> 00:04:54.710 align:start position:0% pretty hectic but yeah yeah I think you know<00:04:51.960> the<00:04:52.380> amount<00:04:52.680> of<00:04:52.860> money<00:04:53.520> getting<00:04:54.180> stolen 00:04:54.710 --> 00:04:54.720 align:start position:0% know the amount of money getting stolen 00:04:54.720 --> 00:04:58.249 align:start position:0% know the amount of money getting stolen on<00:04:55.320> a<00:04:55.500> weekly<00:04:55.860> basis<00:04:56.280> these<00:04:56.699> days<00:04:56.840> is<00:04:57.840> probably 00:04:58.249 --> 00:04:58.259 align:start position:0% on a weekly basis these days is probably 00:04:58.259 --> 00:05:00.530 align:start position:0% on a weekly basis these days is probably greater<00:04:58.800> than<00:04:58.979> what<00:04:59.160> it<00:04:59.340> was<00:04:59.460> three<00:04:59.880> years<00:05:00.240> ago 00:05:00.530 --> 00:05:00.540 align:start position:0% greater than what it was three years ago 00:05:00.540 --> 00:05:03.110 align:start position:0% greater than what it was three years ago I'd<00:05:00.720> say<00:05:00.919> but<00:05:01.919> it's<00:05:02.280> probably<00:05:02.460> due<00:05:02.759> to<00:05:02.940> the 00:05:03.110 --> 00:05:03.120 align:start position:0% I'd say but it's probably due to the 00:05:03.120 --> 00:05:05.090 align:start position:0% I'd say but it's probably due to the fact<00:05:03.300> that<00:05:03.540> there's<00:05:03.780> just<00:05:04.020> so<00:05:04.380> much<00:05:04.500> more<00:05:04.740> so 00:05:05.090 --> 00:05:05.100 align:start position:0% fact that there's just so much more so 00:05:05.100 --> 00:05:07.010 align:start position:0% fact that there's just so much more so many<00:05:05.340> more<00:05:05.699> people<00:05:05.940> getting<00:05:06.419> into<00:05:06.600> the<00:05:06.900> field 00:05:07.010 --> 00:05:07.020 align:start position:0% many more people getting into the field 00:05:07.020 --> 00:05:10.010 align:start position:0% many more people getting into the field a<00:05:07.860> lot<00:05:07.979> of<00:05:08.220> new<00:05:08.639> projects<00:05:09.120> being<00:05:09.300> deployed<00:05:09.780> and 00:05:10.010 --> 00:05:10.020 align:start position:0% a lot of new projects being deployed and 00:05:10.020 --> 00:05:13.030 align:start position:0% a lot of new projects being deployed and obviously<00:05:10.620> you<00:05:11.040> know<00:05:11.160> our<00:05:11.639> time<00:05:11.880> is<00:05:12.180> you<00:05:12.840> know 00:05:13.030 --> 00:05:13.040 align:start position:0% obviously you know our time is you know 00:05:13.040 --> 00:05:15.650 align:start position:0% obviously you know our time is you know constrained<00:05:14.040> we<00:05:14.460> can't<00:05:14.699> unfortunately 00:05:15.650 --> 00:05:15.660 align:start position:0% constrained we can't unfortunately 00:05:15.660 --> 00:05:18.650 align:start position:0% constrained we can't unfortunately service<00:05:16.080> everyone<00:05:16.740> all<00:05:17.340> the<00:05:17.520> time 00:05:18.650 --> 00:05:18.660 align:start position:0% service everyone all the time 00:05:18.660 --> 00:05:21.050 align:start position:0% service everyone all the time um<00:05:18.720> but<00:05:19.139> yeah<00:05:19.259> so<00:05:19.620> goods<00:05:20.460> and<00:05:20.520> bads<00:05:20.880> I<00:05:20.940> guess 00:05:21.050 --> 00:05:21.060 align:start position:0% um but yeah so goods and bads I guess 00:05:21.060 --> 00:05:23.270 align:start position:0% um but yeah so goods and bads I guess we've<00:05:21.720> seen<00:05:21.900> a<00:05:22.080> lot<00:05:22.199> of<00:05:22.259> projects<00:05:22.740> come<00:05:22.919> and<00:05:23.100> go 00:05:23.270 --> 00:05:23.280 align:start position:0% we've seen a lot of projects come and go 00:05:23.280 --> 00:05:25.909 align:start position:0% we've seen a lot of projects come and go too<00:05:23.520> and<00:05:24.180> a<00:05:24.419> lot<00:05:24.539> of<00:05:24.660> money<00:05:24.840> come<00:05:25.080> and<00:05:25.259> go<00:05:25.440> so 00:05:25.909 --> 00:05:25.919 align:start position:0% too and a lot of money come and go so 00:05:25.919 --> 00:05:28.670 align:start position:0% too and a lot of money come and go so yeah<00:05:26.340> I<00:05:26.580> think<00:05:26.940> that<00:05:27.120> like<00:05:27.360> even<00:05:27.780> I<00:05:28.259> fully 00:05:28.670 --> 00:05:28.680 align:start position:0% yeah I think that like even I fully 00:05:28.680 --> 00:05:31.330 align:start position:0% yeah I think that like even I fully agree<00:05:28.919> with<00:05:29.340> Maddie<00:05:29.759> the<00:05:30.360> quality<00:05:30.840> has 00:05:31.330 --> 00:05:31.340 align:start position:0% agree with Maddie the quality has 00:05:31.340 --> 00:05:35.150 align:start position:0% agree with Maddie the quality has definitely<00:05:32.340> improved<00:05:33.060> in<00:05:33.900> I<00:05:34.500> think<00:05:34.620> the<00:05:34.979> bear 00:05:35.150 --> 00:05:35.160 align:start position:0% definitely improved in I think the bear 00:05:35.160 --> 00:05:37.430 align:start position:0% definitely improved in I think the bear Market<00:05:35.460> kind<00:05:35.820> of<00:05:35.940> helped<00:05:36.240> at<00:05:36.419> that<00:05:36.960> okay 00:05:37.430 --> 00:05:37.440 align:start position:0% Market kind of helped at that okay 00:05:37.440 --> 00:05:39.170 align:start position:0% Market kind of helped at that okay anybody<00:05:37.860> have<00:05:38.100> uh<00:05:38.400> something<00:05:38.699> different<00:05:38.940> to 00:05:39.170 --> 00:05:39.180 align:start position:0% anybody have uh something different to 00:05:39.180 --> 00:05:41.689 align:start position:0% anybody have uh something different to say<00:05:39.360> than<00:05:39.600> better<00:05:40.020> quality<00:05:40.860> I<00:05:41.100> have<00:05:41.280> a<00:05:41.400> mixed 00:05:41.689 --> 00:05:41.699 align:start position:0% say than better quality I have a mixed 00:05:41.699 --> 00:05:44.029 align:start position:0% say than better quality I have a mixed bag<00:05:41.759> all<00:05:42.240> right<00:05:42.419> so<00:05:43.020> like 00:05:44.029 --> 00:05:44.039 align:start position:0% bag all right so like 00:05:44.039 --> 00:05:45.830 align:start position:0% bag all right so like three<00:05:44.400> years<00:05:44.520> ago<00:05:44.759> it<00:05:44.940> was<00:05:45.120> it<00:05:45.300> was<00:05:45.419> a<00:05:45.539> simpler 00:05:45.830 --> 00:05:45.840 align:start position:0% three years ago it was it was a simpler 00:05:45.840 --> 00:05:48.770 align:start position:0% three years ago it was it was a simpler time<00:05:45.960> uh<00:05:46.800> things<00:05:47.759> were<00:05:47.940> a<00:05:48.300> lot<00:05:48.360> easier<00:05:48.479> to<00:05:48.660> look 00:05:48.770 --> 00:05:48.780 align:start position:0% time uh things were a lot easier to look 00:05:48.780 --> 00:05:50.270 align:start position:0% time uh things were a lot easier to look at<00:05:48.840> things<00:05:49.080> were<00:05:49.259> a<00:05:49.380> lot<00:05:49.440> more<00:05:49.560> self-contained 00:05:50.270 --> 00:05:50.280 align:start position:0% at things were a lot more self-contained 00:05:50.280 --> 00:05:53.150 align:start position:0% at things were a lot more self-contained uh<00:05:51.060> and<00:05:51.720> as<00:05:52.020> you<00:05:52.259> just<00:05:52.380> said<00:05:52.500> right<00:05:52.680> the<00:05:52.979> the 00:05:53.150 --> 00:05:53.160 align:start position:0% uh and as you just said right the the 00:05:53.160 --> 00:05:56.450 align:start position:0% uh and as you just said right the the complexity<00:05:53.880> the<00:05:54.360> the<00:05:55.080> Maze<00:05:55.800> of<00:05:55.919> dependencies 00:05:56.450 --> 00:05:56.460 align:start position:0% complexity the the Maze of dependencies 00:05:56.460 --> 00:05:59.810 align:start position:0% complexity the the Maze of dependencies the<00:05:57.060> uh<00:05:57.720> the<00:05:58.080> the<00:05:58.220> complexity<00:05:59.220> has<00:05:59.520> kind<00:05:59.699> of 00:05:59.810 --> 00:05:59.820 align:start position:0% the uh the the complexity has kind of 00:05:59.820 --> 00:06:02.150 align:start position:0% the uh the the complexity has kind of exploded<00:06:00.300> at<00:06:01.080> the<00:06:01.259> same<00:06:01.380> time<00:06:01.620> that<00:06:01.919> there's 00:06:02.150 --> 00:06:02.160 align:start position:0% exploded at the same time that there's 00:06:02.160 --> 00:06:03.590 align:start position:0% exploded at the same time that there's more<00:06:02.280> and<00:06:02.400> more<00:06:02.580> value<00:06:02.759> so<00:06:03.060> the<00:06:03.180> stakes<00:06:03.419> are 00:06:03.590 --> 00:06:03.600 align:start position:0% more and more value so the stakes are 00:06:03.600 --> 00:06:05.029 align:start position:0% more and more value so the stakes are much<00:06:03.720> much<00:06:03.900> higher<00:06:04.199> I<00:06:04.560> think<00:06:04.680> on<00:06:04.800> the<00:06:04.979> other 00:06:05.029 --> 00:06:05.039 align:start position:0% much much higher I think on the other 00:06:05.039 --> 00:06:06.770 align:start position:0% much much higher I think on the other hand<00:06:05.160> you're<00:06:05.460> right<00:06:05.580> the<00:06:05.759> tooling<00:06:06.120> has<00:06:06.479> gotten 00:06:06.770 --> 00:06:06.780 align:start position:0% hand you're right the tooling has gotten 00:06:06.780 --> 00:06:08.810 align:start position:0% hand you're right the tooling has gotten a<00:06:06.840> lot<00:06:06.960> better<00:06:07.080> but<00:06:07.320> it's<00:06:07.440> also<00:06:07.740> I<00:06:08.160> think<00:06:08.340> all 00:06:08.810 --> 00:06:08.820 align:start position:0% a lot better but it's also I think all 00:06:08.820 --> 00:06:11.029 align:start position:0% a lot better but it's also I think all of<00:06:09.000> us<00:06:09.120> here<00:06:09.600> working<00:06:09.900> with<00:06:10.080> with<00:06:10.259> firms<00:06:10.740> that 00:06:11.029 --> 00:06:11.039 align:start position:0% of us here working with with firms that 00:06:11.039 --> 00:06:14.150 align:start position:0% of us here working with with firms that are<00:06:11.160> we're<00:06:11.400> getting<00:06:11.580> used<00:06:11.880> to<00:06:12.380> the<00:06:13.380> we're<00:06:13.979> used 00:06:14.150 --> 00:06:14.160 align:start position:0% are we're getting used to the we're used 00:06:14.160 --> 00:06:15.710 align:start position:0% are we're getting used to the we're used to<00:06:14.280> the<00:06:14.520> risks<00:06:14.820> we're<00:06:15.000> used<00:06:15.120> to<00:06:15.240> the<00:06:15.419> threats 00:06:15.710 --> 00:06:15.720 align:start position:0% to the risks we're used to the threats 00:06:15.720 --> 00:06:18.230 align:start position:0% to the risks we're used to the threats we're<00:06:16.020> we're<00:06:16.320> inured<00:06:17.039> to<00:06:17.340> the<00:06:17.520> patterns<00:06:17.880> we<00:06:18.060> we 00:06:18.230 --> 00:06:18.240 align:start position:0% we're we're inured to the patterns we we 00:06:18.240 --> 00:06:19.490 align:start position:0% we're we're inured to the patterns we we can<00:06:18.479> see<00:06:18.600> them<00:06:18.840> a<00:06:18.960> lot<00:06:19.080> more<00:06:19.199> clearly 00:06:19.490 --> 00:06:19.500 align:start position:0% can see them a lot more clearly 00:06:19.500 --> 00:06:21.290 align:start position:0% can see them a lot more clearly everybody<00:06:20.039> here<00:06:20.340> has<00:06:20.520> a<00:06:20.639> lot<00:06:20.699> more<00:06:20.820> experience 00:06:21.290 --> 00:06:21.300 align:start position:0% everybody here has a lot more experience 00:06:21.300 --> 00:06:23.990 align:start position:0% everybody here has a lot more experience in<00:06:21.720> in<00:06:21.960> finding<00:06:22.440> things<00:06:22.620> uh<00:06:23.460> and<00:06:23.639> on<00:06:23.759> the<00:06:23.880> other 00:06:23.990 --> 00:06:24.000 align:start position:0% in in finding things uh and on the other 00:06:24.000 --> 00:06:25.370 align:start position:0% in in finding things uh and on the other other<00:06:24.180> hand 00:06:25.370 --> 00:06:25.380 align:start position:0% other hand 00:06:25.380 --> 00:06:27.350 align:start position:0% other hand um<00:06:25.440> three<00:06:25.680> years<00:06:25.860> ago<00:06:26.100> I<00:06:26.340> remember<00:06:26.520> being 00:06:27.350 --> 00:06:27.360 align:start position:0% um three years ago I remember being 00:06:27.360 --> 00:06:29.689 align:start position:0% um three years ago I remember being describing<00:06:28.020> to<00:06:28.139> board<00:06:28.319> members<00:06:28.680> of<00:06:28.860> a<00:06:29.039> of<00:06:29.460> a 00:06:29.689 --> 00:06:29.699 align:start position:0% describing to board members of a of a 00:06:29.699 --> 00:06:31.670 align:start position:0% describing to board members of a of a pretty<00:06:29.759> large<00:06:29.940> crypto<00:06:30.360> company<00:06:30.539> uh<00:06:31.440> about 00:06:31.670 --> 00:06:31.680 align:start position:0% pretty large crypto company uh about 00:06:31.680 --> 00:06:33.170 align:start position:0% pretty large crypto company uh about nation-state<00:06:32.460> threats<00:06:32.819> specifically 00:06:33.170 --> 00:06:33.180 align:start position:0% nation-state threats specifically 00:06:33.180 --> 00:06:35.450 align:start position:0% nation-state threats specifically talking<00:06:33.419> about<00:06:33.600> North<00:06:34.080> Korea<00:06:34.500> and<00:06:35.160> they<00:06:35.340> kind 00:06:35.450 --> 00:06:35.460 align:start position:0% talking about North Korea and they kind 00:06:35.460 --> 00:06:36.770 align:start position:0% talking about North Korea and they kind of<00:06:35.520> looked<00:06:35.759> at<00:06:35.819> me<00:06:35.880> with<00:06:36.060> blank<00:06:36.300> stairs<00:06:36.600> and 00:06:36.770 --> 00:06:36.780 align:start position:0% of looked at me with blank stairs and 00:06:36.780 --> 00:06:39.230 align:start position:0% of looked at me with blank stairs and they<00:06:36.840> were<00:06:36.960> like<00:06:37.080> well<00:06:37.380> you<00:06:37.860> know<00:06:37.979> so<00:06:38.280> what<00:06:38.520> and 00:06:39.230 --> 00:06:39.240 align:start position:0% they were like well you know so what and 00:06:39.240 --> 00:06:41.150 align:start position:0% they were like well you know so what and I<00:06:39.780> think<00:06:39.900> that<00:06:40.139> over<00:06:40.380> the<00:06:40.560> past<00:06:40.740> three<00:06:40.919> years 00:06:41.150 --> 00:06:41.160 align:start position:0% I think that over the past three years 00:06:41.160 --> 00:06:43.249 align:start position:0% I think that over the past three years that<00:06:41.580> that<00:06:41.819> nation-state<00:06:42.479> involvement<00:06:42.900> has 00:06:43.249 --> 00:06:43.259 align:start position:0% that that nation-state involvement has 00:06:43.259 --> 00:06:45.830 align:start position:0% that that nation-state involvement has gone<00:06:43.440> from<00:06:43.740> a<00:06:44.100> kind<00:06:44.220> of<00:06:44.280> a<00:06:44.460> risk<00:06:44.759> to<00:06:45.360> a<00:06:45.479> definite 00:06:45.830 --> 00:06:45.840 align:start position:0% gone from a kind of a risk to a definite 00:06:45.840 --> 00:06:48.110 align:start position:0% gone from a kind of a risk to a definite and<00:06:46.139> definable<00:06:46.560> threat 00:06:48.110 --> 00:06:48.120 align:start position:0% and definable threat 00:06:48.120 --> 00:06:49.390 align:start position:0% and definable threat yeah 00:06:49.390 --> 00:06:49.400 align:start position:0% yeah 00:06:49.400 --> 00:06:52.189 align:start position:0% yeah uh<00:06:50.400> Chandra<00:06:51.120> do<00:06:51.360> you 00:06:52.189 --> 00:06:52.199 align:start position:0% uh Chandra do you 00:06:52.199 --> 00:06:54.350 align:start position:0% uh Chandra do you so<00:06:52.680> well<00:06:52.860> this<00:06:53.100> is<00:06:53.220> my<00:06:53.400> first<00:06:53.520> Devcon<00:06:53.940> so<00:06:54.180> I 00:06:54.350 --> 00:06:54.360 align:start position:0% so well this is my first Devcon so I 00:06:54.360 --> 00:06:56.570 align:start position:0% so well this is my first Devcon so I wasn't<00:06:54.479> there<00:06:54.720> in<00:06:54.960> the<00:06:55.139> the<00:06:55.440> first<00:06:55.979> the<00:06:56.280> one 00:06:56.570 --> 00:06:56.580 align:start position:0% wasn't there in the the first the one 00:06:56.580 --> 00:06:59.090 align:start position:0% wasn't there in the the first the one three<00:06:56.819> years<00:06:56.940> ago<00:06:57.240> uh<00:06:58.020> but<00:06:58.259> what<00:06:58.500> I've<00:06:58.680> noticed 00:06:59.090 --> 00:06:59.100 align:start position:0% three years ago uh but what I've noticed 00:06:59.100 --> 00:07:00.290 align:start position:0% three years ago uh but what I've noticed is<00:06:59.340> that 00:07:00.290 --> 00:07:00.300 align:start position:0% is that 00:07:00.300 --> 00:07:02.210 align:start position:0% is that um there<00:07:01.020> seems<00:07:01.259> to<00:07:01.319> this<00:07:01.620> is<00:07:01.740> a<00:07:01.919> very<00:07:02.039> fast 00:07:02.210 --> 00:07:02.220 align:start position:0% um there seems to this is a very fast 00:07:02.220 --> 00:07:04.730 align:start position:0% um there seems to this is a very fast moving<00:07:02.699> field<00:07:02.940> and<00:07:03.240> there's<00:07:03.479> like<00:07:03.840> a<00:07:04.319> new 00:07:04.730 --> 00:07:04.740 align:start position:0% moving field and there's like a new 00:07:04.740 --> 00:07:07.850 align:start position:0% moving field and there's like a new terms<00:07:05.160> new<00:07:05.460> buzzwords<00:07:06.060> new<00:07:06.600> Concepts<00:07:07.080> that 00:07:07.850 --> 00:07:07.860 align:start position:0% terms new buzzwords new Concepts that 00:07:07.860 --> 00:07:10.730 align:start position:0% terms new buzzwords new Concepts that keep<00:07:08.400> getting<00:07:08.580> thrown<00:07:09.000> around<00:07:09.120> a<00:07:09.479> lot<00:07:09.600> uh<00:07:10.500> but 00:07:10.730 --> 00:07:10.740 align:start position:0% keep getting thrown around a lot uh but 00:07:10.740 --> 00:07:12.350 align:start position:0% keep getting thrown around a lot uh but I<00:07:10.860> think<00:07:10.979> you<00:07:11.280> know<00:07:11.400> the<00:07:11.580> main<00:07:11.699> thing<00:07:11.880> that<00:07:12.120> I 00:07:12.350 --> 00:07:12.360 align:start position:0% I think you know the main thing that I 00:07:12.360 --> 00:07:15.230 align:start position:0% I think you know the main thing that I would<00:07:12.539> uh<00:07:13.139> you<00:07:13.380> know<00:07:13.440> say<00:07:13.800> here<00:07:14.100> is<00:07:14.580> I<00:07:15.120> think 00:07:15.230 --> 00:07:15.240 align:start position:0% would uh you know say here is I think 00:07:15.240 --> 00:07:17.270 align:start position:0% would uh you know say here is I think it's<00:07:15.419> important<00:07:15.720> to<00:07:16.020> remember<00:07:16.259> that<00:07:16.800> at<00:07:17.160> the 00:07:17.270 --> 00:07:17.280 align:start position:0% it's important to remember that at the 00:07:17.280 --> 00:07:19.850 align:start position:0% it's important to remember that at the end<00:07:17.400> of<00:07:17.520> the<00:07:17.639> day<00:07:17.900> uh<00:07:18.900> like<00:07:19.139> companies<00:07:19.680> like 00:07:19.850 --> 00:07:19.860 align:start position:0% end of the day uh like companies like 00:07:19.860 --> 00:07:21.710 align:start position:0% end of the day uh like companies like surtora<00:07:20.759> or<00:07:20.940> like<00:07:21.120> you<00:07:21.240> know<00:07:21.360> formal 00:07:21.710 --> 00:07:21.720 align:start position:0% surtora or like you know formal 00:07:21.720 --> 00:07:23.870 align:start position:0% surtora or like you know formal verification<00:07:22.139> companies<00:07:22.680> or<00:07:22.979> like<00:07:23.639> any 00:07:23.870 --> 00:07:23.880 align:start position:0% verification companies or like any 00:07:23.880 --> 00:07:26.510 align:start position:0% verification companies or like any company<00:07:24.180> that<00:07:24.479> is<00:07:24.599> building<00:07:24.780> tools<00:07:25.259> for<00:07:25.520> uh 00:07:26.510 --> 00:07:26.520 align:start position:0% company that is building tools for uh 00:07:26.520 --> 00:07:28.909 align:start position:0% company that is building tools for uh verifying<00:07:27.120> smart<00:07:27.240> contracts<00:07:27.780> they<00:07:28.740> actually 00:07:28.909 --> 00:07:28.919 align:start position:0% verifying smart contracts they actually 00:07:28.919 --> 00:07:31.370 align:start position:0% verifying smart contracts they actually rely<00:07:29.280> on<00:07:29.460> a<00:07:29.580> very<00:07:29.699> fundamental<00:07:30.300> uh<00:07:30.960> concept 00:07:31.370 --> 00:07:31.380 align:start position:0% rely on a very fundamental uh concept 00:07:31.380 --> 00:07:34.129 align:start position:0% rely on a very fundamental uh concept and<00:07:31.860> I<00:07:32.099> think<00:07:32.220> that<00:07:32.580> even<00:07:33.060> though<00:07:33.360> this<00:07:33.720> field 00:07:34.129 --> 00:07:34.139 align:start position:0% and I think that even though this field 00:07:34.139 --> 00:07:36.529 align:start position:0% and I think that even though this field is<00:07:34.380> very<00:07:34.560> fast<00:07:34.680> moving<00:07:35.099> uh<00:07:35.819> the<00:07:36.000> fundamentals 00:07:36.529 --> 00:07:36.539 align:start position:0% is very fast moving uh the fundamentals 00:07:36.539 --> 00:07:38.809 align:start position:0% is very fast moving uh the fundamentals are<00:07:36.660> still<00:07:36.780> the<00:07:37.020> same<00:07:37.199> and<00:07:37.860> you<00:07:38.160> know<00:07:38.220> those 00:07:38.809 --> 00:07:38.819 align:start position:0% are still the same and you know those 00:07:38.819 --> 00:07:41.749 align:start position:0% are still the same and you know those ideas<00:07:39.180> uh<00:07:39.840> go<00:07:40.139> really<00:07:40.440> far<00:07:40.680> and<00:07:41.400> I'm<00:07:41.580> actually 00:07:41.749 --> 00:07:41.759 align:start position:0% ideas uh go really far and I'm actually 00:07:41.759 --> 00:07:44.029 align:start position:0% ideas uh go really far and I'm actually excited<00:07:42.180> I<00:07:42.419> think<00:07:42.599> that<00:07:42.960> we<00:07:43.560> should<00:07:43.740> be<00:07:43.860> able 00:07:44.029 --> 00:07:44.039 align:start position:0% excited I think that we should be able 00:07:44.039 --> 00:07:46.730 align:start position:0% excited I think that we should be able to<00:07:44.539> scale<00:07:45.539> some<00:07:45.780> of<00:07:45.900> these<00:07:46.080> techniques<00:07:46.440> uh 00:07:46.730 --> 00:07:46.740 align:start position:0% to scale some of these techniques uh 00:07:46.740 --> 00:07:48.890 align:start position:0% to scale some of these techniques uh pretty<00:07:46.979> well<00:07:47.160> to<00:07:47.580> some<00:07:47.819> of<00:07:48.000> the<00:07:48.240> more<00:07:48.479> recent 00:07:48.890 --> 00:07:48.900 align:start position:0% pretty well to some of the more recent 00:07:48.900 --> 00:07:50.270 align:start position:0% pretty well to some of the more recent uh 00:07:50.270 --> 00:07:50.280 align:start position:0% uh 00:07:50.280 --> 00:07:52.249 align:start position:0% uh Concepts<00:07:51.060> that<00:07:51.180> are<00:07:51.300> coming<00:07:51.419> around<00:07:51.660> in<00:07:52.080> this 00:07:52.249 --> 00:07:52.259 align:start position:0% Concepts that are coming around in this 00:07:52.259 --> 00:07:54.890 align:start position:0% Concepts that are coming around in this field<00:07:52.500> nice<00:07:53.220> okay<00:07:53.699> I'm<00:07:54.000> gonna<00:07:54.180> I'll<00:07:54.599> give<00:07:54.780> you 00:07:54.890 --> 00:07:54.900 align:start position:0% field nice okay I'm gonna I'll give you 00:07:54.900 --> 00:07:56.570 align:start position:0% field nice okay I'm gonna I'll give you the<00:07:55.020> next<00:07:55.199> question<00:07:55.500> but<00:07:55.860> let's<00:07:56.039> we'll<00:07:56.400> keep 00:07:56.570 --> 00:07:56.580 align:start position:0% the next question but let's we'll keep 00:07:56.580 --> 00:07:59.330 align:start position:0% the next question but let's we'll keep it<00:07:56.759> moving<00:07:57.259> uh<00:07:58.259> so 00:07:59.330 --> 00:07:59.340 align:start position:0% it moving uh so 00:07:59.340 --> 00:08:00.650 align:start position:0% it moving uh so yeah<00:07:59.819> so 00:08:00.650 --> 00:08:00.660 align:start position:0% yeah so 00:08:00.660 --> 00:08:02.870 align:start position:0% yeah so we're<00:08:01.020> done<00:08:01.199> with<00:08:01.319> softballs 00:08:02.870 --> 00:08:02.880 align:start position:0% we're done with softballs 00:08:02.880 --> 00:08:04.909 align:start position:0% we're done with softballs um<00:08:03.000> Jonathan<00:08:03.599> what<00:08:03.960> responsibility<00:08:04.560> do 00:08:04.909 --> 00:08:04.919 align:start position:0% um Jonathan what responsibility do 00:08:04.919 --> 00:08:07.490 align:start position:0% um Jonathan what responsibility do Auditors<00:08:05.340> bear<00:08:05.639> when<00:08:06.360> code<00:08:06.780> they've<00:08:07.139> reviewed 00:08:07.490 --> 00:08:07.500 align:start position:0% Auditors bear when code they've reviewed 00:08:07.500 --> 00:08:10.249 align:start position:0% Auditors bear when code they've reviewed has<00:08:07.919> been<00:08:08.160> exploited 00:08:10.249 --> 00:08:10.259 align:start position:0% has been exploited 00:08:10.259 --> 00:08:13.670 align:start position:0% has been exploited thanks<00:08:10.740> for<00:08:10.979> Daisy<00:08:11.699> hey 00:08:13.670 --> 00:08:13.680 align:start position:0% thanks for Daisy hey 00:08:13.680 --> 00:08:16.070 align:start position:0% thanks for Daisy hey nope<00:08:14.280> that's<00:08:14.460> targeted 00:08:16.070 --> 00:08:16.080 align:start position:0% nope that's targeted 00:08:16.080 --> 00:08:18.890 align:start position:0% nope that's targeted um<00:08:16.199> you<00:08:16.440> take<00:08:16.680> a<00:08:16.800> sip<00:08:16.979> of<00:08:17.099> water<00:08:17.220> for<00:08:17.520> yeah 00:08:18.890 --> 00:08:18.900 align:start position:0% um you take a sip of water for yeah 00:08:18.900 --> 00:08:20.930 align:start position:0% um you take a sip of water for yeah well<00:08:19.500> I<00:08:19.800> I<00:08:19.979> think 00:08:20.930 --> 00:08:20.940 align:start position:0% well I I think 00:08:20.940 --> 00:08:21.589 align:start position:0% well I I think um 00:08:21.589 --> 00:08:21.599 align:start position:0% um 00:08:21.599 --> 00:08:24.469 align:start position:0% um first<00:08:22.259> of<00:08:22.440> all<00:08:22.620> I<00:08:23.400> think 00:08:24.469 --> 00:08:24.479 align:start position:0% first of all I think 00:08:24.479 --> 00:08:28.850 align:start position:0% first of all I think all<00:08:25.319> of<00:08:25.500> us<00:08:25.680> because<00:08:26.039> we<00:08:27.020> uh<00:08:28.020> I<00:08:28.560> think 00:08:28.850 --> 00:08:28.860 align:start position:0% all of us because we uh I think 00:08:28.860 --> 00:08:30.529 align:start position:0% all of us because we uh I think everybody<00:08:29.039> up<00:08:29.400> here<00:08:29.520> we<00:08:29.759> take<00:08:29.940> our<00:08:30.120> work<00:08:30.240> so 00:08:30.529 --> 00:08:30.539 align:start position:0% everybody up here we take our work so 00:08:30.539 --> 00:08:32.570 align:start position:0% everybody up here we take our work so seriously<00:08:31.020> that<00:08:31.259> the<00:08:31.979> first<00:08:32.099> order<00:08:32.279> of 00:08:32.570 --> 00:08:32.580 align:start position:0% seriously that the first order of 00:08:32.580 --> 00:08:35.209 align:start position:0% seriously that the first order of responsibility<00:08:33.180> of<00:08:33.479> course<00:08:33.659> is<00:08:33.919> dealing<00:08:34.919> with 00:08:35.209 --> 00:08:35.219 align:start position:0% responsibility of course is dealing with 00:08:35.219 --> 00:08:38.750 align:start position:0% responsibility of course is dealing with the<00:08:35.760> issue<00:08:36.060> that's<00:08:36.360> found<00:08:36.860> and<00:08:37.860> I<00:08:38.219> think<00:08:38.399> that 00:08:38.750 --> 00:08:38.760 align:start position:0% the issue that's found and I think that 00:08:38.760 --> 00:08:41.389 align:start position:0% the issue that's found and I think that I<00:08:39.120> know<00:08:39.180> we<00:08:39.419> at<00:08:39.599> open<00:08:39.719> Zeppelin<00:08:40.260> make<00:08:41.039> every 00:08:41.389 --> 00:08:41.399 align:start position:0% I know we at open Zeppelin make every 00:08:41.399 --> 00:08:43.209 align:start position:0% I know we at open Zeppelin make every effort<00:08:41.880> if 00:08:43.209 --> 00:08:43.219 align:start position:0% effort if 00:08:43.219 --> 00:08:46.010 align:start position:0% effort if we've<00:08:44.219> had<00:08:44.279> situations<00:08:44.880> I'm<00:08:45.540> not<00:08:45.839> going<00:08:45.959> to 00:08:46.010 --> 00:08:46.020 align:start position:0% we've had situations I'm not going to 00:08:46.020 --> 00:08:47.449 align:start position:0% we've had situations I'm not going to say<00:08:46.140> we've<00:08:46.440> had<00:08:46.560> situations<00:08:46.920> where<00:08:47.220> things 00:08:47.449 --> 00:08:47.459 align:start position:0% say we've had situations where things 00:08:47.459 --> 00:08:49.430 align:start position:0% say we've had situations where things we've<00:08:47.700> missed<00:08:48.000> have<00:08:48.120> been<00:08:48.300> found<00:08:48.480> but 00:08:49.430 --> 00:08:49.440 align:start position:0% we've missed have been found but 00:08:49.440 --> 00:08:52.670 align:start position:0% we've missed have been found but customers<00:08:50.279> we<00:08:50.519> work<00:08:50.760> with<00:08:51.000> maybe<00:08:51.540> have<00:08:52.440> a 00:08:52.670 --> 00:08:52.680 align:start position:0% customers we work with maybe have a 00:08:52.680 --> 00:08:56.509 align:start position:0% customers we work with maybe have a situation<00:08:53.160> arise<00:08:53.880> and<00:08:54.800> you<00:08:55.800> are<00:08:55.920> a<00:08:56.160> trusted 00:08:56.509 --> 00:08:56.519 align:start position:0% situation arise and you are a trusted 00:08:56.519 --> 00:08:58.310 align:start position:0% situation arise and you are a trusted security<00:08:56.760> advisor<00:08:57.420> to<00:08:57.600> them<00:08:57.779> you're<00:08:58.019> going<00:08:58.200> to 00:08:58.310 --> 00:08:58.320 align:start position:0% security advisor to them you're going to 00:08:58.320 --> 00:09:00.410 align:start position:0% security advisor to them you're going to Rally<00:08:58.560> to<00:08:58.860> help<00:08:58.980> them<00:08:59.220> in<00:08:59.399> the<00:08:59.580> situation<00:09:00.000> and 00:09:00.410 --> 00:09:00.420 align:start position:0% Rally to help them in the situation and 00:09:00.420 --> 00:09:02.930 align:start position:0% Rally to help them in the situation and that<00:09:00.660> may<00:09:00.839> be<00:09:01.080> in<00:09:01.500> discussing<00:09:01.980> what<00:09:02.640> are<00:09:02.820> the 00:09:02.930 --> 00:09:02.940 align:start position:0% that may be in discussing what are the 00:09:02.940 --> 00:09:05.210 align:start position:0% that may be in discussing what are the potential<00:09:03.300> fixes<00:09:03.779> in<00:09:03.959> reviewing<00:09:04.440> fixes<00:09:04.920> and 00:09:05.210 --> 00:09:05.220 align:start position:0% potential fixes in reviewing fixes and 00:09:05.220 --> 00:09:07.570 align:start position:0% potential fixes in reviewing fixes and even<00:09:05.459> talking<00:09:05.820> about<00:09:06.120> public<00:09:06.420> Communications 00:09:07.570 --> 00:09:07.580 align:start position:0% even talking about public Communications 00:09:07.580 --> 00:09:11.870 align:start position:0% even talking about public Communications and<00:09:08.580> that<00:09:09.060> is<00:09:09.240> a<00:09:09.660> uh<00:09:10.380> I<00:09:10.560> think<00:09:10.680> if<00:09:10.920> you<00:09:11.100> are<00:09:11.459> with 00:09:11.870 --> 00:09:11.880 align:start position:0% and that is a uh I think if you are with 00:09:11.880 --> 00:09:15.410 align:start position:0% and that is a uh I think if you are with a<00:09:12.839> trusted<00:09:13.500> you<00:09:14.339> know<00:09:14.399> we<00:09:14.640> view<00:09:15.060> these 00:09:15.410 --> 00:09:15.420 align:start position:0% a trusted you know we view these 00:09:15.420 --> 00:09:17.030 align:start position:0% a trusted you know we view these relationships<00:09:15.959> as<00:09:16.140> Partnerships<00:09:16.680> then 00:09:17.030 --> 00:09:17.040 align:start position:0% relationships as Partnerships then 00:09:17.040 --> 00:09:18.769 align:start position:0% relationships as Partnerships then that's<00:09:17.339> what<00:09:17.580> what<00:09:17.880> we're<00:09:18.180> going<00:09:18.360> to<00:09:18.480> try<00:09:18.600> to 00:09:18.769 --> 00:09:18.779 align:start position:0% that's what what we're going to try to 00:09:18.779 --> 00:09:19.910 align:start position:0% that's what what we're going to try to do 00:09:19.910 --> 00:09:19.920 align:start position:0% do 00:09:19.920 --> 00:09:21.829 align:start position:0% do um I<00:09:20.160> think<00:09:20.279> that<00:09:20.580> in<00:09:20.880> the<00:09:21.060> case<00:09:21.240> in<00:09:21.660> a 00:09:21.829 --> 00:09:21.839 align:start position:0% um I think that in the case in a 00:09:21.839 --> 00:09:25.009 align:start position:0% um I think that in the case in a specific<00:09:22.019> case<00:09:22.380> where<00:09:23.240> something<00:09:24.240> is<00:09:24.600> missed 00:09:25.009 --> 00:09:25.019 align:start position:0% specific case where something is missed 00:09:25.019 --> 00:09:26.990 align:start position:0% specific case where something is missed in<00:09:25.140> an<00:09:25.320> audit<00:09:25.620> which<00:09:25.920> sometimes 00:09:26.990 --> 00:09:27.000 align:start position:0% in an audit which sometimes 00:09:27.000 --> 00:09:29.530 align:start position:0% in an audit which sometimes um<00:09:27.060> like<00:09:27.480> we've<00:09:27.839> had<00:09:27.959> some<00:09:28.200> situations<00:09:28.680> where 00:09:29.530 --> 00:09:29.540 align:start position:0% um like we've had some situations where 00:09:29.540 --> 00:09:33.530 align:start position:0% um like we've had some situations where uh<00:09:30.540> we'll<00:09:31.200> we'll<00:09:31.440> do<00:09:31.860> an<00:09:32.040> audit<00:09:32.399> and<00:09:33.060> then 00:09:33.530 --> 00:09:33.540 align:start position:0% uh we'll we'll do an audit and then 00:09:33.540 --> 00:09:38.090 align:start position:0% uh we'll we'll do an audit and then before<00:09:34.519> thankfully<00:09:35.600> pre-release<00:09:36.740> an<00:09:37.740> issue 00:09:38.090 --> 00:09:38.100 align:start position:0% before thankfully pre-release an issue 00:09:38.100 --> 00:09:40.190 align:start position:0% before thankfully pre-release an issue is<00:09:38.279> discovered<00:09:38.880> that<00:09:39.360> was<00:09:39.540> missed<00:09:39.899> in<00:09:40.019> the 00:09:40.190 --> 00:09:40.200 align:start position:0% is discovered that was missed in the 00:09:40.200 --> 00:09:43.690 align:start position:0% is discovered that was missed in the audit<00:09:40.440> maybe<00:09:40.680> because<00:09:41.040> there<00:09:41.820> was<00:09:42.000> uh 00:09:43.690 --> 00:09:43.700 align:start position:0% audit maybe because there was uh 00:09:43.700 --> 00:09:46.670 align:start position:0% audit maybe because there was uh another<00:09:44.700> you<00:09:45.300> know<00:09:45.360> set<00:09:45.720> of<00:09:45.839> eyes<00:09:46.019> on<00:09:46.260> it<00:09:46.380> or 00:09:46.670 --> 00:09:46.680 align:start position:0% another you know set of eyes on it or 00:09:46.680 --> 00:09:48.949 align:start position:0% another you know set of eyes on it or maybe<00:09:46.860> there<00:09:47.100> was<00:09:47.220> internal<00:09:47.700> testing<00:09:48.180> and<00:09:48.839> in 00:09:48.949 --> 00:09:48.959 align:start position:0% maybe there was internal testing and in 00:09:48.959 --> 00:09:51.170 align:start position:0% maybe there was internal testing and in that<00:09:49.140> case<00:09:49.320> uh<00:09:50.040> we<00:09:50.339> always<00:09:50.459> view<00:09:50.880> our 00:09:51.170 --> 00:09:51.180 align:start position:0% that case uh we always view our 00:09:51.180 --> 00:09:53.690 align:start position:0% that case uh we always view our responsibility<00:09:51.839> is<00:09:52.380> to<00:09:52.620> do<00:09:52.800> a<00:09:53.160> very<00:09:53.279> thorough 00:09:53.690 --> 00:09:53.700 align:start position:0% responsibility is to do a very thorough 00:09:53.700 --> 00:09:55.190 align:start position:0% responsibility is to do a very thorough postmortem 00:09:55.190 --> 00:09:55.200 align:start position:0% postmortem 00:09:55.200 --> 00:09:57.350 align:start position:0% postmortem on<00:09:55.920> what<00:09:56.459> happened 00:09:57.350 --> 00:09:57.360 align:start position:0% on what happened 00:09:57.360 --> 00:10:00.530 align:start position:0% on what happened exactly<00:09:58.260> what<00:09:58.560> was<00:09:58.740> found<00:09:59.100> have<00:10:00.060> our<00:10:00.360> team 00:10:00.530 --> 00:10:00.540 align:start position:0% exactly what was found have our team 00:10:00.540 --> 00:10:02.750 align:start position:0% exactly what was found have our team analyze<00:10:01.440> itself<00:10:01.800> as<00:10:02.100> well<00:10:02.220> as<00:10:02.339> get<00:10:02.519> other 00:10:02.750 --> 00:10:02.760 align:start position:0% analyze itself as well as get other 00:10:02.760 --> 00:10:06.050 align:start position:0% analyze itself as well as get other people<00:10:03.000> in<00:10:03.360> our<00:10:03.540> team<00:10:03.720> and<00:10:04.440> other<00:10:05.040> get<00:10:05.760> the 00:10:06.050 --> 00:10:06.060 align:start position:0% people in our team and other get the 00:10:06.060 --> 00:10:08.329 align:start position:0% people in our team and other get the customer<00:10:06.420> involved<00:10:07.140> so<00:10:07.620> that<00:10:07.800> we<00:10:07.980> can<00:10:08.160> all 00:10:08.329 --> 00:10:08.339 align:start position:0% customer involved so that we can all 00:10:08.339 --> 00:10:10.910 align:start position:0% customer involved so that we can all learn<00:10:08.640> from<00:10:09.000> that<00:10:09.240> and<00:10:09.720> figure<00:10:09.959> out<00:10:10.260> and 00:10:10.910 --> 00:10:10.920 align:start position:0% learn from that and figure out and 00:10:10.920 --> 00:10:13.670 align:start position:0% learn from that and figure out and explain<00:10:11.399> to<00:10:11.760> ourselves<00:10:12.180> and<00:10:12.720> improve<00:10:13.200> our 00:10:13.670 --> 00:10:13.680 align:start position:0% explain to ourselves and improve our 00:10:13.680 --> 00:10:15.410 align:start position:0% explain to ourselves and improve our processes<00:10:14.160> going<00:10:14.459> forward<00:10:14.760> so<00:10:15.180> I<00:10:15.300> think 00:10:15.410 --> 00:10:15.420 align:start position:0% processes going forward so I think 00:10:15.420 --> 00:10:19.310 align:start position:0% processes going forward so I think that's<00:10:15.720> the<00:10:16.440> very<00:10:16.800> common<00:10:17.040> uh<00:10:17.760> approach<00:10:18.540> so<00:10:19.200> so 00:10:19.310 --> 00:10:19.320 align:start position:0% that's the very common uh approach so so 00:10:19.320 --> 00:10:22.430 align:start position:0% that's the very common uh approach so so we've<00:10:19.560> heard<00:10:19.740> from<00:10:19.980> Jonathan<00:10:20.519> that<00:10:20.959> it's<00:10:21.959> I<00:10:22.260> I 00:10:22.430 --> 00:10:22.440 align:start position:0% we've heard from Jonathan that it's I I 00:10:22.440 --> 00:10:24.470 align:start position:0% we've heard from Jonathan that it's I I think<00:10:22.620> this<00:10:22.740> is<00:10:22.860> just<00:10:22.980> like<00:10:23.040> late<00:10:23.339> to<00:10:23.580> the 00:10:24.470 --> 00:10:24.480 align:start position:0% think this is just like late to the 00:10:24.480 --> 00:10:27.350 align:start position:0% think this is just like late to the preface<00:10:24.899> on<00:10:25.440> the<00:10:25.620> same<00:10:25.740> topic<00:10:26.100> but<00:10:26.519> Jonathan 00:10:27.350 --> 00:10:27.360 align:start position:0% preface on the same topic but Jonathan 00:10:27.360 --> 00:10:30.110 align:start position:0% preface on the same topic but Jonathan has<00:10:27.600> been<00:10:27.899> open<00:10:28.080> that<00:10:28.740> a<00:10:29.279> top-tier<00:10:29.640> auditor 00:10:30.110 --> 00:10:30.120 align:start position:0% has been open that a top-tier auditor 00:10:30.120 --> 00:10:31.790 align:start position:0% has been open that a top-tier auditor can<00:10:30.480> miss<00:10:30.720> something 00:10:31.790 --> 00:10:31.800 align:start position:0% can miss something 00:10:31.800 --> 00:10:34.610 align:start position:0% can miss something and<00:10:32.519> so<00:10:32.940> you're<00:10:33.420> lucky<00:10:33.779> right<00:10:34.080> like<00:10:34.320> it<00:10:34.440> got 00:10:34.610 --> 00:10:34.620 align:start position:0% and so you're lucky right like it got 00:10:34.620 --> 00:10:37.190 align:start position:0% and so you're lucky right like it got caught<00:10:34.860> before<00:10:35.100> it<00:10:35.399> hit<00:10:35.519> production<00:10:36.120> that<00:10:37.080> can 00:10:37.190 --> 00:10:37.200 align:start position:0% caught before it hit production that can 00:10:37.200 --> 00:10:38.750 align:start position:0% caught before it hit production that can happen<00:10:37.380> to<00:10:37.500> anyone<00:10:37.800> so<00:10:38.040> let's<00:10:38.220> like<00:10:38.399> put<00:10:38.580> that 00:10:38.750 --> 00:10:38.760 align:start position:0% happen to anyone so let's like put that 00:10:38.760 --> 00:10:42.170 align:start position:0% happen to anyone so let's like put that out<00:10:38.940> there<00:10:39.600> is<00:10:40.080> anybody<00:10:40.440> on<00:10:40.740> the<00:10:40.920> stage<00:10:41.279> like 00:10:42.170 --> 00:10:42.180 align:start position:0% out there is anybody on the stage like 00:10:42.180 --> 00:10:44.810 align:start position:0% out there is anybody on the stage like actually<00:10:42.540> had<00:10:42.959> something<00:10:43.320> they've<00:10:43.740> added<00:10:44.040> be 00:10:44.810 --> 00:10:44.820 align:start position:0% actually had something they've added be 00:10:44.820 --> 00:10:46.790 align:start position:0% actually had something they've added be exploited<00:10:45.360> in<00:10:45.600> a<00:10:45.839> significant<00:10:46.260> way<00:10:46.440> I'm 00:10:46.790 --> 00:10:46.800 align:start position:0% exploited in a significant way I'm 00:10:46.800 --> 00:10:48.949 align:start position:0% exploited in a significant way I'm curious 00:10:48.949 --> 00:10:48.959 align:start position:0% curious 00:10:48.959 --> 00:10:51.590 align:start position:0% curious not<00:10:49.440> really<00:10:49.560> but<00:10:49.800> we've<00:10:50.100> had<00:10:50.459> stuff<00:10:51.120> being 00:10:51.590 --> 00:10:51.600 align:start position:0% not really but we've had stuff being 00:10:51.600 --> 00:10:53.690 align:start position:0% not really but we've had stuff being disclosed<00:10:52.440> after<00:10:52.620> it's<00:10:52.860> in<00:10:53.040> production<00:10:53.339> yeah 00:10:53.690 --> 00:10:53.700 align:start position:0% disclosed after it's in production yeah 00:10:53.700 --> 00:10:56.449 align:start position:0% disclosed after it's in production yeah like<00:10:54.240> I<00:10:54.540> I<00:10:54.660> think<00:10:54.839> that<00:10:54.959> like<00:10:55.200> we 00:10:56.449 --> 00:10:56.459 align:start position:0% like I I think that like we 00:10:56.459 --> 00:10:58.069 align:start position:0% like I I think that like we establishing<00:10:57.180> and<00:10:57.360> we've<00:10:57.540> said<00:10:57.720> this<00:10:57.899> many 00:10:58.069 --> 00:10:58.079 align:start position:0% establishing and we've said this many 00:10:58.079 --> 00:10:59.990 align:start position:0% establishing and we've said this many many<00:10:58.260> times<00:10:58.440> we're<00:10:58.680> not<00:10:58.920> insurance<00:10:59.339> companies 00:10:59.990 --> 00:11:00.000 align:start position:0% many times we're not insurance companies 00:11:00.000 --> 00:11:03.050 align:start position:0% many times we're not insurance companies right<00:11:00.480> so<00:11:01.019> that's<00:11:01.380> the<00:11:01.560> Baseline<00:11:02.040> but<00:11:02.579> there's 00:11:03.050 --> 00:11:03.060 align:start position:0% right so that's the Baseline but there's 00:11:03.060 --> 00:11:06.290 align:start position:0% right so that's the Baseline but there's an<00:11:03.480> ethical<00:11:03.959> and<00:11:04.620> moral<00:11:04.980> code<00:11:05.160> that<00:11:05.399> like 00:11:06.290 --> 00:11:06.300 align:start position:0% an ethical and moral code that like 00:11:06.300 --> 00:11:09.110 align:start position:0% an ethical and moral code that like that<00:11:07.260> we<00:11:07.440> uphold<00:11:07.800> to<00:11:08.040> and<00:11:08.220> so<00:11:08.640> if<00:11:08.880> something 00:11:09.110 --> 00:11:09.120 align:start position:0% that we uphold to and so if something 00:11:09.120 --> 00:11:11.090 align:start position:0% that we uphold to and so if something happens<00:11:09.420> obviously<00:11:10.140> this<00:11:10.320> is<00:11:10.500> also<00:11:10.740> Case<00:11:10.920> by 00:11:11.090 --> 00:11:11.100 align:start position:0% happens obviously this is also Case by 00:11:11.100 --> 00:11:12.769 align:start position:0% happens obviously this is also Case by case<00:11:11.279> on<00:11:11.579> a<00:11:11.700> case-by-case<00:11:12.180> basis<00:11:12.480> it<00:11:12.660> should 00:11:12.769 --> 00:11:12.779 align:start position:0% case on a case-by-case basis it should 00:11:12.779 --> 00:11:14.150 align:start position:0% case on a case-by-case basis it should be<00:11:12.899> analyzed<00:11:13.320> differently<00:11:13.560> because<00:11:13.740> if<00:11:13.920> it's 00:11:14.150 --> 00:11:14.160 align:start position:0% be analyzed differently because if it's 00:11:14.160 --> 00:11:16.370 align:start position:0% be analyzed differently because if it's if<00:11:14.700> it's<00:11:15.120> our 00:11:16.370 --> 00:11:16.380 align:start position:0% if it's our 00:11:16.380 --> 00:11:18.530 align:start position:0% if it's our the<00:11:16.920> if<00:11:17.279> the<00:11:17.459> problem<00:11:17.579> was<00:11:17.760> created<00:11:18.060> by<00:11:18.240> us 00:11:18.530 --> 00:11:18.540 align:start position:0% the if the problem was created by us 00:11:18.540 --> 00:11:20.810 align:start position:0% the if the problem was created by us specifically<00:11:19.079> then<00:11:19.440> we<00:11:19.920> might<00:11:20.040> react<00:11:20.339> one<00:11:20.579> way 00:11:20.810 --> 00:11:20.820 align:start position:0% specifically then we might react one way 00:11:20.820 --> 00:11:23.449 align:start position:0% specifically then we might react one way whether<00:11:21.180> if<00:11:21.480> if<00:11:21.779> the<00:11:22.260> if<00:11:22.680> there<00:11:22.860> it<00:11:23.100> was<00:11:23.279> just 00:11:23.449 --> 00:11:23.459 align:start position:0% whether if if the if there it was just 00:11:23.459 --> 00:11:25.430 align:start position:0% whether if if the if there it was just like<00:11:23.700> a<00:11:23.940> Miss<00:11:24.360> we<00:11:24.660> might<00:11:24.839> react<00:11:25.140> some<00:11:25.320> other 00:11:25.430 --> 00:11:25.440 align:start position:0% like a Miss we might react some other 00:11:25.440 --> 00:11:27.949 align:start position:0% like a Miss we might react some other way<00:11:25.680> but<00:11:26.279> at<00:11:26.519> the<00:11:26.640> end<00:11:26.760> of<00:11:26.940> the<00:11:27.060> day 00:11:27.949 --> 00:11:27.959 align:start position:0% way but at the end of the day 00:11:27.959 --> 00:11:30.230 align:start position:0% way but at the end of the day we'll<00:11:28.860> try<00:11:29.040> our<00:11:29.279> best<00:11:29.459> but<00:11:29.880> we're<00:11:30.000> not 00:11:30.230 --> 00:11:30.240 align:start position:0% we'll try our best but we're not 00:11:30.240 --> 00:11:32.630 align:start position:0% we'll try our best but we're not obligated<00:11:30.660> to<00:11:30.899> anything<00:11:31.140> right<00:11:31.560> nor<00:11:32.040> can<00:11:32.459> we 00:11:32.630 --> 00:11:32.640 align:start position:0% obligated to anything right nor can we 00:11:32.640 --> 00:11:35.090 align:start position:0% obligated to anything right nor can we be<00:11:32.760> because<00:11:33.000> that<00:11:33.420> actually<00:11:34.019> destroys<00:11:34.680> the 00:11:35.090 --> 00:11:35.100 align:start position:0% be because that actually destroys the 00:11:35.100 --> 00:11:38.930 align:start position:0% be because that actually destroys the entire<00:11:35.339> relationship 00:11:38.930 --> 00:11:38.940 align:start position:0% 00:11:38.940 --> 00:11:40.670 align:start position:0% well<00:11:39.420> I'll<00:11:39.660> go<00:11:39.839> because<00:11:40.019> I'm<00:11:40.200> just<00:11:40.380> gonna<00:11:40.500> just 00:11:40.670 --> 00:11:40.680 align:start position:0% well I'll go because I'm just gonna just 00:11:40.680 --> 00:11:43.310 align:start position:0% well I'll go because I'm just gonna just jump<00:11:40.800> onto<00:11:41.160> it<00:11:41.279> uh<00:11:41.700> we<00:11:42.000> we<00:11:42.180> actually<00:11:42.420> don't 00:11:43.310 --> 00:11:43.320 align:start position:0% jump onto it uh we we actually don't 00:11:43.320 --> 00:11:45.230 align:start position:0% jump onto it uh we we actually don't I<00:11:43.740> don't<00:11:44.040> think<00:11:44.160> that<00:11:44.279> we<00:11:44.459> have<00:11:44.700> a<00:11:45.000> different 00:11:45.230 --> 00:11:45.240 align:start position:0% I don't think that we have a different 00:11:45.240 --> 00:11:46.550 align:start position:0% I don't think that we have a different way<00:11:45.540> I<00:11:45.720> liked<00:11:45.959> what<00:11:46.019> you<00:11:46.140> said<00:11:46.320> about<00:11:46.440> the 00:11:46.550 --> 00:11:46.560 align:start position:0% way I liked what you said about the 00:11:46.560 --> 00:11:47.870 align:start position:0% way I liked what you said about the moral<00:11:46.800> responsibility<00:11:47.160> I<00:11:47.459> think<00:11:47.579> it's<00:11:47.640> really 00:11:47.870 --> 00:11:47.880 align:start position:0% moral responsibility I think it's really 00:11:47.880 --> 00:11:50.449 align:start position:0% moral responsibility I think it's really it's<00:11:48.779> really<00:11:48.959> important<00:11:49.800> um<00:11:49.860> I<00:11:49.980> I<00:11:50.160> don't<00:11:50.339> think 00:11:50.449 --> 00:11:50.459 align:start position:0% it's really important um I I don't think 00:11:50.459 --> 00:11:52.610 align:start position:0% it's really important um I I don't think that<00:11:50.640> we<00:11:50.820> have<00:11:50.940> a<00:11:51.120> different 00:11:52.610 --> 00:11:52.620 align:start position:0% that we have a different 00:11:52.620 --> 00:11:54.410 align:start position:0% that we have a different um<00:11:52.740> process<00:11:53.399> we<00:11:53.700> have<00:11:53.820> we<00:11:54.060> have<00:11:54.180> a<00:11:54.300> pretty 00:11:54.410 --> 00:11:54.420 align:start position:0% um process we have we have a pretty 00:11:54.420 --> 00:11:57.290 align:start position:0% um process we have we have a pretty stringent<00:11:54.839> process<00:11:55.200> to<00:11:55.560> to<00:11:55.740> determine 00:11:57.290 --> 00:11:57.300 align:start position:0% stringent process to to determine 00:11:57.300 --> 00:11:58.190 align:start position:0% stringent process to to determine um 00:11:58.190 --> 00:11:58.200 align:start position:0% um 00:11:58.200 --> 00:12:00.889 align:start position:0% um whether<00:11:58.800> whether<00:11:59.579> something<00:11:59.820> was<00:12:00.060> missed<00:12:00.420> but 00:12:00.889 --> 00:12:00.899 align:start position:0% whether whether something was missed but 00:12:00.899 --> 00:12:03.650 align:start position:0% whether whether something was missed but but<00:12:01.079> much<00:12:01.380> more<00:12:01.560> important<00:12:01.920> is<00:12:02.339> what<00:12:03.240> happened 00:12:03.650 --> 00:12:03.660 align:start position:0% but much more important is what happened 00:12:03.660 --> 00:12:06.290 align:start position:0% but much more important is what happened and<00:12:04.079> how<00:12:04.200> can<00:12:04.320> we<00:12:04.500> help<00:12:04.680> and<00:12:05.519> how<00:12:05.640> can<00:12:05.760> we<00:12:05.940> reach 00:12:06.290 --> 00:12:06.300 align:start position:0% and how can we help and how can we reach 00:12:06.300 --> 00:12:08.210 align:start position:0% and how can we help and how can we reach out<00:12:06.420> proactively<00:12:07.140> they're<00:12:07.800> going<00:12:07.980> to<00:12:08.040> be<00:12:08.100> an 00:12:08.210 --> 00:12:08.220 align:start position:0% out proactively they're going to be an 00:12:08.220 --> 00:12:09.410 align:start position:0% out proactively they're going to be an incident<00:12:08.459> response<00:12:08.880> mode<00:12:09.000> they're<00:12:09.180> going<00:12:09.360> to 00:12:09.410 --> 00:12:09.420 align:start position:0% incident response mode they're going to 00:12:09.420 --> 00:12:10.910 align:start position:0% incident response mode they're going to be<00:12:09.540> their<00:12:09.839> hair's<00:12:10.200> on<00:12:10.320> fire<00:12:10.440> there's<00:12:10.680> going<00:12:10.860> to 00:12:10.910 --> 00:12:10.920 align:start position:0% be their hair's on fire there's going to 00:12:10.920 --> 00:12:12.650 align:start position:0% be their hair's on fire there's going to be<00:12:10.980> media<00:12:11.279> involvement<00:12:11.640> they're<00:12:11.880> they're<00:12:12.240> in 00:12:12.650 --> 00:12:12.660 align:start position:0% be media involvement they're they're in 00:12:12.660 --> 00:12:14.810 align:start position:0% be media involvement they're they're in a<00:12:12.779> world<00:12:12.899> of<00:12:13.019> hurt<00:12:13.140> a<00:12:13.980> lot<00:12:14.160> of<00:12:14.220> us<00:12:14.339> at<00:12:14.459> trail<00:12:14.640> of 00:12:14.810 --> 00:12:14.820 align:start position:0% a world of hurt a lot of us at trail of 00:12:14.820 --> 00:12:15.889 align:start position:0% a world of hurt a lot of us at trail of bits<00:12:15.120> have<00:12:15.240> worked<00:12:15.480> in<00:12:15.600> the<00:12:15.720> incident 00:12:15.889 --> 00:12:15.899 align:start position:0% bits have worked in the incident 00:12:15.899 --> 00:12:18.170 align:start position:0% bits have worked in the incident response<00:12:16.320> field<00:12:16.380> so<00:12:16.620> we're<00:12:16.860> we're<00:12:17.279> very 00:12:18.170 --> 00:12:18.180 align:start position:0% response field so we're we're very 00:12:18.180 --> 00:12:20.750 align:start position:0% response field so we're we're very accustomed<00:12:18.779> to<00:12:18.959> understanding<00:12:19.800> what<00:12:20.640> they 00:12:20.750 --> 00:12:20.760 align:start position:0% accustomed to understanding what they 00:12:20.760 --> 00:12:22.850 align:start position:0% accustomed to understanding what they need<00:12:20.880> to<00:12:21.000> do<00:12:21.120> right<00:12:21.360> now<00:12:21.600> uh<00:12:22.260> to<00:12:22.560> stop<00:12:22.680> the 00:12:22.850 --> 00:12:22.860 align:start position:0% need to do right now uh to stop the 00:12:22.860 --> 00:12:24.590 align:start position:0% need to do right now uh to stop the burning<00:12:23.160> to<00:12:23.339> stop<00:12:23.459> the<00:12:23.579> leaking<00:12:23.820> and<00:12:24.060> and<00:12:24.240> get 00:12:24.590 --> 00:12:24.600 align:start position:0% burning to stop the leaking and and get 00:12:24.600 --> 00:12:26.870 align:start position:0% burning to stop the leaking and and get things<00:12:24.779> done<00:12:24.959> so<00:12:25.320> our<00:12:25.740> first<00:12:25.920> reaction<00:12:26.279> is<00:12:26.519> to 00:12:26.870 --> 00:12:26.880 align:start position:0% things done so our first reaction is to 00:12:26.880 --> 00:12:30.410 align:start position:0% things done so our first reaction is to to<00:12:27.500> refresh<00:12:28.500> ourselves<00:12:28.800> as<00:12:28.980> to<00:12:29.220> what<00:12:29.640> we<00:12:30.300> know 00:12:30.410 --> 00:12:30.420 align:start position:0% to refresh ourselves as to what we know 00:12:30.420 --> 00:12:33.829 align:start position:0% to refresh ourselves as to what we know about<00:12:30.600> this<00:12:31.079> project<00:12:31.279> and<00:12:32.279> then<00:12:32.519> uh 00:12:33.829 --> 00:12:33.839 align:start position:0% about this project and then uh 00:12:33.839 --> 00:12:36.470 align:start position:0% about this project and then uh reach<00:12:34.560> out<00:12:34.680> to<00:12:34.980> try<00:12:35.100> to<00:12:35.399> offer<00:12:35.760> as<00:12:36.360> much 00:12:36.470 --> 00:12:36.480 align:start position:0% reach out to try to offer as much 00:12:36.480 --> 00:12:38.690 align:start position:0% reach out to try to offer as much assistance<00:12:36.899> as<00:12:37.079> we<00:12:37.200> can<00:12:37.320> I'm<00:12:37.740> very<00:12:38.579> very 00:12:38.690 --> 00:12:38.700 align:start position:0% assistance as we can I'm very very 00:12:38.700 --> 00:12:40.490 align:start position:0% assistance as we can I'm very very pleased<00:12:39.120> to<00:12:39.300> say<00:12:39.480> that<00:12:39.720> the<00:12:40.019> entire<00:12:40.200> Rec 00:12:40.490 --> 00:12:40.500 align:start position:0% pleased to say that the entire Rec 00:12:40.500 --> 00:12:41.930 align:start position:0% pleased to say that the entire Rec leaderboard<00:12:40.920> does<00:12:41.100> not<00:12:41.220> have<00:12:41.279> our<00:12:41.459> name<00:12:41.640> on<00:12:41.820> it 00:12:41.930 --> 00:12:41.940 align:start position:0% leaderboard does not have our name on it 00:12:41.940 --> 00:12:44.449 align:start position:0% leaderboard does not have our name on it today<00:12:42.480> that<00:12:43.200> that<00:12:43.380> will<00:12:43.620> change<00:12:43.800> but<00:12:44.160> you<00:12:44.399> know 00:12:44.449 --> 00:12:44.459 align:start position:0% today that that will change but you know 00:12:44.459 --> 00:12:46.190 align:start position:0% today that that will change but you know as<00:12:44.639> of<00:12:44.760> right<00:12:44.940> now<00:12:45.120> but<00:12:45.300> but<00:12:45.540> this<00:12:45.899> is<00:12:46.019> a 00:12:46.190 --> 00:12:46.200 align:start position:0% as of right now but but this is a 00:12:46.200 --> 00:12:47.449 align:start position:0% as of right now but but this is a process<00:12:46.380> that<00:12:46.560> we<00:12:46.740> take<00:12:46.860> very<00:12:47.040> seriously 00:12:47.449 --> 00:12:47.459 align:start position:0% process that we take very seriously 00:12:47.459 --> 00:12:51.590 align:start position:0% process that we take very seriously because<00:12:48.320> uh<00:12:49.320> it<00:12:49.740> it<00:12:49.920> can<00:12:50.160> happen<00:12:50.399> there<00:12:51.360> are<00:12:51.480> no 00:12:51.590 --> 00:12:51.600 align:start position:0% because uh it it can happen there are no 00:12:51.600 --> 00:12:54.110 align:start position:0% because uh it it can happen there are no guarantees<00:12:52.019> in<00:12:52.200> audits<00:12:52.620> we<00:12:52.800> we<00:12:53.100> always<00:12:53.459> do<00:12:53.940> our 00:12:54.110 --> 00:12:54.120 align:start position:0% guarantees in audits we we always do our 00:12:54.120 --> 00:12:58.009 align:start position:0% guarantees in audits we we always do our very<00:12:54.240> best<00:12:54.540> but<00:12:55.079> I<00:12:55.620> think<00:12:56.240> to<00:12:57.240> stick<00:12:57.420> with<00:12:57.779> the 00:12:58.009 --> 00:12:58.019 align:start position:0% very best but I think to stick with the 00:12:58.019 --> 00:12:59.569 align:start position:0% very best but I think to stick with the customer<00:12:58.200> when<00:12:58.680> they're<00:12:58.860> in<00:12:58.980> a<00:12:59.160> bad<00:12:59.279> time<00:12:59.399> as 00:12:59.569 --> 00:12:59.579 align:start position:0% customer when they're in a bad time as 00:12:59.579 --> 00:13:01.129 align:start position:0% customer when they're in a bad time as well<00:12:59.760> as<00:12:59.820> when<00:13:00.000> they're<00:13:00.180> in<00:13:00.300> a<00:13:00.420> good<00:13:00.540> time<00:13:00.660> is 00:13:01.129 --> 00:13:01.139 align:start position:0% well as when they're in a good time is 00:13:01.139 --> 00:13:03.530 align:start position:0% well as when they're in a good time is the<00:13:01.320> most<00:13:01.500> important<00:13:01.860> thing<00:13:01.980> sorry<00:13:02.820> Jenna 00:13:03.530 --> 00:13:03.540 align:start position:0% the most important thing sorry Jenna 00:13:03.540 --> 00:13:05.449 align:start position:0% the most important thing sorry Jenna just<00:13:03.660> give<00:13:03.839> us<00:13:04.019> like<00:13:04.200> an<00:13:04.440> insight<00:13:04.860> into<00:13:05.220> what 00:13:05.449 --> 00:13:05.459 align:start position:0% just give us like an insight into what 00:13:05.459 --> 00:13:07.730 align:start position:0% just give us like an insight into what that<00:13:05.639> process<00:13:06.000> looks<00:13:06.360> like<00:13:06.480> like<00:13:06.959> just<00:13:07.260> one<00:13:07.500> or 00:13:07.730 --> 00:13:07.740 align:start position:0% that process looks like like just one or 00:13:07.740 --> 00:13:11.090 align:start position:0% that process looks like like just one or two<00:13:08.420> actually<00:13:09.420> the<00:13:09.899> the<00:13:10.019> process<00:13:10.500> of<00:13:10.620> choosing 00:13:11.090 --> 00:13:11.100 align:start position:0% two actually the the process of choosing 00:13:11.100 --> 00:13:13.009 align:start position:0% two actually the the process of choosing whether<00:13:11.279> to<00:13:11.519> help<00:13:11.820> the<00:13:12.180> customer<00:13:12.300> or<00:13:12.720> not<00:13:12.839> in 00:13:13.009 --> 00:13:13.019 align:start position:0% whether to help the customer or not in 00:13:13.019 --> 00:13:15.110 align:start position:0% whether to help the customer or not in in<00:13:13.200> one<00:13:13.440> of<00:13:13.560> those<00:13:13.620> situations<00:13:14.100> so<00:13:14.700> the<00:13:14.880> the 00:13:15.110 --> 00:13:15.120 align:start position:0% in one of those situations so the the 00:13:15.120 --> 00:13:17.210 align:start position:0% in one of those situations so the the helping<00:13:15.720> the<00:13:15.839> customer<00:13:16.019> I<00:13:16.320> mean<00:13:16.440> I<00:13:16.560> let<00:13:16.980> me<00:13:17.100> be 00:13:17.210 --> 00:13:17.220 align:start position:0% helping the customer I mean I let me be 00:13:17.220 --> 00:13:18.470 align:start position:0% helping the customer I mean I let me be clear<00:13:17.339> because<00:13:17.579> I<00:13:17.760> made<00:13:17.880> this<00:13:18.000> same<00:13:18.180> mistake 00:13:18.470 --> 00:13:18.480 align:start position:0% clear because I made this same mistake 00:13:18.480 --> 00:13:20.569 align:start position:0% clear because I made this same mistake in<00:13:18.660> Stanford<00:13:19.019> I<00:13:19.440> don't<00:13:19.560> mean<00:13:19.680> free 00:13:20.569 --> 00:13:20.579 align:start position:0% in Stanford I don't mean free 00:13:20.579 --> 00:13:22.910 align:start position:0% in Stanford I don't mean free uh<00:13:21.240> necessarily<00:13:21.779> right<00:13:22.019> like<00:13:22.260> we<00:13:22.500> we<00:13:22.560> will 00:13:22.910 --> 00:13:22.920 align:start position:0% uh necessarily right like we we will 00:13:22.920 --> 00:13:24.350 align:start position:0% uh necessarily right like we we will help<00:13:23.100> obviously<00:13:23.519> for<00:13:23.700> nothing<00:13:23.880> there<00:13:24.180> are 00:13:24.350 --> 00:13:24.360 align:start position:0% help obviously for nothing there are 00:13:24.360 --> 00:13:25.250 align:start position:0% help obviously for nothing there are certain<00:13:24.420> things<00:13:24.660> that<00:13:24.779> we<00:13:24.899> can<00:13:25.019> do<00:13:25.079> as 00:13:25.250 --> 00:13:25.260 align:start position:0% certain things that we can do as 00:13:25.260 --> 00:13:27.590 align:start position:0% certain things that we can do as Auditors<00:13:25.740> and<00:13:25.920> and<00:13:26.040> as<00:13:26.279> experts<00:13:26.760> in<00:13:26.940> in<00:13:27.360> the 00:13:27.590 --> 00:13:27.600 align:start position:0% Auditors and and as experts in in the 00:13:27.600 --> 00:13:29.030 align:start position:0% Auditors and and as experts in in the field<00:13:27.779> where<00:13:28.079> if<00:13:28.380> there's<00:13:28.560> more<00:13:28.860> services 00:13:29.030 --> 00:13:29.040 align:start position:0% field where if there's more services 00:13:29.040 --> 00:13:30.889 align:start position:0% field where if there's more services required<00:13:29.579> if<00:13:29.700> it's<00:13:30.180> fixed<00:13:30.480> reviews<00:13:30.540> if 00:13:30.889 --> 00:13:30.899 align:start position:0% required if it's fixed reviews if 00:13:30.899 --> 00:13:32.569 align:start position:0% required if it's fixed reviews if there's<00:13:31.079> other<00:13:31.260> things<00:13:31.500> but<00:13:32.100> the<00:13:32.339> first<00:13:32.459> thing 00:13:32.569 --> 00:13:32.579 align:start position:0% there's other things but the first thing 00:13:32.579 --> 00:13:34.190 align:start position:0% there's other things but the first thing we<00:13:32.760> want<00:13:32.940> to<00:13:33.000> do<00:13:33.120> is<00:13:33.300> reach<00:13:33.660> out<00:13:33.720> and<00:13:33.899> say<00:13:34.079> hey 00:13:34.190 --> 00:13:34.200 align:start position:0% we want to do is reach out and say hey 00:13:34.200 --> 00:13:36.530 align:start position:0% we want to do is reach out and say hey we<00:13:34.440> saw<00:13:34.560> that<00:13:34.800> this<00:13:34.980> happened<00:13:35.180> do<00:13:36.180> you<00:13:36.300> need 00:13:36.530 --> 00:13:36.540 align:start position:0% we saw that this happened do you need 00:13:36.540 --> 00:13:38.150 align:start position:0% we saw that this happened do you need any<00:13:36.779> do<00:13:37.079> you<00:13:37.200> know<00:13:37.380> do<00:13:37.500> you<00:13:37.680> want<00:13:37.740> to<00:13:37.860> talk<00:13:37.980> to 00:13:38.150 --> 00:13:38.160 align:start position:0% any do you know do you want to talk to 00:13:38.160 --> 00:13:39.889 align:start position:0% any do you know do you want to talk to us<00:13:38.339> about<00:13:38.639> stuff<00:13:39.120> that<00:13:39.360> you're<00:13:39.540> that<00:13:39.720> you're 00:13:39.889 --> 00:13:39.899 align:start position:0% us about stuff that you're that you're 00:13:39.899 --> 00:13:41.150 align:start position:0% us about stuff that you're that you're doing<00:13:40.079> right<00:13:40.260> now<00:13:40.380> I<00:13:40.560> think<00:13:40.740> you<00:13:40.860> you<00:13:40.980> said 00:13:41.150 --> 00:13:41.160 align:start position:0% doing right now I think you you said 00:13:41.160 --> 00:13:42.290 align:start position:0% doing right now I think you you said that<00:13:41.339> pretty<00:13:41.519> well 00:13:42.290 --> 00:13:42.300 align:start position:0% that pretty well 00:13:42.300 --> 00:13:44.690 align:start position:0% that pretty well can<00:13:42.660> we<00:13:42.839> agree<00:13:43.200> that<00:13:43.440> audits<00:13:43.980> is<00:13:44.040> probably<00:13:44.220> the 00:13:44.690 --> 00:13:44.700 align:start position:0% can we agree that audits is probably the 00:13:44.700 --> 00:13:46.970 align:start position:0% can we agree that audits is probably the the<00:13:44.940> one<00:13:45.360> of<00:13:45.480> the<00:13:45.540> worst<00:13:45.839> terms<00:13:46.139> to<00:13:46.260> describe 00:13:46.970 --> 00:13:46.980 align:start position:0% the one of the worst terms to describe 00:13:46.980 --> 00:13:53.410 align:start position:0% the one of the worst terms to describe what<00:13:47.160> we<00:13:47.279> actually<00:13:47.459> do 00:13:53.410 --> 00:13:53.420 align:start position:0% 00:13:53.420 --> 00:13:56.389 align:start position:0% I<00:13:54.420> feel<00:13:54.540> so<00:13:54.779> bad<00:13:54.959> using<00:13:55.320> the<00:13:55.440> word<00:13:55.500> auditing<00:13:56.100> or 00:13:56.389 --> 00:13:56.399 align:start position:0% I feel so bad using the word auditing or 00:13:56.399 --> 00:13:58.550 align:start position:0% I feel so bad using the word auditing or audit<00:13:56.760> every<00:13:57.060> time<00:13:57.240> I<00:13:57.420> do<00:13:57.600> but<00:13:57.959> these<00:13:58.440> are 00:13:58.550 --> 00:13:58.560 align:start position:0% audit every time I do but these are 00:13:58.560 --> 00:14:01.370 align:start position:0% audit every time I do but these are really<00:13:58.740> time<00:13:59.100> boxed<00:13:59.639> security<00:14:00.380> assessments 00:14:01.370 --> 00:14:01.380 align:start position:0% really time boxed security assessments 00:14:01.380 --> 00:14:04.009 align:start position:0% really time boxed security assessments let's<00:14:01.980> just<00:14:02.220> all<00:14:02.399> agree<00:14:02.700> on<00:14:02.940> this<00:14:03.060> as<00:14:03.480> John<00:14:03.779> was 00:14:04.009 --> 00:14:04.019 align:start position:0% let's just all agree on this as John was 00:14:04.019 --> 00:14:06.590 align:start position:0% let's just all agree on this as John was saying<00:14:04.380> these<00:14:04.800> things<00:14:04.980> are<00:14:05.399> not<00:14:05.639> bulletproof 00:14:06.590 --> 00:14:06.600 align:start position:0% saying these things are not bulletproof 00:14:06.600 --> 00:14:08.030 align:start position:0% saying these things are not bulletproof right 00:14:08.030 --> 00:14:08.040 align:start position:0% right 00:14:08.040 --> 00:14:10.790 align:start position:0% right um<00:14:08.100> bugs<00:14:08.519> will<00:14:08.639> be<00:14:08.700> missed<00:14:09.060> and<00:14:09.959> we<00:14:10.260> allocate<00:14:10.680> a 00:14:10.790 --> 00:14:10.800 align:start position:0% um bugs will be missed and we allocate a 00:14:10.800 --> 00:14:13.009 align:start position:0% um bugs will be missed and we allocate a certain<00:14:10.920> amount<00:14:11.040> of<00:14:11.279> time<00:14:11.459> to<00:14:11.880> do<00:14:12.180> our<00:14:12.360> best<00:14:12.540> to 00:14:13.009 --> 00:14:13.019 align:start position:0% certain amount of time to do our best to 00:14:13.019 --> 00:14:15.110 align:start position:0% certain amount of time to do our best to find<00:14:13.440> these<00:14:13.860> uh<00:14:14.040> vulnerabilities<00:14:14.639> in<00:14:15.000> your 00:14:15.110 --> 00:14:15.120 align:start position:0% find these uh vulnerabilities in your 00:14:15.120 --> 00:14:17.509 align:start position:0% find these uh vulnerabilities in your code<00:14:15.360> but<00:14:16.079> guess<00:14:16.380> what<00:14:16.560> if<00:14:16.920> you<00:14:17.100> give<00:14:17.339> us 00:14:17.509 --> 00:14:17.519 align:start position:0% code but guess what if you give us 00:14:17.519 --> 00:14:19.850 align:start position:0% code but guess what if you give us double<00:14:18.000> the<00:14:18.240> amount<00:14:18.480> of<00:14:18.600> time<00:14:18.779> chances<00:14:19.620> are 00:14:19.850 --> 00:14:19.860 align:start position:0% double the amount of time chances are 00:14:19.860 --> 00:14:22.250 align:start position:0% double the amount of time chances are we'll<00:14:20.339> probably<00:14:20.519> find<00:14:20.760> more<00:14:21.000> bugs 00:14:22.250 --> 00:14:22.260 align:start position:0% we'll probably find more bugs 00:14:22.260 --> 00:14:23.810 align:start position:0% we'll probably find more bugs um<00:14:22.320> so<00:14:22.500> let's<00:14:22.680> just<00:14:22.920> you<00:14:23.220> know<00:14:23.279> make<00:14:23.459> sure<00:14:23.639> that 00:14:23.810 --> 00:14:23.820 align:start position:0% um so let's just you know make sure that 00:14:23.820 --> 00:14:26.509 align:start position:0% um so let's just you know make sure that we're<00:14:24.000> all<00:14:24.120> clear<00:14:24.360> on<00:14:24.959> what<00:14:25.139> we<00:14:25.320> do<00:14:25.500> up<00:14:25.740> here<00:14:25.920> in 00:14:26.509 --> 00:14:26.519 align:start position:0% we're all clear on what we do up here in 00:14:26.519 --> 00:14:28.430 align:start position:0% we're all clear on what we do up here in terms<00:14:26.700> of<00:14:26.820> Security<00:14:27.180> reviews<00:14:27.899> and<00:14:28.260> security 00:14:28.430 --> 00:14:28.440 align:start position:0% terms of Security reviews and security 00:14:28.440 --> 00:14:30.889 align:start position:0% terms of Security reviews and security assessments<00:14:29.579> okay 00:14:30.889 --> 00:14:30.899 align:start position:0% assessments okay 00:14:30.899 --> 00:14:32.569 align:start position:0% assessments okay and<00:14:31.320> by<00:14:31.500> the<00:14:31.620> way<00:14:31.620> that's<00:14:31.800> that's<00:14:31.980> not<00:14:32.220> just<00:14:32.399> a 00:14:32.569 --> 00:14:32.579 align:start position:0% and by the way that's that's not just a 00:14:32.579 --> 00:14:33.910 align:start position:0% and by the way that's that's not just a cya 00:14:33.910 --> 00:14:33.920 align:start position:0% cya 00:14:33.920 --> 00:14:35.990 align:start position:0% cya it's<00:14:34.920> not 00:14:35.990 --> 00:14:36.000 align:start position:0% it's not 00:14:36.000 --> 00:14:37.550 align:start position:0% it's not you<00:14:36.060> you<00:14:36.240> said<00:14:36.600> the<00:14:36.720> word<00:14:36.839> partnership<00:14:37.139> or<00:14:37.380> you 00:14:37.550 --> 00:14:37.560 align:start position:0% you you said the word partnership or you 00:14:37.560 --> 00:14:38.990 align:start position:0% you you said the word partnership or you said<00:14:37.680> the<00:14:37.800> word<00:14:37.920> partnership 00:14:38.990 --> 00:14:39.000 align:start position:0% said the word partnership 00:14:39.000 --> 00:14:41.509 align:start position:0% said the word partnership um<00:14:39.320> people<00:14:40.320> wait<00:14:40.560> a<00:14:40.740> long<00:14:40.800> time<00:14:40.920> for<00:14:41.100> audits 00:14:41.509 --> 00:14:41.519 align:start position:0% um people wait a long time for audits 00:14:41.519 --> 00:14:42.650 align:start position:0% um people wait a long time for audits it's<00:14:41.579> a<00:14:41.760> very<00:14:41.880> important<00:14:42.180> part<00:14:42.360> of<00:14:42.540> the 00:14:42.650 --> 00:14:42.660 align:start position:0% it's a very important part of the 00:14:42.660 --> 00:14:44.269 align:start position:0% it's a very important part of the process<00:14:42.899> of<00:14:43.139> going<00:14:43.320> live<00:14:43.620> with<00:14:43.920> with<00:14:44.040> a 00:14:44.269 --> 00:14:44.279 align:start position:0% process of going live with with a 00:14:44.279 --> 00:14:46.069 align:start position:0% process of going live with with a product<00:14:44.399> especially<00:14:44.940> a<00:14:45.420> product<00:14:45.540> where<00:14:45.839> a<00:14:45.959> lot 00:14:46.069 --> 00:14:46.079 align:start position:0% product especially a product where a lot 00:14:46.079 --> 00:14:47.629 align:start position:0% product especially a product where a lot of<00:14:46.199> money<00:14:46.320> you<00:14:46.740> know<00:14:46.800> if<00:14:46.920> it<00:14:47.040> goes<00:14:47.279> bad<00:14:47.339> a<00:14:47.519> lot 00:14:47.629 --> 00:14:47.639 align:start position:0% of money you know if it goes bad a lot 00:14:47.639 --> 00:14:49.430 align:start position:0% of money you know if it goes bad a lot of<00:14:47.699> money<00:14:47.820> can<00:14:48.000> go<00:14:48.120> out<00:14:48.180> the<00:14:48.360> door<00:14:48.480> uh 00:14:49.430 --> 00:14:49.440 align:start position:0% of money can go out the door uh 00:14:49.440 --> 00:14:51.110 align:start position:0% of money can go out the door uh customers<00:14:50.279> have<00:14:50.459> their<00:14:50.639> own<00:14:50.760> priorities 00:14:51.110 --> 00:14:51.120 align:start position:0% customers have their own priorities 00:14:51.120 --> 00:14:52.730 align:start position:0% customers have their own priorities customers<00:14:51.660> have<00:14:51.839> budgets<00:14:52.260> customers<00:14:52.620> have 00:14:52.730 --> 00:14:52.740 align:start position:0% customers have budgets customers have 00:14:52.740 --> 00:14:55.970 align:start position:0% customers have budgets customers have realities<00:14:53.220> and<00:14:54.180> usually<00:14:55.139> it<00:14:55.380> ends<00:14:55.680> up<00:14:55.740> that 00:14:55.970 --> 00:14:55.980 align:start position:0% realities and usually it ends up that 00:14:55.980 --> 00:14:57.230 align:start position:0% realities and usually it ends up that we're<00:14:56.100> not<00:14:56.279> negotiating<00:14:56.760> actually<00:14:57.000> about 00:14:57.230 --> 00:14:57.240 align:start position:0% we're not negotiating actually about 00:14:57.240 --> 00:14:58.730 align:start position:0% we're not negotiating actually about money<00:14:57.480> but<00:14:57.660> about<00:14:57.839> time<00:14:58.139> we're<00:14:58.620> not 00:14:58.730 --> 00:14:58.740 align:start position:0% money but about time we're not 00:14:58.740 --> 00:15:00.110 align:start position:0% money but about time we're not negotiating<00:14:59.100> about<00:14:59.279> money<00:14:59.459> but<00:14:59.699> about<00:14:59.820> the 00:15:00.110 --> 00:15:00.120 align:start position:0% negotiating about money but about the 00:15:00.120 --> 00:15:01.370 align:start position:0% negotiating about money but about the number<00:15:00.240> of<00:15:00.360> Engineers<00:15:00.720> who<00:15:00.959> can<00:15:01.079> be<00:15:01.199> looking 00:15:01.370 --> 00:15:01.380 align:start position:0% number of Engineers who can be looking 00:15:01.380 --> 00:15:04.009 align:start position:0% number of Engineers who can be looking at<00:15:01.620> it<00:15:01.740> so<00:15:01.980> while<00:15:02.339> we<00:15:02.579> can't<00:15:02.699> guarantee<00:15:03.180> that<00:15:03.600> a 00:15:04.009 --> 00:15:04.019 align:start position:0% at it so while we can't guarantee that a 00:15:04.019 --> 00:15:05.930 align:start position:0% at it so while we can't guarantee that a three-week<00:15:04.620> two<00:15:04.800> engineer<00:15:05.160> audit<00:15:05.459> will<00:15:05.639> find 00:15:05.930 --> 00:15:05.940 align:start position:0% three-week two engineer audit will find 00:15:05.940 --> 00:15:08.629 align:start position:0% three-week two engineer audit will find all<00:15:06.360> the<00:15:06.480> bugs<00:15:06.839> we<00:15:07.500> can<00:15:07.680> guarantee<00:15:08.220> that<00:15:08.519> a 00:15:08.629 --> 00:15:08.639 align:start position:0% all the bugs we can guarantee that a 00:15:08.639 --> 00:15:09.949 align:start position:0% all the bugs we can guarantee that a three<00:15:08.760> week<00:15:08.940> two<00:15:09.120> engineer<00:15:09.480> audit<00:15:09.720> will<00:15:09.839> find 00:15:09.949 --> 00:15:09.959 align:start position:0% three week two engineer audit will find 00:15:09.959 --> 00:15:11.389 align:start position:0% three week two engineer audit will find all<00:15:10.139> the<00:15:10.260> bugs<00:15:10.500> that<00:15:10.620> can<00:15:10.740> be<00:15:10.860> found<00:15:10.980> by<00:15:11.220> three 00:15:11.389 --> 00:15:11.399 align:start position:0% all the bugs that can be found by three 00:15:11.399 --> 00:15:13.009 align:start position:0% all the bugs that can be found by three Engineers<00:15:11.760> by<00:15:12.120> two<00:15:12.360> Engineers<00:15:12.660> working<00:15:12.839> for 00:15:13.009 --> 00:15:13.019 align:start position:0% Engineers by two Engineers working for 00:15:13.019 --> 00:15:14.629 align:start position:0% Engineers by two Engineers working for three<00:15:13.139> weeks<00:15:13.440> and<00:15:13.920> that<00:15:14.040> that's<00:15:14.220> a<00:15:14.519> different 00:15:14.629 --> 00:15:14.639 align:start position:0% three weeks and that that's a different 00:15:14.639 --> 00:15:17.689 align:start position:0% three weeks and that that's a different sort<00:15:15.300> of<00:15:15.360> guarantee<00:15:15.839> yeah<00:15:16.500> okay 00:15:17.689 --> 00:15:17.699 align:start position:0% sort of guarantee yeah okay 00:15:17.699 --> 00:15:20.030 align:start position:0% sort of guarantee yeah okay um<00:15:17.760> so<00:15:18.540> I<00:15:18.720> think<00:15:18.779> I<00:15:18.959> think<00:15:19.079> Medi<00:15:19.560> set<00:15:19.740> this<00:15:19.920> up 00:15:20.030 --> 00:15:20.040 align:start position:0% um so I think I think Medi set this up 00:15:20.040 --> 00:15:23.930 align:start position:0% um so I think I think Medi set this up well<00:15:20.279> in<00:15:21.060> that<00:15:21.360> uh<00:15:22.079> by<00:15:22.560> saying<00:15:22.860> like<00:15:23.100> like<00:15:23.639> just 00:15:23.930 --> 00:15:23.940 align:start position:0% well in that uh by saying like like just 00:15:23.940 --> 00:15:25.610 align:start position:0% well in that uh by saying like like just the<00:15:24.120> Magics<00:15:24.600> of<00:15:24.779> what<00:15:24.959> this<00:15:25.079> is<00:15:25.199> what<00:15:25.440> we're 00:15:25.610 --> 00:15:25.620 align:start position:0% the Magics of what this is what we're 00:15:25.620 --> 00:15:28.370 align:start position:0% the Magics of what this is what we're doing<00:15:25.800> how<00:15:26.519> is<00:15:26.639> it<00:15:26.820> defined 00:15:28.370 --> 00:15:28.380 align:start position:0% doing how is it defined 00:15:28.380 --> 00:15:30.350 align:start position:0% doing how is it defined um<00:15:28.440> so<00:15:29.100> we're<00:15:29.339> saying<00:15:29.639> time<00:15:29.880> box<00:15:30.060> Security 00:15:30.350 --> 00:15:30.360 align:start position:0% um so we're saying time box Security 00:15:30.360 --> 00:15:31.850 align:start position:0% um so we're saying time box Security reviews<00:15:30.779> now 00:15:31.850 --> 00:15:31.860 align:start position:0% reviews now 00:15:31.860 --> 00:15:35.329 align:start position:0% reviews now do<00:15:32.579> we<00:15:32.820> need<00:15:33.120> do<00:15:33.959> we<00:15:34.139> need<00:15:34.260> a<00:15:34.500> set<00:15:34.680> of<00:15:34.860> Standards 00:15:35.329 --> 00:15:35.339 align:start position:0% do we need do we need a set of Standards 00:15:35.339 --> 00:15:38.389 align:start position:0% do we need do we need a set of Standards to<00:15:35.639> make<00:15:35.820> it<00:15:36.000> clear<00:15:36.240> whatever<00:15:37.139> word<00:15:37.740> we<00:15:37.980> choose 00:15:38.389 --> 00:15:38.399 align:start position:0% to make it clear whatever word we choose 00:15:38.399 --> 00:15:40.790 align:start position:0% to make it clear whatever word we choose do<00:15:39.360> we<00:15:39.540> need<00:15:39.720> to<00:15:39.899> have<00:15:40.019> a<00:15:40.139> set<00:15:40.260> of<00:15:40.440> standards 00:15:40.790 --> 00:15:40.800 align:start position:0% do we need to have a set of standards 00:15:40.800 --> 00:15:42.889 align:start position:0% do we need to have a set of standards for<00:15:40.980> this<00:15:41.100> and<00:15:41.279> I'll<00:15:41.459> give<00:15:41.639> it<00:15:41.760> to<00:15:41.820> Chandra<00:15:42.300> to 00:15:42.889 --> 00:15:42.899 align:start position:0% for this and I'll give it to Chandra to 00:15:42.899 --> 00:15:43.850 align:start position:0% for this and I'll give it to Chandra to to 00:15:43.850 --> 00:15:43.860 align:start position:0% to 00:15:43.860 --> 00:15:46.490 align:start position:0% to take<00:15:44.339> a<00:15:44.399> crack<00:15:44.579> at<00:15:44.820> it<00:15:44.940> so<00:15:45.480> standards<00:15:46.320> for 00:15:46.490 --> 00:15:46.500 align:start position:0% take a crack at it so standards for 00:15:46.500 --> 00:15:51.250 align:start position:0% take a crack at it so standards for Auditors<00:15:47.040> you<00:15:47.519> mean<00:15:47.940> or<00:15:48.600> for<00:15:49.500> yeah<00:15:50.100> I<00:15:50.339> mean<00:15:50.519> one 00:15:51.250 --> 00:15:51.260 align:start position:0% Auditors you mean or for yeah I mean one 00:15:51.260 --> 00:15:54.949 align:start position:0% Auditors you mean or for yeah I mean one that's<00:15:52.260> a<00:15:52.620> good<00:15:52.800> place<00:15:53.220> to<00:15:53.519> take<00:15:53.639> it<00:15:53.880> as<00:15:54.779> well 00:15:54.949 --> 00:15:54.959 align:start position:0% that's a good place to take it as well 00:15:54.959 --> 00:15:58.910 align:start position:0% that's a good place to take it as well if<00:15:55.260> you<00:15:55.380> like<00:15:55.500> I<00:15:55.860> was<00:15:56.040> thinking<00:15:56.399> more<00:15:56.760> for<00:15:57.480> what 00:15:58.910 --> 00:15:58.920 align:start position:0% if you like I was thinking more for what 00:15:58.920 --> 00:16:01.850 align:start position:0% if you like I was thinking more for what an<00:15:59.519> audit<00:15:59.940> is<00:16:00.120> for<00:16:00.660> what<00:16:00.899> what<00:16:01.380> needs<00:16:01.740> to 00:16:01.850 --> 00:16:01.860 align:start position:0% an audit is for what what needs to 00:16:01.860 --> 00:16:04.009 align:start position:0% an audit is for what what needs to happen<00:16:02.040> during<00:16:02.399> the<00:16:02.760> course<00:16:03.360> of<00:16:03.660> this 00:16:04.009 --> 00:16:04.019 align:start position:0% happen during the course of this 00:16:04.019 --> 00:16:05.689 align:start position:0% happen during the course of this Security<00:16:04.500> review 00:16:05.689 --> 00:16:05.699 align:start position:0% Security review 00:16:05.699 --> 00:16:09.650 align:start position:0% Security review well<00:16:07.019> um<00:16:07.079> so<00:16:07.800> you<00:16:08.040> know<00:16:08.100> I<00:16:08.579> I<00:16:08.940> can<00:16:09.180> perhaps 00:16:09.650 --> 00:16:09.660 align:start position:0% well um so you know I I can perhaps 00:16:09.660 --> 00:16:11.870 align:start position:0% well um so you know I I can perhaps speak<00:16:10.440> from<00:16:10.680> a<00:16:10.860> more<00:16:11.040> automated<00:16:11.399> auditing 00:16:11.870 --> 00:16:11.880 align:start position:0% speak from a more automated auditing 00:16:11.880 --> 00:16:14.030 align:start position:0% speak from a more automated auditing point<00:16:12.180> of<00:16:12.300> view<00:16:12.420> but<00:16:12.720> then<00:16:12.839> I<00:16:13.139> think<00:16:13.320> some<00:16:13.860> of 00:16:14.030 --> 00:16:14.040 align:start position:0% point of view but then I think some of 00:16:14.040 --> 00:16:15.829 align:start position:0% point of view but then I think some of the<00:16:14.100> ideas<00:16:14.220> probably<00:16:14.639> also<00:16:15.060> apply<00:16:15.540> to 00:16:15.829 --> 00:16:15.839 align:start position:0% the ideas probably also apply to 00:16:15.839 --> 00:16:19.310 align:start position:0% the ideas probably also apply to human-based<00:16:16.800> auditing<00:16:17.160> uh<00:16:18.120> I<00:16:18.360> think 00:16:19.310 --> 00:16:19.320 align:start position:0% human-based auditing uh I think 00:16:19.320 --> 00:16:20.930 align:start position:0% human-based auditing uh I think the<00:16:19.800> hardest<00:16:20.040> thing<00:16:20.160> is<00:16:20.339> to<00:16:20.519> come<00:16:20.639> up<00:16:20.760> with 00:16:20.930 --> 00:16:20.940 align:start position:0% the hardest thing is to come up with 00:16:20.940 --> 00:16:23.090 align:start position:0% the hardest thing is to come up with what<00:16:21.540> with<00:16:21.899> the<00:16:22.019> specification<00:16:22.620> right<00:16:22.920> like 00:16:23.090 --> 00:16:23.100 align:start position:0% what with the specification right like 00:16:23.100 --> 00:16:24.710 align:start position:0% what with the specification right like even<00:16:23.279> when<00:16:23.519> you're<00:16:23.639> auditing<00:16:24.060> like<00:16:24.240> what<00:16:24.540> are 00:16:24.710 --> 00:16:24.720 align:start position:0% even when you're auditing like what are 00:16:24.720 --> 00:16:26.810 align:start position:0% even when you're auditing like what are you<00:16:24.839> actually<00:16:25.079> looking<00:16:25.440> for<00:16:25.680> I<00:16:26.339> think<00:16:26.459> that's 00:16:26.810 --> 00:16:26.820 align:start position:0% you actually looking for I think that's 00:16:26.820 --> 00:16:29.810 align:start position:0% you actually looking for I think that's uh<00:16:27.480> one<00:16:27.899> of<00:16:28.019> the<00:16:28.139> main<00:16:28.620> questions<00:16:28.980> that<00:16:29.579> you 00:16:29.810 --> 00:16:29.820 align:start position:0% uh one of the main questions that you 00:16:29.820 --> 00:16:31.490 align:start position:0% uh one of the main questions that you should<00:16:30.060> very<00:16:30.420> carefully<00:16:30.720> think<00:16:30.959> about<00:16:31.139> right 00:16:31.490 --> 00:16:31.500 align:start position:0% should very carefully think about right 00:16:31.500 --> 00:16:33.829 align:start position:0% should very carefully think about right uh<00:16:32.459> and<00:16:32.699> you<00:16:33.000> know<00:16:33.060> I<00:16:33.360> think<00:16:33.420> one<00:16:33.660> of<00:16:33.720> the 00:16:33.829 --> 00:16:33.839 align:start position:0% uh and you know I think one of the 00:16:33.839 --> 00:16:36.829 align:start position:0% uh and you know I think one of the things<00:16:33.959> that's<00:16:34.260> kind<00:16:34.560> of<00:16:34.820> uh<00:16:35.820> difficult<00:16:36.300> for 00:16:36.829 --> 00:16:36.839 align:start position:0% things that's kind of uh difficult for 00:16:36.839 --> 00:16:39.949 align:start position:0% things that's kind of uh difficult for auditing<00:16:37.440> is<00:16:37.980> uh<00:16:38.699> it<00:16:39.060> you<00:16:39.300> it's<00:16:39.540> hard<00:16:39.720> to<00:16:39.899> be 00:16:39.949 --> 00:16:39.959 align:start position:0% auditing is uh it you it's hard to be 00:16:39.959 --> 00:16:41.930 align:start position:0% auditing is uh it you it's hard to be very<00:16:40.199> precise<00:16:40.620> and<00:16:41.100> if<00:16:41.279> you're<00:16:41.339> not<00:16:41.519> precise 00:16:41.930 --> 00:16:41.940 align:start position:0% very precise and if you're not precise 00:16:41.940 --> 00:16:43.430 align:start position:0% very precise and if you're not precise then<00:16:42.180> you<00:16:42.420> kind<00:16:42.540> of<00:16:42.660> think<00:16:42.779> that<00:16:43.019> you<00:16:43.139> did<00:16:43.259> a 00:16:43.430 --> 00:16:43.440 align:start position:0% then you kind of think that you did a 00:16:43.440 --> 00:16:45.230 align:start position:0% then you kind of think that you did a proof<00:16:43.740> or<00:16:44.100> like<00:16:44.339> you<00:16:44.519> have<00:16:44.699> some<00:16:44.940> kind<00:16:45.120> of 00:16:45.230 --> 00:16:45.240 align:start position:0% proof or like you have some kind of 00:16:45.240 --> 00:16:48.110 align:start position:0% proof or like you have some kind of guarantee<00:16:46.079> that<00:16:46.380> this<00:16:46.680> bug<00:16:46.860> isn't<00:16:47.220> there<00:16:47.399> but 00:16:48.110 --> 00:16:48.120 align:start position:0% guarantee that this bug isn't there but 00:16:48.120 --> 00:16:50.749 align:start position:0% guarantee that this bug isn't there but I<00:16:48.360> think<00:16:48.480> you<00:16:48.899> know<00:16:48.959> unless<00:16:49.500> it's<00:16:50.100> very<00:16:50.519> easy 00:16:50.749 --> 00:16:50.759 align:start position:0% I think you know unless it's very easy 00:16:50.759 --> 00:16:53.569 align:start position:0% I think you know unless it's very easy to<00:16:51.420> uh<00:16:51.899> feel<00:16:52.259> like<00:16:52.440> you<00:16:52.740> you<00:16:52.980> know<00:16:53.160> audited 00:16:53.569 --> 00:16:53.579 align:start position:0% to uh feel like you you know audited 00:16:53.579 --> 00:16:55.430 align:start position:0% to uh feel like you you know audited really<00:16:53.820> well<00:16:54.060> if<00:16:54.779> you<00:16:54.899> don't<00:16:55.019> have<00:16:55.259> the 00:16:55.430 --> 00:16:55.440 align:start position:0% really well if you don't have the 00:16:55.440 --> 00:16:58.730 align:start position:0% really well if you don't have the specification<00:16:55.860> correctly<00:16:56.339> in<00:16:56.639> your<00:16:56.820> head<00:16:57.000> and 00:16:58.730 --> 00:16:58.740 align:start position:0% specification correctly in your head and 00:16:58.740 --> 00:17:04.189 align:start position:0% specification correctly in your head and um perhaps<00:16:59.579> a<00:17:00.240> related<00:17:00.660> uh<00:17:01.500> thing<00:17:01.800> is<00:17:02.339> uh 00:17:04.189 --> 00:17:04.199 align:start position:0% um perhaps a related uh thing is uh 00:17:04.199 --> 00:17:05.929 align:start position:0% um perhaps a related uh thing is uh in<00:17:04.860> formal<00:17:05.160> verification<00:17:05.520> there's<00:17:05.760> this 00:17:05.929 --> 00:17:05.939 align:start position:0% in formal verification there's this 00:17:05.939 --> 00:17:07.850 align:start position:0% in formal verification there's this notion<00:17:06.179> of<00:17:06.299> trusted<00:17:06.660> Computing<00:17:07.020> base<00:17:07.199> and<00:17:07.799> I 00:17:07.850 --> 00:17:07.860 align:start position:0% notion of trusted Computing base and I 00:17:07.860 --> 00:17:10.789 align:start position:0% notion of trusted Computing base and I think<00:17:08.040> that<00:17:08.280> idea<00:17:08.640> also<00:17:09.120> uh<00:17:09.780> you<00:17:09.900> know<00:17:10.020> maps<00:17:10.439> to 00:17:10.789 --> 00:17:10.799 align:start position:0% think that idea also uh you know maps to 00:17:10.799 --> 00:17:12.890 align:start position:0% think that idea also uh you know maps to auditing<00:17:11.400> like<00:17:11.640> what<00:17:12.179> part<00:17:12.299> of<00:17:12.419> the<00:17:12.540> code<00:17:12.660> did 00:17:12.890 --> 00:17:12.900 align:start position:0% auditing like what part of the code did 00:17:12.900 --> 00:17:14.750 align:start position:0% auditing like what part of the code did you<00:17:13.020> audit<00:17:13.380> what<00:17:13.860> parts<00:17:13.980> of<00:17:14.160> the<00:17:14.280> code<00:17:14.400> did<00:17:14.640> you 00:17:14.750 --> 00:17:14.760 align:start position:0% you audit what parts of the code did you 00:17:14.760 --> 00:17:17.090 align:start position:0% you audit what parts of the code did you not<00:17:14.939> audit<00:17:15.299> right<00:17:15.600> and<00:17:16.380> you<00:17:16.679> know<00:17:16.740> you<00:17:16.980> can 00:17:17.090 --> 00:17:17.100 align:start position:0% not audit right and you know you can 00:17:17.100 --> 00:17:19.610 align:start position:0% not audit right and you know you can only<00:17:17.220> say<00:17:17.640> confidently<00:17:18.600> well<00:17:19.079> with<00:17:19.439> some 00:17:19.610 --> 00:17:19.620 align:start position:0% only say confidently well with some 00:17:19.620 --> 00:17:21.590 align:start position:0% only say confidently well with some confidence<00:17:19.980> that<00:17:20.400> the<00:17:20.880> code<00:17:21.000> that<00:17:21.299> you<00:17:21.419> did 00:17:21.590 --> 00:17:21.600 align:start position:0% confidence that the code that you did 00:17:21.600 --> 00:17:23.809 align:start position:0% confidence that the code that you did audit<00:17:21.959> maybe<00:17:22.439> doesn't<00:17:22.679> have<00:17:23.040> some 00:17:23.809 --> 00:17:23.819 align:start position:0% audit maybe doesn't have some 00:17:23.819 --> 00:17:25.370 align:start position:0% audit maybe doesn't have some vulnerabilities<00:17:24.480> but<00:17:24.780> the<00:17:24.900> parts<00:17:25.079> that<00:17:25.260> you 00:17:25.370 --> 00:17:25.380 align:start position:0% vulnerabilities but the parts that you 00:17:25.380 --> 00:17:27.230 align:start position:0% vulnerabilities but the parts that you didn't<00:17:25.559> you<00:17:26.400> can't<00:17:26.520> say<00:17:26.640> anything<00:17:26.819> about<00:17:27.059> them 00:17:27.230 --> 00:17:27.240 align:start position:0% didn't you can't say anything about them 00:17:27.240 --> 00:17:28.789 align:start position:0% didn't you can't say anything about them right<00:17:27.419> so<00:17:27.660> it's<00:17:27.959> very<00:17:28.140> important<00:17:28.439> to<00:17:28.559> be<00:17:28.679> very 00:17:28.789 --> 00:17:28.799 align:start position:0% right so it's very important to be very 00:17:28.799 --> 00:17:31.789 align:start position:0% right so it's very important to be very explicit<00:17:29.340> about<00:17:29.700> what<00:17:30.360> the<00:17:30.480> TCB<00:17:30.960> is<00:17:31.200> and<00:17:31.559> what 00:17:31.789 --> 00:17:31.799 align:start position:0% explicit about what the TCB is and what 00:17:31.799 --> 00:17:33.530 align:start position:0% explicit about what the TCB is and what you<00:17:31.919> verified<00:17:32.280> and<00:17:32.700> what<00:17:32.880> you<00:17:33.000> checked<00:17:33.360> or 00:17:33.530 --> 00:17:33.540 align:start position:0% you verified and what you checked or 00:17:33.540 --> 00:17:36.110 align:start position:0% you verified and what you checked or whatever<00:17:33.960> you<00:17:34.260> audited 00:17:36.110 --> 00:17:36.120 align:start position:0% whatever you audited 00:17:36.120 --> 00:17:39.110 align:start position:0% whatever you audited anyone<00:17:36.840> else 00:17:39.110 --> 00:17:39.120 align:start position:0% 00:17:39.120 --> 00:17:41.029 align:start position:0% I<00:17:39.840> would<00:17:40.020> say 00:17:41.029 --> 00:17:41.039 align:start position:0% I would say 00:17:41.039 --> 00:17:44.750 align:start position:0% I would say I'm<00:17:41.700> a<00:17:41.880> little<00:17:42.200> frightened<00:17:43.200> of<00:17:43.860> the<00:17:44.280> word 00:17:44.750 --> 00:17:44.760 align:start position:0% I'm a little frightened of the word 00:17:44.760 --> 00:17:48.909 align:start position:0% I'm a little frightened of the word standard<00:17:45.419> in<00:17:46.200> what<00:17:46.440> we<00:17:46.620> do<00:17:47.299> because 00:17:48.909 --> 00:17:48.919 align:start position:0% standard in what we do because 00:17:48.919 --> 00:17:52.430 align:start position:0% standard in what we do because I<00:17:49.919> think<00:17:50.299> sometimes<00:17:51.299> it<00:17:51.840> comes<00:17:52.080> from<00:17:52.260> the 00:17:52.430 --> 00:17:52.440 align:start position:0% I think sometimes it comes from the 00:17:52.440 --> 00:17:54.650 align:start position:0% I think sometimes it comes from the place<00:17:52.679> of<00:17:52.980> people<00:17:53.280> hoping 00:17:54.650 --> 00:17:54.660 align:start position:0% place of people hoping 00:17:54.660 --> 00:17:55.850 align:start position:0% place of people hoping that 00:17:55.850 --> 00:17:55.860 align:start position:0% that 00:17:55.860 --> 00:17:59.090 align:start position:0% that we're<00:17:56.340> going<00:17:56.460> to<00:17:56.640> simplify<00:17:57.500> down<00:17:58.500> to<00:17:58.740> some 00:17:59.090 --> 00:17:59.100 align:start position:0% we're going to simplify down to some 00:17:59.100 --> 00:18:01.669 align:start position:0% we're going to simplify down to some very<00:17:59.460> simple<00:18:00.059> set<00:18:00.419> of<00:18:00.600> rules<00:18:00.900> what<00:18:01.260> needs<00:18:01.620> to 00:18:01.669 --> 00:18:01.679 align:start position:0% very simple set of rules what needs to 00:18:01.679 --> 00:18:04.190 align:start position:0% very simple set of rules what needs to be<00:18:01.860> covered<00:18:02.340> and<00:18:02.940> then<00:18:03.120> anyone<00:18:03.720> could<00:18:03.960> cover 00:18:04.190 --> 00:18:04.200 align:start position:0% be covered and then anyone could cover 00:18:04.200 --> 00:18:08.150 align:start position:0% be covered and then anyone could cover it<00:18:04.500> and<00:18:05.160> so<00:18:06.000> I<00:18:06.419> do<00:18:06.539> think<00:18:06.900> we<00:18:07.620> need<00:18:07.799> common 00:18:08.150 --> 00:18:08.160 align:start position:0% it and so I do think we need common 00:18:08.160 --> 00:18:12.049 align:start position:0% it and so I do think we need common language<00:18:08.640> we<00:18:09.299> need<00:18:09.480> in<00:18:10.200> many<00:18:11.100> just<00:18:11.580> helped<00:18:11.940> us 00:18:12.049 --> 00:18:12.059 align:start position:0% language we need in many just helped us 00:18:12.059 --> 00:18:13.730 align:start position:0% language we need in many just helped us with<00:18:12.299> some<00:18:12.539> of<00:18:12.600> our<00:18:12.780> common<00:18:13.020> language<00:18:13.380> and 00:18:13.730 --> 00:18:13.740 align:start position:0% with some of our common language and 00:18:13.740 --> 00:18:15.650 align:start position:0% with some of our common language and understanding 00:18:15.650 --> 00:18:15.660 align:start position:0% understanding 00:18:15.660 --> 00:18:17.450 align:start position:0% understanding um so<00:18:15.900> that<00:18:16.080> we're<00:18:16.260> working<00:18:16.440> together<00:18:16.799> but<00:18:17.280> I 00:18:17.450 --> 00:18:17.460 align:start position:0% um so that we're working together but I 00:18:17.460 --> 00:18:20.150 align:start position:0% um so that we're working together but I think<00:18:17.580> what's<00:18:17.880> important<00:18:18.419> is 00:18:20.150 --> 00:18:20.160 align:start position:0% think what's important is 00:18:20.160 --> 00:18:23.570 align:start position:0% think what's important is um if<00:18:20.820> you're<00:18:21.000> if<00:18:21.299> you're<00:18:21.660> a<00:18:21.960> team<00:18:22.740> and<00:18:23.400> you're 00:18:23.570 --> 00:18:23.580 align:start position:0% um if you're if you're a team and you're 00:18:23.580 --> 00:18:26.570 align:start position:0% um if you're if you're a team and you're engaging<00:18:24.120> auditors 00:18:26.570 --> 00:18:26.580 align:start position:0% engaging auditors 00:18:26.580 --> 00:18:27.470 align:start position:0% engaging auditors um 00:18:27.470 --> 00:18:27.480 align:start position:0% um 00:18:27.480 --> 00:18:29.990 align:start position:0% um it<00:18:28.140> as<00:18:28.620> opposed<00:18:28.919> to<00:18:28.919> you<00:18:29.460> want<00:18:29.580> to<00:18:29.700> have<00:18:29.820> common 00:18:29.990 --> 00:18:30.000 align:start position:0% it as opposed to you want to have common 00:18:30.000 --> 00:18:31.909 align:start position:0% it as opposed to you want to have common language<00:18:30.360> about<00:18:30.720> what<00:18:31.080> will<00:18:31.260> be<00:18:31.440> done<00:18:31.620> what 00:18:31.909 --> 00:18:31.919 align:start position:0% language about what will be done what 00:18:31.919 --> 00:18:34.850 align:start position:0% language about what will be done what what<00:18:32.419> won't<00:18:33.419> be<00:18:33.660> done 00:18:34.850 --> 00:18:34.860 align:start position:0% what won't be done 00:18:34.860 --> 00:18:37.970 align:start position:0% what won't be done but<00:18:35.280> this<00:18:35.520> is<00:18:35.700> people<00:18:36.480> also<00:18:37.140> and<00:18:37.440> people<00:18:37.679> with 00:18:37.970 --> 00:18:37.980 align:start position:0% but this is people also and people with 00:18:37.980 --> 00:18:40.430 align:start position:0% but this is people also and people with experience<00:18:38.580> so<00:18:38.880> I<00:18:39.120> think 00:18:40.430 --> 00:18:40.440 align:start position:0% experience so I think 00:18:40.440 --> 00:18:42.409 align:start position:0% experience so I think um<00:18:40.500> getting<00:18:40.980> to<00:18:41.460> know 00:18:42.409 --> 00:18:42.419 align:start position:0% um getting to know 00:18:42.419 --> 00:18:44.810 align:start position:0% um getting to know who<00:18:42.900> are<00:18:43.080> the<00:18:43.200> actual<00:18:43.500> Auditors<00:18:44.039> and<00:18:44.340> not<00:18:44.580> just 00:18:44.810 --> 00:18:44.820 align:start position:0% who are the actual Auditors and not just 00:18:44.820 --> 00:18:46.190 align:start position:0% who are the actual Auditors and not just I<00:18:45.240> think<00:18:45.419> we<00:18:45.539> were<00:18:45.660> talking<00:18:45.840> about<00:18:46.020> this 00:18:46.190 --> 00:18:46.200 align:start position:0% I think we were talking about this 00:18:46.200 --> 00:18:49.549 align:start position:0% I think we were talking about this before<00:18:46.440> not<00:18:46.799> just<00:18:47.039> the<00:18:47.940> team<00:18:48.240> or<00:18:48.600> the 00:18:49.549 --> 00:18:49.559 align:start position:0% before not just the team or the 00:18:49.559 --> 00:18:52.010 align:start position:0% before not just the team or the you<00:18:50.160> know<00:18:50.220> the<00:18:50.520> label<00:18:51.000> but<00:18:51.480> who<00:18:51.660> are<00:18:51.840> the 00:18:52.010 --> 00:18:52.020 align:start position:0% you know the label but who are the 00:18:52.020 --> 00:18:54.169 align:start position:0% you know the label but who are the specific<00:18:52.380> people<00:18:52.679> what<00:18:53.220> is<00:18:53.400> their<00:18:53.640> experience 00:18:54.169 --> 00:18:54.179 align:start position:0% specific people what is their experience 00:18:54.179 --> 00:18:55.909 align:start position:0% specific people what is their experience because<00:18:54.900> those<00:18:55.260> are<00:18:55.380> the<00:18:55.500> people<00:18:55.620> you're 00:18:55.909 --> 00:18:55.919 align:start position:0% because those are the people you're 00:18:55.919 --> 00:18:58.010 align:start position:0% because those are the people you're going<00:18:56.100> to<00:18:56.160> be<00:18:56.280> working<00:18:56.520> with<00:18:56.880> and<00:18:57.240> and<00:18:57.480> what's 00:18:58.010 --> 00:18:58.020 align:start position:0% going to be working with and and what's 00:18:58.020 --> 00:18:59.930 align:start position:0% going to be working with and and what's more<00:18:58.260> important<00:18:58.559> probably<00:18:58.799> than<00:18:59.220> standards 00:18:59.930 --> 00:18:59.940 align:start position:0% more important probably than standards 00:18:59.940 --> 00:19:01.549 align:start position:0% more important probably than standards is 00:19:01.549 --> 00:19:01.559 align:start position:0% is 00:19:01.559 --> 00:19:04.250 align:start position:0% is agreement<00:19:02.400> with<00:19:02.940> who<00:19:03.480> who's<00:19:03.780> going<00:19:04.140> to 00:19:04.250 --> 00:19:04.260 align:start position:0% agreement with who who's going to 00:19:04.260 --> 00:19:06.650 align:start position:0% agreement with who who's going to provide<00:19:04.500> you<00:19:04.679> the<00:19:04.919> security<00:19:05.160> review<00:19:05.700> and<00:19:06.419> who 00:19:06.650 --> 00:19:06.660 align:start position:0% provide you the security review and who 00:19:06.660 --> 00:19:08.330 align:start position:0% provide you the security review and who are<00:19:06.780> those<00:19:07.080> people<00:19:07.380> and<00:19:07.799> what<00:19:08.039> are<00:19:08.160> their 00:19:08.330 --> 00:19:08.340 align:start position:0% are those people and what are their 00:19:08.340 --> 00:19:09.950 align:start position:0% are those people and what are their skills<00:19:08.640> and<00:19:08.760> what<00:19:08.940> are<00:19:09.059> their<00:19:09.299> ex<00:19:09.600> what's 00:19:09.950 --> 00:19:09.960 align:start position:0% skills and what are their ex what's 00:19:09.960 --> 00:19:12.470 align:start position:0% skills and what are their ex what's their<00:19:10.260> experience<00:19:10.620> yeah<00:19:11.340> so<00:19:11.760> I'm<00:19:12.000> gonna<00:19:12.059> like 00:19:12.470 --> 00:19:12.480 align:start position:0% their experience yeah so I'm gonna like 00:19:12.480 --> 00:19:14.810 align:start position:0% their experience yeah so I'm gonna like that<00:19:12.840> I'm<00:19:13.500> gonna<00:19:13.620> go<00:19:13.860> to<00:19:13.980> the<00:19:14.100> other<00:19:14.280> side<00:19:14.580> of 00:19:14.810 --> 00:19:14.820 align:start position:0% that I'm gonna go to the other side of 00:19:14.820 --> 00:19:16.850 align:start position:0% that I'm gonna go to the other side of that<00:19:15.000> the<00:19:15.660> interpretation<00:19:16.140> of<00:19:16.440> the<00:19:16.620> question 00:19:16.850 --> 00:19:16.860 align:start position:0% that the interpretation of the question 00:19:16.860 --> 00:19:20.390 align:start position:0% that the interpretation of the question of<00:19:17.520> standards<00:19:18.120> and<00:19:18.440> well<00:19:19.440> I'm<00:19:19.679> re<00:19:19.860> I'm<00:19:20.280> going 00:19:20.390 --> 00:19:20.400 align:start position:0% of standards and well I'm re I'm going 00:19:20.400 --> 00:19:23.930 align:start position:0% of standards and well I'm re I'm going to<00:19:20.580> just<00:19:20.940> steal<00:19:21.240> the<00:19:21.419> phrasing<00:19:22.039> uh<00:19:23.039> from 00:19:23.930 --> 00:19:23.940 align:start position:0% to just steal the phrasing uh from 00:19:23.940 --> 00:19:25.909 align:start position:0% to just steal the phrasing uh from of<00:19:24.419> Rickard<00:19:24.900> who<00:19:25.320> I<00:19:25.440> was<00:19:25.559> talking<00:19:25.620> to<00:19:25.799> the 00:19:25.909 --> 00:19:25.919 align:start position:0% of Rickard who I was talking to the 00:19:25.919 --> 00:19:27.049 align:start position:0% of Rickard who I was talking to the other<00:19:26.039> day 00:19:27.049 --> 00:19:27.059 align:start position:0% other day 00:19:27.059 --> 00:19:30.830 align:start position:0% other day um<00:19:27.480> he<00:19:27.900> said<00:19:28.020> who<00:19:28.200> odds<00:19:28.559> the<00:19:28.679> Auditors<00:19:29.100> and 00:19:30.830 --> 00:19:30.840 align:start position:0% um he said who odds the Auditors and 00:19:30.840 --> 00:19:33.770 align:start position:0% um he said who odds the Auditors and and<00:19:31.260> so<00:19:31.799> you<00:19:32.280> know<00:19:32.340> as<00:19:32.640> a<00:19:32.880> project<00:19:33.059> and<00:19:33.480> I 00:19:33.770 --> 00:19:33.780 align:start position:0% and so you know as a project and I 00:19:33.780 --> 00:19:35.690 align:start position:0% and so you know as a project and I experience<00:19:34.200> this<00:19:34.380> now 00:19:35.690 --> 00:19:35.700 align:start position:0% experience this now 00:19:35.700 --> 00:19:37.610 align:start position:0% experience this now as<00:19:36.299> somebody<00:19:36.480> who's<00:19:36.720> audited<00:19:37.140> before<00:19:37.320> and 00:19:37.610 --> 00:19:37.620 align:start position:0% as somebody who's audited before and 00:19:37.620 --> 00:19:39.890 align:start position:0% as somebody who's audited before and understands<00:19:38.160> the<00:19:38.280> industry<00:19:38.640> far<00:19:39.360> better<00:19:39.660> than 00:19:39.890 --> 00:19:39.900 align:start position:0% understands the industry far better than 00:19:39.900 --> 00:19:41.210 align:start position:0% understands the industry far better than most 00:19:41.210 --> 00:19:41.220 align:start position:0% most 00:19:41.220 --> 00:19:43.669 align:start position:0% most still<00:19:41.580> scary<00:19:41.940> like<00:19:42.600> talking<00:19:42.900> to<00:19:43.140> like<00:19:43.440> trying 00:19:43.669 --> 00:19:43.679 align:start position:0% still scary like talking to like trying 00:19:43.679 --> 00:19:44.990 align:start position:0% still scary like talking to like trying to<00:19:43.799> evaluate 00:19:44.990 --> 00:19:45.000 align:start position:0% to evaluate 00:19:45.000 --> 00:19:47.090 align:start position:0% to evaluate the<00:19:45.480> auditor<00:19:45.840> like<00:19:46.080> for<00:19:46.320> the<00:19:46.440> code<00:19:46.620> that<00:19:46.980> I 00:19:47.090 --> 00:19:47.100 align:start position:0% the auditor like for the code that I 00:19:47.100 --> 00:19:49.850 align:start position:0% the auditor like for the code that I have<00:19:47.280> that<00:19:47.580> I<00:19:47.760> want<00:19:47.820> looked<00:19:48.299> at<00:19:48.419> does<00:19:49.140> this<00:19:49.500> is 00:19:49.850 --> 00:19:49.860 align:start position:0% have that I want looked at does this is 00:19:49.860 --> 00:19:52.070 align:start position:0% have that I want looked at does this is this<00:19:50.039> the<00:19:50.160> right<00:19:50.340> audit<00:19:50.700> firm<00:19:51.000> and<00:19:51.660> do<00:19:51.960> they 00:19:52.070 --> 00:19:52.080 align:start position:0% this the right audit firm and do they 00:19:52.080 --> 00:19:54.289 align:start position:0% this the right audit firm and do they have<00:19:52.200> the<00:19:52.380> right<00:19:52.559> people<00:19:52.860> available<00:19:53.640> when<00:19:54.120> I 00:19:54.289 --> 00:19:54.299 align:start position:0% have the right people available when I 00:19:54.299 --> 00:19:55.970 align:start position:0% have the right people available when I it's<00:19:54.480> there's<00:19:54.660> so<00:19:54.900> many<00:19:55.020> moving<00:19:55.320> Parts<00:19:55.500> it's 00:19:55.970 --> 00:19:55.980 align:start position:0% it's there's so many moving Parts it's 00:19:55.980 --> 00:19:57.710 align:start position:0% it's there's so many moving Parts it's crazy 00:19:57.710 --> 00:19:57.720 align:start position:0% crazy 00:19:57.720 --> 00:19:59.810 align:start position:0% crazy um<00:19:58.140> but<00:19:58.679> back<00:19:58.980> to<00:19:59.100> that<00:19:59.220> who<00:19:59.400> are<00:19:59.520> as<00:19:59.640> the 00:19:59.810 --> 00:19:59.820 align:start position:0% um but back to that who are as the 00:19:59.820 --> 00:20:01.789 align:start position:0% um but back to that who are as the Auditors<00:20:00.120> like<00:20:00.299> is<00:20:00.480> there<00:20:00.660> some<00:20:00.900> way<00:20:01.140> that<00:20:01.620> we 00:20:01.789 --> 00:20:01.799 align:start position:0% Auditors like is there some way that we 00:20:01.799 --> 00:20:04.610 align:start position:0% Auditors like is there some way that we can<00:20:01.980> that<00:20:02.340> we<00:20:02.580> can<00:20:02.700> or<00:20:03.000> should<00:20:03.299> be 00:20:04.610 --> 00:20:04.620 align:start position:0% can that we can or should be 00:20:04.620 --> 00:20:07.310 align:start position:0% can that we can or should be holding<00:20:05.520> I<00:20:06.419> don't<00:20:06.539> want<00:20:06.660> to<00:20:06.780> go<00:20:06.900> back<00:20:07.020> to<00:20:07.200> like 00:20:07.310 --> 00:20:07.320 align:start position:0% holding I don't want to go back to like 00:20:07.320 --> 00:20:09.110 align:start position:0% holding I don't want to go back to like holding<00:20:07.799> otters<00:20:07.919> accountable<00:20:08.340> and<00:20:08.760> the<00:20:08.940> skin 00:20:09.110 --> 00:20:09.120 align:start position:0% holding otters accountable and the skin 00:20:09.120 --> 00:20:10.970 align:start position:0% holding otters accountable and the skin in<00:20:09.360> the<00:20:09.480> game<00:20:09.660> thing<00:20:10.320> that<00:20:10.500> we<00:20:10.620> can<00:20:10.740> go<00:20:10.860> around 00:20:10.970 --> 00:20:10.980 align:start position:0% in the game thing that we can go around 00:20:10.980 --> 00:20:13.010 align:start position:0% in the game thing that we can go around round<00:20:11.220> about<00:20:11.460> but<00:20:11.760> yeah<00:20:12.360> like<00:20:12.480> how<00:20:12.720> can<00:20:12.840> how 00:20:13.010 --> 00:20:13.020 align:start position:0% round about but yeah like how can how 00:20:13.020 --> 00:20:14.590 align:start position:0% round about but yeah like how can how can<00:20:13.260> we<00:20:13.380> help 00:20:14.590 --> 00:20:14.600 align:start position:0% can we help 00:20:14.600 --> 00:20:17.810 align:start position:0% can we help non-honors<00:20:15.919> evaluate<00:20:16.919> the<00:20:17.340> Otters<00:20:17.520> that 00:20:17.810 --> 00:20:17.820 align:start position:0% non-honors evaluate the Otters that 00:20:17.820 --> 00:20:19.010 align:start position:0% non-honors evaluate the Otters that they're<00:20:17.940> working<00:20:18.120> with<00:20:18.299> should<00:20:18.600> there<00:20:18.780> be 00:20:19.010 --> 00:20:19.020 align:start position:0% they're working with should there be 00:20:19.020 --> 00:20:20.450 align:start position:0% they're working with should there be some<00:20:19.320> kind<00:20:19.559> of 00:20:20.450 --> 00:20:20.460 align:start position:0% some kind of 00:20:20.460 --> 00:20:24.110 align:start position:0% some kind of third-party<00:20:21.240> Watchdog<00:20:21.900> that's<00:20:22.520> ranking<00:20:23.520> you 00:20:24.110 --> 00:20:24.120 align:start position:0% third-party Watchdog that's ranking you 00:20:24.120 --> 00:20:26.990 align:start position:0% third-party Watchdog that's ranking you all<00:20:24.299> or<00:20:24.539> what<00:20:24.900> like<00:20:25.440> there's<00:20:25.679> a<00:20:25.860> I<00:20:26.340> think<00:20:26.580> it's 00:20:26.990 --> 00:20:27.000 align:start position:0% all or what like there's a I think it's 00:20:27.000 --> 00:20:29.570 align:start position:0% all or what like there's a I think it's a<00:20:27.179> place<00:20:27.360> like<00:20:27.720> this<00:20:27.900> a<00:20:28.260> good<00:20:28.380> plug<00:20:28.679> here<00:20:29.280> would 00:20:29.570 --> 00:20:29.580 align:start position:0% a place like this a good plug here would 00:20:29.580 --> 00:20:32.570 align:start position:0% a place like this a good plug here would be<00:20:29.700> like<00:20:29.880> to<00:20:30.120> talk<00:20:30.240> about<00:20:30.360> each<00:20:30.600> trust<00:20:31.100> and<00:20:32.100> I 00:20:32.570 --> 00:20:32.580 align:start position:0% be like to talk about each trust and I 00:20:32.580 --> 00:20:34.610 align:start position:0% be like to talk about each trust and I think<00:20:32.700> we<00:20:33.120> all<00:20:33.419> participated<00:20:34.020> in<00:20:34.380> the 00:20:34.610 --> 00:20:34.620 align:start position:0% think we all participated in the 00:20:34.620 --> 00:20:37.250 align:start position:0% think we all participated in the standard<00:20:34.980> in<00:20:35.220> one<00:20:35.520> form<00:20:36.120> or<00:20:36.360> another<00:20:36.539> and<00:20:37.140> I 00:20:37.250 --> 00:20:37.260 align:start position:0% standard in one form or another and I 00:20:37.260 --> 00:20:38.570 align:start position:0% standard in one form or another and I think<00:20:37.320> it's<00:20:37.440> like<00:20:37.679> a<00:20:37.860> dangerous<00:20:38.160> proposition 00:20:38.570 --> 00:20:38.580 align:start position:0% think it's like a dangerous proposition 00:20:38.580 --> 00:20:40.250 align:start position:0% think it's like a dangerous proposition because<00:20:38.820> what<00:20:39.120> the<00:20:39.360> the<00:20:39.480> proposition<00:20:39.900> of<00:20:40.140> each 00:20:40.250 --> 00:20:40.260 align:start position:0% because what the the proposition of each 00:20:40.260 --> 00:20:43.430 align:start position:0% because what the the proposition of each trust<00:20:40.559> is<00:20:40.740> that<00:20:40.860> there's<00:20:41.039> levels<00:20:41.700> of<00:20:42.440> how 00:20:43.430 --> 00:20:43.440 align:start position:0% trust is that there's levels of how 00:20:43.440 --> 00:20:45.770 align:start position:0% trust is that there's levels of how secure<00:20:44.100> your<00:20:44.400> code<00:20:44.640> bases<00:20:45.240> there's<00:20:45.419> like<00:20:45.660> kind 00:20:45.770 --> 00:20:45.780 align:start position:0% secure your code bases there's like kind 00:20:45.780 --> 00:20:47.810 align:start position:0% secure your code bases there's like kind of<00:20:45.840> a<00:20:45.960> risk<00:20:46.260> assessment<00:20:46.620> of<00:20:46.919> how<00:20:47.340> your<00:20:47.640> code 00:20:47.810 --> 00:20:47.820 align:start position:0% of a risk assessment of how your code 00:20:47.820 --> 00:20:49.669 align:start position:0% of a risk assessment of how your code base<00:20:48.059> will<00:20:48.299> look<00:20:48.419> like<00:20:48.600> after<00:20:48.840> you<00:20:49.200> have<00:20:49.380> done 00:20:49.669 --> 00:20:49.679 align:start position:0% base will look like after you have done 00:20:49.679 --> 00:20:52.789 align:start position:0% base will look like after you have done certain<00:20:50.039> things<00:20:50.340> right<00:20:50.880> so<00:20:51.179> so<00:20:51.419> this<00:20:51.780> this<00:20:52.080> uh 00:20:52.789 --> 00:20:52.799 align:start position:0% certain things right so so this this uh 00:20:52.799 --> 00:20:54.350 align:start position:0% certain things right so so this this uh this<00:20:53.160> is<00:20:53.220> part<00:20:53.400> of<00:20:53.520> the<00:20:53.640> eea<00:20:54.059> the<00:20:54.240> Enterprise 00:20:54.350 --> 00:20:54.360 align:start position:0% this is part of the eea the Enterprise 00:20:54.360 --> 00:20:56.390 align:start position:0% this is part of the eea the Enterprise ethereum<00:20:54.960> Alliance<00:20:55.320> and<00:20:55.500> I<00:20:55.620> think<00:20:55.679> it<00:20:55.799> was<00:20:55.919> uh 00:20:56.390 --> 00:20:56.400 align:start position:0% ethereum Alliance and I think it was uh 00:20:56.400 --> 00:20:58.789 align:start position:0% ethereum Alliance and I think it was uh Tomlin<00:20:57.179> who<00:20:57.660> started<00:20:57.900> it<00:20:58.020> I<00:20:58.320> think<00:20:58.380> it<00:20:58.559> is<00:20:58.679> a 00:20:58.789 --> 00:20:58.799 align:start position:0% Tomlin who started it I think it is a 00:20:58.799 --> 00:21:00.230 align:start position:0% Tomlin who started it I think it is a dangerous<00:20:59.100> proposition<00:20:59.580> but<00:20:59.880> it<00:21:00.000> might 00:21:00.230 --> 00:21:00.240 align:start position:0% dangerous proposition but it might 00:21:00.240 --> 00:21:02.810 align:start position:0% dangerous proposition but it might actually<00:21:00.419> be<00:21:00.660> helpful<00:21:01.020> if<00:21:01.260> you<00:21:01.559> are<00:21:02.220> not<00:21:02.520> super 00:21:02.810 --> 00:21:02.820 align:start position:0% actually be helpful if you are not super 00:21:02.820 --> 00:21:04.430 align:start position:0% actually be helpful if you are not super embedded<00:21:03.299> into<00:21:03.480> the<00:21:03.720> security<00:21:03.900> industry 00:21:04.430 --> 00:21:04.440 align:start position:0% embedded into the security industry 00:21:04.440 --> 00:21:06.950 align:start position:0% embedded into the security industry right<00:21:04.679> again<00:21:05.220> it<00:21:06.120> has 00:21:06.950 --> 00:21:06.960 align:start position:0% right again it has 00:21:06.960 --> 00:21:10.730 align:start position:0% right again it has it<00:21:07.620> is<00:21:07.860> useful<00:21:08.460> but<00:21:09.000> it<00:21:09.600> is<00:21:09.780> it<00:21:10.320> should<00:21:10.620> be 00:21:10.730 --> 00:21:10.740 align:start position:0% it is useful but it is it should be 00:21:10.740 --> 00:21:12.110 align:start position:0% it is useful but it is it should be taken<00:21:10.980> with<00:21:11.100> a<00:21:11.280> grain<00:21:11.460> of<00:21:11.580> salt<00:21:11.760> because<00:21:12.000> like 00:21:12.110 --> 00:21:12.120 align:start position:0% taken with a grain of salt because like 00:21:12.120 --> 00:21:14.450 align:start position:0% taken with a grain of salt because like if<00:21:12.299> you<00:21:12.419> take<00:21:12.720> level<00:21:13.320> three<00:21:13.620> or<00:21:13.919> like<00:21:14.100> formal 00:21:14.450 --> 00:21:14.460 align:start position:0% if you take level three or like formal 00:21:14.460 --> 00:21:16.610 align:start position:0% if you take level three or like formal verification<00:21:14.880> as<00:21:15.179> I'm<00:21:15.360> gonna<00:21:15.480> say<00:21:15.720> it<00:21:15.900> that 00:21:16.610 --> 00:21:16.620 align:start position:0% verification as I'm gonna say it that 00:21:16.620 --> 00:21:19.549 align:start position:0% verification as I'm gonna say it that will<00:21:17.039> probably<00:21:17.460> be<00:21:18.059> a<00:21:18.179> disservice<00:21:18.600> to<00:21:18.900> you<00:21:19.080> so 00:21:19.549 --> 00:21:19.559 align:start position:0% will probably be a disservice to you so 00:21:19.559 --> 00:21:23.570 align:start position:0% will probably be a disservice to you so I'm<00:21:20.840> mixed<00:21:21.840> based<00:21:22.200> on<00:21:22.260> getting<00:21:22.620> standards<00:21:23.280> for 00:21:23.570 --> 00:21:23.580 align:start position:0% I'm mixed based on getting standards for 00:21:23.580 --> 00:21:26.930 align:start position:0% I'm mixed based on getting standards for what<00:21:23.880> a<00:21:24.240> good<00:21:24.480> security<00:21:25.380> practice<00:21:25.799> looks<00:21:26.280> like 00:21:26.930 --> 00:21:26.940 align:start position:0% what a good security practice looks like 00:21:26.940 --> 00:21:30.169 align:start position:0% what a good security practice looks like all<00:21:27.299> right<00:21:27.419> this<00:21:27.960> is<00:21:28.020> a<00:21:28.200> scary<00:21:28.380> one<00:21:28.679> so 00:21:30.169 --> 00:21:30.179 align:start position:0% all right this is a scary one so 00:21:30.179 --> 00:21:33.830 align:start position:0% all right this is a scary one so oh<00:21:30.659> but<00:21:31.080> I'll<00:21:31.200> go<00:21:31.380> ahead<00:21:31.559> I<00:21:32.280> actually<00:21:32.460> think<00:21:32.880> in 00:21:33.830 --> 00:21:33.840 align:start position:0% oh but I'll go ahead I actually think in 00:21:33.840 --> 00:21:37.909 align:start position:0% oh but I'll go ahead I actually think in terms<00:21:34.080> of<00:21:34.200> security<00:21:34.559> work<00:21:35.419> they're<00:21:36.419> and<00:21:37.200> and<00:21:37.679> I 00:21:37.909 --> 00:21:37.919 align:start position:0% terms of security work they're and and I 00:21:37.919 --> 00:21:40.690 align:start position:0% terms of security work they're and and I think<00:21:38.039> about<00:21:38.240> other<00:21:39.240> niches<00:21:39.840> of<00:21:40.020> Technology 00:21:40.690 --> 00:21:40.700 align:start position:0% think about other niches of Technology 00:21:40.700 --> 00:21:42.950 align:start position:0% think about other niches of Technology the<00:21:41.700> work<00:21:41.880> that 00:21:42.950 --> 00:21:42.960 align:start position:0% the work that 00:21:42.960 --> 00:21:45.350 align:start position:0% the work that let's<00:21:43.500> say<00:21:43.679> these<00:21:44.039> teams<00:21:44.280> here<00:21:44.460> do 00:21:45.350 --> 00:21:45.360 align:start position:0% let's say these teams here do 00:21:45.360 --> 00:21:47.630 align:start position:0% let's say these teams here do is<00:21:46.020> very<00:21:46.260> public 00:21:47.630 --> 00:21:47.640 align:start position:0% is very public 00:21:47.640 --> 00:21:49.850 align:start position:0% is very public it's<00:21:47.940> very<00:21:48.659> public 00:21:49.850 --> 00:21:49.860 align:start position:0% it's very public 00:21:49.860 --> 00:21:53.210 align:start position:0% it's very public so<00:21:50.340> in<00:21:50.640> some<00:21:50.760> sense<00:21:51.000> we're<00:21:51.419> watched<00:21:51.960> yeah<00:21:52.559> very 00:21:53.210 --> 00:21:53.220 align:start position:0% so in some sense we're watched yeah very 00:21:53.220 --> 00:21:54.230 align:start position:0% so in some sense we're watched yeah very closely 00:21:54.230 --> 00:21:54.240 align:start position:0% closely 00:21:54.240 --> 00:21:57.350 align:start position:0% closely and<00:21:54.780> so<00:21:54.960> this<00:21:55.260> idea<00:21:55.620> that<00:21:56.039> so<00:21:56.520> our<00:21:56.820> reputations 00:21:57.350 --> 00:21:57.360 align:start position:0% and so this idea that so our reputations 00:21:57.360 --> 00:22:00.230 align:start position:0% and so this idea that so our reputations are<00:21:57.840> on<00:21:58.020> the<00:21:58.200> line<00:21:58.320> all<00:21:58.860> the<00:21:59.039> time<00:21:59.280> all<00:22:00.059> the 00:22:00.230 --> 00:22:00.240 align:start position:0% are on the line all the time all the 00:22:00.240 --> 00:22:03.649 align:start position:0% are on the line all the time all the time<00:22:00.419> and<00:22:01.320> honestly<00:22:02.000> I<00:22:03.000> know<00:22:03.059> all<00:22:03.240> of<00:22:03.419> us<00:22:03.480> up 00:22:03.649 --> 00:22:03.659 align:start position:0% time and honestly I know all of us up 00:22:03.659 --> 00:22:06.169 align:start position:0% time and honestly I know all of us up here<00:22:03.840> we<00:22:04.380> lose<00:22:04.860> sleep<00:22:05.159> over<00:22:05.400> it<00:22:05.640> right<00:22:05.820> like 00:22:06.169 --> 00:22:06.179 align:start position:0% here we lose sleep over it right like 00:22:06.179 --> 00:22:08.630 align:start position:0% here we lose sleep over it right like and<00:22:06.480> and<00:22:06.840> I<00:22:07.260> will<00:22:07.440> say<00:22:07.620> too<00:22:07.919> that<00:22:08.220> like<00:22:08.460> it 00:22:08.630 --> 00:22:08.640 align:start position:0% and and I will say too that like it 00:22:08.640 --> 00:22:10.490 align:start position:0% and and I will say too that like it opens<00:22:08.940> up<00:22:09.059> when<00:22:09.240> we<00:22:09.419> work<00:22:09.600> and<00:22:09.900> opens<00:22:10.260> up<00:22:10.380> on 00:22:10.490 --> 00:22:10.500 align:start position:0% opens up when we work and opens up on 00:22:10.500 --> 00:22:12.830 align:start position:0% opens up when we work and opens up on contracts<00:22:10.980> and<00:22:11.159> we've<00:22:11.340> had<00:22:11.520> issues<00:22:12.000> and<00:22:12.360> you 00:22:12.830 --> 00:22:12.840 align:start position:0% contracts and we've had issues and you 00:22:12.840 --> 00:22:15.230 align:start position:0% contracts and we've had issues and you know<00:22:12.960> so<00:22:13.200> we're<00:22:13.740> our<00:22:14.039> reputations<00:22:14.580> are<00:22:15.059> very 00:22:15.230 --> 00:22:15.240 align:start position:0% know so we're our reputations are very 00:22:15.240 --> 00:22:18.409 align:start position:0% know so we're our reputations are very public<00:22:15.620> and<00:22:16.620> we're<00:22:17.220> all<00:22:17.340> glad<00:22:17.640> we're<00:22:17.880> not<00:22:18.120> on 00:22:18.409 --> 00:22:18.419 align:start position:0% public and we're all glad we're not on 00:22:18.419 --> 00:22:21.350 align:start position:0% public and we're all glad we're not on the<00:22:18.780> rec<00:22:18.900> leaderboard<00:22:19.500> and<00:22:20.640> um<00:22:20.700> so<00:22:21.059> we<00:22:21.240> can 00:22:21.350 --> 00:22:21.360 align:start position:0% the rec leaderboard and um so we can 00:22:21.360 --> 00:22:23.029 align:start position:0% the rec leaderboard and um so we can talk<00:22:21.539> about<00:22:21.780> I<00:22:22.140> think<00:22:22.260> it's<00:22:22.500> perfectly 00:22:23.029 --> 00:22:23.039 align:start position:0% talk about I think it's perfectly 00:22:23.039 --> 00:22:25.909 align:start position:0% talk about I think it's perfectly healthy<00:22:23.460> to<00:22:23.700> have<00:22:23.820> conversations<00:22:24.480> about<00:22:25.260> how 00:22:25.909 --> 00:22:25.919 align:start position:0% healthy to have conversations about how 00:22:25.919 --> 00:22:28.549 align:start position:0% healthy to have conversations about how could<00:22:26.159> we<00:22:27.000> provide<00:22:27.360> more<00:22:27.659> transparency<00:22:28.200> and 00:22:28.549 --> 00:22:28.559 align:start position:0% could we provide more transparency and 00:22:28.559 --> 00:22:30.289 align:start position:0% could we provide more transparency and more<00:22:28.740> info<00:22:29.100> but<00:22:29.280> I<00:22:29.460> think<00:22:29.580> we<00:22:29.880> are<00:22:30.000> actually 00:22:30.289 --> 00:22:30.299 align:start position:0% more info but I think we are actually 00:22:30.299 --> 00:22:33.289 align:start position:0% more info but I think we are actually very<00:22:30.720> yeah<00:22:31.500> well<00:22:31.980> watched<00:22:32.340> right<00:22:32.580> now<00:22:32.760> okay 00:22:33.289 --> 00:22:33.299 align:start position:0% very yeah well watched right now okay 00:22:33.299 --> 00:22:35.210 align:start position:0% very yeah well watched right now okay yeah<00:22:33.600> now<00:22:34.020> now<00:22:34.260> there<00:22:34.559> still<00:22:34.740> is<00:22:34.860> the<00:22:35.100> thing 00:22:35.210 --> 00:22:35.220 align:start position:0% yeah now now there still is the thing 00:22:35.220 --> 00:22:37.310 align:start position:0% yeah now now there still is the thing about<00:22:35.400> what's<00:22:35.700> the<00:22:35.940> right<00:22:36.120> match<00:22:36.480> for<00:22:36.840> you<00:22:37.080> as 00:22:37.310 --> 00:22:37.320 align:start position:0% about what's the right match for you as 00:22:37.320 --> 00:22:38.810 align:start position:0% about what's the right match for you as a<00:22:37.500> project<00:22:37.679> and<00:22:38.039> I<00:22:38.220> think<00:22:38.340> that's<00:22:38.580> an 00:22:38.810 --> 00:22:38.820 align:start position:0% a project and I think that's an 00:22:38.820 --> 00:22:41.690 align:start position:0% a project and I think that's an important<00:22:39.120> consideration<00:22:39.840> yeah<00:22:40.440> yeah<00:22:40.679> and<00:22:41.220> I 00:22:41.690 --> 00:22:41.700 align:start position:0% important consideration yeah yeah and I 00:22:41.700 --> 00:22:43.190 align:start position:0% important consideration yeah yeah and I like<00:22:41.820> how<00:22:41.940> you<00:22:42.120> said<00:22:42.240> like<00:22:42.419> you<00:22:42.780> lose<00:22:42.960> sleep 00:22:43.190 --> 00:22:43.200 align:start position:0% like how you said like you lose sleep 00:22:43.200 --> 00:22:45.529 align:start position:0% like how you said like you lose sleep over<00:22:43.440> it<00:22:43.679> I<00:22:44.340> think<00:22:44.460> you<00:22:44.880> know<00:22:45.000> everybody<00:22:45.179> in 00:22:45.529 --> 00:22:45.539 align:start position:0% over it I think you know everybody in 00:22:45.539 --> 00:22:48.169 align:start position:0% over it I think you know everybody in this<00:22:45.659> room<00:22:45.780> loses<00:22:46.200> sleep<00:22:46.500> about<00:22:47.100> either<00:22:47.940> the 00:22:48.169 --> 00:22:48.179 align:start position:0% this room loses sleep about either the 00:22:48.179 --> 00:22:50.210 align:start position:0% this room loses sleep about either the code<00:22:48.360> that<00:22:48.539> they're<00:22:48.780> running<00:22:48.960> or<00:22:49.799> the<00:22:50.100> code 00:22:50.210 --> 00:22:50.220 align:start position:0% code that they're running or the code 00:22:50.220 --> 00:22:52.970 align:start position:0% code that they're running or the code that<00:22:50.400> they're<00:22:50.580> auditing<00:22:51.059> so 00:22:52.970 --> 00:22:52.980 align:start position:0% that they're auditing so 00:22:52.980 --> 00:22:55.549 align:start position:0% that they're auditing so should<00:22:53.400> all<00:22:53.580> go<00:22:53.700> easier<00:22:53.940> on<00:22:54.059> ourselves<00:22:54.840> um<00:22:54.900> so 00:22:55.549 --> 00:22:55.559 align:start position:0% should all go easier on ourselves um so 00:22:55.559 --> 00:22:58.190 align:start position:0% should all go easier on ourselves um so I<00:22:55.740> just<00:22:55.860> want<00:22:55.980> like<00:22:56.640> I<00:22:56.940> think<00:22:57.059> it'd<00:22:57.600> be<00:22:57.720> fun<00:22:57.960> to 00:22:58.190 --> 00:22:58.200 align:start position:0% I just want like I think it'd be fun to 00:22:58.200 --> 00:23:00.710 align:start position:0% I just want like I think it'd be fun to get<00:22:58.380> some<00:22:58.559> questions<00:22:58.860> from<00:22:59.280> the<00:22:59.460> audience<00:22:59.820> uh 00:23:00.710 --> 00:23:00.720 align:start position:0% get some questions from the audience uh 00:23:00.720 --> 00:23:02.630 align:start position:0% get some questions from the audience uh so<00:23:00.960> if<00:23:01.260> you<00:23:01.380> have<00:23:01.500> a<00:23:01.740> question<00:23:01.919> raise<00:23:02.340> your 00:23:02.630 --> 00:23:02.640 align:start position:0% so if you have a question raise your 00:23:02.640 --> 00:23:05.390 align:start position:0% so if you have a question raise your hand<00:23:02.900> uh<00:23:03.900> and<00:23:04.200> meanwhile<00:23:04.620> while<00:23:04.860> the<00:23:05.039> mics<00:23:05.220> are 00:23:05.390 --> 00:23:05.400 align:start position:0% hand uh and meanwhile while the mics are 00:23:05.400 --> 00:23:06.529 align:start position:0% hand uh and meanwhile while the mics are getting<00:23:05.520> handed<00:23:05.880> out<00:23:06.000> we're<00:23:06.240> gonna<00:23:06.299> try 00:23:06.529 --> 00:23:06.539 align:start position:0% getting handed out we're gonna try 00:23:06.539 --> 00:23:08.690 align:start position:0% getting handed out we're gonna try something<00:23:06.780> overrated<00:23:07.679> underrated<00:23:08.220> lightning 00:23:08.690 --> 00:23:08.700 align:start position:0% something overrated underrated lightning 00:23:08.700 --> 00:23:09.830 align:start position:0% something overrated underrated lightning round 00:23:09.830 --> 00:23:09.840 align:start position:0% round 00:23:09.840 --> 00:23:13.730 align:start position:0% round no<00:23:10.200> people<00:23:10.440> no<00:23:10.679> firms<00:23:11.220> these<00:23:12.000> are<00:23:12.059> Concepts<00:23:12.740> uh 00:23:13.730 --> 00:23:13.740 align:start position:0% no people no firms these are Concepts uh 00:23:13.740 --> 00:23:20.210 align:start position:0% no people no firms these are Concepts uh okay<00:23:14.360> so<00:23:15.679> where<00:23:16.679> should<00:23:16.980> we<00:23:17.340> start<00:23:17.760> uh 00:23:20.210 --> 00:23:20.220 align:start position:0% okay so where should we start uh 00:23:20.220 --> 00:23:22.570 align:start position:0% okay so where should we start uh Nick 00:23:22.570 --> 00:23:22.580 align:start position:0% Nick 00:23:22.580 --> 00:23:26.090 align:start position:0% Nick uh<00:23:23.580> plain<00:23:24.000> English<00:23:24.179> specs<00:23:25.080> overrated<00:23:25.740> or 00:23:26.090 --> 00:23:26.100 align:start position:0% uh plain English specs overrated or 00:23:26.100 --> 00:23:27.890 align:start position:0% uh plain English specs overrated or underrated 00:23:27.890 --> 00:23:27.900 align:start position:0% underrated 00:23:27.900 --> 00:23:32.990 align:start position:0% underrated uh<00:23:28.679> underrated<00:23:29.539> twice<00:23:31.039> it<00:23:32.039> it<00:23:32.340> I<00:23:32.820> was<00:23:32.880> actually 00:23:32.990 --> 00:23:33.000 align:start position:0% uh underrated twice it it I was actually 00:23:33.000 --> 00:23:35.029 align:start position:0% uh underrated twice it it I was actually Jocelyn<00:23:33.659> Feist<00:23:33.960> is<00:23:34.080> here<00:23:34.200> is<00:23:34.380> the<00:23:34.740> head<00:23:34.860> of<00:23:34.980> our 00:23:35.029 --> 00:23:35.039 align:start position:0% Jocelyn Feist is here is the head of our 00:23:35.039 --> 00:23:36.770 align:start position:0% Jocelyn Feist is here is the head of our blockchain<00:23:35.400> and<00:23:35.880> he<00:23:36.179> was<00:23:36.299> saying<00:23:36.480> you<00:23:36.659> know 00:23:36.770 --> 00:23:36.780 align:start position:0% blockchain and he was saying you know 00:23:36.780 --> 00:23:38.690 align:start position:0% blockchain and he was saying you know you<00:23:37.080> can<00:23:37.140> pick<00:23:37.320> the<00:23:37.500> tool<00:23:37.740> you<00:23:38.039> can<00:23:38.159> you<00:23:38.520> can 00:23:38.690 --> 00:23:38.700 align:start position:0% you can pick the tool you can you can 00:23:38.700 --> 00:23:39.950 align:start position:0% you can pick the tool you can you can pick<00:23:38.820> how<00:23:39.000> it<00:23:39.120> is<00:23:39.240> that<00:23:39.360> you<00:23:39.480> want<00:23:39.600> if<00:23:39.780> if 00:23:39.950 --> 00:23:39.960 align:start position:0% pick how it is that you want if if 00:23:39.960 --> 00:23:41.870 align:start position:0% pick how it is that you want if if you're<00:23:40.200> not<00:23:40.440> able<00:23:40.860> to<00:23:41.100> put<00:23:41.280> down<00:23:41.460> in<00:23:41.700> English 00:23:41.870 --> 00:23:41.880 align:start position:0% you're not able to put down in English 00:23:41.880 --> 00:23:43.490 align:start position:0% you're not able to put down in English what<00:23:42.240> what<00:23:42.419> are<00:23:42.659> the<00:23:42.720> invariants<00:23:43.140> what<00:23:43.440> are 00:23:43.490 --> 00:23:43.500 align:start position:0% what what are the invariants what are 00:23:43.500 --> 00:23:44.390 align:start position:0% what what are the invariants what are the<00:23:43.620> things<00:23:43.740> that<00:23:43.919> you're<00:23:43.980> trying<00:23:44.220> to 00:23:44.390 --> 00:23:44.400 align:start position:0% the things that you're trying to 00:23:44.400 --> 00:23:46.370 align:start position:0% the things that you're trying to accomplish<00:23:44.700> here<00:23:44.880> you're<00:23:45.780> you<00:23:46.020> know<00:23:46.140> once<00:23:46.380> you 00:23:46.370 --> 00:23:46.380 align:start position:0% accomplish here you're you know once you 00:23:46.380 --> 00:23:48.289 align:start position:0% accomplish here you're you know once you do<00:23:46.559> that<00:23:46.679> you're<00:23:46.860> 75<00:23:47.280> or<00:23:47.460> 80<00:23:47.640> of<00:23:48.000> the<00:23:48.179> way 00:23:48.289 --> 00:23:48.299 align:start position:0% do that you're 75 or 80 of the way 00:23:48.299 --> 00:23:50.149 align:start position:0% do that you're 75 or 80 of the way through 00:23:50.149 --> 00:23:50.159 align:start position:0% through 00:23:50.159 --> 00:23:51.770 align:start position:0% through it<00:23:50.580> also<00:23:50.820> it<00:23:50.940> just<00:23:51.059> speaks<00:23:51.360> to<00:23:51.419> a<00:23:51.539> number<00:23:51.659> of 00:23:51.770 --> 00:23:51.780 align:start position:0% it also it just speaks to a number of 00:23:51.780 --> 00:23:53.149 align:start position:0% it also it just speaks to a number of things<00:23:51.900> not<00:23:52.140> just<00:23:52.260> for<00:23:52.500> Security<00:23:52.679> review<00:23:52.980> but 00:23:53.149 --> 00:23:53.159 align:start position:0% things not just for Security review but 00:23:53.159 --> 00:23:54.409 align:start position:0% things not just for Security review but also<00:23:53.400> just<00:23:53.520> for<00:23:53.640> your<00:23:53.820> own<00:23:53.880> understanding 00:23:54.409 --> 00:23:54.419 align:start position:0% also just for your own understanding 00:23:54.419 --> 00:23:56.930 align:start position:0% also just for your own understanding yeah<00:23:54.539> to<00:23:54.960> be<00:23:55.440> able<00:23:55.679> to<00:23:55.799> declare<00:23:56.280> this<00:23:56.580> is<00:23:56.700> what 00:23:56.930 --> 00:23:56.940 align:start position:0% yeah to be able to declare this is what 00:23:56.940 --> 00:23:59.149 align:start position:0% yeah to be able to declare this is what this<00:23:57.179> thing<00:23:57.360> does<00:23:57.659> you<00:23:58.320> can't<00:23:58.440> put<00:23:58.620> a<00:23:58.799> value<00:23:58.919> on 00:23:59.149 --> 00:23:59.159 align:start position:0% this thing does you can't put a value on 00:23:59.159 --> 00:24:00.590 align:start position:0% this thing does you can't put a value on that<00:23:59.280> yeah<00:23:59.580> God 00:24:00.590 --> 00:24:00.600 align:start position:0% that yeah God 00:24:00.600 --> 00:24:02.450 align:start position:0% that yeah God uh<00:24:00.960> Gonzalo 00:24:02.450 --> 00:24:02.460 align:start position:0% uh Gonzalo 00:24:02.460 --> 00:24:05.149 align:start position:0% uh Gonzalo overrated<00:24:03.179> underrated<00:24:03.780> contract<00:24:04.740> upgrade 00:24:05.149 --> 00:24:05.159 align:start position:0% overrated underrated contract upgrade 00:24:05.159 --> 00:24:06.049 align:start position:0% overrated underrated contract upgrade ability 00:24:06.049 --> 00:24:06.059 align:start position:0% ability 00:24:06.059 --> 00:24:09.529 align:start position:0% ability so<00:24:06.960> overrated 00:24:09.529 --> 00:24:09.539 align:start position:0% so overrated 00:24:09.539 --> 00:24:10.850 align:start position:0% so overrated okay 00:24:10.850 --> 00:24:10.860 align:start position:0% okay 00:24:10.860 --> 00:24:11.870 align:start position:0% okay um 00:24:11.870 --> 00:24:11.880 align:start position:0% um 00:24:11.880 --> 00:24:14.390 align:start position:0% um expanding<00:24:12.539> upgradability<00:24:13.320> is<00:24:13.740> a<00:24:13.860> bug<00:24:14.039> not 00:24:14.390 --> 00:24:14.400 align:start position:0% expanding upgradability is a bug not 00:24:14.400 --> 00:24:17.210 align:start position:0% expanding upgradability is a bug not always<00:24:14.580> we<00:24:15.120> went<00:24:15.240> through<00:24:15.419> this<00:24:15.659> so<00:24:16.200> there's<00:24:16.980> a 00:24:17.210 --> 00:24:17.220 align:start position:0% always we went through this so there's a 00:24:17.220 --> 00:24:19.310 align:start position:0% always we went through this so there's a there's<00:24:17.580> a<00:24:17.880> longer<00:24:18.299> conversation<00:24:18.780> about<00:24:19.080> this 00:24:19.310 --> 00:24:19.320 align:start position:0% there's a longer conversation about this 00:24:19.320 --> 00:24:21.470 align:start position:0% there's a longer conversation about this that<00:24:19.559> happened<00:24:19.679> at<00:24:19.919> defy<00:24:20.340> security<00:24:20.520> Summit<00:24:21.059> I 00:24:21.470 --> 00:24:21.480 align:start position:0% that happened at defy security Summit I 00:24:21.480 --> 00:24:24.830 align:start position:0% that happened at defy security Summit I think<00:24:21.659> that<00:24:22.200> is<00:24:22.440> available<00:24:23.039> on<00:24:23.520> YouTube<00:24:23.700> so<00:24:24.360> I 00:24:24.830 --> 00:24:24.840 align:start position:0% think that is available on YouTube so I 00:24:24.840 --> 00:24:27.049 align:start position:0% think that is available on YouTube so I could<00:24:24.960> rent<00:24:25.200> on<00:24:25.559> and<00:24:25.740> on<00:24:25.919> about<00:24:26.159> this<00:24:26.640> there's 00:24:27.049 --> 00:24:27.059 align:start position:0% could rent on and on about this there's 00:24:27.059 --> 00:24:29.390 align:start position:0% could rent on and on about this there's also<00:24:27.299> a<00:24:27.480> bunch<00:24:27.720> of<00:24:27.840> articles<00:24:28.200> on<00:24:28.500> the<00:24:28.620> on<00:24:29.220> the 00:24:29.390 --> 00:24:29.400 align:start position:0% also a bunch of articles on the on the 00:24:29.400 --> 00:24:31.549 align:start position:0% also a bunch of articles on the on the internet<00:24:29.520> about<00:24:29.880> this<00:24:30.179> but<00:24:30.559> generally 00:24:31.549 --> 00:24:31.559 align:start position:0% internet about this but generally 00:24:31.559 --> 00:24:34.190 align:start position:0% internet about this but generally speaking<00:24:32.159> it<00:24:33.000> you<00:24:33.360> are<00:24:33.539> just<00:24:33.720> injecting 00:24:34.190 --> 00:24:34.200 align:start position:0% speaking it you are just injecting 00:24:34.200 --> 00:24:35.510 align:start position:0% speaking it you are just injecting another 00:24:35.510 --> 00:24:35.520 align:start position:0% another 00:24:35.520 --> 00:24:38.149 align:start position:0% another um<00:24:35.580> attack<00:24:36.240> Factory<00:24:36.600> in<00:24:37.020> your<00:24:37.140> code<00:24:37.320> base<00:24:37.559> okay 00:24:38.149 --> 00:24:38.159 align:start position:0% um attack Factory in your code base okay 00:24:38.159 --> 00:24:41.090 align:start position:0% um attack Factory in your code base okay all<00:24:38.700> right<00:24:38.880> uh<00:24:39.360> Chandra<00:24:39.900> uh<00:24:40.620> how<00:24:40.799> do<00:24:40.919> you<00:24:40.980> feel 00:24:41.090 --> 00:24:41.100 align:start position:0% all right uh Chandra uh how do you feel 00:24:41.100 --> 00:24:44.270 align:start position:0% all right uh Chandra uh how do you feel about<00:24:41.340> sorry<00:24:42.299> overrated<00:24:42.960> or<00:24:43.200> underrated 00:24:44.270 --> 00:24:44.280 align:start position:0% about sorry overrated or underrated 00:24:44.280 --> 00:24:47.210 align:start position:0% about sorry overrated or underrated reading<00:24:45.059> the<00:24:45.179> code<00:24:45.360> very<00:24:45.720> carefully 00:24:47.210 --> 00:24:47.220 align:start position:0% reading the code very carefully 00:24:47.220 --> 00:24:49.490 align:start position:0% reading the code very carefully truly<00:24:47.940> underrated<00:24:48.419> I<00:24:48.840> think<00:24:48.960> we<00:24:49.140> should<00:24:49.320> read 00:24:49.490 --> 00:24:49.500 align:start position:0% truly underrated I think we should read 00:24:49.500 --> 00:24:51.770 align:start position:0% truly underrated I think we should read code<00:24:49.860> extreme<00:24:50.700> we<00:24:51.000> can't<00:24:51.120> just<00:24:51.240> write<00:24:51.419> rules 00:24:51.770 --> 00:24:51.780 align:start position:0% code extreme we can't just write rules 00:24:51.780 --> 00:24:54.169 align:start position:0% code extreme we can't just write rules and<00:24:52.140> you<00:24:52.559> can't<00:24:52.679> just<00:24:52.860> write<00:24:53.039> rules<00:24:53.520> no<00:24:53.940> you 00:24:54.169 --> 00:24:54.179 align:start position:0% and you can't just write rules no you 00:24:54.179 --> 00:24:55.909 align:start position:0% and you can't just write rules no you definitely<00:24:54.600> need<00:24:54.840> to<00:24:55.080> understand<00:24:55.320> the<00:24:55.799> code 00:24:55.909 --> 00:24:55.919 align:start position:0% definitely need to understand the code 00:24:55.919 --> 00:24:57.289 align:start position:0% definitely need to understand the code before<00:24:56.220> you<00:24:56.520> start<00:24:56.640> writing<00:24:57.000> your<00:24:57.120> rules 00:24:57.289 --> 00:24:57.299 align:start position:0% before you start writing your rules 00:24:57.299 --> 00:24:58.970 align:start position:0% before you start writing your rules formal<00:24:57.900> verification<00:24:58.320> is<00:24:58.559> not<00:24:58.679> a<00:24:58.860> silver 00:24:58.970 --> 00:24:58.980 align:start position:0% formal verification is not a silver 00:24:58.980 --> 00:25:01.430 align:start position:0% formal verification is not a silver bullet<00:24:59.460> it's<00:25:00.419> definitely<00:25:00.900> not<00:25:01.140> a<00:25:01.260> silver 00:25:01.430 --> 00:25:01.440 align:start position:0% bullet it's definitely not a silver 00:25:01.440 --> 00:25:03.409 align:start position:0% bullet it's definitely not a silver bullet<00:25:01.799> but<00:25:02.100> really<00:25:02.280> but<00:25:02.460> really<00:25:02.640> like<00:25:02.880> how 00:25:03.409 --> 00:25:03.419 align:start position:0% bullet but really but really like how 00:25:03.419 --> 00:25:05.090 align:start position:0% bullet but really but really like how you<00:25:03.780> know<00:25:03.840> like<00:25:04.080> it's 00:25:05.090 --> 00:25:05.100 align:start position:0% you know like it's 00:25:05.100 --> 00:25:07.490 align:start position:0% you know like it's uh<00:25:05.940> how<00:25:06.299> do<00:25:06.419> you<00:25:06.600> know<00:25:06.840> what<00:25:07.200> kind<00:25:07.380> of 00:25:07.490 --> 00:25:07.500 align:start position:0% uh how do you know what kind of 00:25:07.500 --> 00:25:08.930 align:start position:0% uh how do you know what kind of guarantees<00:25:07.980> you're<00:25:08.220> getting<00:25:08.340> from<00:25:08.580> formal 00:25:08.930 --> 00:25:08.940 align:start position:0% guarantees you're getting from formal 00:25:08.940 --> 00:25:10.130 align:start position:0% guarantees you're getting from formal verification 00:25:10.130 --> 00:25:10.140 align:start position:0% verification 00:25:10.140 --> 00:25:13.610 align:start position:0% verification uh<00:25:10.919> I<00:25:11.100> mean<00:25:11.280> yeah<00:25:12.240> I<00:25:12.480> think<00:25:12.659> this<00:25:12.960> is<00:25:13.200> a<00:25:13.440> very 00:25:13.610 --> 00:25:13.620 align:start position:0% uh I mean yeah I think this is a very 00:25:13.620 --> 00:25:16.070 align:start position:0% uh I mean yeah I think this is a very good<00:25:13.799> question<00:25:13.980> right<00:25:14.340> like<00:25:14.640> you 00:25:16.070 --> 00:25:16.080 align:start position:0% good question right like you 00:25:16.080 --> 00:25:17.930 align:start position:0% good question right like you I<00:25:16.500> this<00:25:16.980> kind<00:25:17.100> of<00:25:17.220> goes<00:25:17.400> back<00:25:17.460> to<00:25:17.580> what<00:25:17.700> I<00:25:17.880> was 00:25:17.930 --> 00:25:17.940 align:start position:0% I this kind of goes back to what I was 00:25:17.940 --> 00:25:20.810 align:start position:0% I this kind of goes back to what I was saying<00:25:18.179> before<00:25:18.419> you<00:25:18.960> know<00:25:19.020> it's<00:25:19.799> important<00:25:20.220> to 00:25:20.810 --> 00:25:20.820 align:start position:0% saying before you know it's important to 00:25:20.820 --> 00:25:22.010 align:start position:0% saying before you know it's important to think<00:25:21.059> carefully<00:25:21.419> about<00:25:21.659> what<00:25:21.900> you're 00:25:22.010 --> 00:25:22.020 align:start position:0% think carefully about what you're 00:25:22.020 --> 00:25:25.789 align:start position:0% think carefully about what you're approving<00:25:22.500> right<00:25:22.860> and<00:25:23.820> your<00:25:24.240> spec<00:25:24.480> is<00:25:24.840> really 00:25:25.789 --> 00:25:25.799 align:start position:0% approving right and your spec is really 00:25:25.799 --> 00:25:29.330 align:start position:0% approving right and your spec is really all<00:25:26.279> you<00:25:26.460> have<00:25:26.779> and<00:25:27.779> uh<00:25:28.380> you<00:25:28.679> know<00:25:28.740> when<00:25:29.220> you 00:25:29.330 --> 00:25:29.340 align:start position:0% all you have and uh you know when you 00:25:29.340 --> 00:25:31.070 align:start position:0% all you have and uh you know when you say<00:25:29.520> that<00:25:29.700> okay<00:25:30.000> we<00:25:30.240> have<00:25:30.360> a<00:25:30.419> formal<00:25:30.720> guarantee 00:25:31.070 --> 00:25:31.080 align:start position:0% say that okay we have a formal guarantee 00:25:31.080 --> 00:25:32.570 align:start position:0% say that okay we have a formal guarantee you<00:25:31.200> should<00:25:31.380> be<00:25:31.559> very<00:25:31.799> careful<00:25:32.100> when<00:25:32.340> you<00:25:32.460> make 00:25:32.570 --> 00:25:32.580 align:start position:0% you should be very careful when you make 00:25:32.580 --> 00:25:33.890 align:start position:0% you should be very careful when you make these<00:25:32.820> kinds<00:25:33.000> of<00:25:33.059> claims<00:25:33.360> and<00:25:33.539> I<00:25:33.659> think<00:25:33.779> it's 00:25:33.890 --> 00:25:33.900 align:start position:0% these kinds of claims and I think it's 00:25:33.900 --> 00:25:35.210 align:start position:0% these kinds of claims and I think it's very<00:25:34.080> dangerous<00:25:34.440> to<00:25:34.620> make<00:25:34.679> these<00:25:34.919> claims 00:25:35.210 --> 00:25:35.220 align:start position:0% very dangerous to make these claims 00:25:35.220 --> 00:25:36.890 align:start position:0% very dangerous to make these claims because<00:25:35.400> you<00:25:36.179> know 00:25:36.890 --> 00:25:36.900 align:start position:0% because you know 00:25:36.900 --> 00:25:39.769 align:start position:0% because you know um the<00:25:37.620> spec<00:25:37.799> could<00:25:38.039> itself<00:25:38.340> be<00:25:38.520> wrong<00:25:38.779> and 00:25:39.769 --> 00:25:39.779 align:start position:0% um the spec could itself be wrong and 00:25:39.779 --> 00:25:41.930 align:start position:0% um the spec could itself be wrong and even<00:25:40.020> if<00:25:40.200> the<00:25:40.320> spec<00:25:40.559> is<00:25:40.860> reasonable<00:25:41.520> I<00:25:41.820> mean 00:25:41.930 --> 00:25:41.940 align:start position:0% even if the spec is reasonable I mean 00:25:41.940 --> 00:25:43.010 align:start position:0% even if the spec is reasonable I mean there<00:25:42.059> could<00:25:42.179> be<00:25:42.299> a<00:25:42.360> bug<00:25:42.480> in<00:25:42.659> the<00:25:42.779> formal 00:25:43.010 --> 00:25:43.020 align:start position:0% there could be a bug in the formal 00:25:43.020 --> 00:25:44.930 align:start position:0% there could be a bug in the formal verification<00:25:43.380> tool<00:25:43.860> and<00:25:44.039> like<00:25:44.220> then<00:25:44.520> that's 00:25:44.930 --> 00:25:44.940 align:start position:0% verification tool and like then that's 00:25:44.940 --> 00:25:47.390 align:start position:0% verification tool and like then that's you<00:25:45.179> know<00:25:45.240> that's<00:25:45.419> also<00:25:45.720> bad<00:25:45.900> and<00:25:46.320> uh<00:25:47.159> you<00:25:47.340> know 00:25:47.390 --> 00:25:47.400 align:start position:0% you know that's also bad and uh you know 00:25:47.400 --> 00:25:49.430 align:start position:0% you know that's also bad and uh you know just<00:25:47.760> because<00:25:47.940> there<00:25:48.360> is<00:25:48.480> a<00:25:48.960> specific<00:25:49.200> bug 00:25:49.430 --> 00:25:49.440 align:start position:0% just because there is a specific bug 00:25:49.440 --> 00:25:51.230 align:start position:0% just because there is a specific bug that<00:25:49.740> you<00:25:49.860> verify<00:25:50.220> verify<00:25:50.760> your<00:25:50.880> code<00:25:51.059> against 00:25:51.230 --> 00:25:51.240 align:start position:0% that you verify verify your code against 00:25:51.240 --> 00:25:53.810 align:start position:0% that you verify verify your code against does<00:25:51.539> not<00:25:51.720> mean<00:25:51.960> that<00:25:52.320> there's<00:25:52.980> uh<00:25:53.520> you<00:25:53.700> know 00:25:53.810 --> 00:25:53.820 align:start position:0% does not mean that there's uh you know 00:25:53.820 --> 00:25:55.789 align:start position:0% does not mean that there's uh you know it's<00:25:53.940> just<00:25:54.240> bulletproof<00:25:55.080> and<00:25:55.260> you<00:25:55.440> can<00:25:55.559> just 00:25:55.789 --> 00:25:55.799 align:start position:0% it's just bulletproof and you can just 00:25:55.799 --> 00:25:59.269 align:start position:0% it's just bulletproof and you can just trust<00:25:56.640> it<00:25:56.760> with<00:25:57.120> your<00:25:57.539> life<00:25:57.720> right<00:25:58.020> so 00:25:59.269 --> 00:25:59.279 align:start position:0% trust it with your life right so 00:25:59.279 --> 00:26:01.130 align:start position:0% trust it with your life right so um<00:25:59.340> yeah<00:25:59.700> okay 00:26:01.130 --> 00:26:01.140 align:start position:0% um yeah okay 00:26:01.140 --> 00:26:04.070 align:start position:0% um yeah okay um<00:26:01.200> many<00:26:02.039> yeah<00:26:02.580> Europe 00:26:04.070 --> 00:26:04.080 align:start position:0% um many yeah Europe 00:26:04.080 --> 00:26:06.830 align:start position:0% um many yeah Europe um<00:26:04.140> have<00:26:04.380> I<00:26:04.500> asked<00:26:04.740> everybody<00:26:04.860> something<00:26:05.840> okay 00:26:06.830 --> 00:26:06.840 align:start position:0% um have I asked everybody something okay 00:26:06.840 --> 00:26:08.810 align:start position:0% um have I asked everybody something okay all<00:26:07.320> right<00:26:07.380> so<00:26:07.500> you're<00:26:07.799> after<00:26:07.919> many<00:26:08.159> you'll 00:26:08.810 --> 00:26:08.820 align:start position:0% all right so you're after many you'll 00:26:08.820 --> 00:26:10.190 align:start position:0% all right so you're after many you'll get<00:26:09.000> something<00:26:09.179> don't<00:26:09.480> worry 00:26:10.190 --> 00:26:10.200 align:start position:0% get something don't worry 00:26:10.200 --> 00:26:10.850 align:start position:0% get something don't worry um 00:26:10.850 --> 00:26:10.860 align:start position:0% um 00:26:10.860 --> 00:26:12.610 align:start position:0% um Maddie 00:26:12.610 --> 00:26:12.620 align:start position:0% Maddie 00:26:12.620 --> 00:26:15.590 align:start position:0% Maddie alternate<00:26:13.620> virtual<00:26:14.159> machine<00:26:14.400> designs<00:26:15.059> so<00:26:15.299> not 00:26:15.590 --> 00:26:15.600 align:start position:0% alternate virtual machine designs so not 00:26:15.600 --> 00:26:16.909 align:start position:0% alternate virtual machine designs so not the<00:26:15.840> evm 00:26:16.909 --> 00:26:16.919 align:start position:0% the evm 00:26:16.919 --> 00:26:21.169 align:start position:0% the evm overrated<00:26:17.580> or<00:26:17.820> underage 00:26:21.169 --> 00:26:21.179 align:start position:0% 00:26:21.179 --> 00:26:22.789 align:start position:0% override<00:26:22.020> it 00:26:22.789 --> 00:26:22.799 align:start position:0% override it 00:26:22.799 --> 00:26:23.870 align:start position:0% override it okay 00:26:23.870 --> 00:26:23.880 align:start position:0% okay 00:26:23.880 --> 00:26:25.730 align:start position:0% okay I<00:26:24.360> don't<00:26:24.419> know<00:26:24.539> do<00:26:24.779> you<00:26:24.900> wish<00:26:25.020> to<00:26:25.200> qualify<00:26:25.559> that 00:26:25.730 --> 00:26:25.740 align:start position:0% I don't know do you wish to qualify that 00:26:25.740 --> 00:26:28.070 align:start position:0% I don't know do you wish to qualify that or<00:26:26.039> yeah<00:26:26.220> I<00:26:26.640> don't<00:26:26.700> know<00:26:26.760> I've<00:26:27.600> been<00:26:27.720> spending 00:26:28.070 --> 00:26:28.080 align:start position:0% or yeah I don't know I've been spending 00:26:28.080 --> 00:26:30.590 align:start position:0% or yeah I don't know I've been spending a<00:26:28.200> lot<00:26:28.320> of<00:26:28.440> time<00:26:28.620> in<00:26:28.919> on<00:26:29.400> the<00:26:29.580> evm<00:26:30.000> so<00:26:30.299> yeah 00:26:30.590 --> 00:26:30.600 align:start position:0% a lot of time in on the evm so yeah 00:26:30.600 --> 00:26:32.810 align:start position:0% a lot of time in on the evm so yeah getting<00:26:31.140> familiar<00:26:31.620> and<00:26:31.860> you<00:26:32.279> know<00:26:32.400> it's<00:26:32.640> got 00:26:32.810 --> 00:26:32.820 align:start position:0% getting familiar and you know it's got 00:26:32.820 --> 00:26:35.450 align:start position:0% getting familiar and you know it's got its<00:26:33.059> quirks.com<00:26:33.840> syndrome<00:26:34.440> probably<00:26:34.980> yeah 00:26:35.450 --> 00:26:35.460 align:start position:0% its quirks.com syndrome probably yeah 00:26:35.460 --> 00:26:37.250 align:start position:0% its quirks.com syndrome probably yeah probably<00:26:36.120> yeah 00:26:37.250 --> 00:26:37.260 align:start position:0% probably yeah 00:26:37.260 --> 00:26:38.870 align:start position:0% probably yeah um<00:26:37.320> look<00:26:37.559> now<00:26:37.799> we've<00:26:38.039> we've<00:26:38.400> we've<00:26:38.640> definitely 00:26:38.870 --> 00:26:38.880 align:start position:0% um look now we've we've we've definitely 00:26:38.880 --> 00:26:40.490 align:start position:0% um look now we've we've we've definitely done<00:26:39.419> a<00:26:39.600> bunch<00:26:39.659> of<00:26:39.779> security<00:26:39.960> assessments 00:26:40.490 --> 00:26:40.500 align:start position:0% done a bunch of security assessments 00:26:40.500 --> 00:26:41.690 align:start position:0% done a bunch of security assessments targeting<00:26:40.980> different<00:26:41.159> execution 00:26:41.690 --> 00:26:41.700 align:start position:0% targeting different execution 00:26:41.700 --> 00:26:44.210 align:start position:0% targeting different execution environments<00:26:42.539> don't<00:26:42.720> get<00:26:42.960> me<00:26:43.080> wrong 00:26:44.210 --> 00:26:44.220 align:start position:0% environments don't get me wrong 00:26:44.220 --> 00:26:47.870 align:start position:0% environments don't get me wrong um<00:26:44.340> but<00:26:44.820> obviously<00:26:45.480> most<00:26:46.080> developers<00:26:46.880> are 00:26:47.870 --> 00:26:47.880 align:start position:0% um but obviously most developers are 00:26:47.880 --> 00:26:51.230 align:start position:0% um but obviously most developers are operating<00:26:48.419> with<00:26:49.080> solidity<00:26:49.620> Viper<00:26:50.279> at<00:26:50.760> the<00:26:50.880> evm 00:26:51.230 --> 00:26:51.240 align:start position:0% operating with solidity Viper at the evm 00:26:51.240 --> 00:26:54.649 align:start position:0% operating with solidity Viper at the evm level<00:26:51.500> it's<00:26:52.500> got<00:26:52.679> its<00:26:52.980> quirks<00:26:53.400> but<00:26:54.000> it<00:26:54.240> it's 00:26:54.649 --> 00:26:54.659 align:start position:0% level it's got its quirks but it it's 00:26:54.659 --> 00:26:56.810 align:start position:0% level it's got its quirks but it it's kind<00:26:54.960> of<00:26:55.080> working<00:26:55.260> I'd<00:26:55.860> be<00:26:55.980> excited<00:26:56.340> to<00:26:56.520> see 00:26:56.810 --> 00:26:56.820 align:start position:0% kind of working I'd be excited to see 00:26:56.820 --> 00:26:59.690 align:start position:0% kind of working I'd be excited to see the<00:26:57.360> upcoming<00:26:58.080> upgrades<00:26:58.620> uh<00:26:59.340> particularly 00:26:59.690 --> 00:26:59.700 align:start position:0% the upcoming upgrades uh particularly 00:26:59.700 --> 00:27:04.190 align:start position:0% the upcoming upgrades uh particularly eof<00:27:00.440> AVM<00:27:01.440> object<00:27:01.679> files<00:27:02.059> that<00:27:03.059> might<00:27:03.360> change<00:27:03.840> a 00:27:04.190 --> 00:27:04.200 align:start position:0% eof AVM object files that might change a 00:27:04.200 --> 00:27:07.210 align:start position:0% eof AVM object files that might change a lot<00:27:04.320> of<00:27:04.440> things<00:27:04.679> with<00:27:05.220> regards<00:27:05.640> to<00:27:05.700> security 00:27:07.210 --> 00:27:07.220 align:start position:0% lot of things with regards to security 00:27:07.220 --> 00:27:09.230 align:start position:0% lot of things with regards to security guarantees<00:27:08.220> or<00:27:08.340> assumptions<00:27:08.760> that<00:27:09.000> we<00:27:09.120> make 00:27:09.230 --> 00:27:09.240 align:start position:0% guarantees or assumptions that we make 00:27:09.240 --> 00:27:12.830 align:start position:0% guarantees or assumptions that we make with<00:27:09.419> that<00:27:09.600> with<00:27:09.840> the<00:27:09.900> evm<00:27:10.320> but<00:27:11.039> yeah<00:27:11.760> I<00:27:12.720> don't 00:27:12.830 --> 00:27:12.840 align:start position:0% with that with the evm but yeah I don't 00:27:12.840 --> 00:27:15.830 align:start position:0% with that with the evm but yeah I don't know<00:27:12.960> I<00:27:13.140> quite<00:27:13.440> like<00:27:13.559> it<00:27:13.740> by<00:27:13.919> now<00:27:14.100> all<00:27:14.880> right<00:27:15.000> uh 00:27:15.830 --> 00:27:15.840 align:start position:0% know I quite like it by now all right uh 00:27:15.840 --> 00:27:17.930 align:start position:0% know I quite like it by now all right uh Jonathan<00:27:16.919> um 00:27:17.930 --> 00:27:17.940 align:start position:0% Jonathan um 00:27:17.940 --> 00:27:21.470 align:start position:0% Jonathan um how<00:27:18.360> do<00:27:18.480> you<00:27:18.480> feel<00:27:18.659> about<00:27:18.720> like<00:27:19.140> insurance 00:27:21.470 --> 00:27:21.480 align:start position:0% how do you feel about like insurance 00:27:21.480 --> 00:27:25.850 align:start position:0% how do you feel about like insurance against<00:27:22.200> smart<00:27:23.100> contract<00:27:23.520> vulnerabilities 00:27:25.850 --> 00:27:25.860 align:start position:0% against smart contract vulnerabilities 00:27:25.860 --> 00:27:29.810 align:start position:0% against smart contract vulnerabilities over<00:27:26.220> 800<00:27:26.700> that's<00:27:27.299> where<00:27:27.539> to<00:27:27.720> start 00:27:29.810 --> 00:27:29.820 align:start position:0% over 800 that's where to start 00:27:29.820 --> 00:27:32.990 align:start position:0% over 800 that's where to start I<00:27:30.299> guess<00:27:30.419> I'd<00:27:30.720> I<00:27:31.020> mean<00:27:31.260> if<00:27:31.440> I 00:27:32.990 --> 00:27:33.000 align:start position:0% I guess I'd I mean if I 00:27:33.000 --> 00:27:34.730 align:start position:0% I guess I'd I mean if I probably<00:27:33.360> say 00:27:34.730 --> 00:27:34.740 align:start position:0% probably say 00:27:34.740 --> 00:27:36.769 align:start position:0% probably say um 00:27:36.769 --> 00:27:36.779 align:start position:0% um 00:27:36.779 --> 00:27:39.710 align:start position:0% um I'm<00:27:37.020> going<00:27:37.200> to<00:27:37.260> say<00:27:37.380> underrated<00:27:37.919> because<00:27:38.460> I<00:27:39.419> I 00:27:39.710 --> 00:27:39.720 align:start position:0% I'm going to say underrated because I I 00:27:39.720 --> 00:27:43.010 align:start position:0% I'm going to say underrated because I I don't<00:27:40.320> really<00:27:40.620> think<00:27:40.919> it's 00:27:43.010 --> 00:27:43.020 align:start position:0% don't really think it's 00:27:43.020 --> 00:27:45.230 align:start position:0% don't really think it's widely<00:27:43.559> adopted<00:27:44.039> and<00:27:44.279> used<00:27:44.460> at<00:27:44.820> this<00:27:45.000> point 00:27:45.230 --> 00:27:45.240 align:start position:0% widely adopted and used at this point 00:27:45.240 --> 00:27:48.950 align:start position:0% widely adopted and used at this point and<00:27:45.600> I<00:27:45.779> think<00:27:45.900> it's<00:27:46.140> a<00:27:46.799> it's<00:27:47.279> a<00:27:47.700> uh 00:27:48.950 --> 00:27:48.960 align:start position:0% and I think it's a it's a uh 00:27:48.960 --> 00:27:51.850 align:start position:0% and I think it's a it's a uh it's<00:27:49.620> based<00:27:49.980> on<00:27:50.039> where<00:27:50.279> we're<00:27:50.400> at 00:27:51.850 --> 00:27:51.860 align:start position:0% it's based on where we're at 00:27:51.860 --> 00:27:55.909 align:start position:0% it's based on where we're at as<00:27:52.860> as<00:27:52.980> a<00:27:53.640> you<00:27:54.059> know<00:27:54.179> our<00:27:54.900> risk<00:27:55.200> tolerance<00:27:55.620> is 00:27:55.909 --> 00:27:55.919 align:start position:0% as as a you know our risk tolerance is 00:27:55.919 --> 00:27:57.289 align:start position:0% as as a you know our risk tolerance is really<00:27:56.159> high 00:27:57.289 --> 00:27:57.299 align:start position:0% really high 00:27:57.299 --> 00:28:00.649 align:start position:0% really high and<00:27:57.960> our<00:27:58.200> you<00:27:58.860> know<00:27:58.980> our<00:27:59.820> skin<00:28:00.059> in<00:28:00.240> the<00:28:00.360> game<00:28:00.480> is 00:28:00.649 --> 00:28:00.659 align:start position:0% and our you know our skin in the game is 00:28:00.659 --> 00:28:02.690 align:start position:0% and our you know our skin in the game is really<00:28:00.900> high<00:28:01.200> and 00:28:02.690 --> 00:28:02.700 align:start position:0% really high and 00:28:02.700 --> 00:28:06.529 align:start position:0% really high and um<00:28:02.820> and<00:28:03.720> and<00:28:04.020> our<00:28:04.559> risk<00:28:04.860> levels<00:28:05.340> are<00:28:05.880> not<00:28:06.299> well 00:28:06.529 --> 00:28:06.539 align:start position:0% um and and our risk levels are not well 00:28:06.539 --> 00:28:09.710 align:start position:0% um and and our risk levels are not well understood<00:28:07.340> so<00:28:08.340> it's<00:28:09.000> hard<00:28:09.179> to<00:28:09.299> get<00:28:09.480> insurance 00:28:09.710 --> 00:28:09.720 align:start position:0% understood so it's hard to get insurance 00:28:09.720 --> 00:28:13.549 align:start position:0% understood so it's hard to get insurance yeah<00:28:10.559> if<00:28:11.159> not<00:28:11.400> impossible<00:28:12.360> for<00:28:12.960> a<00:28:13.200> lot<00:28:13.320> of<00:28:13.440> us 00:28:13.549 --> 00:28:13.559 align:start position:0% yeah if not impossible for a lot of us 00:28:13.559 --> 00:28:16.130 align:start position:0% yeah if not impossible for a lot of us so<00:28:14.400> I<00:28:14.760> think<00:28:14.880> that'll<00:28:15.240> change<00:28:15.480> that's<00:28:15.900> gonna 00:28:16.130 --> 00:28:16.140 align:start position:0% so I think that'll change that's gonna 00:28:16.140 --> 00:28:18.769 align:start position:0% so I think that'll change that's gonna change<00:28:16.559> for<00:28:16.980> sure<00:28:17.159> and<00:28:18.000> so<00:28:18.179> that's<00:28:18.360> why<00:28:18.539> I<00:28:18.659> say 00:28:18.769 --> 00:28:18.779 align:start position:0% change for sure and so that's why I say 00:28:18.779 --> 00:28:20.630 align:start position:0% change for sure and so that's why I say underrated<00:28:19.260> I<00:28:19.500> think<00:28:19.559> it'll<00:28:19.799> change<00:28:20.100> and<00:28:20.460> then 00:28:20.630 --> 00:28:20.640 align:start position:0% underrated I think it'll change and then 00:28:20.640 --> 00:28:23.930 align:start position:0% underrated I think it'll change and then yeah<00:28:21.299> there'll<00:28:21.840> be<00:28:21.980> Hedges<00:28:22.980> and<00:28:23.400> insurance 00:28:23.930 --> 00:28:23.940 align:start position:0% yeah there'll be Hedges and insurance 00:28:23.940 --> 00:28:25.970 align:start position:0% yeah there'll be Hedges and insurance and<00:28:24.299> I<00:28:24.539> mean<00:28:24.840> it<00:28:24.960> is<00:28:25.080> happening<00:28:25.440> it's<00:28:25.679> not<00:28:25.860> like 00:28:25.970 --> 00:28:25.980 align:start position:0% and I mean it is happening it's not like 00:28:25.980 --> 00:28:28.430 align:start position:0% and I mean it is happening it's not like it<00:28:26.159> isn't<00:28:26.640> happening<00:28:27.059> but<00:28:27.360> I<00:28:27.720> think<00:28:27.779> it'll<00:28:28.080> it 00:28:28.430 --> 00:28:28.440 align:start position:0% it isn't happening but I think it'll it 00:28:28.440 --> 00:28:30.470 align:start position:0% it isn't happening but I think it'll it will<00:28:28.679> happen<00:28:28.919> more 00:28:30.470 --> 00:28:30.480 align:start position:0% will happen more 00:28:30.480 --> 00:28:34.490 align:start position:0% will happen more um<00:28:30.679> and<00:28:31.940> hopefully<00:28:33.020> you<00:28:34.020> know<00:28:34.080> some<00:28:34.260> of<00:28:34.440> the 00:28:34.490 --> 00:28:34.500 align:start position:0% um and hopefully you know some of the 00:28:34.500 --> 00:28:36.289 align:start position:0% um and hopefully you know some of the work<00:28:34.620> that<00:28:34.980> some<00:28:35.159> of<00:28:35.279> us<00:28:35.400> do<00:28:35.700> up<00:28:35.880> here<00:28:36.059> will 00:28:36.289 --> 00:28:36.299 align:start position:0% work that some of us do up here will 00:28:36.299 --> 00:28:37.130 align:start position:0% work that some of us do up here will help 00:28:37.130 --> 00:28:37.140 align:start position:0% help 00:28:37.140 --> 00:28:39.649 align:start position:0% help everybody<00:28:37.799> understand<00:28:38.279> the<00:28:38.700> risk<00:28:39.059> better<00:28:39.240> so 00:28:39.649 --> 00:28:39.659 align:start position:0% everybody understand the risk better so 00:28:39.659 --> 00:28:41.570 align:start position:0% everybody understand the risk better so that<00:28:39.900> insurance<00:28:40.200> will<00:28:40.620> be<00:28:40.799> obtainable<00:28:41.279> and 00:28:41.570 --> 00:28:41.580 align:start position:0% that insurance will be obtainable and 00:28:41.580 --> 00:28:43.010 align:start position:0% that insurance will be obtainable and things<00:28:41.760> like<00:28:41.940> that<00:28:42.059> for<00:28:42.299> those<00:28:42.480> who<00:28:42.720> want<00:28:42.840> it 00:28:43.010 --> 00:28:43.020 align:start position:0% things like that for those who want it 00:28:43.020 --> 00:28:45.350 align:start position:0% things like that for those who want it yeah<00:28:43.380> I<00:28:43.740> do<00:28:43.860> I<00:28:44.100> do<00:28:44.220> like<00:28:44.340> I'll<00:28:44.640> I<00:28:44.820> will<00:28:45.000> give<00:28:45.120> one 00:28:45.350 --> 00:28:45.360 align:start position:0% yeah I do I do like I'll I will give one 00:28:45.360 --> 00:28:47.269 align:start position:0% yeah I do I do like I'll I will give one I<00:28:45.840> haven't<00:28:46.140> given<00:28:46.440> many<00:28:46.559> opinions<00:28:46.980> I<00:28:47.159> don't 00:28:47.269 --> 00:28:47.279 align:start position:0% I haven't given many opinions I don't 00:28:47.279 --> 00:28:50.090 align:start position:0% I haven't given many opinions I don't think<00:28:47.400> but<00:28:47.640> I<00:28:48.600> think<00:28:48.779> that<00:28:49.200> having<00:28:49.679> somebody 00:28:50.090 --> 00:28:50.100 align:start position:0% think but I think that having somebody 00:28:50.100 --> 00:28:52.190 align:start position:0% think but I think that having somebody try<00:28:50.580> to<00:28:50.880> price<00:28:51.059> risk 00:28:52.190 --> 00:28:52.200 align:start position:0% try to price risk 00:28:52.200 --> 00:28:55.430 align:start position:0% try to price risk uh<00:28:53.100> who's<00:28:53.400> not<00:28:53.700> an<00:28:53.880> auditor<00:28:54.299> Auditors<00:28:55.200> don't 00:28:55.430 --> 00:28:55.440 align:start position:0% uh who's not an auditor Auditors don't 00:28:55.440 --> 00:28:57.830 align:start position:0% uh who's not an auditor Auditors don't want<00:28:55.620> to<00:28:55.740> price<00:28:55.919> risk<00:28:56.520> they<00:28:57.179> like<00:28:57.360> look<00:28:57.600> for 00:28:57.830 --> 00:28:57.840 align:start position:0% want to price risk they like look for 00:28:57.840 --> 00:28:59.930 align:start position:0% want to price risk they like look for bugs<00:28:58.260> right<00:28:58.500> but<00:28:58.860> and<00:28:59.279> it's<00:28:59.460> a<00:28:59.700> totally 00:28:59.930 --> 00:28:59.940 align:start position:0% bugs right but and it's a totally 00:28:59.940 --> 00:29:02.390 align:start position:0% bugs right but and it's a totally different<00:29:00.120> thing<00:29:00.480> to<00:29:00.840> be<00:29:01.020> in<00:29:01.260> uh<00:29:01.799> what<00:29:02.039> is<00:29:02.220> an 00:29:02.390 --> 00:29:02.400 align:start position:0% different thing to be in uh what is an 00:29:02.400 --> 00:29:03.529 align:start position:0% different thing to be in uh what is an actuary 00:29:03.529 --> 00:29:03.539 align:start position:0% actuary 00:29:03.539 --> 00:29:06.710 align:start position:0% actuary but<00:29:04.080> there<00:29:04.440> should<00:29:04.679> be<00:29:04.860> actuaries<00:29:05.760> and<00:29:06.539> maybe 00:29:06.710 --> 00:29:06.720 align:start position:0% but there should be actuaries and maybe 00:29:06.720 --> 00:29:08.570 align:start position:0% but there should be actuaries and maybe they<00:29:06.960> are<00:29:07.140> the<00:29:07.320> ones<00:29:07.740> maybe<00:29:07.919> they<00:29:08.159> audit<00:29:08.460> the 00:29:08.570 --> 00:29:08.580 align:start position:0% they are the ones maybe they audit the 00:29:08.580 --> 00:29:10.250 align:start position:0% they are the ones maybe they audit the Auditors<00:29:08.940> they<00:29:09.360> have<00:29:09.480> an<00:29:09.659> incentive<00:29:10.020> to<00:29:10.140> use 00:29:10.250 --> 00:29:10.260 align:start position:0% Auditors they have an incentive to use 00:29:10.260 --> 00:29:11.510 align:start position:0% Auditors they have an incentive to use and<00:29:10.440> we're<00:29:10.559> working<00:29:10.740> what<00:29:10.980> I'm<00:29:11.159> what<00:29:11.400> I'm 00:29:11.510 --> 00:29:11.520 align:start position:0% and we're working what I'm what I'm 00:29:11.520 --> 00:29:13.430 align:start position:0% and we're working what I'm what I'm hoping<00:29:11.760> and<00:29:12.000> and<00:29:12.179> we're<00:29:12.419> doing<00:29:12.539> some<00:29:12.900> work 00:29:13.430 --> 00:29:13.440 align:start position:0% hoping and and we're doing some work 00:29:13.440 --> 00:29:15.890 align:start position:0% hoping and and we're doing some work with<00:29:13.740> with<00:29:14.400> the<00:29:14.580> actuarials<00:29:15.179> and<00:29:15.360> and<00:29:15.480> with 00:29:15.890 --> 00:29:15.900 align:start position:0% with with the actuarials and and with 00:29:15.900 --> 00:29:17.990 align:start position:0% with with the actuarials and and with the<00:29:16.080> insurance<00:29:16.200> companies<00:29:16.740> to<00:29:17.520> make<00:29:17.760> sure 00:29:17.990 --> 00:29:18.000 align:start position:0% the insurance companies to make sure 00:29:18.000 --> 00:29:20.330 align:start position:0% the insurance companies to make sure that<00:29:18.419> insurance<00:29:19.140> in<00:29:19.500> this<00:29:19.679> industry<00:29:19.980> does<00:29:20.220> not 00:29:20.330 --> 00:29:20.340 align:start position:0% that insurance in this industry does not 00:29:20.340 --> 00:29:23.269 align:start position:0% that insurance in this industry does not go<00:29:20.520> the<00:29:20.760> route<00:29:20.940> of<00:29:21.360> insurance<00:29:21.720> in<00:29:22.440> quote<00:29:22.919> cyber 00:29:23.269 --> 00:29:23.279 align:start position:0% go the route of insurance in quote cyber 00:29:23.279 --> 00:29:26.389 align:start position:0% go the route of insurance in quote cyber security<00:29:23.659> where<00:29:24.659> I<00:29:25.140> mean<00:29:25.260> I<00:29:25.679> thought<00:29:26.100> it<00:29:26.279> was 00:29:26.389 --> 00:29:26.399 align:start position:0% security where I mean I thought it was 00:29:26.399 --> 00:29:27.769 align:start position:0% security where I mean I thought it was quite<00:29:26.520> hilarious<00:29:26.940> about<00:29:27.120> a<00:29:27.360> week<00:29:27.419> ago<00:29:27.659> when 00:29:27.769 --> 00:29:27.779 align:start position:0% quite hilarious about a week ago when 00:29:27.779 --> 00:29:29.930 align:start position:0% quite hilarious about a week ago when Lloyds<00:29:28.200> of<00:29:28.260> London<00:29:28.620> got<00:29:28.860> hit<00:29:29.100> with<00:29:29.580> with<00:29:29.640> a 00:29:29.930 --> 00:29:29.940 align:start position:0% Lloyds of London got hit with with a 00:29:29.940 --> 00:29:32.330 align:start position:0% Lloyds of London got hit with with a cyber<00:29:30.179> and<00:29:30.299> like<00:29:30.899> they<00:29:31.320> can't<00:29:31.500> set<00:29:31.740> Actuarial 00:29:32.330 --> 00:29:32.340 align:start position:0% cyber and like they can't set Actuarial 00:29:32.340 --> 00:29:33.590 align:start position:0% cyber and like they can't set Actuarial terms<00:29:32.580> if<00:29:32.700> they<00:29:32.820> can't<00:29:32.940> even<00:29:33.120> secure<00:29:33.419> their 00:29:33.590 --> 00:29:33.600 align:start position:0% terms if they can't even secure their 00:29:33.600 --> 00:29:35.269 align:start position:0% terms if they can't even secure their own<00:29:33.779> systems<00:29:34.200> yeah<00:29:34.380> what<00:29:34.799> we're<00:29:35.100> really 00:29:35.269 --> 00:29:35.279 align:start position:0% own systems yeah what we're really 00:29:35.279 --> 00:29:38.029 align:start position:0% own systems yeah what we're really hoping<00:29:35.580> for<00:29:35.700> is<00:29:36.059> that<00:29:36.539> that 00:29:38.029 --> 00:29:38.039 align:start position:0% hoping for is that that 00:29:38.039 --> 00:29:39.710 align:start position:0% hoping for is that that people<00:29:38.460> doing<00:29:38.700> Security<00:29:38.940> reviews<00:29:39.240> can<00:29:39.539> set 00:29:39.710 --> 00:29:39.720 align:start position:0% people doing Security reviews can set 00:29:39.720 --> 00:29:41.330 align:start position:0% people doing Security reviews can set those<00:29:39.899> standards<00:29:40.260> so<00:29:40.440> that<00:29:40.620> that<00:29:41.039> the 00:29:41.330 --> 00:29:41.340 align:start position:0% those standards so that that the 00:29:41.340 --> 00:29:43.130 align:start position:0% those standards so that that the insurance<00:29:41.520> companies<00:29:42.000> are<00:29:42.179> actually<00:29:42.360> as 00:29:43.130 --> 00:29:43.140 align:start position:0% insurance companies are actually as 00:29:43.140 --> 00:29:44.389 align:start position:0% insurance companies are actually as passionate<00:29:43.500> about<00:29:43.679> what<00:29:43.980> they<00:29:44.100> do<00:29:44.279> that 00:29:44.389 --> 00:29:44.399 align:start position:0% passionate about what they do that 00:29:44.399 --> 00:29:45.350 align:start position:0% passionate about what they do that they're<00:29:44.580> getting<00:29:44.700> into<00:29:44.820> it<00:29:45.000> not<00:29:45.120> just<00:29:45.240> because 00:29:45.350 --> 00:29:45.360 align:start position:0% they're getting into it not just because 00:29:45.360 --> 00:29:46.789 align:start position:0% they're getting into it not just because oh<00:29:45.659> look<00:29:45.840> at<00:29:45.960> that<00:29:46.080> it's<00:29:46.200> a<00:29:46.320> new<00:29:46.440> adjacent 00:29:46.789 --> 00:29:46.799 align:start position:0% oh look at that it's a new adjacent 00:29:46.799 --> 00:29:48.350 align:start position:0% oh look at that it's a new adjacent Market<00:29:46.980> that<00:29:47.220> we<00:29:47.340> can<00:29:47.460> get<00:29:47.580> into<00:29:47.700> and<00:29:48.120> much 00:29:48.350 --> 00:29:48.360 align:start position:0% Market that we can get into and much 00:29:48.360 --> 00:29:49.789 align:start position:0% Market that we can get into and much more<00:29:48.480> around<00:29:48.659> wow<00:29:49.020> this<00:29:49.320> is<00:29:49.559> really 00:29:49.789 --> 00:29:49.799 align:start position:0% more around wow this is really 00:29:49.799 --> 00:29:51.649 align:start position:0% more around wow this is really Innovative<00:29:50.220> stuff<00:29:50.520> we<00:29:51.059> should<00:29:51.179> get<00:29:51.360> in<00:29:51.539> there 00:29:51.649 --> 00:29:51.659 align:start position:0% Innovative stuff we should get in there 00:29:51.659 --> 00:29:53.870 align:start position:0% Innovative stuff we should get in there to<00:29:51.899> make<00:29:52.080> it<00:29:52.260> safer<00:29:52.679> and<00:29:53.279> we're<00:29:53.520> working<00:29:53.700> with 00:29:53.870 --> 00:29:53.880 align:start position:0% to make it safer and we're working with 00:29:53.880 --> 00:29:55.310 align:start position:0% to make it safer and we're working with several<00:29:54.179> people<00:29:54.299> like<00:29:54.539> that<00:29:54.659> and<00:29:54.779> I'm<00:29:54.960> very 00:29:55.310 --> 00:29:55.320 align:start position:0% several people like that and I'm very 00:29:55.320 --> 00:29:56.810 align:start position:0% several people like that and I'm very hopeful<00:29:55.559> so<00:29:55.679> I'm<00:29:55.860> with<00:29:56.100> you<00:29:56.220> about<00:29:56.399> underrated 00:29:56.810 --> 00:29:56.820 align:start position:0% hopeful so I'm with you about underrated 00:29:56.820 --> 00:29:59.090 align:start position:0% hopeful so I'm with you about underrated interesting<00:29:57.539> okay<00:29:57.840> uh<00:29:58.500> is<00:29:58.620> the<00:29:58.860> audience 00:29:59.090 --> 00:29:59.100 align:start position:0% interesting okay uh is the audience 00:29:59.100 --> 00:30:01.250 align:start position:0% interesting okay uh is the audience ready<00:29:59.279> does<00:29:59.640> anybody<00:29:59.940> have<00:30:00.179> a<00:30:00.419> mic<00:30:00.659> and<00:30:01.080> a 00:30:01.250 --> 00:30:01.260 align:start position:0% ready does anybody have a mic and a 00:30:01.260 --> 00:30:03.350 align:start position:0% ready does anybody have a mic and a question<00:30:01.440> yeah<00:30:01.860> I<00:30:01.980> do 00:30:03.350 --> 00:30:03.360 align:start position:0% question yeah I do 00:30:03.360 --> 00:30:05.090 align:start position:0% question yeah I do all<00:30:03.840> right<00:30:03.960> let's<00:30:04.140> just 00:30:05.090 --> 00:30:05.100 align:start position:0% all right let's just 00:30:05.100 --> 00:30:07.490 align:start position:0% all right let's just uh<00:30:05.760> Mike<00:30:05.940> if<00:30:06.120> you<00:30:06.240> I<00:30:06.419> can<00:30:06.600> hear<00:30:06.659> you<00:30:06.840> so<00:30:07.080> I'll 00:30:07.490 --> 00:30:07.500 align:start position:0% uh Mike if you I can hear you so I'll 00:30:07.500 --> 00:30:09.889 align:start position:0% uh Mike if you I can hear you so I'll repeat<00:30:07.799> it 00:30:09.889 --> 00:30:09.899 align:start position:0% repeat it 00:30:09.899 --> 00:30:12.169 align:start position:0% repeat it oh<00:30:10.500> somebody's<00:30:10.919> somebody's<00:30:11.399> set<00:30:11.580> up<00:30:11.700> okay<00:30:11.880> go 00:30:12.169 --> 00:30:12.179 align:start position:0% oh somebody's somebody's set up okay go 00:30:12.179 --> 00:30:15.769 align:start position:0% oh somebody's somebody's set up okay go ahead<00:30:12.299> please<00:30:12.539> hey<00:30:13.140> uh<00:30:14.100> so<00:30:14.460> I<00:30:15.240> was<00:30:15.360> wondering 00:30:15.769 --> 00:30:15.779 align:start position:0% ahead please hey uh so I was wondering 00:30:15.779 --> 00:30:17.990 align:start position:0% ahead please hey uh so I was wondering because<00:30:16.200> of<00:30:16.500> all<00:30:16.740> the<00:30:16.980> monitoring<00:30:17.460> tools<00:30:17.820> that 00:30:17.990 --> 00:30:18.000 align:start position:0% because of all the monitoring tools that 00:30:18.000 --> 00:30:19.730 align:start position:0% because of all the monitoring tools that are<00:30:18.179> coming<00:30:18.299> out<00:30:18.539> like<00:30:18.720> photo<00:30:18.960> for<00:30:19.440> example 00:30:19.730 --> 00:30:19.740 align:start position:0% are coming out like photo for example 00:30:19.740 --> 00:30:23.149 align:start position:0% are coming out like photo for example and<00:30:20.399> there<00:30:20.640> is<00:30:20.820> also<00:30:21.179> private<00:30:21.720> mempools<00:30:22.380> is<00:30:22.980> it 00:30:23.149 --> 00:30:23.159 align:start position:0% and there is also private mempools is it 00:30:23.159 --> 00:30:24.830 align:start position:0% and there is also private mempools is it really<00:30:23.460> overrated 00:30:24.830 --> 00:30:24.840 align:start position:0% really overrated 00:30:24.840 --> 00:30:27.230 align:start position:0% really overrated oh<00:30:25.500> so<00:30:25.799> you<00:30:26.159> keep<00:30:26.279> I<00:30:26.520> like<00:30:26.640> you're<00:30:26.880> using<00:30:27.120> the 00:30:27.230 --> 00:30:27.240 align:start position:0% oh so you keep I like you're using the 00:30:27.240 --> 00:30:28.789 align:start position:0% oh so you keep I like you're using the format 00:30:28.789 --> 00:30:28.799 align:start position:0% format 00:30:28.799 --> 00:30:31.070 align:start position:0% format uh 00:30:31.070 --> 00:30:31.080 align:start position:0% uh 00:30:31.080 --> 00:30:32.990 align:start position:0% uh I<00:30:31.679> don't<00:30:31.740> know<00:30:31.860> who<00:30:31.980> should<00:30:32.159> I<00:30:32.340> give<00:30:32.700> that<00:30:32.820> to 00:30:32.990 --> 00:30:33.000 align:start position:0% I don't know who should I give that to 00:30:33.000 --> 00:30:36.049 align:start position:0% I don't know who should I give that to you<00:30:33.120> later<00:30:33.240> what's<00:30:34.080> the<00:30:34.260> question<00:30:34.380> uh<00:30:34.919> is<00:30:35.100> is 00:30:36.049 --> 00:30:36.059 align:start position:0% you later what's the question uh is is 00:30:36.059 --> 00:30:39.049 align:start position:0% you later what's the question uh is is is<00:30:36.899> about<00:30:37.140> monitoring 00:30:39.049 --> 00:30:39.059 align:start position:0% is about monitoring 00:30:39.059 --> 00:30:41.990 align:start position:0% is about monitoring um<00:30:39.120> is<00:30:39.659> monitoring<00:30:40.200> like<00:30:41.100> mempool<00:30:41.520> monitoring 00:30:41.990 --> 00:30:42.000 align:start position:0% um is monitoring like mempool monitoring 00:30:42.000 --> 00:30:44.409 align:start position:0% um is monitoring like mempool monitoring overrated<00:30:42.419> or<00:30:42.720> underrated 00:30:44.409 --> 00:30:44.419 align:start position:0% overrated or underrated 00:30:44.419 --> 00:30:46.730 align:start position:0% overrated or underrated specifically<00:30:45.419> mempool<00:30:45.960> monitoring<00:30:46.440> I<00:30:46.620> think 00:30:46.730 --> 00:30:46.740 align:start position:0% specifically mempool monitoring I think 00:30:46.740 --> 00:30:48.889 align:start position:0% specifically mempool monitoring I think or<00:30:46.919> just<00:30:47.220> is<00:30:47.460> that<00:30:47.640> is<00:30:47.880> your<00:30:48.779> question 00:30:48.889 --> 00:30:48.899 align:start position:0% or just is that is your question 00:30:48.899 --> 00:30:50.990 align:start position:0% or just is that is your question monitoring<00:30:49.500> in<00:30:49.679> general<00:30:49.860> is<00:30:50.399> monitoring<00:30:50.880> over 00:30:50.990 --> 00:30:51.000 align:start position:0% monitoring in general is monitoring over 00:30:51.000 --> 00:30:54.289 align:start position:0% monitoring in general is monitoring over yeah<00:30:51.480> yeah<00:30:51.779> so<00:30:52.260> uh<00:30:52.799> like<00:30:53.340> for<00:30:53.640> for<00:30:53.820> example 00:30:54.289 --> 00:30:54.299 align:start position:0% yeah yeah so uh like for for example 00:30:54.299 --> 00:30:57.049 align:start position:0% yeah yeah so uh like for for example like<00:30:54.659> uh<00:30:55.620> there<00:30:56.220> are<00:30:56.340> products<00:30:56.760> out<00:30:56.880> there 00:30:57.049 --> 00:30:57.059 align:start position:0% like uh there are products out there 00:30:57.059 --> 00:30:59.090 align:start position:0% like uh there are products out there that<00:30:57.360> claim<00:30:57.840> that<00:30:58.140> they<00:30:58.500> could<00:30:58.679> like<00:30:58.860> maybe 00:30:59.090 --> 00:30:59.100 align:start position:0% that claim that they could like maybe 00:30:59.100 --> 00:31:01.789 align:start position:0% that claim that they could like maybe detect<00:30:59.640> hacks<00:31:00.179> and<00:31:00.299> all<00:31:00.480> that<00:31:00.659> uh<00:31:01.440> or<00:31:01.559> maybe 00:31:01.789 --> 00:31:01.799 align:start position:0% detect hacks and all that uh or maybe 00:31:01.799 --> 00:31:03.710 align:start position:0% detect hacks and all that uh or maybe secure<00:31:02.340> your<00:31:02.580> smart<00:31:02.820> contracts<00:31:03.240> that<00:31:03.419> kind<00:31:03.600> of 00:31:03.710 --> 00:31:03.720 align:start position:0% secure your smart contracts that kind of 00:31:03.720 --> 00:31:06.110 align:start position:0% secure your smart contracts that kind of a<00:31:03.840> thing<00:31:03.960> but<00:31:04.559> a<00:31:04.980> hacker<00:31:05.279> could<00:31:05.460> use<00:31:05.700> like<00:31:05.940> a 00:31:06.110 --> 00:31:06.120 align:start position:0% a thing but a hacker could use like a 00:31:06.120 --> 00:31:07.669 align:start position:0% a thing but a hacker could use like a private<00:31:06.360> mempool<00:31:06.779> to<00:31:07.020> like<00:31:07.140> really<00:31:07.380> send 00:31:07.669 --> 00:31:07.679 align:start position:0% private mempool to like really send 00:31:07.679 --> 00:31:10.190 align:start position:0% private mempool to like really send these<00:31:07.980> transactions<00:31:08.460> across<00:31:08.940> and<00:31:09.539> to<00:31:09.720> even<00:31:09.840> to 00:31:10.190 --> 00:31:10.200 align:start position:0% these transactions across and to even to 00:31:10.200 --> 00:31:12.950 align:start position:0% these transactions across and to even to react<00:31:10.500> right<00:31:10.860> you<00:31:11.520> your<00:31:12.179> transaction<00:31:12.600> maybe 00:31:12.950 --> 00:31:12.960 align:start position:0% react right you your transaction maybe 00:31:12.960 --> 00:31:15.590 align:start position:0% react right you your transaction maybe I'm<00:31:13.740> gonna<00:31:13.919> say 00:31:15.590 --> 00:31:15.600 align:start position:0% I'm gonna say 00:31:15.600 --> 00:31:17.450 align:start position:0% I'm gonna say let's<00:31:16.140> talk<00:31:16.380> after 00:31:17.450 --> 00:31:17.460 align:start position:0% let's talk after 00:31:17.460 --> 00:31:20.990 align:start position:0% let's talk after not<00:31:17.940> sure<00:31:18.059> but<00:31:18.840> what<00:31:19.140> I'll<00:31:19.260> say<00:31:19.440> is<00:31:19.620> that<00:31:20.460> um<00:31:20.460> I 00:31:20.990 --> 00:31:21.000 align:start position:0% not sure but what I'll say is that um I 00:31:21.000 --> 00:31:22.370 align:start position:0% not sure but what I'll say is that um I don't<00:31:21.059> think<00:31:21.179> there's<00:31:21.419> anybody<00:31:21.779> claiming 00:31:22.370 --> 00:31:22.380 align:start position:0% don't think there's anybody claiming 00:31:22.380 --> 00:31:24.830 align:start position:0% don't think there's anybody claiming that<00:31:22.919> we've<00:31:23.460> solved<00:31:23.880> monitoring<00:31:24.419> in<00:31:24.720> the 00:31:24.830 --> 00:31:24.840 align:start position:0% that we've solved monitoring in the 00:31:24.840 --> 00:31:27.049 align:start position:0% that we've solved monitoring in the ecosystem<00:31:25.260> nobody's<00:31:26.039> claiming<00:31:26.399> that<00:31:26.520> or<00:31:26.820> that 00:31:27.049 --> 00:31:27.059 align:start position:0% ecosystem nobody's claiming that or that 00:31:27.059 --> 00:31:27.950 align:start position:0% ecosystem nobody's claiming that or that we<00:31:27.240> can 00:31:27.950 --> 00:31:27.960 align:start position:0% we can 00:31:27.960 --> 00:31:31.549 align:start position:0% we can stop<00:31:28.559> threats<00:31:29.100> but<00:31:29.700> I<00:31:30.240> I<00:31:30.419> what<00:31:30.720> I<00:31:30.840> will<00:31:30.960> say<00:31:31.140> is 00:31:31.549 --> 00:31:31.559 align:start position:0% stop threats but I I what I will say is 00:31:31.559 --> 00:31:32.389 align:start position:0% stop threats but I I what I will say is that 00:31:32.389 --> 00:31:32.399 align:start position:0% that 00:31:32.399 --> 00:31:34.850 align:start position:0% that I<00:31:32.820> think<00:31:32.940> we're<00:31:33.240> all<00:31:33.539> I<00:31:34.140> think<00:31:34.260> there's<00:31:34.500> a<00:31:34.740> lot 00:31:34.850 --> 00:31:34.860 align:start position:0% I think we're all I think there's a lot 00:31:34.860 --> 00:31:36.049 align:start position:0% I think we're all I think there's a lot of<00:31:34.980> agreement 00:31:36.049 --> 00:31:36.059 align:start position:0% of agreement 00:31:36.059 --> 00:31:37.610 align:start position:0% of agreement that 00:31:37.610 --> 00:31:37.620 align:start position:0% that 00:31:37.620 --> 00:31:41.330 align:start position:0% that security<00:31:38.299> is<00:31:39.299> not<00:31:39.659> just<00:31:40.020> a<00:31:40.559> time<00:31:40.679> box<00:31:40.919> Security 00:31:41.330 --> 00:31:41.340 align:start position:0% security is not just a time box Security 00:31:41.340 --> 00:31:42.769 align:start position:0% security is not just a time box Security review 00:31:42.769 --> 00:31:42.779 align:start position:0% review 00:31:42.779 --> 00:31:46.130 align:start position:0% review if<00:31:43.260> you<00:31:43.380> if<00:31:43.500> that's<00:31:43.799> all<00:31:43.980> you<00:31:44.159> do<00:31:44.340> good<00:31:44.760> luck 00:31:46.130 --> 00:31:46.140 align:start position:0% if you if that's all you do good luck 00:31:46.140 --> 00:31:49.250 align:start position:0% if you if that's all you do good luck and<00:31:46.980> and<00:31:47.399> there<00:31:48.360> are<00:31:48.539> things<00:31:48.659> you<00:31:48.899> should<00:31:49.080> be 00:31:49.250 --> 00:31:49.260 align:start position:0% and and there are things you should be 00:31:49.260 --> 00:31:51.230 align:start position:0% and and there are things you should be doing<00:31:49.500> Upstream 00:31:51.230 --> 00:31:51.240 align:start position:0% doing Upstream 00:31:51.240 --> 00:31:53.450 align:start position:0% doing Upstream and<00:31:51.779> considering<00:31:52.260> like<00:31:52.559> formal<00:31:52.919> verification 00:31:53.450 --> 00:31:53.460 align:start position:0% and considering like formal verification 00:31:53.460 --> 00:31:57.830 align:start position:0% and considering like formal verification and<00:31:54.120> fuzzing<00:31:54.600> and<00:31:55.559> various<00:31:55.980> techniques<00:31:56.840> time 00:31:57.830 --> 00:31:57.840 align:start position:0% and fuzzing and various techniques time 00:31:57.840 --> 00:31:59.690 align:start position:0% and fuzzing and various techniques time box<00:31:58.080> Security<00:31:58.380> review<00:31:58.799> part<00:31:59.100> is<00:31:59.279> part<00:31:59.520> of<00:31:59.640> it 00:31:59.690 --> 00:31:59.700 align:start position:0% box Security review part is part of it 00:31:59.700 --> 00:32:01.370 align:start position:0% box Security review part is part of it and<00:31:59.940> there's<00:32:00.120> things<00:32:00.360> you<00:32:00.539> should<00:32:00.720> do<00:32:00.899> so 00:32:01.370 --> 00:32:01.380 align:start position:0% and there's things you should do so 00:32:01.380 --> 00:32:02.930 align:start position:0% and there's things you should do so pre-release 00:32:02.930 --> 00:32:02.940 align:start position:0% pre-release 00:32:02.940 --> 00:32:04.970 align:start position:0% pre-release pre-deployment<00:32:03.840> post<00:32:04.140> deployment<00:32:04.679> there's 00:32:04.970 --> 00:32:04.980 align:start position:0% pre-deployment post deployment there's 00:32:04.980 --> 00:32:06.590 align:start position:0% pre-deployment post deployment there's things<00:32:05.279> you<00:32:05.399> should<00:32:05.580> do<00:32:05.760> in<00:32:06.000> monitoring<00:32:06.480> is 00:32:06.590 --> 00:32:06.600 align:start position:0% things you should do in monitoring is 00:32:06.600 --> 00:32:10.190 align:start position:0% things you should do in monitoring is part<00:32:06.779> of<00:32:06.960> it<00:32:07.080> and<00:32:07.620> so<00:32:08.520> there's<00:32:08.880> value 00:32:10.190 --> 00:32:10.200 align:start position:0% part of it and so there's value 00:32:10.200 --> 00:32:12.289 align:start position:0% part of it and so there's value to<00:32:10.620> an<00:32:10.799> end-to-end<00:32:11.340> security<00:32:11.520> and<00:32:11.940> I<00:32:12.120> think 00:32:12.289 --> 00:32:12.299 align:start position:0% to an end-to-end security and I think 00:32:12.299 --> 00:32:13.789 align:start position:0% to an end-to-end security and I think that's<00:32:12.480> where<00:32:12.720> we're<00:32:12.840> at<00:32:13.020> okay<00:32:13.260> we're 00:32:13.789 --> 00:32:13.799 align:start position:0% that's where we're at okay we're 00:32:13.799 --> 00:32:15.409 align:start position:0% that's where we're at okay we're starting<00:32:14.100> to<00:32:14.279> appreciate<00:32:14.760> that<00:32:14.880> and<00:32:15.120> I<00:32:15.299> want 00:32:15.409 --> 00:32:15.419 align:start position:0% starting to appreciate that and I want 00:32:15.419 --> 00:32:16.850 align:start position:0% starting to appreciate that and I want to<00:32:15.480> seek<00:32:15.720> in<00:32:15.840> quickly<00:32:16.080> while<00:32:16.260> we<00:32:16.440> move<00:32:16.559> the<00:32:16.679> mic 00:32:16.850 --> 00:32:16.860 align:start position:0% to seek in quickly while we move the mic 00:32:16.860 --> 00:32:19.190 align:start position:0% to seek in quickly while we move the mic over<00:32:17.039> uh 00:32:19.190 --> 00:32:19.200 align:start position:0% over uh 00:32:19.200 --> 00:32:21.590 align:start position:0% over uh go<00:32:19.860> ahead<00:32:20.100> Alex<00:32:20.340> you're<00:32:20.700> up<00:32:20.880> next<00:32:21.059> Mike<00:32:21.360> don't 00:32:21.590 --> 00:32:21.600 align:start position:0% go ahead Alex you're up next Mike don't 00:32:21.600 --> 00:32:23.990 align:start position:0% go ahead Alex you're up next Mike don't worry<00:32:21.720> hey<00:32:22.380> uh<00:32:22.799> do<00:32:23.039> your<00:32:23.220> clients<00:32:23.580> request 00:32:23.990 --> 00:32:24.000 align:start position:0% worry hey uh do your clients request 00:32:24.000 --> 00:32:25.970 align:start position:0% worry hey uh do your clients request public<00:32:24.480> reports<00:32:25.020> and<00:32:25.380> when<00:32:25.620> you<00:32:25.799> write 00:32:25.970 --> 00:32:25.980 align:start position:0% public reports and when you write 00:32:25.980 --> 00:32:29.389 align:start position:0% public reports and when you write reports<00:32:26.399> who<00:32:26.640> do<00:32:26.820> you<00:32:26.940> write<00:32:27.059> the<00:32:27.240> report<00:32:27.419> for 00:32:29.389 --> 00:32:29.399 align:start position:0% reports who do you write the report for 00:32:29.399 --> 00:32:31.730 align:start position:0% reports who do you write the report for um<00:32:29.520> yes<00:32:30.059> so<00:32:30.539> I<00:32:30.720> was<00:32:30.840> I<00:32:31.020> was<00:32:31.140> telling<00:32:31.320> one<00:32:31.440> of<00:32:31.620> my 00:32:31.730 --> 00:32:31.740 align:start position:0% um yes so I was I was telling one of my 00:32:31.740 --> 00:32:33.950 align:start position:0% um yes so I was I was telling one of my team<00:32:32.159> members<00:32:32.460> the<00:32:32.640> other<00:32:32.760> day<00:32:32.940> that<00:32:33.299> uh<00:32:33.720> what 00:32:33.950 --> 00:32:33.960 align:start position:0% team members the other day that uh what 00:32:33.960 --> 00:32:37.430 align:start position:0% team members the other day that uh what we<00:32:34.260> sell<00:32:34.559> effectively<00:32:35.340> is<00:32:35.760> PDFs<00:32:36.539> obviously 00:32:37.430 --> 00:32:37.440 align:start position:0% we sell effectively is PDFs obviously 00:32:37.440 --> 00:32:40.430 align:start position:0% we sell effectively is PDFs obviously joking<00:32:37.799> a<00:32:37.919> bit<00:32:37.980> but<00:32:38.220> yeah<00:32:38.640> uh 00:32:40.430 --> 00:32:40.440 align:start position:0% joking a bit but yeah uh 00:32:40.440 --> 00:32:42.649 align:start position:0% joking a bit but yeah uh um<00:32:40.500> yes<00:32:40.860> it's<00:32:41.100> critical<00:32:41.580> the<00:32:41.820> output<00:32:42.179> of<00:32:42.480> the 00:32:42.649 --> 00:32:42.659 align:start position:0% um yes it's critical the output of the 00:32:42.659 --> 00:32:45.049 align:start position:0% um yes it's critical the output of the work<00:32:42.779> that<00:32:43.080> we<00:32:43.200> do<00:32:43.320> is<00:32:43.860> a<00:32:44.279> security<00:32:44.520> assessment 00:32:45.049 --> 00:32:45.059 align:start position:0% work that we do is a security assessment 00:32:45.059 --> 00:32:47.330 align:start position:0% work that we do is a security assessment report<00:32:45.440> which<00:32:46.440> you<00:32:46.620> know<00:32:46.740> contains<00:32:47.159> your 00:32:47.330 --> 00:32:47.340 align:start position:0% report which you know contains your 00:32:47.340 --> 00:32:49.669 align:start position:0% report which you know contains your standard<00:32:47.760> executive<00:32:48.240> summary<00:32:48.679> detailed 00:32:49.669 --> 00:32:49.679 align:start position:0% standard executive summary detailed 00:32:49.679 --> 00:32:50.930 align:start position:0% standard executive summary detailed description<00:32:49.980> of<00:32:50.220> all<00:32:50.340> the<00:32:50.520> vulnerabilities 00:32:50.930 --> 00:32:50.940 align:start position:0% description of all the vulnerabilities 00:32:50.940 --> 00:32:53.950 align:start position:0% description of all the vulnerabilities identified<00:32:51.539> and<00:32:52.440> recommendations 00:32:53.950 --> 00:32:53.960 align:start position:0% identified and recommendations 00:32:53.960 --> 00:32:56.389 align:start position:0% identified and recommendations who<00:32:54.960> do<00:32:55.080> we<00:32:55.260> write<00:32:55.440> that<00:32:55.679> for<00:32:55.860> that's<00:32:56.159> an 00:32:56.389 --> 00:32:56.399 align:start position:0% who do we write that for that's an 00:32:56.399 --> 00:32:59.029 align:start position:0% who do we write that for that's an excellent<00:32:56.760> question<00:32:57.120> we<00:32:57.779> write<00:32:58.020> that<00:32:58.320> for<00:32:58.740> our 00:32:59.029 --> 00:32:59.039 align:start position:0% excellent question we write that for our 00:32:59.039 --> 00:33:02.450 align:start position:0% excellent question we write that for our clients<00:32:59.520> now<00:33:00.179> the<00:33:00.480> problem<00:33:00.720> that<00:33:01.440> we<00:33:02.039> may<00:33:02.159> see 00:33:02.450 --> 00:33:02.460 align:start position:0% clients now the problem that we may see 00:33:02.460 --> 00:33:05.630 align:start position:0% clients now the problem that we may see quite<00:33:02.820> often<00:33:03.120> in<00:33:03.480> our<00:33:03.779> space<00:33:04.080> is<00:33:04.559> uh<00:33:04.980> you<00:33:05.580> know 00:33:05.630 --> 00:33:05.640 align:start position:0% quite often in our space is uh you know 00:33:05.640 --> 00:33:06.889 align:start position:0% quite often in our space is uh you know readers 00:33:06.889 --> 00:33:06.899 align:start position:0% readers 00:33:06.899 --> 00:33:09.049 align:start position:0% readers um<00:33:07.020> sort<00:33:07.260> of<00:33:07.320> going<00:33:07.500> through<00:33:07.799> well<00:33:08.159> users<00:33:08.700> of 00:33:09.049 --> 00:33:09.059 align:start position:0% um sort of going through well users of 00:33:09.059 --> 00:33:10.669 align:start position:0% um sort of going through well users of the<00:33:09.179> protocols<00:33:09.600> that<00:33:09.720> we<00:33:09.840> review<00:33:10.020> going 00:33:10.669 --> 00:33:10.679 align:start position:0% the protocols that we review going 00:33:10.679 --> 00:33:12.649 align:start position:0% the protocols that we review going through<00:33:10.919> our<00:33:11.039> reports<00:33:11.520> and<00:33:12.000> not<00:33:12.120> necessarily 00:33:12.649 --> 00:33:12.659 align:start position:0% through our reports and not necessarily 00:33:12.659 --> 00:33:14.810 align:start position:0% through our reports and not necessarily understanding<00:33:13.320> again<00:33:13.620> the<00:33:13.980> concept<00:33:14.279> of<00:33:14.700> a 00:33:14.810 --> 00:33:14.820 align:start position:0% understanding again the concept of a 00:33:14.820 --> 00:33:17.029 align:start position:0% understanding again the concept of a timebox<00:33:15.179> security<00:33:15.539> assessment<00:33:16.080> in<00:33:16.740> a<00:33:16.860> lot<00:33:16.980> of 00:33:17.029 --> 00:33:17.039 align:start position:0% timebox security assessment in a lot of 00:33:17.039 --> 00:33:19.970 align:start position:0% timebox security assessment in a lot of cases<00:33:17.399> the<00:33:17.940> scope<00:33:18.179> that<00:33:18.659> we<00:33:18.840> actually 00:33:19.970 --> 00:33:19.980 align:start position:0% cases the scope that we actually 00:33:19.980 --> 00:33:22.490 align:start position:0% cases the scope that we actually um go<00:33:20.340> through<00:33:20.519> is<00:33:21.120> a<00:33:21.299> limited<00:33:21.659> part<00:33:21.960> of<00:33:22.320> the 00:33:22.490 --> 00:33:22.500 align:start position:0% um go through is a limited part of the 00:33:22.500 --> 00:33:23.990 align:start position:0% um go through is a limited part of the entire<00:33:22.740> protocol<00:33:23.039> these<00:33:23.460> happens<00:33:23.640> quite 00:33:23.990 --> 00:33:24.000 align:start position:0% entire protocol these happens quite 00:33:24.000 --> 00:33:25.730 align:start position:0% entire protocol these happens quite often<00:33:24.299> particularly<00:33:24.960> with<00:33:25.320> very<00:33:25.500> very 00:33:25.730 --> 00:33:25.740 align:start position:0% often particularly with very very 00:33:25.740 --> 00:33:27.649 align:start position:0% often particularly with very very complex<00:33:26.100> systems 00:33:27.649 --> 00:33:27.659 align:start position:0% complex systems 00:33:27.659 --> 00:33:30.529 align:start position:0% complex systems um<00:33:27.779> and<00:33:28.260> unfortunately<00:33:28.679> some<00:33:29.100> users<00:33:29.580> may<00:33:30.000> use 00:33:30.529 --> 00:33:30.539 align:start position:0% um and unfortunately some users may use 00:33:30.539 --> 00:33:32.570 align:start position:0% um and unfortunately some users may use our<00:33:30.960> security<00:33:31.260> assessment<00:33:31.740> reports<00:33:32.159> and<00:33:32.340> say 00:33:32.570 --> 00:33:32.580 align:start position:0% our security assessment reports and say 00:33:32.580 --> 00:33:35.810 align:start position:0% our security assessment reports and say look<00:33:33.179> this<00:33:33.840> protocol<00:33:34.140> is<00:33:34.860> absolutely<00:33:35.279> safe 00:33:35.810 --> 00:33:35.820 align:start position:0% look this protocol is absolutely safe 00:33:35.820 --> 00:33:37.970 align:start position:0% look this protocol is absolutely safe because<00:33:36.360> this<00:33:36.720> auditing<00:33:37.200> firm<00:33:37.559> has<00:33:37.799> only 00:33:37.970 --> 00:33:37.980 align:start position:0% because this auditing firm has only 00:33:37.980 --> 00:33:39.950 align:start position:0% because this auditing firm has only found<00:33:38.340> a<00:33:38.640> couple<00:33:38.760> of<00:33:39.000> you<00:33:39.179> know<00:33:39.299> mediums<00:33:39.840> and 00:33:39.950 --> 00:33:39.960 align:start position:0% found a couple of you know mediums and 00:33:39.960 --> 00:33:41.750 align:start position:0% found a couple of you know mediums and lows<00:33:40.320> and<00:33:40.440> informationals<00:33:41.159> and<00:33:41.460> they've<00:33:41.700> all 00:33:41.750 --> 00:33:41.760 align:start position:0% lows and informationals and they've all 00:33:41.760 --> 00:33:42.970 align:start position:0% lows and informationals and they've all been<00:33:41.940> resolved 00:33:42.970 --> 00:33:42.980 align:start position:0% been resolved 00:33:42.980 --> 00:33:45.950 align:start position:0% been resolved it<00:33:43.980> right<00:33:44.159> exactly<00:33:44.880> that's<00:33:45.360> right<00:33:45.539> they 00:33:45.950 --> 00:33:45.960 align:start position:0% it right exactly that's right they 00:33:45.960 --> 00:33:49.070 align:start position:0% it right exactly that's right they passed<00:33:46.620> the<00:33:46.799> audit<00:33:47.159> big<00:33:47.580> check<00:33:47.760> mark<00:33:48.000> none<00:33:48.960> of 00:33:49.070 --> 00:33:49.080 align:start position:0% passed the audit big check mark none of 00:33:49.080 --> 00:33:52.250 align:start position:0% passed the audit big check mark none of us<00:33:49.200> here<00:33:49.559> provide<00:33:50.340> you<00:33:50.700> know<00:33:50.820> any<00:33:51.240> big<00:33:52.080> green 00:33:52.250 --> 00:33:52.260 align:start position:0% us here provide you know any big green 00:33:52.260 --> 00:33:54.049 align:start position:0% us here provide you know any big green check<00:33:52.620> mark<00:33:52.860> in<00:33:53.100> our<00:33:53.220> auditing<00:33:53.640> reports 00:33:54.049 --> 00:33:54.059 align:start position:0% check mark in our auditing reports 00:33:54.059 --> 00:33:56.029 align:start position:0% check mark in our auditing reports there's<00:33:54.539> plenty<00:33:54.899> of<00:33:54.960> other<00:33:55.260> firms<00:33:55.679> that<00:33:55.799> do 00:33:56.029 --> 00:33:56.039 align:start position:0% there's plenty of other firms that do 00:33:56.039 --> 00:33:57.889 align:start position:0% there's plenty of other firms that do that<00:33:56.279> unfortunately 00:33:57.889 --> 00:33:57.899 align:start position:0% that unfortunately 00:33:57.899 --> 00:33:59.029 align:start position:0% that unfortunately um so<00:33:58.320> yeah<00:33:58.380> I<00:33:58.559> think<00:33:58.679> I<00:33:58.799> think<00:33:58.919> you're 00:33:59.029 --> 00:33:59.039 align:start position:0% um so yeah I think I think you're 00:33:59.039 --> 00:34:02.029 align:start position:0% um so yeah I think I think you're absolutely<00:33:59.399> right<00:33:59.640> the<00:34:00.059> audience<00:34:00.659> of<00:34:01.380> these 00:34:02.029 --> 00:34:02.039 align:start position:0% absolutely right the audience of these 00:34:02.039 --> 00:34:04.070 align:start position:0% absolutely right the audience of these these<00:34:02.279> security<00:34:02.399> assessment<00:34:02.820> report<00:34:03.059> is<00:34:04.080> um 00:34:04.070 --> 00:34:04.080 align:start position:0% these security assessment report is um 00:34:04.080 --> 00:34:06.049 align:start position:0% these security assessment report is um is<00:34:04.620> a<00:34:04.740> tricky<00:34:05.100> one 00:34:06.049 --> 00:34:06.059 align:start position:0% is a tricky one 00:34:06.059 --> 00:34:06.769 align:start position:0% is a tricky one um 00:34:06.769 --> 00:34:06.779 align:start position:0% um 00:34:06.779 --> 00:34:09.409 align:start position:0% um let<00:34:07.440> me<00:34:07.620> sneak<00:34:07.980> another<00:34:08.220> question<00:34:08.639> if<00:34:09.300> a 00:34:09.409 --> 00:34:09.419 align:start position:0% let me sneak another question if a 00:34:09.419 --> 00:34:12.950 align:start position:0% let me sneak another question if a client<00:34:09.659> asks<00:34:10.139> you<00:34:10.260> to<00:34:10.859> remove<00:34:11.760> something<00:34:12.419> so 00:34:12.950 --> 00:34:12.960 align:start position:0% client asks you to remove something so 00:34:12.960 --> 00:34:15.349 align:start position:0% client asks you to remove something so or<00:34:13.379> rephrase<00:34:13.980> something<00:34:14.280> are<00:34:14.760> you<00:34:14.940> writing<00:34:15.240> it 00:34:15.349 --> 00:34:15.359 align:start position:0% or rephrase something are you writing it 00:34:15.359 --> 00:34:18.349 align:start position:0% or rephrase something are you writing it for<00:34:15.839> a<00:34:15.960> client<00:34:16.379> yeah<00:34:16.940> this<00:34:17.940> happens<00:34:18.060> quite 00:34:18.349 --> 00:34:18.359 align:start position:0% for a client yeah this happens quite 00:34:18.359 --> 00:34:20.270 align:start position:0% for a client yeah this happens quite often<00:34:18.540> I'm<00:34:18.839> sure<00:34:18.960> I'm<00:34:19.200> sure<00:34:19.379> that<00:34:19.859> like<00:34:20.099> it 00:34:20.270 --> 00:34:20.280 align:start position:0% often I'm sure I'm sure that like it 00:34:20.280 --> 00:34:22.430 align:start position:0% often I'm sure I'm sure that like it happens<00:34:20.460> quite<00:34:20.760> often<00:34:21.000> yeah<00:34:21.240> I'll<00:34:21.419> take<00:34:21.540> it<00:34:21.720> uh 00:34:22.430 --> 00:34:22.440 align:start position:0% happens quite often yeah I'll take it uh 00:34:22.440 --> 00:34:25.310 align:start position:0% happens quite often yeah I'll take it uh no<00:34:22.740> no<00:34:23.040> no<00:34:23.040> no<00:34:23.099> I<00:34:23.820> mean<00:34:23.940> I<00:34:24.300> mean<00:34:24.419> a<00:34:24.720> client<00:34:25.020> can 00:34:25.310 --> 00:34:25.320 align:start position:0% no no no no I mean I mean a client can 00:34:25.320 --> 00:34:28.310 align:start position:0% no no no no I mean I mean a client can argue<00:34:25.740> on<00:34:26.099> the<00:34:26.280> severity<00:34:26.760> of<00:34:27.000> a<00:34:27.179> bug<00:34:27.300> right<00:34:27.960> and 00:34:28.310 --> 00:34:28.320 align:start position:0% argue on the severity of a bug right and 00:34:28.320 --> 00:34:30.589 align:start position:0% argue on the severity of a bug right and that's<00:34:28.560> absolutely<00:34:29.159> fine<00:34:30.000> you<00:34:30.359> know<00:34:30.419> we're 00:34:30.589 --> 00:34:30.599 align:start position:0% that's absolutely fine you know we're 00:34:30.599 --> 00:34:31.490 align:start position:0% that's absolutely fine you know we're more<00:34:30.780> than<00:34:30.899> happy<00:34:31.020> to<00:34:31.200> have<00:34:31.320> that 00:34:31.490 --> 00:34:31.500 align:start position:0% more than happy to have that 00:34:31.500 --> 00:34:33.349 align:start position:0% more than happy to have that conversation<00:34:31.919> and<00:34:32.220> be<00:34:32.339> like<00:34:32.520> okay<00:34:32.760> why<00:34:33.119> do<00:34:33.240> you 00:34:33.349 --> 00:34:33.359 align:start position:0% conversation and be like okay why do you 00:34:33.359 --> 00:34:35.149 align:start position:0% conversation and be like okay why do you think<00:34:33.480> this<00:34:33.659> is<00:34:33.780> not<00:34:33.899> a<00:34:34.080> critical<00:34:34.320> like<00:34:34.859> look 00:34:35.149 --> 00:34:35.159 align:start position:0% think this is not a critical like look 00:34:35.159 --> 00:34:36.230 align:start position:0% think this is not a critical like look I've<00:34:35.460> got 00:34:36.230 --> 00:34:36.240 align:start position:0% I've got 00:34:36.240 --> 00:34:38.629 align:start position:0% I've got systems<00:34:36.960> of<00:34:37.080> chain<00:34:37.320> in<00:34:37.679> place<00:34:37.859> to<00:34:38.339> prevent 00:34:38.629 --> 00:34:38.639 align:start position:0% systems of chain in place to prevent 00:34:38.639 --> 00:34:40.010 align:start position:0% systems of chain in place to prevent this<00:34:38.879> from<00:34:39.060> happening<00:34:39.419> that<00:34:39.720> I<00:34:39.839> would 00:34:40.010 --> 00:34:40.020 align:start position:0% this from happening that I would 00:34:40.020 --> 00:34:41.990 align:start position:0% this from happening that I would actually<00:34:40.260> drop<00:34:40.679> down<00:34:40.919> the<00:34:41.099> likelihood<00:34:41.580> of 00:34:41.990 --> 00:34:42.000 align:start position:0% actually drop down the likelihood of 00:34:42.000 --> 00:34:44.750 align:start position:0% actually drop down the likelihood of exploitation<00:34:42.480> I'm<00:34:42.839> like<00:34:43.020> okay<00:34:43.740> fair<00:34:44.399> I'm 00:34:44.750 --> 00:34:44.760 align:start position:0% exploitation I'm like okay fair I'm 00:34:44.760 --> 00:34:46.550 align:start position:0% exploitation I'm like okay fair I'm happy<00:34:44.940> to<00:34:45.119> drop<00:34:45.300> down<00:34:45.540> the<00:34:45.780> likelihood<00:34:46.200> which 00:34:46.550 --> 00:34:46.560 align:start position:0% happy to drop down the likelihood which 00:34:46.560 --> 00:34:48.649 align:start position:0% happy to drop down the likelihood which would<00:34:46.859> effectively<00:34:47.399> impact<00:34:47.820> the<00:34:48.000> severity<00:34:48.419> of 00:34:48.649 --> 00:34:48.659 align:start position:0% would effectively impact the severity of 00:34:48.659 --> 00:34:50.629 align:start position:0% would effectively impact the severity of the<00:34:48.780> bug<00:34:48.960> but<00:34:49.440> removing<00:34:49.919> a<00:34:50.040> bug<00:34:50.159> from<00:34:50.399> a<00:34:50.520> report 00:34:50.629 --> 00:34:50.639 align:start position:0% the bug but removing a bug from a report 00:34:50.639 --> 00:34:52.550 align:start position:0% the bug but removing a bug from a report if<00:34:50.940> it's<00:34:51.060> valid<00:34:51.359> hell<00:34:51.599> no 00:34:52.550 --> 00:34:52.560 align:start position:0% if it's valid hell no 00:34:52.560 --> 00:34:54.710 align:start position:0% if it's valid hell no now<00:34:53.040> this<00:34:53.280> goes<00:34:53.580> against<00:34:53.700> the<00:34:54.240> trusted 00:34:54.710 --> 00:34:54.720 align:start position:0% now this goes against the trusted 00:34:54.720 --> 00:34:58.130 align:start position:0% now this goes against the trusted advisor<00:34:55.580> role<00:34:56.580> which<00:34:56.760> we<00:34:56.879> play<00:34:57.060> and<00:34:57.660> and<00:34:57.839> how 00:34:58.130 --> 00:34:58.140 align:start position:0% advisor role which we play and and how 00:34:58.140 --> 00:34:59.690 align:start position:0% advisor role which we play and and how to<00:34:58.260> read<00:34:58.380> our<00:34:58.560> reports<00:34:58.980> or<00:34:59.160> I<00:34:59.339> think<00:34:59.460> all<00:34:59.640> of 00:34:59.690 --> 00:34:59.700 align:start position:0% to read our reports or I think all of 00:34:59.700 --> 00:35:01.550 align:start position:0% to read our reports or I think all of our<00:34:59.820> reports<00:35:00.180> is<00:35:00.720> that<00:35:00.900> it<00:35:01.020> isn't<00:35:01.260> that<00:35:01.380> check 00:35:01.550 --> 00:35:01.560 align:start position:0% our reports is that it isn't that check 00:35:01.560 --> 00:35:03.589 align:start position:0% our reports is that it isn't that check mark<00:35:01.800> and<00:35:02.099> what<00:35:02.339> I<00:35:02.580> want<00:35:02.760> to<00:35:02.940> see<00:35:03.119> from<00:35:03.420> a 00:35:03.589 --> 00:35:03.599 align:start position:0% mark and what I want to see from a 00:35:03.599 --> 00:35:05.570 align:start position:0% mark and what I want to see from a customer<00:35:03.720> is<00:35:04.619> I<00:35:04.859> want<00:35:04.980> to<00:35:05.040> see<00:35:05.160> them<00:35:05.280> come<00:35:05.460> out 00:35:05.570 --> 00:35:05.580 align:start position:0% customer is I want to see them come out 00:35:05.580 --> 00:35:07.010 align:start position:0% customer is I want to see them come out with<00:35:05.760> our<00:35:05.880> original<00:35:06.060> report<00:35:06.359> which<00:35:06.720> we<00:35:06.900> will 00:35:07.010 --> 00:35:07.020 align:start position:0% with our original report which we will 00:35:07.020 --> 00:35:11.150 align:start position:0% with our original report which we will not<00:35:07.200> change<00:35:07.820> and<00:35:08.820> so<00:35:09.660> you<00:35:10.020> as<00:35:10.260> as<00:35:10.619> the<00:35:10.980> public 00:35:11.150 --> 00:35:11.160 align:start position:0% not change and so you as as the public 00:35:11.160 --> 00:35:12.950 align:start position:0% not change and so you as as the public can<00:35:11.700> look<00:35:12.000> at<00:35:12.119> the<00:35:12.240> report<00:35:12.359> and<00:35:12.660> see<00:35:12.839> the 00:35:12.950 --> 00:35:12.960 align:start position:0% can look at the report and see the 00:35:12.960 --> 00:35:14.569 align:start position:0% can look at the report and see the problems<00:35:13.260> that<00:35:13.380> they<00:35:13.560> faced<00:35:13.920> and<00:35:14.400> then<00:35:14.460> you 00:35:14.569 --> 00:35:14.579 align:start position:0% problems that they faced and then you 00:35:14.579 --> 00:35:16.130 align:start position:0% problems that they faced and then you can<00:35:14.700> look<00:35:14.820> at<00:35:14.940> the<00:35:15.060> fix<00:35:15.180> review<00:35:15.480> report<00:35:15.780> which 00:35:16.130 --> 00:35:16.140 align:start position:0% can look at the fix review report which 00:35:16.140 --> 00:35:17.569 align:start position:0% can look at the fix review report which is<00:35:16.260> separate<00:35:16.619> or<00:35:16.740> an<00:35:16.920> appendix<00:35:17.280> it's<00:35:17.460> just 00:35:17.569 --> 00:35:17.579 align:start position:0% is separate or an appendix it's just 00:35:17.579 --> 00:35:19.910 align:start position:0% is separate or an appendix it's just it's<00:35:17.820> it's<00:35:18.000> different<00:35:18.359> and<00:35:19.079> see<00:35:19.200> okay<00:35:19.440> you<00:35:19.800> can 00:35:19.910 --> 00:35:19.920 align:start position:0% it's it's different and see okay you can 00:35:19.920 --> 00:35:21.770 align:start position:0% it's it's different and see okay you can actually<00:35:20.040> watch<00:35:20.460> the<00:35:20.700> progression<00:35:21.300> as 00:35:21.770 --> 00:35:21.780 align:start position:0% actually watch the progression as 00:35:21.780 --> 00:35:22.970 align:start position:0% actually watch the progression as they're<00:35:21.960> taking<00:35:22.200> the<00:35:22.440> advice<00:35:22.680> they're 00:35:22.970 --> 00:35:22.980 align:start position:0% they're taking the advice they're 00:35:22.980 --> 00:35:24.589 align:start position:0% they're taking the advice they're understanding<00:35:23.400> not<00:35:23.640> just<00:35:23.760> how<00:35:23.940> to<00:35:24.060> fix<00:35:24.240> that 00:35:24.589 --> 00:35:24.599 align:start position:0% understanding not just how to fix that 00:35:24.599 --> 00:35:26.990 align:start position:0% understanding not just how to fix that bug<00:35:24.780> but<00:35:25.380> how<00:35:25.560> to<00:35:25.680> fix<00:35:25.800> bugs<00:35:26.280> like<00:35:26.520> that<00:35:26.760> from 00:35:26.990 --> 00:35:27.000 align:start position:0% bug but how to fix bugs like that from 00:35:27.000 --> 00:35:31.190 align:start position:0% bug but how to fix bugs like that from happening<00:35:27.420> at<00:35:27.780> all<00:35:27.960> and<00:35:28.560> and<00:35:29.119> some<00:35:30.200> companies 00:35:31.190 --> 00:35:31.200 align:start position:0% happening at all and and some companies 00:35:31.200 --> 00:35:32.990 align:start position:0% happening at all and and some companies are<00:35:31.500> afraid<00:35:31.920> to<00:35:32.160> do<00:35:32.280> that<00:35:32.460> because<00:35:32.700> people 00:35:32.990 --> 00:35:33.000 align:start position:0% are afraid to do that because people 00:35:33.000 --> 00:35:34.069 align:start position:0% are afraid to do that because people will<00:35:33.180> think<00:35:33.420> that<00:35:33.540> they're<00:35:33.660> not<00:35:33.839> good<00:35:33.960> at 00:35:34.069 --> 00:35:34.079 align:start position:0% will think that they're not good at 00:35:34.079 --> 00:35:35.569 align:start position:0% will think that they're not good at security<00:35:34.260> I<00:35:34.560> look<00:35:34.680> at<00:35:34.800> it<00:35:34.920> as<00:35:34.980> the<00:35:35.160> exact 00:35:35.569 --> 00:35:35.579 align:start position:0% security I look at it as the exact 00:35:35.579 --> 00:35:38.569 align:start position:0% security I look at it as the exact opposite<00:35:36.060> a<00:35:36.780> company<00:35:37.380> that<00:35:37.800> is<00:35:37.980> proud<00:35:38.280> to<00:35:38.460> say 00:35:38.569 --> 00:35:38.579 align:start position:0% opposite a company that is proud to say 00:35:38.579 --> 00:35:40.490 align:start position:0% opposite a company that is proud to say look<00:35:38.820> these<00:35:39.480> are<00:35:39.540> the<00:35:39.720> challenges<00:35:40.079> we<00:35:40.320> face 00:35:40.490 --> 00:35:40.500 align:start position:0% look these are the challenges we face 00:35:40.500 --> 00:35:42.050 align:start position:0% look these are the challenges we face and<00:35:40.800> here<00:35:41.040> are<00:35:41.160> the<00:35:41.339> innovative<00:35:41.640> solutions 00:35:42.050 --> 00:35:42.060 align:start position:0% and here are the innovative solutions 00:35:42.060 --> 00:35:43.970 align:start position:0% and here are the innovative solutions that<00:35:42.300> we<00:35:42.420> came<00:35:42.540> up<00:35:42.660> with<00:35:42.839> to<00:35:43.380> address<00:35:43.619> them 00:35:43.970 --> 00:35:43.980 align:start position:0% that we came up with to address them 00:35:43.980 --> 00:35:45.710 align:start position:0% that we came up with to address them that's<00:35:44.280> where<00:35:44.520> I<00:35:44.640> want<00:35:44.760> to<00:35:44.880> look<00:35:45.000> because<00:35:45.359> now 00:35:45.710 --> 00:35:45.720 align:start position:0% that's where I want to look because now 00:35:45.720 --> 00:35:47.329 align:start position:0% that's where I want to look because now they're<00:35:46.020> they're<00:35:46.320> actually<00:35:46.619> taking<00:35:47.040> our 00:35:47.329 --> 00:35:47.339 align:start position:0% they're they're actually taking our 00:35:47.339 --> 00:35:48.530 align:start position:0% they're they're actually taking our advice<00:35:47.640> and<00:35:47.880> they're<00:35:48.060> and<00:35:48.240> they're<00:35:48.420> doing 00:35:48.530 --> 00:35:48.540 align:start position:0% advice and they're and they're doing 00:35:48.540 --> 00:35:49.849 align:start position:0% advice and they're and they're doing what<00:35:48.720> they<00:35:48.780> should<00:35:48.900> do<00:35:49.020> with<00:35:49.140> an<00:35:49.260> office<00:35:49.440> is 00:35:49.849 --> 00:35:49.859 align:start position:0% what they should do with an office is 00:35:49.859 --> 00:35:52.490 align:start position:0% what they should do with an office is there<00:35:49.980> I<00:35:50.160> want<00:35:50.460> to<00:35:50.579> like<00:35:50.820> is<00:35:51.320> Chandra<00:35:52.320> is<00:35:52.440> there 00:35:52.490 --> 00:35:52.500 align:start position:0% there I want to like is Chandra is there 00:35:52.500 --> 00:35:54.829 align:start position:0% there I want to like is Chandra is there are<00:35:53.099> a<00:35:53.339> difference 00:35:54.829 --> 00:35:54.839 align:start position:0% are a difference 00:35:54.839 --> 00:35:57.050 align:start position:0% are a difference in<00:35:55.500> the<00:35:55.619> way<00:35:55.740> that<00:35:55.920> like<00:35:56.160> a<00:35:56.339> report<00:35:56.520> needs<00:35:57.000> to 00:35:57.050 --> 00:35:57.060 align:start position:0% in the way that like a report needs to 00:35:57.060 --> 00:35:59.089 align:start position:0% in the way that like a report needs to be<00:35:57.119> presented<00:35:57.599> when<00:35:58.260> it's<00:35:58.500> like<00:35:58.680> heavy<00:35:58.980> on 00:35:59.089 --> 00:35:59.099 align:start position:0% be presented when it's like heavy on 00:35:59.099 --> 00:36:01.130 align:start position:0% be presented when it's like heavy on formal<00:35:59.460> verification 00:36:01.130 --> 00:36:01.140 align:start position:0% formal verification 00:36:01.140 --> 00:36:02.990 align:start position:0% formal verification I<00:36:01.500> mean<00:36:01.619> I 00:36:02.990 --> 00:36:03.000 align:start position:0% I mean I 00:36:03.000 --> 00:36:04.430 align:start position:0% I mean I think we 00:36:04.430 --> 00:36:04.440 align:start position:0% think we 00:36:04.440 --> 00:36:06.109 align:start position:0% think we similar<00:36:04.859> reports<00:36:05.280> and<00:36:05.400> like<00:36:05.579> Maddie<00:36:06.000> said 00:36:06.109 --> 00:36:06.119 align:start position:0% similar reports and like Maddie said 00:36:06.119 --> 00:36:08.870 align:start position:0% similar reports and like Maddie said right<00:36:06.240> like<00:36:06.480> we<00:36:06.900> have<00:36:07.560> the<00:36:08.040> severity<00:36:08.520> of<00:36:08.760> the 00:36:08.870 --> 00:36:08.880 align:start position:0% right like we have the severity of the 00:36:08.880 --> 00:36:12.290 align:start position:0% right like we have the severity of the bugs<00:36:09.240> and<00:36:10.040> we<00:36:11.040> explain<00:36:11.220> exactly<00:36:11.940> what 00:36:12.290 --> 00:36:12.300 align:start position:0% bugs and we explain exactly what 00:36:12.300 --> 00:36:14.210 align:start position:0% bugs and we explain exactly what property<00:36:12.720> we<00:36:12.900> wrote<00:36:13.200> and<00:36:13.560> why<00:36:13.920> that 00:36:14.210 --> 00:36:14.220 align:start position:0% property we wrote and why that 00:36:14.220 --> 00:36:16.130 align:start position:0% property we wrote and why that corresponds<00:36:14.700> to<00:36:14.880> the<00:36:15.119> bug<00:36:15.300> and 00:36:16.130 --> 00:36:16.140 align:start position:0% corresponds to the bug and 00:36:16.140 --> 00:36:18.950 align:start position:0% corresponds to the bug and I<00:36:16.859> think<00:36:17.099> the<00:36:17.579> only<00:36:17.880> additional<00:36:18.359> thing<00:36:18.660> that 00:36:18.950 --> 00:36:18.960 align:start position:0% I think the only additional thing that 00:36:18.960 --> 00:36:22.569 align:start position:0% I think the only additional thing that we<00:36:19.380> very<00:36:20.099> much<00:36:20.400> emphasize<00:36:21.000> is<00:36:21.300> that<00:36:21.599> you<00:36:21.900> know 00:36:22.569 --> 00:36:22.579 align:start position:0% we very much emphasize is that you know 00:36:22.579 --> 00:36:25.250 align:start position:0% we very much emphasize is that you know uh<00:36:23.579> like<00:36:24.000> this<00:36:24.119> like 00:36:25.250 --> 00:36:25.260 align:start position:0% uh like this like 00:36:25.260 --> 00:36:28.849 align:start position:0% uh like this like be<00:36:25.859> careful<00:36:26.160> that<00:36:26.579> don't<00:36:27.079> just<00:36:28.079> take<00:36:28.440> this<00:36:28.680> as 00:36:28.849 --> 00:36:28.859 align:start position:0% be careful that don't just take this as 00:36:28.859 --> 00:36:31.790 align:start position:0% be careful that don't just take this as like<00:36:29.160> the<00:36:29.520> you<00:36:30.119> know<00:36:30.240> uh<00:36:30.960> this<00:36:31.440> is<00:36:31.560> not<00:36:31.680> a 00:36:31.790 --> 00:36:31.800 align:start position:0% like the you know uh this is not a 00:36:31.800 --> 00:36:33.950 align:start position:0% like the you know uh this is not a silver<00:36:31.980> bullet<00:36:32.400> and<00:36:32.579> like<00:36:32.880> the<00:36:33.180> yeah<00:36:33.660> I<00:36:33.780> think 00:36:33.950 --> 00:36:33.960 align:start position:0% silver bullet and like the yeah I think 00:36:33.960 --> 00:36:35.510 align:start position:0% silver bullet and like the yeah I think there's<00:36:34.140> no<00:36:34.320> difference<00:36:34.500> to<00:36:34.800> be<00:36:34.980> honest<00:36:35.280> in 00:36:35.510 --> 00:36:35.520 align:start position:0% there's no difference to be honest in 00:36:35.520 --> 00:36:38.030 align:start position:0% there's no difference to be honest in terms<00:36:35.760> of<00:36:35.880> the<00:36:36.300> reports<00:36:36.660> we<00:36:36.780> write 00:36:38.030 --> 00:36:38.040 align:start position:0% terms of the reports we write 00:36:38.040 --> 00:36:40.849 align:start position:0% terms of the reports we write um<00:36:38.220> okay<00:36:38.579> Mike<00:36:39.180> thank<00:36:39.720> you 00:36:40.849 --> 00:36:40.859 align:start position:0% um okay Mike thank you 00:36:40.859 --> 00:36:42.770 align:start position:0% um okay Mike thank you um<00:36:40.980> so<00:36:41.220> uh<00:36:41.640> disclosure<00:36:42.119> I<00:36:42.180> work<00:36:42.300> with<00:36:42.420> Jonathan 00:36:42.770 --> 00:36:42.780 align:start position:0% um so uh disclosure I work with Jonathan 00:36:42.780 --> 00:36:43.849 align:start position:0% um so uh disclosure I work with Jonathan and<00:36:42.900> open<00:36:43.020> Zeppelin<00:36:43.440> but<00:36:43.560> I<00:36:43.680> didn't<00:36:43.740> tell 00:36:43.849 --> 00:36:43.859 align:start position:0% and open Zeppelin but I didn't tell 00:36:43.859 --> 00:36:44.990 align:start position:0% and open Zeppelin but I didn't tell about<00:36:43.980> the<00:36:44.220> question<00:36:44.339> ahead<00:36:44.579> of<00:36:44.700> time<00:36:44.820> so 00:36:44.990 --> 00:36:45.000 align:start position:0% about the question ahead of time so 00:36:45.000 --> 00:36:46.670 align:start position:0% about the question ahead of time so there's<00:36:45.119> no<00:36:45.359> front<00:36:45.480> running<00:36:45.660> here 00:36:46.670 --> 00:36:46.680 align:start position:0% there's no front running here 00:36:46.680 --> 00:36:49.670 align:start position:0% there's no front running here um<00:36:46.800> if<00:36:47.460> you<00:36:47.640> could<00:36:47.760> wave<00:36:48.060> your<00:36:48.180> hand<00:36:48.359> and<00:36:49.260> every 00:36:49.670 --> 00:36:49.680 align:start position:0% um if you could wave your hand and every 00:36:49.680 --> 00:36:51.530 align:start position:0% um if you could wave your hand and every single<00:36:49.980> developer<00:36:50.640> in<00:36:50.880> the<00:36:51.000> space<00:36:51.119> but<00:36:51.420> most 00:36:51.530 --> 00:36:51.540 align:start position:0% single developer in the space but most 00:36:51.540 --> 00:36:53.030 align:start position:0% single developer in the space but most especially<00:36:51.960> your<00:36:52.140> clients<00:36:52.560> just 00:36:53.030 --> 00:36:53.040 align:start position:0% especially your clients just 00:36:53.040 --> 00:36:54.230 align:start position:0% especially your clients just automatically<00:36:53.520> follow<00:36:53.700> the<00:36:53.940> best<00:36:54.060> practice 00:36:54.230 --> 00:36:54.240 align:start position:0% automatically follow the best practice 00:36:54.240 --> 00:36:55.550 align:start position:0% automatically follow the best practice without<00:36:54.540> you<00:36:54.780> having<00:36:54.900> to<00:36:55.079> tell<00:36:55.200> them<00:36:55.320> ever 00:36:55.550 --> 00:36:55.560 align:start position:0% without you having to tell them ever 00:36:55.560 --> 00:36:56.270 align:start position:0% without you having to tell them ever again 00:36:56.270 --> 00:36:56.280 align:start position:0% again 00:36:56.280 --> 00:36:59.390 align:start position:0% again what<00:36:56.760> would<00:36:56.880> it<00:36:57.060> be<00:36:57.180> yeah<00:36:57.839> yeah<00:36:58.079> it<00:36:58.440> was<00:36:59.220> a<00:36:59.339> bit 00:36:59.390 --> 00:36:59.400 align:start position:0% what would it be yeah yeah it was a bit 00:36:59.400 --> 00:37:01.730 align:start position:0% what would it be yeah yeah it was a bit echoey<00:36:59.880> but<00:37:00.000> uh<00:37:00.359> if<00:37:00.660> you<00:37:00.839> could<00:37:01.020> magically 00:37:01.730 --> 00:37:01.740 align:start position:0% echoey but uh if you could magically 00:37:01.740 --> 00:37:04.490 align:start position:0% echoey but uh if you could magically like<00:37:02.040> if<00:37:02.160> you<00:37:02.640> could<00:37:02.820> be<00:37:03.480> sure<00:37:03.660> that<00:37:04.020> every 00:37:04.490 --> 00:37:04.500 align:start position:0% like if you could be sure that every 00:37:04.500 --> 00:37:06.650 align:start position:0% like if you could be sure that every client<00:37:04.980> if<00:37:05.460> there's<00:37:05.640> one<00:37:05.880> best<00:37:06.119> practice<00:37:06.359> that 00:37:06.650 --> 00:37:06.660 align:start position:0% client if there's one best practice that 00:37:06.660 --> 00:37:09.109 align:start position:0% client if there's one best practice that you<00:37:06.780> wish<00:37:06.960> every<00:37:07.200> client<00:37:07.560> would<00:37:07.980> would<00:37:08.579> adhere 00:37:09.109 --> 00:37:09.119 align:start position:0% you wish every client would would adhere 00:37:09.119 --> 00:37:11.510 align:start position:0% you wish every client would would adhere to<00:37:09.300> what<00:37:09.960> would<00:37:10.079> it<00:37:10.200> be 00:37:11.510 --> 00:37:11.520 align:start position:0% to what would it be 00:37:11.520 --> 00:37:12.290 align:start position:0% to what would it be um 00:37:12.290 --> 00:37:12.300 align:start position:0% um 00:37:12.300 --> 00:37:13.910 align:start position:0% um who's<00:37:12.660> feel<00:37:12.960> yeah<00:37:13.260> all<00:37:13.380> right<00:37:13.440> I've<00:37:13.680> got<00:37:13.800> one 00:37:13.910 --> 00:37:13.920 align:start position:0% who's feel yeah all right I've got one 00:37:13.920 --> 00:37:16.010 align:start position:0% who's feel yeah all right I've got one do<00:37:14.220> not<00:37:14.400> change<00:37:14.760> commits<00:37:15.420> meet<00:37:15.660> the<00:37:15.839> reviews 00:37:16.010 --> 00:37:16.020 align:start position:0% do not change commits meet the reviews 00:37:16.020 --> 00:37:21.650 align:start position:0% do not change commits meet the reviews please<00:37:16.920> thank<00:37:17.880> you 00:37:21.650 --> 00:37:21.660 align:start position:0% 00:37:21.660 --> 00:37:24.710 align:start position:0% should<00:37:22.260> I<00:37:22.560> should<00:37:23.400> I<00:37:23.579> start<00:37:24.000> formal 00:37:24.710 --> 00:37:24.720 align:start position:0% should I should I start formal 00:37:24.720 --> 00:37:27.890 align:start position:0% should I should I start formal verification<00:37:25.260> at<00:37:26.099> the<00:37:26.339> very<00:37:26.940> beginning<00:37:27.180> and 00:37:27.890 --> 00:37:27.900 align:start position:0% verification at the very beginning and 00:37:27.900 --> 00:37:30.530 align:start position:0% verification at the very beginning and continuously<00:37:28.380> throughout<00:37:28.920> the<00:37:29.820> project<00:37:30.000> or 00:37:30.530 --> 00:37:30.540 align:start position:0% continuously throughout the project or 00:37:30.540 --> 00:37:33.170 align:start position:0% continuously throughout the project or only<00:37:30.839> at<00:37:31.320> the<00:37:31.440> very<00:37:31.740> end<00:37:31.980> oh<00:37:32.700> that's<00:37:32.880> such<00:37:33.060> a 00:37:33.170 --> 00:37:33.180 align:start position:0% only at the very end oh that's such a 00:37:33.180 --> 00:37:34.250 align:start position:0% only at the very end oh that's such a good<00:37:33.240> question 00:37:34.250 --> 00:37:34.260 align:start position:0% good question 00:37:34.260 --> 00:37:36.710 align:start position:0% good question uh<00:37:34.800> so<00:37:35.040> the<00:37:35.400> question<00:37:35.520> is<00:37:35.820> do<00:37:36.300> you<00:37:36.420> want<00:37:36.480> should 00:37:36.710 --> 00:37:36.720 align:start position:0% uh so the question is do you want should 00:37:36.720 --> 00:37:39.109 align:start position:0% uh so the question is do you want should we<00:37:36.839> start<00:37:37.020> formal<00:37:37.380> verification<00:37:37.940> towards<00:37:38.940> the 00:37:39.109 --> 00:37:39.119 align:start position:0% we start formal verification towards the 00:37:39.119 --> 00:37:41.030 align:start position:0% we start formal verification towards the end<00:37:39.240> or<00:37:39.540> do<00:37:39.780> towards<00:37:40.200> the<00:37:40.260> beginning<00:37:40.380> of<00:37:40.800> your 00:37:41.030 --> 00:37:41.040 align:start position:0% end or do towards the beginning of your 00:37:41.040 --> 00:37:42.349 align:start position:0% end or do towards the beginning of your development 00:37:42.349 --> 00:37:42.359 align:start position:0% development 00:37:42.359 --> 00:37:44.030 align:start position:0% development so<00:37:42.780> this<00:37:43.020> is<00:37:43.140> a<00:37:43.320> very<00:37:43.440> interesting<00:37:43.800> question 00:37:44.030 --> 00:37:44.040 align:start position:0% so this is a very interesting question 00:37:44.040 --> 00:37:46.609 align:start position:0% so this is a very interesting question you<00:37:44.700> should<00:37:44.880> start<00:37:45.420> as<00:37:45.780> early<00:37:45.960> as<00:37:46.260> you<00:37:46.440> can 00:37:46.609 --> 00:37:46.619 align:start position:0% you should start as early as you can 00:37:46.619 --> 00:37:48.650 align:start position:0% you should start as early as you can that's<00:37:47.160> uh<00:37:47.520> based<00:37:47.880> on<00:37:47.940> you<00:37:48.300> know<00:37:48.359> our 00:37:48.650 --> 00:37:48.660 align:start position:0% that's uh based on you know our 00:37:48.660 --> 00:37:50.450 align:start position:0% that's uh based on you know our experience<00:37:49.020> I<00:37:49.260> think<00:37:49.440> that's<00:37:49.740> the<00:37:50.099> right 00:37:50.450 --> 00:37:50.460 align:start position:0% experience I think that's the right 00:37:50.460 --> 00:37:54.290 align:start position:0% experience I think that's the right place<00:37:50.940> to<00:37:51.720> start<00:37:52.440> thinking<00:37:52.800> about<00:37:52.980> uh<00:37:53.940> formal 00:37:54.290 --> 00:37:54.300 align:start position:0% place to start thinking about uh formal 00:37:54.300 --> 00:37:55.670 align:start position:0% place to start thinking about uh formal verification<00:37:54.660> I<00:37:54.960> think<00:37:55.020> the<00:37:55.200> most<00:37:55.320> important 00:37:55.670 --> 00:37:55.680 align:start position:0% verification I think the most important 00:37:55.680 --> 00:37:58.130 align:start position:0% verification I think the most important thing<00:37:55.859> there<00:37:56.040> is<00:37:56.220> you<00:37:56.460> know<00:37:56.520> you<00:37:56.820> uh<00:37:57.660> it<00:37:58.020> really 00:37:58.130 --> 00:37:58.140 align:start position:0% thing there is you know you uh it really 00:37:58.140 --> 00:38:00.770 align:start position:0% thing there is you know you uh it really helps<00:37:58.560> you<00:37:58.740> sort<00:37:59.099> of<00:37:59.220> write<00:37:59.460> your<00:37:59.760> code<00:38:00.180> in<00:38:00.599> the 00:38:00.770 --> 00:38:00.780 align:start position:0% helps you sort of write your code in the 00:38:00.780 --> 00:38:03.710 align:start position:0% helps you sort of write your code in the most<00:38:00.960> simple<00:38:01.460> modular<00:38:02.460> way<00:38:02.820> because<00:38:03.240> that's 00:38:03.710 --> 00:38:03.720 align:start position:0% most simple modular way because that's 00:38:03.720 --> 00:38:06.109 align:start position:0% most simple modular way because that's really<00:38:04.020> what<00:38:04.380> is<00:38:04.740> best<00:38:05.160> suited<00:38:05.520> for<00:38:05.700> formal 00:38:06.109 --> 00:38:06.119 align:start position:0% really what is best suited for formal 00:38:06.119 --> 00:38:09.470 align:start position:0% really what is best suited for formal verification<00:38:06.740> and<00:38:07.740> you<00:38:08.160> know<00:38:08.220> it<00:38:08.579> just<00:38:08.760> it 00:38:09.470 --> 00:38:09.480 align:start position:0% verification and you know it just it 00:38:09.480 --> 00:38:10.970 align:start position:0% verification and you know it just it automatically<00:38:09.960> just<00:38:10.260> prevents<00:38:10.680> you<00:38:10.800> from 00:38:10.970 --> 00:38:10.980 align:start position:0% automatically just prevents you from 00:38:10.980 --> 00:38:12.890 align:start position:0% automatically just prevents you from making<00:38:11.220> certain<00:38:11.520> mistakes<00:38:11.940> and<00:38:12.359> I<00:38:12.599> think<00:38:12.720> it's 00:38:12.890 --> 00:38:12.900 align:start position:0% making certain mistakes and I think it's 00:38:12.900 --> 00:38:15.950 align:start position:0% making certain mistakes and I think it's extremely<00:38:13.320> important<00:38:13.740> even<00:38:14.460> if<00:38:14.760> you<00:38:15.060> are<00:38:15.599> you 00:38:15.950 --> 00:38:15.960 align:start position:0% extremely important even if you are you 00:38:15.960 --> 00:38:18.290 align:start position:0% extremely important even if you are you know<00:38:16.280> no<00:38:17.280> matter<00:38:17.400> what<00:38:17.700> kind<00:38:17.820> of<00:38:17.880> verification 00:38:18.290 --> 00:38:18.300 align:start position:0% know no matter what kind of verification 00:38:18.300 --> 00:38:20.329 align:start position:0% know no matter what kind of verification technique<00:38:18.660> you're<00:38:18.839> using<00:38:19.200> the<00:38:19.859> earlier<00:38:20.160> you 00:38:20.329 --> 00:38:20.339 align:start position:0% technique you're using the earlier you 00:38:20.339 --> 00:38:23.089 align:start position:0% technique you're using the earlier you start<00:38:20.579> the<00:38:21.060> better<00:38:21.200> and<00:38:22.200> along<00:38:22.680> the<00:38:22.920> same 00:38:23.089 --> 00:38:23.099 align:start position:0% start the better and along the same 00:38:23.099 --> 00:38:25.730 align:start position:0% start the better and along the same lines<00:38:23.400> you<00:38:23.760> know<00:38:23.820> writing<00:38:24.240> your<00:38:24.420> specs<00:38:24.839> out<00:38:24.960> in 00:38:25.730 --> 00:38:25.740 align:start position:0% lines you know writing your specs out in 00:38:25.740 --> 00:38:28.430 align:start position:0% lines you know writing your specs out in English<00:38:25.940> and<00:38:26.940> also<00:38:27.119> like<00:38:27.420> you<00:38:27.960> know<00:38:28.020> gradually 00:38:28.430 --> 00:38:28.440 align:start position:0% English and also like you know gradually 00:38:28.440 --> 00:38:30.230 align:start position:0% English and also like you know gradually making<00:38:28.740> them<00:38:28.980> somewhat<00:38:29.339> more<00:38:29.520> formal<00:38:29.820> I<00:38:30.060> think 00:38:30.230 --> 00:38:30.240 align:start position:0% making them somewhat more formal I think 00:38:30.240 --> 00:38:32.089 align:start position:0% making them somewhat more formal I think the<00:38:30.540> earlier<00:38:30.780> you<00:38:30.900> do<00:38:31.079> it<00:38:31.200> the<00:38:31.320> better<00:38:31.500> like 00:38:32.089 --> 00:38:32.099 align:start position:0% the earlier you do it the better like 00:38:32.099 --> 00:38:33.650 align:start position:0% the earlier you do it the better like once<00:38:32.400> you've<00:38:32.520> already<00:38:32.760> implemented<00:38:33.480> your 00:38:33.650 --> 00:38:33.660 align:start position:0% once you've already implemented your 00:38:33.660 --> 00:38:36.109 align:start position:0% once you've already implemented your code<00:38:33.960> try<00:38:34.680> to<00:38:34.859> come<00:38:34.920> up<00:38:35.040> with<00:38:35.220> an<00:38:35.339> invariant<00:38:35.820> or 00:38:36.109 --> 00:38:36.119 align:start position:0% code try to come up with an invariant or 00:38:36.119 --> 00:38:37.910 align:start position:0% code try to come up with an invariant or like<00:38:36.420> trying<00:38:36.599> to<00:38:36.780> write<00:38:36.960> down<00:38:37.200> the<00:38:37.619> pre<00:38:37.740> and 00:38:37.910 --> 00:38:37.920 align:start position:0% like trying to write down the pre and 00:38:37.920 --> 00:38:39.589 align:start position:0% like trying to write down the pre and post<00:38:38.099> conditions<00:38:38.579> and<00:38:38.700> stuff<00:38:38.820> it's<00:38:39.060> it<00:38:39.300> gets 00:38:39.589 --> 00:38:39.599 align:start position:0% post conditions and stuff it's it gets 00:38:39.599 --> 00:38:41.930 align:start position:0% post conditions and stuff it's it gets really<00:38:39.720> hard<00:38:40.020> so<00:38:40.500> I<00:38:41.280> think<00:38:41.339> there's<00:38:41.520> like<00:38:41.760> I 00:38:41.930 --> 00:38:41.940 align:start position:0% really hard so I think there's like I 00:38:41.940 --> 00:38:44.750 align:start position:0% really hard so I think there's like I like<00:38:42.300> the<00:38:42.839> shift<00:38:43.140> left<00:38:43.440> security<00:38:43.859> meme<00:38:44.339> which 00:38:44.750 --> 00:38:44.760 align:start position:0% like the shift left security meme which 00:38:44.760 --> 00:38:47.390 align:start position:0% like the shift left security meme which is<00:38:45.000> like<00:38:45.720> it<00:38:46.079> basically<00:38:46.680> just<00:38:46.859> the<00:38:47.040> idea<00:38:47.220> if 00:38:47.390 --> 00:38:47.400 align:start position:0% is like it basically just the idea if 00:38:47.400 --> 00:38:49.490 align:start position:0% is like it basically just the idea if you<00:38:47.579> think<00:38:47.700> of<00:38:47.940> your<00:38:48.359> time<00:38:48.660> and<00:38:48.900> your<00:38:49.140> process 00:38:49.490 --> 00:38:49.500 align:start position:0% you think of your time and your process 00:38:49.500 --> 00:38:52.190 align:start position:0% you think of your time and your process is<00:38:49.740> moving<00:38:50.040> from<00:38:50.280> left<00:38:50.520> to<00:38:50.700> right<00:38:51.200> writing 00:38:52.190 --> 00:38:52.200 align:start position:0% is moving from left to right writing 00:38:52.200 --> 00:38:53.690 align:start position:0% is moving from left to right writing writing<00:38:52.619> your<00:38:52.740> code<00:38:52.920> then<00:38:53.220> writing<00:38:53.579> your 00:38:53.690 --> 00:38:53.700 align:start position:0% writing your code then writing your 00:38:53.700 --> 00:38:55.730 align:start position:0% writing your code then writing your specs<00:38:54.119> and<00:38:54.240> tests<00:38:54.599> is<00:38:54.780> doing<00:38:55.020> it<00:38:55.260> on<00:38:55.500> the<00:38:55.619> right 00:38:55.730 --> 00:38:55.740 align:start position:0% specs and tests is doing it on the right 00:38:55.740 --> 00:38:58.069 align:start position:0% specs and tests is doing it on the right hand<00:38:55.920> side<00:38:56.160> so<00:38:56.640> the<00:38:57.300> more<00:38:57.420> that<00:38:57.660> you<00:38:57.839> can<00:38:57.960> do 00:38:58.069 --> 00:38:58.079 align:start position:0% hand side so the more that you can do 00:38:58.079 --> 00:39:00.230 align:start position:0% hand side so the more that you can do any<00:38:58.260> of<00:38:58.440> these<00:38:58.740> things<00:38:58.980> your<00:38:59.460> specs<00:38:59.880> formal 00:39:00.230 --> 00:39:00.240 align:start position:0% any of these things your specs formal 00:39:00.240 --> 00:39:02.150 align:start position:0% any of these things your specs formal verification<00:39:00.720> test<00:39:01.200> writing 00:39:02.150 --> 00:39:02.160 align:start position:0% verification test writing 00:39:02.160 --> 00:39:04.310 align:start position:0% verification test writing earlier<00:39:02.760> in<00:39:02.880> the<00:39:03.060> process<00:39:03.420> generally<00:39:04.079> the 00:39:04.310 --> 00:39:04.320 align:start position:0% earlier in the process generally the 00:39:04.320 --> 00:39:05.810 align:start position:0% earlier in the process generally the better<00:39:04.500> your<00:39:04.740> outcome<00:39:05.040> will<00:39:05.160> be<00:39:05.339> absolutely 00:39:05.810 --> 00:39:05.820 align:start position:0% better your outcome will be absolutely 00:39:05.820 --> 00:39:08.630 align:start position:0% better your outcome will be absolutely yeah<00:39:06.240> yeah<00:39:06.540> I<00:39:07.260> think<00:39:07.380> yeah<00:39:07.859> so<00:39:08.280> I<00:39:08.400> have<00:39:08.520> a 00:39:08.630 --> 00:39:08.640 align:start position:0% yeah yeah I think yeah so I have a 00:39:08.640 --> 00:39:10.130 align:start position:0% yeah yeah I think yeah so I have a question<00:39:08.760> for<00:39:09.000> you<00:39:09.119> I<00:39:09.240> think<00:39:09.359> Jonathan<00:39:09.900> and 00:39:10.130 --> 00:39:10.140 align:start position:0% question for you I think Jonathan and 00:39:10.140 --> 00:39:13.370 align:start position:0% question for you I think Jonathan and Nick<00:39:10.680> were<00:39:10.980> touching<00:39:11.460> upon<00:39:11.700> it<00:39:11.880> but<00:39:12.720> crypto<00:39:13.260> is 00:39:13.370 --> 00:39:13.380 align:start position:0% Nick were touching upon it but crypto is 00:39:13.380 --> 00:39:15.290 align:start position:0% Nick were touching upon it but crypto is a<00:39:13.619> very<00:39:13.740> narrative<00:39:14.280> driven<00:39:14.700> industry<00:39:15.119> in 00:39:15.290 --> 00:39:15.300 align:start position:0% a very narrative driven industry in 00:39:15.300 --> 00:39:18.349 align:start position:0% a very narrative driven industry in general<00:39:15.500> and<00:39:16.500> if<00:39:16.980> we<00:39:17.460> zoom<00:39:17.760> out<00:39:17.880> a<00:39:18.060> little<00:39:18.180> bit 00:39:18.349 --> 00:39:18.359 align:start position:0% general and if we zoom out a little bit 00:39:18.359 --> 00:39:20.990 align:start position:0% general and if we zoom out a little bit and<00:39:19.079> get<00:39:19.260> outside<00:39:19.500> of<00:39:19.859> the<00:39:20.099> security<00:39:20.520> Eco 00:39:20.990 --> 00:39:21.000 align:start position:0% and get outside of the security Eco 00:39:21.000 --> 00:39:23.990 align:start position:0% and get outside of the security Eco Chambers<00:39:21.480> what<00:39:22.200> are<00:39:22.380> some<00:39:22.560> narratives<00:39:23.099> that 00:39:23.990 --> 00:39:24.000 align:start position:0% Chambers what are some narratives that 00:39:24.000 --> 00:39:26.390 align:start position:0% Chambers what are some narratives that you<00:39:24.180> want<00:39:24.480> to<00:39:24.839> see<00:39:25.500> and<00:39:26.040> what<00:39:26.160> are<00:39:26.280> some 00:39:26.390 --> 00:39:26.400 align:start position:0% you want to see and what are some 00:39:26.400 --> 00:39:28.790 align:start position:0% you want to see and what are some narratives<00:39:26.820> you<00:39:27.060> want<00:39:27.240> to<00:39:27.420> correct<00:39:27.720> that<00:39:28.619> are 00:39:28.790 --> 00:39:28.800 align:start position:0% narratives you want to correct that are 00:39:28.800 --> 00:39:30.650 align:start position:0% narratives you want to correct that are floating<00:39:29.339> out<00:39:29.520> right<00:39:29.700> now<00:39:29.880> in<00:39:30.359> terms<00:39:30.540> of 00:39:30.650 --> 00:39:30.660 align:start position:0% floating out right now in terms of 00:39:30.660 --> 00:39:34.849 align:start position:0% floating out right now in terms of security<00:39:30.839> did<00:39:31.800> you<00:39:31.980> catch<00:39:32.220> uh<00:39:33.060> I'll<00:39:33.780> try<00:39:34.079> to<00:39:34.619> so 00:39:34.849 --> 00:39:34.859 align:start position:0% security did you catch uh I'll try to so 00:39:34.859 --> 00:39:36.290 align:start position:0% security did you catch uh I'll try to so you're<00:39:35.040> saying<00:39:35.220> you<00:39:35.460> said<00:39:35.579> it<00:39:35.700> was<00:39:35.820> this<00:39:36.060> is<00:39:36.180> a 00:39:36.290 --> 00:39:36.300 align:start position:0% you're saying you said it was this is a 00:39:36.300 --> 00:39:38.329 align:start position:0% you're saying you said it was this is a very<00:39:36.420> we're<00:39:36.599> in<00:39:36.900> an<00:39:37.079> early<00:39:37.440> stage<00:39:37.800> right<00:39:38.099> now 00:39:38.329 --> 00:39:38.339 align:start position:0% very we're in an early stage right now 00:39:38.339 --> 00:39:40.970 align:start position:0% very we're in an early stage right now we're<00:39:38.820> in<00:39:39.060> an<00:39:39.180> echo<00:39:39.480> chamber<00:39:39.900> of<00:39:40.680> security 00:39:40.970 --> 00:39:40.980 align:start position:0% we're in an echo chamber of security 00:39:40.980 --> 00:39:43.790 align:start position:0% we're in an echo chamber of security conversation<00:39:41.820> and<00:39:42.540> we<00:39:42.839> need<00:39:42.960> like 00:39:43.790 --> 00:39:43.800 align:start position:0% conversation and we need like 00:39:43.800 --> 00:39:45.770 align:start position:0% conversation and we need like I'm<00:39:44.339> struggling<00:39:44.700> yeah<00:39:45.119> I<00:39:45.359> was<00:39:45.480> going<00:39:45.599> to<00:39:45.660> say 00:39:45.770 --> 00:39:45.780 align:start position:0% I'm struggling yeah I was going to say 00:39:45.780 --> 00:39:47.990 align:start position:0% I'm struggling yeah I was going to say if<00:39:45.900> we<00:39:46.320> make<00:39:46.440> an<00:39:46.619> assumption<00:39:47.040> that<00:39:47.400> security 00:39:47.990 --> 00:39:48.000 align:start position:0% if we make an assumption that security 00:39:48.000 --> 00:39:51.290 align:start position:0% if we make an assumption that security Community<00:39:48.540> within<00:39:49.200> crypto<00:39:49.619> uh<00:39:50.400> is<00:39:50.700> is<00:39:50.880> on<00:39:51.180> the 00:39:51.290 --> 00:39:51.300 align:start position:0% Community within crypto uh is is on the 00:39:51.300 --> 00:39:53.630 align:start position:0% Community within crypto uh is is on the on<00:39:51.480> the<00:39:51.660> table<00:39:51.780> and<00:39:52.619> there<00:39:52.980> is<00:39:53.160> a<00:39:53.280> broader 00:39:53.630 --> 00:39:53.640 align:start position:0% on the table and there is a broader 00:39:53.640 --> 00:39:56.089 align:start position:0% on the table and there is a broader developer<00:39:54.300> Community<00:39:54.540> outside<00:39:54.900> as<00:39:55.320> well<00:39:55.500> uh 00:39:56.089 --> 00:39:56.099 align:start position:0% developer Community outside as well uh 00:39:56.099 --> 00:39:57.470 align:start position:0% developer Community outside as well uh who<00:39:56.280> are<00:39:56.400> all<00:39:56.460> developing<00:39:56.880> building<00:39:57.180> the 00:39:57.470 --> 00:39:57.480 align:start position:0% who are all developing building the 00:39:57.480 --> 00:40:00.470 align:start position:0% who are all developing building the tools<00:39:57.839> who<00:39:58.560> are<00:39:58.920> uh<00:39:59.579> susceptible<00:40:00.060> to<00:40:00.240> certain 00:40:00.470 --> 00:40:00.480 align:start position:0% tools who are uh susceptible to certain 00:40:00.480 --> 00:40:02.270 align:start position:0% tools who are uh susceptible to certain narratives<00:40:00.960> what<00:40:01.320> are<00:40:01.500> some<00:40:01.619> narratives<00:40:02.040> that 00:40:02.270 --> 00:40:02.280 align:start position:0% narratives what are some narratives that 00:40:02.280 --> 00:40:03.770 align:start position:0% narratives what are some narratives that are<00:40:02.400> floating<00:40:02.640> around<00:40:02.880> around<00:40:03.240> secured 00:40:03.770 --> 00:40:03.780 align:start position:0% are floating around around secured 00:40:03.780 --> 00:40:05.750 align:start position:0% are floating around around secured around<00:40:04.020> how<00:40:04.320> people<00:40:04.500> see<00:40:04.740> security<00:40:05.040> audits 00:40:05.750 --> 00:40:05.760 align:start position:0% around how people see security audits 00:40:05.760 --> 00:40:07.550 align:start position:0% around how people see security audits around<00:40:06.119> how<00:40:06.480> people<00:40:06.599> see<00:40:06.900> Security<00:40:07.140> in 00:40:07.550 --> 00:40:07.560 align:start position:0% around how people see Security in 00:40:07.560 --> 00:40:09.290 align:start position:0% around how people see Security in general<00:40:07.740> that<00:40:08.339> you<00:40:08.579> want<00:40:08.700> to<00:40:08.820> take<00:40:09.000> the<00:40:09.119> chance 00:40:09.290 --> 00:40:09.300 align:start position:0% general that you want to take the chance 00:40:09.300 --> 00:40:10.790 align:start position:0% general that you want to take the chance to<00:40:09.540> like<00:40:09.660> correct<00:40:10.079> if<00:40:10.320> you<00:40:10.440> see<00:40:10.560> anything 00:40:10.790 --> 00:40:10.800 align:start position:0% to like correct if you see anything 00:40:10.800 --> 00:40:13.630 align:start position:0% to like correct if you see anything wrong<00:40:11.040> what<00:40:11.820> does<00:40:12.240> some<00:40:12.780> ways 00:40:13.630 --> 00:40:13.640 align:start position:0% wrong what does some ways 00:40:13.640 --> 00:40:16.250 align:start position:0% wrong what does some ways all<00:40:14.640> right<00:40:14.700> so<00:40:15.060> I'll<00:40:15.300> just<00:40:15.480> repeat<00:40:15.599> it<00:40:15.900> for<00:40:16.079> for 00:40:16.250 --> 00:40:16.260 align:start position:0% all right so I'll just repeat it for for 00:40:16.260 --> 00:40:17.990 align:start position:0% all right so I'll just repeat it for for everyone<00:40:16.440> from<00:40:16.920> what<00:40:17.160> I<00:40:17.280> heard<00:40:17.460> and<00:40:17.640> correct 00:40:17.990 --> 00:40:18.000 align:start position:0% everyone from what I heard and correct 00:40:18.000 --> 00:40:19.609 align:start position:0% everyone from what I heard and correct me<00:40:18.119> if<00:40:18.300> I<00:40:18.540> mishad 00:40:19.609 --> 00:40:19.619 align:start position:0% me if I mishad 00:40:19.619 --> 00:40:22.849 align:start position:0% me if I mishad um<00:40:19.680> bad<00:40:20.280> narratives<00:40:20.820> in<00:40:21.480> our<00:40:21.599> industry<00:40:22.020> that 00:40:22.849 --> 00:40:22.859 align:start position:0% um bad narratives in our industry that 00:40:22.859 --> 00:40:26.150 align:start position:0% um bad narratives in our industry that should<00:40:23.099> be<00:40:23.280> corrected<00:40:24.200> hopefully<00:40:25.200> quickly 00:40:26.150 --> 00:40:26.160 align:start position:0% should be corrected hopefully quickly 00:40:26.160 --> 00:40:27.650 align:start position:0% should be corrected hopefully quickly and<00:40:26.400> early<00:40:26.760> on 00:40:27.650 --> 00:40:27.660 align:start position:0% and early on 00:40:27.660 --> 00:40:28.810 align:start position:0% and early on um<00:40:27.720> is<00:40:27.960> anybody 00:40:28.810 --> 00:40:28.820 align:start position:0% um is anybody 00:40:28.820 --> 00:40:32.410 align:start position:0% um is anybody got<00:40:29.820> done<00:40:30.000> what<00:40:30.480> are<00:40:30.599> you<00:40:30.660> angry<00:40:30.960> about 00:40:32.410 --> 00:40:32.420 align:start position:0% got done what are you angry about 00:40:32.420 --> 00:40:35.990 align:start position:0% got done what are you angry about see<00:40:33.420> I<00:40:33.660> know<00:40:33.780> I<00:40:34.079> know<00:40:34.200> how<00:40:34.320> to<00:40:34.560> like 00:40:35.990 --> 00:40:36.000 align:start position:0% see I know I know how to like 00:40:36.000 --> 00:40:40.490 align:start position:0% see I know I know how to like um<00:40:36.200> I'm<00:40:37.200> angry<00:40:37.500> about<00:40:37.800> a<00:40:38.339> a<00:40:39.000> lot<00:40:39.300> of<00:40:39.540> the<00:40:40.020> raises 00:40:40.490 --> 00:40:40.500 align:start position:0% um I'm angry about a a lot of the raises 00:40:40.500 --> 00:40:42.530 align:start position:0% um I'm angry about a a lot of the raises that<00:40:40.859> happen<00:40:41.040> in<00:40:41.400> the<00:40:41.520> security<00:40:41.760> industry 00:40:42.530 --> 00:40:42.540 align:start position:0% that happen in the security industry 00:40:42.540 --> 00:40:46.510 align:start position:0% that happen in the security industry recently<00:40:43.500> I<00:40:43.619> think<00:40:43.740> think<00:40:44.339> the<00:40:44.640> the<00:40:45.480> the<00:40:45.540> the 00:40:46.510 --> 00:40:46.520 align:start position:0% recently I think think the the the the 00:40:46.520 --> 00:40:49.450 align:start position:0% recently I think think the the the the money<00:40:47.520> and<00:40:48.180> capitalism<00:40:48.660> is<00:40:48.900> creating 00:40:49.450 --> 00:40:49.460 align:start position:0% money and capitalism is creating 00:40:49.460 --> 00:40:51.010 align:start position:0% money and capitalism is creating legitimacy 00:40:51.010 --> 00:40:51.020 align:start position:0% legitimacy 00:40:51.020 --> 00:40:54.109 align:start position:0% legitimacy for<00:40:52.020> for<00:40:52.680> people<00:40:53.160> that<00:40:53.579> have<00:40:53.820> not 00:40:54.109 --> 00:40:54.119 align:start position:0% for for people that have not 00:40:54.119 --> 00:40:56.150 align:start position:0% for for people that have not demonstrated<00:40:54.599> proficiency<00:40:55.260> so<00:40:55.680> this<00:40:55.920> is<00:40:55.980> a 00:40:56.150 --> 00:40:56.160 align:start position:0% demonstrated proficiency so this is a 00:40:56.160 --> 00:40:58.130 align:start position:0% demonstrated proficiency so this is a narrative<00:40:56.460> that<00:40:57.000> really<00:40:57.240> grinds<00:40:57.660> my<00:40:57.780> gears 00:40:58.130 --> 00:40:58.140 align:start position:0% narrative that really grinds my gears 00:40:58.140 --> 00:41:00.349 align:start position:0% narrative that really grinds my gears for<00:40:58.500> example 00:41:00.349 --> 00:41:00.359 align:start position:0% for example 00:41:00.359 --> 00:41:03.310 align:start position:0% for example um<00:41:00.480> wow<00:41:01.140> and<00:41:01.500> uh<00:41:01.859> yeah 00:41:03.310 --> 00:41:03.320 align:start position:0% um wow and uh yeah 00:41:03.320 --> 00:41:06.890 align:start position:0% um wow and uh yeah yeah<00:41:04.320> I'll<00:41:05.280> give<00:41:05.640> someone<00:41:05.880> else<00:41:06.060> I'll<00:41:06.540> sneak 00:41:06.890 --> 00:41:06.900 align:start position:0% yeah I'll give someone else I'll sneak 00:41:06.900 --> 00:41:08.270 align:start position:0% yeah I'll give someone else I'll sneak in<00:41:06.960> a<00:41:07.140> smart<00:41:07.260> contract<00:41:07.619> over<00:41:07.920> availability 00:41:08.270 --> 00:41:08.280 align:start position:0% in a smart contract over availability 00:41:08.280 --> 00:41:11.089 align:start position:0% in a smart contract over availability here<00:41:08.820> all<00:41:09.300> right<00:41:09.359> since<00:41:09.780> Gonzalo<00:41:10.680> started 00:41:11.089 --> 00:41:11.099 align:start position:0% here all right since Gonzalo started 00:41:11.099 --> 00:41:13.130 align:start position:0% here all right since Gonzalo started with<00:41:11.220> things<00:41:11.579> that<00:41:11.880> make<00:41:12.000> us<00:41:12.180> angry<00:41:12.540> I'll<00:41:12.780> do 00:41:13.130 --> 00:41:13.140 align:start position:0% with things that make us angry I'll do 00:41:13.140 --> 00:41:16.849 align:start position:0% with things that make us angry I'll do one<00:41:13.320> too<00:41:13.560> that<00:41:14.220> um<00:41:14.220> well<00:41:14.579> I<00:41:14.940> think<00:41:15.119> that<00:41:15.859> the 00:41:16.849 --> 00:41:16.859 align:start position:0% one too that um well I think that the 00:41:16.859 --> 00:41:21.650 align:start position:0% one too that um well I think that the our<00:41:17.760> desire<00:41:18.359> for<00:41:19.260> cost<00:41:20.099> efficiency 00:41:21.650 --> 00:41:21.660 align:start position:0% our desire for cost efficiency 00:41:21.660 --> 00:41:26.210 align:start position:0% our desire for cost efficiency and<00:41:22.380> time<00:41:22.680> efficiency<00:41:23.240> is<00:41:24.240> not<00:41:25.140> in<00:41:25.800> our<00:41:26.040> best 00:41:26.210 --> 00:41:26.220 align:start position:0% and time efficiency is not in our best 00:41:26.220 --> 00:41:29.270 align:start position:0% and time efficiency is not in our best interests<00:41:26.820> and<00:41:27.000> I<00:41:27.180> mean<00:41:27.359> gas<00:41:27.839> savings<00:41:28.380> and 00:41:29.270 --> 00:41:29.280 align:start position:0% interests and I mean gas savings and 00:41:29.280 --> 00:41:32.390 align:start position:0% interests and I mean gas savings and speed<00:41:30.000> of<00:41:30.540> transfer<00:41:31.140> from<00:41:31.500> a<00:41:31.619> layer<00:41:31.859> two<00:41:32.040> to<00:41:32.220> a 00:41:32.390 --> 00:41:32.400 align:start position:0% speed of transfer from a layer two to a 00:41:32.400 --> 00:41:34.370 align:start position:0% speed of transfer from a layer two to a layer<00:41:32.640> one<00:41:32.820> through<00:41:33.300> the<00:41:33.599> bridge<00:41:33.780> that<00:41:34.200> was 00:41:34.370 --> 00:41:34.380 align:start position:0% layer one through the bridge that was 00:41:34.380 --> 00:41:37.790 align:start position:0% layer one through the bridge that was just<00:41:34.619> developed<00:41:35.040> yesterday<00:41:35.660> like<00:41:36.660> and<00:41:37.619> our 00:41:37.790 --> 00:41:37.800 align:start position:0% just developed yesterday like and our 00:41:37.800 --> 00:41:40.250 align:start position:0% just developed yesterday like and our lack<00:41:38.040> of<00:41:38.220> acceptance<00:41:39.000> on<00:41:39.359> latency<00:41:39.900> on 00:41:40.250 --> 00:41:40.260 align:start position:0% lack of acceptance on latency on 00:41:40.260 --> 00:41:41.870 align:start position:0% lack of acceptance on latency on anything<00:41:40.500> so<00:41:40.920> that<00:41:41.040> we<00:41:41.280> could<00:41:41.400> do<00:41:41.579> more 00:41:41.870 --> 00:41:41.880 align:start position:0% anything so that we could do more 00:41:41.880 --> 00:41:44.390 align:start position:0% anything so that we could do more security<00:41:42.119> verification<00:41:42.960> so<00:41:43.680> I<00:41:43.980> think<00:41:44.099> these 00:41:44.390 --> 00:41:44.400 align:start position:0% security verification so I think these 00:41:44.400 --> 00:41:47.150 align:start position:0% security verification so I think these things<00:41:44.520> work<00:41:44.880> against<00:41:45.119> us<00:41:45.540> and<00:41:46.440> I<00:41:46.859> understand 00:41:47.150 --> 00:41:47.160 align:start position:0% things work against us and I understand 00:41:47.160 --> 00:41:50.390 align:start position:0% things work against us and I understand why<00:41:48.119> we're<00:41:48.300> doing<00:41:48.540> them<00:41:48.839> and<00:41:49.560> how<00:41:50.220> they're 00:41:50.390 --> 00:41:50.400 align:start position:0% why we're doing them and how they're 00:41:50.400 --> 00:41:52.790 align:start position:0% why we're doing them and how they're helping<00:41:50.820> initially<00:41:51.420> but<00:41:52.020> I<00:41:52.440> hope<00:41:52.619> the 00:41:52.790 --> 00:41:52.800 align:start position:0% helping initially but I hope the 00:41:52.800 --> 00:41:55.310 align:start position:0% helping initially but I hope the narrative<00:41:53.099> changes<00:41:53.760> so<00:41:54.180> that<00:41:54.420> we 00:41:55.310 --> 00:41:55.320 align:start position:0% narrative changes so that we 00:41:55.320 --> 00:41:57.589 align:start position:0% narrative changes so that we um<00:41:55.380> aren't<00:41:56.040> as<00:41:56.280> worried<00:41:56.640> about<00:41:56.760> gas<00:41:57.119> savings 00:41:57.589 --> 00:41:57.599 align:start position:0% um aren't as worried about gas savings 00:41:57.599 --> 00:41:59.450 align:start position:0% um aren't as worried about gas savings and<00:41:57.900> we're<00:41:58.079> more<00:41:58.260> and<00:41:58.500> we<00:41:58.680> aren't<00:41:58.859> as<00:41:59.099> worried 00:41:59.450 --> 00:41:59.460 align:start position:0% and we're more and we aren't as worried 00:41:59.460 --> 00:42:00.290 align:start position:0% and we're more and we aren't as worried about 00:42:00.290 --> 00:42:00.300 align:start position:0% about 00:42:00.300 --> 00:42:02.390 align:start position:0% about speed<00:42:01.079> and<00:42:01.440> we're<00:42:01.619> a<00:42:01.800> little<00:42:01.859> more<00:42:02.099> worried 00:42:02.390 --> 00:42:02.400 align:start position:0% speed and we're a little more worried 00:42:02.400 --> 00:42:04.790 align:start position:0% speed and we're a little more worried about<00:42:02.640> security<00:42:03.180> and<00:42:03.660> safety<00:42:04.079> for<00:42:04.320> the<00:42:04.440> users 00:42:04.790 --> 00:42:04.800 align:start position:0% about security and safety for the users 00:42:04.800 --> 00:42:09.410 align:start position:0% about security and safety for the users hello<00:42:05.579> everyone<00:42:06.140> my<00:42:07.140> question<00:42:07.260> is<00:42:07.619> is<00:42:08.099> uh<00:42:08.880> if 00:42:09.410 --> 00:42:09.420 align:start position:0% hello everyone my question is is uh if 00:42:09.420 --> 00:42:11.390 align:start position:0% hello everyone my question is is uh if auditing<00:42:09.900> is<00:42:10.079> good<00:42:10.260> enough 00:42:11.390 --> 00:42:11.400 align:start position:0% auditing is good enough 00:42:11.400 --> 00:42:14.089 align:start position:0% auditing is good enough or<00:42:12.000> would<00:42:12.240> you<00:42:12.420> consider<00:42:12.960> like<00:42:13.380> uh 00:42:14.089 --> 00:42:14.099 align:start position:0% or would you consider like uh 00:42:14.099 --> 00:42:16.910 align:start position:0% or would you consider like uh Alternatives<00:42:14.760> like<00:42:15.060> open<00:42:15.300> arena<00:42:15.839> or<00:42:16.380> Bounty 00:42:16.910 --> 00:42:16.920 align:start position:0% Alternatives like open arena or Bounty 00:42:16.920 --> 00:42:19.370 align:start position:0% Alternatives like open arena or Bounty bolts<00:42:17.339> like<00:42:17.520> hats<00:42:17.880> Finance<00:42:18.180> for<00:42:18.420> example 00:42:19.370 --> 00:42:19.380 align:start position:0% bolts like hats Finance for example 00:42:19.380 --> 00:42:23.050 align:start position:0% bolts like hats Finance for example or<00:42:19.920> maybe<00:42:20.099> deploying<00:42:20.940> two<00:42:21.300> medium<00:42:21.720> tier<00:42:22.040> uh 00:42:23.050 --> 00:42:23.060 align:start position:0% or maybe deploying two medium tier uh 00:42:23.060 --> 00:42:25.730 align:start position:0% or maybe deploying two medium tier uh Auditors<00:42:24.060> or<00:42:24.480> just<00:42:24.660> one<00:42:24.839> top<00:42:25.020> tier<00:42:25.320> auditor 00:42:25.730 --> 00:42:25.740 align:start position:0% Auditors or just one top tier auditor 00:42:25.740 --> 00:42:28.670 align:start position:0% Auditors or just one top tier auditor per<00:42:25.920> contract<00:42:26.540> considering<00:42:27.540> timeline 00:42:28.670 --> 00:42:28.680 align:start position:0% per contract considering timeline 00:42:28.680 --> 00:42:31.010 align:start position:0% per contract considering timeline so<00:42:29.220> I'm<00:42:29.400> not<00:42:29.640> sure<00:42:29.820> I<00:42:30.060> fully<00:42:30.420> understood<00:42:30.839> the 00:42:31.010 --> 00:42:31.020 align:start position:0% so I'm not sure I fully understood the 00:42:31.020 --> 00:42:32.810 align:start position:0% so I'm not sure I fully understood the question<00:42:31.200> but<00:42:31.500> I<00:42:31.619> think<00:42:31.800> it's 00:42:32.810 --> 00:42:32.820 align:start position:0% question but I think it's 00:42:32.820 --> 00:42:34.250 align:start position:0% question but I think it's please<00:42:33.240> correct<00:42:33.480> me<00:42:33.720> if<00:42:33.780> I'm<00:42:33.900> wrong<00:42:34.020> but<00:42:34.140> I 00:42:34.250 --> 00:42:34.260 align:start position:0% please correct me if I'm wrong but I 00:42:34.260 --> 00:42:35.990 align:start position:0% please correct me if I'm wrong but I think<00:42:34.380> you<00:42:34.500> asked<00:42:34.800> if<00:42:35.220> auditing<00:42:35.640> is<00:42:35.820> good 00:42:35.990 --> 00:42:36.000 align:start position:0% think you asked if auditing is good 00:42:36.000 --> 00:42:40.190 align:start position:0% think you asked if auditing is good enough<00:42:36.180> then<00:42:36.839> why<00:42:37.680> do<00:42:37.859> we<00:42:38.040> need<00:42:38.720> uh<00:42:39.720> the 00:42:40.190 --> 00:42:40.200 align:start position:0% enough then why do we need uh the 00:42:40.200 --> 00:42:42.650 align:start position:0% enough then why do we need uh the bounties<00:42:40.800> let's<00:42:41.700> make<00:42:41.880> it<00:42:42.000> more<00:42:42.119> General<00:42:42.300> I 00:42:42.650 --> 00:42:42.660 align:start position:0% bounties let's make it more General I 00:42:42.660 --> 00:42:44.810 align:start position:0% bounties let's make it more General I like<00:42:42.960> we<00:42:43.140> sort<00:42:43.500> of<00:42:43.619> I<00:42:43.859> I<00:42:43.859> think<00:42:44.280> I<00:42:44.520> think<00:42:44.640> I'll 00:42:44.810 --> 00:42:44.820 align:start position:0% like we sort of I I think I think I'll 00:42:44.820 --> 00:42:46.490 align:start position:0% like we sort of I I think I think I'll get<00:42:45.000> we<00:42:45.180> will<00:42:45.480> get<00:42:45.660> this<00:42:45.839> is<00:42:45.960> like<00:42:46.140> like<00:42:46.260> just 00:42:46.490 --> 00:42:46.500 align:start position:0% get we will get this is like like just 00:42:46.500 --> 00:42:48.470 align:start position:0% get we will get this is like like just generally<00:42:46.800> we<00:42:47.099> have<00:42:47.220> some<00:42:47.579> new<00:42:47.760> alternatives 00:42:48.470 --> 00:42:48.480 align:start position:0% generally we have some new alternatives 00:42:48.480 --> 00:42:51.230 align:start position:0% generally we have some new alternatives to<00:42:48.780> audits<00:42:49.320> that<00:42:49.500> have<00:42:49.680> emerged<00:42:50.520> giant 00:42:51.230 --> 00:42:51.240 align:start position:0% to audits that have emerged giant 00:42:51.240 --> 00:42:55.010 align:start position:0% to audits that have emerged giant bounties<00:42:52.220> uh<00:42:53.220> and<00:42:53.520> and<00:42:53.760> like<00:42:53.940> code<00:42:54.180> Arenas<00:42:54.660> and 00:42:55.010 --> 00:42:55.020 align:start position:0% bounties uh and and like code Arenas and 00:42:55.020 --> 00:42:58.010 align:start position:0% bounties uh and and like code Arenas and Sherlock<00:42:55.440> doing<00:42:55.920> these<00:42:56.520> uh<00:42:57.060> like<00:42:57.359> auditing 00:42:58.010 --> 00:42:58.020 align:start position:0% Sherlock doing these uh like auditing 00:42:58.020 --> 00:42:59.510 align:start position:0% Sherlock doing these uh like auditing competitions<00:42:58.619> that<00:42:58.920> are<00:42:59.040> a<00:42:59.160> little<00:42:59.280> bit<00:42:59.400> like 00:42:59.510 --> 00:42:59.520 align:start position:0% competitions that are a little bit like 00:42:59.520 --> 00:43:04.609 align:start position:0% competitions that are a little bit like a<00:42:59.760> Time<00:43:00.000> boxed<00:43:00.960> uh<00:43:01.619> Bounty<00:43:02.040> program<00:43:02.280> so<00:43:03.180> yeah 00:43:04.609 --> 00:43:04.619 align:start position:0% a Time boxed uh Bounty program so yeah 00:43:04.619 --> 00:43:06.770 align:start position:0% a Time boxed uh Bounty program so yeah um<00:43:04.740> how<00:43:05.280> does<00:43:05.460> that<00:43:05.640> uh<00:43:06.119> how<00:43:06.300> does<00:43:06.420> that<00:43:06.599> like 00:43:06.770 --> 00:43:06.780 align:start position:0% um how does that uh how does that like 00:43:06.780 --> 00:43:09.770 align:start position:0% um how does that uh how does that like substitute<00:43:07.619> or<00:43:07.800> compliment<00:43:08.280> auditing<00:43:09.060> I 00:43:09.770 --> 00:43:09.780 align:start position:0% substitute or compliment auditing I 00:43:09.780 --> 00:43:12.470 align:start position:0% substitute or compliment auditing I don't<00:43:10.200> know<00:43:10.319> this<00:43:10.819> I<00:43:11.819> don't<00:43:11.940> know<00:43:12.000> if<00:43:12.180> anyone's 00:43:12.470 --> 00:43:12.480 align:start position:0% don't know this I don't know if anyone's 00:43:12.480 --> 00:43:15.290 align:start position:0% don't know this I don't know if anyone's like<00:43:12.839> we<00:43:13.020> might<00:43:13.200> yeah<00:43:13.560> yeah<00:43:13.980> but<00:43:14.400> my<00:43:14.940> answer<00:43:15.060> is 00:43:15.290 --> 00:43:15.300 align:start position:0% like we might yeah yeah but my answer is 00:43:15.300 --> 00:43:17.210 align:start position:0% like we might yeah yeah but my answer is is<00:43:15.599> back<00:43:16.079> to<00:43:16.260> what<00:43:16.560> I<00:43:16.680> said<00:43:16.800> a<00:43:16.980> little<00:43:17.099> bit 00:43:17.210 --> 00:43:17.220 align:start position:0% is back to what I said a little bit 00:43:17.220 --> 00:43:19.609 align:start position:0% is back to what I said a little bit before<00:43:17.400> which<00:43:17.760> is<00:43:17.940> a<00:43:18.599> bounty<00:43:19.200> can<00:43:19.380> give<00:43:19.500> you 00:43:19.609 --> 00:43:19.619 align:start position:0% before which is a bounty can give you 00:43:19.619 --> 00:43:22.250 align:start position:0% before which is a bounty can give you that<00:43:19.980> this<00:43:20.220> bug<00:43:20.460> which<00:43:21.119> is<00:43:21.240> interesting<00:43:21.660> but 00:43:22.250 --> 00:43:22.260 align:start position:0% that this bug which is interesting but 00:43:22.260 --> 00:43:24.589 align:start position:0% that this bug which is interesting but it's<00:43:22.380> not<00:43:22.560> really<00:43:22.680> as<00:43:22.859> interesting<00:43:23.280> as<00:43:23.520> as<00:43:24.000> how 00:43:24.589 --> 00:43:24.599 align:start position:0% it's not really as interesting as as how 00:43:24.599 --> 00:43:26.809 align:start position:0% it's not really as interesting as as how you<00:43:24.839> are<00:43:24.900> working<00:43:25.140> with<00:43:25.319> this<00:43:25.619> is<00:43:25.740> a<00:43:25.980> this<00:43:26.520> is<00:43:26.640> a 00:43:26.809 --> 00:43:26.819 align:start position:0% you are working with this is a this is a 00:43:26.819 --> 00:43:29.270 align:start position:0% you are working with this is a this is a holistic<00:43:27.300> view<00:43:27.540> of<00:43:27.900> of<00:43:28.140> all<00:43:28.380> of<00:43:28.560> The<00:43:28.680> Code<00:43:28.800> by 00:43:29.270 --> 00:43:29.280 align:start position:0% holistic view of of all of The Code by 00:43:29.280 --> 00:43:31.370 align:start position:0% holistic view of of all of The Code by by<00:43:29.520> Engineers<00:43:30.000> who<00:43:30.359> are<00:43:30.540> deeply<00:43:31.200> and 00:43:31.370 --> 00:43:31.380 align:start position:0% by Engineers who are deeply and 00:43:31.380 --> 00:43:32.870 align:start position:0% by Engineers who are deeply and intimately<00:43:31.740> involved<00:43:32.099> with<00:43:32.280> the<00:43:32.400> code<00:43:32.520> to<00:43:32.700> the 00:43:32.870 --> 00:43:32.880 align:start position:0% intimately involved with the code to the 00:43:32.880 --> 00:43:34.309 align:start position:0% intimately involved with the code to the same<00:43:33.060> extent<00:43:33.300> that<00:43:33.480> that<00:43:33.720> your<00:43:33.960> internal 00:43:34.309 --> 00:43:34.319 align:start position:0% same extent that that your internal 00:43:34.319 --> 00:43:35.690 align:start position:0% same extent that that your internal people<00:43:34.500> are<00:43:34.740> but<00:43:34.920> they're<00:43:35.099> seeing<00:43:35.400> it<00:43:35.520> from 00:43:35.690 --> 00:43:35.700 align:start position:0% people are but they're seeing it from 00:43:35.700 --> 00:43:37.250 align:start position:0% people are but they're seeing it from through<00:43:35.940> a<00:43:36.119> different<00:43:36.240> lens<00:43:36.540> they're<00:43:37.020> seeing 00:43:37.250 --> 00:43:37.260 align:start position:0% through a different lens they're seeing 00:43:37.260 --> 00:43:39.170 align:start position:0% through a different lens they're seeing it<00:43:37.319> through<00:43:37.440> the<00:43:37.560> lens<00:43:37.740> of<00:43:38.160> people<00:43:38.579> who<00:43:38.940> have 00:43:39.170 --> 00:43:39.180 align:start position:0% it through the lens of people who have 00:43:39.180 --> 00:43:40.910 align:start position:0% it through the lens of people who have literally<00:43:39.839> watched<00:43:40.260> everything<00:43:40.440> that<00:43:40.800> could 00:43:40.910 --> 00:43:40.920 align:start position:0% literally watched everything that could 00:43:40.920 --> 00:43:42.829 align:start position:0% literally watched everything that could go<00:43:41.099> wrong<00:43:41.220> go<00:43:41.579> wrong<00:43:41.700> and<00:43:42.060> and<00:43:42.119> being<00:43:42.420> able<00:43:42.599> to 00:43:42.829 --> 00:43:42.839 align:start position:0% go wrong go wrong and and being able to 00:43:42.839 --> 00:43:43.569 align:start position:0% go wrong go wrong and and being able to see 00:43:43.569 --> 00:43:43.579 align:start position:0% see 00:43:43.579 --> 00:43:46.609 align:start position:0% see mistakes<00:43:44.579> in<00:43:45.599> everything<00:43:46.260> from 00:43:46.609 --> 00:43:46.619 align:start position:0% mistakes in everything from 00:43:46.619 --> 00:43:49.309 align:start position:0% mistakes in everything from documentation<00:43:47.220> to<00:43:47.520> to<00:43:47.760> just<00:43:48.420> your<00:43:48.780> overall 00:43:49.309 --> 00:43:49.319 align:start position:0% documentation to to just your overall 00:43:49.319 --> 00:43:52.190 align:start position:0% documentation to to just your overall maturity<00:43:49.920> it's<00:43:50.819> a<00:43:51.119> different<00:43:51.300> set<00:43:51.839> of<00:43:52.079> things 00:43:52.190 --> 00:43:52.200 align:start position:0% maturity it's a different set of things 00:43:52.200 --> 00:43:54.230 align:start position:0% maturity it's a different set of things if<00:43:52.500> you<00:43:52.619> want<00:43:52.740> if<00:43:53.040> you<00:43:53.160> want<00:43:53.280> to<00:43:53.400> find<00:43:53.700> specific 00:43:54.230 --> 00:43:54.240 align:start position:0% if you want if you want to find specific 00:43:54.240 --> 00:43:57.109 align:start position:0% if you want if you want to find specific bugs<00:43:54.720> and<00:43:54.839> fix<00:43:55.079> those<00:43:55.319> that's<00:43:56.220> great<00:43:56.460> there's 00:43:57.109 --> 00:43:57.119 align:start position:0% bugs and fix those that's great there's 00:43:57.119 --> 00:43:58.430 align:start position:0% bugs and fix those that's great there's other<00:43:57.359> things<00:43:57.599> that<00:43:57.780> are<00:43:57.900> that<00:43:58.079> are<00:43:58.260> outside 00:43:58.430 --> 00:43:58.440 align:start position:0% other things that are that are outside 00:43:58.440 --> 00:44:00.770 align:start position:0% other things that are that are outside the<00:43:58.859> the<00:43:59.160> general<00:43:59.460> scope<00:43:59.880> of<00:44:00.060> what<00:44:00.180> we<00:44:00.359> do<00:44:00.480> in<00:44:00.660> a 00:44:00.770 --> 00:44:00.780 align:start position:0% the the general scope of what we do in a 00:44:00.780 --> 00:44:03.230 align:start position:0% the the general scope of what we do in a Security<00:44:00.900> review<00:44:01.280> uh<00:44:02.280> I'm<00:44:02.700> not<00:44:02.819> suggesting 00:44:03.230 --> 00:44:03.240 align:start position:0% Security review uh I'm not suggesting 00:44:03.240 --> 00:44:05.690 align:start position:0% Security review uh I'm not suggesting that<00:44:03.480> that<00:44:03.900> audit<00:44:04.380> or<00:44:04.740> Security<00:44:05.040> review<00:44:05.400> is 00:44:05.690 --> 00:44:05.700 align:start position:0% that that audit or Security review is 00:44:05.700 --> 00:44:07.630 align:start position:0% that that audit or Security review is the<00:44:05.940> the<00:44:06.060> be-all<00:44:06.480> and<00:44:06.599> end-all<00:44:06.900> but<00:44:07.140> it's<00:44:07.260> also 00:44:07.630 --> 00:44:07.640 align:start position:0% the the be-all and end-all but it's also 00:44:07.640 --> 00:44:10.010 align:start position:0% the the be-all and end-all but it's also uh<00:44:08.640> different<00:44:09.119> from<00:44:09.420> a<00:44:09.540> lot<00:44:09.599> of<00:44:09.660> things<00:44:09.839> that 00:44:10.010 --> 00:44:10.020 align:start position:0% uh different from a lot of things that 00:44:10.020 --> 00:44:11.630 align:start position:0% uh different from a lot of things that I'm<00:44:10.140> seeing<00:44:10.440> out<00:44:10.560> there<00:44:10.740> and<00:44:10.980> as<00:44:11.400> far<00:44:11.520> as 00:44:11.630 --> 00:44:11.640 align:start position:0% I'm seeing out there and as far as 00:44:11.640 --> 00:44:13.790 align:start position:0% I'm seeing out there and as far as automation<00:44:12.000> goes<00:44:12.420> we<00:44:13.079> use<00:44:13.200> automation<00:44:13.560> to 00:44:13.790 --> 00:44:13.800 align:start position:0% automation goes we use automation to 00:44:13.800 --> 00:44:15.290 align:start position:0% automation goes we use automation to find<00:44:13.980> sort<00:44:14.339> of<00:44:14.400> low-hanging<00:44:14.880> fruit<00:44:15.000> or<00:44:15.180> to 00:44:15.290 --> 00:44:15.300 align:start position:0% find sort of low-hanging fruit or to 00:44:15.300 --> 00:44:16.670 align:start position:0% find sort of low-hanging fruit or to point<00:44:15.420> us<00:44:15.599> in<00:44:15.780> the<00:44:15.900> right<00:44:16.020> direction<00:44:16.200> so<00:44:16.500> that 00:44:16.670 --> 00:44:16.680 align:start position:0% point us in the right direction so that 00:44:16.680 --> 00:44:19.010 align:start position:0% point us in the right direction so that humans<00:44:17.040> can<00:44:17.280> look<00:44:17.400> at<00:44:17.579> it<00:44:17.700> and<00:44:18.180> make<00:44:18.420> educated 00:44:19.010 --> 00:44:19.020 align:start position:0% humans can look at it and make educated 00:44:19.020 --> 00:44:21.650 align:start position:0% humans can look at it and make educated decisions<00:44:19.500> about<00:44:19.819> what<00:44:20.819> we<00:44:21.000> think<00:44:21.240> and 00:44:21.650 --> 00:44:21.660 align:start position:0% decisions about what we think and 00:44:21.660 --> 00:44:23.510 align:start position:0% decisions about what we think and there's<00:44:21.839> a<00:44:22.020> lot<00:44:22.140> more<00:44:22.380> than<00:44:22.680> just<00:44:22.920> run<00:44:23.220> this 00:44:23.510 --> 00:44:23.520 align:start position:0% there's a lot more than just run this 00:44:23.520 --> 00:44:25.790 align:start position:0% there's a lot more than just run this tool<00:44:23.940> see<00:44:24.420> what<00:44:24.599> you<00:44:24.780> get<00:44:24.960> and<00:44:25.260> hand<00:44:25.440> over<00:44:25.560> the 00:44:25.790 --> 00:44:25.800 align:start position:0% tool see what you get and hand over the 00:44:25.800 --> 00:44:28.010 align:start position:0% tool see what you get and hand over the report<00:44:25.980> anyone<00:44:26.819> else<00:44:27.000> quickly<00:44:27.420> we're<00:44:27.599> running 00:44:28.010 --> 00:44:28.020 align:start position:0% report anyone else quickly we're running 00:44:28.020 --> 00:44:29.510 align:start position:0% report anyone else quickly we're running low<00:44:28.260> on<00:44:28.440> time 00:44:29.510 --> 00:44:29.520 align:start position:0% low on time 00:44:29.520 --> 00:44:32.510 align:start position:0% low on time um<00:44:29.640> sorry<00:44:30.260> sorry<00:44:31.260> sorry<00:44:31.440> no<00:44:31.980> no<00:44:32.099> that's<00:44:32.339> I 00:44:32.510 --> 00:44:32.520 align:start position:0% um sorry sorry sorry no no that's I 00:44:32.520 --> 00:44:33.950 align:start position:0% um sorry sorry sorry no no that's I meant<00:44:32.700> on<00:44:32.880> the<00:44:33.000> stage<00:44:33.240> like<00:44:33.480> if<00:44:33.660> anybody 00:44:33.950 --> 00:44:33.960 align:start position:0% meant on the stage like if anybody 00:44:33.960 --> 00:44:35.630 align:start position:0% meant on the stage like if anybody wanted<00:44:34.200> to<00:44:34.440> all<00:44:34.800> right<00:44:34.920> I'm<00:44:35.040> gonna<00:44:35.160> be<00:44:35.339> selfish 00:44:35.630 --> 00:44:35.640 align:start position:0% wanted to all right I'm gonna be selfish 00:44:35.640 --> 00:44:37.550 align:start position:0% wanted to all right I'm gonna be selfish too<00:44:35.880> there's<00:44:36.180> something<00:44:36.420> in<00:44:37.140> the<00:44:37.260> time<00:44:37.380> we 00:44:37.550 --> 00:44:37.560 align:start position:0% too there's something in the time we 00:44:37.560 --> 00:44:39.290 align:start position:0% too there's something in the time we have<00:44:37.680> I<00:44:37.920> really<00:44:38.040> want<00:44:38.280> to<00:44:38.400> plant<00:44:38.520> this<00:44:38.819> idea<00:44:39.060> as 00:44:39.290 --> 00:44:39.300 align:start position:0% have I really want to plant this idea as 00:44:39.300 --> 00:44:41.630 align:start position:0% have I really want to plant this idea as much<00:44:39.420> as<00:44:39.540> possible<00:44:39.900> is<00:44:40.140> that<00:44:40.440> it's<00:44:41.160> not<00:44:41.400> the 00:44:41.630 --> 00:44:41.640 align:start position:0% much as possible is that it's not the 00:44:41.640 --> 00:44:43.670 align:start position:0% much as possible is that it's not the auditor's<00:44:42.180> job<00:44:42.420> they're<00:44:42.839> not<00:44:43.020> selling<00:44:43.560> you 00:44:43.670 --> 00:44:43.680 align:start position:0% auditor's job they're not selling you 00:44:43.680 --> 00:44:46.910 align:start position:0% auditor's job they're not selling you Security<00:44:44.040> in<00:44:45.000> my<00:44:45.119> opinion<00:44:45.900> they're<00:44:46.500> selling 00:44:46.910 --> 00:44:46.920 align:start position:0% Security in my opinion they're selling 00:44:46.920 --> 00:44:49.609 align:start position:0% Security in my opinion they're selling you<00:44:47.040> like<00:44:47.339> insight<00:44:48.000> into<00:44:48.540> your<00:44:49.020> ability<00:44:49.319> to 00:44:49.609 --> 00:44:49.619 align:start position:0% you like insight into your ability to 00:44:49.619 --> 00:44:51.109 align:start position:0% you like insight into your ability to write<00:44:49.800> secure<00:44:50.160> code 00:44:51.109 --> 00:44:51.119 align:start position:0% write secure code 00:44:51.119 --> 00:44:54.349 align:start position:0% write secure code so<00:44:51.960> you<00:44:52.859> need<00:44:52.920> to<00:44:53.040> take<00:44:53.280> responsibility<00:44:54.000> for 00:44:54.349 --> 00:44:54.359 align:start position:0% so you need to take responsibility for 00:44:54.359 --> 00:44:58.370 align:start position:0% so you need to take responsibility for writing<00:44:54.720> secure<00:44:55.020> code<00:44:55.520> uh<00:44:56.520> and<00:44:56.880> not<00:44:57.240> act<00:44:58.020> as<00:44:58.200> if 00:44:58.370 --> 00:44:58.380 align:start position:0% writing secure code uh and not act as if 00:44:58.380 --> 00:45:00.109 align:start position:0% writing secure code uh and not act as if like<00:44:58.619> you<00:44:58.859> just<00:44:58.980> get<00:44:59.160> to<00:44:59.280> write<00:44:59.460> code<00:44:59.819> that 00:45:00.109 --> 00:45:00.119 align:start position:0% like you just get to write code that 00:45:00.119 --> 00:45:02.150 align:start position:0% like you just get to write code that does<00:45:00.240> cool<00:45:00.540> stuff<00:45:00.960> and<00:45:01.380> then<00:45:01.500> give<00:45:01.740> it<00:45:01.859> to<00:45:01.980> the 00:45:02.150 --> 00:45:02.160 align:start position:0% does cool stuff and then give it to the 00:45:02.160 --> 00:45:03.770 align:start position:0% does cool stuff and then give it to the auditor<00:45:02.520> and<00:45:02.760> they<00:45:02.880> will<00:45:03.060> make<00:45:03.240> it<00:45:03.359> safe<00:45:03.540> for 00:45:03.770 --> 00:45:03.780 align:start position:0% auditor and they will make it safe for 00:45:03.780 --> 00:45:06.770 align:start position:0% auditor and they will make it safe for you<00:45:04.319> so<00:45:04.920> you<00:45:05.400> need<00:45:05.520> to<00:45:05.640> focus<00:45:05.880> on<00:45:06.180> being<00:45:06.480> able 00:45:06.770 --> 00:45:06.780 align:start position:0% you so you need to focus on being able 00:45:06.780 --> 00:45:08.450 align:start position:0% you so you need to focus on being able to<00:45:06.960> write<00:45:07.079> secure<00:45:07.440> code<00:45:07.560> whatever<00:45:07.859> process 00:45:08.450 --> 00:45:08.460 align:start position:0% to write secure code whatever process 00:45:08.460 --> 00:45:10.190 align:start position:0% to write secure code whatever process you<00:45:08.760> think<00:45:08.940> that<00:45:09.119> might<00:45:09.300> need<00:45:09.420> whatever<00:45:09.660> tool 00:45:10.190 --> 00:45:10.200 align:start position:0% you think that might need whatever tool 00:45:10.200 --> 00:45:12.230 align:start position:0% you think that might need whatever tool you<00:45:10.319> think<00:45:10.500> that<00:45:10.680> requires<00:45:11.220> and<00:45:11.940> then<00:45:12.000> you 00:45:12.230 --> 00:45:12.240 align:start position:0% you think that requires and then you 00:45:12.240 --> 00:45:14.089 align:start position:0% you think that requires and then you give<00:45:12.420> the<00:45:12.599> other<00:45:12.720> your<00:45:12.960> code<00:45:13.260> so<00:45:13.619> that<00:45:13.740> you<00:45:13.980> can 00:45:14.089 --> 00:45:14.099 align:start position:0% give the other your code so that you can 00:45:14.099 --> 00:45:16.730 align:start position:0% give the other your code so that you can understand<00:45:14.540> how<00:45:15.540> close<00:45:15.720> you<00:45:15.960> are<00:45:16.140> to<00:45:16.500> being 00:45:16.730 --> 00:45:16.740 align:start position:0% understand how close you are to being 00:45:16.740 --> 00:45:19.930 align:start position:0% understand how close you are to being able<00:45:17.040> to<00:45:17.280> write<00:45:17.400> secure<00:45:17.819> code<00:45:18.060> amen 00:45:19.930 --> 00:45:19.940 align:start position:0% able to write secure code amen 00:45:19.940 --> 00:45:22.910 align:start position:0% able to write secure code amen it<00:45:20.940> took<00:45:21.180> me<00:45:21.300> a<00:45:21.480> long<00:45:21.540> time<00:45:21.720> to<00:45:21.960> get<00:45:22.079> there<00:45:22.260> so 00:45:22.910 --> 00:45:22.920 align:start position:0% it took me a long time to get there so 00:45:22.920 --> 00:45:25.190 align:start position:0% it took me a long time to get there so it's<00:45:23.099> a<00:45:23.280> bit<00:45:23.400> of<00:45:23.460> an<00:45:23.579> epiphany<00:45:24.060> and<00:45:24.839> I'm<00:45:24.960> trying 00:45:25.190 --> 00:45:25.200 align:start position:0% it's a bit of an epiphany and I'm trying 00:45:25.200 --> 00:45:27.950 align:start position:0% it's a bit of an epiphany and I'm trying to<00:45:25.520> unfortunately<00:45:26.520> we<00:45:26.880> see<00:45:27.060> what<00:45:27.480> John<00:45:27.720> was 00:45:27.950 --> 00:45:27.960 align:start position:0% to unfortunately we see what John was 00:45:27.960 --> 00:45:32.329 align:start position:0% to unfortunately we see what John was describing<00:45:28.500> way<00:45:29.400> too<00:45:30.000> often<00:45:30.560> and<00:45:31.560> yeah<00:45:32.040> it'd 00:45:32.329 --> 00:45:32.339 align:start position:0% describing way too often and yeah it'd 00:45:32.339 --> 00:45:34.069 align:start position:0% describing way too often and yeah it'd be<00:45:32.400> great<00:45:32.579> if<00:45:32.819> we<00:45:33.000> can<00:45:33.180> all<00:45:33.480> collectively 00:45:34.069 --> 00:45:34.079 align:start position:0% be great if we can all collectively 00:45:34.079 --> 00:45:35.329 align:start position:0% be great if we can all collectively shift 00:45:35.329 --> 00:45:35.339 align:start position:0% shift 00:45:35.339 --> 00:45:37.010 align:start position:0% shift um<00:45:35.400> towards<00:45:35.880> a<00:45:36.060> different 00:45:37.010 --> 00:45:37.020 align:start position:0% um towards a different 00:45:37.020 --> 00:45:39.890 align:start position:0% um towards a different um<00:45:37.140> yeah<00:45:37.440> definition<00:45:37.980> of<00:45:38.520> what<00:45:39.000> our<00:45:39.180> work<00:45:39.660> here 00:45:39.890 --> 00:45:39.900 align:start position:0% um yeah definition of what our work here 00:45:39.900 --> 00:45:41.150 align:start position:0% um yeah definition of what our work here means 00:45:41.150 --> 00:45:41.160 align:start position:0% means 00:45:41.160 --> 00:45:43.130 align:start position:0% means um<00:45:41.280> yeah<00:45:41.460> thank<00:45:41.700> you<00:45:41.880> thank<00:45:42.119> you<00:45:42.300> okay<00:45:42.780> there 00:45:43.130 --> 00:45:43.140 align:start position:0% um yeah thank you thank you okay there 00:45:43.140 --> 00:45:45.230 align:start position:0% um yeah thank you thank you okay there was<00:45:43.260> another<00:45:43.380> question<00:45:43.800> so<00:45:44.099> let's<00:45:44.339> have<00:45:44.520> it<00:45:44.700> I 00:45:45.230 --> 00:45:45.240 align:start position:0% was another question so let's have it I 00:45:45.240 --> 00:45:48.349 align:start position:0% was another question so let's have it I think<00:45:45.480> so<00:45:46.140> um<00:45:46.200> Foundry<00:45:46.920> when<00:45:47.280> Foundry<00:45:47.760> first 00:45:48.349 --> 00:45:48.359 align:start position:0% think so um Foundry when Foundry first 00:45:48.359 --> 00:45:50.690 align:start position:0% think so um Foundry when Foundry first came<00:45:48.660> out<00:45:48.839> uh<00:45:49.440> I<00:45:49.619> was<00:45:49.740> surprised<00:45:50.160> by<00:45:50.400> the<00:45:50.640> fact 00:45:50.690 --> 00:45:50.700 align:start position:0% came out uh I was surprised by the fact 00:45:50.700 --> 00:45:52.910 align:start position:0% came out uh I was surprised by the fact that<00:45:50.880> it<00:45:51.000> included<00:45:51.359> fuzzing<00:45:51.960> so<00:45:52.500> my<00:45:52.740> question 00:45:52.910 --> 00:45:52.920 align:start position:0% that it included fuzzing so my question 00:45:52.920 --> 00:45:55.970 align:start position:0% that it included fuzzing so my question is<00:45:53.520> when<00:45:54.119> does<00:45:54.300> fuzzing<00:45:54.839> make<00:45:55.140> sense<00:45:55.440> on<00:45:55.800> these 00:45:55.970 --> 00:45:55.980 align:start position:0% is when does fuzzing make sense on these 00:45:55.980 --> 00:45:57.710 align:start position:0% is when does fuzzing make sense on these code<00:45:56.160> bases<00:45:56.640> which<00:45:56.880> are<00:45:57.060> generally<00:45:57.420> open 00:45:57.710 --> 00:45:57.720 align:start position:0% code bases which are generally open 00:45:57.720 --> 00:46:01.130 align:start position:0% code bases which are generally open source<00:45:58.380> and<00:45:59.040> small<00:45:59.480> and<00:46:00.480> how<00:46:00.720> do<00:46:00.780> you<00:46:00.900> approach 00:46:01.130 --> 00:46:01.140 align:start position:0% source and small and how do you approach 00:46:01.140 --> 00:46:04.970 align:start position:0% source and small and how do you approach fuzzing<00:46:01.740> in<00:46:02.400> your<00:46:02.579> use<00:46:02.819> for<00:46:03.660> auditing 00:46:04.970 --> 00:46:04.980 align:start position:0% fuzzing in your use for auditing 00:46:04.980 --> 00:46:06.890 align:start position:0% fuzzing in your use for auditing fuzzing<00:46:05.760> makes<00:46:05.940> a<00:46:06.119> lot<00:46:06.240> of<00:46:06.359> sense<00:46:06.420> all<00:46:06.660> the 00:46:06.890 --> 00:46:06.900 align:start position:0% fuzzing makes a lot of sense all the 00:46:06.900 --> 00:46:10.010 align:start position:0% fuzzing makes a lot of sense all the time<00:46:07.560> it's<00:46:08.160> we're<00:46:08.880> going<00:46:09.180> to<00:46:09.300> like<00:46:09.599> the<00:46:09.720> shift 00:46:10.010 --> 00:46:10.020 align:start position:0% time it's we're going to like the shift 00:46:10.020 --> 00:46:12.530 align:start position:0% time it's we're going to like the shift left<00:46:10.200> the<00:46:10.980> shift<00:46:11.220> security<00:46:11.460> left<00:46:11.819> narrative 00:46:12.530 --> 00:46:12.540 align:start position:0% left the shift security left narrative 00:46:12.540 --> 00:46:14.390 align:start position:0% left the shift security left narrative and<00:46:12.780> all<00:46:12.960> that<00:46:13.140> like<00:46:13.319> you<00:46:13.500> should<00:46:13.859> use<00:46:14.040> all<00:46:14.220> the 00:46:14.390 --> 00:46:14.400 align:start position:0% and all that like you should use all the 00:46:14.400 --> 00:46:17.150 align:start position:0% and all that like you should use all the tools<00:46:14.700> literally<00:46:15.420> uh<00:46:16.380> you<00:46:16.560> you<00:46:16.680> should<00:46:16.920> write 00:46:17.150 --> 00:46:17.160 align:start position:0% tools literally uh you you should write 00:46:17.160 --> 00:46:19.190 align:start position:0% tools literally uh you you should write specs<00:46:17.700> if<00:46:17.940> you<00:46:18.000> have<00:46:18.119> specs<00:46:18.599> fuzzing<00:46:19.020> will 00:46:19.190 --> 00:46:19.200 align:start position:0% specs if you have specs fuzzing will 00:46:19.200 --> 00:46:21.230 align:start position:0% specs if you have specs fuzzing will work<00:46:19.440> better<00:46:19.680> right 00:46:21.230 --> 00:46:21.240 align:start position:0% work better right 00:46:21.240 --> 00:46:24.230 align:start position:0% work better right um<00:46:21.359> so<00:46:21.780> I<00:46:22.200> I<00:46:22.500> don't<00:46:22.680> yeah<00:46:23.160> you<00:46:23.760> should<00:46:23.940> just<00:46:24.060> do 00:46:24.230 --> 00:46:24.240 align:start position:0% um so I I don't yeah you should just do 00:46:24.240 --> 00:46:26.329 align:start position:0% um so I I don't yeah you should just do it<00:46:24.420> all<00:46:24.960> the<00:46:25.079> time<00:46:25.200> use<00:46:25.440> Foundry<00:46:25.859> and<00:46:26.040> use<00:46:26.160> all 00:46:26.329 --> 00:46:26.339 align:start position:0% it all the time use Foundry and use all 00:46:26.339 --> 00:46:28.670 align:start position:0% it all the time use Foundry and use all the<00:46:26.460> other<00:46:26.579> tools<00:46:26.940> use<00:46:27.240> a<00:46:27.420> kidney<00:46:27.720> use<00:46:28.020> Harvey 00:46:28.670 --> 00:46:28.680 align:start position:0% the other tools use a kidney use Harvey 00:46:28.680 --> 00:46:30.950 align:start position:0% the other tools use a kidney use Harvey by<00:46:29.339> the<00:46:29.520> way<00:46:29.579> I<00:46:30.000> forgot<00:46:30.359> to<00:46:30.480> say<00:46:30.599> I've<00:46:30.780> been 00:46:30.950 --> 00:46:30.960 align:start position:0% by the way I forgot to say I've been 00:46:30.960 --> 00:46:32.390 align:start position:0% by the way I forgot to say I've been announcing<00:46:31.500> this<00:46:31.619> the<00:46:31.740> entire<00:46:31.920> week<00:46:32.099> but<00:46:32.220> this 00:46:32.390 --> 00:46:32.400 align:start position:0% announcing this the entire week but this 00:46:32.400 --> 00:46:34.670 align:start position:0% announcing this the entire week but this is<00:46:32.460> the<00:46:32.640> panel<00:46:32.940> we<00:46:33.540> at<00:46:33.780> diligence<00:46:34.200> will<00:46:34.500> be 00:46:34.670 --> 00:46:34.680 align:start position:0% is the panel we at diligence will be 00:46:34.680 --> 00:46:36.290 align:start position:0% is the panel we at diligence will be open<00:46:34.800> sourcing<00:46:35.160> all<00:46:35.400> our<00:46:35.579> tools<00:46:35.940> just<00:46:36.119> like 00:46:36.290 --> 00:46:36.300 align:start position:0% open sourcing all our tools just like 00:46:36.300 --> 00:46:38.270 align:start position:0% open sourcing all our tools just like trailer<00:46:36.540> bits<00:46:37.020> we<00:46:37.319> are<00:46:37.500> a<00:46:37.740> bit<00:46:37.859> behind 00:46:38.270 --> 00:46:38.280 align:start position:0% trailer bits we are a bit behind 00:46:38.280 --> 00:46:40.309 align:start position:0% trailer bits we are a bit behind schedule<00:46:38.520> but<00:46:39.000> at<00:46:39.359> least<00:46:39.480> very<00:46:39.900> late<00:46:40.140> than 00:46:40.309 --> 00:46:40.319 align:start position:0% schedule but at least very late than 00:46:40.319 --> 00:46:43.370 align:start position:0% schedule but at least very late than never<00:46:40.500> so<00:46:40.800> even<00:46:41.099> Harvey<00:46:41.579> yeah<00:46:42.359> yeah<00:46:42.540> yeah<00:46:42.599> all 00:46:43.370 --> 00:46:43.380 align:start position:0% never so even Harvey yeah yeah yeah all 00:46:43.380 --> 00:46:46.130 align:start position:0% never so even Harvey yeah yeah yeah all the<00:46:43.500> code<00:46:43.680> bases<00:46:44.160> so<00:46:44.400> yeah 00:46:46.130 --> 00:46:46.140 align:start position:0% the code bases so yeah 00:46:46.140 --> 00:46:50.809 align:start position:0% the code bases so yeah foreign 00:46:50.809 --> 00:46:50.819 align:start position:0% 00:46:50.819 --> 00:46:54.230 align:start position:0% did<00:46:51.420> you<00:46:51.540> uh<00:46:52.260> I<00:46:52.560> just<00:46:52.680> well<00:46:52.859> yeah<00:46:53.160> I<00:46:53.339> guess<00:46:53.460> I<00:46:53.760> to 00:46:54.230 --> 00:46:54.240 align:start position:0% did you uh I just well yeah I guess I to 00:46:54.240 --> 00:46:57.170 align:start position:0% did you uh I just well yeah I guess I to add<00:46:54.780> to<00:46:55.140> what<00:46:55.260> Gonzalo<00:46:55.800> said<00:46:55.920> I<00:46:56.099> think<00:46:56.280> uh 00:46:57.170 --> 00:46:57.180 align:start position:0% add to what Gonzalo said I think uh 00:46:57.180 --> 00:46:59.630 align:start position:0% add to what Gonzalo said I think uh using<00:46:57.599> tools<00:46:57.900> is<00:46:58.020> actually<00:46:58.319> good<00:46:58.619> so<00:46:59.099> fuzzing 00:46:59.630 --> 00:46:59.640 align:start position:0% using tools is actually good so fuzzing 00:46:59.640 --> 00:47:01.970 align:start position:0% using tools is actually good so fuzzing makes<00:46:59.940> sense<00:47:00.180> to<00:47:00.359> me<00:47:00.480> I<00:47:00.780> mean<00:47:00.900> you<00:47:01.440> know<00:47:01.500> again 00:47:01.970 --> 00:47:01.980 align:start position:0% makes sense to me I mean you know again 00:47:01.980 --> 00:47:04.309 align:start position:0% makes sense to me I mean you know again it's<00:47:02.460> not<00:47:02.640> a<00:47:02.819> guarantee<00:47:03.180> but<00:47:03.599> you<00:47:03.900> know<00:47:03.960> I 00:47:04.309 --> 00:47:04.319 align:start position:0% it's not a guarantee but you know I 00:47:04.319 --> 00:47:06.890 align:start position:0% it's not a guarantee but you know I think<00:47:04.680> uh<00:47:05.640> it's<00:47:05.940> just<00:47:06.119> like<00:47:06.300> good<00:47:06.540> software 00:47:06.890 --> 00:47:06.900 align:start position:0% think uh it's just like good software 00:47:06.900 --> 00:47:08.750 align:start position:0% think uh it's just like good software engineering<00:47:07.319> right<00:47:07.500> like<00:47:07.800> you<00:47:08.099> write<00:47:08.520> code 00:47:08.750 --> 00:47:08.760 align:start position:0% engineering right like you write code 00:47:08.760 --> 00:47:11.089 align:start position:0% engineering right like you write code and<00:47:09.060> you<00:47:09.300> want<00:47:09.420> to<00:47:09.540> write<00:47:09.660> tests<00:47:10.140> and<00:47:10.560> you<00:47:10.980> want 00:47:11.089 --> 00:47:11.099 align:start position:0% and you want to write tests and you want 00:47:11.099 --> 00:47:12.770 align:start position:0% and you want to write tests and you want to<00:47:11.220> do<00:47:11.339> fuzzing<00:47:11.880> and<00:47:12.119> you<00:47:12.300> want<00:47:12.420> to<00:47:12.599> write 00:47:12.770 --> 00:47:12.780 align:start position:0% to do fuzzing and you want to write 00:47:12.780 --> 00:47:14.750 align:start position:0% to do fuzzing and you want to write specs<00:47:13.380> and<00:47:13.500> these<00:47:14.099> are<00:47:14.160> all<00:47:14.280> good<00:47:14.460> software 00:47:14.750 --> 00:47:14.760 align:start position:0% specs and these are all good software 00:47:14.760 --> 00:47:16.250 align:start position:0% specs and these are all good software engineering<00:47:15.119> practices<00:47:15.480> and<00:47:15.839> I<00:47:15.960> think<00:47:16.079> they 00:47:16.250 --> 00:47:16.260 align:start position:0% engineering practices and I think they 00:47:16.260 --> 00:47:18.829 align:start position:0% engineering practices and I think they also<00:47:16.560> just<00:47:16.800> are<00:47:17.640> they<00:47:17.940> carry<00:47:18.240> to<00:47:18.359> this<00:47:18.480> domain 00:47:18.829 --> 00:47:18.839 align:start position:0% also just are they carry to this domain 00:47:18.839 --> 00:47:21.710 align:start position:0% also just are they carry to this domain as<00:47:19.020> well<00:47:19.140> so<00:47:19.560> it<00:47:19.920> makes<00:47:20.280> sense 00:47:21.710 --> 00:47:21.720 align:start position:0% as well so it makes sense 00:47:21.720 --> 00:47:23.210 align:start position:0% as well so it makes sense um the<00:47:21.960> one<00:47:22.079> the<00:47:22.200> one<00:47:22.380> comment<00:47:22.680> about<00:47:22.800> that 00:47:23.210 --> 00:47:23.220 align:start position:0% um the one the one comment about that 00:47:23.220 --> 00:47:25.730 align:start position:0% um the one the one comment about that you<00:47:23.520> just<00:47:23.640> made<00:47:23.760> well<00:47:24.000> both<00:47:24.240> of<00:47:24.359> you<00:47:24.480> like<00:47:24.839> uh 00:47:25.730 --> 00:47:25.740 align:start position:0% you just made well both of you like uh 00:47:25.740 --> 00:47:27.890 align:start position:0% you just made well both of you like uh that<00:47:26.280> the<00:47:26.579> Declaration<00:47:27.000> of<00:47:27.240> things<00:47:27.480> the 00:47:27.890 --> 00:47:27.900 align:start position:0% that the Declaration of things the 00:47:27.900 --> 00:47:30.530 align:start position:0% that the Declaration of things the ability<00:47:28.319> to<00:47:28.560> set<00:47:28.980> forth<00:47:29.280> the<00:47:29.400> spec<00:47:29.579> uh<00:47:30.359> and 00:47:30.530 --> 00:47:30.540 align:start position:0% ability to set forth the spec uh and 00:47:30.540 --> 00:47:32.030 align:start position:0% ability to set forth the spec uh and then<00:47:30.599> and<00:47:30.720> then<00:47:30.900> fuzz<00:47:31.319> around<00:47:31.619> that<00:47:31.859> that's 00:47:32.030 --> 00:47:32.040 align:start position:0% then and then fuzz around that that's 00:47:32.040 --> 00:47:34.609 align:start position:0% then and then fuzz around that that's really<00:47:32.280> important<00:47:32.700> that<00:47:33.540> first<00:47:33.839> part<00:47:34.079> is<00:47:34.380> what 00:47:34.609 --> 00:47:34.619 align:start position:0% really important that first part is what 00:47:34.619 --> 00:47:36.530 align:start position:0% really important that first part is what Jocelyn<00:47:35.099> and<00:47:35.339> and<00:47:35.579> Gustavo<00:47:36.119> are<00:47:36.300> going<00:47:36.420> to<00:47:36.480> be 00:47:36.530 --> 00:47:36.540 align:start position:0% Jocelyn and and Gustavo are going to be 00:47:36.540 --> 00:47:38.270 align:start position:0% Jocelyn and and Gustavo are going to be doing<00:47:36.660> tomorrow<00:47:37.020> there's<00:47:37.680> going<00:47:37.859> to<00:47:37.920> be<00:47:38.040> a 00:47:38.270 --> 00:47:38.280 align:start position:0% doing tomorrow there's going to be a 00:47:38.280 --> 00:47:40.550 align:start position:0% doing tomorrow there's going to be a two-hour<00:47:38.579> workshop<00:47:39.119> on<00:47:39.480> how<00:47:39.960> do<00:47:40.079> you<00:47:40.200> declare 00:47:40.550 --> 00:47:40.560 align:start position:0% two-hour workshop on how do you declare 00:47:40.560 --> 00:47:42.290 align:start position:0% two-hour workshop on how do you declare these<00:47:40.920> things<00:47:41.040> how<00:47:41.400> do<00:47:41.520> you<00:47:41.640> actually<00:47:41.760> set<00:47:42.119> out 00:47:42.290 --> 00:47:42.300 align:start position:0% these things how do you actually set out 00:47:42.300 --> 00:47:45.170 align:start position:0% these things how do you actually set out and<00:47:42.900> and<00:47:43.200> describe<00:47:43.980> in<00:47:44.099> variants<00:47:44.520> and<00:47:44.760> how<00:47:45.000> how 00:47:45.170 --> 00:47:45.180 align:start position:0% and and describe in variants and how how 00:47:45.180 --> 00:47:46.970 align:start position:0% and and describe in variants and how how can<00:47:45.420> you<00:47:45.599> use<00:47:45.839> those<00:47:46.079> to<00:47:46.319> make<00:47:46.380> your<00:47:46.560> fuzzing 00:47:46.970 --> 00:47:46.980 align:start position:0% can you use those to make your fuzzing 00:47:46.980 --> 00:47:48.589 align:start position:0% can you use those to make your fuzzing more<00:47:47.460> effective<00:47:47.880> so<00:47:48.180> I<00:47:48.420> would<00:47:48.480> really 00:47:48.589 --> 00:47:48.599 align:start position:0% more effective so I would really 00:47:48.599 --> 00:47:50.450 align:start position:0% more effective so I would really recommend<00:47:48.960> that<00:47:49.079> that<00:47:49.319> you<00:47:49.500> go<00:47:49.619> to<00:47:49.740> that<00:47:49.920> so 00:47:50.450 --> 00:47:50.460 align:start position:0% recommend that that you go to that so 00:47:50.460 --> 00:47:52.250 align:start position:0% recommend that that you go to that so just<00:47:50.640> to<00:47:50.760> be<00:47:50.880> fair<00:47:51.119> I<00:47:51.420> know<00:47:51.540> like<00:47:51.780> we're<00:47:51.960> at<00:47:52.140> a 00:47:52.250 --> 00:47:52.260 align:start position:0% just to be fair I know like we're at a 00:47:52.260 --> 00:47:53.990 align:start position:0% just to be fair I know like we're at a time<00:47:52.380> by<00:47:52.560> this<00:47:52.740> timer<00:47:52.980> let's<00:47:53.520> give<00:47:53.760> every 00:47:53.990 --> 00:47:54.000 align:start position:0% time by this timer let's give every 00:47:54.000 --> 00:47:57.589 align:start position:0% time by this timer let's give every speaker<00:47:54.300> like<00:47:54.900> 30<00:47:55.740> seconds<00:47:56.040> to<00:47:56.400> sorry 00:47:57.589 --> 00:47:57.599 align:start position:0% speaker like 30 seconds to sorry 00:47:57.599 --> 00:47:59.690 align:start position:0% speaker like 30 seconds to sorry all<00:47:58.560> right<00:47:58.740> so<00:47:58.920> we<00:47:59.099> started<00:47:59.460> the<00:47:59.579> questions 00:47:59.690 --> 00:47:59.700 align:start position:0% all right so we started the questions 00:47:59.700 --> 00:48:02.750 align:start position:0% all right so we started the questions way<00:48:00.119> early<00:48:00.240> we've<00:48:00.540> got<00:48:00.660> tons<00:48:00.900> of<00:48:01.079> time 00:48:02.750 --> 00:48:02.760 align:start position:0% way early we've got tons of time 00:48:02.760 --> 00:48:05.210 align:start position:0% way early we've got tons of time um<00:48:02.880> I<00:48:03.240> should<00:48:03.420> have<00:48:03.540> read<00:48:03.660> the<00:48:03.780> manual 00:48:05.210 --> 00:48:05.220 align:start position:0% um I should have read the manual 00:48:05.220 --> 00:48:06.349 align:start position:0% um I should have read the manual um<00:48:05.339> did 00:48:06.349 --> 00:48:06.359 align:start position:0% um did 00:48:06.359 --> 00:48:08.750 align:start position:0% um did uh<00:48:07.020> Brian<00:48:07.140> I<00:48:07.500> know<00:48:07.619> Brian<00:48:07.800> had<00:48:08.099> his<00:48:08.220> hand<00:48:08.400> up<00:48:08.579> at 00:48:08.750 --> 00:48:08.760 align:start position:0% uh Brian I know Brian had his hand up at 00:48:08.760 --> 00:48:10.550 align:start position:0% uh Brian I know Brian had his hand up at one<00:48:09.000> point 00:48:10.550 --> 00:48:10.560 align:start position:0% one point 00:48:10.560 --> 00:48:12.290 align:start position:0% one point um<00:48:10.680> and 00:48:12.290 --> 00:48:12.300 align:start position:0% um and 00:48:12.300 --> 00:48:14.990 align:start position:0% um and I'll<00:48:12.599> get<00:48:12.780> you<00:48:12.960> please<00:48:13.680> just<00:48:14.160> get<00:48:14.400> just<00:48:14.819> like 00:48:14.990 --> 00:48:15.000 align:start position:0% I'll get you please just get just like 00:48:15.000 --> 00:48:16.849 align:start position:0% I'll get you please just get just like I'll<00:48:15.300> I'll<00:48:15.480> repeat<00:48:15.720> it<00:48:16.020> through<00:48:16.260> the<00:48:16.440> mic<00:48:16.560> so 00:48:16.849 --> 00:48:16.859 align:start position:0% I'll I'll repeat it through the mic so 00:48:16.859 --> 00:48:18.589 align:start position:0% I'll I'll repeat it through the mic so go<00:48:17.040> ahead 00:48:18.589 --> 00:48:18.599 align:start position:0% go ahead 00:48:18.599 --> 00:48:20.089 align:start position:0% go ahead that's<00:48:19.079> that's<00:48:19.079> cool<00:48:19.500> is<00:48:19.680> there<00:48:19.800> a<00:48:19.920> way<00:48:19.980> to 00:48:20.089 --> 00:48:20.099 align:start position:0% that's that's cool is there a way to 00:48:20.099 --> 00:48:22.190 align:start position:0% that's that's cool is there a way to make<00:48:20.220> like<00:48:20.400> the<00:48:20.579> the<00:48:20.700> output<00:48:21.119> of<00:48:21.480> of<00:48:21.720> audits 00:48:22.190 --> 00:48:22.200 align:start position:0% make like the the output of of audits 00:48:22.200 --> 00:48:23.569 align:start position:0% make like the the output of of audits machine<00:48:22.440> readable 00:48:23.569 --> 00:48:23.579 align:start position:0% machine readable 00:48:23.579 --> 00:48:25.309 align:start position:0% machine readable um<00:48:23.700> and<00:48:23.940> it's<00:48:24.000> interesting<00:48:24.359> because<00:48:24.540> we<00:48:24.839> we<00:48:25.079> do 00:48:25.309 --> 00:48:25.319 align:start position:0% um and it's interesting because we we do 00:48:25.319 --> 00:48:31.150 align:start position:0% um and it's interesting because we we do actually 00:48:31.150 --> 00:48:31.160 align:start position:0% 00:48:31.160 --> 00:48:33.050 align:start position:0% that's<00:48:32.160> really<00:48:32.339> interesting<00:48:32.700> and<00:48:32.819> I<00:48:32.940> think 00:48:33.050 --> 00:48:33.060 align:start position:0% that's really interesting and I think 00:48:33.060 --> 00:48:34.849 align:start position:0% that's really interesting and I think we're<00:48:33.180> gonna<00:48:33.359> take<00:48:33.720> that<00:48:33.900> up<00:48:34.020> and<00:48:34.200> talk<00:48:34.619> to<00:48:34.740> us 00:48:34.849 --> 00:48:34.859 align:start position:0% we're gonna take that up and talk to us 00:48:34.859 --> 00:48:36.950 align:start position:0% we're gonna take that up and talk to us hit<00:48:35.220> us<00:48:35.400> up<00:48:35.520> afterwards 00:48:36.950 --> 00:48:36.960 align:start position:0% hit us up afterwards 00:48:36.960 --> 00:48:39.410 align:start position:0% hit us up afterwards um<00:48:37.079> I<00:48:37.260> I<00:48:37.380> think<00:48:37.800> it's<00:48:38.220> gonna<00:48:38.640> really<00:48:38.880> depend<00:48:39.240> on 00:48:39.410 --> 00:48:39.420 align:start position:0% um I I think it's gonna really depend on 00:48:39.420 --> 00:48:41.569 align:start position:0% um I I think it's gonna really depend on the<00:48:39.780> writing<00:48:40.200> style<00:48:40.380> of<00:48:40.740> of<00:48:40.980> the<00:48:41.220> security 00:48:41.569 --> 00:48:41.579 align:start position:0% the writing style of of the security 00:48:41.579 --> 00:48:44.089 align:start position:0% the writing style of of the security firm<00:48:42.119> that<00:48:42.359> you<00:48:42.540> engage<00:48:43.020> with 00:48:44.089 --> 00:48:44.099 align:start position:0% firm that you engage with 00:48:44.099 --> 00:48:46.190 align:start position:0% firm that you engage with um<00:48:44.220> but<00:48:44.640> it<00:48:44.819> is<00:48:45.060> something<00:48:45.240> I'd<00:48:45.480> like<00:48:45.660> to<00:48:45.839> think 00:48:46.190 --> 00:48:46.200 align:start position:0% um but it is something I'd like to think 00:48:46.200 --> 00:48:47.569 align:start position:0% um but it is something I'd like to think about<00:48:46.319> a<00:48:46.500> bit<00:48:46.619> more<00:48:46.800> yeah 00:48:47.569 --> 00:48:47.579 align:start position:0% about a bit more yeah 00:48:47.579 --> 00:48:48.349 align:start position:0% about a bit more yeah um 00:48:48.349 --> 00:48:48.359 align:start position:0% um 00:48:48.359 --> 00:48:51.170 align:start position:0% um perhaps<00:48:49.079> we<00:48:49.319> could<00:48:49.500> parse<00:48:50.160> some<00:48:50.700> of<00:48:50.819> those 00:48:51.170 --> 00:48:51.180 align:start position:0% perhaps we could parse some of those 00:48:51.180 --> 00:48:54.770 align:start position:0% perhaps we could parse some of those reports<00:48:52.020> into<00:48:52.380> a<00:48:53.220> readable<00:48:53.940> format<00:48:54.420> or<00:48:54.660> a 00:48:54.770 --> 00:48:54.780 align:start position:0% reports into a readable format or a 00:48:54.780 --> 00:48:56.270 align:start position:0% reports into a readable format or a machine<00:48:54.900> readable<00:48:55.319> format<00:48:55.740> that<00:48:56.099> shouldn't 00:48:56.270 --> 00:48:56.280 align:start position:0% machine readable format that shouldn't 00:48:56.280 --> 00:48:58.250 align:start position:0% machine readable format that shouldn't be<00:48:56.339> too<00:48:56.460> hard<00:48:56.640> to<00:48:56.760> do<00:48:56.880> we<00:48:57.300> write<00:48:57.480> a<00:48:57.720> report<00:48:57.780> in 00:48:58.250 --> 00:48:58.260 align:start position:0% be too hard to do we write a report in 00:48:58.260 --> 00:49:00.230 align:start position:0% be too hard to do we write a report in reports<00:48:58.859> in<00:48:58.920> latex<00:48:59.339> so 00:49:00.230 --> 00:49:00.240 align:start position:0% reports in latex so 00:49:00.240 --> 00:49:02.270 align:start position:0% reports in latex so it<00:49:00.300> should<00:49:00.480> be<00:49:00.660> pretty<00:49:00.839> trivial<00:49:01.260> for<00:49:01.440> us<00:49:01.500> to<00:49:01.680> do 00:49:02.270 --> 00:49:02.280 align:start position:0% it should be pretty trivial for us to do 00:49:02.280 --> 00:49:06.050 align:start position:0% it should be pretty trivial for us to do cool<00:49:02.700> so<00:49:03.599> uh<00:49:04.020> so<00:49:04.500> try<00:49:04.740> actually<00:49:04.920> we<00:49:05.280> do<00:49:05.460> have<00:49:05.700> we 00:49:06.050 --> 00:49:06.060 align:start position:0% cool so uh so try actually we do have we 00:49:06.060 --> 00:49:08.690 align:start position:0% cool so uh so try actually we do have we have<00:49:06.240> been<00:49:06.359> working<00:49:06.540> on<00:49:06.780> a<00:49:07.020> related<00:49:07.380> things<00:49:07.619> so 00:49:08.690 --> 00:49:08.700 align:start position:0% have been working on a related things so 00:49:08.700 --> 00:49:09.770 align:start position:0% have been working on a related things so um<00:49:08.760> I<00:49:08.940> don't<00:49:09.060> know<00:49:09.119> if<00:49:09.240> you've<00:49:09.420> ever<00:49:09.599> heard 00:49:09.770 --> 00:49:09.780 align:start position:0% um I don't know if you've ever heard 00:49:09.780 --> 00:49:12.230 align:start position:0% um I don't know if you've ever heard like<00:49:09.960> there's<00:49:10.260> things<00:49:10.440> like<00:49:10.680> deoxygen<00:49:11.579> or<00:49:12.000> the 00:49:12.230 --> 00:49:12.240 align:start position:0% like there's things like deoxygen or the 00:49:12.240 --> 00:49:13.430 align:start position:0% like there's things like deoxygen or the oxygen<00:49:12.599> I<00:49:12.720> don't<00:49:12.839> know<00:49:12.900> how<00:49:12.960> to<00:49:13.079> pronounce<00:49:13.319> it 00:49:13.430 --> 00:49:13.440 align:start position:0% oxygen I don't know how to pronounce it 00:49:13.440 --> 00:49:16.010 align:start position:0% oxygen I don't know how to pronounce it and<00:49:13.859> like<00:49:14.099> there's<00:49:14.220> also<00:49:14.700> uh<00:49:15.240> Nat<00:49:15.599> spec<00:49:15.780> is 00:49:16.010 --> 00:49:16.020 align:start position:0% and like there's also uh Nat spec is 00:49:16.020 --> 00:49:19.970 align:start position:0% and like there's also uh Nat spec is another<00:49:16.280> similar<00:49:17.280> Library<00:49:17.540> so<00:49:18.540> uh<00:49:19.200> the<00:49:19.859> nice 00:49:19.970 --> 00:49:19.980 align:start position:0% another similar Library so uh the nice 00:49:19.980 --> 00:49:21.650 align:start position:0% another similar Library so uh the nice thing<00:49:20.160> about<00:49:20.400> you<00:49:20.880> know<00:49:20.940> if<00:49:21.060> you're<00:49:21.240> if<00:49:21.540> you 00:49:21.650 --> 00:49:21.660 align:start position:0% thing about you know if you're if you 00:49:21.660 --> 00:49:22.970 align:start position:0% thing about you know if you're if you have<00:49:21.720> a<00:49:21.780> formal<00:49:22.079> spec<00:49:22.260> it's<00:49:22.619> actually<00:49:22.800> a 00:49:22.970 --> 00:49:22.980 align:start position:0% have a formal spec it's actually a 00:49:22.980 --> 00:49:25.069 align:start position:0% have a formal spec it's actually a little<00:49:23.040> bit<00:49:23.220> easier<00:49:23.640> to<00:49:24.480> like<00:49:24.839> sort<00:49:24.960> of 00:49:25.069 --> 00:49:25.079 align:start position:0% little bit easier to like sort of 00:49:25.079 --> 00:49:27.170 align:start position:0% little bit easier to like sort of convert<00:49:25.440> that<00:49:25.619> to<00:49:25.859> a<00:49:26.099> format<00:49:26.579> because<00:49:26.819> you<00:49:27.060> can 00:49:27.170 --> 00:49:27.180 align:start position:0% convert that to a format because you can 00:49:27.180 --> 00:49:29.510 align:start position:0% convert that to a format because you can annotate<00:49:27.720> your<00:49:28.680> code<00:49:28.859> and<00:49:29.040> then<00:49:29.220> you<00:49:29.460> can 00:49:29.510 --> 00:49:29.520 align:start position:0% annotate your code and then you can 00:49:29.520 --> 00:49:32.410 align:start position:0% annotate your code and then you can automatically<00:49:30.060> generate<00:49:30.599> some<00:49:31.380> kind<00:49:31.560> of<00:49:31.680> a 00:49:32.410 --> 00:49:32.420 align:start position:0% automatically generate some kind of a 00:49:32.420 --> 00:49:35.390 align:start position:0% automatically generate some kind of a formatted<00:49:33.420> report<00:49:33.660> from<00:49:34.020> from<00:49:34.319> that<00:49:34.619> so<00:49:34.920> I 00:49:35.390 --> 00:49:35.400 align:start position:0% formatted report from from that so I 00:49:35.400 --> 00:49:36.829 align:start position:0% formatted report from from that so I think<00:49:35.460> it's<00:49:35.579> a<00:49:35.760> good<00:49:35.880> idea 00:49:36.829 --> 00:49:36.839 align:start position:0% think it's a good idea 00:49:36.839 --> 00:49:39.770 align:start position:0% think it's a good idea uh<00:49:37.619> Hey<00:49:37.859> guys<00:49:38.040> Kevin<00:49:38.339> over<00:49:38.760> here<00:49:38.880> uh<00:49:39.660> Hey 00:49:39.770 --> 00:49:39.780 align:start position:0% uh Hey guys Kevin over here uh Hey 00:49:39.780 --> 00:49:40.790 align:start position:0% uh Hey guys Kevin over here uh Hey friends 00:49:40.790 --> 00:49:40.800 align:start position:0% friends 00:49:40.800 --> 00:49:43.190 align:start position:0% friends um<00:49:40.859> so<00:49:41.160> having<00:49:41.880> come<00:49:42.180> from<00:49:42.420> sort<00:49:43.020> of<00:49:43.140> the 00:49:43.190 --> 00:49:43.200 align:start position:0% um so having come from sort of the 00:49:43.200 --> 00:49:44.990 align:start position:0% um so having come from sort of the security<00:49:43.380> side<00:49:43.740> and<00:49:44.040> now<00:49:44.220> being<00:49:44.460> protocol 00:49:44.990 --> 00:49:45.000 align:start position:0% security side and now being protocol 00:49:45.000 --> 00:49:46.910 align:start position:0% security side and now being protocol engineer<00:49:45.480> and<00:49:45.660> founder 00:49:46.910 --> 00:49:46.920 align:start position:0% engineer and founder 00:49:46.920 --> 00:49:49.190 align:start position:0% engineer and founder um<00:49:46.980> I'm<00:49:47.099> wondering<00:49:47.400> about<00:49:47.520> this<00:49:48.000> this<00:49:48.839> line 00:49:49.190 --> 00:49:49.200 align:start position:0% um I'm wondering about this this line 00:49:49.200 --> 00:49:53.390 align:start position:0% um I'm wondering about this this line you<00:49:50.099> tread<00:49:50.640> as<00:49:51.240> an<00:49:51.480> author<00:49:51.839> of<00:49:52.560> being<00:49:53.160> very 00:49:53.390 --> 00:49:53.400 align:start position:0% you tread as an author of being very 00:49:53.400 --> 00:49:56.089 align:start position:0% you tread as an author of being very slow<00:49:53.700> methodical<00:49:54.420> you<00:49:55.260> know<00:49:55.319> heavy<00:49:55.740> testing 00:49:56.089 --> 00:49:56.099 align:start position:0% slow methodical you know heavy testing 00:49:56.099 --> 00:49:59.089 align:start position:0% slow methodical you know heavy testing core<00:49:56.400> protocol<00:49:56.940> must<00:49:57.420> be<00:49:57.599> super<00:49:57.780> secure<00:49:58.200> to 00:49:59.089 --> 00:49:59.099 align:start position:0% core protocol must be super secure to 00:49:59.099 --> 00:50:00.710 align:start position:0% core protocol must be super secure to now<00:49:59.339> okay<00:49:59.579> now<00:49:59.819> I'm<00:50:00.000> wanting<00:50:00.240> to<00:50:00.300> move<00:50:00.420> a<00:50:00.599> bit 00:50:00.710 --> 00:50:00.720 align:start position:0% now okay now I'm wanting to move a bit 00:50:00.720 --> 00:50:03.290 align:start position:0% now okay now I'm wanting to move a bit faster<00:50:01.079> maybe<00:50:01.980> their<00:50:02.220> integration<00:50:02.640> contracts 00:50:03.290 --> 00:50:03.300 align:start position:0% faster maybe their integration contracts 00:50:03.300 --> 00:50:05.390 align:start position:0% faster maybe their integration contracts or<00:50:03.839> something<00:50:04.440> that's<00:50:04.680> not<00:50:04.920> in<00:50:05.040> my<00:50:05.220> core 00:50:05.390 --> 00:50:05.400 align:start position:0% or something that's not in my core 00:50:05.400 --> 00:50:06.770 align:start position:0% or something that's not in my core protocol 00:50:06.770 --> 00:50:06.780 align:start position:0% protocol 00:50:06.780 --> 00:50:09.950 align:start position:0% protocol um<00:50:06.839> you<00:50:07.380> know<00:50:07.440> how<00:50:08.099> much<00:50:08.460> time<00:50:09.119> am<00:50:09.420> I<00:50:09.599> spending 00:50:09.950 --> 00:50:09.960 align:start position:0% um you know how much time am I spending 00:50:09.960 --> 00:50:11.690 align:start position:0% um you know how much time am I spending and<00:50:10.140> testing<00:50:10.500> and<00:50:10.680> auditing<00:50:11.220> how<00:50:11.400> much<00:50:11.460> money 00:50:11.690 --> 00:50:11.700 align:start position:0% and testing and auditing how much money 00:50:11.700 --> 00:50:14.390 align:start position:0% and testing and auditing how much money am<00:50:11.880> I<00:50:12.060> spending<00:50:12.359> there<00:50:12.540> versus<00:50:13.020> move<00:50:13.859> fast<00:50:14.160> and 00:50:14.390 --> 00:50:14.400 align:start position:0% am I spending there versus move fast and 00:50:14.400 --> 00:50:16.670 align:start position:0% am I spending there versus move fast and see<00:50:14.819> if<00:50:14.940> things<00:50:15.119> work<00:50:15.359> I<00:50:15.960> wonder<00:50:16.140> if<00:50:16.260> there's<00:50:16.440> I 00:50:16.670 --> 00:50:16.680 align:start position:0% see if things work I wonder if there's I 00:50:16.680 --> 00:50:18.470 align:start position:0% see if things work I wonder if there's I have<00:50:16.800> my<00:50:16.920> own<00:50:17.040> opinion<00:50:17.339> but<00:50:17.700> interested<00:50:18.359> to 00:50:18.470 --> 00:50:18.480 align:start position:0% have my own opinion but interested to 00:50:18.480 --> 00:50:20.150 align:start position:0% have my own opinion but interested to hear<00:50:18.599> what's<00:50:19.020> on<00:50:19.200> the<00:50:19.319> stage<00:50:19.500> I'll<00:50:19.980> just 00:50:20.150 --> 00:50:20.160 align:start position:0% hear what's on the stage I'll just 00:50:20.160 --> 00:50:22.609 align:start position:0% hear what's on the stage I'll just quickly<00:50:20.460> I'll<00:50:20.579> say<00:50:21.300> um<00:50:21.359> the<00:50:21.900> most<00:50:22.079> secure<00:50:22.380> code 00:50:22.609 --> 00:50:22.619 align:start position:0% quickly I'll say um the most secure code 00:50:22.619 --> 00:50:25.250 align:start position:0% quickly I'll say um the most secure code is<00:50:22.800> the<00:50:22.980> code<00:50:23.040> that<00:50:23.220> never<00:50:23.460> hits<00:50:23.640> mainnet<00:50:24.300> so 00:50:25.250 --> 00:50:25.260 align:start position:0% is the code that never hits mainnet so 00:50:25.260 --> 00:50:27.349 align:start position:0% is the code that never hits mainnet so just<00:50:25.920> keep<00:50:26.099> testing 00:50:27.349 --> 00:50:27.359 align:start position:0% just keep testing 00:50:27.359 --> 00:50:29.750 align:start position:0% just keep testing I<00:50:28.079> also<00:50:28.380> think<00:50:28.680> it<00:50:28.920> depends<00:50:29.220> on<00:50:29.400> how<00:50:29.640> much 00:50:29.750 --> 00:50:29.760 align:start position:0% I also think it depends on how much 00:50:29.760 --> 00:50:31.970 align:start position:0% I also think it depends on how much money<00:50:30.000> you<00:50:30.240> raised<00:50:30.599> or<00:50:31.079> how<00:50:31.260> much<00:50:31.380> money<00:50:31.619> you 00:50:31.970 --> 00:50:31.980 align:start position:0% money you raised or how much money you 00:50:31.980 --> 00:50:34.069 align:start position:0% money you raised or how much money you have<00:50:32.099> and<00:50:32.640> now<00:50:32.819> it's<00:50:33.000> like<00:50:33.240> it's<00:50:33.420> very<00:50:33.660> it's<00:50:33.960> a 00:50:34.069 --> 00:50:34.079 align:start position:0% have and now it's like it's very it's a 00:50:34.079 --> 00:50:36.410 align:start position:0% have and now it's like it's very it's a very<00:50:34.319> practical<00:50:34.619> thing<00:50:34.920> you<00:50:35.280> know<00:50:35.400> like<00:50:35.760> you 00:50:36.410 --> 00:50:36.420 align:start position:0% very practical thing you know like you 00:50:36.420 --> 00:50:38.270 align:start position:0% very practical thing you know like you can<00:50:36.540> spend<00:50:36.839> a<00:50:37.020> lot<00:50:37.200> of<00:50:37.319> time<00:50:37.560> and<00:50:37.740> resources 00:50:38.270 --> 00:50:38.280 align:start position:0% can spend a lot of time and resources 00:50:38.280 --> 00:50:41.150 align:start position:0% can spend a lot of time and resources doing<00:50:38.819> doing<00:50:39.300> writing<00:50:40.200> tests<00:50:40.560> but<00:50:40.740> at<00:50:40.920> the<00:50:41.040> end 00:50:41.150 --> 00:50:41.160 align:start position:0% doing doing writing tests but at the end 00:50:41.160 --> 00:50:43.309 align:start position:0% doing doing writing tests but at the end of<00:50:41.280> the<00:50:41.400> day<00:50:41.520> if<00:50:41.880> you<00:50:42.000> run<00:50:42.180> out<00:50:42.359> of<00:50:42.480> money<00:50:42.720> and 00:50:43.309 --> 00:50:43.319 align:start position:0% of the day if you run out of money and 00:50:43.319 --> 00:50:44.930 align:start position:0% of the day if you run out of money and you<00:50:43.500> only<00:50:43.560> have<00:50:43.800> the<00:50:43.980> test<00:50:44.160> you're<00:50:44.700> probably 00:50:44.930 --> 00:50:46.910 align:start position:0% you only have the test you're probably 00:50:46.910 --> 00:50:46.920 align:start position:0% 00:50:46.920 --> 00:50:49.309 align:start position:0% okay<00:50:47.400> cool<00:50:47.640> it<00:50:48.000> might<00:50:48.119> come<00:50:48.300> off<00:50:48.540> as<00:50:48.900> somewhat 00:50:49.309 --> 00:50:49.319 align:start position:0% okay cool it might come off as somewhat 00:50:49.319 --> 00:50:51.770 align:start position:0% okay cool it might come off as somewhat pedantic<00:50:49.920> but<00:50:50.160> I'm<00:50:50.339> curious<00:50:50.640> looking<00:50:51.300> at<00:50:51.599> the 00:50:51.770 --> 00:50:51.780 align:start position:0% pedantic but I'm curious looking at the 00:50:51.780 --> 00:50:53.750 align:start position:0% pedantic but I'm curious looking at the different<00:50:51.960> way<00:50:52.319> that<00:50:52.619> auditing<00:50:53.040> firms<00:50:53.460> do 00:50:53.750 --> 00:50:53.760 align:start position:0% different way that auditing firms do 00:50:53.760 --> 00:50:58.609 align:start position:0% different way that auditing firms do severity<00:50:54.680> or<00:50:55.680> impact<00:50:56.400> and<00:50:57.119> then<00:50:57.619> difficulty 00:50:58.609 --> 00:50:58.619 align:start position:0% severity or impact and then difficulty 00:50:58.619 --> 00:51:01.130 align:start position:0% severity or impact and then difficulty slash<00:50:59.040> likelihood<00:50:59.640> I'll<00:51:00.420> be<00:51:00.540> honest<00:51:00.780> I<00:51:00.960> like 00:51:01.130 --> 00:51:01.140 align:start position:0% slash likelihood I'll be honest I like 00:51:01.140 --> 00:51:01.970 align:start position:0% slash likelihood I'll be honest I like when 00:51:01.970 --> 00:51:01.980 align:start position:0% when 00:51:01.980 --> 00:51:05.569 align:start position:0% when I<00:51:02.460> prefer<00:51:02.839> likelihood<00:51:03.839> so<00:51:04.140> that<00:51:04.260> it's<00:51:04.440> like<00:51:04.740> uh 00:51:05.569 --> 00:51:05.579 align:start position:0% I prefer likelihood so that it's like uh 00:51:05.579 --> 00:51:08.930 align:start position:0% I prefer likelihood so that it's like uh difficulty<00:51:06.319> is<00:51:07.319> low<00:51:07.559> when<00:51:08.160> likelihood<00:51:08.700> is 00:51:08.930 --> 00:51:08.940 align:start position:0% difficulty is low when likelihood is 00:51:08.940 --> 00:51:11.390 align:start position:0% difficulty is low when likelihood is high<00:51:09.119> so<00:51:09.660> I<00:51:10.200> was<00:51:10.500> just<00:51:10.619> wondering<00:51:10.980> you<00:51:11.280> know 00:51:11.390 --> 00:51:11.400 align:start position:0% high so I was just wondering you know 00:51:11.400 --> 00:51:14.990 align:start position:0% high so I was just wondering you know High<00:51:12.440> likelihood<00:51:13.440> and<00:51:13.920> high<00:51:14.220> impact<00:51:14.700> would 00:51:14.990 --> 00:51:15.000 align:start position:0% High likelihood and high impact would 00:51:15.000 --> 00:51:16.730 align:start position:0% High likelihood and high impact would equal<00:51:15.180> High<00:51:15.599> severity<00:51:16.020> have<00:51:16.440> you<00:51:16.559> seen 00:51:16.730 --> 00:51:16.740 align:start position:0% equal High severity have you seen 00:51:16.740 --> 00:51:18.530 align:start position:0% equal High severity have you seen clients<00:51:17.160> get<00:51:17.400> confused<00:51:17.880> about<00:51:18.119> this 00:51:18.530 --> 00:51:18.540 align:start position:0% clients get confused about this 00:51:18.540 --> 00:51:20.809 align:start position:0% clients get confused about this different<00:51:18.720> and<00:51:19.079> without<00:51:19.500> being<00:51:19.859> overly<00:51:20.400> like 00:51:20.809 --> 00:51:20.819 align:start position:0% different and without being overly like 00:51:20.819 --> 00:51:23.270 align:start position:0% different and without being overly like strict<00:51:21.540> as<00:51:22.079> the<00:51:22.559> industry<00:51:22.920> is<00:51:23.040> still 00:51:23.270 --> 00:51:23.280 align:start position:0% strict as the industry is still 00:51:23.280 --> 00:51:25.490 align:start position:0% strict as the industry is still developing<00:51:23.760> I'm<00:51:24.480> also<00:51:24.780> curious<00:51:25.020> about<00:51:25.260> like 00:51:25.490 --> 00:51:25.500 align:start position:0% developing I'm also curious about like 00:51:25.500 --> 00:51:28.190 align:start position:0% developing I'm also curious about like how<00:51:25.800> we<00:51:25.980> might<00:51:26.160> classify<00:51:26.940> things<00:51:27.660> trail<00:51:27.960> of 00:51:28.190 --> 00:51:28.200 align:start position:0% how we might classify things trail of 00:51:28.200 --> 00:51:30.010 align:start position:0% how we might classify things trail of bits<00:51:28.440> has<00:51:28.559> a<00:51:28.740> nice<00:51:28.859> classification 00:51:30.010 --> 00:51:30.020 align:start position:0% bits has a nice classification 00:51:30.020 --> 00:51:33.430 align:start position:0% bits has a nice classification swc<00:51:31.020> seems<00:51:31.619> like<00:51:31.800> outdated<00:51:32.339> and<00:51:32.640> not<00:51:32.819> updated 00:51:33.430 --> 00:51:33.440 align:start position:0% swc seems like outdated and not updated 00:51:33.440 --> 00:51:35.870 align:start position:0% swc seems like outdated and not updated as<00:51:34.440> well<00:51:34.559> as<00:51:34.680> or<00:51:34.920> maybe<00:51:35.099> it<00:51:35.339> could<00:51:35.460> be<00:51:35.579> going 00:51:35.870 --> 00:51:35.880 align:start position:0% as well as or maybe it could be going 00:51:35.880 --> 00:51:37.790 align:start position:0% as well as or maybe it could be going forward<00:51:36.119> are<00:51:36.780> there<00:51:36.960> things<00:51:37.260> that<00:51:37.440> we<00:51:37.559> can<00:51:37.680> do 00:51:37.790 --> 00:51:37.800 align:start position:0% forward are there things that we can do 00:51:37.800 --> 00:51:40.849 align:start position:0% forward are there things that we can do as<00:51:37.980> an<00:51:38.160> industry<00:51:38.460> to<00:51:38.880> improve<00:51:39.480> and<00:51:39.660> start<00:51:39.960> to 00:51:40.849 --> 00:51:40.859 align:start position:0% as an industry to improve and start to 00:51:40.859 --> 00:51:43.549 align:start position:0% as an industry to improve and start to I<00:51:41.339> hate<00:51:41.520> to<00:51:41.640> say<00:51:41.760> solidify<00:51:42.359> but<00:51:42.660> structure<00:51:43.380> our 00:51:43.549 --> 00:51:43.559 align:start position:0% I hate to say solidify but structure our 00:51:43.559 --> 00:51:45.170 align:start position:0% I hate to say solidify but structure our information<00:51:43.800> architecture<00:51:44.640> a<00:51:44.940> little<00:51:45.059> bit 00:51:45.170 --> 00:51:45.180 align:start position:0% information architecture a little bit 00:51:45.180 --> 00:51:47.030 align:start position:0% information architecture a little bit more<00:51:45.359> so<00:51:45.599> that<00:51:45.780> clients<00:51:46.140> can<00:51:46.319> understand<00:51:46.500> when 00:51:47.030 --> 00:51:47.040 align:start position:0% more so that clients can understand when 00:51:47.040 --> 00:51:48.470 align:start position:0% more so that clients can understand when they're<00:51:47.220> getting<00:51:47.400> multiple<00:51:47.760> audit<00:51:48.119> reports 00:51:48.470 --> 00:51:48.480 align:start position:0% they're getting multiple audit reports 00:51:48.480 --> 00:51:51.410 align:start position:0% they're getting multiple audit reports and<00:51:48.780> reduce<00:51:49.260> confusion<00:51:50.000> I<00:51:51.000> think<00:51:51.119> I<00:51:51.359> think 00:51:51.410 --> 00:51:51.420 align:start position:0% and reduce confusion I think I think 00:51:51.420 --> 00:51:53.210 align:start position:0% and reduce confusion I think I think it's<00:51:51.599> uh<00:51:51.839> yeah<00:51:52.020> it's<00:51:52.200> a<00:51:52.319> great<00:51:52.440> Point<00:51:52.619> as<00:51:52.859> you 00:51:53.210 --> 00:51:53.220 align:start position:0% it's uh yeah it's a great Point as you 00:51:53.220 --> 00:51:56.569 align:start position:0% it's uh yeah it's a great Point as you said<00:51:53.339> uh<00:51:53.760> well<00:51:53.940> for<00:51:54.180> us<00:51:54.300> for<00:51:54.839> us<00:51:54.960> at<00:51:55.200> CP<00:51:55.740> a<00:51:56.339> high 00:51:56.569 --> 00:51:56.579 align:start position:0% said uh well for us for us at CP a high 00:51:56.579 --> 00:52:00.770 align:start position:0% said uh well for us for us at CP a high likelihood<00:51:57.059> high<00:51:57.839> impact<00:51:58.200> critical 00:52:00.770 --> 00:52:00.780 align:start position:0% likelihood high impact critical 00:52:00.780 --> 00:52:02.750 align:start position:0% likelihood high impact critical um<00:52:00.900> and<00:52:01.140> I<00:52:01.319> think<00:52:01.440> we<00:52:01.740> all<00:52:01.920> use<00:52:02.220> perhaps 00:52:02.750 --> 00:52:02.760 align:start position:0% um and I think we all use perhaps 00:52:02.760 --> 00:52:07.790 align:start position:0% um and I think we all use perhaps similar<00:52:03.660> types<00:52:04.200> of<00:52:04.460> risk<00:52:05.460> rating<00:52:06.059> matrices 00:52:07.790 --> 00:52:07.800 align:start position:0% similar types of risk rating matrices 00:52:07.800 --> 00:52:10.309 align:start position:0% similar types of risk rating matrices um it<00:52:08.579> it's<00:52:09.180> probably<00:52:09.359> beneficial<00:52:09.960> if<00:52:10.079> you 00:52:10.309 --> 00:52:10.319 align:start position:0% um it it's probably beneficial if you 00:52:10.319 --> 00:52:13.730 align:start position:0% um it it's probably beneficial if you could<00:52:10.500> standardize<00:52:11.119> on<00:52:12.119> on<00:52:12.900> how<00:52:13.260> we<00:52:13.500> would 00:52:13.730 --> 00:52:13.740 align:start position:0% could standardize on on how we would 00:52:13.740 --> 00:52:16.190 align:start position:0% could standardize on on how we would write<00:52:14.099> severity<00:52:14.760> so<00:52:15.480> as<00:52:15.720> you<00:52:15.839> said<00:52:15.960> it's 00:52:16.190 --> 00:52:16.200 align:start position:0% write severity so as you said it's 00:52:16.200 --> 00:52:18.309 align:start position:0% write severity so as you said it's typically<00:52:16.619> likelihood<00:52:17.400> of<00:52:17.579> exploitation 00:52:18.309 --> 00:52:18.319 align:start position:0% typically likelihood of exploitation 00:52:18.319 --> 00:52:21.470 align:start position:0% typically likelihood of exploitation impact<00:52:19.319> of<00:52:19.500> exploitation<00:52:20.240> but<00:52:21.240> there's 00:52:21.470 --> 00:52:21.480 align:start position:0% impact of exploitation but there's 00:52:21.480 --> 00:52:24.230 align:start position:0% impact of exploitation but there's different<00:52:21.780> levels<00:52:22.380> so<00:52:22.980> we<00:52:23.160> only<00:52:23.339> have<00:52:23.640> we<00:52:24.119> got 00:52:24.230 --> 00:52:24.240 align:start position:0% different levels so we only have we got 00:52:24.240 --> 00:52:28.849 align:start position:0% different levels so we only have we got four<00:52:24.660> of<00:52:24.839> them<00:52:25.020> at<00:52:25.440> CP<00:52:26.180> so<00:52:27.180> informational<00:52:27.859> low 00:52:28.849 --> 00:52:28.859 align:start position:0% four of them at CP so informational low 00:52:28.859 --> 00:52:31.549 align:start position:0% four of them at CP so informational low medium<00:52:29.520> high<00:52:30.359> and<00:52:30.599> critical<00:52:30.960> that's<00:52:31.319> actually 00:52:31.549 --> 00:52:31.559 align:start position:0% medium high and critical that's actually 00:52:31.559 --> 00:52:32.870 align:start position:0% medium high and critical that's actually five 00:52:32.870 --> 00:52:32.880 align:start position:0% five 00:52:32.880 --> 00:52:34.849 align:start position:0% five um<00:52:32.940> but<00:52:33.540> yeah<00:52:33.839> I<00:52:34.079> think<00:52:34.200> I<00:52:34.380> think<00:52:34.500> it's<00:52:34.619> a<00:52:34.800> great 00:52:34.849 --> 00:52:34.859 align:start position:0% um but yeah I think I think it's a great 00:52:34.859 --> 00:52:37.190 align:start position:0% um but yeah I think I think it's a great idea<00:52:35.160> there's<00:52:35.400> been<00:52:35.579> a<00:52:35.760> lot<00:52:35.880> of<00:52:36.200> initiatives 00:52:37.190 --> 00:52:37.200 align:start position:0% idea there's been a lot of initiatives 00:52:37.200 --> 00:52:38.870 align:start position:0% idea there's been a lot of initiatives over<00:52:37.380> the<00:52:37.559> past<00:52:37.740> few<00:52:37.920> years<00:52:38.099> on<00:52:38.400> The<00:52:38.579> Ether 00:52:38.870 --> 00:52:38.880 align:start position:0% over the past few years on The Ether 00:52:38.880 --> 00:52:41.510 align:start position:0% over the past few years on The Ether security<00:52:39.059> channel<00:52:39.780> to<00:52:40.559> try<00:52:40.740> to<00:52:40.980> standardize 00:52:41.510 --> 00:52:41.520 align:start position:0% security channel to try to standardize 00:52:41.520 --> 00:52:44.809 align:start position:0% security channel to try to standardize some<00:52:41.819> of<00:52:41.940> this<00:52:42.119> stuff<00:52:42.420> it's<00:52:43.260> never<00:52:43.500> happened<00:52:43.819> I 00:52:44.809 --> 00:52:44.819 align:start position:0% some of this stuff it's never happened I 00:52:44.819 --> 00:52:46.970 align:start position:0% some of this stuff it's never happened I don't<00:52:44.940> I<00:52:45.059> don't<00:52:45.240> really<00:52:45.359> know<00:52:45.660> why 00:52:46.970 --> 00:52:46.980 align:start position:0% don't I don't really know why 00:52:46.980 --> 00:52:49.250 align:start position:0% don't I don't really know why um<00:52:47.000> but<00:52:48.000> I<00:52:48.240> think<00:52:48.300> it<00:52:48.480> would<00:52:48.599> be<00:52:48.780> it<00:52:48.960> would<00:52:49.140> be 00:52:49.250 --> 00:52:49.260 align:start position:0% um but I think it would be it would be 00:52:49.260 --> 00:52:50.809 align:start position:0% um but I think it would be it would be quite<00:52:49.380> beneficial 00:52:50.809 --> 00:52:50.819 align:start position:0% quite beneficial 00:52:50.819 --> 00:52:52.849 align:start position:0% quite beneficial I'm<00:52:51.480> going<00:52:51.720> to<00:52:51.839> give<00:52:51.900> you<00:52:52.079> a<00:52:52.380> bit<00:52:52.559> of<00:52:52.680> a<00:52:52.740> left 00:52:52.849 --> 00:52:52.859 align:start position:0% I'm going to give you a bit of a left 00:52:52.859 --> 00:52:54.890 align:start position:0% I'm going to give you a bit of a left field<00:52:53.099> question<00:52:53.520> so<00:52:53.940> there's<00:52:54.119> been<00:52:54.359> a<00:52:54.599> few 00:52:54.890 --> 00:52:54.900 align:start position:0% field question so there's been a few 00:52:54.900 --> 00:52:57.530 align:start position:0% field question so there's been a few regulatory<00:52:55.559> proposals<00:52:56.280> that<00:52:56.520> includes<00:52:57.119> uh 00:52:57.530 --> 00:52:57.540 align:start position:0% regulatory proposals that includes uh 00:52:57.540 --> 00:53:00.470 align:start position:0% regulatory proposals that includes uh software<00:52:57.960> security<00:52:58.200> best<00:52:58.619> practices<00:52:59.300> in<00:53:00.300> The 00:53:00.470 --> 00:53:00.480 align:start position:0% software security best practices in The 00:53:00.480 --> 00:53:04.549 align:start position:0% software security best practices in The Proposal<00:53:00.960> uh<00:53:01.680> what<00:53:02.099> sorts<00:53:02.460> of<00:53:02.960> standards<00:53:03.960> that 00:53:04.549 --> 00:53:04.559 align:start position:0% Proposal uh what sorts of standards that 00:53:04.559 --> 00:53:06.950 align:start position:0% Proposal uh what sorts of standards that are<00:53:04.740> driven<00:53:05.040> by<00:53:05.280> regulations<00:53:05.880> could<00:53:06.359> be<00:53:06.599> do 00:53:06.950 --> 00:53:06.960 align:start position:0% are driven by regulations could be do 00:53:06.960 --> 00:53:08.510 align:start position:0% are driven by regulations could be do you<00:53:07.200> think<00:53:07.260> could<00:53:07.440> be<00:53:07.619> damaging<00:53:07.980> to<00:53:08.160> the<00:53:08.339> space 00:53:08.510 --> 00:53:08.520 align:start position:0% you think could be damaging to the space 00:53:08.520 --> 00:53:10.549 align:start position:0% you think could be damaging to the space and<00:53:09.000> what<00:53:09.240> ones<00:53:09.660> do<00:53:09.839> you<00:53:09.960> think<00:53:10.079> could<00:53:10.200> be<00:53:10.380> good 00:53:10.549 --> 00:53:10.559 align:start position:0% and what ones do you think could be good 00:53:10.559 --> 00:53:14.270 align:start position:0% and what ones do you think could be good like<00:53:11.400> so<00:53:11.880> so<00:53:12.119> almost<00:53:12.359> like<00:53:12.660> uh<00:53:13.380> yeah<00:53:13.920> the 00:53:14.270 --> 00:53:14.280 align:start position:0% like so so almost like uh yeah the 00:53:14.280 --> 00:53:17.210 align:start position:0% like so so almost like uh yeah the typical<00:53:14.579> like<00:53:15.180> like<00:53:15.480> a<00:53:15.900> regular<00:53:16.440> comes<00:53:16.920> out<00:53:17.099> of 00:53:17.210 --> 00:53:17.220 align:start position:0% typical like like a regular comes out of 00:53:17.220 --> 00:53:18.950 align:start position:0% typical like like a regular comes out of nowhere<00:53:17.520> and<00:53:17.700> they're<00:53:17.880> maybe<00:53:18.059> a<00:53:18.300> bit<00:53:18.359> naive 00:53:18.950 --> 00:53:18.960 align:start position:0% nowhere and they're maybe a bit naive 00:53:18.960 --> 00:53:21.230 align:start position:0% nowhere and they're maybe a bit naive what<00:53:19.920> kind<00:53:20.099> of<00:53:20.220> damage<00:53:20.460> could<00:53:20.700> they<00:53:20.880> perhaps 00:53:21.230 --> 00:53:21.240 align:start position:0% what kind of damage could they perhaps 00:53:21.240 --> 00:53:23.770 align:start position:0% what kind of damage could they perhaps do<00:53:21.480> by<00:53:22.099> uh 00:53:23.770 --> 00:53:23.780 align:start position:0% do by uh 00:53:23.780 --> 00:53:27.230 align:start position:0% do by uh misunderstanding<00:53:24.780> well<00:53:25.680> I<00:53:25.859> think<00:53:26.040> I<00:53:26.940> I<00:53:27.059> don't 00:53:27.230 --> 00:53:27.240 align:start position:0% misunderstanding well I think I I don't 00:53:27.240 --> 00:53:29.329 align:start position:0% misunderstanding well I think I I don't know<00:53:27.359> if<00:53:27.480> it<00:53:27.660> goes<00:53:27.900> to<00:53:28.020> like 00:53:29.329 --> 00:53:29.339 align:start position:0% know if it goes to like 00:53:29.339 --> 00:53:31.670 align:start position:0% know if it goes to like the<00:53:29.880> intent<00:53:30.240> of<00:53:30.359> your<00:53:30.540> question<00:53:30.780> having<00:53:31.319> to<00:53:31.559> do 00:53:31.670 --> 00:53:31.680 align:start position:0% the intent of your question having to do 00:53:31.680 --> 00:53:32.990 align:start position:0% the intent of your question having to do with 00:53:32.990 --> 00:53:33.000 align:start position:0% with 00:53:33.000 --> 00:53:35.450 align:start position:0% with structure<00:53:33.660> of<00:53:33.839> code<00:53:34.200> I<00:53:34.800> think<00:53:34.920> we<00:53:35.160> all<00:53:35.280> know 00:53:35.450 --> 00:53:35.460 align:start position:0% structure of code I think we all know 00:53:35.460 --> 00:53:37.910 align:start position:0% structure of code I think we all know we're<00:53:35.940> concerned<00:53:36.599> about 00:53:37.910 --> 00:53:37.920 align:start position:0% we're concerned about 00:53:37.920 --> 00:53:40.069 align:start position:0% we're concerned about regulations<00:53:38.819> that<00:53:39.300> would<00:53:39.480> impose 00:53:40.069 --> 00:53:40.079 align:start position:0% regulations that would impose 00:53:40.079 --> 00:53:42.410 align:start position:0% regulations that would impose requirements<00:53:40.800> on<00:53:41.040> protocols 00:53:42.410 --> 00:53:42.420 align:start position:0% requirements on protocols 00:53:42.420 --> 00:53:44.809 align:start position:0% requirements on protocols to<00:53:42.839> be<00:53:42.900> able<00:53:43.079> to<00:53:43.319> block<00:53:43.559> certain<00:53:44.040> parties<00:53:44.520> as 00:53:44.809 --> 00:53:44.819 align:start position:0% to be able to block certain parties as 00:53:44.819 --> 00:53:48.829 align:start position:0% to be able to block certain parties as an<00:53:45.000> example<00:53:45.359> so<00:53:46.200> I<00:53:46.559> think<00:53:46.680> the<00:53:46.920> biggest 00:53:48.829 --> 00:53:48.839 align:start position:0% an example so I think the biggest 00:53:48.839 --> 00:53:50.930 align:start position:0% an example so I think the biggest a<00:53:49.380> lot<00:53:49.619> of<00:53:49.740> our<00:53:49.859> concerns<00:53:50.460> are<00:53:50.700> around 00:53:50.930 --> 00:53:50.940 align:start position:0% a lot of our concerns are around 00:53:50.940 --> 00:53:52.490 align:start position:0% a lot of our concerns are around regulations<00:53:51.660> that<00:53:52.079> would<00:53:52.200> have<00:53:52.380> a 00:53:52.490 --> 00:53:52.500 align:start position:0% regulations that would have a 00:53:52.500 --> 00:53:54.109 align:start position:0% regulations that would have a requirement<00:53:52.920> so<00:53:53.099> I<00:53:53.280> don't<00:53:53.339> know<00:53:53.460> if<00:53:53.579> that<00:53:53.760> goes 00:53:54.109 --> 00:53:54.119 align:start position:0% requirement so I don't know if that goes 00:53:54.119 --> 00:53:56.390 align:start position:0% requirement so I don't know if that goes to<00:53:54.420> your<00:53:55.079> thought<00:53:55.319> about<00:53:55.559> the<00:53:55.859> question 00:53:56.390 --> 00:53:56.400 align:start position:0% to your thought about the question 00:53:56.400 --> 00:53:58.190 align:start position:0% to your thought about the question having<00:53:56.819> to<00:53:57.059> do<00:53:57.180> with 00:53:58.190 --> 00:53:58.200 align:start position:0% having to do with 00:53:58.200 --> 00:53:59.930 align:start position:0% having to do with specific 00:53:59.930 --> 00:53:59.940 align:start position:0% specific 00:53:59.940 --> 00:54:02.690 align:start position:0% specific processes 00:54:02.690 --> 00:54:02.700 align:start position:0% processes 00:54:02.700 --> 00:54:05.450 align:start position:0% processes your<00:54:03.359> contracts<00:54:03.900> must<00:54:04.079> be<00:54:04.200> upgradable<00:54:04.680> for 00:54:05.450 --> 00:54:05.460 align:start position:0% your contracts must be upgradable for 00:54:05.460 --> 00:54:06.950 align:start position:0% your contracts must be upgradable for whatever<00:54:05.579> reason 00:54:06.950 --> 00:54:06.960 align:start position:0% whatever reason 00:54:06.960 --> 00:54:08.809 align:start position:0% whatever reason those<00:54:07.619> things<00:54:07.800> are<00:54:07.980> always<00:54:08.220> damaging<00:54:08.640> if 00:54:08.809 --> 00:54:08.819 align:start position:0% those things are always damaging if 00:54:08.819 --> 00:54:10.730 align:start position:0% those things are always damaging if you're<00:54:09.180> talking<00:54:09.420> about<00:54:09.540> regulations<00:54:10.079> at<00:54:10.619> the 00:54:10.730 --> 00:54:10.740 align:start position:0% you're talking about regulations at the 00:54:10.740 --> 00:54:12.710 align:start position:0% you're talking about regulations at the code<00:54:10.920> level<00:54:11.160> I<00:54:11.579> think<00:54:11.700> there's<00:54:12.000> no<00:54:12.420> way<00:54:12.540> they 00:54:12.710 --> 00:54:12.720 align:start position:0% code level I think there's no way they 00:54:12.720 --> 00:54:16.309 align:start position:0% code level I think there's no way they can<00:54:12.900> be<00:54:13.020> good<00:54:13.200> you<00:54:13.619> know<00:54:13.740> like<00:54:14.040> I<00:54:14.880> I<00:54:15.180> think<00:54:15.599> that 00:54:16.309 --> 00:54:16.319 align:start position:0% can be good you know like I I think that 00:54:16.319 --> 00:54:19.069 align:start position:0% can be good you know like I I think that um<00:54:16.380> as<00:54:16.740> an<00:54:16.920> example<00:54:17.280> having<00:54:17.700> worked<00:54:18.240> in 00:54:19.069 --> 00:54:19.079 align:start position:0% um as an example having worked in 00:54:19.079 --> 00:54:20.990 align:start position:0% um as an example having worked in uh 00:54:20.990 --> 00:54:21.000 align:start position:0% uh 00:54:21.000 --> 00:54:23.870 align:start position:0% uh security<00:54:21.660> before<00:54:22.140> and<00:54:22.619> in<00:54:22.740> the<00:54:23.040> in<00:54:23.339> the<00:54:23.579> cloud 00:54:23.870 --> 00:54:23.880 align:start position:0% security before and in the in the cloud 00:54:23.880 --> 00:54:25.130 align:start position:0% security before and in the in the cloud space 00:54:25.130 --> 00:54:25.140 align:start position:0% space 00:54:25.140 --> 00:54:27.250 align:start position:0% space the<00:54:25.559> sock<00:54:25.800> 2<00:54:26.099> standard 00:54:27.250 --> 00:54:27.260 align:start position:0% the sock 2 standard 00:54:27.260 --> 00:54:30.890 align:start position:0% the sock 2 standard and<00:54:28.260> actually<00:54:28.940> I<00:54:29.940> believe<00:54:30.059> it<00:54:30.300> has<00:54:30.480> a<00:54:30.720> lot<00:54:30.780> of 00:54:30.890 --> 00:54:30.900 align:start position:0% and actually I believe it has a lot of 00:54:30.900 --> 00:54:33.770 align:start position:0% and actually I believe it has a lot of really<00:54:31.200> good<00:54:31.440> aspects<00:54:32.160> to<00:54:33.059> the<00:54:33.480> software 00:54:33.770 --> 00:54:33.780 align:start position:0% really good aspects to the software 00:54:33.780 --> 00:54:37.010 align:start position:0% really good aspects to the software development<00:54:34.260> the<00:54:34.619> secure<00:54:35.160> security<00:54:36.020> focused 00:54:37.010 --> 00:54:37.020 align:start position:0% development the secure security focused 00:54:37.020 --> 00:54:38.870 align:start position:0% development the secure security focused processes<00:54:37.619> of<00:54:37.859> your<00:54:38.040> software<00:54:38.400> development 00:54:38.870 --> 00:54:38.880 align:start position:0% processes of your software development 00:54:38.880 --> 00:54:41.030 align:start position:0% processes of your software development life<00:54:39.180> cycle<00:54:39.480> and<00:54:40.200> I<00:54:40.319> think<00:54:40.440> those<00:54:40.619> are<00:54:40.800> good 00:54:41.030 --> 00:54:41.040 align:start position:0% life cycle and I think those are good 00:54:41.040 --> 00:54:42.650 align:start position:0% life cycle and I think those are good practices<00:54:41.460> and<00:54:41.940> if 00:54:42.650 --> 00:54:42.660 align:start position:0% practices and if 00:54:42.660 --> 00:54:44.930 align:start position:0% practices and if teams<00:54:43.500> were<00:54:43.740> transparent<00:54:44.339> about<00:54:44.640> the 00:54:44.930 --> 00:54:44.940 align:start position:0% teams were transparent about the 00:54:44.940 --> 00:54:47.329 align:start position:0% teams were transparent about the processes<00:54:45.420> they<00:54:45.839> follow<00:54:46.079> I<00:54:46.740> think<00:54:47.099> that's 00:54:47.329 --> 00:54:47.339 align:start position:0% processes they follow I think that's 00:54:47.339 --> 00:54:49.370 align:start position:0% processes they follow I think that's healthy<00:54:47.760> and<00:54:48.059> if<00:54:48.300> held<00:54:48.900> to<00:54:49.020> a<00:54:49.200> certain 00:54:49.370 --> 00:54:49.380 align:start position:0% healthy and if held to a certain 00:54:49.380 --> 00:54:51.950 align:start position:0% healthy and if held to a certain standard<00:54:50.339> all<00:54:50.880> those<00:54:51.059> things<00:54:51.240> always<00:54:51.660> have 00:54:51.950 --> 00:54:51.960 align:start position:0% standard all those things always have 00:54:51.960 --> 00:54:54.230 align:start position:0% standard all those things always have downsides<00:54:52.740> in<00:54:52.980> terms<00:54:53.280> of<00:54:53.339> the<00:54:53.640> effort<00:54:54.059> that 00:54:54.230 --> 00:54:54.240 align:start position:0% downsides in terms of the effort that 00:54:54.240 --> 00:54:57.290 align:start position:0% downsides in terms of the effort that goes<00:54:54.540> into<00:54:54.680> auditing<00:54:55.680> them<00:54:55.920> and<00:54:56.339> proving<00:54:57.059> them 00:54:57.290 --> 00:54:57.300 align:start position:0% goes into auditing them and proving them 00:54:57.300 --> 00:54:59.510 align:start position:0% goes into auditing them and proving them but<00:54:57.599> yeah<00:54:57.839> the<00:54:58.200> life<00:54:58.500> cycle<00:54:58.740> of<00:54:58.920> Regulation<00:54:59.339> is 00:54:59.510 --> 00:54:59.520 align:start position:0% but yeah the life cycle of Regulation is 00:54:59.520 --> 00:55:00.890 align:start position:0% but yeah the life cycle of Regulation is really<00:54:59.700> tough 00:55:00.890 --> 00:55:00.900 align:start position:0% really tough 00:55:00.900 --> 00:55:03.349 align:start position:0% really tough um<00:55:00.960> getting<00:55:01.319> getting<00:55:01.880> regulators<00:55:02.880> and 00:55:03.349 --> 00:55:03.359 align:start position:0% um getting getting regulators and 00:55:03.359 --> 00:55:05.870 align:start position:0% um getting getting regulators and government<00:55:03.660> officials<00:55:04.140> to<00:55:04.380> understand<00:55:04.880> the 00:55:05.870 --> 00:55:05.880 align:start position:0% government officials to understand the 00:55:05.880 --> 00:55:07.250 align:start position:0% government officials to understand the key<00:55:06.180> areas 00:55:07.250 --> 00:55:07.260 align:start position:0% key areas 00:55:07.260 --> 00:55:09.230 align:start position:0% key areas they<00:55:07.980> have<00:55:08.400> a<00:55:08.520> goal<00:55:08.760> of<00:55:08.819> what<00:55:08.940> they<00:55:09.059> want<00:55:09.180> to 00:55:09.230 --> 00:55:09.240 align:start position:0% they have a goal of what they want to 00:55:09.240 --> 00:55:11.329 align:start position:0% they have a goal of what they want to accomplish<00:55:09.599> but<00:55:10.380> usually<00:55:10.680> they're<00:55:11.099> they're 00:55:11.329 --> 00:55:11.339 align:start position:0% accomplish but usually they're they're 00:55:11.339 --> 00:55:13.790 align:start position:0% accomplish but usually they're they're rather<00:55:11.640> far<00:55:11.880> behind<00:55:12.180> the<00:55:12.480> technology<00:55:12.900> I<00:55:13.680> think 00:55:13.790 --> 00:55:13.800 align:start position:0% rather far behind the technology I think 00:55:13.800 --> 00:55:15.349 align:start position:0% rather far behind the technology I think it's<00:55:13.920> up<00:55:14.099> to<00:55:14.220> us<00:55:14.339> everybody<00:55:14.760> here<00:55:15.180> we 00:55:15.349 --> 00:55:15.359 align:start position:0% it's up to us everybody here we 00:55:15.359 --> 00:55:16.910 align:start position:0% it's up to us everybody here we certainly<00:55:15.599> do<00:55:15.780> this<00:55:15.900> I<00:55:16.140> bet<00:55:16.440> everybody<00:55:16.619> else 00:55:16.910 --> 00:55:16.920 align:start position:0% certainly do this I bet everybody else 00:55:16.920 --> 00:55:18.650 align:start position:0% certainly do this I bet everybody else up<00:55:17.160> here<00:55:17.339> does<00:55:17.520> this<00:55:17.700> we<00:55:18.059> spend<00:55:18.300> a<00:55:18.420> lot<00:55:18.480> of<00:55:18.540> time 00:55:18.650 --> 00:55:18.660 align:start position:0% up here does this we spend a lot of time 00:55:18.660 --> 00:55:20.030 align:start position:0% up here does this we spend a lot of time talking<00:55:18.839> to<00:55:19.079> Regulators<00:55:19.440> about<00:55:19.619> what<00:55:19.920> is 00:55:20.030 --> 00:55:20.040 align:start position:0% talking to Regulators about what is 00:55:20.040 --> 00:55:21.650 align:start position:0% talking to Regulators about what is possible<00:55:20.339> and<00:55:20.460> what<00:55:20.640> isn't<00:55:20.940> we<00:55:21.240> spent<00:55:21.480> a<00:55:21.540> lot 00:55:21.650 --> 00:55:21.660 align:start position:0% possible and what isn't we spent a lot 00:55:21.660 --> 00:55:24.109 align:start position:0% possible and what isn't we spent a lot of<00:55:21.720> time<00:55:21.839> talking<00:55:22.020> about<00:55:22.380> the<00:55:23.160> intent<00:55:23.520> and 00:55:24.109 --> 00:55:24.119 align:start position:0% of time talking about the intent and 00:55:24.119 --> 00:55:26.150 align:start position:0% of time talking about the intent and trying<00:55:24.300> to<00:55:24.480> come<00:55:24.599> up<00:55:24.720> with<00:55:24.900> sort<00:55:25.140> of<00:55:25.260> more<00:55:25.680> more 00:55:26.150 --> 00:55:26.160 align:start position:0% trying to come up with sort of more more 00:55:26.160 --> 00:55:28.970 align:start position:0% trying to come up with sort of more more open<00:55:26.720> suggestions<00:55:27.720> to<00:55:28.140> Industry<00:55:28.500> as<00:55:28.680> opposed 00:55:28.970 --> 00:55:28.980 align:start position:0% open suggestions to Industry as opposed 00:55:28.980 --> 00:55:30.890 align:start position:0% open suggestions to Industry as opposed to<00:55:29.040> specific<00:55:29.520> because<00:55:29.760> if<00:55:30.000> if<00:55:30.180> you<00:55:30.420> say<00:55:30.540> thou 00:55:30.890 --> 00:55:30.900 align:start position:0% to specific because if if you say thou 00:55:30.900 --> 00:55:33.170 align:start position:0% to specific because if if you say thou shalt<00:55:31.260> do<00:55:31.440> the<00:55:31.680> following<00:55:32.160> it's<00:55:32.700> always<00:55:32.940> going 00:55:33.170 --> 00:55:33.180 align:start position:0% shalt do the following it's always going 00:55:33.180 --> 00:55:35.089 align:start position:0% shalt do the following it's always going to<00:55:33.359> be<00:55:33.420> out<00:55:33.540> of<00:55:33.660> date<00:55:33.780> by<00:55:34.020> the<00:55:34.140> time<00:55:34.260> it<00:55:34.500> passes 00:55:35.089 --> 00:55:35.099 align:start position:0% to be out of date by the time it passes 00:55:35.099 --> 00:55:36.950 align:start position:0% to be out of date by the time it passes and<00:55:35.760> and<00:55:35.940> it<00:55:36.180> just<00:55:36.240> becomes<00:55:36.599> very<00:55:36.780> very 00:55:36.950 --> 00:55:36.960 align:start position:0% and and it just becomes very very 00:55:36.960 --> 00:55:39.410 align:start position:0% and and it just becomes very very difficult<00:55:37.380> so<00:55:37.980> I<00:55:38.099> think<00:55:38.220> that<00:55:38.400> the<00:55:38.880> best<00:55:39.240> thing 00:55:39.410 --> 00:55:39.420 align:start position:0% difficult so I think that the best thing 00:55:39.420 --> 00:55:40.670 align:start position:0% difficult so I think that the best thing that<00:55:39.599> we<00:55:39.660> can<00:55:39.780> do<00:55:39.839> the<00:55:40.020> most<00:55:40.200> practical<00:55:40.440> thing 00:55:40.670 --> 00:55:40.680 align:start position:0% that we can do the most practical thing 00:55:40.680 --> 00:55:42.650 align:start position:0% that we can do the most practical thing we<00:55:40.800> can<00:55:40.920> do<00:55:40.980> is<00:55:41.099> educate<00:55:41.640> those<00:55:42.240> those<00:55:42.420> people 00:55:42.650 --> 00:55:42.660 align:start position:0% we can do is educate those those people 00:55:42.660 --> 00:55:44.510 align:start position:0% we can do is educate those those people who<00:55:42.960> would<00:55:43.079> regulate<00:55:43.500> us<00:55:43.619> thanks<00:55:44.339> for 00:55:44.510 --> 00:55:44.520 align:start position:0% who would regulate us thanks for 00:55:44.520 --> 00:55:46.790 align:start position:0% who would regulate us thanks for clarifying<00:55:45.119> Brian<00:55:45.300> uh<00:55:46.079> yeah<00:55:46.260> that<00:55:46.500> makes<00:55:46.680> a 00:55:46.790 --> 00:55:46.800 align:start position:0% clarifying Brian uh yeah that makes a 00:55:46.800 --> 00:55:48.049 align:start position:0% clarifying Brian uh yeah that makes a lot<00:55:46.920> more<00:55:47.040> sense 00:55:48.049 --> 00:55:48.059 align:start position:0% lot more sense 00:55:48.059 --> 00:55:50.630 align:start position:0% lot more sense um<00:55:48.180> just<00:55:48.660> to<00:55:48.839> give<00:55:48.960> you<00:55:49.079> guys<00:55:49.200> maybe<00:55:49.380> an<00:55:50.220> exotic 00:55:50.630 --> 00:55:50.640 align:start position:0% um just to give you guys maybe an exotic 00:55:50.640 --> 00:55:53.329 align:start position:0% um just to give you guys maybe an exotic perspective<00:55:51.540> I<00:55:52.140> was<00:55:52.260> catching<00:55:52.559> up<00:55:52.680> with<00:55:53.040> some 00:55:53.329 --> 00:55:53.339 align:start position:0% perspective I was catching up with some 00:55:53.339 --> 00:55:55.309 align:start position:0% perspective I was catching up with some of<00:55:53.460> the<00:55:53.579> Regulators<00:55:54.000> in<00:55:54.240> Australia<00:55:54.900> a<00:55:55.200> few 00:55:55.309 --> 00:55:55.319 align:start position:0% of the Regulators in Australia a few 00:55:55.319 --> 00:55:58.250 align:start position:0% of the Regulators in Australia a few weeks<00:55:55.619> ago<00:55:55.819> and<00:55:56.819> this<00:55:57.000> is<00:55:57.180> exactly<00:55:57.660> what<00:55:58.140> they 00:55:58.250 --> 00:55:58.260 align:start position:0% weeks ago and this is exactly what they 00:55:58.260 --> 00:56:00.829 align:start position:0% weeks ago and this is exactly what they were<00:55:58.380> asking<00:55:58.680> for<00:55:58.859> they<00:55:59.460> said<00:55:59.700> what<00:56:00.420> should<00:56:00.660> we 00:56:00.829 --> 00:56:00.839 align:start position:0% were asking for they said what should we 00:56:00.839 --> 00:56:03.950 align:start position:0% were asking for they said what should we be<00:56:01.079> you<00:56:01.619> know<00:56:01.680> requesting<00:56:02.640> from<00:56:03.000> projects<00:56:03.660> to 00:56:03.950 --> 00:56:03.960 align:start position:0% be you know requesting from projects to 00:56:03.960 --> 00:56:07.010 align:start position:0% be you know requesting from projects to do<00:56:04.680> in<00:56:04.920> terms<00:56:05.160> of<00:56:05.280> security<00:56:05.780> practices<00:56:06.780> in 00:56:07.010 --> 00:56:07.020 align:start position:0% do in terms of security practices in 00:56:07.020 --> 00:56:09.109 align:start position:0% do in terms of security practices in terms<00:56:07.140> of<00:56:07.260> security<00:56:07.740> development<00:56:08.400> secure 00:56:09.109 --> 00:56:09.119 align:start position:0% terms of security development secure 00:56:09.119 --> 00:56:10.150 align:start position:0% terms of security development secure development 00:56:10.150 --> 00:56:10.160 align:start position:0% development 00:56:10.160 --> 00:56:12.589 align:start position:0% development and<00:56:11.160> you<00:56:11.520> know<00:56:11.579> what<00:56:12.119> should<00:56:12.300> we<00:56:12.420> be 00:56:12.589 --> 00:56:12.599 align:start position:0% and you know what should we be 00:56:12.599 --> 00:56:16.069 align:start position:0% and you know what should we be regulating<00:56:13.079> in<00:56:13.319> the<00:56:13.440> space<00:56:13.559> so<00:56:14.040> I<00:56:15.000> try<00:56:15.480> to<00:56:15.660> sort 00:56:16.069 --> 00:56:16.079 align:start position:0% regulating in the space so I try to sort 00:56:16.079 --> 00:56:17.390 align:start position:0% regulating in the space so I try to sort of<00:56:16.140> convince<00:56:16.500> them<00:56:16.680> to<00:56:16.859> go<00:56:16.980> down<00:56:17.160> the 00:56:17.390 --> 00:56:17.400 align:start position:0% of convince them to go down the 00:56:17.400 --> 00:56:20.690 align:start position:0% of convince them to go down the educational<00:56:17.819> part<00:56:18.300> and<00:56:19.619> um<00:56:19.680> and<00:56:20.099> yeah<00:56:20.280> this<00:56:20.579> is 00:56:20.690 --> 00:56:20.700 align:start position:0% educational part and um and yeah this is 00:56:20.700 --> 00:56:22.069 align:start position:0% educational part and um and yeah this is this<00:56:20.880> is<00:56:21.000> spot<00:56:21.180> on<00:56:21.359> I<00:56:21.540> think<00:56:21.660> it's<00:56:21.839> certainly 00:56:22.069 --> 00:56:22.079 align:start position:0% this is spot on I think it's certainly 00:56:22.079 --> 00:56:24.589 align:start position:0% this is spot on I think it's certainly something<00:56:22.380> that<00:56:22.740> is<00:56:23.000> happening<00:56:24.000> at<00:56:24.300> least<00:56:24.420> in 00:56:24.589 --> 00:56:24.599 align:start position:0% something that is happening at least in 00:56:24.599 --> 00:56:26.329 align:start position:0% something that is happening at least in Australia<00:56:25.020> these<00:56:25.440> people<00:56:25.859> are<00:56:26.160> starting 00:56:26.329 --> 00:56:26.339 align:start position:0% Australia these people are starting 00:56:26.339 --> 00:56:28.309 align:start position:0% Australia these people are starting these<00:56:26.760> conversations<00:56:27.119> and<00:56:27.720> are<00:56:27.839> starting<00:56:28.079> to 00:56:28.309 --> 00:56:28.319 align:start position:0% these conversations and are starting to 00:56:28.319 --> 00:56:31.130 align:start position:0% these conversations and are starting to realize<00:56:28.619> the<00:56:28.980> need<00:56:29.160> of<00:56:29.640> you<00:56:30.599> you<00:56:30.780> can't 00:56:31.130 --> 00:56:31.140 align:start position:0% realize the need of you you can't 00:56:31.140 --> 00:56:33.410 align:start position:0% realize the need of you you can't enforce<00:56:31.740> these<00:56:32.040> things<00:56:32.220> on<00:56:32.640> projects<00:56:33.059> but<00:56:33.300> at 00:56:33.410 --> 00:56:33.420 align:start position:0% enforce these things on projects but at 00:56:33.420 --> 00:56:34.490 align:start position:0% enforce these things on projects but at least<00:56:33.540> you<00:56:33.720> can<00:56:33.839> have<00:56:33.960> these<00:56:34.200> set<00:56:34.380> of 00:56:34.490 --> 00:56:34.500 align:start position:0% least you can have these set of 00:56:34.500 --> 00:56:38.569 align:start position:0% least you can have these set of guidelines<00:56:35.119> and<00:56:36.119> point<00:56:36.540> your<00:56:36.900> users<00:56:37.619> your<00:56:38.339> you 00:56:38.569 --> 00:56:38.579 align:start position:0% guidelines and point your users your you 00:56:38.579 --> 00:56:40.849 align:start position:0% guidelines and point your users your you know<00:56:38.700> citizens<00:56:39.119> to<00:56:39.480> these<00:56:39.900> guidelines<00:56:40.200> and 00:56:40.849 --> 00:56:40.859 align:start position:0% know citizens to these guidelines and 00:56:40.859 --> 00:56:43.309 align:start position:0% know citizens to these guidelines and get<00:56:41.040> them<00:56:41.220> to<00:56:41.520> demand<00:56:42.000> these<00:56:42.480> standards<00:56:42.960> these 00:56:43.309 --> 00:56:43.319 align:start position:0% get them to demand these standards these 00:56:43.319 --> 00:56:46.430 align:start position:0% get them to demand these standards these set<00:56:43.440> of<00:56:43.819> minimum<00:56:44.819> requirements<00:56:45.720> from<00:56:46.260> the 00:56:46.430 --> 00:56:46.440 align:start position:0% set of minimum requirements from the 00:56:46.440 --> 00:56:48.589 align:start position:0% set of minimum requirements from the projects<00:56:46.800> they<00:56:46.980> interact<00:56:47.280> with 00:56:48.589 --> 00:56:48.599 align:start position:0% projects they interact with 00:56:48.599 --> 00:56:49.930 align:start position:0% projects they interact with thank<00:56:49.260> you 00:56:49.930 --> 00:56:49.940 align:start position:0% thank you 00:56:49.940 --> 00:56:54.880 align:start position:0% thank you [Applause]