WEBVTT Kind: captions Language: en 00:00:00.030 --> 00:00:03.409 align:start position:0% alright<00:00:00.960> hey<00:00:01.439> everybody<00:00:01.790> welcome<00:00:02.790> to<00:00:02.939> the<00:00:03.090> end 00:00:03.409 --> 00:00:03.419 align:start position:0% alright hey everybody welcome to the end 00:00:03.419 --> 00:00:07.579 align:start position:0% alright hey everybody welcome to the end of<00:00:03.629> day<00:00:04.080> 2<00:00:04.140> now<00:00:05.009> for<00:00:05.310> DEFCON<00:00:06.440> thanks<00:00:07.440> for 00:00:07.579 --> 00:00:07.589 align:start position:0% of day 2 now for DEFCON thanks for 00:00:07.589 --> 00:00:09.680 align:start position:0% of day 2 now for DEFCON thanks for sticking<00:00:07.890> it<00:00:07.950> out<00:00:08.040> with<00:00:08.099> us<00:00:08.480> we're<00:00:09.480> just<00:00:09.510> gonna 00:00:09.680 --> 00:00:09.690 align:start position:0% sticking it out with us we're just gonna 00:00:09.690 --> 00:00:13.160 align:start position:0% sticking it out with us we're just gonna have<00:00:10.440> a<00:00:10.469> conversation<00:00:10.950> about<00:00:11.400> current<00:00:12.170> state 00:00:13.160 --> 00:00:13.170 align:start position:0% have a conversation about current state 00:00:13.170 --> 00:00:16.220 align:start position:0% have a conversation about current state of<00:00:13.200> security<00:00:13.710> in<00:00:13.830> aetherium<00:00:14.929> we're<00:00:15.929> gonna<00:00:16.020> do 00:00:16.220 --> 00:00:16.230 align:start position:0% of security in aetherium we're gonna do 00:00:16.230 --> 00:00:19.849 align:start position:0% of security in aetherium we're gonna do about<00:00:16.410> 25<00:00:17.310> 20<00:00:18.300> 25<00:00:18.630> minutes<00:00:18.900> of<00:00:19.080> questions<00:00:19.590> here 00:00:19.849 --> 00:00:19.859 align:start position:0% about 25 20 25 minutes of questions here 00:00:19.859 --> 00:00:21.140 align:start position:0% about 25 20 25 minutes of questions here and<00:00:19.949> then<00:00:20.070> we'll<00:00:20.310> take<00:00:20.730> some<00:00:20.760> questions<00:00:20.880> from 00:00:21.140 --> 00:00:21.150 align:start position:0% and then we'll take some questions from 00:00:21.150 --> 00:00:25.130 align:start position:0% and then we'll take some questions from the<00:00:21.300> crowd<00:00:21.390> so<00:00:23.449> first<00:00:24.449> I<00:00:24.539> guess<00:00:24.689> maybe<00:00:24.930> we'll 00:00:25.130 --> 00:00:25.140 align:start position:0% the crowd so first I guess maybe we'll 00:00:25.140 --> 00:00:26.599 align:start position:0% the crowd so first I guess maybe we'll introduce<00:00:25.380> ourselves<00:00:25.710> you<00:00:26.130> guys<00:00:26.250> want<00:00:26.460> to<00:00:26.519> go 00:00:26.599 --> 00:00:26.609 align:start position:0% introduce ourselves you guys want to go 00:00:26.609 --> 00:00:27.230 align:start position:0% introduce ourselves you guys want to go down<00:00:26.760> the<00:00:26.849> line 00:00:27.230 --> 00:00:27.240 align:start position:0% down the line 00:00:27.240 --> 00:00:29.359 align:start position:0% down the line I'm<00:00:27.810> just<00:00:27.960> saying<00:00:28.080> who<00:00:28.140> you<00:00:28.199> are<00:00:28.410> and<00:00:28.710> what's 00:00:29.359 --> 00:00:29.369 align:start position:0% I'm just saying who you are and what's 00:00:29.369 --> 00:00:32.720 align:start position:0% I'm just saying who you are and what's your<00:00:29.580> what<00:00:29.789> you're<00:00:29.910> doing<00:00:30.920> alright 00:00:32.720 --> 00:00:32.730 align:start position:0% your what you're doing alright 00:00:32.730 --> 00:00:35.450 align:start position:0% your what you're doing alright I'm<00:00:33.329> Martin<00:00:33.840> Olsen<00:00:33.930> spandy<00:00:34.500> and<00:00:34.770> I<00:00:35.010> work<00:00:35.160> as 00:00:35.450 --> 00:00:35.460 align:start position:0% I'm Martin Olsen spandy and I work as 00:00:35.460 --> 00:00:37.760 align:start position:0% I'm Martin Olsen spandy and I work as the<00:00:35.850> security<00:00:36.809> lead<00:00:36.960> for<00:00:37.200> the<00:00:37.320> Theorem 00:00:37.760 --> 00:00:37.770 align:start position:0% the security lead for the Theorem 00:00:37.770 --> 00:00:41.810 align:start position:0% the security lead for the Theorem Foundation<00:00:38.370> and<00:00:39.800> also<00:00:40.800> work<00:00:40.980> at<00:00:41.219> gas 00:00:41.810 --> 00:00:41.820 align:start position:0% Foundation and also work at gas 00:00:41.820 --> 00:00:46.069 align:start position:0% Foundation and also work at gas developments<00:00:43.550> I'm<00:00:44.550> Phil<00:00:44.940> Diane<00:00:45.329> I<00:00:45.600> am<00:00:45.690> at 00:00:46.069 --> 00:00:46.079 align:start position:0% developments I'm Phil Diane I am at 00:00:46.079 --> 00:00:47.690 align:start position:0% developments I'm Phil Diane I am at Cornell<00:00:46.410> University<00:00:46.440> and<00:00:47.010> I<00:00:47.070> see<00:00:47.250> three<00:00:47.489> I'm<00:00:47.670> a 00:00:47.690 --> 00:00:47.700 align:start position:0% Cornell University and I see three I'm a 00:00:47.700 --> 00:00:49.790 align:start position:0% Cornell University and I see three I'm a PhD<00:00:48.059> student<00:00:48.600> working<00:00:48.719> on<00:00:48.989> smart<00:00:49.350> contract 00:00:49.790 --> 00:00:49.800 align:start position:0% PhD student working on smart contract 00:00:49.800 --> 00:00:53.569 align:start position:0% PhD student working on smart contract security<00:00:50.870> I'm<00:00:51.870> Matthew<00:00:52.379> D<00:00:52.620> Ferrante<00:00:53.100> I<00:00:53.129> am<00:00:53.399> the 00:00:53.569 --> 00:00:53.579 align:start position:0% security I'm Matthew D Ferrante I am the 00:00:53.579 --> 00:00:55.910 align:start position:0% security I'm Matthew D Ferrante I am the founder<00:00:54.030> of<00:00:54.059> Zika<00:00:54.329> labs<00:00:54.510> he<00:00:55.199> theorem<00:00:55.530> focused 00:00:55.910 --> 00:00:55.920 align:start position:0% founder of Zika labs he theorem focused 00:00:55.920 --> 00:00:59.420 align:start position:0% founder of Zika labs he theorem focused auditing<00:00:56.520> firm<00:00:56.730> and<00:00:56.969> also<00:00:57.770> cartographer<00:00:58.770> I'd 00:00:59.420 --> 00:00:59.430 align:start position:0% auditing firm and also cartographer I'd 00:00:59.430 --> 00:01:01.639 align:start position:0% auditing firm and also cartographer I'd you<00:00:59.760> know<00:00:59.850> by<00:01:00.300> implementation<00:01:00.840> I<00:01:00.930> do<00:01:00.989> if<00:01:01.289> he 00:01:01.639 --> 00:01:01.649 align:start position:0% you know by implementation I do if he 00:01:01.649 --> 00:01:04.479 align:start position:0% you know by implementation I do if he cryptography<00:01:02.640> related<00:01:02.940> things<00:01:03.059> on<00:01:03.149> the<00:01:03.239> side 00:01:04.479 --> 00:01:04.489 align:start position:0% cryptography related things on the side 00:01:04.489 --> 00:01:07.130 align:start position:0% cryptography related things on the side I'm<00:01:05.489> brilliant<00:01:05.790> a<00:01:06.119> founding<00:01:06.780> member<00:01:06.840> of 00:01:07.130 --> 00:01:07.140 align:start position:0% I'm brilliant a founding member of 00:01:07.140 --> 00:01:09.590 align:start position:0% I'm brilliant a founding member of consensus<00:01:07.979> diligence<00:01:08.549> and<00:01:08.880> a<00:01:09.210> smart<00:01:09.450> contract 00:01:09.590 --> 00:01:09.600 align:start position:0% consensus diligence and a smart contract 00:01:09.600 --> 00:01:13.820 align:start position:0% consensus diligence and a smart contract auditor<00:01:11.360> hey<00:01:12.360> I'm<00:01:12.479> Dan<00:01:12.720> Guido<00:01:13.020> the<00:01:13.200> co-founder 00:01:13.820 --> 00:01:13.830 align:start position:0% auditor hey I'm Dan Guido the co-founder 00:01:13.830 --> 00:01:15.859 align:start position:0% auditor hey I'm Dan Guido the co-founder and<00:01:13.860> CEO<00:01:14.100> of<00:01:14.430> trilobites<00:01:14.750> software<00:01:15.750> security 00:01:15.859 --> 00:01:15.869 align:start position:0% and CEO of trilobites software security 00:01:15.869 --> 00:01:19.190 align:start position:0% and CEO of trilobites software security research<00:01:16.409> development<00:01:16.920> firm<00:01:17.780> awesome<00:01:18.780> thanks 00:01:19.190 --> 00:01:19.200 align:start position:0% research development firm awesome thanks 00:01:19.200 --> 00:01:20.179 align:start position:0% research development firm awesome thanks guys 00:01:20.179 --> 00:01:20.189 align:start position:0% guys 00:01:20.189 --> 00:01:21.679 align:start position:0% guys so<00:01:20.640> we're<00:01:20.729> gonna<00:01:20.820> start<00:01:21.360> it<00:01:21.420> off<00:01:21.479> with<00:01:21.540> a 00:01:21.679 --> 00:01:21.689 align:start position:0% so we're gonna start it off with a 00:01:21.689 --> 00:01:23.840 align:start position:0% so we're gonna start it off with a softball<00:01:22.110> and<00:01:22.320> what's<00:01:23.009> the<00:01:23.130> biggest<00:01:23.520> change 00:01:23.840 --> 00:01:23.850 align:start position:0% softball and what's the biggest change 00:01:23.850 --> 00:01:28.270 align:start position:0% softball and what's the biggest change in<00:01:24.090> aetherium<00:01:24.360> security<00:01:24.900> in<00:01:25.020> the<00:01:25.110> last<00:01:25.320> year 00:01:28.270 --> 00:01:28.280 align:start position:0% 00:01:28.280 --> 00:01:32.210 align:start position:0% so<00:01:29.299> I'll<00:01:30.299> take<00:01:30.509> it<00:01:30.630> first<00:01:30.810> yeah<00:01:30.990> I<00:01:31.860> think 00:01:32.210 --> 00:01:32.220 align:start position:0% so I'll take it first yeah I think 00:01:32.220 --> 00:01:33.230 align:start position:0% so I'll take it first yeah I think there's<00:01:32.430> been<00:01:32.549> a<00:01:32.579> couple<00:01:32.759> of<00:01:32.909> things<00:01:33.060> I've 00:01:33.230 --> 00:01:33.240 align:start position:0% there's been a couple of things I've 00:01:33.240 --> 00:01:35.749 align:start position:0% there's been a couple of things I've noticed<00:01:33.380> the<00:01:34.380> first<00:01:34.619> is<00:01:34.979> that<00:01:35.159> the<00:01:35.430> soluti 00:01:35.749 --> 00:01:35.759 align:start position:0% noticed the first is that the soluti 00:01:35.759 --> 00:01:37.910 align:start position:0% noticed the first is that the soluti compiler<00:01:36.060> itself<00:01:36.270> is<00:01:36.810> a<00:01:37.200> little<00:01:37.439> bit<00:01:37.530> less<00:01:37.740> on 00:01:37.910 --> 00:01:37.920 align:start position:0% compiler itself is a little bit less on 00:01:37.920 --> 00:01:41.149 align:start position:0% compiler itself is a little bit less on fire<00:01:38.310> today<00:01:38.670> than<00:01:39.000> it<00:01:39.119> was<00:01:39.150> a<00:01:39.329> year<00:01:39.509> ago<00:01:40.159> there 00:01:41.149 --> 00:01:41.159 align:start position:0% fire today than it was a year ago there 00:01:41.159 --> 00:01:42.530 align:start position:0% fire today than it was a year ago there are<00:01:41.189> certain<00:01:41.759> patterns<00:01:41.909> that<00:01:42.329> we<00:01:42.450> had 00:01:42.530 --> 00:01:42.540 align:start position:0% are certain patterns that we had 00:01:42.540 --> 00:01:43.880 align:start position:0% are certain patterns that we had implemented<00:01:42.869> in<00:01:43.140> our<00:01:43.229> own<00:01:43.350> static<00:01:43.710> analysis 00:01:43.880 --> 00:01:43.890 align:start position:0% implemented in our own static analysis 00:01:43.890 --> 00:01:46.069 align:start position:0% implemented in our own static analysis tools<00:01:44.340> that<00:01:45.000> have<00:01:45.119> been<00:01:45.149> deprecated<00:01:45.689> because 00:01:46.069 --> 00:01:46.079 align:start position:0% tools that have been deprecated because 00:01:46.079 --> 00:01:48.499 align:start position:0% tools that have been deprecated because the<00:01:46.320> compiler<00:01:46.619> now<00:01:47.549> checks<00:01:47.880> for<00:01:48.030> those<00:01:48.149> issues 00:01:48.499 --> 00:01:48.509 align:start position:0% the compiler now checks for those issues 00:01:48.509 --> 00:01:51.289 align:start position:0% the compiler now checks for those issues things<00:01:48.930> like<00:01:49.310> the<00:01:50.310> constructor<00:01:50.850> being<00:01:51.180> the 00:01:51.289 --> 00:01:51.299 align:start position:0% things like the constructor being the 00:01:51.299 --> 00:01:53.359 align:start position:0% things like the constructor being the same<00:01:51.509> name<00:01:51.750> as<00:01:51.899> the<00:01:51.930> contract<00:01:52.470> and<00:01:52.680> having 00:01:53.359 --> 00:01:53.369 align:start position:0% same name as the contract and having 00:01:53.369 --> 00:01:56.660 align:start position:0% same name as the contract and having divergences<00:01:54.210> of<00:01:54.360> those<00:01:54.509> two<00:01:55.460> allowing<00:01:56.460> you<00:01:56.579> to 00:01:56.660 --> 00:01:56.670 align:start position:0% divergences of those two allowing you to 00:01:56.670 --> 00:01:58.420 align:start position:0% divergences of those two allowing you to exploit<00:01:57.030> you<00:01:57.240> know<00:01:57.329> on<00:01:57.479> an<00:01:57.570> uninitialized 00:01:58.420 --> 00:01:58.430 align:start position:0% exploit you know on an uninitialized 00:01:58.430 --> 00:02:01.660 align:start position:0% exploit you know on an uninitialized contracts<00:01:59.430> and<00:01:59.670> variables<00:02:00.420> within<00:02:00.600> them 00:02:01.660 --> 00:02:01.670 align:start position:0% contracts and variables within them 00:02:01.670 --> 00:02:03.499 align:start position:0% contracts and variables within them another<00:02:02.670> thing<00:02:02.850> that<00:02:03.030> I<00:02:03.060> think<00:02:03.270> is<00:02:03.360> pretty 00:02:03.499 --> 00:02:03.509 align:start position:0% another thing that I think is pretty 00:02:03.509 --> 00:02:06.440 align:start position:0% another thing that I think is pretty unique<00:02:03.840> is<00:02:04.079> that<00:02:04.350> a<00:02:05.070> lot<00:02:05.850> of<00:02:05.939> the<00:02:06.030> less<00:02:06.210> serious 00:02:06.440 --> 00:02:06.450 align:start position:0% unique is that a lot of the less serious 00:02:06.450 --> 00:02:07.850 align:start position:0% unique is that a lot of the less serious people<00:02:06.960> have<00:02:07.110> dropped<00:02:07.320> out<00:02:07.500> of<00:02:07.619> the<00:02:07.680> community 00:02:07.850 --> 00:02:07.860 align:start position:0% people have dropped out of the community 00:02:07.860 --> 00:02:11.690 align:start position:0% people have dropped out of the community so<00:02:08.580> the<00:02:08.700> post<00:02:08.910> ICO<00:02:09.360> kind<00:02:10.289> of<00:02:10.379> field<00:02:11.160> of<00:02:11.400> people 00:02:11.690 --> 00:02:11.700 align:start position:0% so the post ICO kind of field of people 00:02:11.700 --> 00:02:13.160 align:start position:0% so the post ICO kind of field of people that<00:02:11.879> are<00:02:11.970> left<00:02:12.180> now<00:02:12.420> are<00:02:12.690> a<00:02:12.720> lot<00:02:12.900> more 00:02:13.160 --> 00:02:13.170 align:start position:0% that are left now are a lot more 00:02:13.170 --> 00:02:14.839 align:start position:0% that are left now are a lot more serious<00:02:13.530> about<00:02:13.770> developing<00:02:13.950> applications 00:02:14.839 --> 00:02:14.849 align:start position:0% serious about developing applications 00:02:14.849 --> 00:02:17.120 align:start position:0% serious about developing applications that<00:02:15.000> work<00:02:15.209> and<00:02:16.200> I<00:02:16.290> think<00:02:16.380> that<00:02:16.530> shift<00:02:16.950> in 00:02:17.120 --> 00:02:17.130 align:start position:0% that work and I think that shift in 00:02:17.130 --> 00:02:21.110 align:start position:0% that work and I think that shift in culture<00:02:17.599> Thanks<00:02:19.160> that<00:02:20.160> shift<00:02:20.430> in<00:02:20.610> culture<00:02:20.819> has 00:02:21.110 --> 00:02:21.120 align:start position:0% culture Thanks that shift in culture has 00:02:21.120 --> 00:02:23.510 align:start position:0% culture Thanks that shift in culture has led<00:02:21.330> to<00:02:21.510> much<00:02:21.690> better<00:02:21.930> code<00:02:22.250> and<00:02:23.250> the<00:02:23.340> last 00:02:23.510 --> 00:02:23.520 align:start position:0% led to much better code and the last 00:02:23.520 --> 00:02:25.100 align:start position:0% led to much better code and the last thing<00:02:23.730> is<00:02:23.880> I<00:02:24.000> think<00:02:24.060> that<00:02:24.270> today<00:02:24.599> we<00:02:24.930> have 00:02:25.100 --> 00:02:25.110 align:start position:0% thing is I think that today we have 00:02:25.110 --> 00:02:27.500 align:start position:0% thing is I think that today we have substantially<00:02:26.010> better<00:02:26.220> tools<00:02:26.580> so<00:02:27.300> that<00:02:27.330> if 00:02:27.500 --> 00:02:27.510 align:start position:0% substantially better tools so that if 00:02:27.510 --> 00:02:29.320 align:start position:0% substantially better tools so that if you<00:02:27.599> care<00:02:27.930> to<00:02:28.080> write<00:02:28.260> good<00:02:28.440> code<00:02:28.680> you<00:02:28.920> can 00:02:29.320 --> 00:02:29.330 align:start position:0% you care to write good code you can 00:02:29.330 --> 00:02:32.030 align:start position:0% you care to write good code you can things<00:02:30.330> from<00:02:30.690> you<00:02:30.959> know<00:02:31.050> my<00:02:31.230> company<00:02:31.440> slither 00:02:32.030 --> 00:02:32.040 align:start position:0% things from you know my company slither 00:02:32.040 --> 00:02:34.640 align:start position:0% things from you know my company slither Manticore<00:02:32.910> echidna<00:02:33.390> things<00:02:33.959> from<00:02:34.200> everyone 00:02:34.640 --> 00:02:34.650 align:start position:0% Manticore echidna things from everyone 00:02:34.650 --> 00:02:37.660 align:start position:0% Manticore echidna things from everyone else<00:02:34.800> on<00:02:34.980> this<00:02:35.300> panel<00:02:36.300> of<00:02:36.390> experts<00:02:36.750> here<00:02:36.989> have 00:02:37.660 --> 00:02:37.670 align:start position:0% else on this panel of experts here have 00:02:37.670 --> 00:02:39.740 align:start position:0% else on this panel of experts here have demonstrably<00:02:38.670> improved<00:02:39.150> the<00:02:39.300> code<00:02:39.480> that<00:02:39.630> I've 00:02:39.740 --> 00:02:39.750 align:start position:0% demonstrably improved the code that I've 00:02:39.750 --> 00:02:48.620 align:start position:0% demonstrably improved the code that I've seen<00:02:39.959> from<00:02:40.140> our<00:02:40.290> clients<00:02:47.209> yes<00:02:48.209> I<00:02:48.360> was<00:02:48.480> gonna 00:02:48.620 --> 00:02:48.630 align:start position:0% seen from our clients yes I was gonna 00:02:48.630 --> 00:02:51.289 align:start position:0% seen from our clients yes I was gonna say<00:02:48.870> that<00:02:48.900> a<00:02:49.709> year<00:02:50.310> ago<00:02:50.340> when<00:02:51.030> we<00:02:51.150> were<00:02:51.269> in 00:02:51.289 --> 00:02:51.299 align:start position:0% say that a year ago when we were in 00:02:51.299 --> 00:02:55.160 align:start position:0% say that a year ago when we were in Mexico<00:02:53.090> there<00:02:54.090> wasn't<00:02:54.390> much<00:02:54.540> of<00:02:54.569> a<00:02:54.750> security 00:02:55.160 --> 00:02:55.170 align:start position:0% Mexico there wasn't much of a security 00:02:55.170 --> 00:02:57.050 align:start position:0% Mexico there wasn't much of a security community<00:02:55.950> and<00:02:56.160> that's<00:02:56.310> something<00:02:56.790> which<00:02:56.910> I 00:02:57.050 --> 00:02:57.060 align:start position:0% community and that's something which I 00:02:57.060 --> 00:02:58.880 align:start position:0% community and that's something which I feel<00:02:57.269> is<00:02:57.420> really<00:02:57.630> taking<00:02:58.140> off<00:02:58.260> in<00:02:58.590> the<00:02:58.680> last 00:02:58.880 --> 00:02:58.890 align:start position:0% feel is really taking off in the last 00:02:58.890 --> 00:03:03.680 align:start position:0% feel is really taking off in the last maybe<00:02:59.280> half<00:02:59.670> a<00:02:59.850> year<00:03:00.150> and<00:03:02.239> most<00:03:03.239> of<00:03:03.450> the<00:03:03.510> people 00:03:03.680 --> 00:03:03.690 align:start position:0% maybe half a year and most of the people 00:03:03.690 --> 00:03:06.979 align:start position:0% maybe half a year and most of the people who<00:03:03.989> were<00:03:04.560> interested<00:03:04.709> in<00:03:05.010> in<00:03:05.280> security<00:03:05.989> came 00:03:06.979 --> 00:03:06.989 align:start position:0% who were interested in in security came 00:03:06.989 --> 00:03:09.650 align:start position:0% who were interested in in security came from<00:03:07.200> the<00:03:07.350> ethereum<00:03:07.739> space<00:03:08.010> and<00:03:08.370> and<00:03:08.700> really 00:03:09.650 --> 00:03:09.660 align:start position:0% from the ethereum space and and really 00:03:09.660 --> 00:03:11.259 align:start position:0% from the ethereum space and and really were<00:03:09.810> ethereum<00:03:10.739> and<00:03:10.890> through<00:03:11.010> the 00:03:11.259 --> 00:03:11.269 align:start position:0% were ethereum and through the 00:03:11.269 --> 00:03:14.390 align:start position:0% were ethereum and through the enthusiasts<00:03:12.269> who<00:03:12.930> were<00:03:13.799> also<00:03:14.010> interested<00:03:14.190> in 00:03:14.390 --> 00:03:14.400 align:start position:0% enthusiasts who were also interested in 00:03:14.400 --> 00:03:15.800 align:start position:0% enthusiasts who were also interested in security<00:03:14.819> and<00:03:14.910> now<00:03:15.090> I<00:03:15.120> think<00:03:15.299> we've<00:03:15.630> seen<00:03:15.750> a 00:03:15.800 --> 00:03:15.810 align:start position:0% security and now I think we've seen a 00:03:15.810 --> 00:03:18.370 align:start position:0% security and now I think we've seen a kind<00:03:16.350> of<00:03:16.440> large<00:03:16.650> influx<00:03:17.280> from<00:03:17.609> traditional 00:03:18.370 --> 00:03:18.380 align:start position:0% kind of large influx from traditional 00:03:18.380 --> 00:03:22.370 align:start position:0% kind of large influx from traditional security<00:03:19.380> into<00:03:20.280> this<00:03:20.430> space<00:03:20.700> and<00:03:21.090> that<00:03:22.049> really 00:03:22.370 --> 00:03:22.380 align:start position:0% security into this space and that really 00:03:22.380 --> 00:03:26.060 align:start position:0% security into this space and that really changes<00:03:22.980> things<00:03:24.200> yeah<00:03:25.200> to<00:03:25.470> speak<00:03:25.739> to<00:03:25.890> what 00:03:26.060 --> 00:03:26.070 align:start position:0% changes things yeah to speak to what 00:03:26.070 --> 00:03:30.050 align:start position:0% changes things yeah to speak to what what<00:03:26.760> Martin<00:03:27.390> just<00:03:27.570> said<00:03:28.370> sort<00:03:29.370> of<00:03:29.489> recently<00:03:29.970> I 00:03:30.050 --> 00:03:30.060 align:start position:0% what Martin just said sort of recently I 00:03:30.060 --> 00:03:32.150 align:start position:0% what Martin just said sort of recently I attended<00:03:30.239> an<00:03:30.570> academic<00:03:31.019> conference<00:03:31.230> USENIX 00:03:32.150 --> 00:03:32.160 align:start position:0% attended an academic conference USENIX 00:03:32.160 --> 00:03:33.949 align:start position:0% attended an academic conference USENIX 18<00:03:32.579> and<00:03:32.850> they<00:03:33.180> had<00:03:33.359> actually<00:03:33.660> an<00:03:33.750> entire 00:03:33.949 --> 00:03:33.959 align:start position:0% 18 and they had actually an entire 00:03:33.959 --> 00:03:35.900 align:start position:0% 18 and they had actually an entire session<00:03:34.530> on<00:03:34.650> smart<00:03:34.920> contract<00:03:35.310> security<00:03:35.760> which 00:03:35.900 --> 00:03:35.910 align:start position:0% session on smart contract security which 00:03:35.910 --> 00:03:38.090 align:start position:0% session on smart contract security which had<00:03:36.120> I<00:03:36.329> think<00:03:36.390> around<00:03:36.690> four<00:03:37.049> talks<00:03:37.350> that<00:03:37.980> were 00:03:38.090 --> 00:03:38.100 align:start position:0% had I think around four talks that were 00:03:38.100 --> 00:03:39.860 align:start position:0% had I think around four talks that were aetherium<00:03:38.430> related<00:03:38.910> and<00:03:39.090> that's<00:03:39.510> a<00:03:39.660> community 00:03:39.860 --> 00:03:39.870 align:start position:0% aetherium related and that's a community 00:03:39.870 --> 00:03:41.420 align:start position:0% aetherium related and that's a community that's<00:03:40.230> completely<00:03:40.620> outside<00:03:41.040> of<00:03:41.190> this<00:03:41.310> space 00:03:41.420 --> 00:03:41.430 align:start position:0% that's completely outside of this space 00:03:41.430 --> 00:03:43.099 align:start position:0% that's completely outside of this space those<00:03:41.820> are<00:03:41.940> people<00:03:42.180> who<00:03:42.209> normally<00:03:42.540> would<00:03:42.930> not 00:03:43.099 --> 00:03:43.109 align:start position:0% those are people who normally would not 00:03:43.109 --> 00:03:45.500 align:start position:0% those are people who normally would not be<00:03:43.260> working<00:03:43.560> on<00:03:43.650> these<00:03:43.799> tools<00:03:44.070> so<00:03:44.510> definitely 00:03:45.500 --> 00:03:45.510 align:start position:0% be working on these tools so definitely 00:03:45.510 --> 00:03:47.090 align:start position:0% be working on these tools so definitely a<00:03:45.540> lot<00:03:45.690> of<00:03:45.720> outside<00:03:46.140> people<00:03:46.410> have<00:03:46.530> come<00:03:46.709> in<00:03:46.920> and 00:03:47.090 --> 00:03:47.100 align:start position:0% a lot of outside people have come in and 00:03:47.100 --> 00:03:49.220 align:start position:0% a lot of outside people have come in and we've<00:03:47.370> also<00:03:47.609> seen<00:03:48.030> sort<00:03:48.780> of<00:03:48.840> the<00:03:48.900> people<00:03:49.049> who 00:03:49.220 --> 00:03:49.230 align:start position:0% we've also seen sort of the people who 00:03:49.230 --> 00:03:50.539 align:start position:0% we've also seen sort of the people who are<00:03:49.320> already<00:03:49.470> in<00:03:49.769> the<00:03:49.859> space<00:03:50.100> start<00:03:50.340> producing 00:03:50.539 --> 00:03:50.549 align:start position:0% are already in the space start producing 00:03:50.549 --> 00:03:52.400 align:start position:0% are already in the space start producing artifacts<00:03:51.150> so<00:03:51.390> we've<00:03:51.510> seen<00:03:51.780> the<00:03:51.930> first<00:03:52.170> set<00:03:52.380> of 00:03:52.400 --> 00:03:52.410 align:start position:0% artifacts so we've seen the first set of 00:03:52.410 --> 00:03:54.590 align:start position:0% artifacts so we've seen the first set of formally<00:03:52.859> verified<00:03:52.890> contracts<00:03:53.790> we've<00:03:54.329> seen 00:03:54.590 --> 00:03:54.600 align:start position:0% formally verified contracts we've seen 00:03:54.600 --> 00:03:56.270 align:start position:0% formally verified contracts we've seen smoother<00:03:54.959> processes<00:03:55.500> for<00:03:55.739> like<00:03:55.890> engaging 00:03:56.270 --> 00:03:56.280 align:start position:0% smoother processes for like engaging 00:03:56.280 --> 00:03:58.880 align:start position:0% smoother processes for like engaging that<00:03:56.660> and<00:03:57.660> just<00:03:58.049> a<00:03:58.200> lot<00:03:58.350> of<00:03:58.380> improvement 00:03:58.880 --> 00:03:58.890 align:start position:0% that and just a lot of improvement 00:03:58.890 --> 00:04:00.259 align:start position:0% that and just a lot of improvement across<00:03:59.100> the<00:03:59.250> board<00:03:59.430> I<00:03:59.519> think<00:03:59.730> kind<00:04:00.150> of 00:04:00.259 --> 00:04:00.269 align:start position:0% across the board I think kind of 00:04:00.269 --> 00:04:01.670 align:start position:0% across the board I think kind of everything<00:04:00.569> is<00:04:00.810> a<00:04:00.840> little<00:04:00.959> bit<00:04:01.170> less<00:04:01.319> on<00:04:01.500> fire 00:04:01.670 --> 00:04:01.680 align:start position:0% everything is a little bit less on fire 00:04:01.680 --> 00:04:08.780 align:start position:0% everything is a little bit less on fire than<00:04:01.920> it<00:04:02.010> was<00:04:02.160> a<00:04:02.190> year<00:04:02.370> or<00:04:02.609> two<00:04:02.730> ago<00:04:02.850> so<00:04:07.549> yeah<00:04:08.549> I 00:04:08.780 --> 00:04:08.790 align:start position:0% than it was a year or two ago so yeah I 00:04:08.790 --> 00:04:10.789 align:start position:0% than it was a year or two ago so yeah I think<00:04:09.060> sort<00:04:09.510> of<00:04:09.600> echo<00:04:10.230> what<00:04:10.380> everyone<00:04:10.680> else 00:04:10.789 --> 00:04:10.799 align:start position:0% think sort of echo what everyone else 00:04:10.799 --> 00:04:13.490 align:start position:0% think sort of echo what everyone else has<00:04:10.950> said<00:04:10.980> I<00:04:11.459> think<00:04:11.940> really<00:04:12.150> like<00:04:12.329> not<00:04:13.290> only 00:04:13.490 --> 00:04:13.500 align:start position:0% has said I think really like not only 00:04:13.500 --> 00:04:16.849 align:start position:0% has said I think really like not only has<00:04:13.739> the<00:04:13.859> security<00:04:14.400> community<00:04:15.239> grown<00:04:16.139> there's 00:04:16.849 --> 00:04:16.859 align:start position:0% has the security community grown there's 00:04:16.859 --> 00:04:18.740 align:start position:0% has the security community grown there's been<00:04:17.130> massive<00:04:17.400> increase<00:04:18.180> awareness<00:04:18.419> and 00:04:18.740 --> 00:04:18.750 align:start position:0% been massive increase awareness and 00:04:18.750 --> 00:04:20.629 align:start position:0% been massive increase awareness and security<00:04:19.079> issues<00:04:19.169> I<00:04:19.440> think<00:04:19.979> you<00:04:20.400> know<00:04:20.489> like 00:04:20.629 --> 00:04:20.639 align:start position:0% security issues I think you know like 00:04:20.639 --> 00:04:22.909 align:start position:0% security issues I think you know like most<00:04:20.789> exchanges<00:04:21.359> now<00:04:21.510> require<00:04:22.409> a<00:04:22.440> security 00:04:22.909 --> 00:04:22.919 align:start position:0% most exchanges now require a security 00:04:22.919 --> 00:04:25.040 align:start position:0% most exchanges now require a security audit<00:04:23.280> of<00:04:23.490> some<00:04:23.700> sort<00:04:24.060> before<00:04:24.270> they<00:04:24.659> you<00:04:24.930> know 00:04:25.040 --> 00:04:25.050 align:start position:0% audit of some sort before they you know 00:04:25.050 --> 00:04:26.990 align:start position:0% audit of some sort before they you know interact<00:04:25.409> with<00:04:25.560> products<00:04:25.950> which<00:04:26.190> is<00:04:26.310> you<00:04:26.729> know 00:04:26.990 --> 00:04:27.000 align:start position:0% interact with products which is you know 00:04:27.000 --> 00:04:28.970 align:start position:0% interact with products which is you know surprisingly<00:04:27.480> shockingly<00:04:28.260> that<00:04:28.380> wasn't<00:04:28.800> the 00:04:28.970 --> 00:04:28.980 align:start position:0% surprisingly shockingly that wasn't the 00:04:28.980 --> 00:04:30.620 align:start position:0% surprisingly shockingly that wasn't the case<00:04:29.100> always<00:04:29.520> right 00:04:30.620 --> 00:04:30.630 align:start position:0% case always right 00:04:30.630 --> 00:04:34.010 align:start position:0% case always right the<00:04:31.290> like<00:04:32.250> there's<00:04:32.550> more<00:04:33.180> awareness<00:04:33.300> and 00:04:34.010 --> 00:04:34.020 align:start position:0% the like there's more awareness and 00:04:34.020 --> 00:04:36.050 align:start position:0% the like there's more awareness and generally<00:04:34.740> that<00:04:34.770> you<00:04:35.490> know<00:04:35.550> before<00:04:35.700> you<00:04:35.910> go 00:04:36.050 --> 00:04:36.060 align:start position:0% generally that you know before you go 00:04:36.060 --> 00:04:38.690 align:start position:0% generally that you know before you go live<00:04:36.240> we<00:04:36.510> do<00:04:36.630> need<00:04:36.810> a<00:04:36.870> security<00:04:37.170> audit<00:04:37.700> there's 00:04:38.690 --> 00:04:38.700 align:start position:0% live we do need a security audit there's 00:04:38.700 --> 00:04:41.150 align:start position:0% live we do need a security audit there's like<00:04:39.000> that<00:04:39.450> there's<00:04:40.350> your<00:04:40.560> best<00:04:40.740> best 00:04:41.150 --> 00:04:41.160 align:start position:0% like that there's your best best 00:04:41.160 --> 00:04:44.120 align:start position:0% like that there's your best best practices<00:04:41.700> that<00:04:41.850> need<00:04:41.910> to<00:04:42.120> be<00:04:42.180> followed<00:04:43.130> so 00:04:44.120 --> 00:04:44.130 align:start position:0% practices that need to be followed so 00:04:44.130 --> 00:04:46.040 align:start position:0% practices that need to be followed so like<00:04:44.580> you<00:04:44.760> know<00:04:44.850> we're<00:04:45.030> playing<00:04:45.420> a<00:04:45.600> bit<00:04:45.780> less 00:04:46.040 --> 00:04:46.050 align:start position:0% like you know we're playing a bit less 00:04:46.050 --> 00:04:49.010 align:start position:0% like you know we're playing a bit less fast<00:04:46.650> and<00:04:46.890> loose<00:04:47.070> and<00:04:47.430> and<00:04:47.580> more<00:04:47.880> that<00:04:48.510> more 00:04:49.010 --> 00:04:49.020 align:start position:0% fast and loose and and more that more 00:04:49.020 --> 00:04:51.200 align:start position:0% fast and loose and and more that more realizing<00:04:49.770> that<00:04:49.890> you<00:04:50.400> know<00:04:50.430> if<00:04:50.850> you<00:04:50.970> write<00:04:51.180> a 00:04:51.200 --> 00:04:51.210 align:start position:0% realizing that you know if you write a 00:04:51.210 --> 00:04:53.960 align:start position:0% realizing that you know if you write a smart<00:04:51.480> contract<00:04:52.040> you<00:04:53.040> know<00:04:53.130> that<00:04:53.490> may<00:04:53.760> hold 00:04:53.960 --> 00:04:53.970 align:start position:0% smart contract you know that may hold 00:04:53.970 --> 00:04:56.180 align:start position:0% smart contract you know that may hold even<00:04:54.870> if<00:04:54.990> you<00:04:55.050> don't<00:04:55.200> intend<00:04:55.470> it<00:04:55.560> to<00:04:55.590> many 00:04:56.180 --> 00:04:56.190 align:start position:0% even if you don't intend it to many 00:04:56.190 --> 00:04:57.830 align:start position:0% even if you don't intend it to many millions<00:04:56.520> of<00:04:56.610> dollars<00:04:56.910> and<00:04:57.180> you<00:04:57.450> know<00:04:57.510> that 00:04:57.830 --> 00:04:57.840 align:start position:0% millions of dollars and you know that 00:04:57.840 --> 00:04:59.360 align:start position:0% millions of dollars and you know that you<00:04:57.900> don't<00:04:58.020> want<00:04:58.140> to<00:04:58.200> be<00:04:58.260> directly<00:04:59.190> or 00:04:59.360 --> 00:04:59.370 align:start position:0% you don't want to be directly or 00:04:59.370 --> 00:05:01.250 align:start position:0% you don't want to be directly or indirectly<00:04:59.550> responsible<00:04:59.970> for<00:05:00.450> a<00:05:00.660> loss<00:05:01.080> of 00:05:01.250 --> 00:05:01.260 align:start position:0% indirectly responsible for a loss of 00:05:01.260 --> 00:05:05.240 align:start position:0% indirectly responsible for a loss of that<00:05:02.750> it's<00:05:03.750> hard<00:05:03.840> to<00:05:04.260> go<00:05:04.590> after<00:05:04.740> all<00:05:05.040> these 00:05:05.240 --> 00:05:05.250 align:start position:0% that it's hard to go after all these 00:05:05.250 --> 00:05:07.600 align:start position:0% that it's hard to go after all these guys<00:05:05.460> and<00:05:05.490> have<00:05:05.850> something<00:05:06.060> original<00:05:06.300> to<00:05:06.600> say 00:05:07.600 --> 00:05:07.610 align:start position:0% guys and have something original to say 00:05:07.610 --> 00:05:10.970 align:start position:0% guys and have something original to say so<00:05:08.610> tools<00:05:08.850> this<00:05:09.540> it's<00:05:09.810> been<00:05:10.020> an<00:05:10.110> explosion<00:05:10.500> and 00:05:10.970 --> 00:05:10.980 align:start position:0% so tools this it's been an explosion and 00:05:10.980 --> 00:05:13.930 align:start position:0% so tools this it's been an explosion and I<00:05:11.160> just<00:05:11.400> wanna<00:05:11.550> like<00:05:11.760> call<00:05:12.270> it<00:05:12.300> like<00:05:12.720> Zeppelin 00:05:13.930 --> 00:05:13.940 align:start position:0% I just wanna like call it like Zeppelin 00:05:13.940 --> 00:05:16.760 align:start position:0% I just wanna like call it like Zeppelin change<00:05:14.940> security<00:05:15.260> trail<00:05:16.260> if<00:05:16.350> it's<00:05:16.530> really 00:05:16.760 --> 00:05:16.770 align:start position:0% change security trail if it's really 00:05:16.770 --> 00:05:18.500 align:start position:0% change security trail if it's really like<00:05:16.890> coming<00:05:17.370> on<00:05:17.490> hardened<00:05:17.880> last<00:05:18.090> year<00:05:18.390> is 00:05:18.500 --> 00:05:18.510 align:start position:0% like coming on hardened last year is 00:05:18.510 --> 00:05:20.420 align:start position:0% like coming on hardened last year is really<00:05:19.020> like<00:05:19.260> stepped<00:05:19.680> up<00:05:19.830> everybody's<00:05:20.220> game 00:05:20.420 --> 00:05:20.430 align:start position:0% really like stepped up everybody's game 00:05:20.430 --> 00:05:24.290 align:start position:0% really like stepped up everybody's game up<00:05:20.750> and<00:05:21.750> then<00:05:22.050> like<00:05:22.400> Bernard<00:05:23.400> and<00:05:23.760> mithril 00:05:24.290 --> 00:05:24.300 align:start position:0% up and then like Bernard and mithril 00:05:24.300 --> 00:05:26.980 align:start position:0% up and then like Bernard and mithril within<00:05:24.630> consensus<00:05:25.140> are<00:05:25.320> kind<00:05:25.919> of<00:05:25.980> going<00:05:26.190> crazy 00:05:26.980 --> 00:05:26.990 align:start position:0% within consensus are kind of going crazy 00:05:26.990 --> 00:05:30.260 align:start position:0% within consensus are kind of going crazy you<00:05:27.990> know<00:05:28.110> good<00:05:28.500> fun<00:05:28.710> way<00:05:28.860> and<00:05:29.760> then<00:05:29.940> I<00:05:29.970> think 00:05:30.260 --> 00:05:30.270 align:start position:0% you know good fun way and then I think 00:05:30.270 --> 00:05:31.490 align:start position:0% you know good fun way and then I think like<00:05:30.450> maybe<00:05:30.750> the<00:05:30.960> thing<00:05:31.140> that<00:05:31.260> I've<00:05:31.350> heard 00:05:31.490 --> 00:05:31.500 align:start position:0% like maybe the thing that I've heard 00:05:31.500 --> 00:05:34.820 align:start position:0% like maybe the thing that I've heard more<00:05:31.650> conversation<00:05:32.310> about<00:05:32.490> recently<00:05:33.030> is<00:05:33.830> like 00:05:34.820 --> 00:05:34.830 align:start position:0% more conversation about recently is like 00:05:34.830 --> 00:05:36.950 align:start position:0% more conversation about recently is like the<00:05:34.950> awareness<00:05:35.400> of<00:05:35.580> incentives<00:05:36.090> and<00:05:36.390> how 00:05:36.950 --> 00:05:36.960 align:start position:0% the awareness of incentives and how 00:05:36.960 --> 00:05:39.560 align:start position:0% the awareness of incentives and how crypto<00:05:37.620> economic<00:05:38.100> mechanisms<00:05:38.669> themself<00:05:39.240> can 00:05:39.560 --> 00:05:39.570 align:start position:0% crypto economic mechanisms themself can 00:05:39.570 --> 00:05:43.280 align:start position:0% crypto economic mechanisms themself can actually<00:05:40.070> contribute<00:05:41.070> to<00:05:41.390> security<00:05:42.390> in<00:05:43.050> like 00:05:43.280 --> 00:05:43.290 align:start position:0% actually contribute to security in like 00:05:43.290 --> 00:05:45.100 align:start position:0% actually contribute to security in like one<00:05:43.500> way<00:05:43.650> is<00:05:43.860> just<00:05:44.190> like<00:05:44.610> automated 00:05:45.100 --> 00:05:45.110 align:start position:0% one way is just like automated 00:05:45.110 --> 00:05:48.230 align:start position:0% one way is just like automated deterministic<00:05:46.550> non-subjective<00:05:47.550> bounties 00:05:48.230 --> 00:05:48.240 align:start position:0% deterministic non-subjective bounties 00:05:48.240 --> 00:05:49.820 align:start position:0% deterministic non-subjective bounties that<00:05:48.270> payout<00:05:48.810> when<00:05:49.050> you<00:05:49.140> break<00:05:49.320> the<00:05:49.470> thing<00:05:49.650> I 00:05:49.820 --> 00:05:49.830 align:start position:0% that payout when you break the thing I 00:05:49.830 --> 00:05:52.240 align:start position:0% that payout when you break the thing I think<00:05:49.890> that's<00:05:50.160> amazing 00:05:52.240 --> 00:05:52.250 align:start position:0% think that's amazing 00:05:52.250 --> 00:05:56.540 align:start position:0% think that's amazing cool<00:05:53.300> so<00:05:54.300> next<00:05:54.570> one<00:05:54.720> compared<00:05:55.710> to<00:05:55.770> securing 00:05:56.540 --> 00:05:56.550 align:start position:0% cool so next one compared to securing 00:05:56.550 --> 00:05:58.790 align:start position:0% cool so next one compared to securing traditional<00:05:57.090> systems<00:05:57.510> how<00:05:58.050> do<00:05:58.110> the<00:05:58.260> economic 00:05:58.790 --> 00:05:58.800 align:start position:0% traditional systems how do the economic 00:05:58.800 --> 00:06:01.040 align:start position:0% traditional systems how do the economic properties<00:05:59.250> of<00:05:59.400> smart<00:05:59.669> contracts<00:06:00.030> change<00:06:00.450> how 00:06:01.040 --> 00:06:01.050 align:start position:0% properties of smart contracts change how 00:06:01.050 --> 00:06:06.140 align:start position:0% properties of smart contracts change how you<00:06:01.110> approach<00:06:01.229> their<00:06:01.590> security<00:06:02.270> okay<00:06:03.270> well<00:06:05.150> so 00:06:06.140 --> 00:06:06.150 align:start position:0% you approach their security okay well so 00:06:06.150 --> 00:06:08.900 align:start position:0% you approach their security okay well so I<00:06:06.180> mean<00:06:06.720> like<00:06:07.260> what<00:06:07.710> I<00:06:07.740> think<00:06:07.830> is<00:06:08.130> one<00:06:08.550> way<00:06:08.729> that 00:06:08.900 --> 00:06:08.910 align:start position:0% I mean like what I think is one way that 00:06:08.910 --> 00:06:11.350 align:start position:0% I mean like what I think is one way that we're<00:06:09.120> tackling<00:06:09.600> that<00:06:09.810> is<00:06:10.140> actually<00:06:10.770> through 00:06:11.350 --> 00:06:11.360 align:start position:0% we're tackling that is actually through 00:06:11.360 --> 00:06:13.850 align:start position:0% we're tackling that is actually through actually<00:06:12.360> creating<00:06:12.750> like<00:06:12.870> incentives<00:06:13.290> for 00:06:13.850 --> 00:06:13.860 align:start position:0% actually creating like incentives for 00:06:13.860 --> 00:06:15.440 align:start position:0% actually creating like incentives for coordination<00:06:14.430> within<00:06:14.850> the<00:06:14.970> security 00:06:15.440 --> 00:06:15.450 align:start position:0% coordination within the security 00:06:15.450 --> 00:06:18.890 align:start position:0% coordination within the security community<00:06:15.900> so<00:06:16.140> our<00:06:16.380> Pam<00:06:16.919> ballot<00:06:17.340> project<00:06:17.850> is<00:06:18.090> a 00:06:18.890 --> 00:06:18.900 align:start position:0% community so our Pam ballot project is a 00:06:18.900 --> 00:06:20.960 align:start position:0% community so our Pam ballot project is a set<00:06:19.380> of<00:06:19.470> incentives<00:06:19.740> that<00:06:20.520> bring<00:06:20.790> people 00:06:20.960 --> 00:06:20.970 align:start position:0% set of incentives that bring people 00:06:20.970 --> 00:06:25.159 align:start position:0% set of incentives that bring people together<00:06:21.680> developers<00:06:23.090> auditors<00:06:24.090> to<00:06:24.390> try<00:06:25.110> to 00:06:25.159 --> 00:06:25.169 align:start position:0% together developers auditors to try to 00:06:25.169 --> 00:06:28.219 align:start position:0% together developers auditors to try to establish<00:06:26.100> clarity<00:06:26.910> around<00:06:27.030> what<00:06:27.330> is<00:06:27.840> a<00:06:27.870> safe 00:06:28.219 --> 00:06:28.229 align:start position:0% establish clarity around what is a safe 00:06:28.229 --> 00:06:31.760 align:start position:0% establish clarity around what is a safe contract<00:06:28.740> to<00:06:28.890> use<00:06:29.300> and<00:06:30.300> if<00:06:31.020> you're<00:06:31.320> interested 00:06:31.760 --> 00:06:31.770 align:start position:0% contract to use and if you're interested 00:06:31.770 --> 00:06:33.590 align:start position:0% contract to use and if you're interested in<00:06:31.800> that<00:06:31.890> we<00:06:32.250> recently<00:06:32.460> put<00:06:32.820> a<00:06:32.880> video<00:06:33.270> of<00:06:33.450> the 00:06:33.590 --> 00:06:33.600 align:start position:0% in that we recently put a video of the 00:06:33.600 --> 00:06:35.750 align:start position:0% in that we recently put a video of the process<00:06:33.810> for<00:06:34.320> for<00:06:34.710> seeking<00:06:35.099> consensus<00:06:35.610> around 00:06:35.750 --> 00:06:35.760 align:start position:0% process for for seeking consensus around 00:06:35.760 --> 00:06:38.270 align:start position:0% process for for seeking consensus around that<00:06:36.090> I'll<00:06:37.050> tweet<00:06:37.410> it<00:06:37.530> after<00:06:37.860> and<00:06:38.010> we'd<00:06:38.130> love 00:06:38.270 --> 00:06:38.280 align:start position:0% that I'll tweet it after and we'd love 00:06:38.280 --> 00:06:39.740 align:start position:0% that I'll tweet it after and we'd love to<00:06:38.340> get<00:06:38.520> your<00:06:38.669> feedback<00:06:38.729> on<00:06:39.060> it 00:06:39.740 --> 00:06:39.750 align:start position:0% to get your feedback on it 00:06:39.750 --> 00:06:41.810 align:start position:0% to get your feedback on it and<00:06:39.840> I<00:06:40.200> we<00:06:40.770> have<00:06:40.890> got<00:06:41.070> some<00:06:41.280> already<00:06:41.430> and<00:06:41.760> I'm 00:06:41.810 --> 00:06:41.820 align:start position:0% and I we have got some already and I'm 00:06:41.820 --> 00:06:50.000 align:start position:0% and I we have got some already and I'm looking<00:06:42.090> forward<00:06:42.330> to<00:06:42.360> more<00:06:48.020> okay<00:06:49.020> I<00:06:49.740> think 00:06:50.000 --> 00:06:50.010 align:start position:0% looking forward to more okay I think 00:06:50.010 --> 00:06:53.650 align:start position:0% looking forward to more okay I think like<00:06:50.280> one<00:06:50.970> of<00:06:51.030> the<00:06:51.120> big<00:06:51.210> distinctions<00:06:51.810> is<00:06:52.020> the 00:06:53.650 --> 00:06:53.660 align:start position:0% like one of the big distinctions is the 00:06:53.660 --> 00:06:56.420 align:start position:0% like one of the big distinctions is the irreversibility<00:06:54.660> and<00:06:55.020> the<00:06:55.590> transparency<00:06:56.160> of 00:06:56.420 --> 00:06:56.430 align:start position:0% irreversibility and the transparency of 00:06:56.430 --> 00:06:58.910 align:start position:0% irreversibility and the transparency of the<00:06:57.180> smart<00:06:57.570> contract<00:06:57.720> environment<00:06:58.410> versus 00:06:58.910 --> 00:06:58.920 align:start position:0% the smart contract environment versus 00:06:58.920 --> 00:07:01.220 align:start position:0% the smart contract environment versus the<00:06:59.310> you<00:07:00.000> know<00:07:00.120> like<00:07:00.300> traditional<00:07:00.900> security 00:07:01.220 --> 00:07:01.230 align:start position:0% the you know like traditional security 00:07:01.230 --> 00:07:03.530 align:start position:0% the you know like traditional security domain<00:07:01.520> kind<00:07:02.520> of<00:07:02.670> you<00:07:03.060> can<00:07:03.210> can't<00:07:03.360> usually 00:07:03.530 --> 00:07:03.540 align:start position:0% domain kind of you can can't usually 00:07:03.540 --> 00:07:05.300 align:start position:0% domain kind of you can can't usually just<00:07:03.960> read<00:07:04.140> traditional<00:07:04.740> security<00:07:05.070> almost 00:07:05.300 --> 00:07:05.310 align:start position:0% just read traditional security almost 00:07:05.310 --> 00:07:08.240 align:start position:0% just read traditional security almost like<00:07:05.460> insurance<00:07:06.030> you<00:07:06.240> know<00:07:06.330> it's<00:07:07.260> like<00:07:07.710> often 00:07:08.240 --> 00:07:08.250 align:start position:0% like insurance you know it's like often 00:07:08.250 --> 00:07:10.400 align:start position:0% like insurance you know it's like often less<00:07:08.460> costly<00:07:08.940> to<00:07:08.970> just<00:07:09.270> fix<00:07:09.960> the<00:07:10.050> issue<00:07:10.140> after 00:07:10.400 --> 00:07:10.410 align:start position:0% less costly to just fix the issue after 00:07:10.410 --> 00:07:13.640 align:start position:0% less costly to just fix the issue after the<00:07:10.560> fact<00:07:10.800> then<00:07:11.160> to<00:07:11.610> prepare<00:07:11.940> for<00:07:12.180> it<00:07:12.300> or<00:07:13.290> you 00:07:13.640 --> 00:07:13.650 align:start position:0% the fact then to prepare for it or you 00:07:13.650 --> 00:07:14.930 align:start position:0% the fact then to prepare for it or you know<00:07:13.740> you<00:07:13.830> have<00:07:13.980> like<00:07:14.130> safeguards<00:07:14.730> or 00:07:14.930 --> 00:07:14.940 align:start position:0% know you have like safeguards or 00:07:14.940 --> 00:07:17.240 align:start position:0% know you have like safeguards or abilities<00:07:15.480> that<00:07:15.570> you<00:07:15.690> just<00:07:15.870> don't<00:07:16.020> have<00:07:16.250> in 00:07:17.240 --> 00:07:17.250 align:start position:0% abilities that you just don't have in 00:07:17.250 --> 00:07:18.770 align:start position:0% abilities that you just don't have in smart<00:07:17.520> contracts<00:07:17.910> where<00:07:18.120> you<00:07:18.630> know<00:07:18.720> if 00:07:18.770 --> 00:07:18.780 align:start position:0% smart contracts where you know if 00:07:18.780 --> 00:07:20.330 align:start position:0% smart contracts where you know if somebody<00:07:19.080> drains<00:07:19.590> your<00:07:19.710> contract<00:07:20.130> I<00:07:20.220> mean 00:07:20.330 --> 00:07:20.340 align:start position:0% somebody drains your contract I mean 00:07:20.340 --> 00:07:22.580 align:start position:0% somebody drains your contract I mean it's<00:07:20.490> over<00:07:20.700> there's<00:07:20.880> there's<00:07:21.150> no<00:07:21.240> recourse<00:07:21.590> so 00:07:22.580 --> 00:07:22.590 align:start position:0% it's over there's there's no recourse so 00:07:22.590 --> 00:07:27.140 align:start position:0% it's over there's there's no recourse so and<00:07:23.190> I<00:07:23.310> think<00:07:23.370> like<00:07:23.700> it's<00:07:24.260> it's<00:07:25.430> a<00:07:26.430> lot<00:07:27.090> of 00:07:27.140 --> 00:07:27.150 align:start position:0% and I think like it's it's a lot of 00:07:27.150 --> 00:07:29.360 align:start position:0% and I think like it's it's a lot of people<00:07:27.420> say<00:07:27.540> hey<00:07:27.720> look<00:07:27.900> you<00:07:28.170> know<00:07:28.370> smart 00:07:29.360 --> 00:07:29.370 align:start position:0% people say hey look you know smart 00:07:29.370 --> 00:07:30.950 align:start position:0% people say hey look you know smart contracts<00:07:29.730> just<00:07:30.120> never<00:07:30.420> gonna<00:07:30.540> work<00:07:30.750> because 00:07:30.950 --> 00:07:30.960 align:start position:0% contracts just never gonna work because 00:07:30.960 --> 00:07:32.420 align:start position:0% contracts just never gonna work because look<00:07:31.320> at<00:07:31.410> all<00:07:31.530> the<00:07:31.680> exploits<00:07:32.160> that<00:07:32.250> have 00:07:32.420 --> 00:07:32.430 align:start position:0% look at all the exploits that have 00:07:32.430 --> 00:07:34.850 align:start position:0% look at all the exploits that have happened<00:07:32.610> but<00:07:33.030> I<00:07:33.720> don't<00:07:34.230> think<00:07:34.440> it's<00:07:34.560> a<00:07:34.650> smart 00:07:34.850 --> 00:07:34.860 align:start position:0% happened but I don't think it's a smart 00:07:34.860 --> 00:07:37.100 align:start position:0% happened but I don't think it's a smart contract<00:07:35.070> thing<00:07:35.460> I<00:07:35.550> think<00:07:35.730> it's<00:07:36.210> well<00:07:37.020> of 00:07:37.100 --> 00:07:37.110 align:start position:0% contract thing I think it's well of 00:07:37.110 --> 00:07:38.360 align:start position:0% contract thing I think it's well of course<00:07:37.169> it's<00:07:37.500> it's<00:07:37.620> a<00:07:37.680> new<00:07:37.770> space<00:07:38.070> and<00:07:38.190> it's<00:07:38.340> a 00:07:38.360 --> 00:07:38.370 align:start position:0% course it's it's a new space and it's a 00:07:38.370 --> 00:07:41.000 align:start position:0% course it's it's a new space and it's a bit<00:07:38.490> hard<00:07:38.730> to<00:07:39.380> have<00:07:40.380> a<00:07:40.410> good<00:07:40.740> security 00:07:41.000 --> 00:07:41.010 align:start position:0% bit hard to have a good security 00:07:41.010 --> 00:07:43.370 align:start position:0% bit hard to have a good security framework<00:07:41.250> in<00:07:41.610> such<00:07:41.760> an<00:07:41.880> ass<00:07:42.000> in<00:07:42.150> space<00:07:42.390> but<00:07:42.660> I 00:07:43.370 --> 00:07:43.380 align:start position:0% framework in such an ass in space but I 00:07:43.380 --> 00:07:45.080 align:start position:0% framework in such an ass in space but I think<00:07:43.740> this<00:07:43.860> is<00:07:44.010> a<00:07:44.040> problem<00:07:44.400> that's<00:07:44.490> exists<00:07:45.000> in 00:07:45.080 --> 00:07:45.090 align:start position:0% think this is a problem that's exists in 00:07:45.090 --> 00:07:46.250 align:start position:0% think this is a problem that's exists in all<00:07:45.180> software<00:07:45.570> and<00:07:45.750> it's<00:07:45.840> just<00:07:45.990> far<00:07:46.230> more 00:07:46.250 --> 00:07:46.260 align:start position:0% all software and it's just far more 00:07:46.260 --> 00:07:49.580 align:start position:0% all software and it's just far more clear<00:07:46.890> in<00:07:47.250> the<00:07:47.940> smart<00:07:48.150> contract<00:07:48.300> space<00:07:48.750> and 00:07:49.580 --> 00:07:49.590 align:start position:0% clear in the smart contract space and 00:07:49.590 --> 00:07:52.880 align:start position:0% clear in the smart contract space and and<00:07:49.830> damages<00:07:50.640> are<00:07:50.760> reversible<00:07:51.450> so<00:07:52.080> it's<00:07:52.680> more 00:07:52.880 --> 00:07:52.890 align:start position:0% and damages are reversible so it's more 00:07:52.890 --> 00:07:54.710 align:start position:0% and damages are reversible so it's more it's<00:07:53.100> not<00:07:53.250> that<00:07:53.430> you<00:07:54.030> know<00:07:54.150> smart<00:07:54.419> contracts 00:07:54.710 --> 00:07:54.720 align:start position:0% it's not that you know smart contracts 00:07:54.720 --> 00:07:56.840 align:start position:0% it's not that you know smart contracts are<00:07:54.840> necessarily<00:07:55.320> hard<00:07:55.620> they're<00:07:55.979> hard<00:07:56.490> in<00:07:56.760> a 00:07:56.840 --> 00:07:56.850 align:start position:0% are necessarily hard they're hard in a 00:07:56.850 --> 00:07:58.130 align:start position:0% are necessarily hard they're hard in a different<00:07:57.180> way<00:07:57.330> but<00:07:57.570> I<00:07:57.600> would<00:07:57.690> say<00:07:57.870> that<00:07:58.020> the 00:07:58.130 --> 00:07:58.140 align:start position:0% different way but I would say that the 00:07:58.140 --> 00:07:59.750 align:start position:0% different way but I would say that the level<00:07:58.380> of<00:07:58.440> difficulty<00:07:58.710> is<00:07:58.830> similar<00:07:59.520> to<00:07:59.640> other 00:07:59.750 --> 00:07:59.760 align:start position:0% level of difficulty is similar to other 00:07:59.760 --> 00:08:02.420 align:start position:0% level of difficulty is similar to other domains<00:08:00.090> it's<00:08:00.540> just<00:08:00.750> that<00:08:00.900> it<00:08:01.169> if<00:08:01.620> you're<00:08:01.830> bad 00:08:02.420 --> 00:08:02.430 align:start position:0% domains it's just that it if you're bad 00:08:02.430 --> 00:08:04.760 align:start position:0% domains it's just that it if you're bad if<00:08:02.970> you<00:08:03.060> don't<00:08:03.240> do<00:08:03.479> your<00:08:03.750> due<00:08:04.229> diligence<00:08:04.290> you 00:08:04.760 --> 00:08:04.770 align:start position:0% if you don't do your due diligence you 00:08:04.770 --> 00:08:06.860 align:start position:0% if you don't do your due diligence you don't<00:08:05.250> follow<00:08:05.430> the<00:08:05.580> right<00:08:05.700> process<00:08:06.120> there<00:08:06.720> is 00:08:06.860 --> 00:08:06.870 align:start position:0% don't follow the right process there is 00:08:06.870 --> 00:08:09.110 align:start position:0% don't follow the right process there is no<00:08:07.169> hiding<00:08:07.410> behind<00:08:08.130> you<00:08:08.850> know<00:08:08.940> like<00:08:09.090> a 00:08:09.110 --> 00:08:09.120 align:start position:0% no hiding behind you know like a 00:08:09.120 --> 00:08:11.390 align:start position:0% no hiding behind you know like a firewall<00:08:09.990> or<00:08:10.140> closed<00:08:10.410> guard<00:08:10.650> and<00:08:10.890> there's<00:08:11.250> no 00:08:11.390 --> 00:08:11.400 align:start position:0% firewall or closed guard and there's no 00:08:11.400 --> 00:08:14.120 align:start position:0% firewall or closed guard and there's no I'll<00:08:12.030> report<00:08:12.390> it<00:08:12.540> if<00:08:12.720> I<00:08:12.960> have<00:08:13.169> to<00:08:13.410> it's<00:08:13.680> just 00:08:14.120 --> 00:08:14.130 align:start position:0% I'll report it if I have to it's just 00:08:14.130 --> 00:08:16.159 align:start position:0% I'll report it if I have to it's just there<00:08:14.310> for<00:08:14.340> the<00:08:14.520> world<00:08:14.729> and<00:08:15.000> so<00:08:15.180> all<00:08:15.540> mistakes 00:08:16.159 --> 00:08:16.169 align:start position:0% there for the world and so all mistakes 00:08:16.169 --> 00:08:17.300 align:start position:0% there for the world and so all mistakes are<00:08:16.410> very<00:08:16.740> clear 00:08:17.300 --> 00:08:17.310 align:start position:0% are very clear 00:08:17.310 --> 00:08:19.580 align:start position:0% are very clear so<00:08:17.760> it<00:08:17.880> seems<00:08:18.090> like<00:08:18.270> there's<00:08:18.450> more<00:08:18.660> but<00:08:19.260> you 00:08:19.580 --> 00:08:19.590 align:start position:0% so it seems like there's more but you 00:08:19.590 --> 00:08:21.560 align:start position:0% so it seems like there's more but you know<00:08:19.620> like<00:08:19.919> there's<00:08:20.160> the<00:08:20.700> banks<00:08:21.240> have<00:08:21.360> lost 00:08:21.560 --> 00:08:21.570 align:start position:0% know like there's the banks have lost 00:08:21.570 --> 00:08:23.210 align:start position:0% know like there's the banks have lost far<00:08:21.780> more<00:08:21.810> than<00:08:22.169> some<00:08:22.350> are<00:08:22.440> contracts<00:08:22.890> to<00:08:23.130> the 00:08:23.210 --> 00:08:23.220 align:start position:0% far more than some are contracts to the 00:08:23.220 --> 00:08:26.719 align:start position:0% far more than some are contracts to the date<00:08:23.400> to<00:08:23.640> date<00:08:25.040> yeah<00:08:26.040> so<00:08:26.190> I<00:08:26.250> think<00:08:26.340> for<00:08:26.580> me 00:08:26.719 --> 00:08:26.729 align:start position:0% date to date yeah so I think for me 00:08:26.729 --> 00:08:28.940 align:start position:0% date to date yeah so I think for me economic<00:08:27.540> sort<00:08:27.780> of<00:08:27.870> has<00:08:27.990> a<00:08:28.020> dual<00:08:28.350> nature<00:08:28.560> here 00:08:28.940 --> 00:08:28.950 align:start position:0% economic sort of has a dual nature here 00:08:28.950 --> 00:08:30.830 align:start position:0% economic sort of has a dual nature here in<00:08:29.370> one<00:08:29.640> way<00:08:29.790> it's<00:08:29.970> very<00:08:30.120> helpful<00:08:30.390> in<00:08:30.660> securing 00:08:30.830 --> 00:08:30.840 align:start position:0% in one way it's very helpful in securing 00:08:30.840 --> 00:08:32.630 align:start position:0% in one way it's very helpful in securing these<00:08:31.169> systems<00:08:31.590> so<00:08:31.860> something<00:08:32.280> like<00:08:32.430> just 00:08:32.630 --> 00:08:32.640 align:start position:0% these systems so something like just 00:08:32.640 --> 00:08:34.370 align:start position:0% these systems so something like just knowing<00:08:33.150> the<00:08:33.300> value<00:08:33.690> of<00:08:33.839> the<00:08:33.960> system<00:08:34.140> you're 00:08:34.370 --> 00:08:34.380 align:start position:0% knowing the value of the system you're 00:08:34.380 --> 00:08:36.440 align:start position:0% knowing the value of the system you're securing<00:08:34.890> is<00:08:35.039> not<00:08:35.640> something<00:08:36.030> that<00:08:36.060> you<00:08:36.240> can 00:08:36.440 --> 00:08:36.450 align:start position:0% securing is not something that you can 00:08:36.450 --> 00:08:38.600 align:start position:0% securing is not something that you can do<00:08:36.630> in<00:08:36.990> sort<00:08:37.409> of<00:08:37.440> classical<00:08:37.979> systems<00:08:38.339> like 00:08:38.600 --> 00:08:38.610 align:start position:0% do in sort of classical systems like 00:08:38.610 --> 00:08:40.670 align:start position:0% do in sort of classical systems like what<00:08:38.820> is<00:08:38.909> the<00:08:39.060> value<00:08:39.360> of<00:08:39.390> a<00:08:39.690> power<00:08:40.140> plants 00:08:40.670 --> 00:08:40.680 align:start position:0% what is the value of a power plants 00:08:40.680 --> 00:08:42.529 align:start position:0% what is the value of a power plants Ethernet<00:08:41.370> system<00:08:41.729> or<00:08:41.849> what<00:08:41.969> is<00:08:42.089> the<00:08:42.210> value<00:08:42.510> of 00:08:42.529 --> 00:08:42.539 align:start position:0% Ethernet system or what is the value of 00:08:42.539 --> 00:08:44.840 align:start position:0% Ethernet system or what is the value of an<00:08:43.440> election<00:08:43.890> system<00:08:44.039> for<00:08:44.370> a<00:08:44.400> county<00:08:44.730> or 00:08:44.840 --> 00:08:44.850 align:start position:0% an election system for a county or 00:08:44.850 --> 00:08:46.610 align:start position:0% an election system for a county or something<00:08:45.150> like<00:08:45.240> that<00:08:45.300> so<00:08:46.170> it<00:08:46.260> makes<00:08:46.290> some 00:08:46.610 --> 00:08:46.620 align:start position:0% something like that so it makes some 00:08:46.620 --> 00:08:48.470 align:start position:0% something like that so it makes some kinds<00:08:46.920> of<00:08:46.980> security<00:08:47.430> analyses<00:08:47.820> much<00:08:48.089> easier 00:08:48.470 --> 00:08:48.480 align:start position:0% kinds of security analyses much easier 00:08:48.480 --> 00:08:50.570 align:start position:0% kinds of security analyses much easier on<00:08:48.750> the<00:08:49.350> other<00:08:49.470> hand<00:08:49.709> because<00:08:49.920> a<00:08:50.100> lot<00:08:50.310> of<00:08:50.339> the 00:08:50.570 --> 00:08:50.580 align:start position:0% on the other hand because a lot of the 00:08:50.580 --> 00:08:52.310 align:start position:0% on the other hand because a lot of the security<00:08:50.850> assumptions<00:08:51.510> we<00:08:51.600> have<00:08:51.750> to<00:08:51.870> make<00:08:52.050> to 00:08:52.310 --> 00:08:52.320 align:start position:0% security assumptions we have to make to 00:08:52.320 --> 00:08:53.610 align:start position:0% security assumptions we have to make to show<00:08:52.470> that<00:08:52.620> these<00:08:52.770> systems<00:08:52.980> are<00:08:53.220> secure 00:08:53.610 --> 00:08:53.620 align:start position:0% show that these systems are secure 00:08:53.620 --> 00:08:56.070 align:start position:0% show that these systems are secure are<00:08:53.740> themselves<00:08:54.010> economic<00:08:54.970> it<00:08:55.510> also<00:08:55.660> sort<00:08:55.990> of 00:08:56.070 --> 00:08:56.080 align:start position:0% are themselves economic it also sort of 00:08:56.080 --> 00:08:57.390 align:start position:0% are themselves economic it also sort of brings<00:08:56.290> security<00:08:56.770> into<00:08:56.950> this<00:08:57.040> realm<00:08:57.310> of 00:08:57.390 --> 00:08:57.400 align:start position:0% brings security into this realm of 00:08:57.400 --> 00:08:58.980 align:start position:0% brings security into this realm of economics<00:08:58.029> which<00:08:58.120> is<00:08:58.150> much<00:08:58.420> more<00:08:58.630> subjective 00:08:58.980 --> 00:08:58.990 align:start position:0% economics which is much more subjective 00:08:58.990 --> 00:09:01.590 align:start position:0% economics which is much more subjective and<00:08:59.529> nebulous<00:08:59.950> we're<00:09:00.700> like<00:09:00.910> even<00:09:01.360> to 00:09:01.590 --> 00:09:01.600 align:start position:0% and nebulous we're like even to 00:09:01.600 --> 00:09:03.210 align:start position:0% and nebulous we're like even to economists<00:09:02.080> might<00:09:02.320> not<00:09:02.470> agree<00:09:02.650> on<00:09:02.740> basic 00:09:03.210 --> 00:09:03.220 align:start position:0% economists might not agree on basic 00:09:03.220 --> 00:09:05.550 align:start position:0% economists might not agree on basic definitions<00:09:03.760> or<00:09:03.940> basic<00:09:04.480> principles<00:09:04.960> so<00:09:05.529> I 00:09:05.550 --> 00:09:05.560 align:start position:0% definitions or basic principles so I 00:09:05.560 --> 00:09:06.930 align:start position:0% definitions or basic principles so I think<00:09:05.680> we're<00:09:05.860> gonna<00:09:05.980> see<00:09:06.250> a<00:09:06.279> lot<00:09:06.910> of 00:09:06.930 --> 00:09:06.940 align:start position:0% think we're gonna see a lot of 00:09:06.940 --> 00:09:09.630 align:start position:0% think we're gonna see a lot of subjective<00:09:07.870> security<00:09:08.470> sort<00:09:08.770> of<00:09:08.920> develop<00:09:09.430> as 00:09:09.630 --> 00:09:09.640 align:start position:0% subjective security sort of develop as 00:09:09.640 --> 00:09:11.070 align:start position:0% subjective security sort of develop as this<00:09:09.910> space<00:09:10.150> starts<00:09:10.600> to<00:09:10.690> differentiate 00:09:11.070 --> 00:09:11.080 align:start position:0% this space starts to differentiate 00:09:11.080 --> 00:09:13.920 align:start position:0% this space starts to differentiate itself<00:09:11.350> from<00:09:11.650> traditional<00:09:12.430> systems<00:09:12.790> and<00:09:13.089> I 00:09:13.920 --> 00:09:13.930 align:start position:0% itself from traditional systems and I 00:09:13.930 --> 00:09:16.350 align:start position:0% itself from traditional systems and I kind<00:09:14.529> of<00:09:14.589> look<00:09:14.710> forward<00:09:14.980> to<00:09:15.070> that<00:09:15.210> also<00:09:16.210> on<00:09:16.300> a 00:09:16.350 --> 00:09:16.360 align:start position:0% kind of look forward to that also on a 00:09:16.360 --> 00:09:18.810 align:start position:0% kind of look forward to that also on a personal<00:09:16.390> note<00:09:16.779> the<00:09:17.680> economic<00:09:18.460> nature<00:09:18.730> of 00:09:18.810 --> 00:09:18.820 align:start position:0% personal note the economic nature of 00:09:18.820 --> 00:09:20.220 align:start position:0% personal note the economic nature of these<00:09:18.910> systems<00:09:19.300> kind<00:09:19.510> of<00:09:19.660> keeps<00:09:19.839> me<00:09:20.020> up<00:09:20.110> at 00:09:20.220 --> 00:09:20.230 align:start position:0% these systems kind of keeps me up at 00:09:20.230 --> 00:09:22.200 align:start position:0% these systems kind of keeps me up at night<00:09:20.290> so<00:09:20.860> I<00:09:21.130> don't<00:09:21.520> know<00:09:21.670> about<00:09:21.760> you<00:09:22.000> guys<00:09:22.150> but 00:09:22.200 --> 00:09:22.210 align:start position:0% night so I don't know about you guys but 00:09:22.210 --> 00:09:24.570 align:start position:0% night so I don't know about you guys but when<00:09:22.870> I'm<00:09:22.990> doing<00:09:23.230> an<00:09:23.320> audit<00:09:23.470> I'm<00:09:23.770> you<00:09:24.100> know<00:09:24.220> I'm 00:09:24.570 --> 00:09:24.580 align:start position:0% when I'm doing an audit I'm you know I'm 00:09:24.580 --> 00:09:27.570 align:start position:0% when I'm doing an audit I'm you know I'm worried<00:09:25.270> about<00:09:25.390> that<00:09:25.720> a<00:09:25.990> lot<00:09:26.440> more<00:09:26.650> than<00:09:26.920> yeah 00:09:27.570 --> 00:09:27.580 align:start position:0% worried about that a lot more than yeah 00:09:27.580 --> 00:09:32.370 align:start position:0% worried about that a lot more than yeah it<00:09:28.000> motivating<00:09:28.510> exactly<00:09:30.779> yeah<00:09:31.779> that's<00:09:32.110> kind 00:09:32.370 --> 00:09:32.380 align:start position:0% it motivating exactly yeah that's kind 00:09:32.380 --> 00:09:35.460 align:start position:0% it motivating exactly yeah that's kind of<00:09:32.529> really<00:09:33.220> what<00:09:33.580> you<00:09:33.820> should<00:09:34.050> you<00:09:35.050> should<00:09:35.080> be 00:09:35.460 --> 00:09:35.470 align:start position:0% of really what you should you should be 00:09:35.470 --> 00:09:37.500 align:start position:0% of really what you should you should be awakened<00:09:35.890> that<00:09:36.010> because<00:09:36.580> of<00:09:36.700> that<00:09:36.730> because<00:09:36.880> I 00:09:37.500 --> 00:09:37.510 align:start position:0% awakened that because of that because I 00:09:37.510 --> 00:09:39.720 align:start position:0% awakened that because of that because I mean<00:09:38.410> if<00:09:38.529> you<00:09:38.589> come<00:09:38.710> from<00:09:38.890> from<00:09:39.190> traditional 00:09:39.720 --> 00:09:39.730 align:start position:0% mean if you come from from traditional 00:09:39.730 --> 00:09:41.790 align:start position:0% mean if you come from from traditional IT<00:09:39.820> security<00:09:40.260> you<00:09:41.260> try<00:09:41.470> and<00:09:41.589> find 00:09:41.790 --> 00:09:41.800 align:start position:0% IT security you try and find 00:09:41.800 --> 00:09:43.560 align:start position:0% IT security you try and find vulnerabilities<00:09:42.490> and<00:09:42.760> you<00:09:42.940> might<00:09:43.120> find<00:09:43.330> I 00:09:43.560 --> 00:09:43.570 align:start position:0% vulnerabilities and you might find I 00:09:43.570 --> 00:09:47.010 align:start position:0% vulnerabilities and you might find I know<00:09:43.630> like<00:09:44.020> cross-site<00:09:44.410> scripting<00:09:45.510> some<00:09:46.510> SQL 00:09:47.010 --> 00:09:47.020 align:start position:0% know like cross-site scripting some SQL 00:09:47.020 --> 00:09:49.980 align:start position:0% know like cross-site scripting some SQL injection<00:09:47.470> some<00:09:47.860> data<00:09:48.160> leakage<00:09:48.670> you<00:09:49.060> can<00:09:49.510> take 00:09:49.980 --> 00:09:49.990 align:start position:0% injection some data leakage you can take 00:09:49.990 --> 00:09:52.860 align:start position:0% injection some data leakage you can take money<00:09:50.620> even<00:09:51.130> maybe<00:09:51.370> sometimes<00:09:52.060> from<00:09:52.480> one 00:09:52.860 --> 00:09:52.870 align:start position:0% money even maybe sometimes from one 00:09:52.870 --> 00:09:55.170 align:start position:0% money even maybe sometimes from one account<00:09:53.140> and<00:09:53.470> do<00:09:53.620> something<00:09:54.070> but<00:09:54.760> the<00:09:54.910> stakes 00:09:55.170 --> 00:09:55.180 align:start position:0% account and do something but the stakes 00:09:55.180 --> 00:09:57.650 align:start position:0% account and do something but the stakes are<00:09:55.360> so<00:09:55.510> much<00:09:55.540> higher<00:09:55.720> here<00:09:56.350> and<00:09:56.529> it's<00:09:57.220> like 00:09:57.650 --> 00:09:57.660 align:start position:0% are so much higher here and it's like 00:09:57.660 --> 00:10:00.300 align:start position:0% are so much higher here and it's like someone<00:09:58.660> can<00:09:58.870> randomly<00:09:59.350> make<00:09:59.650> a<00:09:59.680> contract 00:10:00.300 --> 00:10:00.310 align:start position:0% someone can randomly make a contract 00:10:00.310 --> 00:10:03.269 align:start position:0% someone can randomly make a contract which<00:10:00.990> all<00:10:01.990> of<00:10:02.200> a<00:10:02.260> sudden<00:10:02.529> has<00:10:02.770> millions<00:10:03.190> of 00:10:03.269 --> 00:10:03.279 align:start position:0% which all of a sudden has millions of 00:10:03.279 --> 00:10:08.550 align:start position:0% which all of a sudden has millions of dollars<00:10:03.610> and<00:10:06.120> we<00:10:07.120> need<00:10:07.750> to<00:10:07.870> kind<00:10:08.050> of<00:10:08.170> realize 00:10:08.550 --> 00:10:08.560 align:start position:0% dollars and we need to kind of realize 00:10:08.560 --> 00:10:11.730 align:start position:0% dollars and we need to kind of realize that<00:10:08.890> the<00:10:09.790> stakes<00:10:10.150> are<00:10:10.300> so<00:10:10.330> much<00:10:10.570> higher<00:10:10.720> so<00:10:11.290> so 00:10:11.730 --> 00:10:11.740 align:start position:0% that the stakes are so much higher so so 00:10:11.740 --> 00:10:13.280 align:start position:0% that the stakes are so much higher so so easily<00:10:12.010> in<00:10:12.279> this<00:10:12.400> system<00:10:12.670> which<00:10:12.970> is<00:10:13.089> just 00:10:13.280 --> 00:10:13.290 align:start position:0% easily in this system which is just 00:10:13.290 --> 00:10:17.570 align:start position:0% easily in this system which is just negativities<00:10:14.290> with<00:10:14.589> currencies<00:10:15.130> stuff<00:10:15.670> oh 00:10:17.570 --> 00:10:17.580 align:start position:0% negativities with currencies stuff oh 00:10:17.580 --> 00:10:19.980 align:start position:0% negativities with currencies stuff oh keep<00:10:18.580> my<00:10:18.700> answer<00:10:18.910> brief<00:10:19.120> I<00:10:19.330> think<00:10:19.600> the<00:10:19.839> one 00:10:19.980 --> 00:10:19.990 align:start position:0% keep my answer brief I think the one 00:10:19.990 --> 00:10:21.750 align:start position:0% keep my answer brief I think the one side<00:10:20.260> of<00:10:20.350> all<00:10:20.440> anecdote<00:10:20.860> back<00:10:21.339> up<00:10:21.520> Phil's 00:10:21.750 --> 00:10:21.760 align:start position:0% side of all anecdote back up Phil's 00:10:21.760 --> 00:10:23.640 align:start position:0% side of all anecdote back up Phil's point<00:10:22.089> is<00:10:22.360> this<00:10:22.630> bank<00:10:22.900> chain<00:10:23.080> bug<00:10:23.290> that<00:10:23.440> came 00:10:23.640 --> 00:10:23.650 align:start position:0% point is this bank chain bug that came 00:10:23.650 --> 00:10:25.829 align:start position:0% point is this bank chain bug that came out<00:10:23.800> just<00:10:24.160> a<00:10:24.250> few<00:10:24.430> weeks<00:10:24.550> ago<00:10:24.700> where<00:10:25.450> the<00:10:25.660> blog 00:10:25.829 --> 00:10:25.839 align:start position:0% out just a few weeks ago where the blog 00:10:25.839 --> 00:10:27.930 align:start position:0% out just a few weeks ago where the blog post<00:10:26.110> described<00:10:26.620> hey<00:10:27.100> we<00:10:27.279> didn't<00:10:27.520> do<00:10:27.610> an<00:10:27.730> audit 00:10:27.930 --> 00:10:27.940 align:start position:0% post described hey we didn't do an audit 00:10:27.940 --> 00:10:29.850 align:start position:0% post described hey we didn't do an audit of<00:10:28.029> this<00:10:28.240> because<00:10:28.660> it<00:10:29.080> would<00:10:29.290> have<00:10:29.410> cost<00:10:29.589> more 00:10:29.850 --> 00:10:29.860 align:start position:0% of this because it would have cost more 00:10:29.860 --> 00:10:31.230 align:start position:0% of this because it would have cost more than<00:10:30.070> the<00:10:30.160> value<00:10:30.430> held<00:10:30.640> in<00:10:30.760> the<00:10:30.820> contract 00:10:31.230 --> 00:10:31.240 align:start position:0% than the value held in the contract 00:10:31.240 --> 00:10:33.720 align:start position:0% than the value held in the contract itself<00:10:31.860> that's<00:10:32.860> not<00:10:33.070> something<00:10:33.550> you<00:10:33.700> can 00:10:33.720 --> 00:10:33.730 align:start position:0% itself that's not something you can 00:10:33.730 --> 00:10:36.120 align:start position:0% itself that's not something you can really<00:10:33.880> do<00:10:34.300> with<00:10:34.510> a<00:10:34.540> classical<00:10:35.020> system<00:10:35.200> and<00:10:35.620> I 00:10:36.120 --> 00:10:36.130 align:start position:0% really do with a classical system and I 00:10:36.130 --> 00:10:37.530 align:start position:0% really do with a classical system and I totally<00:10:36.400> agree<00:10:36.730> with<00:10:36.760> Phil's<00:10:37.060> point<00:10:37.360> there 00:10:37.530 --> 00:10:37.540 align:start position:0% totally agree with Phil's point there 00:10:37.540 --> 00:10:38.850 align:start position:0% totally agree with Phil's point there that<00:10:37.570> this<00:10:37.839> is<00:10:38.020> something<00:10:38.320> completely<00:10:38.560> unique 00:10:38.850 --> 00:10:38.860 align:start position:0% that this is something completely unique 00:10:38.860 --> 00:10:42.060 align:start position:0% that this is something completely unique about<00:10:39.339> the<00:10:39.490> field<00:10:39.670> that<00:10:39.820> we're<00:10:39.940> in<00:10:40.650> so<00:10:41.650> I<00:10:41.980> think 00:10:42.060 --> 00:10:42.070 align:start position:0% about the field that we're in so I think 00:10:42.070 --> 00:10:43.710 align:start position:0% about the field that we're in so I think that's<00:10:42.370> the<00:10:42.670> biggest<00:10:43.089> difference<00:10:43.480> I<00:10:43.570> could 00:10:43.710 --> 00:10:43.720 align:start position:0% that's the biggest difference I could 00:10:43.720 --> 00:10:46.320 align:start position:0% that's the biggest difference I could point<00:10:43.870> to<00:10:43.930> yeah<00:10:44.560> cool 00:10:46.320 --> 00:10:46.330 align:start position:0% point to yeah cool 00:10:46.330 --> 00:10:47.670 align:start position:0% point to yeah cool and<00:10:46.630> so<00:10:46.750> actually<00:10:46.990> Dan<00:10:47.170> we<00:10:47.320> were<00:10:47.410> having<00:10:47.620> this 00:10:47.670 --> 00:10:47.680 align:start position:0% and so actually Dan we were having this 00:10:47.680 --> 00:10:49.530 align:start position:0% and so actually Dan we were having this conversation<00:10:47.770> the<00:10:48.250> other<00:10:48.310> day<00:10:48.550> about<00:10:48.580> bug 00:10:49.530 --> 00:10:49.540 align:start position:0% conversation the other day about bug 00:10:49.540 --> 00:10:52.740 align:start position:0% conversation the other day about bug bounties<00:10:49.930> and<00:10:50.670> whether<00:10:51.670> they're<00:10:51.910> a<00:10:52.300> good 00:10:52.740 --> 00:10:52.750 align:start position:0% bounties and whether they're a good 00:10:52.750 --> 00:10:55.440 align:start position:0% bounties and whether they're a good practice<00:10:53.110> or<00:10:53.670> using<00:10:54.670> tools<00:10:54.910> to<00:10:55.240> find 00:10:55.440 --> 00:10:55.450 align:start position:0% practice or using tools to find 00:10:55.450 --> 00:10:58.170 align:start position:0% practice or using tools to find repeatable<00:10:56.380> bugs<00:10:56.620> and<00:10:57.160> you<00:10:57.760> want<00:10:57.910> to<00:10:58.000> launch 00:10:58.170 --> 00:10:58.180 align:start position:0% repeatable bugs and you want to launch 00:10:58.180 --> 00:11:01.680 align:start position:0% repeatable bugs and you want to launch into<00:10:58.390> that<00:10:58.450> yeah<00:10:59.490> so<00:11:00.490> I<00:11:00.820> think<00:11:01.000> the<00:11:01.180> concept<00:11:01.390> of 00:11:01.680 --> 00:11:01.690 align:start position:0% into that yeah so I think the concept of 00:11:01.690 --> 00:11:03.420 align:start position:0% into that yeah so I think the concept of bug<00:11:01.870> bounties<00:11:02.230> makes<00:11:02.950> sense 00:11:03.420 --> 00:11:03.430 align:start position:0% bug bounties makes sense 00:11:03.430 --> 00:11:06.240 align:start position:0% bug bounties makes sense if<00:11:03.610> all<00:11:04.270> you<00:11:04.900> get<00:11:05.140> if<00:11:05.350> all<00:11:05.500> you<00:11:05.680> want<00:11:05.950> to<00:11:06.070> get 00:11:06.240 --> 00:11:06.250 align:start position:0% if all you get if all you want to get 00:11:06.250 --> 00:11:07.110 align:start position:0% if all you get if all you want to get from<00:11:06.459> an<00:11:06.579> auditor<00:11:06.940> is 00:11:07.110 --> 00:11:07.120 align:start position:0% from an auditor is 00:11:07.120 --> 00:11:08.850 align:start position:0% from an auditor is list<00:11:07.330> of<00:11:07.450> bugs<00:11:07.630> if<00:11:08.290> that's<00:11:08.589> all<00:11:08.710> you're 00:11:08.850 --> 00:11:08.860 align:start position:0% list of bugs if that's all you're 00:11:08.860 --> 00:11:10.860 align:start position:0% list of bugs if that's all you're expecting<00:11:09.370> to<00:11:09.460> receive<00:11:09.610> from<00:11:10.330> hiring<00:11:10.570> anybody 00:11:10.860 --> 00:11:10.870 align:start position:0% expecting to receive from hiring anybody 00:11:10.870 --> 00:11:12.960 align:start position:0% expecting to receive from hiring anybody on<00:11:11.140> stage<00:11:11.380> here<00:11:11.740> to<00:11:12.130> review<00:11:12.370> your<00:11:12.550> project<00:11:12.910> as 00:11:12.960 --> 00:11:12.970 align:start position:0% on stage here to review your project as 00:11:12.970 --> 00:11:14.460 align:start position:0% on stage here to review your project as a<00:11:13.000> list<00:11:13.240> of<00:11:13.360> bugs<00:11:13.540> and<00:11:13.750> sure<00:11:13.960> a<00:11:13.990> bug<00:11:14.200> battery 00:11:14.460 --> 00:11:14.470 align:start position:0% a list of bugs and sure a bug battery 00:11:14.470 --> 00:11:16.290 align:start position:0% a list of bugs and sure a bug battery makes<00:11:14.680> sense<00:11:14.890> I<00:11:15.100> wouldn't<00:11:15.670> think<00:11:15.760> that<00:11:15.880> any<00:11:16.120> of 00:11:16.290 --> 00:11:16.300 align:start position:0% makes sense I wouldn't think that any of 00:11:16.300 --> 00:11:18.269 align:start position:0% makes sense I wouldn't think that any of us<00:11:16.420> expect<00:11:17.170> to<00:11:17.260> only<00:11:17.440> provide<00:11:17.890> that<00:11:18.070> as<00:11:18.250> a 00:11:18.269 --> 00:11:18.279 align:start position:0% us expect to only provide that as a 00:11:18.279 --> 00:11:21.210 align:start position:0% us expect to only provide that as a service<00:11:19.140> second<00:11:20.140> really<00:11:20.320> big<00:11:20.470> issue<00:11:20.650> here<00:11:21.010> and 00:11:21.210 --> 00:11:21.220 align:start position:0% service second really big issue here and 00:11:21.220 --> 00:11:23.790 align:start position:0% service second really big issue here and really<00:11:21.880> you<00:11:22.060> should<00:11:22.210> be<00:11:22.240> upset<00:11:22.690> if<00:11:23.350> you've 00:11:23.790 --> 00:11:23.800 align:start position:0% really you should be upset if you've 00:11:23.800 --> 00:11:25.800 align:start position:0% really you should be upset if you've hired<00:11:24.010> someone<00:11:24.520> like<00:11:24.700> one<00:11:25.120> of<00:11:25.210> us<00:11:25.330> up<00:11:25.510> here<00:11:25.540> and 00:11:25.800 --> 00:11:25.810 align:start position:0% hired someone like one of us up here and 00:11:25.810 --> 00:11:27.269 align:start position:0% hired someone like one of us up here and that's<00:11:25.930> all<00:11:26.050> you<00:11:26.200> get<00:11:26.320> that's<00:11:26.620> that's<00:11:26.920> not<00:11:27.070> the 00:11:27.269 --> 00:11:27.279 align:start position:0% that's all you get that's that's not the 00:11:27.279 --> 00:11:29.070 align:start position:0% that's all you get that's that's not the service<00:11:27.610> that<00:11:27.790> you<00:11:27.880> should<00:11:28.120> get<00:11:28.330> in<00:11:28.779> order<00:11:28.960> to 00:11:29.070 --> 00:11:29.080 align:start position:0% service that you should get in order to 00:11:29.080 --> 00:11:31.110 align:start position:0% service that you should get in order to end<00:11:29.500> up<00:11:30.040> eventually<00:11:30.220> getting<00:11:30.580> secure<00:11:30.940> code 00:11:31.110 --> 00:11:31.120 align:start position:0% end up eventually getting secure code 00:11:31.120 --> 00:11:33.060 align:start position:0% end up eventually getting secure code the<00:11:31.810> second<00:11:32.140> thing<00:11:32.260> is<00:11:32.380> you<00:11:32.620> don't<00:11:32.860> know<00:11:32.950> how 00:11:33.060 --> 00:11:33.070 align:start position:0% the second thing is you don't know how 00:11:33.070 --> 00:11:35.760 align:start position:0% the second thing is you don't know how to<00:11:33.130> measure<00:11:33.490> the<00:11:33.790> output<00:11:34.240> of<00:11:34.720> having<00:11:35.500> that<00:11:35.589> bug 00:11:35.760 --> 00:11:35.770 align:start position:0% to measure the output of having that bug 00:11:35.770 --> 00:11:37.560 align:start position:0% to measure the output of having that bug bounty<00:11:36.100> so<00:11:36.279> what<00:11:36.490> did<00:11:36.610> you<00:11:36.730> receive<00:11:37.089> like<00:11:37.420> did 00:11:37.560 --> 00:11:37.570 align:start position:0% bounty so what did you receive like did 00:11:37.570 --> 00:11:39.480 align:start position:0% bounty so what did you receive like did enough<00:11:37.750> people<00:11:37.930> look<00:11:38.200> at<00:11:38.350> it<00:11:38.529> how<00:11:39.010> much<00:11:39.160> code 00:11:39.480 --> 00:11:39.490 align:start position:0% enough people look at it how much code 00:11:39.490 --> 00:11:41.970 align:start position:0% enough people look at it how much code coverage<00:11:39.880> was<00:11:40.060> gained<00:11:40.350> did<00:11:41.350> they<00:11:41.440> inspect<00:11:41.860> it 00:11:41.970 --> 00:11:41.980 align:start position:0% coverage was gained did they inspect it 00:11:41.980 --> 00:11:43.170 align:start position:0% coverage was gained did they inspect it for<00:11:42.070> the<00:11:42.190> issues<00:11:42.490> you<00:11:42.610> actually<00:11:42.910> care<00:11:43.089> about 00:11:43.170 --> 00:11:43.180 align:start position:0% for the issues you actually care about 00:11:43.180 --> 00:11:46.260 align:start position:0% for the issues you actually care about you<00:11:43.420> have<00:11:43.540> no<00:11:43.750> idea<00:11:44.220> a<00:11:45.220> lot<00:11:45.520> of<00:11:45.580> this<00:11:45.760> has<00:11:45.970> to<00:11:46.000> do 00:11:46.260 --> 00:11:46.270 align:start position:0% you have no idea a lot of this has to do 00:11:46.270 --> 00:11:47.670 align:start position:0% you have no idea a lot of this has to do with<00:11:46.390> just<00:11:46.630> a<00:11:46.690> lack<00:11:46.930> of<00:11:46.960> talent<00:11:47.500> in<00:11:47.589> the 00:11:47.670 --> 00:11:47.680 align:start position:0% with just a lack of talent in the 00:11:47.680 --> 00:11:49.650 align:start position:0% with just a lack of talent in the industry<00:11:47.710> like<00:11:48.339> people<00:11:49.120> at<00:11:49.240> trailer<00:11:49.450> bits 00:11:49.650 --> 00:11:49.660 align:start position:0% industry like people at trailer bits 00:11:49.660 --> 00:11:51.240 align:start position:0% industry like people at trailer bits have<00:11:49.810> done<00:11:49.960> bug<00:11:50.140> bounties<00:11:50.470> before<00:11:50.800> and<00:11:51.070> the 00:11:51.240 --> 00:11:51.250 align:start position:0% have done bug bounties before and the 00:11:51.250 --> 00:11:53.280 align:start position:0% have done bug bounties before and the way<00:11:51.400> that<00:11:51.550> we<00:11:51.640> do<00:11:51.760> it<00:11:51.910> is<00:11:52.029> we<00:11:52.060> spend<00:11:52.390> about<00:11:52.480> 10 00:11:53.280 --> 00:11:53.290 align:start position:0% way that we do it is we spend about 10 00:11:53.290 --> 00:11:54.900 align:start position:0% way that we do it is we spend about 10 minutes<00:11:53.500> to<00:11:53.890> just<00:11:54.070> scan<00:11:54.250> over<00:11:54.430> the<00:11:54.580> code<00:11:54.730> by 00:11:54.900 --> 00:11:54.910 align:start position:0% minutes to just scan over the code by 00:11:54.910 --> 00:11:56.880 align:start position:0% minutes to just scan over the code by hand<00:11:54.940> run<00:11:55.480> our<00:11:55.600> slither<00:11:55.900> static<00:11:56.290> analyzer<00:11:56.680> on 00:11:56.880 --> 00:11:56.890 align:start position:0% hand run our slither static analyzer on 00:11:56.890 --> 00:11:58.440 align:start position:0% hand run our slither static analyzer on it<00:11:57.040> and<00:11:57.190> if<00:11:57.520> it<00:11:57.610> doesn't<00:11:57.730> find<00:11:57.970> anything<00:11:58.210> we 00:11:58.440 --> 00:11:58.450 align:start position:0% it and if it doesn't find anything we 00:11:58.450 --> 00:12:00.660 align:start position:0% it and if it doesn't find anything we move<00:11:58.600> on<00:11:58.750> the<00:11:59.560> smartest<00:11:59.980> people<00:12:00.100> in<00:12:00.279> the<00:12:00.339> space 00:12:00.660 --> 00:12:00.670 align:start position:0% move on the smartest people in the space 00:12:00.670 --> 00:12:02.610 align:start position:0% move on the smartest people in the space are<00:12:00.910> not<00:12:01.270> doing<00:12:01.630> bug<00:12:01.779> bounties<00:12:02.170> because<00:12:02.470> we 00:12:02.610 --> 00:12:02.620 align:start position:0% are not doing bug bounties because we 00:12:02.620 --> 00:12:04.740 align:start position:0% are not doing bug bounties because we have<00:12:02.770> better<00:12:03.100> things<00:12:03.520> more<00:12:03.970> impactful<00:12:04.540> things 00:12:04.740 --> 00:12:04.750 align:start position:0% have better things more impactful things 00:12:04.750 --> 00:12:07.380 align:start position:0% have better things more impactful things to<00:12:04.960> do<00:12:05.140> to<00:12:05.740> improve<00:12:06.130> the<00:12:06.370> ecosystem<00:12:07.089> itself 00:12:07.380 --> 00:12:07.390 align:start position:0% to do to improve the ecosystem itself 00:12:07.390 --> 00:12:10.290 align:start position:0% to do to improve the ecosystem itself like<00:12:07.839> build<00:12:08.320> tools<00:12:08.650> and<00:12:09.010> do<00:12:09.100> research<00:12:09.279> than<00:12:10.120> to 00:12:10.290 --> 00:12:10.300 align:start position:0% like build tools and do research than to 00:12:10.300 --> 00:12:12.090 align:start position:0% like build tools and do research than to spend<00:12:10.510> it<00:12:10.630> all<00:12:10.690> on<00:12:10.750> bug<00:12:10.990> bounties<00:12:11.320> so<00:12:11.950> I<00:12:11.980> think 00:12:12.090 --> 00:12:12.100 align:start position:0% spend it all on bug bounties so I think 00:12:12.100 --> 00:12:14.070 align:start position:0% spend it all on bug bounties so I think that<00:12:12.490> a<00:12:12.700> lot<00:12:13.180> of<00:12:13.209> people<00:12:13.540> in<00:12:13.600> the<00:12:13.690> community 00:12:14.070 --> 00:12:14.080 align:start position:0% that a lot of people in the community 00:12:14.080 --> 00:12:15.930 align:start position:0% that a lot of people in the community have<00:12:14.140> been<00:12:14.200> misled<00:12:14.500> about<00:12:15.010> the<00:12:15.130> efficacy<00:12:15.400> of 00:12:15.930 --> 00:12:15.940 align:start position:0% have been misled about the efficacy of 00:12:15.940 --> 00:12:17.790 align:start position:0% have been misled about the efficacy of what<00:12:16.660> bug<00:12:16.870> bounties<00:12:17.230> actually<00:12:17.650> can 00:12:17.790 --> 00:12:17.800 align:start position:0% what bug bounties actually can 00:12:17.800 --> 00:12:19.740 align:start position:0% what bug bounties actually can accomplish<00:12:18.070> so<00:12:18.910> if<00:12:19.029> you<00:12:19.120> really<00:12:19.630> need 00:12:19.740 --> 00:12:19.750 align:start position:0% accomplish so if you really need 00:12:19.750 --> 00:12:21.360 align:start position:0% accomplish so if you really need security<00:12:20.200> guidance<00:12:20.650> you<00:12:20.860> really<00:12:21.100> should<00:12:21.279> be 00:12:21.360 --> 00:12:21.370 align:start position:0% security guidance you really should be 00:12:21.370 --> 00:12:23.519 align:start position:0% security guidance you really should be talking<00:12:21.580> to<00:12:22.180> a<00:12:22.209> smart<00:12:22.600> human<00:12:22.750> that<00:12:23.050> can<00:12:23.170> reason 00:12:23.519 --> 00:12:23.529 align:start position:0% talking to a smart human that can reason 00:12:23.529 --> 00:12:25.290 align:start position:0% talking to a smart human that can reason about<00:12:23.620> security<00:12:24.310> properties<00:12:24.730> of<00:12:24.850> your<00:12:24.940> system 00:12:25.290 --> 00:12:25.300 align:start position:0% about security properties of your system 00:12:25.300 --> 00:12:27.210 align:start position:0% about security properties of your system and<00:12:25.480> the<00:12:26.170> bug<00:12:26.320> bounty<00:12:26.440> thing<00:12:26.830> is<00:12:26.950> just<00:12:27.160> a 00:12:27.210 --> 00:12:27.220 align:start position:0% and the bug bounty thing is just a 00:12:27.220 --> 00:12:28.920 align:start position:0% and the bug bounty thing is just a secondary<00:12:27.670> kind<00:12:28.000> of<00:12:28.060> cover<00:12:28.240> your<00:12:28.420> ass<00:12:28.570> type 00:12:28.920 --> 00:12:28.930 align:start position:0% secondary kind of cover your ass type 00:12:28.930 --> 00:12:31.230 align:start position:0% secondary kind of cover your ass type type<00:12:29.410> deal<00:12:29.650> which<00:12:30.220> sure<00:12:30.580> you<00:12:30.730> could<00:12:30.850> have<00:12:31.029> you 00:12:31.230 --> 00:12:31.240 align:start position:0% type deal which sure you could have you 00:12:31.240 --> 00:12:32.640 align:start position:0% type deal which sure you could have you could<00:12:31.330> not<00:12:31.510> have<00:12:31.720> but<00:12:32.080> it's<00:12:32.200> not<00:12:32.380> the<00:12:32.529> first 00:12:32.640 --> 00:12:32.650 align:start position:0% could not have but it's not the first 00:12:32.650 --> 00:12:34.829 align:start position:0% could not have but it's not the first place<00:12:32.950> you<00:12:33.100> start<00:12:33.400> and<00:12:33.550> it<00:12:34.029> it<00:12:34.330> doesn't<00:12:34.540> cover 00:12:34.829 --> 00:12:34.839 align:start position:0% place you start and it it doesn't cover 00:12:34.839 --> 00:12:36.630 align:start position:0% place you start and it it doesn't cover nearly<00:12:35.200> as<00:12:35.410> many<00:12:35.529> bases<00:12:35.800> as<00:12:36.100> people<00:12:36.370> think<00:12:36.550> it 00:12:36.630 --> 00:12:36.640 align:start position:0% nearly as many bases as people think it 00:12:36.640 --> 00:12:42.740 align:start position:0% nearly as many bases as people think it does<00:12:36.790> I<00:12:38.339> agree<00:12:39.339> I<00:12:39.550> don't<00:12:40.540> have<00:12:40.630> anything<00:12:40.839> that 00:12:42.740 --> 00:12:42.750 align:start position:0% does I agree I don't have anything that 00:12:42.750 --> 00:12:47.250 align:start position:0% does I agree I don't have anything that I'll<00:12:43.750> go<00:12:44.290> and<00:12:44.529> yeah<00:12:45.370> I<00:12:45.400> know<00:12:45.520> I<00:12:45.640> agree<00:12:46.570> that<00:12:46.990> the 00:12:47.250 --> 00:12:47.260 align:start position:0% I'll go and yeah I know I agree that the 00:12:47.260 --> 00:12:49.860 align:start position:0% I'll go and yeah I know I agree that the efficacy<00:12:47.529> of<00:12:47.860> background<00:12:48.310> T's<00:12:48.459> is<00:12:48.730> dubious<00:12:49.510> in 00:12:49.860 --> 00:12:49.870 align:start position:0% efficacy of background T's is dubious in 00:12:49.870 --> 00:12:51.870 align:start position:0% efficacy of background T's is dubious in certain<00:12:50.440> some<00:12:50.620> cats<00:12:50.830> circumstances<00:12:51.700> I<00:12:51.820> think 00:12:51.870 --> 00:12:51.880 align:start position:0% certain some cats circumstances I think 00:12:51.880 --> 00:12:55.019 align:start position:0% certain some cats circumstances I think like<00:12:52.330> if<00:12:52.540> you<00:12:53.080> have<00:12:53.380> like<00:12:53.800> the<00:12:54.400> contract<00:12:54.910> is 00:12:55.019 --> 00:12:55.029 align:start position:0% like if you have like the contract is 00:12:55.029 --> 00:12:57.329 align:start position:0% like if you have like the contract is the<00:12:55.240> bug<00:12:55.390> bounty<00:12:55.540> in<00:12:55.959> a<00:12:56.050> lot<00:12:56.200> of<00:12:56.320> cases<00:12:56.890> right 00:12:57.329 --> 00:12:57.339 align:start position:0% the bug bounty in a lot of cases right 00:12:57.339 --> 00:12:59.160 align:start position:0% the bug bounty in a lot of cases right if<00:12:57.550> you<00:12:57.880> have<00:12:58.029> a<00:12:58.060> monetary<00:12:58.600> compensation<00:12:58.750> for 00:12:59.160 --> 00:12:59.170 align:start position:0% if you have a monetary compensation for 00:12:59.170 --> 00:13:02.190 align:start position:0% if you have a monetary compensation for being<00:12:59.560> ethical<00:13:00.160> that's<00:13:00.610> like<00:13:01.020> you<00:13:02.020> know<00:13:02.050> an 00:13:02.190 --> 00:13:02.200 align:start position:0% being ethical that's like you know an 00:13:02.200 --> 00:13:05.430 align:start position:0% being ethical that's like you know an auxiliary<00:13:02.529> incentive<00:13:03.370> like<00:13:03.760> if<00:13:04.260> really<00:13:05.260> the 00:13:05.430 --> 00:13:05.440 align:start position:0% auxiliary incentive like if really the 00:13:05.440 --> 00:13:07.860 align:start position:0% auxiliary incentive like if really the people<00:13:05.620> who<00:13:05.980> have<00:13:06.220> who<00:13:06.490> go<00:13:06.700> around<00:13:07.060> looking<00:13:07.750> at 00:13:07.860 --> 00:13:07.870 align:start position:0% people who have who go around looking at 00:13:07.870 --> 00:13:09.870 align:start position:0% people who have who go around looking at contracts<00:13:08.440> and<00:13:09.250> testing<00:13:09.640> if<00:13:09.730> they're 00:13:09.870 --> 00:13:09.880 align:start position:0% contracts and testing if they're 00:13:09.880 --> 00:13:10.980 align:start position:0% contracts and testing if they're vulnerable 00:13:10.980 --> 00:13:10.990 align:start position:0% vulnerable 00:13:10.990 --> 00:13:13.079 align:start position:0% vulnerable you<00:13:11.680> know<00:13:11.770> randomly<00:13:12.220> generally<00:13:12.880> those<00:13:13.060> are 00:13:13.079 --> 00:13:13.089 align:start position:0% you know randomly generally those are 00:13:13.089 --> 00:13:15.030 align:start position:0% you know randomly generally those are all<00:13:13.480> so<00:13:13.750> unless<00:13:14.560> you're<00:13:14.770> like<00:13:14.890> you<00:13:15.010> know 00:13:15.030 --> 00:13:15.040 align:start position:0% all so unless you're like you know 00:13:15.040 --> 00:13:16.500 align:start position:0% all so unless you're like you know unless<00:13:15.610> you're<00:13:15.730> one<00:13:15.910> of<00:13:16.000> those<00:13:16.060> hacker<00:13:16.270> one 00:13:16.500 --> 00:13:16.510 align:start position:0% unless you're one of those hacker one 00:13:16.510 --> 00:13:18.000 align:start position:0% unless you're one of those hacker one types<00:13:16.720> those<00:13:17.200> are<00:13:17.350> not<00:13:17.500> the<00:13:17.620> people<00:13:17.860> who<00:13:17.890> are 00:13:18.000 --> 00:13:18.010 align:start position:0% types those are not the people who are 00:13:18.010 --> 00:13:19.410 align:start position:0% types those are not the people who are going<00:13:18.160> to<00:13:18.220> report<00:13:18.640> the<00:13:18.700> bug<00:13:18.850> bounty<00:13:19.060> to<00:13:19.329> you 00:13:19.410 --> 00:13:19.420 align:start position:0% going to report the bug bounty to you 00:13:19.420 --> 00:13:20.850 align:start position:0% going to report the bug bounty to you there's<00:13:19.630> like<00:13:19.780> many<00:13:20.050> there's<00:13:20.680> my 00:13:20.850 --> 00:13:20.860 align:start position:0% there's like many there's my 00:13:20.860 --> 00:13:22.710 align:start position:0% there's like many there's my other<00:13:21.040> ways<00:13:21.190> through<00:13:21.490> the<00:13:21.880> profit<00:13:22.330> besides 00:13:22.710 --> 00:13:22.720 align:start position:0% other ways through the profit besides 00:13:22.720 --> 00:13:25.110 align:start position:0% other ways through the profit besides reporting<00:13:23.230> it<00:13:23.320> to<00:13:23.470> the<00:13:23.680> arena<00:13:24.400> responsibly<00:13:24.970> to 00:13:25.110 --> 00:13:25.120 align:start position:0% reporting it to the arena responsibly to 00:13:25.120 --> 00:13:28.080 align:start position:0% reporting it to the arena responsibly to the<00:13:25.240> to<00:13:25.480> the<00:13:25.570> company<00:13:25.930> and<00:13:26.280> you<00:13:27.280> know<00:13:27.430> and<00:13:27.670> like 00:13:28.080 --> 00:13:28.090 align:start position:0% the to the company and you know and like 00:13:28.090 --> 00:13:29.850 align:start position:0% the to the company and you know and like I'd<00:13:28.270> echoed<00:13:28.630> a<00:13:28.720> statement<00:13:28.960> that<00:13:29.410> you 00:13:29.850 --> 00:13:29.860 align:start position:0% I'd echoed a statement that you 00:13:29.860 --> 00:13:32.660 align:start position:0% I'd echoed a statement that you shouldn't<00:13:30.310> really<00:13:30.430> just<00:13:30.970> be<00:13:31.180> looking<00:13:32.080> for 00:13:32.660 --> 00:13:32.670 align:start position:0% shouldn't really just be looking for 00:13:32.670 --> 00:13:35.250 align:start position:0% shouldn't really just be looking for lists<00:13:33.670> of<00:13:33.820> bugs<00:13:34.090> or<00:13:34.420> vulnerabilities<00:13:35.080> like 00:13:35.250 --> 00:13:35.260 align:start position:0% lists of bugs or vulnerabilities like 00:13:35.260 --> 00:13:36.900 align:start position:0% lists of bugs or vulnerabilities like how<00:13:35.410> many<00:13:35.470> vulnerabilities<00:13:36.070> did<00:13:36.670> this<00:13:36.790> guy 00:13:36.900 --> 00:13:36.910 align:start position:0% how many vulnerabilities did this guy 00:13:36.910 --> 00:13:39.300 align:start position:0% how many vulnerabilities did this guy find<00:13:37.210> shouldn't<00:13:37.780> be<00:13:37.840> the<00:13:37.930> metric<00:13:38.080> for<00:13:38.470> quality 00:13:39.300 --> 00:13:39.310 align:start position:0% find shouldn't be the metric for quality 00:13:39.310 --> 00:13:41.280 align:start position:0% find shouldn't be the metric for quality security<00:13:39.460> audit<00:13:39.880> it<00:13:40.030> should<00:13:40.180> be<00:13:40.270> how<00:13:40.870> are<00:13:41.080> we 00:13:41.280 --> 00:13:41.290 align:start position:0% security audit it should be how are we 00:13:41.290 --> 00:13:43.080 align:start position:0% security audit it should be how are we informed<00:13:41.800> now<00:13:41.950> to<00:13:42.010> make<00:13:42.250> better<00:13:42.460> decisions<00:13:42.940> in 00:13:43.080 --> 00:13:43.090 align:start position:0% informed now to make better decisions in 00:13:43.090 --> 00:13:45.630 align:start position:0% informed now to make better decisions in the<00:13:43.120> future<00:13:43.210> how<00:13:43.990> have<00:13:44.440> we<00:13:44.470> gotten<00:13:44.890> comments 00:13:45.630 --> 00:13:45.640 align:start position:0% the future how have we gotten comments 00:13:45.640 --> 00:13:47.970 align:start position:0% the future how have we gotten comments on<00:13:45.760> improving<00:13:46.150> our<00:13:46.270> process<00:13:46.750> such<00:13:47.140> that<00:13:47.380> you 00:13:47.970 --> 00:13:47.980 align:start position:0% on improving our process such that you 00:13:47.980 --> 00:13:49.950 align:start position:0% on improving our process such that you know<00:13:48.100> we<00:13:48.280> we<00:13:48.580> don't<00:13:48.790> make<00:13:49.060> fragile<00:13:49.540> code<00:13:49.780> we 00:13:49.950 --> 00:13:49.960 align:start position:0% know we we don't make fragile code we 00:13:49.960 --> 00:13:51.120 align:start position:0% know we we don't make fragile code we don't<00:13:49.990> get<00:13:50.230> into<00:13:50.380> that<00:13:50.530> situations<00:13:50.980> in<00:13:51.070> the 00:13:51.120 --> 00:13:51.130 align:start position:0% don't get into that situations in the 00:13:51.130 --> 00:13:54.840 align:start position:0% don't get into that situations in the future<00:13:51.430> I<00:13:52.060> think<00:13:52.960> realistically<00:13:53.640> both<00:13:54.640> in 00:13:54.840 --> 00:13:54.850 align:start position:0% future I think realistically both in 00:13:54.850 --> 00:13:57.420 align:start position:0% future I think realistically both in this<00:13:55.090> industry<00:13:55.360> and<00:13:55.660> outside<00:13:55.750> if<00:13:56.650> possible 00:13:57.420 --> 00:13:57.430 align:start position:0% this industry and outside if possible 00:13:57.430 --> 00:13:58.770 align:start position:0% this industry and outside if possible it's<00:13:57.670> always<00:13:57.940> best<00:13:58.120> to<00:13:58.210> hire<00:13:58.450> a<00:13:58.480> security 00:13:58.770 --> 00:13:58.780 align:start position:0% it's always best to hire a security 00:13:58.780 --> 00:14:00.810 align:start position:0% it's always best to hire a security person<00:13:59.110> internally<00:13:59.770> right<00:14:00.070> like<00:14:00.460> someone 00:14:00.810 --> 00:14:00.820 align:start position:0% person internally right like someone 00:14:00.820 --> 00:14:02.190 align:start position:0% person internally right like someone should<00:14:00.940> be<00:14:01.090> with<00:14:01.120> you<00:14:01.450> every<00:14:01.720> step<00:14:01.780> of<00:14:01.930> the<00:14:02.050> way 00:14:02.190 --> 00:14:02.200 align:start position:0% should be with you every step of the way 00:14:02.200 --> 00:14:05.040 align:start position:0% should be with you every step of the way security<00:14:02.860> is<00:14:02.980> not<00:14:03.010> like<00:14:03.640> a<00:14:03.670> an<00:14:04.390> afterthought 00:14:05.040 --> 00:14:05.050 align:start position:0% security is not like a an afterthought 00:14:05.050 --> 00:14:06.570 align:start position:0% security is not like a an afterthought it's<00:14:05.320> not<00:14:05.470> like<00:14:05.650> a<00:14:05.680> thing<00:14:06.130> at<00:14:06.250> the<00:14:06.310> end<00:14:06.340> of<00:14:06.520> the 00:14:06.570 --> 00:14:06.580 align:start position:0% it's not like a thing at the end of the 00:14:06.580 --> 00:14:09.090 align:start position:0% it's not like a thing at the end of the process<00:14:06.760> it's<00:14:07.390> part<00:14:08.020> of<00:14:08.200> the<00:14:08.590> process<00:14:08.980> of 00:14:09.090 --> 00:14:09.100 align:start position:0% process it's part of the process of 00:14:09.100 --> 00:14:11.550 align:start position:0% process it's part of the process of creating<00:14:09.160> software<00:14:09.790> and<00:14:09.940> really<00:14:10.870> in<00:14:11.230> the 00:14:11.550 --> 00:14:11.560 align:start position:0% creating software and really in the 00:14:11.560 --> 00:14:13.770 align:start position:0% creating software and really in the blockchain<00:14:11.740> space<00:14:12.240> you<00:14:13.240> know<00:14:13.330> it's<00:14:13.480> this<00:14:13.720> is 00:14:13.770 --> 00:14:13.780 align:start position:0% blockchain space you know it's this is 00:14:13.780 --> 00:14:15.540 align:start position:0% blockchain space you know it's this is very<00:14:14.080> evident<00:14:14.290> but<00:14:14.740> I<00:14:14.800> hope<00:14:15.010> that<00:14:15.040> you<00:14:15.460> know 00:14:15.540 --> 00:14:15.550 align:start position:0% very evident but I hope that you know 00:14:15.550 --> 00:14:17.370 align:start position:0% very evident but I hope that you know like<00:14:15.820> even<00:14:16.180> the<00:14:16.390> traditional<00:14:16.810> industry 00:14:17.370 --> 00:14:17.380 align:start position:0% like even the traditional industry 00:14:17.380 --> 00:14:20.940 align:start position:0% like even the traditional industry starts<00:14:18.010> to<00:14:18.130> think<00:14:18.310> more<00:14:18.490> this<00:14:18.670> way<00:14:19.530> so<00:14:20.530> I<00:14:20.740> agree 00:14:20.940 --> 00:14:20.950 align:start position:0% starts to think more this way so I agree 00:14:20.950 --> 00:14:22.380 align:start position:0% starts to think more this way so I agree with<00:14:21.070> most<00:14:21.190> of<00:14:21.400> what's<00:14:21.550> been<00:14:21.700> said<00:14:21.880> so<00:14:22.120> far 00:14:22.380 --> 00:14:22.390 align:start position:0% with most of what's been said so far 00:14:22.390 --> 00:14:24.360 align:start position:0% with most of what's been said so far I<00:14:22.570> do<00:14:22.660> think<00:14:23.080> dan<00:14:23.560> was<00:14:23.800> maybe<00:14:23.980> a<00:14:24.070> little<00:14:24.130> too 00:14:24.360 --> 00:14:24.370 align:start position:0% I do think dan was maybe a little too 00:14:24.370 --> 00:14:28.320 align:start position:0% I do think dan was maybe a little too too<00:14:24.940> negative<00:14:25.330> on<00:14:25.480> bug<00:14:25.690> bounties<00:14:26.520> so<00:14:27.520> the<00:14:28.240> way 00:14:28.320 --> 00:14:28.330 align:start position:0% too negative on bug bounties so the way 00:14:28.330 --> 00:14:29.520 align:start position:0% too negative on bug bounties so the way I<00:14:28.360> see<00:14:28.600> bug<00:14:28.780> bounties<00:14:29.110> is<00:14:29.260> that<00:14:29.410> it's 00:14:29.520 --> 00:14:29.530 align:start position:0% I see bug bounties is that it's 00:14:29.530 --> 00:14:32.010 align:start position:0% I see bug bounties is that it's obviously<00:14:29.890> not<00:14:30.130> a<00:14:30.460> sort<00:14:31.120> of<00:14:31.210> substitute<00:14:31.810> for 00:14:32.010 --> 00:14:32.020 align:start position:0% obviously not a sort of substitute for 00:14:32.020 --> 00:14:33.960 align:start position:0% obviously not a sort of substitute for doing<00:14:32.230> your<00:14:32.350> homework<00:14:32.530> so<00:14:33.100> it's<00:14:33.310> your<00:14:33.490> job<00:14:33.520> as 00:14:33.960 --> 00:14:33.970 align:start position:0% doing your homework so it's your job as 00:14:33.970 --> 00:14:36.300 align:start position:0% doing your homework so it's your job as as<00:14:34.330> a<00:14:34.360> company<00:14:34.840> to<00:14:35.020> ensure<00:14:35.650> that<00:14:35.860> you<00:14:35.950> hire<00:14:36.130> the 00:14:36.300 --> 00:14:36.310 align:start position:0% as a company to ensure that you hire the 00:14:36.310 --> 00:14:37.560 align:start position:0% as a company to ensure that you hire the right<00:14:36.340> people<00:14:36.610> to<00:14:36.880> have<00:14:37.000> them<00:14:37.120> put<00:14:37.270> into<00:14:37.390> your 00:14:37.560 --> 00:14:37.570 align:start position:0% right people to have them put into your 00:14:37.570 --> 00:14:39.450 align:start position:0% right people to have them put into your code<00:14:37.780> that<00:14:38.020> you<00:14:38.410> hire<00:14:38.620> external<00:14:38.890> people<00:14:39.250> as 00:14:39.450 --> 00:14:39.460 align:start position:0% code that you hire external people as 00:14:39.460 --> 00:14:41.340 align:start position:0% code that you hire external people as well<00:14:39.640> as<00:14:39.730> yourselves<00:14:40.090> that<00:14:40.720> you<00:14:40.840> run<00:14:41.050> security 00:14:41.340 --> 00:14:41.350 align:start position:0% well as yourselves that you run security 00:14:41.350 --> 00:14:43.440 align:start position:0% well as yourselves that you run security processes<00:14:42.070> and<00:14:42.370> engage<00:14:42.640> in<00:14:42.820> critical<00:14:43.000> review 00:14:43.440 --> 00:14:43.450 align:start position:0% processes and engage in critical review 00:14:43.450 --> 00:14:45.450 align:start position:0% processes and engage in critical review of<00:14:43.540> your<00:14:43.630> software<00:14:43.990> that<00:14:44.680> you<00:14:44.770> understand<00:14:45.310> the 00:14:45.450 --> 00:14:45.460 align:start position:0% of your software that you understand the 00:14:45.460 --> 00:14:46.860 align:start position:0% of your software that you understand the limitations<00:14:46.000> of<00:14:46.120> the<00:14:46.240> people<00:14:46.510> you're<00:14:46.630> hiring 00:14:46.860 --> 00:14:46.870 align:start position:0% limitations of the people you're hiring 00:14:46.870 --> 00:14:49.080 align:start position:0% limitations of the people you're hiring because<00:14:47.320> while<00:14:47.920> all<00:14:48.130> of<00:14:48.280> us<00:14:48.400> are<00:14:48.580> a<00:14:48.610> competent 00:14:49.080 --> 00:14:49.090 align:start position:0% because while all of us are a competent 00:14:49.090 --> 00:14:50.640 align:start position:0% because while all of us are a competent security<00:14:49.420> professionals<00:14:49.960> were<00:14:50.110> humans<00:14:50.470> who 00:14:50.640 --> 00:14:50.650 align:start position:0% security professionals were humans who 00:14:50.650 --> 00:14:52.020 align:start position:0% security professionals were humans who have<00:14:50.770> like<00:14:50.980> a<00:14:51.010> certain<00:14:51.370> amount<00:14:51.490> of<00:14:51.610> hours<00:14:51.880> in 00:14:52.020 --> 00:14:52.030 align:start position:0% have like a certain amount of hours in 00:14:52.030 --> 00:14:53.610 align:start position:0% have like a certain amount of hours in the<00:14:52.120> day<00:14:52.270> and<00:14:52.300> we<00:14:52.540> all<00:14:52.780> focus<00:14:53.170> on<00:14:53.320> different 00:14:53.610 --> 00:14:53.620 align:start position:0% the day and we all focus on different 00:14:53.620 --> 00:14:56.340 align:start position:0% the day and we all focus on different aspects<00:14:53.950> of<00:14:54.100> security<00:14:54.420> so<00:14:55.420> it's<00:14:55.540> your<00:14:55.810> job<00:14:56.110> to 00:14:56.340 --> 00:14:56.350 align:start position:0% aspects of security so it's your job to 00:14:56.350 --> 00:14:58.230 align:start position:0% aspects of security so it's your job to ensure<00:14:56.830> you<00:14:56.920> hire<00:14:57.130> a<00:14:57.160> diversity<00:14:57.700> of<00:14:57.850> opinions 00:14:58.230 --> 00:14:58.240 align:start position:0% ensure you hire a diversity of opinions 00:14:58.240 --> 00:15:00.060 align:start position:0% ensure you hire a diversity of opinions and<00:14:58.390> skillsets<00:14:58.900> to<00:14:59.170> sort<00:14:59.380> of<00:14:59.470> inform<00:14:59.950> you 00:15:00.060 --> 00:15:00.070 align:start position:0% and skillsets to sort of inform you 00:15:00.070 --> 00:15:02.070 align:start position:0% and skillsets to sort of inform you about<00:15:00.310> how<00:15:00.520> to<00:15:00.580> proceed<00:15:00.880> with<00:15:01.150> your<00:15:01.180> code<00:15:01.450> but 00:15:02.070 --> 00:15:02.080 align:start position:0% about how to proceed with your code but 00:15:02.080 --> 00:15:03.480 align:start position:0% about how to proceed with your code but at<00:15:02.170> the<00:15:02.260> same<00:15:02.410> time<00:15:02.620> if<00:15:02.770> you<00:15:02.830> don't<00:15:03.040> have<00:15:03.220> a<00:15:03.250> bug 00:15:03.480 --> 00:15:03.490 align:start position:0% at the same time if you don't have a bug 00:15:03.490 --> 00:15:05.310 align:start position:0% at the same time if you don't have a bug bounty<00:15:03.640> you're<00:15:04.570> sort<00:15:04.780> of<00:15:04.840> skewing<00:15:05.230> the 00:15:05.310 --> 00:15:05.320 align:start position:0% bounty you're sort of skewing the 00:15:05.320 --> 00:15:06.870 align:start position:0% bounty you're sort of skewing the incentives<00:15:05.800> for<00:15:05.980> anyone<00:15:06.310> who<00:15:06.430> eventually 00:15:06.870 --> 00:15:06.880 align:start position:0% incentives for anyone who eventually 00:15:06.880 --> 00:15:09.210 align:start position:0% incentives for anyone who eventually finds<00:15:07.150> a<00:15:07.210> vulnerability<00:15:07.570> in<00:15:07.780> your<00:15:07.930> program<00:15:08.290> so 00:15:09.210 --> 00:15:09.220 align:start position:0% finds a vulnerability in your program so 00:15:09.220 --> 00:15:10.710 align:start position:0% finds a vulnerability in your program so you<00:15:09.280> want<00:15:09.580> to<00:15:09.730> have<00:15:09.880> something<00:15:10.180> to<00:15:10.480> sort<00:15:10.660> of 00:15:10.710 --> 00:15:10.720 align:start position:0% you want to have something to sort of 00:15:10.720 --> 00:15:12.090 align:start position:0% you want to have something to sort of offer<00:15:10.960> somebody<00:15:11.410> who<00:15:11.530> does<00:15:11.680> find<00:15:11.950> that 00:15:12.090 --> 00:15:12.100 align:start position:0% offer somebody who does find that 00:15:12.100 --> 00:15:13.620 align:start position:0% offer somebody who does find that vulnerability<00:15:12.490> to<00:15:12.790> stop<00:15:13.030> them<00:15:13.270> from<00:15:13.450> just 00:15:13.620 --> 00:15:13.630 align:start position:0% vulnerability to stop them from just 00:15:13.630 --> 00:15:14.970 align:start position:0% vulnerability to stop them from just taking<00:15:13.930> it<00:15:14.020> to<00:15:14.080> the<00:15:14.170> chain<00:15:14.410> or<00:15:14.590> something<00:15:14.770> like 00:15:14.970 --> 00:15:14.980 align:start position:0% taking it to the chain or something like 00:15:14.980 --> 00:15:16.500 align:start position:0% taking it to the chain or something like that<00:15:15.040> so<00:15:15.910> I<00:15:15.940> think<00:15:16.060> from<00:15:16.330> an<00:15:16.420> economic 00:15:16.500 --> 00:15:16.510 align:start position:0% that so I think from an economic 00:15:16.510 --> 00:15:19.080 align:start position:0% that so I think from an economic security<00:15:17.170> perspective<00:15:18.070> bug<00:15:18.610> bounties<00:15:18.970> are 00:15:19.080 --> 00:15:19.090 align:start position:0% security perspective bug bounties are 00:15:19.090 --> 00:15:23.060 align:start position:0% security perspective bug bounties are sort<00:15:19.270> of<00:15:19.330> necessary<00:15:19.540> but<00:15:20.080> not<00:15:20.110> sufficient 00:15:23.060 --> 00:15:23.070 align:start position:0% 00:15:23.070 --> 00:15:25.230 align:start position:0% just<00:15:24.070> to<00:15:24.130> respond<00:15:24.460> to<00:15:24.550> that<00:15:24.640> I<00:15:24.700> agree<00:15:24.880> with 00:15:25.230 --> 00:15:25.240 align:start position:0% just to respond to that I agree with 00:15:25.240 --> 00:15:26.970 align:start position:0% just to respond to that I agree with everything<00:15:25.450> you<00:15:25.660> said<00:15:25.810> and<00:15:26.050> I<00:15:26.410> think<00:15:26.620> that<00:15:26.800> if 00:15:26.970 --> 00:15:26.980 align:start position:0% everything you said and I think that if 00:15:26.980 --> 00:15:28.350 align:start position:0% everything you said and I think that if you<00:15:27.100> don't<00:15:27.250> have<00:15:27.430> an<00:15:27.520> easy<00:15:27.730> way<00:15:27.940> to<00:15:28.000> report 00:15:28.350 --> 00:15:28.360 align:start position:0% you don't have an easy way to report 00:15:28.360 --> 00:15:29.520 align:start position:0% you don't have an easy way to report bugs<00:15:28.600> that<00:15:28.810> are<00:15:28.870> discovered<00:15:29.320> in<00:15:29.380> your 00:15:29.520 --> 00:15:29.530 align:start position:0% bugs that are discovered in your 00:15:29.530 --> 00:15:31.380 align:start position:0% bugs that are discovered in your application<00:15:30.430> after<00:15:30.610> it's<00:15:30.910> been<00:15:31.060> deployed 00:15:31.380 --> 00:15:31.390 align:start position:0% application after it's been deployed 00:15:31.390 --> 00:15:34.290 align:start position:0% application after it's been deployed you're<00:15:31.960> making<00:15:32.230> a<00:15:32.320> huge<00:15:32.530> mistake<00:15:33.150> we<00:15:34.150> have<00:15:34.270> a 00:15:34.290 --> 00:15:34.300 align:start position:0% you're making a huge mistake we have a 00:15:34.300 --> 00:15:34.530 align:start position:0% you're making a huge mistake we have a little 00:15:34.530 --> 00:15:34.540 align:start position:0% little 00:15:34.540 --> 00:15:36.450 align:start position:0% little Wiki<00:15:34.840> that<00:15:35.080> like<00:15:35.230> talks<00:15:35.590> about<00:15:35.860> some<00:15:36.280> easy 00:15:36.450 --> 00:15:36.460 align:start position:0% Wiki that like talks about some easy 00:15:36.460 --> 00:15:38.160 align:start position:0% Wiki that like talks about some easy things<00:15:36.670> you<00:15:37.000> can<00:15:37.150> do<00:15:37.300> to<00:15:37.480> make<00:15:37.600> it<00:15:37.720> easier<00:15:38.050> to 00:15:38.160 --> 00:15:38.170 align:start position:0% things you can do to make it easier to 00:15:38.170 --> 00:15:40.170 align:start position:0% things you can do to make it easier to communicate<00:15:38.320> with<00:15:38.710> your<00:15:38.830> project<00:15:39.220> I<00:15:39.790> believe 00:15:40.170 --> 00:15:40.180 align:start position:0% communicate with your project I believe 00:15:40.180 --> 00:15:42.000 align:start position:0% communicate with your project I believe it's<00:15:40.480> called<00:15:40.600> blockchain<00:15:41.080> security<00:15:41.500> contacts 00:15:42.000 --> 00:15:42.010 align:start position:0% it's called blockchain security contacts 00:15:42.010 --> 00:15:44.700 align:start position:0% it's called blockchain security contacts so<00:15:42.910> that<00:15:43.060> if<00:15:43.180> any<00:15:43.450> security<00:15:44.050> researcher<00:15:44.470> does 00:15:44.700 --> 00:15:44.710 align:start position:0% so that if any security researcher does 00:15:44.710 --> 00:15:46.470 align:start position:0% so that if any security researcher does find<00:15:45.040> a<00:15:45.130> bug<00:15:45.310> in<00:15:45.460> your<00:15:45.490> code<00:15:45.610> they<00:15:46.330> can 00:15:46.470 --> 00:15:46.480 align:start position:0% find a bug in your code they can 00:15:46.480 --> 00:15:48.480 align:start position:0% find a bug in your code they can actually<00:15:46.630> communicate<00:15:46.960> it<00:15:47.380> to<00:15:47.470> you<00:15:47.590> so<00:15:48.370> don't 00:15:48.480 --> 00:15:48.490 align:start position:0% actually communicate it to you so don't 00:15:48.490 --> 00:15:50.970 align:start position:0% actually communicate it to you so don't neglect<00:15:48.730> that<00:15:49.140> but<00:15:50.140> yes<00:15:50.290> you're<00:15:50.620> completely 00:15:50.970 --> 00:15:50.980 align:start position:0% neglect that but yes you're completely 00:15:50.980 --> 00:15:54.320 align:start position:0% neglect that but yes you're completely correct<00:15:51.900> yeah<00:15:52.900> I<00:15:52.930> just<00:15:53.170> echo<00:15:53.440> what<00:15:53.590> Phil<00:15:53.920> said 00:15:54.320 --> 00:15:54.330 align:start position:0% correct yeah I just echo what Phil said 00:15:54.330 --> 00:15:57.620 align:start position:0% correct yeah I just echo what Phil said I'm<00:15:55.330> all<00:15:55.510> for<00:15:55.690> bug<00:15:55.900> bounties<00:15:56.320> but<00:15:56.800> not 00:15:57.620 --> 00:15:57.630 align:start position:0% I'm all for bug bounties but not 00:15:57.630 --> 00:16:01.860 align:start position:0% I'm all for bug bounties but not exclusive<00:15:58.630> or<00:15:58.720> security<00:15:59.680> work<00:16:00.150> yes<00:16:01.150> Amy<00:16:01.840> I 00:16:01.860 --> 00:16:01.870 align:start position:0% exclusive or security work yes Amy I 00:16:01.870 --> 00:16:02.910 align:start position:0% exclusive or security work yes Amy I don't<00:16:02.110> think<00:16:02.320> it<00:16:02.380> should<00:16:02.470> be<00:16:02.530> the<00:16:02.740> only 00:16:02.910 --> 00:16:02.920 align:start position:0% don't think it should be the only 00:16:02.920 --> 00:16:04.650 align:start position:0% don't think it should be the only security<00:16:03.730> that's<00:16:04.000> done<00:16:04.210> I<00:16:04.240> mean<00:16:04.450> there<00:16:04.630> should 00:16:04.650 --> 00:16:04.660 align:start position:0% security that's done I mean there should 00:16:04.660 --> 00:16:07.920 align:start position:0% security that's done I mean there should be<00:16:04.930> like<00:16:05.050> a<00:16:05.110> process<00:16:05.740> that<00:16:06.600> you<00:16:07.600> know<00:16:07.720> makes 00:16:07.920 --> 00:16:07.930 align:start position:0% be like a process that you know makes 00:16:07.930 --> 00:16:10.650 align:start position:0% be like a process that you know makes your<00:16:08.110> development<00:16:08.610> more<00:16:09.610> more<00:16:09.940> secure<00:16:10.300> like 00:16:10.650 --> 00:16:10.660 align:start position:0% your development more more secure like 00:16:10.660 --> 00:16:12.570 align:start position:0% your development more more secure like there<00:16:10.870> should<00:16:11.080> be<00:16:11.110> someone<00:16:11.470> in-house<00:16:11.800> there 00:16:12.570 --> 00:16:12.580 align:start position:0% there should be someone in-house there 00:16:12.580 --> 00:16:15.390 align:start position:0% there should be someone in-house there should<00:16:12.760> be<00:16:12.880> a<00:16:12.910> formal<00:16:13.360> audit<00:16:13.660> or<00:16:13.840> three<00:16:14.500> and 00:16:15.390 --> 00:16:15.400 align:start position:0% should be a formal audit or three and 00:16:15.400 --> 00:16:16.350 align:start position:0% should be a formal audit or three and then<00:16:15.430> there<00:16:15.610> should<00:16:15.700> probably<00:16:15.730> be<00:16:16.030> a<00:16:16.180> bug 00:16:16.350 --> 00:16:16.360 align:start position:0% then there should probably be a bug 00:16:16.360 --> 00:16:19.200 align:start position:0% then there should probably be a bug bounty<00:16:16.510> like<00:16:17.380> a<00:16:17.620> cross<00:16:17.890> at<00:16:18.070> all<00:16:18.160> I<00:16:18.430> just<00:16:19.030> think 00:16:19.200 --> 00:16:19.210 align:start position:0% bounty like a cross at all I just think 00:16:19.210 --> 00:16:20.520 align:start position:0% bounty like a cross at all I just think we've<00:16:19.330> been<00:16:19.450> sort<00:16:19.720> of<00:16:19.750> like<00:16:19.900> a<00:16:20.110> false 00:16:20.520 --> 00:16:20.530 align:start position:0% we've been sort of like a false 00:16:20.530 --> 00:16:22.530 align:start position:0% we've been sort of like a false equivalency<00:16:20.770> there's<00:16:21.430> like<00:16:21.610> to<00:16:22.030> an<00:16:22.210> audit 00:16:22.530 --> 00:16:22.540 align:start position:0% equivalency there's like to an audit 00:16:22.540 --> 00:16:24.630 align:start position:0% equivalency there's like to an audit don't<00:16:23.320> do<00:16:23.410> a<00:16:23.440> bounty<00:16:23.830> instead<00:16:24.190> of<00:16:24.280> an<00:16:24.340> audit 00:16:24.630 --> 00:16:24.640 align:start position:0% don't do a bounty instead of an audit 00:16:24.640 --> 00:16:27.300 align:start position:0% don't do a bounty instead of an audit and<00:16:24.760> then<00:16:24.910> run<00:16:25.510> a<00:16:25.680> bounty<00:16:26.680> so<00:16:26.890> that<00:16:27.010> somebody 00:16:27.300 --> 00:16:27.310 align:start position:0% and then run a bounty so that somebody 00:16:27.310 --> 00:16:28.890 align:start position:0% and then run a bounty so that somebody has<00:16:27.400> a<00:16:27.430> reason<00:16:27.820> to<00:16:27.850> report<00:16:28.270> it<00:16:28.360> to<00:16:28.480> you<00:16:28.570> there 00:16:28.890 --> 00:16:28.900 align:start position:0% has a reason to report it to you there 00:16:28.900 --> 00:16:32.040 align:start position:0% has a reason to report it to you there there's<00:16:29.320> separate<00:16:29.620> things<00:16:29.890> right<00:16:30.870> all<00:16:31.870> right 00:16:32.040 --> 00:16:32.050 align:start position:0% there's separate things right all right 00:16:32.050 --> 00:16:34.380 align:start position:0% there's separate things right all right next<00:16:32.710> one<00:16:32.860> is<00:16:33.070> what<00:16:33.850> advice<00:16:34.060> would<00:16:34.090> you<00:16:34.270> give 00:16:34.380 --> 00:16:34.390 align:start position:0% next one is what advice would you give 00:16:34.390 --> 00:16:37.050 align:start position:0% next one is what advice would you give someone<00:16:34.840> who's<00:16:34.990> interested<00:16:35.560> in<00:16:36.060> becoming 00:16:37.050 --> 00:16:37.060 align:start position:0% someone who's interested in becoming 00:16:37.060 --> 00:16:39.150 align:start position:0% someone who's interested in becoming more<00:16:37.420> involved<00:16:37.930> in<00:16:38.110> smart<00:16:38.380> contract<00:16:38.740> security 00:16:39.150 --> 00:16:39.160 align:start position:0% more involved in smart contract security 00:16:39.160 --> 00:16:43.500 align:start position:0% more involved in smart contract security wherever<00:16:39.820> they<00:16:39.940> start<00:16:40.260> so<00:16:41.260> my<00:16:42.240> answer<00:16:43.240> to<00:16:43.270> that 00:16:43.500 --> 00:16:43.510 align:start position:0% wherever they start so my answer to that 00:16:43.510 --> 00:16:46.230 align:start position:0% wherever they start so my answer to that would<00:16:43.780> be<00:16:44.460> because<00:16:45.460> that's<00:16:45.670> the<00:16:45.790> way<00:16:45.880> I<00:16:45.910> came 00:16:46.230 --> 00:16:46.240 align:start position:0% would be because that's the way I came 00:16:46.240 --> 00:16:48.690 align:start position:0% would be because that's the way I came into<00:16:46.390> smart<00:16:47.050> contract<00:16:47.410> security<00:16:47.770> to<00:16:48.400> learn 00:16:48.690 --> 00:16:48.700 align:start position:0% into smart contract security to learn 00:16:48.700 --> 00:16:52.220 align:start position:0% into smart contract security to learn the<00:16:49.320> intricate<00:16:50.320> details<00:16:50.800> and<00:16:51.010> integrate<00:16:51.430> the 00:16:52.220 --> 00:16:52.230 align:start position:0% the intricate details and integrate the 00:16:52.230 --> 00:16:56.340 align:start position:0% the intricate details and integrate the mechanics<00:16:53.230> of<00:16:53.380> the<00:16:53.620> EVM<00:16:54.130> and<00:16:55.230> execution<00:16:56.230> of 00:16:56.340 --> 00:16:56.350 align:start position:0% mechanics of the EVM and execution of 00:16:56.350 --> 00:17:00.510 align:start position:0% mechanics of the EVM and execution of transaction<00:16:57.570> from<00:16:58.570> the<00:16:58.690> bottom<00:16:58.960> up<00:16:59.520> that 00:17:00.510 --> 00:17:00.520 align:start position:0% transaction from the bottom up that 00:17:00.520 --> 00:17:04.950 align:start position:0% transaction from the bottom up that would<00:17:00.670> be<00:17:00.700> my<00:17:00.910> first<00:17:01.600> advice<00:17:01.930> kind<00:17:02.260> of<00:17:03.960> yeah 00:17:04.950 --> 00:17:04.960 align:start position:0% would be my first advice kind of yeah 00:17:04.960 --> 00:17:06.420 align:start position:0% would be my first advice kind of yeah that's<00:17:05.200> definitely<00:17:05.350> great<00:17:05.740> advice<00:17:05.980> I<00:17:06.250> would 00:17:06.420 --> 00:17:06.430 align:start position:0% that's definitely great advice I would 00:17:06.430 --> 00:17:08.850 align:start position:0% that's definitely great advice I would also<00:17:06.580> say<00:17:06.940> look<00:17:07.330> at<00:17:07.540> past<00:17:07.810> security<00:17:08.260> failures 00:17:08.850 --> 00:17:08.860 align:start position:0% also say look at past security failures 00:17:08.860 --> 00:17:10.560 align:start position:0% also say look at past security failures and<00:17:09.160> replicate<00:17:09.640> them<00:17:09.790> yourselves<00:17:10.360> so<00:17:10.510> you 00:17:10.560 --> 00:17:10.570 align:start position:0% and replicate them yourselves so you 00:17:10.570 --> 00:17:12.030 align:start position:0% and replicate them yourselves so you should<00:17:10.840> be<00:17:10.960> able<00:17:11.080> to<00:17:11.230> pull<00:17:11.500> off<00:17:11.650> something 00:17:12.030 --> 00:17:12.040 align:start position:0% should be able to pull off something 00:17:12.040 --> 00:17:14.370 align:start position:0% should be able to pull off something like<00:17:12.220> the<00:17:12.520> DAO<00:17:12.700> hack<00:17:13.000> you<00:17:13.930> should<00:17:14.080> be<00:17:14.200> able<00:17:14.260> to 00:17:14.370 --> 00:17:14.380 align:start position:0% like the DAO hack you should be able to 00:17:14.380 --> 00:17:16.110 align:start position:0% like the DAO hack you should be able to understand<00:17:14.890> how<00:17:15.100> to<00:17:15.130> exploit<00:17:15.580> various 00:17:16.110 --> 00:17:16.120 align:start position:0% understand how to exploit various 00:17:16.120 --> 00:17:17.970 align:start position:0% understand how to exploit various peoples<00:17:16.450> coding<00:17:16.810> error<00:17:16.990> and<00:17:17.200> you<00:17:17.290> should<00:17:17.470> try 00:17:17.970 --> 00:17:17.980 align:start position:0% peoples coding error and you should try 00:17:17.980 --> 00:17:20.070 align:start position:0% peoples coding error and you should try it<00:17:18.040> by<00:17:18.280> example<00:17:18.790> and<00:17:19.480> then<00:17:19.630> once<00:17:19.780> you're<00:17:19.930> sort 00:17:20.070 --> 00:17:20.080 align:start position:0% it by example and then once you're sort 00:17:20.080 --> 00:17:21.000 align:start position:0% it by example and then once you're sort of<00:17:20.140> done<00:17:20.320> doing<00:17:20.470> that<00:17:20.590> and<00:17:20.830> you<00:17:20.890> feel 00:17:21.000 --> 00:17:21.010 align:start position:0% of done doing that and you feel 00:17:21.010 --> 00:17:21.840 align:start position:0% of done doing that and you feel comfortable<00:17:21.250> that<00:17:21.580> you're<00:17:21.700> at<00:17:21.760> the 00:17:21.840 --> 00:17:21.850 align:start position:0% comfortable that you're at the 00:17:21.850 --> 00:17:23.280 align:start position:0% comfortable that you're at the state-of-the-art<00:17:22.030> maybe<00:17:22.540> try<00:17:22.810> finding 00:17:23.280 --> 00:17:23.290 align:start position:0% state-of-the-art maybe try finding 00:17:23.290 --> 00:17:25.260 align:start position:0% state-of-the-art maybe try finding something<00:17:23.500> new<00:17:23.650> even<00:17:24.340> if<00:17:24.550> it's<00:17:24.730> not<00:17:24.880> a<00:17:24.910> very 00:17:25.260 --> 00:17:25.270 align:start position:0% something new even if it's not a very 00:17:25.270 --> 00:17:27.120 align:start position:0% something new even if it's not a very high<00:17:25.450> severity<00:17:25.750> thing<00:17:26.140> find<00:17:26.710> something<00:17:27.010> that 00:17:27.120 --> 00:17:27.130 align:start position:0% high severity thing find something that 00:17:27.130 --> 00:17:28.470 align:start position:0% high severity thing find something that people<00:17:27.280> haven't<00:17:27.670> thought<00:17:27.700> of<00:17:27.820> yet<00:17:28.090> in<00:17:28.270> some 00:17:28.470 --> 00:17:28.480 align:start position:0% people haven't thought of yet in some 00:17:28.480 --> 00:17:30.390 align:start position:0% people haven't thought of yet in some edge<00:17:28.660> case<00:17:28.930> and<00:17:29.770> whether<00:17:29.920> that<00:17:30.130> takes<00:17:30.310> you 00:17:30.390 --> 00:17:30.400 align:start position:0% edge case and whether that takes you 00:17:30.400 --> 00:17:31.740 align:start position:0% edge case and whether that takes you three<00:17:30.610> months<00:17:30.880> or<00:17:31.000> six<00:17:31.180> months<00:17:31.240> sort<00:17:31.540> of<00:17:31.630> at 00:17:31.740 --> 00:17:31.750 align:start position:0% three months or six months sort of at 00:17:31.750 --> 00:17:32.880 align:start position:0% three months or six months sort of at the<00:17:31.840> end<00:17:31.930> of<00:17:32.050> that<00:17:32.140> process<00:17:32.350> you'll<00:17:32.680> probably 00:17:32.880 --> 00:17:32.890 align:start position:0% the end of that process you'll probably 00:17:32.890 --> 00:17:34.890 align:start position:0% the end of that process you'll probably know<00:17:33.310> a<00:17:33.340> lot<00:17:33.550> more<00:17:33.730> about<00:17:33.790> the<00:17:34.090> EVM<00:17:34.390> and<00:17:34.630> smart 00:17:34.890 --> 00:17:34.900 align:start position:0% know a lot more about the EVM and smart 00:17:34.900 --> 00:17:38.790 align:start position:0% know a lot more about the EVM and smart contracts<00:17:36.240> yeah<00:17:37.240> I<00:17:37.270> know<00:17:37.510> I<00:17:37.540> agree<00:17:38.260> with<00:17:38.380> both 00:17:38.790 --> 00:17:38.800 align:start position:0% contracts yeah I know I agree with both 00:17:38.800 --> 00:17:40.260 align:start position:0% contracts yeah I know I agree with both of<00:17:38.950> those<00:17:39.040> statements<00:17:39.520> especially<00:17:39.970> the 00:17:40.260 --> 00:17:40.270 align:start position:0% of those statements especially the 00:17:40.270 --> 00:17:42.000 align:start position:0% of those statements especially the intricate<00:17:40.600> details<00:17:40.870> part<00:17:41.140> like<00:17:41.440> most 00:17:42.000 --> 00:17:42.010 align:start position:0% intricate details part like most 00:17:42.010 --> 00:17:44.250 align:start position:0% intricate details part like most security<00:17:42.400> issues<00:17:42.790> come<00:17:43.360> from<00:17:43.630> misplaced 00:17:44.250 --> 00:17:44.260 align:start position:0% security issues come from misplaced 00:17:44.260 --> 00:17:45.780 align:start position:0% security issues come from misplaced assumptions<00:17:44.800> right<00:17:44.980> so<00:17:45.130> you<00:17:45.220> have<00:17:45.340> this<00:17:45.520> black 00:17:45.780 --> 00:17:45.790 align:start position:0% assumptions right so you have this black 00:17:45.790 --> 00:17:47.580 align:start position:0% assumptions right so you have this black box<00:17:46.060> and<00:17:46.360> has<00:17:46.750> a<00:17:46.780> set<00:17:47.050> of<00:17:47.080> properties<00:17:47.440> that 00:17:47.580 --> 00:17:47.590 align:start position:0% box and has a set of properties that 00:17:47.590 --> 00:17:48.450 align:start position:0% box and has a set of properties that youth 00:17:48.450 --> 00:17:48.460 align:start position:0% youth 00:17:48.460 --> 00:17:51.990 align:start position:0% youth you<00:17:48.610> feel<00:17:49.570> comfortable<00:17:49.780> with<00:17:50.730> award<00:17:51.730> that<00:17:51.880> or 00:17:51.990 --> 00:17:52.000 align:start position:0% you feel comfortable with award that or 00:17:52.000 --> 00:17:53.670 align:start position:0% you feel comfortable with award that or someone<00:17:52.270> else<00:17:52.450> has<00:17:52.570> told<00:17:52.750> you<00:17:52.990> those<00:17:53.470> are<00:17:53.620> the 00:17:53.670 --> 00:17:53.680 align:start position:0% someone else has told you those are the 00:17:53.680 --> 00:17:56.160 align:start position:0% someone else has told you those are the properties<00:17:54.160> and<00:17:55.030> like<00:17:55.240> it's<00:17:55.390> that<00:17:55.540> telephone 00:17:56.160 --> 00:17:56.170 align:start position:0% properties and like it's that telephone 00:17:56.170 --> 00:17:58.380 align:start position:0% properties and like it's that telephone game<00:17:56.500> right<00:17:56.800> like<00:17:57.100> depending<00:17:57.850> on<00:17:57.940> how<00:17:58.120> far 00:17:58.380 --> 00:17:58.390 align:start position:0% game right like depending on how far 00:17:58.390 --> 00:17:59.790 align:start position:0% game right like depending on how far away<00:17:58.570> the<00:17:58.870> person<00:17:59.140> that<00:17:59.260> originally<00:17:59.440> actually 00:17:59.790 --> 00:17:59.800 align:start position:0% away the person that originally actually 00:17:59.800 --> 00:18:02.370 align:start position:0% away the person that originally actually you<00:18:00.460> know<00:18:00.580> made<00:18:00.760> the<00:18:00.880> thing<00:18:01.090> how<00:18:02.050> many<00:18:02.200> levels 00:18:02.370 --> 00:18:02.380 align:start position:0% you know made the thing how many levels 00:18:02.380 --> 00:18:04.350 align:start position:0% you know made the thing how many levels around<00:18:02.620> between<00:18:03.040> you<00:18:03.160> and<00:18:03.340> that<00:18:03.430> person<00:18:03.460> like 00:18:04.350 --> 00:18:04.360 align:start position:0% around between you and that person like 00:18:04.360 --> 00:18:06.210 align:start position:0% around between you and that person like it's<00:18:04.840> likely<00:18:05.260> that<00:18:05.410> the<00:18:05.530> your<00:18:05.830> understanding 00:18:06.210 --> 00:18:06.220 align:start position:0% it's likely that the your understanding 00:18:06.220 --> 00:18:08.370 align:start position:0% it's likely that the your understanding of<00:18:06.310> that<00:18:06.400> black<00:18:06.610> box<00:18:06.820> is<00:18:07.030> twisted<00:18:07.540> and<00:18:07.930> then 00:18:08.370 --> 00:18:08.380 align:start position:0% of that black box is twisted and then 00:18:08.380 --> 00:18:10.170 align:start position:0% of that black box is twisted and then you<00:18:08.440> write<00:18:08.650> code<00:18:08.860> that<00:18:09.370> has<00:18:09.550> a<00:18:09.850> better 00:18:10.170 --> 00:18:10.180 align:start position:0% you write code that has a better 00:18:10.180 --> 00:18:11.460 align:start position:0% you write code that has a better understanding<00:18:10.570> and<00:18:10.690> misleads<00:18:11.050> the<00:18:11.230> next 00:18:11.460 --> 00:18:11.470 align:start position:0% understanding and misleads the next 00:18:11.470 --> 00:18:14.040 align:start position:0% understanding and misleads the next person<00:18:11.920> and<00:18:12.370> then<00:18:12.760> it<00:18:13.000> just<00:18:13.180> you<00:18:13.420> know<00:18:13.720> builds 00:18:14.040 --> 00:18:14.050 align:start position:0% person and then it just you know builds 00:18:14.050 --> 00:18:16.110 align:start position:0% person and then it just you know builds up<00:18:14.170> over<00:18:14.410> and<00:18:14.530> over<00:18:14.680> right<00:18:14.710> so<00:18:14.830> the<00:18:15.400> more<00:18:15.610> you 00:18:16.110 --> 00:18:16.120 align:start position:0% up over and over right so the more you 00:18:16.120 --> 00:18:18.180 align:start position:0% up over and over right so the more you can<00:18:16.300> open<00:18:16.600> black<00:18:16.810> boxes<00:18:17.320> and<00:18:17.470> say<00:18:17.590> this<00:18:17.920> is<00:18:18.100> how 00:18:18.180 --> 00:18:18.190 align:start position:0% can open black boxes and say this is how 00:18:18.190 --> 00:18:19.710 align:start position:0% can open black boxes and say this is how that<00:18:18.250> really<00:18:18.610> works<00:18:18.790> this<00:18:19.000> is<00:18:19.180> where<00:18:19.510> that 00:18:19.710 --> 00:18:19.720 align:start position:0% that really works this is where that 00:18:19.720 --> 00:18:21.480 align:start position:0% that really works this is where that interacts<00:18:20.110> the<00:18:20.380> less<00:18:20.860> prone<00:18:21.100> you<00:18:21.250> are<00:18:21.370> the 00:18:21.480 --> 00:18:21.490 align:start position:0% interacts the less prone you are the 00:18:21.490 --> 00:18:24.900 align:start position:0% interacts the less prone you are the security<00:18:21.790> mistakes<00:18:22.120> and<00:18:22.360> also<00:18:23.320> just<00:18:24.310> try<00:18:24.610> just 00:18:24.900 --> 00:18:24.910 align:start position:0% security mistakes and also just try just 00:18:24.910 --> 00:18:26.580 align:start position:0% security mistakes and also just try just write<00:18:25.360> a<00:18:25.390> big<00:18:25.540> a<00:18:25.570> developer<00:18:25.960> and<00:18:26.080> write<00:18:26.260> anti 00:18:26.580 --> 00:18:26.590 align:start position:0% write a big a developer and write anti 00:18:26.590 --> 00:18:29.190 align:start position:0% write a big a developer and write anti fragile<00:18:26.770> code<00:18:27.160> you<00:18:27.340> know<00:18:27.460> if<00:18:27.670> the<00:18:28.150> the<00:18:28.870> big<00:18:29.020> one 00:18:29.190 --> 00:18:29.200 align:start position:0% fragile code you know if the the big one 00:18:29.200 --> 00:18:31.170 align:start position:0% fragile code you know if the the big one of<00:18:29.260> the<00:18:29.350> one<00:18:29.530> of<00:18:29.620> the<00:18:29.680> recent<00:18:29.980> bingo<00:18:30.370> bugs<00:18:30.670> is<00:18:30.880> a 00:18:31.170 --> 00:18:31.180 align:start position:0% of the one of the recent bingo bugs is a 00:18:31.180 --> 00:18:32.910 align:start position:0% of the one of the recent bingo bugs is a perfect<00:18:31.540> example<00:18:31.690> of<00:18:32.020> that<00:18:32.080> is<00:18:32.230> when<00:18:32.830> you 00:18:32.910 --> 00:18:32.920 align:start position:0% perfect example of that is when you 00:18:32.920 --> 00:18:34.890 align:start position:0% perfect example of that is when you write<00:18:33.610> a<00:18:33.670> function<00:18:33.880> that<00:18:34.060> seems<00:18:34.510> like<00:18:34.750> it 00:18:34.890 --> 00:18:34.900 align:start position:0% write a function that seems like it 00:18:34.900 --> 00:18:37.730 align:start position:0% write a function that seems like it makes<00:18:35.290> a<00:18:35.410> check<00:18:35.620> you<00:18:36.550> know<00:18:36.640> like<00:18:36.820> the<00:18:37.300> the<00:18:37.330> name 00:18:37.730 --> 00:18:37.740 align:start position:0% makes a check you know like the the name 00:18:37.740 --> 00:18:40.140 align:start position:0% makes a check you know like the the name misleads<00:18:38.740> it<00:18:38.890> into<00:18:39.190> the<00:18:39.250> into<00:18:39.790> the<00:18:39.850> making<00:18:40.000> you 00:18:40.140 --> 00:18:40.150 align:start position:0% misleads it into the into the making you 00:18:40.150 --> 00:18:42.210 align:start position:0% misleads it into the into the making you think<00:18:40.300> that<00:18:40.390> it<00:18:40.540> makes<00:18:40.660> the<00:18:40.780> check<00:18:41.020> like<00:18:41.920> the 00:18:42.210 --> 00:18:42.220 align:start position:0% think that it makes the check like the 00:18:42.220 --> 00:18:43.770 align:start position:0% think that it makes the check like the the<00:18:42.430> file<00:18:42.610> it's<00:18:42.850> in<00:18:42.970> whatever<00:18:43.180> and<00:18:43.540> so 00:18:43.770 --> 00:18:43.780 align:start position:0% the file it's in whatever and so 00:18:43.780 --> 00:18:45.180 align:start position:0% the file it's in whatever and so somebody<00:18:44.020> will<00:18:44.260> see<00:18:44.380> like<00:18:44.500> Oh<00:18:44.650> fine<00:18:44.980> that 00:18:45.180 --> 00:18:45.190 align:start position:0% somebody will see like Oh fine that 00:18:45.190 --> 00:18:46.290 align:start position:0% somebody will see like Oh fine that makes<00:18:45.400> that<00:18:45.580> check<00:18:45.790> and<00:18:45.820> I<00:18:45.970> don't<00:18:46.120> have<00:18:46.210> to 00:18:46.290 --> 00:18:46.300 align:start position:0% makes that check and I don't have to 00:18:46.300 --> 00:18:47.790 align:start position:0% makes that check and I don't have to check<00:18:46.510> it<00:18:46.690> in<00:18:46.840> the<00:18:46.990> container<00:18:47.200> function<00:18:47.650> and 00:18:47.790 --> 00:18:47.800 align:start position:0% check it in the container function and 00:18:47.800 --> 00:18:49.160 align:start position:0% check it in the container function and then<00:18:47.920> you<00:18:48.010> get<00:18:48.160> you<00:18:48.430> know<00:18:48.550> infinite<00:18:49.000> money 00:18:49.160 --> 00:18:49.170 align:start position:0% then you get you know infinite money 00:18:49.170 --> 00:18:52.530 align:start position:0% then you get you know infinite money being<00:18:50.170> printed<00:18:50.320> so<00:18:50.830> we'd<00:18:51.550> be<00:18:51.700> really<00:18:52.210> careful 00:18:52.530 --> 00:18:52.540 align:start position:0% being printed so we'd be really careful 00:18:52.540 --> 00:18:54.720 align:start position:0% being printed so we'd be really careful about<00:18:52.690> your<00:18:52.780> assumptions<00:18:53.290> just<00:18:53.730> cultivate 00:18:54.720 --> 00:18:54.730 align:start position:0% about your assumptions just cultivate 00:18:54.730 --> 00:18:56.790 align:start position:0% about your assumptions just cultivate that<00:18:54.850> -<00:18:55.330> mindset<00:18:55.840> of<00:18:55.930> awareness<00:18:56.170> that's<00:18:56.680> how 00:18:56.790 --> 00:18:56.800 align:start position:0% that - mindset of awareness that's how 00:18:56.800 --> 00:19:02.670 align:start position:0% that - mindset of awareness that's how you<00:18:56.860> become<00:18:57.040> good<00:18:57.160> at<00:18:57.280> security<00:19:01.080> it<00:19:02.080> takes<00:19:02.380> I 00:19:02.670 --> 00:19:02.680 align:start position:0% you become good at security it takes I 00:19:02.680 --> 00:19:05.400 align:start position:0% you become good at security it takes I guess<00:19:02.770> taking<00:19:03.640> a<00:19:03.670> bit<00:19:04.000> different<00:19:04.360> direction 00:19:05.400 --> 00:19:05.410 align:start position:0% guess taking a bit different direction 00:19:05.410 --> 00:19:08.010 align:start position:0% guess taking a bit different direction I'd<00:19:05.980> say<00:19:06.190> contribute<00:19:06.700> like<00:19:07.180> learn<00:19:07.360> by<00:19:07.570> doing 00:19:08.010 --> 00:19:08.020 align:start position:0% I'd say contribute like learn by doing 00:19:08.020 --> 00:19:10.860 align:start position:0% I'd say contribute like learn by doing so<00:19:08.430> like<00:19:09.430> participate<00:19:09.970> in<00:19:10.150> bounties<00:19:10.510> which 00:19:10.860 --> 00:19:10.870 align:start position:0% so like participate in bounties which 00:19:10.870 --> 00:19:13.980 align:start position:0% so like participate in bounties which are<00:19:11.020> like<00:19:11.290> not<00:19:11.470> that<00:19:11.680> bad<00:19:11.890> we<00:19:12.040> agreed<00:19:12.370> and<00:19:12.990> like 00:19:13.980 --> 00:19:13.990 align:start position:0% are like not that bad we agreed and like 00:19:13.990 --> 00:19:16.290 align:start position:0% are like not that bad we agreed and like run<00:19:14.230> the<00:19:14.380> tools<00:19:14.590> on<00:19:14.800> the<00:19:14.830> contracts<00:19:15.310> before<00:19:15.730> we 00:19:16.290 --> 00:19:16.300 align:start position:0% run the tools on the contracts before we 00:19:16.300 --> 00:19:18.300 align:start position:0% run the tools on the contracts before we do<00:19:16.480> so<00:19:16.810> that<00:19:16.840> maybe<00:19:17.200> you'll<00:19:17.440> like<00:19:17.830> get<00:19:18.010> a<00:19:18.040> list 00:19:18.300 --> 00:19:18.310 align:start position:0% do so that maybe you'll like get a list 00:19:18.310 --> 00:19:19.770 align:start position:0% do so that maybe you'll like get a list of<00:19:18.430> things<00:19:18.880> and<00:19:19.090> make<00:19:19.210> some<00:19:19.360> money<00:19:19.540> and<00:19:19.690> then 00:19:19.770 --> 00:19:19.780 align:start position:0% of things and make some money and then 00:19:19.780 --> 00:19:21.120 align:start position:0% of things and make some money and then you'll<00:19:19.870> feel<00:19:20.020> great<00:19:20.260> and<00:19:20.650> then<00:19:20.770> you'll<00:19:20.980> do 00:19:21.120 --> 00:19:21.130 align:start position:0% you'll feel great and then you'll do 00:19:21.130 --> 00:19:23.310 align:start position:0% you'll feel great and then you'll do more<00:19:21.340> and<00:19:21.640> then<00:19:22.420> you<00:19:22.600> can<00:19:22.750> start<00:19:22.990> contributing 00:19:23.310 --> 00:19:23.320 align:start position:0% more and then you can start contributing 00:19:23.320 --> 00:19:27.570 align:start position:0% more and then you can start contributing to<00:19:23.730> you<00:19:24.730> know<00:19:24.850> very<00:19:25.120> like<00:19:25.300> documentation<00:19:26.580> our 00:19:27.570 --> 00:19:27.580 align:start position:0% to you know very like documentation our 00:19:27.580 --> 00:19:29.520 align:start position:0% to you know very like documentation our best<00:19:27.940> practices<00:19:28.600> would<00:19:28.750> be<00:19:28.870> great<00:19:29.110> or<00:19:29.380> like 00:19:29.520 --> 00:19:29.530 align:start position:0% best practices would be great or like 00:19:29.530 --> 00:19:33.930 align:start position:0% best practices would be great or like Dan's<00:19:29.800> not<00:19:29.980> so<00:19:30.130> smart<00:19:30.370> contracts<00:19:31.680> and<00:19:32.680> as<00:19:33.520> well 00:19:33.930 --> 00:19:33.940 align:start position:0% Dan's not so smart contracts and as well 00:19:33.940 --> 00:19:36.210 align:start position:0% Dan's not so smart contracts and as well as<00:19:34.150> our<00:19:34.360> smart<00:19:35.350> contract<00:19:35.770> weakness 00:19:36.210 --> 00:19:36.220 align:start position:0% as our smart contract weakness 00:19:36.220 --> 00:19:39.480 align:start position:0% as our smart contract weakness classification<00:19:37.060> registry<00:19:38.130> like<00:19:39.130> you<00:19:39.250> you 00:19:39.480 --> 00:19:39.490 align:start position:0% classification registry like you you 00:19:39.490 --> 00:19:41.130 align:start position:0% classification registry like you you know<00:19:39.610> and<00:19:39.760> then<00:19:40.030> teach<00:19:40.240> other<00:19:40.480> people<00:19:40.870> like 00:19:41.130 --> 00:19:41.140 align:start position:0% know and then teach other people like 00:19:41.140 --> 00:19:42.720 align:start position:0% know and then teach other people like that's<00:19:41.350> that's<00:19:41.650> how<00:19:41.920> I<00:19:41.950> would<00:19:42.310> go<00:19:42.460> about<00:19:42.670> doing 00:19:42.720 --> 00:19:42.730 align:start position:0% that's that's how I would go about doing 00:19:42.730 --> 00:19:45.420 align:start position:0% that's that's how I would go about doing it<00:19:43.150> and<00:19:43.210> then<00:19:43.390> show<00:19:43.660> up<00:19:43.870> at<00:19:44.740> these<00:19:44.920> things<00:19:45.160> and 00:19:45.420 --> 00:19:45.430 align:start position:0% it and then show up at these things and 00:19:45.430 --> 00:19:49.170 align:start position:0% it and then show up at these things and ask<00:19:45.580> good<00:19:45.790> questions<00:19:47.430> so<00:19:48.430> I<00:19:48.700> think<00:19:48.820> it<00:19:49.000> kind<00:19:49.150> of 00:19:49.170 --> 00:19:49.180 align:start position:0% ask good questions so I think it kind of 00:19:49.180 --> 00:19:50.340 align:start position:0% ask good questions so I think it kind of depends<00:19:49.480> on<00:19:49.600> what<00:19:49.750> you<00:19:49.840> want<00:19:49.990> to<00:19:50.050> get<00:19:50.200> out<00:19:50.320> of 00:19:50.340 --> 00:19:50.350 align:start position:0% depends on what you want to get out of 00:19:50.350 --> 00:19:52.050 align:start position:0% depends on what you want to get out of working<00:19:50.770> with<00:19:50.890> the<00:19:50.980> community<00:19:51.340> like<00:19:51.730> are<00:19:51.940> you 00:19:52.050 --> 00:19:52.060 align:start position:0% working with the community like are you 00:19:52.060 --> 00:19:54.480 align:start position:0% working with the community like are you someone<00:19:52.480> that<00:19:52.510> wants<00:19:52.930> to<00:19:53.020> go<00:19:53.170> like<00:19:54.040> stun<00:19:54.280> hack 00:19:54.480 --> 00:19:54.490 align:start position:0% someone that wants to go like stun hack 00:19:54.490 --> 00:19:55.770 align:start position:0% someone that wants to go like stun hack and<00:19:54.670> flex<00:19:54.880> on<00:19:55.030> Twitter<00:19:55.270> about<00:19:55.510> it 00:19:55.770 --> 00:19:55.780 align:start position:0% and flex on Twitter about it 00:19:55.780 --> 00:19:58.290 align:start position:0% and flex on Twitter about it are<00:19:56.290> you<00:19:56.530> a<00:19:56.920> researcher<00:19:57.760> that<00:19:57.910> wants<00:19:58.090> to<00:19:58.120> build 00:19:58.290 --> 00:19:58.300 align:start position:0% are you a researcher that wants to build 00:19:58.300 --> 00:20:00.690 align:start position:0% are you a researcher that wants to build tools<00:19:58.570> or<00:19:58.930> are<00:19:59.650> you<00:19:59.800> a<00:19:59.830> developer<00:20:00.370> that<00:20:00.400> needs 00:20:00.690 --> 00:20:00.700 align:start position:0% tools or are you a developer that needs 00:20:00.700 --> 00:20:01.800 align:start position:0% tools or are you a developer that needs to<00:20:00.790> secure<00:20:01.090> your<00:20:01.270> code 00:20:01.800 --> 00:20:01.810 align:start position:0% to secure your code 00:20:01.810 --> 00:20:03.240 align:start position:0% to secure your code and<00:20:01.900> with<00:20:02.560> each<00:20:02.590> of<00:20:02.800> those<00:20:02.860> different 00:20:03.240 --> 00:20:03.250 align:start position:0% and with each of those different 00:20:03.250 --> 00:20:04.590 align:start position:0% and with each of those different constraints<00:20:03.640> there's<00:20:03.940> probably<00:20:04.240> a<00:20:04.330> different 00:20:04.590 --> 00:20:04.600 align:start position:0% constraints there's probably a different 00:20:04.600 --> 00:20:06.780 align:start position:0% constraints there's probably a different pathway<00:20:05.020> to<00:20:05.080> learn<00:20:05.290> what<00:20:05.470> you<00:20:05.560> need<00:20:05.740> I<00:20:05.980> think 00:20:06.780 --> 00:20:06.790 align:start position:0% pathway to learn what you need I think 00:20:06.790 --> 00:20:08.760 align:start position:0% pathway to learn what you need I think that<00:20:06.910> each<00:20:07.150> of<00:20:07.210> those<00:20:07.600> starts<00:20:08.530> with<00:20:08.650> two 00:20:08.760 --> 00:20:08.770 align:start position:0% that each of those starts with two 00:20:08.770 --> 00:20:11.970 align:start position:0% that each of those starts with two things<00:20:09.010> and<00:20:09.280> first<00:20:10.240> to<00:20:10.720> Martin's<00:20:11.260> point<00:20:11.560> you 00:20:11.970 --> 00:20:11.980 align:start position:0% things and first to Martin's point you 00:20:11.980 --> 00:20:13.590 align:start position:0% things and first to Martin's point you have<00:20:12.190> to<00:20:12.340> learn<00:20:12.460> the<00:20:12.610> lower<00:20:12.790> level<00:20:13.090> details<00:20:13.420> of 00:20:13.590 --> 00:20:13.600 align:start position:0% have to learn the lower level details of 00:20:13.600 --> 00:20:14.760 align:start position:0% have to learn the lower level details of all<00:20:13.720> the<00:20:13.810> languages<00:20:14.230> and<00:20:14.260> tools<00:20:14.500> that<00:20:14.650> you're 00:20:14.760 --> 00:20:14.770 align:start position:0% all the languages and tools that you're 00:20:14.770 --> 00:20:18.750 align:start position:0% all the languages and tools that you're working<00:20:14.890> with<00:20:15.150> and<00:20:16.800> the<00:20:17.800> second<00:20:18.190> is<00:20:18.310> that<00:20:18.370> you 00:20:18.750 --> 00:20:18.760 align:start position:0% working with and the second is that you 00:20:18.760 --> 00:20:20.040 align:start position:0% working with and the second is that you should<00:20:19.120> review<00:20:19.450> what's<00:20:19.630> already<00:20:19.780> been<00:20:19.990> done 00:20:20.040 --> 00:20:20.050 align:start position:0% should review what's already been done 00:20:20.050 --> 00:20:22.380 align:start position:0% should review what's already been done we<00:20:21.010> tried<00:20:21.220> to<00:20:21.310> do<00:20:21.430> our<00:20:21.460> best<00:20:21.760> to<00:20:22.180> make<00:20:22.330> a 00:20:22.380 --> 00:20:22.390 align:start position:0% we tried to do our best to make a 00:20:22.390 --> 00:20:24.300 align:start position:0% we tried to do our best to make a compendium<00:20:22.840> of<00:20:23.110> that<00:20:23.290> with<00:20:23.830> the<00:20:23.950> awesome 00:20:24.300 --> 00:20:24.310 align:start position:0% compendium of that with the awesome 00:20:24.310 --> 00:20:26.880 align:start position:0% compendium of that with the awesome aetherium<00:20:24.730> security<00:20:25.150> list<00:20:25.330> just<00:20:25.990> a<00:20:26.200> few<00:20:26.560> links 00:20:26.880 --> 00:20:26.890 align:start position:0% aetherium security list just a few links 00:20:26.890 --> 00:20:28.230 align:start position:0% aetherium security list just a few links and<00:20:27.070> places<00:20:27.430> where<00:20:27.580> we<00:20:27.670> think<00:20:27.820> people<00:20:28.120> can 00:20:28.230 --> 00:20:28.240 align:start position:0% and places where we think people can 00:20:28.240 --> 00:20:30.300 align:start position:0% and places where we think people can start<00:20:28.450> off<00:20:28.600> to<00:20:28.780> learn<00:20:29.010> but<00:20:30.010> it's<00:20:30.160> really 00:20:30.300 --> 00:20:30.310 align:start position:0% start off to learn but it's really 00:20:30.310 --> 00:20:31.710 align:start position:0% start off to learn but it's really important<00:20:30.700> to<00:20:30.790> keep<00:20:30.880> in<00:20:31.030> mind<00:20:31.060> what<00:20:31.540> your 00:20:31.710 --> 00:20:31.720 align:start position:0% important to keep in mind what your 00:20:31.720 --> 00:20:35.450 align:start position:0% important to keep in mind what your goals<00:20:32.080> are<00:20:32.850> because<00:20:33.850> you<00:20:34.720> know<00:20:34.840> you<00:20:34.900> want<00:20:35.080> to 00:20:35.450 --> 00:20:35.460 align:start position:0% goals are because you know you want to 00:20:35.460 --> 00:20:37.470 align:start position:0% goals are because you know you want to spend<00:20:36.460> the<00:20:36.520> least<00:20:36.670> time<00:20:36.940> to<00:20:37.120> get<00:20:37.240> the<00:20:37.330> most 00:20:37.470 --> 00:20:37.480 align:start position:0% spend the least time to get the most 00:20:37.480 --> 00:20:41.550 align:start position:0% spend the least time to get the most effort<00:20:39.180> cool<00:20:40.180> so<00:20:41.050> I<00:20:41.080> think<00:20:41.170> we<00:20:41.380> might<00:20:41.530> actually 00:20:41.550 --> 00:20:41.560 align:start position:0% effort cool so I think we might actually 00:20:41.560 --> 00:20:43.830 align:start position:0% effort cool so I think we might actually go<00:20:41.920> to<00:20:42.010> the<00:20:42.100> crowd<00:20:42.310> now<00:20:42.490> if<00:20:43.300> anybody<00:20:43.570> has<00:20:43.690> any 00:20:43.830 --> 00:20:43.840 align:start position:0% go to the crowd now if anybody has any 00:20:43.840 --> 00:20:45.510 align:start position:0% go to the crowd now if anybody has any questions<00:20:43.870> we<00:20:44.320> have<00:20:44.350> mics<00:20:44.680> down<00:20:44.920> here<00:20:45.340> on 00:20:45.510 --> 00:20:45.520 align:start position:0% questions we have mics down here on 00:20:45.520 --> 00:20:47.160 align:start position:0% questions we have mics down here on either<00:20:45.700> side<00:20:45.880> of<00:20:45.910> the<00:20:46.060> stage<00:20:46.300> and<00:20:46.750> if<00:20:46.930> you<00:20:47.020> want 00:20:47.160 --> 00:20:47.170 align:start position:0% either side of the stage and if you want 00:20:47.170 --> 00:20:49.230 align:start position:0% either side of the stage and if you want to<00:20:47.230> come<00:20:47.350> down<00:20:47.530> I've<00:20:48.220> got<00:20:48.250> more<00:20:48.760> questions<00:20:48.910> to 00:20:49.230 --> 00:20:49.240 align:start position:0% to come down I've got more questions to 00:20:49.240 --> 00:20:52.280 align:start position:0% to come down I've got more questions to ask<00:20:49.330> but<00:20:49.630> thought<00:20:49.960> I<00:20:49.990> might<00:20:50.140> turn<00:20:50.260> it<00:20:50.380> to<00:20:50.440> you 00:20:52.280 --> 00:20:52.290 align:start position:0% ask but thought I might turn it to you 00:20:52.290 --> 00:21:01.680 align:start position:0% ask but thought I might turn it to you you<00:20:53.290> want<00:20:53.440> to<00:20:53.500> ask<00:20:53.590> you<00:20:53.710> at<00:20:53.770> the<00:20:53.830> mic<00:20:53.950> here 00:21:01.680 --> 00:21:01.690 align:start position:0% 00:21:01.690 --> 00:21:04.860 align:start position:0% hi<00:21:02.200> I<00:21:02.410> was<00:21:02.680> making<00:21:03.070> some<00:21:03.220> notes<00:21:03.630> my<00:21:04.630> name<00:21:04.780> is 00:21:04.860 --> 00:21:04.870 align:start position:0% hi I was making some notes my name is 00:21:04.870 --> 00:21:07.350 align:start position:0% hi I was making some notes my name is Dimitri<00:21:05.290> CEO<00:21:06.190> and<00:21:06.460> co-founder<00:21:06.640> of<00:21:07.000> cyber 00:21:07.350 --> 00:21:07.360 align:start position:0% Dimitri CEO and co-founder of cyber 00:21:07.360 --> 00:21:09.570 align:start position:0% Dimitri CEO and co-founder of cyber security<00:21:07.570> consultant<00:21:08.320> company<00:21:08.530> how<00:21:08.860> can<00:21:09.040> I've 00:21:09.570 --> 00:21:09.580 align:start position:0% security consultant company how can I've 00:21:09.580 --> 00:21:12.600 align:start position:0% security consultant company how can I've made<00:21:09.850> about<00:21:10.060> 70<00:21:10.690> woods<00:21:11.230> for<00:21:11.770> the<00:21:11.800> last<00:21:12.040> nine 00:21:12.600 --> 00:21:12.610 align:start position:0% made about 70 woods for the last nine 00:21:12.610 --> 00:21:15.450 align:start position:0% made about 70 woods for the last nine months<00:21:12.640> and<00:21:13.380> we<00:21:14.380> are<00:21:14.440> all<00:21:14.590> based<00:21:14.830> in<00:21:14.950> Ukraine 00:21:15.450 --> 00:21:15.460 align:start position:0% months and we are all based in Ukraine 00:21:15.460 --> 00:21:19.560 align:start position:0% months and we are all based in Ukraine so<00:21:16.050> what<00:21:17.050> woods<00:21:17.380> I<00:21:18.040> made<00:21:18.610> notice<00:21:19.150> that<00:21:19.330> you 00:21:19.560 --> 00:21:19.570 align:start position:0% so what woods I made notice that you 00:21:19.570 --> 00:21:22.230 align:start position:0% so what woods I made notice that you like<00:21:20.080> were<00:21:20.770> saying<00:21:21.130> that<00:21:21.370> people<00:21:22.060> from 00:21:22.230 --> 00:21:22.240 align:start position:0% like were saying that people from 00:21:22.240 --> 00:21:24.300 align:start position:0% like were saying that people from traditional<00:21:22.780> cyber<00:21:23.290> security<00:21:23.650> companies<00:21:24.130> are 00:21:24.300 --> 00:21:24.310 align:start position:0% traditional cyber security companies are 00:21:24.310 --> 00:21:28.410 align:start position:0% traditional cyber security companies are entering<00:21:24.670> the<00:21:24.850> industry<00:21:25.090> yes<00:21:26.190> and<00:21:27.190> I<00:21:28.000> totally 00:21:28.410 --> 00:21:28.420 align:start position:0% entering the industry yes and I totally 00:21:28.420 --> 00:21:30.420 align:start position:0% entering the industry yes and I totally agree<00:21:28.660> that<00:21:28.960> the<00:21:29.080> bug<00:21:29.350> bounty<00:21:29.530> is<00:21:29.920> not<00:21:30.160> enough 00:21:30.420 --> 00:21:30.430 align:start position:0% agree that the bug bounty is not enough 00:21:30.430 --> 00:21:35.970 align:start position:0% agree that the bug bounty is not enough but<00:21:31.030> my<00:21:31.870> comment<00:21:32.770> is<00:21:33.040> that<00:21:34.050> it's<00:21:35.050> like<00:21:35.770> the 00:21:35.970 --> 00:21:35.980 align:start position:0% but my comment is that it's like the 00:21:35.980 --> 00:21:37.710 align:start position:0% but my comment is that it's like the traditional<00:21:36.460> people<00:21:36.610> like<00:21:36.910> I'm<00:21:37.360> eight<00:21:37.660> years 00:21:37.710 --> 00:21:37.720 align:start position:0% traditional people like I'm eight years 00:21:37.720 --> 00:21:39.750 align:start position:0% traditional people like I'm eight years delue<00:21:38.230> it<00:21:38.350> like<00:21:38.530> what<00:21:38.830> we<00:21:39.010> want<00:21:39.220> we<00:21:39.490> want<00:21:39.670> to 00:21:39.750 --> 00:21:39.760 align:start position:0% delue it like what we want we want to 00:21:39.760 --> 00:21:43.020 align:start position:0% delue it like what we want we want to have<00:21:39.970> a<00:21:40.350> methodology<00:21:41.350> and<00:21:41.470> guideline<00:21:42.400> like 00:21:43.020 --> 00:21:43.030 align:start position:0% have a methodology and guideline like 00:21:43.030 --> 00:21:45.750 align:start position:0% have a methodology and guideline like what<00:21:43.750> needs<00:21:44.410> to<00:21:44.560> be<00:21:44.740> done<00:21:44.890> in<00:21:45.070> order<00:21:45.190> to<00:21:45.460> be 00:21:45.750 --> 00:21:45.760 align:start position:0% what needs to be done in order to be 00:21:45.760 --> 00:21:47.760 align:start position:0% what needs to be done in order to be sure<00:21:46.060> that's<00:21:46.360> the<00:21:46.930> word<00:21:47.080> it<00:21:47.230> was<00:21:47.260> done 00:21:47.760 --> 00:21:47.770 align:start position:0% sure that's the word it was done 00:21:47.770 --> 00:21:51.390 align:start position:0% sure that's the word it was done correctly<00:21:47.980> and<00:21:48.520> I<00:21:49.530> think<00:21:50.530> that<00:21:50.800> this<00:21:51.070> is<00:21:51.220> what 00:21:51.390 --> 00:21:51.400 align:start position:0% correctly and I think that this is what 00:21:51.400 --> 00:21:54.780 align:start position:0% correctly and I think that this is what is<00:21:51.630> missing<00:21:52.630> so<00:21:53.080> far<00:21:53.350> in<00:21:53.560> this<00:21:53.770> industry<00:21:54.100> yes 00:21:54.780 --> 00:21:54.790 align:start position:0% is missing so far in this industry yes 00:21:54.790 --> 00:21:57.270 align:start position:0% is missing so far in this industry yes the<00:21:55.150> weakness<00:21:55.750> classification<00:21:56.470> work<00:21:56.920> is 00:21:57.270 --> 00:21:57.280 align:start position:0% the weakness classification work is 00:21:57.280 --> 00:21:59.310 align:start position:0% the weakness classification work is great<00:21:57.760> but<00:21:58.090> there<00:21:58.270> are<00:21:58.300> still<00:21:58.690> like<00:21:58.900> so<00:21:59.170> many 00:21:59.310 --> 00:21:59.320 align:start position:0% great but there are still like so many 00:21:59.320 --> 00:22:01.470 align:start position:0% great but there are still like so many things<00:21:59.440> needs<00:22:00.010> to<00:22:00.100> be<00:22:00.160> done<00:22:00.400> like<00:22:01.060> there<00:22:01.360> are 00:22:01.470 --> 00:22:01.480 align:start position:0% things needs to be done like there are 00:22:01.480 --> 00:22:04.320 align:start position:0% things needs to be done like there are two<00:22:02.010> ways<00:22:03.010> how<00:22:03.190> you<00:22:03.220> can<00:22:03.400> do<00:22:03.640> the<00:22:03.730> methodology 00:22:04.320 --> 00:22:04.330 align:start position:0% two ways how you can do the methodology 00:22:04.330 --> 00:22:06.630 align:start position:0% two ways how you can do the methodology is<00:22:04.390> a<00:22:04.510> principle<00:22:05.080> based<00:22:05.320> approach<00:22:05.710> like<00:22:06.010> what 00:22:06.630 --> 00:22:06.640 align:start position:0% is a principle based approach like what 00:22:06.640 --> 00:22:08.400 align:start position:0% is a principle based approach like what are<00:22:06.820> the<00:22:06.910> risks<00:22:07.270> and<00:22:07.390> how<00:22:07.570> to<00:22:07.630> cover<00:22:07.930> them<00:22:08.110> or 00:22:08.400 --> 00:22:08.410 align:start position:0% are the risks and how to cover them or 00:22:08.410 --> 00:22:12.270 align:start position:0% are the risks and how to cover them or the<00:22:08.860> second<00:22:09.280> is<00:22:09.430> the<00:22:09.930> checklists<00:22:10.930> what<00:22:11.740> what 00:22:12.270 --> 00:22:12.280 align:start position:0% the second is the checklists what what 00:22:12.280 --> 00:22:15.090 align:start position:0% the second is the checklists what what tests<00:22:12.490> needs<00:22:12.700> to<00:22:12.820> be<00:22:12.910> done<00:22:13.060> so<00:22:13.600> my<00:22:14.560> question<00:22:14.980> is 00:22:15.090 --> 00:22:15.100 align:start position:0% tests needs to be done so my question is 00:22:15.100 --> 00:22:18.030 align:start position:0% tests needs to be done so my question is like<00:22:15.160> how<00:22:15.730> do<00:22:16.360> you<00:22:16.660> see<00:22:17.050> what<00:22:17.440> is<00:22:17.620> the<00:22:17.800> right 00:22:18.030 --> 00:22:18.040 align:start position:0% like how do you see what is the right 00:22:18.040 --> 00:22:20.670 align:start position:0% like how do you see what is the right roadmap<00:22:18.730> to<00:22:19.060> create<00:22:19.420> this<00:22:19.570> methodology<00:22:19.990> who 00:22:20.670 --> 00:22:20.680 align:start position:0% roadmap to create this methodology who 00:22:20.680 --> 00:22:24.300 align:start position:0% roadmap to create this methodology who is<00:22:20.800> leading<00:22:21.160> this<00:22:21.340> process<00:22:21.640> and<00:22:22.060> like<00:22:23.070> like<00:22:24.070> I 00:22:24.300 --> 00:22:24.310 align:start position:0% is leading this process and like like I 00:22:24.310 --> 00:22:26.220 align:start position:0% is leading this process and like like I want<00:22:24.610> to<00:22:24.700> underline<00:22:24.940> I<00:22:25.120> think<00:22:25.480> this<00:22:25.720> is<00:22:25.870> one<00:22:26.200> of 00:22:26.220 --> 00:22:26.230 align:start position:0% want to underline I think this is one of 00:22:26.230 --> 00:22:27.660 align:start position:0% want to underline I think this is one of the<00:22:26.440> most<00:22:26.590> important<00:22:27.070> thing<00:22:27.280> right<00:22:27.490> now<00:22:27.520> that 00:22:27.660 --> 00:22:27.670 align:start position:0% the most important thing right now that 00:22:27.670 --> 00:22:29.790 align:start position:0% the most important thing right now that needs<00:22:28.030> to<00:22:28.150> be<00:22:28.180> done<00:22:28.390> in<00:22:28.540> this<00:22:28.660> industry<00:22:28.960> thank 00:22:29.790 --> 00:22:29.800 align:start position:0% needs to be done in this industry thank 00:22:29.800 --> 00:22:34.580 align:start position:0% needs to be done in this industry thank you<00:22:29.920> I<00:22:30.390> feel<00:22:31.390> that<00:22:31.450> one<00:22:31.920> yeah<00:22:32.920> so<00:22:33.220> we<00:22:34.030> do<00:22:34.180> have<00:22:34.360> a 00:22:34.580 --> 00:22:34.590 align:start position:0% you I feel that one yeah so we do have a 00:22:34.590 --> 00:22:37.770 align:start position:0% you I feel that one yeah so we do have a a<00:22:35.590> community<00:22:36.250> called<00:22:36.430> East<00:22:36.640> security<00:22:37.060> which 00:22:37.770 --> 00:22:37.780 align:start position:0% a community called East security which 00:22:37.780 --> 00:22:39.480 align:start position:0% a community called East security which is<00:22:37.810> a<00:22:38.080> community<00:22:38.500> that<00:22:38.530> I<00:22:38.680> lead<00:22:38.890> and<00:22:39.220> then<00:22:39.370> out 00:22:39.480 --> 00:22:39.490 align:start position:0% is a community that I lead and then out 00:22:39.490 --> 00:22:40.530 align:start position:0% is a community that I lead and then out of<00:22:39.520> that<00:22:39.640> we<00:22:39.760> have<00:22:40.000> a<00:22:40.030> number<00:22:40.210> of<00:22:40.330> working 00:22:40.530 --> 00:22:40.540 align:start position:0% of that we have a number of working 00:22:40.540 --> 00:22:42.960 align:start position:0% of that we have a number of working groups<00:22:40.690> so<00:22:41.560> there's<00:22:41.710> actually<00:22:42.100> a<00:22:42.520> working 00:22:42.960 --> 00:22:42.970 align:start position:0% groups so there's actually a working 00:22:42.970 --> 00:22:46.800 align:start position:0% groups so there's actually a working group<00:22:43.240> for<00:22:43.410> developer<00:22:44.410> guidelines<00:22:45.210> and<00:22:46.210> as 00:22:46.800 --> 00:22:46.810 align:start position:0% group for developer guidelines and as 00:22:46.810 --> 00:22:50.700 align:start position:0% group for developer guidelines and as well<00:22:46.990> as<00:22:48.570> auditor<00:22:49.570> guidelines<00:22:49.960> or<00:22:50.170> assessment 00:22:50.700 --> 00:22:50.710 align:start position:0% well as auditor guidelines or assessment 00:22:50.710 --> 00:22:52.830 align:start position:0% well as auditor guidelines or assessment guidelines<00:22:51.150> so<00:22:52.150> the<00:22:52.420> smart<00:22:52.690> contract 00:22:52.830 --> 00:22:52.840 align:start position:0% guidelines so the smart contract 00:22:52.840 --> 00:22:55.130 align:start position:0% guidelines so the smart contract Alliance<00:22:53.590> is<00:22:53.710> one<00:22:53.890> of<00:22:53.980> the<00:22:54.040> groups<00:22:54.250> in 00:22:55.130 --> 00:22:55.140 align:start position:0% Alliance is one of the groups in 00:22:55.140 --> 00:22:57.180 align:start position:0% Alliance is one of the groups in SecureAuth<00:22:56.170> is<00:22:56.380> making<00:22:56.710> the<00:22:56.800> developer 00:22:57.180 --> 00:22:57.190 align:start position:0% SecureAuth is making the developer 00:22:57.190 --> 00:22:59.580 align:start position:0% SecureAuth is making the developer guidelines<00:22:57.430> so<00:22:57.790> I<00:22:58.360> encourage<00:22:58.840> you<00:22:59.020> to<00:22:59.140> reach 00:22:59.580 --> 00:22:59.590 align:start position:0% guidelines so I encourage you to reach 00:22:59.590 --> 00:23:01.590 align:start position:0% guidelines so I encourage you to reach out<00:22:59.740> and<00:22:59.950> get<00:23:00.820> involved<00:23:01.030> in<00:23:01.240> those<00:23:01.360> groups 00:23:01.590 --> 00:23:01.600 align:start position:0% out and get involved in those groups 00:23:01.600 --> 00:23:03.450 align:start position:0% out and get involved in those groups because<00:23:01.750> they<00:23:01.840> are<00:23:01.990> open<00:23:02.290> if<00:23:03.130> you<00:23:03.190> want<00:23:03.220> to<00:23:03.370> hit 00:23:03.450 --> 00:23:03.460 align:start position:0% because they are open if you want to hit 00:23:03.460 --> 00:23:04.890 align:start position:0% because they are open if you want to hit me<00:23:03.520> up<00:23:03.610> on<00:23:03.730> telegram<00:23:04.150> I<00:23:04.180> can<00:23:04.420> add<00:23:04.540> you<00:23:04.570> to<00:23:04.690> the 00:23:04.890 --> 00:23:04.900 align:start position:0% me up on telegram I can add you to the 00:23:04.900 --> 00:23:07.410 align:start position:0% me up on telegram I can add you to the correct<00:23:05.080> channels<00:23:06.090> you're<00:23:07.090> in<00:23:07.180> the<00:23:07.270> group 00:23:07.410 --> 00:23:07.420 align:start position:0% correct channels you're in the group 00:23:07.420 --> 00:23:10.410 align:start position:0% correct channels you're in the group cool<00:23:08.130> awesome<00:23:09.220> yes<00:23:09.340> I'm<00:23:09.490> you<00:23:09.610> having<00:23:10.180> elseis 00:23:10.410 --> 00:23:10.420 align:start position:0% cool awesome yes I'm you having elseis 00:23:10.420 --> 00:23:13.860 align:start position:0% cool awesome yes I'm you having elseis anything<00:23:10.720> on<00:23:10.990> that<00:23:12.180> yeah<00:23:13.180> so<00:23:13.390> I<00:23:13.420> would<00:23:13.660> caution 00:23:13.860 --> 00:23:13.870 align:start position:0% anything on that yeah so I would caution 00:23:13.870 --> 00:23:15.630 align:start position:0% anything on that yeah so I would caution against<00:23:14.380> trusting<00:23:14.770> any<00:23:14.950> formal<00:23:15.370> like 00:23:15.630 --> 00:23:15.640 align:start position:0% against trusting any formal like 00:23:15.640 --> 00:23:17.280 align:start position:0% against trusting any formal like checklist<00:23:15.970> or<00:23:16.180> process<00:23:16.600> too<00:23:16.780> much<00:23:16.960> because 00:23:17.280 --> 00:23:17.290 align:start position:0% checklist or process too much because 00:23:17.290 --> 00:23:19.410 align:start position:0% checklist or process too much because the<00:23:17.590> entire<00:23:17.890> sort<00:23:18.490> of<00:23:18.580> point<00:23:18.880> of<00:23:19.030> an<00:23:19.150> attacker 00:23:19.410 --> 00:23:19.420 align:start position:0% the entire sort of point of an attacker 00:23:19.420 --> 00:23:21.660 align:start position:0% the entire sort of point of an attacker in<00:23:19.840> in<00:23:20.110> in<00:23:20.320> the<00:23:20.650> security<00:23:21.040> world<00:23:21.070> is<00:23:21.460> that<00:23:21.580> they 00:23:21.660 --> 00:23:21.670 align:start position:0% in in in the security world is that they 00:23:21.670 --> 00:23:23.010 align:start position:0% in in in the security world is that they understand<00:23:22.150> your<00:23:22.300> assumptions<00:23:22.720> and<00:23:22.810> try<00:23:22.960> to 00:23:23.010 --> 00:23:23.020 align:start position:0% understand your assumptions and try to 00:23:23.020 --> 00:23:24.930 align:start position:0% understand your assumptions and try to violate<00:23:23.200> them<00:23:23.620> so<00:23:24.190> that<00:23:24.340> checklist<00:23:24.580> could 00:23:24.930 --> 00:23:24.940 align:start position:0% violate them so that checklist could 00:23:24.940 --> 00:23:26.520 align:start position:0% violate them so that checklist could actually<00:23:25.090> lead<00:23:25.420> to<00:23:25.450> sort<00:23:25.810> of<00:23:25.870> blind<00:23:26.110> spots<00:23:26.410> in 00:23:26.520 --> 00:23:26.530 align:start position:0% actually lead to sort of blind spots in 00:23:26.530 --> 00:23:28.710 align:start position:0% actually lead to sort of blind spots in your<00:23:26.590> process<00:23:27.040> as<00:23:27.220> well<00:23:27.370> so<00:23:28.270> what<00:23:28.390> I<00:23:28.420> would<00:23:28.510> say 00:23:28.710 --> 00:23:28.720 align:start position:0% your process as well so what I would say 00:23:28.720 --> 00:23:30.450 align:start position:0% your process as well so what I would say is<00:23:28.870> that<00:23:28.900> any<00:23:29.200> sort<00:23:29.530> of<00:23:29.560> halfway<00:23:29.800> competent 00:23:30.450 --> 00:23:30.460 align:start position:0% is that any sort of halfway competent 00:23:30.460 --> 00:23:31.890 align:start position:0% is that any sort of halfway competent person<00:23:30.730> you<00:23:30.820> hire<00:23:31.030> to<00:23:31.300> take<00:23:31.450> a<00:23:31.480> look<00:23:31.660> at<00:23:31.780> your 00:23:31.890 --> 00:23:31.900 align:start position:0% person you hire to take a look at your 00:23:31.900 --> 00:23:33.330 align:start position:0% person you hire to take a look at your contract<00:23:32.020> should<00:23:32.920> sort<00:23:33.070> of<00:23:33.160> know 00:23:33.330 --> 00:23:33.340 align:start position:0% contract should sort of know 00:23:33.340 --> 00:23:35.160 align:start position:0% contract should sort of know subjectively<00:23:33.940> like<00:23:34.180> as<00:23:34.330> a<00:23:34.360> human<00:23:34.690> being<00:23:34.870> like 00:23:35.160 --> 00:23:35.170 align:start position:0% subjectively like as a human being like 00:23:35.170 --> 00:23:36.810 align:start position:0% subjectively like as a human being like where<00:23:35.440> are<00:23:35.650> my<00:23:35.800> blind<00:23:36.070> spots<00:23:36.340> what<00:23:36.640> have<00:23:36.790> I 00:23:36.810 --> 00:23:36.820 align:start position:0% where are my blind spots what have I 00:23:36.820 --> 00:23:38.730 align:start position:0% where are my blind spots what have I looked<00:23:37.150> at<00:23:37.300> what<00:23:37.600> have<00:23:37.720> I<00:23:37.840> not<00:23:38.020> what 00:23:38.730 --> 00:23:38.740 align:start position:0% looked at what have I not what 00:23:38.740 --> 00:23:40.290 align:start position:0% looked at what have I not what state-of-the-art<00:23:39.280> stuff<00:23:39.580> have<00:23:39.820> I<00:23:39.940> done<00:23:40.090> what 00:23:40.290 --> 00:23:40.300 align:start position:0% state-of-the-art stuff have I done what 00:23:40.300 --> 00:23:41.430 align:start position:0% state-of-the-art stuff have I done what state-of-the-art<00:23:40.690> stuff<00:23:40.960> have<00:23:41.170> I<00:23:41.260> not<00:23:41.380> done 00:23:41.430 --> 00:23:41.440 align:start position:0% state-of-the-art stuff have I not done 00:23:41.440 --> 00:23:42.990 align:start position:0% state-of-the-art stuff have I not done and<00:23:41.860> they<00:23:42.160> should<00:23:42.310> actually<00:23:42.550> inform<00:23:42.850> you 00:23:42.990 --> 00:23:43.000 align:start position:0% and they should actually inform you 00:23:43.000 --> 00:23:45.510 align:start position:0% and they should actually inform you about<00:23:43.090> that<00:23:43.420> as<00:23:43.630> part<00:23:43.960> of<00:23:44.020> the<00:23:44.140> process<00:23:44.520> and 00:23:45.510 --> 00:23:45.520 align:start position:0% about that as part of the process and 00:23:45.520 --> 00:23:47.220 align:start position:0% about that as part of the process and and<00:23:46.090> having<00:23:46.300> someone<00:23:46.540> internal<00:23:46.990> who<00:23:47.080> also 00:23:47.220 --> 00:23:47.230 align:start position:0% and having someone internal who also 00:23:47.230 --> 00:23:48.510 align:start position:0% and having someone internal who also understands<00:23:47.680> the<00:23:47.800> state-of-the-art<00:23:48.190> could 00:23:48.510 --> 00:23:48.520 align:start position:0% understands the state-of-the-art could 00:23:48.520 --> 00:23:52.680 align:start position:0% understands the state-of-the-art could help<00:23:48.670> you<00:23:48.790> with<00:23:48.910> that<00:23:49.030> -<00:23:50.190> yeah<00:23:51.190> I<00:23:52.000> just<00:23:52.270> like<00:23:52.540> to 00:23:52.680 --> 00:23:52.690 align:start position:0% help you with that - yeah I just like to 00:23:52.690 --> 00:23:56.300 align:start position:0% help you with that - yeah I just like to add<00:23:52.780> that<00:23:52.870> I<00:23:53.470> think<00:23:53.830> checklists<00:23:54.490> are<00:23:55.170> great 00:23:56.300 --> 00:23:56.310 align:start position:0% add that I think checklists are great 00:23:56.310 --> 00:23:59.040 align:start position:0% add that I think checklists are great but<00:23:57.310> they're<00:23:57.520> not<00:23:57.550> for<00:23:57.820> auditors<00:23:58.240> they're<00:23:58.810> for 00:23:59.040 --> 00:23:59.050 align:start position:0% but they're not for auditors they're for 00:23:59.050 --> 00:24:01.620 align:start position:0% but they're not for auditors they're for developers<00:23:59.710> to<00:24:00.130> kind<00:24:00.550> of<00:24:00.610> check<00:24:00.970> while<00:24:01.420> they 00:24:01.620 --> 00:24:01.630 align:start position:0% developers to kind of check while they 00:24:01.630 --> 00:24:04.170 align:start position:0% developers to kind of check while they write<00:24:01.810> in<00:24:01.990> the<00:24:02.020> code<00:24:02.670> but<00:24:03.670> the<00:24:03.790> auditors 00:24:04.170 --> 00:24:04.180 align:start position:0% write in the code but the auditors 00:24:04.180 --> 00:24:07.080 align:start position:0% write in the code but the auditors shouldn't<00:24:04.780> have<00:24:04.870> to<00:24:05.220> you<00:24:06.220> know<00:24:06.340> rely<00:24:06.730> on<00:24:06.760> those 00:24:07.080 --> 00:24:07.090 align:start position:0% shouldn't have to you know rely on those 00:24:07.090 --> 00:24:09.360 align:start position:0% shouldn't have to you know rely on those who<00:24:07.330> use<00:24:07.630> those<00:24:07.840> extensively<00:24:08.410> yeah<00:24:08.800> I<00:24:08.860> will 00:24:09.360 --> 00:24:09.370 align:start position:0% who use those extensively yeah I will 00:24:09.370 --> 00:24:11.940 align:start position:0% who use those extensively yeah I will add<00:24:09.520> those<00:24:09.760> the<00:24:10.390> developer<00:24:10.810> and<00:24:10.960> assessment 00:24:11.940 --> 00:24:11.950 align:start position:0% add those the developer and assessment 00:24:11.950 --> 00:24:13.410 align:start position:0% add those the developer and assessment guidelines<00:24:12.250> are<00:24:12.370> more<00:24:12.580> framework<00:24:13.000> for<00:24:13.240> like 00:24:13.410 --> 00:24:13.420 align:start position:0% guidelines are more framework for like 00:24:13.420 --> 00:24:15.210 align:start position:0% guidelines are more framework for like as<00:24:13.630> I<00:24:13.690> enter<00:24:14.230> into<00:24:14.410> the<00:24:14.620> product<00:24:14.920> like<00:24:15.010> as<00:24:15.130> a 00:24:15.210 --> 00:24:15.220 align:start position:0% as I enter into the product like as a 00:24:15.220 --> 00:24:16.560 align:start position:0% as I enter into the product like as a developer<00:24:15.670> what<00:24:16.030> are<00:24:16.180> the<00:24:16.240> steps<00:24:16.450> I'm<00:24:16.540> going 00:24:16.560 --> 00:24:16.570 align:start position:0% developer what are the steps I'm going 00:24:16.570 --> 00:24:17.760 align:start position:0% developer what are the steps I'm going to<00:24:16.720> go<00:24:16.840> through<00:24:17.140> so<00:24:17.380> that<00:24:17.500> I<00:24:17.530> have<00:24:17.740> a 00:24:17.760 --> 00:24:17.770 align:start position:0% to go through so that I have a 00:24:17.770 --> 00:24:21.930 align:start position:0% to go through so that I have a consistent<00:24:18.900> product<00:24:19.900> to<00:24:20.310> then<00:24:21.310> hand<00:24:21.580> over<00:24:21.700> to 00:24:21.930 --> 00:24:21.940 align:start position:0% consistent product to then hand over to 00:24:21.940 --> 00:24:23.280 align:start position:0% consistent product to then hand over to an<00:24:22.060> auditor<00:24:22.360> when<00:24:22.510> they<00:24:22.630> receive<00:24:22.960> it<00:24:23.050> so<00:24:23.170> it's 00:24:23.280 --> 00:24:23.290 align:start position:0% an auditor when they receive it so it's 00:24:23.290 --> 00:24:26.460 align:start position:0% an auditor when they receive it so it's not<00:24:23.380> just<00:24:23.440> like<00:24:23.710> a<00:24:23.740> bunch<00:24:23.980> of<00:24:24.100> like<00:24:24.250> files<00:24:25.470> and 00:24:26.460 --> 00:24:26.470 align:start position:0% not just like a bunch of like files and 00:24:26.470 --> 00:24:28.470 align:start position:0% not just like a bunch of like files and only<00:24:27.220> only<00:24:27.610> assessment<00:24:27.880> sighs<00:24:28.120> like<00:24:28.270> okay 00:24:28.470 --> 00:24:28.480 align:start position:0% only only assessment sighs like okay 00:24:28.480 --> 00:24:31.200 align:start position:0% only only assessment sighs like okay what<00:24:28.720> are<00:24:28.810> we<00:24:28.840> going<00:24:29.140> to<00:24:29.320> be<00:24:29.740> delivering<00:24:30.280> back 00:24:31.200 --> 00:24:31.210 align:start position:0% what are we going to be delivering back 00:24:31.210 --> 00:24:33.360 align:start position:0% what are we going to be delivering back to<00:24:31.360> the<00:24:31.450> client<00:24:31.690> and<00:24:32.020> so<00:24:32.440> that<00:24:32.710> the<00:24:32.800> process<00:24:33.220> is 00:24:33.360 --> 00:24:33.370 align:start position:0% to the client and so that the process is 00:24:33.370 --> 00:24:34.650 align:start position:0% to the client and so that the process is a<00:24:33.400> little<00:24:33.610> bit<00:24:33.700> more<00:24:33.910> there's<00:24:34.540> some 00:24:34.650 --> 00:24:34.660 align:start position:0% a little bit more there's some 00:24:34.660 --> 00:24:36.870 align:start position:0% a little bit more there's some expectations<00:24:35.260> on<00:24:35.500> what<00:24:35.980> you<00:24:36.100> give<00:24:36.850> and 00:24:36.870 --> 00:24:36.880 align:start position:0% expectations on what you give and 00:24:36.880 --> 00:24:39.860 align:start position:0% expectations on what you give and receive 00:24:39.860 --> 00:24:39.870 align:start position:0% 00:24:39.870 --> 00:24:44.040 align:start position:0% somebody<00:24:40.870> else<00:24:40.990> over<00:24:41.170> here<00:24:41.320> I<00:24:42.780> would<00:24:43.780> like<00:24:43.930> to 00:24:44.040 --> 00:24:44.050 align:start position:0% somebody else over here I would like to 00:24:44.050 --> 00:24:47.070 align:start position:0% somebody else over here I would like to ask<00:24:44.200> you<00:24:44.470> about<00:24:44.610> security<00:24:45.610> in<00:24:45.790> future<00:24:46.600> proof 00:24:47.070 --> 00:24:47.080 align:start position:0% ask you about security in future proof 00:24:47.080 --> 00:24:48.660 align:start position:0% ask you about security in future proof of<00:24:47.200> stake<00:24:47.440> actually 00:24:48.660 --> 00:24:48.670 align:start position:0% of stake actually 00:24:48.670 --> 00:24:52.590 align:start position:0% of stake actually security<00:24:49.240> of<00:24:49.480> validators<00:24:50.490> and<00:24:51.600> because 00:24:52.590 --> 00:24:52.600 align:start position:0% security of validators and because 00:24:52.600 --> 00:24:54.660 align:start position:0% security of validators and because basically<00:24:52.930> issue<00:24:53.320> is<00:24:53.560> that<00:24:53.590> what<00:24:54.550> you 00:24:54.660 --> 00:24:54.670 align:start position:0% basically issue is that what you 00:24:54.670 --> 00:24:55.770 align:start position:0% basically issue is that what you mentioned<00:24:54.850> anion<00:24:55.240> validator 00:24:55.770 --> 00:24:55.780 align:start position:0% mentioned anion validator 00:24:55.780 --> 00:24:58.110 align:start position:0% mentioned anion validator I<00:24:55.960> will<00:24:56.170> put<00:24:56.290> like<00:24:56.440> 1,000<00:24:57.250> of<00:24:57.340> ether<00:24:57.550> in<00:24:57.820> the<00:24:57.970> my 00:24:58.110 --> 00:24:58.120 align:start position:0% I will put like 1,000 of ether in the my 00:24:58.120 --> 00:25:01.260 align:start position:0% I will put like 1,000 of ether in the my wallet<00:24:58.510> and<00:24:58.740> I<00:24:59.740> will<00:24:59.920> register<00:25:00.160> the<00:25:00.700> wallet 00:25:01.260 --> 00:25:01.270 align:start position:0% wallet and I will register the wallet 00:25:01.270 --> 00:25:03.660 align:start position:0% wallet and I will register the wallet for<00:25:01.780> force<00:25:02.290> taking<00:25:02.530> right<00:25:03.040> I<00:25:03.280> will<00:25:03.520> register 00:25:03.660 --> 00:25:03.670 align:start position:0% for force taking right I will register 00:25:03.670 --> 00:25:06.660 align:start position:0% for force taking right I will register with<00:25:04.060> my<00:25:04.180> private<00:25:04.390> key<00:25:04.750> and<00:25:05.620> what<00:25:05.830> happen<00:25:06.220> if 00:25:06.660 --> 00:25:06.670 align:start position:0% with my private key and what happen if 00:25:06.670 --> 00:25:09.300 align:start position:0% with my private key and what happen if I'm<00:25:07.420> signing<00:25:07.810> blog<00:25:08.230> with<00:25:08.440> the<00:25:08.530> same<00:25:08.770> key<00:25:09.100> in 00:25:09.300 --> 00:25:09.310 align:start position:0% I'm signing blog with the same key in 00:25:09.310 --> 00:25:11.040 align:start position:0% I'm signing blog with the same key in the<00:25:09.550> internet<00:25:10.060> work<00:25:10.300> and<00:25:10.570> let's<00:25:10.840> say<00:25:10.930> that 00:25:11.040 --> 00:25:11.050 align:start position:0% the internet work and let's say that 00:25:11.050 --> 00:25:12.990 align:start position:0% the internet work and let's say that someone<00:25:11.260> will<00:25:11.500> hack<00:25:11.680> my<00:25:11.860> note<00:25:12.130> can<00:25:12.790> he 00:25:12.990 --> 00:25:13.000 align:start position:0% someone will hack my note can he 00:25:13.000 --> 00:25:15.090 align:start position:0% someone will hack my note can he actually<00:25:13.450> use<00:25:13.630> the<00:25:13.780> same<00:25:13.960> private<00:25:14.350> key<00:25:14.560> to<00:25:14.830> the 00:25:15.090 --> 00:25:15.100 align:start position:0% actually use the same private key to the 00:25:15.100 --> 00:25:18.540 align:start position:0% actually use the same private key to the registered<00:25:15.580> my<00:25:15.790> note<00:25:16.090> and<00:25:16.800> actually<00:25:17.800> take 00:25:18.540 --> 00:25:18.550 align:start position:0% registered my note and actually take 00:25:18.550 --> 00:25:21.560 align:start position:0% registered my note and actually take mistake<00:25:19.000> or<00:25:19.660> my<00:25:20.260> question<00:25:20.650> is<00:25:20.770> how<00:25:21.070> can<00:25:21.280> I 00:25:21.560 --> 00:25:21.570 align:start position:0% mistake or my question is how can I 00:25:21.570 --> 00:25:24.360 align:start position:0% mistake or my question is how can I secure<00:25:22.570> my<00:25:22.630> stake<00:25:23.050> in<00:25:23.380> the<00:25:23.560> future<00:25:23.740> proposal 00:25:24.360 --> 00:25:24.370 align:start position:0% secure my stake in the future proposal 00:25:24.370 --> 00:25:28.350 align:start position:0% secure my stake in the future proposal I'm<00:25:24.580> trying<00:25:24.910> to<00:25:25.030> find<00:25:25.210> it<00:25:25.390> but<00:25:26.940> did<00:25:27.940> you<00:25:28.030> get<00:25:28.210> it 00:25:28.350 --> 00:25:28.360 align:start position:0% I'm trying to find it but did you get it 00:25:28.360 --> 00:25:29.240 align:start position:0% I'm trying to find it but did you get it what<00:25:28.750> I 00:25:29.240 --> 00:25:29.250 align:start position:0% what I 00:25:29.250 --> 00:25:32.010 align:start position:0% what I can<00:25:30.250> i<00:25:30.340> rephrase<00:25:30.580> it<00:25:30.880> because<00:25:31.420> i'm<00:25:31.570> not<00:25:31.720> sure 00:25:32.010 --> 00:25:32.020 align:start position:0% can i rephrase it because i'm not sure 00:25:32.020 --> 00:25:35.220 align:start position:0% can i rephrase it because i'm not sure and<00:25:32.200> i'm<00:25:32.320> no<00:25:32.470> probe<00:25:32.890> a<00:25:32.920> stack<00:25:33.190> expert<00:25:33.610> but<00:25:34.230> what 00:25:35.220 --> 00:25:35.230 align:start position:0% and i'm no probe a stack expert but what 00:25:35.230 --> 00:25:38.100 align:start position:0% and i'm no probe a stack expert but what i<00:25:35.260> think<00:25:35.410> you're<00:25:36.190> asking<00:25:36.400> is<00:25:36.850> the<00:25:36.970> same<00:25:37.270> as<00:25:37.660> for 00:25:38.100 --> 00:25:38.110 align:start position:0% i think you're asking is the same as for 00:25:38.110 --> 00:25:40.799 align:start position:0% i think you're asking is the same as for proof<00:25:38.380> of<00:25:38.530> authority<00:25:39.130> chains<00:25:39.520> where<00:25:40.390> the 00:25:40.799 --> 00:25:40.809 align:start position:0% proof of authority chains where the 00:25:40.809 --> 00:25:43.260 align:start position:0% proof of authority chains where the actual<00:25:41.470> sealing<00:25:42.070> requires<00:25:42.520> the<00:25:42.790> presence<00:25:43.179> of 00:25:43.260 --> 00:25:43.270 align:start position:0% actual sealing requires the presence of 00:25:43.270 --> 00:25:46.520 align:start position:0% actual sealing requires the presence of the<00:25:43.450> of<00:25:43.960> the<00:25:44.230> private<00:25:44.800> key<00:25:44.980> in<00:25:45.190> the<00:25:45.429> node<00:25:45.610> yes 00:25:46.520 --> 00:25:46.530 align:start position:0% the of the private key in the node yes 00:25:46.530 --> 00:25:51.750 align:start position:0% the of the private key in the node yes and<00:25:48.360> yes<00:25:49.360> that<00:25:50.260> is<00:25:50.380> the<00:25:50.530> case<00:25:50.710> so<00:25:51.460> you<00:25:51.520> will 00:25:51.750 --> 00:25:51.760 align:start position:0% and yes that is the case so you will 00:25:51.760 --> 00:25:53.700 align:start position:0% and yes that is the case so you will actually<00:25:52.000> have<00:25:52.390> a<00:25:52.420> network<00:25:52.900> node<00:25:53.170> which 00:25:53.700 --> 00:25:53.710 align:start position:0% actually have a network node which 00:25:53.710 --> 00:25:55.500 align:start position:0% actually have a network node which contains<00:25:54.309> the<00:25:54.460> private<00:25:54.820> key<00:25:55.030> or<00:25:55.210> private 00:25:55.500 --> 00:25:55.510 align:start position:0% contains the private key or private 00:25:55.510 --> 00:25:58.650 align:start position:0% contains the private key or private secret<00:25:55.870> alternative<00:25:56.830> they<00:25:57.179> can<00:25:58.179> talk<00:25:58.630> to 00:25:58.650 --> 00:25:58.660 align:start position:0% secret alternative they can talk to 00:25:58.660 --> 00:26:03.270 align:start position:0% secret alternative they can talk to back-end<00:25:59.200> to<00:25:59.410> get<00:26:00.360> something<00:26:01.360> sealed<00:26:02.280> is 00:26:03.270 --> 00:26:03.280 align:start position:0% back-end to get something sealed is 00:26:03.280 --> 00:26:06.980 align:start position:0% back-end to get something sealed is there<00:26:03.490> actually<00:26:04.090> any<00:26:04.120> solution<00:26:05.429> actually 00:26:06.980 --> 00:26:06.990 align:start position:0% there actually any solution actually 00:26:06.990 --> 00:26:10.650 align:start position:0% there actually any solution actually there<00:26:07.990> is<00:26:08.080> a<00:26:08.110> solution<00:26:09.330> that<00:26:10.330> there<00:26:10.570> are 00:26:10.650 --> 00:26:10.660 align:start position:0% there is a solution that there are 00:26:10.660 --> 00:26:11.520 align:start position:0% there is a solution that there are different<00:26:10.929> ways<00:26:11.080> to<00:26:11.260> do<00:26:11.380> it 00:26:11.520 --> 00:26:11.530 align:start position:0% different ways to do it 00:26:11.530 --> 00:26:18.630 align:start position:0% different ways to do it one<00:26:12.040> thing<00:26:14.490> is<00:26:15.490> the<00:26:15.960> this<00:26:17.010> i've<00:26:18.010> been<00:26:18.220> working 00:26:18.630 --> 00:26:18.640 align:start position:0% one thing is the this i've been working 00:26:18.640 --> 00:26:19.860 align:start position:0% one thing is the this i've been working like<00:26:18.730> the<00:26:18.880> last<00:26:19.059> year<00:26:19.240> building<00:26:19.450> something 00:26:19.860 --> 00:26:19.870 align:start position:0% like the last year building something 00:26:19.870 --> 00:26:21.840 align:start position:0% like the last year building something called<00:26:20.050> clay<00:26:20.320> clef<00:26:20.890> it's<00:26:21.160> in<00:26:21.280> the<00:26:21.340> go<00:26:21.460> theorem 00:26:21.840 --> 00:26:21.850 align:start position:0% called clay clef it's in the go theorem 00:26:21.850 --> 00:26:23.790 align:start position:0% called clay clef it's in the go theorem repo<00:26:22.210> it's<00:26:22.690> an<00:26:22.870> account<00:26:23.140> management<00:26:23.500> tool 00:26:23.790 --> 00:26:23.800 align:start position:0% repo it's an account management tool 00:26:23.800 --> 00:26:27.570 align:start position:0% repo it's an account management tool which<00:26:24.960> can<00:26:25.960> also<00:26:26.260> do<00:26:26.559> signing<00:26:27.040> for<00:26:27.250> click 00:26:27.570 --> 00:26:27.580 align:start position:0% which can also do signing for click 00:26:27.580 --> 00:26:33.270 align:start position:0% which can also do signing for click blocks<00:26:28.210> which<00:26:28.809> is<00:26:28.990> a<00:26:30.780> proof<00:26:31.780> of<00:26:32.280> authority 00:26:33.270 --> 00:26:33.280 align:start position:0% blocks which is a proof of authority 00:26:33.280 --> 00:26:38.900 align:start position:0% blocks which is a proof of authority chain<00:26:33.580> type<00:26:34.330> so<00:26:34.780> there<00:26:35.590> are<00:26:35.770> solutions<00:26:36.270> but 00:26:38.900 --> 00:26:38.910 align:start position:0% chain type so there are solutions but 00:26:38.910 --> 00:26:43.500 align:start position:0% chain type so there are solutions but it's<00:26:39.910> not<00:26:40.170> production-ready<00:26:41.170> i<00:26:41.320> guess<00:26:41.530> yet<00:26:42.510> so 00:26:43.500 --> 00:26:43.510 align:start position:0% it's not production-ready i guess yet so 00:26:43.510 --> 00:26:44.970 align:start position:0% it's not production-ready i guess yet so so<00:26:43.720> from<00:26:43.809> my<00:26:43.960> conversations<00:26:44.590> I've<00:26:44.710> had<00:26:44.740> with 00:26:44.970 --> 00:26:44.980 align:start position:0% so from my conversations I've had with 00:26:44.980 --> 00:26:47.160 align:start position:0% so from my conversations I've had with caspere<00:26:45.910> people<00:26:46.270> and<00:26:46.420> it's<00:26:46.540> kind<00:26:46.600> of<00:26:46.870> hard<00:26:47.110> to 00:26:47.160 --> 00:26:47.170 align:start position:0% caspere people and it's kind of hard to 00:26:47.170 --> 00:26:48.720 align:start position:0% caspere people and it's kind of hard to nail<00:26:47.410> down<00:26:47.440> because<00:26:48.040> the<00:26:48.130> spec<00:26:48.400> is<00:26:48.550> so 00:26:48.720 --> 00:26:48.730 align:start position:0% nail down because the spec is so 00:26:48.730 --> 00:26:50.940 align:start position:0% nail down because the spec is so constantly<00:26:49.210> evolving<00:26:49.720> it<00:26:50.590> would<00:26:50.710> certainly 00:26:50.940 --> 00:26:50.950 align:start position:0% constantly evolving it would certainly 00:26:50.950 --> 00:26:52.710 align:start position:0% constantly evolving it would certainly be<00:26:51.130> possible<00:26:51.160> to<00:26:51.670> have<00:26:51.790> a<00:26:51.820> separate<00:26:52.210> key<00:26:52.420> for 00:26:52.710 --> 00:26:52.720 align:start position:0% be possible to have a separate key for 00:26:52.720 --> 00:26:54.480 align:start position:0% be possible to have a separate key for signing<00:26:53.080> proof<00:26:53.260> of<00:26:53.350> stake<00:26:53.559> messages<00:26:54.010> than<00:26:54.250> for 00:26:54.480 --> 00:26:54.490 align:start position:0% signing proof of stake messages than for 00:26:54.490 --> 00:26:56.280 align:start position:0% signing proof of stake messages than for moving<00:26:54.700> funds<00:26:55.030> and<00:26:55.360> then<00:26:55.780> essentially<00:26:56.080> what 00:26:56.280 --> 00:26:56.290 align:start position:0% moving funds and then essentially what 00:26:56.290 --> 00:26:57.930 align:start position:0% moving funds and then essentially what you<00:26:56.380> would<00:26:56.470> do<00:26:56.590> is<00:26:56.740> you'd<00:26:56.920> sort<00:26:57.250> of<00:26:57.370> delegate 00:26:57.930 --> 00:26:57.940 align:start position:0% you would do is you'd sort of delegate 00:26:57.940 --> 00:26:59.910 align:start position:0% you would do is you'd sort of delegate to<00:26:58.059> that<00:26:58.179> key<00:26:58.390> and<00:26:58.600> that<00:26:58.720> key<00:26:58.900> would<00:26:59.679> put<00:26:59.830> you 00:26:59.910 --> 00:26:59.920 align:start position:0% to that key and that key would put you 00:26:59.920 --> 00:27:01.350 align:start position:0% to that key and that key would put you at<00:26:59.950> risk<00:27:00.100> in<00:27:00.550> the<00:27:00.670> way<00:27:00.760> that<00:27:01.000> it<00:27:01.120> could<00:27:01.240> get 00:27:01.350 --> 00:27:01.360 align:start position:0% at risk in the way that it could get 00:27:01.360 --> 00:27:03.120 align:start position:0% at risk in the way that it could get your<00:27:01.480> funds<00:27:01.690> slash<00:27:01.990> if<00:27:02.380> someone<00:27:02.620> misbehaved 00:27:03.120 --> 00:27:03.130 align:start position:0% your funds slash if someone misbehaved 00:27:03.130 --> 00:27:05.340 align:start position:0% your funds slash if someone misbehaved on<00:27:03.280> your<00:27:03.429> behalf<00:27:03.730> but<00:27:04.600> maybe<00:27:04.750> the<00:27:04.960> protocol 00:27:05.340 --> 00:27:05.350 align:start position:0% on your behalf but maybe the protocol 00:27:05.350 --> 00:27:06.930 align:start position:0% on your behalf but maybe the protocol only<00:27:05.650> allows<00:27:05.890> funds<00:27:06.220> to<00:27:06.400> be<00:27:06.490> slashed<00:27:06.730> so 00:27:06.930 --> 00:27:06.940 align:start position:0% only allows funds to be slashed so 00:27:06.940 --> 00:27:08.760 align:start position:0% only allows funds to be slashed so quickly<00:27:07.300> so<00:27:07.450> you<00:27:07.540> can<00:27:07.690> still<00:27:07.929> sort<00:27:08.110> of<00:27:08.230> get 00:27:08.760 --> 00:27:08.770 align:start position:0% quickly so you can still sort of get 00:27:08.770 --> 00:27:10.230 align:start position:0% quickly so you can still sort of get some<00:27:08.980> guarantees<00:27:09.370> by<00:27:09.580> maintaining<00:27:10.030> some<00:27:10.210> sort 00:27:10.230 --> 00:27:10.240 align:start position:0% some guarantees by maintaining some sort 00:27:10.240 --> 00:27:12.360 align:start position:0% some guarantees by maintaining some sort of<00:27:10.450> cold<00:27:10.690> storage<00:27:10.870> and<00:27:11.770> I'm<00:27:11.860> not<00:27:12.010> sure<00:27:12.130> if<00:27:12.250> that 00:27:12.360 --> 00:27:12.370 align:start position:0% of cold storage and I'm not sure if that 00:27:12.370 --> 00:27:13.950 align:start position:0% of cold storage and I'm not sure if that will<00:27:12.520> make<00:27:12.550> it<00:27:12.790> into<00:27:12.910> the<00:27:13.059> final<00:27:13.300> protocol 00:27:13.950 --> 00:27:13.960 align:start position:0% will make it into the final protocol 00:27:13.960 --> 00:27:16.020 align:start position:0% will make it into the final protocol I<00:27:13.990> think<00:27:14.370> preliminary<00:27:15.370> discussions<00:27:15.850> I've<00:27:16.000> had 00:27:16.020 --> 00:27:16.030 align:start position:0% I think preliminary discussions I've had 00:27:16.030 --> 00:27:17.940 align:start position:0% I think preliminary discussions I've had suggested<00:27:16.690> that<00:27:16.750> it<00:27:16.960> might<00:27:17.110> it's<00:27:17.350> kind<00:27:17.740> of<00:27:17.830> an 00:27:17.940 --> 00:27:17.950 align:start position:0% suggested that it might it's kind of an 00:27:17.950 --> 00:27:19.890 align:start position:0% suggested that it might it's kind of an engineering<00:27:18.280> detail<00:27:18.670> but<00:27:18.940> in<00:27:19.120> theory<00:27:19.750> that's 00:27:19.890 --> 00:27:19.900 align:start position:0% engineering detail but in theory that's 00:27:19.900 --> 00:27:21.600 align:start position:0% engineering detail but in theory that's sort<00:27:20.110> of<00:27:20.170> one<00:27:20.350> way<00:27:20.500> to<00:27:20.559> mitigate<00:27:21.190> against 00:27:21.600 --> 00:27:21.610 align:start position:0% sort of one way to mitigate against 00:27:21.610 --> 00:27:24.720 align:start position:0% sort of one way to mitigate against those<00:27:21.820> risks<00:27:22.150> also<00:27:23.010> I'll<00:27:24.010> just<00:27:24.220> say<00:27:24.370> that<00:27:24.580> if 00:27:24.720 --> 00:27:24.730 align:start position:0% those risks also I'll just say that if 00:27:24.730 --> 00:27:26.340 align:start position:0% those risks also I'll just say that if people<00:27:24.910> have<00:27:25.150> detailed<00:27:25.540> technical<00:27:25.750> questions 00:27:26.340 --> 00:27:26.350 align:start position:0% people have detailed technical questions 00:27:26.350 --> 00:27:28.020 align:start position:0% people have detailed technical questions they'd<00:27:26.590> like<00:27:26.620> to<00:27:26.740> get<00:27:26.950> answered<00:27:27.280> by<00:27:27.429> security 00:27:28.020 --> 00:27:28.030 align:start position:0% they'd like to get answered by security 00:27:28.030 --> 00:27:29.310 align:start position:0% they'd like to get answered by security experts<00:27:28.390> they<00:27:28.570> should<00:27:28.750> join<00:27:28.900> some<00:27:29.140> of<00:27:29.230> the 00:27:29.310 --> 00:27:29.320 align:start position:0% experts they should join some of the 00:27:29.320 --> 00:27:30.860 align:start position:0% experts they should join some of the communities<00:27:29.710> that<00:27:29.740> Kevin<00:27:30.160> mentioned<00:27:30.309> before 00:27:30.860 --> 00:27:30.870 align:start position:0% communities that Kevin mentioned before 00:27:30.870 --> 00:27:34.049 align:start position:0% communities that Kevin mentioned before and<00:27:31.870> then<00:27:32.080> I<00:27:32.309> personally<00:27:33.309> trail<00:27:33.640> Abbot's<00:27:33.910> has 00:27:34.049 --> 00:27:34.059 align:start position:0% and then I personally trail Abbot's has 00:27:34.059 --> 00:27:35.640 align:start position:0% and then I personally trail Abbot's has open<00:27:34.450> office<00:27:34.720> hours<00:27:34.990> we<00:27:35.200> run<00:27:35.320> every<00:27:35.559> other 00:27:35.640 --> 00:27:35.650 align:start position:0% open office hours we run every other 00:27:35.650 --> 00:27:37.440 align:start position:0% open office hours we run every other week<00:27:35.890> where<00:27:36.370> people<00:27:36.700> can<00:27:36.820> just<00:27:36.970> engage<00:27:37.270> with 00:27:37.440 --> 00:27:37.450 align:start position:0% week where people can just engage with 00:27:37.450 --> 00:27:39.390 align:start position:0% week where people can just engage with us<00:27:37.600> and<00:27:37.809> pepper<00:27:37.990> us<00:27:38.230> with<00:27:38.350> questions<00:27:38.740> like 00:27:39.390 --> 00:27:39.400 align:start position:0% us and pepper us with questions like 00:27:39.400 --> 00:27:41.970 align:start position:0% us and pepper us with questions like that<00:27:39.610> one<00:27:39.790> and<00:27:40.059> get<00:27:40.710> sophisticated<00:27:41.710> answers 00:27:41.970 --> 00:27:41.980 align:start position:0% that one and get sophisticated answers 00:27:41.980 --> 00:27:43.070 align:start position:0% that one and get sophisticated answers back 00:27:43.070 --> 00:27:43.080 align:start position:0% back 00:27:43.080 --> 00:27:45.570 align:start position:0% back khulus<00:27:44.080> we<00:27:44.200> got<00:27:44.380> about<00:27:44.559> two<00:27:45.130> minutes<00:27:45.250> left 00:27:45.570 --> 00:27:45.580 align:start position:0% khulus we got about two minutes left 00:27:45.580 --> 00:27:47.990 align:start position:0% khulus we got about two minutes left let's<00:27:46.330> come<00:27:46.510> back<00:27:46.540> over<00:27:46.780> to<00:27:46.870> the<00:27:46.960> said<00:27:47.170> hey 00:27:47.990 --> 00:27:48.000 align:start position:0% let's come back over to the said hey 00:27:48.000 --> 00:27:50.370 align:start position:0% let's come back over to the said hey what<00:27:49.000> should<00:27:49.150> be<00:27:49.270> added<00:27:49.750> or<00:27:49.870> changed<00:27:49.900> to<00:27:50.320> the 00:27:50.370 --> 00:27:50.380 align:start position:0% what should be added or changed to the 00:27:50.380 --> 00:27:52.080 align:start position:0% what should be added or changed to the standard<00:27:50.650> development<00:27:51.010> process<00:27:51.370> to<00:27:51.700> enhance 00:27:52.080 --> 00:27:52.090 align:start position:0% standard development process to enhance 00:27:52.090 --> 00:27:54.690 align:start position:0% standard development process to enhance security<00:27:52.690> so<00:27:52.870> it's<00:27:53.290> built<00:27:53.710> in<00:27:53.890> and<00:27:54.160> and 00:27:54.690 --> 00:27:54.700 align:start position:0% security so it's built in and and 00:27:54.700 --> 00:27:56.549 align:start position:0% security so it's built in and and enhanced<00:27:55.690> as<00:27:55.780> much<00:27:55.929> as<00:27:56.080> possible<00:27:56.230> during 00:27:56.549 --> 00:27:56.559 align:start position:0% enhanced as much as possible during 00:27:56.559 --> 00:27:58.710 align:start position:0% enhanced as much as possible during development<00:27:56.880> not<00:27:57.880> including<00:27:58.210> the<00:27:58.299> external 00:27:58.710 --> 00:27:58.720 align:start position:0% development not including the external 00:27:58.720 --> 00:28:03.840 align:start position:0% development not including the external audit<00:27:58.870> something<00:27:59.080> like<00:27:59.230> that<00:28:02.520> yeah<00:28:03.520> I<00:28:03.549> feel 00:28:03.840 --> 00:28:03.850 align:start position:0% audit something like that yeah I feel 00:28:03.850 --> 00:28:05.160 align:start position:0% audit something like that yeah I feel like<00:28:03.970> this<00:28:04.090> is<00:28:04.210> a<00:28:04.240> chance<00:28:04.540> for<00:28:04.630> all<00:28:04.750> of<00:28:04.870> us<00:28:05.020> to 00:28:05.160 --> 00:28:05.170 align:start position:0% like this is a chance for all of us to 00:28:05.170 --> 00:28:08.250 align:start position:0% like this is a chance for all of us to plug<00:28:05.350> our<00:28:05.500> tools<00:28:05.710> here<00:28:06.690> yeah<00:28:07.690> in<00:28:07.840> general<00:28:07.960> I 00:28:08.250 --> 00:28:08.260 align:start position:0% plug our tools here yeah in general I 00:28:08.260 --> 00:28:09.750 align:start position:0% plug our tools here yeah in general I think<00:28:08.470> trying<00:28:08.860> to<00:28:08.950> work<00:28:09.070> out<00:28:09.250> like<00:28:09.490> what<00:28:09.670> are 00:28:09.750 --> 00:28:09.760 align:start position:0% think trying to work out like what are 00:28:09.760 --> 00:28:10.680 align:start position:0% think trying to work out like what are the<00:28:09.820> properties<00:28:10.210> that<00:28:10.240> your<00:28:10.510> code<00:28:10.660> is 00:28:10.680 --> 00:28:10.690 align:start position:0% the properties that your code is 00:28:10.690 --> 00:28:12.720 align:start position:0% the properties that your code is supposed<00:28:11.080> to<00:28:11.170> have<00:28:11.350> and<00:28:11.650> the<00:28:12.100> invariants<00:28:12.610> that 00:28:12.720 --> 00:28:12.730 align:start position:0% supposed to have and the invariants that 00:28:12.730 --> 00:28:14.070 align:start position:0% supposed to have and the invariants that you<00:28:12.790> don't<00:28:12.970> think<00:28:13.150> should<00:28:13.270> ever<00:28:13.450> be<00:28:13.630> violated 00:28:14.070 --> 00:28:14.080 align:start position:0% you don't think should ever be violated 00:28:14.080 --> 00:28:16.280 align:start position:0% you don't think should ever be violated about<00:28:14.290> it<00:28:14.440> are<00:28:14.679> kind<00:28:15.100> of<00:28:15.220> a<00:28:15.280> good<00:28:15.460> first<00:28:15.669> step 00:28:16.280 --> 00:28:16.290 align:start position:0% about it are kind of a good first step 00:28:16.290 --> 00:28:18.659 align:start position:0% about it are kind of a good first step you<00:28:17.290> know<00:28:17.410> we<00:28:17.830> have<00:28:17.950> a<00:28:17.980> wealth<00:28:18.280> of<00:28:18.460> tools 00:28:18.659 --> 00:28:18.669 align:start position:0% you know we have a wealth of tools 00:28:18.669 --> 00:28:21.240 align:start position:0% you know we have a wealth of tools available<00:28:18.850> now<00:28:19.270> we<00:28:19.330> mentioned<00:28:19.690> in<00:28:20.410> 2018<00:28:21.100> that 00:28:21.240 --> 00:28:21.250 align:start position:0% available now we mentioned in 2018 that 00:28:21.250 --> 00:28:22.680 align:start position:0% available now we mentioned in 2018 that we<00:28:21.309> didn't<00:28:21.490> have<00:28:21.610> last<00:28:21.790> year<00:28:22.090> we<00:28:22.240> have<00:28:22.360> static 00:28:22.680 --> 00:28:22.690 align:start position:0% we didn't have last year we have static 00:28:22.690 --> 00:28:24.750 align:start position:0% we didn't have last year we have static analyzers<00:28:23.200> that<00:28:23.470> pick<00:28:24.070> out<00:28:24.220> examples<00:28:24.669> of 00:28:24.750 --> 00:28:24.760 align:start position:0% analyzers that pick out examples of 00:28:24.760 --> 00:28:27.060 align:start position:0% analyzers that pick out examples of incorrect<00:28:25.240> code<00:28:25.480> but<00:28:26.290> we<00:28:26.380> also<00:28:26.530> have<00:28:26.799> tools 00:28:27.060 --> 00:28:27.070 align:start position:0% incorrect code but we also have tools 00:28:27.070 --> 00:28:28.680 align:start position:0% incorrect code but we also have tools that<00:28:27.250> allow<00:28:27.549> you<00:28:27.610> to<00:28:27.730> prove<00:28:28.000> properties<00:28:28.480> about 00:28:28.680 --> 00:28:28.690 align:start position:0% that allow you to prove properties about 00:28:28.690 --> 00:28:31.560 align:start position:0% that allow you to prove properties about your<00:28:28.840> own<00:28:28.960> code<00:28:29.490> so<00:28:30.490> like<00:28:30.640> at<00:28:31.059> a<00:28:31.090> basic<00:28:31.419> level 00:28:31.560 --> 00:28:31.570 align:start position:0% your own code so like at a basic level 00:28:31.570 --> 00:28:33.390 align:start position:0% your own code so like at a basic level you<00:28:31.720> should<00:28:31.870> be<00:28:32.049> running<00:28:32.200> static<00:28:32.980> analysis 00:28:33.390 --> 00:28:33.400 align:start position:0% you should be running static analysis 00:28:33.400 --> 00:28:35.370 align:start position:0% you should be running static analysis tools<00:28:33.640> and<00:28:33.940> bug<00:28:34.240> finding<00:28:34.600> tools<00:28:34.809> like<00:28:35.110> slither 00:28:35.370 --> 00:28:35.380 align:start position:0% tools and bug finding tools like slither 00:28:35.380 --> 00:28:37.500 align:start position:0% tools and bug finding tools like slither or<00:28:35.620> mythril<00:28:35.980> early<00:28:36.940> on<00:28:37.059> in<00:28:37.240> the<00:28:37.299> development 00:28:37.500 --> 00:28:37.510 align:start position:0% or mythril early on in the development 00:28:37.510 --> 00:28:39.990 align:start position:0% or mythril early on in the development cycle<00:28:37.950> you<00:28:38.950> should<00:28:39.130> be<00:28:39.220> thinking<00:28:39.610> about<00:28:39.669> what 00:28:39.990 --> 00:28:40.000 align:start position:0% cycle you should be thinking about what 00:28:40.000 --> 00:28:42.260 align:start position:0% cycle you should be thinking about what kinds<00:28:40.270> of<00:28:40.330> properties<00:28:40.540> the<00:28:41.500> spec<00:28:41.860> or 00:28:42.260 --> 00:28:42.270 align:start position:0% kinds of properties the spec or 00:28:42.270 --> 00:28:43.980 align:start position:0% kinds of properties the spec or invariants<00:28:43.270> that<00:28:43.419> you'd<00:28:43.510> like<00:28:43.660> your<00:28:43.780> code<00:28:43.960> to 00:28:43.980 --> 00:28:43.990 align:start position:0% invariants that you'd like your code to 00:28:43.990 --> 00:28:46.169 align:start position:0% invariants that you'd like your code to hold<00:28:44.290> and<00:28:44.500> then<00:28:44.980> using<00:28:45.280> tools<00:28:45.520> like<00:28:45.640> a<00:28:45.760> kid<00:28:46.030> 'no 00:28:46.169 --> 00:28:46.179 align:start position:0% hold and then using tools like a kid 'no 00:28:46.179 --> 00:28:48.510 align:start position:0% hold and then using tools like a kid 'no Manticore<00:28:46.780> or<00:28:47.020> k<00:28:47.230> to<00:28:47.830> actually<00:28:48.190> prove<00:28:48.490> that 00:28:48.510 --> 00:28:48.520 align:start position:0% Manticore or k to actually prove that 00:28:48.520 --> 00:28:50.580 align:start position:0% Manticore or k to actually prove that those<00:28:48.850> properties<00:28:49.330> hold<00:28:49.510> for<00:28:50.230> all<00:28:50.290> the<00:28:50.410> cases 00:28:50.580 --> 00:28:50.590 align:start position:0% those properties hold for all the cases 00:28:50.590 --> 00:28:52.860 align:start position:0% those properties hold for all the cases you<00:28:50.830> think<00:28:51.010> they<00:28:51.100> do<00:28:51.390> and<00:28:52.390> then<00:28:52.540> you<00:28:52.630> should<00:28:52.720> be 00:28:52.860 --> 00:28:52.870 align:start position:0% you think they do and then you should be 00:28:52.870 --> 00:28:55.890 align:start position:0% you think they do and then you should be engaging<00:28:53.110> with<00:28:53.320> experts<00:28:53.740> to<00:28:53.860> think<00:28:54.270> like<00:28:55.270> you 00:28:55.890 --> 00:28:55.900 align:start position:0% engaging with experts to think like you 00:28:55.900 --> 00:28:59.430 align:start position:0% engaging with experts to think like you know<00:28:55.990> in<00:28:56.950> an<00:28:57.309> adversarial<00:28:57.880> fashion<00:28:58.330> about<00:28:59.049> how 00:28:59.430 --> 00:28:59.440 align:start position:0% know in an adversarial fashion about how 00:28:59.440 --> 00:29:00.960 align:start position:0% know in an adversarial fashion about how the<00:28:59.500> environment<00:28:59.890> that<00:29:00.250> you're<00:29:00.370> executing<00:29:00.640> in 00:29:00.960 --> 00:29:00.970 align:start position:0% the environment that you're executing in 00:29:00.970 --> 00:29:02.700 align:start position:0% the environment that you're executing in can<00:29:01.179> affect<00:29:01.450> that<00:29:01.570> contract<00:29:02.020> so<00:29:02.290> like<00:29:02.530> whether 00:29:02.700 --> 00:29:02.710 align:start position:0% can affect that contract so like whether 00:29:02.710 --> 00:29:05.490 align:start position:0% can affect that contract so like whether you<00:29:02.860> can<00:29:02.950> be<00:29:03.070> front<00:29:03.280> run<00:29:03.429> or<00:29:03.549> not<00:29:03.809> and<00:29:04.809> then 00:29:05.490 --> 00:29:05.500 align:start position:0% you can be front run or not and then 00:29:05.500 --> 00:29:09.780 align:start position:0% you can be front run or not and then also<00:29:06.240> whether<00:29:07.240> there<00:29:07.480> are<00:29:07.600> ways<00:29:07.780> for<00:29:08.790> people 00:29:09.780 --> 00:29:09.790 align:start position:0% also whether there are ways for people 00:29:09.790 --> 00:29:13.320 align:start position:0% also whether there are ways for people to<00:29:10.320> work<00:29:11.320> within<00:29:11.530> your<00:29:11.740> system<00:29:12.100> to<00:29:12.850> collect 00:29:13.320 --> 00:29:13.330 align:start position:0% to work within your system to collect 00:29:13.330 --> 00:29:15.030 align:start position:0% to work within your system to collect you<00:29:13.540> know<00:29:13.570> tokens<00:29:14.049> or<00:29:14.200> incentives<00:29:14.799> and 00:29:15.030 --> 00:29:15.040 align:start position:0% you know tokens or incentives and 00:29:15.040 --> 00:29:17.730 align:start position:0% you know tokens or incentives and produce<00:29:15.730> suboptimal<00:29:16.120> results<00:29:16.750> and 00:29:17.730 --> 00:29:17.740 align:start position:0% produce suboptimal results and 00:29:17.740 --> 00:29:19.289 align:start position:0% produce suboptimal results and eventually<00:29:18.190> just<00:29:18.309> you<00:29:18.549> know<00:29:18.640> degrade<00:29:19.150> the 00:29:19.289 --> 00:29:19.299 align:start position:0% eventually just you know degrade the 00:29:19.299 --> 00:29:20.460 align:start position:0% eventually just you know degrade the effectiveness<00:29:19.720> of<00:29:19.960> whatever<00:29:20.140> the 00:29:20.460 --> 00:29:20.470 align:start position:0% effectiveness of whatever the 00:29:20.470 --> 00:29:21.870 align:start position:0% effectiveness of whatever the decentralized<00:29:21.010> system<00:29:21.309> it<00:29:21.429> is<00:29:21.549> that<00:29:21.790> you've 00:29:21.870 --> 00:29:21.880 align:start position:0% decentralized system it is that you've 00:29:21.880 --> 00:29:24.450 align:start position:0% decentralized system it is that you've created<00:29:22.799> those<00:29:23.799> are<00:29:23.950> some<00:29:24.070> things<00:29:24.220> that<00:29:24.429> I 00:29:24.450 --> 00:29:24.460 align:start position:0% created those are some things that I 00:29:24.460 --> 00:29:25.890 align:start position:0% created those are some things that I think<00:29:24.730> I<00:29:24.790> would<00:29:24.850> think<00:29:25.090> about<00:29:25.179> if<00:29:25.540> you<00:29:25.660> want<00:29:25.840> to 00:29:25.890 --> 00:29:25.900 align:start position:0% think I would think about if you want to 00:29:25.900 --> 00:29:28.190 align:start position:0% think I would think about if you want to end<00:29:26.049> up<00:29:26.140> with<00:29:26.260> a<00:29:26.429> good<00:29:27.429> product<00:29:27.640> at<00:29:27.850> the<00:29:27.940> end 00:29:28.190 --> 00:29:28.200 align:start position:0% end up with a good product at the end 00:29:28.200 --> 00:29:30.810 align:start position:0% end up with a good product at the end right<00:29:29.200> a<00:29:29.260> damn<00:29:29.679> spec<00:29:30.040> please<00:29:30.400> because 00:29:30.810 --> 00:29:30.820 align:start position:0% right a damn spec please because 00:29:30.820 --> 00:29:32.760 align:start position:0% right a damn spec please because otherwise<00:29:31.120> we<00:29:31.660> can<00:29:32.200> have<00:29:32.380> no<00:29:32.590> way<00:29:32.710> to 00:29:32.760 --> 00:29:32.770 align:start position:0% otherwise we can have no way to 00:29:32.770 --> 00:29:34.380 align:start position:0% otherwise we can have no way to understand<00:29:33.370> what<00:29:33.700> you<00:29:33.850> think<00:29:34.179> you're 00:29:34.380 --> 00:29:34.390 align:start position:0% understand what you think you're 00:29:34.390 --> 00:29:36.299 align:start position:0% understand what you think you're building<00:29:34.780> so<00:29:35.169> write<00:29:35.440> a<00:29:35.470> spec<00:29:35.770> and<00:29:35.799> make<00:29:36.100> it<00:29:36.190> as 00:29:36.299 --> 00:29:36.309 align:start position:0% building so write a spec and make it as 00:29:36.309 --> 00:29:38.700 align:start position:0% building so write a spec and make it as formal<00:29:36.640> as<00:29:36.730> possible<00:29:37.210> yeah<00:29:37.870> yeah<00:29:38.559> I<00:29:38.590> also 00:29:38.700 --> 00:29:38.710 align:start position:0% formal as possible yeah yeah I also 00:29:38.710 --> 00:29:40.860 align:start position:0% formal as possible yeah yeah I also again<00:29:38.980> write<00:29:39.400> a<00:29:39.429> spec<00:29:39.760> write<00:29:40.120> a<00:29:40.150> lot<00:29:40.480> of<00:29:40.600> specs 00:29:40.860 --> 00:29:40.870 align:start position:0% again write a spec write a lot of specs 00:29:40.870 --> 00:29:42.539 align:start position:0% again write a spec write a lot of specs write<00:29:41.140> specs<00:29:41.440> every<00:29:41.770> time<00:29:41.890> your<00:29:42.040> code<00:29:42.190> changes 00:29:42.539 --> 00:29:42.549 align:start position:0% write specs every time your code changes 00:29:42.549 --> 00:29:45.360 align:start position:0% write specs every time your code changes and<00:29:42.760> also<00:29:43.500> code<00:29:44.500> review<00:29:44.799> with<00:29:45.040> each<00:29:45.160> other 00:29:45.360 --> 00:29:45.370 align:start position:0% and also code review with each other 00:29:45.370 --> 00:29:46.770 align:start position:0% and also code review with each other make<00:29:45.700> sure<00:29:45.730> everyone's<00:29:46.390> on<00:29:46.480> the<00:29:46.600> same<00:29:46.630> page 00:29:46.770 --> 00:29:46.780 align:start position:0% make sure everyone's on the same page 00:29:46.780 --> 00:29:49.380 align:start position:0% make sure everyone's on the same page about<00:29:47.110> what<00:29:47.410> your<00:29:47.530> code<00:29:47.740> does<00:29:48.010> the<00:29:48.580> like<00:29:49.030> huge 00:29:49.380 --> 00:29:49.390 align:start position:0% about what your code does the like huge 00:29:49.390 --> 00:29:51.000 align:start position:0% about what your code does the like huge amounts<00:29:49.809> of<00:29:49.840> security<00:29:50.230> issues<00:29:50.290> come<00:29:50.710> from<00:29:50.919> the 00:29:51.000 --> 00:29:51.010 align:start position:0% amounts of security issues come from the 00:29:51.010 --> 00:29:52.409 align:start position:0% amounts of security issues come from the fact<00:29:51.220> that<00:29:51.309> just<00:29:51.790> people<00:29:52.030> are<00:29:52.090> not<00:29:52.240> on<00:29:52.330> the 00:29:52.409 --> 00:29:52.419 align:start position:0% fact that just people are not on the 00:29:52.419 --> 00:29:56.430 align:start position:0% fact that just people are not on the same<00:29:52.540> page<00:29:54.510> yeah<00:29:55.510> so 00:29:56.430 --> 00:29:56.440 align:start position:0% same page yeah so 00:29:56.440 --> 00:30:00.930 align:start position:0% same page yeah so thrill<00:29:56.650> me<00:29:56.860> throw<00:29:57.100> me<00:29:57.250> through<00:29:57.370> mithril<00:29:59.940> you 00:30:00.930 --> 00:30:00.940 align:start position:0% thrill me throw me through mithril you 00:30:00.940 --> 00:30:02.430 align:start position:0% thrill me throw me through mithril you should<00:30:01.150> run<00:30:01.300> it<00:30:01.480> you<00:30:01.690> should<00:30:01.840> also<00:30:01.990> run<00:30:02.230> his 00:30:02.430 --> 00:30:02.440 align:start position:0% should run it you should also run his 00:30:02.440 --> 00:30:05.040 align:start position:0% should run it you should also run his run<00:30:03.130> a<00:30:03.190> linter<00:30:03.580> I<00:30:03.790> really<00:30:04.180> like<00:30:04.330> solium<00:30:04.810> and 00:30:05.040 --> 00:30:05.050 align:start position:0% run a linter I really like solium and 00:30:05.050 --> 00:30:06.960 align:start position:0% run a linter I really like solium and like<00:30:05.320> if<00:30:05.500> you<00:30:05.620> if<00:30:05.920> it's<00:30:06.040> enforcing<00:30:06.640> like<00:30:06.790> some 00:30:06.960 --> 00:30:06.970 align:start position:0% like if you if it's enforcing like some 00:30:06.970 --> 00:30:09.660 align:start position:0% like if you if it's enforcing like some reasonable<00:30:07.510> code<00:30:07.750> style<00:30:08.380> that<00:30:08.830> goes<00:30:09.340> much 00:30:09.660 --> 00:30:09.670 align:start position:0% reasonable code style that goes much 00:30:09.670 --> 00:30:11.550 align:start position:0% reasonable code style that goes much further<00:30:09.910> than<00:30:10.180> you<00:30:10.300> might<00:30:10.450> think 00:30:11.550 --> 00:30:11.560 align:start position:0% further than you might think 00:30:11.560 --> 00:30:14.340 align:start position:0% further than you might think right<00:30:12.460> a<00:30:12.490> lot<00:30:12.670> of<00:30:12.760> tests<00:30:13.210> ideally<00:30:13.720> write<00:30:13.900> write 00:30:14.340 --> 00:30:14.350 align:start position:0% right a lot of tests ideally write write 00:30:14.350 --> 00:30:16.110 align:start position:0% right a lot of tests ideally write write a<00:30:14.380> spec<00:30:14.710> and<00:30:14.920> then<00:30:15.010> write<00:30:15.250> tests<00:30:15.760> and<00:30:15.970> then 00:30:16.110 --> 00:30:16.120 align:start position:0% a spec and then write tests and then 00:30:16.120 --> 00:30:21.180 align:start position:0% a spec and then write tests and then write<00:30:16.810> the<00:30:17.050> code<00:30:17.260> that<00:30:17.530> does<00:30:17.590> the<00:30:17.950> thing<00:30:20.190> yeah 00:30:21.180 --> 00:30:21.190 align:start position:0% write the code that does the thing yeah 00:30:21.190 --> 00:30:23.160 align:start position:0% write the code that does the thing yeah that's<00:30:21.580> I<00:30:21.940> don't<00:30:22.270> have<00:30:22.420> anything<00:30:22.660> to<00:30:22.780> add<00:30:22.900> at 00:30:23.160 --> 00:30:23.170 align:start position:0% that's I don't have anything to add at 00:30:23.170 --> 00:30:23.910 align:start position:0% that's I don't have anything to add at this<00:30:23.350> time 00:30:23.910 --> 00:30:23.920 align:start position:0% this time 00:30:23.920 --> 00:30:25.710 align:start position:0% this time awesome<00:30:24.370> and<00:30:24.640> that<00:30:24.970> is<00:30:25.120> all<00:30:25.240> the<00:30:25.300> time<00:30:25.360> we<00:30:25.570> have 00:30:25.710 --> 00:30:25.720 align:start position:0% awesome and that is all the time we have 00:30:25.720 --> 00:30:27.810 align:start position:0% awesome and that is all the time we have so<00:30:26.020> thank<00:30:26.200> you<00:30:26.290> all<00:30:26.380> for<00:30:26.500> being<00:30:26.590> here<00:30:26.830> and<00:30:26.980> I 00:30:27.810 --> 00:30:27.820 align:start position:0% so thank you all for being here and I 00:30:27.820 --> 00:30:28.980 align:start position:0% so thank you all for being here and I think<00:30:28.000> we're<00:30:28.090> gonna<00:30:28.180> have<00:30:28.360> Hudson<00:30:28.600> come<00:30:28.870> back 00:30:28.980 --> 00:30:28.990 align:start position:0% think we're gonna have Hudson come back 00:30:28.990 --> 00:30:43.120 align:start position:0% think we're gonna have Hudson come back out<00:30:29.140> and<00:30:29.260> close<00:30:29.440> this<00:30:29.530> out<00:30:29.710> these<00:30:30.580> guys 00:30:43.120 --> 00:30:43.130 align:start position:0% 00:30:43.130 --> 00:30:45.190 align:start position:0% you